Motherboard ID Reading and Viewing
Please do not modify the configuration when translating web pages.
Please do not modify the configuration when translating web pages.
Please do not modify the configuration when translating web pages.
- USB ID Acquisition
- USB Bridge CAN ID Acquisition
- Please prepare a data cable with data transfer 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)
- Note that you must log in to SSH via the network rather than via serial port
- Ensure that the mainboard with the flashed USB firmware is properly connected and that the data cable connecting it to the host computer has data transfer capability
Search for Devices
- Ensure that the host computer can access the internet normally and that the data cable connecting the peripheral device to the host computer has data transfer capability.
- After connecting to the host computer via SSH, enter
lsusb
and press Enter. If the information circled in the following image appears, you can proceed to the next step.- If there is no feedback, this indicates a problem with the host computer's system, and we are unable to assist; you need to replace the system with one that is confirmed to be working or replace the host computer.
- If the instruction
lsusb
is not found, you can execute the following command to install it:sudo apt-get install usbutils
1d50:6177
is the device you will be using for this task. The suffixOpenMoko, Inc. stm32f407xx
is somewhat indicative but should not be used as a basis for judgment.- Some host computers may display incomplete or no information due to system issues.
- If the
lsusb
command displays the device but does not show1d50:6177
, try changing the data cable and connecting the mainboard to another USB port on the host computer.
- If you have previously executed the above steps and successfully burned the Klipper firmware, and the mainboard is running normally, but you just want to update the Klipper firmware, refer directly to the
Firmware Update
section in the right-hand menu of this page.
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, a blue ID will appear. (The ID below is for reference only)

- If no ID appears after entering the command below, but
lsusb
shows devices, please replace the host computer or change the host computer system
If multiple IDs appear, select the appropriate 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 options in the left sidebar: fluidd is{...}
, mainsail isMachine
, click to enter. -
Copy the blue ID and paste it into the
serial:
field under the[mcu]
section in theprinter.cfg
configuration file. After saving and restarting, the mainboard should be connected. If Klipper promptsADC out of range
, this 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.
Note: All IDs mentioned in the document are examples. Each mainboard's ID is different, so modify and fill in according to the actual ID obtained.
- Please prepare a data cable with data transfer function. If the length is particularly long, it is recommended to use a data cable with a magnetic ring.
- Before searching for the ID, connect the tool board to the Gemini main board flashed with bridge firmware using an XT30 data cable.
- CAN tool board wiring reference:
- The 120Ω jumper needs to be connected:
CAN Configuration and ID Search
- If you need to use CAN, ensure that the host machine has been configured for CAN.
Ensure the main board is properly connected to the host machine before proceeding with the following operations.
Ensure the CAN network of the host machine, the CAN rate of the bridge main board, and the rate of the CAN tool board are completely consistent.
Precautions Before Searching for Devices
- Before searching for the CAN ID, please first connect to SSH.
- Ensure you are logged in via the network to SSH, not via serial port login.
- Ensure the UTOC is connected or the motherboard flashed with CAN bridge firmware, and the data cable connecting to the host machine has data transfer capability.
Device Search
- After logging into the host machine, enter the command
lsusb
to search for devices. Several scenarios may occur:- If the prompt says the
ls
command is not found, you can enter the following command to install it:sudo apt-get install usbutils
- If
lsusb
shows no reaction, this is a system issue, requiring a system replacement or using a normal system. - If the following information appears, confirm the presence of
1d50:606f
:
- If the prompt says the
1d50:606f
is the device required for this session. If there are multiple1d50:606f
, it is recommended to exclude one to avoid affecting subsequent operations.- If none are found, check whether the data cable is properly connected and whether the firmware is correctly flashed.
A 1d50:606f
must exist to search for the CAN ID.
CAN ID Search
- Enter the following command to search for the ID:
python ~/klipper/scripts/canbus_query.py can0
- If the ID appears and the
Application:
displaysKlipper
, then this ID can be used directly. - If the
Application:
displaysCANBOOT
orKatapult
, then the firmware needs to be flashed:
CAN Problem Collection
- If the CAN ID cannot be found, refer to the following document: CAN Problem Collection
Filling the CAN ID into the Configuration
- Open the printer's web interface and find the
printer.cfg
under the configuration option in the left sidebar:- fluidd:
{…}
- mainsail:
Machine
- fluidd:
- After clicking into it, copy and paste the queried UUID into the
canbus_uuid:
field under the[mcu]
node, save and restart to connect to the main board. - If Klipper prompts that the firmware needs to be updated or reports an ADC error, this indicates that Klipper has successfully connected to the main board.
Notice: All IDs in the documentation are examples. Each main board's ID is different, so please modify and fill in according to the actual obtained ID.