Repository navigation
Conversation
Request MSP_MOTOR_TELEMETRY from Betaflight and append four 12-bit RPM values so goggles can synthesize motor audio without new RF opcodes.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Summary
MSP_MOTOR_TELEMETRY(139) after FC init and keep mechanical RPM for motors 0..3 (quad only).0xFFservice payload from 15 to 21 bytes with four 12-bit quantized RPMs (6 bytes). No new RF opcodes; MSP RX buffer stays 64 bytes.docs/synthetic-motor-audio.md. Pair with the matching goggle PR for decode/synth.Packet
q = min((rpm + 16) >> 5, 4095)(32 RPM steps, max 131040).lengthaccept the longer frame and ignore the unknown tail.Test plan
BTFL.0xFFservice length is 21 and CRC still validates on current goggle firmware.