-
Notifications
You must be signed in to change notification settings - Fork 19
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Unknown config object 'adxl345 usbadxl' when using default PIS.cfg #12
Comments
Guys, Please update your example config to complete the last change. if your going to call it by name in
|
I ended up with this and it seemed to work. [mcu PIS] Obtain definition by "ls -l /dev/serial/by-id/" then unplug to verifyserial: /dev/serial/by-id/XXXX [adxl345] [resonance_tester] accel_chip: adxl345 usbadxlaccel_chip: adxl345 |
+1 on this - there is even a pull ready to be merged with the fixed code. |
@GerogeFu Come on man, it's embarrassing that something this simple has been broken in your examples for 6 months |
Hi, [mcu PIS] #Obtain definition by "ls -l /dev/serial/by-id/" then unplug to verify [resonance_tester] |
I can confirm that the fix above (renaming "[adxl345 usbadxl]" or the value for "accel chip:" such that they match) works, and that as of 1/27/2024, they still haven't fixed the example config. EDIT: Scratch that. It won't throw errors if you use the "usbadxl" in both, but when running ACCELEROMETER_QUERY you WILL get a "!! Error on 'ACCELEROMETER_QUERY': missing CHIP" if you do. Instead, delete the "usbadxl" from the "accel chip;" line. |
After fighting and fighting to get this thing to work, then finally using KIAUH to flash it, I still received this error when trying to start klipper:
Unknown config object 'adxl345 usbadxl'
Disabling that line, enabling the line without "usbadxl", then restarting the firmware fixed it.
The text was updated successfully, but these errors were encountered: