[TC]: Add distance thresholds and handling of default process data #486
+798
−112
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.
Describe your changes
set_distance
function on the TC client now to cause the client to evaluate all TC-configured distance interval measurement commands, which previously weren't really supported. Distance triggers are not often used, but at least we now support it. When the distance set to the client causes any process data variable to need to be resent, the client will now automatically query the user's value callback and send an update to the TC. In general it's very automated, but the user is required to manage the vehicle's total driven distance in the consuming application, maybe by using our speed and distance interfaces or via proprietary means.Fixes #485
How has this been tested?