help after calibrating beacon, printer seems to be reading all Z axis values incorrectl
Seeing some stange behaviour with my printer, curious if this may be something easy. I've had a very difficult time getting my beacon sensor to finish the
BEACON_RATOS_CALIBRATE command successfully. It ended up being the z1 gantry was not straight and once I fixed this, everything worked perfect. Now though what IM seeing is that the scans in HEIGHTMAP appear that they are reading off by 0.5mm or so. Basicallly if I have the Flat option checked in the display, I will see what looks like I'd expect with the PEI sheet on, but it's all showing everything .5mm off from the flat section. not a corner, or 2 corners, but I mean the whole thing is registering like it's offset .5mm. The little lip at the top is just the PEI sheet and Im not concerned with or trying to fix that, it's the fact that it's reading what appears to be everything offset from the bed. I took the PEI sheet off and I get the same results with the range I'd expect., but iwth this strange .5mm (or so) offset. I really noticed this because I ran BEACON_MEASURE_GANTRY_TWIST and it gave me this message:
When the BEACON_RATOS_CALIBRATE ran successfully, it did not report this at all. Though the range from min to max was about the same, it was relative to 0 and it reported it as a Low gantry twist. Because those numebrs don't have anything close to 0, or even any negative numbers is why Im thinking there is some kind of offset happening. I'd note this all happened after I did the VAOC calibration. After the BEACON_RATOS_CALIBRATION succeeded,. I moved to complete the VAOC calibration and it failed with some out of range errors, and then all this has measurements with some kind of offset started to being.
Any help / guidance would bew appreciated.18 Replies
Here is the error message I got when running the
BEACON_MEASURE_GANTRY_TWIST command:
It looks like my screenshoty didn't get attached correctly either, here is what I mean in HEIGHTMAP section where it seems like it's reading with some kind of offset
Haven't seen that before, sorry 😦
Thanks. Do you think what Im saying seems correct about it looking like some kind of offset being applied? Whenver I was dealing w/ bed leveling I was always at one side or the other above and below the
Flat plane, but it seems like its all registering incorrectly to me. Curioous if Im just way off base with this thinking? My reasoning is that it could be some config or parameter related and an option would be to start over from scratch if I can't resovleyeah, usually the wobbly plane of the bed is centered around zero, that does seem odd.
And you haven't done any manual editing of files, right?
this is correct. I finally got the
BEACON_RATOS_CALIBRATE command to complete. It had taken me over a week of fighting it to figure out al the things that were wrong. I did this just yesterday. By the evening I was on to the VAOC calibration. I even did a BEACON_MEASURE_GANTRY_TWIST comamnd just to be sure it was all good, as my problems rel;ated to the beacon calibration were due to a crooked z gantry (that I had fixed/corrected). But this ran correct, and gave me the same results that came in the very long BEACON_RATOS_CALIBRATE scan. (this was a twise of something like 40-60 microns. the text was in blue and it was classified as Low gantry twist. So I go through the VAOC calibration, get everything aligned on both toolheads and went to save that and I ended up getting an error. I didn't save exactly what it was, but somehting about bad range. The printer was acting strange after that so I just did a firmware restart and since then, I every time I have interaced with the bed it's had this strange offset like appearance. I can't say for sure it's related to the VAOC calibration error, but I can say for sure this all was noticable immediately after that and I had never seen it before that.quick look at klipper docs and googling the offset didn't find me anything :/
Yeah I wasn't able to see anythign that seemed straigthforward or obvious. But I have never used Klipper before too 🙂
Did you use the set kinematic center command Instead of homing?
I am unsure what that is. Can you confirm?
This isnt that unusual and theres generally nothing wrong its just a bug.
Just double check your zero_reference_position, but also just try doing a hard power cycle of the printer, that often sorts it out.
OH man
🙂
Ok so to confirm, wherer it shows the extreme gantry twist, I shouldn't worryu about this, @Martin Hanbury ? Where would I set
zero_reference_position and what would the correct value be versus incorrect? Also I'll jkust note, I've hard power cycled the printer at least 2 or 3 times and this is staying the same.THis seems somewhat bad and somehting I shoudln't ignore, no? I've done multiple cold power cycles and still this is the results Im seeing where it seems like it's misreading everything by a signficiant margin. As well on the dashboard where it reports the position, it seems there is some kind of discrepency between where it thinks it shoudl be and where it is. X and Y seem to be correct but for Z it seems like there is a discropency of almost 1mm. This would roughly correlate to the discrepency Im seeing in the bed mesh utitilty, but Im at a loss for where to go from here.
I alsio checked out all the bug reports on the RatOS project but I coudln't see any that correspond to something like this. When you mentioned that this was a known issue, @Martin Hanbury , was it in RatOS or Klipper maybe?
Just within Klipper, it happens occasionally
Your
zero_reference_position gets defined in the [bed_mesh] section of your printer.cfg, and you would generally always do it in the position that gets used for the Beacon calibration (middle of the bed).
I do think this looks like you have an offset being applied somewhere for some reason. Klippy log might help.Ok so here is some more info, hoping someone may can validate ---
I did a complete reinstall of RatOS on a fresh sdcard. After the install I setup my
printer.cfg as I would normally and the same exactly problem exists. This make me curious, when combined with the issue in VAOC calibration that I wonder if the beacon is damaged somehow. So when I go into printer.cfg and comment out the line
the systems appears as I would normall expect and the values don't have this strange offset. I wonder is that telling me somehting is wrong with the beacon contact for z level?
Additionally, when I do this the value I would expect to see in Dashboard after doing a Z tilt adjust appear correct,. whereas before it had this strange offset of almost 1mm
I think we need klippy or debug logs to help man, this feels like a strange config problem not a hardware problem