First print - Error: G0/G1: insufficient axes homed
-
@selva_tvi We'd need much more information. G28 will run the homing macros so you need to upload those. Also, if you are relying on the G28 command to be embedded in the gcode file, then please upload the slicer start code that you are using and also a sample of a the first few lines of a sliced gcode file up to the G28 command at least. You have provided very little information but it sounds like your start gcode contains an axis move command before the G28.
-
Slicer Start Gcode:
G28;
G29;I have attached my homeall.g
Please find the starting lines of Simplify3d:
G90
M82
M106 S0
M104 S195 T0
M109 S195 T0
G28 ; home all axes
G29 ;
; process Process1
; layer 1, Z = 0.384
T0
G92 E0.0000
G1 E-1.5000 F2100 -
Please post your full config.g along with the results of sending M122 and
M98 P"config.g"
in the gcode console tab in DWC. -
-
@selva_tvi
Do you have a start.g in you /sys directory?
Any movement here would happen before your print called G28 -
@OwenD There is no start.g used.
-
@selva_tvi @Phaedrux @OwenD Can you please check and update? Thanks
-
@selva_tvi When you start a print and get the error message about insufficient axes homed, what does the web interface show at that point? i.e which axes show as homed and which one (or ones) show as not homed?
-
@deckingman None of the axis are homed.
'Error: G0/G1: insufficient axes homed'
'The following axes are not homed: X, Y, Z, U'
I have sliced the file properly with start Gcode having G28 and G29.
Scenario 1:
I am switching on the printer. Directly starting the print.
It reaches the target temperature. Then it shows the following error ' 'Error: G0/G1: insufficient axes homed'
I am giving the print again. It reaches temperature and starts the print without any issues.
Scenario 2:
I am switching on the printer. Manually giving home all.
Then starting the print. It reaches temperature and starts the print without any issues.
So, the issue is for the first time giving print after switching on the machine
-
To help trace it down you can add M117 message commands between the lines in your homeall and slicer start gcode to see where it's getting thrown. That may help narrow it down.