gek-113493c.pdf

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 RelayCommunications Guide

369 Revision: 3.4x

Manual P/N: 1601-9046-A4

Publication Number: GEK-113493C

Copyright 2010 GE Multilin

GE Consumer & IndustrialMultilin

*1601-9046-A4*

GE Multilin's Quality Management System is registered to

ISO9001:2000

QMI # 005094UL # 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.

Part number: 1601-9046-A4 (July 2010)

TABLE OF CONTENTS

369 MOTOR MANAGEMENT RELAY INSTRUCTION MANUAL TOC1

Table of Contents

OVERVIEW .........................................................................................................................................1ELECTRICAL INTERFACE .....................................................................................................1PROFIBUS COMMUNICATIONS .........................................................................................2DEVICENET COMMUNICATIONS .......................................................................................2MODBUS COMMUNICATIONS ...........................................................................................2MODBUS/TCP COMMUNICATIONS .................................................................................3

PROFIBUS-DP COMMUNICATIONS .........................................................................................6PROFIBUS COMMUNICATION OPTIONS ..........................................................................6369 RELAY PROFIBUS-DP PARAMETERIZATION ...........................................................6369 RELAY PROFIBUS-DP CONFIGURATION ................................................................6369 RELAY PROFIBUS-DP DIAGNOSTICS ..................................................................11PROFIBUS-DP LOSS OF COMMUNICATION TRIP .......................................................18

PROFIBUS-DPV1 COMMUNICATIONS ................................................................................19369 RELAY PROFIBUS-DPV1 PARAMETERIZATION ..................................................19369 RELAY PROFIBUS CONFIGURATION .....................................................................19369 RELAY PROFIBUS INPUT DATA ............................................................................20369 RELAY PROFIBUS OUTPUT DATA ........................................................................21369 RELAY PROFIBUS DIAGNOSTICS ..........................................................................22369 RELAY PROFIBUS-DPV1 ACYCLICAL COMMUNICATION ..................................22369 RELAY PROFIBUS-DPV1 LOSS OF COMMUNICATION TRIP ............................23

DEVICENET PROTOCOL ............................................................................................................ 24DEVICENET COMMUNICATIONS ....................................................................................24POLL DATA ......................................................................................................................25CHANGE OF STATE (COS) .............................................................................................27IDENTITY OBJECT (CLASS CODE 01H) ..........................................................................28MESSAGE ROUTER (CLASS CODE 02H) ........................................................................28DEVICENET OBJECT (CLASS CODE 03H) .....................................................................28ASSEMBLY OBJECT (CLASS CODE 04H) .......................................................................29DEVICENET CONNECTION OBJECT (CLASS CODE 05H) ............................................31ACKNOWLEDGE HANDLER OBJECT (CLASS CODE 2BH) ...........................................32I/O DATA INPUT MAPPING OBJECT (CLASS CODE A0H) ..........................................32I/O DATA OUTPUT MAPPING OBJECT (CLASS CODE A1H) ......................................33PARAMETER DATA INPUT MAPPING OBJECT (CLASS CODE B0H) ............................33DEVICENET LOSS OF COMMUNICATION TRIP ............................................................41DEVICENET DATA FORMATS .........................................................................................42

MODBUS RTU PROTOCOL .......................................................................................................46DATA FRAME FORMAT AND DATA RATE .....................................................................46DATA PACKET FORMAT ..................................................................................................46ERROR CHECKING ..........................................................................................................47CRC-16 ALGORITHM ....................................................................................................47TIMING .............................................................................................................................48SUPPORTED MODBUS FUNCTIONS ..............................................................................48ERROR RESPONSES ........................................................................................................48MODBUS COMMANDS ...................................................................................................49

MEMORY MAP ...............................................................................................................................51MEMORY MAP INFORMATION .......................................................................................51USER DEFINABLE MEMORY MAP AREA .......................................................................51EVENT RECORDER ..........................................................................................................52WAVEFORM CAPTURE ....................................................................................................52

TOC2 369 MOTOR MANAGEMENT RELAY INSTRUCTION MANUAL

TABLE OF CONTENTS

MOTOR START DATA LOGGER ......................................................................................52DATA LOGGER .................................................................................................................53MODBUS MEMORY MAP ................................................................................................54FORMAT CODES ........................................................................................................... 131

CHANGE NOTES ........................................................................................................................ 163REVISION HISTORY ...................................................................................................... 163

WARRANTY ................................................................................................................................. 165WARRANTY INFORMATION ......................................................................................... 165

369 MOTOR MANAGEMENT RELAY COMMUNICATIONS GUIDE CG1

369 Motor Management Relay

Communications Guide

GE Consumer & IndustrialMultilin

Communications 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 CommunicationsThe 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 CommunicationsThe 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 CommunicationsThe 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


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.1SUBNET MASK: 255.255.255.252GATEWAY ADDRESS: 127.0.0.1

SETPOINT MEMORY MAPADDRESS

DATA VALUE(DEC)

IP ADDRESS OCTET1 0x101C 127IP ADDRESS OCTET2 0x101D 0IP ADDRESS OCTET3 0x101E 0IP ADDRESS OCTET4 0x101F 1SUBNET MASK OCTET1 0x1020 255SUBNET MASK OCTET2 0x1021 255SUBNET MASK OCTET3 0x1022 255SUBNET MASK OCTET4 0x1023 252GATEWAY ADDRESS OCTET1 0x1024 127GATEWAY ADDRESS OCTET2 0x1025 0GATEWAY ADDRESS OCTET3 0x1026 0


OVERVIEW 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.

Ethernet Loss Of Communication Trip

The 369 can detect a failure in communication activity with the MODBUS Master through Ethernet port. The Ethernet Loss of Communications feature can be used to trip any combination of output relays.

When equipped with the Ethernet option, the 369 can be configured to check for MODBUS TCP/IP activity, and raise an alarm and trip an output relay if activity is not detected within the configured delay. Delays of 0.25 to 10.00 seconds may be configured by the user.

If the Fieldbus Loss of Comms function is enabled , the 369 considers an Ethernet loss of communication to have occurred in the following conditions:

1. Link failure (break in physical connection)

2. If valid MODBUS packets are not received within the configured delay period. Invalid MODBUS packets, such as ones that contain the wrong slave ID, are not considered valid. Please note that an ICMP PING message is not a valid MODBUS packet

3. If packets cannot be received because of buffer overflows or lack of queue space, the delay timer will continue to decrement, and will not be reset until valid packets are received. If the queues / buffers cannot be recovered within the configured delay, the Loss of Communication alarm will be raised, and any configured relays shall trip.

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. To avoid false trips, it is advised to set the trip delay greater than MODBUS timeout delay.

This feature can be programmed for Latched or Unlatched operation.

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

GATEWAY ADDRESS OCTET4 0x1027 1

SETPOINT MEMORY MAPADDRESS

DATA VALUE(DEC)

CGCOMMUNICATIONS GUIDE OVERVIEW


3. Assign Loss of Comms Relay

Refer to the 369 Instruction Manual, chapter 5: 369 Relay Communications for more information on these setpoints.


PROFIBUS-DP COMMUNICATIONS CGCOMMUNICATIONS GUIDE

2 Profibus-DP Communications

2.1 Profibus Communication OptionsThe 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 ParameterizationThe 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 ConfigurationThe 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.

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:

CGCOMMUNICATIONS GUIDE PROFIBUS-DP COMMUNICATIONS


FIGURE CG1: Slave Configuration

Table CG1: Profibus Input Data (Sheet 1 of 5)

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

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 RealPowerkW 2 32000 8300 32000 7D00 1 kW F4 0

76 RealPowerhp 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 Mvarh F1 0

86 NegativeMvarh 2 0 0000 65535 FFFF 1 Mvarh F1 0

88 HottestStatorRtd 2 0 0000 12 000C 1 F2 0



LENGTH (BYTES)


UNITS FORMAT CODE

DEFAULT

VALUE HEX VALUE HEX



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

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



LENGTH (BYTES)


UNITS FORMAT CODE

DEFAULT

VALUE HEX VALUE HEX



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 pretrip Vab 2 0 0000 65000 FDE8 1 V F1 0

200 Last pretrip Vbc 2 0 0000 65000 FDE8 1 V F1 0

202 Last pretrip Vca 2 0 0000 65000 FDE8 1 V F1 0

204 Last pretrip Van 2 0 0000 65000 FDE8 1 V F1 0

206 Last pretrip Vbn 2 0 0000 65000 FDE8 1 V F1 0



LENGTH (BYTES)


UNITS FORMAT CODE

DEFAULT

VALUE HEX VALUE HEX



2.4 369 Relay Profibus-DP DiagnosticsThe 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.

208 Last pretrip Vcn 2 0 0000 65000 FDE8 1 V F1 0

210 Last pretrip Frequency 2 0 0000 12000 2EE0 1 Hz F3 0

212 Last pretrip KiloWatts 2 32000 8300 32000 7D00 1 kW F4 0

214 Last pretrip KiloVAR 2 32000 8300 32000 7D00 1 kvar F4 0

216 Last pretrip KiloVA 2 0 0000 50000 C350 1 kVA F1 0

218 Last pretrip PowerFactor

2 99 FF9D 100 0064 1 F21 0



LENGTH (BYTES)


UNITS FORMAT CODE

DEFAULT

VALUE HEX VALUE HEX

Table CG2: Diagnostic bytes 1 through 7

BYTE DESCRIPTION

1 Station Status 1

2 Station Status 2

3 Station Status 3

4 Diagnostic Master Address

5 Identification Number (High Byte)

6 Identification Number (Low Byte)

Table CG3: Profibus Diagnostics (Sheet 1 of 8)

BIT BYTE FUNCTION

0 to 7 7 Number of Diagnostic Bytes

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


BIT BYTE FUNCTION



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


BIT BYTE FUNCTION



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



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


BIT BYTE FUNCTION



99 20 TimeBetweenStartsBlock

100 20 RestartBlock

101 20 Reserved

102 20 BackSpinBlock

103 20 LossofRemoteRTDCommunication

104 21 RemoteRTD1Rtd1Trip




























BIT BYTE FUNCTION
























152 27 RemoteRTD1Rtd1Alarm












BIT BYTE FUNCTION




































BIT BYTE FUNCTION



2.5 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 operate on 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 Fieldbus Loss of Comms function (if enabled) will activate. This feature can be programmed for Latched or Unlatched operation.


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.


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.




3. Assigned Fieldbus Loss of Comms Relay








BIT BYTE FUNCTION

CGCOMMUNICATIONS GUIDE PROFIBUS-DPV1 COMMUNICATIONS


3 Profibus-DPV1 Communications

3.1 369 Relay Profibus-DPV1 ParameterizationThe 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 CG2: User Parameter Setup Enable DPV1

3.2 369 Relay Profibus ConfigurationThe Profibus-DPV1 basic configuration has one DP/V1 master and one DPV1 slave. In a typical bus segment up to 32 stations can be connected (a repeater has to be used if more then 32 stations operate on a bus). The end nodes on a Profibus-DPV1 network must be terminated to avoid reflections on the bus line.

The bus address for the relay as Profibus-DPV1 node can be set using the S1 369 SETUP 369 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.


PROFIBUS-DPV1 COMMUNICATIONS CGCOMMUNICATIONS GUIDE

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.

3.3 369 Relay Profibus Input DataThere are two options for configuring what data is made available through Profibus Input Data, based on the value of the PROFIBUS CYCLIC IN DATA setpoint (see 369 Instruction Manual, chapter 5 for details). If the PROFIBUS CYCLIC IN DATA setpoint is set to 0 (default map), then the data available to be read matches Table CG1: Profibus Input Data on page CG7.

The user can also exactly define the data provided and the order of that data. The Modbus User Definable Memory Map area and the PROFIBUS CYCLIC IN DATA setpoint are used to define this data. The PROFIBUS CYCLIC IN DATA setpoint determines the number of 16-bit registers available to be read through Profibus Input Data and the Modbus User Definable Memory Map is used to determine the data provided and the order of the data.

For example, if the user only wishes to read two 16-bit registers of data (4 bytes), the user selects a number of Input Modules from the GSD file that add up to a total of 4 bytes. When the Profibus Master is reading the Input data, only 4 bytes of Input data will be sent in the communication packet. The number of words should match the PROFIBUS CYCLIC IN DATA setpoint, but it's not necessary. If the number of Input data bytes read from the master is greater than the user has defined with the PROFIBUS CYCLIC IN DATA setpoint, the balance of the data will return zero values.



FIGURE CG3: Slave Configuration Example 1 4 Bytes of Input Data

FIGURE CG4: Slave Configuration Example 2 220 Bytes of Input Data

3.4 369 Relay Profibus Output DataThe capability to force the output relays states has been implemented in cyclic output data. As cyclic data is continuously written, the 369 looks for a change in the value to execute the force relays command. Refer to the 369 Instruction Manual, chapter 5 for more information about the force output relays feature.


PROFIBUS-DPV1 COMMUNICATIONS CGCOMMUNICATIONS GUIDE

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

3.5 369 Relay Profibus DiagnosticsThe diagnostic data available for the Profibus-DPV1 option matches Table CG3: Profibus Diagnostics on page CG11. When no diagnostic information is available and the master initiates a diagnostics read, the six slave mandatory bytes are read.

3.6 369 Relay Profibus-DPV1 Acyclical CommunicationThe following items have been made available through Profibus-DPV1 acyclical communication. Data is addressed through the use of slot and index addressing. Three parameters are required to read or write data from the 369 Relay using a Profibus-DPV1 master:

1. Slot number

2. Index number

3. Data length (number of 16-bit words)

Table CG4: Profibus Output Data

OFFSET

CYCLIC DATA (ACTUAL VALUES)

LENGTH (BYTES)

MINIMUM MAXIMUM FORMAT CODE

VALUE HEX VALUE HEX

0 Force Output Relays 2 0 0 15 F F141



Note The value that is written acyclically to either FORCE OUTPUT RELAYS or BLOCK 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.

3.7 369 Relay Profibus-DPV1 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 operate on any combination of output relays. Refer to the following sections for more information regarding this feature:

369 Communications Guide: Section 2.5: Profibus-DP Loss Of Communication Trip

369 Instruction Manual: Chapter 5: 369 Communications (for information regarding the setpoints for this feature).

Table CG5: Profibus-DPV1 Acyclic Write Data

OBJECT SLOT INDEX LENGTH DESCRIPTION FORMAT

0 0 0 2 bytes Force Output Relays F141

2 2 bytes Block Protection Functions F180

Table CG6: Profibus-DPV1 Acyclic Read Data

OBJECT SLOT INDEX LENGTH DATA ITEM FORMAT

0 0

0 2 bytes Trip Relay Status F150

2 2 bytes Alarm Relay Status F150

4 2 bytes Aux1 Relay Status F150

6 2 bytes Aux2 Relay Status F150

8 2 bytes Functions Currently Blocked F141


DEVICENET PROTOCOL CGCOMMUNICATIONS GUIDE

4 DeviceNet Protocol

4.1 DeviceNet CommunicationsThe device profile is an extension of the Generic Device Profile (0x00). It is a group 2 only server. The MAC ID and baud rate are programmable through relay front panel or the EnerVista 369 Setup software. The polling function consumes one byte of control data (described under assembly object class 04, instance 96h) and produces data as per Poll Data Group 1, Poll Data Group 2, or the User-Defined poll data (described in assembly object class 04, instance 64h). The COS\CYC operation produces 4 bytes of data as per Class 4, Instance 66h, Attribute 3.

The EDS file for use with a DeviceNet master can be generated using the EnerVista 369 Setup program. The EDS file differs depending on which Poll Group is selected, and by the amount of data being returned for the User-Defined Poll Data. Note that only one version of the EDS file may be used for any one DeviceNet master.

The 369 Motor Management Relay supports following DeviceNet object classes.

DeviceNet Loss Of Communication Trip

If the 369 detects a failure in communicating with the DeviceNet master, the Fieldbus Loss of Communications feature can be used to trip any combination of output relays.

If the 369 DeviceNet communications is offline and not communicating with a master, then the Fieldbus Loss of Comms function (if enabled) will activate. This feature can be programmed for Latched or Unlatched operation.

If the Fieldbus Loss of Comms function is enabled , the 369 considers a DeviceNet loss of communication to have occurred in the following conditions:

1. Online; not connected

2. Critical link failure

3. Connection timeout.

Table CG7: DeviceNet Object Classes

CLASS Object

01h Identity

02h Message Router

03h DeviceNet

04h Assembly

05h Connection

2Bh Acknowledge Handler

A0h IO data Input Mapping

A1h IO data Output Mapping

B0h Parameter Data input Mapping

CGCOMMUNICATIONS GUIDE DEVICENET PROTOCOL


Note Critical link failure is caused by failure of CAN_H or CAN_L bus. To re-establish 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.


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.


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.




3. Assign Loss of Comms Relay


4.2 Poll DataThe polling function consumes one byte of control data and produces data as per Poll Data Group 1, Poll Data Group 2, or the User-Defined poll data. The control data format is as follows:

Bit Position Name Value

0 Motor Start 0.1

1 Motor Stop 0.1

2 Fault Reset 0.1

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

Note The corresponding command bit should be high for more than 500 ms to execute the 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:

Table CG8: Poll Data Group 1

Byte Description Length Units Format Default

1 Motor Status 1 - F172 0

2 Digital Input Status 1 - F173 0

3 Digital Output Status 1 - F174 0

4 Flag Change State 1 - F175 0

5 Thermal Capacity Used 1 % UINT 0

6 (low), 7 (high) Time to Trip 2 seconds F20 -1



1 Motor Status - Stopped, Starting, Running, Tripped

1 - F172 0

2,3 Cause of Last Trip 2 - F134 0

4,5 Average Phase Current 2 A F1 0

6,7 Ground Current 2 A F23 0

8,9 Average Line Voltage 2 V F1 0

10,11 Real Power (kW) 2 kW F4 0

12,13 Power Factor 2 - F21 0



User-Defined Poll Data

The user can also define exactly which data will be provided and the order in which that data is given. The Modbus User Definable Memory Map area (refer to Section 9.6.2: User Definable Memory Map Area on page 934) and the User-Defined Data Size setpoint are used to define this data and data size. The User-Defined Data Size setpoint determines the number of 16-bit registers available to be read through DeviceNet Poll Input Data and the Modbus User Definable Memory Map is used to determine the data provided and the order of the data.

For example, if the user only wishes to read two 16-bit registers of data (4 bytes), the user sets the DeviceNet Input Poll Data Group setpoint to User-Defined and then programs a value of 2 for the User-Defined Data Size setpoint. When the DeviceNet master reads the Poll Input data, 4 bytes of Input data will be read as follows.

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.

4.3 Change of State (COS)The COS data is described under class 4, instance 66h, attribute 3. The following data is provided:

14 Local Hottest Stator RTD Number 2 - F1 0

15,16 Local Hottest Stator RTD Temperature 2 c F4 0

17 Digital Input Status - Access Switch, Speed Switch, Spare Switch, Differential Switch, Emergency Switch, Reset Switch

1 - F173 0

18 Digital Output Status - Trip Relay, Alarm Relay, Aux Relay 1, Aux Relay 2

1 - F174 0



Byte Description Length

1 (Hi), 2 (Lo) User Defined Memory Map Register 1 1 word3 (Hi), 4 (lo) User Defined Memory Map Register 2 1 word


1 Motor Status 1 - F172 0

2 Digital Input Status 1 - F173 0

3 Digital Output Status 1 - F174 0

4 Flag Change State 1 - F175 0



4.4 Identity Object (class code 01h)Identity object, Class code 01h, Services.

Identity object, Class code 01h, Attributes.

Identity object, Class code 01h, Instance 01h, Attributes.

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).

4.5 Message Router (class code 02h)The message router (class code 2) object provides a messaging connection point through which a client may address a service to any object or instance residing in the physical device. There is no external visible interface to the message router object.

4.6 DeviceNet Object (class code 03h)DeviceNet object, Class code 03h, Services:

DeviceNet object, Class Code 03h, Attributes:

DeviceNet object, Class Code 03h, Instance 01h, Attributes:

CODE SERVICES AVAILABLE TO THIS OBJECT

NAME DESCRIPTION

0x05 Reset Reset the device to power up configuration

0x0E Get_Attribute_Single Returns the contents of the given attribute

ATTRIBUTE ACCESS NAME/DESCRIPTION DATA TYPE VALUE

01h Get Revision of Identity object UINT 1


01h Get Vendor ID UINT 928

02h Get Device Type UINT 003h Get Product Code UINT 5304h Get Revision (Major, Minor) USINT (2) 2.20

05h Get Status F178 ---

07h Get Product Name Short-String369 Motor Management Relay


NAME DESCRIPTION



01h Get Revision of DeviceNet object USINT 2


01h Get MAC ID USINT 0 to 63



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).

4.7 Assembly Object (class code 04h)Assembly object, Class code 04h, Services:

Assembly object, Class code 04h, Attributes.

Assembly object, Class code 04h, Instance 64h, Attributes.



02h Get Baud Rate USINT 0 = 125 kbps, 1 = 250 kbps,2 = 500 kbps

05h GetAllocation choice BYTE

Bit 0: explicit messagingBit 1: polled I/OBit 4: COS I/OBit 5: cyclic I/OBit 6: acknowledge suppression

Masters MAC ID USINT 0 to 63: address;255 = unallocated



NAME DESCRIPTION

0x0E Get_Attribute_Single Returns the contents of the given attribute0X10 Set_Attribute_Single Sets the contents of the given attribute


01h Get Revision of Assembly object UINT 202h Get Maximum instance number UINT 150


03h Get Motor data1

1. The data available through this Class/Instance/Attribute will depend on which Poll Group isused (see section 4.2: Poll Data).

bytes (7) see below


03h Get Flag change state byte see below

DATA FORMATS, FLAG CHANGE STATE

BIT POSITION NAME VALUES

0 Trip/alarm flag 0 = no change; 1 = trip or alarm1 to 7 Reserved ---


03h Get Digital data bytes (4) see below

DATA FORMATS, DIGITAL DATA

BYTE DESCRIPTION LENGTH UNITS FORMAT DEFAULT

1 Motor status 1 byte --- F172 0






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 stop2. Fault reset3. Motor start

The corresponding command bit should be high for more than 500 ms to execute the command.

2 Digital input status 1 byte --- F173 03 Digital output status 1 byte --- F174 0

4 Flag change state 1 byte --- F175 0


03h Get Thermal capacity used USINT %

ATTRIBUTE ACCESS NAME/DESCRIPTION DATA TYPE DATA FORMAT VALUE

03h Get Time to trip Word F20 1 second


03h Set Control byte 1 byte see below

DATA FORMATS, CONTROL BYTE

BIT POSITION NAME VALUE

0 Motor start 0, 1

1 Motor stop 0, 12 Fault reset 0, 13 Reserved ---

4 Reserved ---5 Reserved ---6 Reserved ---

7 Reserved ---





4.8 DeviceNet Connection Object (class code 05h)The connection objects manage the characteristics of each communication connection. There are two instances of the connection object in the device: explicit connection (



4.9 Acknowledge Handler Object (class code 2Bh)Acknowledge Handler Object, Class Code 2Bh, Services:

Acknowledge Handler object, Class code 2Bh, Attributes.

Acknowledge Handler object, Class code 2Bh, Instance 01h, Attributes:

4.10 I/O Data Input Mapping Object (class code A0h)I/O Data Input Mapping Object, Class code A0h, Services:

Input/Output Data Input Mapping object, Class code A0h, Attributes.

I/O Data Input Mapping object, Class code A0h, Instance 01h, Attributes:

0Dh Get Produced path length UINT 0x0006

0Eh Get Produced path BYTE [6] 0Fh Get Consumed path length UINT 0x000610h Get Consumed path BYTE [6]

11h Get Production inhibit timer UINT 0x0000


CODE NAME DESCRIPTION

0x0E Get_Attribute_Single Returns the contents of the given attribute0x10 Set_Attribute_Single Sets the contents of the given attribute


01h Get Revision of Acknowledge Handler object UINT 1

02h Get Maximum instance number UINT 1


01h Get Acknowledge timer UINT 16 ms02h Get Retry limit USINT 1




01h Get Revision of I/O Data Input Mapping object UINT 1

ATTRIBUTE ACCESS NAME/DESCRIPTION DATA TYPE DATA FORMAT

01h Get Motor data1

1. The data available through this Class/Instance/Attribute will depend on which Poll Group is used(see section 4.2: Poll Data)

bytes (7) see below

02h Get Flag change state byte F17503h Get Digital data bytes (4) see below

04h Get Thermal capacity used USINT %05h Get Time to trip Word F20



4.11 I/O Data Output Mapping Object (class code A1h)I/O Data Output Mapping Object, Class code A1h, Services:

I/O Data Input Mapping object, Class code A0h, Instance 01h, Attributes:

4.12 Parameter Data Input Mapping Object (class code B0h)Parameter Data Input Mapping object, Class code B0h, Services:

Parameter Data Input Mapping object, Class code B0h, Attributes.

Parameter Data Input Mapping object, Class code B0h, Instance 01h, Attributes:



1 Motor status 1 byte --- F172 02 Digital input status 1 byte --- F173 0

3 Digital output status 1 byte --- F174 04 Flag change state 1 byte --- F175 0



0x10 Set_Attribute_Single Sets the contents of the given attribute

ATTRIBUTE ACCESS NAME/DESCRIPTION DATA TYPE DATA FORMAT

01h Set Control byte 1 byte see below

DATA FORMATS, CONTROL BYTE

BIT POSITION NAME VALUES

0 Motor start 0, 11 Motor stop 0, 1

2 Fault reset 0, 13 Reserved ---4 Reserved ---

5 Reserved ---6 Reserved ---7 Reserved ---




01h Get Revision of Identity object UINT 1


01h Get Currents bytes (10) see below02h Get Current angles bytes (6) see below

03h Get Motor load bytes (6) see below04h Get Line voltages bytes (8) see below05h Get Phase voltages bytes (8) see below



06h Get Phase voltage angles bytes (6) see below

07h Get Frequency bytes (2) see below08h Get BSD state and frequency bytes (6) see below09h Get Power bytes (10) see below

0Ah Get Energy bytes (6) see below

0Bh Get Local hottest stator RTD and temperature bytes (4) see below

0Ch Get Local RTD temperatures bytes (24) see below0Dh Get Demand bytes (8) see below0Eh Get Peak values bytes (8) see below

0Fh Get Learned data bytes (14) see below10h Get Motor statistics bytes (8) see below11h Get Cause of trip bytes (2) see below

12h Get Last trip date and time bytes (8) see below13h Get Last pre-trip currents bytes (8) see below14h Get Last pre-trip motor load bytes (4) see below

15h Get Pre-trip local hottest stator RTD and temperature bytes (4) see below

16h Get Last pre-trip line voltages bytes (6) see below17h Get Last pre-trip phase voltages bytes (6) see below

18h Get Last pre-trip frequency bytes (2) see below19h Get Last pre-trip power bytes (8) see below1Ah Get Trip diagnostic data bytes (6) see below

1Bh Get Alarm diagnostic data bytes (8) see below1Ch Get Start block status data bytes (18) see below1Dh Get Actual values bytes (202) see below


DATA FORMATS FOR CLASS CODE B0H, INSTANCE 1 (Sheet 1 of 8)

ATTRIBUTE BYTES DESCRIPTION LENGTH FORMAT VALUE/UNIT

01hCURRENTS

1,2 (low, high) Phase Current Ia 16 bits UINT A3,4 (low, high) Phase Current Ib 16 bits UINT A

5,6 (low, high) Phase Current Ic 16 bits UINT A

7,8 (low, high) Average phase current Iav 16 bits UINT A

9,10 (low, high) Ground current Ig 16 bits F23 0.1 A or 0.01 A

02hCURRENT ANGLES

1,2 (low, high) Ia angle 16 bits UINT degrees3,4 (low, high) Ib angle 16 bits UINT degrees5,6 (low, high) Ic angle 16 bits UINT degrees

03hMOTOR LOAD

1,2 (low, high) Motor load 16 bits F3 0.01 FLA3,4 (low, high) Current unbalance 16 bits UINT %

5,6 (low, high) Unbalanced biased motor load (Ieq) 16 bits F3 0.01 FLA

04hLINE VOLTAGES

1,2 (low, high) Voltage Vab 16 bits UINT V3,4 (low, high) Voltage Vbc 16 bits UINT V

5,6 (low, high) Voltage Vca 16 bits UINT V7,8 (low, high) Average line voltage 16 bits UINT V



05hPHASE VOLTAGES

1,2 (low, high) Voltage Van 16 bits UINT V3,4 (low, high) Voltage Vbn 16 bits UINT V

5,6 (low, high) Voltage Vcn 16 bits UINT V

7,8 (low, high) Average phase voltage 16 bits UINT V

06hPHASE VOLTAGE ANGLES

1,2 (low, high) Va angle 16 bits UINT degrees3,4 (low, high) Vb angle 16 bits UINT degrees5,6 (low, high) Vc angle 16 bits UINT degrees

07hFREQUENCY 1,2 (low, high) Frequency 16 bits F3 0.01 Hz

08hBSD STATE AND FREQ.

1,2 (low, high) BSD state 16 bits F27 --3,4 (low, high) Backspin frequency 16 bits F3 0.01 Hz

5,6 (low, high) Backspin prediction timer 16 bits F1 s

09hPOWER

1,2 (low, high) Power factor 16 bits F21 0.01 PF3,4 (low, high) Real power (kW) 16 bits F4 kW

5,6 (low, high) Real power (hp) 16 bits UINT hp7,8 (low, high) Reactive power 16 bits F4 kvar9,10 (low, high) Apparent power 16 bits UINT kVA

0AhENERGY

1,2 (low, high) MWh 16 bits UINT MWh3,4 (low, high) Positive Mvarh 16 bits UINT Mvarh5,6 (low, high) Negative Mvarh 16 bits UINT Mvarh

0BhRTD TEMP-ERATURE

1,2 (low, high) Local hottest stator RTD 16 bits UINT ---

3,4 (low, high) Local hottest stator RTD temperature 16 bits F4 C

0ChLOCAL RTD TEMP-ERATURE

1,2 (low, high) Local RTD 1 temperature 16 bits F4 C
















0DhDEMAND

1,2 (low, high) Current demand 16 bits UINT A3,4 (low, high) Real power demand 16 bits UINT kW

5,6 (low, high) Reactive power demand 16 bits UINT kvar

7,8 (low, high) Apparent power demand 16 bits UINT kVA

0EhPEAK DEMAND

1,2 (low, high) Peak current demand 16 bits UINT A

3,4 (low, high) Peak real power demand 16 bits UINT kW

5,6 (low, high) Peak reactive power demand 16 bits UINT kvar

7,8 (low, high) Peak apparent power demand 16 bits UINT kVA

0FhLEARNED DATA

1,2 (low, high) Learned acceleration time 16 bits F2 x 0.1 seconds

3,4 (low, high) Learned starting current 16 bits UINT A

5,6 (low, high) Learned starting capacity 16 bits UINT %

7,8 (low, high) Learned running cool time constant 16 bits UINT minutes

9,10 (low, high) Learned stopped cool time constant 16 bits UINT minutes

11,12 (low, high) Last starting capacity 16 bits UINT %

13,14 (low, high) Learned unbalance k-factor 16 bits UINT --

10hMOTOR STATISTICS

1,2 (low, high) Number of starts 16 bits UINT --

3,4 (low, high) Number of restarts 16 bits UINT --5,6 (low, high) Digital counter 16 bits UINT --7,8 (low, high) Motor running hours 16 bits UINT hours

11hCAUSE OF LAST TRIP

1,2 (low, high) Cause of last trip 16 bits F134 --

12hLAST PRE-TRIP DATE AND TIME.

1 to 4(low, high) Last trip date 32 bits F18 --

5 to 8(low, high) Last trip time 32 bits F19 --

13hLAST PRE-TRIP CURRENTS

1,2 (low, high) Last pre-trip Ia 16 bits UINT A

3,4 (low, high) Last pre-trip Ib 16 bits UINT A5,6 (low, high) Last pre-trip Ic 16 bits UINT A7,8 (low, high) Last pre-trip Ig 16 bits F2 0.1 A

14hLAST PRE-TRIP MOTOR LOAD

1,2 (low, high) Last pre-trip motor load 16 bits F3 0.01 FLA

3,4 (low, high) Last pre-trip unbalance 16 bits UINT %

15hPRE-TRIP STATOR RTD TEMP.

1,2 (low, high) Local pre-trip hottest stator RTD 16 bits UINT ---

3,4 (low, high)Local pre-trip hottest stator RTD temperature

16 bits F4 C





16hLAST PRE-TRIP LINE VOLTAGES

1,2 (low, high) Last pre-trip Vab 16 bits UINT volts3,4 (low, high) Last pre-trip Vbc 16 bits UINT volts

5,6 (low, high) Last pre-trip Vca 16 bits UINT volts

17hLAST PRE-TRIP PHASE VOLTAGES

1,2 (low, high) Last pre-trip Van 16 bits UINT volts

3,4 (low, high) Last pre-trip Vbn 16 bits UINT volts5,6 (low, high) Last pre-trip Vcn 16 bits UINT volts

18hLAST PRE-TRIP FREQ.

1,2 (low, high) Last pre-trip frequency 16 bits F3 0.01 Hz

19hLAST PRE-TRIP POWER

1,2 (low, high) Last pre-trip kilowatts 16 bits F4 kW

3,4 (low, high) Last pre-trip kvar 16 bits F4 kvar5,6 (low, high) Last pre-trip KVA 16 bits UINT kVA

7,8 (low, high) Last pre-trip power factor 16 bits F21 0.01 PF

1AhTRIP DIAG. 6 bytes Trip diagnostic data 48 bits F176

1BhALARM DIAG. 8 bytes

Alarm diagnostic data 64 bits F177

1ChSTART BLOCK STATUS

1,2 (low, high) Overload lockout timer 16 bits UINT minutes

3,4 (low, high) Starts timer [1] 16 bits UINT minutes5,6 (low, high) Starts timer [2] 16 bits UINT minutes

7,8 (low, high) Starts timer [3] 16 bits UINT minutes9,10 (low, high) Starts timer [4] 16 bits UINT minutes11,12 (low, high) Starts timer [5] 16 bits UINT minutes

13,14 (low, high) Time between starts timer 16 bits UINT minutes

15,16 (low, high) Restart block timer 16 bits UINT seconds17,16 (low, high) Start inhibit timer 16 bits UINT minutes

1DhACTUAL VALUES

1,2 (low, high) Phase current Ia 16 bits UINT A

3,4 (low, high) Phase current Ib 16 bits UINT A5,6 (low, high) Phase current Ic 16 bits UINT A

7,8 (low, high) Average phase current Iav 16 bits UINT A

9,10 (low, high) Ground current Ig 16 bits F23 0.1 A or 0.01 A11,12 (low, high) Ia angle 16 bits UINT degrees

13,14 (low, high) Ib angle 16 bits UINT degrees15,16 (low, high) Ic angle 16 bits UINT degrees17,18 (low, high) Motor load 16 bits F3 0.01 FLA

19,20 (low, high) Current unbalance 16 bits UINT %

21,22 (low, high) Unbalanced biased motor load (Ieq) 16 bits F3 0.01 FLA

23,24 (low, high) Voltage Vab 16 bits UINT V





1DhACTUAL VALUEScontinued

25,26 (low, high) Voltage Vbc 16 bits UINT V

27,28 (low, high) Voltage Vca 16 bits UINT V

29,30 (low, high) Average line voltage 16 bits UINT V31,32 (low, high) Voltage Van 16 bits UINT V

33,34 (low, high) Voltage Vbn 16 bits UINT V35,36 (low, high) Voltage Vcn 16 bits UINT V

37,38 (low, high) Average phase voltage 16 bits UINT V

39,40 (low, high) Va angle 16 bits UINT degrees41,42 (low, high) Vb angle 16 bits UINT degrees43,44 (low, high) Vc angle 16 bits UINT degrees

45,46 (low, high) Frequency 16 bits F3 0.01 Hz47,48 (low, high) BSD state 16 bits F27 --49,50 (low, high) Backspin frequency 16 bits F3 0.01 Hz

51,52 (low, high) Backspin prediction timer 16 bits F1 seconds

53,54 (low, high) Power factor 16 bits F21 0.01 PF55,56 (low, high) Real power (kW) 16 bits F4 kW

57,58 (low, high) Real power (hp) 16 bits UINT hp59,60 (low, high) Reactive power 16 bits F4 kvar61,62 (low, high) Apparent power 16 bits UINT kVA

63,64 (low, high) MWh 16 bits UINT MWh65,66 (low, high) Positive Mvarh 16 bits UINT Mvarh67,68 (low, high) Negative Mvarh 16 bits UINT Mvarh

69,70 (low, high) Local Hottest stator RTD 16 bits UINT ---


71,72 (low, high) Local Hottest stator RTD temperature 16 bits F4 C

















97,98 (low, high) Current demand 16 bits UINT A99,100 (low, high) Real power demand 16 bits UINT kW101,102 (low, high)

Reactive power demand 16 bits F4 kvar

103, 104 (low, high)

Apparent power demand 16 bits UINT kVA

105, 106 (low, high)

Peak current demand 16 bits UINT A

107, 108 (low, high)

Peak real power demand 16 bits UINT kW

109, 110 (low, high)

Peak reactive power demand 16 bits F4 kvar

111,112 (low, high)

Peak apparent power demand 16 bits UINT kVA

113,114 (low, high)

Learned acceleration time 16 bits F2 0.1 seconds

115,116 (low, high)

Learned starting current 16 bits UINT A

117,118 (low, high)

Learned starting capacity 16 bits UINT %


119,120 (low, high)

Learned running cool time constant 16 bits UINT minutes

121,122 (low, high)

Learned stopped cool time constant 16 bits UINT minutes

123,124 (low, high)

Last starting capacity 16 bits UINT %

125,126 (low, high)

Learned unbalance k-factor 16 bits UINT --

127,128 (low, high) Number of starts 16 bits UINT --

129,130 (low, high) Number of restarts 16 bits UINT --

131,132 (low, high) Digital counter 16 bits UINT --

133,134 (low, high) Motor running Hours 16 bits UINT hours

135,136 (low, high) Cause of last trip 16 bits F134 --

137 to 140 (low, high) Last trip date 32 bits F18 --

141 to 144 (low, high) Last trip time 32 bits F19 --

145, 146 (low, high) Last pre-trip Ia 16 bits UINT A





147, 148 (low, high) Last pre-trip Ib 16 bits UINT A

149, 150 (low, high) Last Pre-trip Ic 16 bits UINT A

151, 152 (low, high) Last Pre-trip Ig 16 bits F2 0.1 A

153, 154 (low, high)

Last pre-trip motor load 16 bits F3 0.01 FLA

155, 156 (low, high)

Last pre-trip unbalance 16 bits UINT %

157, 158 (low, high)

Last pre-trip local hottest stator RTD 16 bits UINT ---

159, 160 (low, high)

Last pre-trip local hottest stator RTD temperature

16 bits F4 C

161, 162 (low, high) Last pre-trip Vab 16 bits UINT volts

163, 164 (low, high) Last pre-trip Vbc 16 bits UINT volts

165, 166 (low, high) Last pre-trip Vca 16 bits UINT volts

167, 168 (low, high) Last pre-trip Van 16 bits UINT volts


169, 170 (low, high) Last pre-trip Vbn 16 bits UINT volts

171, 172 (low, high) Last pre-trip Vcn 16 bits UINT volts

173, 174 (low, high)

Last pre-trip frequency 16 bits F3 0.01 Hz

175, 176 (low, high)

Last pre-trip kilowatts 16 bits F4 kW

177, 178 (low, high) Last pre-trip kvar 16 bits F4 kvar

179, 180 (low, high) Last pre-trip KVA 16 bits UINT kVA

181, 182 (low, high)

Last pre-trip power factor 16 bits F21 0.01 PF

183 to 188 Trip diagnostic data 48 bits F176

189 to 196 Alarm diagnostic data 64 bits F177

197, 198 (low, high)

Overload lockout timer 16 bits UINT minutes

199, 200 (low, high) Starts timer [1] 16 bits UINT minutes









4.13 DeviceNet Loss Of Communication Trip If the 369 detects a problem in communicating with the DeviceNet master, the DeviceNet Loss of Communications feature can be used to operate on any combination of output relays.

If the 369 DeviceNet communications is offline and not communicating with a master, then the Fieldbus Loss of Comms function (if enabled) will activate. This feature can be programmed for Latched or Unlatched operation.


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.


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.




3. Assigned Fieldbus Loss of Comms Relay

Refer to the 369 Instruction Manual, Chapter 5: 369 Relay Communications for more information on these setpoints.

209, 210 (low, high)

Time between starts timer 16 bits UINT minutes

211, 212 (low, high) Restart block timer 16 bits UINT seconds

213, 214 (low, high) Start inhibit timer 16 bits UINT minutes





4.14 DeviceNet Data Formats

FORMAT VALUE NAME/DESCRIPTION

F167 Network status: unsigned 16 bit integer

0 Power off / Not online1 Online, Connected

2 Link failure3 Not defined

F168 Connection status: unsigned 16 bit integer

0 Nonexistent1 Configuring

2 (Not used)3 Established4 Timed out

5 Deferred deleteF170 DeviceNet baud rate: unsigned 16 bit integer

0 125 kbps1 250 kbps2 500 kbps

F172 Motor status: Unsigned 8 bit integer

Bit 0 Stopped

Bit 1 StartingBit 2 RunningBit 3 Overloaded

Bit 4 TrippedBits 5 to 7 Reserved

F173 Digital input status: unsigned 8 bit integer

Bit 0 Access Switch Status0 = Open, 1= Closed

Bit 1 Speed Switch Status0 = Open, 1= Closed

Bit 2 Spare Switch Status0 = Open, 1= Closed

Bit 3 Differential Switch Status0 = Open, 1= Closed

Bit 4 Emergency Switch status0 = Open, 1= Closed

Bit 5 Reset Switch Status0 = Open, 1= ClosedBit 6 ReservedBit 7 Reserved

F174 Output relay status: unsigned 8 bit integer

Bit 0 Trip Relay Status0 = De-energized, 1 = Energized

Bit 1 Alarm Relay Status0 = De-energized, 1 = Energized

Bit 2 Aux1 Relay Status0 = De-energized, 1 = Energized

Bit 3 Aux2 Relay Status0 = De-energized, 1 = Energized



Bits 4 to 7 ReservedF175 Flag change state: unsigned 8 bit integer

Bit 0 Trip/Alarm status; 1= operated

Bits 1 to 7 ReservedF176 Relay trips: bitmask

Byte 1 Bit 0 Single Phasing TripBit 1 Spare Switch Trip

Bit 2 Emergency Switch TripBit 3 Differential Switch TripBit 4 Speed Switch Trip

Bit 5 Reset Switch TripBit 6 ReservedBit 7 Overload Trip

Byte 2 Bit 0 Short Circuit TripBit 1 Short Circuit Backup TripBit 2 Mechanical Jam Trip

Bit 3 Undercurrent TripBit 4 Current Unbalance TripBit 5 Ground Fault Trip

Bit 6 Ground Fault Backup TripBit 7 Reserved

Byte 3 Bit 0 Acceleration Timer Trip

Bit 1 RTD 1 TripBit 2 RTD 2 TripBit 3 RTD 3 Trip


Bit 7 RTD 7 TripByte 4 Bit 0 RTD 8 Trip

Bit 1 RTD 9 Trip


Bit 5 Undervoltage TripBit 6 Overvoltage TripBit 7 Voltage Phase Reversal Trip

F176ctd. Byte 5 Bit 0 Underfrequency Trip

Bit 1 Overfrequency TripBit 2 Lead Power Factor Trip

Bit 3 Lag Power Factor TripBit 4 Positive kvar TripBit 5 Negative kvar Trip

Bit 6 Underpower TripBit 7 Reverse Power Trip




Byte 6 Bit 0 Incomplete Sequence Trip

Bit 1 ReservedBit 2 ReservedBit 3 Reserved

Bit 4 ReservedBit 5 Reserved

Bit 6 ReservedBit 7 Reserved

F177 Relay alarms: bitmask

Byte 1 Bit 0 Spare Switch AlarmBit 1 Emergency Switch Alarm

Bit 2 Differential Switch AlarmBit 3 Speed Switch AlarmBit 4 Reset Switch Alarm

Bit 5 ReservedBit 6 Thermal Capacity AlarmBit 7 Overload Alarm

Byte 2 Bit 0 Mechanical Jam AlarmBit 1 Undercurrent AlarmBit 2 Current Unbalance Alarm

Bit 3 Ground Fault AlarmBit 4 Undervoltage AlarmBit 5 Overvoltage Alarm

Bit 6 Overfrequency AlarmBit 7 Underfrequency Alarm

Byte 3 Bit 0 Lead Power Factor Alarm

Bit 1 Lag Power Factor AlarmBit 2 Positive kvar AlarmBit 3 Negative kvar Alarm

Bit 4 Underpower AlarmBit 5 Reverse Power AlarmBit 6 RTD 1 Alarm

Bit 7 RTD 2 AlarmF177ctd. Byte 4 Bit 0 RTD 3 Alarm

Bit 1 RTD 4 AlarmBit 2 RTD 5 Alarm

Bit 3 RTD 6 AlarmBit 4 RTD 7 AlarmBit 5 RTD 8 Alarm

Bit 6 RTD 9 AlarmBit 7 RTD 10 Alarm

Byte 5 Bit 0 RTD 11 AlarmBit 1 RTD 12 AlarmBit 2 RTD 1 High Alarm




Bit 3 RTD 2 High Alarm

Bit 4 RTD 3 High AlarmBit 5 RTD 4 High AlarmBit 6 RTD 5 High Alarm

Bit 7 RTD 6 High AlarmByte 6 Bit 0 RTD 7 High Alarm

Bit 1 RTD 8 High AlarmBit 2 RTD 9 High AlarmBit 3 RTD 10 High Alarm

Bit 4 RTD 11 High AlarmBit 5 RTD 12 High AlarmBit 6 Open RTD Sensor Alarm

Bit 7 Short RTD AlarmByte 7 Bit 0 Trip Counters Alarm

Bit 1 Starter Failure Alarm

Bit 2 Current Demand AlarmBit 3 kW Demand AlarmBit 4 kvar Demand Alarm

Bit 5 kVA Demand AlarmBit 6 Digital Counter AlarmBit 7 Overload Lockout Block

Byte 8 Bit 0 Start Inhibit BlockBit 1 Starts Hour BlockBit 2 Time Between Starts Block

Bit 3 Restart BlockBit 4 ReservedBit 5 Back-Spin Block

Bit 6 Loss of Remote RTD CommunicationBit 7 Spare Switch Alarm

F178 DeviceNet Communication status: unsigned 16 bit integer

Bit 0 0 = not owned,1 = owned by master

Bit 1 Reserved

Bit 2 0 = factory default, 1= configuredBits 3 to 7 Reserved

Bit 8 1 = Minor recoverable faultBit 9 1 = Minor unrecoverable faultBit 10 1 = Major recoverable fault

Bit 11 1 = Major unrecoverable faultBits 12 to 15 Reserved



MODBUS RTU PROTOCOL CGCOMMUNICATIONS GUIDE

5 Modbus RTU Protocol

5.1 Data Frame Format and Data Rate One data frame of an asynchronous transmission to or from an 369 is default to 1 start bit, 8 data bits, and 1 stop bit . This produces a 10 bit data frame. This is important for transmission through modems at high bit rates (11 bit data frames are not supported by Hayes modems at bit rates of greater than 300 bps). The parity bit is optional as odd or even. If it is programmed as odd or even, the data frame consists of 1 start bit, 8 data bits, 1 parity bit, and 1 stop bit.

Modbus protocol can be implemented at any standard communication speed. The 369 RS485, fiber optic and RS232 ports support operation at 1200, 2400, 4800, 9600, and 19200 baud.

5.2 Data Packet Format A complete request/response sequence consists of the following bytes (transmitted as separate data frames):

Master Request Transmission:

SLAVE ADDRESS - 1 byteFUNCTION CODE - 1 byteDATA - variable number of bytes depending on FUNCTION CODECRC - 2 bytes

Slave Response Transmission:

SLAVE ADDRESS - 1 byteFUNCTION CODE - 1 byteDATA - variable number of bytes depending on FUNCTION CODECRC - 2 bytes

SLAVE ADDRESS: This is the first byte of every transmission. It represents the user-assigned address of the slave device that is to receive the message sent by the master. Each slave device must be assigned a unique address and only the addressed slave will respond to a transmission that starts with its address. In a master request transmission the SLAVE ADDRESS represents the address of the slave to which the request is being sent. In a slave response transmission the SLAVE ADDRESS represents the address of the slave that is sending the response. Note: A master transmission with a SLAVE ADDRESS of 0 indicates a broadcast command. Broadcast commands can be used for specific functions.

FUNCTION CODE: This is the second byte of every transmission. The modbus protocol defines function codes of 1 to 127. The 369 implements some of these functions. In a master request transmission the FUNCTION CODE tells the slave what action to perform. In a slave response transmission if the FUNCTION CODE sent from the slave is the same as the FUNCTION CODE sent from the master indicating the slave performed the function as requested. If the high order bit of the FUNCTION CODE sent from the slave is a 1 (i.e. if the FUNCTION CODE is > 127) then the slave did not perform the function as requested and is sending an error or exception response.

CGCOMMUNICATIONS GUIDE MODBUS RTU PROTOCOL


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.

5.3 Error Checking The RTU version of Modbus includes a two byte CRC-16 (16 bit cyclic redundancy check) with every transmission. The CRC-16 algorithm essentially treats the entire data stream (data bits only; start, stop and parity ignored) as one continuous binary number. This number is first shifted left 16 bits and then divided by a characteristic polynomial (11000000000000101B). The 16 bit remainder of the division is appended to the end of the transmission, LSByte first. The resulting message including CRC, when divided by the same polynomial at the receiver will give a zero remainder if no transmission errors have occurred.

If an 369 Modbus slave device receives a transmission in which an error is indicated by the CRC-16 calculation, the slave device will not respond to the transmission. A CRC-16 error indicates than one or more bytes of the transmission were received incorrectly and thus the entire transmission should be ignored in order to avoid the 369 performing any incorrect operation.

The CRC-16 calculation is a

gek-113493c.pdf

Documents

relay profibus configuration

relay profibus diagnostics

relay profibusdp diagnostics

relay profibus input

relay profibus output

property of ge multilin

ge multilin incorporated

permission of ge multilin