G30 Insufficient Axes Homed For Bed Probing
-
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.
-
@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.
-
@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.
-
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.
-
@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).
-
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?
-
sorry, you were typing while I was... problem gone... Thanks so much guys!
This was a painful, yet informative exercise! I'm really embarrassed.
-
@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.
-
Glad you guys figured it out.
-
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!
-
@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 YG1 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 endstopG90 ;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
