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

Updated Calibration (markdown)

Candas1
2020-11-19 22:14:52 +01:00
parent 1e4bc6bba3
commit a25773ea07
1 changed files with 7 additions and 2 deletions
Download Patch File Download Diff File Expand all files Collapse all files

9
Calibration.md

@@ -4,6 +4,7 @@ Setting the type of input:
* If you don't need an input, disable it by setting INPUT1_TYPE or INPUT2_TYPE to 0, it will be ignored
* For normal potis, set INPUT1_TYPE or INPUT2_TYPE to 1
* For middle resting potis, set INPUT1_TYPE or INPUT2_TYPE to 2
* If INPUT1_TYPE or INPUT2_TYPE is set to 3, the right input type will be automatically identified during auto-calibration
Setting Minimum, Middle and Maximum position:
* Connect FTDI RX to blue wire from right sensor board cable to read USART DEBUG values, baud rate should be 38400
@@ -14,7 +15,7 @@ Setting Minimum, Middle and Maximum position:
Config.h values will be ignored if you have already used the auto-calibration procedure below.
# Auto-calibration:
Auto-calibration finds the minimum, middle and maximum values for inputs.
Auto-calibration finds the minimum, middle and maximum values for the inputs.
It also identifies the type of input and checks if it can be protected (ADC only).
* Press the power button for more than 5 sec and release after the beep sound
@@ -26,5 +27,9 @@ If you haven't moved one of the inputs, if it's floating or is grounded, it will
If min and mid values are close, the inputs will be identified as normal potis.<br />
Otherwise the inputs will be identified as middle resting potis.<br />
For inputs with type 3 (AUTO) in config.h, auto-calibration will automatically identify the right input type.
If input type 0,1,2 has been selected in config.h, auto-calibration will fail if identified input type is not matching and disable the input.
⚠The limits will be stored in flash memory and will be erased only if you fully delete memory before flashing.<br />
An alternative to bypass those limits is to change **FLASH_WRITE_KEY** in config.h to a value different than 0x1233.
An alternative to bypass those limits is to change **FLASH_WRITE_KEY** in config.h.