Motherboard ID Reading and Viewing

tip

Please do not modify the configuration when translating on the web.

Notice

Please do not modify the configuration when translating on the web.

Important Notice

Please do not modify the configuration when translating on the web.

USB ID Acquisition

• Please prepare a data cable with data transmission capability. If the length is particularly long, it is recommended to use a cable with a magnetic ring.

  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.

USB Bridge CAN ID Acquisition

• Please prepare a data cable with data transmission capability. If the length is particularly long, it is recommended to use a cable with a magnetic ring.
• Before searching for the ID, use the XT30 data cable to connect the tool board to the D7 motherboard flashed with bridge firmware.
• Please connect the 120Ω jumper, and below is a reference wiring diagram.
  
• CAN tool board wiring reference
  

  CAN Configuration and ID Search

  • If you need to use CAN, make sure your host computer has undergone CAN configuration.

  ---

  Notice

  Please ensure the motherboard is properly connected to the host computer before proceeding with the following operations.

  warning

  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 the ls 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.
      
  • 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 the FLY 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.
  Note

  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 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 you need to flash the firmware to use it.
    

  CAN Issue Collection

  Notice

  • 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 access printer.cfg.

    

  • Copy the queried UUID and paste it into the [mcu] section of the printer.cfg configuration under canbus_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.

    
    dangerous

    Note: All IDs mentioned in the document are examples. Each motherboard's ID is unique, so please modify according to the actual ID obtained.

RS232 ID Acquisition

• Please check if the DIP switch is set to the correct position.
  

  Search for RS232 ID

  Precautions Before Searching for Devices

  • Before searching for the RS232 ID, please first connect to SSH
  • Please note that you need to ensure that you are logging in via SSH using the network, not via a serial port
  • Please ensure that UTOR is properly connected and that the data cable connecting to the host computer has data transfer capabilities
  • If using G2T, confirm whether the system supports UART connection

  Searching for Devices

  • Now that you have successfully logged into the host machine, you can enter lsusb to search for devices. This will result in one of the following scenarios:
    • If entering lsusb prompts that the ls command cannot be 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. You will need to change the system or use a confirmed working system.
    • If you see the information shown in the image below, please note that this is just a reference. You only need to determine the characters after the ID.
    
  • 1a86:7523 belongs to the device you need to use. The subsequent prompts do not need to be concerned with because system issues may cause it to display incompletely or not at all.
  • If none of these apply, please check if the data cable is properly connected and if the firmware has been correctly flashed.
  Note

  You can only use the commands below to search for the RS232 ID when you have 1a86:7523.

  Searching for RS232 ID

  ls /dev/serial/by-path/*
  
  • If entering ls /dev/serial/by-path/* does not produce any IDs, but lsusb shows devices, consider replacing the host machine or the host machine's system.
  • Please note that using UTOR will output three IDs, and if you have used another UTOR system before, it may record them, leading to multiple IDs appearing during the search.
  • Ensure that the ID ends with -port0, otherwise it cannot be used.
  Note

  Please make sure that the tool board and UTOR are grounded!!! Otherwise, you will not be able to connect to the tool board!!!

  Enter the RS232 ID into the Configuration

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

    

  • Copy the blue ID and paste it into the [mcu] section of the printer.cfg configuration file under serial:. After saving and restarting, you should be able to connect to the mainboard. If Klipper prompts ADC out of range, this is normal. Connect the hotbed and thermistor properly, configure the thermistor pins and output pins for the nozzle and hotbed, then save and restart.

    
  Note

  • The RS232 ID needs to be configured with baud: and restart_method:command.
  • Below is a reference configuration:

  [mcu SHT36]
  serial: /dev/serial/by-path/platform-1c1c000.usb-usb-0:1.2:1.0-port0
  baud: 250000
  restart_method:command
  dangerous

  Note: All IDs mentioned in the document are examples. Each motherboard’s ID is unique, so please modify and fill in according to the actual ID obtained.

  dangerous

  Please note that the IDs below cannot be used!!!

  serial: /dev/serial/by-id/usb-1a86_USB_Serial-if00-port0

  ---