GE Multilin MM200 Communications Manual
  1. Manuals
  2. Brands
  3. GE Multilin Manuals
  4. Control Systems
  5. MM200
  6. Communications manual

GE Multilin MM200 Communications Manual

Motor management system
Hide thumbs Also See for MM200:
Table of Contents

Advertisement

Quick Links

GE
Grid Solutions
Communications Guide
MM200 Revision: 1.2x
Manual P/N: 1601-9033-A5
Manual Order Code: GEK-113402D
*1601-9033-A5*
MM200 Motor Management
System
E83849
LISTED
IND.CONT. EQ.
52TL

Advertisement

Table of Contents
loading

Related Manuals for GE Multilin MM200

Summary of Contents for GE Multilin MM200

  • Page 1 Grid Solutions MM200 Motor Management System Communications Guide MM200 Revision: 1.2x Manual P/N: 1601-9033-A5 Manual Order Code: GEK-113402D E83849 LISTED *1601-9033-A5* IND.CONT. EQ. 52TL...
  • 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.
  • Page 3 Worldwide telephone: +1 905 927 7070 Europe/Middle East/Africa telephone: +34 94 485 88 54 North America toll-free: 1 800 547 8629 Fax: +1 905 927 5098 Worldwide e-mail: multilin.tech@ge.com Europe e-mail: multilin.tech.euro@ge.com Website: http://www.gegridsolutions.com/multilin MM200 MOTOR MANAGEMENT SYSTEM – COMMUNICATIONS GUIDE...
  • Page 4 MM200 MOTOR MANAGEMENT SYSTEM – COMMUNICATIONS GUIDE...

  • Page 5: Table Of Contents

    Message Router (Class Code 02H).....................3-47 DeviceNet Object (Class Code 03H) ....................3-48 DeviceNet Connection Object (Class Code 05H).................3-48 DeviceNet Motor Data - Explicit Object (Class Code A0H)............3-49 DeviceNet Motor Data - Explicit Object (Class Code A1H)............3-51 MM200 MOTOR MANAGEMENT SYSTEM – COMMUNICATIONS GUIDE...
  • Page 6 DeviceNet Motor Analog Data - Explicit Object (Class Code A2H) ........3-53 DeviceNet - Explicit Motor Analog Data Object, Class Code B0H, Services....3-55 DeviceNet - Explicit Motor Object, Class Code B1H ..............3-57 A.APPENDIX Change notes ............................A-1 Revision history............................A-1 Warranty..............................A-2 MM200 MOTOR MANAGEMENT SYSTEM – COMMUNICATIONS GUIDE...
  • Page 7 External power must be present on the Fieldbus port at power-up, in order to correctly NOTE: initialize. NOTE For full details, please refer to the MM200 Communications Guide, to be found on the GE NOTE: Multilin web site. NOTE MM200 MOTOR MANAGEMENT SYSTEM – COMMUNICATIONS GUIDE...
  • Page 8 CHAPTER 1: COMMUNICATIONS INTERFACES MM200 MOTOR MANAGEMENT SYSTEM – COMMUNICATIONS GUIDE...

  • Page 9: (Modbus Rtu) Electrical Interface

    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.

  • Page 10: Data Frame Format And Data Rate

    Data Frame Format and Data Rate 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).

  • Page 11: Crc-16 Algorithm

    CHAPTER 2: RS485 INTERFACE (MODBUS RTU) MODBUS PROTOCOL 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.

  • Page 12: Mm200 Supported Functions

    Modbus 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.

  • Page 13: Function Code 04H

    Modbus 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.

  • Page 14: Function Code 06H

    1 CODE VALUE FF 00 perform function DF 6A CRC error code The commands that can be performed by the MM200 using function code 05 can also be initiated by using function code 16. Operation Code Description Reset Lockout Reset...

  • Page 15: Function Code 07H

    Table 2-6: MASTER/SLAVE PACKET FORMAT FOR FUNCTION CODE 07H MASTER TRANSMISSION BYTES EXAMPLE DESCRIPTION SLAVE ADDRESS message for slave 17 FUNCTION CODE read device status 4C 22 CRC error code SLAVE RESPONSE BYTES EXAMPLE DESCRIPTION SLAVE ADDRESS message from slave MM200 MOTOR MANAGEMENT SYSTEM – COMMUNICATIONS GUIDE...

  • Page 16: Function Code 08H

    Function Code 08H Modbus 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 2-7: MASTER/SLAVE PACKET FORMAT FOR FUNCTION CODE 08H...

  • Page 17: Error Responses

    CRC error code Error Responses When 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).

  • Page 18: Modbus Memory Map

    00C9 Pre Trip Current Unbalance 30203 00CA Pre Trip Ig 30205 00CC Reserved Reserved 30229 00E4 Reserved TRIP COUNTERS 30230 00E5 Total Number of Trips 30231 00E6 Reserved 30232 00E7 Overload Trips 2-10 MM200 MOTOR MANAGEMENT SYSTEM – COMMUNICATIONS GUIDE...
  • Page 19 Extended Status FC178 30307 0132 Thermal Cap Used 30308 0133 Time to Overload Trip 30310 0135 Drive Status FC143 30311 0136 Reserved 30312 0137 Command Status FC128 30313 0138 Reserved 30314 0139 Reserved MM200 MOTOR MANAGEMENT SYSTEM – COMMUNICATIONS GUIDE 2-11...
  • Page 20 User Map Value 123 30647 0286 User Map Value 124 30648 0287 User Map Value 125 30649 0288 Reserved Reserved 30656 028F Reserved SELF TEST 30657 0290 Internal Fault Cause FC188 30659 0292 Reserved 2-12 MM200 MOTOR MANAGEMENT SYSTEM – COMMUNICATIONS GUIDE...
  • Page 21 Command Data 5 65535 40136 0087 Command Data 6 65535 40137 0088 Command Data 7 65535 40138 0089 Command Data 8 65535 40139 008A Command Data 9 65535 40140 008B Command Data 10 65535 MM200 MOTOR MANAGEMENT SYSTEM – COMMUNICATIONS GUIDE 2-13...
  • Page 22 Motor Nameplate Voltage 40301 012C Reserved 40302 012D Reserved 40303 012E Transfer Time 40304 012F High Speed Start Block FC126 40305 0130 Reserved 40306 0131 Reserved 40307 0132 Pre-contactor Time 40308 0133 Reserved 2-14 MM200 MOTOR MANAGEMENT SYSTEM – COMMUNICATIONS GUIDE...
  • Page 23 Overload Reset Mode FC160 40715 02CA Reserved 40716 02CB Reserved 40717 02CC Reserved 40718 02CD Reserved MECHANICAL JAM 40719 02CE Mechanical Jam Level x FLA 40720 02CF Mechanical Jam Delay 40721 02D0 Reserved Reserved MM200 MOTOR MANAGEMENT SYSTEM – COMMUNICATIONS GUIDE 2-15...
  • Page 24 CBCT Ground Trip Level 40870 0365 Ground Trip Delay On Start 40871 0366 Ground Alarm Delay On Run 40872 0367 Ground Trip Delay On Run 40873 0368 Reserved 40874 0369 Reserved LOAD INCREASE 2-16 MM200 MOTOR MANAGEMENT SYSTEM – COMMUNICATIONS GUIDE...
  • Page 25 Hard Wired Permissive 57344 FC142 41386 0569 Field Start A 57344 FC142 41387 056A Field Start B 57344 FC142 41388 056B Field Stop 57344 FC142 41389 056C Contactor Status A 57344 FC142 MM200 MOTOR MANAGEMENT SYSTEM – COMMUNICATIONS GUIDE 2-17...
  • Page 26 MCC Stop Mode FC172 41584 062F MCC Stop Action FC174 41585 0630 Test Auto Mode FC175 41586 0631 Test Manual Mode FC175 41587 0632 External Stop Action FC174 41588 0633 Auto/Manual Key FC126 2-18 MM200 MOTOR MANAGEMENT SYSTEM – COMMUNICATIONS GUIDE...

  • Page 27: Format Codes

    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 MM200 MOTOR MANAGEMENT SYSTEM – COMMUNICATIONS GUIDE 2-19...
  • Page 28 RS 485 Baud Rate 9600 baud 19200 baud 38400 baud 57600 baud 115200 baud FC105 16 bits CT Type None 1 A Secondary 5 A Secondary Direct Connect FC107 16 bits Supply Frequency 2-20 MM200 MOTOR MANAGEMENT SYSTEM – COMMUNICATIONS GUIDE...
  • Page 29 0x8442 Comm Fail Trip 0x8482 Relay Not Configured 0x8742 Hard Wired Trip 0x8782 Field Trip 0x87C2 MCC Trip 0x8842 Emergency Stop 0x88C2 Open Control Trip 0x8902 Thermistor Trip 0x89C2 Self Test Trip MM200 MOTOR MANAGEMENT SYSTEM – COMMUNICATIONS GUIDE 2-21...
  • Page 30 Bit 15 USER1 Green Bit 16 USER2 Red Bit 17 USER2 Green Bit 20 50% Red Bit 21 50% Green Bit 22 80% Red Bit 23 80% Green Bit 24 100% Red 2-22 MM200 MOTOR MANAGEMENT SYSTEM – COMMUNICATIONS GUIDE...
  • Page 31 Wire Selection FC174 16 bits Source Stop Action Stop Trip FC175 16 bits Test Auto/Manual Mode Unaffected FC178 16 bits Motor Status Bit 0 Lockout Bit 1 Non-Lockout Trip Bit 4 Running MM200 MOTOR MANAGEMENT SYSTEM – COMMUNICATIONS GUIDE 2-23...
  • Page 32 Bit 31 MCC Trip FC184 32 bits Trip Status 2 Bit 1 Emergency Stop Bit 3 OpenControl Circuit Bit 4 Thermistor Trip FC191 32 bits Ctrl Element Status 1 Bit 0 Any Stop 2-24 MM200 MOTOR MANAGEMENT SYSTEM – COMMUNICATIONS GUIDE...

  • Page 33: Performing Commands Using Function Code 10H

    EXAMPLE DESCRIPTION SLAVE ADDRESS message from slave FUNCTION CODE store multiple setpoints DATA STARTING ADDRESS 00 80 setpoint address 00 NUMBER OF SETPOINTS 00 02 2 setpoints 42 B0 CRC error code MM200 MOTOR MANAGEMENT SYSTEM – COMMUNICATIONS GUIDE 2-25...

  • Page 34: Using The User Definable Memory Map

    CHAPTER 2: RS485 INTERFACE (MODBUS RTU) Using the User Definable Memory Map The MM200 contains a User Definable area in the memory map. This area allows re- mapping of the addresses of any Actual Values or Setpoints registers. The User Definable...

  • Page 35: Fieldbus Interface

    V– Pin 5 Pin 8, line A (negative TX/RX) Common drain Pin 3, line B (positive TX/RX) Pin 6 Table 3-2: DB9 signal pin applicability to MM200 DB9 pin (external device) MM200 pin Signal Description (shield) Shield or potential equalization...

  • Page 36: Profibus Power Supply Configuration

    No connection CNTR-N Repeater control 1.The MM200 can accept an external voltage level up to 24VDC on its V- and V+ terminals. Note that specifically for termination, the voltage must be reduced to 5V; refer to the Profibus Termination section below.

  • Page 37: Profibus Termination

    The MM200 relay supports mandatory parameterization. The relay keeps its user parameter data / setpoints in non-volatile memory and does not need device related parameterization during startup of the DP master. The EnerVista MM200 Setup software is the best tool for user parameterization of the MM200 device.

  • Page 38: Profibus Dp-Configuration

    The end nodes on a Profibus-DP network must be terminated to avoid reflections on the bus line. The Profibus bus address (MAC ID) of the MM200 slave, which has a range from 1 to 126, can be set via the EnerVista MM200 Setup software. Address 126 is used only for commissioning purposes and should not be used to exchange user data.
  • Page 39 When a size of input data smaller than the maximum is configured, the data read from the MM200 by the master will start at address 0 of the Profibus Input Data table (refer to section 4.4.4) and provide data in the order shown in that table, up to the size configured.

  • Page 40: Profibus Input Data

    Motor Running Hours Current metering Iavg Motor Load Current Unbalance Voltage metering Reserved Power Metering Reserved Reserved Last Trip Data Cause of Last Trip FC134 Pre Trip Ia Pre Trip Ib Pre Trip Ic MM200 MOTOR MANAGEMENT SYSTEM – COMMUNICATIONS GUIDE...

  • Page 41: Profibus Output Data

    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 MM200 looks for a change in the value to execute any command. Byte...
  • Page 42 Master Address Man Id Man Id Length Reserved Reserved Reserved Reserved Reserved Reserved Reserved Reserved Reserved Reserved Reserved Reserved Reserved Reserved Reserved Reserved Reserved Reserved Reserved Reserved Reserved Reserved Reserved Reserved Reserved Reserved MM200 MOTOR MANAGEMENT SYSTEM – COMMUNICATIONS GUIDE...
  • Page 43 Reserved Reserved Reserved Reserved Reserved Reserved Reserved Reserved Reserved Reserved Reserved Reserved Reserved Reserved Reserved Reserved Reserved Reserved Reserved Reserved Reserved Reserved Reserved Reserved Reserved Reserved Reserved Reserved Reserved Reserved Reserved Reserved Reserved MM200 MOTOR MANAGEMENT SYSTEM – COMMUNICATIONS GUIDE...
  • Page 44 "Comm Fail Trip" "Relay Not Configured" Reserved Reserved Reserved Reserved Reserved "Mechanical Jam Trip" "UnderCurrent Trip" "Unbalance Trip" Reserved Reserved Reserved Reserved Reserved "Any Trip" "Thermal O/L Trip" "Ground Fault Trip" "Acceleration Trip" 3-10 MM200 MOTOR MANAGEMENT SYSTEM – COMMUNICATIONS GUIDE...
  • Page 45 Reserved Reserved Reserved Reserved Reserved Reserved Reserved Reserved Reserved Reserved Reserved Reserved Reserved Reserved Reserved Reserved Reserved Reserved Reserved Reserved Reserved Reserved Reserved Reserved Reserved Reserved Reserved Reserved Reserved Reserved Reserved Reserved MM200 MOTOR MANAGEMENT SYSTEM – COMMUNICATIONS GUIDE 3-11...
  • Page 46 "External Start A Alarm" "External Start B Alarm" Reserved Reserved Reserved Reserved Reserved Reserved Reserved Reserved Reserved Reserved Reserved Reserved Reserved Reserved Reserved Reserved Reserved "UnderCurrent Alarm" "Unbalance Alarm" Reserved Reserved Reserved 3-12 MM200 MOTOR MANAGEMENT SYSTEM – COMMUNICATIONS GUIDE...
  • Page 47 Reserved Reserved Reserved Reserved Reserved Reserved Reserved Reserved Reserved Reserved Reserved Reserved Reserved Reserved Reserved Reserved Reserved Reserved Reserved Reserved Reserved Reserved Reserved Reserved Reserved Reserved Reserved Reserved Reserved Reserved Reserved Reserved MM200 MOTOR MANAGEMENT SYSTEM – COMMUNICATIONS GUIDE 3-13...
  • Page 48 Reserved Reserved Reserved Reserved Reserved Reserved Reserved Reserved Reserved Reserved Reserved Reserved Reserved Reserved Reserved Reserved Reserved Reserved "HW Stop" "Field Stop" "MCC Stop" Reserved Reserved Reserved Reserved Reserved Reserved Reserved Reserved 3-14 MM200 MOTOR MANAGEMENT SYSTEM – COMMUNICATIONS GUIDE...
  • Page 49 The following diagram shows an example of the extended diagnostic data sent to the Profibus master by the MM200. 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"...

  • Page 50: Profibus Dpv1

    CHAPTER 3: FIELDBUS INTERFACE Figure 3-8: Profibus - no extended diagnostic data Profibus DPV1 The MM200 relay also supports DPV1 extensions. The device supports Class 1 and Class 2 acyclic reads and writes as well as DPV1 Diagnostics. Profibus DPV1-Acyclic read/write data The motor status data can be read acyclically by retrieving the byte lengths indicated below from the relevant Object, Slot, Index.

  • Page 51: Extended Profibus Dpv1 Functionality

    The MM200 memory is mapped in 16 bits variables, thus, only communication data exchange with even data quantities is accepted. The security functionality implemented on MM200 is strictly applicable. Parameter write access is controlled by passwords as defined in Security Section of the MM200 Instruction Manual. Acyclic Read...

  • Page 52: Profibus Dpv1-Diagnostics

    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 MM200 is controlling and monitoring. Messages are categorized as Diagnostic Alarms as these provide detailed MM200 diagnostic information.
  • Page 53 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 MM200 MOTOR MANAGEMENT SYSTEM – COMMUNICATIONS GUIDE 3-19...
  • Page 54 Alarm Specifier 9 Alarm Specifier Reserved Reserved Reserved Reserved Reserved Reserved Reserved Reserved Reserved Reserved Reserved Reserved Reserved Reserved Reserved Reserved Reserved Reserved Reserved Reserved Reserved Reserved Reserved Reserved Reserved Reserved Reserved Reserved Reserved 3-20 MM200 MOTOR MANAGEMENT SYSTEM – COMMUNICATIONS GUIDE...
  • Page 55 "Aux U/V Trip" "Emergency Stop" Reserved "OpenControl Circuit" "Thermistor Trip" Reserved Reserved "Self Test Trip" Reserved Reserved Reserved Reserved Reserved "Hard Wired Trip" "Field Trip" "MCC Trip" "RTD 6 Trip" "Comm Fail Trip" MM200 MOTOR MANAGEMENT SYSTEM – COMMUNICATIONS GUIDE 3-21...
  • Page 56 "Ground Fault Trip" "Acceleration Trip" Reserved "UnderPower Trip" Reserved Reserved Reserved Reserved Reserved Reserved Reserved Reserved Reserved Reserved Reserved Reserved Reserved Reserved Reserved Reserved Reserved Reserved Reserved Reserved Reserved Reserved Reserved Reserved Reserved 3-22 MM200 MOTOR MANAGEMENT SYSTEM – COMMUNICATIONS GUIDE...
  • Page 57 "Contactor Inspect Alarm" "Max Stopped Alarm" "Aux U/V Alarm" "External Stop Alarm" Reserved "Open Ctrl Cct Alarm" "Thermistor Alarm" Reserved "External Start A Alarm" "External Start B Alarm" Reserved Reserved Reserved Reserved MM200 MOTOR MANAGEMENT SYSTEM – COMMUNICATIONS GUIDE 3-23...
  • Page 58 "Any Alarm" "Thermal Level Alarm" "Ground Fault Alarm" "Acceleration Alarm" Reserved "UnderPower Alarm" Reserved Reserved Reserved Reserved Reserved Reserved Reserved Reserved Reserved Reserved Reserved Reserved Reserved Reserved Reserved Reserved Reserved Reserved Reserved 3-24 MM200 MOTOR MANAGEMENT SYSTEM – COMMUNICATIONS GUIDE...
  • Page 59 Reserved Reserved Reserved Reserved Reserved Reserved Reserved Reserved Reserved Reserved Reserved Reserved Reserved Reserved Reserved Reserved Reserved Reserved Reserved Reserved Reserved Reserved Reserved Reserved Reserved Reserved Reserved Reserved Reserved Reserved Reserved Reserved MM200 MOTOR MANAGEMENT SYSTEM – COMMUNICATIONS GUIDE 3-25...

  • Page 60: 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. 3-26 MM200 MOTOR MANAGEMENT SYSTEM – COMMUNICATIONS GUIDE...

  • Page 61: Devicenet Power Supply Configuration

    DeviceNet supports external power only. NOTE: Figure 3-9: Comms board power supply configuration NOTE 1 2 3 4 5 6 7 8 EXTERNAL POWER SUPPLY = switch position 888846A2.CDR MM200 MOTOR MANAGEMENT SYSTEM – COMMUNICATIONS GUIDE 3-27...

  • Page 62: Devicenet Setup And Configuration (Typical)

    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 3-28 MM200 MOTOR MANAGEMENT SYSTEM – COMMUNICATIONS GUIDE...
  • Page 63 10-pin linear plug into the connector. Connect the other end of the DeviceNet cable into this connector. Locate the DeviceNet connector on the MM200 (see top left-hand corner of the diagram below) and connect it to the scanner using the DeviceNet Cable.
  • Page 64 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: Powering up the network 3-30 MM200 MOTOR MANAGEMENT SYSTEM – COMMUNICATIONS GUIDE...
  • Page 65 CHAPTER 3: FIELDBUS INTERFACE DEVICENET PROTOCOL Before switching ON the network power make sure that the MACID of MM200 is set to something other than 63. Switch on the power supply to the chassis that will power up the device.
  • Page 66 DEVICENET PROTOCOL CHAPTER 3: FIELDBUS INTERFACE Select DeviceNet Drivers from the above pull-down menu and Click Add/New. The following menu will appear: Select the Allen-Bradley™ 1770-KFD driver. The Driver Configuration dialog appears: 3-32 MM200 MOTOR MANAGEMENT SYSTEM – COMMUNICATIONS GUIDE...
  • Page 67 This dialog will only appear if there is at least one active node on the DeviceNet network. NOTE: So ensure that the network power is on and that the MM200 relay and the scanner are on the DeviceNet network. NOTE Select the default driver name, 1770-KFD-1, and click OK.
  • Page 68 CHAPTER 3: FIELDBUS INTERFACE From the File menu, choose New. Highlight DeviceNet Configuration and click OK. Next step is to register the EDS file for the MM200. Select the EDS Wizard from the Tools menu as shown below: 3-34 MM200 MOTOR MANAGEMENT SYSTEM – COMMUNICATIONS GUIDE...
  • Page 69 CHAPTER 3: FIELDBUS INTERFACE DEVICENET PROTOCOL Press Next Click on Register an EDS file: MM200 MOTOR MANAGEMENT SYSTEM – COMMUNICATIONS GUIDE 3-35...
  • Page 70 DEVICENET PROTOCOL CHAPTER 3: FIELDBUS INTERFACE Browse and select the EDS file for MM200. 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 71 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. MM200 MOTOR MANAGEMENT SYSTEM – COMMUNICATIONS GUIDE 3-37...
  • Page 72 CHAPTER 3: FIELDBUS INTERFACE 13. When the software has finished browsing, the network displayed on your screen should appear similar to the one shown below. MM200, Scanner and the 1770 KFD modules will appear with MACIDs just below each device.
  • Page 73 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: MM200 MOTOR MANAGEMENT SYSTEM – COMMUNICATIONS GUIDE 3-39...
  • Page 74 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: 3-40 MM200 MOTOR MANAGEMENT SYSTEM – COMMUNICATIONS GUIDE...
  • Page 75 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 MM200 relay will be seen in the Available Devices list. Verify that the Automap on Add box is NOT checked.
  • Page 76 DEVICENET PROTOCOL CHAPTER 3: FIELDBUS INTERFACE Click the double arrow (>>)to move the MM200 from the Available Devices list to the Scanlist. Select Major Revision as the part of the electronic key for MM200. Double-click MM200 in the Scanlist. The Edit I/O Parameters dialog (shown below) appears for the MM200.

  • Page 77: Devicenet Setup And Configuration (Adr)

    In the MM200, only the contents of the A1 object are supported by ADR. Enabling ADR Before proceeding to the next step ensure that the MM200 relay and the network are NOTE: configured as desired. These configurations will be then stored in the scanner for the ADR feature.
  • Page 78 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. 3-44 MM200 MOTOR MANAGEMENT SYSTEM – COMMUNICATIONS GUIDE...
  • Page 79 So always remember to UPLOAD the MM200 configuration into the RSNetWorx and SAVE the file before enabling ADR. The MM200 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 MM200 is the same as that of the scanner.

  • Page 80: Devicenet Communications

    DEVICENET PROTOCOL CHAPTER 3: 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 MM200 relays in the DeviceNet network. DeviceNet Communications The device profile is an extension of the Communications Adapter Device Profile (0xC0). It is a group 2 only server.

  • Page 81: Identity Object (Class Code 01H)

    Drive Available is true In the event that there is a communication fault, and a pre-fault polled output command caused the MM200 to start a motor, the motor will continue to run even after the communication fault. Figure 3-10: DeviceNet polled I/O data...

  • Page 82: Devicenet Object (Class Code 03H)

    - MAC ID Consumed connection ID UINT 10xxxxxx100, xxxxxx - MAC ID Initial comm. characteristics USINT 0x21 Produced connection size UINT 0x00EF Consumed connection size UINT 0x00EF Get/Set Expected package rate UINT 0x0000 3-48 MM200 MOTOR MANAGEMENT SYSTEM – COMMUNICATIONS GUIDE...

  • Page 83: Devicenet Motor Data - Explicit Object (Class Code A0H)

    Table 3-25: Motor Data Object, Class Code A0h, Instance 01h, Attributes, Get Access: ATTRIBUTE NAME/DESCRIPTION SIZE IN FORMAT BYTES Motor Data See below Digital Data See below Summary of Motor Data See below Reserved Motor status FC129 (low byte only) MM200 MOTOR MANAGEMENT SYSTEM – COMMUNICATIONS GUIDE 3-49...
  • Page 84 Reserved Contact Input Status BIT per input Contact Output Status BIT per output Reserved Reserved DATA FORMAT, CURRENT METERING ITEM DESCRIPTION SIZE IN BYTES FORMAT Average phase current (A) Ground current (A) 3-50 MM200 MOTOR MANAGEMENT SYSTEM – COMMUNICATIONS GUIDE...

  • Page 85: Devicenet Motor Data - Explicit Object (Class Code A1H)

    10001 10001 Motor Volts Nameplate Voltage Transfer Time Seconds High Speed None FC126 Start Block Pre-contactor Seconds Time Comms OK None FC131 Evaluation Overload Pickup Level Cool Time Mins 1000 Constant Running MM200 MOTOR MANAGEMENT SYSTEM – COMMUNICATIONS GUIDE 3-51...
  • Page 86 None FC142 0xE000 Remote Reset None FC142 0xE000 None FC142 0xE000 Permissive Hard Wired None FC142 0xE000 Start A Hard Wired None FC142 0xE000 Start B Hard Wired None FC142 0xE000 Stop 3-52 MM200 MOTOR MANAGEMENT SYSTEM – COMMUNICATIONS GUIDE...

  • Page 87: Devicenet Motor Analog Data - Explicit Object (Class Code A2H)

    DeviceNet Motor Analog Data - Explicit Object (Class Code A2H) Table 3-28: Explicit Motor Analog Data Object, Class Code A2h, Services: CODE SERVICES AVAILABLE TO THIS OBJECT NAME DESCRIPTION 0x0E Get_Attribute_Single Returns the contents of the given attribute MM200 MOTOR MANAGEMENT SYSTEM – COMMUNICATIONS GUIDE 3-53...
  • Page 88 Start Timer 4 Secs Start Timer 5 Secs Restart Block Secs Lockout Motor Status None FC129 Motor Thermal Capacity Used Contact Input 32-1 None FC167 Status Contact Output None FC167 32-1 Status 3-54 MM200 MOTOR MANAGEMENT SYSTEM – COMMUNICATIONS GUIDE...

  • Page 89: Devicenet - Explicit Motor Analog Data Object, Class Code B0H, Services

    Start block status data All actual values Table 3-32: Data Formats, Explicit Motor Analog Data Object ATTRIBUTE ITEM DESCRIPTION SIZE IN FORMAT BYTES Currents Iavg Igrd Motor load Motor Load I Unb Reserved MM200 MOTOR MANAGEMENT SYSTEM – COMMUNICATIONS GUIDE 3-55...
  • Page 90 Pre Trip Motor Load Pre Trip Current Unbalance Reserved Reserved Last pre-trip frequency Pre Trip System Frequency Reserved Trip diagnostic data Trip Status 3 FC185 Trip Status 2 FC184 Trip Status 1 FC183 3-56 MM200 MOTOR MANAGEMENT SYSTEM – COMMUNICATIONS GUIDE...

  • Page 91: Devicenet - Explicit Motor Object, Class Code B1H

    Table 3-34: Explicit Motor Control Object, Class Code B1h, Attributes: ATTRIBUTE ACCESS DESCRIPTION DATA TYPE VALUE Control Command BYTE See below Table 3-35: Explicit Motor Control Data Format VALUE DESCRIPTION Reset Lockout Reset Stop Start A Start B MM200 MOTOR MANAGEMENT SYSTEM – COMMUNICATIONS GUIDE 3-57...
  • Page 92 DEVICENET PROTOCOL CHAPTER 3: FIELDBUS INTERFACE 3-58 MM200 MOTOR MANAGEMENT SYSTEM – COMMUNICATIONS GUIDE...

  • Page 93: Revision History

    Table A–3: Major Updates for MM300 Comm Guide-A4 Section Number CHANGES Manual revision number from A3 to A4 Added Profibus DP Termination section Added DB9 signal pin applicability table to Profibus DP section MM200 MOTOR MANAGEMENT SYSTEM – COMMUNICATIONS GUIDE...

  • Page 94: Warranty

    For products shipped as of 1 October 2013, GE warrants most of its GE manufactured products for 10 years. For warranty details including any limitations and disclaimers, see our Terms and Conditions at https://www.gegridsolutions.com/multilin/warranty.htm For products shipped before 1 October 2013, the standard 24-month warranty applies. MM200 MOTOR MANAGEMENT SYSTEM – COMMUNICATIONS GUIDE...

Table of Contents