Beacon offset incorrect
Hey everyone, I have just done a fresh install of RC3 on my rebuild 3 hybrid
The issue I am running into is thst when the beacon does z tilt, it seems to be using the offset of a blTouch or induction probe instead of the nozzle for the beacon probe.
I have done the configuration and set it to beacon. Is there anything else I need to do to fix this?
I have not touched any printer.cfg setting other than what was automatically done via the wizard 🧙♂️
43 Replies
drop your debug.zip in here. That does look like a non-beacon offset, very interesting
Here you go @TheTik
Found anything interesting in there @TheTik ?
sorry, got pulled away. I'll take a look when I can
Appreciate it!
looks like the offset is correct there at least
wonder if I could figure out how to use the console command
debug_echo but my machine is unresponsive right now and I need to reboot it
just ratos will spit out some variables, but not the ones we're interested in
Going through the code, trying to figure out how the beacon offsets are gathered@TheTik if it helps. I originally set it up as a VC4 and then re did it as a VC3
If not sure if that info will give you any leads
That should have reset everything afaik
I would have assumed too. just incase you cant work it out, maybe there was some bug there that didnt fully reset it or something. Im just grasping at straws here
Try reflashing the sd card and start over?
Would rather not if I dont have to 🥲
@miklschmidt any ideas why it would be doing this? Seems like it could potentially be a RatOS thing
@jLynx 🇳🇿 - VC3-400 any luck? i got the exact same issue
Oh good to know I'm not going crazy. No luck here sadly 😦
Are you on a fresh install and on RC3?
If so, I'll open a GitHub issue
I created an issue here: https://github.com/Rat-OS/RatOS/issues/196
GitHub
Beacon probe using incorrect offset during Z-tilt (appears to use B...
What happened After performing a fresh install of RatOS RC3 on a V-Core 3 hybrid with Beacon probe, the Z-tilt operation is using an incorrect offset. Instead of using the nozzle offset (0mm) for t...
im using ratos 2.1
Yeah 2.1 but is that RC2 or RC3?
@jLynx im also getting this while doing the bed mesh
I'm not getting that issue. This one seems like a config issue. If you open a new issue and tag me. Upload your debug zip file and I'll take a look for you
done
Maybe related to this comment? https://discord.com/channels/582187371529764864/1254429925268787311/1254718041972019240
But it doesn't sound correct
Yes, probe offsets aren't dynamic (for a multitude of reasons, one being the toolhead dimensions and hardware locations are completely unknown to RatOS), so if your probe hardware or toolhead isn't stock for the printer you're using, you have to set the probe offsets, z_tilt positions and bed_mesh min/max yourself.
I would say "it's intended", but it's not, it's just a consequence of not having enough time to solve that issue as it's unfortunately quite a big task because of the way klipper does offsets.
My probe is dead center for the nozzle. You can see in the video above
So in that case, how do I update it to use 0 for the y?
yeah the stock vc3 isn't
For the beacon or just for a generic probe?
I know generic probes are off the side(like blTouch) , but I thought because i selected the beacon, it would have changed it to be the center
There's no difference. The bed_mesh and z_tilt coordinates don't change because you change the probe.
bed_mesh and z_tilt config is static, you have to manually handhold those.
So in that case, what is the lines I need to add in my printer.cfg to center it?
The klipper docs explain how to set bed_mesh min/max and z_tilt positions
Thanks, I assume it's here somewhere? https://www.klipper3d.org/Config_Reference.html
I'm not really too sure what I am looking for here. Are you able to point out the specific part?
yessir under [bed_mesh] and [z_tilt], there's a longer guide on bed mesh configuration as well.
Like i mentioned,
points under z_tilt and mesh_min and mesh_max under bed_meshI guess I could also just take the one from the vc4 config as that would be the same? Or no as the vc4 is wider?
And can I just add this to my printer.cfg to change these, or do I need to do it somewhere else?
Also @miklschmidt where would I find the current default ones?
Oh found it under /RatOS/printers/v-core3/400.cfg
And here is the v-core4 config file
Solution
----
Alright! Adding:
To my printer.cfg solves the issue of the incorrect offset for the beacon probe. This one I just took from the vc4 config file
@miklschmidt Shouldent we be able to apply that in the
RatOS/z-probe/beacon.cfg file automatically though and have it based on the printer size?
@someaction Above I have posted the solutionShould work
Nope, there’s nothing dynamic about cfgs. Jinja only works in gcode macros.
Oh yeah I know the files themselves are not dynamic. I was talking about with the configurator
so this should help? or do i have to copy paste the whole [bed_mesh] u posted?
Just adding that should be all that's needed
long time no see. havnt had any time to dig in to it since now for a few minutes. got it working with the z-tilt. calibrating bed mesh is still reading more to the left side and is not scaning as much in the right side as the left
That's all I needed to do. But since then I have gone and set it up as a VC4 since I have a hybrid vc 3.1 and that also fixed it
For anyone that comes across this in the future, for the 500 it's