Add little-endian support for register data #1
Conversation
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
This change introduces little-endian support for the Modbus library. A `byte_order` parameter has been added to the constructors of the `TCP` and `Serial` client classes, as well as the `ModbusTCP` and `ModbusRTU` host classes. This parameter allows you to specify the byte order for the register data. The default is big-endian (`>`) for backward compatibility. The following modules have been updated: - `umodbus/common.py`: `CommonModbusFunctions` now handles `byte_order`. - `umodbus/functions.py`: Data packing/unpacking functions now respect the `byte_order`. The PDU header remains big-endian as per the Modbus specification. - `umodbus/tcp.py`: `TCP` and `ModbusTCP` classes now accept `byte_order`. - `umodbus/serial.py`: `Serial` and `ModbusRTU` classes now accept `byte_order`. - `umodbus/modbus.py`: The `Modbus` host class now handles `byte_order` for incoming write requests.
This change introduces little-endian support for the Modbus library. A `byte_order` parameter has been added to the constructors of the `TCP` and `Serial` client classes, as well as the `ModbusTCP` and `ModbusRTU` host classes. The `byte_order` parameter accepts "big" or "little" as values, with "big" as the default for backward compatibility. This provides a more user-friendly API than using ">" or "<". The following modules have been updated: - `umodbus/common.py`: `CommonModbusFunctions` now handles `byte_order`. - `umodbus/functions.py`: Data packing/unpacking functions now respect the `byte_order`. The PDU header remains big-endian as per the Modbus specification. - `umodbus/tcp.py`: `TCP` and `ModbusTCP` classes now accept `byte_order`. - `umodbus/serial.py`: `Serial` and `ModbusRTU` classes now accept `byte_order`. - `umodbus/modbus.py`: The `Modbus` host class now handles `byte_order` for incoming write requests.
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.
This change introduces little-endian support for the Modbus library. A
byte_orderparameter has been added to the client and host classes to allow specifying the byte order for register data, with 'big' as the default. The parameter accepts 'big' or 'little' for a more user-friendly API.