Error during accelerometer data streaming
After update to latest Ratos 2.1 (v2.1.0-RC3-25-g0477559b) I get this error when I want to enable de data stream on the beacon. Data stream on EBB42 works. Beacon seams to work normally.
I get the same result if I disable all extensions in Chrome and restart chrome.
Is this update related or did I mess up something else?
Any help is appreciated
15 Replies
I get the same error in Firefox.
I might have also updated Beacon? now at v2.0.0-21-gee5d7709
Same issue here. Everything is up to date.
All modules up to date and printer seems to be working fine with beacon. Even the SHAPER_CALIBRATE command works, as do the GENERATE_SHAPER_GRAPHS, MEASURE_COREXY_BELT_TENSION macros
Did your issue start also when you updated Beacon or did you also update Beacon and Ratos at the same time?
I upgraded to RatOS 2.1 yesterday and after upgrading, I tried the analysis tool but it never worked.
As a workaround, if you have a EBB42 or EBB 36, you could try selecting that as your measurement tool (in the analyses page). Could be sufficient for now.
Unfortunately, I don't have a toolboard on this printer. It's just the beacon. I can try installing a separate ADXL345 to see if that works
@miklschmidt Apologies for tagging you in here. Is this a User error or something that is known (or both 🙂 )
@Azzkikkr any change on this topic from your side?
@Arthur_C no change here. My printer is currently out of commission as I'm replacing the belts and pulleys. I noticed VFAs in my print and no amount of tension adjustment corrected it. I wanted to use the RAT to check resonance during a print, but it's been non functional this entire time
Well, that is crap .. and it appears it is "just the 2 of us" with this issue....
While I'm at it, I think I'm going to try and reinstall RatOS 2.1 to see if that fixes it. There is an open GitHub issue for RatOS 2.1 installation where if you follow the directions and update the RatOS packages before finishing configuration, you get a 502 gateway error when trying to access the configurator and to work around it you have to finish the configuration and setup completely before updating the RatOS packages. I wonder if that has something to do with it
That error comes from klipper, it should be there, unless the naming of the beacon accelerometer changed, will check.
Do note that you'll get that error if you haven't saved the beacon as your configured probe. Klipper needs the [beacon] config to load the beacon code which exposes the accelerometer data stream.
Yep, something seems to have changed, fixing 🙂
Ah, it's because beacon now supports multiple beacons, and thus the sensor name should be omitted if the [beacon] isn't explicitly named.
Solution
Fix deployed in 5 minutes (and will be ready for update) 🙂
Sorry for the late response @Arthur_C @Azzkikkr i've been busy the last couple weeks.
(reminds me that we need to pin commits on all dependencies and not just klipper/moonraker).
No worries! Appreciate the help and work!
Confirmed fixed, Mikl!