chore: bump model-garage to v1.0.16 (Ruptela CAN EV zero as not available) - #284
Merged
Merged
Conversation
…able) Pulls in DIMO-Network/model-garage#266: a literal 0 from the Ruptela CAN EV elements 515 (SoC), 516 (distance until recharge) and 720 (battery-2 SoC) is now treated as "not available" like the FF sentinel. On R1 units whose CAN profile does not decode the vehicle, the resolver fell through from OBD 722 (FF every other record) to 515 = 0, so powertrainTractionBatteryStateOfChargeCurrent alternated between the real value and 0% (vehicle 192097, 2025 VW ID. Buzz).
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.
What
Bump
github.com/DIMO-Network/model-garagev1.0.15 -> v1.0.16. Onlygo.mod/go.sumchange.Why
Pulls in DIMO-Network/model-garage#266. Ruptela R1 units on vehicles the CAN profile does not decode fill the CAN EV elements 515 (SoC), 516 (distance until recharge) and 720 (battery-2 SoC) with a literal
0instead of theFF"not available" sentinel. The state-of-charge resolver tries OBD element 722 first and falls through to 515 whenever 722 readsFF, which on these devices is every other record, sopowertrainTractionBatteryStateOfChargeCurrentalternated between the real value and 0%.Seen on vehicle 192097 (2025 VW ID. Buzz, device 36798): at 10-minute buckets
MINwas 0 in every bucket whileMAXtraced a clean 78% -> 19% discharge.With v1.0.16 a literal zero from those three elements returns not-found and the resolver falls through as it does for
FF. Affected telemetry fields:powertrainTractionBatteryStateOfChargeCurrentandpowertrainTractionBatteryRange, Ruptela source only, and only their CAN fallback sources. OBD 722/723 and the boolean 517 are unchanged.Verification
go build ./...andgo test ./...green on this branch.Follow-ups
CurrentPower/ChargingAddedEnergyfor Ruptela.🤖 Generated with Claude Code
https://claude.ai/code/session_01CoGJaQVZPFGMbQ7of5wBnJ