Reading and Checking 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.

USB ID Retrieval

Search USB Tutorial

Precautions Before Searching for Devices

• Please connect to SSH before searching for the USB ID Connect to SSH
• Please note that you need to ensure that you log in to SSH via the network rather than via serial port
• Please ensure that the mainboard with the flashed USB firmware is connected, and the data cable connecting to the host computer has data transmission function

Search for Devices

• Ensure that the host computer can connect normally to the network, and ensure that the data cable connecting the downstream device to the host computer has data transmission function.
• After SSH connection to the host computer, 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 feedback at all, this is a system problem with the host computer. We are unable to help. You need to replace it with a confirmed normal system or replace the host computer.
  • If the prompt says there is no lsusb command, you can execute the following command to install:

    sudo apt-get install usbutils

    
• 1d50:6177 belongs to the device you will use this time.
  • Some host computers may not display fully or not display due to system issues.
  • If the lsusb command can display the device but does not show 1d50:6177, please try replacing the data cable and connecting the mainboard to another USB port on the host computer.
• If you have executed the above steps before and successfully burned the Klipper firmware, the mainboard is running normally, and you just need to update the Klipper firmware, please directly refer to the Firmware Update section in the right-hand menu bar of this page.

Note

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, one blue ID will appear. (The following is for reference only)

• If no ID appears after entering the command below, but lsusb shows the device, please replace the host computer or the host computer system.

Note

If multiple IDs appear, please select the corresponding 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 option 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] node in the printer.cfg configuration file. After saving and restarting, the motherboard can be connected. If Klipper prompts ADC out of range, it 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 shown in the document are examples. The actual ID of each mainboard is different. Please modify and fill in according to the actual obtained ID.

CANBus UUID Retrieval

CAN Configuration and ID Search

• If you need to use CAN, please confirm that your host computer has performed CAN configuration.

---

Notice

Please ensure the motherboard is connected to the host computer before performing the following operations.

warning

Please make sure the CAN network of the host computer, the CAN rate of the bridge motherboard, and the rate of the CAN tool board are completely consistent.

Precautions Before Device Search

• Before searching for the CAN ID, please first connect to SSH.
• Please note that it is necessary to ensure that the network login is used to SSH instead of serial port login.
• Please ensure that the UTOC is connected or the CAN bridge firmware is flashed on the motherboard, and ensure that the data cable connecting the host computer has data transmission capability.

Device Search

• Now that you have successfully logged into the host computer, you can enter lsusb to search for devices, which will result in 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 results in no response, this indicates a system issue, and we cannot help. You need to replace the system or use a confirmed normal system.
  • If the information shown in the image below appears, please note that this is just a reference. You only need to confirm that 1d50:606f appears.
    
• 1d50:606f belongs to the device you need to use. The subsequent prompts do not need to be concerned about, as system issues may cause them to display incompletely or not at all.
• If there are multiple 1d50:606f, it is recommended to exclude one, otherwise it will affect the subsequent burning and firmware connection. For example, if it is FLY MINI PAD, it is recommended to use the onboard UTOC and not other CAN bridge devices.
• If none appear, please check whether the data cable is properly connected and whether the firmware has been correctly flashed.

Notice

You can only proceed with CAN ID search when 1d50:606f appears.

CAN ID Search

• Enter the following command to search for the ID:

~/klippy-env/bin/python ~/klipper/scripts/canbus_query.py can0

• If an ID appears and the Application: at the end shows Klipper, it means this ID can be used directly.
• If an ID appears and the Application: at the end shows CANBOOT or Katapult, it means the firmware needs to be flashed before it can be used.
  

CAN Problem Collection

Notice

• If you cannot find the CAN ID, see the document below.
• CAN Problem Collection

Fill in the CAN ID into the Configuration

• Open the printer web interface, find printer.cfg in the configuration options on the left sidebar. For fluidd, it is {...}; for mainsail, it is Machine. Click to enter and locate printer.cfg.

  

• Copy the queried UUID and fill it into the canbus_uuid: field under the [mcu] node in the printer.cfg configuration. After saving and restarting, the mainboard can be connected. If Klipper prompts that the firmware needs to be updated or reports errors such as ADC, it indicates that Klipper has connected to the mainboard.

• If the Application: displays Canboot, it cannot be configured into the configuration file. You need to flash the Klipper firmware before proceeding.

  
  dangerous

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

• Below is a reference configuration:

  dangerous

  • This is a reference configuration method for one mainboard and one tool board.
  • If it is the mainboard ID, it must be [mcu] plus canbus_uuid: followed by the ID you searched for.
  • If it is the tool board, it must be [mcu tool board name] plus canbus_uuid: followed by the ID you searched for.