Fix field encoding of Read File Record Response #2075
Merged
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
The Modbus spec V1.1b3 states the following field order: 1. Function Code (0x14) 2. Resp. data Length (in bytes) 3. Sub-Req. x, File Resp. length (in registers) 4. Sub-Req. x, Reference Type: 0x6 (fixed) 5. Sub-Req. x, Record Data 6. Sub-Req. x+1, ... Previously, field 4 was before field 4.
justinsg
force-pushed
the
fix-read-file-record-response-encoding
branch
from
f1a6eee
to
cf2e0ed
Compare
janiversen
reviewed
Mar 4, 2024
janiversen
approved these changes
Mar 4, 2024
|
Thanks. |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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 Modbus spec V1.1b3 states the following field order:
Previously, field 4 was before field 3.