Toyota LTA: fix the way the torque sample_t
's are used
#1948
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.
The problem is how the safety was using the torque samples to enforce the torque winddown. To avoid erroneous blocked messages from panda getting a steer torque message before openpilot, we used the minimum of the last few values which provides tolerance. But this doesn't work if the torque oscillates heavily above the threshold, like when going over a pot hole.
After the oscillation, openpilot tries to enable torque correctly, but panda still thinks that torque is high since it isn't using the latest value, only the min.
8494c69d3c710e81/00000019--7c84cbf43c/11