SPIDER is a small but powerful 3D printer control board. In a limited space, it integrates 8 stepper motor drives, 5A 12V power supply, 8A 5V power supply, which provides powerful energy for fans of various voltages, various RGB light strips and Raspberry Pi. You can build a 3D printer with rich functions through SPIDER. Especially for VORON V2.4, we cooperated with the VORON team in the early stage of design, and many features have been recognized by the VORON team. If you are building VORON, this will be your best choice.
V1.1
Add 5pin connector for BL-Touch
Switch EXP1 & EXP2 mark(Only mark, not socket)
Add +/- mark
Add room for RaspberryPI USB-A power supply port
You can solder the below USB port, then you can power-up RPI with a USB-A cable. It is USB power-supply port without USB signal.
V2.0
V2.1
V2.2
V2.3
V3.0
48v and 24v connector
为了兼容某些主板,如RAMPS1.4,FYSETC mini12864 设置了 RST(R3) 和 KILL(R4) 的可选择电阻。目前,有些主板(S6/Spider)将 KILL 换成 5V,此时,请确认FYSETC mini12864 上 R4处于空贴状态,否则按下屏幕上的按钮会致使 5V 与 GND 短路,长时间操作会导致主板损坏。
In order to be compatible with some motherboards, such as RAMPS1.4, mini12864 is equipped with RST (R3) and KILL (R4) optional resistors. At present, some motherboards (S6/Spider) change the KILL to 5V. At this time, please make sure that R4 is not on the mini12864 (please remove it if it is on the board), otherwise pressing the button on the screen will cause a short circuit between 5V and GND, and long-term operation will cause the motherboard to be damaged.
目前发现有些主板在接上 mini12864,并采用 USB 进行烧录时会导致无法烧录的情况,请去除 R1 10K 电阻。
At the moment , some Spider can't upload the firmware using USB if mini12864 is connected to the board, if you run into this issue, please remove R1 resistor.
If you want to enable Spider CANBUS network in Klipper, please check 4.2.1 chapter Communication interface
section.
Features | Spider Pin | STM32 Pin | Pin No. | Comment |
X-MOTOR(1) | X-Step | PE11 | 42 | |
X-DIR | PE10 | 41 | ||
X-EN | PE9 | 40 | ||
X-CS/PDN | PE7 | 38 | ||
Y-MOTOR(2) | Y-Step | PD8 | 55 | |
Y-DIR | PB12 | 51 | ||
Y-EN | PD9 | 56 | ||
Y-CS/PDN | PE15 | 46 | ||
Z-MOTOR(3) | Z-Step | PD14 | 61 | |
Z-DIR | PD13 | 60 | ||
Z-EN | PD15 | 62 | ||
Z-CS/PDN | PD10 | 57 | ||
E0-MOTOR(4) | E0-Step | PD5 | 86 | |
E0-DIR | PD6 | 87 | ||
E0-EN | PD4 | 85 | ||
E0-CS/PDN | PD7 | 88 | ||
E1-MOTOR(5) | E1-Step | PE6 | 5 | |
E1-DIR | PC13 | 7 | ||
E1-EN | PE5 | 4 | ||
E1-CS/PDN | PC14 | 8 | ||
E2-MOTOR(6) | E2-Step | PE2 | 1 | |
E2-DIR | PE4 | 3 | ||
E2-EN | PE3 | 2 | ||
E2-CS/PDN | PC15 | 9 | ||
E3-MOTOR(7) | E3-Step | PD12 | 39 | |
E3-DIR | PC4 | 33 | ||
E3-EN | PE8 | 59 | ||
E3-CS/PDN | PA15 | 77 | ||
E4-MOTOR(8) | E4-Step | PE1 | 34 | |
E4-DIR | PE0 | 97 | ||
E4-EN | PC5 | 98 | ||
E4-CS/PDN | PD11 | 58 | ||
TMC Driver SPI (SPI4) | MOSI | PE14 | 45 | |
MISO | PE13 | 44 | ||
SCK | PE12 | 43 | ||
End-stops | X-MIN | PB14 | 53 | Share with X-DIAG |
X-MAX | PA1 | 24 | Share with E0-DIAG | |
Y-MIN | PB13 | 52 | Share with Y-DIAG | |
Y-MAX | PA2 | 25 | Share with E1-DIAG | |
Z-MIN | PA0 | 23 | Share with Z-DIAG | |
Z-MAX(Probe) | PA3 | 26 | Share with E2-DIAG | |
FAN/RGB | FAN0 | PB0 | 35 | |
FAN1 | PB1 | 36 | ||
FAN2 | PB2/BOOT1 | 37 | ||
LED-R | PB6 | 92 | Can be used for fan3 | |
LED-G | PB5 | 91 | Can be used for fan4 | |
LED-B | PB7 | 93 | Can be used for fan5 | |
5V-LED(WS2812) | PD3 | 84 | Share with flash indicator(Bootloader) | |
Heating | E0-Heater | PB15 | 54 | |
E1-Heater | PC8 | 65 | ||
E2-Heater | PB3 | 89 | ||
Heated-Bed | PB4 | 90 | ||
Temperature | TE0(THERM0) | PC0 | 15 | A 4.7kOhm 0.1% temperature sensor pull up resistor is used,PT1000 can be connected directly. For PT100, an amplifier board must be used. |
TE1(THERM1) | PC1 | 16 | A 4.7kOhm 0.1% temperature sensor pull up resistor is used,PT1000 can be connected directly. For PT100, an amplifier board must be used. | |
TE2(THERM2) | PC2 | 17 | A 4.7kOhm 0.1% temperature sensor pull up resistor is used,PT1000 can be connected directly. For PT100, an amplifier board must be used. | |
TB(THERM3) | PC3 | 18 | A 4.7kOhm 0.1% temperature sensor pull up resistor is used,PT1000 can be connected directly. For PT100, an amplifier board must be used. | |
EXP2 | LCD_D7 | PD1/CAN-TX1 | 82 | Share with CAN-TX1 |
LCD_D6 | PD0/CAN-RX1 | 81 | Share with CAN-RX1 | |
LCD_D5 | PC12/MOSI3/TX5/SDA2 | 80 | ||
LCD_D4 | PC10/SCK3/TX3/4 | 78 | ||
LCD_EN | PC11/MISO3/RX3/4 | 79 | ||
LCD_RS | PD2/RX5 | 83 | ||
ENC_C | PA8/SCL3 | 67 | ||
BEEP | PC9/SDA3 | 66 | ||
EXP1 | RESET | NRST | 14 | |
ENC_A | PC6/TX6 | 63 | ||
ENC_B | PC7/RX6 | 64 | ||
SD-DET | PB10/SCL2 | 47 | ||
SD-MISO | PA6/MISO1 | 31 | ||
SD-MOSI | PA7/MOSI1 | 32 | ||
SCK | PA5/SCK1 | 30 | ||
CS | PA4/CS1 | 29 | ||
EEPROM(4K) I2C Pin-Out | SCL | PB8/SCL1 | 95 | Connect to 24LC32(4K EEPROM) |
SDA | PB9/SDA1 | 96 | Connect to 24LC32(4K EEPROM) | |
Pi_PWR/UART | TX | PA9/TX1 | 68 | |
RX | PA10/RX1 | 69 | ||
SWD Debug | PA13/SWDIO | 72 | only used for debugging now and can be used for other purposes. | |
PA14/SWCLK | 76 | only used for debugging now and can be used for other purposes. |
Features | Spider Pin | STM32 Pin | Pin No. | Comment |
X-MOTOR(1) | X-Step | PE11 | 42 | |
X-DIR | PE10 | 41 | ||
X-EN | PE9 | 40 | ||
X-CS/PDN | PE7 | 38 | ||
Y-MOTOR(2) | Y-Step | PD8 | 55 | |
Y-DIR | PB12 | 51 | ||
Y-EN | PD9 | 56 | ||
Y-CS/PDN | PE15 | 46 | ||
Z-MOTOR(3) | Z-Step | PD14 | 61 | |
Z-DIR | PD13 | 60 | ||
Z-EN | PD15 | 62 | ||
Z-CS/PDN | PD10 | 57 | ||
E0-MOTOR(4) | E0-Step | PD5 | 86 | |
E0-DIR | PD6 | 87 | ||
E0-EN | PD4 | 85 | ||
E0-CS/PDN | PD7 | 88 | ||
E1-MOTOR(5) | E1-Step | PE6 | 5 | |
E1-DIR | PC13 | 7 | ||
E1-EN | PE5 | 4 | ||
E1-CS/PDN | PC14 | 8 | ||
E2-MOTOR(6) | E2-Step | PE2 | 1 | |
E2-DIR | PE4 | 3 | ||
E2-EN | PE3 | 2 | ||
E2-CS/PDN | PC15 | 9 | ||
E3-MOTOR(7) | E3-Step | PD12 | 39 | |
E3-DIR | PC4 | 33 | ||
E3-EN | PE8 | 59 | ||
E3-CS/PDN | PA15 | 77 | ||
E4-MOTOR(8) | E4-Step | PE1 | 34 | |
E4-DIR | PE0 | 97 | ||
E4-EN | PC5 | 98 | ||
E4-CS/PDN | PD11 | 58 | ||
TMC Driver SPI (SPI4) | MOSI | PE14 | 45 | |
MISO | PE13 | 44 | ||
SCK | PE12 | 43 | ||
End-stops | X-MIN | PB14 | 53 | Share with X-DIAG |
X-MAX | PA1 | 24 | Share with E0-DIAG | |
Y-MIN | PB13 | 52 | Share with Y-DIAG | |
Y-MAX | PA2 | 25 | Share with E1-DIAG | |
Z-MIN | PA0 | 23 | Share with Z-DIAG | |
Z-MAX(Probe) | PA3 | 26 | Share with E2-DIAG | |
FAN/RGB | FAN0 | PA13 | 72 | |
FAN1 | PA14 | 76 | ||
FAN2 | PB2/BOOT1 | 37 | ||
LED-R | PB6 | 92 | Can be used for fan3 | |
LED-G | PB5 | 91 | Can be used for fan4 | |
LED-B | PB7 | 93 | Can be used for fan5 | |
5V-LED(WS2812) | PD3 | 84 | Share with flash indicator(Bootloader) | |
Heating | E0-Heater | PB15 | 54 | |
E1-Heater | PC8 | 65 | ||
E2-Heater | PB3 | 89 | ||
Heated-Bed | PB4 | 90 | ||
Temperature | TE0(THERM0) | PC0 | 15 | A 4.7kOhm 0.1% temperature sensor pull up resistor is used,PT1000 can be connected directly. For PT100, an amplifier board must be used. |
TE1(THERM1) | PC1 | 16 | A 4.7kOhm 0.1% temperature sensor pull up resistor is used,PT1000 can be connected directly. For PT100, an amplifier board must be used. | |
TE2(THERM2) | PC2 | 17 | A 4.7kOhm 0.1% temperature sensor pull up resistor is used,PT1000 can be connected directly. For PT100, an amplifier board must be used. | |
TE3(THERM3) | PC3 | 18 | A 4.7kOhm 0.1% temperature sensor pull up resistor is used,PT1000 can be connected directly. For PT100, an amplifier board must be used. | |
TE4(THERM4) | PB1 | 36 | A 4.7kOhm 0.1% temperature sensor pull up resistor is used,PT1000 can be connected directly. For PT100, an amplifier board must be used. | |
TB(THERM3) | PB0 | 35 | A 4.7kOhm 0.1% temperature sensor pull up resistor is used,PT1000 can be connected directly. For PT100, an amplifier board must be used. | |
EXP2 | LCD_D7 | PD1/CAN-TX1 | 82 | Share with CAN-TX1 |
LCD_D6 | PD0/CAN-RX1 | 81 | Share with CAN-RX1 | |
LCD_D5 | PC12/MOSI3/TX5/SDA2 | 80 | ||
LCD_D4 | PC10/SCK3/TX3/4 | 78 | ||
LCD_EN | PC11/MISO3/RX3/4 | 79 | ||
LCD_RS | PD2/RX5 | 83 | ||
ENC_C | PA8/SCL3 | 67 | ||
BEEP | PC9/SDA3 | 66 | ||
EXP1 | RESET | NRST | 14 | |
ENC_A | PC6/TX6 | 63 | ||
ENC_B | PC7/RX6 | 64 | ||
SD-DET | PB10/SCL2 | 47 | ||
SD-MISO | PA6/MISO1 | 31 | ||
SD-MOSI | PA7/MOSI1 | 32 | ||
SCK | PA5/SCK1 | 30 | ||
CS | PA4/CS1 | 29 | ||
EEPROM(4K) I2C Pin-Out | SCL | PB8/SCL1 | 95 | Connect to 24LC32(4K EEPROM) |
SDA | PB9/SDA1 | 96 | Connect to 24LC32(4K EEPROM) | |
Pi_PWR/UART | TX | PA9/TX1 | 68 | |
RX | PA10/RX1 | 69 | ||
SWD Debug | PA13/SWDIO | 72 | only used for debugging now and can be used for other purposes. | |
PA14/SWCLK | 76 | only used for debugging now and can be used for other purposes. |
Spider support Marlin firmware, Klipper firmware and RRF firmware. Choose one you need.
To compile the firmware , you need to install Visual Studio Code and the platformio pulg-in.
The Marlin firmware is in the firmware/Marlin
folder in this repository , you can also get the firmware from latest Marlin bugfix-2.0.x branch. You need to enable following define in configuration.h
file
#define MOTHERBOARD BOARD_FYSETC_SPIDER
#define SERIAL_PORT -1
Then we need to change platformio.ini
file
default_envs = FYSETC_S6
(For old bootloader,boot address is 0x10000
, see below)
default_envs = FYSETC_S6_8000
(For new bootloader,boot address is 0x8000
, see below)
Note: The bootloader boot address have been change to 0x08008000
since 2021/06/23, you can check bootloader details github or gitee, and you can check the Marlin PR here.
Open Vscode and open platformio main page and click the "Open Project" button , and direct to the folder where you put your firmware.
If everything goes fine , at the bottom you can see several buttons
The check mark is for compiling , click it to compile. You can find built firmware.bin
at .pio\build\FYSETC_S6
or .pio\build\FYSETC_S6_8000
folder.
Follow Firmware Update guide here.
We put Klipper related files like printer.cfg
in firmware/Klipper
folder in this repo. Please read the README there.
If you want to use Klipper. You need to follow the Klipper installation guide to install Klipper first. When we try to compile it, we need to call make menuconfig
to choose compile options, please select options for Spider as below describe.
Please choose these options for Spider, you need to decide which to choose according to your board and wiring on some options.
extra low-level configuration options
Select STMicroelectronics STM32
Select STM32F446
Select 12 MHz crystal
Choose 32kiB bootloader
offset in Klipper make menuconfig
. You may need to flash the spider board bootloader named Bootloader_FYSETC_SPIDER
first(If you get your Spider board after 2021/06/23
, no worries, the bootloader is on the board when it leave the factory,if not,flash it first). The bootloader is in the folder named bootloader
in this repo, please follow the README in bootloader folder(github or gitee) to flash the bootloader. We provide pre-build firmwares with 32KiB bootloader
named klipper-32k-USB.bin
and klipper-32k-UART.bin
for you,find them here github gitee. These pre-build firmware will be outdated if Klipper update and will not match your new downloaded Klipper and cause annoying issues. We will try to catch up with Klipper, but i recommend to build the firmware yourself.
You have there choices here, if you use USB cable to connect RaspeberryPI and Spider, you need to follow 1. USB (on PA11/PA12)
below. If you use serial to connect RaspberryPI and Spider, then check 2. Serial (on USART1 PA10/PA9)
. If you connect RaspberryPI and Spider with CAN bus, then check 3. CAN bus (on PD0/PD1)
.
If you want to connect Spider to RaspberryPI with USB cable. You need to select USB (on PA11/PA12)
And in printer.cfg
you need to set the serial as below. We provide an example cfg file printer.cfg
for VORON 2 machine here.
Obtain definition by "ls -l /dev/serial/by-id/" then unplug to verify
##--------------------------------------------------------------------
serial: /dev/serial/by-id/usb-Klipper_stm32f446xx_230032000851363131363530-if00
If you want to connect Spider UART1(RX1:PA10, TX1:PA9) port to RPI uart0(TX:GPIO14,RX:GPIO15) port, you need to select Serial (on USART1 PA10/PA9)
In printer.cfg
you need to uncomment the following line as our example printer.cfg
file here (github gitee)do, if your cfg file don't have this line, please add it.
serial: /dev/ttyAMA0
Besides this make option, you still need to follow the instructions that Connect RPI uart.md
file says, you can find the file github or gitee.
You need to follow Klipper CANBUS instruction here CANBUS - Klipper documentation after you compiled and upload the firmware.
make
Follow Firmware Update guide here.
As RRF firmware requires more than 512KB of Flash space, the Spider equipped with 446 cannot meet its requirements. So it needs to disable some features to make it work, please check the README in firmware/RRF folder github gitee.
We provide several ways to upload the firmware including SDCARD, dfu-util, DFU and platformio.
Uploading firmware using SD card is our default way to update the firmware as Spider already has the bootloader in it when it leave the factory. But if you once upload the firmware to Spider flash address 0x08000000
, then the bootloader in Spider will be gone, then you need to upload the bootloader to Spider yourself, please follow the README in bootloader folder (github or gitee) to upload the bootloader.
Uploading firmware using SD card: copy your compiled firmware file firmware.bin
(If you use klipper firmware, you need to rename klipper.bin
to firmware.bin
) file to the SD card , and insert it to the SD card slot which is at the right side of the board, and then power up the board. You may need to wait for about 30s to finish uploading, there is LED beside the sdcard slot blinking when it is uploading.
This method works in linux, that means should work in raspberry pi.
First power off the board
Set jumper on 5V pin and DC5V
Place jumper on BT0 to 3.3V pin
Connect USB cable to the board and your computer (If you use raspberry pi to upload firmware, connect USB cable to your raspberry pi)
Power up the board with 24v
Now the board is in DFU mode. If not, click the reset button. Also you can power on the board with 5v, but you need to set jumper on 5V and USB5V (Check the silkscreen lable on the back of the board) but not on 5V and DC5V.
REMEMBER to remove BT0 jumper if you finish uploading firmware or it will enter DFU mode again.
Make sure dfu-util is installed, shoot dfu-util --version
command to check.
Sample output:
dfu-util 0.9
Copyright 2005-2009 Weston Schmidt, Harald Welte and OpenMoko Inc.
Copyright 2010-2016 Tormod Volden and Stefan Schmidt
This program is Free Software and has ABSOLUTELY NO WARRANTY
Please report bugs to http://sourceforge.net/p/dfu-util/tickets/
If not , you should install it first, use the package manager of your distribution to get the latest version, like
sudo apt-get install dfu-util
Then use the command below to upload the firmware. You should replace firmware.bin
below with your built firmware bin(or hex) file location like out/klipper.bin
. Change flash address 0x08008000
to bootloader you choosed. (If you use Marlin firmware and your platformio env is default_envs = FYSETC_S6
, then you need to set it to 0x08010000
, if env is default_envs = FYSETC_S6_8000
, then you need to set it to 0x08008000
. If you use klipper firmware and you choose boot address No bootloader
when compiling then set it 0x08000000
, if 32kiB bootloader
, set it 0x08008000
. if 64KiB bootloader
set it to 0x08010000
.If yours is hex file, set it 0x08000000
).
dfu-util -R -a 0 -s 0x08008000:leave -D firmware.bin
Remove BT0 jumper and click the Spider RESET button.
The other way to upload the firmware is using DFU.
You can download it from ST website.
Chinese: STM32CubeProg
English: STM32CubeProg
Open the STM32CubeProgrammer software.
Now the board is in DFU mode. If not, click the reset button. Also you can power on the board with 5v, but you need to set jumper on 5V and USB5V (Check the silkscreen lable on the back of the board) but not on 5V and DC5V.
REMEMBER to remove BT0 jumper if you finish uploading firmware or it will enter DFU mode again.
Now you can connect and flash the Spider board with stm32cubeprogrammer with the following operation.
Do as the red number shows in the screen shot.
default_envs = FYSETC_S6
, then you need to set it to 0x08010000
, if env is default_envs = FYSETC_S6_8000
, then you need to set it to 0x08008000
. If you use klipper firmware and you choose boot address no bootloader
when compiling then set it 0x08000000
, if 32kiB bootloader
, set it 0x08008000
. if 64KiB bootloader
set it to 0x08010000
. If yours is hex file, don't need to set anything).Remove BT0 jumper and click the Spider RESET button.
If you compile Marlin yourself with platformio,you can follow the instructions below to upload the firmware.
First power off the board
Set jumper on 5v pin and DC5V
Place jumper on BT0 to 3.3V pin
Connect USB cable to the board and your computer
Power up the board with 24v
Now the board is in DFU mode. If not, click the reset button. Also you can power on the board with 5v, but you need to set jumper on 5V and USB5V (Check the silkscreen lable on the back of the board) but not on 5V and DC5V.
REMEMBER to remove BT0 jumper if you finish uploading firmware or it will enter DFU mode again.
If you suspect there is something wrong with your board, you can use our test firmware to have a test. Follow the README here (github gitee).
Please check here(github gitee).
Fix 1 : Please add a jumper on each TMC2209 on your Spider board. And restart the machine again.
Fix 2: Try to shoot Klipper command
INIT_TMC STEPPER=<name>
name can be stepper_x
,stepper_y
and other stepper in your printer.cfg
.
firmware.bin
not changed to old.bin
/bootloader not workingFix 1: Reflash the bootloader, follow the instruction here ( github gitee ).
Fix 2: Format your SD card with SD Card Formatter.
Fix 3: If you use Klipper firmware, choose No bootloader
option when compiling, and upload the firmware to 0x08000000
flash address. Refer to Upload the firmware(dfu-util) or Upload the firmware(DFU) chapter.
Try to set No bootloader
bootloader offset in Klipper make menuconfig
.This option means you don't have any bootloader flashed or don't want any bootloader, then you can follow Upload the firmware(DFU) to upload the firmware to Spider board. But you need to set the 'Start address' to 0x08000000.
You can submit issue in our github https://github.com/FYSETC/FYSETC-SPIDER/issues Or submit any technical issue into our forum