GE Multilin MM200 Motor Management System Communications Guide for revision 1.0x.
MM200 Motor Management System, EnerVista, EnerVista Launchpad, EnerVista MM200
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.
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 ........................................................................................................................................7
Function Code 08H ........................................................................................................................................8
Function Code 10H ........................................................................................................................................9
Performing Commands Using Function Code 10H .......................................................................10
Using the User Definable Memory Map .............................................................................................10
Format codes ................................................................................................................................................. 20
Profibus Output Data .................................................................................................................................... 8
Profibus Input Data ......................................................................................................................................29
The MM200 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 MM200 Modbus
implementation employs two-wire RS485 hardware. Using RS485, up to 32 MM200s can be
daisy-chained together on a single communication channel.
The MM200 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 InterfaceThe hardware or electrical interface in the MM200 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 MM200s 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:
Data Frame Format
and Data Rate
Polarity is important in RS485 communications. The '+' (positive) terminals of every device
must be connected together.
E
One data frame of an asynchronous transmission to or from a MM200 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 MM200
supports operation at 9600, 19200, 38400, 57600, and 115200 baud.
Data Packet FormatA complete request/response sequence consists of the following bytes (transmitted as
separate data frames):
Master Request Transmission:
SLAVE ADDRESS: 1 byte
FUNCTION CODE: 1 byte
DATA: variable number of bytes depending on FUNCTION CODE
2MM200 MOTOR MANAGEMENT SYSTEM – COMMUNICATIONS GUIDE
COMMUNICATIONS GUIDERS485 INTERFACE (MODBUS RTU)
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 CheckingThe 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 MM200 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 MM200 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.
CRC-16 AlgorithmOnce 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
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)
MM200 MOTOR MANAGEMENT SYSTEM – COMMUNICATIONS GUIDE3
RS485 INTERFACE (MODBUS RTU)COMMUNICATIONS GUIDE
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
TimingData 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.
MM200 supported
functions
The following functions are supported by the MM200:
•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 03HModbus implementation: Read Holding Registers
MM200 implementation: Read Setpoints
For the MM200 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 MM200 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:
4MM200 MOTOR MANAGEMENT SYSTEM – COMMUNICATIONS GUIDE
COMMUNICATIONS GUIDERS485 INTERFACE (MODBUS RTU)
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
SLAVE RESPONSEBYTESEXAMPLEDESCRIPTION
SLAVE ADDRESS111message from
FUNCTION CODE103read registers
BYTE COUNT1063 registers = 6
DATA 1 (see definition above) 202 2Bvalue in address
DATA 2 (see definition above) 200 00value in address
DATA 3 (see definition above) 200 64value in address
CRC254 83CRC error code
17
006B
bytes total
slave 17
bytes
006B
006C
006D
Function Code 04HModbus Implementation: Read Input Registers
MM200 implementation: Read Actual Values
For the MM200 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 MM200 Actual Values 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
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.
MM200 MOTOR MANAGEMENT SYSTEM – COMMUNICATIONS GUIDE5
RS485 INTERFACE (MODBUS RTU)COMMUNICATIONS GUIDE
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 05HModbus Implementation: Force Single Coil
MM200 Implementation: Execute Operation
This function code allows the master to request a MM200 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
FUNCTION CODE105execute operation
OPERATION CODE200 01operation code 1
CODE VALUE2FF 00perform function
CRC2DF 6ACRC error code
SLAVE RESPONSEBYTESEXAMPLEDESCRIPTION
SLAVE ADDRESS111message from
FUNCTION CODE105execute operation
OPERATION CODE200 01operation code 1
CODE VALUE2FF 00perform function
CRC2DF 6ACRC error code
17
slave 17
The commands that can be performed by the MM200 using function code 05 can also be
initiated by using function code 16.
6MM200 MOTOR MANAGEMENT SYSTEM – COMMUNICATIONS GUIDE
COMMUNICATIONS GUIDERS485 INTERFACE (MODBUS RTU)
Operation CodeDescription
1Reset
2Lockout Reset
3Stop
4Start A
5Start B
96Clear Last Trip Data Prompt
99Clear Counters
113Reset Motor Information
114Auto Mode
115Manual Mode
116Manual Inhibit
117Manual Restore
Function Code 06HModbus Implementation: Preset Single Register
MM200 Implementation: Store Single Setpoint
This command allows the master to store a single setpoint into the memory of a MM200
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
FUNCTION CODE106store single
DATA STARTING ADDRESS204 5Csetpoint address
DATA200 02data for setpoint
CRC2CB B9CRC error code
SLAVE RESPONSEBYTESEXAMPLEDESCRIPTION
SLAVE ADDRESS111message from
FUNCTION CODE106store single
DATA STARTING ADDRESS204 5Csetpoint address
DATA200 02data stored in
CRC2CB B9CRC error code
Function Code 07HModbus Implementation: Read Exception Status
MM200 Implementation: Read Device Status
17
setpoint
04 5C
address 04 5C
slave 17
setpoint
04 5C
setpoint address
04 5C
MM200 MOTOR MANAGEMENT SYSTEM – COMMUNICATIONS GUIDE7
RS485 INTERFACE (MODBUS RTU)COMMUNICATIONS GUIDE
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 MM200 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
17
SLAVE RESPONSEBYTESEXAMPLEDESCRIPTION
SLAVE ADDRESS111message from
FUNCTION CODE107read device status
DEVICE STATUS (see
definition above)
CRC222 28CRC error code
12Cstatus = 00101100
Function Code 08HModbus Implementation: Loopback
Test MM200 Implementation: Loopback Test
This function is used to test the integrity of the communication link. The MM200 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 17
(in binary)
17
8MM200 MOTOR MANAGEMENT SYSTEM – COMMUNICATIONS GUIDE
COMMUNICATIONS GUIDERS485 INTERFACE (MODBUS RTU)
SLAVE RESPONSEBYTESEXAMPLEDESCRIPTION
SLAVE ADDRESS111message from
FUNCTION CODE108loopback test
DIAG CODE200 00must be 00 00
DATA200 00must be 00 00
CRC2E0 0BCRC error code
slave 17
Function Code 10HModbus Implementation: Preset Multiple Registers
MM200 Implementation: Store Multiple Setpoints
This function code allows multiple Setpoints to be stored into the MM200 memory. Modbus
“registers” are 16-bit (two byte) values transmitted high order byte first. Thus all MM200
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 MM200 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, MM200 slave 17 will have the following setpoints information stored:
AddressData
04 5C00 02
04 5D01 F4
The master/slave packets have the following format:
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
MM200 MOTOR MANAGEMENT SYSTEM – COMMUNICATIONS GUIDE9
RS485 INTERFACE (MODBUS RTU)COMMUNICATIONS GUIDE
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:
Table 9: MASTER/SLAVE PACKET FORMAT FOR PERFORMING COMMANDS
MASTER TRANSMISSIONBYTESEXAMPLEDESCRIPTION
SLAVE ADDRESS111message for slave
17
FUNCTION CODE110store multiple
setpoints
DATA STARTING ADDRESS200 80setpoint address
00 80
NUMBER OF SETPOINTS200 022 setpoints = 4
bytes total
BYTE COUNT1044 bytes of data
DATA 1200 05data for address
00 80
DATA 2200 01data for address
00 81
CRC27E CECRC error code
Using the User
Definable Memory
Map
SLAVE RESPONSEBYTESEXAMPLEDESCRIPTION
SLAVE ADDRESS111message from
slave 17
FUNCTION CODE110store multiple
setpoints
DATA STARTING ADDRESS200 80setpoint address
00 80
NUMBER OF SETPOINTS200 022 setpoints
CRC242 B0CRC error code
The MM200 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 MM200, 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.
10MM200 MOTOR MANAGEMENT SYSTEM – COMMUNICATIONS GUIDE
COMMUNICATIONS GUIDERS485 INTERFACE (MODBUS RTU)
2.Write 30310 to address 020CH (40525) (User Definable Register Index 0001) using
function code 06 or 16.
The MM200PC software can be used to write these locations to the User Definable Register
Index using the Setpoints > Modbus Memory Map > User Map screen.
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.
Error ResponsesWhen a MM200 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 MM200.
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 MM200 implements the following exception response codes:
01 - ILLEGAL FUNCTION
The function code transmitted is not one of the functions supported by the MM200.
02 - ILLEGAL DATA ADDRESS
The address referenced in the data field transmitted by the master is not an allowable
address for the MM200.
03 - ILLEGAL DATA VALUE
The value referenced in the data field transmitted by the master is not within range for the
selected data address.
Modbus memory map
ModbusHexDescriptionMinMaxStepUnitsFormat DefaultSize in
ACTUAL VALUES
PRODUCT INFORMATION
300010000Product Device Code------------F22N/A1
300020001Hardware Revision------------F15N/A1
300030002Firmware Version------------F3N/A1
300040003Reserved------------------1
300050004Modification Number------------F1N/A1
300060005Boot Version------------F3N/A1
300070006Reserved------------------1
300080007Serial Number------------F22N/A6
30014000DOrder Code------------F22N/A16
300360023Reserved------------------1
MM200 MOTOR MANAGEMENT SYSTEM – COMMUNICATIONS GUIDE11
Words
RS485 INTERFACE (MODBUS RTU)COMMUNICATIONS GUIDE
ModbusHexDescriptionMinMaxStepUnitsFormat DefaultSize in
409140391Max Motor Stopped T ime101001010hrsF1*100101
409150392Reserved------------------1
▼▼▼▼▼ ▼▼▼▼ ▼
41039040EReserved1
CALIBRATION
41040040FCalibration Date02033603021---F1802
410420411Calibration T ime03897577951---F1902
410440413Reserved------------------1
▼▼▼▼▼ ▼▼▼▼ ▼
411050450Reserved1
1601s F111
Words
18MM200 MOTOR MANAGEMENT SYSTEM – COMMUNICATIONS GUIDE
COMMUNICATIONS GUIDERS485 INTERFACE (MODBUS RTU)
ModbusHexDescriptionMinMaxStepUnitsFormat DefaultSize in
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
▼▼▼▼▼ ▼▼▼▼ ▼
41372055BReserved------------------1
CONTACT INPUT ASSIGNMENT
41373055CReserved------------------1
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
413940571Reserved------------------1
▼▼▼▼▼ ▼▼▼▼ ▼
4147505C2Reserved------------------1
LEDs
4147605C3Reserved------------------1
▼▼▼▼▼ ▼▼▼▼ ▼
4149505D6USER1 LED Assignment0573441---FC14201
4149605D7USER1 LED Color031---FC15711
4149705D8USER2 LED Assignment0573441---FC14201
4149805D9USER2 LED Color031---FC15711
4149905DAReserved------------------1
▼▼▼▼▼ ▼▼▼▼ ▼
4151405E9Reserved------------------1
Words
MM200 MOTOR MANAGEMENT SYSTEM – COMMUNICATIONS GUIDE19
RS485 INTERFACE (MODBUS RTU)COMMUNICATIONS GUIDE
ModbusHexDescriptionMinMaxStepUnitsFormat DefaultSize in
CONTACT OUTPUTS
4151505EAContact Output 10573440---FC14201
4151605EBContact Output 20573440---FC14201
4151705ECContact Output 30573440---FC14201
4151805EDReserved------------------1
▼▼▼▼▼ ▼▼▼▼ ▼
415710622Reserved------------------1
AUTO / MANUAL CONTROL
415720623Comms Start Ctrl011---FC12601
415730624Comms Stop Mode011---FC17201
415740625Hard Wired Start Ctrl011---FC12601
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
Words
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
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
20MM200 MOTOR MANAGEMENT SYSTEM – COMMUNICATIONS GUIDE
COMMUNICATIONS GUIDERS485 INTERFACE (MODBUS RTU)
CodeTypeDefinition
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
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
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”
F2216 bitsTWO 8-BIT CHARACTERS PACKED INTO 16-BIT UNSIGNED
MSBFirst Character
LSBSecond Character
Example: String ‘AB’ stored as 4142 hex
MM200 MOTOR MANAGEMENT SYSTEM – COMMUNICATIONS GUIDE21
RS485 INTERFACE (MODBUS RTU)COMMUNICATIONS GUIDE
CodeTypeDefinition
FC10116 bitsRS 485 Baud Rate
09600 baud
119200 baud
238400 baud
357600 baud
4115200 baud
FC10516 bitsCT Type
0None
11 A Secondary
25 A Secondary
3Direct Connect
FC10716 bitsSupply Frequency
060
150
FC11216 bitsCommunication Status
0Error
1OK
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
FC13116 bitsComm Fail Mode
1Serial
2Reserved
4Serial & FieldBus
8Reserved
16FieldBus
32Reserved
64All
FC13416 bitsCause of Event
0No Event/Trip To Date
1Control Power Lost
22MM200 MOTOR MANAGEMENT SYSTEM – COMMUNICATIONS GUIDE
COMMUNICATIONS GUIDERS485 INTERFACE (MODBUS RTU)
CodeTypeDefinition
2Control Power Applied
3Date or Time Set
4Reset
5Lockout Reset
0x8002Any Trip
0x8042Thermal O/L Trip
0x8082Ground Fault Trip
0x80C2Acceleration Trip
0x8202Mechanical Jam Trip
0x8242UnderCurrent Trip
0x8282Unbalance Trip
0x8442Comm Fail Trip
0x8742Hard Wired Trip
0x8782Field Trip
0x87C2MCC Trip
0x8842Emergency Stop
0x8902Thermistor Trip
0xA002Any Alarm
0xA042Thermal Level Alarm
0xA082Ground Fault Alarm
0xA0C2Acceleration Alarm
0xA242UnderCurrent Alarm
0xA282Unbalance Alarm
0xA842External Stop Alarm
0xA8C2Open Ctrl Cct Alarm
0xA902Thermistor Alarm
0xAB02Load Increase Alarm
0XAB42Drive Greasing Alarm
0xAB82Contactor Inspect Alarm
0xABC2Max Stopped Alarm
0xAC82Comm Fail Alarm
0xC002Any Stop
0xC082AutoMode
0xC0C2Manual Mode
0xC102Auto/Manual Mode Input
0xC182Contactor A
0xC1C2Contactor B
0xC202Forward Limit
0xC302Level 1 Access
0xC342Level 2 Access
0xC382Level 3 Access
0xC3C2Comms Ctrl Active
0xC402Hard Wired Ctrl Active
0xC442Field Ctrl Active
0xC482MCC Ctrl Active
0xC742HW Stop
0xC782Field Stop
MM200 MOTOR MANAGEMENT SYSTEM – COMMUNICATIONS GUIDE23
RS485 INTERFACE (MODBUS RTU)COMMUNICATIONS GUIDE
CodeTypeDefinition
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
0xCB42Pre-Contactor
0xCB82MCC Start A
0xCBC2MCC Start B
FC13916 bitsStarter Type
0None
1FV Nonreversing
2FV Reversing
3Two Speed
FC14216 bitsContact Input/Contact Output Element Assignment
0x0000OFF
0x0001ON
0x0040Contact Inputs
0x8000Trip
0xA000Alarm
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
24MM200 MOTOR MANAGEMENT SYSTEM – COMMUNICATIONS GUIDE
COMMUNICATIONS GUIDERS485 INTERFACE (MODBUS RTU)
CodeTypeDefinition
Bit 12Comms OK Red
Bit 13Comms OK Green
Bit 14USER1 Red
Bit 15USER1 Green
Bit 16USER2 Red
Bit 17USER2 Green
Bit 2050% Red
Bit 2150% Green
Bit 2280% Red
Bit 2380% Green
Bit 24100% Red
Bit 25100% Green
FC15516 bitsProfibus Baud Rate
0x00019600
0x000219200
0x000431250
0x000845450
0x001093750
0x0020187500
0x0040500000
0x00801500000
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 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
FC17216 bitsAuto/Manual Control Stop Mode
0Always Enabled
1Follow Ctrl Mode
FC17316 bitsWire Selection
02W
13W
MM200 MOTOR MANAGEMENT SYSTEM – COMMUNICATIONS GUIDE25
RS485 INTERFACE (MODBUS RTU)COMMUNICATIONS GUIDE
CodeTypeDefinition
FC17416 bitsSource Stop Action
0Stop
1Trip
FC17516 bitsTest Auto/Manual Mode
0ON
1OFF
2Unaffected
FC17816 bitsMotor Status
Bit 0Lockout
Bit 1Non-Lockout Trip
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 9UnderCurrent Alarm
Bit 10Unbalance Alarm
FC18032 bitsAlarm Status 2
Bit 0Aux U/V Alarm
Bit 1External Stop 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
FC18332 bitsTrip Status 1
Bit 0Any Trip
Bit 1Thermal O/L Trip
Bit 2Ground Fault Trip
Bit 3Acceleration Trip
Bit 8Mechanical Jam Trip
26MM200 MOTOR MANAGEMENT SYSTEM – COMMUNICATIONS GUIDE
COMMUNICATIONS GUIDERS485 INTERFACE (MODBUS RTU)
CodeTypeDefinition
Bit 9UnderCurrent Trip
Bit 10Unbalance Trip
Bit 29Hard Wired Trip
Bit 30Field Trip
Bit 31MCC Trip
FC18432 bitsTrip Status 2
Bit 1Emergency Stop
Bit 3OpenControl Circuit
Bit 4Thermistor Trip
FC19132 bitsCtrl Element Status 1
Bit 0Any Stop
Bit 1Thermal Inhibit
Bit 2AutoMode
Bit 3Manual Mode
Bit 4AutoManualMode
Bit 8Forward Limit
Bit 9Reverse Limit
Bit 15Comms Ctrl Active
Bit 16Hard Wired Ctrl Active
Bit 17Field Ctrl Active
Bit 18MCC Ctrl Active
MM200 MOTOR MANAGEMENT SYSTEM – COMMUNICATIONS GUIDE27
FIELDBUS INTERFACECOMMUNICATIONS GUIDE
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) are on. The external connections through the
Fieldbus interface are as follows.
Commands are actioned on rising edge (0 to 1 transition).
Profibus DP-
MM200 supports bot slave mandatory and slave specific diagnostic data.
Diagnostics
28MM200 MOTOR MANAGEMENT SYSTEM – COMMUNICATIONS GUIDE
COMMUNICATIONS GUIDEFIELDBUS INTERFACE
Table 12: System Standard Diagnostics Bytes 1 through 6
ByteDescription
0Station Status 1
1Station Status 2
2Station Status 3
3Diagnostic Master Address
4Identification Number (High Byte)
5Identification 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
6No. of Extended Diagnostic BytesUnsigned
7-10Reserved
11-14Trip Status 2FC184
15-18Trip Status 1FC183
19-22 Reserved
23-26Alarm Status 2FC180
27-30Alarm Status 1FC179
31-46Reserved
47-50Ctrl Element Status 2FC192
51-54Ctrl Element Status 1FC191
Profibus Input Data
CategoryAddress (By Bytes)DescriptionFormat
Status-Motor0Motor StatusFC129
2Extended StatusFC178
4Thermal Cap UsedF1
6Time to Overload TripF20
10Overload LockoutF1
12ReservedNA
14ReservedNA
16ReservedF1
18ReservedNA
20ReservedNA
22ReservedNA
24ReservedNA
26ReservedNA
Learned28Learned Acceleration TimeF2
30Learned Starting CurrentF10
34Learned Starting CapacityF1
Counters36Number of Motor StartsF1
38ReservedNA
40Motor Running HoursF9
44ReservedNA
46ReservedNA
MM200 MOTOR MANAGEMENT SYSTEM – COMMUNICATIONS GUIDE29
FIELDBUS INTERFACECOMMUNICATIONS GUIDE
CategoryAddress (By Bytes)DescriptionFormat
48ReservedNA
50ReservedNA
52ReservedNA
54ReservedNA
56ReservedNA
58ReservedNA
Current Metering60IaF10
64IbF10
68IcF10
72ReservedNA
74ReservedNA
76ReservedNA
78IavgF10
82IgrdF10
86Motor LoadF1
88I UnbF1
90ReservedNA
92ReservedNA
94ReservedNA
96ReservedNA
98ReservedNA
100ReservedNA
102ReservedNA
104ReservedNA
106ReservedNA
108ReservedNA
110ReservedNA
112ReservedNA
114ReservedNA
116ReservedF3
118ReservedNA
120ReservedNA
122ReservedNA
126ReservedNA
128ReservedNA
132ReservedNA
134ReservedNA
138ReservedNA
140ReservedNA
142ReservedNA
146ReservedNA
148ReservedNA
150ReservedNA
152ReservedNA
154ReservedNA
156ReservedNA
158ReservedNA
30MM200 MOTOR MANAGEMENT SYSTEM – COMMUNICATIONS GUIDE
COMMUNICATIONS GUIDEFIELDBUS INTERFACE
CategoryAddress (By Bytes)DescriptionFormat
160ReservedNA
162ReservedNA
164ReservedNA
166ReservedNA
168ReservedNA
170ReservedNA
172ReservedNA
174ReservedNA
176ReservedNA
178ReservedNA
Last Trip Data180Cause of Last TripFC134
182ReservedNA
186ReservedNA
190Pre Trip IaF10
194Pre Trip IbF10
198Pre Trip IcF10
202Pre Trip Motor LoadF1
204Pre Trip Current UnbalanceF1
206Pre Trip IgrdF10
210ReservedNA
212ReservedNA
214ReservedNA
216ReservedNA
218ReservedNA
220ReservedNA
222ReservedNA
224ReservedNA
226ReservedNA
228ReservedNA
232ReservedNA
236ReservedNA
238ReservedNA
MM200 MOTOR MANAGEMENT SYSTEM – COMMUNICATIONS GUIDE31
FIELDBUS INTERFACECOMMUNICATIONS GUIDE
DeviceNet protocol
To enable the DeviceNet physical interface, ensure that switches 1 and 2 of the DIP switch
communications card (on the CPU) 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
MM200 Setup software. The MM200 supports the following DeviceNet object classes.
CLASSOBJECT
01HIdentify
02HMessage Router
03HDeviceNet
05HConnection
64HIO Data
A0HGeneric Data - Polling/Explicit
B1HExplicit Control Writes
B0HAnalog Data - Explicit
32MM200 MOTOR MANAGEMENT SYSTEM – COMMUNICATIONS GUIDE
COMMUNICATIONS GUIDEFIELDBUS INTERFACE
The MM200 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)
Message Router (Class
Code 02H)
Table 15: Identity Object, Class Code 01h, Services:
CODESERVICES AVAILABLE TO THIS OBJECT
NAMEDESCRIPTION
0x05ResetReset the device to power up configuration
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)2USINT1.00
07hGetProduct NameSHORTSTRINGMM200 MOTOR
MANAGEMENT RELAY
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
NAMEDESCRIPTION
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
MM200 MOTOR MANAGEMENT SYSTEM – COMMUNICATIONS GUIDE33
FIELDBUS INTERFACECOMMUNICATIONS GUIDE
Table 20: Identity Object, Class Code 03h, Instance 01h, Attributes: