Académique Documents
Professionnel Documents
Culture Documents
Multilin
GE Multilin
215 Anderson Avenue, Markham, Ontario, Canada L6E 1B3
Tel: (905) 294-6222, 1-800-547-8629 (North America)
Fax: (905) 201-2098
GE Multilin's Quality Management
Internet: http://www.GEmultilin.com System is registered to
ISO9001:2000
QMI # 005094
*1601-9046-A4* UL # A3775
2010 GE Multilin Incorporated. All rights reserved.
GE Multilin 369 Motor Management Relay Communications Guide for revision
3.4x.
369 Motor Management Relay, is a registered trademark of GE Multilin Inc.
The contents of this manual are the property of GE Multilin Inc. This
documentation is furnished on license and may not be reproduced in whole or
in part without the permission of GE Multilin. The content of this manual is for
informational use only and is subject to change without notice.
Part numbers contained in this manual are subject to change without notice,
and should therefore be verified by GE Multilin before ordering.
Table of Contents
OVERVIEW .........................................................................................................................................1
ELECTRICAL INTERFACE .....................................................................................................1
PROFIBUS COMMUNICATIONS .........................................................................................2
DEVICENET COMMUNICATIONS .......................................................................................2
MODBUS COMMUNICATIONS ...........................................................................................2
MODBUS/TCP COMMUNICATIONS .................................................................................3
PROFIBUS-DP COMMUNICATIONS .........................................................................................6
PROFIBUS COMMUNICATION OPTIONS ..........................................................................6
369 RELAY PROFIBUS-DP PARAMETERIZATION ...........................................................6
369 RELAY PROFIBUS-DP CONFIGURATION ................................................................6
369 RELAY PROFIBUS-DP DIAGNOSTICS ..................................................................11
PROFIBUS-DP LOSS OF COMMUNICATION TRIP .......................................................18
PROFIBUS-DPV1 COMMUNICATIONS ................................................................................19
369 RELAY PROFIBUS-DPV1 PARAMETERIZATION ..................................................19
369 RELAY PROFIBUS CONFIGURATION .....................................................................19
369 RELAY PROFIBUS INPUT DATA ............................................................................20
369 RELAY PROFIBUS OUTPUT DATA ........................................................................21
369 RELAY PROFIBUS DIAGNOSTICS ..........................................................................22
369 RELAY PROFIBUS-DPV1 ACYCLICAL COMMUNICATION ..................................22
369 RELAY PROFIBUS-DPV1 LOSS OF COMMUNICATION TRIP ............................23
DEVICENET PROTOCOL ............................................................................................................ 24
DEVICENET COMMUNICATIONS ....................................................................................24
POLL DATA ......................................................................................................................25
CHANGE OF STATE (COS) .............................................................................................27
IDENTITY OBJECT (CLASS CODE 01H) ..........................................................................28
MESSAGE ROUTER (CLASS CODE 02H) ........................................................................28
DEVICENET OBJECT (CLASS CODE 03H) .....................................................................28
ASSEMBLY OBJECT (CLASS CODE 04H) .......................................................................29
DEVICENET CONNECTION OBJECT (CLASS CODE 05H) ............................................31
ACKNOWLEDGE HANDLER OBJECT (CLASS CODE 2BH) ...........................................32
I/O DATA INPUT MAPPING OBJECT (CLASS CODE A0H) ..........................................32
I/O DATA OUTPUT MAPPING OBJECT (CLASS CODE A1H) ......................................33
PARAMETER DATA INPUT MAPPING OBJECT (CLASS CODE B0H) ............................33
DEVICENET LOSS OF COMMUNICATION TRIP ............................................................41
DEVICENET DATA FORMATS .........................................................................................42
MODBUS RTU PROTOCOL .......................................................................................................46
DATA FRAME FORMAT AND DATA RATE .....................................................................46
DATA PACKET FORMAT ..................................................................................................46
ERROR CHECKING ..........................................................................................................47
CRC-16 ALGORITHM ....................................................................................................47
TIMING .............................................................................................................................48
SUPPORTED MODBUS FUNCTIONS ..............................................................................48
ERROR RESPONSES ........................................................................................................48
MODBUS COMMANDS ...................................................................................................49
MEMORY MAP ...............................................................................................................................51
MEMORY MAP INFORMATION .......................................................................................51
USER DEFINABLE MEMORY MAP AREA .......................................................................51
EVENT RECORDER ..........................................................................................................52
WAVEFORM CAPTURE ....................................................................................................52
Communications Guide
Communications Guide
1 Overview
RS232 port. Modbus is a single master, multiple slave protocol suitable for a multi-drop
configuration as provided by RS485 hardware. In this configuration up to 32 slaves can be
daisy-chained together on a single communication channel.
The 369 is always a slave. It cannot be programmed as a master. Computers or PLCs are
commonly programmed as masters. The Modbus protocol exists in two versions: Remote
Terminal Unit (RTU, binary) and ASCII. Only the RTU version is supported by the 369.
Monitoring, programming and control functions are possible using read and write register
commands.
Modbus/TCP Option:
When configured with the E Option, the 369 can connect to Ethernet networks via the
rear RJ45 connection, using the Modbus/TCP protocol as detailed in the document Open
Modbus / TCP Specification by Andy Swales, Release 1.0, 29 March 1999 (a search via the
internet can produce a free copy of this document).
This description contains information to the location of Setting registers for configuring the
369 for a LAN connection, and the physical connection of the 369. Information pertaining
to the application of an IED over Ethernet is beyond the scope of this manual and users
should consult their Network Administrators for configuration details.
The implementation of this option is for the intention of data retrieval and device
Note
configuration. The 369 does not support firmware upgrade via this connection.
Setpoints Configuration:
The user needs to configure the following settings for interface to a LAN: IP ADDRESS,
SUBNET MASK , and GATEWAY ADDRESS. Each setting contains 4 octets. The user
configures the octets as shown in the following example:
IP ADDRESS: 127.0.0.1
SUBNET MASK: 255.255.255.252
GATEWAY ADDRESS: 127.0.0.1
These settings can also be configured via the keypad under the S1 369 SETUP 369
COMMUNICATIONS path.
Physical Connection:
The 369 can be connected to an Ethernet LAN via the RJ45 connector at the back of the
369.
If programmed as Latched:
The Fieldbus Loss of Comms trip will remain latched until the communication with the
Modbus Master through Ethernet port is (re) established AND the latched trip is manually
reset or remotely reset via Modbus communications.
If programmed as Unlatched:
Any programmed output relays for this feature will be activated until communication with
the Modbus master through Ethernet port is active. Once communication is active, the trip
condition will be cleared and the assigned output relays will automatically de-activate.
The setpoints associated with this feature are:
1. Fieldbus Loss of Comms Enable
2. Fieldbus Loss of Comms Delay
2 Profibus-DP Communications
OFFSET CYCLIC DATA LENGTH MINIMUM MAXIMUM STEP UNITS FORMAT DEFAULT
(ACTUAL VALUES) (BYTES) VALUE CODE
VALUE HEX VALUE HEX
OFFSET CYCLIC DATA LENGTH MINIMUM MAXIMUM STEP UNITS FORMAT DEFAULT
(ACTUAL VALUES) (BYTES) VALUE CODE
VALUE HEX VALUE HEX
OFFSET CYCLIC DATA LENGTH MINIMUM MAXIMUM STEP UNITS FORMAT DEFAULT
(ACTUAL VALUES) (BYTES) VALUE CODE
VALUE HEX VALUE HEX
OFFSET CYCLIC DATA LENGTH MINIMUM MAXIMUM STEP UNITS FORMAT DEFAULT
(ACTUAL VALUES) (BYTES) VALUE CODE
VALUE HEX VALUE HEX
174 Last trip Date 4 N/A N/A N/A N/A N/A N/A F18 N/A
178 Last trip Time 4 N/A N/A N/A N/A N/A N/A F19 N/A
OFFSET CYCLIC DATA LENGTH MINIMUM MAXIMUM STEP UNITS FORMAT DEFAULT
(ACTUAL VALUES) (BYTES) VALUE CODE
VALUE HEX VALUE HEX
BYTE DESCRIPTION
1 Station Status 1
2 Station Status 2
3 Station Status 3
The extended diagnosis for the relay is composed of 26 bytes (bytes 7 to 32) and contains
diagnostic information according to the following table.
0 8 SinglePhasingTrip
1 8 SpareSwitchTrip
2 8 EmergencySwitchTrip
3 8 DifferentialSwitchTrip
4 8 SpeedSwitchTrip
5 8 ResetSwitchTrip
6 8 Reserved
7 8 OverloadTrip
8 9 ShortCircuitTrip
9 9 ShortCircuitBackupTrip
10 9 MechanicalJamTrip
11 9 UndercurrentTrip
12 9 CurrentUnbalanceTrip
13 9 GroundFaultTrip
14 9 GroundFaultBackupTrip
15 9 Reserved
16 10 AccelerationTimerTrip
17 10 Rtd1Trip
18 10 Rtd2Trip
19 10 Rtd3Trip
20 10 Rtd4Trip
21 10 Rtd5Trip
22 10 Rtd6Trip
23 10 Rtd7Trip
24 11 Rtd8Trip
25 11 Rtd9Trip
26 11 Rtd10Trip
27 11 Rtd11Trip
28 11 Rtd12Trip
29 11 UnderVoltageTrip
30 11 OverVoltageTrip
31 11 VoltagePhaseReversalTrip
32 12 UnderfrequencyTrip
33 12 OverfrequencyTrip
34 12 LeadPowerFactorTrip
35 12 LagPowerFactorTrip
36 12 PositivekvarTrip
37 12 NegativekvarTrip
38 12 UnderpowerTrip
39 12 ReversePowerTrip
40 13 IncompleteSequenceTrip
41 13 SpareSwitchAlarm
42 13 EmergencySwitchAlarm
43 13 DifferentialSwitchAlarm
44 13 SpeedSwitchAlarm
45 13 ResetSwitchAlarm
46 13 Reserved
47 13 ThermalCapacityAlarm
48 14 OverloadAlarm
49 14 MechanicalJamAlarm
50 14 UndercurrentAlarm
51 14 CurrentUnbalanceAlarm
52 14 GroundFaultAlarm
53 14 UndervoltageAlarm
54 14 OvervoltageAlarm
55 14 OverfrequencyAlarm
56 15 UnderfrequencyAlarm
57 15 LeadPowerFactorAlarm
58 15 LagPowerFactorAlarm
59 15 PositivekvarAlarm
60 15 NegativekvarAlarm
61 15 UnderpowerAlarm
62 15 ReversePowerAlarm
63 15 Rtd1Alarm
64 16 Rtd2Alarm
65 16 Rtd3Alarm
66 16 Rtd4Alarm
67 16 Rtd5Alarm
68 16 Rtd6Alarm
69 16 Rtd7Alarm
70 16 Rtd8Alarm
71 16 Rtd9Alarm
72 17 Rtd10Alarm
73 17 Rtd11Alarm
74 17 Rtd12Alarm
75 17 Rtd1HighAlarm
76 17 Rtd2HighAlarm
77 17 Rtd3HighAlarm
78 17 Rtd4HighAlarm
79 17 Rtd5HighAlarm
80 18 Rtd6HighAlarm
81 18 Rtd7HighAlarm
82 18 Rtd8HighAlarm
83 18 Rtd9HighAlarm
84 18 Rtd10HighAlarm
85 18 Rtd11HighAlarm
86 18 Rtd12HighAlarm
87 18 OpenRTDSensorAlarm
88 19 ShortRTDAlarm
89 19 TripCountersAlarm
90 19 StarterFailureAlarm
91 19 CurrentDemandAlarm
92 19 KWDemandAlarm
93 19 KVARDemandAlarm
94 19 KVADemandAlarm
95 19 DigitalCounterAlarm
96 20 OverloadLockoutBlock
97 20 StartInhibitBlock
98 20 StartsHourBlock
99 20 TimeBetweenStartsBlock
100 20 RestartBlock
101 20 Reserved
102 20 BackSpinBlock
103 20 LossofRemoteRTDCommunication
104 21 RemoteRTD1Rtd1Trip
105 21 RemoteRTD1Rtd2Trip
106 21 RemoteRTD1Rtd3Trip
107 21 RemoteRTD1Rtd4Trip
108 21 RemoteRTD1Rtd5Trip
109 21 RemoteRTD1Rtd6Trip
110 21 RemoteRTD1Rtd7Trip
111 21 RemoteRTD1Rtd8Trip
112 22 RemoteRTD1Rtd9Trip
113 22 RemoteRTD1Rtd10Trip
114 22 RemoteRTD1Rtd11Trip
115 22 RemoteRTD1Rtd12Trip
116 22 RemoteRTD2Rtd1Trip
117 22 RemoteRTD2Rtd2Trip
118 22 RemoteRTD2Rtd3Trip
119 22 RemoteRTD2Rtd4Trip
120 23 RemoteRTD2Rtd5Trip
121 23 RemoteRTD2Rtd6Trip
122 23 RemoteRTD2Rtd7Trip
123 23 RemoteRTD2Rtd8Trip
124 23 RemoteRTD2Rtd9Trip
125 23 RemoteRTD2Rtd10Trip
126 23 RemoteRTD2Rtd11Trip
127 23 RemoteRTD2Rtd12Trip
128 24 RemoteRTD3Rtd1Trip
129 24 RemoteRTD3Rtd2Trip
130 24 RemoteRTD3Rtd3Trip
131 24 RemoteRTD3Rtd4Trip
132 24 RemoteRTD3Rtd5Trip
133 24 RemoteRTD3Rtd6Trip
134 24 RemoteRTD3Rtd7Trip
135 24 RemoteRTD3Rtd8Trip
136 25 RemoteRTD3Rtd9Trip
137 25 RemoteRTD3Rtd10Trip
138 25 RemoteRTD3Rtd11Trip
139 25 RemoteRTD3Rtd12Trip
140 25 RemoteRTD4Rtd1Trip
141 25 RemoteRTD4Rtd2Trip
142 25 RemoteRTD4Rtd3Trip
143 25 RemoteRTD4Rtd4Trip
144 26 RemoteRTD4Rtd5Trip
145 26 RemoteRTD4Rtd6Trip
146 26 RemoteRTD4Rtd7Trip
147 26 RemoteRTD4Rtd8Trip
148 26 RemoteRTD4Rtd9Trip
149 26 RemoteRTD4Rtd10Trip
150 26 RemoteRTD4Rtd11Trip
151 26 RemoteRTD4Rtd12Trip
152 27 RemoteRTD1Rtd1Alarm
153 27 RemoteRTD1Rtd2Alarm
154 27 RemoteRTD1Rtd3Alarm
155 27 RemoteRTD1Rtd4Alarm
156 27 RemoteRTD1Rtd5Alarm
157 27 RemoteRTD1Rtd6Alarm
158 27 RemoteRTD1Rtd7Alarm
159 27 RemoteRTD1Rtd8Alarm
160 28 RemoteRTD1Rtd9Alarm
161 28 RemoteRTD1Rtd10Alarm
162 28 RemoteRTD1Rtd11Alarm
163 28 RemoteRTD1Rtd12Alarm
164 28 RemoteRTD2Rtd1Alarm
165 28 RemoteRTD2Rtd2Alarm
166 28 RemoteRTD2Rtd3Alarm
167 28 RemoteRTD2Rtd4Alarm
168 29 RemoteRTD2Rtd5Alarm
169 29 RemoteRTD2Rtd6Alarm
170 29 RemoteRTD2Rtd7Alarm
171 29 RemoteRTD2Rtd8Alarm
172 29 RemoteRTD2Rtd9Alarm
173 29 RemoteRTD2Rtd10Alarm
174 29 RemoteRTD2Rtd11Alarm
175 29 RemoteRTD2Rtd12Alarm
176 30 RemoteRTD3Rtd1Alarm
177 30 RemoteRTD3Rtd2Alarm
178 30 RemoteRTD3Rtd3Alarm
179 30 RemoteRTD3Rtd4Alarm
180 30 RemoteRTD3Rtd5Alarm
181 30 RemoteRTD3Rtd6Alarm
182 30 RemoteRTD3Rtd7Alarm
183 30 RemoteRTD3Rtd8Alarm
184 31 RemoteRTD3Rtd9Alarm
185 31 RemoteRTD3Rtd10Alarm
186 31 RemoteRTD3Rtd11Alarm
187 31 RemoteRTD3Rtd12Alarm
188 31 RemoteRTD4Rtd1Alarm
189 31 RemoteRTD4Rtd2Alarm
190 31 RemoteRTD4Rtd3Alarm
191 31 RemoteRTD4Rtd4Alarm
192 32 RemoteRTD4Rtd5Alarm
193 32 RemoteRTD4Rtd6Alarm
194 32 RemoteRTD4Rtd7Alarm
195 32 RemoteRTD4Rtd8Alarm
196 32 RemoteRTD4Rtd9Alarm
197 32 RemoteRTD4Rtd10Alarm
198 32 RemoteRTD4Rtd11Alarm
199 32 RemoteRTD4Rtd12Alarm
If programmed as Latched:
The Fieldbus Loss of Comms output relay will remain latched until communication with
the Master is (re) established AND the latched output relay is manually reset or remotely
reset via Modbus communications.
If programmed as Unlatched:
Any output relays programmed for this feature will be de-activated once communication is
restored; the Loss of Communication condition will be cleared and the assigned output
relays will automatically de-activate.
The setpoints associated with this feature are:
1. Fieldbus Loss of Comms Enable
2. Fieldbus Loss of Comms Delay
3. Assigned Fieldbus Loss of Comms Relay
Refer to the 369 Instruction Manual, chapter 5: 369 Relay Communications for more
information on these setpoints.
3 Profibus-DPV1 Communications
The Profibus media is a twisted-pair copper cable along with 9-pin Sub-D connector, which
connects the bus to the 369 Relay socket on the back of the relay. The 369 Motor
Management Relay has autobaud support. The baud rates and other slave specific
information needed for configuration are contained in the 369_09E6.gse file, which is used
by a network configuration program.
The 369 Motor Management Relay as a DPV1 slave transfers fast process data to the DP/
V1 master according to master-slave principle. The 369 Relay is a modular device,
supporting up to 111 input modules.
Modules define a block size of input data to be read by the master, starting from offset
zero. Adding modules in your Master configuration increases the size of the total block of
data that the Master will read, making it easy to choose a total block size of data that
matches the user's requirements.
A slave configuration example for 4 bytes of input data and 2 bytes of output data is
shown below.
FIGURE CG5: Slave Configuration Example 4 Bytes of Input Data, 2 bytes of Output Data
2. Index number
The value that is written acyclically to either FORCE OUTPUT RELAYS or BLOCK
Note
PROTECTION FUNCTIONS must be a 16-bit value. The lower byte contains the bitmask
data (as per format codes noted) and the upper byte written must always contain a value
of zero.
Refer to the 369 Instruction Manual, chapter 5 for additional information about the force
output relays feature. Refer to the 369 Instruction Manual, chapter 5.3.4 for additional
information about the protection function blocking feature.
Functions Currently
8 2 bytes F141
Blocked
4 DeviceNet Protocol
CLASS Object
01h Identity
03h DeviceNet
04h Assembly
05h Connection
communication after recovery of critical link faliure, the 369 Fieldbus comms interface
must be reset. This can be done without recycling the control power to the 369 by using
"RESET FIELDBUS COMMS INTERFACE" command under setting S1 369 SETUP\369
COMMUNICATIONS\ . Refer to section 5.2.3 for more details.
A delay of 0.25 sec to 10.00 sec in steps of 0.25 sec can be programmed to delay the
output relay activation.
This feature can be programmed for Latched or Unlatched operation.
If programmed as Latched:
The DeviceNet Loss of Comms trip will remain latched until the communication with the
Master is (re) established AND the latched trip is manually reset or remotely reset via
Modbus communications.
If programmed as Unlatched:
Any programmed output relays for this feature will be activated until communication is
active. Once communication is active, the trip condition will be cleared and the assigned
output relays will automatically de-activate.
The setpoints associated with this feature are:
1. Fieldbus Loss of Comms Enable
2. Fieldbus Loss of Comms Delay
3. Assign Loss of Comms Relay
Refer to the 369 Instruction Manual, chapter 5: 369 Relay Communications for more
information on these setpoints.
3 Reserved -
4 Reserved -
5 Reserved -
6 Reserved -
7 Reserved -
For execution of DeviceNet control commands, one of the switch assignments should be
set to DeviceNet Control and be closed.
The motor start command energizes the output relay set with the START CONTROL RELAY
setpoint. The motor stop command energizes the trip relay. The fault reset command
resets the latched trip and alarm conditions, provided the cause of alarm/trip is removed.
The commands are executed continuously as long as the control bits are high. When two
or more commands are executed simultaneously, only one will be executed. The command
hierarchy for execution is given below.
1. Motor stop
2. Fault reset
3. Motor start
The corresponding command bit should be high for more than 500 ms to execute the
Note
command.
The Polled input bytes can be selected from two predefined groups of parameters or one
group of user-defined parameters with the DeviceNet Input Poll Data Group setpoint. The
list of parameters in each group is given below:
Note that the Explicit message data provided both via Class 04, Instance 64h, Attribute 03
and Class A0h, Instance 01, Attribute 01 will match the the Poll data configuration.
The USINT and UINT data types are defined as follows: USINT = Unsigned integer byte
(range 0 to 255); UINT = Unsigned integer word (range 0 to 65535).
The USINT and UINT data types are defined as follows: USINT = Unsigned integer byte
(range 0 to 255); UINT = Unsigned integer word (range 0 to 65535).
For execution of DeviceNet control commands, one of the switch assignments should be
set to DeviceNet Control and be closed.
The motor start command energizes the output relay set with the START CONTROL
RELAY setpoint. The motor stop command energizes the trip relay. The fault reset
command resets the latched trip and alarm conditions, provided the cause of alarm/trip is
removed. The commands are executed continuously as long as the control bits are high.
When two or more commands are executed simultaneously, only one will be executed. The
command hierarchy for execution is given below.
1. Motor stop
2. Fault reset
3. Motor start
The corresponding command bit should be high for more than 500 ms to execute the
command.
Connection Object, Class Code 05h, Instance 01h (explicit message connection):
ATTRIBUTE ACCESS NAME/DESCRIPTION DATA VALUE
TYPE
01h Get State BYTE 0x03
02h Get Instance_type BYTE 0x00, 0x01
03h Get Export class trigger BYTE 0x83
10xxxxxx011, xxxxxx =
04h Get Produced connection ID UINT MAC ID
10xxxxxx011, xxxxxx =
05h Get Consumed connection ID UINT MAC ID
Initial comm.
06h Get UINT 0x21
characteristics
07h Get Produced connection size UINT 0x12
Consumed connection
08h Get UINT 0x12
size
09h Get/Set Expected package rate UINT 0x00
0 = transition to time-out
1 = auto delete, 2 = auto
0Ch Get/Set Watchdog timeout action USINT reset
3 = deferred delete
0Dh Get Produced path length UINT 0x0000
0Eh Get Produced path BYTE [6] <null>
0Fh Get Consumed path length UINT 0x0000
10h Get Consumed path BYTE [6] <null>
11h Get Production inhibit timer UINT 0x0000
Connection Object, Class Code 05h, Instance 02h (polled input/output connection):
ATTRIBUTE ACCESS NAME/DESCRIPTION DATA TYPE VALUE
01h Get State BYTE 0x03
02h Get Instance_type BYTE 0x01
03h Get Export class trigger BYTE 0x80, 0x82
04h Get Produced connection ID UINT MAC ID
05h Get Consumed connection ID UINT MAC ID
06h Get Initial comm. characteristics UINT 0x01, 0xF1
07h Get Produced connection size UINT 0x01
08h Get Consumed connection size UINT 0x01
09h Get/Set Expected package rate UINT 0x00
0Ch Get/Set Watchdog timeout action UINT 0x00
I/O Data Input Mapping object, Class code A0h, Instance 01h, Attributes:
ATTRIBUTE ACCESS NAME/DESCRIPTION DATA TYPE DATA FORMAT
01h Get Motor data1 bytes (7) see below
02h Get Flag change state byte F175
03h Get Digital data bytes (4) see below
04h Get Thermal capacity used USINT %
05h Get Time to trip Word F20
1. The data available through this Class/Instance/Attribute will depend on which Poll Group is used
(see section 4.2: Poll Data)
I/O Data Input Mapping object, Class code A0h, Instance 01h, Attributes:
ATTRIBUTE ACCESS NAME/DESCRIPTION DATA TYPE DATA FORMAT
01h Set Control byte 1 byte see below
Parameter Data Input Mapping object, Class code B0h, Instance 01h, Attributes:
ATTRIBUTE ACCESS NAME/DESCRIPTION DATA TYPE VALUE
01h Get Currents bytes (10) see below
02h Get Current angles bytes (6) see below
03h Get Motor load bytes (6) see below
04h Get Line voltages bytes (8) see below
05h Get Phase voltages bytes (8) see below
Learned starting
3,4 (low, high) 16 bits UINT A
current
Learned starting
5,6 (low, high) 16 bits UINT %
capacity
0Fh Learned running cool
LEARNED 7,8 (low, high) time constant 16 bits UINT minutes
DATA
Learned stopped
9,10 (low, high) 16 bits UINT minutes
cool time constant
Last starting
11,12 (low, high) 16 bits UINT %
capacity
Learned unbalance
13,14 (low, high) 16 bits UINT --
k-factor
1,2 (low, high) Number of starts 16 bits UINT --
10h 3,4 (low, high) Number of restarts 16 bits UINT --
MOTOR
STATISTICS 5,6 (low, high) Digital counter 16 bits UINT --
7,8 (low, high) Motor running hours 16 bits UINT hours
11h
CAUSE OF 1,2 (low, high) Cause of last trip 16 bits F134 --
LAST TRIP
12h 1 to 4(low, high) Last trip date 32 bits F18 --
LAST PRE-
TRIP DATE 5 to 8(low, high) Last trip time 32 bits F19 --
AND TIME.
1,2 (low, high) Last pre-trip Ia 16 bits UINT A
13h
LAST PRE- 3,4 (low, high) Last pre-trip Ib 16 bits UINT A
TRIP 5,6 (low, high) Last pre-trip Ic 16 bits UINT A
CURRENTS
7,8 (low, high) Last pre-trip Ig 16 bits F2 0.1 A
14h Last pre-trip motor
1,2 (low, high) 16 bits F3 0.01 FLA
LAST PRE- load
TRIP MOTOR Last pre-trip
LOAD 3,4 (low, high) 16 bits UINT %
unbalance
Local pre-trip hottest
15h 1,2 (low, high) 16 bits UINT ---
stator RTD
PRE-TRIP
STATOR RTD Local pre-trip hottest
TEMP. 3,4 (low, high) stator RTD 16 bits F4 C
temperature
If programmed as Latched:
The Fieldbus Loss of Comms output relay will remain latched until communication with
the Master is (re) established AND the latched output relay is manually reset or remotely
reset via Modbus communications.
If programmed as Unlatched:
Any output relays programmed for this feature will be de-activated once communication is
restored; the Loss of Communications condition will be cleared and the assigned output
relays will automatically de-activate.
The setpoints associated with this feature are:
1. Fieldbus Loss of Comms Enable
2. Fieldbus Loss of Comms Delay
3. Assigned Fieldbus Loss of Comms Relay
Refer to the 369 Instruction Manual, Chapter 5: 369 Relay Communications for more
information on these setpoints.
DATA: This will be a variable number of bytes depending on the FUNCTION CODE. This may
be actual values, setpoints, or addresses sent by the master to the slave or by the slave to
the master. Data is sent MSByte first followed by the LSByte.
CRC: This is a two byte error checking code. CRC is sent LSByte first followed by the
MSByte.
2. 0 --> i
3. 0 --> j
4. Di (+) AL --> AL
5. j+1 --> j
6. shr(A)
7. is there a carry? No: go to 8.
Yes: G (+) A --> A
8. is j = 8? No: go to 5.
Yes: go to 9.
9. i+1 --> i
10. is i = N? No: go to 3.
Yes: go to 11.
11. A --> CRC
5.5 Timing
Data packet synchronization is maintained by timing constraints. The receiving device
must measure the time between the reception of characters. If three and one half
character times elapse without a new character or completion of the packet, then the
communication link must be reset (i.e. all slaves start listening for a new transmission from
the master). Thus at 9600 baud a delay of greater than 3.5 1 / 9600 10 = 3.65 ms will
cause the communication link to be reset.
When this command is sent to the 369, the protection function blocking setpoints
(Modbus addresses 1520 to 1528) are updated accordingly. For example, for Bit 0 in
the 2nd data word, the setpoint value for Block Undercurrent/Underpower at address
1521 will be modified to contain either a 1 or 0, depending on the bit value.
Refer to the 369 Instruction Manual, chapter 5: Block Functions for additional
information about the protection function blocking feature.
Command 21 (Force Output Relays): Modbus Command 20 must be sent using
Modbus function code 10h (Store Multiple Setpoints). This allows the 369 to accept the
two required 16-bit values in one transmission. The first data word is the command
number (21). The 2nd data word contains the bitmask information for which relays to
energize/de-energize as per format code F141.
The purpose of this command is to allow the control of the output relay status,
regardless of the motor status (running, stopped, etc.). Only relays that have been
programmed under the ASSIGN COMMS FORCE RELAYS setpoint can be forced
using this command.
Refer to the 369 Instruction Manual, chapter 5: Force Output Relays for more
information about the force output relays feature.
Command 24 (Clear Data Logger Data): This command will clear all the existing data
presently available in the Data Logger feature. Please refer to the 369 Instruction
Manual, chapter 6: Data Logger and 6.6: Data Logger for more information on the Data
Logger feature.
6 Memory Map
Many Modbus communications drivers add 40001d to the actual address of the
Note
register addresses. For example: if address 0h was to be read, 40001d would be the
address required by the Modbus communications driver; if address 320h (800d) was to
be read, 40801d would be the address required by the Modbus communications driver.
True RMS values of the Phase A-N, B-N, and C-N voltages (Van, Vbn, and Vcn) if VT
CONNECTION TYPE is set to Wye.
True RMS values of the Phase A-B, B-C and C-A voltages (Vab, Vbc, and Vca) if VT
CONNECTION TYPE is set to Delta.
Thermal Capacity Used (%).
Frequency.
Breaker/Contactor Contact Input Status
Motor Speed (low/high).
1 second of pre-trigger data and 29 seconds of post-trigger data are recorded. The data
logger ignores all subsequent triggers and continues to record data until the active record
is finished.
A total of 6 logs are stored in the relay. Log #1 is the baseline log, it is written only by the
first start after clearing the MOTOR START DATA LOGGER (see the 369 Instruction
Manual, chapter 5: Clear/Preset Data). Logs #2 to 6 are rolling buffers of the last 5 motor
starts. Each new log automatically shifts the rolling buffer and overwrites the oldest log,
#2.
Log files are formatted using CSV (comma delimited values). The files can be downloaded
and displayed via EnerVista 369 Setup software. All files are stored in non-volatile memory;
information is retained when power to the relay is lost.
Total Logs Presently Used: This value indicates the total number of Logs that have
been captured and are presently available in the 369.
Total Records Presently Used: This is the number of records that have been written
into the Data Log and are presently available in the 369.
Log Status: This reports the current status of the Data Logger (Running or Stopped).
Log Time Remaining Until Next Reading: This is a counter showing how much time
remains until the next record is to be written into the Data Log (1~3600s).
Data Logger Percentage Full: Indicates what percentage of the total available
memory is used.
Pointer To Next Record To Write: This value points to the internal data address of the
location of the next record to be written.
Pointer To Log (1-50) Starting Address : This value points to the internal data address
of the location of each of the potential 50 records.
Log (1-50) Number of Records: This value provides the number of records that each of
the 50 potential Logs contain.
Log (1-50) Start/Stop Method: This value is used to indicate the method by which each
log was started and stopped. If the bit value for the Start is zero, it was started by a
motor start event. Refer to Modbus format code F191 for more information on the
format of this data.
UNSIGNED VALUE
F1 16 bits Example: 1234 stored as 1234
DATE (MM/DD/YYYY)
F18 32 bits Example: Feb. 20, 1995 stored as 34867142 (i.e. 1st word:
0214, 2nd word 07C6)
TIME (HH:MM:SS:hh)
F19 32 bits Example: 2:05pm stored as 235208704 (i.e. 1st word: 0E05,
2nd word 0000)
0 0 - 1mA
1 0 - 20 mA
2 4 - 20 mA
0 Motor Running
1 No Backspin
2 Slowdown
3 Acceleration
4 ---
5 Backspinning
6 Prediction
7 Soon to Restart
0 Disabled
1 Enabled
0 Not in use
1 Reset 369
2 Motor Start
3 Motor Stop
4 Waveform Trigger
5 Reserved
8 Reserved
9 Reserved
0 None
1 Manual
2 Automatic
0 Celsius
1 Fahrenheit
0 1200 baud
1 2400 baud
2 4800 baud
3 9600 baud
4 19200 baud
0 None
1 Odd
2 Even
0 Off / No
1 On / Yes
0 None
1 1 A Secondary
2 5 A Secondary
3 Multilin CT 50/0.025
0 None
1 1 A Secondary
2 5 A Secondary
0 None
1 Open Delta
2 Wye
0 60 Hz
1 50 Hz
2 Variable
0 Current Only
1 Current or Timer
0 Off
1 Emergency Switch
2 General Switch
3 Digital Counter
4 Waveform Capture
5 DeviceNet Control
6 Speed Switch1
7 Reserved
0 none
1 Trip
2 Aux1
3 Aux2
0 None
1 Alarm
2 Aux1
3 Aux2
0 Increment
1 Decrement
0 Off
1 Latched
2 Unlatched
0 Normally Open
1 Normally Closed
0 All Resets
0 None
1 Aux 1
3 Aux2
3 10 Ohm Copper
0 None
1 Stator
2 Bearing
3 Ambient
4 Other
0 Off
1 RTD #1
2 RTD #2
3 RTD #3
4 RTD #4
5 RTD #5
6 RTD #6
7 RTD #7
8 RTD #8
9 RTD #9
10 RTD #10
11 RTD #11
12 RTD #12
13 All Stator
0 Off
1 Not Active
2 Timing Out
3 Active
4 Latched
0 ABC
1 ACB
0 Breaker
1 Contactor
0 Phase A Current
1 Phase B Current
2 Phase C Current
4 AB Line Voltage
5 BC Line Voltage
6 CA Line Voltage
8 Phase AN Voltage
9 Phase BN Voltage
10 Phase CN Voltage
13 Local RTD #1
14 Local RTD #2
15 Local RTD #3
16 Local RTD #4
17 Local RTD #5
18 Local RTD #6
19 Local RTD #7
20 Local RTD #8
21 Local RTD #9
25 Power Factor
31 Reserved
32 Reserved
33 Reserved
34 Reserved
35 Motor Load
36 MWhrs
0 Standard
1 Custom
0 Over
1 Under
0 Open
1 Closed
0 Stopped
1 Starting
2 Running
3 Overloaded
4 Tripped
0 No Event
4 Reserved
7 Unexpected Reset
8 EEPROM Memory
11 Overload Trip
15 Undercurrent Trip
20 Overload Block
25 Restart Block
26 Backspin Block
28 Undervoltage Trip
29 Overvoltage Trip
31 Underfrequency Trip
32 Overfrequency Trip
37 Underpower Trip
39 RTD1 Trip
40 RTD2 Trip
41 RTD3 Trip
42 RTD4 Trip
43 RTD5 Trip
44 RTD6 Trip
45 RTD7 Trip
46 RTD8 Trip
47 RTD9 Trip
48 RTD10 Trip
49 RTD11 Trip
50 RTD12 Trip
51 Reserved
52 Reserved
58 Reserved
60 Overload Alarm
62 Undercurrent Alarm
65 Undervoltage Alarm
66 Overvoltage Alarm
67 Overfrequency Alarm
68 Underfrequency Alarm
73 Underpower Alarm
75 RTD1 Alarm
76 RTD2 Alarm
77 RTD3 Alarm
78 RTD4 Alarm
79 RTD5 Alarm
80 RTD6 Alarm
81 RTD7 Alarm
82 RTD8 Alarm
83 RTD9 Alarm
84 RTD10 Alarm
85 RTD11 Alarm
86 RTD12 Alarm
87 RTD1 Hi Alarm
88 RTD2 Hi Alarm
89 RTD3 Hi Alarm
90 RTD4 Hi Alarm
91 RTD5 Hi Alarm
92 RTD6 Hi Alarm
93 RTD7 Hi Alarm
94 RTD8 Hi Alarm
95 RTD9 Hi Alarm
96 RTD10 Hi Alarm
97 RTD11 Hi Alarm
98 RTD12 Hi Alarm
99 Reserved
114 Reserved
118 Reserved
119 Reserved
120 Reserved
315 Block Starts Per Hour and Time Between Starts (66)
316 Unblock Starts Per Hour and Time Between Starts (66)
bit 0 Trip
bit 1 Alarm
bit 2 Auxiliary 1
bit 3 Auxiliary 2
Unsigned 16 Bit
F149 CHANNEL 3 APPLICATION
Integer
0 MODBUS
1 Remote RTD
Unsigned 16 Bit
F150 OUTPUT RELAY STATUS
Integer
0 De - Energized
1 Energized
Unsigned 16 Bit
F151 CHANNEL TYPE
Integer
0 RS 485
1 Fiber Optic
Unsigned 16 Bit
F152 NUMBER OF RECORDS
Integer
0 1 64 cycles
1 2 32 cycles
2 4 16 cycles
3 8 8 cycles
Unsigned 16 Bit
F156 REMOTE RTD COMMUNICATION STATUS
Integer
Unsigned 16 Bit
F157 DIFFERENTIAL SWITCH INPUT FUNCTION
Integer
0 OFF
1 Differential Switch
2 General Switch
3 Digital Counter
4 Waveform Capture
5 DeviceNet Control
6 Reserved
7 Reserved
Unsigned 16 Bit
F158 SPEED SWITCH INPUT FUNCTION
Integer
0 OFF
1 Speed Switch
2 General Switch
3 Digital Counter
4 Waveform Capture
5 DeviceNet Control
6 Two-speed Monitor1
7 Reserved
Unsigned 16 Bit
F159 SPARE SWITCH INPUT FUNCTION
Integer
0 OFF
2 General Switch
3 Digital Counter
4 Waveform Capture
5 DeviceNet Control
6 Reserved
7 Reserved
Unsigned 16 Bit
F160 RESET SWITCH INPUT FUNCTION
Integer
0 OFF
1 Reset Switch
2 General Switch
3 Digital Counter
4 Waveform Capture
5 DeviceNet Control
6 Speed Switch1
7 Reserved
Unsigned 16 Bit
F161 OUTPUT RELAY FAILSAFE CODE
Integer
0 Failsafe
1 Non Failsafe
Unsigned 16 Bit
F162 ACCESS LEVEL
Integer
0 Read Only
1 Read / Write
2 Factory Service
Unsigned 16 Bit
F163 RRTD DIGITAL INPUT FUNCTION
Integer
0 Off
1 undefined
2 General Switch
3 Digital Counter
Unsigned 16 Bit
F164 COMMUNICATIONS MODULE STATUS
Integer
0x0002 IP Configuration OK
Unsigned 16 Bit
F165 OVERALL HOTTEST STATOR RTD OWNER
Integer
1 Remote RTD #1
2 Remote RTD #2
3 Remote RTD #3
4 Remote RTD #4
5 Local 369
Unsigned 16 Bit
F166 ENERGY UNIT DISPLAY
Integer
0 Mega
1 Kilo
Unsigned 16 Bit
F169 TRIP AND ALARM RELAYS
Integer
0 None
1 Trip
2 Alarm
3 Aux1
4 Aux2
15 All Relays
Unsigned 16 Bit
F180 ANSI/IEEE DEVICE
Integer
0 37 - Undercurrent/Underpower
1 46 - Current Unbalance
2 48 - Incomplete Sequence
3 49 - Thermal Model
5 51 - Overload Alarm
Unsigned 16 Bit
F181 OUTPUT RELAY TYPE
Integer
0 Latched
1 Pulsed
Unsigned 16 Bit
F182 PROTECTION FUNCTION BLOCKING STATUS
Integer
0 Not Blocked
1 Blocked
Unsigned 16 bit
F184 DATA RECORD ACCESS TYPE
Integer
Unsigned 16 bit
F185 VT CONNECTION TYPE
Integer
0 Phase-Neutral Voltage
1 Phase-Phase Voltage
Unsigned 16 bit
F186 MOTOR SPEED
Integer
0 Not Programmed
1 Start Log
2 Stop Log
0 Run To Fill
1 Circulate
0 Stopped
1 Running
BIT VALUE
3 Phase A Current F1
4 Phase B Current F1
5 Phase C Current F1
7 Motor Load F3
8 Current Unbalance F1
11 Vab* F1
12 Vbc* F1
13 Vca* F1
15 Van* F1
16 Vbn* F1
17 Vcn* F1
19 System Frequency F3
23 Reactive Power F4
24 Apparent Power F1
25 Positive MegaWatthours F1
26 Positive Megavarhours F1
27 Negative Megavarhours F1
28 Positive KiloWatthours F1
29 Positive Kilovarhours F1
30 Negative Kilovarhours F1
43 Current Demand F1
Appendix: Revisions
Revisions
A.2 Warranty
Warranty shall not apply to any relay which has been subject to misuse,
negligence, accident, incorrect installation or use not in accordance with
instructions nor any unit that has been altered outside a GE Multilin
authorized factory outlet.