Motherboard ID Reading and Viewing

tip

Please do not modify the configuration while translating the webpage

Notice

Please do not modify the configuration while translating the webpage

Important

Please do not modify the configuration while translating the webpage

CANBus UUID Acquisition

• Before searching for the ID, connect the tool board to the UTOC or the motherboard with the bridging firmware flashed using the XT30 data cable, and the reference wiring diagram is below
• Please ensure the dip switch is set to the correct position
  
• Please ensure that the resistance between CAN H and CAN L is about 60Ω when measured with a multimeter under power-off condition. If it is 120Ω, the 120Ω dip switch needs to be turned on. If it is about 40Ω, the dip switch needs to be turned off
  

  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.
    

RS232 ID Acquisition

• Before searching for the ID, connect the tool board to the UTOR or G2T using the XT30 data cable, and the reference wiring diagram is below
• Please ensure the dip switch is set to the correct position
  

  Search for RS232 ID

  Precautions Before Searching for the Device

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

  Search for the Device

  • Now that you have successfully logged into the host computer, you can enter lsusb to search for devices. It 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 reaction, this is a system issue and beyond our control. You will need to change the system or use a confirmed normal system
    • If the information shown below appears, please note that this is just a reference. You only need to confirm the characters after the ID.
    
  • 1a86:7523 belongs to the device you need to use. The subsequent prompt does not need to be managed as the system issue may cause it to display incompletely or not at all.
  • If not, please check if the data cable is properly connected and if the firmware has been correctly flashed.
  Precautions

  You can only use the following command to search for the RS232 ID when there is 1a86:7523.

  Search for RS232 ID

  ls /dev/serial/by-path/*

  
  • If there is no ID output after entering ls /dev/serial/by-path/*, but lsusb shows a device, please replace the host computer or the host computer system
  • Please note that UTOR will output three IDs, and if you have used another UTOR system, it will record it and cause multiple IDs to appear during the search
  • Please ensure that the ID ends with -port0 otherwise it cannot be used.
  Precautions

  Please make sure that the tool board and UTOR are grounded!!! Otherwise, you cannot connect to the tool board!!!

  Fill in the RS232 ID into the Configuration

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

    

  • Copy the blue ID and fill it into the serial: field in the [mcu SHT36] section of the printer.cfg configuration. After saving and restarting, you can connect to the mainboard. If Klipper prompts ADC out of range, it is a normal phenomenon. Connect the hot bed and thermistor well, configure the thermistor pins and output pins for the nozzle and hot bed, then save and restart.

    
  Precautions

  • The RS232 ID needs to configure 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 appearing in the document are examples. Each mainboard's ID is different, so please modify and fill in according to the actual obtained ID.

  dangerous

  Please note that the following ID cannot be used!!!!

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

  ---