Baby Stepping Not Effective? Z Probe offset does nothing?
-
correct, and if you have a Z-min endstop that is in use on the printer, and the height that the nozzle needs to reach is below that Z-min endstop, you will crash into and possibly dmamage the Z-min endstop. it is better to not use one when using a probe to home and probe the bed. you are better off to use the probe to home and physically remove the Z-min endstop as it is being physically replaced and functionally replaced by the Z-probe.
It wasnt stated if you use a Z-min endstop, I am just stating the reason why you don't need one, just in case you do.
-
correct, and if you have a Z-min endstop that is in use on the printer, and the height that the nozzle needs to reach is below that Z-min endstop, you will crash into and possibly dmamage the Z-min endstop. it is better to not use one when using a probe to home and probe the bed. you are better off to use the probe to home and physically remove the Z-min endstop as it is being physically replaced and functionally replaced by the Z-probe.
It wasnt stated if you use a Z-min endstop, I am just stating the reason why you don't need one, just in case you do.
Nope I don't have a Z end stop, just the inductive sensor. I didn't know that the homing files were automatically set up for end stop usage. As previously stated, the files were set up just as they are when the duet is initially started up with the exception of a movement command and changing the reported value.
Also, after some trial and error with the G30 inserted in the homing files instead of the G1 Z-9999 S1 commands, it has successfully homed and returned to the proper location for Z0!
NOW I just need to hope and pray it STAYS THAT WAY after it does the quick 5 point 'bed compensation' if it does that, then hopefully everything should be set!
-
ALRIGHT! I'm closer finally! After a bed compensation, THINGS HAVE CHANGED… Except, now its too low (by .60) instead of being several mm higher. Least now I've gotten somewhere and not feeling like I'm demonstrating the definition of insanity!
-
SUCCESS! I changed the G31 value in the 0.94 and it appears to be as perfect as can be after a bed compensation! .66 was too low apparently, and so I added the difference it was missing and then it became too high, and slowly took away .10 from it until after a bed compensation it fit the paper just right!
Starting a quick print to see if it actually remains working. And if it does, THANK YOU ALL SO MUCH for putting up with an idiot such as myself lol. I wouldn't have ever known that G30 was needed in the homing files if it wasn't for all of you!
-
No worries. Enjoy, don't let it annoy you more than absolutely necessary.
-
FINALLY! Print started and its actually sticking!
Thanks again so much guys. Never would have figured it out or gotten it to work at all on my own. Power of the internet for ya!
Also, sorry for the large picture if it shows up that way. I did the preview thingy but I couldn't figure out how to make the image smaller…
-
Glad yo got it sorted and your frustrations are at an end. So NOW you can use baby stepping if necessary to make fine adjustments to that first layer.
-
BTW, something that tripped me up for a few hours, is that if your config.g includes M501 (to apply config-override.g), this will also change the probe offset from G31, because the probe offset is included in the saved data from M500.
So I was adjusting the Z height in config.g then issuing it manually in the Gcode console during tuning, have it work just fine, then I would lose my changes the next time the Duet rebooted even though I had adjusted my config.g! This made it seem like my Z sensor was inconsistent and set me off a wild goose chase trying to fix a non-existent problem.
In the end I decided that config-override.g was just hiding important config bits to another file, so I disabled M501 and put everything in config.g, this made everything work as expected. IIRC @deckingman you don't use config-override.g either, now I know why.
Cheers,
Ben. -
…................................IIRC @deckingman you don't use config-override.g either, now I know why.
Cheers,
Ben.Yup. Sooner or later it'll bite you in the ar.. I prefer just to have one file that contains all the settings. Admittedly, I have to make note of changes and manually edit config.g, so it's not as convenient as using M500 but personally, I'd rather do it that way.
-
Well I recall David was reluctant to have a config override and this is why. It gets me from time to time. Maybe it would be possible to pop up something to say "would you like to save?" when it's a command saved into config override, it's only a short list of commands?
-
The parameters stored are listed in the wiki entry:
https://duet3d.com/wiki/G-code#M500:_Store_parametersI also resisted using M500 but now just use it to save typeing, especially after delta calibration:
Run M500, go to system files, open config-overide.g, copy the values. open config.g paste the values….
Maybe I should just remove them from config.g completely and only use the config-override.g values now i think about it!
