Skip to main content

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

  • Please ensure the dip switch is set to the correct position
  • Please ensure that CAN H and CAN L measure about 60Ω with a multimeter when powered off. If it is 120Ω, the 120Ω jumper cap needs to be inserted. If it is about 40Ω, the jumper cap does not need to be inserted
  • Before burning the firmware, use an XT30 data cable to connect the tool board to the UTOC or the motherboard with the bridging firmware flashed. Below is the reference wiring diagram
  • Please ensure the dip switch is set to the correct position

Schematic diagram of KF interface​

Schematic diagram of XT30 interface​

  • Please ensure that CAN H and CAN L measure about 60Ω with a multimeter when powered off. If it is 120Ω, the 120Ω jumper needs to be connected. If it is about 40Ω, the jumper needs to be removed

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

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

    warning

    Please ensure that the host computer's CAN network, the CAN rate of the bridge mainboard, and the CAN tool board rate are completely consistent.

    • Before searching for CAN IDs, please connect to SSH.
    • Please note that you must ensure you are logging into SSH via the network rather than via serial port.
    • Ensure that the UTOC is properly connected or the mainboard has been flashed with the CAN bridge firmware, and ensure that the data cable connecting to the host computer has data transmission capability.
    • Now that you have successfully logged into the host computer, 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 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 are unable to assist. You 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 that 1d50:606f appears.
    • 1d50:606f belongs to the device you will be using. Ignore any subsequent prompts as system issues may cause it to display incompletely or not at all.
    • If there are multiple 1d50:606f, it is recommended to exclude one to avoid affecting subsequent firmware burning and connection to the firmware. For example, if it is FLY MINI PAD, it is recommended to use the onboard UTOC and not other CAN bridge devices.
    • If not, please check whether the data cable is properly connected and whether the firmware has been correctly flashed.
    Note

    You can only proceed with searching for CAN IDs when 1d50:606f is present.

    • Enter the following command to perform an ID search:
    ~/klippy-env/bin/python ~/klipper/scripts/canbus_query.py can0
    • If the ID appears and the Application: at the end shows Klipper, then this ID can be used directly.
    • If the ID appears and the Application: at the end shows CANBOOT or Katapult, then you need to flash the firmware to use it.

    CAN Issue Collection​

    Note
    • If you cannot find the CAN ID, please refer to the documentation below.
    • CAN Issue Collection

    Fill in the CAN ID into the Configuration​

    • Open the printer web interface, find printer.cfg under the configuration options on the left sidebar: for fluidd {...}; for mainsail machine, click to enter, and you can find printer.cfg.

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

      dangerous

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