G30 Insufficient Axes Homed For Bed Probing

Steve Lynch · 18 Jul 2019, 20:51

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

deckingman · 18 Jul 2019, 20:54

@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?

Steve Lynch · 18 Jul 2019, 20:56

@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!

Steve Lynch · 18 Jul 2019, 20:57

@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.

deckingman · 18 Jul 2019, 21:01

@steve-lynch It sounds like something is amiss with your sd card or the way you are editing the homeall.g file. If you take it out of the machine and put it in a PC, you shoudl a number of folders like "filaments", "gcodes", "macros", "sys" and "www" . You may not have all of the folders. But the important one is "sys". Inside there you will see all the relevant files that the firmware uses. Starting with bed.g then config.g etc. Further down is homeall.g and that's the file that runs when you press homeall. So check that and see if it bears any resemblance to the file that you think is your homeall.g.

EDIT. IGNORE THIS - SEE MY NEXT POST DOWN.

deckingman · 18 Jul 2019, 21:04

@steve-lynch said in G30 Insufficient Axes Homed For Bed Probing:

@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.

Ahhh. That's where you are going wrong. You should go to "settings" at bottom left, then click on "system editor". There you will find the homeall.g file. Right click and edit it.

Steve Lynch · 18 Jul 2019, 21:06

pushing the home all button on the web interface, and running the homeall.g file manually from the g code list does not yield the same result.... is there anywhere else that the Home all button could be grabbing instructions from?

Actually, they all do that... If I manually run the file from the Gcode list, the axes slam into the end stops with no regards for the end stop switch... If I use the buttons on the web interface, they home properly.

deckingman · 18 Jul 2019, 21:14

@steve-lynch You shouldn't have any homeing files in the gcode list. These are files that you print and reside in the "gcodes" folder on the sd card. The homing files that are run when you do homeall or homex or homey etc, reside in the "sys" folder. You edit these as I've described above.

If you want to upload a file to that .sys directory, you go into "Settings", pick the "General" tab and there you will see a big button that says "Upload File". Press that then navigate to the file you want and it will get uploaded to the .sys directory (where it belongs). DO NOT upload homing files to the gcode folder (or if you do they will only get ignored unless you try to print one).

Steve Lynch · 18 Jul 2019, 21:16

Ugh! It was that simple.... I feel like such a dumb ass! I actually should have known that... I've set these up before.... I'm soooo sorry!

So should I delete all of those gcode files from the gcode list? not in system editor, but the gcode list?

Those don't belong in that directory, do they?

Steve Lynch · 18 Jul 2019, 21:18

sorry, you were typing while I was... problem gone... Thanks so much guys!

This was a painful, yet informative exercise! I'm really embarrassed.

deckingman · 18 Jul 2019, 21:43

@steve-lynch Don't worry about it. I'm just glad we got there in the end - I was beginning to doubt my own sanity there for a while.

Yes you can delete any homing files that are in the gcode list. Obviously don't delete anything that is in the "sys" folder.

Phaedrux · 18 Jul 2019, 22:20

Glad you guys figured it out.

Steve Lynch · 18 Jul 2019, 22:28

I was working out of the system settings for the first 2/3 of this project, because most of the files were correct... I just somehow migrated to changing files in the gcode directory a few days ago, so basically everything we discussed since saturday or sunday was being changed on files that did nothing... lol. I cleaned all that out. I'm literally as we speak screwing together a railcore I ordered all the parts for... So this will definitely help me out, as I understand a whole lot more than I did a couple weeks ago... and.... It's fresh in my mind. You guys are Legends! Thanks!

Steve Lynch · 19 Jul 2019, 19:14

@deckingman @Phaedrux Hey Guys, can you explain what's wrong with this portion of my Home all? It's the "go back a few MM" G1 X5 Y5 F600

The homing works correctly except for this portion... It goes to X/Y max quickly, and slams into the end of the Max... I've tried a few different variants, but with the same result. I followed the example from here: https://duet3d.dozuki.com/Wiki/ConfiguringRepRapFirmwareCoreXYPrinter

The individual homing files work fine, and omitting this single line from Home all completes without incident.. I've tried to sort this one out myself, but I'm afraid It's right in front of me, and I'm just missing it..

G91 ; relative positioning
G1 Z5 F6000 S2
G1 S1 X-400 Y-400 F10000 ;move quickly to X or Y endstop and stop there (first pass)
G1 S1 X-400 F6000 ;Now do a fast move just on X and detect end stop
G1 S1 Y-400 F6000 ;Likewise Y

G1 X5 Y5 F600 ;go back a few mm

G1 S1 X-300 F360 ;move slowly to X axis endstop once more (second pass)
G1 S1 Y-300 F360 ;then move slowly to Y axis endstop

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

Steve Lynch · 19 Jul 2019, 19:27

I thought it was that line, but apparently it's not... it seems to have to do with the Z homing... I'll go back through the older posts above real quick..

Steve Lynch · 19 Jul 2019, 19:34

Ok, I'm tanked again... I've tried nearly everything above..

End stops are correct, home x, homey, homez work right... what did I screw up now?

Phaedrux · 19 Jul 2019, 19:36

I'm wondering if your motor directions and coordinate system is correct.

Can you verify for me that the 0,0 origin point is in the front left of the print bed?

-x movement goes to the left, +x to the right
-y movement to the front, +y to the back

Also where are the end stops in relation to x and y movement?

Steve Lynch · 19 Jul 2019, 19:36

aaaaaaah! I didn't need that extra G90 prior to moving to the first probe point!

Phaedrux · 19 Jul 2019, 19:37

That g90 should be ok there.

Steve Lynch · 19 Jul 2019, 19:39

Yes, all directions are correct, end stops are correct, I was putting it into absolute mode which was pissing it off! It seems fine now.

manual G code moves are as expected!

If I put the G90, it runs off to x300 y300+... if I remove it, it simply goes to the first probe position and homes Z as it's supposed to.. If it's working, am I ok to leave it out?
?