198
9440300990 Rev J
Modbus™ Communication
DECS-250
MBAP Header Description
The MBAP Header contains the fields listed in Table 20.
Table 20. MBAP Header Fields
Fields
Length
Description
Client
Server
Transaction
Identifier
2 Bytes Identification of a Modbus
request/response transaction.
Initialized by
the client.
Recopied by the
server from the
received request.
Protocol
Identifier
2 Bytes 0 = Modbus protocol.
Initialized by
the client.
Recopied by the
server from the
received request.
Length
2 Bytes Number of following bytes.
Initialized by
the client
(request).
Initialized by the
server (response).
Unit Identifier
1 Byte
Identification of a remote
slave connected on a serial
line or on other buses.
Initialized by
the client.
Recopied by the
server from the
received request.
The header is 7 bytes long:
•
Transaction Identifier
– Used for transaction pairing, the Modbus server copies in the response
the transaction identifier of the request.
•
Protocol Identifier
– Used for intra-system multiplexing. The Modbus protocol is identified by the
value 0.
•
Length
– A byte count of the following fields, including the Unit Identifier and data fields.
•
Unit Identifier
– 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.
Note: All Modbus/TCP ADU are sent via TCP on registered port 502.
Error Handling and Exception Responses
Any query received that contains a non-existent device address, a framing error, or CRC error is ignored.
No response is transmitted. Queries addressed to the DECS-250 with an unsupported function or illegal
values in the data block result in an error response message with an exception response code. The
exception response codes supported by the DECS-250 are provided in
Table 21.
Table 21. Supported Exception Response Codes
Code
Name
Description
01
Illegal Function
The query Function/Subfunction Code is unsupported;
query read of more than 125 registers; query preset of
more than 100 registers.
02
Illegal Data
Address
A register referenced in the data block does not support
queried read/write; query preset of a subset of a numerical
register group.
03
Illegal Data Value
A preset register data block contains an incorrect number
of bytes or one or more data values out of range.
DECS-250 Modbus
™
via Ethernet
Modbus can communicate through Ethernet if the IP address of the DECS-250 is configured as described
in the
Communications
chapter of this manual.
Summary of Contents for DECS-250
Page 2: ......
Page 6: ...iv 9440300990 Rev J Revision History DECS 250 ...
Page 16: ...xiv 9440300990 Rev J Contents DECS 250 ...
Page 20: ...4 9440300990 Rev J Introduction DECS 250 ...
Page 28: ...12 9440300990 Rev J Power Stage DECS 250 ...
Page 32: ...16 9440300990 Rev J Voltage and Current Sensing DECS 250 ...
Page 40: ...24 9440300990 Rev J Synchronizer DECS 250 ...
Page 52: ...36 9440300990 Rev J Auxiliary Control DECS 250 ...
Page 56: ...40 9440300990 Rev J Contact Inputs and Outputs DECS 250 ...
Page 84: ...68 9440300990 Rev J Limiters DECS 250 ...
Page 114: ...98 9440300990 Rev J Power System Stabilizer DECS 250 Figure 96 PSS Parameter Settings ...
Page 124: ...108 9440300990 Rev J Stability Tuning DECS 250 ...
Page 126: ...110 9440300990 Rev J Mounting DECS 250 Figure 103 Overall and Projection Mounting Dimensions ...
Page 127: ...9440300990 Rev J 111 DECS 250 Mounting Figure 104 DECS 250 Escutcheon Plate Dimensions ...
Page 198: ...182 9440300990 Rev J Timekeeping DECS 250 ...
Page 210: ...194 9440300990 Rev J CAN Communication DECS 250 ...
Page 304: ...288 9440300990 Rev J Maintenance DECS 250 ...
Page 316: ...300 9440300990 Rev J Specifications DECS 250 ...
Page 334: ...318 9440300990 Rev J Analog Expansion Module DECS 250 ...
Page 351: ......