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, connect the tool board to the UTOC or the motherboard with the bridge firmware flashed using an XT30 data cable, and the reference wiring diagram is below
• Please ensure that the dip switch is set to the correct position
  
• 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, please ensure that your host computer has performed CAN configuration.

  ---

  Note

  Please ensure that the motherboard is properly connected to the host computer before performing the following operations.

  warning

  Please ensure that the CAN network of the host computer, the CAN rate of the bridged motherboard, and the rate of the CAN tool board are all identical.

  Precautions Before Searching for Devices

  • Before searching for the CAN ID, please first connect to SSH
  • Please note that you must log in to SSH via the network, not via serial port
  • Please ensure that a UTOC is connected or a motherboard with the CAN bridge firmware flashed is used, and ensure that the data cable connecting 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; one of the following situations may occur:
    • If entering lsusb prompts that the ls command is not found, you can install the command using the following instruction:

      sudo apt-get install usbutils

    • If nothing happens after entering lsusb, this is a system issue that we cannot resolve; you need to change the system or use a known good system
    • If information like in the image below appears, note that this is only a reference. You just need to confirm that 1d50:606f appears:
      
  • 1d50:606f is the device you will use this time
  • If there are multiple 1d50:606f, it is recommended to eliminate one as it may affect subsequent flashing and firmware connection; for example, FLY MINI PAD suggests using the onboard UTOC rather than other CAN bridge devices
  • If not present, please check that the data cable is properly connected and that the firmware is correctly flashed.
  Note

  The 1d50:606f must be present before searching for the CAN ID.

  Search for CAN ID

  • Enter the following command to search for the ID:

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

  • For FAST systems, use the following command:

  python ~/klipper/scripts/canbus_query.py can0

  • 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
    

  CAN Issue Collection

  Note

  • Before using CAN for the first time, it is recommended to read the CAN issue collection document below.
  • If you cannot find the CAN ID, please refer to the document below
  • CAN Issue Collection

  Fill in the CAN ID into the Configuration

  In Fluidd: {…}, click into it, and you can find printer.cfg

  In Mainsail: Machine, click into it, and you can find printer.cfg

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

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

    
    dangerous

    Note: All IDs appearing in the document are examples. Each motherboard has a different ID; please modify and fill in according to the ID actually obtained.

  • Below is a reference configuration

    dangerous

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

    • Below is a reference configuration method for the MCU ID in the case of one motherboard plus one tool board
    • If it is the motherboard ID, it must be [mcu] followed by canbus_uuid: and then the ID you searched for
    • If it is the tool board, it must be [mcu tool board name] followed by canbus_uuid: and then the ID you searched for
    

RS232 ID Acquisition

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

Search RS232 ID

Notes Before Searching for the Device

• Before searching for the RS232 ID, please ensure the following conditions are met:
• Please ensure the tool board has the RS232 firmware flashed
• Please ensure the tool board is connected to UTOR or G2T (if the main board has built-in RS232, please ignore this line)
• Please ensure the tool board and host computer share a common ground!!! This step is very important

Search for RS232 ID

1. Open a browser and enter the IP address of the host computer in the address bar. For example, if my host IP is 192.168.101.179, just type it in and press Enter.

2. Open the host computer's WEB interface and find the following in the configuration section of the left sidebar:

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

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

3. After clicking into printer.cfg, click on DEVICES at the top right corner:

4. Click on SERIAL, then refresh:

   Refresh in fluidd

   Refresh in mainsail

5. Copy the ID, click on the arrow to copy:

   In fluidd check if ttyUSB exists and ensure Path_by_hardware exists; this is the RS232_ID

   In mainsail check if ttyUSB exists and ensure Path_by_hardware exists; this is the RS232_ID

Fill in the RS232 ID

1. Close DEVICES and fill in the ID

Note

[mcu <Tool_board_name>]
serial: <Replace this with the ID you just found>
baud: 250000
restart_method:command

2. Fill the ID into the configuration:

tip

• After filling in the ID, click SAVE & RESTART at the top right corner

Note

• Among FLY products currently, only tool board type expansion boards use RS232 connection
• Mainboards use USB or CAN connections
• Therefore, this RS232 tutorial assumes that the [mcu] is already configured and only the tool board needs to be configured separately

dangerous

Note: All IDs shown in this document are examples. Each mainboard's ID is different, please fill in the actual obtained ID.

dangerous

Please note the IDs below are not usable !!!!!!

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

---

USB ID Acquisition

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

  Search USB Tutorial

  Precautions Before Searching for Devices

  • Please connect to SSH before searching for the USB ID Connect to SSH
  • Please note that you need to ensure that you log in to SSH via the network rather than via serial port
  • Please ensure that the mainboard with the flashed USB firmware is connected, and the data cable connecting to the host computer has data transmission function

  Search for Devices

  • Ensure that the host computer can connect normally to the network, and ensure that the data cable connecting the downstream device to the host computer has data transmission function.
  • After SSH connection to the host computer, enter lsusb and press Enter. If the information circled in the image below appears, you can proceed to the next step.
    • If there is no feedback at all, this is a system problem with the host computer. We are unable to help. You need to replace it with a confirmed normal system or replace the host computer.
    • If the prompt says there is no lsusb command, you can execute the following command to install:

      sudo apt-get install usbutils

      
  • 1d50:6177 belongs to the device you will use this time.
    • Some host computers may not display fully or not display due to system issues.
    • If the lsusb command can display the device but does not show 1d50:6177, please try replacing the data cable and connecting the mainboard to another USB port on the host computer.
  • If you have executed the above steps before and successfully burned the Klipper firmware, the mainboard is running normally, and you just need to update the Klipper firmware, please directly refer to the Firmware Update section in the right-hand menu bar of this page.
  Note

  You must query the 1d50:6177 device before proceeding to the next step

  Search for USBID

  ls /dev/serial/by-id/*

  • Enter the command below and press Enter. If everything is normal, one blue ID will appear. (The following is for reference only)
  
  • If no ID appears after entering the command below, but lsusb shows the device, please replace the host computer or the host computer system.
  Note

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

  Fill in the USB ID into the configuration

  • Open the printer web interface, find printer.cfg under the configuration option in the left sidebar: fluidd is {...}, mainsail is Machine, click to enter.

    

  • Copy the blue ID and paste it into the serial: field under the [mcu] node in the printer.cfg configuration file. After saving and restarting, the motherboard can be connected. If Klipper prompts ADC out of range, it is a normal phenomenon. Connect the heated bed and thermistor properly, configure the thermistor and output pins for the nozzle and heated bed, then save and restart.

    
  dangerous

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