Invalid adxl345 id (got ff vs e5).
hello
i got this error i am using fysetc input shaper that one use USB type C and it work perfect with my other printers very well but with my RR vcore i got this problem .. need help
24 Replies
subsequent-cyanOP•2y ago
Can you upload your printer.cfg?
I suspect you didn't update your config to use this adxl and Rat-OS is expecting the adxl to be attached to the MCU
subsequent-cyanOP•2y ago
sure let me finish my food and i will move to my workshop
subsequent-cyanOP•2y ago
subsequent-cyanOP•2y ago
done
Are you running Rat-OS 1.x?
subsequent-cyanOP•2y ago
how i can know !!
i fellow the documentation on ratos page
RatOS
v1.2.4-4-g898b8ae
this one u mean ?
Yeah, this looks like an old template and not the 2.x version
subsequent-cyanOP•2y ago
its up to date
do i need reflash it for new version ?
Yes, they are not compatible with each other (breaking changes)
In Rat-OS 2.x you should be able to specify your toolboard and then just use the import and have the adxl work
subsequent-cyanOP•2y ago
ok any link for ratos2.x?
Ratos 1.x will stop being supported soon
subsequent-cyanOP•2y ago
thanks for this info
GitHub
Release RatOS-v2.0.1 · Rat-OS/RatOS
RatOS V2.0.1
This is a small patch release to fix some minor issues. V2.0.1 also contains the newest versions of all packages (klipper, moonraker, klipperscreen, mainsail, etc etc).
As always, if y...
subsequent-cyanOP•2y ago
i am to busy to check info
thanks
going to reflash it
do i need to reflash klipper on main board to ?
Well hopefully you aren't too busy to read the documentation or you will have more problems
subsequent-cyanOP•2y ago
hahahahaha
no i will read it carefully this time
Then you should be fine
subsequent-cyanOP•2y ago
thanks dude i will try to reflash it now and update you
Ok. I will be going to bed soon, good luck!
subsequent-cyanOP•2y ago
thanks .. good night dude
still same problem
exotic-emerald•2y ago
Same issue here. But I only have it with klipperscreen
yeah this didn't have anything to do with RatOS v2 vs v1. That config you included didn't define an ADXL.. so it wouldn't do anything. You have to define an adxl for that separate ADXL345 mcu.
your PIS.cfg should look like this:
And all queries need to reference PIS.. So ACCELEROMETER_QUERY CHIP=PIS for example.
See above, mainly:
Also please start you own thread.
Also if you update your system packages this:
will not work anymore.
see #announcements
subsequent-cyanOP•2y ago
ok i wil try to do what i did understand
thanks for replay
@miklschmidt @blacksmithforlife thanks guys finaly it work perfect