Closed definitely-not-a-t-rex closed 4 years ago
Have you tried replacing the USB cable?
Have you tried replacing the USB cable?
Both blue short ones from the boards and a longer one that I got with probably a printer or a microphone, I printed fine with the 1.4 and the cable that I used for the log just yesterday. The boards do show up using ls /dev/serial/by-id/* on all cables
Have you tried a different sdcard on your Pi?
Have you tried a different sdcard on your Pi?
No, do you think the could problem could lie on the sd itself or what's on it? It's the only a2 class that I have not in use elsewhere, I can try only klipper and octo on another one for a test but migrating not from a backup would take me a really long time. I can try but I don't see how it would cause Got error -1 in read: (11)Resource temporarily unavailable
orUnable to open port: [Errno 16] could not open port /dev/serial/by-id/usb-Klipper_lpc1769_1F20001722813AAFF63A6A5CC62000F5-if00: [Errno 16] Device or resource busy: '/dev/serial/by-id/usb-Klipper_lpc1769_1F20001722813AAFF63A6A5CC62000F5-if00'
You could look at the RasPi's kernel log for USB dropouts.
e.g.
dmesg | grep 'usb'
and look for sequential 'USB disconnect' and 'New USB device'
or
dmesg -w
for a realtime monitoring
You could look at the RasPi's kernel log for USB dropouts.
e.g.
dmesg | grep 'usb'
and look for sequential 'USB disconnect' and 'New USB device' ordmesg -w
for a realtime monitoring
the second one doesn't seems to give me any info about it and dmesg | grep 'usb'
gives me the same output when the device becomes shutdown as when it's active so ```
[ 0.128800] usbcore: registered new interface driver usbfs
[ 0.128882] usbcore: registered new interface driver hub
[ 0.128999] usbcore: registered new device driver usb
[ 1.111628] usbcore: registered new interface driver r8152
[ 1.111692] usbcore: registered new interface driver lan78xx
[ 1.111760] usbcore: registered new interface driver smsc95xx
[ 1.115755] usb usb1: New USB device found, idVendor=1d6b, idProduct=0002, bcdDevice= 5.04
[ 1.115772] usb usb1: New USB device strings: Mfr=3, Product=2, SerialNumber=1
[ 1.115787] usb usb1: Product: xHCI Host Controller
[ 1.115801] usb usb1: Manufacturer: Linux 5.4.51-v7l+ xhci-hcd
[ 1.115814] usb usb1: SerialNumber: 0000:01:00.0
[ 1.117496] usb usb2: New USB device found, idVendor=1d6b, idProduct=0003, bcdDevice= 5.04
[ 1.117512] usb usb2: New USB device strings: Mfr=3, Product=2, SerialNumber=1
[ 1.117527] usb usb2: Product: xHCI Host Controller
[ 1.117541] usb usb2: Manufacturer: Linux 5.4.51-v7l+ xhci-hcd
[ 1.117555] usb usb2: SerialNumber: 0000:01:00.0
[ 1.120361] usbcore: registered new interface driver uas
[ 1.120466] usbcore: registered new interface driver usb-storage
[ 1.130368] usbcore: registered new interface driver usbhid
[ 1.130380] usbhid: USB HID core driver
[ 1.480573] usb 1-1: new high-speed USB device number 2 using xhci_hcd
[ 1.663193] usb 1-1: New USB device found, idVendor=2109, idProduct=3431, bcdDevice= 4.21
[ 1.663210] usb 1-1: New USB device strings: Mfr=0, Product=1, SerialNumber=0
[ 1.663225] usb 1-1: Product: USB2.0 Hub
[ 1.990576] usb 1-1.3: new high-speed USB device number 3 using xhci_hcd
[ 2.121765] usb 1-1.3: New USB device found, idVendor=14cd, idProduct=1212, bcdDevice= 1.00
[ 2.121784] usb 1-1.3: New USB device strings: Mfr=1, Product=3, SerialNumber=2
[ 2.121800] usb 1-1.3: Product: Mass Storage Device
[ 2.121814] usb 1-1.3: Manufacturer: Generic
[ 2.121829] usb 1-1.3: SerialNumber: 121220160204
[ 2.124560] usb-storage 1-1.3:1.0: USB Mass Storage device detected
[ 2.125595] scsi host0: usb-storage 1-1.3:1.0
[ 5.953668] usbcore: registered new interface driver brcmfmac
[ 257.972726] usb 1-1.4: new full-speed USB device number 4 using xhci_hcd
[ 258.114695] usb 1-1.4: New USB device found, idVendor=1d50, idProduct=614e, bcdDevice= 1.00
[ 258.114713] usb 1-1.4: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[ 258.114726] usb 1-1.4: Product: stm32f407xx
[ 258.114740] usb 1-1.4: Manufacturer: Klipper
[ 258.114752] usb 1-1.4: SerialNumber: 2F003700065052504B313720
[ 258.173172] usbcore: registered new interface driver cdc_acm
which seems to be fine
If you've checked your RasPi's USB ports (try different port?), your USB cables, your USB connections, two different boards, then my guesses would be:
How are you powering the RasPi? Hopefully not off the SKRs' 5V supply... Also, check for the RasPi undervolt flags. Also, check that the SKRs are not pulling 5V from the USB (J2 on the SKR Pro, J15 on the SKR 1.4).
Otherwise I don't have any other bright suggestions.
If you've checked your RasPi's USB ports (try different port?), your USB cables, your USB connections, two different boards, then my guesses would be:
- some rogue process on your RasPi? (perhaps re-image)
- flaky power supply perhaps affecting the printer boards and/or RasPi
- a bug in Klipper (unusual, given you've tested both an lpc1768 & an stm32f407, and no-one else is reporting these issues)
How are you powering the RasPi? Hopefully not off the SKRs' 5V supply... Also, check for the RasPi undervolt flags. Also, check that the SKRs are not pulling 5V from the USB (J2 on the SKR Pro, J15 on the SKR 1.4).
Otherwise I don't have any other bright suggestions.
I'm using a 5v 3A psu and vcgencmd get_throttled
returns throttled=0x0
which means I should be in the clear for that.
I tried reinstalling just octoprint and klipper without any success, in the meantime tho I also noticed that my homeassistant install seems to be dead so I might try reinstalling the whole os and rechecking after that once I have a few hours for it. I wouldn't know how to check for other processes interfering with this but seems to be the most likely explanation. For the pulling you mean the switch from powering the board from either 12/24v and 5v? Both are set to 24v.
FWIW, the best advice I have is in the FAQ: https://www.klipper3d.org/FAQ.html#i-keep-getting-random-lost-communication-with-mcu-errors
As far as we know, the code works as intended. In similar reports in the past it was ultimately tracked down to loose wires, voltage fluctuations, or similar.
-Kevin
FWIW, the best advice I have is in the FAQ: https://www.klipper3d.org/FAQ.html#i-keep-getting-random-lost-communication-with-mcu-errors
As far as we know, the code works as intended. In similar reports in the past it was ultimately tracked down to loose wires, voltage fluctuations, or similar.
-KevinI'
Hi, following those didn't fix it but reinstalling the os, octoprint, restoring octo backup and klipper did so I don't know what was the issue but it doesn't seem to be klipper's fault, probably some rogue process, I'll close the issue.
klippy.log Hi, I recently set up and started using klipper on my ender 5 pro using an skr 1.4 turbo but after a couple days of almost flawless prints (once calibrated pressure advance) it started not being able to boot for enough time to even home x/y and then z, looking through the log there seem to be many [Errno16] Unable to open port:
[Errno 16] could not open port /dev/serial/by-id/
, I thought it could be a board problem and since I have an skr 1.2 pro laying around I also tried it with that other board (after changing the config to one that would work for the pro and compiling the firmware for it using stm32f407 and 32kib bootloader) and it gives me the same result and that leads me to believe that the problem doesn't lie on the 1.4t but it probably depends probably on klipper. The log includes both boards with their config and all the errors. A typical episode of this is like this one:and what shows in the log after it resembles
or