Motherboard ID Reading and Viewing
Please do not modify the configuration when translating the webpage
Please do not modify the configuration when translating the webpage
Please do not modify the configuration when translating the webpage
- CANBus UUID Acquisition
- USB ID Acquisition
- Before searching for the ID, connect the tool board to the UTOC or the motherboard with the bridge firmware flashed using the XT30 data cable, and the reference wiring diagram is below
- Please ensure that the CAN H and CAN L are measured with a multimeter at around
60Ω
under power-off conditions. If it is120Ω
, you need to connect a120Ω
jumper. If it is around40Ω
, you need to remove the jumperCAN Configuration and ID Search
- If you need to use CAN, please ensure that your host computer has performed CAN configuration.
NotePlease ensure that the mainboard is properly connected to the host computer before proceeding with the following operations.
warningPlease ensure that the host computer's CAN network, the CAN rate of the bridge mainboard, and the CAN tool board rate are completely consistent.
Precautions Before Device Search
- 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.
Device Search
- 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 thels
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.
- If entering
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 isFLY 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.
NoteYou can only proceed with searching for CAN IDs when
1d50:606f
is present.CAN ID Search
- 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 showsKlipper
, then this ID can be used directly. - If the ID appears and the
Application:
at the end showsCANBOOT
orKatapult
, 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 mainsailmachine
, click to enter, and you can findprinter.cfg
. -
Copy the queried UUID and fill it into the
[mcu]
section of thecanbus_uuid:
in theprinter.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.dangerousNote: 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.
-
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)
- 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.
PrecautionsYou 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
PrecautionsIf 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.
dangerousNote: 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.