Duet - no response back
-
cool cuz its at -43 now…....i moved it closer.
Also with regards to this in the 1.21 RC5 update
On Cartesian and CoreXY printers, normal G0 and G1 moves are no longer allowed before the corresponding axes have been homed. In particular, if your homex.g, homey.g and homeall.g files raise Z a little at the start and lower it at the end, you will need to add the S2 parameter to those G1 Z moves. Otherwise the G1 Z move will be refused unless Z has already been homed and the homing macro will be terminated.would that be like this?
G1 S2 Z5 F6000 ; lift Z relative to current positionIt was G1 Z5 F6000
getting errors about homing now, and z axis doesnt stop when endstop is triggered.M120
G91
G1 Z-1 F6000
M121
Error: G0/G1: insufficient axes homed
Error: Pop(): stack underflow! -
Yes, adding S2 to that G1 Z5 command should fix that.
1.21RC5 is now out of date because version 1.21 has been released. (RC means Release candidate).
-
thank you. Updated the web interface and now to test… still getting errors.
7:37:08 AM G28 Z
Error: G0/G1: insufficient axes homed
7:37:06 AM G28 Y
Error: G0/G1: insufficient axes homed
7:36:58 AM G28 X
Error: G0/G1: insufficient axes homed -
It sounds that you are still missing some S2 modifiers in your homez.g, homey.g and homeall.g files. If you are using a Z probe to home Z then you need to home X and Y first.
-
; homeall.g
; called to home all axes
;
; generated by RepRapFirmware Configuration Tool on Fri Feb 16 2018 11:11:03 GMT-0500 (Eastern Standard Time)
G91 ; relative positioning
G1 S2 Z5 F6000 ; lift Z relative to current position
G1 S1 X-305 Y-305 F1800 ; move quickly to X or Y endstop and stop there (first pass)
G1 S1 X-305 ; home X axis
G1 S1 Y-305 ; home Y axis
G1 X5 Y5 F6000 ; go back a few mm
G1 S1 X-305 F360 ; move slowly to X axis endstop once more (second pass)
G1 S1 Y-305 ; then move slowly to Y axis endstop
G90 ; absolute positioning
G1 X-13 Y3 F6000 ; go to first bed probe point and home Z
G30 ; home Z by probing the bed
;G1 Z5 F100 ; uncomment this line to lift the nozzle after homing -
; homex.g
; called to home the X axis
;
; generated by RepRapFirmware Configuration Tool on Fri Feb 16 2018 11:11:03 GMT-0500 (Eastern Standard Time)
G91 ; relative positioning
G1 S2 Z5 F6000 ; lift Z relative to current position
G1 S1 X-305 F1800 ; move quickly to X axis endstop and stop there (first pass)
G1 X5 F6000 ; go back a few mm
G1 S1 X-305 F360 ; move slowly to X axis endstop once more (second pass)
G1 Z-5 F6000 ; lower Z again
G90 ; absolute positioning -
; homey.g
; called to home the Y axis
;
; generated by RepRapFirmware Configuration Tool on Fri Feb 16 2018 11:11:03 GMT-0500 (Eastern Standard Time)
G91 ; relative positioning
G1 S2 Z5 F6000 ; lift Z relative to current position
G1 S1 Y-305 F1800 ; move quickly to Y axis endstop and stop there (first pass)
G1 Y5 F6000 ; go back a few mm
G1 S1 Y-305 F360 ; move slowly to Y axis endstop once more (second pass)
G1 Z-5 F6000 ; lower Z again
G90 ; absolute positioning -
; homez.g
; called to home the Z axis
;
; generated by RepRapFirmware Configuration Tool on Fri Feb 16 2018 11:11:03 GMT-0500 (Eastern Standard Time)
G91 ; relative positioning
G1 Z5 F6000 ; lift Z relative to current position
G90 ; absolute positioning
G1 X-13 Y3 F6000 ; go to first probe point
G30 ; home Z by probing the bed; Uncomment the following lines to lift Z after probing
;G91 ; relative positioning
;G1 Z5 F100 ; lift Z relative to current position
;G90 ; absolute positioning -
homeall.g looks ok to me.
homex.g needs S2 added to line "G1 Z-5 F6000" because Z is not necessarily homed at that point. Same for homey.g.
homez.g looks OK, but you need to home X and Y before running homez.
-
thank you
-
Added the S2 command to those files….
homed x - no error
homed y - no error
homed z and....G28 Z
Error: G0/G1: insufficient axes homed
however when I use Home All
no errors and homes greatI added S2 to the homez file and seems to work fine now
-
new issue….
when i load an .stl file and try to print, the connection terminates. -
You can't print an STL file directly, you need to slice it first and then upload and print the .gcode file that the slicer generates.
