1. Product Introduction¶
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.
- Compact size: 155.3mm x 76.5mm
- Based on STM32F446 180Mhz，all IOs can withstand 5V voltage
- 8 TMC stepper drivers support, with Uart&SPI support
- Improved TMC jumper settings again，simpler and easier
- 28V input max，12V@5A DC-DC，5V@8A DC-DC (Especially for Raspberry Pi)，3.3V@0.8A LDO
- Two car fuses for hot bed input and main power input
- Limit switch socket 24V/5V/3.3V optional, ready for more other equipment, such as -inductive sensor, BL-Touch
- XH2.54 connectors
- 10x PWM capable power mosfet outputs (1 for HotBed, 3 for Heat-End, 3 for fans, 3 for RGB LED strip)
- 3pin temperature header, you can use thermistor or thermocouple (requires AD597 module)
- Up to 8 ways PWM fans (only use 1 extrueder and no 12V/24V RGB used )，2 ways RGB led(12V & 24V optional) ，1 way 5V-RGB led (NEO-PIXEL/WS2812)
- RepRapDiscount SmartController compatible pin header on board
- UART1-Raspberry Pi pin header (including 5V@8A power supply)
- 2X4 PinHeader Out for SD Card moudle
- Onboard micro-SD card
- Type-C and Type-B USB connector optional
- EXP1 & EXP2 have more multiplexing functions, such as USART, I2C, CAN
- SD card & USB upload support
- 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.
3. Haredware Guide¶
3.2 Wiring : FYSETC mini 12864 v2.1¶
为了兼容某些主板，如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.
3.3 Wiring : TMC2209¶
3.4 Pin Out¶
3.5 Pin Definition¶
|Features||Spider Pin||STM32 Pin||Pin No.||Comment|
|TMC Driver SPI (SPI4)||MOSI||PE14||45|
|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|
|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)|
|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.|
|EXP2||LCD_D7||PD1/CAN-TX1||82||Share with CAN-TX1|
|LCD_D6||PD0/CAN-RX1||81||Share with CAN-RX1|
|EEPROM(4K) I2C Pin-Out||SCL||PB8/SCL1||95||Connect to 24LC32(4K EEPROM)|
|SDA||PB9/SDA1||96||Connect to 24LC32(4K EEPROM)|
|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.|
4. Firmware Guide¶
4.1.1 Download Vscode + platformio¶
To compile the firmware , you need to install Visual Studio Code and the platformio pulg-in.
4.1.2 Download firmware¶
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
#define MOTHERBOARD BOARD_FYSETC_SPIDER
then change the
default_envs variant in
default_envs = FYSETC_SPIDER
4.1.3 Compile the firmware¶
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.
If you generate the hex file fail you may need to open vscode using Administrator Account .
4.1.5 Upload the firmware(SDCARD)¶
We provide several ways to upload the firmware .Uploading with SD card is our default way to update the firmware as the board already has the sdcard bootloader in it when it leave the factory. There is sdcard slot at the right side of the board.
Then,copy your compiled firmware file
klipper.binfile to the SD card , and insert it to the SD card slot, 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.
Note: The bootloader is in the folder named
bootloader, please follow the README in bootloader folder.
4.1.6 Upload the firmware(DFU)¶
The other way to upload the firmware is using DFU.
You can download it from ST website.
Open the STM32CubeProgrammer software.
b.Enter DFU mode¶
First power off the board , then jumper the BT0 to 3.3V (You can find them in the middle area of the board) , then connect the USB to the board and your computer , it will enter DFU mode . Now you can take the jumper away.
REMEMBER to remove the jumper if you finish uploading or it will enter DFU mode again.
c.Upload the firmware¶
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.
- Click the button to flesh the DFU port.
- Connect the DFU
- Choose the "firmware.bin" file.
- fill in the 'Start address' with 0x8010000
- Start Programming
When calling "menuconfig", enable "extra low-level configuration setup" and select the "12MHz crystal" as clock reference.
Boot address option1
At the moment ,i don't find boot address setting in Klipper, so all two firmwares we pre-build klipper.bin and klipper-UART0.bin (The differences between two firmware , you can check README here) are at boot address 0x8000000. Please follow Upload the firmware(DFU) to upload the firmware to Spider board. But you need to set the 'Start address' to 0x08000000 and Choose klipper.bin file but not firmware.bin.
Boot address option2
If Klipper future update support boot address settings for STM32F446 chips, then you can set the boot address to 0x08010000 and build Klipper yourself. Then you need to flash the spider board bootloader first. The bootloader is in the folder named
bootloader in this repo, please follow the README in bootloader folder. Then you can follow Upload the firmware(SDCARD) to flash your built Klipper firmware to Spider.
As RRF firmware requires more than 512KB of Flash space, the Spider equipped with 446 cannot meet its requirements. So Spider has another version dedicated to running RRF firmware, which uses STM32F407VGT6 MCU.
6. How to buy¶
7. Tech Support¶
Spider To-Do List:¶
Introduction This document introduces the use of Spider in detail, which will be designed by FYSETC and completed by your crowdsourcing.
Group friends who complete each document can get a piece of Spider (not including stepping driver), and difficult documents will increase the return as appropriate.
Friends who need any tutorials can leave a message here or firstname.lastname@example.org, I will add it to the TODO List.
This wiki will update the developer tasks from time to time. There are motherboard-related and other small projects. Friends who are interested can send an email to email@example.com.
Ordinary and simple tasks should be completed within one week, and difficult tasks should be relaxed as appropriate.
Each task can be claimed by multiple people at the same time, and the one who completes it first gets the reward. It can also be claimed by a team, and the rewards will be negotiated and distributed by the team.