Native RatOS Adaptive Bed Mesh hits the bed in prime location

hope it didnt break my new Rapido, but it hit the bed on prime blob and I hit emergency stop luckily as it zoomed to start (why is that first jerk so fast?) Since adaptive mesh uses the Z-offset to dynamically transform the g-code, where is it pulling this value? I use PROBE_CALIBRATE to set my offset in my printer.cfg file
59 Replies
BulMaster
BulMaster13mo ago
Your config is a bit of a mess tbh. User overrides are best in their dedicated section. Not all over the place On your actual prob Your z offset is wrong ## [probe] ## z_offset = -0.100
SteveBorough
SteveBorough13mo ago
all my overides are in their section no? PROBE_CALIBRATE sets the offset other than comment out my includes this is stock above the override section
BulMaster
BulMaster13mo ago
Doesn’t seem like it. You have overrides all over the config file
SteveBorough
SteveBorough13mo ago
are you sure youre looking at my config?
BulMaster
BulMaster13mo ago
🤔 Let me check again I am@on my phone Oh wait yeah I was looking at someone else’s
SteveBorough
SteveBorough13mo ago
haha
BulMaster
BulMaster13mo ago
Let me check yours 🙊
SteveBorough
SteveBorough13mo ago
thanks!
BulMaster
BulMaster13mo ago
Stupid iPhone You use an skrat on vcore 400?
SteveBorough
SteveBorough13mo ago
yes with EBB42
BulMaster
BulMaster13mo ago
Neat Try setting adaptive mesh to false to see what happens Also have you put the slicer g code start stuff?
SteveBorough
SteveBorough13mo ago
thats how im running it now until this gets resolved set to false adn it runs as before yes I did, it ran a new mesh around the print space but crashed into bed on prime blob my theory is the dynamic part is not reading my offset "# [probe] ## z_offset = 1.320" set by PROBE_CALIBRATE
BulMaster
BulMaster13mo ago
I will try it a bit later in my printer as well. I just woke up and saw the update
SteveBorough
SteveBorough13mo ago
Great, thanks I'm running some late prints and tried out the new hotness (adaptive mesh)
BulMaster
BulMaster13mo ago
Yeah I will need to disable PAM first Was checking in case you had it too and it was conflicting or something
SteveBorough
SteveBorough13mo ago
nope, raw RatOS
stormy-gold
stormy-gold13mo ago
@miklschmidt (just tagging as it’s a new feature push)
miklschmidt
miklschmidt13mo ago
please post klippy.log @steveborough RatOS should echo RESPOND MSG="ADD_PRIME_PROBE_TO_OFFSET: adjusting z offset by {printer.configfile.settings.probe.z_offset - last_z}" when adjusting the Z offset. My assumption is probe repeatibility is poor in your case. Also just realized Adaptive Mesh doesn't work with bltouch currently. But you're not using a bltouch.
SteveBorough
SteveBorough13mo ago
Ive since printed stuff with Adaptive mesh turned off, will the log still hold this info also i rarely set z probe height and print fine
miklschmidt
miklschmidt13mo ago
Strange. I tested it on 2 printers, and had Helge test it too and it worked as intended. Without the output it's gonna be hard determining what's up. Let me check if it even makes it into the log in the first place.
BulMaster
BulMaster13mo ago
I can check in a bit too. just need to do something first using a beacon here though
miklschmidt
miklschmidt13mo ago
It doesn't make it into the log, i wish there was better logging in klipper. All that makes it in is this:
probe at 365.000,20.000 is z=8.649687
Result is z=8.649687
probe at 365.000,20.000 is z=8.649687
Result is z=8.649687
Which isn't super helpful, but better than nothing, so @steveborough please post klippy.log, at least i can look for that. Hold off on that one, let me verify it works first. Yeah beacon will need special case handling. Wouldn't currently work for adaptive priming.
SteveBorough
SteveBorough13mo ago
This is similar to my experience trying to set z offset before just using probe_calibrate, prime blob smack into the bed…after using the probe_calibrate “wizard” and replacing my bent rapido, it works/prints reliably well What’s the difference in config between manually setting z offset and using probe_calibrate
miklschmidt
miklschmidt13mo ago
This indicates your issue is probably more about calibrating. Your current z_offset looks normal though. For a superpinda or other inductive probe there's none It results in the same z_offset under [probe]
SteveBorough
SteveBorough13mo ago
How it’s stored in printer.cig? Ah
miklschmidt
miklschmidt13mo ago
[probe]
z_offset
[probe]
z_offset
in the klipper config section at the very bottom. It will comment out any previous z_offset parameter in your config.
SteveBorough
SteveBorough13mo ago
I noticed it probes the blob area during the adaptive mesh, I think just 1 point right?
miklschmidt
miklschmidt13mo ago
yes, which should be enough The beacon devs have added the feature i need to their todo list, but i don't know when it'll land. I'll add a warning to the docs and bail from priming if using Beacon.
BulMaster
BulMaster13mo ago
Ah thanks!
xenial-black
xenial-black13mo ago
Why? I am using BL and pam was working ok ;/ and now i dont know if its safe to use that adaptive bed mesh for me anymore;/
miklschmidt
miklschmidt13mo ago
You can use it without priming. You cannot use it with adaptive priming before i've had time to test the fix i made earlier today. Bltouch requires special treatment as it's a separate module.
xenial-black
xenial-black13mo ago
How to turn off adaptive priming, and still use adaptive mesh from ratos?
miklschmidt
miklschmidt13mo ago
Actually it won't work at all, yet.
BulMaster
BulMaster13mo ago
Just get PAM for now.
miklschmidt
miklschmidt13mo ago
But i can't just push stuff live without testing. And i unfortunately have a bunch of other things to do today, hopefully i can test it tonight.
xenial-black
xenial-black13mo ago
I already redefined those macros in custom cfg area for bltouch but if you are working on this i will not use them for now.
miklschmidt
miklschmidt13mo ago
Let me know if it works
inc-lavender
inc-lavender13mo ago
I already have PAM and Beacon configured and working. Anything I should or shouldn't do when updating RatOS to latest version with these features?
abcurrie
abcurrie13mo ago
Trying to use the new adaptive mesh. I now understand that it does not work with the BLTouch probe. I did try the latest macro change for Adding_Prime_Probe_To_Offset as found in github but I got an error.
Error evaluating 'gcode_macro ADD_PRIME_PROBE_TO_OFFSET:gcode': jinja2.exceptions.UndefinedError: 'dict object' has no attribute 'probe' I hope this helps and will wait for changes you might be pushing soon.
SteveBorough
SteveBorough13mo ago
Thready Jackson? Jk, I still have a non bl touch issue with my nozzle hitting the bed only when using adaptive mesh
miklschmidt
miklschmidt13mo ago
Currently it doesn't work with beacon (https://discord.com/channels/582187371529764864/1108979027965902858/1109144522908237925 needs to be merged before it won't throw errors). Adaptive priming will require beacon code changes, it's on their list. Hmm.. I will look into this, but looks like it'll be tomorrow.
inc-lavender
inc-lavender13mo ago
Ok, so better not upgrade RatOS with a working Beacon at this time?
miklschmidt
miklschmidt13mo ago
You can upgrade, just don't enable adaptive_mesh yet I'd recommend you clean up your old beacon installation first though (includes deleting the symlinked klippy extra in ~/klipper/klippy/extras)
inc-lavender
inc-lavender13mo ago
OK. Clear. Thanks.
miklschmidt
miklschmidt13mo ago
Tested (with probe and beacon) and merged, if i can have someone with a bltouch test it out that would be great (make sure you remove any overrides). There was a bug in the prime offset adjustment, it was applying an inverted offset, the original issue in this thread should be fixed now (in v2.0.0-69-ga62032c). @d6_gameover let me know if your issue is corrected after updating
Jens
Jens13mo ago
problem is fixed now. everybody with a klicky probe (and most likely other stowable probes as well) needs to make sure the adaptive mesh is probing for the prime blob in the correct position. i had to change my mesh_min to 20,30
miklschmidt
miklschmidt13mo ago
I might just make this stock for safety However it will throw an error now if more than 1mm adjustment is needed
miklschmidt
miklschmidt13mo ago
GitHub
RatOS-configuration/macros.cfg at v2.x · Rat-OS/RatOS-configuration
The RatOS modular klipper configuration. Contribute to Rat-OS/RatOS-configuration development by creating an account on GitHub.
Jens
Jens13mo ago
since my adjustment was 2mm, this would prevent permanent drawings on the pei^^
xenial-black
xenial-black13mo ago
bltouch - I run one test print on my vcore3 - it works I think (in basic small print scenario)
SteveBorough
SteveBorough13mo ago
Works well now! thank you for the quick support!!
inc-lavender
inc-lavender13mo ago
After updating RatOS to v2.0.0-70, adaptive mesh works great with Beacon, but I have no priming what-so-ever, not adaptive, not regularly, just no priming. Did I miss anything?
xenial-black
xenial-black13mo ago
You should have info in console that beacon priming is not supported in adaptive mesh for now if I read last code update correctly.
inc-lavender
inc-lavender13mo ago
I was looking for that, but no info in the console. Just the adaptive mesh and after that the print. But it adaptive priming is not yet available for Beacon, shouldn't it prime the regular way?
xenial-black
xenial-black13mo ago
Current logic is: if you have adaptive mesh active and beacon in config turn off priming, as I see.
inc-lavender
inc-lavender13mo ago
Ah. OK. That explains it. Thanks!
miklschmidt
miklschmidt13mo ago
Can't do that, we can't probe the prime location, so the risk of damaging the bed is too high. If you want priming with beacon you'd have to disable adaptive_mesh. The beacon devs are adding the functionality i need to make it work, but it'll be a while.
inc-lavender
inc-lavender13mo ago
No problem. Mesh is quite fast with beacon, so the advantage of adaptive mesh is the smallest with Beacon I guess.