The latest release of the Fysetc Voron 2.4 Pro Kit comes with the Spider V3 and a SB CAN Toolhead Board. This guide will walk you through the setup process of the CAN network. The Spider has a built in CAN transceiver, so we need to flash it without the need of an additional CAN adapter. Make sure to read everything in full first, and the follow these steps in order.
The can0 file configures the speed at which the CAN network will run at. Follow these steps to create this file.
sudo nano /etc/network/interfaces.d/can0allow-hotplug can0
iface can0 can static
bitrate 1000000
up ip link set can0 txqueuelen 1024
sudo reboot and wait for the pi to reboot and make the changes. Now that we have the can0 file, the next step is the flash the Spider board.In order to flash the STMF446 chip in the Spider board, we need to put it in DFU mode. DFU mode will allow the board to accept new firmware that we flash to it.
lsusb in the SSH terminal. You should see the following:
There is no point in continuing if you do not see the desired result above. Firmware flash will not work if the board is not sitting in DFU mode. If you are not successful, repeat the procedure again or try the next method.

lsusb in the SSH terminal. You should see the following:
There is no point in continuing if you do not see the desired result above. Firmware flash will not work if the board is not sitting in DFU mode. If you are not successful, repeat the procedure again or send a message on Discord for help.
Now that the Spider is in DFU mode, we can flash some firmware to it.
cd klipper to change into the Klipper directory.make menuconfig to open the Klipper Firmware Configuration portal
q to exit, and then press y when prompted to save. You should be back into the normal ssh terminal now.make flash FLASH_DEVICE=0483:df11 to build and flash the firmware image to the Spider. If your board is not in DFU, this will not work.
This is an example of a successful flash. Note the "File downloaded successfully"
lsusb in the SSH terminal.Bus 001 Device 006: ID 1d50:606f OpenMoko, Inc. orBus 001 Device 006: ID 1d50:606f OpenMoko, Inc. Geschwister Schneider CAN adapterKlipper requires a CANBUS UUID for configuration instead of a traditional serial. Follow these steps to obtain it.
~/klippy-env/bin/python ~/klipper/scripts/canbus_query.py can0
The UUID is different for every Spider. Copy and paste your unique UUID in a notepad, and label it for the Spider. Later on we will get another one, so it is important to label it as the Spider's UUID.
Now that we have successfully flashed the Spider, we now need to do the same for the CAN Toolhead Board.
Just like how we put the Spider in DFU mode to flash it, we also need to put the CAN Toolhead Board in DFU mode. DFU mode will allow the board to accept firmware that we flash to it.

lsusb in the SSH terminal. You should see the following:
There is no point in continuing if you do not see the desired result above. Firmware flash will not work if the board is not sitting in DFU mode. If you are not successful, repeat the procedure again or leave a message on Discord for further assistance.
Now that the CAN Toolhead board is in DFU mode, we can flash some firmware to it.
cd klipper to change into the Klipper directory.make clean to get rid of the old make we used for the Spidermake menuconfig to open the Klipper Firmware Configuration portal
q to exit, and then press y when prompted to save. You should be back into the normal ssh terminal now.make flash FLASH_DEVICE=0483:df11 to build and flash the firmware image to the CAN Toolhead board. If your board is not in DFU, this will not work.
This is an example of a successful flash. Note the "File downloaded successfully"
Now that both boards are flashed with the correct firmware, we should have both UUIDs needed for Klipper.
~/klippy-env/bin/python ~/klipper/scripts/canbus_query.py can0
One of those UUIDs should be the Spider's, which you should have noted perviously. The other one is the CAN Toolhead board's UUID. Record and label it, as we will need to know which one is which.
The configuration files are available already on the Fysetc Github. In your printer.cfg, you will need to add the UUIDs in the right places. Ask for more assistance in Discord if you are unsure on how to do this, as it differs deepening on the config you are using.
QQ:1041794121
Facebook:https://www.facebook.com/groups/197476557529090
Discord:https://discord.gg/Fb6FdND4
E-mail:support@fysetc.com