Random G28 Error G0/G1 Insufficient axes homed
-
@Titus-A-Duxass
; homey.g; called to home the Y axis
;
; generated by RepRapFirmware Configuration Tool v3.3.15 on Sun Jan 08 2023 10:35:48 GMT+0100 (Mitteleuropäische Normalzeit)
G91 ; relative positioning
G1 H2 Z5 F6000 ; lift Z relative to current position
G1 H1 Y295 F1800 ; move quickly to Y axis endstop and stop there (first pass)
G1 H2 Y-5 F6000 ; go back a few mm
G1 H1 Y295 F360 ; move slowly to Y axis endstop once more (second pass)
G1 H2 Z-5 F6000 ; lower Z again
G90 ; absolute positioning -
@Titus-A-Duxass
; homez.g; called to home the Z axis
;
; generated by RepRapFirmware Configuration Tool v3.3.15 on Sun Jan 08 2023 10:32:41 GMT+0100 (Mitteleuropäische Normalzeit)
G91 ; relative positioning
G1 H2 Z5 F6000 ; lift Z relative to current position
G90 ; absolute positioning
G1 X15 Y-10 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 -
@Titus-A-Duxass
Homez puzzles me, it does a 2 stage/speed pass which I do not see in the homez.g. -
@Titus-A-Duxass i can't see anything there that would flag an unhomed axis.
you'll be getting 2 stage probing if you have 2 speeds set in M558 (e.g. F600:180) -
@jay_s_uk
I have that in M558.
I feel like I need to wipe everything and start again from fresh - is it possible.
There just so many odd issues that keep cropping up, I started off wanting the use the Z endstop switch but have now reverted to just the Z probe.
I have changed the config.g to suit but things like setting G31 still does not work. -
@Titus-A-Duxass a wipe and start again is literally a fresh SD card.
Post your config.g
Do you also have a config-override.g? if so post that too -
@jay_s_uk
; Configuration file for Duet 3 MB 6HC (firmware version 3.3)
; executed by the firmware on start-up
;
; generated by RepRapFirmware Configuration Tool v3.3.15 on Wed Jan 04 2023 15:34:18 GMT+0100 (Mitteleuropäische Normalzeit); General preferences
G90 ; send absolute coordinates...
M83 ; ...but relative extruder moves
M550 P"Voron" ; set printer name
M669 K1 ; select CoreXY mode; Wait a moment for the CAN expansion boards to start
G4 S2; Network
M552 P192.168.2.163 S1 ; enable network and set IP address
M553 P255.255.255.0 ; set netmask
M554 P192.168.1.254 ; set gateway
M586 P0 S1 ; enable HTTP
M586 P1 S0 ; disable FTP
M586 P2 S0 ; disable Telnet;Bed mapping
M671 X-60:-60:357:357 Y-6:365:365:-6; Drives
M584 X0.4 Y0.5 Z0.0:0.1:0.2:0.3 E1.0M569 P0.4 S0 ; A goes forwards
M569 P0.5 S0 ; B goes BackwardsM569 P0.0 S1 ; FL goes forwards
M569 P0.1 S0 ; RL goes backwards
M569 P0.2 S1 ; RR goes forwards
M569 P0.3 S0 ; FR goes forwardsM569 P1.0 S0 ; physical drive 1.0 goes forwards
M350 X16 Y16 Z16 E16 I1 ; configure microstepping with interpolation
M92 X80.00 Y80.00 Z400.00 E720.03 ; set steps per mm
M566 X900.00 Y900.00 Z60.00 E120.00 ; set maximum instantaneous speed changes (mm/min)
M203 X60000.00 Y60000.00 Z18000.00 E1200.00 ; set maximum speeds (mm/min)
M201 X6000.00 Y6000.00 Z4000.00 E250.00 ; set accelerations (mm/s^2)
M906 X1600 Y1600 Z1400 E400 I30 ; set motor currents (mA) and motor idle factor in per cent
M84 S10 ; Set idle timeout; Axis Limits
M208 X0 Y0 Z0 S1 ; set axis minima
M208 X295 Y295 Z250 S0 ; set axis maxima; Endstops
M574 X2 S1 P"^io1.in" ; configure switch-type (e.g. microswitch) endstop for high end on X via pin ^io1.in
M574 Y2 S1 P"^io2.in" ; configure switch-type (e.g. microswitch) endstop for high end on Y via pin ^io2.in
M574 Z1 S1 P"^io3.in" ; configure switch-type (e.g. microswitch) endstop for low end on Z via pin ^io3.in; Z-Probe
M558 P5 C"^io4.in" H10 F600 T6000 ; set Z probe type to switch and the dive height + speeds
G31 P500 X0 Y25 Z0.50 ; set Z probe trigger value, offset and trigger height
M557 X15:265 Y15:265 S20 ; define mesh grid; Heaters
M308 S0 P"temp0" Y"thermistor" T100000 B4138 ; configure sensor 0 as thermistor on pin temp0
M950 H0 C"out0" T0 ; create bed heater output on out0 and map it to sensor 0
M307 H0 B1 S1.00 ; enable 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"temp1" Y"thermistor" T100000 B4725 C7.06e-8 ; configure sensor 1 as thermistor on pin temp1
M950 H1 C"out1" T1 ; create nozzle heater output on out1 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"out9" Q500 ; create fan 0 on pin out9 and set its frequency PARTS FAN
M106 P1 S1 H-1 ; set fan 0 value. Thermostatic control is turned off
M950 F1 C"out7" Q500 ; create fan 1 on pin out7 and set its frequency TOOL FAN
M106 P1 S1 H1 T45 ; set fan 1 value. Thermostatic control is turned on; Tools
M563 P0 S"Revo" D0 H1 F1 ; define tool 0
M563 P2 D0:1 H1:2 X0:3 F0:2
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
; Miscellaneous
M501 ; load saved parameters from non-volatile memory
T0 ; select first tool -
@Titus-A-Duxass
Here is the config-overide which does not get update with the M500 command. I have tried entering the new G31 value in but I never see it entered.; config-override.g file generated in response to M500 at 2023-01-08 11:17
; This is a system-generated file - do not edit
; Heater model parameters
M307 H0 R0.456 K0.312:0.000 D6.24 E1.35 S1.00 B0
M307 H1 R4.739 K0.625:0.000 D3.15 E1.35 S1.00 B0 V23.7
; 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 -
@Titus-A-Duxass
The G28 error only happens with Homeall. Homing the axes individually does not produce the same error. -
@Titus-A-Duxass said in Random G28 Error G0/G1 Insufficient axes homed:
@Titus-A-Duxass
Here is the config-overide which does not get update with the M500 command. I have tried entering the new G31 value in but I never see it entered.I think I may have slightly mis-informed you in another thread.
To save the G31 value in config-override.g you must use M500 P31
M500 on its own won't do it. -
@Titus-A-Duxass said in Random G28 Error G0/G1 Insufficient axes homed:
@Titus-A-Duxass
The G28 error only happens with Homeall. Homing the axes individually does not produce the same error.I think you're missing a step in homing XY on a CoreXY.
See the example here: https://docs.duet3d.com/en/User_manual/Machine_configuration/Configuration_coreXY#homing-files
G91 ; relative mode G1 H1 X-240 Y-240 F3000 ; coarse home X or Y G1 H1 X-240 ; coarse home X G1 H1 Y-240 ; coarse home Y G1 X4 Y4 F600 ; move away from the endstops G1 H1 X-10 ; fine home X G1 H1 Y-10 ; fine home YAnd compare to your homeall XY section
G1 H1 X295 Y295 F1800 ; move quickly to X and Y axis endstops and stop there (first pass) G1 H2 X-5 Y-5 F6000 ; go back a few mm G1 H1 X295 Y295 F360 ; move slowly to X and Y axis endstops once more (second pass)In corexy when you home both X and Y at the same time when either endstop is hit both motors will stop. The example has an added homing move for X and Y individually to get them all the way home.
The method of setting up simultaneous homing is different for CoreXY printers. On a Cartesian printer, if you use the G1 command with H1 parameter to perform a homing move on several axes simultaneously, each axis will continue moving until either the specified movement amount has been completed or the homing switch for that axis has been triggered. On a CoreXY printer, the whole move will be terminated when the first homing switch is triggered. Therefore, to do simultaneous XY homing, your homeall.g file needs to first home X and Y together, then home them separately.
So depending on the position of your print head on the X and Y axis, you may or may not have both X and Y homed.
Now I'm curious where you got that homing file. The header test indicates it was generated by the config tool, but I just checked and it generates the correct moves, so I'm assuming you've modified it since you got it?
; homeall.g ; called to home all axes ; ; generated by RepRapFirmware Configuration Tool v3.3.15 on Mon Jan 09 2023 22:34:24 GMT-0600 (Central Standard Time) G91 ; relative positioning G1 H2 Z5 F6000 ; lift Z relative to current position G1 H1 X-235 Y-215 F1800 ; move quickly to X or Y endstop and stop there (first pass) G1 H1 X-235 ; home X axis G1 H1 Y-215 ; home Y axis G1 X5 Y5 F6000 ; go back a few mm G1 H1 X-235 F360 ; move slowly to X axis endstop once more (second pass) G1 H1 Y-215 ; then move slowly to Y axis endstop G1 H1 Z-205 F360 ; move Z down stopping at the endstop G90 ; absolute positioning G92 Z0 ; set Z position to axis minimum (you may want to adjust this) ; Uncomment the following lines to lift Z after probing ;G91 ; relative positioning ;G1 Z5 F100 ; lift Z relative to current position ;G90 ; absolute positioning -
@Phaedrux thanks for the response.
This is the auto generated file from the configuration tool, I have not modified it.This is why I've been looking at wiping everything and doing a fresh start.
I sometimes get the feeling that it's following a "ghost" configuration. Unfortunately doing a wipe and fresh start is not so easy. -
@Titus-A-Duxass
Having given this some, I cannot rule out finger trouble from my side.
So the plan is now to manually update each file using a freshly generated output from the config tool, or update my files with data from a firmware configuration that has been posted in Github. -
@Titus-A-Duxass
I manually updated the 4 homeing files and all is well. -
@Titus-A-Duxass said in Random G28 Error G0/G1 Insufficient axes homed:
fresh start is not so easy.
Wel all the configuration is contained to the config files, so a fresh set from the config tool is as close as you can get anyway.
For the firmware, you can simply re-upload the full firmware zip file and that will take care of that.
-
undefined dc42 marked this topic as a question
-
undefined dc42 has marked this topic as solved
