Вы находитесь на странице: 1из 5

GE Consumer & Industrial

369 Motor Management

Product Release Notes
GE Publication Number: GER-4071
Copyright © 2005 GE Multilin


• Affected products: 369 Motor Management Relay
• Date of release: November 18, 2005
• Firmware revision: 2.40
• Manual revision: GEK-106288F

Release summary
This release note covers the version 2.40 release of the 369 Motor Management Relay. This release includes the
following changes: Profibus-DPV1 communication protocol, the “Force Output Relays” control feature, Protection
Function Blocking feature, and custom curve enhancements.

GE Multilin technical support

GE Multilin contact information and call center for product support is shown below:
GE Multilin
215 Anderson Avenue
Markham, Ontario
Canada L6E 1B3
Telephone: 905-294-6222 or 1-800-547-8629 (North America), +34 94 485 88 00 (Europe)
Fax: 905-201-2098 (North America), +34 94 485 88 45 (Europe)
E-mail: multilin.tech@ge.com
Home Page: http://www.GEmultilin.com

GE Multilin 1
Release details 369 revision 2.40 release notes

Release details

New features
Communications: Profibus-DPV1 protocol support
The 369 Motor Management Relay now supports the optional Profibus-DPV1 protocol as a slave that can be read
by a Profibus master.
The relay supports following configuration.
• Fieldbus type: Profibus-DPV1 (IEC 61158 Type 3, and IEC 61784)
• Function support: Cyclic Input/Output Data, Acyclic Read/Write, and Extended Diagnostic data
• Auto baud rate detection: 9.6Kbps to 12Mbps
• Address range: 1 to 126, set via the EnerVista 369 Setup software or front keypad
Cyclic Input Data:
There are two options for configuring what data is made available through Profibus Input Data reads, based on
the value of the PROFIBUS CYCLIC IN DATA setpoint (see the 369 Communications section on page 5-5 of the
manual for details). If the PROFIBUS CYCLIC IN DATA setpoint is set to “Default Map”, then the data available to read
matches a predefined data set (refer to Table 9-1: Profibus Input Data on page 9-5 of the manual).
The user can also define the data provided and the order of that data. The Modbus User Definable Memory Map
area (refer to the User Definable Memory Map Area section on page 9-34 of the manual) 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 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.
Cyclic Output Data:
The 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.
Acyclic Read/Write:
The following new features are available with the 2.30 release of the 369 (“Force Output Relays” and “Protection
Function Blocking”) via Profibus acyclical communications. Refer to the tables below.

Table 1: Profibus-DPV1 acyclic write data

0 0 0 2 bytes Force Output Relays F141
2 2 bytes Block Protection Functions F180

2 GE Multilin
369 revision 2.40 release notes Release details

Table 2: Profibus-DPV1 acyclic read data

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

Refer to Section 9.2.1 Profibus Communication Options of the 369 manual for additional information. The 369
Profibus-DPV1 GSD file can be found on the web at:

Custom curves: custom curve feature enhanced for 2.40 release

It may be necessary to use a custom curve to ensure successful starting without compromising motor protection.
The custom overload curve of the 369 allows the user to program their own curve by entering trip times for 30
predetermined current levels and then “smoothes” the areas between these points to make the protection curve.
The custom curve settings have been enhanced modified from “0 to 32767 seconds” to “0 to 65534 seconds”.
This change is reflected in the 369 memory map for the 2.40 (and above) release, and affects all trip ranges in
memory map addresses 0x15B0 through 0x15EA.

Force Output Relays: functionality added for 2.30 release

The force output relays function allows the user to energize and de-energize output relays for the purpose of
control via remote communications through the following methods:
1. Profibus-DPV1 acyclical communication
2. Profibus-DPV1 cyclical communication
3. Modbus command 21
To allow the forcing of relay states, the ASSIGN COMMS FORCE RELAY setting must be programmed. Only relays
assigned under this setpoint can be forced through Modbus or Profibus-DPV1 communications. Commands can
be sent to energize or de-energize any of the four output relays. A bit value of “1” for the corresponding relay will
energize that relay; a bit value of “0” will de-energize that relay. The COM FORCE O/P TYPE setting for each relay
determines whether it remains latched in the state sent through the command, or whether it operates for the
duration programmed in the associated PULSED OP DWELL TIME setting. Refer to the Force Output Relays section
on page 5-23 of the manual additional information on this feature.

Protection Function Blocking: added for 2.30 release

The Protection Function Blocking feature allows the user to block protection functions through the following
1. Profibus-DPV1 acyclical communication
2. Modbus command 20
3. Modbus setpoints
4. The front panel interface

GE Multilin 3
Release details 369 revision 2.40 release notes

The protection functions that can be blocked are indicated in the following table.

Table 3: ANSI/IEEE Device Number

37 Undercurrent/underpower
46 Current unbalance
48 Incomplete sequence
49 Thermal model
50 Short circuit and backup
51 Overload alarm
51G Ground fault
66 Starts per hour / time between starts

Blocking a protection function is essentially the same as disabling it. If the protection function is blocked and a
situation occurs where it would have been activated (if enabled), no indication will be given and no events are
recorded. If the protection function has picked up and/or is timing out, the internal timers will be reset to zero.
If the LOG BLOCKING EVENTS setpoint is enabled, an event will be stored indicating when a function changes from
being blocked to unblocked, or vice versa.

Modified features
Ethernet: Ethernet communications functionality modified
For 369 versions 2.30 and below with the Ethernet option, the 369 communications port will stop operating and
will require user intervention if the user requests more than 123 registers; protection is not affected. With the 2.40
release, the 369 will support a request for a maximum of 123 registers, corresponding to a packet size of 246
bytes (i.e. 123 registers + 9 bytes of overhead information for total packet size of 255 bytes). If the user requests
more than 123 registers through the Ethernet port, the relay will return Modbus Exception Code 0x01: Illegal

4 GE Multilin
369 revision 2.40 release notes Upgrading firmware/software

Ordering: order code modified for Profibus-DPV1 communications

The 369 order code has been modified for the Profibus-DPV1 communications protocol option. The updated order
code is shown below.

Table 4: 369 order codes

369 – * – * – * – * – * – *
Base unit 369 | | | | | | 369 revision 2.40 release notes (no RTD)
Control power HI | | | | | 50 to 300 V DC / 40 to 265 V AC
LO | | | | | 20 to 60 V DC / 20 to 48 V AC
RTD inputs R | | | | 12 optional RTD inputs (built-in)
0 | | | | No RTD inputs
Metering / M | | | Optional metering package
backspin detection B | | | Optional backspin detection (includes metering)
0 | | | No metering or backspin detection
Fiber optic port F | | Optional fiber optic port
0 | | No fiber optic port
Communication protocol E | Optional Modbus/TCP protocol interface
P | Optional Profibus-DP protocol interface
P1 | Optional Profibus-DPV1 protocol interface
D | Optional DeviceNet protocol interface
0 | No protocol interfaces
Harsh environment H Harsh environment option
0 No harsh environment option

Upgrading firmware/software

Software and firmware information

Firmware file location and name
File location: http://www.GEindustrial.com/products/software/369/
File name: 53CMB240.000

Software location and file name

File location: http://www.GEindustrial.com/multilin/software/369
File name: 369SETUP330.EXE

Settings file maintenance

Settings files can be updated for version 2.30 firmware using the EnerVista 369 Setup software.

Firmware Upgrade
Use the EnerVista 369 Setup software to upgrade to the latest firmware version.

Software Upgrade
The latest EnerVista 369 Setup installation file can be downloaded from

GE Multilin 5