Skip to main content

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 after lsusb.
  • If it is a USB bridge CAN firmware, 1d50:606f should appear after lsusb.
  • 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 after lsusb.

Precautions While Searching for Devices​

Note

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. After 2e8a: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.

Search USB Tutorial​

Precautions Before Searching for Devices​

  • Before searching for the USB ID, please first connect to SSH
  • Please make sure you are logging in via network SSH rather than serial port SSH
  • Please ensure that the motherboard with the USB firmware installed is properly connected, and the data cable connecting it to the host computer has data transfer capability

Search for Devices​

  • Now that you have successfully logged into the host machine, you can enter lsusb to search for devices. You will encounter one of the following scenarios:
    • If entering lsusb prompts that the ls command is not found, you can enter the following command to install the command: 
      sudo apt-get install usbutils
    • If entering lsusb produces no response, this indicates a system issue beyond our control. You need to change the system or use a confirmed working system.
    • If you see the information shown in the image below, note that this is just a reference. You only need to confirm the characters after the ID.
  • 1d50:614e belongs to the device you will be using. Ignore the rest of the prompt as the system issue may cause it to display incompletely or not at all.
  • If none of the above occur, please check if the data cable is properly connected and if the firmware is correctly installed.
Note

You can only search for the USB ID when you have 1d50:614e.

Search for USB ID​

ls /dev/serial/by-id/*
  • Enter the command below and press Enter. If everything is normal, a blue ID will appear (the one below is just an example).
  • If no ID appears after entering the command below, but lsusb shows devices, try changing the host machine or the host machine's system.
Note

If multiple IDs appear, select the appropriate one based on your motherboard's MCU model.

Fill in the USB ID in the Configuration​

  • Open the printer web interface, find the configuration option in the left sidebar: for fluidd, it is {...}; for mainsail, it is machine, and click to access printer.cfg.

  • Copy the blue ID and fill it into the [mcu] section of the serial: parameter in the printer.cfg configuration file. Save and restart to connect to the motherboard. If Klipper displays ADC out of range, it is normal. Connect the bed and thermistor properly, configure the hotend and bed thermistor and output pins, then save and restart.

dangerous

Note: All IDs mentioned in the document are examples. The actual ID for each motherboard is unique. Please modify according to the actual ID obtained.