Adding BLE Support (SpeedyBee, HM-1X) #1441
Closed
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Support for Bluetooth low Energy devices:
Supported are:
BLE to UART adapters:
SpeedyBee adapters and FCs with integrated Bluetooth.
Unfortunately, the Chrome BLE API is somewhat limited compared to Android. This results in the effect with the UART adapters, due to the buffers, that either the order of the bytes is messed up or even bytes are missing. Therefore, the FC must split large frames and send them one after the other with a certain delay.
There is a new MSP command for this: MSP2_INAV_SET_MSP_OPTIONS, with which the configurator can request transmission in chunks and a delay between the cunks, see here: iNavFlight/inav#7783
The Speedybee adapters are not affected by this, they seem to have a large enough buffer.
#1001