Skip to content

FYSETC SPIDER

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.

2. Features

  • 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. Hardware Guide

3.1 Spider v1.0 wiring

3.2 Spider v1.1 wiring

3.3 Wiring : FYSETC mini 12864 v2.1

注意/NOTICE

为了兼容某些主板,如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.4 Wiring : TMC2209

3.5 Pin Out

3.6 Pin Definition

FeaturesSpider PinSTM32 PinPin No.Comment
X-MOTOR(1)X-StepPE1142
X-DIRPE1041
X-ENPE940
X-CS/PDNPE738
Y-MOTOR(2)Y-StepPD855
Y-DIRPB1251
Y-ENPD956
Y-CS/PDNPE1546
Z-MOTOR(3)Z-StepPD1461
Z-DIRPD1360
Z-ENPD1562
Z-CS/PDNPD1057
E0-MOTOR(4)E0-StepPD586
E0-DIRPD687
E0-ENPD485
E0-CS/PDNPD788
E1-MOTOR(5)E1-StepPE65
E1-DIRPC137
E1-ENPE54
E1-CS/PDNPC148
E2-MOTOR(6)E2-StepPE21
E2-DIRPE43
E2-ENPE32
E2-CS/PDNPC159
E3-MOTOR(7)E3-StepPD1239
E3-DIRPC433
E3-ENPE859
E3-CS/PDNPA1577
E4-MOTOR(8)E4-StepPE134
E4-DIRPE097
E4-ENPC598
E4-CS/PDNPD1158
TMC Driver SPI (SPI4)MOSIPE1445
MISOPE1344
SCKPE1243
End-stopsX-MINPB1453Share with X-DIAG
X-MAXPA124Share with E0-DIAG
Y-MINPB1352Share with Y-DIAG
Y-MAXPA225Share with E1-DIAG
Z-MINPA023Share with Z-DIAG
Z-MAX(Probe)PA326Share with E2-DIAG
FAN/RGBFAN0PB035
FAN1PB136
FAN2PB2/BOOT137
LED-RPB692Can be used for fan3
LED-GPB591Can be used for fan4
LED-BPB793Can be used for fan5
5V-LED(WS2812)PD384Share with flash indicator(Bootloader)
HeatingE0-HeaterPB1554
E1-HeaterPC865
E2-HeaterPB389
Heated-BedPB490
TemperatureTE0(THERM0)PC015A 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)PC116A 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)PC217A 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)PC318A 4.7kOhm 0.1% temperature sensor pull up resistor is used, PT1000 can be connected directly. For PT100, an amplifier board must be used.
EXP2LCD_D7PD1/CAN-TX182Share with CAN-TX1
LCD_D6PD0/CAN-RX181Share with CAN-RX1
LCD_D5PC12/MOSI3/TX5/SDA280
LCD_D4PC10/SCK3/TX3/478
LCD_ENPC11/MISO3/RX3/479
LCD_RSPD2/RX583
ENC_CPA8/SCL367
BEEPPC9/SDA366
EXP1RESETNRST14
ENC_APC6/TX663
ENC_BPC7/RX664
SD-DETPB10/SCL247
SD-MISOPA6/MISO131
SD-MOSIPA7/MOSI132
SCKPA5/SCK130
CSPA4/CS129
EEPROM(4K) I2C Pin-OutSCLPB8/SCL195Connect to 24LC32(4K EEPROM)
SDAPB9/SDA196Connect to 24LC32(4K EEPROM)
Pi_PWR/UARTTXPA9/TX168
RXPA10/RX169
SWD DebugPA13/SWDIO72only used for debugging now and can be used for other purposes.
PA14/SWCLK76only used for debugging now and can be used for other purposes.

4. Firmware Guide

4.1 Marlin

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 configuration.h file

#define MOTHERBOARD BOARD_FYSETC_SPIDER

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.

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.

1561099422559

If everything goes fine , at the bottom you can see several buttons

1561099546202

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.4 Upload firmware

Follow Firmware Update guide here.

4.2 Klipper

You need to follow the Klipper installation guide to install Klipper.

When calling make menuconfig, please select below options

4.2.1 menuconfig

  • Enable extra low-level configuration options
  • Micro-controller Architecture

Select STMicroelectronics STM32

  • Processor model

Select STM32F446

  • Clock reference

Select 12 MHz crystal

  • Bootloader offset
  • 1. Boot address no

If you choose No bootloader bootloader offset in Klipper make menuconfig, 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. So the sequence be

  1. Click the button to find the DFU port.
  2. Connect the DFU
  3. Choose the "klipper.bin" file.
  4. fill in the 'Start address' with 0x08000000
  5. Start Programming

We have two pre-build firmwares for you klipper-USB.bin( github gitee) and klipper-UART.bin(github gitee). But these pre-build firmware will be outdated as time pass. We will try to catch up with Klipper, but i recommend to build the firmware yourself.

image-20210705151440643

  • 2. Boot address 32k

If you choose 32k bootloader offset in Klipper make menuconfig. Then you need to flash the spider board bootloader named Bootloader_FYSETC_SPIDER first, we recommend you to use this bootloader as we already change default bootloader offset from 64k to 32k since 2021/06/23. If you are not clear about it, you'd better flash the bootloader first. The bootloader is in the folder named bootloader in this repo, please follow the README in bootloader folder(github or gitee). Then you can follow Upload the firmware(SDCARD) to flash your built Klipper firmware to Spider. We provide pre-build firmwares named klipper-32k-USB.bin and klipper-32k-UART.bin for you github gitee.

image-20210705151337765

  • 3. Boot address 64k

If you choose 64k bootloader offset in Klipper make menuconfig. Then you need to flash the spider board bootloader named Bootloader_FYSETC_SPIDER_10000 first. The bootloader is in the folder named bootloader in this repo, please follow the README in bootloader folder(github or gitee). Then you can follow Upload the firmware(SDCARD) to flash your built Klipper firmware to Spider. We provide pre-build firmwares named klipper-64k-USB.bin and klipper-64k-UART.bin for you github gitee.

image-20210705151951142

  • Communication interface
  • 1. USB (on PA11/PA12)

If you want to connect Spider to RaspberryPI with USB cable. You need to select USB (on PA11/PA12)

image-20210705154413053

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
  • 2. Serial (on USART1 PA10/PA9)

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)

image-20210705154625673

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.

4.2.2 Compile firmware

make

4.2.3 Upload firmware

Follow Firmware Update guide here.

4.3 RRF

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.

4.4 Firmware Upload

4.4.1 Upload the firmware(SDCARD)

We provide several ways to upload the firmware .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.

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.

4.4.2 Upload the firmware(dfu-util)

This method works in linux, that means should work in raspberry pi.

  1. 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
  1. Power off board, remove SD Card, place jumper on BT0 and 3.3V. (Between Z- endstop and E0 driver) Connect Spider to PC/RaspberryPi with USB cable with jumper in place. Set U5V jumper closest to stepper driver modules to power Spider from the Pi USB, or power up with 24V. Verify 3.3V LED is lit and board is detected with dfu-util --list, should look something like
<snip>
Found DFU: [0483:df11] ver=2200, devnum=13, cfg=1, intf=0, path="1-1.3", alt=3, name="@Device Feature/0xFFFF0000/01*004 e", serial="STM32FxSTM32"
Found DFU:<snip>
  1. You should replace firmware.bin below with your built firmware bin file location like out/klipper.bin.
dfu-util -R -a 0 -s 0x08008000:leave -D firmware.bin

4.4.3 Upload the firmware(DFU)

The other way to upload the firmware is using DFU.

a.Download stm32cubeprogrammer

You can download it from ST website.

https://www.st.com/zh/development-tools/stm32cubeprog.html

Open the STM32CubeProgrammer software.

1574332767079

b.Enter DFU mode
  1. First power off the board
  2. Place jumper on BT0 to 3.3V pin (You can find them in the middle area of the board)
  3. Connect USB cable to the board and your computer
  4. Power up the board

Now the board is in DFU mode.

REMEMBER to remove the jumper if you finish uploading firmware 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.

1574386395071

Do as the red number shows in the screen shot.

  1. Click the button to find the DFU port.
  2. Connect the DFU
  3. Choose the "firmware.bin" file.
  4. Fill in the 'Start address' with 0x08008000 (If your platformio env is default_envs = FYSETC_S6, then you need to set it to 0x08010000, in klipper if you choose boot address 32k then set it 0x08008000, if 64k , set it 0x08010000, yes , you need different bootloader here (github or gitee)
  5. Start Programming

5. Issue shot

5.1 Spider 3.3v issue

Please check here.

6. Attachments

7. How to buy

8. Tech Support

You can submit issue in our github https://github.com/FYSETC/FYSETC-SPIDER/issues Or submit any technical issue into our forum

English

Español

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 want@fysetc.com, 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 task@fysetc.com.

Note

Ordinary and simple tasks should be completed within one week, and difficult tasks should be relaxed as appropriate.

Note

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.