GE 369 Use and care manual

GE Multilin
215 Anderson Avenue, Markham, Ontario, Canada L6E 1B3
Tel: [phone] (North America)
Fax: [phone]
Internet: http://www.GEmultilin.com
369 Motor Management Relay
Communications Guide
369 Revision: 3.2x
Manual P/N: 1601-9046-A1 (GEK-113493)
Copyright © 2008 GE Multilin
GE Consumer & Industrial
Multilin
*1601-9046-A1*
GE Multilin's Quality Management
System is registered to
ISO9001:2000
QMI # 005094
UL # A3775

© 2008 GE Multilin Incorporated. All rights reserved.
GE Multilin 369 Motor Management Relay Communications Guide for revision
3.2x.
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.
Part number: 1601-9046-A1 (February 2008)

TABLE OF CONTENTS
369 MOTOR MANAGEMENT RELAY– INSTRUCTION MANUAL TOC–1
Table of Contents
OVERVIEW ........................................................................................................................ 1
ELECTRICAL INTERFACE .....................................................................................................1
PROFIBUS COMMUNICATIONS .........................................................................................2
DEVICENET COMMUNICATIONS .......................................................................................2
MODBUS COMMUNICATIONS ...........................................................................................2
MODBUS/TCP COMMUNICATIONS .................................................................................3
PROFIBUS-DP COMMUNICATIONS ............................................................................ 4
PROFIBUS COMMUNICATION OPTIONS ..........................................................................4
369 RELAY PROFIBUS-DP PARAMETERIZATION ...........................................................4
369 RELAY PROFIBUS-DP CONFIGURATION ................................................................4
369 RELAY PROFIBUS-DP DIAGNOSTICS .....................................................................9
369 RELAY PROFIBUS-DP LOSS OFCOMMUNICATION TRIP ..................................15
PROFIBUS-DPV1 COMMUNICATIONS .....................................................................16
369 RELAY PROFIBUS-DPV1 PARAMETERIZATION ..................................................16
369 RELAY PROFIBUS CONFIGURATION .....................................................................17
369 RELAY PROFIBUS INPUT DATA ............................................................................17
369 RELAY PROFIBUS OUTPUT DATA ........................................................................18
369 RELAY PROFIBUS DIAGNOSTICS ..........................................................................19
369 RELAY PROFIBUS-DPV1 ACYCLICAL COMMUNICATION ..................................19
369 RELAY PROFIBUS-DPV1 LOSS OFCOMMUNICATION TRIP ............................20
DEVICENET PROTOCOL .............................................................................................. 20
DEVICENET COMMUNICATIONS ....................................................................................20
POLL DATA ......................................................................................................................21
CHANGE OF STATE (COS) .............................................................................................23
IDENTITY OBJECT (CLASS CODE 01H) ..........................................................................23
MESSAGE ROUTER (CLASS CODE 02H) ........................................................................24
DEVICENET OBJECT (CLASS CODE 03H) .....................................................................24
ASSEMBLY OBJECT (CLASS CODE 04H) .......................................................................25
DEVICENET CONNECTION OBJECT (CLASS CODE 05H) ............................................26
ACKNOWLEDGE HANDLER OBJECT (CLASS CODE 2BH) ...........................................27
I/O DATA INPUT MAPPING OBJECT (CLASS CODE A0H) ..........................................28
I/O DATA OUTPUT MAPPING OBJECT (CLASS CODE A1H) ......................................28
PARAMETER DATA INPUT MAPPING OBJECT (CLASS CODE B0H) ............................29
DEVICENET DATA FORMATS .........................................................................................35
MODBUS RTU PROTOCOL ..........................................................................................38
DATA FRAME FORMAT AND DATA RATE .....................................................................38
DATA PACKET FORMAT ..................................................................................................39
ERROR CHECKING ..........................................................................................................39
CRC-16 ALGORITHM ....................................................................................................40
TIMING .............................................................................................................................41
SUPPORTED MODBUS FUNCTIONS ..............................................................................41
ERROR RESPONSES ........................................................................................................41
MODBUS COMMANDS ...................................................................................................42

TOC–2 369 MOTOR MANAGEMENT RELAY– INSTRUCTION MANUAL
TABLE OF CONTENTS
MEMORY MAP ...............................................................................................................43
MEMORY MAP INFORMATION .......................................................................................43
USER DEFINABLE MEMORY MAP AREA .......................................................................43
EVENT RECORDER ...........................................................................................................44
WAVEFORM CAPTURE ....................................................................................................44
MOTOR START DATA LOGGER ......................................................................................44
DATA LOGGER .................................................................................................................45
MODBUS MEMORY MAP ................................................................................................46
FORMAT CODES ........................................................................................................... 103

369 MOTOR MANAGEMENT RELAY – COMMUNICATIONS GUIDE CG–1
369 Motor Management Relay
Communications Guide
GE Consumer & Industrial
Multilin
Communicatio ns Guide
1 Overview
1.1 Electrical Interface
The hardware or electrical interface is one of the following:
• one of three 2-wire RS485 ports from the rear terminal connector,
• the RS232 from the front panel connector
• a fibre optic connection.
In a 2-wire RS485 link, data flow is bidirectional. Data flow is half-duplex for both the RS485
and the RS232 ports. That is, data is never transmitted and received at the same time.
RS485 lines should be connected in a daisy chain configuration (avoid star connections)
with a terminating network installed at each end of the link, i.e. at the master end and at
the slave farthest from the master. The terminating network should consist of a 120 ohm
resistor in series with a 1 nF ceramic capacitor when used with Belden 9841 RS485 wire.
The value of the terminating resistors should be equal to the characteristic impedance of
the line. This is approximately 120 ohms for standard #22 AWG twisted pair wire. Shielded
wire should always be used to minimize noise. Polarity is important in RS485
communications. Each '+' terminal of every 369 must be connected together for the
system to operate. See the 369 Instruction Manual, chapter 3 for details on correct serial
port wiring.
When using a fibre optic link the Tx from the 369 should be connected to the Rx of the
Master device and the Rx from the 369 should be connected to the Tx of the Master device.

CG2 369 MOTOR MANAGEMENT RELAY – COMMUNICATIONS GUIDE
OVERVIEW CGCOMMUNICATIONS GUIDE
1.2 Profibus Communications
The 369 Motor Management Relay supports both Profibus-DP (order code P) and Profibus-
DPV1 (order code P1) communication interfaces as slave that can be read and written to/
from a Profibus-DP/V1 master. The Profibus-DP/V1 Master must read the GSD (Device
Master Data) file of the 369 for the purposes of configuration and parameterization.
• The GSD file for the Profibus-DP option is 369_090C.gse.
• The GSD file for the Profibus-DPV1 option is 369_09E6.gse.
• The relay supports the following configurations and indications:
• Fieldbus type: PROFIBUS-DP (IEC 61158 Type 3, and IEC 61784)
• Auto baud rate detection 9.6Kbit - 12Mbit.
• Address range: 1-126, setting via EnerVista 369 Setup software or front
keypad.
• Input data: 220 bytes - cyclical.
• Extended Diagnostic data: 26 bytes - non-cyclical.
• Sections 2.2 to 2.4 pertain to the Profibus-DP option.
• In addition to the above, the Profibus-DPV1 (P1) option supports:
• Fieldbus type: Profibus-DPV1 (IEC 61158 Type 3, and IEC 61784)
• Acyclic read/write between a Master (Class1/Class2) and the 369 slave
according to the DPV1 extensions of IEC 61158.
• Output Data: 2 bytes - cyclical.
Sections 3.1 to 3.6 of this manual pertain to the Profibus-DPV1 option.
1.3 DeviceNet Communications
The 369 Motor Management Relay supports the optional DeviceNet protocol as slave that
can be read by a DeviceNet master. The device can be added to a DeviceNet list by adding
the 369.eds file in the scanner list. The EDS file can be generated using the EnerVista 369
Setup program.
The relay supports following configuration.
• Field bus type: DeviceNet
• Functions supported: Explicit, Polled, COS and Cyclic IO messaging
• Baud Rate: 125, 250 and 500 kbps, programmable through software or relay front
keypad
• Mac ID: 0 to 63, programmable through software or relay front keypad
See section 4: DeviceNet Protocol, for complete details.
1.4 Modbus Communications
The 369 implements a subset of the AEG Modicon Modbus RTU serial communication
standard. Many popular programmable controllers support this protocol directly with a
suitable interface card allowing direct connection of relays. Although the Modbus protocol
is hardware independent, the 369 interfaces include three 2-wire RS485 ports and one

CGCOMMUNICATIONS GUIDE OVERVIEW
369 MOTOR MANAGEMENT RELAY – COMMUNICATIONS GUIDE CG3
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.
1.5 Modbus/TCP Communications
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.
Note The implementation of this option is for the intention of data retrieval and device
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”
SETPOINT MEMORY MAP
ADDRESS
DATA VALUE
(DEC)
IP ADDRESS OCTET1 0x101C 127
IP ADDRESS OCTET2 0x101D 0
IP ADDRESS OCTET3 0x101E 0
IP ADDRESS OCTET4 0x101F 1
SUBNET MASK OCTET1 0x1020 255
SUBNET MASK OCTET2 0x1021 255
SUBNET MASK OCTET3 0x1022 255
SUBNET MASK OCTET4 0x1023 252
GATEWAY ADDRESS OCTET1 0x1024 127
GATEWAY ADDRESS OCTET2 0x1025 0
GATEWAY ADDRESS OCTET3 0x1026 0

CG4 369 MOTOR MANAGEMENT RELAY – COMMUNICATIONS GUIDE
PROFIBUS-DP COMMUNICATIONS CGCOMMUNICATIONS GUIDE
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.
2 Profibus-DP Communications
2.1 Profibus Communication Options
The 369 Motor Management Relay supports either Profibus-DP (order code P) or Profibus-
DPV1 (order code P1) communication interfaces as slave that can be read and written to/
from a Profibus-DP/V1 master. The Profibus-DP/V1 Master must read the GSD (Device
Master Data) file of the 369 for the purposes of configuration and parameterization.
• The GSD file for the Profibus-DP option is 369_090C.GSE.
• The GSD file for the Profibus-DPV1 option is 369_09E6.GSE.
Sections 2.2 to 2.4 pertain to the Profibus-DP option.
Sections 3.1 to 3.6 of this manual pertain to the Profibus-DPV1 option.
2.2 369 Relay Profibus-DP Parameterization
The 369 Motor Management Relay supports mandatory parametrization. The relay keeps
its user parameter data / setpoints in a non-volatile memory and does not need device
related parametrization during startup of the DP master. The EnerVista 369 Setup software
is the best tool for user parametrization of the 369 device.
2.3 369 Relay Profibus-DP Configuration
The Profibus-DP basic configuration has one DP master and one DP slave. In a typical bus
segment up to 32 stations can be connected (a repeater has to be used if more than 32
stations operate on a bus). The end nodes on a Profibus-DP network must be terminated to
avoid reflections on the bus line.
The bus address for the relay as Profibus-DP node can be set using the S1 369 RELAY
SETUP Ø369 RELAY COMMUNICATIONS ØPROFIBUS ADDRESS setpoint or via the EnerVista
369 Setup software, which extends address range from 1 to 126. Address 126 is used only
for commissioning purposes and should not be used to exchange user data.
GATEWAY ADDRESS OCTET4 0x1027 1
SETPOINT MEMORY MAP
ADDRESS
DATA VALUE
(DEC)

CGCOMMUNICATIONS GUIDE PROFIBUS-DP COMMUNICATIONS
369 MOTOR MANAGEMENT RELAY – COMMUNICATIONS GUIDE CG5
The media for the fieldbus is a twisted pair copper cable along with 9-pin SUB-D connector,
which connects the bus to the 369 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 369_090C.gs* which is used by a
network configuration program.
The 369 Motor Management Relay as a DP slave transfers fast process data to the DP
master according to master-slave principle. The 369 Motor Management Relay is a
modular device, supporting up to 8 input modules.
During the configuration session, all modules have to be selected in order to get the entire
area of 110 words of input data. There are no output data for processing. The following
diagram shows the possible DP Master Class 2 configuration menu:
FIGURE CG–1: Slave Configuration

CG6 369 MOTOR MANAGEMENT RELAY – COMMUNICATIONS GUIDE
PROFIBUS-DP COMMUNICATIONS CGCOMMUNICATIONS GUIDE
Table CG–1: Profibus Input Data (Sheet 1 of 4)
OFFSET CYCLIC DATA
(ACTUAL VALUES)
LENGTH
(BYTES)
MINIMUM MAXIMUM STEP
VALUE
UNITS FORMAT
CODE
DEFAULT
VALUE HEX VALUE HEX
0 MotorStatus 2 0 0000 4 0004 1 – F133 0
2 TC_Used 2 0 0000 100 0064 1 % F1 0
4 Time_to_Trip 2 –1 FFFF 65500 FFDC 1 s F20 –1
6 OverloadLT 2 0 0000 50000 C350 1 s F1 0
8 StartsHourLT[5] 2 0 0000 60 003C 1 min F1 0
10 TimeBetween StartsLT 2 0 0000 500 01F4 1 min F1 0
12 RestartBlock LT 2 0 0000 50000 C350 1 s F1 0
14 StartInhibitLT 2 0 0000 60 003C 1 min F1 0
16 AccessSwitch Status 2 0 0000 1 0001 1 – F131 0
18 SpeedSwitch Status 2 0 0000 1 0001 1 – F131 0
20 SpareSwitch Status 2 0 0000 1 0001 1 – F131 0
22 DiffSwitch Status 2 0 0000 1 0001 1 – F131 0
24 EmergencySwitch status 2 0 0000 1 0001 1 – F131 0
26 ResetSwitch Status 2 0 0000 1 0001 1 – F131 0
28 TripRelayStatus 2 0 0000 1 0001 1 N/A F150 2
30 AlarmRelayStatus 2 0 0000 1 0001 1 N/A F150 2
32 Aux1RelayStatus 2 0 0000 1 0001 1 N/A F150 2
34 Aux2RelayStatus 2 0 0000 1 0001 1 N/A F150 2
36 Ia 2 0 0000 65535 FFFF 1 A F1 0
38 Ib 2 0 0000 65535 FFFF 1 A F1 0
40 Ic 2 0 0000 65535 FFFF 1 A F1 0
42 AveragePhaseCurrent 2 0 0000 65535 FFFF 1 A F1 0
44 MotorLoad 2 0 0000 2000 07D0 1 xFLA F3 0
46 CurrentUnbalance 2 0 0000 100 0064 1 % F1 0
48 U/B Biased Motor Load 2 0 0000 2000 07D0 1 xFLC F3 0
50 GroundCurrent 2 0 0000 50000 C350 1 A F23 0
52 Vab 2 0 0000 65000 FDE8 1 V F1 0
54 Vbc 2 0 0000 65000 FDE8 1 V F1 0
56 Vca 2 0 0000 65000 FDE8 1 V F1 0
58 Van 2 0 0000 65000 FDE8 1 V F1 0
60 Vbn 2 0 0000 65000 FDE8 1 V F1 0
62 Vcn 2 0 0000 65000 FDE8 1 V F1 0
64 AvgLineVoltage 2 0 0000 65000 FDE8 1 V F1 0