Important Notes
- This tutorial specifically introduces wiring and searching IDs for the tool board; related steps do not apply to the main board, please distinguish carefully.
- If you are not using a tool board, please ignore this tutorial.
Tool Board ID Reading and Viewing
- Obtaining CANBus UUID
-
Please prepare a data cable with data transfer functionality; if the length is particularly long, it is recommended to use a cable with a ferrite core.
-
Before searching for the ID, connect the tool board to a Super8 main board flashed with bridging firmware using an XT30 data cable.
-
CAN tool board wiring reference:
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 withUSB to CAN
firmware; - Then connect the
UTOC
or the main board withUSB 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 theFly-Armbian
orFly-FAST
system,CAN
is already configured by default with a CAN speed of1M
. - 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 thels
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:
- If entering
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, withFLY MINI PAD
, it is recommended to use the onboardUTOC
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.
NoteYou 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
- Search Method Using Fly_FAST
- Enter the following command to search for the ID:
~/klippy-env/bin/python ~/klipper/scripts/canbus_query.py can0
- 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 showsKlipper
, it means this ID can be used directly. - If an ID appears and the
Application:
at the end showsCANBOOT
orKatapult
, 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.
- If an ID appears and the
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.dangerousNote: 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 findprinter.cfg
- For mainsail:
Machine
, click into it to findprinter.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 bycanbus_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.
- The
- Ensure the tool board has been flashed with