From 38a2491e94b17f0e0b23aa3959202eceb1e328dd Mon Sep 17 00:00:00 2001 From: Guilherme Date: Fri, 12 Apr 2024 00:02:30 -0300 Subject: [PATCH] Update no_uuid.md added a section into possible wiring issues. --- troubleshooting/no_uuid.md | 1 + 1 file changed, 1 insertion(+) diff --git a/troubleshooting/no_uuid.md b/troubleshooting/no_uuid.md index a3bec99..f90792a 100644 --- a/troubleshooting/no_uuid.md +++ b/troubleshooting/no_uuid.md @@ -41,6 +41,7 @@ If it's sitting in Katapult but you still can't see a UUID then your problem is - If you suspect that CAN_L or CAN_H might be broken, measure in resistance mode (not continuity!) between CAN_L on one board with CAN_L on the other board. If you get 240 Ohms, then there's a break in CAN_L. Repeat the measurement for CAN_H +- Some users have encountered issues despite following the guide guide here. Everything seemed fine until attempting to flash Klipper on the SB2209. They could locate the board in DFU mode over USB, but the CAN UUID wasn't visible. Consequently, they were unable to flash Klipper onto the SB2209. It was discovered that the CAN wire provided with the BTT EBB SB2209 had the high and low data wire colors swapped compared to the picture in their documentation. By swapping the high and low data wires in the adapter, they were able to locate the CAN signal and successfully flash Klipper on the SB2209. ### can0 Interface