Motherboard ID Reading and Viewing
Please do not modify the configuration while translating the webpage
Please do not modify the configuration while translating the webpage
Please do not modify the configuration while translating the webpage
- CANBus UUID Acquisition
- RS232 ID Acquisition
- Before searching for the ID, connect the tool board to the UTOC or the motherboard with the bridging firmware flashed using the XT30 data cable, and the reference wiring diagram is below
- Please ensure the dip switch is set to the correct position
- Please ensure that the resistance between CAN H and CAN L is about
60Ω
when measured with a multimeter under power-off condition. If it is120Ω
, the120Ω
dip switch needs to be turned on. If it is about40Ω
, the dip switch needs to be turned offCAN 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.
- Before searching for the ID, connect the tool board to the UTOR or G2T using the XT30 data cable, and the reference wiring diagram is below
- Please ensure the dip switch is set to the correct position
Search for RS232 ID
Precautions Before Searching for the Device
- Before searching for the RS232 ID, please first connect to SSH
- Please note that you need to ensure that you are logging in to SSH via the network rather than through a serial port
- Please ensure that UTOR is connected and that the data cable connecting to the host computer has data transfer capability
- If using G2T, please determine whether the system supports UART connection
Search for the Device
- Now that you have successfully logged into the host computer, you can enter
lsusb
to search for devices. It will result in one of the following scenarios:- If entering
lsusb
prompts that thels
command cannot be found, you can enter the following command to install the command:sudo apt-get install usbutils
- If entering
lsusb
results in no reaction, this is a system issue and beyond our control. You will 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 the characters after the ID.
- If entering
1a86:7523
belongs to the device you need to use. The subsequent prompt does not need to be managed as the system issue may cause it to display incompletely or not at all.- If not, please check if the data cable is properly connected and if the firmware has been correctly flashed.
PrecautionsYou can only use the following command to search for the RS232 ID when there is
1a86:7523
.Search for RS232 ID
ls /dev/serial/by-path/*
- If there is no ID output after entering
ls /dev/serial/by-path/*
, butlsusb
shows a device, please replace the host computer or the host computer system - Please note that UTOR will output three IDs, and if you have used another UTOR system, it will record it and cause multiple IDs to appear during the search
- Please ensure that the ID ends with
-port0
otherwise it cannot be used.
PrecautionsPlease make sure that the tool board and UTOR are grounded!!! Otherwise, you cannot connect to the tool board!!!
Fill in the RS232 ID into the Configuration
-
Open the printer web interface, find
printer.cfg
under the configuration option on the left sidebar; for fluidd it is{...}
, and for mainsail it ismachine
, click in to findprinter.cfg
-
Copy the blue ID and fill it into the
serial:
field in the[mcu SHT36]
section of theprinter.cfg
configuration. After saving and restarting, you can connect to the mainboard. If Klipper promptsADC out of range
, it is a normal phenomenon. Connect the hot bed and thermistor well, configure the thermistor pins and output pins for the nozzle and hot bed, then save and restart.
Precautions- The RS232 ID needs to configure
baud:
andrestart_method:command
- Below is a reference configuration
[mcu SHT36]
serial: /dev/serial/by-path/platform-1c1c000.usb-usb-0:1.2:1.0-port0
baud: 250000
restart_method:commanddangerousNote: All IDs appearing in the document are examples. Each mainboard's ID is different, so please modify and fill in according to the actual obtained ID.
dangerousPlease note that the following ID cannot be used!!!!
serial: /dev/serial/by-id/usb-1a86_USB_Serial-if00-port0