Posts made by ReVeRb

@dc42

Ok, sorry for the delay. I had a lot of stuff going on, but I came back to say that it work like a charm.

I ordered the thermocoupler you mentioned and instead of passing it's wire in the looming with all other wire, I decided to install it in parallel.(didn't take a chance)

It work amazingly well to be honest, the reading is spot on and precise.

Thanks.

By the way, I don't know how to tag this post as "solved". Can you explain it to me so I can do it. ?

Big thanks dc42, your help is always efficient!!

@dc42

I was having spike all around, so I changed the entire wire for an insulated wire (strainless braided). Which mean, from the thermocoupler to the effector, it's a k-type, stainless braided wire and from the effector to the Duet2, same thing. I still have spike all around.

I've checked the isolation of the thermocouple from it's casing and there is continuity, which mean the probe inside the casing is touching the case... isn't supposed to be like that to allow thermal transfer(since air is an isolation by itself).

I've tested an other model of K-type thermocoupler and it also has the same conductivity between the thermocouple and it's casing. Isn't normal?

What should I expect it to be ?

Is there a model you can recommend that is electricaly isolated ?

Note that my printer is a Delta, with a semi-floading stepper for the extruder. And the signal that "pollute" my thermocoupler is when there is a retraction/pression of that stepper, so I pick-up the magnetic flux from it's wiring, despite the fact that all the wiring of the thermocouple is stainless braided.

Also, starting the heatsink fan or the cooling fan doesn't create spike, neither the heater (I've tested them all), which lead me to ask: If all these doesn't interfere with the thermocoupler (specially the heater), how can the thermocoupler(non-isolated) be affected by the extruder stepper and not by the heater nor the fans ?

I'll try to remove the thermocouple wire from the sleeve spiral wrap and see if it pick up the stepper signal again, if so, maybe it pick up electromagnetic flux from the motherboard ? <-- is that even possible ?

Sorry for the long text, I shoot in every direction, trying to figure out the cause...

Any input/advice are welcomed!

Side note: I finished a print of 3h30 and have no problem. There was spike(+/- 45 to 60sec interval), more or less, but still I was able to print and the temp was always spot on (+/- 0,3 °C), which is "normal" for me condition here.

@ReVeRb Hi dc42, glad to hear from you!

I finally get the board. it's tiny, but I can read on the back:

MAXTempTC v0.2
K Thermocouple Board
Design by: ...
...
...
www.Duet3d.com

So I assume it's a OEM part, is that correct ?

If so, since it's the v0.2 I can assume the capacitors are already on it, is that correct ?

I joined a photo of it.

Should I consider adding a shield too or is it enough to deal with the problem ? The thermocoupler will have approximately 2 inch(or more) of distance mostly everywhere. Except from the thermocouple to the connexion(under the effector) but this part is shilded.

Hi everyone, hope your doing great!!

I've been given a thermocoupler K1000, with what appear to be a third-party board or maybe the board is simply old? I dunno, but it is supposed to work, which is the important part!! I should receive it in few days so I'll be able to confirm the board model then. Anyway, I proactively did some research and found all the information I needed, except one thing about the capacitor...

Here, dc42(administrator) said in 2017: " The mod consists of adding a 0.01uF ceramic capacitor between each thermocouple terminal and ground."

https://forum.duet3d.com/topic/1270/thermocouple-issues/13

And by searching more, I found that one: "If you purchased a third-party thermocouple interface board, check that there is a 10nF or greater capacitor in parallel with the thermocouple terminals."

https://docs.duet3d.com/User_manual/Connecting_hardware/Temperature_connecting_thermocouples

If the board is a Duet, I assume it will have the capacitor. Or maybe not... In any case, I'll look for them on the board and if they aren't, here come my question:

Does a 0,1uf would do the trick ? dc42 suggest a 0,01uf(10nf) and in the manual it is recommended to install a capacitor with "at least" 0,01uf, which open the door to a bigger one, but how much bigger is my main concern.

I already have plenty of common 104 ceramic capacitor on hand(0,1uf) and few 103Z(0,01uf), but they are +80%/-20% tolerance and I don't know if they would be good enough for such application.

Any info or input would be greatly appreciated

thanks

@dc42 Ok, it's been a while, but I finally had the time to build the PCB capacitor bank and install it. It work good and I have approx. 1.5 - 2 sec. before the board shut down.

I'm not sure I understand how to implement it in the firmware, neither how to program it for my needs and limitations...

This is the code provided on the documentation:
M911 S21.0 R23.0 P"M913 X0 Y0 G91 M83 G1 Z3 E-5 F1000"

As far as I understand, I simply copy that line of code info config.g and configure it for my needs?

I have a Delta, with a 12V setup pushing around 13.5V... so it would be:
M911 S12 R13 P"M913 X100 Y100 Z100 M83 G1 Z3 E-5 F1000

Which would raise the nozzle 3mm from it's actual position and retract 5mm all motors(X,Y,Z,E0) at F1000 speed right after it detect a power outage ?

Then it will save the position ?

Does it have to home before it save ? If not, can it just raise the nozzle and retract a bit, then save the position... And when the power is back, I simply home the printer and re-launch the print and it will move where is stopped ?

I don't understand very well how the whole process work all together to be honest and some explanation is welcome!!

@dc42

Yes, my PSU have a potentiometer to adjust the voltage. As for the maximum rating when everything is turned on, I have no certainty, just a vague idea...

Duet2 board: 12V, 0,5W
Panel Due: ??
Heat bed: 12V, 120W
Heating cartridge for the nozzle: 12V, 70W
stepper(extruder): 600mA max
stepper(x,y,z): 800mA max each.
1 fan: 5V 0.15A

I doubt I'm over 20Amp max... I have plenty of room.

So I could just connect my capacitor in parallel to reach 20 000uF, and install the capacitor apparatus in parallel with the PSU and I should be fine ? I just want to be 1000% sure that I won't create a ShortCircuit to the PSU because I have no idea if the PSU has a SC protection and I'm too low on a budget to buy a replacement.

About the ESR. On the other post, it is mentioned that low ESR cap draw a lot of current from the PSU and the more cap. are connected in parallel, the higher the current draw is... I though the Rippler Current spec was the max current draw of the cap, but apparently no. How to I determine that ? (I just like to validate as much as I can with some formula before I solder anything in place).

How does turning the PSU voltage up will affect the setup? The potential difference will increase, passing from 4V =(10.5V to 6.5v) to 6V = (12.5V to 6.5V), so the delay before everything shut down will increase a bit. On the other hand, that's the reason I bought 2x 10 000uF. I though that it would be well sufficient to add some delay while staying at 12V+/-5% on my PSU...

What is the main advantage of raising the PSU voltage slightly ? How will it affect the 5v supply from the Duet board ? Does anyone tried that 14V supply instead of 12V and if so, how does that affected your bead heater, your heating cartridge, fans, etc.

Thank you guys

Re: [Resume from power outage](really only with 24V?)

I recently faced an unpleasant situation like many of you... A 3 day print that ended after 2 and a half days due to a loss of electricity...

So I decided to consult the information on the forum to add capacitors on my 12v setup.

Being on low budget, I acquired 2x 10,000uF 25V, low ESR, Ripple current:2.9A@120Hz-3.335A@10kHz. and will salvage other parts from different electronic part I already recycled/ kept in a box (like the resistor if needed).

I saw this post and inspired myself from it:

https://forum.duet3d.com/topic/19468/resume-from-power-outage-really-only-with-24v/57?_=1658360305205

But, I don't know how to properly install everything(which configuration to be optimal for my setup) to avoid burning my PSU (Chinese 12v 360W, 30A).

Also, I'm in no way an engineer and only have basic technical knowledge of electricity, but capacitors is out of my knowledge so I double checked and the first formula seems to be wrong. Isn't C=Q/V instead of C=Q*V ?

In the post, they talk about the ESR, I have no idea what it represent nor how it work in my case. As I understand it from the reading, if I connect my capacitors in parallel, the low ESR of my capacitors will play a significant role, but I don't understand how to determine if I'm "ok" or not, if I absolutely need a resistor or not and if I do, which kind...

How to I determine the proper resistance value I need to add in series with the capacitor. Anyone have a formula, maybe?

As far as I understand it:

With 2x 10 000uF capacitor. I could store plenty of energy, enough to save on the sdcard, that's for sure, but could I also be able to move the nozzle away (assuming that cooling fan, the bead and nozzle heater are shut down, and maybe even the nozzle fan).

Thank you guys

I tried 800, 700, 600, they all are worst... 550 just get slightly better with a peak at 65%, but the fan stop passed 90% and the second serie I tested is at 450, 430, 480, 470 the fan try to kick-in if I jump from 0% to 100% but the fan just "wiggle" a bit and stop after 2 sec. Also, the fan power is way weaker at any level... but it will kick-in if I jump from standstill to 99%... not at 100%...

What are the frequency range I can work with without damaging the fan or the motherboard ?

-EDIT- I also tested 525 and get the highest peak at 60%, with the same symptoms... from 0 to 99%, the fan kick-in but is weak... from 0-100% it just "wiggle".

-EDIT 2- I also tested 1000 and beside having a fan blowing even harder on the whole spectrum until 60-65%, I have the same behavior overall. At 1% we clearly hear the high pitch frequency noise from the fan. The noise is lesser the closer to 60-65% I get... passed 70% we clearly hear the bearing rattling... passed 80% the performance drop significantly... at 0-100% the fan wiggle again, but wont kick-in and at 0-99% is will start but the air flow is weaker as usual...

Did the same test at 2000Hz... same result but a slightly higher flow between 0 to 60-65%, weaker flow passed 70-75%, the bearing rattle is stronger and the initial high pitch sound is slightly stronger...

I guess that if I keep raising the Hz, I'll just damage/destroy the fans...

So what is my solution?

Is there a way to set the maximum fan speed to 60% for the PID calibration?

@phaedrux Sorry for the delay...

I did all the verification/calibration except one and everything is mostly the same. The only problem remaining (I had it before) is that when I calibrate the nozzle heater as a tool, the cooling fan never turn on. The walk around I used last year was to manually start the cooling fan during the PID calibration.

Known issue with cooling fan: 60% is the real maximum speed. From standstill jump to 100%, the fan just don't kick-in... From standstill jump to 60%, the fan will kick-in... If the fan is running already, it will increase in speed until around 60%(like it should do), then the higher I go(passed the 60% limit), the slower it get... At 100%, it's like being at around 20%-25%? (hard to tell, but it's definitely slower). If I jump from anything lower than 80% to 100%, the fan will stop spinning(I didn't test higher than 85%)... The only way to reach 100%, is to slowly increase, wait a bit, and repeat... Maybe that's the reason why the fan never spin during the PID sequence ?

For info: I connected 2x 3031 5v fan in parallel.

@phaedrux config.g

Also, my bowden is around 210mm long, straight... and the pressure advance need to be set way out of the parameters suggested in the instruction provided on duet3d.

The Bowden setup is made from a PTFE tube and a BMG clone, suspended by a gt2 strap. There is no bent or curvature on the PTFE...

Before it start acting crazy, I normally used (as you can see in the config file) a way lower step/mm for the extruder...

But I now have to use a way higher e-step/mm, otherwise, I'm under-extruding.

I have absolutely no clue what is suddenly happening to my printer. I worked on machine for more than 10 years of my life as an electro-technician of automated system and built myself 2 delta printer and never had this kind of randomized/weird behavior from a machine. I know it's not the case, but I felt like I was working with the machine and someone was reprogramming it every night...

I'm clueless and I ran out of expertise.

Hi everyone,

Recently(ish), for no apparent reason, my printer seem to be hunted and act randomly... I never ever had such problem before. It started to do that last year by randomly doing random stuff here and there, but it wasn't very often and I believed it was related to some glitch introduced by the different processes, slicing, ethernet connexion packet, or anything I just don't know what could do that... A few month back, it happened 25% of the time... I tried to found the problem, without success, so I decided to put the printer aside and search a bit more before using it again. I decided to give it a try recently, because you know, having a printer sitting there doing nothing is just a nonsense to be, so yeah, I started to model and print again... But, and it get worst... For now, 50% of the time, the printer now act randomly... It throw me heating error for no reason(it just stop reading the thermistor)then start again(Yes I recalibrated the PID so many time, changed the thermistor, even the wiring)... Or, when I pause/cancel a print and try to home, one of the motor may randomly stop and since I have a quite tall delta printer, it cause the effector to move very far from the bed radius and snap the magball or hit the box wall or any unwanted s**t that could break. An other one is the random inaccuracy of the babystep. Sometime it is considered, sometime it is not, sometime the nozzle will crashed in the bed. (It didn't do that before last year, but since last year, I normally have to set -0.05 to -0.1 on baby step to have a proper bed adhesion) It's like after the auto calibration, the printer set itself short... But as I said, randomly, it use the proper height(the real one) and it caused to crash in the bed(-0.05 to -0.1mm)...

I'm using the same slicer as before, nothing had changed anywhere, same computer... But the printer just started to act weirdly. I'm seriously out of ideas... It ALL started to happen last year, about a year after I acquired all the Duet hardware I'm using and it just get worst overtime, slowly... Now I don't even dare to leave the printer for 5 minutes...

Here my info:

M122
=== Diagnostics ===
RepRapFirmware for Duet 2 WiFi/Ethernet version 3.3 (2021-06-15 21:44:54) running on Duet Ethernet 1.02 or later
Board ID: 0JD0M-9P6B2-NJ4S8-6J1FJ-3SJ6L-T84LK
Used output buffers: 1 of 24 (13 max)
=== RTOS ===
Static ram: 23876
Dynamic ram: 70020 of which 0 recycled
Never used RAM 20520, free system stack 116 words
Tasks: NETWORK(ready,28.7%,233) HEAT(delaying,0.0%,330) Move(notifyWait,0.1%,303) MAIN(running,70.9%,420) IDLE(ready,0.2%,29), total 100.0%
Owned mutexes:
=== Platform ===
Last reset 00:07:37 ago, cause: software
Last software reset at 2022-06-13 15:52, reason: User, GCodes spinning, available RAM 20520, slot 2
Software reset code 0x0003 HFSR 0x00000000 CFSR 0x00000000 ICSR 0x0041f000 BFAR 0xe000ed38 SP 0x00000000 Task MAIN Freestk 0 n/a
Error status: 0x00
Aux0 errors 0,0,0
Step timer max interval 0
MCU temperature: min 34.6, current 34.7, max 35.5
Supply voltage: min 11.8, current 12.2, max 12.3, under voltage events: 0, over voltage events: 0, power good: yes
Heap OK, handles allocated/used 0/0, heap memory allocated/used/recyclable 0/0/0, gc cycles 0
Driver 0: position 52885, standstill, SG min/max 0/393
Driver 1: position 52885, standstill, SG min/max 0/377
Driver 2: position 52885, standstill, SG min/max 0/1023
Driver 3: position 0, standstill, SG min/max 0/621
Driver 4: position 0, standstill, SG min/max not available
Driver 5: position 0
Driver 6: position 0
Driver 7: position 0
Driver 8: position 0
Driver 9: position 0
Driver 10: position 0
Driver 11: position 0
Date/time: 2022-06-13 16:00:12
Cache data hit count 4294967295
Slowest loop: 136.17ms; fastest: 0.12ms
I2C nak errors 0, send timeouts 0, receive timeouts 0, finishTimeouts 0, resets 0
=== Storage ===
Free file entries: 10
SD card 0 detected, interface speed: 20.0MBytes/sec
SD card longest read time 3.9ms, write time 4.6ms, max retries 0
=== Move ===
DMs created 83, maxWait 41115ms, bed compensation in use: none, comp offset 0.000
=== MainDDARing ===
Scheduled moves 237, completed moves 237, hiccups 0, stepErrors 0, LaErrors 0, Underruns [0, 0, 0], CDDA state -1
=== AuxDDARing ===
Scheduled moves 0, completed moves 0, hiccups 0, stepErrors 0, LaErrors 0, Underruns [0, 0, 0], CDDA state -1
=== Heat ===
Bed heaters = 0 -1 -1 -1, chamberHeaters = -1 -1 -1 -1
Heater 0 is on, I-accum = 0.1
Heater 1 is on, I-accum = 0.2
=== GCodes ===
Segments left: 0
Movement lock held by null
HTTP is idle in state(s) 0
Telnet is idle in state(s) 0
File is idle in state(s) 0
USB is idle in state(s) 0
Aux is idle in state(s) 0
Trigger is idle in state(s) 0
Queue is idle in state(s) 0
LCD is idle in state(s) 0
Daemon is idle in state(s) 0
Autopause is idle in state(s) 0
Code queue is empty.
=== Network ===
Slowest loop: 140.37ms; fastest: 0.02ms
Responder states: HTTP(0) HTTP(0) HTTP(0) HTTP(0) FTP(0) Telnet(0), 0 sessions
HTTP sessions: 1 of 8
Interface state active, link 100Mbps full duplex

@dc42 Thank you everyone for your help !

@dc42 done, I changed them to 1.0, and it solved the problem !

How do I tag as "solved" ?

@phaedrux Here, manually tested all endstops, homed, send M119 to show they are all actiavted, sent a G32, then M500.

Start to read from bottom , sorry.

8/18/2021, 5:27:17 PM M500
8/18/2021, 5:27:11 PM G32
Calibrated 6 factors using 10 points, (mean, deviation) before (-0.035, 0.020) after (-0.000, 0.016)
8/18/2021, 5:26:26 PM M119
Endstops - X: at max stop, Y: at max stop, Z: at max stop, Z probe: not stopped
8/18/2021, 5:26:23 PM G28
8/18/2021, 5:26:10 PM M119
Endstops - X: not stopped, Y: not stopped, Z: at max stop, Z probe: not stopped
8/18/2021, 5:26:07 PM M119
Endstops - X: not stopped, Y: at max stop, Z: not stopped, Z probe: not stopped
8/18/2021, 5:26:04 PM M119
Endstops - X: at max stop, Y: not stopped, Z: not stopped, Z probe: not stopped
8/18/2021, 5:25:57 PM M119
Endstops - X: not stopped, Y: not stopped, Z: not stopped, Z probe: not stopped

The problem persist...

I updated the files:

Duet2_Sdiap32_WiFiEth.bin
Duet2CombinedFirmware.bin
Duet2Firmware_SBC.bin
DuetWebControl-SD.zip

Do I should wipe out everything and start from scratch or... ?

M115

FIRMWARE_NAME: RepRapFirmware for Duet 2 WiFi/Ethernet FIRMWARE_VERSION: 3.3 ELECTRONICS: Duet Ethernet 1.02 or later FIRMWARE_DATE: 2021-06-15 21:45:03

Bed.g

; bed.g
; called to perform automatic delta calibration via G32
;
; generated by RepRapFirmware Configuration Tool v3.2.3 on Mon Jun 28 2021 20:11:21 GMT-0400 (heure d’été de l’Est)
M561 ; clear any bed transform
; Probe the bed at 6 peripheral and 3 halfway points, and perform 6-factor auto compensation
; Before running this, you should have set up your Z-probe trigger height to suit your build, in the G31 command in config.g.
G30 P0 X0 Y84.2 H0 Z-99999
G30 P1 X66.01 Y38.11 H0 Z-99999
G30 P2 X66.01 Y-38.11 H0 Z-99999
G30 P3 X0 Y-84.2 H0 Z-99999
G30 P4 X-73.61 Y-42.5 H0 Z-99999
G30 P5 X-73.61 Y42.5 H0 Z-99999
G30 P6 X0 Y41.05 H0 Z-99999
G30 P7 X29.84 Y-17.23 H0 Z-99999
G30 P8 X-36.81 Y-21.25 H0 Z-99999
G30 P9 X0 Y0 H0 Z-99999 S6
; Use S-1 for measurements only, without calculations. Use S4 for endstop heights and Z-height only. Use S6 for full 6 factors
; If your Z probe has significantly different trigger heights depending on XY position, adjust the H parameters in the G30 commands accordingly. The value of each H parameter should be (trigger height at that XY position) - (trigger height at centre of bed)

config-eoverride.g

; config-override.g file generated in response to M500 at 2021-08-18 16:20
; This is a system-generated file - do not edit
; Delta parameters
M665 L288.065:288.065:288.065 R127.923 H292.702 B85.0 X-0.103 Y0.529 Z0.000
M666 X0.321 Y0.093 Z-0.414 A0.00 B0.00
; Heater model parameters
M307 H0 R0.256 C213.522:213.522 D3.59 S1.00 V12.1 B0 I0
M307 H1 R3.286 C260.834:260.834 D9.98 S1.00 V12.1 B0 I0
; Workplace coordinates
G10 L2 P1 X0.00 Y0.00 Z0.00
G10 L2 P2 X0.00 Y0.00 Z0.00
G10 L2 P3 X0.00 Y0.00 Z0.00
G10 L2 P4 X0.00 Y0.00 Z0.00
G10 L2 P5 X0.00 Y0.00 Z0.00
G10 L2 P6 X0.00 Y0.00 Z0.00
G10 L2 P7 X0.00 Y0.00 Z0.00
G10 L2 P8 X0.00 Y0.00 Z0.00
G10 L2 P9 X0.00 Y0.00 Z0.00

config.g

; Configuration file for Duet WiFi (firmware version 3)
; executed by the firmware on start-up
;
; generated by RepRapFirmware Configuration Tool v3.2.3 on Mon Jun 28 2021 20:11:23 GMT-0400 (heure d’été de l’Est)

; General preferences
G90                                           ; send absolute coordinates...
M83                                           ; ...but relative extruder moves
M550 P"MiniKossel"                            ; set printer name
M665 R133.565 L288.065 B95 H292                    ; Set delta radius, diagonal rod length, printable radius and homed height
M666 X0 Y0 Z0 A0 B0                           ; X,Y,Z endstop adjustments and X,Y Bed tilt(% per 100mm), or let auto calibration find them

; Network
M540 PBE:EF:DE:AD:FE:ED                       ; set custom MAC address
M552 P0.0.0.0 S1                              ; enable network and acquire dynamic address via DHCP
M586 P0 S1                                    ; enable HTTP
M586 P1 S0                                    ; disable FTP
M586 P2 S0                                    ; disable Telnet

; Drives
M569 P0 S0                                    ; physical drive 0 goes backwards
M569 P1 S0                                    ; physical drive 1 goes backwards
M569 P2 S0                                    ; physical drive 2 goes backwards
M569 P3 S0                                    ; physical drive 3 goes backwards
M584 X0 Y1 Z2 E3                              ; set drive mapping
M350 X16 Y16 Z16 E16 I1                       ; configure microstepping with interpolation
M92 X100.00 Y100.00 Z100.00 E358          ; set steps per mm E0386.02
M566 X1200.00 Y1200.00 Z1200.00 E1200.00      ; set maximum instantaneous speed changes (mm/min)
M203 X18000.00 Y18000.00 Z18000.00 E12000.00   ; set maximum speeds (mm/min)
M201 X2400.00 Y2400.00 Z2400.00 E2400.00      ; set accelerations (mm/s^2)
M906 X800 Y800 Z800 E500 I30                  ; set motor currents (mA) and motor idle factor in per cent
M84 S30                                       ; Set idle timeout

; Axis Limits
M208 Z0 S1                                    ; set minimum Z

; Endstops
M574 X2 S1 P"xstop"                           ; configure active-high endstop for high end on X via pin xstop
M574 Y2 S1 P"ystop"                           ; configure active-high endstop for high end on Y via pin ystop
M574 Z2 S1 P"zstop"                           ; configure active-high endstop for high end on Z via pin zstop

; Z-Probe
M558 P8 R0.4 C"zprobe.in+zprobe.mod" H5 F1200 T2400                 ; disable Z probe but set dive height, probe speed and travel speed
G31 P100 X0 Y0 Z-0.1                          ; set Z probe trigger value, offset and trigger height
M557 R85 S20                                  ; define mesh grid


; Heaters
M308 S0 P"bedtemp" Y"thermistor" T100000 B3950 ; configure sensor 0 as thermistor on pin bedtemp
M950 H0 C"bedheat" T0                         ; create bed heater output on bedheat and map it to sensor 0
M307 H0 B0 S1.00                              ; disable bang-bang mode for the bed heater and set PWM limit
M140 H0                                       ; map heated bed to heater 0
M143 H0 S120                                  ; set temperature limit for heater 0 to 120C
M308 S1 P"e0temp" Y"thermistor" T100000 B3950  ; configure sensor 1 as thermistor on pin e0temp
M950 H1 C"e0heat" T1                          ; create nozzle heater output on e0heat and map it to sensor 1
M307 H1 B0 S1.00                              ; disable bang-bang mode for heater  and set PWM limit
M143 H1 S280                                  ; set temperature limit for heater 1 to 280C

; Fans
M950 F0 C"fan0" Q500                          ; create fan 0 on pin fan0 and set its frequency
M106 P0 S0.01 H-1                              ; set fan 0 value. Thermostatic control is turned off
M950 F1 C"fan1" Q500                          ; create fan 1 on pin fan1 and set its frequency
M106 P1 S0.5 H-1                                ; set fan 1 value. Thermostatic control is turned off

; Tools
M563 P0 D0 H1 F0                              ; define tool 0
G10 P0 X0 Y0 Z0                               ; set tool 0 axis offsets
G10 P0 R0 S0                                  ; set initial tool 0 active and standby temperatures to 0C

; Custom settings are not defined

; Miscellaneous
M575 P1 S1 B57600                             ; enable support for PanelDue
M501
T0                                            ; select first tool

; Scale Cartesian Axes
M579 X0.000 Y0.000 Z0.000

heightmap.csv

RepRapFirmware height map file v2 generated at 2021-08-17 21:08, min error -0.052, max error 0.043, mean -0.010, deviation 0.022
xmin,xmax,ymin,ymax,radius,xspacing,yspacing,xnum,ynum
-80.00,80.10,-80.00,80.10,85.00,20.00,20.00,9,9
      0,      0,      0,  0.001, -0.032, -0.007,      0,      0,      0
      0, -0.002, -0.007, -0.031, -0.020, -0.032, -0.028,  0.012,      0
      0, -0.016, -0.013, -0.029, -0.037, -0.003,  0.011,  0.009,      0
  0.003,  0.008,  0.010, -0.024, -0.023, -0.032, -0.020, -0.020,  0.009
  0.002, -0.013, -0.032, -0.040, -0.023, -0.017, -0.012, -0.003,  0.043
  0.000, -0.018, -0.024, -0.023, -0.021, -0.021, -0.032, -0.041, -0.002
      0,  0.002,  0.020,  0.021,  0.011,  0.039,  0.032,  0.030,      0
      0,  0.013, -0.020, -0.049, -0.052, -0.029, -0.020,  0.040,      0
      0,      0,      0, -0.007, -0.031, -0.027,      0,      0,      0

homedelta.g

; homedelta.g
; called to home all towers on a delta printer
;
; generated by RepRapFirmware Configuration Tool v3.2.3 on Mon Jun 28 2021 20:11:23 GMT-0400 (heure d’été de l’Est)
G91                       ; relative positioning
;*** Slow homing has been configured. Change F180 to F1800 below when your configuration is working
G1 H1 X309 Y309 Z309 F1800 ; move all towers to the high end stopping at the endstops (first pass)
G1 H2 X-5 Y-5 Z-5 F1800   ; go down a few mm
;*** Slow homing has been configured. Change F180 to F360 below when your configuration is working
G1 H1 X10 Y10 Z10 F180    ; move all towers up once more (second pass)
G1 Z-5 F2400              ; move down a few mm so that the nozzle can be centred
G90                       ; absolute positioning
G1 X0 Y0 F2400            ; move X+Y to the centre

pause.g

resume.g

; resume.g
; called before a print from SD card is resumed
;
; generated by RepRapFirmware Configuration Tool v3.2.3 on Mon Jun 28 2021 20:11:24 GMT-0400 (heure d’été de l’Est)
G1 R1 X0 Y0 Z5 F6000 ; go to 5mm above position of the last print move
G1 R1 X0 Y0 ; go back to the last print move
M83 ; relative extruder moves
G1 E10 F3600 ; extrude 10mm of filament

; pause.g
; called when a print from SD card is paused
;
; generated by RepRapFirmware Configuration Tool v3.2.3 on Mon Jun 28 2021 20:11:23 GMT-0400 (heure d’été de l’Est)
M83            ; relative extruder moves
G1 E-10 F3600  ; retract 10mm of filament
G91            ; relative positioning
G1 Z5 F360     ; lift Z by 5mm
G90            ; absolute positioning
G1 X0 Y0 F6000 ; go to X=0 Y=0

sleep.g

; sleep.g
; called when M1 (Sleep) is being processed
;
; generated by RepRapFirmware Configuration Tool v3.2.3 on Mon Jun 28 2021 20:11:24 GMT-0400 (heure d’été de l’Est)

stop.g

; stop.g
; called when M0 (Stop) is run (e.g. when a print from SD card is cancelled)
;
; generated by RepRapFirmware Configuration Tool v3.2.3 on Mon Jun 28 2021 20:11:24 GMT-0400 (heure d’été de l’Est)

tfree0.g

; tfree0.g
; called when tool 0 is freed
;
; generated by RepRapFirmware Configuration Tool v3.2.3 on Mon Jun 28 2021 20:11:25 GMT-0400 (heure d’été de l’Est)

tpost0.g

; tpost0.g
; called after tool 0 has been selected
;
; generated by RepRapFirmware Configuration Tool v3.2.3 on Mon Jun 28 2021 20:11:26 GMT-0400 (heure d’été de l’Est)
; Wait for set temperatures to be reached
M116 P0

tpre0.g

; tpre0.g
; called before tool 0 is selected
;
; generated by RepRapFirmware Configuration Tool v3.2.3 on Mon Jun 28 2021 20:11:25 GMT-0400 (heure d’été de l’Est)

I have deleted resurrect.g file but still have it in my backup if I absolutely need to have it.

Here is everything I have. Anyone know why my printer has become crazy this morning ? Not enough sleep or too much sugar, maybe? lol

By the way, I still have all the same after HOMING. It behave the same:

1. move upward, activate the endstops, move downward a bit, raise again until endstops activation and stay there (endstop sactive). Tool coordinate is n/a.

@phaedrux I followed the instruction you provided me.

I deleted the config-override and send G28, G32 and M500.

I generated a new config-override file.

but, I didn't had to copy/paste my Heater model parameters, they were already there in the new file with the proper parameters. is that normal ?

New config-override.h :

; config-override.g file generated in response to M500 at 2021-08-18 16:20
; This is a system-generated file - do not edit
; Delta parameters
M665 L288.065:288.065:288.065 R127.923 H292.702 B85.0 X-0.103 Y0.529 Z0.000
M666 X0.321 Y0.093 Z-0.414 A0.00 B0.00
; Heater model parameters
M307 H0 R0.256 C213.522:213.522 D3.59 S1.00 V12.1 B0 I0
M307 H1 R3.286 C260.834:260.834 D9.98 S1.00 V12.1 B0 I0
; Workplace coordinates
G10 L2 P1 X0.00 Y0.00 Z0.00
G10 L2 P2 X0.00 Y0.00 Z0.00
G10 L2 P3 X0.00 Y0.00 Z0.00
G10 L2 P4 X0.00 Y0.00 Z0.00
G10 L2 P5 X0.00 Y0.00 Z0.00
G10 L2 P6 X0.00 Y0.00 Z0.00
G10 L2 P7 X0.00 Y0.00 Z0.00
G10 L2 P8 X0.00 Y0.00 Z0.00
G10 L2 P9 X0.00 Y0.00 Z0.00

@phaedrux Ok, please explain me how you "published" the file in such way so everyone can see ?

I simply select "upload file" and it does not show like that. Which one I should select to have that ?

@phaedrux Yes, that's what I though... So I deleted the file (where we upload our print) from the list because I believe it may be related to that. (instead of printing the new file, it try to resume an old one ?) Anyway, I deleted every upload I had, upload a new one and it behave the same.

I'm clueless for why it suddenly behave such way for no apparent reason.

I printed a lot of parts in the past without any issue. I mean, really no issue at all. I installed the duet effector 3 days ago and started to have all kind of issue (my nozzles heater stop to heat randomly, and now that).

I doubt they are linked, but maybe ?

@phaedrux I did it plenty of time and it didn't resolve the new problem I facing now... Is it because it does not take into account the G32 or the M500 anymore for unknown reason ?