G30 Insufficient Axes Homed For Bed Probing
-
@steve-lynch Sorry, I was typing my other lengthy post so didn't see your latest.
Yes you are getting closer.
You can uncomment this line - it saves a bit of time if that first move is a diagonal move which stop when one or other end stops triggers.
;G1 S1 X-300 Y-300 F10000 ;move quickly to X or Y endstop and stop there (first pass)Your second "G1 Z5 F6000 ;lift Z relative to current position" needs an S2 because at that point in time, the Z axis still hasn't been homed.
-
yes actually, that's kind of what I surmised... That way no matter where it is on the bed, it has a theoretical travel distance equal to the total dimensions of the build volume.. That actually makes perfect sense!
Cheers! -
@steve-lynch said in G30 Insufficient Axes Homed For Bed Probing:
yes actually, that's kind of what I surmised... That way no matter where it is on the bed, it has a theoretical travel distance equal to the total dimensions of the build volume.. That actually makes perfect sense!
Cheers!We seem to be typing at the same time - see my latest.
-
@deckingman OOps! I left that commented, because I was observing what each G code did... Forgot to free that back up! Good eye!
-
Dang it! Can ya' throw me a bone? What is it that is causing the error... It seems to be in relation to the first set of moves... this block of moves
;G1 S1 X-300 Y-300 F10000 ;move quickly to X or Y endstop and stop there (first pass)
G1 S1 X-300 F10000 ;Now do a fast move just on X and detect end stop
G1 S1 Y-300 F10000 ;Likewise Yas soon as the gantry starts moving, it errors... But I do not see any G28 reference in there, or G30 at this stage of the Gcode.... is it right in front of me?
-
@steve-lynch What;s teh error message exactly? And did you put that S2 in the second G1 Z move?
-
G28! (in a little exclaimation Triangle) then below it it says G30 insufficient homing for bed probing
uncommented fthat line, and added S2 to the second Z5...
G91 ; relative positioning
G1 Z5 F6000 S2 ; lift Z relative to current position
M401 ;deploy mechanical z probe
G1 S1 X-300 Y-300 F10000 ;move quickly to X or Y endstop and stop there (first pass)
G1 S1 X-300 F10000 ;Now do a fast move just on X and detect end stop
G1 S1 Y-300 F10000 ;Likewise YG1 X5 Y5 F6000 ;go back a few mm
G1 S1 X50 F360 ;move slowly to X axis endstop once more (second pass)
G1 S1 Y50 ;then move slowly to Y axis endstopG1 S2 Z5 F6000 ;lift Z relative to current position
G90 ;absolute positioning
G1 X190 Y150 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 positioningM402 ;retract mechanical Z probe
-
@steve-lynch said in G30 Insufficient Axes Homed For Bed Probing:
G1 S1 X50 F360 ;move slowly to X axis endstop once more (second pass)
G1 S1 Y50 ;then move slowly to Y axis endstopThese need to be negative moves again to go back towards the endstop.
And if you're using the BLTouch, just remove these entirely.
M401 ;deploy mechanical z probe and M402 ;retract mechanical Z probe.They are not needed. The probe pin will deploy automatically with G30. Deploying it before your other moves risks it either hitting the bed and causing an error, or getting caught on something and breaking. -
Yeah, That's what I thought.. DC42 Told me to put them back in... I didn't specify what Build I was on... I read that that is handled by Type 9 probe now. Cool!
Thanks! -
UGH! Still! G30 Insufficient Axes Homed for Bed probing!
we trim more and more off each go-round, but still we do not kill the error!
-
@steve-lynch can you post your homeall one more time?
-
@phaedrux said in G30 Insufficient Axes Homed For Bed Probing:
@steve-lynch can you post your homeall one more time?
@Steve-Lynch That - and also your deploy probe and retract probe macros - there could be a move in there that needs an S2
EDIT. Inore that - you aren't now using them
-
G91 ; relative positioning
G1 Z5 F6000 S2 ; lift Z relative to current position
G1 S1 X-300 Y-300 F10000 ;move quickly to X or Y endstop and stop there (first pass)
G1 S1 X-300 F10000 ;Now do a fast move just on X and detect end stop
G1 S1 Y-300 F10000 ;Likewise YG1 X5 Y5 F6000 ;go back a few mm
G1 S1 X-300 F360 ;move slowly to X axis endstop once more (second pass)
G1 S1 Y-300 ;then move slowly to Y axis endstopG1 S2 Z5 F6000 ;lift Z relative to current position
G90 ;absolute positioning
G1 X190 Y150 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 -
I posted the deploy and retract above.. they're really short...
deploy just contains M280 P3 S10 I1
retract contains: M280 P3 S90 I1
-
Honestly, the more we cull from the Homeall.g, the more I see just how much unnecessary, redundant, and counter intuitive stuff I had going on there... It's like the file was fighting against itself.. lol
-
Can you confirm that when you hit home all the X and Y axis start moving towards the endstops and actually hit them?
You can remove the second Z lift as well. It's already lifted once at the start of the file, so no need to raise it again. This one before the G90. Though it shouldn't be causing the problem.
G1 S2 Z5 F6000 ;lift Z relative to current position
G90 ;absolute positioning -
Try again stepping through the file one line at a time by copying and pasting each line exactly as you you have it in the homeall file, into the console. But before you do that, cycle the power so that you start with all axes un - homed. If you look at the "Machine Control" tab, you start with all the axes highlighted in yellow. So switch to the console, enter the first commend, then switch back to the Machine Control tab. Then repeat for the next command in your homeall file. Every time an axis homes successfully, (i.e. an endstop triggers when the move has an S1 command) each one will change from yellow to blue. At the end of the sequence, they should all be blue. If not, where did it go tits up?
-
@phaedrux yes, they physically hit the end stops, at which time they clear the "not homed" status.
X, Y, and Z
-
Yes when X and Y hit the endstops they should be marked as homed, that is correct. Are you saying they also mark the Z axis as homed?
Can you post your config.g file so we can see what your endstops are configured as?
-
it looks like the very first G1 Z5 F6000 S2 is the culprit
