Motherboard ID Reading and Viewing

tip

Please do not modify the configuration when translating the webpage

Notice

Please do not modify the configuration when translating the webpage

Important

Please do not modify the configuration when translating the webpage

CANBus UUID Acquisition

• Before searching for the ID, use an XT30 data cable to connect the tool board to the UTOC or the motherboard with the bridge firmware flashed. Below is the reference wiring diagram
  
• Please ensure that the CAN H and CAN L have a resistance of about 60Ω when measured with a multimeter under power-off conditions. If it is 120Ω, a 120Ω jumper needs to be connected. If it is about 40Ω, the jumper needs to be removed
  

  CAN Configuration and ID Search

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

  ---

  Notes

  Make sure the mainboard is connected to the host computer before proceeding with the following operations

  warning

  Make sure the CAN network of the host computer, the CAN speed of the bridge mainboard, and the CAN tool board speed are completely consistent

  Precautions Before Searching for Devices

  • Before searching for CAN ID, please connect to SSH
  • Please note that you need to log in to SSH via the network, not via the serial port
  • Make sure you have connected the UTOC or have flashed the CAN bridge firmware on the mainboard, and ensure that the data line connected to the host computer has data transmission functionality

  Search for Devices

  • Now that you have successfully logged in to the host computer, you can enter lsusb to search for devices, and one of the following situations will occur
    • Entering lsusb prompts that the ls command is not found, then you can enter the following command to install the command

      sudo apt-get install usbutils

    • Entering lsusb has no response, this is a system issue, we cannot do anything about it, you need to change the system or use a confirmed normal system
    • The information 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 this time
  • If there are multiple 1d50:606f, it is recommended to exclude one, otherwise it will affect the subsequent burning and firmware connection. For example, FLY MINI PAD is recommended to use the built-in UTOC instead of other CAN bridge devices
  • If not, please check by yourself whether the data cable is connected properly and whether the firmware is flashed correctly.
  Notes

  You can only search for CAN ID when there is 1d50:606f

  Search for CAN ID

  • Enter the following command to search for ID

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

  • FAST system uses the following command

  python ~/klipper/scripts/canbus_query.py can0

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

  CAN Problem Collection

  Notes

  • If you cannot find the CAN ID, please see the following document
  • CAN Problem Collection

  Fill in the CAN ID into the configuration

  Fluidd is: {…} , click to enter, you can find printer.cfg

  Mainsail is: Machine, click to enter, you can find printer.cfg

  • Copy the queried UUID and fill it into the canbus_uuid: in the [mcu] node of the printer.cfg configuration. After saving and restarting, it can connect to the mainboard. If Klipper prompts that the firmware needs to be updated, ADC error, etc., it means that Klipper has already connected to the mainboard

  • If Application: shows Canboot, it cannot be configured into the configuration, and you need to flash the Klipper firmware to proceed

    
    dangerous

    Note: All IDs mentioned in the document are examples. The actual ID of each mainboard is different. Please modify and fill in according to the actual ID obtained.

  • The following is a reference configuration

    dangerous

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

    • The following is a reference configuration method for MCU ID in the case of one mainboard and one tool board
    • If it is a mainboard ID, it must be [mcu] plus canbus_uuid: plus the ID you searched for
    • If it is a tool board, it must be [mcu Tool Board Name] plus canbus_uuid: plus the ID you searched for