Everytime I run stop.g I get a heater 1 fault.....

dmandn

Everytime I run stop.g I get a heater 1 fault, I can print with this printer fine and everything seems normal, until stop.g is called.

Board: Duet 2 WiFi (2WiFi)
Firmware: RepRapFirmware for Duet 2 WiFi/Ethernet 3.4.1 (2022-06-01)
Duet WiFi Server Version: 1.26

I think I have made a mistake in my stop.g code, but can't seem to find the issue. I have ruled out the tune played at the end, and can see that the temps drop away normally to around 65ish then it goes crazy. So guessing it is to do with turning the hotend off?

Note, this issue has carried through a firmware update and a temp sensor and wiring replacement.

Stop.g
; stop.g
; called when M0 (Stop) is run (e.g. when a print from SD card is cancelled)

M83 ; Relative extruder moves
G91 ; Relative positioning

G1 Z10 F3000 ; Lift gantry + nozzle 10mm
G1 E-10 F600 ; Retract 10mm of filament
; M702 ; Unload filament settings from tool
M117 "Retracted filament!"

G10 ; Retract
G1 E-5 F300 ; Retract 5mm filament to ensure clean homing on next run

G10 P0 R0 S0 ; Turn-off hotend
M116 P0 S50 ; Wait for temperatures to drop
M117 "Extruder cooled!"

; Turn off fan
M106 P1 S0 ;Turn-off extruder/HS fan
M117 "Extruder fan off!"

M140 S0 ; Turn off bed heater
M106 S0 ; turn off part cooling fan
M117 "Bed off!"

G28 X ; Home X
G1 Y330 ; Move head to rear left for complete bed & print access

M98 P0:/Macros/Tunes/Mario.g ; call Mario.g tune macro file
M81 ;Power Down to save power.

gloomyandy

@dmandn What heater fault are you getting? It would also probably help if you could post a screen grab of the temperature chart when you get the error.

Phaedrux

How are you invoking stop.g?

OwenD

@dmandn said in Everytime I run stop.g I get a heater 1 fault.....:

G10 P0 R0 S0 ; Turn-off hotend
M116 P0 S50 ; Wait for temperatures to drop

This shouldn't cause a heater fault but it won't work as you intend.
Based on the S parameter of 50, I suspect you're trying to wait till the hotend gets to 50 degrees. (0 degrees +/- 50)
However, M116 won't wait for target temps less than or equal to 40 degrees C
So you would need to do it in two steps

G10 P0 R0 S41
M116
G10 P0 S0 R0

You should probably use M568 as G10 will likely be deprecated in future

dmandn

@phaedrux I'm using M0 in my slicer endcode.

dmandn

@owend Ok, I will try this and see if it helps. Thank you!

dmandn

Interesting, I just tried a print from prusaslicer and did not get an error after..... Maybe I have my profile wrong in Cura. Will have a look and get back to you.

Phaedrux

Can you post an example file sliced in each?

dmandn

@phaedrux Yes, I will need to run more tests but will get an example from each from my printer tomorrow. Apologies for the slow replies. I only get to work with my printers on some weekends. My wife doesn't like me spending time with them XD

dmandn

Ok, this has now been resolved (at least on one printer. Will test on the others once I have rewired them).

To fix the issue, had to update firmware and rewrite the stop.g and cancel.g files. Guessing issue was somewhere in the old firmware or in those configs.

Updated to RRF3.4.4 (Sorry, the printers were in storage for months).
Cleared all entries in stop.g and started over.
Then found it would throw the heater fault on cancel.g but is now fine on stop.g.
Cleared cancel.g, then rewrote it calling stop.g with a couple calls before and it works now too.

On another topic, also found on very rare occasions to be breaking contact on the connector, even with new wires, new molex connector crimped, and new senso with appropriate connector. I have found this can be averted by fixing the connectors so they are not free to move around. ...I need to revise my cable management.