Repository navigation
TPMS: sensor battery voltage per wheel, and TPMS values for dash apps - #275
Merged
Merged
Conversation
…boards
VCSEC_TPMSData muxes 0-3 also carry each sensor's battery voltage
(VCSEC_TPMSBatVoltage0-3, 0.01 V + 1.5). Decode it with the same
mux-to-wheel map as the temperatures into tpmsBatt{FL,FR,RL,RR}
(V, -1 = no reading; raw 0xFF = not available is rejected). The four
values join the TPMS block after the temperatures (TPMS_COUNT 8 -> 12,
CarState slots 47-50, FIELD_COUNT = 51), carried through the iOS bridge
and both apps.
Rive dashboards get the TPMS values: dashValues (Android and iOS) add the
twelve tpmsPressure*/tpmsTemp*/tpmsBatt* keys, which softwiredtech#270 left out. README
documents them (Rive only for now; the WebView bridge doesn't carry TPMS).
Replaying four Model Y CAN logs through the mapper gives 2.98-3.01 V per
wheel, steady. Host test passes; Android debug APK builds; iOS not built.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
ehoeve786
force-pushed
the
tpms-battery
branch
from
November 8, 2026 03:31
2151cfa to
ba975b9
Compare
ehoeve786
marked this pull request as ready for review
November 8, 2026 03:32
Android WebView getters getTpmsPressure*/getTpmsTemp*/getTpmsBatt* and the same twelve keys in the iOS WebView JSON, so web dash apps get the tyre values like Rive ones. README no longer marks them Rive only. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
ehoeve786
changed the title
wpmed92
approved these changes
Nov 8, 2026
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.
VCSEC_TPMSDatamuxes 0–3 also carry each sensor's battery voltage (VCSEC_TPMSBatVoltage0–3, 0.01 V + 1.5). This decodes it with the same mux-to-wheel map as the temperatures intotpmsBatt{FL,FR,RL,RR}(V, -1 = no reading; raw 0xFF = not available is rejected). The four values join the TPMS block right after the temperatures (TPMS_COUNT8 → 12, slots 47–50,FIELD_COUNT = 51), carried through the iOS bridge and both apps.It also gives dash apps the TPMS values, which #270 left out: the twelve
tpmsPressure*/tpmsTemp*/tpmsBatt*keys go to Rive dashboards (dashValues, Android and iOS) and web dashboards (Android WebView gettersgetTpmsPressureFL…, iOS WebView JSON), and the README documents them.Based on
main, independent of #273. Both append to theCarStatearray, so whichever merges second needs a small rebase (its Android indices andFIELD_COUNT); #273'sDOOR_OFFSETfollowsTPMS_OFFSET + TPMS_COUNT, so the C++ side shifts by itself.Verification: replaying four Model Y CAN logs (2026-10-26..28) through the mapper gives 2.98–3.01 V per wheel, steady. Host test passes; Android debug APK builds; iOS not built.
🤖 Generated with Claude Code