Fill out above information andin all cases attach yourklippy.logfile (use zip to compress it, if too big). Pasting yourprinter.cfgis not needed Be sure to check our “Knowledge Base” Category first. Most relevant items, e.g. error messages, are covered there
Describe your issue:
I recently installed Klipper on my Prusa MK3S+ and my Raspberry Pi 400 and it has been working fine so far. I started to run into problems when I tried to use my GY-521 (MPU-6050) accelerometer to tune input shaper. When I run ACCELEROMETER_QUERY, it gives me No accelerometer measurements found. I already looked through several online forums, including this one, with a very similar issue to mine, except mine DOESN’T shutdown when I try to query the accelerometer: https://klipper.discourse.group/t/mpu-6050-accelerometer-issues-no-accelerometer-measurements-found/3509
EDIT:
I have already verified my wiring over and over again (I’m using a dissected CAT5 ethernet cable) and checked that I have followed the tutorial step by step. My accelerometer’s indicator light is on, so it is still functional.
Thank you for replying so quickly. Unfortunately, I wasn’t able to find any of @mattaw 's solutions that worked for me. As for the accelerometer, I have had it for quite a long time, so the board may indeed be dead. When I use the i2c-tools that you sent me, the Z-axis returns 0x0000. I am planning on ordering an AXDL345 accelerometer + RPi Pico (I kept thinking that the Pico’s price went up with the other RPi’s did so I was hesitant at first until I saw it’s $10) to see if those would work better.
I just saw this after I placed my order. I am getting an AXDL345 that has a voltage regulator + level shifter, and an RPi Pico so I can use Raspberry Pi Pico + ADXL345 Also, I plan on using the AXDL345 and the RPi Pico for other projects, so I want to keep them on hand
I recently purchased this with the mount: https://de.aliexpress.com/item/1005005743140702.html
It is like the second link from @Sineos but directly sits on the nozzle tip where the vibration has the greatest impact.
However I was not yet able to test it. My v0-S1 just received a new Revo nozzle where this does not fit and the other printers are in hibernation…
Thanks for the photos! It all looks great. Followup questions:
I am assuming you have tried swapping SDA and SCL just in case?
Have you got the whole i2c_baudrate=400000 on the correct i2c interface in config.txt?
If you have a DMM, with the bus idle could you measure the voltage from GND to VCC, SCL and SDA?
If you have a DMM/resistance meter with the whole system powered off could you measure the resistance from SCL and SDA to 3.3V on the Pi’s header? - I have met some really bad MPU pcbs/boards before, and the onboard pullups might be messing with the Pi’s 1.8k pullups on its PCB.
Sorry to answer with more questions, your setup looks very good and should work well. My current theory where the MPU can be detected but doesn’t work is either the i2c bus speed being too low (it has to be 400kHz or 400 baud), or the voltages /bus-pullups from the daughterboard + RPi being wrong. I experienced the symptom of the MPU being identified correctly, but failing during measurement due to either bus speed or pull-up issues a lot. RPi Pico or atmega was much more reliable than linux, as the CPU was not off somewhere doing something else. I need to write a proper linux driver for the MPU at some point.
I have checked that I have the i2c_baudrate=400000 in config.txt. I have tried swapping SDA and SCL to test this to no avail. Also, my MPU has been sitting in a drawer for a few years, so it may not be functional.
I just got a FYSETC Portable Input Shaper and I am having some issues with not starting Klipper with mcu 'PIS': Unable to connect Here’s my klippy.log: Klippy.zip (101.7 KB)
This is really puzzling because I was able to find where it said resource temporarily unavailable so when I used the terminal to find what PID was using the /dev/serial/by-id/—- port, it stopped Klipper. So Klipper is accessing the PIS, but it doesn’t want to acknowledge it?
I tried building and flashing new firmware for the RP2040 and installing it on the PIS in bootloader mode, to no avail. I also tried using the by-id path with no success. I used the ACM0 port to test if that would work.
[ 2.562868] usb 1-1.1: New USB device found, idVendor=1d50, idProduct=614e, bcdDevice= 1.00
[ 2.562943] usb 1-1.1: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[ 2.562987] usb 1-1.1: Product: rp2040
[ 2.563018] usb 1-1.1: Manufacturer: Klipper
[ 2.563052] usb 1-1.1: SerialNumber: E6611CB6973C5C24
[ 2.663532] usb 1-1.2: new full-speed USB device number 4 using xhci_hcd
Please provide / do:
Output of the groups command
Output of ls /dev/serial/by-id/*
Should look like /dev/serial/by-id/usb-Klipper_rp2040_E6611CB6973C5C24-if00
Add this to your printer.cfg and produce a new log
When changing the serial path for the accelerometer, I got an error regarding usbadxl adxl345 but after changing that to adxl345, I get accelerometer values! Thank you for all your help!
