Add hard-coded odometer value in VD script #2482
Merged
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.
This PR is [ready] for review.
Summary
Sometimes script:
may fail on PTU step with message:
The reason of that is
odometer
trigger.In case if the difference between current odometer value and the one received on a previous PTU update exceeds
exchange_after_x_kilometers
parameter SDL triggers new PTU update.ATF version
develop
Changelog
odometer
inOnVehicleData
by a hard-coded one (e.g.1
). This would makeodometer
trigger is never happen.CLA