EFeru/hoverboard-firmware-hack-FOC
1
0
Fork 1
mirror of https://github.com/EFeru/hoverboard-firmware-hack-FOC.git synced 2025-08-04 01:54:27 +02:00
Code Issues Packages Projects Releases Wiki Activity

Updated Firmware Compatibility (markdown)

Candas1
2022-01-04 23:48:55 +01:00
parent ad93a543cb
commit 004be64882
1 changed files with 27 additions and 24 deletions
Download Patch File Download Diff File Expand all files Collapse all files

51
Firmware-Compatibility.md

@@ -1,27 +1,17 @@
## Mainboard
Typically, the mainboard brain is an [STM32F103RCT6](/docs/literature/[10]_STM32F103xC_datasheet.pdf), however some mainboards feature a [GD32F103RCT6](/docs/literature/[11]_GD32F103xx-Datasheet-Rev-2.7.pdf) which is also supported by this firmware.<br>
For the reverse-engineered schematics of the mainboard, see [20150722_hoverboard_sch.pdf](/docs/20150722_hoverboard_sch.pdf).<br>
# Mainboard
The mainboards with a [STM32F103RCT6](/docs/literature/[10]_STM32F103xC_datasheet.pdf) or a [GD32F103RCT6](/docs/literature/[11]_GD32F103xx-Datasheet-Rev-2.7.pdf) should be supported by this firmware.<br>
<img src="https://github.com/EmanuelFeru/hoverboard-firmware-hack-FOC/blob/master/docs/pictures/mainboard_pinout.png" width="700"><br>
For the reverse-engineered schematics of the mainboard, see [20150722_hoverboard_sch.pdf](/docs/20150722_hoverboard_sch.pdf).<br>
Some boards have 6 wires on the hall sensors cable, with an additional white wire.<br>
For those you can use the alternate mapping by changing parameter BOARD_VARIANT in [config.h](https://github.com/EmanuelFeru/hoverboard-firmware-hack-FOC/blob/master/Inc/config.h)
For those you can use the alternate mapping by changing parameter BOARD_VARIANT in [config.h](https://github.com/EmanuelFeru/hoverboard-firmware-hack-FOC/blob/master/Inc/config.h)<br>
It could be that your mainboard was designed differently, please check if the pin mapping is matching with the one in this [section](https://github.com/EFeru/hoverboard-firmware-hack-FOC/wiki/Firmware-Compatibility#pin-mapping).
## Split Boards
For split boards with a STM32F130C8 or GD32F130C8 chip, please check following [Firmware](https://github.com/flo199213/Hoverboard-Firmware-Hack-Gen2) and its forks.<br>
<img src="https://github.com/flo199213/Hoverboard-Firmware-Hack-Gen2/blob/master/Hardware_Overview_small.png" width="500">
For split boards with a GD32F103C8, please check following [Firmware](https://github.com/JohMah/Hoverboard-JC2015.7.31.V2.0-Hack)<br>
<img src="https://user-images.githubusercontent.com/3137332/43365339-733124a0-9323-11e8-897e-572af14a56d6.jpg" width="300">
For split boards with a GD32F130K6 chip, please check the progress on following [repository](https://github.com/JRomainG/GD32F130K6-hoverboard-hack).<br>
<img src="https://github.com/JRomainG/GD32F130K6-hoverboard-hack/blob/master/images/sideboard.jpg" width="500">
## Artery boards
For boards with AT32F403RCT6 or AT32F413RCT7 chips, please check following [Firmware](https://github.com/cloidnerux/hoverboard-firmware-hack).<br>
<img src="https://raw.githubusercontent.com/cloidnerux/hoverboard-firmware-hack/master/pinout.png" width="700">
## Troubleshooting
* Motors are cogging/not running in a smooth way - please try to swap the phases. Usually, color-correct mapping (blue to blue, green to green, yellow to yellow) works fine. However, some hoverboards have a different layout then others, and this might be the reason your motor isn't spinning well
* In speed mode, wheel are running at maximum speed - find the right mapping for hall sensors, firmware probably measures a speed with opposite sign
* With hovercar variant in torque mode, braking actually accelerates - find the right mapping for hall sensors, firmware probably measures a speed with opposite sign
## Pin Mapping
This is the pin mapping this firmware is using, you might have to adapt it to your board variant in [defines.h](https://github.com/EmanuelFeru/hoverboard-firmware-hack-FOC/blob/master/Inc/defines.h) file
@@ -65,7 +55,20 @@ This is the pin mapping this firmware is using, you might have to adapt it to yo
|BUTTON|PA1|PB9|
|CHARGER|PA12|PA11|
## Troubleshooting
* Motors are cogging/not running in a smooth way - please try to swap the phases. Usually, color-correct mapping (blue to blue, green to green, yellow to yellow) works fine. However, some hoverboards have a different layout then others, and this might be the reason your motor isn't spinning well
* In speed mode, wheel are running at maximum speed - find the right mapping for hall sensors, firmware probably measures a speed with opposite sign
* With hovercar variant in torque mode, braking actually accelerates - find the right mapping for hall sensors, firmware probably measures a speed with opposite sign
# Other boards and available firmware
## Artery boards
For boards with AT32F403RCT6 or AT32F413RCT7 chips, please check following [Firmware](https://github.com/cloidnerux/hoverboard-firmware-hack).<br>
<img src="https://raw.githubusercontent.com/cloidnerux/hoverboard-firmware-hack/master/pinout.png" width="700">
## Split Boards
For split boards with a STM32F130C8 or GD32F130C8 chip, please check following [Firmware](https://github.com/flo199213/Hoverboard-Firmware-Hack-Gen2) and its forks.<br>
<img src="https://github.com/flo199213/Hoverboard-Firmware-Hack-Gen2/blob/master/Hardware_Overview_small.png" width="500"><br>
For split boards with a GD32F103C8, please check following [Firmware](https://github.com/JohMah/Hoverboard-JC2015.7.31.V2.0-Hack)<br>
<img src="https://user-images.githubusercontent.com/3137332/43365339-733124a0-9323-11e8-897e-572af14a56d6.jpg" width="300"><br>
For split boards with a GD32F130K6 chip, please check the progress on following [repository](https://github.com/JRomainG/GD32F130K6-hoverboard-hack).<br>
<img src="https://github.com/JRomainG/GD32F130K6-hoverboard-hack/blob/master/images/sideboard.jpg" width="500">