CHAPTER 1: COMMUNICATIONS GUIDE FIELDBUS INTERFACE
MM300 MOTOR MANAGEMENT SYSTEM – COMMUNICATIONS GUIDE 125
4. Considering the scanner’s limited memory for storage of the ADR configuration, more
than one scanner will be required if there are many MM300 relays in the DeviceNet
network.
DeviceNet
Communications
The MM300 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.
The MM300 supports poll and explicit messaging types.
The Poll function consumes one byte of control data (described under User Object Class
B1h, Instance 01h, Attribute 01h) and produces 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
Poll data The Polling function consumes one byte of control data and produces 38 bytes of status
and metering data as described in User Object Class A0h, Instance 01h, Attribute 01h. The
control data format is as follows:
Table 19: Data Value, polled output data
CLASS OBJECT
01H Identify
02H Message Router
03H DeviceNet
05H Connection
A0H Generic Data - Polling/Explicit
B1H Explicit Control Writes
B0H Analog Data - Explicit
A1H Configuration Data - Explicit
A2H Analog Data - Explicit
VALUE DESCRIPTION
Dec Hex
1 0x01 Reset
20x02Lockout Reset
30x03Stop
40x04Start A
50x05Start B
66 0x42 Clear Last Trip Data Prompt
67 0x43 Reset MWh and Mvarh Meters
68 0x44 Clear Counters
69 0x45 Clear Event Records
70 0x46 Clear Waveform Data
71 0x47 Clear Maintenance Timer
72 0x48 Clear RTD Maximums
73 0x49 Reset Motor Information
To Next Page