Mainboard ID Reading and Viewing

Note

• This tutorial describes how to read and view the mainboard ID. For tool boards, please refer to the corresponding product ID search tutorial.
• If you are using a tool board, please click the button below to jump to the relevant page.
• Connect Tool Board

USB ID Retrieval

Notes

Note

• Make sure the motherboard has flashed the USB firmware before operating;
• This tutorial is only applicable for searching the Motherboard ID, not for Toolboard ID;
• Please ensure the host computer is properly connected to the motherboard before proceeding;
• For instructions on viewing the Toolboard ID, please refer to the relevant product documentation.

Connect to SSH

• Please log in to SSH via the network first
• Please ensure you are logging in to SSH via the network, not via serial port

Search for Device

• Please ensure the host computer is connected to the Internet and that the data cable connecting the device to the host computer supports data transfer.
• After SSH connecting to the host computer, enter lsusb and press Enter. If you see the information circled in the image below, you can proceed to the next step.
  • If no information is displayed, this indicates a system issue with the host computer. We cannot assist with this, and you will need to replace the system with a confirmed working one or change the host computer.
  • If the lsusb command is not found, install it by running the following command:

    sudo apt-get install usbutils

    
• 1d50:614e is the device you will use in this process.
  • Some host computers may fail to fully display or not display the information due to system issues.
  • If the device is shown after running the lsusb command but 1d50:614e is missing, try using a different data cable or connect the main board to another USB port on the host computer.

Note

You must proceed to the next step only after one of the 1d50:614e devices is found.

Search for USB ID

ls /dev/serial/by-id/*

• Enter the command below and press Enter. If everything works properly, a blue ID line like the one below will appear. (The example below is for reference only)

• If no ID appears after entering the command, but the device shows up in lsusb, please try using a different host computer or operating system

Note

If multiple IDs appear, please choose the corresponding ID based on your motherboard's MCU model.

Fill in the USB ID into the Configuration

For fluidd: {…}, click into it, and you can find printer.cfg

For mainsail: Machine, click into it, and you can find printer.cfg

Note: All IDs shown in this document are examples. The actual ID varies for each motherboard. Please modify and fill in based on the ID you obtained.

Fill in the USB ID

• Locate [mcu] and replace it

Note

• In the configuration file, replace:

[mcu]
serial: <Replace this with the ID you just queried>

• Reference examples

Example for fluidd

Example for mainsail

• Click SAVE & RESTART in the upper right corner. It will automatically save and restart klipper

CANBus UUID Retrieval

Precautions

Note

• Before proceeding, ensure the mainboard has been flashed with the USB bridge CAN firmware;
• This tutorial is only applicable for searching the mainboard ID, not for searching the toolboard ID;
• Please perform subsequent operations after correctly connecting the host computer to the mainboard;
• If you need to view the toolboard ID, please refer to the corresponding product directory for related tutorials.

CAN Precautions

• This tutorial assumes your host computer has already been configured for CAN
• If you are using a Fly host computer and are running the Fly-Armbian or Fly-FAST system, then CAN is already configured by default with a CAN baud rate of 1M
• If this is your first time using CAN, please read the tutorial below first
• CAN Configuration Tutorial

Connect to SSH

• Please first log in to SSH via the network
• Please note that you must use network login to SSH, not serial port login

Search for Devices

• Now that you have successfully logged into the host computer, you can enter lsusb to search for devices. You may encounter one of the following situations:
  • If entering lsusb prompts that the ls command is not found, you can install the required utility by entering the following command:

    sudo apt-get install usbutils

  • If there is no response after entering lsusb, this is a system issue and cannot be resolved here. You will need to change the system or use a known working system.
  • If information like that shown in the image below appears, please note that this is only a reference. You only need to confirm that 1d50:606f appears:
    
• 1d50:606f is the device you will use in this instance.
• If multiple 1d50:606f devices appear, one must be excluded, as multiple entries may affect subsequent flashing and firmware connection. For example, with FLY MINI PAD, it is recommended to use the onboard UTOC and avoid using other CAN bridges.
• If the device does not appear, please check whether the data cable is properly connected and whether the correct firmware has been flashed.

Note

You can proceed to search for the CAN ID only when 1d50:606f appears.

Search for CAN ID

Search method using Fly_Armbian or a regular host computer

• Enter the following command to search for the ID

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

Search method using Fly_FAST

• Enter the following command to search for the ID

python ~/klipper/scripts/canbus_query.py can0

• After executing the search command, there may be several scenarios, please troubleshoot and judge according to your specific situation
  • If an ID appears and the Application: at the end shows Klipper, then this ID can be used directly
  • If an ID appears and the Application: at the end shows CANBOOT or Katapult, then firmware flashing is required before use
  • If Total 0 uuids found appears, there could be several causes
    • The CAN network configuration is incorrect
    • The CAN baud rates are inconsistent, please ensure that the CAN baud rate of the host computer matches that of the mainboard, toolboard, etc.
    • If the corresponding ID has already been configured in Klipper, you need to disable the ID in the system configuration, then shut down the system, disconnect power, and restart
      

Enter the CAN ID into the configuration

• Copy the queried UUID, then go to the printer.cfg configuration

• If the Application: shows Canboot, it cannot be configured; you need to flash the Klipper firmware before proceeding to the next step

  
  dangerous

  Note: All IDs shown in this document are examples. The ID of each mainboard is different, please modify and enter the actual obtained ID.

In fluidd: {…} , click to enter and you can find printer.cfg

In mainsail: Machine, click to enter and you can find printer.cfg

• Below is a sample configuration
  dangerous

  [mcu]
  canbus_uuid: <Replace this with the ID you just queried>

  • The mainboard ID must be [mcu] followed by canbus_uuid: and then the ID you searched for
  
  • Click SAVE & RESTART in the upper right corner, which will automatically save and restart Klipper