GCS Modbus protocol reference guide
GCS Modbus protocol reference guide
The ECM contains data that can be read using a remote device communicating with the ECM via Modbus protocol
on a two-wire half-duplex RS-485 serial communications bus. In this arrangement, the remote device is the master,
and the ECM is a slave, supplying data to the master when requested. For further details refer to the Modbus mas-
ter-slave technique described in the Modbus Protocol Reference Guide (Modicon Document No. PI-MBUS-300).
The Modbus Protocol Reference Guide can be found on the World-Wide-Web (WWW) at the Schneider Automation
Inc. web-site. The document is accessible on-line using Universal Resource Locator (URL):
http://www.modicon.com/techpubs/techpubnew/pi_mbus_300.pdf
The customer can implement the RS-485 physical interface by connecting the shielded twisted-pair serial commu-
nications bus wires RS485+ and RS485- (pins 21 and 18 respectively) and the bus shield (pin 20) of ECM connector
06.
The Modbus operates at a communications rate of 9600 baud. At this data rate, the maximum specified bus length
of 4000 ft. [1219m] can be achieved. If the ECM is connected at either end of the communications bus, Term 1 and
Term 2 (pins 22 and 19 respectively) of ECM connector 06 are to be jumpered by shorting these two pins together.
If the ECM is not connected at either end of the bus, Term 1 and Term 2 should be left unconnected.
For further details regarding RS-485 implementation and applications, refer to Electronic Industries Association
Standard EIA-485, "Electrical Characteristics of Generators and Receivers for use in Balanced Digital Multi-Point
Systems". Additional information can be found on the WWW at the B&B Electronics Manufacturing Company web-
site. Refer to the "RS-422 and RS-485 Application Note" accessible on-line using URL:
http://www.bb-elec.com/bb-elec/literature/tech/485appnote.pdf
The information following provides specific details required to implement the digital portion of the Modbus Interface.
Please refer to Modicon’s Modbus Protocol Reference Guide for further details not inlcuded in this manual
The Modbus interface supports the Remote Terminal Unit (RTU) mode message framing only. The communications
parameters are set at 1 start bit, 8 data bits, no parity and 2 stop bits. The ECM slave device address is 1.
Modbus register data available for all engine models is defined in Appendix A. Appendix B Modbus Bit Data. Ap-
pendix C Supported Modbus Exception Codes. Modbus register parameters are identified as either Signed (S) or
Unsigned (U) in the Type column of the respective tables. Where signed values are used, the value is a 16-bit 2’s
complement number. The maximum amount of register data the ECM can return in a slave response is 16 registers.
The maximum length of the entire message must not exceed 256 bytes.
Appendix E defines the bit data available via the Modbus for all engine models. The maximum amount of bit data
the ECM can return in a slave response is 32 bits (specified as “inputs”, per the Modbus Protocol Reference Guide).
The maximum length of the entire message must not exceed 256 bytes.
Supported Modbus exception codes are defined in Appendix C, and supported diagnostic sub-functions are defined
in Appendix D.
Miscellaneous Application Requirements and Information
Page 104 Generator Drive Control System (GCS) Manual
1. The maximum amount of data the ECM can return in response to a Read Input Registers request (Function Code 04) is 16 registers.
The maximum length of an entire message must not exceed 256 bytes.
Miscellaneous Application Requirements and Information
Generator Drive Control System (GCS) Manual Page 105
b. The Most Recent Fault Events List consists of 42 records of fault data. Each record consists of 12 bytes containing data for
the Fault Code. Fault Code, Fault Count, ECM On-Time Time Stamp, and Engine Running Time Stamp. The Fault Count is
the number of occurences for the respective Fault Codes.
Miscellaneous Application Requirements and Information
Page 106 Generator Drive Control System (GCS) Manual
a. The Load Profile Monitor is a record consisting of percentile Ranges #1 through #10. Each range consists of 4 bytes desig-
nating the amount of time (in minutes) that the engine has been operating in the respective load range.
Miscellaneous Application Requirements and Information
Generator Drive Control System (GCS) Manual Page 107
a. The Load Profile Monitor is a record consisting of percentile Ranges #1 through #10. Each range consists of 4 bytes desig-
nating the amount of time (in minutes) that the engine has been operating in the respective load range.
Appendix B - Modbus Bit Data
Page 108 Generator Drive Control System (GCS) Manual
Coil/Input Total
Function
Switch Name Address number Read/Write States
Code
(Decimal) of bits
Remote Emergency-Stop Input 02 10003 1 Read Only Stop =1, Not Stop =0
Coolant Level Switch Stateb 02 10004 1 Read Only Low =1, Normal =0
a. The Fault Acknowledge command is a momentary signal and should be held in the “acknowledge” state for no
longer than 0.5 seconds when acknowledging a fault condition.
b. The Coolant Level Switch is to be supplied by the customer. The control system must be set -up to read the
Coolant Level Switch signal. See the Customer Supplied Coolant Level Switch section on page 101 for fur-
ther details.
Bit No. B A 9 8
Off 0 0 0 0
Ready 0 0 0 1
Fault Flashout 0 0 1 0
Non-Running Test 0 0 1 1
Starting 0 1 0 0
Idle 0 1 0 1
Rated 0 1 1 0
Normal Stop 0 1 1 1
Emergency Stop 1 0 0 0
Watchdog Test 1 0 0 1
1. The maximum amount of data the ECM can return in response to: i) a Read Coil Status request (Function Code 01) is 32 coils,
ii) a Force Single Coil request (Function Code 05) is 1 coil, or iii) a Read Input Status request (Function Code 02) is 32 inputs.
The maximum length of an entire message must not exceed 256 bytes.
Appendix C - Supported Modbus Exception Codes
Generator Drive Control System (GCS) Manual Page 109
02 Illegal Data Address The data address received in the query is not a
valid address
03 Illegal Data Value A value contained in the query data field is not a
valid value for the slave
Appendix D - Supported Modbus Diagnostics
Page 110 Generator Drive Control System (GCS) Manual
Sub-
Function Name Description
Code
00 Return Query Data The data passed in the query data field is to be returned (looped back) in the
response. The entire response message should be identical to the query.
01 Restart Communica- The slave’s peripheral port is to be initialized and restarted, and all of its communi-
tions Option cations event counters are to be cleared. If the port is currently in Listen Only
Mode, no response is returned. If the port is not currently in Listen Only Mode, a
normal response is returned.
04 Force Listen Only Forces the ECM into Listen Only Mode. This isolates it from the other devices on
Mode the network, allowing them to continue communicating without interruption from the
addressed slave. No response is returned.
The only function that will be processed after this mode is entered will be the
Restart Communications Option function (function code 08, subfunction 01)
10 Clear Counters and Clears all counters and the diagnostic register.
Diagnostic Register
11 Return Bus Message The response data field returns the quantity of messages that the slave has
Count detected on the communications system, since its last restart, clear counters opera-
tion, or power up.
12 Return Bus Commu- The response data field returns the quantity of CRC errors encountered by the ECM
nication Error Count since the its last restart, clear counters operation, or power-up.
13 Return Bus Exception The response data field returns the quantity of Modbus exception responses
Error Count returned by the ECM since the its last restart, clear counters operation, or power-
up.
14 Return Slave Mes- The response data field returns the quantity of messages addressed to the ECM, or
sage Count broadcast, that the ECM has processed since its last restart, clear counters opera-
tion, or power-up.
15 Return Slave No The response data field returns the quantity of messages addressed to the ECM for
Response Count which it did not return a response (neither a normal response nor an exception
response), since its last restart, clear counters operation, or power-up