fysetc / fysetc-cheetah-v2 Goto Github PK

FYSETC Board - 32bit control board for creality 3D printer，includ Ender3 ，Ender3 pro，Ender5.

Makefile 0.26% C 31.65% C++ 65.96% Python 0.72% Shell 0.67% GDB 0.01% NASL 0.01% OpenSCAD 0.05% JavaScript 0.36% G-code 0.02% HTML 0.27% CSS 0.04% Dockerfile 0.01% BitBake 0.01%

fysetc-cheetah-v2's Introduction

Cheetah v2.0

1. Product Introduction

Cheetah 2.0 is a single-head main control board based on STM32F401, with 4 TMC2209 onboard, supports sensor-less homing, can be connected to a variety of displays, compatible with the installation size of most of the Creality 3D machines, such as ender3, ender3 V2, ender3 pro, ender5, and is also suitable for general 3D printers DIY.

2. Features

Compact size: 101.5mm x 72mm，Compatible with the Creatlity ender 3 motherboard size
Fully integrated all in one solution:
STM32F401MCU (Run Marlin 2.0**/**Klipper )
4X TMC2209 stepper drivers, Support sensor-less homing
UNIVERSAL POWER:
Can be used with 12V/24V for motors / heated bed
24V to 12V/2A DC-DC for fans
Integrated high precision power regulators (DC/DC): 5V 2A Max and 3.3V 600mA Max LDO
12V&24V power pin out
Onboard TF card socket- EXP3 for 12864 display panel (Creality 12864 panel or FYSETC Generic12864)
EXP1&EXP2 RepRapDiscount SmartController compatible pin header on board
EXP4 with I2C and UART1
Onboard 5V WS2812 RGB control
SD card & USB upload support
Car fuses for main power input
Up to 3 ways PWM fans (5/12/24 Optional)
PCB： FR4-TG155 PCB - Gold ENIG finishing

3. Application

3D printer
CNC Device
Other similar machines
Voron 0.1(github gitee)

4. Hardware

4.1 Hardware Reasources

Board Name	Cheetah v2.0
License	GPL V2.0
Latest Version	V2.0
Extruders	1
Controlled Fans	3 Max
Heaters	2 Max
Endstops	3 Max
Temp sens	2 Max
UART	1
I2C	1
SWD	1
USB	1
CPU	STM32F401
CPU Speed ( MHz )	84 Mhz
Stepper driver	4X TMC2209
Stepper driver Type	Onboard
Input	12v/24v
Output	BED OUT：10A Max ；Heater Out：5A Max

4.2 Connectors and jumpers define

Coming soon...

4.3 Pin Definition

Features	Cheetah Pin	STM32 Pin	Pin No.	Comment
X-MOTOR(1)	X-Step	PC0	8
	X-DIR	PC1	9
	X-EN	PA8	41
Y-MOTOR(2)	Y-Step	PC14	3
	Y-DIR	PC13	2
	Y-EN	PC15	4
Z-MOTOR(3)	Z-Step	PB9	62
	Z-DIR	PB8	61
	Z-EN	PC2	10
E0-MOTOR(4)	E0-Step	PB2	28
	E0-DIR	PA15	50
	E0-EN	PD2	54
TMC2209 SERIAL (UART2)	TX2	PA2	16
TMC2209 SERIAL (UART2)	RX2	PA3	17
End-stops	X-MIN	PB4	56
	Y-MIN	PC8	39
	Z-MIN	PB1	27
PWM	BLTOUCH/PROBE	PA0	14
FIL-DET	FIL-DET	PB5	57
FAN	FAN0	PA14	49
	FAN1	PA13	46
	FAN2	PA1	15
RGB	Neo-pixel	PB0	26	Can be used for fan4
Heating	E0-Heater	PC6	37
Heating	Heated-Bed	PC7	38
Temperature	TE0	PC4	24
Temperature	TB	PC5	25
EXP1	SD-MISO	PA6	22
	SD-SCK	PA5	21
	BTN_EN1	PC10	51
	SD-SS	PA4	20
	BTN_EN2	PC11	52
	SD-MOSI	PA7	23
	SD-DET	PC3	11
	RESET	NRST	7
	GND	GND	NA
	5V	5V	NA
EXP2	BEEP	PC9	40
	BTN_ENC	PC12	53
	LCD_EN	PB15	36
	LCD_RS	PB12	33
	LCD_D4	PB13	34
	LCD_D5	PB14	35
	LCD_D6	PB6	58
	LCD_D7	PB7	59
	GND	GND	NA
	5V	5V	NA
UART	TX	PA9/TX1	42
UART	RX	PA10/RX1	43
I2C	I2C2 SCL	PB10	29
I2C	I2C2 SDA	PB11	30
SWD Debug	SWDIO	PA13	46	only used for debugging now and can be used for other purposes.
	SWCLK	PA14	49	only used for debugging now and can be used for other purposes.

4.4 Wiring

4.4.1 Bltouch wiring

klipper config

[bltouch]
sensor_pin: ^PA0
control_pin: PB1

4.4.2 VORON 0.1 wiring

Please refer to our VORON 0.1 kit wiring here( github or 国内)

5. Firmware

5.1 Marlin

Follow the steps below to compile the firmware yourself. You can learn more on Marlin official website here.

5.1.1 Download Vscode + platformio

To compile the firmware , you need to install Visual Studio Code and the platformio pulg-in.

5.1.2 Config firmware

Step 1: Get marlin code

You have two choices to get Marlin code.

Choice 1

You can get Marlin code in the firmware/Marlin folder in this repository ( github gitee ).

Choice 2

Also you can get upstream Marlin official branch from github or gitee.

Step 2: Change motherboard related configurations.

In marlin firmware you have downloaded, you should find platformio.ini , configuration.h and configuration_adv.h file.

First we need to change default_envs in platformio.ini file.

default_envs = FYSETC_CHEETAH_V20

Change MOTHERBOARD define in Configuration.h

#define MOTHERBOARD BOARD_FYSETC_CHEETAH_V20

Change Serial port define in Configuration.h

#define SERIAL_PORT -1
#define BAUDRATE 115200

Step 3: Change other configurations

Except the motherboard related configurations, you still need to set like machine size and print speed and others configurations in configuration.h, and configuration_adv.h. And you can find machine related example configurations on Marlin github here which you can refer to.

5.1.3 Compile the firmware

Once you finish setting the firmware, we can try to 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

Just click check mark to compile.

5.1.4 Upload the firmware

Follow the instruction here.

5.2 Klipper

Till now(2021/11/30), Klipper don't have boot offset setting for STM32F401 chip, so we use no Bootloader option first. (If you want still want to use Cheetah bootloader, you can change the code following the PR here, then use 32KiB bootloader option).

make clean
make

Then follow the Firmware Upload section instruction below to upload the firmware.

I made the PR for Klipper of Cheetah v2.0 config, you can check it here.

5.3 Firmware Upload

We provide several ways to upload the firmware.

5.3.1 Upload the firmware(SDCARD)

If you use Klipper firmware with No bootloader option, you can't use this method. This method only works with bootloader.

Uploading firmware using SD card is our default way to update the firmware as Cheetah v2.0 already has the bootloader on it when it leave the factory. But if you once upload the firmware to Cheetah v2.0 flash address 0x08000000, then the bootloader in Cheetah v2.0 will be gone, then you need to upload the bootloader to Cheetah v2.0 yourself, please follow the README in bootloader folder (github or gitee) to upload the bootloader.

How to upload firmware with 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. When finished firmware name will change to old.bin.

5.3.2 Upload the firmware(dfu-util)

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

Enter DFU mode first
- First power off the board
- Place jumper on BT0 and 3.3V pin
- Connect USB cable to the board and your computer
- Power up the board with 24v

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 file location like out/klipper.bin. Change flash address 0x08008000 to bootloader you choosed. (If you use Marlin firmware, you need to set it to 0x08008000. If you use klipper firmware and you choose boot address 32kiB bootloader (decribe here) when compiling klipper then set it 0x08008000, if no Bootloader , set it 0x08000000.)
```
dfu-util -R -a 0 -s 0x08008000:leave -D firmware.bin
```
Remove boot jumper and power-off then power on the board.

5.3.3 Upload the firmware(WINDOWS DFU)

The other way to upload the firmware is using DFU.

Step 1. Download stm32cubeprogrammer

You can download it from ST website.

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

Open the STM32CubeProgrammer software.

Step 2. Enter DFU mode

First power off the board
Place jumper on BT0 and 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.

REMEMBER to remove the jumper if you finish uploading firmware or it will enter DFU mode again.

Step 3. Upload the firmware

Now you can connect and flash the Cheetah board with stm32cubeprogrammer with the following operation.

Do as the red number shows in the screen shot.

Click the button to find the DFU port.
Connect the DFU
Choose the "firmware.bin" file.
If your firmware is .hex file, skip this step. Fill in the 'Start address' with (If you use Marlin, set it 0x08008000. If you use Klipper firmware and you choose boot address 32kiB bootloader (decribe here) when compiling klipper then set it 0x08008000, if no Bootloader , set it 0x08000000.)
Start Programming
Remove boot jumper and power-off then power on the board.

5.3.4 Upload firmware(platformio)

If you compile Marlin yourself with platformio,you can follow the instructions below to upload the firmware.

Step 1. Enter DFU mode first

First power off the board
Place jumper on BT0 and 3.3V pin
Connect USB cable to the board and your computer
Power up the board with 24v

Step 2. Click the upload button to upload firmware

6. FAQ

To be done...

7. Tech Support

Please submit any technical issue into our forum

fysetc-cheetah-v2's People

Contributors

Stargazers

Watchers

Forkers

mankid-leung repairsyl openthings rh101 micki0271 oddwatcher fex42 yuratos

fysetc-cheetah-v2's Issues

BL touch wiring image is incorrect on main git page

The image showing the connection for a BL touch is incorrect and will damage the BLT and / or control board !!!

this is what it should be >>

i2c2 pins in cheetah v2.0

There is a discrepancy in schematic (Cheetah_Board V2.0_SCH.pdf) of the board and pin definitions, i2c2 should be PB10/PB11, but in schematic it's PB10/PB3? There is also a note about capacitor on PB11 that disables i2c, so what is the state of the hardware? I'm trying to connect ssd1306 display via i2c to be used in klipper, but it timeouts on PB10/PB11.

mini lcd 12864 v2.1

hi,
i can switch on my fysetc lcd v2.1 on cheetah but nothing appear...

here is my setup...

[display]
lcd_type: uc1701
cs_pin: PB15
a0_pin: PB12
rst_pin: PB13
contrast: 63
encoder_pins: ^PC10, ^PC11
click_pin: ^!PC12

Some micro-controller boards may require an spi bus to be specified:

#spi_bus: spi

Alternatively, some micro-controller boards may work with software spi:

spi_software_miso_pin: PA6
spi_software_mosi_pin: PA7
spi_software_sclk_pin: PA5

#[output_pin beeper]
#pin: EXP2_10

[neopixel fysetc_mini12864]
pin: PB0
chain_count: 3
color_order: RGB
initial_RED: 0.1
initial_GREEN: 0.5
initial_BLUE: 0.0

[delayed_gcode setdisplayneopixel]
initial_duration: 1
gcode:
SET_LED LED=fysetc_mini12864 RED=1 GREEN=1 BLUE=1 INDEX=1 TRANSMIT=0
SET_LED LED=fysetc_mini12864 RED=1 GREEN=0 BLUE=0 INDEX=2 TRANSMIT=0
SET_LED LED=fysetc_mini12864 RED=1 GREEN=0 BLUE=0 INDEX=3

Cheetah V2 - Enable Printcount

Hello, please help me, i want to enable PRINTCOUNT, but i take an error:

Fans are not spinning on ender3

i used the provided generic icd hardware but the fans i directly attached to it refused to spin i had placed the jumpers over 24 volt still have nothing

Cheetah-v2 short?

I am using Cheetash-v2 as control board for Voron 0.1. I found that the heaters does not work and the cooling fans will not start when I was running the intial startup for voron 0.1.

I tested the output pins of the cheetah-v2 board, and both the power and ground pins for heaters and cooling fans give me 24V. Then I turn off the power and tested the resistance of those pins. It seems they are all good and no short is happening.

I am really not sure if there is a short happening, since the reisistances are normal and I do not think there was any magic gas leaking when I first boot the board. So I am not sure about what to do. Is there anything I can do to find out the issue? Or should I just buy a new board?

extruder thermistor is not accurate

on the tempertaure grapth the line is not straight and there are a lot +/-1 degree of celsius lag which causes inconsitent extrusion. after switching to skr pico with the same rest of hardware I can see +/- 0.2 degree of celsius lag.

Fan pins are flipped

and - of the fans are the flipped. I solved this on my board by just flipping the white sockets for the fans. You can get them off the board with tweezers.

#define PRINTCOUNTER: not worlking

getting compile error: Marlin\src\HAL\STM32../../inc/../HAL/STM32/inc/SanityCheck.h:42:4: error: #error "Disable PRINTCOUNTER or choose another EEPROM emulation."

Connection issue with TFT24 v1.1

Hello,

I bought a Cheetah v2.0, that I would like to run with a TFT24 v1.1 screen. I managed to connect it in "Touch screen mod" (still got a "no printer attached" issue, but it's not a big deal I think).

What bothers me, i can't connect it either in "Marlin mode", with EXP1 and EXP2 ports...

I found EXP1 pin definition here, but does anyone have those for the other EXP ports please?

Thanks a lot.

3d model

Is there a 3D model (in something like STEP, STL or 3mf format) of the Cheetah v2 board?

Getting Klipper to run on Ender3 hardware

Hello
I was looking for a new board for my first revision Ender 3 which used old Creality v1.1.4 board. Of course my first choice was SKR Mini E3 v3 but then I found FYSETC Cheetah v2 which has a few advantages in my opinion. I want ahead and bought one.

I'm trying to get Klipper to run on my machine but I noticed the provided configuration files are not 100% correct for Ender3. I had to make a few changes:

@@ -1,129 +1,195 @@
 [mcu]
 ##	Obtain mcu value by "ls -l /dev/serial/by-id/"
-serial: /dev/serial/by-id/usb-Klipper_stm32f401xc_4C004E000C51383336383937-if00
+serial: /dev/serial/by-id/usb-Klipper_stm32f401xc_150036001951383336383937-if00

 [stepper_x]
 step_pin: PC0
-dir_pin: PC1
+dir_pin: !PC1
 enable_pin: !PA8
 rotation_distance: 40
 microsteps: 16
 endstop_pin: ^PB4
 position_endstop: 0
-position_max: 200
+position_max: 240
 homing_speed: 50

 [tmc2209 stepper_x]
 uart_pin: PA3
 tx_pin: PA2
 uart_address: 0
 run_current: 0.800
 hold_current: 0.500
 stealthchop_threshold: 250

 [stepper_y]
 step_pin: PC14
 dir_pin: !PC13
 enable_pin: !PC15
 rotation_distance: 40
 microsteps: 16
-endstop_pin: ^PB3
+endstop_pin: ^PC8
 position_endstop: 0
-position_max: 200
+position_max: 240
 homing_speed: 50

 [tmc2209 stepper_y]
 uart_pin: PA3
 tx_pin: PA2
 uart_address: 2
 run_current: 0.800
 hold_current: 0.500
 stealthchop_threshold: 250

 [stepper_z]
 step_pin: PB9
 dir_pin: PB8
 enable_pin: !PC2
 rotation_distance: 8
 microsteps: 16

endstop_pin: ^PB1
position_endstop: 0
position_max: 250

 [tmc2209 stepper_z]
 uart_pin: PA3
 tx_pin: PA2
 uart_address: 1
 run_current: 0.800
 hold_current: 0.500
 stealthchop_threshold: 5

 [extruder]
 step_pin: PB2
 dir_pin: !PA15
 enable_pin: !PD2
-rotation_distance: 33.500
+rotation_distance: 33.683
 microsteps: 16

 nozzle_diameter: 0.400
 filament_diameter: 1.750
 heater_pin: PC6
 sensor_type: EPCOS 100K B57560G104F
 sensor_pin: PC4
 control: pid
 pid_kp: 21.527
 pid_ki: 1.063
 pid_kd: 108.982
 min_temp: 0
 max_temp: 250

 [tmc2209 extruder]
 uart_pin: PA3
 tx_pin: PA2
 uart_address: 3
 run_current: 1.0
 hold_current: 0.500
 stealthchop_threshold: 5

 [heater_bed]
 heater_pin: PC7
 sensor_type: EPCOS 100K B57560G104F
 sensor_pin: PC5
 control: pid
 pid_kp: 54.027
 pid_ki: 0.770
 pid_kd: 948.182
 min_temp: 0
 max_temp: 130

 #fan for printed model FAN0
 [fan]
 pin: PA14

 #fan for hotend FAN1
-#[heater_fan my_nozzle_fan]
-#pin: PA13
+[heater_fan hotend_fan]
+pin: PA13
+heater: extruder
+heater_temp: 50.0
+
+#fan for mainboard FAN2
+[fan_generic mcu_fan]
+pin: PA1

 [printer]
 kinematics: cartesian
 max_velocity: 300
 max_accel: 3000
 max_z_velocity: 5
 max_z_accel: 100

 [board_pins]
 aliases:
     # EXP1 header
     EXP1_1=<5V>,  EXP1_3=<RST>, EXP1_5=PA7,  EXP1_7=PA4,  EXP1_9=PA5,
     EXP1_2=<GND>, EXP1_4=PC3,   EXP1_6=PC11, EXP1_8=PC10, EXP1_10=PA6,

     # EXP2 header
     EXP2_1=<5V>,  EXP2_3=PB7, EXP2_5=PB14, EXP2_7=PB12, EXP2_9=PC12,
     EXP2_2=<GND>, EXP2_4=PB6, EXP2_6=PB13, EXP2_8=PB15, EXP2_10=PC9,

     # EXP3 header
     EXP3_1=PC9,  EXP3_3=PC10, EXP3_5=PC11, EXP3_7=PB12, EXP3_9=<GND>,
     EXP3_2=PC12, EXP3_4=PB14, EXP3_6=PB13, EXP3_8=PB15, EXP3_10=<5V>
     # Pins EXP1_4, EXP1_8, EXP1_6 are also MISO, MOSI, SCK of bus "spi2"

+[display]
+lcd_type: st7920
+cs_pin: EXP3_7
+sclk_pin: EXP3_6
+sid_pin: EXP3_8
+encoder_pins: ^EXP3_5, ^EXP3_3
+click_pin: ^!EXP3_2
+
+[output_pin beeper]
+pin: EXP3_1

This is a good starting point if someone is struggling to get Ender3 hardware to work properly.

I have multiple isues though:

I can't get internal MCU temperature sensor to work. Since Ender3 has additional fan for the mainboard I'd like to run it only when it gets too warm. I tried configuring custom temperature sensor:

[temperature_sensor mcu_temp]
sensor_type: temperature_mcu
sensor_mcu: mcu
min_temp: 0
max_temp: 100

But I get MCU 'mcu' shutdown: Not a valid ADC pin error.

Can't get BLTouch to work - this is the most frustrating one. I'm using v3.0 3D Touch clone on my setup and it was working properly with previous board. Now with Cheetah v2 Klipper can't control the probe, it doesn't react to any BLTOUCH_DEBUG commands. My config for BLTouch looks like this:

[bltouch]
sensor_pin = ^PB1
control_pin = PA0
x_offset: -45
y_offset: -8
z_offset: 3.2
samples: 2
speed: 10.0
probe_with_touch_mode: true
stow_on_each_sample: false

Any idea how to deal with these issues, especially BLTouch?

MCU Temperature sensor not working

When I define the MCU temperature sensor in printer.cfg I get the MCU 'mcu' shutdown: Not a valid ADC pin error.
That should work with the STM32 pcu. Is the internal temp sensor included?

[temperature_sensor mcu_temp]
sensor_type: temperature_mcu
min_temp: 0
max_temp: 100

Difference between 5V, DC5V and USB_5V?

The image below shows three power pins that are grouped on the board:

I'm unable to tell what the difference between these pins is. They all seem to do the same thing: provide 5V power. However, they're separate, and named differently, so what exactly is the difference, if any?

Context for this question: I am trying to power a SBC running Klipper, and would like to know which of these pins I can use for 5V power.

Wiki shows wrong pinout (RGB and PWR-PROBE flipped)

The wiki for the cheetah 2 shows a wrong pinout:
In this wiki the pinout image has the RGB and PWR-PROBE pins switched. This lead to me killing my LEDs. The GitHub readme already has a correct version of the image this one

Please update the wiki!

Example connection for neopixel

In the readme there is a mention of neopixel support, but there is no indication of where it should be used. It is also mentioned that the board pins can be used as 4th fan, but still no 2-pin connector that seems suitable can be seen in the pictures

EXP1 and EXP2 are mirrored

After spending plenty of time trying to get one of your 12864 displays connected, I have figured out the reason: The mapping of EXP1 and EXP2 (and possibly EXP3 too, haven't checked) is inverted (e.g. 1 is 10, 10 is 1, and so on). When trying to set up your 12864 according to the default klipper config for lcds, this leads to klipper not being able to run due to errors such as pin EXP1_3 is reserved for <RST> preventing startup. When invering the pin headers, the display starts working flawlessly.