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

Updated Variant IBUS (markdown)

Candas1
2022-01-02 12:04:09 +01:00
parent 7e4ff41cd1
commit 97f6daa13a
1 changed files with 7 additions and 4 deletions
Download Patch File Download Diff File Expand all files Collapse all files

11
Variant-IBUS.md

@@ -1,12 +1,15 @@
This variant can be used with Flysky RC Receivers compatible with IBUS protocol.<br /> This variant can be used with Flysky RC Receivers compatible with IBUS protocol.<br />
It will send all channels on a single wire like PPM, but is more reliable as it is a digital protocol using a USART frame and checksum.<br /> It will send all channels on a single wire like PPM, but is more reliable as it is a digital protocol using a USART frame and checksum.<br />
Default number of channels for IBUS in config.h is 14 (successfully tested with Flysky fs-I6AB and RX2A).
⚠ Ibus telemetry is not handled by the firmware ⚠ Ibus telemetry is not handled by the firmware
## Configuration/Parameters
Ibus control is reusing some of the USART control parameters.<br>
Use CONTROL_SERIAL_USART3 and FEEDBACK_SERIAL_USART3 for the right sensor cable(default), or CONTROL_SERIAL_USART2 and FEEDBACK_SERIAL_USART2 for left sensor cable.<br>
IBUS_NUM_CHANNELS is the number of channels for IBUS and is 14 by default. As an example Flysky fs-i6ab or RX2A receivers are sending 14 channels even when used with a 6 channel transmitter<br>
## Wiring: ## Wiring:
* Connect IBUS port of your receiver to green wire on right sensor cable(shorter) * Connect IBUS port of your receiver to green wire on the cable selected in config.h
* If you want to use the left cable instead, replace CONTROL_SERIAL_USART3 by CONTROL_SERIAL_USART2 and FEEDBACK_SERIAL_USART3 by FEEDBACK_SERIAL_USART2 in config.h
⚠ Red wire from sensor cable delivers 15v !!! ⚠ Red wire from sensor cable delivers 15v !!!
Use 3.3v from programming port, 5v from hall sensor cable, or a voltage regulator. Use 3.3v from programming port, 5v from hall sensor cable, or a voltage regulator.
@@ -23,6 +26,6 @@ Proceed with [calibration](https://github.com/EmanuelFeru/hoverboard-firmware-ha
If the board is [beeping](https://github.com/EmanuelFeru/hoverboard-firmware-hack-FOC/wiki/Diagnostics) If the board is [beeping](https://github.com/EmanuelFeru/hoverboard-firmware-hack-FOC/wiki/Diagnostics)
* Check the number of channels, even if you transmitter only handles 6 channels, you receiver might transmit more channels * Check the number of channels, even if you transmitter only handles 6 channels, you receiver might transmit more channels
* Make sure you enabled IBUS on your transmitter, on some models it is activated together with PPM * Make sure you enabled IBUS on your transmitter, on some models it is activated together with PPM
* Make sure you are using the sensor cable(left or right) selected in config.h * Make sure you are using the sensor cable(left=CONTROL_SERIAL_USART2 or right=CONTROL_SERIAL_USART3) selected in config.h
* On some boards the wire colors might differ, try the blue wire * On some boards the wire colors might differ, try the blue wire
* You might have a defective input, because of a fried resistor or MCU pin (e.g. [issue](https://github.com/EFeru/hoverboard-firmware-hack-FOC/issues/244)), you can configure the firmware to work on the other cable * You might have a defective input, because of a fried resistor or MCU pin (e.g. [issue](https://github.com/EFeru/hoverboard-firmware-hack-FOC/issues/244)), you can configure the firmware to work on the other cable