G30 Insufficient Axes Homed For Bed Probing
-
it looks like the very first G1 Z5 F6000 S2 is the culprit
-
excerpt from my config.g
; Axis Limits
M208 X-8:300 Y0:300 ;Set Axis Limits; Endstops
M574 X1 Y0 S1 ; Set active low and disabled endstops
M591 D0 P1 C3 S0; Z-Probe
M574 Z0 S2 ; Set endstops controlled by probe
M307 H3 A-1 C-1 D-1 ; Disable heater on PWM channel for BLTouch
M558 P9 H5 F120 T9000 ; Set Z probe type to bltouch and the dive height + speeds
G31 P500 X-39 R0.2 Y0 A3 Z1.34 ; Set Z probe trigger value, offset and trigger height
M557 X50:230 Y10:270 S50 ; Define mesh grid -
should the Y axis be negative here as well? Or is the end stop establishing "Hard Zero"?
-
OK, didn't I read that Z cannot make a move without Homing the other exes first? I had the comment to allow moves before homing, but I was told to remove that. S2 denotes a move ignoring limits though, correct?
-
@steve-lynch said in G30 Insufficient Axes Homed For Bed Probing:
it looks like the very first G1 Z5 F6000 S2 is the culprit
Why do you think that? What happens? What should happen is that the bed moves 5mm away from the nozzle and nothing else. You shouldn't get an error message. The homing state won't change because of the S2 parameter. If you do get an error message at this point, try deleting that line and re-typing it, just in case there is a hidden character or some such that is screwing things up.
OK, didn't I read that Z cannot make a move without Homing the other exes first? I had the comment to allow moves before homing, but I was told to remove that. S2 denotes a move ignoring limits though, correct?
You can move Z if you include the S2 parameter. S2 ignores end stop detection.
M574 X1 Y0 S1 ; Set active low and disabled endstops
This looks odd.
-
@steve-lynch said in G30 Insufficient Axes Homed For Bed Probing:
; Axis Limits
M208 X-8:300 Y0:300 ;Set Axis LimitsThat would indicate that your X axis is potentially longer than just 300mm. It's 308 actually. so in the rare case that your X axis is all the way to the max end, it won't be able to reach the endstop switch if your homing file only tells it to move 300mm. So your X axis homing move would need to be more than 300.
So your first X and Y moves should be:
G1 S1 X-400 Y-400 F10000 ;move quickly to X or Y endstop and stop there (first pass) G1 S1 X-400 F10000 ;Now do a fast move just on X and detect end stop G1 S1 Y-400 F10000 ;Likewise YS2 denotes a move ignoring limits though, correct?
The G1 S2 switch will allow that move even if the axis isn't homed. So for the Z axis, it is raising it out of the way a short amount to prevent any collisions.
; Endstops
M574 X1 Y0 S1 ; Set active low and disabled endstopsThis is incorrect. Y0 indicates there is no endstop for Y.
https://duet3d.dozuki.com/Wiki/Gcode#Section_M574_Set_endstop_configuration
If the X and Y endstops are on the low end, it should be
M574 X1 Y1 Z0 S1 -
Ok, I had to take a break... I was too frustrated...
If I manually type in the individual lines of G code... Not copy and paste, physically type them in, I can get the entire code in without an error...
So I re-typed the entire Homeall.G from scratch, and it errors... Error: G30 Insufficient axes homed for bed probing....... @dc42, any ideas? This is weeks I've been fighting the same problem. I know everyone has picked my homeall apart, but nothing I've changed seemed to have an effect on the actual problem I'm having.
-
Did you make the fixes from my last post?
-
yes, I did that yesterday... No change...
-
Does homex honey and homez work independently?
-
yes, the individual homing buttons work fine....
Just the Homeall is hosed.. -
If I simply take each of the x, Y, and Z files, and paste them into a Homeall, could you tell me what stuff to remove if it tests ok?
-
Ok, I made a fresh .txt file, and re-named it so the file extension was .g I simply pasted the 3 scripts that do successfully run when run individually, and put them into one file so they should run in the exact same manner as If I manually pushed the Home x home Y and Home Z buttons, and it still gives the G30 error... it doesn't seem to care what is in the file, it's going to error.
-
@steve-lynch I think this is driving all of us crazy - not just you
Can you post you entire config.g file - not just extracts. Can you also post your config-override.g if you use one.
Oh and let us know what firmware version and whether this is an Ethernet/WiFi board or a Maestro.
-
sure.. i'll post the actual files as attachments.
it's a legit Duet 2 wifi from Filastruder (latest one)
Firmware version 2.03 (2019-06-13b20
Wifi server version 1.21
Web interface version 1.22.6I'm not using config override. It has been deleted.
-
@steve-lynch Nothing drastic there that leaps out at me except you have some strange parameters in your G31 that I'm not familiar with, and they aren't documented in the Wiki. Specifically R0.2 and A3. Is that something to do with the BL touch? Like I said, they aren't documented here
https://duet3d.dozuki.com/Wiki/Gcode#Section_G31_Set_or_Report_Current_Probe_status
but I don't use a BL touch so maybe you need them? Maybe someone else will know.
Just a small thing, but if you don't have config_override.g file, you might as well delete the M501 which calls it at the end of your config.g.
-
Strange twist here... If I comment out literally everything in the Homeall.g file, and simply enable small groups of commands, it still does the entire homing sequence...
That should not be happening, right?
Does the home all button on the web interface actually call the homeall.G? or does it simply run each of the buttons below it in succession?
Could the old Homeall be stuck in memory or something? is there a way to factory wipe the duet, and re-load my configuration?
Sometimes the "scorched earth" approach is better than chasing a gremlin! lol
-
@steve-lynch Now that is weird. No, the home all button should run the homeall macro that sits in the .sys folder of your sd card. How are you editing that file? Have you tried creating the file on a PC and uploading it?
-
@deckingman The R value is simply the delay after probing, and The A value is the amount of times to probe to find the "average" they are BL Touch Specific.
They're documented here: https://duet3d.dozuki.com/Wiki/BLTouch_Troubleshooting
I got rid of the M501. Thanks!
-
@deckingman I'm editing the file from the web interface.. I go to Gcode files, right click and edit.. I have also created a fresh Gcode file, and uploaded it through the web interface.. same result with either method.
