GE 369 Communications Manual

Brand: GE

Model: 369

Type: Communications Manual

GE Multilin

215 Anderson Avenue, Markham, Ontario, Canada L6E 1B3

Tel: (905) 294-6222, 1-800-547-8629 (North America)

Fax: (905) 201-2098

Internet: http://www.GEmultilin.com

369 Motor Management Relay

Communications Guide

369 Revision: 3.2x

Manual P/N: 1601-9046-A1 (GEK-113493)

GE Consumer & Industrial

Multilin

*1601-9046-A1*

GE Multilin's Quality Management

System is registered to

ISO9001:2000

QMI # 005094

UL # A3775

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

LECTRICAL INTERFACE .....................................................................................................1

ROFIBUS COMMUNICATIONS .........................................................................................2

EVICENET COMMUNICATIONS .......................................................................................2

ODBUS COMMUNICATIONS ...........................................................................................2

ODBUS/TCP COMMUNICATIONS .................................................................................3

PROFIBUS-DP COMMUNICATIONS ............................................................................ 4

ROFIBUS COMMUNICATION OPTIONS ..........................................................................4

369 R

ELAY PROFIBUS-DP PARAMETERIZATION ...........................................................4

369 R

ELAY PROFIBUS-DP CONFIGURATION ................................................................4

369 R

ELAY PROFIBUS-DP DIAGNOSTICS .....................................................................9

369 R

ELAY PROFIBUS-DP LOSS OF COMMUNICATION TRIP ..................................15

PROFIBUS-DPV1 COMMUNICATIONS ..................................................................... 16

369 R

ELAY PROFIBUS-DPV1 PARAMETERIZATION ..................................................16

369 R

ELAY PROFIBUS CONFIGURATION .....................................................................17

369 R

ELAY PROFIBUS INPUT DATA ............................................................................17

369 R

ELAY PROFIBUS OUTPUT DATA ........................................................................18

369 R

ELAY PROFIBUS DIAGNOSTICS ..........................................................................19

369 R

ELAY PROFIBUS-DPV1 ACYCLICAL COMMUNICATION ..................................19

369 R

ELAY PROFIBUS-DPV1 LOSS OF COMMUNICATION TRIP ............................20

DEVICENET PROTOCOL ..............................................................................................20

EVICENET COMMUNICATIONS ....................................................................................20

OLL DATA ......................................................................................................................21

HANGE OF STATE (COS) .............................................................................................23

DENTITY OBJECT (CLASS CODE 01H) ..........................................................................23

ESSAGE ROUTER (CLASS CODE 02H) ........................................................................24

EVICENET OBJECT (CLASS CODE 03H) .....................................................................24

SSEMBLY OBJECT (CLASS CODE 04H) .......................................................................25

EVICENET CONNECTION OBJECT (CLASS CODE 05H) ............................................26

CKNOWLEDGE HANDLER OBJECT (CLASS CODE 2BH) ...........................................27

I/O D

ATA INPUT MAPPING OBJECT (CLASS CODE A0H) ..........................................28

I/O D

ATA OUTPUT MAPPING OBJECT (CLASS CODE A1H) ......................................28

ARAMETER DATA INPUT MAPPING OBJECT (CLASS CODE B0H) ............................29

EVICENET DATA FORMATS .........................................................................................35

MODBUS RTU PROTOCOL ..........................................................................................38

ATA FRAME FORMAT AND DATA RATE .....................................................................38

ATA PACKET FORMAT ..................................................................................................39

RROR CHECKING ..........................................................................................................39

CRC-16 A

LGORITHM ....................................................................................................40

IMING .............................................................................................................................41

UPPORTED MODBUS FUNCTIONS ..............................................................................41

RROR RESPONSES ........................................................................................................41

ODBUS COMMANDS ...................................................................................................42

TOC–2 369 MOTOR MANAGEMENT RELAY– INSTRUCTION MANUAL

TABLE OF CONTENTS

MEMORY MAP ...............................................................................................................43

EMORY MAP INFORMATION .......................................................................................43

SER DEFINABLE MEMORY MAP AREA .......................................................................43

VENT RECORDER ...........................................................................................................44

AVEFORM CAPTURE ....................................................................................................44

OTOR START DATA LOGGER ......................................................................................44

ATA LOGGER .................................................................................................................45

ODBUS MEMORY MAP ................................................................................................46

ORMAT 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

CGCOMMUNICATIONS GUIDE PROFIBUS-DP COMMUNICATIONS

369 MOTOR MANAGEMENT RELAY – COMMUNICATIONS GUIDE CG7

66 AvgPhaseVoltage 2 0 0000 65000 FDE8 1 V F1 0

68 Frequency 2 0 0000 12000 2EE0 1 Hz F3 0

70 BackSpinFrequency 2 1 0001 12000 2EE0 1 Hz F3 0

72 PowerFactor 2 –99 FF9D 100 0064 1 – F21 0

74 RealPower–kW 2

–

32000

8300 32000 7D00 1 kW F4 0

76 RealPower–hp 2 0 0000 65000 FDE8 1 hp F1 0

78 ReactivePower 2

–

32000

8300 32000 7D00 1 kvar F4 0

80 ApparentPower 2 0 0000 65000 FDE8 1 kVA F1 0

82 MWh 2 0 0000 65535 FFFF 1 MWh F1 0

84 PositiveMvarh 2 0 0000 65535 FFFF 1

Mvar

F1 0

86 NegativeMvarh 2 0 0000 65535 FFFF 1

Mvar

F1 0

88 HottestStatorRtd 2 0 0000 12 000C 1 F2 0

90 HottestStatorRtdTemp 2 –40 FFD8 200 00C8 1 °C F4 –42

92 LocalRtd1 2 –40 FFD8 200 00C8 1 °C F4 –42

94 LocalRtd2 2 –40 FFD8 200 00C8 1 °C F4 –42

96 LocalRtd3 2 –40 FFD8 200 00C8 1 °C F4 –42

98 LocalRtd4 2 –40 FFD8 200 00C8 1 °C F4 –42

100 LocalRtd5 2 –40 FFD8 200 00C8 1 °C F4 –42

102 LocalRtd6 2 –40 FFD8 200 00C8 1 °C F4 –42

104 LocalRtd7 2 –40 FFD8 200 00C8 1 °C F4 –42

106 LocalRtd8 2 –40 FFD8 200 00C8 1 °C F4 –42

108 LocalRtd9 2 –40 FFD8 200 00C8 1 °C F4 –42

110 LocalRtd10 2 –40 FFD8 200 00C8 1 °C F4 –42

112 LocalRtd11 2 –40 FFD8 200 00C8 1 °C F4 –42

114 LocalRtd12 2 –40 FFD8 200 00C8 1 °C F4 –42

116 CurrentDemand 2 0 0000 50000 C350 1 A F1 0

118 RealPowerDemand 2 0 0000 50000 C350 1 kW F1 0

120 ReactivePowerDemand 2

–

32000

8300 32000 7D00 1 kvar F4 0

122 ApparentPowerDemand 2 0 0000 50000 C350 1 kVA F1 0

124 PeakCurrent 2 0 0000 65535 FFFF 1 A F1 0

126 PeakRealPower 2 0 0000 50000 C350 1 kW F1 0

128 PeakReactivePower 2

–

32000

8300 32000 7D00 1 kvar F4 0

Table CG–1: Profibus Input Data (Sheet 2 of 4)

OFFSET CYCLIC DATA

(ACTUAL VALUES)

LENGTH

(BYTES)

MINIMUM MAXIMUM STEP

VALUE

UNITS FORMAT

CODE

DEFAULT

VALUE HEX VALUE HEX

CG8 369 MOTOR MANAGEMENT RELAY – COMMUNICATIONS GUIDE

PROFIBUS-DP COMMUNICATIONS CGCOMMUNICATIONS GUIDE

130 PeakApparentPower 2 0 0000 50000 C350 1 kVA F1 0

132 Va angle 2 0 0000 359 0167 1 o F1 0

134 Vb angle 2 0 0000 359 0167 1 o F1 0

136 Vc angle 2 0 0000 359 0167 1 o F1 0

138 Ia angle 2 0 0000 359 0167 1 o F1 0

140 Ib angle 2 0 0000 359 0167 1 o F1 0

142 Ic angle 2 0 0000 359 0167 1 o F1 0

144 Learned AccelerationTime 2 1 0001 2500 09C4 1 s F2 0

146 Learned StartingCurrent 2 0 0000 65535 FFFF 1 A F1 0

148 Learned StartingCapacity 2 0 0000 100 0064 1 % F1 0

150

Learned RunningCoolTime

Constant

2 0 0000 500 01F4 1 min F1 0

152

LearnedStoppedCoolTime

Constant

2 0 0000 500 01F4 1 min F1 0

154 Last StartingCapacity 2 0 0000 100 0064 1 % F1 0

156 Learned UnbalanceKfactor 2 0 0000 29 001D 1 – F1 0

158 BSDState 2 0 0000 6 0006 1 – F27 0

160 RawPredictionTimer 2 0 0000 50000 C350 1 s F2 0

162 NumberOfStarts 2 0 0000 50000 C350 1 – F1 0

164 NumberOfRestarts 2 0 0000 50000 C350 1 – F1 0

166 DigitalCounter 2 0 0000 65535 FFFF 1 – F1 0

168 MotorRunningHours 2 0 0000 65535 FFFF 1 hr F1 0

170 RelayOperatingHours 2 0 0000 65535 FFFF 1 hr F1 0

172 Last trip Cause 2 0 0000 169 00A9 1 – F134 0

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

182 Last pre-trip Ia 2 0 0000 65535 FFFF 1 A F1 0

184 Last pre-trip Ib 2 0 0000 65535 FFFF 1 A F1 0

186 Last pre-trip Ic 2 0 0000 65535 FFFF 1 A F1 0

188 Last pre-trip MotorLoad 2 0 0000 2000 07D0 1 FLA F3 0

190 Last pre-trip Unbalance 2 0 0000 100 0064 1 % F1 0

192 Last pre-trip Ig 2 0 0000 50000 C350 1 A F23 0

194 Last trip HottestStatorRtd 2 0 0000 12 000C 1 – F1 0

196 Last trip HottestStatorTemp 2 –40 FFD8 200 00C8 1 °C F4 0

198 Last pre–trip Vab 2 0 0000 65000 FDE8 1 V F1 0

200 Last pre–trip Vbc 2 0 0000 65000 FDE8 1 V F1 0

Table CG–1: Profibus Input Data (Sheet 3 of 4)

OFFSET CYCLIC DATA

(ACTUAL VALUES)

LENGTH

(BYTES)

MINIMUM MAXIMUM STEP

VALUE

UNITS FORMAT

CODE

DEFAULT

VALUE HEX VALUE HEX

CGCOMMUNICATIONS GUIDE PROFIBUS-DP COMMUNICATIONS

369 MOTOR MANAGEMENT RELAY – COMMUNICATIONS GUIDE CG9

2.4 369 Relay Profibus-DP Diagnostics

The 369 Motor Management Relay supports both slave mandatory (6 bytes system-wide

standardized) and slave specific diagnostic data. If the diagnostics are considered high

priority, the PLC/host program will be informed of the fault (alarm or trip) and can call a

special error routine.

Diagnostic bytes 1 through 6 represent standard diagnostic data and are formatted as

follows.

The extended diagnosis for the relay is composed of 26 bytes (bytes 7 to 32) and contains

diagnostic information according to the following table.

202 Last pre–trip Vca 2 0 0000 65000 FDE8 1 V F1 0

204 Last pre–trip Van 2 0 0000 65000 FDE8 1 V F1 0

206 Last pre–trip Vbn 2 0 0000 65000 FDE8 1 V F1 0

208 Last pre–trip Vcn 2 0 0000 65000 FDE8 1 V F1 0

210 Last pre–trip Frequency 2 0 0000 12000 2EE0 1 Hz F3 0

212 Last pre–trip KiloWatts 2

–

32000

8300 32000 7D00 1 kW F4 0

214 Last pre–trip KiloVAR 2

–

32000

8300 32000 7D00 1 kvar F4 0

216 Last pre–trip KiloVA 2 0 0000 50000 C350 1 kVA F1 0

218 Last pre–trip PowerFactor 2 –99 FF9D 100 0064 1 – F21 0

Table CG–1: Profibus Input Data (Sheet 4 of 4)

OFFSET CYCLIC DATA

(ACTUAL VALUES)

LENGTH

(BYTES)

MINIMUM MAXIMUM STEP

VALUE

UNITS FORMAT

CODE

DEFAULT

VALUE HEX VALUE HEX

Table CG–2: Diagnostic bytes 1 through 7

BYTE DESCRIPTION

1Station Status 1

2Station Status 2

3Station Status 3

4 Diagnostic Master Address

5 Identification Number (High Byte)

6 Identification Number (Low Byte)

Table CG–3: Profibus Diagnostics (Sheet 1 of 7)

BIT BYTE FUNCTION

0 to 7 7 Number of Diagnostic Bytes

0 8 SinglePhasingTrip

1 8 SpareSwitchTrip

CG10 369 MOTOR MANAGEMENT RELAY – COMMUNICATIONS GUIDE

PROFIBUS-DP COMMUNICATIONS CGCOMMUNICATIONS GUIDE

2 8 EmergencySwitchTrip

3 8 DifferentialSwitchTrip

4 8 SpeedSwitchTrip

5 8 ResetSwitchTrip

68Reserved

7 8 OverloadTrip

89ShortCircuitTrip

99ShortCircuitBackupTrip

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

Table CG–3: Profibus Diagnostics (Sheet 2 of 7)

BIT BYTE FUNCTION

CGCOMMUNICATIONS GUIDE PROFIBUS-DP COMMUNICATIONS

369 MOTOR MANAGEMENT RELAY – COMMUNICATIONS GUIDE CG11

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

Table CG–3: Profibus Diagnostics (Sheet 3 of 7)

BIT BYTE FUNCTION

CG12 369 MOTOR MANAGEMENT RELAY – COMMUNICATIONS GUIDE

PROFIBUS-DP COMMUNICATIONS CGCOMMUNICATIONS GUIDE

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

Table CG–3: Profibus Diagnostics (Sheet 4 of 7)

BIT BYTE FUNCTION

CGCOMMUNICATIONS GUIDE PROFIBUS-DP COMMUNICATIONS

369 MOTOR MANAGEMENT RELAY – COMMUNICATIONS GUIDE CG13

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

Table CG–3: Profibus Diagnostics (Sheet 5 of 7)

BIT BYTE FUNCTION

CG14 369 MOTOR MANAGEMENT RELAY – COMMUNICATIONS GUIDE

PROFIBUS-DP COMMUNICATIONS CGCOMMUNICATIONS GUIDE

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

Table CG–3: Profibus Diagnostics (Sheet 6 of 7)

BIT BYTE FUNCTION

CGCOMMUNICATIONS GUIDE PROFIBUS-DP COMMUNICATIONS

369 MOTOR MANAGEMENT RELAY – COMMUNICATIONS GUIDE CG15

2.5 369 Relay Profibus-DP Loss Of Communication Trip

If the 369 detects a problem in communicating with the Profibus master, the Profibus Loss

of Communications feature can be used to trip any combination of output relays.

During parameterization, a Profibus master sets up the communication and monitoring

times for the slave including the watchdog time. A Profibus slave uses a watchdog timer to

enable it to detect bus inactivity with its master. The watchdog timer is reset every time an

error free message is received from the master. If no valid message is received within the

time specified during parameterization, the slave assumes a communication error.

If the 369 Profibus communications is offline and not communicating with a master, then

the “Profibus Loss of Comms” function (if enabled) will activate. This feature can be

programmed for Latched or Unlatched operation.

If programmed as Latched:

The “Profibus 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.

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

Table CG–3: Profibus Diagnostics (Sheet 7 of 7)

BIT BYTE FUNCTION

CG16 369 MOTOR MANAGEMENT RELAY – COMMUNICATIONS GUIDE

PROFIBUS-DPV1 COMMUNICATIONS CGCOMMUNICATIONS GUIDE

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. Profibus Loss of Comms Enable

2. Profibus Loss of Comms Delay

3. Assigned Profibus 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

3.1 369 Relay Profibus-DPV1 Parameterization

The 369 Motor Management Relay supports mandatory parametrization as well as three

bytes of user parameter data necessary for DPV1 devices. The relay keeps its user

parameter data/setpoints in a non-volatile memory and does not require device related

parametrization during startup of the DP/V1 master, with the exception of the DPV1 Enable

parameter. To enable the DPV1 acyclical functionality, the DPV1 parameter must be set to

“Enable” when configuring the device in your master using the GSD file.

The EnerVista 369 Setup software is the best tool for editing user parametrization

(setpoints) of the 369 Relay device.

FIGURE CG–2: User Parameter Setup – Enable DPV1

Page is loading ...

GE 369 Communications Manual

GE 369 Communications Manual

GE 369 Communications Manual

Related papers

Other documents