Skip to main content

Reading and Viewing the Motherboard ID

Precautions Before Searching for Devices​

  • Before obtaining the ID, please first connect to SSH.
  • Please ensure that the data cable connecting the lower computer to the upper computer has data transfer capabilities.
  • After connecting to the upper computer via SSH, input lsusb and press Enter. Several devices may appear.
  • If the system does not support lsusb, you can execute the following command to install it.
  • If no devices appear after lsusb, please replace the upper computer!
sudo apt-get install usbutils
  • Please confirm whether the motherboard firmware has been flashed with the correct firmware.
  • 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 an RS232 firmware, UTOR or G2T must be used in conjunction. G2T does not require firmware searching, while UTOR should appear as 1a86:7523 after lsusb.

Precautions During Searching for Devices​

Notice

The search ID command 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 indicate that the firmware has been flashed but the motherboard was not powered off and restarted. If the issue persists after powering off and restarting the motherboard, check if DFU (jumper/dip switch/button) has been disconnected.
  • If 2e8a:0003 appears, it may indicate that the wrong firmware has been flashed. Note that RP2040 can only flash UF2 firmware compiled from source code; other firmware cannot be flashed. After 2e8a:0003 appears, disconnect BOOT (jumper/dip switch/button) to avoid flashing failure!!!
  • The UF2 firmware for RP2040 is compiled with No bootloader option to generate the UF2 firmware.

Search USB Tutorial​

Precautions Before Searching for Devices​

  • Please connect to SSH before searching for the USB ID (Connect to SSH)
  • Note that you must log in to SSH via the network rather than via serial port
  • Ensure that the mainboard with the flashed USB firmware is properly connected and that the data cable connecting it to the host computer has data transfer capability

Search for Devices​

  • Ensure that the host computer can access the internet normally and that the data cable connecting the peripheral device to the host computer has data transfer capability.
  • After connecting to the host computer via SSH, enter lsusb and press Enter. If the information circled in the following image appears, you can proceed to the next step.
    • If there is no feedback, this indicates a problem with the host computer's system, and we are unable to assist; you need to replace the system with one that is confirmed to be working or replace the host computer.
    • If the instruction lsusb is not found, you can execute the following command to install it: 
      sudo apt-get install usbutils
  • 1d50:6177 is the device you will be using for this task. The suffix OpenMoko, Inc. stm32f407xx is somewhat indicative but should not be used as a basis for judgment.
    • Some host computers may display incomplete or no information due to system issues.
    • If the lsusb command displays the device but does not show 1d50:6177, try changing the data cable and connecting the mainboard to another USB port on the host computer.
  • If you have previously executed the above steps and successfully burned the Klipper firmware, and the mainboard is running normally, but you just want to update the Klipper firmware, refer directly to the Firmware Update section in the right-hand menu of this page.
Precautions

You must query the 1d50:6177 device before proceeding to the next step.

Search for USBID​

ls /dev/serial/by-id/*
  • Enter the command below and press Enter. If everything is normal, a blue ID will appear. (The ID below is for reference only)
  • If no ID appears after entering the command below, but lsusb shows devices, please replace the host computer or change the host computer system
Precautions

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

Fill in the USB ID into the Configuration​

  • Open the printer web interface, find printer.cfg under the configuration options in the left sidebar: fluidd is {...}, mainsail is Machine, click to enter.

  • Copy the blue ID and paste it into the serial: field under the [mcu] section in the printer.cfg configuration file. After saving and restarting, the mainboard should be connected. If Klipper prompts ADC out of range, this is a normal phenomenon; connect the heated bed and thermistor properly, configure the thermistor and output pins for the nozzle and heated bed, then save and restart.

dangerous

Note: All IDs mentioned in the document are examples. Each mainboard's ID is different, so modify and fill in according to the actual ID obtained.