Page 2
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.
DeviceNet - Explicit Motor Analog Data Object (Class Code A2H, Services) ..133 DeviceNet - Explicit Motor Analog Data Object, Class Code B0H, Services..135 DeviceNet - Explicit Motor Object, Class Code B1H............138 Change notes ..........................141 Revision history..........................141 MM300 MOTOR MANAGEMENT SYSTEM – COMMUNICATIONS GUIDE...
Page 4
MM300 MOTOR MANAGEMENT SYSTEM – COMMUNICATIONS GUIDE...
External power must be present on the Fieldbus port at power-up, in order to correctly NOTE: initialize and operate. NOTE For full details, please refer to the MM300 Communications Guide, to be found on the GE NOTE: Multilin web site. NOTE...
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.
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...
Modbus implementation: Read Holding Registers 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.
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.
CODE VALUE FF 00 perform function DF 6A CRC error code The commands that can be performed by the MM300 using function code 05 can also be initiated by using function code 10. MM300 MOTOR MANAGEMENT SYSTEM – COMMUNICATIONS GUIDE...
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.
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...
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.
CHAPTER 1: COMMUNICATIONS GUIDE 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).
Pre Trip Motor Load 2000 30202 00C9 Pre Trip Current Unbalance 30203 00CA Pre Trip Ig 30205 00CC Pre Trip Vab 30206 00CD Pre Trip Vbc 30207 00CE Pre Trip Vca 30208 00CF Pre Trip Van MM300 MOTOR MANAGEMENT SYSTEM – COMMUNICATIONS GUIDE...
Page 16
Start Timer 2 30264 0107 Start Timer 3 30265 0108 Start Timer 4 30266 0109 Start Timer 5 30267 010A TransferTimer 30268 010B Power Loss Time 0xFFFF 30269 010C Motor Stopped Hours START BLOCKS MM300 MOTOR MANAGEMENT SYSTEM – COMMUNICATIONS GUIDE...
Page 17
▼ ▼ ▼ ▼ ▼ ▼ ▼ ▼ ▼ 30327 0146 Reserved CURRENT METERING 30328 0147 30330 0149 30332 014B 30334 014D Iavg 30336 014F Motor Load 30337 0150 Current Unbalance 30338 0151 MM300 MOTOR MANAGEMENT SYSTEM – COMMUNICATIONS GUIDE...
Page 18
Phase A Apparent Power 50000 30408 0197 Phase A Reactive Power -50000 50000 kvar 30409 0198 Phase A Power Factor eUnitPF 30410 0199 Phase B Real Power -50000 50000 30411 019A Phase B Apparent Power 50000 MM300 MOTOR MANAGEMENT SYSTEM – COMMUNICATIONS GUIDE...
Page 19
30471 01D6 Reserved ▼ ▼ ▼ ▼ ▼ ▼ ▼ ▼ ▼ ▼ 30483 01E2 Reserved 30484 01E3 Average Motor Load Learned %FLA RTD MAXIMIUM TEMPERATURE 30485 01E4 RTD 1 MAX Temp °C MM300 MOTOR MANAGEMENT SYSTEM – COMMUNICATIONS GUIDE...
Page 20
30659 0292 Event Recorder Last Reset 2 words 30661 0294 Total Number of Events Since Last Clear 30662 0295 Cause FC134 30663 0296 Contactor FC136 30664 0297 Time 30666 0299 Date 30668 029B MM300 MOTOR MANAGEMENT SYSTEM – COMMUNICATIONS GUIDE...
Page 21
Sample Index + Trace Memory -32767 32767 Sample7 30727 Sample Index + Trace Memory -32767 32767 Sample8 30728 Sample Index + Trace Memory -32767 32767 Sample9 30729 Sample Index + Trace Memory -32767 32767 Sample10 MM300 MOTOR MANAGEMENT SYSTEM – COMMUNICATIONS GUIDE...
Page 22
Sample Index + Trace Memory -32767 32767 Sample36 30755 Sample Index + Trace Memory -32767 32767 Sample37 30756 Sample Index + Trace Memory -32767 32767 Sample38 30757 Sample Index + Trace Memory -32767 32767 Sample39 MM300 MOTOR MANAGEMENT SYSTEM – COMMUNICATIONS GUIDE...
Page 23
Sample Index + Trace Memory -32767 32767 Sample64 30783 Sample Index + Trace Memory -32767 32767 Sample65 30784 Sample Index + Trace Memory -32767 32767 Sample66 30785 Sample Index + Trace Memory -32767 32767 Sample67 MM300 MOTOR MANAGEMENT SYSTEM – COMMUNICATIONS GUIDE...
Page 24
Sample Index + Trace Memory -32767 32767 Sample91 30811 Sample Index + Trace Memory -32767 32767 Sample92 30812 Sample Index + Trace Memory -32767 32767 Sample93 30813 Sample Index + Trace Memory -32767 32767 Sample94 MM300 MOTOR MANAGEMENT SYSTEM – COMMUNICATIONS GUIDE...
Page 25
Sample Index + Trace Memory -32767 32767 Sample119 30839 Sample Index + Trace Memory -32767 32767 Sample120 30840 Sample Index + Trace Memory -32767 32767 Sample121 30841 Sample Index + Trace Memory -32767 32767 Sample122 MM300 MOTOR MANAGEMENT SYSTEM – COMMUNICATIONS GUIDE...
Page 26
31375 055E Reserved 31376 055F Reserved 31377 0560 Reserved COMMUNICATION 31378 0561 Serial Status FC112 31379 0562 Ethernet Status FC112 31380 0563 Profibus Status FC112 31381 0564 DeviceNet Status FC112 31382 0565 Reserved MM300 MOTOR MANAGEMENT SYSTEM – COMMUNICATIONS GUIDE...
Page 28
Aux VT Secondary 40280 0117 Reserved 40281 0118 Reserved 40282 0119 Reserved 40283 011A Reserved MOTOR DATA SETUP 40284 011B Supply Frequency FC107 40285 011C Motor Name 40295 0126 Starter Type FC139 40296 0127 Reserved MM300 MOTOR MANAGEMENT SYSTEM – COMMUNICATIONS GUIDE...
Page 29
IL C Running Override 3601 40372 0173 IL C Healthy State FC116 40373 0174 Reserved ▼ ▼ ▼ ▼ ▼ ▼ ▼ ▼ ▼ ▼ 40377 0178 Reserved 40378 0179 IL D Name MM300 MOTOR MANAGEMENT SYSTEM – COMMUNICATIONS GUIDE...
Page 30
01D7 IL H Healthy State FC116 40473 01D8 Reserved ▼ ▼ ▼ ▼ ▼ ▼ ▼ ▼ ▼ ▼ 40477 01DC Reserved 40478 01DD IL I Name 40488 01E7 IL I Function FC140 MM300 MOTOR MANAGEMENT SYSTEM – COMMUNICATIONS GUIDE...
Page 31
Event Recorder Function FC126 40660 0293 Recording of Trip Events FC126 40661 0294 Recording of Alarm Events FC126 40662 0295 Recording of Control Events FC126 40663 0296 Recording of Logic Input FC126 Events MM300 MOTOR MANAGEMENT SYSTEM – COMMUNICATIONS GUIDE...
Page 41
Process Interlock B 0xE000 FC142 41396 0573 Process Interlock C 0xE000 FC142 41397 0574 Process Interlock D 0xE000 FC142 41398 0575 Process Interlock E 0xE000 FC142 41399 0576 Process Interlock F 0xE000 FC142 MM300 MOTOR MANAGEMENT SYSTEM – COMMUNICATIONS GUIDE...
Page 42
41497 05D8 USER2 LED Assignment 0xE000 FC142 41498 05D9 USER2 LED Colour FC157 41499 05DA USER3 LED Assignment 0xE000 FC142 41500 05DB USER3 LED Colour FC157 41501 05DC 50% LED Assignment 0xE000 FC142 MM300 MOTOR MANAGEMENT SYSTEM – COMMUNICATIONS GUIDE...
High Order Word of Long Value 2nd 16 bits Low Order Word of Long Value Example: -12345.6 stored as -123456 i.e. 1st word: FFFE hex, 2nd word: 1DC0 hex 16 bits HARDWARE REVISION Prototype MM300 MOTOR MANAGEMENT SYSTEM – COMMUNICATIONS GUIDE...
Page 46
Lagging Power Factor - Positive Example: Power Factor of 0.87 lag is used as 87 i.e. 0057 16 bits TWO 8-BIT CHARACTERS PACKED INTO 16-BIT UNSIGNED First Character Second Character Example: String ‘AB’ stored as 4142 hex MM300 MOTOR MANAGEMENT SYSTEM – COMMUNICATIONS GUIDE...
Page 47
DATA LOGGER CHANNEL DATA Disabled Phase A Current Phase B Current Phase C Current Average Phase Current Motor Load Current Unbalance Ground Current System Frequency Power Factor Real Power (kW) Reactive Power (kvar) Apparent Power (kVA) MM300 MOTOR MANAGEMENT SYSTEM – COMMUNICATIONS GUIDE...
Page 48
FC109 16 bits Flex Logic Status Unknown Token Too Many Latches Too Many Timers Too Many + OneShots Too Many - OneShots Too Many Duel OneShots Stack Overflow Stack Underflow Program Too Long MM300 MOTOR MANAGEMENT SYSTEM – COMMUNICATIONS GUIDE...
Page 49
Bit 4 Contactor A Bit 5 Contactor B Bit 6 Contact Output 3 Bit 7 Drive Available FC130 16 bits LED Flash Bit 0 Running Bit 1 Stopped Bit 2 Tripped Bit 3 Alarm MM300 MOTOR MANAGEMENT SYSTEM – COMMUNICATIONS GUIDE...
Page 50
0xD0 VO 17 0xD1 VO 18 0xD2 VO 19 0xD3 VO 20 0xD4 VO 21 0xD5 VO 22 0xD6 VO 23 0xD7 VO 24 0xD8 VO 25 0xD9 VO 26 0xDA VO 27 MM300 MOTOR MANAGEMENT SYSTEM – COMMUNICATIONS GUIDE...
Page 51
Process ILock A Trip 0x8502 Process ILock B Trip 0x8542 Process ILock C Trip 0x8582 Process ILock D Trip 0x85C2 Process ILock E Trip 0x8602 Process ILock F Trip 0x8642 Process ILock G Trip MM300 MOTOR MANAGEMENT SYSTEM – COMMUNICATIONS GUIDE...
Page 52
Process ILock I Alarm 0xA702 Process ILock J Alarm 0xA742 Drive Failed to Start 0xA782 Inverter Failed 0xA7C2 Drive Stop Failed 0xA802 Aux U/V Alarm 0xA842 External Stop Alarm 0xA882 Fuse Fail Alarm MM300 MOTOR MANAGEMENT SYSTEM – COMMUNICATIONS GUIDE...
Page 53
Process ILock I Stop 0xC702 Process ILock J Stop 0xC742 HW Stop 0xC782 Field Stop 0xC7C2 MCC Stop 0xC802 Access Switch Closed 0xC842 Test Switch Closed 0xC882 Hard Wired Start A 0xC8C2 Hard Wired Start B MM300 MOTOR MANAGEMENT SYSTEM – COMMUNICATIONS GUIDE...
Page 54
High Speed FC136 16 bits Contactor None FC139 16 bits Starter Type None FV Nonreversing FV Reversing Two Speed Wye-Delta Inverter Soft Starter Custom Starter FC140 16 bits Interlock Function Disabled Trip Alarm Stop MM300 MOTOR MANAGEMENT SYSTEM – COMMUNICATIONS GUIDE...
Page 55
Virtual Input 4 On 0x0084 Virtual Input 5 On 0x0085 Virtual Input 6 On 0x0086 Virtual Input 7 On 0x0087 Virtual Input 8 On 0x0088 Virtual Input 9 On 0x0089 Virtual Input 10 On MM300 MOTOR MANAGEMENT SYSTEM – COMMUNICATIONS GUIDE...
Page 56
Virtual Output 19 On 0x00D3 Virtual Output 20 On 0x00D4 Virtual Output 21 On 0x00D5 Virtual Output 22 On 0x00D6 Virtual Output 23 On 0x00D7 Virtual Output 24 On 0x00D8 Virtual Output 25 On MM300 MOTOR MANAGEMENT SYSTEM – COMMUNICATIONS GUIDE...
Page 57
AND (14 inputs) 0x054F AND (15 inputs) 0x0550 AND (16 inputs) 0x0582 NOR (2 inputs) 0x0583 NOR (3 inputs) 0x0584 NOR (4 inputs) 0x0585 NOR (5 inputs) 0x0586 NOR (6 inputs) 0x0587 NOR (7 inputs) MM300 MOTOR MANAGEMENT SYSTEM – COMMUNICATIONS GUIDE...
Page 61
0xC1C2 Contactor B 0xC202 Forward Limit 0xC242 Reverse Limit 0xC282 Starts/Hr Inhibit 0xC2C2 Time Between Inhibit 0xC3C2 Comms Ctrl Active 0xC402 Hard Wired Ctrl Active 0xC442 Field Ctrl Active 0xC482 MCC Ctrl Active MM300 MOTOR MANAGEMENT SYSTEM – COMMUNICATIONS GUIDE...
Page 62
UV Restart Inhibit 0xCE02 Drive Available 0xCE42 Drive Available Manual 0xCE82 Drive Available Auto 0xCEC2 Stop A 0xCF02 Stop B FC143 16 bits Drive Status Drive Unavailable Available Auto Available Manual Available Running MM300 MOTOR MANAGEMENT SYSTEM – COMMUNICATIONS GUIDE...
Page 63
Trace Memory Trigger Mode Retrigger One-Shot FC150 32 bits IP Address 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 MM300 MOTOR MANAGEMENT SYSTEM – COMMUNICATIONS GUIDE...
Page 64
Input/Output 16 Bit 16 Input/Output 17 Bit 17 Input/Output 18 Bit 18 Input/Output 19 Bit 19 Input/Output 20 Bit 20 Input/Output 21 Bit 21 Input/Output 22 Bit 22 Input/Output 23 Bit 23 Input/Output 24 MM300 MOTOR MANAGEMENT SYSTEM – COMMUNICATIONS GUIDE...
Page 65
Bit 26 Input/Output 59 Bit 27 Input/Output 60 Bit 28 Input/Output 61 Bit 29 Input/Output 62 Bit 30 Input/Output 63 Bit 31 Input/Output 64 FC169 16 bits Month Not Set January February March April MM300 MOTOR MANAGEMENT SYSTEM – COMMUNICATIONS GUIDE...
Page 66
Stop Trip FC175 16 bits Test Auto/Manual Mode Unaffected FC176 16 bits Auxiliary VT Connection Vab VT Vbc VT Vca VT Van VT Vbn VT Vcn VT Van Direct Vbn Direct Vcn Direct MM300 MOTOR MANAGEMENT SYSTEM – COMMUNICATIONS GUIDE...
Page 67
Process ILock F Alarm Bit 25 Process ILock G Alarm Bit 26 Process ILock H Alarm Bit 27 Process ILock I Alarm Bit 28 Process ILock J Alarm Bit 29 Drive Failed to Start MM300 MOTOR MANAGEMENT SYSTEM – COMMUNICATIONS GUIDE...
Page 68
Process ILock C Trip Bit 22 Process ILock D Trip Bit 23 Process ILock E Trip Bit 24 Process ILock F Trip Bit 25 Process ILock G Trip Bit 26 Process ILock H Trip MM300 MOTOR MANAGEMENT SYSTEM – COMMUNICATIONS GUIDE...
Page 69
Message Status 3 (Reserved) FC190 32 bits Message Status 4 (Reserved) FC191 32 bits Ctrl Element Status 1 Bit 0 Any Stop Bit 1 Thermal Inhibit Bit 2 AutoMode Bit 3 Manual Mode MM300 MOTOR MANAGEMENT SYSTEM – COMMUNICATIONS GUIDE...
Page 70
Bit 10 Remote Reset Bit 11 Lockout Reset Bit 12 UV Restart Bit 13 Pre-Contactor Bit 14 MCC Start A Bit 15 MCC Start B Bit 16 Bypass Contact Bit 17 Comm Start A MM300 MOTOR MANAGEMENT SYSTEM – COMMUNICATIONS GUIDE...
2 setpoints = 4 bytes total BYTE COUNT 4 bytes of data DATA 1 00 05 data for address 00 DATA 2 00 01 data for address 00 7E CE CRC error code MM300 MOTOR MANAGEMENT SYSTEM – COMMUNICATIONS GUIDE...
42 B0 CRC error code Using the User The MM300 contains a User Definable area in the memory map. This area allows re- Definable Memory mapping of the addresses of any Actual Values or Setpoints registers. The User Definable area has two sections: A Register Index area (memory map addresses 020BH-0287H) that contains 125 Actual Values or Setpoints register addresses.
Once connected to the source, the clock is updated every 30 seconds. If the IP address of the relay is changed for any reason, the relay must be powered down NOTE: then restarted in order for the new IP address to take effect. NOTE MM300 MOTOR MANAGEMENT SYSTEM – COMMUNICATIONS GUIDE...
Modbus User Map feature available on the MM300. Configure the setpoint Fieldbus Input Data available in the Communications Settings group (Home > Setpnts > Cfg > Comms) page from the MM300 Graphical front panel if you have ordered one with your unit).
Pin 5 Pin 8, line A (negative TX/RX) Common drain Pin 3, line B (positive TX/RX) Pin 6 The Modbus status (MS) and network status (NS) LEDs indicate the status of the Fieldbus interface. MM300 MOTOR MANAGEMENT SYSTEM – COMMUNICATIONS GUIDE...
Auto-detect includes baud rates 19.2 kbps, 187.5 kbps, 500 kbps, and 1.5 Mbps. The Profibus DP Master must read the GSE (Device Master Data) file of the MM300 for the purposes of configuration and parameterization. The GSE file for the MM300 is named GEMU4D20.gse.
The Profibus bus address (MAC ID) of the MM300 slave, which has a range from 1 to 126, can be set via the Profibus Address setting on the HMI from the Home > Setpnts > Cfg >...
Page 78
FIELDBUS INTERFACE CHAPTER 1: COMMUNICATIONS GUIDE Figure 2: Profibus configuration menu The diagram below shows the input and output data read from the MM300 with the configuration above Figure 3: Profibus I/O data - 95 words in, 1 word out The following DP Master configuration menu shows how a smaller set of I/O poll data can be chosen from the available modules in the GSE file.
Page 79
When a size of input data smaller than the maximum is configured, the data read from the MM300 by the master will start at address 0 of the Profibus Input Data table (refer to section 4.1.4) and provide data in the order shown in that table, up to the size configured.
The capability to reset, stop, and start the motor has been made available via the Profibus Output data. Because polled output data is continuously written to the slave device, the MM300 looks for a change in the value to execute any command. Byte...
Page 92
Reserved Reserved Reserved Reserved Reserved Reserved Reserved Reserved Reserved Reserved Reserved "Transfer Timer" "FLA Not Set" "CT Type Not Set" "Starter Type Not Set" "No Control Source" "Clock Not Set" "FLA Too High" MM300 MOTOR MANAGEMENT SYSTEM – COMMUNICATIONS GUIDE...
The following diagram shows an example of the extended diagnostic data sent to the Profibus master by the MM300. The extended diagnostic data is only provided when one of the states listed in the above extended diagnostic table has become true. In this example, the extended diagnostic data has been sent because the "External Start A Alarm"...
The extended diagnosis consists of Process Alarms and Diagnostic Alarms. Trip, Alarm, and Control status are categorized as Process Alarms, as these provide information pertaining to the Motor health that MM300 is controlling and monitoring. Messages are categorized as Diagnostic Alarms as these provide detailed MM300 diagnostic information.
Page 97
Table 16: DPV1 diagnostic alarms Byte GSE Bit # Ext. Diag Byte Standard Station Status 1 Diagnosis Station Status 2 Station Status 3 Master Address Man Id Man Id Length Alarm Type Alarm Type - Process Alarm MM300 MOTOR MANAGEMENT SYSTEM – COMMUNICATIONS GUIDE...
I&M records can be read using the following sequence of Reads and Writes from the Maintenance) records Profibus Master. Send a Write Call-REQ-PDU i.e., DPV1 write request (MS1 and MS2) to the MM300, on slot 0, index 255 and FI_Index = 65000 Content...
Page 108
(same as that in request) Index 1 Octet fixed Length 1 Octet Call Header Send a Read-REQ-PDU i.e., DPV1 Read request (MS1 and MS2) to MM300, on slot 0, index 255 and Length = 68: Content Size Coding Notes DPV1 Header...
Figure 7: I&MO example on MS1 connection Figure 8: I&MO example on MS2 connection The MM300 supports the mandatory I&M0 record. It does not support the optional I&M1, I&M2, I&M3 and I&M4 records. Requests for these I&M Records would result in an error response from the MM300.
Connect the DeviceNet connector on the 1770-KFD module to a DeviceNet cable. The terminal designations are as shown in the table below: Terminal Signal Function Color Common Black CAN_L Signal Low Blue Drain Shield Non-insulated CAN_H Signal High White Power Supply MM300 MOTOR MANAGEMENT SYSTEM – COMMUNICATIONS GUIDE...
Page 112
10-pin linear plug into the connector. Connect the other end of the DeviceNet cable into this connector. Locate the DeviceNet connector on the MM300 (see top left-hand corner of the diagram below) and connect it to the scanner using the DeviceNet Cable.
Page 113
Terminal designations are as shown in the table below: Terminal Function Color Common Black Signal Low Blue Shield Non insulated Signal High White Power Supply After the connections are complete, the network will look something like this: MM300 MOTOR MANAGEMENT SYSTEM – COMMUNICATIONS GUIDE...
Page 114
CHAPTER 1: COMMUNICATIONS GUIDE Powering up the network Before switching ON the network power make sure that the MACID of MM300 is set to something other than 63. Switch on the power supply to the chassis that will power up the device.
Page 115
CHAPTER 1: COMMUNICATIONS GUIDE FIELDBUS INTERFACE The following dialog appears: Select DeviceNet Drivers from the above pull-down menu and Click Add/New. The following menu will appear: MM300 MOTOR MANAGEMENT SYSTEM – COMMUNICATIONS GUIDE...
Page 116
This dialog will only appear if there is at least one active node on the DeviceNet network, so NOTE: ensure that the network power is on and that the MM300 relay and the scanner are on the DeviceNet network. NOTE Select the default driver name, 1770-KFD-1, and click OK.
Page 117
From the File menu, choose New. Highlight DeviceNet Configuration and click OK. Next step is to register the EDS file for the MM300. Select the EDS Wizard from the Tools menu as shown below: MM300 MOTOR MANAGEMENT SYSTEM – COMMUNICATIONS GUIDE...
Page 118
FIELDBUS INTERFACE CHAPTER 1: COMMUNICATIONS GUIDE Press Next Click on Register an EDS file: MM300 MOTOR MANAGEMENT SYSTEM – COMMUNICATIONS GUIDE...
Page 119
CHAPTER 1: COMMUNICATIONS GUIDE FIELDBUS INTERFACE Browse and select the EDS file for MM300. Make sure that the Icon file is present in the same folder as the EDS file. Save the DeviceNet file after registering the EDS file. Close the RSNetworx software and reboot the PC.
Page 120
11. Select the 1770-KFD-1, DeviceNet driver and click OK. You will be prompted to upload or download devices before going online. 12. Click OK to upload the devices and go online. RSNetWorx for DeviceNet software begins browsing for network devices. MM300 MOTOR MANAGEMENT SYSTEM – COMMUNICATIONS GUIDE...
Page 121
FIELDBUS INTERFACE 13. When the software has finished browsing, the network displayed on your screen should appear similar to the one shown below. MM300, Scanner and the 1770 KFD modules will appear with MACIDs just below each device. 14. After the network is uploaded, the next step is to set the node address of the 1747 SDN scanner and to configure the scan list.
Page 122
From the right panel,select the device you are commissioning and click OK. The Node Commissioning dialog appears with the current settings for your 1747-SDN module. The dialog should look similar to the one shown below: MM300 MOTOR MANAGEMENT SYSTEM – COMMUNICATIONS GUIDE...
Page 123
After setting node address of the scanner click on Single Browse from the network menu. The 1747 SDN module should appear with the new node ID. Double-click the 1747-SDN module icon. The following dialog will appear: Click the Module tab. You will receive the following prompt: MM300 MOTOR MANAGEMENT SYSTEM – COMMUNICATIONS GUIDE...
Page 124
Click Upload. After uploading, the following dialog will appear: Verify the 1747-SDN-module slot number is correct for the system. Select the Scanlist tab. The MM300 relay will be seen in the Available Devices list. Verify that the Automap on Add box is NOT checked.
Page 125
CHAPTER 1: COMMUNICATIONS GUIDE FIELDBUS INTERFACE Click the double arrow (>>)to move the MM300 from the Available Devices list to the Scanlist. Select Major Revision as the part of the electronic key for MM300. Double-click MM300 in the Scanlist. The Edit I/O Parameters dialog (shown below) appears for the MM300.
In the MM300, only the contents of the A1 object are supported by ADR. Enabling ADR Before proceeding to the next step ensure that the MM300 relay and the network are NOTE: configured as desired. These configurations will be then stored in the scanner for the ADR feature.
Page 127
10. This will enable the Configuration Recovery check box. Click the box to enable it. If the device also has Auto-Address Recovery and if this option is also desired, then click it too. MM300 MOTOR MANAGEMENT SYSTEM – COMMUNICATIONS GUIDE...
Page 128
So always remember to UPLOAD the MM300 configuration into the RSNetWorx and SAVE the file before enabling ADR. The MM300 does not support auto baud detection. So in a situation where the faulted device is replaced with a new device with default settings, ensure that the baud rate of the MM300 is same as that of the scanner.
CHAPTER 1: COMMUNICATIONS GUIDE FIELDBUS INTERFACE 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 The MM300 profile is an extension of the Communications Adapter Device Profile (0xC0). It Communications is a group 2 only server.
In the event that there is a communication fault, and a pre-fault polled output command caused the MM300 to start a motor, the motor will continue to run even after the communication fault. To prevent this situation from occurring when remote communication is used with the device the user must ensure that the 'Comm Failure Trip' feature is configured.
SERVICES AVAILABLE TO THIS OBJECT 05H) NAME DESCRIPTION 0x05 Reset Reset the device to power up configuration 0x0E Get_Attribute_Single Returns the contents of the given attribute 0x10 Set_Attribute_Single Sets the contents of the given attribute MM300 MOTOR MANAGEMENT SYSTEM – COMMUNICATIONS GUIDE...
DeviceNet Motor Data Table 29: Motor Data Object, Class Code A0h, Services: - Explicit Object (Class CODE SERVICES AVAILABLE TO THIS OBJECT Code A0H) NAME DESCRIPTION 0x0E Get_Attribute_Single Returns the contents of the given attribute MM300 MOTOR MANAGEMENT SYSTEM – COMMUNICATIONS GUIDE...
Page 133
Average Line Voltage (V) Real power (kW) Power factor Contact Input Status BIT per input Contact Output Status BIT per output Local hottest RTD number Unsigned 8 bit integer Local hottest RTD temperature MM300 MOTOR MANAGEMENT SYSTEM – COMMUNICATIONS GUIDE...
Aux VT Primary Volts Aux VT Secondary Volts Supply Frequency FC107 Starter Type None FC139 Motor FLA Amps 10001 10001 High Speed FLA Amps 10001 10001 Motor Name Plate Voltage Volts Change Over Current MM300 MOTOR MANAGEMENT SYSTEM – COMMUNICATIONS GUIDE...
ATTRIBUTE NO. DESCRIPTION UNIT FORMAT SIZE IN BYTES (HEX VALUE) CODE Phase A current Amps Phase B current Amps Phase C current Amps Average Phase current Amps Ground Current Amps Motor Load Current Unbalance MM300 MOTOR MANAGEMENT SYSTEM – COMMUNICATIONS GUIDE...
Page 138
Pre Trip Motor Load Pre Trip Current Unbalance Pre Trip Vab Voltage Volts Pre Trip Vbc Voltage Volts Pre Trip Vca Voltage Volts Pre Trip Van Voltage Volts Pre Trip Vbn Voltage Volts MM300 MOTOR MANAGEMENT SYSTEM – COMMUNICATIONS GUIDE...
Table 36: Explicit Motor Analog Data Object, Class Code B0h, Services: Motor Analog Data CODE SERVICES AVAILABLE TO THIS OBJECT Object, Class Code NAME DESCRIPTION B0H, Services 0x0E Get_Attribute_Single Returns the contents of the given attribute MM300 MOTOR MANAGEMENT SYSTEM – COMMUNICATIONS GUIDE...
Page 140
Table 38: Data Formats, Explicit Motor Analog Data Object ATTRIBUTE ITEM DESCRIPTION SIZE IN FORMAT BYTES Currents Iavg Igrd Motor load Motor Load I Unb Line voltages Average Line Voltage Phase voltages Reserved MM300 MOTOR MANAGEMENT SYSTEM – COMMUNICATIONS GUIDE...
Page 141
Last pre-trip line voltages Pre Trip Vab Pre Trip Vbc Pre Trip Vca Last pre-trip phase voltages Pre Trip Van Pre Trip Vbn Pre Trip Vcn Last pre-trip frequency Pre Trip System Frequency MM300 MOTOR MANAGEMENT SYSTEM – COMMUNICATIONS GUIDE...
Clear Last Trip Data Prompt 0x43 Reset MWh and Mvarh Meters 0x44 Clear Counters 0x45 Clear Event Records 0x46 Clear Waveform Data 0x47 Clear Maintenance Timer 0x48 Clear RTD Maximums 0x49 Reset Motor Information 0x4A Auto Mode MM300 MOTOR MANAGEMENT SYSTEM – COMMUNICATIONS GUIDE...
11 June 2008 1601-9025-A4 17 October 2008 1601-9025-A5 2 June 2009 1601-9025-A6 15 April 2010 Table A–2: Major Updates for MM300 Comm Guide-A6 Section Number CHANGES Manual revision number from A5 to A6 Modbus Memory Map Changes Format Codes Changes General Minor Corrections and Updates MM300 MOTOR MANAGEMENT SYSTEM –...
Page 146
APPENDIX Table A–3: Major Updates for MM300 Comm Guide-A5 Section Number CHANGES Manual revision number from A4 to A5 2.1.1 Electrical Interface Section updated 4.1.6 Profibus DPV0 Diagnostics Added DPV0 Diagnostic Alarm table 4.2 Profibus DPV1 New section added 4.3.1 DeviceNet PS Config...
Need help?
Do you have a question about the MM300 and is the answer not in the manual?
Questions and answers