Reading and Viewing Motherboard ID
Precautions Before Searching for Devices
- Before starting to get the ID, please first connect to SSH
- Please ensure that the data cable connecting the lower-level machine to the upper-level machine has data transmission capabilities
- After connecting to the upper-level machine via SSH, enter
lsusb
and press Enter. Several devices may appear as follows: - If the system does not support
lsusb
, you can execute the following command to install it:
sudo apt-get install usbutils


- Please confirm whether the motherboard firmware has been correctly flashed.
- If it is a USB firmware,
1d50:614e
should appear afterlsusb
. - If it is a USB bridge CAN firmware,
1d50:606f
should appear afterlsusb
. - If it is RS232, it needs to be paired with UTOR or G2T. G2T does not require searching for firmware, while UTOR should appear
1a86:7523
afterlsusb
.
Precautions While Searching for Devices
Search ID commands cannot be mixed!
- Please note that USB firmware can only use the USB ID search method.
- Please note that USB bridge CAN firmware can only use the CAN ID search method.
- Please note that RS232 firmware can only use the RS232 ID search method.
- If
0483:df11
appears, it may be due to the firmware being flashed but the motherboard not being powered off and restarted. If the motherboard remains unchanged after power-off and re-power-on, please check if DFU (jumpers/dip switches/buttons) has been disconnected. - If
2e8a:0003
appears, it may indicate that the wrong firmware was flashed. Please note that RP2040 can only flash UF2 firmware compiled, not other types of firmware. After2e8a:0003
appears, disconnect BOOT (jumpers/dip switches/buttons) to avoid flashing failure!!! - The UF2 firmware for RP2040 is compiled with
No bootloader
selected during compilation.
- USB ID Retrieval
- CANBus UUID Retrieval
Search for USB Tutorial
Precautions before searching for devices
- Before searching for the USB ID, please first connect to SSH
- Please note that it is necessary to ensure that the SSH is logged in using the network rather than the serial port.
- Please ensure that the motherboard with the USB firmware flashed is connected, and ensure that the data cable connecting the upper computer has a data transmission function.
Search for devices
- Please ensure that the upper computer can be connected to the network normally, and ensure that the data cable connecting the lower computer to the upper computer has a data transmission function.
- After connecting to the upper computer via SSH, enter
lsusb
and press Enter. If the information circled in the image below appears, you can proceed to the next step.- If there is no information feedback, this is a system problem of the upper computer, and we are powerless. You need to replace the system with a confirmed normal one or replace the upper computer.
- If the
lsusb
command is not found, you can execute this command to install it:sudo apt-get install usbutils
1d50:6177
is the device you need to use this time. The suffixOpenMoko, Inc. stm32f407xx
has a certain reference value, but it is not used as a judgment basis.- Some upper computers may have incomplete or no display due to system problems.
- If the
lsusb
command can display the device, but there is no1d50:6177
, please try to change the data cable and try to connect the motherboard to other USB ports of the upper computer.
- If you have previously performed the above steps and successfully burned the Klipper firmware, and the motherboard is operating normally, but only need to update the Klipper firmware, please directly view the
Firmware Update
chapter in the right sidebar of this page.
The next step can only be performed after the 1d50:6177
device is found.
Search for USBID
ls /dev/serial/by-id/*
- Enter the following command and press Enter. If everything is normal, a blue ID will appear in the following line. (The following is just for reference)

- If there is no ID after entering the following command, but there is a device in
lsusb
, please replace the upper computer or the upper computer system.
If multiple IDs appear, please select the corresponding ID according to the MCU model of your motherboard.
Fill in the USB ID in the configuration
-
Open the printer web interface, find in the configuration options on the left sidebar: for fluidd:
{…}
; for mainsail:Machine
, click to enter, and you can findprinter.cfg
. -
Copy the blue ID and fill it in the
serial:
of the[mcu]
node in theprinter.cfg
configuration. After saving and restarting, the motherboard can be connected. If Klipper promptsADC out of range
, it is a normal phenomenon. Connect the heated bed and the thermistor, configure the thermistor pins and output pins of the nozzle and the heated bed, and then save and restart.
Note: All IDs appearing in the document are examples. The actual ID of each motherboard is different. Please modify and fill in according to the ID actually obtained.
CAN Configuration and ID Search
- If you need to use CAN, make sure your host computer has undergone CAN configuration.
Please ensure the motherboard is properly connected to the host computer before proceeding with the following operations.
Please ensure that the CAN network on the host computer, the CAN rate of the bridge motherboard, and the CAN tool board rate are all consistent.
Precautions Before Device Search
- Before searching for CAN IDs, please first connect to SSH.
- Please note that you need to ensure you are logging into SSH via the network, not via serial port.
- Please ensure that the UTOC or a motherboard with CAN bridge firmware installed is properly connected, and the data cable connecting to the host computer has data transfer capability.
Device Search
- Now that you have successfully logged into the host computer, you can enter
lsusb
to search for devices. You will encounter one of the following situations:- Entering
lsusb
prompts that thels
command is not found; in this case, you can enter the following command to install the command:sudo apt-get install usbutils
- Entering
lsusb
produces no response. This is a system issue beyond our control; you will need to replace the system or use a confirmed working system. - The information shown below appears. Please note that this is only for reference. You only need to confirm that
1d50:606f
appears.
- Entering
1d50:606f
belongs to the device you will be using. Ignore any subsequent prompts as they may be incomplete or not displayed due to system issues.- If there are multiple
1d50:606f
, it is recommended to exclude one, otherwise it may affect subsequent firmware burning and connection, such as when using theFLY MINI PAD
, it is recommended to use the onboard UTOC and not other CAN bridge devices. - If none appear, please check if the data cable is properly connected and if the firmware is correctly installed.
You can only proceed with CAN ID search when 1d50:606f
is present.
CAN ID Search
- Enter the following command to search for IDs:
~/klippy-env/bin/python ~/klipper/scripts/canbus_query.py can0
- If an ID appears and the
Application:
at the end showsKlipper
, it means this ID can be used directly. - If an ID appears and the
Application:
at the end showsCANBOOT
orKatapult
, it means you need to flash the firmware to use it.
CAN Issue Collection
- If you cannot find a CAN ID, refer to the documentation below.
- CAN Issue Collection
Fill in the CAN ID into the Configuration
-
Open the printer's web interface. In the configuration options on the left sidebar, find
fluidd
:{...}
;mainsail
:Machine
, then click to accessprinter.cfg
. -
Copy the queried UUID and paste it into the
[mcu]
section of theprinter.cfg
configuration undercanbus_uuid:
. After saving and restarting, you should be able to connect to the motherboard. If Klipper prompts for firmware updates, ADC errors, etc., it indicates that Klipper has successfully connected to the motherboard.dangerousNote: All IDs mentioned in the document are examples. Each motherboard's ID is unique, so please modify according to the actual ID obtained.