fix: scale FTMS speed commands for Horizon T202 - #4904
Merged
Conversation
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
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
JFTM T202*Horizon treadmill devices.Background
mail Horizon t202 on 9/8/2026
The supplied debug log showed the treadmill interpreting FTMS speed commands with an approximately 1.609 scaling factor:
1.0, the treadmill reported approximately1.6.1.4, the treadmill reported approximately2.2.The log also showed that the FTMS path was active (
JFTM T202-5_4DEE, FTMS service0x1826, Control Point0x2AD9, andhorizon_treadmill_force_ftms=true).Implementation
The T202 is identified from the BLE name prefix and the target speed is converted with the existing
0.621371miles conversion before encodingFTMS_SET_TARGET_SPEED.Test plan
git diff --checkbuild/)horizontreadmill.cppandhorizontreadmill.h+and-