Toolboard ID Reading and Viewing

CANBus UUID Retrieval

• Please ensure the DIP switch is set to CAN mode
• Please confirm that the resistance measured with a multimeter between CAN H and CAN L is approximately 60Ω when powered off. If it is 120Ω, you need to enable the 120Ω DIP switch; if it is about 40Ω, the DIP switch should be turned off.
  
• Use an XT30 data cable to connect the toolboard to a UTOC or mainboard flashed with bridging firmware before searching for the ID. Below is a reference wiring diagram.
  

  Notes

  Notice

  • Ensure the tool board has been flashed with CAN firmware before the operation;
  • This tutorial is only applicable for searching the tool board ID, not for the main board ID;
  • Please connect the tool board to UTOC or a main board flashed with USB to CAN firmware;
  • Then connect the UTOC or the main board with USB to CAN firmware to the host computer before proceeding with the following operations.

  CAN Notes

  • This tutorial assumes your host computer has already been configured for CAN.
  • If you are using a Fly host computer and running either the Fly-Armbian or Fly-FAST system, CAN is already configured by default with a CAN speed of 1M.
  • If this is your first time using CAN, please read the tutorial below first.
  • CAN Configuration Tutorial

  Connect to SSH

  • First, log in to SSH via the network.
  • Please note that you must use network login to SSH, not serial port login.

  Search for Devices

  • Now that you have successfully logged into the host computer, you can enter lsusb to search for devices. You may encounter one of the following situations:
    • If entering lsusb prompts that the ls command is not found, you can install the required utility by entering the following command:

      sudo apt-get install usbutils

    • If there is no response after entering lsusb, this is a system issue and cannot be resolved here. You will need to change the system or use a known working system.
    • If information like that shown in the image below appears, please note that this is only a reference. You only need to confirm that 1d50:606f appears:
      
  • 1d50:606f is the device you will use in this instance.
  • If multiple 1d50:606f devices appear, one must be excluded, as multiple entries may affect subsequent flashing and firmware connection. For example, with FLY MINI PAD, it is recommended to use the onboard UTOC and avoid using other CAN bridges.
  • If the device does not appear, please check whether the data cable is properly connected and whether the correct firmware has been flashed.
  Note

  You can proceed to search for the CAN ID only when 1d50:606f appears.

  Search for CAN ID

  Search Method Using Fly_Armbian or Regular Host

  • Enter the following command to search for the ID:

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

  Search Method Using Fly_FAST

  • Enter the following command to search for the ID:

  python ~/klipper/scripts/canbus_query.py can0

  • After executing the search command, there may be several situations as follows. Please check and judge according to your own case:
    • 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 use.
    • If Total 0 uuids found appears, there may be several possible situations:
      • There is an issue with the CAN network configuration.
      • The CAN speed is inconsistent. Please ensure that the CAN speed of the host computer, main board, tool board, etc., is consistent.
      • The corresponding ID has already been configured in Klipper. You need to disable the ID in the system configuration, then shut down, power off, and restart.
        

  Fill the CAN ID into the configuration

  • Copy the queried UUID and then configure it into printer.cfg.

  • If the Application: shows Canboot, you cannot configure it into the configuration. You need to flash the Klipper firmware to proceed to the next step.

    
    dangerous

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

  For fluidd: {…}, click into it to find printer.cfg

  For mainsail: Machine, click into it to find printer.cfg

  • The following is a reference configuration:

    Notes

    • The toolboard in the configuration below refers to the name of the tool board. If it has a different name, please replace it accordingly.
    dangerous

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

    • The following is a reference configuration method for the MCU ID in the case of one main board plus one tool board.
    • If it is a main board ID, it must be [mcu toolboard] followed by canbus_uuid: and then the ID you searched for.
    • The following is a reference configuration:
    • Please note that this tutorial is for searching and configuring the tool board ID. Under normal circumstances, it is already properly connected to the main board.
    • And the main board must be [mcu], while the tool board is [mcu toolboard]
    
    • Click the SAVE & RESTART button in the upper right corner. It will automatically save and restart Klipper after clicking.

RS232 ID Retrieval

• Please ensure the DIP switch is set to RS232 mode
  
• Use an XT30 data cable to connect the toolboard to a UTOR or G2T before searching for the ID. Below is a reference wiring diagram.
  

  RS232 ID of the Toolboard

  Notes

  Important Preparation

  1. Firmware Requirement:
     The toolboard must be flashed with RS232 firmware, otherwise communication will not be possible.
  2. Common Ground Required:
     ⚠️ Before connecting the toolboard, ensure that the toolboard and mainboard share the same GND (can be achieved by using the same 24V/12V power supply)

  RS232 Notes

  • In addition to D8, D8PRO, and C8P, no other mainboards support the RS232 interface.
  • For unsupported mainboards, use G2T or UTOR for connection. This tutorial uses UTOR for connection.

  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 computer's IP is 192.168.101.179, directly enter it and press Enter.
  
  2. Open the WEB interface of the host computer, and in the configuration section of the left sidebar, find:

  For fluidd: {…}, click into it to find printer.cfg

  For mainsail: Machine, click into it to find printer.cfg

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

  4. Click SERIAL, then refresh:

     Refresh in fluidd:

     Refresh in mainsail:

  5. Copy the ID. Click as indicated by 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

     Notes

     • When connecting the toolboard using UTOR, two RS232_IDs typically appear. Please try them one by one.

  Fill in the Toolboard RS232 ID

  • Below is a reference configuration

    Notes

    • toolboard in the configuration below refers to the name of the toolboard. Replace it with the corresponding name if different.
    dangerous

    [mcu toolboard]
    serial: <Replace this with the ID you just looked up>

    • To add the ID for the toolboard, it must be [mcu toolboard] followed by serial:, then the ID of the toolboard you searched for.
    • Below is a reference configuration.
    • Please note that this tutorial focuses on searching for and configuring the toolboard ID, and normally the connection to the mainboard is already established.
    • Also note that the mainboard must be [mcu], and the toolboard is [mcu toolboard].
    • Click SAVE & RESTART at the top right corner, which will automatically save and restart klipper.
  dangerous

  Note: All IDs appearing in this document are examples. The ID of each mainboard is different in reality. Please fill in the actual obtained ID.

  dangerous

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

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

  ---