Change format of Clarity torqueBP values from hexadecimal to decimal #269
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
Evaluated values are unchanged. "Kiril — 9/16/2021 2:27 PM It would be so much easier if people just used integers for both instead of hex"
|
Thank you for your PR! If you're not already in the FrogPilot Discord, feel free to join and let me know you've opened a PR! |
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.
Evaluated values are unchanged.
"Kiril — 9/16/2021 2:27 PM
It would be so much easier if people just used integers for both instead of hex"
Clarity is the only car in the Honda interface.py that uses heaxdecimal modded torqueBP values; stock torqueBP values are in decimal and all other cars' stock and modded torqueBP values are also in decimal.
This PR brings Clarity in line with all the other Hondas.