Gek 106491e
Gek 106491e
g
GE Industrial Systems
T
GIS ERE
RE
GE Multilin ISO9001:2000
215 Anderson Avenue, Markham, Ontario EM I
G
U LT I L
Canada L6E 1B3
Tel: (905) 294-6222 Fax: (905) 201-2098 GE Multilin's Quality Management
System is registered to
Internet: http://www.GEmultilin.com ISO9001:2000
QMI # 005094
UL # A3775
Table of Contents
469
Communications Guide
Table of Contents
GE Multilin http://www.GEindustrial.com/multilin i
469 Table of Contents
Communications Guide
ii http://www.GEindustrial.com/multilin GE Multilin
Modbus Protocol 469
Communications Guide
469 Communications
Guide
GE Publication Code: GEK-106491D
Copyright © 2008 GE Multilin
Modbus Protocol
Electrical Interface The hardware or electrical interface is one of the following: one of two 2-wire RS485
ports from the rear terminal connector or the RS232 from the front panel connector.
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 Ω 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 Ω 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 469 must be connected together for the system to operate. See Chapter 2
of the 469 manual for details on correct serial port wiring.
Modbus RTU Protocol The 469 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 469 interfaces include two 2-wire RS485
ports and one 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 469 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 469. Monitoring, programming and control functions are possible
using read and write register commands.
Data Frame Format and One data frame of an asynchronous transmission to or from an 469 is default to 1
Data Rate 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
469 RS485/RS232 ports support operation at 1200, 2400, 4800, 9600, and 19200
baud.
GE Multilin http://www.GEmultilin.com 1
469 Modbus Protocol
Communications Guide
Data Packet Format A complete request/response sequence consists of the following bytes (transmitted
as separate data frames):
MASTER QUERY MESSAGE:
SLAVE ADDRESS: (1 byte)
FUNCTION CODE: (1 byte)
DATA: (variable number of bytes depending on FUNCTION CODE)
CRC: (2 bytes)
SLAVE RESPONSE MESSAGE:
SLAVE ADDRESS: (1 byte)
FUNCTION CODE: (1 byte)
DATA: (variable number of bytes depending on FUNCTION CODE)
CRC: (2 bytes)
• SLAVE ADDRESS: This is the first byte of every transmission. This byte
represents the user-assigned address of the slave device that receives the
message sent by the master. Each slave device must be assigned a unique
address and only the addressed slave responds 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 that 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. Modbus
defines function codes of 1 to 127. The 469 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.
• DATA: 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 vice
versa. 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. 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 469 Modbus slave device receives a transmission in which an error is indi-
cated by the CRC-16 calculation, the slave device will not respond to the trans-
mission. 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 469 performing any incorrect operation. The CRC-16 calcula-
tion is an industry standard method used for error detection. An algorithm is
included here to assist programmers in situations where no standard CRC-16
calculation routines are available.
2 http://www.GEmultilin.com GE Multilin
Modbus Functions 469
Communications Guide
CRC-16 Algorithm Once the following algorithm is complete, the working register “A” will contain the
CRC value to be transmitted. Note that this algorithm requires the characteristic
polynomial to be reverse bit ordered. The MSbit of the characteristic polynomial is
dropped since it does not affect the value of the remainder.
The symbols used in the algorithm are shown below:
--> data transfer
A; Alow; Ahigh 16-bit working register; low and high order bytes of A (the 16-bit
working register)
CRC 16 bit CRC-16 result
i, j loop counters
(+) logical EXCLUSIVE-OR operator
N total number of data bytes
Di i-th data byte (i = 0 to N – 1)
G 16 bit characteristic polynomial = 1010000000000001 (binary)
with MSbit dropped and bit order reversed
shr (x) right shift operator (the LSbit of x is shifted into a carry flag, a '0' is
shifted into the MSbit of x, all other bits are shifted right one
location)
The CRC algorithm is shown below:
1. FFFF (hex) --> A
2. 0 --> i
3. 0 --> j
4. Di (+) Alow --> Alow
5. j + 1 --> j
6. shr (A)
7. Is there a carry? No: go to step 8.
Yes: G (+) A --> A and continue.
8. Is j = 8? No: go to 5.
Yes: continue.
9. i + 1 --> i
10. Is i = N? No: go to 3.
Yes: continue.
11. A --> CRC
Modbus Functions
Supported Functions The following functions are supported by the 469:
Modbus Function Code 01: Read Relay Coil
Modbus Function Code 02: Read Digital Input Status
Modbus Function Code 03: Read Setpoints and Actual Values
Modbus Function Code 04: Read Setpoints and Actual Values
Modbus Function Code 05: Execute Operation
Modbus Function Code 06: Store Single Setpoint
Modbus Function Code 07: Read Device Status
Modbus Function Code 08: Loopback Test
Modbus Function Code 16: Store Multiple Setpoints
GE Multilin http://www.GEmultilin.com 3
469 Modbus Functions
Communications Guide
Read Relay Coil / Digital Modbus implementation: Read Coil and Input Status
Input Status 469 Implementation: Read Relay Coil and Digital Input Status
For the 469 implementation of Modbus, these commands can be used to read Relay
Coil Status or Digital Input Status.
MESSAGE FORMAT AND EXAMPLE, FUNCTION 01:
The standard implementation requires the following: slave address (one byte),
function code (one byte), starting relay coil (two bytes), number of coils to read
(two bytes), and CRC (two bytes). The slave response is the slave address (one
byte), function code (one byte), relay coil mask byte count (one byte; always 01
since only six relay coils), bit mask indicating the status of requested relay coils
(one byte), and CRC (two bytes).
Request slave 11 to respond with status of relay coil 3 to 5:
Relay Status
1 TRIP Energized
2 AUXILIARY De-energized
3 AUXILIARY De-energized
4 ALARM De-energized
5 BLOCK START Energized
6 SERVCE Energized
Bit Mask 0011 0001 (0 × 31)
If a Starting Relay Coil (Starting Digital Input) of “0” is entered, the 469 will default
it to “1”. If the Number of Relays (Number of Digital Inputs) requested exceeds the
NOTE number of relays available, the user is prompted with a ILLEGAL DATA message.
MESSAGE FORMAT AND EXAMPLE, FUNCTION 02:
The standard implementation requires the following: slave address (one byte),
function code (one byte), starting digital input (two byte), number of digital inputs
to read (two bytes), and CRC (two bytes). The slave response is the slave address
(one byte), function code (one byte), byte count of digital input mask (one byte), bit
mask indicating the status of requested digital inputs (one or two bytes), and CRC
(two bytes).
The CRC is sent as a two byte number with the low order byte sent first.
NOTE
4 http://www.GEmultilin.com GE Multilin
Modbus Functions 469
Communications Guide
GE Multilin http://www.GEmultilin.com 5
469 Modbus Functions
Communications Guide
Read Setpoints and Modbus implementation: Read Input and Holding Registers
Actual Values 469 Implementation: Read Setpoints and Actual Values
For the 469 implementation of Modbus, these commands can be used to read any
setpoint (“holding registers”) or actual value (“input registers”). Holding and input
registers are 16 bit (two byte) values transmitted high order byte first. Thus all 469
setpoints and actual values are sent as two bytes. The maximum number of
registers that can be read in one transmission is 125. Function codes 03 and 04 are
configured to read setpoints or actual values interchangeably because some PLCs do
not support both function codes.
The slave response to these function codes is the slave address, function code, a
count of the number of data bytes to follow, the data itself and the CRC. Each data
item is sent as a two byte number with the high order byte sent first. The CRC is
sent as a two byte number with the low order byte sent first.
MESSAGE FORMAT AND EXAMPLE:
Request slave 11 to respond with 2 registers starting at address 0308. For this
example the register data in these addresses is:
Address Data
0308 0064
0309 000A
6 http://www.GEmultilin.com GE Multilin
Modbus Functions 469
Communications Guide
GE Multilin http://www.GEmultilin.com 7
469 Modbus Functions
Communications Guide
If status is neither stopped or running, the motor is starting or has been tripped.
MESSAGE FORMAT AND EXAMPLE:
Request status from slave 11.
8 http://www.GEmultilin.com GE Multilin
Modbus Functions 469
Communications Guide
Address Data
1180 01F4
1181 01DE
Performing Commands Some PLCs may not support execution of commands using function code 5 but do
support storing multiple setpoints using function code 16. To perform this operation
using function code 16 (10H), a certain sequence of commands must be written at
the same time to the 469. The sequence consists of: command function register,
command operation register and command data (if required). The command
function register must be written with the value of 5 indicating an execute operation
is requested. The command operation register must then be written with a valid
command operation number from the list of commands shown in the memory map.
The command data registers must be written with valid data if the command
operation requires data. The selected command will execute immediately upon
receipt of a valid transmission.
GE Multilin http://www.GEmultilin.com 9
469 Modbus Functions
Communications Guide
Error Responses When an 469 detects an error other than a CRC error, a response will be sent to the
master. The MSbit of the Function Code byte will be set to 1 (i.e. the function code
sent from the slave will be equal to the function code sent from the master plus
128). The following byte will be an exception code indicating the type of error that
occurred.
Transmissions received from the master with CRC errors will be ignored by the 469.
The slave response to an error (other than CRC error) will be:
SLAVE ADDRESS: 1 byte
FUNCTION CODE: 1 byte (with MSbit set to 1)
EXCEPTION CODE: 1 byte
CRC: 2 bytes
The 469 implements the following exception response codes.
01: ILLEGAL FUNCTION
The function code transmitted is not one of the functions supported by the 469.
02: ILLEGAL DATA ADDRESS
The address referenced in the data field transmitted by the master is not an
allowable address for the 469.
03: ILLEGAL DATA VALUE
The value referenced in the data field transmitted by the master is not within range
for the selected data address.
10 http://www.GEmultilin.com GE Multilin
Modbus Memory Map 469
Communications Guide
User-Definable Memory The 469 has a powerful feature, called the User Definable Memory Map, which
Map Area allows a computer to read up to 125 non-consecutive data registers (setpoints or
actual values) by using one Modbus packet. It is often necessary for a master
computer to continuously poll various values in each of the connected slave relays.
If these values are scattered throughout the memory map, reading them would
require numerous transmissions and would burden the communication link. The
User Definable Memory Map can be programmed to join any memory map address
to one in the block of consecutive User Map locations, so that they can be accessed
by reading these consecutive locations.
The User Definable area has two sections:
1. User-Definable Addresses 1 to 125 (memory map registers 0180h to 01FCh)
that contain 125 actual values or setpoints register addresses.
2. User-Definable Values 1 to 125 (memory map registers 0100h to 017Ch) that
contains the data in the corresponding user-definable addresses.
Register data that is separated in the rest of the memory map may be remapped to
adjacent register addresses in the values area. This is accomplished by writing to
register addresses in the user-definable address area. This improves data
throughput and can eliminate the need for multiple read command sequences.
For example, if the values of Average Phase Current (register address 0306h) and
Hottest Stator RTD Temperature (register address 0320h) are required to be read
from an 469, their addresses may be remapped as follows:
1. Write 0306h to address 0180h (User Definable Address #1) using function code
06 or 16.
2. Write 0307h to address 0181h (User Definable Address #2) using function code
06 or 16 (Average Phase Current is a double register number).
3. Write 0320h to address 0182h (User Definable Address #3) using function code
06 or 16.
A read (function code 03 or 04) of registers 0100h (User Definable Address #1) and
0101h (User Definable Address #2) will return the Phase A Current and register
0102h (User Definable Address #3) will return Hottest Stator RTD Temperature.
Event Recorder The 469 event recorder data starts at address 3000h. Address 3003h is a pointer to
the event of interest (1 representing the latest event and 256 representing the
oldest event). To retrieve Event 1, write ‘1’ to the Event Record Selector (3003h)
and read the data from 3004h to 3035h. To retrieve Event 2, write ‘2’ to the Event
Record Selector (3003h) and read the data from 3004h to 3035h. All 256 events
may be retrieved in this manner. The time and date stamp of each event may be
used to ensure that all events have been retrieved in order without new events
corrupting the sequence of events (Event 1 should be more recent than Event 2,
Event 2 should be more recent than Event 3, etc.).
GE Multilin http://www.GEmultilin.com 11
469 Modbus Memory Map
Communications Guide
Waveform Capture The 469 stores a number of cycles of A/D samples each time a trip occurs in a trace
buffer. The trace buffer is partitioned according to the S1 PREFERENCES ZV TRACE
MEMORY BUFFERS setpoint. The Trace Memory Trigger is set up with the S1
PREFERENCES ZV TRACE MEMORY TRIGGER setpoint and this determines how many pre-
trip and post-trip cycles are stored. The trace buffer is time and date stamped and
may be correlated to a trip in the event record. 10 waveforms are captured this way
when a trip occurs. These are the 3 phase currents, 3 differential currents, ground
current and 3 voltage waveforms. This information is stored in volatile memory and
will be lost if power is cycled to the relay.
To access the captured waveforms, select the waveform of interest by writing its
trace memory channel (see following table) to the Trace Memory Channel Selector
(address 30F1h). Then read the trace memory data from address 3100h to 3700h.
There are 12 samples per cycle for each of the cycles. The values read are in actual
amperes or volts.
Address 30F8h shows the number of traces taken. To access the latest use the value
at address 30F0h. To access more than 1 trace, reduce this value to access the older
traces.
12 http://www.GEmultilin.com GE Multilin
Modbus Memory Map 469
Communications Guide
469 Memory Map The 469 memory map is shown in the following table.
GE Multilin http://www.GEmultilin.com 13
469 Modbus Memory Map
Communications Guide
14 http://www.GEmultilin.com GE Multilin
Modbus Memory Map 469
Communications Guide
GE Multilin http://www.GEmultilin.com 15
469 Modbus Memory Map
Communications Guide
16 http://www.GEmultilin.com GE Multilin
Modbus Memory Map 469
Communications Guide
GE Multilin http://www.GEmultilin.com 17
469 Modbus Memory Map
Communications Guide
18 http://www.GEmultilin.com GE Multilin
Modbus Memory Map 469
Communications Guide
GE Multilin http://www.GEmultilin.com 19
469 Modbus Memory Map
Communications Guide
20 http://www.GEmultilin.com GE Multilin
Modbus Memory Map 469
Communications Guide
GE Multilin http://www.GEmultilin.com 21
469 Modbus Memory Map
Communications Guide
22 http://www.GEmultilin.com GE Multilin
Modbus Memory Map 469
Communications Guide
GE Multilin http://www.GEmultilin.com 23
469 Modbus Memory Map
Communications Guide
24 http://www.GEmultilin.com GE Multilin
Modbus Memory Map 469
Communications Guide
GE Multilin http://www.GEmultilin.com 25
469 Modbus Memory Map
Communications Guide
26 http://www.GEmultilin.com GE Multilin
Modbus Memory Map 469
Communications Guide
GE Multilin http://www.GEmultilin.com 27
469 Modbus Memory Map
Communications Guide
28 http://www.GEmultilin.com GE Multilin
Modbus Memory Map 469
Communications Guide
GE Multilin http://www.GEmultilin.com 29
469 Modbus Memory Map
Communications Guide
30 http://www.GEmultilin.com GE Multilin
Modbus Memory Map 469
Communications Guide
GE Multilin http://www.GEmultilin.com 31
469 Modbus Memory Map
Communications Guide
32 http://www.GEmultilin.com GE Multilin
Modbus Memory Map 469
Communications Guide
GE Multilin http://www.GEmultilin.com 33
469 Modbus Memory Map
Communications Guide
34 http://www.GEmultilin.com GE Multilin
Modbus Memory Map 469
Communications Guide
GE Multilin http://www.GEmultilin.com 35
469 Modbus Memory Map
Communications Guide
36 http://www.GEmultilin.com GE Multilin
Modbus Memory Map 469
Communications Guide
GE Multilin http://www.GEmultilin.com 37
469 Modbus Memory Map
Communications Guide
38 http://www.GEmultilin.com GE Multilin
Modbus Memory Map 469
Communications Guide
GE Multilin http://www.GEmultilin.com 39
469 Modbus Memory Map
Communications Guide
40 http://www.GEmultilin.com GE Multilin
Modbus Memory Map 469
Communications Guide
GE Multilin http://www.GEmultilin.com 41
469 Modbus Memory Map
Communications Guide
42 http://www.GEmultilin.com GE Multilin
Modbus Memory Map 469
Communications Guide
GE Multilin http://www.GEmultilin.com 43
469 Modbus Memory Map
Communications Guide
44 http://www.GEmultilin.com GE Multilin
Modbus Memory Map 469
Communications Guide
GE Multilin http://www.GEmultilin.com 45
469 Modbus Memory Map
Communications Guide
46 http://www.GEmultilin.com GE Multilin
Modbus Memory Map 469
Communications Guide
GE Multilin http://www.GEmultilin.com 47
469 Modbus Memory Map
Communications Guide
48 http://www.GEmultilin.com GE Multilin
Modbus Memory Map 469
Communications Guide
GE Multilin http://www.GEmultilin.com 49
469 Modbus Memory Map
Communications Guide
50 http://www.GEmultilin.com GE Multilin
Modbus Memory Map 469
Communications Guide
GE Multilin http://www.GEmultilin.com 51
469 Modbus Memory Map
Communications Guide
52 http://www.GEmultilin.com GE Multilin
Modbus Memory Map 469
Communications Guide
GE Multilin http://www.GEmultilin.com 53
469 Modbus Memory Map
Communications Guide
54 http://www.GEmultilin.com GE Multilin
Modbus Memory Map 469
Communications Guide
GE Multilin http://www.GEmultilin.com 55
469 Modbus Memory Map
Communications Guide
56 http://www.GEmultilin.com GE Multilin
Modbus Memory Map 469
Communications Guide
GE Multilin http://www.GEmultilin.com 57
469 Modbus Memory Map
Communications Guide
58 http://www.GEmultilin.com GE Multilin
Modbus Memory Map 469
Communications Guide
GE Multilin http://www.GEmultilin.com 59
469 Modbus Memory Map
Communications Guide
60 http://www.GEmultilin.com GE Multilin
Modbus Memory Map 469
Communications Guide
GE Multilin http://www.GEmultilin.com 61
469 Modbus Memory Map
Communications Guide
62 http://www.GEmultilin.com GE Multilin
Modbus Memory Map 469
Communications Guide
GE Multilin http://www.GEmultilin.com 63
469 Modbus Memory Map
Communications Guide
64 http://www.GEmultilin.com GE Multilin
Modbus Memory Map 469
Communications Guide
GE Multilin http://www.GEmultilin.com 65
469 Modbus Memory Map
Communications Guide
66 http://www.GEmultilin.com GE Multilin
Modbus Memory Map 469
Communications Guide
GE Multilin http://www.GEmultilin.com 67
469 Modbus Memory Map
Communications Guide
68 http://www.GEmultilin.com GE Multilin
Modbus Memory Map 469
Communications Guide
GE Multilin http://www.GEmultilin.com 69
469 Modbus Memory Map
Communications Guide
70 http://www.GEmultilin.com GE Multilin
Modbus Memory Map 469
Communications Guide
GE Multilin http://www.GEmultilin.com 71
469 Modbus Memory Map
Communications Guide
72 http://www.GEmultilin.com GE Multilin
Modbus Memory Map 469
Communications Guide
Format Codes The data formats used in the Modbus memory map are shown below.
Table 2: Data Formats (Sheet 1 of 14) Table 2: Data Formats (Sheet 2 of 14)
CODE TYPE DEFINITION CODE TYPE DEFINITION
F1 16 bits UNSIGNED VALUE F11 32 bits UNSIGNED LONG
VALUE, 2 DECIMAL
Example: 1234 stored as 1234 PLACES
F2 16 bits UNSIGNED VALUE, 1st 16 bits High Order Word of Long
1 DECIMAL PLACE Value
Example: 123.4 stored as 1234 2nd 16 bits Low Order Word of Long
F3 16 bits UNSIGNED VALUE, Value
2 DECIMAL PLACES Example: 1234.56 stored as 123456
Example: 12.34 stored as 1234 (i.e. 1st word: 0001 hex, 2nd word:
E240 hex)
F4 16 bits 2’s COMPLEMENT
SIGNED VALUE F12 32 bits 2’s COMPLEMENT
SIGNED LONG VALUE
Example: –1234 stored as –1234 (i.e.
64302) 1st 16 bits High Order Word of Long
Value
F5 16 bits 2’s COMPLEMENT
SIGNED VALUE 2nd 16 bits Low Order Word of Long
1 DECIMAL PLACES Value
Example: -123.4 stored as -1234 (i.e. Example: -123456 stored as -123456
64302) (i.e. 1st word: FFFE hex, 2nd word:
1DC0 hex)
F6 16 bits 2’s COMPLEMENT
SIGNED VALUE F13 32 bits 2’s COMPLEMENT
2 DECIMAL PLACES SIGNED LONG VALUE,
1 DECIMAL PLACE
Example: –12.34 stored as –1234 (i.e.
64302) 1st 16 bits High Order Word of Long
Value
F7 16 bits 2’s COMPLEMENT
SIGNED VALUE 2nd 16 bits Low Order Word of Long
3 DECIMAL PLACES Value
Example: –1.234 stored as –1234 (i.e. Example: -12345.6 stored as -123456
64302) (i.e. 1st word: FFFE hex, 2nd word:
1DC0 hex)
F8 16 bits 2’s COMPLEMENT
SIGNED VALUE F14 32 bits 2’s COMPLEMENT
4 DECIMAL PLACES SIGNED LONG VALUE,
2 DECIMAL PLACES
Example: -0.1234 stored as -1234
(i.e. 64302) 1st 16 bits High Order Word of Long
Value
F9 32 bits UNSIGNED LONG
VALUE 2nd 16 bits Low Order Word of Long
Value
1st 16 bits High Order Word of Long
Value Example: -1234.56 stored as -123456
(i.e. 1st word: FFFE hex, 2nd word:
2nd 16 bits Low Order Word of Long 1DC0 hex)
Value
F15 16 bits HARDWARE REVISION
Example: 123456 stored as 123456
(i.e. 1st word: 0001 hex, 2nd word: 0000 0000 1=A
E240 hex) 0000 0001
F10 32 bits UNSIGNED LONG 0000 0000 2=B
VALUE, 1 DECIMAL 0000 0010
PLACE ... ...
1st 16 bits High Order Word of Long 0000 0000 26 = Z
Value 0001 1010
2nd 16 bits Low Order Word of Long
Value
Example: 12345.6 stored as 123456
(i.e. 1st word: 0001 hex, 2nd word:
E240 hex)
GE Multilin http://www.GEmultilin.com 73
469 Modbus Memory Map
Communications Guide
Table 2: Data Formats (Sheet 3 of 14) Table 2: Data Formats (Sheet 4 of 14)
CODE TYPE DEFINITION CODE TYPE DEFINITION
F16 16 bits SOFTWARE REVISION F24 32 bits TIME FORMAT FOR
BROADCAST
1111 1111 Major Revision Number
xxxx xxxx 0 to 9 in steps of 1 1st byte Hours (0 to 23)
xxxx xxxx Minor Revision Number 2nd byte Minutes (0 to 59)
1111 1111 (two BCD digits)
00 to 99 in steps of 1 3rd & 4th Milliseconds (0 to 59999)
bytes Note: Clock resolution
Example: Revision 2.30 stored as limited to 0.01 sec
0230 hex
Example: 1:15:48:572 stored as
F17 32 bits UNSIGNED LONG 17808828 (i.e., 1st word 010F, 2nd
VALUE, 3 DECIMAL word BDBC)
PLACES
F25 16 bits UNSIGNED VALUE, 4
1st 16 bits High Order Word of Long DECIMAL PLACES
Value
Example: 0.1234 stored as 1234
2nd 16 bits Low Order Word of Long
Value F26 16 bits UNSIGNED VALUE, 3
DECIMAL PLACES
Example: 123.456 stored as 123456
(i.e. 1st word: 0001 hex, 2nd word: Example: 1.234 stored as 1234
E240 hex) F100 Unsigned TEMPERATURE
F18 32 bits DATE (MM/DD/YYYY) 16 bit DISPLAY UNITS
integer
1st byte Month (1 to 12)
0 Celsius
2nd byte Day (1 to 31)
1 Fahrenheit
3rd & 4th Year (1995 to 2094)
byte F101 Unsigned RS 485 BAUD RATE
16 bit
Example: Feb. 20, 1995 stored as integer
34867142 (i.e. 1st word: 0214, 2nd
word 07C6) 0 300 baud
74 http://www.GEmultilin.com GE Multilin
Modbus Memory Map 469
Communications Guide
Table 2: Data Formats (Sheet 5 of 14) Table 2: Data Formats (Sheet 6 of 14)
CODE TYPE DEFINITION CODE TYPE DEFINITION
F107 Unsigned NOMINAL FREQUENCY F113 Unsigned ALARM RELAYS
16 bit 16 bit
integer integer
0 60 Hz 0 Alarm
1 50 Hz 1 Alarm & Aux2
2 Variable 2 Alarm & Aux2 & Aux3
F108 Unsigned REDUCED VOLTAGE 3 Alarm & Aux3
16 bit STARTING
integer TRANSITION ON 4 Aux2
0 Off 1 Latched
GE Multilin http://www.GEmultilin.com 75
469 Modbus Memory Map
Communications Guide
Table 2: Data Formats (Sheet 7 of 14) Table 2: Data Formats (Sheet 8 of 14)
CODE TYPE DEFINITION CODE TYPE DEFINITION
F121 Unsigned RTD APPLICATION F127 Unsigned ANALOG OUTPUT
16 bit 16 bit PARAMETER
integer integer SELECTION
0 None 0 None
1 Stator 1 Phase A Current
2 Bearing 2 Phase B Current
3 Ambient 3 Phase C Current
4 Other 4 Average Phase Current
F122 Unsigned RTD VOTING 5 AB Line Voltage
16 bit SELECTION
integer 6 BC Line Voltage
76 http://www.GEmultilin.com GE Multilin
Modbus Memory Map 469
Communications Guide
Table 2: Data Formats (Sheet 9 of 14) Table 2: Data Formats (Sheet 10 of 14)
CODE TYPE DEFINITION CODE TYPE DEFINITION
F129 Unsigned ANALOG INPUT F134 26 RTD 5 Trip
16 bit SELECTION ctd.
integer 27 RTD 6 Trip
GE Multilin http://www.GEmultilin.com 77
469 Modbus Memory Map
Communications Guide
Table 2: Data Formats (Sheet 11 of 14) Table 2: Data Formats (Sheet 12 of 14)
CODE TYPE DEFINITION CODE TYPE DEFINITION
F134 79 Undervoltage Alarm F134 136 4 ALARM Relay Forced
ctd. ctd.
80 Overvoltage Alarm 137 5 BLOCK Relay Forced
81 Volt. Frequency Alarm 138 Force 1 TRIP Disabled
82 Power Factor Alarm 139 Force 2 AUX Disabled
83 Reactive Power Alarm 140 Force 3 AUX Disabled
84 Underpower Alarm 141 Force 4 ALARM Disabled
85 Trip Counter Alarm 142 Force 5 BLOCK Disabled
86 Starter Failed Alarm 143 Motor Started
87 Current Demand Alarm F135 Unsigned MOTOR SPEED
16 bit
88 kW Demand Alarm integer
89 kvar Demand Alarm 0 Low Speed (Speed 1)
90 kVA Demand Alarm 1 High Speed (Speed 2)
91 F136 Unsigned ORDER CODE
92 Analog I/P 1 Alarm 16 bit
integer
93 Analog I/P 2 Alarm
Bit 0 0 = P5 (5A phase CT),
94 Analog I/P 3 Alarm 1 = P1 (1A phase CT)
95 Analog I/P 4 Alarm Bit 1 0 = HI (High Voltage
Power Supply),
96 Reverse Power Alarm 1 = LO (Low Voltage
97 Incomplete Seq Alarm Power Supply)
(Valid only for Mod 001) Bit 2 0 = A20 (4-20 mA
98 Analog Diff 1-2 Alarm Analog Outputs), 1 = A1
(0-1 mA Analog Outputs)
99 Analog Diff 3-4 Alarm
F137 Unsigned CONTROL RELAYS FOR
100 ---- 16 bit REDUCED VOLTAGE
integer STARTING
101 Service Alarm
0 Auxiliary 2
102 Control Power Lost
1 Auxiliary 2 & Auxiliary 3
103 Cont. Power Applied
2 Auxiliary 3
104 Emergency Rst. Close
F138 Unsigned SIMULATION MODE
105 Emergency Rst. Open 16 bit
106 Start While Blocked integer
107 Relay Not Inserted 0 Off
108 Trip Coil Super. 1 Simulate Pre-Fault
109 Breaker Failure 2 Simulate Fault
110 Welded Contactor 3 Pre-Fault to Fault
111 Simulation Started F139 Unsigned FORCE OPERATION OF
16 bit RELAYS
112 Simulation Stopped integer
↓ ↓ 0 Disabled
118 Digital Trace Trigger 1 1 TRIP
119 Serial Trace Trigger 2 2 AUXILIARY
120 RTD 1 High Alarm 3 3 AUXILIARY
121 RTD 2 High Alarm 4 4 ALARM
122 RTD 3 High Alarm 5 5 BLOCK START
123 RTD 4 High Alarm 6 6 SERVICE
124 RTD 5 High Alarm 7 All Relays
125 RTD 6 High Alarm 8 No Relays
126 RTD 7 High Alarm F140 Unsigned GENERAL STATUS
127 RTD 8 High Alarm 16 bit
integer
128 RTD 9 High Alarm
bit 0 Relay in Service
129 RTD 10 High Alarm
bit 1 Active Trip Condition
130 RTD 11 High Alarm
bit 2 Active Alarm Condition
131 RTD 12 High Alarm
bit 3 Reserved
132 Overtorque Alarm
bit 4 Reserved
133 1 TRIP Relay Forced
bit 5 Reserved
134 2 AUX Relay Forced
bit 6 Reserved
135 3 AUX Relay Forced
bit 7 Reserved
78 http://www.GEmultilin.com GE Multilin
Modbus Memory Map 469
Communications Guide
Table 2: Data Formats (Sheet 13 of 14) Table 2: Data Formats (Sheet 14 of 14)
CODE TYPE DEFINITION CODE TYPE DEFINITION
F140 bit 8 Motor Stopped F149 Unsigned UNDERVOLTAGE TRIP
ctd. 16 bit MODE
bit 9 Motor Starting integer
bit 10 Motor Running 0 1-Phase
bit 11 Overload Pickup 1 3-Phase
bit 12 Unbalance Pickup F150 Unsigned IP ADDRESS
bit 13 Ground Pickup 32 bit
integer
bit 14 Hot RTD
IP address, subnet mask or default
bit 15 Loss of Load gateway. Each byte in this register
represents one octet of an IP address.
F141 Unsigned OUTPUT RELAY For example: 0x015EDA1F represents
16 bit STATUS address 1.94.218.31
integer
F151 Unsigned DEVICENET
bit 0 1 TRIP 16 bit CONNECTION STATUS
bit 1 2 AUXILIARY integer
bit 2 3 AUXILIARY 0 Nonexistent
bit 3 4 ALARM 1 Configuring
bit 4 5 BLOCK START 2 --
bit 5 6 SERVICE 3 Established
bit 6 to 15 Not Used 4 Time Out
F142 Unsigned TRIP COIL 5 Deferred Date
16 bit SUPERVISION F152 Unsigned ETHERNET STATUS
integer SELECTION 16 bit
0 Disabled integer
1 S2 Closed BIT 0 Diagnostic
2 S2 Open/Closed BIT 1 Connection Status
F143 Unsigned SINGLE VT SELECTION BIT 2 Not Used
16 bit BIT 3 Ethernet Link Status
integer
F153 Unsigned DEVICENET PORT
0 Off 16 bit STATUS
1 AN (Wye), AB (Delta) integer
2 BN (Wye), BC (Delta) 0 Not Powered
3 CN (Wye), N/A (Delta) 1 Port Operational
F144 Unsigned PULSED OUTPUT 2 Internal Configuration
16 bit RELAY SELECTION Error - Data Size Larger
integer Than Confirmed
0 Off 3 Unrecoverable Fault
1 2 AUXILIARY 4 Minor Fault
2 3 AUXILIARY F154 Unsigned DEVICENET LINK
16 bit STATUS
3 4 ALARM integer
F145 Unsigned ANALOG IN 0 Not Online, Not Powered
16 bit DIFFERENTIAL
integer COMPARISON 1 Online, Connected
0 % Difference 2 --
1 Absolute Difference 3 Online, Not Connected
F146 Unsigned ANALOG IN 4 Critical Link Failure
16 bit DIFFERENTIAL LOGIC 5 Connection Timeout
integer
F155 Unsigned ACTIVE ALARM
0 1>2 (or 3>4) 16 bit
1 2>1 (or 4>3) integer
2 1<>2 (or 3<>4) 1xxx xxxx Active Alarm
xxxx xxxx
F147 Unsigned ANALOG IN
16 bit DIFFERENTIAL x111 1111 Alarm Count
integer ACTIVE WHEN 1111 1111
0 Always F156 Unsigned DEVICENET BAUD
16 bit RATE
1f Start/Run integer
F148 Unsigned TORQUE DISPLAY 0 125 kbps
16 bit UNITS
integer 1 250 kbps
0 Newton-meter 2 500 kbps
1 Foot-pound
GE Multilin http://www.GEmultilin.com 79
469 DeviceNet Protocol
Communications Guide
DeviceNet Protocol
Overview The 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 469 Setup software. The polling function produces 10 bytes
of data (described in assembly object Class 04h, Instance 64h, Attribute 03h). The
COS\CYC operation produces 4 bytes of data as per Class 04h,Instance 66h,
Attribute 03h.
The following master/slave connection objects are supported by the 469 DeviceNet
implementation:
• Explicit Messaging Connection
• Poll I/O Connection
• Change of State or Cyclic I/O Connection
The following objects have been implemented:
Object Class
DeviceNet objects
Identity object 01h
Message Router object 02h
DeviceNet object 03h
Assembly object 04h
Connection object 05h
Acknowledge Handler object 2Bh
469 specific objects
I/O Data Input Mapping object A0h
Parameter Data Input Mapping object B0h
Poll Data The polling data function produces 10 bytes of data as described under Class 04h,
Instance 64h, Attribute 03h.
Change of State (COS) The COS data is described under Class 4, Instance 66h, Attribute 03h. The following
data is provided
80 http://www.GEmultilin.com GE Multilin
DeviceNet Protocol 469
Communications Guide
STATUS OF ANYBUS DEVICE (Class code 01h, Instance 01h, Attribute 05h)
BIT ON (=1) DESCRIPTION
BIT 0 Pre-defined master/slave connection set has been allocated to a master.
A master owns the device
BIT 2 DeviceNet has been configured
BIT 8 Minor recoverable fault
BIT 9 Minor unrecoverable fault
BIT 10 Major recoverable fault
BIT 11 Major unrecoverable fault
GE Multilin http://www.GEmultilin.com 81
469 DeviceNet Protocol
Communications Guide
Table 11: Assembly object, Class code 04h, Instance 64h, Attributes:
Attribute Byte Name/ Services Default, Min, Max Format Code
Description
03h 1, 2 (low, IO polled data: Get_Attribute_Single 0, 0, FFFF F162
high) relay status
3, 4 (low, Input switches and Get_Attribute_Single 0, 0, FFFF F163
high) output relay status
5, 6 (low, Motor thermal Get_Attribute_Single 0, 0, 100 F1
high) capacity used
7 to 10 Time to trip Get_Attribute_Single –1, –1, 99999 F20
(low, high)
82 http://www.GEmultilin.com GE Multilin
DeviceNet Protocol 469
Communications Guide
The attributes in this class can be accessed using Poll I/O Connection or Explicit
Messages Connection. This data could be polled from Class A0h, I/O Data Input
Mapping Object, instance 1, attribute 1 as well.
Table 12: Assembly object, Class code 04h, Instance 66h, Attributes:
Attribute Byte Name/Description Services Default, Min, Max Format Code
03h 1, 2 (low, IO polled data: relay Get_Attribute_Single 0, 0, FFFF F162
high) status
3, 4 (low, Input switches and Get_Attribute_Single 0, 0, FFFF F163
high) output relay status
Table 14: Connection object, Class code 05h, Instance 01h (explicit message connection),
Attributes:
Attribute Name/Description Services Default, Min, Max Data type
01h State of the object. Get_Attribute_Single 1, 0, 5 USINT
0 = Nonexistent;
1 = Configuring; 3 = Established;
4=Timed Out;
5 = Deferred delete
02h Instance type. Indicates either IO Get_Attribute_Single 0, 0, 0 USINT
or messaging connection.
03h Transport class trigger. Defines Get_Attribute_Single 83h, 83h, 83h USINT
behavior of the connection.
04h Produced Cxnx ID. Placed in CAN Get_Attribute_Single N/A, N/A, N/A UINT
identifier field when the
connection transmits.
05h Consumed Cxnx ID. CAN Get_Attribute_Single N/A, N/A, N/A UINT
identifier field value that denotes
message to be received.
06h Initial comm characteristics. Get_Attribute_Single N/A, N/A, N/A USINT
Defines the message group(s)
across which productions and
consumptions associated with
this object occur.
07h Produced connection size. Get_Attribute_Single 512, 512, 512 UINT
Maximum number of bytes
transmitted across this
connection.
08h Consumed connection size. Get_Attribute_Single 512, 512, 512 UINT
Maximum number of bytes
received across this connection
09h Expected packet rate. Defines Get_Attribute_Single N/A, N/A, N/A UINT
timing associated with this
connection. Resolution is 10 ms.
GE Multilin http://www.GEmultilin.com 83
469 DeviceNet Protocol
Communications Guide
Table 14: Connection object, Class code 05h, Instance 01h (explicit message connection),
Attributes:
Attribute Name/Description Services Default, Min, Max Data type
0Ch Watchdog timeout action. Defines Get_Attribute_Single N/A, N/A, N/A USINT
how to handle inactivity/
watchdog time-outs.
0 = Transition to time out
1 = Auto delete; 2 = Auto reset
3 = Deferred delete
0Dh Produced connection path length: Get_Attribute_Single 0, 0, 0 UINT
Number of bytes in the produced
connection_path_length attribute
0Eh Produced connection path: Get_Attribute_Single 0, 0, 0 Array of
Application object producing data USINT
on the connection.
0Fh Consumed connection path Get_Attribute_Single 0, 0, 0 UINT
length. Number of bytes in the
consumed_connection_path
length attribute
10h Consumed connection path. Get_Attribute_Single N/A, N/A, N/A Array of UINT
Specifies the application object(s)
to receive the data consumed by
this connection object.
11h Production inhibit time. Defines Get_Attribute_Single 0, 0, 0 UINT
the minimum time between new
data production.
Table 15: Connection Object, Class code 05h, Instance 02h (Polled I/O connection),
Attributes:
Attribute Name/Description Services Default, Min, Max Data type
01h State of the object. Get_Attribute_Single 1, 0, 5 USINT
0 = Nonexistent;
1 = Configuring; 3 = Established;
4=Timed Out;
5 = Deferred delete
02h Instance type. Indicates either IO Get_Attribute_Single 0, 0, 1 USINT
or messaging connection.
03h Transport class trigger. Defines Get_Attribute_Single N/A, N/A, N/A USINT
behavior of the connection.
04h Produced Cxnx ID. Placed in CAN Get_Attribute_Single N/A, N/A, N/A UINT
identifier field when the
connection transmits.
05h Consumed Cxnx ID. CAN Get_Attribute_Single N/A, N/A, N/A UINT
identifier field value that denotes
message to be received.
06h Initial comm characteristics. Get_Attribute_Single N/A, N/A, N/A USINT
Defines the message group(s)
across which productions and
consumptions associated with
this object occur.
07h Produced connection size. Get_Attribute_Single I/O in length, 0, UINT
Maximum number of bytes I/O in length
transmitted across this
connection.
08h Consumed connection size. Get_Attribute_Single I/O out length, 0, UINT
Maximum number of bytes I/O out length
received across this connection
09h Expected packet rate. Defines Get_Attribute_Single N/A, N/A, N/A UINT
timing associated with this
connection.
0Ch Watchdog timeout action. Defines Get_Attribute_Single N/A, N/A, N/A USINT
how to handle inactivity/
watchdog time-outs.
0 = Transition to time out
1 = Auto delete; 2 = Auto reset
3 = Deferred delete
84 http://www.GEmultilin.com GE Multilin
DeviceNet Protocol 469
Communications Guide
Table 15: Connection Object, Class code 05h, Instance 02h (Polled I/O connection),
Attributes:
Attribute Name/Description Services Default, Min, Max Data type
0Dh Produced connection path length: Get_Attribute_Single 6, 6, 6 UINT
Number of bytes in the produced
connection_path_length attribute
0Eh Produced connection path: Get_Attribute_Single 20 04 24 64 30 03, Array of
Application object producing data N/A, N/A USINT
on the connection.
0Fh Consumed connection path Get_Attribute_Single 6, 6, 6 UINT
length. Number of bytes in the
consumed_connection_path
length attribute
10h Consumed connection path. Get_Attribute_Single 20 04 24 64 30 03, Array of UINT
Specifies the application object(s) N/A, N/A
to receive the data consumed by
this connection object.
11h Production inhibit time. Defines Get_Attribute_Single 0, 0, 0 UINT
the minimum time between new
data production.
GE Multilin http://www.GEmultilin.com 85
469 DeviceNet Protocol
Communications Guide
Table 17: Acknowledge handler object, Class code 2Bh, Instance 01h, Attributes:
Attribute Name/Description Services Default, Min, Max Data type
01h Acknowledge timer. The Get_Attribute_Single 16, 1, 65535 UINT
time to wait for an
acknowledge before re-
sending.
02h Retry limit. This is the Get_Attribute_Single 1, 0, 255 USINT
number of acknowledge
time-outs to wait before
informing the application
of a retry_limit_reached
event
03h COS producing Get_Attribute_Single N/A UINT
connection instance. This
is the connection instance
which contains the oath
of the producing I/O
application object which
will be notified of
acknowledge handle
events.
04h ACK list size. This is the Get_Attribute_Single
maximum number of
members in the
acknowledge list.
0 = dynamic.
05h ACK list. List of active Get_Attribute_Single N/A Byte array of
connection instances USINT
which are receiving
acknowledges.
06h Data with ACK path list Get_Attribute_Single
size. Maximum number of
members in data with
acknowledge path list.
0 = dynamic.
07h Data with ACK path list. Get_Attribute_Single N/A Byte array of
List of connection UINT, USINT;
instance / consuming Array of USINT
application object pairs.
This attribute is used to
forward data received
with acknowledgement.
469 Specific Objects a) I/O DATA INPUT MAPPING OBJECT (CLASS CODE A0H)
The class and instance attributes for the I/O data input mapping object (class code
A0h) are as follows:
Table 18: I/O data input mapping object, Class code A0h, Attributes:
Attribute Name/Description Services Default, Min, Max Data type
1 Revision of the I/O data Get_Attribute_All 1, 1, 1 UINT
input mapping handler
object.
86 http://www.GEmultilin.com GE Multilin
DeviceNet Protocol 469
Communications Guide
Table 19: I/O data input mapping object, Class code A0h, Instance 01h, Attributes:
Attribute Name/ Services Default, Min, Max Format
Description Code
01h 1, 2 (low, high) Relay status Get_Attribute_Single 0, 0, FFFF F162
3, 4 (low, high) Input switches and Get_Attribute_Single 0, 0, FFFF F163
output relay status
5, 6 (low, high) Motor thermal Get_Attribute_Single 0, 0, 100 F1
capacity used
7 to 10 (low, Time to trip Get_Attribute_Single –1, –1, 99999 F20
high)
03h 1, 2 (low, high) Change of state Get_Attribute_Single 0, 0, FFFF F162
data: Relay status
3, 4 (low, high) Input switches and Get_Attribute_Single 0, 0, FFFFF F163
output relay status
Attributes #1 and 3 in this class can be accessed using polled connection or explicit
messages connection. This data could be polled from Class 04h, Assembly Object,
Instance 64h, Attribute #1 as well.
Consult the Modbus memory map for additional details on the output messages.
Table 20: Parameter data input mapping object, Class B0h, Attributes:
Attribute Name/Description Services Default, Min, Max Data type
01h Revision of the parameter data Get_Attribute_All 1, 1, 1 UINT
input mapping object.
Table 21: Parameter data input mapping object, Class B0h, Instance 01h, Attributes:
Attribute Access Name/Description Data Length Value
01h Get Phase & ground currents bytes (20) Refer Table 22
02h Get Current angles bytes (6) Refer Table 22
03h Get Differential currents bytes (6) Refer Table 22
04h Get Motor load bytes (6) Refer Table 22
05h Get Line voltages bytes (8) Refer Table 22
06h Get Voltage angles bytes (6) Refer Table 22
07h Get Power bytes (14) Refer Table 22
08h Get Energy bytes (12) Refer Table 22
09h Get Demand bytes (14) Refer Table 22
0Ah Get Peak demand bytes (14) Refer Table 22
0Bh Get Speed & Torque bytes (8) Refer Table 22
0Ch Get Analog inputs bytes (24) Refer Table 22
0Dh Get Motor statistics bytes (16) Refer Table 22
0Eh Get Temperatures bytes (24) Refer Table 22
0Fh Get Last trip date & time bytes (8) Refer Table 22
10h Get Alarm data bytes (62) Refer Table 22
11h Get Frequency bytes (2) Refer Table 22
12h Get Phase voltages bytes (8) Refer Table 22
13h Get Motor starting data bytes (16) Refer Table 22
14h Get Start blocks bytes (10) Refer Table 22
15h Get Cause of last trip bytes (2) Refer Table 22
16h Get Pre-trip currents bytes (22) Refer Table 22
17h Get Pre-trip phase voltages bytes (12) Refer Table 22
GE Multilin http://www.GEmultilin.com 87
469 DeviceNet Protocol
Communications Guide
Table 21: Parameter data input mapping object, Class B0h, Instance 01h, Attributes:
18h Get Pre-trip line voltages bytes (12) Refer Table 22
19h Get Pre-trip system frequency bytes (2) Refer Table 22
1Ah Get Pre-trip motor load unbalance bytes (4) Refer Table 22
1Bh Get Pre-trip power & power factor bytes (12) Refer Table 22
1Ch Get Pre-trip analog input data bytes (16) Refer Table 22
1Dh Get Pre-trip hottest RTD & temperature bytes (16) Refer Table 22
1Eh Get Pre-trip motor speed bytes (4) Refer Table 22
1Fh Get RTD maximums bytes (24) Refer Table 22
20h Get Analog input maximums & minimums bytes (32) Refer Table 22
21h Get Motor thermal capacity used bytes (2) Refer Table 22
22h Get Time to trip bytes (4) Refer Table 22
23h Get Contain attributes 01h to 10h together bytes (248) Refer Table 22
88 http://www.GEmultilin.com GE Multilin
DeviceNet Protocol 469
Communications Guide
GE Multilin http://www.GEmultilin.com 89
469 DeviceNet Protocol
Communications Guide
0Fh LAST TRIP 1 to 4 (low,high) Time of Last Trip 32 bits N/A, N/A, N/A -- F19
DATE & TIME 5 to 8 (low,high) Date of Last Trip 32 bits N/A, N/A, N/A -- F18
1 Pressure switch 8bits 0, 0, 4 -- F160
2 Vibration switch 8bits 0, 0, 4 -- F160
3 Digital counter 8bits 0, 0, 4 -- F160
4 Tachometer 8bits 0, 0, 4 -- F160
5 General switch A 8bits 0, 0, 4 -- F160
6 General switch B 8bits 0, 0, 4 -- F160
7 General switch C 8bits 0, 0, 4 -- F160
8 General switch D 8bits 0, 0, 4 -- F160
9 Thermal capacity 8bits 0, 0, 4 -- F160
10 Overload 8bits 0, 0, 4 -- F160
10h ALARM
11 Undercurrent 8bits 0, 0, 4 -- F160
DATA
12 Current unbalance 8bits 0, 0, 4 -- F160
13 Ground fault 8bits 0, 0, 4 -- F160
14 RTD 1 8bits 0, 0, 4 -- F160
15 RTD 2 8bits 0, 0, 4 -- F160
16 RTD 3 8bits 0, 0, 4 -- F160
17 RTD 4 8bits 0, 0, 4 -- F160
18 RTD 5 8bits 0, 0, 4 -- F160
19 RTD 6 8bits 0, 0, 4 -- F160
20 RTD 7 8bits 0, 0, 4 -- F160
21 RTD 8 8bits 0, 0, 4 -- F160
90 http://www.GEmultilin.com GE Multilin
DeviceNet Protocol 469
Communications Guide
GE Multilin http://www.GEmultilin.com 91
469 DeviceNet Protocol
Communications Guide
92 http://www.GEmultilin.com GE Multilin
DeviceNet Protocol 469
Communications Guide
GE Multilin http://www.GEmultilin.com 93
469 DeviceNet Protocol
Communications Guide
20h ANALOG 13 to 16 (low,high) Analog input 2 maximum 32bits 0, -50000, 50000 -- F12
INPUT
MAXIMUMS & 17 to 20 (low,high) Analog input 3 minimum 32bits 0, -50000, 50000 -- F12
MINIMUMS
21 to 24 (low,high) Analog input 3 maximum 32bits 0, -50000, 50000 -- F12
94 http://www.GEmultilin.com GE Multilin
DeviceNet Protocol 469
Communications Guide
DeviceNet Data Formats DeviceNet also uses the same format codes specified in Modbus Memory Map.
Consult the Modbus memory map for additional details on the output messages.
The DeviceNet specific Format codes are as follows:
0 Off
1 Not Active
2 Timing Out
3 Active
4 Latched
BIT 0 Reserved
BIT 1 Reserved
BIT 2 Relay in service
BIT 3 Active trip condition
BIT 4 Active alarm condition
BIT 5 In simulation mode
BIT 6 Motor overloaded
BIT 7 Motor tripped
BIT 8 Motor stopped
BIT 9 Motor starting
BIT 10 Motor running
BIT 11 Overload pickup
BIT 12 Unbalance pickup
BIT 13 Ground pickup
BIT 14 Hot RTD
BIT 15 Loss of load
BIT 0 Trip
BIT 1 Auxiliary 2
BIT 2 Auxiliary 3
BIT 3 Alarm
BIT 4 Block start
BIT 5 Service
BIT 6 Access switch
BIT 7 Test switch
BIT 8 Starter switch
BIT 9 Emergency restart switch
BIT 10 Remote reset switch
BIT 11 Assignable switch 1
BIT 12 Assignable switch 2
BIT 13 Assignable switch 3
BIT 14 Assignable switch 4
BIT 15 Trip coil
GE Multilin http://www.GEmultilin.com 95
469 DeviceNet Protocol
Communications Guide
The figure below illustrates the bit placement rules associated with the Compact
Encoding of a FixedLengthBitString used in DeviceNet data.
7------0 7------0
HI LO
WORD Byte 2 Byte 1 Byte 1 Byte 2
HI LO
96 http://www.GEmultilin.com GE Multilin
Index
Index 469
Communications Guide
C H
CLEAR DATA ..................................................................... 30
COMMANDS ....................................................................... 13
COMMUNICATIONS ........................................................... 26 I
CRC-16 ............................................................................ 2, 3
CURRENT DEMAND ........................................................... 47 INSTALLATION ................................................................... 30
CURRENT METERING ........................................................ 21
CURRENT SENSING .......................................................... 30
CURRENT UNBALANCE ..................................................... 37
CYCLIC REDUNDANCY CHECK ........................................... 2
J
JOGGING BLOCK ............................................................... 38
D
DATA FORMATS, MEMORY MAP ........................................ 73
K
DATA FRAME FORMAT ........................................................ 1
DATA PACKET FORMAT ...................................................... 2
DATA RATE .......................................................................... 1 L
DEFAULT MESSAGES ........................................................ 27
DEMAND .......................................................................47, 48 LAST TRIP DATA ................................................................ 18
DEMAND METERING .......................................................... 23 LOAD SHED TRIP ............................................................... 32
DEVICENET LOOPBACK TEST ................................................................. 8
469 specific objects .......................................................... 86
acknowledge handler object .............................................. 85
assembly object ............................................................... 82
connection object ............................................................. 83 M
description ....................................................................... 80
MECHANICAL JAM ............................................................. 37
DeviceNet object .............................................................. 82
MEMORY MAP
identity object ................................................................... 81
description ........................................................................ 11
message router object ...................................................... 81
format codes ..................................................................... 73
Modbus registers .............................................................. 27
table ................................................................................. 13
DIGITAL COUNTERS .......................................................... 33
user-definable area ........................................................... 11
DIGITAL INPUTS ................................................................ 21
MEMORY MAP FORMAT CODES ........................................ 73
MEMORY MAP INFORMATION ............................................ 11
MESSAGE SCRATCHPAD ....................................... 27, 28, 29
E MODBUS
description .......................................................................... 1
ELECTRICAL INTERFACE .................................................... 1 digital input status ............................................................... 4
ERROR CHECKING .............................................................. 2 execute operation ............................................................... 7
ERROR RESPONSES ......................................................... 10 function code 01 ................................................................. 4
ETHERNET ........................................................................ 27 function code 02 ................................................................. 4
EVENT RECORD function code 03 ................................................................. 6
memory map locations ...................................................... 11 function code 04 ................................................................. 6
EVENT RECORDER function code 05 ................................................................. 7
memory map locations ...................................................... 11 function code 06 ................................................................. 7
GE Multilin http://www.GEindustrial.com/multilin i
469 Index
Communications Guide
R U
REACTIVE POWER ............................................................. 46
UNDERCURRENT ...............................................................37
REAL TIME CLOCK ....................................................... 21, 27
UNDERPOWER ...................................................................46
REDUCED VOLTAGE .......................................................... 31
UNDERVOLTAGE .......................................................... 44, 45
RELAY RESET MODE ......................................................... 35
USER DEFINABLE MEMORY MAP .......................................11
REMOTE ALARM ................................................................ 31
USER MAP ..........................................................................13
REMOTE TRIP .................................................................... 32
RESTART BLOCK ............................................................... 38
REVERSE POWER ............................................................. 46
REVISION ........................................................................... 13 V
RS232 .................................................................................. 1
RS485 .................................................................................. 1 VIBRATION SWITCH ALARM ...............................................32
RTD #1 ............................................................................... 39 VIBRATION SWITCH TRIP ...................................................33
RTD #10 ............................................................................. 42 VOLTAGE FREQUENCY ......................................................45
RTD #11 ....................................................................... 42, 43 VOLTAGE SENSING ............................................................30
RTD #12 ............................................................................. 43
ii http://www.GEindustrial.com/multilin GE Multilin
Index 469
Communications Guide
W XYZ
WAVEFORM CAPTURE ...................................................... 12
iv http://www.GEindustrial.com/multilin GE Multilin