Professional Documents
Culture Documents
http://slidepdf.com/reader/full/gcs-modbus-protocol-support-2v0 1/52
7/18/2019 GCS Modbus Protocol Support 2v0
Table of Contents
OVERVIEW................................................................................................ 3
INTRODUCTION........................................................................................ 3
FUNCTION CODE SUPPORT................................................................... 3
READ INPUT STATUS (FUNCTION CODE 02).................................... 4
READ OUTPUT REGISTERS (FUNCTION CODE 03) ......................... 5
READ INPUT REGISTERS (FUNCTION CODE 04) ............................. 5
FORCE SINGLE COIL (FUNCTION CODE 05)..................................... 6
PRESET SINGLE REGISTER (FUNCTION CODE 06)......................... 6
WRITE MULTIPLE COILS (FUNCTION CODE 15)............................... 7
WRITE MULTIPLE OUTPUT REGISTERS (FUNCTION CODE 16)..... 7
ERROR / EXCEPTION RESPONSE ....................................................... 22
ERROR RESPONSE FUNCTION CODE ............................................ 22
EXCEPTION RESPONSE CODE ........................................................ 22
OUTPUT FREQUENCY CONTROL VIA MODBUS................................ 23
KEYPAD FREQUENCY MODE ........................................................... 23
ANALOG FOLLOWER MODE ............................................................. 24
PID CONTROL MODE ......................................................................... 24
STATUS AND REGISTER ADDRESSES............................................... 27
TABLE 1: INPUT STATUS REGISTERS ............................................. 27
TABLE 2: OUTPUT STATUS REGISTERS ......................................... 30
TABLE 3: INPUT REGISTERS ............................................................ 35
TABLE 4: OUTPUT REGISTERS ........................................................ 39
http://slidepdf.com/reader/full/gcs-modbus-protocol-support-2v0 2/52
7/18/2019 GCS Modbus Protocol Support 2v0
OVERVIEW
This document provides the technical specifications of the Modbus RTU protocol support included with all
Centrilift’s Graphic Control System (GCS) control units. All modules within the GCS group utilize the same
register address map to facilitate exchanging model types with minimal disruptions to the central SCADA
system’s configuration.
INTRODUCTION
The Graphic Control System products support a subset of the functions of Modicon Modbus Protocol in RTU (or
binary) format as described in Modicon Modbus Protocol Reference Guide PI-MBUS-300, Rev C, dated
January 1991. Specifically, the supported Modbus function codes are:
This document describes the supported functions and the response to each valid request from the host. It is
intended to be used in conjunction with the Modicon Modbus protocol definition and applies to GCS (Graphic
Control System) system controller software revision 6.44 or higher. All numeric values shown in the function
code request and response examples are in hexadecimal (base 16) format, even when not denoted with an “H”.
http://slidepdf.com/reader/full/gcs-modbus-protocol-support-2v0 3/52
7/18/2019 GCS Modbus Protocol Support 2v0
Digital output states are read by the host via Function Code 01, "Read Output Status". The first “coil” of this
block reflects the state of the motor contactor or RUN state of the controller. If the motor is shut down Coil 0200
H will be set; if it has been requested to start, Coil 0200 H will be clear. All other output status coils will return
their status in the same fashion.
For a complete list of the registers, see the tables at the end of this document.
Query:
Response:
RTU FUNCTION BYTE COUNT DATA COIL CRC
ADDRESS CODE STATUS
Status inputs are accessed by the host via Function Code 02H, "Read Input Status". These status locations
receive their values from devices connected to the I/O channels available or internal processes such as alarms,
and can only be read, not altered within the system unit or via Modbus protocol.
For a complete list of the registers, see the tables at the end of this document.
Query:
Response:
http://slidepdf.com/reader/full/gcs-modbus-protocol-support-2v0 4/52
7/18/2019 GCS Modbus Protocol Support 2v0
Output registers are read via Function Code 03, "Read Output Registers". Up to 125 registers can be obtained
by one request.
For a complete list of the registers, see the tables at the end of this document.
Query:
Response:
Analog inputs are read via Function Code 04, "Read Input Registers". These registers locations receive their
values from devices connected to the I/O channels available to the GCS controller and can only be read, not
altered directly within the controller or via Modbus protocol. The GCS controller allows up to 125 registers to be
obtained by one request. For a complete list of the registers, see the tables at the end of this document.
Example: Function Code 4
Query:
Response:
RTU FUNCTION BYTE COUNT RETURNING DATA CRC
ADDRESS CODE
http://slidepdf.com/reader/full/gcs-modbus-protocol-support-2v0 5/52
7/18/2019 GCS Modbus Protocol Support 2v0
Individual digital outputs (coils) are modified by the Modbus host via Function Code 05, "Force Single Coil". The
GCS controller has only three physical digital outputs onboard (relay contacts) but many virtual digital outputs
that are used to control various processes in the controller. Expansion I/O modules can be connected to a GCS
control unit thereby increasing the available physical digital outputs (relay contacts)
Query:
RTU FUNCTION COIL ADDR COIL ADDR DATA ON/OFF DATA CRC
ADDRESS CODE HIGH LOW
Response:
RTU FUNCTION COIL ADDR COIL ADDR DATA ON/OFF DATA CRC
ADDRESS CODE HIGH LOW
Individual output registers are modified by the host via Function Code 06, "Preset Single Register".
For a complete list of the registers, see the tables at the end of this document.
Query:
RTU FUNCTION REG. ADDR REG. ADDR DATA VALUE DATA VALUE CRC
ADDRESS CODE HIGH LOW HIGH LOW
Response:
RTU FUNCTION COIL ADDR COIL ADDR DATA ON/OFF DATA CRC
ADDRESS CODE HIGH LOW
http://slidepdf.com/reader/full/gcs-modbus-protocol-support-2v0 6/52
7/18/2019 GCS Modbus Protocol Support 2v0
Multiple digital outputs are modified by the host in a single message via Function Code 15, "Write Multiple
Coils". The GCS controller has only three physical digital outputs (relay contacts) but many virtual digital outputs
that are used to control various processes in the controller. Additional digital outputs can be added to a GCS
system by using Expansion I/O modules. For a complete list of the output status points, see the tables at the
Query:
01H 0FH 02H 02H 00H 01H 01H 00H 56H B5H
Response:
aMultiple
completeoutput
list ofregisters are modified
the registers, see theby the host
tables viaend
at the Function
of thisCode 16, "Write Multiple Output Registers". For
document.
Query:
01H 10H 02H 20H 00H 01H 02H 00H 22H F0H 78H
Response:
http://slidepdf.com/reader/full/gcs-modbus-protocol-support-2v0 7/52
7/18/2019 GCS Modbus Protocol Support 2v0
When retrieving information from a GCS unit using function code 65, the query will always adhere to the
following form:
Where:
rtuAddress is the modbus address of the GCS unit being queried
functionCode is always 65 (41 HEX)
startingAddress is:
pointCount is 0 if the packet marks the first packet of an exchange and is 1 if the packet is the
continuation of the exchange.
The first four bytes of the GCS’s response will always be the RTU address, the function code and a block count.
The block count will be positive as long there is un-transferred data within the GCS unit. To signal the last
packet, the block count (signed short integer) goes negative. The negative number is to be interpreted as ( –1 *
(the number of records within the packet)). For example, if the block count was returned as FFEC hex, convert
that value into the decimal equivalent as follows:
FFEC = 65,516 ------ 0x10000= 65,536 ------ 65,516 – 65536 = -20 ------ -20 * -1 = 20 records
The following describes the data dependant responses by the GCS controller to Modbus 65 packets.
http://slidepdf.com/reader/full/gcs-modbus-protocol-support-2v0 8/52
7/18/2019 GCS Modbus Protocol Support 2v0
SHUTDOWN HISTORY
unsigned char
signed short functionCode;
blockCount;
shutDownHistory data[HISTORY_RECORDS_PER_PACKET];
unsigned short crc;
}aHistoryResponse;
where, HISTORY_RECORDS_PER_PACKET is 10 .
where,
ampsA, ampsB and ampsC are the three phase current at the time of the decision to shutdown.
VoltAB, voltBC and voltCA are the phase to phase voltage at the time of the decision to shutdown.
AnalogIn1 and analogIn2 are the value at the analog inputs of the GCS system controller.
CauseOfShutdown is a number indicating why the shutdown happened.
Lockout is a number indicating if the motor start was locked out because of the shutdown.
The timeStamp is a signed 32bit integer that holds the number of seconds since January 1, 1970 and can be
de-coded using the library routines supplied with most C compilers.
http://slidepdf.com/reader/full/gcs-modbus-protocol-support-2v0 9/52
7/18/2019 GCS Modbus Protocol Support 2v0
Query:
n 1 y
r y
r y
r y
r
w # o o o o
e o d t t t t A A
s d d
t r s )
i s )
i s )
i s )
i b b
s o t t H p H p H p H p e e e e
e n n u o s s s s
r C u u h c n m n m n m n m a a a a
d n o o S e
r w
a
T w
a
T w
a
T w
a
T h h h h
d o
i C C f y o S o S o S o S P P P ) P
A t k ) o r
k ) t d d d d s ) s )
U
c
n c h
g
o
c w r t t e
u m
t e
u m
t e
u m
t e
u m p h
g p w s
p h
g
s )
p w
T u o i l
l o o t
a i
s h i h i h i h i m i m o m i m o
R F B h
( B L
( S H S t
( S t
( S t
( S t
( A h
( A l
( a h
( a l
(
01H 41H 00H 0AH 3EH A6H 65H 2DH 00H 4FH 00H 4EH
n
w t t n 2 y
r y
r y
r y
r
o u ) u w # o o o o
d
t ) o o o d t t t t A
u w k h
g k ) d
t r s )
i s )
i s )
i s )
i
h l c i c w u o H p H p H p H p e
o o h o o s
s l l h c n m n m n m n m
f -
- f -
- f l S e
r w
a
w
a
w
a
w
a a
h …
o d
i o d
i o d
i f y T
o S
T
o S
T
o S
T
o S P a
r
-
e t -
e t -
e t o r
s i
n s i
n s i
n t o d
t e d
t e d
t e d
t e s )
h
e
t
u o u o u o r t u m u m u m u m p g e
a p a p a p t s
a i h i h i h i h i m c
i t
C ( C ( C ( S H S t
( S t
( S t
( S t
( A h
( E
http://slidepdf.com/reader/full/gcs-modbus-protocol-support-2v0 10/52
7/18/2019 GCS Modbus Protocol Support 2v0
Convert the hexadecimal values into decimal notation and history record #1 in the above example yields the
following information:
Shutdown occurred on April 23, 2003 at the time of 10:04:29. (Time integer value: 3E A6 65 2D hex.)
The three phase volts were: Phase AB = 481 volts AC (01E1 hex)
Phase BC = 484 volts AC (01E4 hex)
Phase CA = 483 volts AC (01E3 hex)
http://slidepdf.com/reader/full/gcs-modbus-protocol-support-2v0 11/52
7/18/2019 GCS Modbus Protocol Support 2v0
STARTUP WAVEFORM
Startup waveform data consists of the three motor currents and voltages sampled at 600 readings per second
for 2 seconds after the start of the motor.
typedef struct
{
unsigned char rtuAddress;
unsigned char functionCode;
signed short blockCount;
highSpeedTrend data[TREND_RECORDS_PER_PACKET];
unsigned short crc;
}aStartupWaveformResponse;
where TREND_RECORDS_PER_PACKET is 20
where,
ampsA, ampsB and ampsC are the instantaneous values of the three phase currents and VoltAB,
voltBC and voltCA are the phase to phase voltage at the time of the sample.
To fetch the time at which the motor was started, build a request packet with its startingAddress field set to 1
and its pointCount set to –1. The GCS units will return a packet formatted as
typedef struct
{
unsigned char rtuAddress;
unsigned char functionCode;
signed short blockCount;
time_t timeStamp;
unsigned short crc;
}aStartupTimestampResponse;
http://slidepdf.com/reader/full/gcs-modbus-protocol-support-2v0 12/52
7/18/2019 GCS Modbus Protocol Support 2v0
First, send a message with a point count of -1 (FFFE hex), to retrieve the “start time” of the last motor start.
Query:
RTU
ADDRESS FUNCTION
CODE START
ADDR HIGH START
ADDR LOW POINT COUNT
HIGH POINT COUNT
LOW CRC
r
o
t t t t t
e o r r r r
d m a )
t a )
t a )
t a )
t
s t t t s p s p s p s p
s o n n t p
e
r C u u s m r m r m r m r m
d o o a e
l o a
t o a
t o a
t o a
t
n t
f t o T o T o T o T
d o
i C C o a S S S S
A t k ) k ) M M M M ) )
U
T c
n c h
o
l g
i c
o w
o e
m t
r
a t
s e
m
l L i t a i t
s e
m t
s e
m t
s e
m C h
g
i C w
R
u
F h
B ( B ( T s L (
a i
t L t
(
a i
t
L ( t R
a i
L ( h R
C (
o
l
C (
01H 41H 00H 01H 3EH 64H BEH 86H 51H 36H
Query: Next, retrieve the first 20 of 1200 samples by using function code 65.
d
e B B
e A A B B C C A A
p 1 e e e e e e
e
d S #
t s s s s s s e e
s t t h e a a a a a a s s
s o n n h h h h h h a a
e
r C u u i k
g h h
d n o o H c
a
P P P P P P P P
d o C C f p t t t t t t e e
A i
t ) o n ) n n ) n n ) n g ) g )
c k h k ) t d e
r h e
r ) e
r h e
r ) e
r h e
r ) a h a
U n c g c w r n r i
g r w r i
g r w r i
g r w t
l i
g t
l w
o i o o a e
T
R u
F l (
B h l
B L t T
( S r u (
C h u (
C l
o u (
C h u (
C l
o u (
C h u (
C l
o o (
V h o (
V l
o
01H 41H 00H 14H 00H 08H 00H 10H FFH EBH 01H 15H
http://slidepdf.com/reader/full/gcs-modbus-protocol-support-2v0 13/52
7/18/2019 GCS Modbus Protocol Support 2v0
d
C C A A e B B
B B C C e A A B B C C A A
p 2 e e e e e e
e e e e S #
t s s s s s s e e
s s s s h e a a a a a a s s
a a a a h h h h h h a a
h h h h i k
g h h
P P P P H c
a
P P P P P P P P
e e e e f p t t t t t t e e
g
a )
h g
a ) g
a )
h g
a ) o d
t n
e
r )
h n
e
r ) n
e
r )
h n
e
r ) n
e
r )
h n
e
r ) g
a )
h g
a )
t
l i
g t
l w t
l i
g t
l w r n r i
g r w r i
g r w r i
g r w t
l i
g t
l w
o h o o o h o o a e
t r u h u o u h u o u h u o o h o o
V ( V l
( V ( V l
( S T C ( C l
( C ( C l
( C ( C l
( V ( V l
(
FEH CDH 00H 1EH 00H 00H FFH F0H 00H 10H 00H 69H
d
C C A A e
B B C C e A A
p 3 e e
e e e e S #
t s s
s s s s h e a a
a a a a h h
h h h h i k
g
P P P P H c
a
P P …
a
e e e e f p t t r
o n n
g h
a
t
l ) g )
a
g t
l g h
a
w t
l )
g g )
a
t
l w t
r d
n e h
r
r )
g e )
r
r w t
e
o i o o i
o l o l a e
o t r u i u o c
t
V ( V ( V h
h ( V ( S T C h
( C l
( E
Query: Now retrieve the remaining data by setting the point count to 0001 and repeat the request for data until
the block count value in the response switches to a negative number as shown below.
d
e B B
e A A B B C C A A
p e e e e e e
e S t s s s s s s e e
s d t t h e a a a a a a s s
s o n n g k h h h h h h a a
e
r C u u i h h
d n o o H c
a
P P P P P P P P …
a
d o C C f p t t t t t t e e r
A i
t ) ) o n ) n n ) n n ) n g ) g ) e
k h k d e e ) e e ) e e ) t
U
c
n c g c w t
r n r h
r i
g
r
r w r h
r i
g
r
r w r h
r i
g
r
r w
a h
t
l i
g
a
t
l w e
T u o i l
l o o t
a e
r u h u l
o u h u l
o u h u l
o o h o l
o c
t
R F h B (
B ( L S T C ( C ( C ( C ( C ( C ( V ( V ( E
01H 41H FFH ECH 00H 73H FFH 59H 00H 35H FFH B9H …
As illustrated in the example above, the GCS responded with a block count of FFEC hex or -19 decimal. This
indicates that there are no more un-retrieved waveforms packets and that this message contains the normal 20
records
The instantaneous values of the current and voltage can be graphed by using common PC software such as
MS Excel spreadsheet.
http://slidepdf.com/reader/full/gcs-modbus-protocol-support-2v0 14/52
7/18/2019 GCS Modbus Protocol Support 2v0
EVENTS
typedef struct
{
unsigned char rtuAddress;
unsigned char functionCode;
signed short blockCount;
anEventRecord eventRecord[EVENT_RECORDS_PER_PACKET];
unsigned short crc;
}anEventRecordResponse;
where, EVENT_RECORDS_PER_PACKET is 20
typedef struct
{
time_t timeStamp;
unsigned char EventType;
unsigned char Exponent;
PointId PointIdent;
PValue ValueBeforeEvent;
PValue ValueAfterEvent;
}anEventRecord;
Query: Retrieve the first packet of event history by setting the point count to 0000H.
http://slidepdf.com/reader/full/gcs-modbus-protocol-support-2v0 15/52
7/18/2019 GCS Modbus Protocol Support 2v0
Response: (First packet of event history, only the first portion of the reply is shown)
The time integer “3EA67A4F” converts to April 23, 2003 at 11:34:39 am.
The Event type is reported as a “02” which is defined as an “Alarm return to normal” or Alarm_RTN
The exponent is reported as a “00” which means there is no decimal point in the value.
The Event Point Identifier is reported as 00A7 or 167 decimal. Table 5 lists Point ID 167 as being Overload
Alarm. Since this event had no data values associated with it, the before and after values are left at zero.
Query: Continue to retrieve the next 20 event records by setting the point count to 0001H, until the block count
in the reply turns negative as shown in the example below.
Response: (Last packet of event history, only part of the reply is shown)
) ) t
h w e e e e n
g
i o 1 c c c c e t 2
h L # n n n n v n #
e ( ( t e e ) e ) e ) ) ) e e t
s d r ) r p r p r h v
s o t t n r p r r r p g w e
r e n
e n n e u m u m u m u m e i o r e
r C u u v c a c a c a c a p t h
( l
( o
f e v
d n o o E c T c T c T c T y n e t
f E
d o
i C C f O O S O S O S T e D
I D
I b a f
A t k k o
t t S t e t e t e t n t t e e o
t
c c c r n e n n n n o n n u u r
U n o o a e m e i
m e i
m e i
m e p i i l l a
T u l l t v i
t v t v t v t v x o o a a t
R F B B S E ( E ( E ( E ( E E P P V V S
01H 41H FFH F1H 3EH A6H 63H 9EH 03H 00H 00H 5BH 00H 02H
The reply illustrated above shows a block count of FFF1H (-15 decimal). That means there are no more event
records to be retrieved and that this packet does contain 15 event records.
http://slidepdf.com/reader/full/gcs-modbus-protocol-support-2v0 16/52
7/18/2019 GCS Modbus Protocol Support 2v0
AMPCHARTING
The GCS motor controllers record the motor current present of Phase B of the power system. This current data
is sampled at high speeds and converted to RMS values. The high speed values are averaged over a four
minute period and the minimum and maximum values are recorded in each 1 minute portion of the four minute
The ampchart data consisting of four minute averages and minimum / maximum values is accessed using a
starting address of 3, within a Function Code 65 query.
typedef struct
{
unsigned char rtuAddress;
unsigned char functionCode;
signed short blockCount;
aFourMinuteAmpchartRecord data[FOUR_MINUTE_AC_RECORDS_PER_PACKET];
unsigned short crc;
}anAmpchartRecordResponse;
typedef struct
{
time_t timeStamp;
PValue average;
PValue minimum;
PValue maximum;
}aFourMinuteAmpchartRecord;
http://slidepdf.com/reader/full/gcs-modbus-protocol-support-2v0 17/52
7/18/2019 GCS Modbus Protocol Support 2v0
Query: Retrieve the first packet of four minute ampchart records by setting the point count to 0000H.
The block count 0018H indicates that 24 ampchart records are contained in this packet.
http://slidepdf.com/reader/full/gcs-modbus-protocol-support-2v0 18/52
7/18/2019 GCS Modbus Protocol Support 2v0
Ampchart: Four minute average, plus one minute minimum and maximum values
The ampchart data consisting of a four minute average and four, one minute minimum / maximum values is
accessed using a starting address of 6, within a Function Code 65 query.
typedef struct
{
unsigned char rtuAddress;
unsigned char functionCode;
signed short blockCount;
aOneMinuteAmpchartRecord data[ONE_MINUTE_AC_RECORDS_PER_PACKET];
unsigned short crc;
}anAmpchartRecordResponse;
where, ONE_MINUTE_READINGS_PER_RECORD is 4
timeStamp is the time of the most recent reading. This field is updated every minute.
Average is the average of the current over a four minute period.
where minumum and maximum are the extremes of phase B current in amps measured during the one minute
period.
Query: The first message requesting ampchart data must have a point count value of zero, as shown below.
RTU
ADDRESS FUNCTION
CODE START
ADDR HIGH START
ADDR LOW POINT
HIGH COUNT POINT
LOW COUNT CRC
http://slidepdf.com/reader/full/gcs-modbus-protocol-support-2v0 19/52
7/18/2019 GCS Modbus Protocol Support 2v0
The block count 000BH indicates that 11 ampchart records are contained in this packet.
The
The average
minimumcurrent
currentduring
value the fourall
during minute period
four one wassample
minute 0016Hex = 22 amps
periods (decimal)= 21 amps
was 0015Hex
The maximum current value during all four one minute sample periods was 0017Hex = 23 amps )
After using a point count of 0000H to initiate the transfer of the ampchart records, use a point count of 0001 for
all subsequent queries until the block count value is returned as a negative value. As in all function code 65
transfers, a negative block count indicates that the response contains the final records to be transferred and the
negative value multiplied by negative 1 represents the number of records in this message. An example is shown
below:
Query: The point count is set to one to continue the transfer of ampchart records.
http://slidepdf.com/reader/full/gcs-modbus-protocol-support-2v0 20/52
7/18/2019 GCS Modbus Protocol Support 2v0
The block count FFFEH indicates that this response contains the last un-transferred records of the
ampchart and that a total of 2 records are contained in this packet. (10000H – FFFEH) = 2
Record #1 reports
The average a time
current stamp
during of 3EA95DA3
the four Hexwas
minute period or 2003/04/25
0006Hex =16:09:07
06 amps (decimal)
The minimum current value during all four one minute sample periods was 0006Hex = 06 amps
The maximum current value during all four one minute sample periods was 0006Hex = 06 amps )
http://slidepdf.com/reader/full/gcs-modbus-protocol-support-2v0 21/52
7/18/2019 GCS Modbus Protocol Support 2v0
10 90
http://slidepdf.com/reader/full/gcs-modbus-protocol-support-2v0 22/52
7/18/2019 GCS Modbus Protocol Support 2v0
Percentage of full scale = (Present Value of input / full scale value of input) * 100
Next the GCS drive's High Speed clamp and Low Speed clamp settings are determined. The Low Speed clamp
is designated as 0 % speed, while the High Speed Clamp is designated as 100% speed. The controller then
calculates the actual frequency value that corresponds to the percentage of full scale and uses that value as the
desired output frequency. Additionally, the drive can be set to react in forward or reverse. In forward acting, as
the analog setpoint signal is increased, the drive frequency increases. In reverse acting, as the analog setpoint
is increased, the drive frequency decreases.
The GCS drives provide support for Modbus RTU protocol. Using this communication capability, the user can
modify the variables using the following modbus address registers.
If Keypad Frequency Setpoint is selected, (Modbus Address 40811 = 1), the user can set the frequency by
writing 10 times the desired value (in decimal) to Modbus address: 40784 (0x030F).
For example: to set the frequency to 59.5 Hz, write the value of 595 to address 40784
to set the frequency to 22.9 Hz, write the value of 229 to address 40784
http://slidepdf.com/reader/full/gcs-modbus-protocol-support-2v0 23/52
7/18/2019 GCS Modbus Protocol Support 2v0
If Analog Follower Mode is selected, (Modbus Address 40811 = 2), the user can configure which analog input is
used as the setpoint and whether the controller is forward or reverse acting.
Setpoint input for Analog Follower mode is located at Modbus address 40761 (0x02F8). This setpoint can
Expansion I/O Module 1, Analog Input #1: 1213 (Modbus address 40761 = 1213 decimal)
Expansion I/O Module 1, Analog Input #2: 1214 (Modbus address 40761 = 1214 decimal)
Expansion I/O Module 2, Analog Input #1: 1215 (Modbus address 40761 = 1215 decimal)
Expansion I/O Module 2, Analog Input #2: 1216 (Modbus address 40761 = 1216 decimal)
Expansion I/O Module 3, Analog Input #1: 1217 (Modbus address 40761 = 1217 decimal)
Expansion I/O Module 3, Analog Input #2: 1218 (Modbus address 40761 = 1218 decimal)
Controller direction:
The controller is set to be forward acting by writing Modbus Address 45822 (0x16BD) = 0
The controller is set to be reverse acting by writing Modbus Address 45822 (0x16BD) = 1
Setpoint input for PID Control mode is located at Modbus address 40762 (0x02F9). This setpoint can accept the
following decimal values:
Expansion I/O Module 1, Analog Input #1: 1213 (Modbus address 40762 = 1213 decimal)
Expansion I/O Module 1, Analog Input #2: 1214 (Modbus address 40762 = 1214 decimal)
Expansion I/O Module 2, Analog Input #1: 1215 (Modbus address 40762 = 1215 decimal)
Expansion I/O Module 2, Analog Input #2: 1216 (Modbus address 40762 = 1216 decimal)
Expansion I/O Module 3, Analog Input #1: 1217 (Modbus address 40762 = 1217 decimal)
Expansion I/O Module 3, Analog Input #2: 1218 (Modbus address 40762 = 1218 decimal)
http://slidepdf.com/reader/full/gcs-modbus-protocol-support-2v0 24/52
7/18/2019 GCS Modbus Protocol Support 2v0
Note: Take care that both the setpoint and feedback inputs do not contain the same value.
If the Manual Setpoint Value is selected, then the actual setpoint value is written to Modbus address 40662
(0x0295). For example, if the manual setpoint value of 1595(decimal) is desired, write to Modbus address
40662 = 1595
Value of Manual Setpoint == Modbus address 40662 (0x295)
Feedback input for PID Control mode is located at Modbus address 40763 (0x02FA). This setpoint can accept
the following decimal values:
Expansion I/O Module 1, Analog Input #1: 1213 (Modbus address 40763 = 1213 decimal)
Expansion I/O Module 1, Analog Input #2: 1214 (Modbus address 40763 = 1214 decimal)
Expansion I/O Module 2, Analog Input #1: 1215 (Modbus address 40763 = 1215 decimal)
Expansion I/O Module 2, Analog Input #2: 1216 (Modbus address 40763 = 1216 decimal)
Expansion I/O Module 3, Analog Input #1: 1217 (Modbus address 40763 = 1217 decimal)
Expansion I/O Module 3, Analog Input #2: 1218 (Modbus address 40763 = 1218 decimal)
Note: Take care that both the setpoint and feedback inputs do not contain the same value.
Proportional Gain:
The proportional gain value is located at Modbus address 45829. This value is written as ten times the desired
value. For example, if 12.5% gain is desired, write 125 (decimal) to Modbus address 45829.
Integral Gain:
The integral gain value is located at Modbus address 45830. This value is written as ten times the desired value.
For example, if 10.1% gain is desired, write 101 (decimal) to Modbus address 45830.
Derivative Gain:
The derivative gain value is located at Modbus address 45831. This value is written as ten times the desired
value. For example, if 3.2 % gain is desired, write 32 (decimal) to Modbus address 45831.
http://slidepdf.com/reader/full/gcs-modbus-protocol-support-2v0 25/52
7/18/2019 GCS Modbus Protocol Support 2v0
Controller direction:
The controller is set to be forward acting by writing Modbus Address 45832 (0x16C7) = 0
The controller is set to be reverse acting by writing Modbus Address 45832 (0x16C7) = 1
http://slidepdf.com/reader/full/gcs-modbus-protocol-support-2v0 26/52
7/18/2019 GCS Modbus Protocol Support 2v0
INPUT STATUS
(READ INPUT STATUS = FUNCTION CODE 02)
(V =Vortex, E =Electrospeed, T =Trident, M =Expansion Module)
DIGITAL_IN1_SD_ALARM Digital Input 1 Shutdown Alarm 0x0100 10257
DIGITAL_IN2_SD_ALARM Digital Input 2 Shutdown Alarm 0x0101 10258
IUNBAL_SD_ALARM Current Unbalance Shutdown Alarm 0x0102 10259 V
VUNBAL_SD_ALARM Voltage Unbalance Shutdown Alarm 0x0103 10260
OVERVOLT_SD_ALARM Over Voltage Shutdown Alarm 0x0104 10261
UNDERVOLT_SD_ALARM Under Voltage Shutdown Alarm 0x0105 10262
UNDERLOAD_SD_ALARM Undercurrent Shutdown Alarm 0x0106 10263
OVERLOAD_SD_ALARM Over current Shutdown Alarm 0x0107 10264
CONTACTOR Status of motor contactor 0x0108 10265
RED Relay contact Status for Red panel light 0x0109 10266
AUTO Optional HOA mode switch in “AUTO” 0x010A 10267
HAND Optional HOA mode switch in “HAND” 0x010B 10268
LOCKOUT Status of Auto restarts Lockout / permit 0x010C 10269
START Optional Start switch input status 0x010D 10270
ROTATION_ALARM Incoming phase rotation change alarm 0x010E 10271
ANALOG1_HI_THLD_SD_ALARM High Threshold Shutdown Alarm 0x010F 10272
ANALOG1_LO_THLD_SD_ALARM Low Threshold Shutdown Alarm 0x0110 10273
ANALOG2_HI_THLD_SD_ALARM
ANALOG2_LO_THLD_SD_ALARM High Threshold Shutdown
Low Threshold Shutdown Alarm
Alarm 0x0111
0x0112 10274
10275
NULL_POINT Unused /Reserved 0x0113 10276
DIGITAL_IN1_SDSTATE_TRUE Digital In 1 in Alarm, in Shutdown Delay 0x0114 10277
DIGITAL_IN2_SDSTATE_TRUE Digital In 2 in Alarm, in Shutdown Delay 0x0115 10278
OVERLOAD_HI_THLD_XCEED Overload in Alarm, in Shutdown Delay 0x0116 10279
UNDERLOAD_LO_THLD_XCEED Underload in Alarm, in Shutdown Delay 0x0117 10280
ANALOG1_HI_THLD_XCEED Analog1 Hi in Alarm, in Shutdown Delay 0x0118 10281
DIGITAL_IN3_SD_ALARM Digital Input 3 Shutdown Alarm 0x0119 10282 E
OVERVOLT_HI_THLD_XCEED Over Voltage Alarm, in Shutdown Delay 0x011A 10283
UNDERLOAD_LO_THLD_XCEED Under Current Alarm, in Shutdown Delay 0x011B 10284
ROTATION_SDSTATE_TRUE Incoming Phase Rotation has Changed 0x011C 10285
ANALOG1_LO_THLD_XCEED Analog1 Lo in Alarm, in Shutdown Delay 0x011D 10286
ANALOG2_HI_THLD_XCEED Analog 2 Hi in Alarm, in Shutdown Delay 0x011E 10287
ANALOG2_LO_THLD_XCEED Analog 2 Lo in Alarm, in Shutdown Delay 0x011F 10288
PCM_CONSTANT_TORQUE Constant Torque Mode 0x0120 10289 E
PCM_ILIMIT Current Limit Active 0x0121 10290 E
DIGITAL_IN1 On board Digital Input 1 0x0122 10291
DIGITAL_IN2 On board Digital Input 2 0x0123 10292
DIGITAL_IN3 On board Digital Input 3 0x0124 10293 E
IO1DI1_DEBOUNCED I/O Module 1 Digital Input 1 0x0125 10294 M
IO1DI2_DEBOUNCED I/O Module 1 Digital Input 2 0x0126 10295 M
http://slidepdf.com/reader/full/gcs-modbus-protocol-support-2v0 27/52
7/18/2019 GCS Modbus Protocol Support 2v0
INPUT STATUS
(READ INPUT STATUS = FUNCTION CODE 02)
(V =Vortex, E =Electrospeed, T =Trident, M =Expansion Module)
IO1DI3_DEBOUNCED I/O Module 1 Digital Input 3 0x0127 10296 M
IO2DI1_DEBOUNCED I/O Module 2 Digital Input 1 0x0128 10297 M
IO2DI2_DEBOUNCED I/O Module 2 Digital Input 2 0x0129 10298 M
IO2DI3_DEBOUNCED I/O Module 2 Digital Input 3 0x012A 10299 M
IO3DI1_DEBOUNCED I/O Module 3 Digital Input 1 0x012B 10300 M
IO3DI2_DEBOUNCED I/O Module 3 Digital Input 2 0x012C 10301 M
IO3DI3_DEBOUNCED I/O Module 3 Digital Input 3 0x012D 10302 M
IO1DI1_DETECT_AC I/O Module 1 Digital Input 1 (AC Input) 0x012E 10303 M
IO1DI2_DETECT_AC I/O Module 1 Digital Input 2 (AC Input) 0x012F 10304 M
IO1DI3_DETECT_AC I/O Module 1 Digital Input 3 (AC Input) 0x0130 10305 M
IO2DI1_DETECT_AC I/O Module 2 Digital Input 1 (AC Input) 0x0131 10306 M
IO2DI2_DETECT_AC I/O Module 2 Digital Input 2 (AC Input) 0x0132 10307 M
IO2DI3_DETECT_AC I/O Module 2 Digital Input 3 (AC Input) 0x0133 10308 M
IO3DI1_DETECT_AC I/O Module 3 Digital Input 1 (AC Input) 0x0134 10309 M
IO3DI2_DETECT_AC I/O Module 3 Digital Input 2 (AC Input) 0x0135 10310 M
IO3DI3_DETECT_AC I/O Module 3 Digital Input 3 (AC Input) 0x0136 10311 M
**RESERVED** Reserved 0x0137 10312
PASSWORD_INVALID User Password is invalid / expired 0x0138 10313
NULL_POINT Reserved 0x0139 10314
NULL_POINT Reserved 0x013A 10315
NULL_POINT Reserved 0x013B 10316
NULL_POINT Reserved 0x013C 10317
IUNBAL_HI_THLD_XCEED Current Unbalance Threshold exceeded 0x013D 10318 V
VUNBAL_HI_THLD_XCEED Voltage Unbalance Threshold exceeded 0x013E 10319
PCM STATUS WORD 1 Power Conversion Module
PCM_RUNNING Running 0x0140 10321 E
PCM_STOPPED Stopped: All gate signals inhibited 0x0141 10322 E
PCM_STOPPING Stopping: Command acknowledged 0x0142 10323 E
PCM_ACCEL Accelerating 0x0143 10324 E
PCM_DECEL Decelerating 0x0144 10325 E
PCM_ILIMIT Current Limit 0x0145 10326 E
PCM_BUS_VOLTS_BIT DC Bus voltage High Threshold 0x0146 10327 E
PCM STATUS WORD 2 Power Conversion Module
PCM_FAULT PCM Fault word is active 0x0147 10328 E
PCM_INVERTER_ROTATION Output inverter phase rotation 0x0148 10329 E
PCM_CONVERTER1_ROTATION Converter 1 input phase rotation 0x0149 10330 E
PCM_CONVERTER2_ROTATION Converter 2 input phase rotation 0x014A 10331 E
PCM_PHASED Input phase rotation determined 0x014B 10332 E
PCM_IN_SYNC_DELAY Inverter in synchronization delay 0x014C 10333 E
PCM_PHASE_LOCKED Converter Zero Crossing established 0x014D 10334 E
PCM Fault Word Power Conversion Module
PCM_FAULT PCM Fault word is active 0x014E 10335 E
PCM_PHASE_APOSITIVE_IOT A Ø Positive Instantaneous overload 0x014F 10336 E
PCM_PHASE_BPOSITIVE_IOT B Ø Positive Instantaneous overload 0x0150 10337 E
PCM_PHASE_CPOSITIVE_IOT C Ø Positive Instantaneous overload 0x0151 10338 E
PCM_PHASE_ANEGATIVE_IOT A Ø Negative Instantaneous overload 0x0152 10339 E
PCM_PHASE_BNEGATIVE_IOT B Ø Positive Instantaneous overload 0x0153 10340 E
PCM_PHASE_CNEGATIVE_IOT C Ø Positive Instantaneous overload 0x0154 10341 E
PCM_ZERO_CROSSING_FAULT Input Zero Crossing signal loss 0x0155 10342 E
http://slidepdf.com/reader/full/gcs-modbus-protocol-support-2v0 28/52
7/18/2019 GCS Modbus Protocol Support 2v0
INPUT STATUS
(READ INPUT STATUS = FUNCTION CODE 02)
(V =Vortex, E =Electrospeed, T =Trident, M =Expansion Module)
PCM_SYSTEM_ERROR Processor software or hardware fault 0x0156 10343 E
PCM_CONVERTER_FAULT Input converter fault 0x0157 10344 E
PCM_INVERTER_FAULT, Output inverter fault 0x0158 10345 E
PCM_OVER_CURRENT_A_FAULT A Ø Peak Over current 0x0159 10346 E
PCM_OVER_CURRENT_B_FAULT B Ø Peak Over current 0x015A 10347 E
PCM_OVER_CURRENT_C_FAULT B Ø Peak Over current 0x015B 10348 E
PCM_BUS_OVER_VOLTAGE_FLT DC Bus overvoltage 0x015C 10349 E
RCB_COMM_ERROR Remote Converter Board Com. Failure 0x015D 10350 E
STATUS WORD 3 Power Conversion Module
PCM_TORQUE_ILIMIT Output Torque/Current Limit 0x015E 10351 E
NULL_POINT Reserved 0x015F 10352
DRIVE_STOPPED_MANUALLY Keypad / HOA switch Stop 0x0160 10353
TRIDENT_DIGITAL_IN1 Trident Onboard Digital Input #1 0x0161 10354 T
TRIDENT_DIGITAL_IN2 Trident Onboard Digital Input #2 0x0162 10355 T
http://slidepdf.com/reader/full/gcs-modbus-protocol-support-2v0 29/52
7/18/2019 GCS Modbus Protocol Support 2v0
http://slidepdf.com/reader/full/gcs-modbus-protocol-support-2v0 30/52
7/18/2019 GCS Modbus Protocol Support 2v0
http://slidepdf.com/reader/full/gcs-modbus-protocol-support-2v0 31/52
7/18/2019 GCS Modbus Protocol Support 2v0
http://slidepdf.com/reader/full/gcs-modbus-protocol-support-2v0 32/52
7/18/2019 GCS Modbus Protocol Support 2v0
http://slidepdf.com/reader/full/gcs-modbus-protocol-support-2v0 33/52
7/18/2019 GCS Modbus Protocol Support 2v0
http://slidepdf.com/reader/full/gcs-modbus-protocol-support-2v0 34/52
7/18/2019 GCS Modbus Protocol Support 2v0
http://slidepdf.com/reader/full/gcs-modbus-protocol-support-2v0 35/52
7/18/2019 GCS Modbus Protocol Support 2v0
IO1AI2_AVERAGE_SLOW
IO2AI1_AVERAGE_SLOW IO1
IO2 Analog
Analog input
input 2
1 “fast”
“fast” averaged
averaged signal
signal value
value 0x0146
0x0147 30327
30328 M
M
IO2AI2_AVERAGE_SLOW IO2 Analog input 2 “fast” averaged signal value 0x0148 30329 M
IO3AI1_AVERAGE_SLOW IO3 Analog input 1 “fast” averaged signal value 0x0149 30330 M
IO3AI2_AVERAGE_SLOW IO3 Analog input 2 “fast” averaged signal value 0x014A 30331 M
IO1AI1_RAW IO1 Analog input 1 raw A/D counts 0x014B 30332 M
IO1AI2_RAW IO1 Analog input 2 raw A/D counts 0x014C 30333 M
IO2AI1_RAW IO2 Analog input 1 raw A/D counts 0x014D 30334 M
IO2AI2_RAW IO2 Analog input 2 raw A/D counts 0x014E 30335 M
IO3AI1_RAW IO3 Analog input 1 raw A/D counts 0x014F 30336 M
IO3AI2_RAW IO3 Analog input 2 raw A/D counts 0x0150 30337 M
PACKED_DIGITALS1 Copy of first 16 digital inputs bit-packed 0x0151 30338
PACKED_DIGITALS2 Copy of second 16 digital inputs bit-packed 0x0152 30339
PACKED_DIGITALS3 Copy of third 16 digital inputs bit-packed 0x0153 30340
PCM_STATUS1 Copy of PCM Status word 1 0x0154 30341 E
PCM_STATUS2 Copy of PCM Status word 2 0x0155 30342 E
PCM_FAULT_WORD Copy of PCM Fault word 0x0156 30343 E
IO1AI1_RMS IO1 Analog in 1 RMS of AC input signal 0x0157 30344 M
IO1AI2_RMS IO1 Analog in 2 RMS of AC input signal 0x0158 30345 M
IO2AI1_RMS IO2 Analog in 1 RMS of AC input signal 0x0159 30346 M
IO2AI2_RMS IO2 Analog in 2 RMS of AC input signal 0x015A 30347 M
IO3AI1_RMS IO3 Analog in 1 RMS of AC input signal 0x015B 30348 M
IO3AI2_RMS IO3 Analog in 2 RMS of AC input signal 0x015C 30349 M
IO1AI1_MAXIMUM IO1 Analog in 1 Peak input signal 0x015D 30350 M
IO1AI2_MAXIMUM IO1 Analog in 2 Peak input signal 0x015E 30351 M
IO2AI1_MAXIMUM IO2 Analog in 1 Peak input signal 0x015F 30352 M
IO2AI2_MAXIMUM IO2 Analog in 2 Peak input signal 0x0160 30353 M
IO3AI1_MAXIMUM IO1 Analog in 1 Peak input signal 0x0161 30354 M
IO3AI2_MAXIMUM IO1 Analog in 2 Peak input signal 0x0162 30355 M
IO1AI1_MINIMUM IO1 Analog in 1 Lowest value of input signal 0x0163 30356 M
IO1AI2_MINIMUM IO1 Analog in 2 Lowest value of input signal 0x0164 30357 M
IO2AI1_MINIMUM IO2 Analog in 1 Lowest value of input signal 0x0165 30358 M
IO2AI2_MINIMUM IO2 Analog in 2 Lowest value of input signal 0x0166 30359 M
IO3AI1_MINIMUM IO1 Analog in 1 Lowest value of input signal 0x0167 30360 M
IO3AI2_MINIMUM IO1 Analog in 2 Lowest value of input signal 0x0168 30361 M
PCM_REVISION_NUMBER Power Conversion Module Software Revision 0x0169 30362 E
TRIDENT_PROG_REV_NUM Trident Module Software Revision 0x016A 30363 T
IO1_SOFTWARE_REVISION I/O Module #1 Software Revision 0x016B 30364 M
http://slidepdf.com/reader/full/gcs-modbus-protocol-support-2v0 36/52
7/18/2019 GCS Modbus Protocol Support 2v0
TRIDENT_MODEL_NUMBER
TRIDENT_XMIT1_CHAN1 Trident
Trident Down hole model
Transmitter number
1, Channel 1 data value 0x017D
0x017E 30382
30383 T
T
TRIDENT_XMIT1_CHAN2 Trident Transmitter 1, Channel 2 data value 0x017F 30384 T
TRIDENT_XMIT1_CHAN3 Trident Transmitter 1, Channel 3 data value, 0x0180 30385 T
TRIDENT_XMIT1_CHAN4 Trident Transmitter 1, Channel 4 data value 0x0181 30386 T
TRIDENT_XMIT1_CHAN5 Trident Transmitter 1, Channel 5 data value 0x0182 30387 T
TRIDENT_XMIT1_CHAN6 Trident Transmitter 1, Channel 6 data value 0x0183 30388 T
TRIDENT_XMIT1_CHAN7 Trident Transmitter 1, Channel 7 data value 0x0184 30389 T
TRIDENT_XMIT1_CHAN8 Trident Transmitter 1, Channel 8 data value 0x0185 30390 T
TRIDENT_XMIT2_CHAN1 Trident Transmitter 2, Channel 1 data value 0x0186 30391 T
TRIDENT_XMIT2_CHAN2 Trident Transmitter 2, Channel 2 data value 0x0187 30392 T
TRIDENT_XMIT2_CHAN3 Trident Transmitter 2, Channel 3 data value, 0x0188 30393 T
TRIDENT_XMIT2_CHAN4 Trident Transmitter 2, Channel 4 data value 0x0189 30394 T
TRIDENT_XMIT2_CHAN5 Trident Transmitter 2, Channel 5 data value 0x018A 30395 T
TRIDENT_XMIT2_CHAN6 Trident Transmitter 2, Channel 6 data value 0x018B 30396 T
TRIDENT_XMIT2_CHAN7 Trident Transmitter 2, Channel 7 data value 0x018C 30397 T
TRIDENT_XMIT2_CHAN8 Trident Transmitter 2, Channel 8 data value 0x018D 30398 T
TRIDENT_XMIT3_CHAN1 Trident Transmitter 3, Channel 1 data value 0x018E 30399 T
TRIDENT_XMIT3_CHAN2 Trident Transmitter 3, Channel 2 data value 0x018F 30400 T
TRIDENT_XMIT3_CHAN3 Trident Transmitter 3, Channel 3 data value, 0x0190 30401 T
TRIDENT_XMIT3_CHAN4 Trident Transmitter 3, Channel 4 data value 0x0191 30402 T
TRIDENT_XMIT3_CHAN5 Trident Transmitter 3, Channel 5 data value 0x0192 30403 T
TRIDENT_XMIT3_CHAN6 Trident Transmitter 3, Channel 6 data value 0x0193 30404 T
TRIDENT_XMIT3_CHAN7 Trident Transmitter 3, Channel 7 data value 0x0194 30405 T
TRIDENT_XMIT3_CHAN8 Trident Transmitter 3, Channel 8 data value 0x0195 30406 T
TRIDENT_XMIT4_CHAN1 Trident Transmitter 4, Channel 1 data value 0x0196 30407 T
TRIDENT_XMIT4_CHAN2 Trident Transmitter 4, Channel 2 data value 0x0197 30408 T
TRIDENT_XMIT4_CHAN3 Trident Transmitter 4, Channel 3 data value, 0x0198 30409 T
TRIDENT_XMIT4_CHAN4 Trident Transmitter 4, Channel 4 data value 0x0199 30410 T
TRIDENT_XMIT4_CHAN5 Trident Transmitter 4, Channel 5 data value 0x019A 30411 T
TRIDENT_XMIT4_CHAN6 Trident Transmitter 4, Channel 6 data value 0x019B 30412 T
TRIDENT_XMIT4_CHAN7 Trident Transmitter 4, Channel 7 data value 0x019C 30413 T
TRIDENT_XMIT4_CHAN8 Trident Transmitter 4, Channel 8 data value 0x019D 30414 T
TRIDENT_XMIT5_CHAN1 Trident Transmitter 5, Channel 1 data value 0x019E 30415 T
TRIDENT_XMIT5_CHAN2 Trident Transmitter 5, Channel 2 data value 0x019F 30416 T
TRIDENT_XMIT5_CHAN3 Trident Transmitter 5, Channel 3 data value, 0x01A0 30417 T
TRIDENT_XMIT5_CHAN4 Trident Transmitter 5, Channel 4 data value 0x01A1 30418 T
TRIDENT_XMIT5_CHAN5 Trident Transmitter 5, Channel 5 data value 0x01A2 30419 T
http://slidepdf.com/reader/full/gcs-modbus-protocol-support-2v0 37/52
7/18/2019 GCS Modbus Protocol Support 2v0
TRIDENT_XMIT7_CHAN7
TRIDENT_XMIT7_CHAN8 Trident
Trident Transmitter
Transmitter 7,
7, Channel
Channel 7
8 data
data value
value 0x01B4
0x01B5 30437
30438 T
T
TRIDENT_XMIT8_CHAN1 Trident Transmitter 8, Channel 1 data value 0x01B6 30439 T
TRIDENT_XMIT8_CHAN2 Trident Transmitter 8, Channel 2 data value 0x01B7 30440 T
TRIDENT_XMIT8_CHAN3 Trident Transmitter 8, Channel 3 data value, 0x01B8 30441 T
TRIDENT_XMIT8_CHAN4 Trident Transmitter 8, Channel 4 data value 0x01B9 30442 T
TRIDENT_XMIT8_CHAN5 Trident Transmitter 8, Channel 5 data value 0x01BA 30443 T
TRIDENT_XMIT8_CHAN6 Trident Transmitter 8, Channel 6 data value 0x01BB 30444 T
TRIDENT_XMIT8_CHAN7 Trident Transmitter 8, Channel 7 data value 0x01BC 30445 T
TRIDENT_XMIT8_CHAN8 Trident Transmitter 8, Channel 8 data value 0x01BD 30446 T
IO0AI1_AVERAGE_FAST RTU Analog input 1 fast signal average 0x01BE 30447 R
IO0AI1_AVERAGE_SLOW RTU Analog input 1 slow signal average 0x01BF 30448 R
IO0AI1_MAXIMUM RTU Analog input 1 maximum recorded signal 0x01C0 30449 R
IO0AI1_MINIMUM RTU Analog input 1 minimum recorded signal 0x01C1 30450 R
IO0AI1_RMS RTU Analog input 1 RMS of AC input signal 0x01C2 30451 R
IO0AI2_AVERAGE_FAST RTU Analog input 2 fast signal average 0x01C3 30452 R
IO0AI2_AVERAGE_SLOW RTU Analog input 2 slow signal average 0x01C4 30453 R
IO0AI2_MAXIMUM RTU Analog input 2 maximum recorded signal 0x01C5 30454 R
IO0AI2_MINIMUM RTU Analog input 2 minimum recorded signal 0x01C6 30455 R
IO0AI2_RMS RTU Analog input 2 RMS of AC input signal 0x01C7 30456 R
http://slidepdf.com/reader/full/gcs-modbus-protocol-support-2v0 38/52
7/18/2019 GCS Modbus Protocol Support 2v0
http://slidepdf.com/reader/full/gcs-modbus-protocol-support-2v0 39/52
7/18/2019 GCS Modbus Protocol Support 2v0
http://slidepdf.com/reader/full/gcs-modbus-protocol-support-2v0 40/52
7/18/2019 GCS Modbus Protocol Support 2v0
http://slidepdf.com/reader/full/gcs-modbus-protocol-support-2v0 41/52
7/18/2019 GCS Modbus Protocol Support 2v0
http://slidepdf.com/reader/full/gcs-modbus-protocol-support-2v0 42/52
7/18/2019 GCS Modbus Protocol Support 2v0
http://slidepdf.com/reader/full/gcs-modbus-protocol-support-2v0 43/52
7/18/2019 GCS Modbus Protocol Support 2v0
http://slidepdf.com/reader/full/gcs-modbus-protocol-support-2v0 44/52
7/18/2019 GCS Modbus Protocol Support 2v0
http://slidepdf.com/reader/full/gcs-modbus-protocol-support-2v0 45/52
7/18/2019 GCS Modbus Protocol Support 2v0
http://slidepdf.com/reader/full/gcs-modbus-protocol-support-2v0 46/52
7/18/2019 GCS Modbus Protocol Support 2v0
http://slidepdf.com/reader/full/gcs-modbus-protocol-support-2v0 47/52
7/18/2019 GCS Modbus Protocol Support 2v0
http://slidepdf.com/reader/full/gcs-modbus-protocol-support-2v0 48/52
7/18/2019 GCS Modbus Protocol Support 2v0
DESCRIPTION ACTIVE ALARM ID SHUTDOWN ID LOCKOUT ID
ANALOG1_HI_THLD_SD_ALARM 45 50 48
ANALOG1_LO_THLD_SD_ALARM 45 61 59
ANALOG2_HI_THLD_SD_ALARM 69 74 72
ANALOG2_LO_THLD_SD_ALARM 69 84 82
http://slidepdf.com/reader/full/gcs-modbus-protocol-support-2v0 49/52
7/18/2019 GCS Modbus Protocol Support 2v0
DESCRIPTION ACTIVE ALARM ID SHUTDOWN ID LOCKOUT ID
http://slidepdf.com/reader/full/gcs-modbus-protocol-support-2v0 50/52
7/18/2019 GCS Modbus Protocol Support 2v0
DESCRIPTION ACTIVE ALARM ID SHUTDOWN ID LOCKOUT ID
http://slidepdf.com/reader/full/gcs-modbus-protocol-support-2v0 51/52
7/18/2019 GCS Modbus Protocol Support 2v0
When a recordable event occurs on a GCS controller, the event identification returned via MODBUS will be
simply a number. The following table lists the descriptor associated with each number.
CITIBUS_NODE_LOSS 6
CITIBUS_NODE_RECOVERY 7
SYSTEM_CONTROLLER_IPL 8
FACTORY_DEFAULT_CHANGE
MINIMUM_CHANGE 9
10
MAXIMUM_CHANGE 11
BITFIELD_CHANGE 12
EXPONENT_CHANGE 13
UNITS_CHANGE 14
STAGE_CHANGE 15
PRIMARY_POWER_FAILURE 16
UNKNOWN_PCM_FAULT_CODE 17
REAL_TIME_CLOCK_CHANGE 18
SETPOINTS_RELOADED
CALLOUT_EVENT 19
20
REMOTE_WORMHOLE_CLOSED 21
FREQ_AVOID_TABLE_CHANGED 22
PID_CONTROLLER_TABLE_CHANGED 23
USER_PLC_BLOCK_CHANGED 24
USER_DATABASE_POINT_CHANGED 25
HARDWARE_RESET 26
http://slidepdf.com/reader/full/gcs-modbus-protocol-support-2v0 52/52