KUSBA
KUSBA copied to clipboard
xbst
Kusba doesn't shows on raspberry klipper usb ports
Hello,
I have a kusba v2.3. I try to get it to work on klipper. I previously installed the gpio adxl but I want the usb version.
I tried to flash the kusba, I pressed the button and connected it to my laptop, then I copied the klippee.u2f that I created with "menu makeconfig".
With the settings "no bootloader" "usb" and "raspberry rf 2040".
The kusba restarts, then I plugged it in the raspberry with my klipper. But I can't find ethe device under the usb ports (dsmeg or the other command. )
I tried different cables, Noone work.has someone a idea ?
Thank
Ciao, ho esattamente lo stesso problema tuo. Dopo vari tentativi oggi sono riuscito a fare l'input shaping però dal momento che spengo e riaccendo la stampante non mi trova più il seriale. Tu hai risolto?
I have the same problem. The KUSBA does not show up when I plug it in holding the boot button in. The ls /dev/ command results are identical with and without it plugged in. Unfortunately the KUBSA does not have any LED showing the unit is actually powered on so I can't even tell if it is working. I'm running Klipper on a BTT Pi v1.2 with a HDMI5 screen and I'm not sure if either one could be causing the issue.
hi, I solved the problem. in the cfg printer I had the configuration of another accelerometer and therefore they conflicted, after which I also made a mistake in pressing the button when I wanted to make it work. therefore, I insert the USB cable without pressing the button, I remove the
from the cfg printer, I do shaper_calibrate, the first time it gives an
error and the second time it starts working.
Il Lun 11 Set 2023, 02:33 Johnmkar @.***> ha scritto:
I have the same problem. The KUSBA does not show up when I plug it in holding the boot button in. The ls /dev/ command results are identical with and without it plugged in. Unfortunately the KUBSA does not have any LED showing the unit is actually powered on so I can't even tell if it is working. I'm running Klipper on a BTT Pi v1.2 with a HDMI5 screen and I'm not sure if either one could be causing the issue.
— Reply to this email directly, view it on GitHub https://github.com/xbst/KUSBA/issues/25#issuecomment-1712991553, or unsubscribe https://github.com/notifications/unsubscribe-auth/AVJFCYNNWL2OMO56HCD6A5DXZZL4HANCNFSM6AAAAAA3WS32AI . You are receiving this because you commented.Message ID: @.***>
I haven't gotten to the point of configuring the accelerometer in printer.cfg. There is nothing configured for another one. I can't located it when ssh into the Pi and do the ls/dev/ command so I can flash the firmware. That's why I'm wondering if the board is dead or there is a conflict with my HDMI5 screen, since the only USB listed is TTYUSB0, and it's shown regardless of whether or not the KUSBA is plugged in or not. I would expect TTYUSB1 to show up.
I can't comment on the potential display conflict as I don't have a setup like that, but one of the first steps of troubleshooting issues like this is trying another USB cable. A lot of USB C cables don't have the data pins so it can't communicate with the Pi. I'd also try connecting it to a different computer to verify if the issue is caused by the setup with the display or cable or bad KUSBA. On a Windows PC, unflashed KUSBA will look like a USB drive, flashed one will open a serial (COM) port, which should show up in device manager.
From: Johnmkar @.> Sent: Monday, September 11, 2023 7:50:21 AM To: xbst/KUSBA @.> Cc: Subscribed @.***> Subject: Re: [xbst/KUSBA] Kusba doesn't shows on raspberry klipper usb ports (Issue #25)
I haven't gotten to the point of configuring the accelerometer in printer.cfg. There is nothing configured for another one. I can't located it when ssh into the Pi and do the ls/dev/ command so I can flash the firmware. That's why I'm wondering if the board is dead or there is a conflict with my HDMI5 screen, since the only USB listed is TTYUSB0, and it's shown regardless of whether or not the KUSBA is plugged in or not. I would expect TTYUSB1 to show up.
— Reply to this email directly, view it on GitHubhttps://github.com/xbst/KUSBA/issues/25#issuecomment-1713814498, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AO2M47OUH4RILPO7TYMDFOLXZ4CI3ANCNFSM6AAAAAA3WS32AI. You are receiving this because you are subscribed to this thread.Message ID: @.***>
I too have tried different cables, however I am noticing that every now and then I connect the USB cable and there is no signal, I plug it in and out 2/3 times and it goes. it is a strange thing. Luckily it works but it's not accurate on the first try
Il Lun 11 Set 2023, 16:58 xbst @.***> ha scritto:
I can't comment on the potential display conflict as I don't have a setup like that, but one of the first steps of troubleshooting issues like this is trying another USB cable. A lot of USB C cables don't have the data pins so it can't communicate with the Pi. I'd also try connecting it to a different computer to verify if the issue is caused by the setup with the display or cable or bad KUSBA. On a Windows PC, unflashed KUSBA will look like a USB drive, flashed one will open a serial (COM) port, which should show up in device manager.
From: Johnmkar @.> Sent: Monday, September 11, 2023 7:50:21 AM To: xbst/KUSBA @.> Cc: Subscribed @.***> Subject: Re: [xbst/KUSBA] Kusba doesn't shows on raspberry klipper usb ports (Issue #25)
I haven't gotten to the point of configuring the accelerometer in printer.cfg. There is nothing configured for another one. I can't located it when ssh into the Pi and do the ls/dev/ command so I can flash the firmware. That's why I'm wondering if the board is dead or there is a conflict with my HDMI5 screen, since the only USB listed is TTYUSB0, and it's shown regardless of whether or not the KUSBA is plugged in or not. I would expect TTYUSB1 to show up.
— Reply to this email directly, view it on GitHub< https://github.com/xbst/KUSBA/issues/25#issuecomment-1713814498>, or unsubscribe< https://github.com/notifications/unsubscribe-auth/AO2M47OUH4RILPO7TYMDFOLXZ4CI3ANCNFSM6AAAAAA3WS32AI>.
You are receiving this because you are subscribed to this thread.Message ID: @.***>
— Reply to this email directly, view it on GitHub https://github.com/xbst/KUSBA/issues/25#issuecomment-1714062331, or unsubscribe https://github.com/notifications/unsubscribe-auth/AVJFCYJ2N5XFV7MPS6NEW7LXZ4RKVANCNFSM6AAAAAA3WS32AI . You are receiving this because you commented.Message ID: @.***>