Modbus |
The ModbusTCPProtocol type exposes the following members.
Properties| Name | Description | |
|---|---|---|
 | DeviceName | The name of the ED Device |
| LastRequest | The last Modbus TCP Request sent encoded as string |
| LastResponse | The Modbus TCP Response for the last Request sent note this could be null as the request may not have completed at time of asking |
| ProtocolId | The ModbusTCP protocol, always 0 From Modbus.org: Protocol Identifier – It is used for intra-system multiplexing. The MODBUS protocol is identified by the value 0. |
| RequestLength | The Modbus TCP Length of Request From Modbus.rog: Length - The length field is a byte count of the following fields, including the Unit Identifier and data fields. |
| ResponseLength | The Modbus TCP Length of Response From Modbus.rog: Length - The length field is a byte count of the following fields, including the Unit Identifier and data fields. |
| Stream |
Set the stream which the protocol data is written and read from
(Inherited from Protocol) |
| TransactionId | The ModbusTCP transaction Id starts at one and should be incremented each time from Modbus.org: Transaction Identifier - It is used for transaction pairing, the MODBUS server copies in the response the transaction identifier of the request. |
| UnitId | The ModbusTCP Unit identifier, From Modbus.org: Unit Identifier – This field is used for intra-system routing purpose. It is typically used to communicate to a MODBUS+ or a MODBUS serial line slave through a gateway between an Ethernet TCP-IP network and a MODBUS serial line.This field is set by the MODBUS Client in the request and must be returned with the same value in the response by the server. For our purposes: always 0xff |
See Also