Change comparison for new IO data according to specification #511
Conversation
This file contains 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
…ta, if CIP sequence count is different than previous one, Vol2_1.33 3-4.1
|
Hi, I am not aware on any recent changes on the logic for class 0/1 messages. Have you tested this with the recent CT Tool or has there been issues somewhere else? For quite some time a new package is considered to reset the timeout watchdog, but ordering of messages is still relevant for the update of data Cheers, |
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.
A received packet is considered to be new data whenever the CIP Sequence Count is
different (either greater or lesser) than the previous packet’s CIP Sequence Count, Vol2_1.33 3-4.1