G32 in the beginning of my print gcode turns off heaters
I'm very new to duet or RRF and am just now trying my first prints on my cbot. I replaced a smoothieboard that i never particularly cared for. I'm amazed at how smooth/quiet it is.. i didn't know sound levels like this were possible!
I heat my bed / nozzle up before running g32. After running g32 both heaters turn off… i didn't think much of that until i put it in the startup of my print gcode. Now as soon as the g32 finishes duet thinks the print is done.
Is that normal? I've read a bunch of threads where people do something similar so I'm thinking I'm doing something wrong or maybe it has changed recently?
this is from my config.g
M558 P4 X0 Y0 Z1 H5 F120 T6000 I1 ; Set Z probe type to switch, the axes for which it is used and the probe + travel speeds
G31 P500 X-30 Y0 Z1 ; Set Z probe trigger value, offset and trigger height
I think something in your bed.g file must be turning the heaters off. Please share the contents of bed.g.
you are quick to respond!
this is my bed.g
; Home all axes
; Probe the bed at 4 points
G30 P0 X15 Y15 H0 Z-99999
G30 P1 X15 Y285 H0 Z-99999
G30 P2 X335 Y285 H0 Z-99999
G30 P3 X335 Y15 H0 Z-99999 S
G1 X0 Y0
That looks OK to me. Please post the contents of your homeall.g file, or homedelta.g if it is a delta printer.
I added an S1 to one of the G1 commands because otherwise it would ignore the endstop and keep running in.. this is a corexy setup, fyi
; called to home all axes
; generated by RepRapFirmware Configuration Tool on Sat Mar 18 2017 08:59:01 GMT-0600 (MDT)
; Relative positioning
; Lift Z
G1 Z5 F6000
; Course home Y
G1 Y-305 S1
; Course home X
G1 X-355 S1
: Move away from the endstops
G1 X15 Y15 F6000
; Fine home X
G1 X-355 F360 S1
; Fine home Y
G1 Y-305 F360 S1
; Move Z down until the switch triggers
G1 Z-305 F1800 S1
; Absolute positioning
; Tell the firmware where we are
; Uncomment the following line to lift the nozzle after probing
;G1 Z5 F100
That looks OK to me. I don't see any reason why G32 would turn your heaters off, so I suspect that you are getting a heating fault. Are any messages displayed on the GCode Console page of the web interface? Does the web interface show either of the heaters as being in an error state?