GE Multilin MM300 Motor Management System Communications Guide for revision 1.0x.
MM300 Motor Management System, EnerVista, EnerVista Launchpad, EnerVista MM300
Setup, and FlexLogic are registered trademarks 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 number: 1601-9025-A1 (July 2007)
TABLE OF CONTENTS
Table of Contents
COMMUNICATIONS GUIDE ............................................................................................................................ i
Data Frame Format and Data Rate........................................................................................................ 2
Data Packet Format .......................................................................................................................................2
Function Code 03H ......................................................................................................................................... 4
Function Code 04H ......................................................................................................................................... 5
Function Code 05H ......................................................................................................................................... 6
Function Code 06H ......................................................................................................................................... 7
Function Code 07H ......................................................................................................................................... 8
Function Code 08H ......................................................................................................................................... 9
Function Code 10H ......................................................................................................................................... 9
Format codes ..................................................................................................................................................34
Performing Commands Using Function Code 10H ....................................................................... 49
Using the User Definable Memory Map..............................................................................................50
The MM300 implements a subset of the Modicon Modbus RTU serial communication
standard. The Modbus protocol is hardware-independent. That is, the physical layer can be
any of a variety of standard hardware configurations. This includes RS232, RS422, RS485,
fibre optics, etc. Modbus is a single master / multiple slave type of protocol suitable for a
multi-drop configuration as provided by RS485 hardware. The MM300 Modbus
implementation employs two-wire RS485 hardware. Using RS485, up to 32 MM300s can be
daisy-chained together on a single communication channel.
The MM300 is always a Modbus slave. It can not be programmed as a Modbus master.
Computers or PLCs are commonly programmed as masters.
Both monitoring and control are possible using read and write register commands. Other
commands are supported to provide additional functions.
Electrical Interface
The hardware or electrical interface in the MM300 is two-wire RS485. In a two-wire link,
data is transmitted and received over the same two wires. Although RS485 two wire
communication is bi-directional, the data is never transmitted and received at the same
time. This means that the data flow is half duplex.
RS485 lines should be connected in a daisy chain configuration with terminating networks
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 W resistor in series with a 1 nF
ceramic capacitor when used with Belden 9841 RS485 wire. Shielded wire should always
be used to minimize noise. The shield should be connected to all of the MM300s as well as
the master, then grounded at one location only. This keeps the ground potential at the
same level for all of the devices on the serial link.
NOTE:
Polarity is important in RS485 communications. The '+' (positive) terminals of every device
must be connected together.
E
Data Frame Format and Data Rate
One data frame of an asynchronous transmission to or from a MM300 typically consists of
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).
Modbus protocol can be implemented at any standard communication speed. The
MM300supports operation at 9600, 19200, 38400, 57600, and 115200 baud.
Data Packet Format
A complete request/response sequence consists of the following bytes (transmitted as
separate data frames):
2MM300 MOTOR MANAGEMENT SYSTEM – COMMUNICATIONS GUIDE
COMMUNICATIONS GUIDERS485 INTERFACE (MODBUS RTU)
Master Request Transmission:
SLAVE ADDRESS: 1 byte
FUNCTION CODE: 1 byte
DATA: variable number of bytes depending on FUNCTION CODE
CRC: 2 bytes
Slave Response Transmission:
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 userassigned 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.
FUNCTION CODE: This is the second byte of every transmission. Modbus defines function
codes of 1 to 127.
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.
CRC: This is a two byte error checking code.
Error Checking
CRC-16 Algorithm
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, MSByte 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 a MM300 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 MM300 performing
any incorrect operation.
The CRC-16 calculation 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.
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 following symbols are used in the algorithm:
—>: data transfer
A: 16 bit working register
MM300 MOTOR MANAGEMENT SYSTEM – COMMUNICATIONS GUIDE3
RS485 INTERFACE (MODBUS RTU)COMMUNICATIONS GUIDE
AL: low order byte of A
AH: high order byte of A
CRC: 16 bit CRC-16 value
i, j: loop counters
(+): logical exclusive or operator
Di: i-th data byte (i = 0 to N-1)
G: 16 bit characteristic polynomial = 1010000000000001 with MSbit dropped and bit order
reversed
shr(x): shift right (the LSbit of the low order byte of x shifts into a carry flag, a '0' is shifted
into the MSbit of the high order byte of x, all other bits shift right one location
The algorithm is:
1. FFFF hex —> A
2. 0 —> i
3. 0 —> j
4. Di (+) AL —> AL
5. j+1 —> j
6. shr(A)
7. is there a carry? No: go to 8. Yes: G (+) A —> A
8. is j = 8? No: go to 5. Yes: go to 9.
9. i+1 —> i
10. is i = N? No: go to 3. Yes: go to 11.
11. A —> CRC
Timing
Data packet synchronization is maintained by timing constraints. The receiving device
must measure the time between the reception of characters. If 3.5 character times elapse
without a new character or completion of the packet, then the communication link must
be reset (i.e. all slaves start listening for a new transmission from the master). Thus at 9600
baud a delay of greater than 3.5 x 1 / 9600 x 10 x = x 3.65 x ms will cause the
communication link to be reset.
MM300 supported functions
The following functions are supported by the MM300:
•FUNCTION CODE 03 - Read Setpoints and Actual Values
•FUNCTION CODE 04 - Read Setpoints and Actual Values
•FUNCTION CODE 05 - Execute Operation
•FUNCTION CODE 06 - Store Single Setpoint
•FUNCTION CODE 07 - Read Device Status
•FUNCTION CODE 08 - Loopback Test
•FUNCTION CODE 10 - Store Multiple Setpoints
Modbus Functions
Function Code 03H
Modbus implementation: Read Holding Registers
4MM300 MOTOR MANAGEMENT SYSTEM – COMMUNICATIONS GUIDE
COMMUNICATIONS GUIDERS485 INTERFACE (MODBUS RTU)
MM300 implementation: Read Setpoints
For the MM300 implementation of Modbus, this function code can be used to read any
setpoints (“holding registers”). Holding registers are 16 bit (two byte) values transmitted
high order byte first . Thus all MM300 Setpoints are sent as two bytes. The maximum
number of registers that can be read in one transmission is 125.
The slave response to this function code 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.
For example, consider a request for slave 17 to respond with 3 registers starting at address
006B. For this example the register data in these addresses is as follows:
AddressData
006B022B
006C0000
006D0064
The master/slave packets have the following format:
Table 1: Master/slave packet format for function code 03H
MASTER TRANSMISSIONBYTESEXAMPLEDESCRIPTION
SLAVE ADDRESS111message for slave
FUNCTION CODE103read registers
DATA STARTING ADDRESS200 6Bdata starting at
NUMBER OF SETPOINTS200 033 registers = 6
CRC276 87CRC error code
17
006B
bytes total
Function Code 04H
SLAVE RESPONSEBYTESEXAMPLEDESCRIPTION
SLAVE ADDRESS111message from
slave 17
FUNCTION CODE103read registers
BYTE COUNT1063 registers = 6
bytes
DATA 1 (see definition above) 202 2Bvalue in address
006B
DATA 2 (see definition above) 200 00value in address
006C
DATA 3 (see definition above) 200 64value in address
006D
CRC254 83CRC error code
Modbus Implementation: Read Input Registers
MM300 implementation: Read Actual Values
For the MM300 implementation of Modbus, this function code can be used to read any
actual values (“input registers”). Input registers are 16 bit (two byte) values transmitted high
order byte first . Thus all MM300 Actual Values are sent as two bytes. The maximum
number of registers that can be read in one transmission is 125.
MM300 MOTOR MANAGEMENT SYSTEM – COMMUNICATIONS GUIDE5
RS485 INTERFACE (MODBUS RTU)COMMUNICATIONS GUIDE
The slave response to this function code is the slave address, function code, a count of the
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 .
For example, request slave 17 to respond with 1 register starting at address 0008. For this
example the value in this register (0008) is 0000.
Table 2: Master/slave packet format for function code 04H
MASTER TRANSMISSIONBYTESEXAMPLEDESCRIPTION
SLAVE ADDRESS111message for slave
FUNCTION CODE104read registers
DATA STARTING ADDRESS200 08data starting at
NUMBER OF ACTUAL VALUES 200 011 register = 2 bytes
CRC2B2 98CRC error code
SLAVE RESPONSEBYTESEXAMPLEDESCRIPTION
SLAVE ADDRESS111message from
FUNCTION CODE104read registers
BYTE COUNT1021 register = 2 bytes
DATA (see definition above)200 00value in address
CRC278 F3CRC error code
17
0008
slave 17
0008
Function Code 05H
Modbus Implementation: Force Single Coil
MM300 Implementation: Execute Operation
This function code allows the master to request a MM300 to perform specific command
operations.
For example, to request slave 17 to execute operation code 1 (reset), we have the following
master/slave packet format:
Table 3: Master/slave packet format for function code 05H
MASTER TRANSMISSIONBYTESEXAMPLEDESCRIPTION
SLAVE ADDRESS111message for slave
17
FUNCTION CODE105execute operation
OPERATION CODE200 01operation code 1
CODE VALUE2FF 00perform function
CRC2DF 6ACRC error code
SLAVE RESPONSEBYTESEXAMPLEDESCRIPTION
SLAVE ADDRESS111message from
slave 17
FUNCTION CODE105execute operation
OPERATION CODE200 01operation code 1
CODE VALUE2FF 00perform function
CRC2DF 6ACRC error code
6MM300 MOTOR MANAGEMENT SYSTEM – COMMUNICATIONS GUIDE
COMMUNICATIONS GUIDERS485 INTERFACE (MODBUS RTU)
The commands that can be performed by the MM300 using function code 05 can also be
initiated by using function code 10.
Operation CodeDescription
1Reset
2Lockout Reset
3Stop
4Start A
5Start B
96Clear Last Trip Data Prompt
97Reset MWh and Mvarh Meters
99Clear Counters
100Clear Event Records
102Clear Maintenance Timer
112Clear RTD Maximums
113Reset Motor Information
114Auto Mode
115Manual Mode
116Manual Inhibit
117Manual Restore
Function Code 06H
Modbus Implementation: Preset Single Register
MM300 Implementation: Store Single Setpoint
This command allows the master to store a single setpoint into the memory of a MM300
The slave response to this function code is to echo the entire master transmission.
For example, request slave 17 to store the value 2 in setpoint address 04 5C. After the
transmission in this example is complete, setpoints address 04 5C will contain the value
01F4. The master/slave packet format is shown below:
Table 4: Master/slave packet format for function code 06H
MASTER TRANSMISSIONBYTESEXAMPLEDESCRIPTION
SLAVE ADDRESS111message for slave
17
FUNCTION CODE106store single
setpoint
DATA STARTING ADDRESS204 5Csetpoint address
04 5C
DATA200 02data for setpoint
address 04 5C
CRC2CB B9CRC error code
MM300 MOTOR MANAGEMENT SYSTEM – COMMUNICATIONS GUIDE7
RS485 INTERFACE (MODBUS RTU)COMMUNICATIONS GUIDE
SLAVE RESPONSEBYTESEXAMPLEDESCRIPTION
SLAVE ADDRESS111message from
FUNCTION CODE106store single
DATA STARTING ADDRESS204 5Csetpoint address
DATA200 02data stored in
CRC2CB B9CRC error code
slave 17
setpoint
04 5C
setpoint address
04 5C
Function Code 07H
Modbus Implementation: Read Exception Status
MM300 Implementation: Read Device Status
This is a function used to quickly read the status of a selected device. A short message
length allows for rapid reading of status. The status byte returned will have individual bits
set to 1 or 0 depending on the status of the slave device. For this example, consider the
following MM300 general status byte:
The master/slave packets have the following format:
Table 5: Function code 7 bitmask
BitFunction
0Alarm
1Trip
2Internal fault
3Auto
4Contactor A
5Contactor B
6Contact output 3
7Drive available (communications control)
Table 6: Master/slave packet format for function code 07H
MASTER TRANSMISSIONBYTESEXAMPLEDESCRIPTION
SLAVE ADDRESS111message for slave
FUNCTION CODE107read device status
CRC24C 22CRC error code
SLAVE RESPONSEBYTESEXAMPLEDESCRIPTION
SLAVE ADDRESS111message from
FUNCTION CODE107read device status
DEVICE STATUS (see
definition above)
CRC222 28CRC error code
12Cstatus = 00101100
17
slave 17
(in binary)
8MM300 MOTOR MANAGEMENT SYSTEM – COMMUNICATIONS GUIDE
COMMUNICATIONS GUIDERS485 INTERFACE (MODBUS RTU)
Function Code 08H
Modbus Implementation: Loopback
Test MM300 Implementation: Loopback Test
This function is used to test the integrity of the communication link. The MM300 will echo
the request.
For example, consider a loopback test from slave 17:
Table 7: Master/slave packet format for function code 08H
MASTER TRANSMISSIONBYTESEXAMPLEDESCRIPTION
SLAVE ADDRESS111message for slave
FUNCTION CODE108loopback test
DIAG CODE200 00must be 00 00
DATA200 00must be 00 00
CRC2E0 0BCRC error code
SLAVE RESPONSEBYTESEXAMPLEDESCRIPTION
SLAVE ADDRESS111message from
FUNCTION CODE108loopback test
DIAG CODE200 00must be 00 00
DATA200 00must be 00 00
CRC2E0 0BCRC error code
17
slave 17
Function Code 10H
Modbus Implementation: Preset Multiple Registers
MM300 Implementation: Store Multiple Setpoints
This function code allows multiple Setpoints to be stored into the MM300 memory. Modbus
“registers” are 16-bit (two byte) values transmitted high order byte first. Thus all MM300
setpoints are sent as two bytes. The maximum number of Setpoints that can be stored in
one transmission is dependent on the slave device. Modbus allows up to a maximum of 60
holding registers to be stored. The MM300 response to this function code is to echo the
slave address, function code, starting address, the number of Setpoints stored, and the
CRC.
For example, consider a request for slave 17 to store the value 00 02 to setpoint address
04 5C and the value 01 F4 to setpoint address 04 5D. After the transmission in this example
is complete, MM300 slave 17 will have the following setpoints information stored:
AddressData
04 5C00 02
04 5D01 F4
The master/slave packets have the following format:
MM300 MOTOR MANAGEMENT SYSTEM – COMMUNICATIONS GUIDE9
RS485 INTERFACE (MODBUS RTU)COMMUNICATIONS GUIDE
Table 8: Master/slave packet format for function code 10H
MASTER TRANSMISSIONBYTESEXAMPLEDESCRIPTION
SLAVE ADDRESS111message for slave
FUNCTION CODE110store setpoints
DATA STARTING ADDRESS204 5Csetpoint address
NUMBER OF SETPOINTS200 022 setpoints = 4
BYTE COUNT1044 bytes of data
DATA 1200 02data for setpoint
DATA 2201 F4data for setpoint
CRC231 11CRC error code
SLAVE RESPONSEBYTESEXAMPLEDESCRIPTION
SLAVE ADDRESS111message from
FUNCTION CODE110store setpoints
DATA STARTING ADDRESS204 5Csetpoint address
NUMBER OF SETPOINTS200 022 setpoints
CRC282 7ACRC error code
17
04 5C
bytes total
address 04 5C
address 04 5D
slave 17
04 5C
Error Responses
When a MM300 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 MM300.
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 MM300 implements the following exception response codes:
01 - ILLEGAL FUNCTION
The function code transmitted is not one of the functions supported by the MM300.
02 - ILLEGAL DATA ADDRESS
The address referenced in the data field transmitted by the master is not an allowable
address for the MM300.
03 - ILLEGAL DATA VALUE
The value referenced in the data field transmitted by the master is not within range for the
selected data address.
10MM300 MOTOR MANAGEMENT SYSTEM – COMMUNICATIONS GUIDE
COMMUNICATIONS GUIDERS485 INTERFACE (MODBUS RTU)
Modbus memory map
ModbusHexDescriptionMinMaxStepUnitsFormat DefaultSize in
409140391Max Motor Stopped Time101001010hrsF1*100101
409150392Reserved------------------1
409160393Reserved------------------1
START INHIBIT
409170394Start Inhibit Margin0111%F1*111
409180395Reserved------------------1
409190396Starts/Hour Limit161---F1*61
409200397Time Between Starts136011sF1*36011
409210398Reserved------------------1
CHANGE MODE
409220399Change Mode on Comm Alarm 011---FC12601
40923039AChange Mode when running011---FC12601
40924039BReserved------------------1
40925039CReserved------------------1
RESTART BLOCK
40926039DRestart Block Time1500011sF1*500011
40927039EReserved------------------1
▼▼▼▼▼ ▼▼▼▼ ▼
41039040EReserved1
CALIBRATION
41040040FCalibration Date02033603021---F1802
410420411Calibration Time03897577951---F1902
410440413Reserved------------------1
▼▼▼▼▼ ▼▼▼▼ ▼
411050450Reserved1
SECURITY
411060451Passcode Level 111111 555561---F1*111111
411070452Passcode Level 211111 555561---F1*222221
411080453Reserved------------------1
411090454Access Switch Level131---F111
411100455Comms Security011---FC12601
411110456MCC Setpoint Access011---FC12611
411120457Passcode Entry0555551---F101
411130458Reserved------------------1
411140459Reserved------------------1
41115045AReserved------------------1
41116045BReserved------------------1
FLEXLOGIC TIMERS
41117045CTimer 1 Type021---FC14101
41118045DTimer 1 Pickup Delay010001---F111
41119045ETimer 1 Dropout Delay010001---F111
41120045FReserved------------------1
Words
26MM300 MOTOR MANAGEMENT SYSTEM – COMMUNICATIONS GUIDE
COMMUNICATIONS GUIDERS485 INTERFACE (MODBUS RTU)
ModbusHexDescriptionMinMaxStepUnitsFormat DefaultSize in
▼▼▼▼▼ ▼▼▼▼ ▼
411240463Reserved------------------1
411250464Timer 2 Type021---FC14101
411260465Timer 2 Pickup Delay010001---F111
411270466Timer 2 Dropout Delay010001---F111
411280467Reserved------------------1
▼▼▼▼▼ ▼▼▼▼ ▼
41132046BReserved------------------1
41133046CTimer 3 Type021---FC14101
41134046DTimer 3 Pickup Delay010001---F111
41135046ETimer 3 Dropout Delay010001---F111
41136046FReserved------------------1
▼▼▼▼▼ ▼▼▼▼ ▼
411400473Reserved------------------1
411410474Timer 4 Type021---FC14101
411420475Timer 4 Pickup Delay010001---F111
411430476Timer 4 Dropout Delay010001---F111
411440477Reserved------------------1
▼▼▼▼▼ ▼▼▼▼ ▼
41148047BReserved------------------1
41149047CTimer 5 Type021---FC14101
41150047DTimer 5 Pickup Delay010001---F111
41151047ETimer 5 Dropout Delay010001---F111
41152047FReserved------------------1
▼▼▼▼▼ ▼▼▼▼ ▼
411560483Reserved------------------1
411570484Timer 6 Type021---FC14101
411580485Timer 6 Pickup Delay010001---F111
411590486Timer 6 Dropout Delay010001---F111
411600487Reserved------------------1
▼▼▼▼▼ ▼▼▼▼ ▼
41164048BReserved------------------1
41165048CTimer 7 Type021---FC14101
41166048DTimer 7 Pickup Delay010001---F111
41167048ETimer 7 Dropout Delay010001---F111
41168048FReserved------------------1
▼▼▼▼▼ ▼▼▼▼ ▼
411720493Reserved------------------1
411730494Timer 8 Type021---FC14101
411740495Timer 8 Pickup Delay010001---F111
411750496Timer 8 Dropout Delay010001---F111
411760497Reserved------------------1
▼▼▼▼▼ ▼▼▼▼ ▼
41180049BReserved------------------1
41181049CTimer 9 Type021---FC14101
41182049DTimer 9 Pickup Delay010001---F111
Words
MM300 MOTOR MANAGEMENT SYSTEM – COMMUNICATIONS GUIDE27
RS485 INTERFACE (MODBUS RTU)COMMUNICATIONS GUIDE
ModbusHexDescriptionMinMaxStepUnitsFormat DefaultSize in
41183049ETimer 9 Dropout Delay010001---F111
41184049FReserved------------------1
▼▼▼▼▼ ▼▼▼▼ ▼
4118804A3Reserved------------------1
4118904A4Timer 10 Type021---FC14101
4119004A5Timer 10 Pickup Delay010001---F111
4119104A6Timer 10 Dropout Delay010001---F111
4119204A7Reserved------------------1
▼▼▼▼▼ ▼▼▼▼ ▼
4119604ABReserved------------------1
4119704ACTimer 11 Type021---FC14101
4119804ADT imer 11 Pickup Delay010001---F111
4119904AET imer 11 Dropout Delay010001---F111
4120004AFReserved------------------1
▼▼▼▼▼ ▼▼▼▼ ▼
4120404B3Reserved------------------1
4120504B4Timer 12 Type021---FC14101
4120604B5Timer 12 Pickup Delay010001---F111
4120704B6Timer 12 Dropout Delay010001---F111
4120804B7Reserved------------------1
▼▼▼▼▼ ▼▼▼▼ ▼
4121204BBReserved------------------1
4121304BCTimer 13 Type021---FC14101
4121404BDT imer 13 Pickup Delay010001---F111
4121504BET imer 13 Dropout Delay010001---F111
4121604BFReserved------------------1
▼▼▼▼▼ ▼▼▼▼ ▼
4122004C3Reserved------------------1
4122104C4Timer 14 Type021---FC14101
4122204C5Timer 14 Pickup Delay010001---F111
4122304C6Timer 14 Dropout Delay010001---F111
4122404C7Reserved------------------1
▼▼▼▼▼ ▼▼▼▼ ▼
4122804CBReserved------------------1
4122904CCTimer 15 Type021---FC14101
4123004CDT imer 15 Pickup Delay010001---F111
4123104CET imer 15 Dropout Delay010001---F111
4123204CFReserved------------------1
▼▼▼▼▼ ▼▼▼▼ ▼
4123604D3Reserved------------------1
4123704D4Timer 16 Type021---FC14101
4123804D5Timer 16 Pickup Delay010001---F111
4123904D6Timer 16 Dropout Delay010001---F111
4124004D7Reserved------------------1
▼▼▼▼▼ ▼▼▼▼ ▼
4124404DBReserved------------------1
Words
28MM300 MOTOR MANAGEMENT SYSTEM – COMMUNICATIONS GUIDE
COMMUNICATIONS GUIDERS485 INTERFACE (MODBUS RTU)
ModbusHexDescriptionMinMaxStepUnitsFormat DefaultSize in
4124504DCT imer 17 Type021---FC14101
4124604DDTimer 17 Pickup Delay010001---F111
4124704DETimer 17 Dropout Delay010001---F111
4124804DFReserved------------------1
▼▼▼▼▼ ▼▼▼▼ ▼
4125204E3Reserved------------------1
4125304E4Timer 18 Type021---FC14101
4125404E5Timer 18 Pickup Delay010001---F111
4125504E6Timer 18 Dropout Delay010001---F111
4125604E7Reserved------------------1
▼▼▼▼▼ ▼▼▼▼ ▼
4126004EBReserved------------------1
4126104ECT imer 19 Type021---FC14101
4126204EDTimer 19 Pickup Delay010001---F111
4126304EETimer 19 Dropout Delay010001---F111
4126404EFReserved------------------1
▼▼▼▼▼ ▼▼▼▼ ▼
4126804F3Reserved------------------1
4126904F4Timer 20 Type021---FC14101
4127004F5Timer 20 Pickup Delay010001---F111
4127104F6Timer 20 Dropout Delay010001---F111
4127204F7Reserved------------------1
▼▼▼▼▼ ▼▼▼▼ ▼
4127604FBReserved------------------1
4127704FCTimer 21 Type021---FC14101
4127804FDTimer 21 Pickup Delay010001---F111
4127904FET imer 21 Dropout Delay010001---F111
4128004FFReserved------------------1
▼▼▼▼▼ ▼▼▼▼ ▼
412840503Reserved------------------1
412850504Timer 22 Type021---FC14101
412860505Timer 22 Pickup Delay010001---F111
412870506Timer 22 Dropout Delay010001---F111
412880507Reserved------------------1
▼▼▼▼▼ ▼▼▼▼ ▼
41292050BReserved------------------1
41293050CTimer 23 Type021---FC14101
41294050DTimer 23 Pickup Delay010001---F111
41295050ETimer 23 Dropout Delay010001---F111
41296050FReserved------------------1
▼▼▼▼▼ ▼▼▼▼ ▼
413000513Reserved------------------1
413010514Timer 24 Type021---FC14101
413020515Timer 24 Pickup Delay010001---F111
413030516Timer 24 Dropout Delay010001---F111
413040517Reserved------------------1
Words
MM300 MOTOR MANAGEMENT SYSTEM – COMMUNICATIONS GUIDE29
RS485 INTERFACE (MODBUS RTU)COMMUNICATIONS GUIDE
ModbusHexDescriptionMinMaxStepUnitsFormat DefaultSize in
▼▼▼▼▼ ▼▼▼▼ ▼
41308051BReserved------------------1
41309051CTimer 25 Type021---FC14101
41310051DTimer 25 Pickup Delay010001---F111
41311051ETimer 25 Dropout Delay010001---F111
41312051FReserved------------------1
▼▼▼▼▼ ▼▼▼▼ ▼
413160523Reserved------------------1
413170524Timer 26 Type021---FC14101
413180525Timer 26 Pickup Delay010001---F111
413190526Timer 26 Dropout Delay010001---F111
413200527Reserved------------------1
▼▼▼▼▼ ▼▼▼▼ ▼
41324052BReserved------------------1
41325052CTimer 27 Type021---FC14101
41326052DTimer 27 Pickup Delay010001---F111
41327052ETimer 27 Dropout Delay010001---F111
41328052FReserved------------------1
▼▼▼▼▼ ▼▼▼▼ ▼
413320533Reserved------------------1
413330534Timer 28 Type021---FC14101
413340535Timer 28 Pickup Delay010001---F111
413350536Timer 28 Dropout Delay010001---F111
413360537Reserved------------------1
▼▼▼▼▼ ▼▼▼▼ ▼
41340053BReserved------------------1
41341053CTimer 29 Type021---FC14101
41342053DTimer 29 Pickup Delay010001---F111
41343053ETimer 29 Dropout Delay010001---F111
41344053FReserved------------------1
▼▼▼▼▼ ▼▼▼▼ ▼
413480543Reserved------------------1
413490544Timer 30 Type021---FC14101
413500545Timer 30 Pickup Delay010001---F111
413510546Timer 30 Dropout Delay010001---F111
413520547Reserved------------------1
▼▼▼▼▼ ▼▼▼▼ ▼
41356054BReserved------------------1
41357054CTimer 31 Type021---FC14101
41358054DTimer 31 Pickup Delay010001---F111
41359054ETimer 31 Dropout Delay010001---F111
41360054FReserved------------------1
▼▼▼▼▼ ▼▼▼▼ ▼
413640553Reserved------------------1
413650554Timer 32 Type021---FC14101
413660555Timer 32 Pickup Delay010001---F111
Words
30MM300 MOTOR MANAGEMENT SYSTEM – COMMUNICATIONS GUIDE
COMMUNICATIONS GUIDERS485 INTERFACE (MODBUS RTU)
ModbusHexDescriptionMinMaxStepUnitsFormat DefaultSize in
413670556Timer 32 Dropout Delay010001---F111
413680557Reserved------------------1
▼▼▼▼▼ ▼▼▼▼ ▼
41372055BReserved------------------1
CONTACT INPUT ASSIGNMENT
41373055CU/V Restart Inhibit0573440---FC14201
41374055DLockout Reset0573440---FC14201
41375055EAccess Switch0573440---FC14201
41376055FField Permissive0573440---FC14201
413770560Comms Permissive0573440---FC14201
413780561Forward Limit0573440---FC14201
413790562Reverse Limit0573440---FC14201
413800563Remote Reset0573440---FC14201
413810564MCC Permissive0573440---FC14201
413820565Hard Wired Start A0573440---FC14201
413830566Hard Wired Start B0573440---FC14201
413840567Hard Wired Stop0573440---FC14201
413850568Hard Wired Permissive0573440---FC14201
413860569Field Start A0573440---FC14201
41387056AField Start B0573440---FC14201
41388056BField Stop0573440---FC14201
41389056CContactor Status A0573440---FC14201
41390056DContactor Status B0573440---FC14201
41391056EAuto/Manual Switch0573440---FC14201
41392056FReserved------------------1
413930570Test Switch0573440---FC14201
413940571Process Interlock A0573440---FC14201
413950572Process Interlock B0573440---FC14201
413960573Process Interlock C0573440---FC14201
413970574Process Interlock D0573440---FC14201
413980575Process Interlock E0573440---FC14201
413990576Process Interlock F0573440---FC14201
414000577Process Interlock G0573440---FC14201
414010578Process Interlock H0573440---FC14201
414020579Process Interlock I0573440---FC14201
41403057AProcess Interlock J0573440---FC14201
41404057BReserved------------------1
▼▼▼▼▼ ▼▼▼▼ ▼
4147005BDReserved1
SELF TEST
4147105BESelf Test Action011---FC11101
4147205BFReserved------------------1
4147305C0Reserved------------------1
4147405C1Reserved------------------1
4147505C2Reserved------------------1
LEDs
Words
MM300 MOTOR MANAGEMENT SYSTEM – COMMUNICATIONS GUIDE31
RS485 INTERFACE (MODBUS RTU)COMMUNICATIONS GUIDE
ModbusHexDescriptionMinMaxStepUnitsFormat DefaultSize in
4147605C3Orange LED Intensity0151---FC14701
4147705C4Green LED Intensity0151---FC14701
4147805C5Red LED Intensity0151---FC14701
4147905C6LED colour invert011---FC17701
4148005C7Tripped LED Flasher011---FC10301
4148105C8Reserved------------------1
▼▼▼▼▼ ▼▼▼▼ ▼
4149405D5Reserved------------------1
4149505D6USER1 LED Assignment0573441---FC14201
4149605D7USER1 LED Colour031---FC15711
4149705D8USER2 LED Assignment0573441---FC14201
4149805D9USER2 LED Colour031---FC15711
4149905DAUSER3 LED Assignment0573441---FC14201
4150005DBUSER3 LED Colour031---FC15711
4150105DCReserved------------------1
▼▼▼▼▼ ▼▼▼▼ ▼
4151405E9Reserved------------------1
CONTACT OUTPUTS
4151505EAContact Output 10573440---FC14201
4151605EBContact Output 20573440---FC14201
4151705ECContact Output 30573440---FC14201
4151805EDContact Output 40573440---FC14201
▼▼▼▼▼ ▼▼▼▼ ▼
415430606Contact Output 290573440---FC14201
415440607Contact Output 300573440---FC14201
415450608Contact Output 310573440---FC14201
415460609Contact Output 320573440---FC14201
41547060AReserved------------------1
▼▼▼▼▼ ▼▼▼▼ ▼
41552060FReserved------------------1
UNDERVOLTAGE RESTART
415530610Under Voltage Restart011---FC12601
415540611UVR Short Dip Time10051010msF1*2001
415550612UVR Med Dip Time11001sF2201
415560613UVR Long Dip Time56055minF2*6051
415570614UVR Med Dip Delay26002sF2201
415580615UVR Long Dip Delay2120002sF21001
415590616UVR Dropout Level601001%F1651
415600617UVR Pickup Level601001%F1901
415610618Reserved------------------1
▼▼▼▼▼ ▼▼▼▼ ▼
415710622Reserved------------------1
AUTO / MANUAL CONTROL
415720623Comms Start Ctrl011---FC12601
415730624Comms Stop Mode011---FC17201
415740625Hard Wired Start Ctrl011---FC12601
Words
32MM300 MOTOR MANAGEMENT SYSTEM – COMMUNICATIONS GUIDE
COMMUNICATIONS GUIDERS485 INTERFACE (MODBUS RTU)
ModbusHexDescriptionMinMaxStepUnitsFormat DefaultSize in
415750626Hard Wired Stop Mode011---FC17201
415760627Hard Wired Stop Actn011---FC17401
415770628Hard Wired 2W/3W011---FC17311
415780629Field Start Ctrl011---FC12601
41579062AField Stop Mode011---FC17201
41580062BField Stop Action011---FC17401
41581062CField 2W/3W011---FC17311
41582062DMCC Start Ctrl011---FC12601
41583062EMCC Stop Mode011---FC17201
41584062FMCC Stop Action011---FC17401
415850630Test Auto Mode021---FC17511
415860631Test Manual Mode021---FC17501
415870632External Stop Action011---FC17401
415880633Auto/Manual Key011---FC12601
415890634Reserved------------------7
▼▼▼▼▼ ▼▼▼▼ ▼
41696069FReserved1
FLEXLOGIC EQUATION
4169706A0Flex Equation0655351---FC1421024512
4220908A0Reserved------------------1
▼▼▼▼▼ ▼▼▼▼ ▼
437630EB2Reserved2
1.Maximum setpoint values represent OFF.
Words
MM300 MOTOR MANAGEMENT SYSTEM – COMMUNICATIONS GUIDE33
RS485 INTERFACE (MODBUS RTU)COMMUNICATIONS GUIDE
Format codes
CodeTypeDefinition
F116 bitsUNSIGNED VALUE
Example: 1234 stored as 1234
F216 bitsUNSIGNED VALUE, 1 DECIMAL PLACE
Example: 123.4 stored as 1234
F316 bitsUNSIGNED VALUE, 2 DECIMAL PLACES
Example: 12.34 stored as 1234
F416 bits2’s COMPLEMENT SIGNED VALUE
Example: -1234 stored as -1234 i.e. 64302
F616 bits2’s COMPLEMENT SIGNED VALUE, 2 DECIMAL PLACES
Example: -12.34 stored as -1234 i.e. 64302
F932 bitsUNSIGNED LONG VALUE
1st 16 bitsHigh Order Word of Long Value
2nd 16 bitsLow Order Word of Long Value
Example: 123456 stored as 123456
i.e. 1st word: 0001 hex, 2nd word: E240 hex
F1032 bitsUNSIGNED LONG VALUE, 1 DECIMAL PLACE
1st 16 bitsUNSIGNED LONG VALUE, 1 DECIMAL PLACE
2nd 16 bitsLow Order Word of Long Value
Example: 12345.6 stored as 123456
i.e. 1st word: 0001 hex, 2nd word: E240 hex
F1332 bits2’s COMPLEMENT SIGNED LONG VALUE, 1 DECIMAL PLACE
1st 16 bitsHigh Order Word of Long Value
2nd 16 bitsLow Order Word of Long Value
Example: -12345.6 stored as -123456
i.e. 1st word: FFFE hex, 2nd word: 1DC0 hex
F1516 bitsHARDWARE REVISION
0Prototype
1A
2B
3C
4D
5E
6F
7G
8H
9I
10J
11K
12L
13M
14N
15O
16P
17Q
34MM300 MOTOR MANAGEMENT SYSTEM – COMMUNICATIONS GUIDE
COMMUNICATIONS GUIDERS485 INTERFACE (MODBUS RTU)
CodeTypeDefinition
18R
19S
20T
21U
22V
23W
24X
25Y
26Z
F1732 bitsUNSIGNED LONG VALUE, 3 DECIMAL PLACES
1st 16 bitsHigh Order Word of Long Value
2nd 16 bitsLow Order Word of Long Value
Example: 123456 stored as 123456
i.e. 1st word: 0001 hex, 2nd word: E240 hex
F1832 bitsDATE MM/DD/YYYY
1st byteMonth 1 to 12
2nd byteDay 1 to 31
3rd and 4th byteYear 1995 to 2094
Example: Feb 20, 1995 stored as 34867142
i.e. 1st word: 0214, 2nd word 07C6
F1932 bitsTIME HH:MM:SS:hh
1st byteHours 0 to 23
2nd byteMinutes 0 to 59
3rd byteSeconds 0 to 59
4th byteHundredths of seconds 0 to 99
Example: 2:05pm stored as 235208704
i.e. 1st word: 0E05, 2nd word 0000
F2032 bits2’s COMPLEMENT SIGNED LONG VALUE
1st 16 bitsHigh Order Word of Long Value
2nd 16 bitsLow Order Word of Long Value
Note: -1 means “Never”
F2116 bits2’s COMPLEMENT SIGNED VALUE, 2 DECIMAL PLACES
< 0Leading Power Factor - Negative
> 0Lagging Power Factor - Positive
Example: Power Factor of 0.87 lag is used as 87
i.e. 0057
F2216 bitsTWO 8-BIT CHARACTERS PACKED INTO 16-BIT UNSIGNED
MSBFirst Character
LSBSecond Character
Example: String ‘AB’ stored as 4142 hex
FC10116 bitsRS 485 Baud Rate
09600 baud
119200 baud
238400 baud
357600 baud
4115200 baud
Power Factor
MM300 MOTOR MANAGEMENT SYSTEM – COMMUNICATIONS GUIDE35
RS485 INTERFACE (MODBUS RTU)COMMUNICATIONS GUIDE
CodeTypeDefinition
FC10316 bitsOff / On or No / Yes Selection
0OFF / NO
1ON / YES
FC10416 bitsGround CT Type
0None
1Residual
2CBCT 2000:1
FC10516 bitsDifferential CT Type
0None
11 A Secondary
25 A Secondary
3Direct Connect
FC10616 bitsVoltage Transformer Connection Type
0Wye
1Delta
FC10716 bitsSupply Frequency
060
150
FC10916 bitsFlex Logic Status
0OK
1Unknown Token
2Too Many Latches
3Too Many Timers
4Too Many + OneShots
5Too Many - OneShots
6Too Many Duel OneShots
7Stack Overflow
8Stack Underflow
9Program Too Long
FC11116 bitsTrip Relays
0Trip
1Alarm
FC11216 bitsCommunication Status
0Error
1OK
FC11616 bitsSwitch Type
0Open
1Closed
FC12116 bitsRTD Application
0None
1Stator
2Bearing
3Ambient
4Other
FC12216 bitsRTD Voting Selection
0OFF
1RTD #1
36MM300 MOTOR MANAGEMENT SYSTEM – COMMUNICATIONS GUIDE
COMMUNICATIONS GUIDERS485 INTERFACE (MODBUS RTU)
CodeTypeDefinition
2RTD #2
3RTD #3
4RTD #4
5RTD #5
6RTD #6
FC12616 bitsDisabled / Enabled Selection
0Disabled
1Enabled
FC12816 bitsCommand Status
0Manual
1Auto
2Manual Inhibit
3Auto/ Manual
4Hardwired Auto
5None
FC12916 bitsQuick Status Status
Bit 0Alarm
Bit 1Trip
Bit 2Self Test Fault
Bit 3Auto
Bit 4Contactor A
Bit 5Contactor B
Bit 6Contact Output 3
Bit 7Drive Available
FC13016 bitsLED Flash
Bit 0Running
Bit 1Stopped
Bit 2Tripped
Bit 3Alarm
Bit 4Comms OK
Bit 5Auto
Bit 6Manual
Bit 7USER1
Bit 8USER2
Bit 9USER3
Bit 1050%
Bit 1180%
Bit 12100%
FC13116 bitsComm Fail Mode
1Serial
2Serial & Ethernet
4Serial & FieldBus
8Ethernet
16FieldBus
32Ethernet & Fieldbus
64All
FC13416 bitsCause of Event
MM300 MOTOR MANAGEMENT SYSTEM – COMMUNICATIONS GUIDE37
RS485 INTERFACE (MODBUS RTU)COMMUNICATIONS GUIDE
CodeTypeDefinition
0No Event/Trip To Date
1Control Power Lost
2Control Power Applied
3Date or Time Set
4Reset
5Lockout Reset
0x8002Any Trip
0x8042Thermal O/L Trip
0x8082Ground Fault Trip
0x80C2Acceleration Trip
0x8102Phase Reversal Trip
0x8142UnderPower Trip
0x8182UnderVoltage Trip
0x81C2OverVoltage Trip
0x8202Mechanical Jam Trip
0x8242UnderCurrent Trip
0x8282Unbalance Trip
0x82C2RTD 1 Trip
0x8302RTD 2 Trip
0x8342RTD 3 Trip
0x8382RTD 4 Trip
0x83C2RTD 5 Trip
0x8402RTD 6 Trip
0x8442Comm Fail Trip
0x8482Relay Not Configured
0x84C2Process ILock A Trip
0x8502Process ILock B Trip
0x8542Process ILock C Trip
0x8582Process ILock D Trip
0x85C2Process ILock E Trip
0x8602Process ILock F Trip
0x8642Process ILock G Trip
0x8682Process ILock H Trip
0x86C2Process ILock I Trip
0x8702Process ILock J Trip
0x8742Hard Wired Trip
0x8782Field Trip
0x87C2MCC Trip
0x8802Aux U/V Trip
0x8842Emergency Stop
0x8882Fuse Fail Trip
0x88C2Open Control Circuit Trip
0x8902Thermistor Trip
0x89C2Self Test Trip
0xA002Any Alarm
0xA042Thermal Level Alarm
0xA082Ground Fault Alarm
38MM300 MOTOR MANAGEMENT SYSTEM – COMMUNICATIONS GUIDE
COMMUNICATIONS GUIDERS485 INTERFACE (MODBUS RTU)
CodeTypeDefinition
0xA0C2Acceleration Alarm
0xA102Phase Reversal Alarm
0xA142UnderPower Alarm
0xA182UnderVoltage Alarm
0xA1C2OverVoltage Alarm
0xA242UnderCurrent Alarm
0xA282Unbalance Alarm
0xA2C2RTD 1 Alarm
0xA302RTD 2 Alarm
0xA342RTD 3 Alarm
0xA382RTD 4 Alarm
0xA3C2RTD 5 Alarm
0xA402RTD 6 Alarm
0xA442RTD Open/Short Alarm
0xA482RTD Open/Short Alarm
0xA4C2Process ILock A Alarm
0xA502Process ILock B Alarm
0xA542Process ILock C Alarm
0xA582Process ILock D Alarm
0xA5C2Process ILock E Alarm
0xA602Process ILock F Alarm
0xA642Process ILock G Alarm
0xA682Process ILock H Alarm
0xA6C2Process ILock I Alarm
0xA702Process ILock J Alarm
0xA742Drive Failed to Start
0xA782Inverter Failed
0xA7C2Drive Stop Failed
0xA802Aux U/V Alarm
0xA842External Stop Alarm
0xA882Fuse Fail Alarm
0xA8C2Open Ctrl Cct Alarm
0xA902Thermistor Alarm
0xA982External Start A Alarm
0xA9C2External Start B Alarm
0xAA02Welded Contactor
0xAB02Load Increase Alarm
0XAB42Drive Greasing Alarm
0xAB82Contactor Inspect Alarm
0xABC2Max Stopped Alarm
0xAC82Comm Fail Alarm
0xC002Any Stop
0xC042Thermal Inhibit
0xC082AutoMode
0xC0C2Manual Mode
0xC102Auto/Manual Mode Input
0xC142Restart Inhibit
MM300 MOTOR MANAGEMENT SYSTEM – COMMUNICATIONS GUIDE39
RS485 INTERFACE (MODBUS RTU)COMMUNICATIONS GUIDE
CodeTypeDefinition
0xC182Contactor A
0xC1C2Contactor B
0xC202Forward Limit
0xC242Reverse Limit
0xC282Starts/Hr Inhibit
0xC2C2Time Between Inhibit
0xC3C2Comms Ctrl Active
0xC402Hard Wired Ctrl Active
0xC442Field Ctrl Active
0xC482MCC Ctrl Active
0xC4C2Process ILock A Stop
0xC502Process ILock B Stop
0xC542Process ILock C Stop
0xC582Process ILock D Stop
0xC5C2Process ILock E Stop
0xC602Process ILock F Stop
0xC642Process ILock G Stop
0xC682Process ILock H Stop
0xC6C2Process ILock I Stop
0xC702Process ILock J Stop
0xC742HW Stop
0xC782Field Stop
0xC7C2MCC Stop
0xC802Access Switch Closed
0xC842Test Switch Closed
0xC882Hard Wired Start A
0xC8C2Hard Wired Start B
0xC902Start A
0xC942Start B
0xC982Field Start A
0xC9C2Field Start B
0xCA02Contactor A Status
0xCA42Contactor B Status
0xCA82Remote Reset Closed
0xCAC2Lockout Reset Closed
0xCB02UV Restart
0xCB42Pre-Contactor
0xCB82MCC Start A
0xCBC2MCC Start B
0xCC02Bypass Contact
0xCC42Comm Start A
0xCC82Comm Start B
0xCCC2Comm Stop
0xCD02Fuse Fail Inhibit
0xCD42Phase Reversal Inhibit
0xCD82Low Aux Voltage Inhibit
FC13516 bitsMotor Speed During Trip / Motor Speed During Event
40MM300 MOTOR MANAGEMENT SYSTEM – COMMUNICATIONS GUIDE
COMMUNICATIONS GUIDERS485 INTERFACE (MODBUS RTU)
CodeTypeDefinition
0Low Speed
1High Speed
FC13616 bitsMotor Speed During Trip / Motor Speed During Event
0None
1A
2B
FC13916 bitsStarter Type
0None
1FV Nonreversing
2FV Reversing
3Two Speed
4Wye-Delta
5Inverter
6Soft Starter
7Custom Starter
FC14016 bitsInterlock Function
0Disabled
1Trip
2Alarm
3Stop
FC14116 bitsTimer Type
0Millisecond
1Second
2Minute
FC14216 bitsFlexLogic Bit Field EEETTTTTTTSSSSSS S-Bits denotes the
0x0000OFF
0x0001ON
0x0040Contact Inputs
0x0080Virtual Inputs
0x00C0Virtual Outputs
0x01C0Remote Inputs
0x0380Insert
0x0400End
0x0440NOT
0x0480XOR
0x04C0LATCH
0x0500OR
0x0540AND
0x0580NOR
0x05C0NAND
0x0600TIMER
0x0640ASSIGN
0x8000Trip
0xA000Alarm
element state or Operator specific data Number of inputs
T-Bits denote Flex logic Operands and Parameters or
when one of the E bits are set they denote specific details
for the Element Type E-Bits
MM300 MOTOR MANAGEMENT SYSTEM – COMMUNICATIONS GUIDE41
RS485 INTERFACE (MODBUS RTU)COMMUNICATIONS GUIDE
CodeTypeDefinition
0xC000Control
FC14316 bitsDrive Status
0Drive Unavailable
1Available Auto
2Available Manual
3Available
4Running
FC14432 bitsLED Status
Bit 0Running Red
Bit 1Running Green
Bit 2Stopped Red
Bit 3Stopped Green
Bit 4Tripped Red
Bit 5Tripped Green
Bit 6Alarm Red
Bit 7Alarm Green
Bit 8Auto Red
Bit 9Auto Green
Bit 10Manual Red
Bit 11Manual Green
Bit 12Comms OK Red
Bit 13Comms OK Green
Bit 14USER1 Red
Bit 15USER1 Green
Bit 16USER2 Red
Bit 17USER2 Green
Bit 18USER3 Red
Bit 19USER3 Green
Bit 2050% Red
Bit 2150% Green
Bit 2280% Red
Bit 2380% Green
Bit 24100% Red
Bit 25100% Green
FC14516 bitsElement Status 1
Bit 0Level
Bit 1Operated
Bit 2Latched
Bit 3Spare
FC14716 bitsLED Intensity
0Level 1
3Level 2
6Level 3
9Level 4
12Level 5
15Level 6
FC15032 bitsIP Address
42MM300 MOTOR MANAGEMENT SYSTEM – COMMUNICATIONS GUIDE
COMMUNICATIONS GUIDERS485 INTERFACE (MODBUS RTU)
CodeTypeDefinition
IP address, subnet mask or default gateway Each byte in this register represents one octet of an IP address
For example: 0x015EDA1F represents address 19421831
FC15516 bitsProfibus Baud Rate
0x00019600
0x000219200
0x000431250
0x000845450
0x001093750
0x0020187500
0x0040500000
0x00801500000
0x07E2Auto Detect
FC15616 bitsDeviceNet Baud Rate
0125 kbps
1250 kbps
2500 kbps
FC15716 bitsLED Colour
0None
1Red
2Green
3Orange
FC16016 bitsAuto/Manual Mode
0Auto
1Manual
FC16732 bitsContact/Virtual Input/Output Status
Bit 0Input/Output 1
Bit 1Input/Output 2
Bit 2Input/Output 3
Bit 3Input/Output 4
Bit 4Input/Output 5
Bit 5Input/Output 6
Bit 6Input/Output 7
Bit 7Input/Output 8
Bit 8Input/Output 9
Bit 9Input/Output 10
Bit 10Input/Output 11
Bit 11Input/Output 12
Bit 12Input/Output 13
Bit 13Input/Output 14
Bit 14Input/Output 15
Bit 15Input/Output 16
Bit 16Input/Output 17
Bit 17Input/Output 18
Bit 18Input/Output 19
Bit 19Input/Output 20
Bit 20Input/Output 21
Bit 21Input/Output 22
MM300 MOTOR MANAGEMENT SYSTEM – COMMUNICATIONS GUIDE43
RS485 INTERFACE (MODBUS RTU)COMMUNICATIONS GUIDE
CodeTypeDefinition
Bit 22Input/Output 23
Bit 23Input/Output 24
Bit 24Input/Output 25
Bit 25Input/Output 26
Bit 26Input/Output 27
Bit 27Input/Output 28
Bit 28Input/Output 29
Bit 29Input/Output 30
Bit 30Input/Output 31
Bit 31Input/Output 32
FC16832 bitsContact/Virtual Input/Output Status
Bit 0Input/Output 33
Bit 1Input/Output 34
Bit 2Input/Output 35
Bit 3Input/Output 36
Bit 4Input/Output 37
Bit 5Input/Output 38
Bit 6Input/Output 39
Bit 7Input/Output 40
Bit 8Input/Output 41
Bit 9Input/Output 42
Bit 10Input/Output 43
Bit 11Input/Output 44
Bit 12Input/Output 45
Bit 13Input/Output 46
Bit 14Input/Output 47
Bit 15Input/Output 48
Bit 16Input/Output 49
Bit 17Input/Output 50
Bit 18Input/Output 51
Bit 19Input/Output 52
Bit 20Input/Output 53
Bit 21Input/Output 54
Bit 22Input/Output 55
Bit 23Input/Output 56
Bit 24Input/Output 57
Bit 25Input/Output 58
Bit 26Input/Output 59
Bit 27Input/Output 60
Bit 28Input/Output 61
Bit 29Input/Output 62
Bit 30Input/Output 63
Bit 31Input/Output 64
FC16916 bitsMonth
0Not Set
1January
2February
44MM300 MOTOR MANAGEMENT SYSTEM – COMMUNICATIONS GUIDE
COMMUNICATIONS GUIDERS485 INTERFACE (MODBUS RTU)
CodeTypeDefinition
3March
4April
5May
6June
7July
8August
9September
10October
11November
12December
FC17016 bitsCount of Week
0Not Set
11st
22nd
33rd
44th
5Last
FC17116 bitsWeekdays
0Not Set
1SUN
2MON
3TUE
4WED
5THU
6FRI
7SAT
FC17216 bitsAuto/Manual Control Stop Mode
0Always Enabled
1Follow Ctrl Mode
FC17316 bitsWire Selection
02W
13W
FC17416 bitsSource Stop Action
0Stop
1Trip
FC17516 bitsTest Auto/Manual Mode
0ON
1OFF
2Unaffected
FC17616 bitsAuxiliary VT Connection
0Vab VT
1Vbc VT
2Vca VT
3Van VT
4Vbn VT
5Vcn VT
6Van Direct
MM300 MOTOR MANAGEMENT SYSTEM – COMMUNICATIONS GUIDE45
RS485 INTERFACE (MODBUS RTU)COMMUNICATIONS GUIDE
CodeTypeDefinition
7Vbn Direct
8Vcn Direct
FC17716 bitsLED Color Invert
0Green/Red
1Red/Green
FC17816 bitsMotor Status
Bit 0Lockout
Bit 1Non-Lockout Trip
Bit 2UVR Pending
Bit 4Running
Bit 5Precontactor
Bit 6Starting
Bit 8Inhibit
Bit 9Stopped
Bit 10Self Test Fault
Bit 11Alarm
Bit 12Forward
Bit 13Reverse
Bit 14Low Speed
Bit 15High Speed
FC17932 bitsAlarm Status 1
Bit 0Any Alarm
Bit 1Thermal Level Alarm
Bit 2Ground Fault Alarm
Bit 3Acceleration Alarm
Bit 4Phase Reversal Alarm
Bit 5UnderPower Alarm
Bit 6UnderVoltage Alarm
Bit 7OverVoltage Alarm
Bit 9UnderCurrent Alarm
Bit 10Unbalance Alarm
Bit 11RTD 1 Alarm
Bit 12RTD 2 Alarm
Bit 13RTD 3 Alarm
Bit 14RTD 4 Alarm
Bit 15RTD 5 Alarm
Bit 16RTD 6 Alarm
Bit 17RTD Open/Short Alarm
Bit 18RTD Open/Short Alarm
Bit 19Process ILock A Alarm
Bit 20Process ILock B Alarm
Bit 21Process ILock C Alarm
Bit 22Process ILock D Alarm
Bit 23Process ILock E Alarm
Bit 24Process ILock F Alarm
Bit 25Process ILock G Alarm
Bit 26Process ILock H Alarm
46MM300 MOTOR MANAGEMENT SYSTEM – COMMUNICATIONS GUIDE
COMMUNICATIONS GUIDERS485 INTERFACE (MODBUS RTU)
CodeTypeDefinition
Bit 27Process ILock I Alarm
Bit 28Process ILock J Alarm
Bit 29Drive Failed to Start
Bit 30Inverter Failed
Bit 31Drive Stop Failed
FC18032 bitsAlarm Status 2
Bit 0Aux U/V Alarm
Bit 1External Stop Alarm
Bit 2Fuse Fail Alarm
Bit 3Open Ctrl Cct Alarm
Bit 4Thermistor Alarm
Bit 6External Start A Alarm
Bit 7External Start B Alarm
Bit 8Welded Contactor
Bit 12Load Increase Alarm
Bit 13Drive Greasing Alarm
Bit 14Contactor Inspect Alarm
Bit 15Max Stopped Alarm
Bit 18Comm Fail Alarm
FC18132 bitsAlarm Status 3 (Reserved)
FC18232 bitsAlarm Status 4 (Reserved)
FC18332 bitsTrip Status 1
Bit 0Any Trip
Bit 1Thermal O/L Trip
Bit 2Ground Fault Trip
Bit 3Acceleration Trip
Bit 4Phase Reversal Trip
Bit 5UnderPower Trip
Bit 6UnderVoltage Trip
Bit 7OverVoltage Trip
Bit 8Mechanical Jam Trip
Bit 9UnderCurrent Trip
Bit 10Unbalance Trip
Bit 11RTD 1 Trip
Bit 12RTD 2 Trip
Bit 13RTD 3 Trip
Bit 14RTD 4 Trip
Bit 15RTD 5 Trip
Bit 16RTD 6 Trip
Bit 17Comm Fail Trip
Bit 18Relay Not Configured
Bit 19Process ILock A Trip
Bit 20Process ILock B Trip
Bit 21Process ILock C Trip
Bit 22Process ILock D Trip
Bit 23Process ILock E Trip
Bit 24Process ILock F Trip
MM300 MOTOR MANAGEMENT SYSTEM – COMMUNICATIONS GUIDE47
RS485 INTERFACE (MODBUS RTU)COMMUNICATIONS GUIDE
CodeTypeDefinition
Bit 25Process ILock G Trip
Bit 26Process ILock H Trip
Bit 27Process ILock I Trip
Bit 28Process ILock J Trip
Bit 29Hard Wired Trip
Bit 30Field Trip
Bit 31MCC Trip
FC18432 bitsTrip Status 2
Bit 0Aux U/V Trip
Bit 1Emergency Stop
Bit 2Fuse Fail Trip
Bit 3OpenControl Circuit
Bit 4Thermistor Trip
FC18532 bitsTrip Status 3 (Reserved)
FC18632 bitsTrip Status 4 (Reserved)
FC18732 bitsMessage Status 1
Bit 1Transfer Timer
Bit 2FLA Not Set
Bit 3CT Type Not Set
Bit 4Starter Type Not Set
Bit 5No Control Source
Bit 6Clock Not Set
Bit 7FLA Too High
FC18832 bitsMessage Status 2
Bit 1IO Communication Failure
Bit 2Metering Failure
Bit 3Order Code Error
Bit 4Clock Error
Bit 5Calibration Error
Bit 6EEPROM Error
Bit 7IO Input Read Error
Bit 8IO 3.3V Error
Bit 9IO 5V Error
Bit 10IO -5V Error
Bit 11IO Input Overvoltage
Bit 12IO Frequency Error
Bit 13DPRAM Error
Bit 14System Health Error
FC18932 bitsMessage Status 3 (Reserved)
FC19032 bitsMessage Status 4 (Reserved)
FC19132 bitsCtrl Element Status 1
Bit 0Any Stop
Bit 1Thermal Inhibit
Bit 2AutoMode
Bit 3Manual Mode
Bit 4AutoManualMode
Bit 5Restart Inhibit
48MM300 MOTOR MANAGEMENT SYSTEM – COMMUNICATIONS GUIDE
COMMUNICATIONS GUIDERS485 INTERFACE (MODBUS RTU)
CodeTypeDefinition
Bit 8Forward Limit
Bit 9Reverse Limit
Bit 10Starts/Hr Inhibit
Bit 11Time Between Inhibit
Bit 15Comms Ctrl Active
Bit 16Hard Wired Ctrl Active
Bit 17Field Ctrl Active
Bit 18MCC Ctrl Active
Bit 19Process ILock A Stop
Bit 20Process ILock B Stop
Bit 21Process ILock C Stop
Bit 22Process ILock D Stop
Bit 23Process ILock E Stop
Bit 24Process ILock F Stop
Bit 25Process ILock G Stop
Bit 26Process ILock H Stop
Bit 27Process ILock I Stop
Bit 28Process ILock J Stop
FC19232 bitsCtrl Element Status 2
Bit 0Access Switch
Bit 1Test Switch
Bit 10Remote Reset
Bit 11Lockout Reset
Bit 13Pre-Contactor
Bit 20Fuse Fail Inhibit
Bit 21Phase Reversal Inhibit
Bit 22Low Aux Voltage Inhibit
FC19332 bitsCtrl Status 3 (Reserved)
FC19432 bitsCtrl Status 4 (Reserved)
FC21216 bitsLCD Test Paint Color
0None
1Red
2Green
3Blue
Performing Commands Using Function Code 10H
Commands can be performed using function code 16 as well as function code 5. When
using FUNCTION CODE 16, the Command Function register must be written with a value of
5. The Command Operation register must be written with a valid command operation
number. The Command Data registers must be written with valid data; this is dependent
upon the command operation.
For example, consider a request for slave 17 to perform command operation 1 (RESET): The
master/slave packets have the following format:
MM300 MOTOR MANAGEMENT SYSTEM – COMMUNICATIONS GUIDE49
RS485 INTERFACE (MODBUS RTU)COMMUNICATIONS GUIDE
Table 9: Master/slave packet format for performing commands
MASTER TRANSMISSIONBYTESEXAMPLEDESCRIPTION
SLAVE ADDRESS111message for slave
FUNCTION CODE110store multiple
DATA STARTING ADDRESS200 80setpoint address
NUMBER OF SETPOINTS200 022 setpoints = 4
BYTE COUNT1044 bytes of data
DATA 1200 05data for address
DATA 2200 01data for address
CRC27E CECRC error code
SLAVE RESPONSEBYTESEXAMPLEDESCRIPTION
SLAVE ADDRESS111message from
FUNCTION CODE110store multiple
DATA STARTING ADDRESS200 80setpoint address
NUMBER OF SETPOINTS200 022 setpoints
CRC242 B0CRC error code
17
setpoints
00 80
bytes total
00 80
00 81
slave 17
setpoints
00 80
Using the User Definable Memory Map
The MM300 contains a User Definable area in the memory map. This area allows remapping of the addresses of any Actual Values or Setpoints registers. The User Definable
area has two sections:
1.A Register Index area (memory map addresses 020BH-0287H) that contains 125
Actual Values or Setpoints register addresses.
2.A Register area (memory map addresses 020BH-0287H) that contains the data at the
addresses in the Register Index.
Register data that is separated in the rest of the memory map may be re-mapped to
adjacent register addresses in the User Definable Registers area. This is accomplished by
writing to register addresses in the User Definable Register Index area. This allows for
improved throughput of data and can eliminate the need for multiple read command
sequences. The User Definable Register Index is stored as a setpoint and therefore it is
“remembered” even when the power is removed.
For example, if the values of MOTOR LOAD (register address 014FH; modbus address
30336) and DRIVE STATUS (register address 0135H; modbus address 30310) are required to
be read from a MM300, their addresses may be re-mapped as follows:
1.Write 30336 to address 020BH (40524) (User Definable Register Index 0000) using
function code 06 or 16.
2.Write 30310 to address 020CH (40525) (User Definable Register Index 0001) using
function code 06 or 16.
The MM300PC software can be used to write these locations to the User Definable Register
Index using the Setpoints > Modbus Memory Map > User Map screen.
50MM300 MOTOR MANAGEMENT SYSTEM – COMMUNICATIONS GUIDE
COMMUNICATIONS GUIDERS485 INTERFACE (MODBUS RTU)
It is now possible to read these two data registers with one read, at addresses 020BH,
020CH. Address 020BH will contain MOTOR LOAD. Address 020CH will contain DRIVE
STATUS.
MM300 MOTOR MANAGEMENT SYSTEM – COMMUNICATIONS GUIDE51
ETHERNET INTERFACECOMMUNICATIONS GUIDE
Ethernet interface
The 10/100Base-T Ethernet interface is configured as a Modbus RTU slave. The Ethernet
port has the following characteristics.
•Configuration: setup using IP address, subnet mask, and gateway address.
•Supported Modbus function codes: 3, 4, 5, 6, and 16.
•Supports time/date synchronization via the Network Time Protocol (NTP).
•Ethernet port 502.
•Supports a maximum of 5 virtual connections.
The Ethernet interface has the same memory map layout as the serial Modbus RTU
interface.
Network Time Protocol is enabled if the NTP address is non-zero and the source is
detected.
Once connected to the source, the clock is updated every 30 seconds.
52MM300 MOTOR MANAGEMENT SYSTEM – COMMUNICATIONS GUIDE
COMMUNICATIONS GUIDEFIELDBUS INTERFACE
Fieldbus interface
The fieldbus interface is configurable as either Profibus DPV0 or DeviceNet. Both Fieldbus
interfaces support control and status – refer to the specific data map below for details.
Note that external power, 5 to 24 VDC, is required for this interface to operate. (Ensure that
switches 7 and 8 of the DIPswitch on the communication card, are ON.)
Profibus protocol (DP V0)
To enable the Profibus physical interface, ensure that switches 3 and 4 of the DIP switch on
the communications card (on the CPU module) are on. The external connections through
the Fieldbus interface are as follows.
Output bit must be 1 for a minimum time of 100 ms, to be actioned.
BitDescription
1Reset
2Lockout Reset
3Stop
4Start A
5Start B
Commands are actioned on rising edge (0 to 1 transition).
MM300 MOTOR MANAGEMENT SYSTEM – COMMUNICATIONS GUIDE53
FIELDBUS INTERFACECOMMUNICATIONS GUIDE
Profibus DP-Diagnostics
MM300 supports both slave mandatory and slave specific diagnostic data.
Table 12: System Standard Diagnostics Bytes 1 through 6
ByteDescription
1Station Status 1
2Station Status 2
3Station Status 3
4Diagnostic Master Address
5Identification Number (High Byte)
6Identification Number (Low Byte)
The extended diagnosis for the relay is composed of 49 bytes (bytes 7 to 55) and contains
diagnostic information according to the following table, with bit descriptions listed in the
following pages.
Address (By Bytes)DescriptionFormat
7No. of Extended Diagnostic BytesUnsigned
8-11Trip Status 3FC185
12-15Trip Status 2FC184
16-19Trip Status 1FC183
20-23Alarm Status 3FC181
24-27Alarm Status 2FC180
28-31Alarm Status 1FC179
32-35Message Status 3FC189
36-39Message Status 2FC188
40-43Message Status 1FC187
44-47Ctrl Element Status 3FC193
48-51Ctrl Element Status 2FC192
52-55Ctrl Element Status 1FC191
Profibus Input Data
CategoryAddress (By Bytes)DescriptionFormat
Status-Motor0Motor StatusFC129
2Extended StatusFC178
4Thermal Cap UsedF1
6Time to Overload TripF20
10ReservedNA
Start Blocks12Starts/Hour BlockF1
14Time Between Starts LockoutF1B
16Restart Block LockoutF1
18ReservedNA
20ReservedNA
22ReservedNA
24ReservedNA
Learned26Average Motor Load LearnedF3
28Learned Acceleration TimeF2
30Learned Starting CurrentF10
54MM300 MOTOR MANAGEMENT SYSTEM – COMMUNICATIONS GUIDE
COMMUNICATIONS GUIDEFIELDBUS INTERFACE
CategoryAddress (By Bytes)DescriptionFormat
34Learned Starting CapacityF1
Counters36Number of Motor StartsF1
38Number of UV RestartsF1
40Motor Running HoursF9
44Motor Stopped HoursF1
46ReservedNA
48ReservedNA
50ReservedNA
52ReservedNA
54ReservedNA
56ReservedNA
58ReservedNA
Current Metering60IaF10
64IbF10
68IcF10
72ReservedNA
74ReservedNA
76ReservedNA
78IavgF10
82IgrdF10
86Motor LoadF1
88I UnbF1
Voltage Metering90VabF1
92VbcF1
94VcaF1
96Va1 AngleF1
98Vb1 AngleF1
100Vc1 AngleF1
102VanF1
104VbnF1
106VcnF1
108VAuxF1
110ReservedNA
112ReservedNA
114ReservedNA
116FrequencyF3
118ReservedNA
Power Metering120Power FactorF21
122Real PowerF13
126ReservedNA
128Reactive PowerF13
132Apparent PowerF2
134MWh ConsumptionF17
138ReservedNA
140ReservedNA
142Mvarh ConsumptionF17
146ReservedNA
MM300 MOTOR MANAGEMENT SYSTEM – COMMUNICATIONS GUIDE55
FIELDBUS INTERFACECOMMUNICATIONS GUIDE
CategoryAddress (By Bytes)DescriptionFormat
148ReservedNA
150ReservedNA
Sensor Metering152Hottest Stator RTDF1
154Hottest Stator RTD TempF4
156RTD 1 TempF4
158RTD 2 TempF4
160RTD 3 TempF4
162RTD 4 TempF4
164RTD 5 TempF4
166RTD 6 TempF4
168ReservedNA
170ReservedNA
172ReservedNA
174ReservedNA
176ReservedNA
178ReservedNA
Last Trip Data180Cause of Last TripFC134
182Date of Last Trip 2 wordsF18
186Time of Last Trip 2 wordsF19
190Pre Trip IaF10
194Pre Trip IbF10
198Pre Trip IcF10
202Pre Trip Motor LoadF3
204Pre Trip Current UnbalanceF1
206Pre Trip IgrdF10
210ReservedNA
212ReservedNA
214Pre Trip VabF1
216Pre Trip VbcF1
218Pre Trip VcaF1
220Pre Trip VanF1
222Pre Trip VbnF1
224Pre Trip VcnF1
226Pre Trip System FrequencyF3
228Pre Trip Real PowerF13
232Pre Trip Reactive PowerF13
236Pre Trip Apparent PowerF2
238Pre Trip Power FactorF21
56MM300 MOTOR MANAGEMENT SYSTEM – COMMUNICATIONS GUIDE
COMMUNICATIONS GUIDEFIELDBUS INTERFACE
DeviceNet protocol
To enable the DeviceNet physical interface, ensure that switches 1 and 2 of the DIP switch
communications card (on the CPU module) are on. The external connections through the
fieldbus interface are as follows.
The Modbus status (MS) and network status (NS) LEDs indicate the status of the Fieldbus
interface.
Table 14: DeviceNet LED indications
LEDLED operationDescription
MSGreen on, red on, green onDevice self-test
Flashing greenDevice in standby state
Green onDevice operational
Flashing redRecoverable fault
Red onUnrecoverable fault
NSFlashing greenOnline, not connected
Green onOnline, connected
Flashing redConnection timeout
Red onCritical link failure
Red and greenNetwork access detected
DeviceNet Communications
When used for DeviceNet, the fieldbus port has the following characteristics.
•Baud rate: 125, 250, and 500 kbps
•MAC ID: 0 to 63
•Vendor ID: 928
•Product Code: 0x4D39
•Message types: poll, and explicit messaging
The device profile is an extension of the Communications Adapter Device Profile (0xC0). It is
a group 2 only server. The MAC ID and baud rate are programmable through the EnerVista
MM300 Setup software and the Graphical Control Panel. The MM300 supports the
following DeviceNet object classes.
CLASSOBJECT
01HIdentify
02HMessage Router
03HDeviceNet
05HConnection
A0HGeneric Data - Polling/Explicit
B1HExplicit Control Writes
B0HAnalog Data - Explicit
MM300 MOTOR MANAGEMENT SYSTEM – COMMUNICATIONS GUIDE57
FIELDBUS INTERFACECOMMUNICATIONS GUIDE
The MM300 supports poll and explicit messaging types.
The Poll function will return 38 bytes of status and metering data as described in User
Object Class A0h, Instance 01h, Attribute 01h.
USINT, UINT, UDINT and DINT, stated in this document, stand for the following data types :
USINT = Unsigned integer byte
UINT = Unsigned integer word
UDINT = Unsigned integer double word
DINT = Signed integer double word
Identity Object (Class Code 01H)
Table 15: Identity Object, Class Code 01h, Services:
CODESERVICES AVAILABLE TO THIS OBJECT
NAMEDESCRIPTION
0x05ResetReset the device to power up conf iguration
0x0EGet_Attribute_Single Returns the contents of the given attribute
Table 16: Identity Object, Class Code 01h, Attributes:
ATTRIBUTEACCESSNAME/DESCRIPTIONDATA TYPEVALUE
01hGetRevision of Identity ObjectUINT1
Table 17: Identity Object, Class Code 01h, Instance 01h, Attributes:
ATTRIBUTEACCESSNAME/DESCRIPTIONDATA TYPEVALUE
01hGetVendor IDUINT928
02hGetDevice TypeUINT12
03hGetProduct CodeUINT0x4D39
04hGetRevision (Major, Minor)USINT1.00
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.
DeviceNet Object (Class Code 03H)
Table 18: Identity Object, Class Code 03h, Services:
CODESERVICES AVAILABLE TO THIS OBJECT
0x0EGet_Attribute_Single Returns the contents of the given attribute
Table 19: Identity Object, Class Code 03h, Attributes:
ATTRIBUTEACCESSNAME/DESCRIPTIONDATA TYPEVALUE
01hGetRevision of DeviceNet Object UINT1
NAMEDESCRIPTION
58MM300 MOTOR MANAGEMENT SYSTEM – COMMUNICATIONS GUIDE
COMMUNICATIONS GUIDEFIELDBUS INTERFACE
Table 20: Identity Object, Class Code 03h, Instance 01h, Attributes: