Table of Contents
Advertisement
11. Modbus communication protocol
11.1 About the Modbus communication protocol
SGC 420 supports a custom protocol based on the standard Modbus over an RS-485 layer. operates in a slave mode and responds
to commands received from an external Modbus master.
11.2 Modbus connection details
The transmission mode used by SGC 420/421 is Modbus RTU (not Modbus ASCII). The byte format for communication is 1 start bit,
8 data bits, no parity bits and 1 stop bit, Cyclic Redundancy Check (CRC).
Precautions
•
Find the slave ID from the SMPS and configure the same ID in the controller.
•
Enable the controller in the configuration of the SMPS after hardware connections are made.
•
Connect the controller terminals 31 and 32 to the SMPS terminals A and B.
•
Connect the controller terminal 30 to the ground of the SMPS. If the SMPS ground is not present, leave the controller terminal 30
open.
•
Use a two-core shielded cable for connection.
•
Use different colour wires for terminals 31 and 32 for easy detection and connection.
•
Route the wires properly ensuring they do not get short with any other wires.
•
Do not use multi strand wires for the connection.
11.3 Modbus functions
This genset controller operates as a Modbus slave that responds to certain commands (or functions, as defined by Modbus
standard) received from the Modbus master in appropriate format. Supported functions and respective command-response structure
is as shown below. If the command received from the Modbus master is other than the three functions mentioned below, an
exception message is generated.
Function code
03
16
USER MANUAL 4189341243A UK
Modbus name
Read holding register
Write holding register
Description
Reads one or more 16-bit registers from the slave device read/write location.
Writes one or more 16-bit registers to the slave device.
Page 53 of 78
Advertisement
Table of Contents
