Open
Conversation
Member
BrianJKoopman
left a comment
There was a problem hiding this comment.
I remember we discussed this in person before I went to site. I think where we ended up was that this needs to be split into separate blocks, since the block structure can't change once published.
The 372 agent is one example of having different blocks per field. Also see the ocs docs on message format.
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
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.
Fixes #927
Description
Checks if sensor list has changed (due to deactivating or activating slots) and if so re-grabs the list of desired sensors to query.
Motivation and Context
See #927
How Has This Been Tested?
Hasn't been tested, needs testing on site.
Types of changes
Checklist: