Home

MVI56E-MNETCR User Manual

1. 62 2 3 Using ClPconnect to Connect to the Module 63 2 3 1 Example 1 Local Rack Application 65 2 3 2 Example 2 Remote Rack 68 3 Ladder Logic 71 3 1 Module Data Object MNETCRMODULEDEF sss 72 3 1 1 User Data Object 00 04 4 00 10000 0000 nnne nnns 73 3 1 2 Command Control Data Object 74 3 1 3 Status Object 0 0 04 224 0 0000 ener nennen enne 75 3 1 4 Backplane Control Object MNETCRUTIL eseseeseseeeneeneneneennenn 77 ProSoft Technology Inc June 14 2011 Page 5 of 159 Contents User Manual MVI56E MNETCR 4 ControlLogix Platform Modbus TCP IP Multi Client Enhanced Communications Module for Remote Chassis 4 Diagnostics and Troubleshooting 79 4 1 LED Status 80 4 1 1 Scrolling LED Status Indicators sssssssseeseeeeeneeneenne 80 4 1 2 Ethernet LED Indicators nere tenet ee peri 81 4 1 3 Non Scrolling LED Status 81 4 1 4 TroudblesHOoOLlllg e head tte uius 82 4 1 5 7 gt 83 4 2 Using the Diagnostics Menu in ProSoft Configuration Builder 84 4 2 1 The Diagnostic
2. Ethernet g 1756 RemoteENBT 6 9 1756 Backplane 1756 A7 8 1 1756 MODULE MNETCR J 8 6 1756 ENBT A RemoteENET Slot BJ 1756 ENBT A Local 5 Expand the TASKS folder and then expand the MAINTASK folder 6 MAINPROGRAM folder double click to open the MAINROUTINE ladder 7 Select an empty rung in the routine and then click the right mouse button to open a shortcut menu On the shortcut menu choose IMPORT RUNG 6 RSLogix 5000 ControlLogix in MVIBGEMNETCR v16 ACD 1756 L63 MainProgram MainRoutine Ele Edit View Search Logic Communications Tools Window Help Biela S HSE 55 memorem gt 4818 8 te edel 0 ERUN A Pan eon No Forces mr 1 4 lolol 7 ny 8 Favorites 56207 K Tmertowter Ki E Controler ControLogx sss es e Controller Tags Controller Fat Herder Add On for Power Up Handler MVI56 MNETCR and Tasks MVI56E MNETCR 68 MainTask Modules m ec m 6 Eb MainRoutine Add On for MVI56 MNETCR and MVI56E MNETCR Unscheduled Programs AOIS6MNETCR AOIS6MNETCR 9 08 Motion Groups Connection Input RemoteENBT_Slot6 1 1 Data E Add On Instructions Connection Output RemoteENBT_Slot6 1 0 Data ec MNETCR MNETCR rends 51 9 1 0 Configuration S 1756 Backplane 1756 A4 CutRung 0 1756463 ControlLogix
3. Add On for MVI56 MNETCR and MVI56E MNETCR Modules r AOI56MNETCR Add On for MVI56 MNETCR MVI56E MNETCR AOI56MNETCR 56 Connection Input RemoteENBT 8 Connection Output RemoteENBT Slot6 1 O Data MNETCR MNETCR MVI56E MNETCR Optional Add On Ethernet Clock AOI56EMNETCR_OPTIONAL MVI56E MNETCR Optional Add On Ethernet Clock AOI56EMNETCR OPTIONAL MVIS6MNETCREthernet MVIS6MNETCRClock ReadEthernetMSG WriteEthernetMSG ReadClockMSG MVIS6EMNETCRETHERNET MVISGEMNETCRCLOCK WRITEETHERNETMSG WriteClockMSG AOI56EMNETCR_OPTIONAL READETHERNETMSG READCLOCKMSG WRITECLOCKMSG ProSoft Technology Inc June 14 2011 Page 135 of 159 Reference User Manual MVI56E MNETCR 4 ControlLogix Platform Modbus TCP IP Multi Client Enhanced Communications Module for Remote Chassis You will notice that new tags have been imported four MESSAGE tags MVIS6MNETCCLOCK and MVIS6MNETCETHERNET tags amp RSLogix 5000 ControlLogix MVIBGEMNETCR v16 ACD 1756 L63 Controller Tags ControlLogix controller Elle Edit View Search Logic Communications Tools Window Help gt uNeTRUTILntOutputdata 95185 ES Path nne sp per HB D alsia miel Offline 1 m RUN No Forces be No Edits Fr vo 57 EI Controller ControlLogix 18 Controller Tags C
4. 4 120440 nennen en 117 5 5 Modbus Protocol Specification esses 118 5 5 1 Read Coil Status Function Code 01 2 40400000 000 118 5 5 2 Read Input Status Function Code 02 120 5 5 3 Read Holding Registers Function Code 03 121 5 5 4 Read Input Registers Function Code 00 122 5 5 5 Force Single Coil Function Code 05 222 0 0000 0 123 5 5 6 Preset Single Register Function Code 06 124 5 5 7 Diagnostics Function Code 08 2 202040 0 000 125 5 5 8 Force Multiple Coils Function Code 15 2 0 000 0 127 5 5 9 Preset Multiple Registers Function Code 16 128 5 5 10 Modbus Exception Responses essen 129 5 6 Using the Optional Add On Instruction Rung 132 5 6 1 Before You Pre eoi bruts 132 5 6 2 MI M M 132 5 6 3 Installing the Rung Import with Utility Add On 5008 133 5 6 4 Reading the Ethernet Settings from the 138 5 6 5 Writing the Ethernet Settings to the 139 5
5. CIPconnect Path Editor ef Connect PATH EDITOR Destination Module Source Module Source Module Node Address Address Slot Number No Source Module Destination Module vseener 1921600100 _ t 192 168 0 100 p 1 8 0 Add Rack __ Delete Rack Construct CIP Path C Pconnect Path Editor allows you to define the path between the PC and the module The first connection from the PC is always a 1756 ENBT Ethernet IP module Each row corresponds to a physical rack in the CIP path MVIS6E MNETCR module is located in the same rack as the first 1756 ENBT module select RACK No 1 and configure the associated parameters MVIS6E MNETCR is available in a remote rack accessible through ControlNet or Ethernet IP include all racks by using the ADD RACK button Parameter Description Source Module Source module type This field is automatically selected depending on the destination module of the last rack 1756 CNB or 1756 ENBT Source Module IP Address IP address of the source module only applicable for 1756 ENBT Source Module Node Address Node address of the source module only applicable for 1756 CNB Destination Module Select the destination module associated to the source module in the rack The connection between the source and destination modules is performed through the backplane Destination Module
6. 1d Pe edd OLOGI Where Automation Connects inRAx MVI56E MNETCR ControlLogix Platform Modbus TCP IP Multi Client Enhanced Communications Module for Remote Chassis June 14 2011 USER MANUAL Your Feedback Please We always want you to feel that you made the right decision to use our products If you have suggestions comments compliments or complaints about our products documentation or support please write or call us How to Contact Us ProSoft Technology 5201 Truxtun Ave 3rd Floor Bakersfield CA 93309 1 661 716 5100 1 661 716 5101 Fax www prosoft technology com support prosoft technology com Copyright 2011 ProSoft Technology Inc all rights reserved MVI56E MNETCR User Manual June 14 2011 ProSoft Technology ProLinx 9 inRAx ProTalk 9 and RadioLinx are Registered Trademarks of ProSoft Technology Inc All other brand or product names are or may be trademarks of and are used to identify products and services of their respective owners ProSoft Technology Product Documentation In an effort to conserve paper ProSoft Technology no longer includes printed manuals with our product shipments User Manuals Datasheets Sample Ladder Files and Configuration Files are provided on the enclosed CD ROM and are available at no charge from our web site www prosoft technology com Battery Life Advisory Note Modules manufactured after April 1 2011 do not contain a b
7. B 1 1755 0 rrr Module Analog Communications Controllers Digital Drives Motion Other 1756 MODULE Specialty Generic 1756 Module Description Allen Bradley End Add Favorite By Category By Vendor Favorites OK Cancel Help 3 Fill the module properties as follows Parameter Value Name Enter a module identification string Example MNETCR 2 Description Enter a description for the module Example Modbus TCP IP Multi Client Enhanced Communications Module for Remote Chassis Comm Format Select DATA INT Slot Enter the slot number in the rack where the MVI56E MNETCR module is located Input Assembly Instance 1 Input Size 42 Output Assembly Instance 2 Output Size 42 Configuration Assembly Instance 4 Configuration Size 0 ProSoft Technology Inc June 14 2011 Page 37 of 159 Start Here MVI56E MNETCR 4 ControlLogix Platform User Manual Modbus TCP IP Multi Client Enhanced Communications Module for Remote Chassis 4 Click OK to confirm The new module is now visible gt Controller ControlLogix Controller Tags Controller Fault Handler Z3 Power Up Handler amp Tasks MainTask Cg MainProgram Unscheduled Programs Motion Groups Add On Instructions Data Types Trends 6 1 0 Configuration 1756 Backplane 1756 A4 fa 0 1756463 ControlLogix 3 1756 ENBT A Local
8. For Coil address 00115 specify 114 00115 00001 114 For register read or write commands FC 3 6 or 16 range for 40001 specify a value of 0 40001 40001 0 For 01101 11101 31101 or 41101 specify a value of 1100 01101 00001 1100 11101 10001 1100 31101 30001 1100 41101 40001 1100 Note If the documentation for a particular Modbus Server device lists data addresses in hexadecimal base16 notation you will need to convert the hexadecimal value to a decimal value to enter in this parameter In such cases it is not usually necessary to subtract 1 from the converted decimal number as this addressing scheme typically uses the exact offset address expressed as a hexadecimal number Comment 0 to 35 alphanumeric characters ProSoft Technology Inc Page 59 of 159 June 14 2011 Configuring the MVI56E MNETCR Module MVI56E MNETCR ControlLogix Platform User Manual Modbus TCP IP Multi Client Enhanced Communications Module for Remote Chassis 2 1 6 Static ARP Table The Static ARP Table defines a list of static IP addresses that the module will use when an ARP Address Resolution Protocol is required The module will accept up to 40 static IP MAC address data sets Use the Static ARP table to reduce the amount of network traffic by specifying IP addresses and their associated MAC hardware addresses that the MVI56E MNETCR module will be communicating with regularly Important If th
9. Latin America Oficina Regional Tel 1 281 2989109 E Mail latinam prosoft technology com Languages spoken include Spanish English Latin America location in Puebla Mexico Tel 52 222 3 99 6565 E mail soporte prosoft technology com Languages spoken include Spanish Brasil location in Sao Paulo Tel 55 76 E mail brasil prosoft technology com Languages spoken include Portuguese English Page 148 of 159 ProSoft Technology Inc June 14 2011 MVI56E MNETCR 4 ControlLogix Platform Support Service amp Warranty Modbus TCP IP Multi Client Enhanced Communications Module for Remote Chassis User Manual 6 1 Return Material Authorization RMA Policies and Conditions The following Return Material Authorization RMA Policies and Conditions collectively RMA Policies apply to any returned product These RMA Policies are subject to change by ProSoft Technology Inc without notice For warranty information see Limited Warranty page 151 In the event of any inconsistency between the RMA Policies and the Warranty the Warranty shall govern 6 1 1 Returning Any Product a In order to return a Product for repair exchange or otherwise the Customer must obtain a Return Material Authorization RMA number from ProSoft Technology and comply with ProSoft Technology shipping instructions b In the event that the Customer experiences a problem with the Product for any reason Customer should
10. ProSoft Technology Inc June 14 2011 Page 77 of 159 Ladder Logic MVI56E MNETCR ControlLogix Platform User Manual Modbus TCP IP Multi Client Enhanced Communications Module for Remote Chassis Page 78 of 159 ProSoft Technology Inc June 14 2011 MVI56E MNETCR 4 ControlLogix Platform Diagnostics and Troubleshooting Modbus TCP IP Multi Client Enhanced Communications Module for Remote Chassis User Manual 4 Diagnostics and Troubleshooting In This Chapter e LED Status Indicaltots e aee 80 Using the Diagnostics Menu in ProSoft Configuration Builder 84 Reading Status Data from the Module 91 The module provides information on diagnostics and troubleshooting in the following forms LED status indicators on the front of the module provide information on the module s status Status data contained in the module can be viewed in ProSoft Configuration Builder through the Ethernet port Status data values are transferred from the module to the processor ProSoft Technology Inc Page 79 of 159 June 14 2011 Diagnostics and Troubleshooting MVI56E MNETCR ControlLogix Platform User Manual Modbus TCP IP Multi Client Enhanced Communications Module for Remote Chassis 4 1 LED Status Indicators 4 1 1 Scrolling LED Status Indicators The scrolling LED display indicates the module s operating status as follows Initialization Mes
11. 1 amp 1 0 Configuration 11756 Backplane 1756 A 0 1756463 My_Cor FJ New Module 3 This action opens the SELECT MODULE dialog box Select Module Module Analog Communications Controllers Digital Drives Motion Other 1756 MODULE Generic 1756 Module Allen Bradley Specialty Find Add Favorite By Category Favorites OK Cancel Help 4 Select the 1756 MODULE GENERIC 1756 MODULE from the list and click OK 5 Set the Module Properties values as follows Parameter Value Name Enter a module identification string The recommended value is MNETCR Description Enter a description for the module Example Modbus TCP IP Multi Client Enhanced Communications Module for Remote Chassis Comm Format Select DATA INT Very Important Slot Enter the slot number in the rack where the MVIS6E MNETCR module is to be installed Input Assembly Instance 1 Input Size 42 Output Assembly Instance 2 Output Size 42 Configuration Assembly Instance 4 Configuration Size 0 ProSoft Technology Inc Page 31 of 159 June 14 2011 Start Here MVI56E MNETCR 4 ControlLogix Platform User Manual Modbus TCP IP Multi Client Enhanced Communications Module for Remote Chassis 6 Onthe CONNECTION tab set the RPI value for your project Five milliseconds is usually a good starting value Click OK to confirm Wil Module Properties Local 2 1756 MODULE 1 1 General Conne
12. 1 6 1 Installing ProSoft Configuration Builder To install ProSoft Confiquration Builder from the CD ROM 1 Insert the ProSoft Solutions CD ROM into the CD drive of your PC Wait for the startup screen to appear s 29 TECHNOLOGY Enjoy easy connectivity with ProSoft Technology 2 Powerful diagnostics features for you Install ProSoft to gather real time module status p Discovery Service and analyze the data stream moving through the module Use PCB to configure some modules Install ProSoft Configuration Builder Consult the product documentation to determine the correct configuration method for your product Y Documentation 2 Onthe startup screen click INSTALL PROSOFT CONFIGURATION BUILDER This action starts the installation wizard for ProSoft Configuration Builder 3 Click NEXT on each page of the installation wizard Click FINISH on the last page of the wizard Page 16 of 159 ProSoft Technology Inc June 14 2011 MVI56E MNETCR ControlLogix Platform Start Here Modbus TCP IP Multi Client Enhanced Communications Module for Remote Chassis User Manual 17 Connecting Your PC to the Module With the module securely mounted connect one end of the Ethernet cable to the Config E1 Port and the other end to an Ethernet hub or switch accessible from the same network as your PC You can also connect directly from the Ethernet Port on your PC to the Config E1 Port on the
13. 2 6 MVI56E MNETCR Page 68 of 159 ProSoft Technology Inc June 14 2011 MVI56E MNETCR 4 ControlLogix Platform Configuring the MVI56E MNETCR Module Modbus TCP IP Multi Client Enhanced Communications Module for Remote Chassis User Manual 1 Inthe Download dialog box click CIP PATH EDIT Download files from PC to module STEP 1 Select Communication Path Select Connection Type 1756 ENBT 7 Ethernet CIPconnect t 192 168 0 100 p 1 s 0 CIP Path Edit STEP 2 Transfer File s DOWNLOAD Test Connection Cancel 2 Configure the path as shown in the following illustration and click CONSTRUCT CIP PATH to build the path in text format CIPconnect Path Editor Connect PATH EDITOR Destination Module Destination Module Slot Number No Source Module 1756 ENBT 1921680700 1756 CNB BE 0 MVI56 Module Source Module IP Source Module Node Add t 192 168 0 100 p 1 s 2 p 2 c 0 p 1 s 6 Add Rack Delete Rack Construct Path Click OK to close the C Pconnect Path Editor and return to the Download dialog box ProSoft Technology Inc Page 69 of 159 June 14 2011 Configuring the MVIBG6E MNETCR Module MVI56E MNETCR 4 ControlLogix Platform User Manual Modbus TCP IP Multi Client Enhanced Communications Module for Remote Chassis 3 Check the new path the Download dialog box Download files from PC to module
14. Client Status Request Blocks 3000 to 3029 Offset Description Length 0 3000 to 3029 last digits indicate which client to consider 1 1 to 41 Spare 40 Client Status Response Offset Description Length 0 Write Block ID 1 1 3000 to 3029 number requested 1 2 to 11 Client status data 10 12 to 27 Command error list data for client 16 28 to 40 Reserved 13 41 3000 to 3029 1 Client Status Data Word Offset Client Status 3 Total number of command list requests 4 Total number of command list responses 5 Total number of command list errors 6 Total number of requests of slave 7 Total number of responses 8 Total number of errors sent 9 Total number of errors received 10 Configuration Error Word 11 Current Error 12 Last Error ProSoft Technology Inc Page 105 of 159 June 14 2011 Reference MVI56E MNETCR 4 ControlLogix Platform User Manual Modbus TCP IP Multi Client Enhanced Communications Module for Remote Chassis Command Control Blocks 5001 to 5016 Command control blocks place commands in the command list into the command queue The client has a command queue of up to 16 commands The module services commands in the queue before the user defined command list This gives high priority to commands in the queue Commands placed in the queue through this mechanism must be defined in the module s command list Under normal command list execution the module
15. June 14 2011 MVI56E MNETCR ControlLogix Platform Modbus TCP IP Multi Client Enhanced Communications Module for Remote Chassis Reference User Manual 5 6 5 Writing the Ethernet Settings to the Module Expand the MVIS6EMNETCRETHERNET controller tag Set the new Ethernet configuration in MVIBGEMNETCRETHERNET CONFIG Move a value of 1 to MVIBGEMNETCRETHERNET WRITE MVIBBEMNETCRETHERNET MVIBBEMNETCRETHERNET Read MVISBEMNETCRETHERNET write MVIBBEMNETCRETHERNET Config MVIBBEMNETCRETHERNET Config IP MVIBBEMNETCRETHERNET Config IP 0 MVIBEEMNETCRETHERNET Config IP 1 MVIBEEMNETCRETHERNET Config IP 2 MVIBEEMNETCRETHERNET Config MVIBGEMNETCRETHERNET Config Netmask MVIBBEMNETCRETHERNET Config Netmask 0 MVIBEEMNETCRETHERNET Config Netmask 1 MVIBBEMNETCRETHERNET Config Netmask 2 MVIBBEMNETCRETHERNET Config Netmask 3 MVIBSEMNETCRETHERNET Config Gateway MVIBBEMNETCRETHERNET Config Gateway 0 MVIBBEMNETCRETHERNET Config Gateway 1 MVIBBEMNETCRETHERNET Config Gateway 2 MVIBBEMNETCRETHERNET Config Gateway 3 8 After the message is executed the MVIBGEMNETCRETHERNET WhITE bit resets to O MVIBBEMNETCRETHERNET MVIBGEMNETCRETHERNET Read MVIBBEMNE TCRETHERNET Write MVI56EMNETCRETHERNET Config MVI56EMNETCRETHERNET Config IP MVIBBEMNETCRETHERNET Confia IP 0 MVIBBEMNETCRETHERNET Config IP 1 MVIB
16. Note The standard connector view shown is color coded for a straight through cable Crossover cable Straight through cable RJ 45 PIN RJ 45 PIN RJ 45 PIN RJ 45 PIN 1 3 Tx 1 1 2 Rx 6 2 Rx 2 3 Tx 1 3 TX 3 Rx 6 2 Rx 6 6 Rx 10 BaseT ui Nc pin 5145 Page 116 of 159 ProSoft Technology Inc June 14 2011 MVI56E MNETCR ControlLogix Platform Reference Modbus TCP IP Multi Client Enhanced Communications Module for Remote Chassis User Manual 5 4 2 Ethernet Performance Ethernet performance on the MVI56E MNETCR module can affect the operation of the MNETCR application ports in the following ways Accessing the web interface refreshing the page downloading files and so on may affect MNETCR performance High Ethernet traffic may impact MNETCR performance consider page 63 page 22 for these applications and disconnect the module Ethernet port from the network ProSoft Technology Inc Page 117 of 159 June 14 2011 Reference User Manual 5 5 Modbus Protocol Specification The following pages give additional reference information regarding the Modbus protocol commands supported by the MVIBbGE MNETCR 5 5 1 Read Coil Status Function Code 01 Query This function allows the user to obtain the ON OFF status of logic coils used to control discrete outputs from the addressed Server only Broadca
17. Special block handling Status data receipt Additionally a power up handler may be needed to initialize the module s database and may clear some processor fault conditions The sample Import Rung with Add On Instruction is extensively commented to provide information on the purpose and function of each user defined data type and controller tag For most applications the Import Rung with Add On Instruction will work without modification ProSoft Technology Inc Page 71 of 159 June 14 2011 Ladder Logic MVI56E MNETCR 4 ControlLogix Platform User Manual Modbus TCP IP Multi Client Enhanced Communications Module for Remote Chassis 31 Module Data Object MNETCRMODULEDEF All data related to the MVI56E MNETCR is stored a user defined data type An instance of the data type is required before the module can be used This is done by declaring a variable of the data type the CONTROLLER TAGS EDIT TAGS dialog box The following table describes the structure of this object Name Data Type Description DATA MNETCRDATA page Data read from module 73 CONTROL MNETCRCONTROL Module control page 74 STATUS MNETCRSTATUS Client Server Status and blocks status page 75 UTIL MNETCRUTIL page Block statistics 7T This object contains objects that define the configuration user data status and command control data related to the module Page 72 of 159 ProSoft Technology Inc June 14 2011
18. 4 8 6 2 10 Controlling Law and Index ProSoft Technology Inc June 14 2011 Page 7 of 159 Contents MVI56E MNETCR 4 ControlLogix Platform User Manual Modbus TCP IP Multi Client Enhanced Communications Module for Remote Chassis Page 8 of 159 ProSoft Technology Inc June 14 2011 MVI56E MNETCR ControlLogix Platform Modbus TCP IP Multi Client Enhanced Communications Module for Remote Chassis Start Here User Manual 1 Start Here In This Chapter Whats New iode optet tete ees 10 System 11 Package 00 0 000 12 Setting Jumbpets bee ie Debet de eie 13 Installing the Module in the Rack sem 14 Installing the Configuration Tools eee 16 Connecting Your to the 17 Setting Temporary IP 0 18 Connecting to the Module s Web 24 Uploading the Add On Instruction from the Module 25 Creating a New RSLogix 5000 26 To get the most benefit from this User Manual you should have the following skills Rockwell Automation RSLogix so
19. GENERIC 1756 MODULE Select Module Module Analog Communications Controllers Digital Drives 1 Motion Other 1756 MODULE Specialty Generic 1756 Module Allen Bradley Eind Favorite By Category By Vendor Favorites DK Cancel 3 Setthe Module Properties values as follows Parameter Value Name Enter a module identification string The recommended value is MNETCR Description Enter a description for the module Example Modbus TCP IP Multi Client Enhanced Communications Module for Remote Chassis Comm Format Select DATA INT Very Important Slot Enter the slot number in the rack where the MVIS6E MNETCR module will be installed Input Assembly Instance 1 Input Size 42 Output Assembly Instance 2 Output Size 42 Configuration Assembly Instance 4 Configuration Size 0 ProSoft Technology Inc June 14 2011 Page 29 of 159 Start Here MVI56E MNETCR 4 ControlLogix Platform User Manual Modbus TCP IP Multi Client Enhanced Communications Module for Remote Chassis 4 Onthe CONNECTION tab set the RPI value for your project Fifty milliseconds is usually a good starting value Wil Module Properties Local 2 1756 MODULE 1 1 General Connection Module Info Backplane Requested Packet Interval RPI 50 05 ms 0 2 750 0 ms Inhibit Module Major Fault On Co
20. RSLogix 5000 XML Files L5X Cancel te My Network Places 4 Navigate to the location on your PC where you saved page 25 the Add On This action opens the IMPORT CONFIGURATION dialog box showing the controller tags that will be created ProSoft Technology Inc Page 34 of 159 June 14 2011 MVI56E MNETCR 4 ControlLogix Platform Start Here Modbus TCP IP Multi Client Enhanced Communications Module for Remote Chassis User Manual o If you are installing the module in a Remote Rack open the dropdown menus for the Input and Output tags and select the MNETCR module in the remote rack Import Configuration Tags Data Types Add On Instructions ADIBBMNETCR Use Existing MNETCR Use E sisting a odes H emoteENBT 1796 Use Existing i Bj x RemoteENBT Slot6 1 1 g RemoteENBT_Slot6 1 0 AB 1756_MODULE_INT_84Bytes 0 0 g grj RemoteENBT Slot l AB 1756 7510 0 g j RemoteENBT 51016 0 AB 1756 ENET 7510 0 0 g E WRITECLOCKMSG MESSAGE Controller Program Show Show All Import Configuration Tags Data Types Add On Instructions Names fins For Data Type AOISEMNETCR ADISEMNETC Use Existing 1 MNETCR MNETCRMOD Use Existing RemateENBT_Slot6 1 1 1756 Use Existing 1756 Use Existing AB 1756 MODULE INT 84Bytes 0 0 g RemoteENBT_Slot
21. Refer to your Rockwell Automation documentation for information on other connection methods 1 Connect the right angle connector end of the cable to your controller at the communications port Communications Port 2 Connect the straight connector end of the cable to the serial port on your computer 1 11 4 Downloading the Sample Program to the Processor Note The key switch on the front of the ControlLogix processor must be in the REM or PROG position ProSoft Technology Inc Page 43 of 159 June 14 2011 Start Here MVI56E MNETCR 4 ControlLogix Platform User Manual Modbus TCP IP Multi Client Enhanced Communications Module for Remote Chassis 1 If you are not already online with the processor open the Communications menu and then choose DOWNLOAD RSLogix 5000 will establish communication with the processor You do not have to download through the processor s serial port as shown here You may download through any available network connection 2 When communication is established RSLogix 5000 will open a confirmation dialog box Click the DOWNLOAD button to transfer the sample program to the processor A Download to the controller Name My_Controller Type 1756 L63 ControlLogix5563 Controller Path AB_DF1 1 Security lt None gt Cancel Help 3 RSLogix 5000 will compile the program and transfer it t
22. S B 3 1756 ENBT A Local Rung d Ethernet f 1756 ENBT A RemoteENET 6 3 1756 Backplane 1756 7 Delete Rung AddRung Edit Rung Edit Rung Comment Export Rung Verify Rung Go To Add Ladder Element Rung End ofi APP Page 38 of 159 ProSoft Technology Inc June 14 2011 Start Here MVI56E MNETCR ControlLogix Platform User Manual Modbus TCP IP Multi Client Enhanced Communications Module for Remote Chassis 8 Select the MVIBGEMNETCR RuNG v1 3 L5X file and then click IMPORT Import Rung oO Y My Computer Documents Network Places downloads MVI56 E MNETCR_AddOn_Rung_v1_3 L5X File name MVIS6 E MNETCR_AddOn_Rung_v1_315X Files of type RSLogix 5000 XML Files L5X Cancel e 9 This action opens the IMPORT CONFIGURATION window which shows the tags that will be imported Import Configuration Tags Data Types Add On Instructions 0 Use Existing MNETER MNETCRMOD Use Existing RiemoteENBT_Slot6 1 1 1756 MOD Use Existing RemoteENBT_Slot6 1 0 1756 MD Use Existing ProSoft Technology Inc Page 39 of 159 June 14 2011 Start Here User Manual MVI56E MNETCR ControlLogix Platform Modbus TCP IP Multi Client Enhanced Communications Module for Remote Chassis 10 Associate the connection variables to the correct module T
23. The Write Register Count parameter specifies the size of the Write Data area of module memory and the number of registers to transfer from the processor to this memory area up to a maximum value of 5000 words Note Total Read Register Count and Write Register Count cannot exceed 5000 total registers Read Data and Write Data Areas must be configured to occupy separate address ranges in module memory and should not be allowed to overlap Failure Flag Count If this value is greater than zero the protocol communication will be interrupted once the backplane failure is detected or communication with the processor fails A value of zero will disable this feature Initialize Output Data 0 No 1 Yes This parameter is used to determine if the output data for the module should be initialized with values from the processor If the value is set to 0 the output data will be initialized to O If the value is set to 1 the data will be initialized with data from the processor Use of this option requires associated ladder logic to pass the data from the processor to the module ProSoft Technology Inc Page 51 of 159 June 14 2011 Configuring the MVIBGE MNETCR Module MVI56E MNETCR ControlLogix Platform User Manual Modbus TCP IP Multi Client Enhanced Communications Module for Remote Chassis Duplex Speed Code 0 1 2 3or4 This parameter allows you to cause the module to use a specific duplex Speed setting Value 1 Half d
24. following message should be displayed upon success Download files from PC to module STEP 1 Select Communication Path Select Connection Type 1756 ENBT r Jevice Ethernet It Ir CIPconnect Successfully Connected STEP 2 Transfer File DOWNLOAD Connection 5 Click OK to close the Test Connection pop up and then click DOWNLOAD to download the configuration files to the module through the path Download files from PC to module Running STEP 1 Select Communication Path Select Connection Type 1756 ENBT rowse Device s Ethernet Use Default IF CIPconnect t 192 168 0 100 p 1 s 2 STEP 2 Transfer File s DOWNLOAD Abort Test Connection Bk Cancel ProSoft Technology Inc Page 67 of 159 June 14 2011 Configuring the MVIBGE MNETCR Module MVI56E MNETCR 4 ControlLogix Platform User Manual Modbus TCP IP Multi Client Enhanced Communications Module for Remote Chassis 2 3 2 Example 2 Remote Rack Application For this example the MVI56E MNETCR module is located a remote rack accessible through ControlNet as shown in the following illustration 1756 CNB 1756 ENBT Rack 1 Ethernet ControlNet Rack 1 Slot Module Network Address 0 ControlLogix Processor 1 1756 CNB Node 1 2 1756 ENBT 192 168 0 100 3 Any Rack 2 Slot Module Network Address 0 Any 1 Any 2 Any 3 Any 4 Any 5 1756 CNB Node
25. gt STEP 1 Select Communication Path Select Connection Type 1756 ENBT gt Ethernet CIPconnect 192 168 0 100 1 5 2 2 STEP 2 Transfer File s DOWNLOAD Test Connection Ok Cancel 4 Click TEST CONNECTION to verify that the physical path is available The following message should be displayed upon success Download files from PC to module r STEP 1 Select Communication Path Select Connection Type 1756 ENBT v Ethernet CIPconnect Successfully Connected STEP 2 Transfer File DOWNLOAD Connection 5 Click DOWNLOAD to download the configuration files to the module through the path Download files from PC to module Module Running r STEP 1 Select Communication Path Select Connection Type 1756 ENBT Ethernet CIPconnect t 192 168 0 100 p 1 s 2 p 2 STEP 2 Transfer File s DOWNLOAD Test Connection Ok Cancel Page 70 of 159 ProSoft Technology Inc June 14 2011 MVI56E MNETCR 4 ControlLogix Platform Ladder Logic Modbus TCP IP Multi Client Enhanced Communications Module for Remote Chassis User Manual 3 Ladder Logic In This Chapter gt Module Data Object 72 Ladder logic is required for managing communication between the MVI56E MNETCR module and the processor The ladder logic handles tasks such as Module backplane data transfer
26. or similar infringement The Buyer assumes all risks including the risk of suit that the product or any use of the product will infringe existing or subsequently issued patents trademarks or copyrights a Any documentation included with Product purchased from ProSoft is protected by copyright and may not be duplicated or reproduced in any form without prior written consent from ProSoft b ProSoft s technical specifications and documentation that are included with the Product are subject to editing and modification without notice c Transfer of title shall not operate to convey to Customer any right to make or have made any Product supplied by ProSoft d Customer is granted no right or license to use any software or other intellectual property in any manner or for any purpose not expressly permitted by any license agreement accompanying such software or other intellectual property e Customer agrees that it shall not and shall not authorize others to copy software provided by ProSoft except as expressly permitted in any license agreement accompanying such software transfer software to a third party separately from the Product modify alter translate decode decompile disassemble reverse engineer or otherwise attempt to derive the source code of the software or create derivative works based on the software export the software or underlying technology in contravention of applicable US and international export laws and regulation
27. 0 00000000 000 0 00000000 000 0 00000000 000 0 00000000 00 0 00000000 000 0 00000000 000 0 00000000 000 0 00000000 000 0 0 0 00000000 000 0 00000000 000 0 00000000 000 0 00000000 000 0 0 Hexadecimal DATABASE DISPLAY 0 to 99 HEXADECIMAL 8164 4340 5245 2 32 3130 3430 3930 Use the scroll bar on the right edge of the window to view each page 100 words of data Page 90 of 159 ProSoft Technology Inc June 14 2011 MVI56E MNETCR ControlLogix Platform Diagnostics and Troubleshooting Modbus TCP IP Multi Client Enhanced Communications Module for Remote Chassis User Manual 4 3 Reading Status Data from the Module MVI56E MNETCR module maintains a Status Data Table that can be used to determine the module s operating status This data is located in the module s database at the location specified by the Error Status Pointer configuration parameter page 50 This data is transferred to the processor continuously For a complete listing of the status data object refer to Status Data Definition page 105 page 112 The Configuration Debug port provides the following functionality Full view of the module s configuration data View of the module s status data Complete display of the module s internal database registers O to 3999 Version Information Control over the module warm boot cold boot transfer configuration Facility to upload and download the module s configuration fi
28. 0 0 1 Write Block ID 2 First digit of dotted IP address 3 Second digit of dotted IP address 4 5 6 Third digit of dotted IP address Last digit of dotted IP address to 41 Spare data area 35 4 4 2 oa Warm Boot Block 9998 This block is equivalent to performing a software reset and causes the module to exit the program reload the configuration file and then restart the program The Warm Boot control block also initializes the application port s and status data and resets all internal registers to zero Note In some cases the read section of the module database transferred from module to processor must keep its values after a reboot To repopulate the module s registers with the last values the module sent to the processor set the INITIALIZE OUTPUT DATA parameter in the module configuration to YES The following table describes the format of the control block Offset Description Length 0 9998 1 1 to 1 Spare 41 The module does not send a response block for this command ProSoft Technology Inc Page 109 of 159 June 14 2011 Reference MVI56E MNETCR 4 ControlLogix Platform User Manual Modbus TCP IP Multi Client Enhanced Communications Module for Remote Chassis Cold Boot Block 9999 This block is equivalent to performing a hardware reset and causes the module to restart in the same way as if the power was cycled The Cold Boot control block also reloads
29. 1 8 Setting Temporary IP 402224424400 4 00000 18 1 8 1 Using ClPconnect to Connect to the 22 1 9 Connecting to the Module s Web Page 24 1 10 Uploading the Add On Instruction from the 25 1 11 Creating a New RSLogix 5000 26 1 11 1 Create the Remote Network sssssssssssssssseeeeeeenee enne nennen nennen 27 1 11 2 Import Add On Instruction 33 1 11 3 Connecting Your PC to the ControlLogix 43 1 11 4 Downloading the Sample Program to the 43 2 Configuring the MVI56E MNETCR Module 45 2 1 Using ProSoft Configuration Builder 46 2 1 1 Setting Up the 47 2 1 2 Renaming PCB Objects i PE DOE 49 2 1 3 50 2 1 4 MNET ClIGntx A 52 54 2 1 5 2 1 6 Static ARP Tables ierit ete ee E 60 2 1 7 Ethernet Configuration nnne nennen SENDRA 61 2 2 Downloading the Project to the
30. 1756 ENBT module that you just created in the Controller Organization pane and click the right mouse button to open a shortcut menu On the shortcut menu choose NEw MODULE 3 Controller My Controller Controller Tags Controller Fault Handler Power Up Handler Gi Tasks Motion Groups Ungrouped Axes Add On Instructions Data Types Trends 1 0 Configuration 9 1756 Backplane 1756 A4 fa 0 1756463 Controller 8 12 1756 ENBT A Local a 5 amp cut Ctrl x Copy Ctrl C Delete Del Cross Reference Ctrl4E Alt Enter Properties 6 Repeat steps 2 and 3 to add the second EtherNet IP module to the remote rack Page 28 of 159 ProSoft Technology Inc June 14 2011 MVI56E MNETCR ControlLogix Platform Modbus TCP IP Multi Client Enhanced Communications Module for Remote Chassis Start Here User Manual Create the Module Remote Rack 1 Inthe CONTROLLER ORGANIZATION window select the remote 1756 BACKPLANE node and then click the right mouse button to open a shortcut menu On the shortcut menu choose NEW MODULE 3 8 1 0 Configuration 1756 Backplane 1756 A7 0 1756 L63 Controller 3 1756 CNB D Local_CNBR1 ControlNet 8 11756 CNB D Local CNER1 2 1756 CNB D Remote 2 11756 Backplane 1756 A17 2 This action opens the SELECT MODULE dialog box Expand the OTHER node and then select 1756 MODULE
31. 2 Transfer File s DOWNLOAD Test Connection Cancel ProSoft Technology Inc Page 65 of 159 June 14 2011 Configuring the MVIBGE MNETCR Module MVI56E MNETCR 4 ControlLogix Platform User Manual Modbus TCP IP Multi Client Enhanced Communications Module for Remote Chassis 2 Configure the path as shown in the following illustration and click CONSTRUCT CIP PATH to build the path in text format Path Editor Connect PATH EDITOR Source Module IP Source Module Node Destination Modul Destination Module Address Address eme Slot Number 1756 ENBT 192168010 v 2 No Source Module t 192 168 0 100 p 1 s 2 Add Rack Delete Rack Construct CIP Path Click OK to close the C Pconnect Path Editor and return to the Download dialog box 3 Check the new path in the Download dialog box Download files from PC to module STEP 1 Select Communication Path Select Connection Type 1756 ENBT Ethernet 1 t 192 168 0 100 p 1 5 2 STEP 2 Transfer File s DOWNLOAD Test Connection Cancel 66 159 ProSoft Technology Inc June 14 2011 MVI56E MNETCR ControlLogix Platform Configuring the MVI56E MNETCR Module Modbus TCP IP Multi Client Enhanced Communications Module for Remote Chassis User Manual 4 Click TEST CONNECTION to verify that the physical path is available The
32. A C and D T5 Hazardous Locations or Non Hazardous Locations ATEX Warnings and Conditions of Safe Usage Power Input and Output I O wiring must be in accordance with the authority having jurisdiction A Warning Explosion Hazard When in hazardous locations turn off power before replacing or wiring modules B Warning Explosion Hazard Do not disconnect equipment unless power has been switched off or the area is known to be non hazardous C These products are intended to be mounted in an IP54 enclosure The devices shall provide external means to prevent the rated voltage being exceeded by transient disturbances of more than 4095 This device must be used only with ATEX certified backplanes D DO NOT OPEN WHEN ENERGIZED Electrical Ratings Backplane Current Load 800 mA 5 3 mA 24 Operating Temperature 0 C to 60 C 32 F to 140 F Storage Temperature 40 C to 85 C 40 F to 185 F Shock 30 g operational 50 g non operational Vibration 5 g from 10 Hz to 150 Hz Relative Humidity 5 to 95 without condensation All phase conductor sizes must be at least 1 3 mm squared and all earth ground conductors must be at least 4mm squared Markings Agency Applicable Standards RoHS ATEX EN60079 0 July 2006 EN60079 15 October 2005 CSA IEC61010 CE 61326 1 2006 61000 6 4 2007 CSA CB Safety CA 10533 CSA IEC 61010 1 Ed 2 CB 243333 2056722 2090408 cULus GOST R Test 2 4 R
33. Configuring the MVIBG6E MNETCR Module Modbus TCP IP Multi Client Enhanced Communications Module for Remote Chassis User Manual 2 3 Using ClPconnect to Connect to the Module You can use ClPconnect to connect a PC to the ProSoft Technology MVI56E MNETCR module over Ethernet using Rockwell Automation s 1756 ENBT EtherNet IP module This allows you to configure the MVIS6E MNETCR network settings and view module diagnostics from a PC RSLinx is not required when you use ClPconnect All you need are The IP addresses and slot numbers of any 1756 ENBT modules in the path The slot number of the MVI56E MNETCR in the destination ControlLogix chassis the last ENBTx and chassis in the path To use follow these steps 1 Inthe Select Port dropdown list choose 1756 ENBT The default path appears in the text box as shown in the following illustration Download files from PC to module STEP 1 Select Communication Path Select Connection Type 1756 ENBT 7 Ethernet CIPconnect t 192 168 0 100 p 1 5 0 CIP Path Edit STEP 2 Transfer File s DOWNLOAD Test Connection Cancel 2 Click CIP PATH EDIT to open the C Pconnect Path Editor dialog box CIPconnect Path Editor 4 Connect PATH EDITOR Source Module IP Source Module Node Destination Module Address Address Destination Module Slot Number 175 EneT 1921680100 MVI56 Module 0 No So
34. Favorites Add On Alarms it aalelel x Path none z 2 Add On for MVI56 MNETCR and MVI56E MNETCR Modules AOIS6MNETCR Add On for MVI56 MNETCR and MVI56E MNETCR AOI56MNETCR AOIS6MNETCR Connection Input RemoteENBT_Slot6 1 1 Data Connection Output RemoteENBT_Slot6 1 0 Data MNETCR MNETCR CutRung Copy Rung Delete Rung Add Rung Edit Rung Edit Rung Comment Import Rung Export Rung Verify Rung GoTo Add Ladder Element ProSoft Technology Inc June 14 2011 Page 133 of 159 Reference MVI56E MNETCR 4 ControlLogix Platform User Manual Modbus TCP IP Multi Client Enhanced Communications Module for Remote Chassis 2 Navigate to the folder where you saved MVIBGEMNETCR Optional AddOn Rung version gt L5X and select the file Import Rung in MVIS6E MNETCR ek Ee MVIS6 E MNETCR AddOn Rung vi 3 L5X MVIS6EMNETCR Optional AddOn Rung vi 0 15 name MVISGEMNETCR Optional AddOn Rung v1 v Files of type RSLogix 5000 XML Files L5X Cancel In the IMPORT CONFIGURATION window click OK Import Configuration Tags Data Types Add On Instructions Use Existing MVI56EMNETCRCLOCK MNETCRCLO Use Existing MVI56E MNETCRETHER Use Existing READCLOCKMSG MESSAGE Use Existing READETHERNETMSG MESSAGE Existing WRITECLOCKMSG
35. Holding Registers 03 allows the user to obtain the binary contents of holding registers 4xxxx in the addressed Server The registers can store the numerical values of associated timers and counters which can be driven to external devices The addressing allows up to 125 registers to obtained at each request however the specific Server device may have restriction that lower this maximum quantity The registers are numbered form zero 40001 zero 40002 one and so on The broadcast mode is not allowed The example below reads registers 40108 through 40110 from Server 584 number 11 Adr Func Data Start Reg Hi Data Start Reg Lo Data tof Regs Hi Data tof Regs Lo Error Check Field 11 3 00 6B 00 03 CRC Response The addressed Server responds with its address and the function code followed by the information field The information field contains 1 byte describing the quantity of data bytes to be returned The contents of the registers requested DATA are two bytes each with the binary content right justified within each pair of characters The first byte includes the high order bits and the second the low order bits Because the Server interface device is normally serviced at the end of the controller s scan the data will reflect the register content at the end of the scan Some Servers will limit the quantity of register content provided each scan thus for large register quantities multiple transmissions will be made using re
36. MNETCR ProSoft Add On Ethernet Address Software TA 0D 8D 00 3A 98 Technology Datasheet IP Address 10 1 3 195 Rockwell duct Revision 2 04 006 2 6 25 20 Automation FUNCTIONS Firmware Version Date 11 12 09 01 i Modbus Firmware Serial Numbe 0 E9 4 Upgrade Organization P9 Status Running Set Date amp Time Technical Support Homepage Important The temporary IP address is only valid until the next time the module is initialized Please refer to Setting Temporary IP Address page 18 in the MVIBGE MNETCR User Manual for information on how to set the module s permanent IP address Page 24 of 159 ProSoft Technology Inc June 14 2011 MVI56E MNETCR ControlLogix Platform Modbus TCP IP Multi Client Enhanced Communications Module for Remote Chassis Start Here User Manual 1 10 Uploading the Add On Instruction from the Module Configuration and control information for the module is provided as an Add On Instruction for RSLogix 5000 version 16 or higher TECHNOLOGY DOWNLOADS MVIS6E MNETCR Safety Info Add on Software Setup Guide User Manuals Software Instruction Rung Import with Utility Add On Instruction Optional How to install the Add On Instruction Datasheet FUNCTIONS Firmware Upgrade Click to upload Add On Instruction Set Date amp Time Technical Support Homepage Two Add On Instr
37. MVI56E MNETCR ControlLogix Platform Ladder Logic Modbus TCP IP Multi Client Enhanced Communications Module for Remote Chassis User Manual 3 1 1 User Data Object MNETCRDATA These objects hold data to be transferred between the processor and the MVI56E MNETCR module The user data is the read and write data transferred between the processor and the module as pages of data up to 200 words long Name Data Type Description ReadData INT 600 Data Read from the Module Set array equal to the size set in the Configuration file WriteData INT 600 Data Write to the Module Set array equal to the size set in the Configuration file ReaabData is a controller tag array that should be sized to match the value entered in the READ REGISTER COUNT parameter of the CFG file or in ProSoft Configuration Builder PCB page 50 For ease of use both this array and the READ REGISTER COUNT should be dimensioned in even increments of 40 words This data is paged up to 40 words at a time from the module to the processor The 6800818 ladder logic task places the data received into the proper position in the MNETCR DATA ReadData array The data received in the 76800818 array will contain status and control information sent by other nodes on the network for use by processor logic The ReadData array may also be used to hold certain module status and error data which can then be monitored by processor logic WriteData is a controller tag array th
38. Multiple Register 4x The first part of the record is the module information which relates to the MVI56E module and the second part contains information required to interface to the server device ProSoft Technology Inc Page 55 of 159 June 14 2011 Configuring the MVIBGE MNETCR Module MVI56E MNETCR ControlLogix Platform User Manual Modbus TCP IP Multi Client Enhanced Communications Module for Remote Chassis Command list example Fdit MNet Client 0 Commands Enable Internal amp ddress Poll Interval Reg Count Swap Code NodelP Address ServPort Slave Addr ModBus Function 1 1000 D 10 NoChange 1821680249 502 1 FC 3 Read Holding 2 Yes 0 0 10 Change 192 168 0 249 502 1 FC 16 Preset writ Enable Value Status Setto Add Row Insert Row Delete Row Move Up Move Down Edit Row Row OK Enable No 0 or YES 1 This field defines whether or not the command is to be executed Value Description No 0 The command is disabled and will not be executed in the normal polling sequence Yes 1 The command is executed each scan of the command list if the Poll Interval Time is set to zero If the Poll Interval time is set the command will be executed when the interval timer expires Internal Address 0 to 4999 for word level addressing or 0 to 65535 for bit level addressing This field specifies the
39. Network ProSoft Technology Inc Page 111 of 159 June 14 2011 Reference MVI56E MNETCR 4 ControlLogix Platform User Manual Modbus TCP IP Multi Client Enhanced Communications Module for Remote Chassis 5 3 1 Client Driver In the client driver the MVIBGE MNETCR module issues read or write commands to servers on the Modbus TCP IP network using 30 simulated clients These commands are user configured in the module via the Client Command List for each client received from the module s configuration file MNET CFG or issued directly from the processor event command control Command status is returned to the processor for each individual command in the command list status block The location of this status block in the module s internal database is user defined The following flow chart and associated table describe the flow of data into and out of the module Processor Memory Backplane Interface MNetCR Database Modbus Controller Tags Address Addresses 8 i i Client Driver 4999 i Status from Status Stat Event Cmd Event Cmd i Data Data ent Cmd Data ommand Command como Command Control Step Description Register Data Register Data Storage Client Command List Control 1 The client driver obtains configuration data from the MNET CFG file when the module restarts The configuration data obtained includes the timeout
40. On Instruction only supports the two features listed above You must use the sample ladder logic for all other features including backplane transfer of Modbus TCP IP data Page 132 of 159 ProSoft Technology Inc June 14 2011 MVI56E MNETCR 4 ControlLogix Platform Modbus TCP IP Multi Client Enhanced Communications Module for Remote Chassis Reference User Manual 5 6 3 Installing the Rung Import with Utility Add On Instruction 1 and choose IMPORT RUNG Right click on an empty rung in the main routine of your existing ladder logic f RSLogix 5000 ControlLogix in MVISGEMNETCR v16 ACD 1756 L63 MainProgram MainRoutine File Edit View Search Logic Communications Tools Window Help alsa umetR ute intoutputdata Tre 81385 alal Offline m RUN No Forces 5 5 No Edits 65 Controller ControlLogix Controller Tags Controller Fault Handler Power Up Handler Tasks MainTask El Cg MainProgram Program Tags MainRoutine Gi Unscheduled Programs 055 Motion Groups 9 08 Add On Instructions Data Types G Trends 5 6 1 0 Configuration 1756 Backplane 1756 A4 0 1756463 ControlLogix B 3 1756 ENST A Local dg Ethernet i756 ENBT A RemoteENET Slot 1756 Backplane 1756 7 3 1 1756 MODULE MNETCR a MONIN 30 Ladder Diagram Main lt Hite y 4 j a
41. PCB Pentium 11 450 MHz minimum Pentium III 733 MHz or better recommended Supported operating systems Microsoft Windows Vista Microsoft Windows XP Professional with Service Pack 1 or 2 Microsoft Windows 2000 Professional with Service Pack 1 2 or 3 o Microsoft Windows Server 2003 128 Mbytes of RAM minimum 256 Mbytes of RAM recommended 100 Mbytes of free hard disk space or more based on application requirements 256 color VGA graphics adapter 800 x 600 minimum resolution True Color 1024 x 768 recommended CD ROM drive Note Hardware and Operating System requirements in this list the minimum recommended to install and run software provided by ProSoft Technology Other third party applications may have different minimum requirements Refer to the documentation for any third party applications for system requirements Note You can install the module in a local or remote rack For remote rack installation the module requires EtherNet IP or ControlNet communication with the processor ProSoft Technology Inc Page 11 of 159 June 14 2011 Start Here MVI56E MNETCR 4 ControlLogix Platform User Manual Modbus TCP IP Multi Client Enhanced Communications Module for Remote Chassis 1 3 Package Contents The following components are included with your MVIS6E MNETCR module and are all required for installation and configuration Important Before beginning the installation please verify that a
42. Reference MVI56E MNETCR ControlLogix Platform User Manual Modbus TCP IP Multi Client Enhanced Communications Module for Remote Chassis Normal Data Transfers Normal data transfer includes the paging of the user data and status data found in the module s internal database in registers 0 to 4999 These data are transferred through read input image and write output image blocks The following topics describe the function and structure of each block Block Response from Module to Processor These blocks of data transfer information from the module to the ControlLogix processor The following table describes the structure of the input image Offset Description Length 0 Write Block ID 1 1 to 40 Read Data 40 41 Read Block ID 1 The Read Block ID is an index value used to determine the location of where the data will be placed in the ControlLogix processor controller tag array of module read data Each transfer can move up to 40 words block offsets 1 to 40 of data In addition to moving user data the block also contains status data for the module The Write Block ID associated with the block requests data from the ControlLogix processor Under normal program operation the module sequentially sends read blocks and requests write blocks For example if the application uses three read and two write blocks the sequence will be as follows R1W1 R2W25R3W1 R1W29R2W 15 R3W25R1W1 This sequence will continue until int
43. Slot Number slot number where the destination MVI56E module is located To use the ClPconnect Path Editor follow these steps 1 Configure the path between the 1756 ENBT connected to your PC and the MVI56E MNETCR module o If the module is located in a remote rack add more racks to configure the full path o The path can only contain ControlNet or Ethernet IP networks o maximum number of supported racks is six 2 Click CONSTRUCT PATH to build the path in text format 3 Click OK to confirm the configured path ProSoft Technology Inc Page 23 of 159 June 14 2011 Start Here MVI56E MNETCR ControlLogix Platform User Manual Modbus TCP IP Multi Client Enhanced Communications Module for Remote Chassis 1 9 Connecting to the Module s Web Page 1 ProSoft Discovery Service select the module to configure and then click the right mouse button to open a shortcut menu 2 Onthe shortcut menu choose VIEW MODULE S WEBPAGE Prosoft Discovery Service Assign Temporary IP Device Details Remove Temporary IP View module s webpage Select for PCB Click the search icon to begin the browse The web page contains the product documentation and sample programs All manuals and configuration tools are available from the module s web page DOWNLOADS Modbus TCP IP Client for Remote ControlLogix Safety Info MVISGE MNETCR Setup Guide RESOURCES User Manuals E Module Name MVIS6E
44. The multi Client module improves performance when controlling multiple servers on a Modbus TCP IP network by supporting up to 30 Clients MVI56E enhancements include configuration and management through the module s Ethernet port ClPconnect technology for bridging though ControlNet and EtherNet IP networks and a web server to access on board documentation Add On Instructions and sample program files This module uses a small I O data image for transfer of data between the module and the ControlLogix processor making it ideal for ControlNet or Ethernet applications with the module in a remote rack 5 1 1 General Specifications Backward compatible with previous MVI56 MNETC versions Single slot 1756 ControlLogix backplane compatible 10 100 Mbps auto crossover detection Ethernet configuration and application port User definable module data memory mapping of up to 5000 16 bit registers ClPconnect enabled network configuration and diagnostics monitoring using ControlLogix 1756 ENxT and 1756 CNB modules ProSoft Configuration Builder PCB software supported a Windows based graphical user interface providing simple product and network configuration Sample ladder logic and Add On Instructions AOI are used for data transfer between module and processor Internal web server provides access to product documentation module status diagnostics and firmware updates 4 character alpha numeric scrolling LED displa
45. application port hardware during startup The module is shutting down module is rebooting due to a ColdBoot or WarmBoot request from the ladder logic or Debug Menu OK Redor OFF Green The module is not receiving adequate power or is not securely plugged into the rack GREEN The module is operating normally RED The module has detected an internal error or is being initialized If the LED remains RED for over 10 seconds the module is not working Remove it from the rack and re insert it to restart its internal program ERR Not Used ProSoft Technology Inc June 14 2011 Page 81 of 159 Diagnostics and Troubleshooting User Manual MVI56E MNETCR ControlLogix Platform Modbus TCP IP Multi Client Enhanced Communications Module for Remote Chassis 4 1 4 Troubleshooting Use the following troubleshooting steps if you encounter problems when the module is powered up If these steps do not resolve your problem please contact ProSoft Technology Technical Support Processor Errors Problem description Steps to take Processor fault Verify that the module is plugged into the slot that has been configured for the module in the I O Configuration of RSLogix Verify that the slot location in the rack has been configured correctly in the ladder logic Processor I O LED flashes This indicates a problem with backplane communications A problem could exist between th
46. complete this step you can connect to the module with an Ethernet cable 1 Determine the network settings for your module with the help of your network administrator if necessary You will need the following information IP address fixed IP required Subnet mask o Gateway address Note The gateway address is optional and is not required for networks that do not use a default gateway 2 Double click the ETHERNET CONFIGURATION icon This action opens the Edit dialog box Edit WATTCP 192 168 0 250 netmask 255 255 255 0 gateway 192 168 0 1 168 Comment Definition Default private class 3 address Reset Tag Reset All OK Cancel 3 Edit the values for my ip netmask subnet mask and gateway default gateway 4 When you are finished editing click OK to save your changes and return to the ProSoft Configuration Builder window ProSoft Technology Inc Page 61 of 159 June 14 2011 Configuring the MVIBGE MNETCR Module MVI56E MNETCR 4 ControlLogix Platform User Manual Modbus TCP IP Multi Client Enhanced Communications Module for Remote Chassis 2 2 Downloading the Project to the Module In order for the module to use the settings you configured you must download copy the updated Project file from your PC to the module 1 Inthe tree view in ProSoft Configuration Builder click once to select the MVI56E MNETCR module 2 Open the PROJECT me
47. contact ProSoft Technical Support at one of the telephone numbers listed above page 147 A Technical Support Engineer will request that you perform several tests in an attempt to isolate the problem If after completing these tests the Product is found to be the source of the problem we will issue an RMA C All returned Products must be shipped freight prepaid in the original shipping container or equivalent to the location specified by ProSoft Technology and be accompanied by proof of purchase and receipt date The RMA number is to be prominently marked on the outside of the shipping box Customer agrees to insure the Product or assume the risk of loss or damage in transit Products shipped to ProSoft Technology using a shipment method other than that specified by ProSoft Technology or shipped without an RMA number will be returned to the Customer freight collect Contact ProSoft Technical Support for further information d 10 restocking fee applies to all warranty credit returns whereby a Customer has an application change ordered too many does not need etc Returns for credit require that all accessory parts included in the original box i e antennas cables be returned Failure to return these items will result in a deduction from the total credit due for each missing item ProSoft Technology Inc Page 149 of 159 June 14 2011 Support Service amp Warranty MVI56E MNETCR ControlLogix Platform User Manual Modbus TC
48. data address Illegal data value Failure in associated device Acknowledge Busy message was rejected Module Communication Error Codes Code Description 2 Timeout while transmitting message 11 Timeout waiting for response after request 253 Incorrect slave server address in response 254 Incorrect function code in response 255 Invalid CRC LRC value in response MNET Client Specific Errors Code Description 33 Failed to connect to server specified in command 36 MNET command response timeout 37 TCP IP connection ended before session finished Page 114 of 159 ProSoft Technology Inc June 14 2011 MVI56E MNETCR 4 ControlLogix Platform Reference Modbus TCP IP Multi Client Enhanced Communications Module for Remote Chassis User Manual Command List Entry Errors Code Description 40 Too few parameters 41 Invalid enable code 42 Internal address maximum address 43 Invalid node address 0 or gt 255 44 Count parameter set to 0 45 Invalid function code 46 Invalid swap code 47 ARP could not resolve MAC from IP bad IP address not part of a network invalid parameter to ARP routine 48 Error during ARP operation the response to the ARP request did not arrive to the module after a user adjustable ARP Timeout Note When the Client gets error 47 or 48 it uses the adjustable ARP Timeout param
49. even multiples of eight the last characters will be filled in with zeros at high order end The quantity of data characters is always specified as a quantity of RTU characters that is the number is the same whether RTU or ASCII is used Because the Server interface device is serviced at the end of a controller s scan data will reflect input status at the end of the scan Some Servers will limit the quantity of inputs provided each scan thus for large coil quantities multiple PC transactions must be made using coil status for sequential scans Adr Func Byte Data Discrete Input Data Discrete Input Data Discrete Input Error Check Field Count 10197 to 10204 10205 to 10212 10213 to 10218 11 02 03 AC DB 35 CRC The status of inputs 10197 to 10204 is shown as AC HEX 10101 1100 binary Reading left to right this show that inputs 10204 10202 and 10199 are all on The other input data bytes are decoded similar Due to the quantity of input statuses requested the last data field which is shown as 35 HEX 0011 0101 binary contains the status of only 6 inputs 10213 to 102180 instead of 8 inputs The two left most bits are provided as zeros to fill the 8 bit format Page 120 of 159 ProSoft Technology Inc June 14 2011 MVI56E MNETCR ControlLogix Platform Reference Modbus TCP IP Multi Client Enhanced Communications Module for Remote Chassis User Manual 5 5 3 Read Holding Registers Function Code 03 Query Read
50. of 502 will cause a MBAP formatted message to be generated All other values will generate an encapsulated Modbus message 6 This word contains the Modbus node address for the message This field should have a value from 0 to 41 7 This word contains the internal Modbus address in the module to use with the command This word can contain a value from 0 to 4999 8 This word contains the count parameter that determines the number of digital points or registers to associate with the command 9 The parameter specifies the swap type for the data This function is only valid for function codes 3 and 4 10 This word contains the Modbus function code for the command 11 This word contains the Modbus address in the slave device to be associated with the command 12 to 41 Spare The module will respond to each command block with a read block The following table describes the format of this block Offset Description Length 0 Write Block ID 1 1 0 Fail 1 Success 1 2 to 40 Spare 39 41 2000 to 2029 1 Word two of the block can be used by the ladder logic to determine if the command was added to the command queue of the module The command will only fail if the command queue for the port is full 16 commands for each queue Page 104 of 159 ProSoft Technology Inc June 14 2011 MVI56E MNETCR 4 ControlLogix Platform Reference Modbus TCP IP Multi Client Enhanced Communications Module for Remote Chassis User Manual
51. parameters and the Command List These values are used by the driver to determine the type of commands to be issued to the other nodes on the Modbus TCP IP network 2 When configured the client driver begins transmitting read and or write commands to the other nodes on the network If writing data to another node the data for the write command is obtained from the module s internal database to build the command 3 Presuming successful processing by the node specified in the command a response message is received into the client driver for processing 4 Data received from the node on the network is passed into the module s internal database assuming a read command 5 Status data is returned to the processor for the client and a Command List error table can be established in the module s internal database Page 112 of 159 ProSoft Technology Inc June 14 2011 MVI56E MNETCR 4 ControlLogix Platform Reference Modbus TCP IP Multi Client Enhanced Communications Module for Remote Chassis User Manual 5 3 2 Client Command List In order for the Client to function the module s Client Command List must be defined in the MNET Client x Commands section of the configuration This list contains up to 16 individual entries with each entry containing the information required to construct a valid command This includes the following Command enable mode 0 disabled or 1 continuous IP address and service port to connect t
52. should work with most applications Wil Module Properties Local 1 1756 MODULE 1 1 General Connection Module Info Backplane Requested Packet Interval RPI Bo ms 0 2 750 0 ms Inhibit Module Major Fault On Controller Connection Fails While in Run Mode Module Fault Status Offline Cancel 3 Save the module Click OK to dismiss the dialog box The CONTROLLER ORGANIZATION window now displays the module s presence 7 5 Controller A Controller Tags Controller Fault Handler Power Up Handler 3 8 Tasks fa MainTask amp MainProgram Unscheduled Programs Motion Groups Ungrouped Axes Add On Instructions e Data Types Cg User Defined a Strings Ga Add On Defined ER Predefined 046 Module Defined Trends 1 0 Configuration 1756 Backplane 1756 A4 fa 0 1756 L63My_Controller 8 1 1756 MODULE Mvi 4 Copy the Controller Tags from the sample program 5 Copy the User Defined Data Types from the sample program 6 Copy the Ladder Rungs from the sample program 7 Save and Download page 43 the new application to the controller and place the processor in run mode Page 144 of 159 ProSoft Technology Inc June 14 2011 MVI56E MNETCR ControlLogix Platform Reference Modbus TCP IP Multi Client Enhanced Communications Module for Remote Chassis User Manual 5 8 Using the Sample Program RSLogix 5000 Version 15 and earlier The sample pro
53. the MNETCR STATUS array This data is transferred from the module to the processor as part of each read block Offset Content Description 1 Pass Count This value is incremented each time a complete program cycle occurs in the module 2 Read Block Count This field contains the total number of read blocks transferred from the module to the processor 3 Write Block Count This field contains the total number of write blocks transferred from the processor to the module 4 Parse Block Count This field contains the total number of blocks successfully parsed that were received from the processor 5 Command Event Block This field contains the total number of command event Count blocks received from the processor 6 Command Block Count This field contains the total number of command blocks received from the processor 7 Error Block Count This field contains the total number of block errors recognized by the module 8 to 37 Enable Disable Each bit in each word is used to enable or disable individual Command Bits commands in each client ProSoft Technology Inc Page 101 of 159 June 14 2011 Reference MVI56E MNETCR ControlLogix Platform User Manual Modbus TCP IP Multi Client Enhanced Communications Module for Remote Chassis Initialize Output Data When the module performs a restart operation it will request blocks of output data from the processor to initialize the module s output data Read Data Area Use the In
54. will not affect that coil The use of Server address 00 Broadcast Mode will force all attached Servers to modify the desired coil Note Functions 5 6 15 and 16 are the only messages that will be recognized as valid for broadcast The example below is a request to Server number 11 to turn ON coil 0173 Adr Func Data Coil Hi Data 601410 Data Data Error Check Field 11 05 00 AC FF 00 CRC Response The normal response to the Command Request is to re transmit the message as received after the coil state has been altered Adr Func Data Coil Hi Data Coil Lo Data On Data Error Check Field 11 05 00 AC FF 00 CRC The forcing of a coil via MODBUS function 5 will be accomplished regardless of whether the addressed coil is disabled or not In ProSoft products the coil is only affected if the necessary ladder logic is implemented Note The Modbus protocol does not include standard functions for testing or changing the DISABLE state of discrete inputs or outputs Where applicable this may be accomplished via device specific Program commands ProSoft products this is only accomplished through ladder logic programming Coils that are reprogrammed in the controller logic program not automatically cleared upon power up Thus if such a coil is set ON by function Code 5 and even months later an output is connected to that coil the output will be hot ProSoft Technology
55. 0 This parameter specifies the number of 100 millisecond intervals to turn off a command in the error list after an error is recognized for the command If this parameter is set to 0 there will be no delay MBAP Port Override YES or NO If this parameter is set to YES all messages generated by the Client driver will be MBAP format messages to all Service Port values If this parameter is set to No default value or is omitted from the configuration file all messages sent to Service Port 502 will be MBAP format messages and all other Service Ports values will use the encapsulated Modbus message format MNET Each Client is configured independently in the configuration file This parameter applies to firmware version 1 05 and above For downward compatibility you may omit this parameter from the Client s configuration 2 1 5 MNET Client x Commands The MNET Client x Commands section of the configuration sets the Modbus TCP IP Client command list This command list polls Modbus TCP IP server devices attached to the Modbus TCP IP Client port The module supports numerous commands This permits the module to interface with a wide variety of Modbus TCP IP protocol devices The function codes used for each command are those specified in the Modbus protocol Each command list record has the same format The first part of the record contains the information relating to the MVI56E MNETCR communication module and the second part contains i
56. 000 MVI46 C MVIS6 C MVI71 C All C 5000 PTQ C MVI69 MVISSE Search Module Type STEP 1 Select Module Type Module Definition Action Required MVIS6E MNETR 5 Inthe Product Line Filter area of the dialog box select MVI56E In the SELECT MODULE TYPE dropdown list select MVIS6E MNETCR and then click OK to save your settings and return to the ProSoft Configuration Builder window 6 Right click the module icon Default Project 2 8 Default Location h PEE ProSoft Technology Inc Page 19 of 159 June 14 2011 Start Here MVI56E MNETCR 4 ControlLogix Platform User Manual Modbus TCP IP Multi Client Enhanced Communications Module for Remote Chassis 7 On the shortcut menu choose DIAGNOSTICS 0 Default Project Default Location eno Delete Rename Copy Choose Module Type View Configuration Export Configuration File s Load Config File Download from PC to Device Upload from Device to PC This action opens the Diagnostics dialog box Diagnostics Connection Log Module esse MVI56E MNETCR Time 10 28 59 MODULE Select item within MVISGE MNETCR for diagnostic information Version Config NIC Status Static ARP BACKPLANE Status DATABASE ASCII Decimal Hex Float MNET CLIENT 0 Config Status Command List Command Status MNET CLIENT 1 Contig Status Command List Command Status MNET CLIENT 2 P
57. 12 fora complete listing of the data stored in the status object Page 76 of 159 ProSoft Technology Inc June 14 2011 MVI56E MNETCR ControlLogix Platform Modbus TCP IP Multi Client Enhanced Communications Module for Remote Chassis Ladder Logic User Manual 3 1 4 Backplane Control Object MNETCRUTIL This data object stores the variables required for the data transfer between the processor and the MVI5GE MNETCR module The following table shows the structure of the object Name Data Type Description LastRead INT Index of last read block LastWrite INT Index of last write block Computed block offset for data table ReadDataSizeGet INT Gets ReadData Array Length WriteDataSizeGet INT Gets WriteData Array Length ReadDataBlkCount INT Holds the value of the Block Counts of the Read Data Array WriteDataBlkCount INT Holds the value of the Block Counts of the Write Data Array RBTSremainder INT Holds remainder calculation value from the read array WBTSremainder INT Holds remainder calculation value from the write array IPgetPending BOOL Allows setting module IP address IPsetPending BOOL Allows getting module IP address The LastRead tag stores the latest Read Block ID received from the module The LastWrite tag stores the latest Write Block ID to be sent to the module The Block Index tag is an intermediate variable used during the block calculation
58. 21 8 bit Comm Format Data INT _ Slot EE Open Module Properties Cancel Help Parameter Value Name Enter a module identification string The recommended value is MNETCR Description Enter a description for the module Example Modbus TCP IP Multi Client Enhanced Communications Module for Remote Chassis Comm Format Select DATA INT Very Important Slot Enter the slot number in the rack where the MVIS6E MNETCR module will be installed Input Assembly Instance 1 Input Size 42 Output Assembly Instance 2 Output Size 42 Configuration Assembly Instance 4 Configuration Size 0 Enter the Name Description and Slot options for your application You must select the FORMAT AS DATA INT in the dialog box otherwise the module will not communicate over the backplane of the ControlLogix rack Click OK to continue ProSoft Technology Inc June 14 2011 Page 143 of 159 Reference MVI56E MNETCR 4 ControlLogix Platform User Manual Modbus TCP IP Multi Client Enhanced Communications Module for Remote Chassis 2 Edit the Module Properties Select the REQUESTED PACKET INTERVAL value for scanning the on the module This value represents the minimum frequency that the module will handle scheduled events This value should not be set to less than 1 millisecond The default value is 5 milliseconds Values between 1 and 10 milliseconds
59. 5 my_ip 192 168 0 250 sta MNET Client 16 netmask 2 255 255 255 0 sfa MNET Client 17 gateway 192 168 0 1 MNET Client 18 9 46 MNET Client 19 Module Configuration MNet Client 1 Values OK MNet Client 2 Values OK lt sfa Client 20 lt iiie de MVIS6E MNETCR At this time you may wish to rename the Default Project and Default Location folders in the tree view 1 2 3 Select the object and then click the right mouse button to open a shortcut menu From the shortcut menu choose RENAME Type the name to assign to the object Click away from the object to save the new name Configuring Module Parameters 1 2 Click on the sign next to the module icon to expand module information Click on the sign next to any amp amp icon to view module information and configuration options Double click any 8 icon to open an Edit dialog box To edit a parameter select the parameter in the left pane and make your changes in the right pane Click OK to save your changes Printing a Confiquration File 1 Select the module icon and then click the right mouse button to open a shortcut menu 2 Onthe shortcut menu choose VIEW CONFIGURATION This action opens the View Configuration window 3 Inthe View Configuration window open the FILE menu and choose PRINT This action opens the Print dialog box 4 Inthe Print dialog box choose the printer to use from the drop down list
60. 6 1756 7510 0 0 1756 7510 0 0 g Ej WRITECLOCKMSG MESSAGE g WRITEETHERNETMSG MESSAGE Controller Program Show Show All 5 Click OK to confirm the import RSLogix will indicate that the import is in progress Importing Creating routine Prescan ProSoft Technology Inc Page 35 of 159 June 14 2011 Start Here User Manual MVI56E MNETCR ControlLogix Platform Modbus TCP IP Multi Client Enhanced Communications Module for Remote Chassis When the import is complete you will see the new Add On Instruction rung in the ladder fs RSLogix 5000 ControlLogix in MVIS6EMNETCR_v16 ACD 1756 L63 MainProgram MainRoutine File Edit View Search Logic Communications Tools Window 1 41918 18 aAa E alsa S Offline f F RUN No Forces b No Edits 5 vo A Controller ControlLogix Controller Tags 1 Controller Fault Handler 9 Power Up Handler Tasks 5 MainTask amp MainProgram Program Tags MainRoutine Unscheduled Programs 1 3 Motion Groups Ungrouped Axes Add On Instructions AOIS6EMNETCR OPTIONAL 02 AOISGMNETCR Data Types Cg User Defined E Strings Gy Add On Defined E Predefined ig Module Defined G Trends 51 35 1 0 Configuration 1756 Backplane 1756 A4 fa 0 1756463 ControlLogix 8 3 1756 ENBT A Local 8 Ethernet
61. 6 6 Reading the Clock Value from the Module 2 140 5 6 7 Writing the Clock Value to the 141 5 7 Adding the Module to an Existing 142 Page 6 of 159 ProSoft Technology Inc June 14 2011 MVI56E MNETCR ControlLogix Platform Modbus TCP IP Multi Client Enhanced Communications Module for Remote Chassis Contents User Manual 5 8 Using the Sample Program RSLogix 5000 Version 15 and earlier 6 Support Service amp Warranty Contacting Technical Support 6 1 Return Material Authorization RMA Policies and Conditions 6 1 1 Returning Any Product 6 1 2 Returning Units Under 6 1 3 Returning Units Out of 6 2 LIMITED WARRANTY 00000 6 2 1 What Is Covered By This 6 2 2 What Is Not Covered By This Warranty 6 2 3 Disclaimer Regarding High Risk Activities 6 2 4 Intellectual Property 6 2 5 Disclaimer of all Other Warranties 6 2 6 Limitation of Remedies aiat 6 2 7 Time Limit for Bringing 6 2 8 No Other Warranties 2 6 2 9 Allocation of 4
62. 8 1756 ENBT A RemoteENET 6 1756 Backplane 1756 A7 B 1756 MODULE MNETCR 6 1756 ENBT A RemoteENET EJ 1756 ENET A Local 4 H f 3e mn 4 phe 84 0 A Al A Bt Add On for MVI56 MNETCR and MVI56E MNETCR Modules AOIS6MNETCR Add On for MVI56 MNETCR and MVIS56E MNETCR AOI56MNETCR AOIS6MNETCR Connection_Input RemoteENBT_Slot6 1 1 Data Connection Output RemoteENBT_Slot6 1 0 Data MNETCR MNETCR MainRoutine Rung 10f 2 fice The procedure has also imported new User Defined Data Types data objects and the Add On instruction for your project 4 _ Ao 6 Save the application and then download the sample ladder logic into the processor Page 36 of 159 ProSoft Technology Inc June 14 2011 MVI56E MNETCR 4 ControlLogix Platform Modbus TCP IP Multi Client Enhanced Communications Module for Remote Chassis Start Here User Manual Adding Multiple Modules Optional Important If your application requires more than one 56 module into the same project follow the steps below 1 In the I O CONFIGURATION folder click the right mouse button to open shortcut menu and then choose NEW MODULE 1 0 Configuration 11756 Backplane 1756 fia 0 1756163 2 New Module 2 Select 1756 MODULE Select Module
63. 9 for further information about the error Page 80 of 159 ProSoft Technology Inc June 14 2011 MVI56E MNETCR 4 ControlLogix Platform Modbus TCP IP Multi Client Enhanced Communications Module for Remote Chassis Diagnostics and Troubleshooting User Manual 4 1 2 Ethernet LED Indicators The Ethernet LEDs indicate the module s Ethernet port status as follows LED State Description Data OFF Ethernet connected at 10Mbps duplex speed AMBER Solid Ethernet connected at 100Mbps duplex speed Link OFF No physical network connection is detected No Ethernet communication is possible Check wiring and cables GREEN Solid Physical network connection detected This LED must be ON solid or Blinking for Ethernet communication to be possible 4 1 3 Non Scrolling LED Status Indicators The non scrolling LEDs indicate the module s operating status as follows LED Label Color Status Indication APP Redor OFF Green The module is not receiving adequate power or is not securely plugged into the rack May also be OFF during configuration download GREEN The MVI56E MNETCR is working normally RED The most common cause is that the module has detected a communication error during operation of an application port The following conditions may also cause a RED LED firmware is initializing during startup The firmware detects an on board hardware problem during startup Failure of
64. BBEMNETERCLOCK Write 0 MVI56EMNETCRCLOCK Config MVIBBEMNETCRELDCK Config Year 0 MVIBBEMNETCRCLOCK Config Month 0 MVIBEEMNETCRCLOCK Canfig Day 0 MVIBBEMNE TCRCLOCK Config Hour 0 MVIBBEMNETCRCLOCK Config Minute 0 MVIBEEMNETCRCLDEK Config Seconds 0 The bit will be automatically reset and the current clock value will be copied to controller tag as follows ted MVIBBEMNETCRCLOCK Read 0 MVI56EMNETCRCLOCK Write 0 MVIBBEMNETCRCLOCK Config Hood MVIBBEMNETCRCLOCK Config Y ear 2009 MVIBBEMNETCRCLOCK Config Month 11 MVIBBEMNETCRCLOCK Config D ay 18 MVIBBEMNETCRCLOCK Config Hour 10 MVIBBEMNETCRCLOCK Config Minute 21 MVIBBEMNETCRCLOCK Config Seconds 45 check the status of the message refer to the READCLOCKMSG tag READCLOCKMSG EST READCLOCKMSG Flags 1680200 READCLOCKMSG E Ww 0 READCLOCKMSG ER 0 READCLOCKMSG DN 0 READCLOCKMSG ST 0 READCLOCKMSG EN 0 READCLOCKMSG TO 0 READCLOCKMSG EN CC 1 READCLOCKMSG ERR 1000 READCLOCKMSG EXERR 1680000 0 READCLOCKMSG ERR_SRC 0 READCLOCKMSG DN LEN 0 READCLOCKMSG REGO LEN 0 Page 140 of 159 ProSoft Technology Inc June 14 2011 MVI56E MNETCR ControlLogix Platform Reference Modbus TCP IP Multi Client Enhanced Communications Module for Remote Chassis User Manual 5 6 7 Writing the Clock Value to the Module Expand the con
65. BEMNETCRETHERNET Config IP 2 MVIBBEMNETCRETHERNET Config IP 3 MVIBBEMNETCRETHERNET Config Netmask MVIBBEMNETCRETHERNET Config Netmask 0 MVIBBEMNETCRETHERNET Config Netmask 1 MVIBBEMNETCRETHERNET Config Netmask 2 MVIBBEMNETCRETHERNET Config Netmask 3 MVIBBEMNETCRETHERNET Canfig Gateway MVIBBEMNETCRETHERNET Config Gateway 0 MVIBBEMNETCRETHERNET Config Gateway 1 MVIBBEMNETCRETHERNET Config Gateway 2 MVIBBEMNETCRETHERNET Config Gateway 3 oi Em mmm ble le ls ajoj ojo i Qi 9 i en on Rib e uw 5 To check the status of the message refer to the WRITEETHERNETMSG tag WRITEETHERNETMSG WRITEETHERNETMSG Flags WRITEETHERNETMSG EW WRITEETHERNETMSG ER WRITEETHERNETMSG DN WRITEETHERNETMSG ST WRITEETHERNETMSG EN WRITEETHERNETMSG TO WRITEETHERNETMSG EN_CC WRITEETHERNETMSG ERR WRITEETHERNETMSG EXERR WRITEETHERNETMSG ERR_SRC WRITEETHERNETMSG DN_LEN 10 D 0 1 16 0000 16 0000_0000 0 0 ProSoft Technology Inc June 14 2011 Page 139 of 159 Reference MVI56E MNETCR ControlLogix Platform User Manual Modbus TCP IP Multi Client Enhanced Communications Module for Remote Chassis 5 6 6 Reading the Clock Value from the Module Expand the controller tag and move a value of 1 to MVIB6EMNETCRCLOCK READ TET MVIBBEMNETCRCLOCK Read MVI
66. Command Control status page 75 CmdControlTrigger BOOL Initiates Command Control CmdControlPending BOOL Halts rung until Module is ready IPAddress MNETCRIPADDRESS IP address statistics including triggers page 75 WriteCmdBits INT 30 Selects individual clients to to activate its commands Event Command Data Object MNETCREVENTCMD The Event object is not placed in the module definition object and is only required when event commands are utilized in the application This structure holds the information required for an event command An array of these objects should be defined and hold the event command set to be employed in the application The following illustration shows the structure of the object Name Data Type Description IPO INT First digit of IP address IP1 INT Second digit of IP address IP2 INT Third digit of IP address IP3 INT Last digit of IP address ServPort INT TCP Service Port number 0 65535 502 for MBAP 2000 for MNET SlvAddrNode INT Modbus slave node address 0 to 247 DBAddress INT Module internal database to use with message Count INT Register or data point count Swap INT Swap code to use with functions 3 and 4 MBFunction INT Modbus function code for message Address INT Address to interface with in device Page 74 of 159 ProSoft Technology Inc June 14 2011 MVI56E MNETCR 4 ControlLogix Platform Ladder Logic Modbus TCP IP Multi Client Enhanced Co
67. Definition Action Required MVIS6E MNETR 3 Inthe Product Line Filter area of the dialog box select MVI56E In the SELECT MODULE TYPE dropdown list select MVIS6E MNETCR and then click OK to save your settings and return to the ProSoft Configuration Builder window Page 48 of 159 ProSoft Technology Inc June 14 2011 MVI56E MNETCR ControlLogix Platform Configuring the MVIBG6E MNETCR Module Modbus TCP IP Multi Client Enhanced Communications Module for Remote Chassis User Manual 2 1 2 Renaming PCB Objects Notice that the contents of the information pane and the configuration pane changed when you added the module to the project f Untitled ppf ProSoft Configuration Builder Ele View Project Tools Help Default Project Name Status Information Default Location MVISGE MNETCR Configured MVIS6E MNETCR E MVIS6E MTER 2 04 Module Module Values OK gf MNET Client 0 MNet Client 0 Values OK MNET Client 1 amp 4 MNET Client 2 9 285 MNET Client 3 48 MNET Client 4 9 48 MNET Client 5 9 3 MNET Client 6 Module Information Client 7 Last Change Never i i MNET Client 8 Last Download Never l MNET Client 9 Application Rev MNET Client 10 qe sa MNET Client 11 MAC Address fH gy MNET Client 12 configEdit version 2 1 9 Build 1 MNET Client 13 9 48 MNET Client 14 EtherNet Configuration 9 58 fy MNET Clent 1
68. IO Scanner 1756 DH Bridge RIO Scanner 1756 DeviceNet Scanner 1756 10 100 Mbps Ethernet Bridge Fiber Media 1756 10 100 Mbps Ethernet Bridge Twisted Pair Media 1756 10 100 Mbps Ethernet Bridge Fiber Media 1756 10 100 Mbps Ethernet Bridge Twisted Pair Media 1756 Ethernet Communication Interface Allen Bradi 1756 Ethernet Communication Interface Allen Bradl 1756 10 100 Mbps Ethernet Bridge w Enhanced Web Serv gt gt gt lt lt Allen Bradley ley ley ley SynchLink Interface Allen Brad Find Add Favorite Favorites ley Note If you are prompted to Select Major Revision choose the lower of the available revision numbers ProSoft Technology Inc June 14 2011 Page 27 of 159 Start Here MVI56E MNETCR 4 ControlLogix Platform User Manual Modbus TCP IP Multi Client Enhanced Communications Module for Remote Chassis 3 Name the ENBT A module then set the IP Address and slot location in the local rack with the ControlLogix processor New Module Type 1756 ENBT A 1756 10 100 Mbps Ethemet Bridge Twisted Pair Media Vendor Allen Bradley Parent Local Name Local ENBT1 Address Host Name Description P Address 192 168 10 120 C HostName Slot 1 E Revision 1 B 1 Electronic Keying Compatible Keying v Open Module Properties Cancel Help 4 Click OK 5 Next select the
69. Inc Page 123 of 159 June 14 2011 Reference MVI56E MNETCR 4 ControlLogix Platform User Manual Modbus TCP IP Multi Client Enhanced Communications Module for Remote Chassis 5 5 6 Preset Single Register Function Code 06 Query Function 06 allows the user to modify the contents of a holding register Any holding register that exists within the controller can have its contents changed by this message However because the controller is actively scanning it also can alter the content of any holding register at any time The values are provided in binary up to the maximum capacity of the controller unused high order bits must be set to zero When used with Server address zero Broadcast mode all Server controllers will load the specified register with the contents specified Note Functions 5 6 15 and 16 are the only messages that will be recognized as valid for broadcast Adr Func DataStart Reg DataStartReg Data of Regs Hi Data ofRegsLo Error Check Field Hi Lo 11 06 00 01 00 03 CRC Response The response to a preset single register request is to re transmit the query message after the register has been altered Adr Func DataRegHi DataRegLo DatalnputRegHi Data Input RegLo Error Check Field 11 06 00 01 00 03 CRC Page 124 of 159 ProSoft Technology Inc June 14 2011 MVI56E MNETCR ControlLogix Platform Reference Modbus TCP IP Multi Client Enhanced Communications Module for Remote Chassis User Man
70. MESSAGE Use Existing WRITEETHERNETMSG MESSAGE Use Existing Page 134 of 159 ProSoft Technology Inc June 14 2011 MVI56E MNETCR ControlLogix Platform Modbus TCP IP Multi Client Enhanced Communications Module for Remote Chassis Reference User Manual The Add On Instruction will be now visible in the ladder logic Observe that the procedure has also imported data types and controller tags associated to the Add On Instruction f RSLogix 5000 ControlLogix in MVIS6EMNETCR_v16 ACD 1756 L63 MainProgram MainRoutine Ele Edit View Search Logic Communications Tools Window Help alsm al uner intoutputData Trig v c gr alal Offline No Forces D RUN p Sox gu Vi BAT nie 7 No Edits renes gt oy 4 e orites f Add On seele Controller Tags Controller Fault Handler Power Up Handler c Tasks 5 68 MainTask amp MainProgram Program Tags E MainRoutine Unscheduled Programs 21 5 Motion Groups Ungrouped Axes 1 65 Add On Instructions Q3 OPTIONAL AOISEMNETCR amp Data Types GB User Defined MNETCRBLOCKSTATS MNETCRCLIENTSTATS MNETCRCLOCKTYPE MNETCRCMDCONTROL MNETCRCONTROL MNETCRDATA MNETCRDATETIME MNETCRETHERNET MNETCRETHERNETTYPE MNETCREVENTCMD MNETCRIPADDRESS MNETCRMODULEDEF MNETCRSTATUS MNETCRUTIL ce 08 Strings f yg Add On Defined jg Predefined
71. Module Slot Number slot number where the destination MVI56E module is located To use the ClPconnect Path Editor follow these steps 1 Configure the path between the 1756 ENBT connected to your PC and the MVI56E MNETCR module o l fthe module is located in a remote rack add more racks to configure the full path o path can only contain ControlNet or Ethernet IP networks o maximum number of supported racks is six 2 Click CONSTRUCT CIP PATH to build the path in text format 3 Click OK to confirm the configured path The following examples should provide a better understanding on how to set up the path for your network Page 64 of 159 ProSoft Technology Inc June 14 2011 MVI56E MNETCR 4 ControlLogix Platform Configuring the MVIBG6E MNETCR Module Modbus TCP IP Multi Client Enhanced Communications Module for Remote Chassis User Manual 2 3 1 Example 1 Local Rack Application For this example the MVIS6E MNETCR module is located in the same rack as the 1756 ENBT that is connected to the PC MVI56E Module 1756 ENBT Ethernet Rack 1 Slot Module Network Address 0 ControlLogix Processor 1 Any 2 MVI56E MNETCR 3 1756 ENBT IP 192 168 0 100 1 Inthe Download dialog box click CIP PATH EDIT Download files from PC to module STEP 1 Select Communication Path Select Connection Type 1756 ENBT fig Ethernet CIPconnect 192 168 0 100 1 5 0 Path Edit STEP
72. NET Config Gateway 2 MVIBBEMNETCRETHERNET Config Gateway 3 o le lo 8 The bit will be automatically reset and the current Ethernet settings will be copied MVIS6EMNETCRETHERNET controller tag as follows MVIBBEMNETCRETHERNET dom MVIBBEMNETCRETHERNET Read MVISBEMNETCRETHERNET Write MVIBBEMNETCRETHERNET Config ls MVIBBEMNETCRETHERNET Config IP deme MVIBBEMNETCRETHERNET Config IP 0 1 MVIBBEMNETCRETHERNET Config IP 1 1 MVIBBEMNETCRETHERNET Config IP 2 MVIBBEMNETCRETHERNET Config IP 3 12 MVIBBEMNETCRETHERNET Config Netmask ei MVIBBEMNETCRETHERNET Config Netmask 0 255 MVIBBEMNETCRETHERNET Config Netmask 1 MVIBBEMNETCRETHERNET Config Netmask 2 MVIBBEMNETCRETHERNET Config Netmask 3 MVI56EMNETCRETHERNET Config Gateway ec MVI56EMNETCRETHERNET Config Gateway 0 192 MVIBEEMNETCRETHERNET Config Giateway 1 16 MVIBEEMNETCRETHERNET Config Gateway 2 0 MVIBEEMNETCRETHERNET Config Gateway 3 F To check the status of the message refer to the READETHERNETMSG tag Ded READETHERNETMSG Flags 1680200 READETHERNETMSG EW 0 READETHERNETMSG ER 0 READETHERNETMSG DN 0 READETHERNETMSG ST 0 READETHERNETMSG EN 0 READETHERNETMSG TO 0 READETHERNETMSG EN CC 1 READETHERNETMSG ERR 1640000 READETHERNETMSG EXERR 16 0000_0000 READETHERNETMSG ERR SRC 0 READETHERNETMSG DN LEN 0 Page 138 of 159 ProSoft Technology Inc
73. OHS 6 66 Wu pcs 243333 E183151 06 Class Division 2 Groups B C and D Temp Code T5 3 G Ex nA nL IIC T5 X 0 lt Ta lt 60 Il Equipment intended for above ground use not for use in mines 3 Category equipment investigated for normal operation only G Equipment protected against explosive gasses MVI56E MNETCR 4 ControlLogix Platform Contents Modbus TCP IP Multi Client Enhanced Communications Module for Remote Chassis User Manual Contents Your Feedback Please une tei cette eee ei ebbe ade en pe d re 2 How to eb eee a etai be e ated 2 ProSoft Technology Product 2 Battery bife AdViSOty et ire nee gr tele ie indo eere Sotto Rid 3 Important Safety Information 3 1 Start Here 9 1 1 Whats sien Pa tpe oti tee b et te e to Ets 10 1 2 System REQUIFEMENIS eere t ae e n ee edo De 11 1 3 Package Contents tate orte eel 12 1 4 Setting JUM ee eiat 13 14 1 5 1 6 Installing the Configuration 1 2422 0100 16 1 6 1 Installing ProSoft Configuration Builder 222 24 42 4 16 1 7 Connecting Your PC to the Module sse enne 17
74. P IP Multi Client Enhanced Communications Module for Remote Chassis 6 1 2 Returning Units Under Warranty A Technical Support Engineer must approve the return of Product under ProSoft Technology s Warranty a A replacement module will be shipped and invoiced A purchase order will be required b Credit for a product under warranty will be issued upon receipt of authorized product by ProSoft Technology at designated location referenced on the Return Material Authorization i lf a defect is found and is determined to be customer generated or if the defect is otherwise not covered by ProSoft Technology s warranty there will be no credit given Customer will be contacted and can request module be returned at their expense ii If defect is customer generated and is repairable customer can authorize ProSoft Technology to repair the unit by providing a purchase order for 30 of the current list price plus freight charges duties and taxes as applicable 6 1 3 Returning Units Out of Warranty a Customer sends unit in for evaluation to location specified by ProSoft Technology freight prepaid b If no defect is found Customer will be charged the equivalent of 100 USD plus freight charges duties and taxes as applicable A new purchase order will be required If unit is repaired charge to Customer will be 30 of current list price USD plus freight charges duties and taxes as applicable A new purchase order will be required
75. User Manual MVI56E MNETCR 4 ControlLogix Platform Modbus TCP IP Multi Client Enhanced Communications Module for Remote Chassis 4 2 5 Monitoring Database Information Use the DATABASE menu to view the contents of the MVIS6E MNETCR module s internal database The data locations on this menu corresponds with the MVI56E MNETCR Database Definition You can view data in the following formats DATABASE DISPLAY 0 to 99 ASCII ER2 0104092101 8211 8 5 8 5 8 5 Decimal DATABASE DISPLAY 0 to 99 DECIMAL Refresh counter 24 0 5520 17229 21061 11826 12592 13360 14640 12594 12592 892 0 3566 3567 0 0 0 0 2 0 3566 3567 0 0 0 0 28075 28074 28074 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 Float DATABASE DISPLAY 0 to 49 FLOAT Refresh counter 8 1 42363105 028 2 11809419 011 2 56376298 009 1 68041093E 004 2 56393351E 009 1 25976732 042 1 71398323E 030 0 000000005 000 0 000000005 000 7 2 1 71398323E 030 0 00000000E 000 0 000000005 000 1 08282789E 034 4 30548953E 041 0 00000000 000 0 000000005 000 0 00000000 000 0 00000000E 000 0 00000000 000 0 00000000 000 0 00000000 000 0 00000000 000 0 00000000 000 0 0 0 00000000 000 0 00000000 000 0 00000000 000 0 00000000 000 0 00000000 000 0 00000000 000 0 00000000 000 0 00000000 000 0 00000000 000 0 00000000 00 0 00000000 000
76. a Areas must be configured to occupy separate address ranges in module memory and should not be allowed to overlap Read Register Count 0 to 5000 The Read Register Count parameter specifies the size of the Read Data area of module memory and the number of registers to transfer from this area to the processor up to a maximum of 5000 words Note Total Read Register Count and Write Register Count cannot exceed 5000 total registers Read Data and Write Data Areas must be configured to occupy separate address ranges in module memory and should not be allowed to overlap Page 50 of 159 ProSoft Technology Inc June 14 2011 MVI56E MNETCR ControlLogix Platform Configuring the MVI56E MNETCR Module Modbus TCP IP Multi Client Enhanced Communications Module for Remote Chassis User Manual Write Register Start 0 to 4999 The Write Register Start parameter specifies the start of the Write Data area in module memory Data in this area will be transferred in from the processor Note Total user database memory space is limited to the first 5000 registers of module memory addresses 0 through 4999 Therefore the practical limit for this parameter is 4999 minus the value entered for Write Register Count so that the Write Data Area does not try to extend above address 4999 Read Data and Write Data Areas must be configured to occupy separate address ranges in module memory and should not be allowed to overlap Write Register Count 0 to 5000
77. and flexibility for industrial networks the MODBUS TCP protocol allows for remote administration and control of devices over an Internet connection It is important to note that not all Internet protocols are implemented in the module for example HTTP and SMTP protocols are not available Nevertheless the efficiency scalability and low cost of a MODBUS TCP network make this an ideal solution for industrial applications The MVI56E MNETCR module acts as an input output module between devices on a MODBUS TCP network and the Rockwell Automation backplane The module uses an internal database to pass data and commands between the processor and the server devices on the MODBUS TCP network ProSoft Technology Inc Page 97 of 159 June 14 2011 Reference MVI56E MNETCR 4 ControlLogix Platform User Manual Modbus TCP IP Multi Client Enhanced Communications Module for Remote Chassis 5 2 2 Backplane Data Transfer The MVI56E MNETCR module communicates directly over the ControlLogix backplane Data is paged between the module and the ControlLogix processor across the backplane using the module s input and output images The update frequency of the images is determined by the scheduled scan rate defined by the user for the module and the communication load on the module Typical updates are in the range of 1 to 10 milliseconds This bi directional transference of data is accomplished by the module filling in data in the module s input image to s
78. at should be sized to match the value entered in the WRITE REGISTER COUNT parameter of the CFG file or in PCB page 51 For ease of use both this array and the WRITE REGISTER COUNT parameter should be dimensioned in even increments of 40 words This data is paged up to 40 words at a time from the processor to the module The WriteData ladder logic task gets the data from the proper position in the MNETCR DATA WriteData and puts that data into the output image for transfer to the module Once the data has been stored in the module s database it is available for use as status and control information by other nodes on the network ProSoft Technology Inc Page 73 of 159 June 14 2011 Ladder Logic User Manual MVI56E MNETCR 4 ControlLogix Platform Modbus TCP IP Multi Client Enhanced Communications Module for Remote Chassis 3 1 2 Command Control Data Object MNETCCONTROL Values used by program for data transfer operation between the module and the processor Name Data Type Description BootTimer TIMER Timer used to clear both cold and warm boot requests WarmBoot BOOL Hardware reset of the Module ColdBoot BOOL Configuration data reset in the Module EventCmdTrigger BOOL Initiates Event Command EventCmdPending BOOL Allows Event Command ClientID INT Client ID to poll a server with the Event Command EventCmd MNETCREVENTCMD Holds Event Command configuration page 74 CmdControl MNETCRCMDCONTROL Holds
79. ath Ethernet 10 1 1 219 If there is no response from the module ProSoft Configuration Builder Page 20 of 159 ProSoft Technology Inc June 14 2011 MVI56E MNETCR ControlLogix Platform Start Here Modbus TCP IP Multi Client Enhanced Communications Module for Remote Chassis User Manual 1 Click the SET UP CONNECTION button to browse for the module s IP address Click to set up connection 2 Onthe Connection Setup dialog box click the TEST CONNECTION button to verify if the module is accessible with the current settings Connection Setup Select Connection Type 21727 Ethernet 192 168 0 250 ProSoft Discovery Service PDS Browse Device s CIPconnect EE Test Connection Cancel 3 If PCB is still unable to connect to the module click the BROWSE DEVICE S button to open the ProSoft Discovery Service 4 Select the module then right click and choose ASSIGN TEMPORARY IP Device Details Remove Temporary View module s webpage Select for PCB Click the search icon to begin the browse ProSoft Technology Inc Page 21 of 159 June 14 2011 Start Here MVI56E MNETCR ControlLogix Platform User Manual Modbus TCP IP Multi Client Enhanced Communications Module for Remote Chassis 5 The module s default IP address is 192 168 0 250 Assign Temporary Address DER Temporary IP 192 168 0 250 0 Network Mask 255 255 255 6 Ch
80. attery For modules manufactured before that date the following applies The module uses a rechargeable Lithium Vanadium Pentoxide battery to back up the real time clock and CMOS settings The battery itself should last for the life of the module However if left in an unpowered state for 14 to 21 days the battery may become fully discharged and require recharging by being placed in a powered up ControlLogix chassis The time required to fully recharge the battery may be as long as 24 hours Once it is fully charged the battery provides backup power for the CMOS setup and the real time clock for approximately 21 days Before you remove a module from its power source ensure that the battery within the module is fully charged the BATT LED on the front of the module goes OFF when the battery is fully charged If the battery is allowed to become fully discharged the module will revert to the default BIOS and clock settings Note The battery is not user replaceable or serviceable Important Safety Information MVI56E Modules North America Warnings A Warning Explosion Hazard Substitution of components may impair suitability for Class 1 Division 2 B Warning Explosion Hazard When in hazardous locations turn off power before replacing or rewiring modules Warning Explosion Hazard Do not disconnect equipment unless power has been switched off or the area is known to be nonhazardous C Suitable for use in Class Division 2 Groups
81. b Page 24 Connecting Your PC to the ControlLogix Processor 43 Connecting Your PC to the Module 17 Contacting Technical Support 147 149 Controlling Law and Severability 155 Create the Module Local Rack 26 31 Create the Module Remote Rack 29 Create the Remote Network 27 30 Creating a New RSLogix 5000 Project 26 D Data Flow between MVI56E MNETCR Module Processor and Network 111 Diagnostics Function Code 08 5 Diagnostics and Troubleshooting 79 80 Disclaimer of all Other Warranties 153 Disclaimer Regarding High Risk Activities 152 Downloading the Project to the Module 62 Downloading the Sample Program to the Processor 43 144 Duplex Speed Code 52 E Enable 56 Error Status Pointer 50 52 91 Ethernet Cable Configuration 116 Ethernet Cable Specifications 116 Ethernet Configuration 61 Ethernet LED Indicators 81 Ethernet Performance 117 Event Command Blocks 2000 to 2029 103 Event Command Data Object MNETCREVENTCMD 74 Example 1 Local Rack Application 65 Example 2 Remote Rack Application 68 Example and state diagram 125 F Failure Flag Count 51 Float Flag 53 Float Offset 53 Float Start 53 Force Multiple Coils Function Code 15 127 Force Single Coil Function Code 05 123 Functional Overview 97 Functional Specifications 95 ProSoft Technology Inc June 14 2011 Page 157 of 159 MVI56E MNETCR 4 ControlL
82. ber of registers to be transferred by the command Swap Code NONE SWAP WORDS SWAP WORDS amp BYTES SWAP BYTES This parameter defines if and how the order of bytes in data received or sent is to be rearranged This option exists to allow for the fact that different manufacturers store and transmit multi byte data in different combinations This parameter is helpful when dealing with floating point or other multi byte values as there is no one standard method of storing these data types The parameter can be set to rearrange the byte order of data received or sent into an order more useful or convenient for other applications The following table defines the valid Swap Code values and the effect they have on the byte order of the data Swap Code Description NONE No change is made in the byte ordering 1234 1234 SwAP WORDS The words are swapped 123423412 Swap Worps amp BYTES The words are swapped then the bytes in each word are swapped 123424321 Swap 5 The bytes in each word are swapped 1234 2143 These swap operations affect 4 byte or 2 word groups of data Therefore data swapping using these Swap Codes should be done only when using an even number of words such as when 32 bit integer or floating point data is involved ProSoft Technology Inc Page 57 of 159 June 14 2011 Configuring the MVIS56E MNETCR Module MVI56E MNETCR ControlLogix Platform User Manual Modbus TCP IP Multi Client Enhanced Communi
83. can examine the data field for the exception code Data Field In a normal response the server may return data or statistics in the data field any information that was requested in the request In an exception response the server returns an exception code in the data field This defines the server condition that caused the exception The following table shows an example of a Client request and server exception response Request Response Field Name Hex Field Name Hex Function 01 Function 81 Starting Address Hi 04 Exception Code 02 Starting Address Lo A1 Quantity of Outputs Hi 00 Quantity of Outputs Lo 1 In this example the Client addresses a request to server device The function code 01 is for a Read Output Status operation It requests the status of the output at address 1245 04A1 hex Note that only that one output is to be read as specified by the number of outputs field 0001 ProSoft Technology Inc Page 129 of 159 June 14 2011 Reference User Manual MVI56E MNETCR 4 ControlLogix Platform Modbus TCP IP Multi Client Enhanced Communications Module for Remote Chassis If the output address is non existent in the server device the server will return the exception response with the exception code shown 02 This specifies an illegal data address for the Server Modbus Exception Codes Code Name Meaning 01 Illegal Function The function code received in the quer
84. cations Module for Remote Chassis Node IP Address XXX XXX XXX XXX The IP address of the device being addressed by the command Service Port 502 or other supported ports on server Use a value of 502 when addressing Modbus TCP IP servers that are compatible with the Schneider Electric MBAP specifications this will be most devices If a server implementation supports another service port enter the value here Slave Address 0 Broadcast to all nodes 1 to 255 Use this parameter to specify the slave address of a remote Modbus Serial device through a Modbus Ethernet to Serial converter Note Use the Node Address parameter page 58 to address commands to a remote Modbus TCP IP device Note Most Modbus devices accept an address in the range of only 1 to 247 so check with the slave device manufacturer to see if a particular slave can use addresses 248 to 255 If the value is set to zero the command will be a broadcast message on the network The Modbus protocol permits broadcast commands for write operations Do not use node address 0 for read operations Modbus Function 1 2 3 4 5 6 15 or 16 This parameter specifies the Modbus Function Code to be executed by the command These function codes are defined in the Modbus protocol The following table lists the purpose of each function supported by the module More information on the protocol is available from www modbus org Modbus Fun
85. cators 81 Normal Data Transfers 100 0 Overview 2 P Package Contents 12 Pinouts 96 116 Poll Interval 57 Preset Multiple Registers Function Code 16 128 Preset Single Register Function Code 06 124 Printing a Configuration File 49 Product Specifications 94 ProSoft Technology Product Documentation 2 R Read Coil Status Function Code 01 118 Read Holding Registers Function Code 03 121 Read Input Registers Function Code 04 122 Read Input Status Function Code 02 120 Read Register Count 73 Read Register Start 50 Reading Status Data from the Module 91 Reading the Clock Value from the Module 140 Reading the Ethernet Settings from the Module 138 Reference 93 Reg Count 57 Renaming PCB Objects 49 Response Timeout 52 Retry Count 53 Return Material Authorization RMA Policies and Conditions 149 Returning Any Product 149 Returning Units Out of Warranty 150 Returning Units Under Warranty 150 S Scrolling LED Status Indicators 80 Service Port 58 Setting Jumpers 13 Setting Temporary IP Address 18 24 Setting Up the Project 47 Slave Address 58 Special Function Blocks 99 102 Standard Modbus Exception Code Errors 114 Start Here 9 Static ARP 88 Static ARP Table 60 88 Status 89 Status Data Block Structure 101 Status Object MNETCRSTATUS 72 75 Status Read Data Block IDs 0 and 1 101 Sub fun
86. ced Communications Module for Remote Chassis User Manual Event Command Blocks 2000 to 2029 Event command control blocks send Modbus TCP IP commands directly from the ladder logic to one of the clients on the module The following table describes the format of these blocks Offset Description Length 0 2000 to 2029 1 1 4 IP Address 4 5 Service Port 1 6 Slave Address 1 7 Internal DB Address 1 8 Point Count 1 9 Swap Code 1 10 Modbus Function Code 1 11 Device Database Address 1 12 to 41 Spare 30 Use the parameters passed with the block to construct the command The IP Address for the node to reach on the network is entered in four registers 1 to 4 Each digit of the IP address is entered in the appropriate register For example to interface with node 192 168 0 100 enter the values 192 168 0 and 100 in registers 1 to 4 The Service Port field selects the TCP service port on the server to connect If the parameter is set to 502 a standard MBAP message will be generated All other service port values will generate a Modbus command message encapsulated in a TCP IP packet The Internal DB Address parameter specifies the module s database location to associate with the command The Point Count parameter defines the number of points or registers for the command The Swap Code is used with Modbus functions 3 and 4 requests to change the word or byte order The Modbus Function Code has one of th
87. ch 32 bit floating point value it expects to receive or send or if you do not plan to use floating point data in your application then set this parameter to No which is the default setting You will also need to set the F oat Start and Float Offset parameters to appropriate values whenever the Float Flag parameter is set to YES Float Start 0 to 65535 This parameter defines the first register of floating point data All requests with register values greater than or equal to this value will be considered floating point data requests This parameter is only used if the Float Flag is enabled For example if a value of 7000 is entered all requests for registers 7000 and above will be considered as floating point data Float Offset 0 to 9999 This parameter defines the start register for floating point data in the internal database This parameter is used only if the Float Flag is enabled For example if the Float Offset value is set to 3000 and the Float Start parameter is set to 7000 data requests for register 7000 will use the internal Modbus register 3000 ARP Timeout 1 to 60 This parameter specifies the number of seconds to wait for an ARP reply after a request is issued ProSoft Technology Inc Page 53 of 159 June 14 2011 Configuring the MVIBGE MNETCR Module MVI56E MNETCR ControlLogix Platform User Manual Modbus TCP IP Multi Client Enhanced Communications Module for Remote Chassis Command Error Delay 0 to 30
88. controller can also alter the state of the coil Coils are numbered from zero coil 00001 zero coil 00002 one so on The desired status of each coil is packed in the data field one bit for each coil 12 ON 0 OFF The use of Server address 0 Broadcast Mode will force all attached Servers to modify the desired coils Note Functions 5 6 15 and 16 are the only messages other than Loopback Diagnostic Test that will be recognized as valid for broadcast The following example forces 10 coils starting at address 20 13 HEX The two data fields CD 21100 and 00 0000 000 indicate that coils 27 26 23 22 20 are to be forced on Adr Func HiAdd 10 Quantity Byte Data Coil Status Data Coil Status Error Check Add Cnt 20 to 27 28 to 29 Field 11 OF 00 13 00 0A 02 CD 00 CRC Response The normal response will be an echo of the Server address function code starting address and quantity of coils forced Adr Func Hi Addr Lo Addr Quantity Error Check Field 11 OF 00 13 00 0A CRC The writing of coils via Modbus function 15 will be accomplished regardless of whether the addressed coils are disabled or not Coils that are in the controller logic program are not automatically cleared upon power up Thus if such a coil is set ON by function code 15 and even months later an output is connected to that coil the output will be hot ProSoft Technology Inc Page 127 of 159 J
89. ction Module Info Backplane Requested Packet Interval RPI ms 0 2 750 0 ms Inhibit Module Major Fault On Controller If Connection Fails While in Run Mode Module Fault Status Offline Cancel Help The MVI56E MNETCR module is now visible the I O CONFIGURATION pane amp Controller My Controller Controller Tags Controller Fault Handler Power Up Handler Tasks 5 a MainTask C MainProgram Unscheduled Programs Motion Groups Ungrouped Axes Add On Instructions Data Types User Defined Strings GR Add On Defined 8 Predefined i Module Defined 28 Trends 2 5 1 0 Configuration 1756 Backplane 1756 A7 0 1756 163 My Controller g Page 32 of 159 ProSoft Technology Inc June 14 2011 MVI56E MNETCR 4 ControlLogix Platform Modbus TCP IP Multi Client Enhanced Communications Module for Remote Chassis Start Here User Manual 1 11 2 Import Add On Instruction 1 Inthe CONTROLLER ORGANIZATION window expand the TASKS folder and subfolder until you reach the MAINPROGRAM folder 2 Inthe MAINPROGRAM folder double click to open the MAINROUTINE ladder 3 Select an empty rung in the new routine and then click the right mouse button to open a shortcut menu On the shortcut menu choose IMPORT RUNG f RSLogix 5000 Controller 1756 L63 MainProgram MainRoutine Ele Edit view Search Logic Communications Too
90. ction Code Description 1 Read Coil Status 2 Read Input Status 3 Read Holding Registers 4 Read Input Registers 5 Force Write Single Coil 6 Preset Write Single Register 15 Force Multiple Coils 16 Preset Multiple Registers Page 58 of 159 ProSoft Technology Inc June 14 2011 MVI56E MNETCR 4 ControlLogix Platform Configuring the MVI56E MNETCR Module Modbus TCP IP Multi Client Enhanced Communications Module for Remote Chassis User Manual MB Address in Device This parameter specifies the starting Modbus register or bit address in the Server to be used by the command Refer to the documentation of each Modbus Server device for the register and bit address assignments valid for that device The Modbus Function Code determines whether the address will be a register level or bit level OFFSET address into a given data type range The offset will be the target data address in the Server minus the base address for that data type Base addresses for the different data types are 00001 or 000001 0x0001 for bit level Coil data Function Codes 1 5 and 15 10001 or 100001 1x0001 for bit level Input Status data Function Code 2 30001 or 300001 3x0001 for Input Register data Function Code 4 40001 or 400001 4x0001 for Holding Register data Function Codes 3 6 and 16 Address calculation examples For bit level Coil commands FC 1 5 or 15 to read or write a Coil OX address 00001 specify a value of 0 00001 00001 0
91. ction codes supported 5 Support Service amp Warranty 147 Swap 0006 57 System Requirements 11 T The Diagnostics Menu 87 Time Limit for Bringing Suit 4 Troubleshooting 82 Page 158 of 159 ProSoft Technology Inc June 14 2011 MVI56E MNETCR 4 ControlLogix Platform Support Service amp Warranty Modbus TCP IP Multi Client Enhanced Communications Module for Remote Chassis User Manual U Uploading the Add On Instruction from the Module 25 34 User Data Object MNETCRDATA 72 73 Using ClPconnect to Connect to the Module 22 85 117 Using ClPconnect to Connect to the Module 63 85 117 Using ProSoft Configuration Builder Software 46 Using the Diagnostics Menu in ProSoft Configuration Builder 84 Using the Optional Add On Instruction Rung Import 132 Using the Sample Program RSLogix 5000 Version 15 and earlier 25 145 V Version 87 What Is Covered By This Warranty 151 153 What Is Not Covered By This Warranty 152 What s New 10 Write Register Count 51 73 Write Register Start 51 Writing the Clock Value to the Module 141 Writing the Ethernet Settings to the Module 139 Y Your Feedback Please 2 ProSoft Technology Inc Page 159 of 159 June 14 2011
92. database address in the module s internal database to use as the destination for data brought in by a read command or as the source for data to be sent out by a write command The database address is interpreted as a bit address or a 16 bit word register address depending on the Modbus Function Code used in the command For Modbus functions 1 2 5 and 15 this parameter is interpreted as a bit level address For Modbus functions 3 4 6 and 16 this parameter is interpreted as a word or register level address Page 56 of 159 ProSoft Technology Inc June 14 2011 MVI56E MNETCR 4 ControlLogix Platform Configuring the MVI56E MNETCR Module Modbus TCP IP Multi Client Enhanced Communications Module for Remote Chassis User Manual Poll Interval 0 to 65535 This parameter specifies the minimum interval to execute continuous commands Enable code of 1 The parameter is entered in tenths of a second Therefore if a value of 100 is entered for a command the command executes no more frequently than every 10 seconds Count Regs 1 to 125 Coils 1 to 800 This parameter specifies the number of 16 bit registers or binary bits to be transferred by the command Functions 5 6 ignore this field as they apply only to a single data point For functions 1 2 and 15 this parameter sets the number of bits inputs or coils to be transferred by the command For functions 4 and 16 this parameter sets the num
93. dress to connect with a module s web page ClPconnect enabled Allows PC to module configuration and diagnostics from the Ethernet network through a ControlLogix 1756 ENBT EtherNet IP module Personality Module An industrial compact flash memory card storing the module s complete configuration and Ethernet settings allowing quick and easy replacement LED Scrolling Diagnostic Display 4 character alphanumeric display providing standard English messages for status and alarm data and for processor and network communication status Page 10 of 159 ProSoft Technology Inc June 14 2011 MVI56E MNETCR 4 ControlLogix Platform Start Here Modbus TCP IP Multi Client Enhanced Communications Module for Remote Chassis User Manual 1 2 System Requirements The MVI56E MNETCR module requires the following minimum hardware software components Rockwell Automation ControlLogix processor firmware version 10 or higher with compatible power supply and one free slot in the rack for the MVI56E MNETCR module The module requires 800 mA of available 5 Vdc power Rockwell Automation RSLogix 5000 programming software o Version 16 or higher required for Add On Instruction o Version 15 or lower must use Sample Ladder available from www prosoft technology com Rockwell Automation RSLinx communication software version 2 51 or higher ProSoft Configuration Builder PCB included ProSoft Discovery Service PDS included in
94. dule to the project Select the I O CONFIGURATION folder in the CONTROLLER ORGANIZATION window and then click the right mouse button to open a shortcut menu On the shortcut menu choose NEW MODULE Controller Controller Tags Controller Fault Handler Power Up Handler Tasks fa MainTask Cg MainProgram Unscheduled Programs Motion Groups Ungrouped Axes Add On Instructions 3 6 Data Types 048 User Defined Ga Strings Add On Defined ig Predefined a Module Defined Trends 1 0 Configuration EN ackplane TF NES This action opens the SELECT MODULE dialog box lll Select Module lodule Analog Communications Controllers Digital Drives Motion Other 1756 MODULE Generic 1756 Module Allen Bradley Specialty Find Add Favorite By Category Favorites OK Cancel Help Page 142 of 159 ProSoft Technology Inc June 14 2011 MVI56E MNETCR 4 ControlLogix Platform Modbus TCP IP Multi Client Enhanced Communications Module for Remote Chassis Reference User Manual Select the 1756 MODULE Generic 1756 Module from the list and click OK This action opens the NEw MODULE dialog box New Module Type Parent 1756 MODULE Generic 1756 Module Remote_ENBT2 Connection Parameters Assembly Instance Name ProSoft MvI56 Module Input 16 bit Description Output 16 bit Configuration 4
95. e device in the field is changed this table must be updated to contain the new MAC address for the device and downloaded to the module If the MAC is not changed no communications with the module will be provided IP Address Dotted notation This table contains a list of static IP addresses that the module will use when an ARP is required The module will accept up to 40 static IP MAC address data sets Important If the device in the field is changed this table must be updated to contain the new MAC address for the device and downloaded to the module If the MAC is not changed no communications with the module will occur Hardware MAC Address Hex value This table contains a list of static MAC addresses that the module will use when an ARP is required The module will accept up to 40 static IP MAC address data sets Important If the device in the field is changed this table must be updated to contain the new MAC address for the device and downloaded to the module If the MAC is not changed no communications with the module will occur Page 60 of 159 ProSoft Technology Inc June 14 2011 MVI56E MNETCR ControlLogix Platform Configuring the MVIBG6E MNETCR Module Modbus TCP IP Multi Client Enhanced Communications Module for Remote Chassis User Manual 2 1 7 Ethernet Configuration Use this procedure to configure the Ethernet settings for your module You must assign an IP address subnet mask and gateway address After you
96. e following values 1 2 3 4 5 6 15 or 16 The Device Database Address is the Modbus register or point in the remote slave device to be associated with the command When the module receives the block it will process it and place it in the command queue The following table describes the format of this block Word Description 0 This word contains the block 2000 identification code to indicate that this block contains a command to execute by the Client Driver 1104 These words contain the IP address for the server the message is intended Each digit 0 to 255 of the IP address is placed in one of the four registers For example to reach IP address 192 168 0 100 enter the following values in words 1 to 4 192 168 0 and 100 The module will construct the normal dotted IP address from the values entered The values entered will be anded with the mask OxOOff to insure the values are in the range of 0 to 255 ProSoft Technology Inc Page 103 of 159 June 14 2011 Reference MVI56E MNETCR 4 ControlLogix Platform User Manual Modbus TCP IP Multi Client Enhanced Communications Module for Remote Chassis Word Description 5 This word contains the TCP service port the message will be interfaced For example to interface with a MBAP device the word should contain a value of 502 To interface with a MNET device a value of 2000 should be utilized Any value from 0 to 65535 is permitted A value
97. e operation and any unusual behavior Configuration Debug status information LED patterns Details about the serial Ethernet or fieldbus devices interfaced to the module if any 50 gt Note For technical support calls within the United States an after hours answering system allows 24 hour 7 days a week pager access to one of our qualified Technical and or Application Support Engineers ProSoft Technology Inc Page 147 of 159 June 14 2011 Support Service amp Warranty MVI56E MNETCR 4 ControlLogix Platform User Manual Modbus TCP IP Multi Client Enhanced Communications Module for Remote Chassis Internet Web Site www prosoft technology com support E mail address support prosoft technology com Asia Pacific Tel 603 7724 2080 E mail asiapc prosoft technology com location in Malaysia Languages spoken include Chinese English Asia Pacific Tel 86 21 5187 7337 x888 E mail asiapc prosoft technology com location in China Languages spoken include Chinese English Europe Tel 33 0 5 34 36 87 20 location in Toulouse France E mail support EMEA prosoft technology com Languages spoken include French English Europe location in Dubai UAE Tel 971 4 214 6911 E mail mea prosoft technology com Languages spoken include English Hindi North America location in California Tel 1 661 716 5100 E mail support prosoft technology com Languages spoken include English Spanish
98. e processor and any installed I O module not just the MVI56E MNETCR Verify that all modules in the rack are correctly configured in the ladder logic Module Errors Problem description Steps to take BP ACT LED not present on MVI56E modules remains OFF or blinks slowly MVI56E modules with scrolling LED display lt Backplane Status gt condition reads ERR This indicates that backplane transfer operations are failing Connect to the module s Configuration Debug port to check this To establish backplane communications verify the following items The processor is RUN or REM RUN mode The backplane driver is loaded in the module The module is configured for read and write data block transfer The ladder logic handles all read and write block situations The module is properly configured in the processor I O configuration and ladder logic OK LED remains RED The program has halted or a critical error has occurred Connect to the Configuration Debug port to see if the module is running If the program has halted turn off power to the rack remove the card from the rack and re insert it and then restore power to the rack Page 82 of 159 ProSoft Technology Inc June 14 2011 MVI56E MNETCR ControlLogix Platform Diagnostics and Troubleshooting Modbus TCP IP Multi Client Enhanced Communications Module for Remote Chassis User Manual 4 1 5 Clearing a Fault Condition Typically i
99. ead Data area Important Because the module pages data in blocks of 200 registers at a time you must configure your user data in multiples of 200 registers Edit Module 2 modify the WriteData array follow the above steps substituting WriteData for ReadData Also make sure that the ReadData and WriteData arrays do not overlap in the module memory For example if your application requires 2000 words of WriteData starting at register 0 then your Head Register Start parameter must be set to a value of 2000 or greater in ProSoft Configuration Builder 3 Save download the sample configuration to the module It is unnecessary to manually edit the ReadData and WriteData user defined data types in the ladder logic as these are automatically updated to match the changed array sizes in ProSoft Configuration Builder Page 42 of 159 ProSoft Technology Inc June 14 2011 MVI56E MNETCR ControlLogix Platform Start Here Modbus TCP IP Multi Client Enhanced Communications Module for Remote Chassis User Manual 1 11 3 Connecting Your PC to the ControlLogix Processor There are several ways to establish communication between your PC and the ControlLogix processor The following steps show how to establish communication through the serial interface It is not mandatory that you use the processor s serial interface You may access the processor through whatever network interface is available on your system
100. ed The contents of the registers requested DATA are 2 bytes each with the binary content right justified within each pair of characters The first byte includes the high order bits and the second the low order bits Because the Server interface is normally serviced at the end of the controller s scan the data will reflect the register content at the end of the scan Each PC will limit the quantity of register contents provided each scan thus for large register quantities multiple PC scans will be required and the data provided will be form sequential scans In the example below the register 3009 contains the decimal value 0 Adr Func ByteCount Data Input Reg Hi Data Input Reg Lo Error Check Field 11 04 02 00 00 E9 Page 122 of 159 ProSoft Technology Inc June 14 2011 MVI56E MNETCR ControlLogix Platform Reference Modbus TCP IP Multi Client Enhanced Communications Module for Remote Chassis User Manual 5 5 5 Force Single Coil Function Code 05 Query This message forces a single coil either ON or OFF Any coil that exists within the controller can be forced to either state ON or OFF However because the controller is actively scanning unless the coil is disabled the controller can also alter the state of the coil Coils are numbered from zero coil 0001 zero coil 0002 one and so on The data value 65 280 FF00 HEX will set the coil ON and the value zero will turn it OFF all other values are illegal and
101. eeds PCB is not only a powerful solution for new configuration files but also allows you to import information from previously installed known working configurations to new projects Note During startup and initialization the MVIS6E MNETCR module receives its protocol and backplane configuration information from the installed Personality Module Compact Flash Use ProSoft Configuration Builder to configure module settings and to download changes to the Personality Module Page 46 of 159 ProSoft Technology Inc June 14 2011 MVI56E MNETCR ControlLogix Platform Configuring the MVI56E MNETCR Module Modbus TCP IP Multi Client Enhanced Communications Module for Remote Chassis User Manual 2 1 1 Setting Up the Project To begin start PROSOFT CONFIGURATION BUILDER PCB Set Program Access and Defaults WA Windows Catalog Windows Update Microsoft Update Accessories Administrative Tools f Programs fam ProSoft Technology ProSoft Configuration Builder B Documents 4 Internet Explorer ProSoft Transport Path Editor gt Settings Paint ProSoft Discovery Service 4 Search gt Windows Media Player Help and Support Run Shut Down 2 Start If you have used other Windows configuration tools before you will find the screen layout familiar PCB s window consists of a tree view on the left and an information pane and a configuration pane on the right side of
102. efore you will find the screen layout familiar PCB s window consists of a tree view on the left and an information pane and a configuration pane on the right side of the window When you first start PCB the tree view consists of folders for Default Project and Default Location with a Default Module in the Default Location folder The following illustration shows the PCB window with a new project f Untitled ProSoft Configuration Builder BEE Eile View Project Tools Help Default Project Name Status Default Location A Default Module Please Select Module Type Default Module Unknown Product Line Last Change Last Download Module Information Last Change Never Last Download Never Application Rev OS Rev Loader Rev MAC Address configEdit version 2 2 0 Build 1 Module configuration Module Module Type Module Name Default Module Default Module Page 18 of 159 ProSoft Technology Inc June 14 2011 Start Here MVI56E MNETCR ControlLogix Platform User Manual Modbus TCP IP Multi Client Enhanced Communications Module for Remote Chassis 3 Use the mouse to select DEFAULT MODULE in the tree view and then click the right mouse button to open a shortcut menu 4 Onthe shortcut menu select CHOOSE MODULE TYPE This action opens the Choose Module Type dialog box Choose Module Product Line Filter C PLX4000 PLx6
103. end to the processor Data in the input image is placed in the Controller Tags in the processor by the ladder logic The input image for the module is set to 42 words This data is transferred in the scheduled l O timeslot The processor inserts data to the module s output image to transfer to the module The module s program extracts the data and places it in the module s internal database The output image for the module is set to 42 words This data is transferred in the scheduled timeslot The following illustration shows the data transfer method used to move data between the ControlLogix processor the module and the Modbus TCP IP Network ControlLogix Processor MVI58 MNETCR Module Contral Tags Internal DB for Clients Write Data ier logic A j transfers data Special o ssors Control Blocks ata objects to utput image All data transferred between the module and the processor over the backplane is through the input and output images Ladder logic must be written in the ControlLogix processor to interface the input and output image data with data defined in the Controller Tags All data used by the module is stored in its internal database This database is defined as a virtual Modbus data table with addresses from 0 40001 Modbus to 4999 45000 Modbus The following illustration shows the layout of the database Module s Internal Database Structure 5000 registers for user data 0 Regis
104. errupted by other write block numbers sent by the controller or by a command request from a node on the Modbus network or operator control through the module s Configuration Debug port Block Request from Processor to Module These blocks of data transfer information from the ControlLogix processor to the module The following table describes the structure of the output image Offset Description Length 0 Write Block ID 1 1 to 40 Write Data 40 41 Spare 1 The Write Block ID is an index value used to determine the location in the module s database where the data will be placed Each transfer can move up to 40 words block offsets 1 to 40 of data Page 100 of 159 ProSoft Technology Inc June 14 2011 MVI56E MNETCR ControlLogix Platform Reference Modbus TCP IP Multi Client Enhanced Communications Module for Remote Chassis User Manual Status Read Data Block IDs 0 and 1 This block is automatically copied from the module into the MNETCR STATUS array when the block ID is 0 or 1 and contains status information about the module Offset Description Length 0 Write Block ID 1 1 Program Scan Counter 1 2107 Block Transfer Status Read Write Parse Command 6 Event and Error Counts 8 to 37 Client 0 to Client 22 Command Execution Control Bits 2 38 to 40 Reserved 17 41 Read Block ID 1 or 0 1 Status Data Block Structure This section contains a description of the members present in
105. es that no response was obtained from the target device Usually means that the device is not present on the network ProSoft Technology Inc June 14 2011 Page 131 of 159 Reference MVI56E MNETCR 4 ControlLogix Platform User Manual Modbus TCP IP Multi Client Enhanced Communications Module for Remote Chassis 5 6 Using the Optional Add On Instruction Rung Import 5 6 1 Before You Begin Make sure that you have installed RSLogix 5000 version 16 or later Download the Optional Add On file MVI56EMNETCH Optional Rung 0 L5X from the module s web page and copy it to a folder in your PC 5 6 2 Overview The Optional Add On Instruction Rung Import contains optional logic for MVIBGE MNETCR applications to perform the following tasks Read Write Ethernet Configuration Allows the processor to read or write the module IP address netmask and gateway values Note This is an optional feature You can perform the same task through PCB ProSoft Configuration Builder Even if your PC is in a different network group you can still access the module through PCB by setting a temporary IP address Read Write Module Clock Value Allows the processor to read and write the module clock settings The module clock stores the last time that the Ethernet configuration was changed The date and time of the last Ethernet configuration change is displayed in the scrolling LED during module power up Important The Optional Add
106. eter in the configuration file to set an amount of time to wait before trying again to connect to this non existent server This feature allows the Client to continue sending commands and polling other existing servers while waiting for the non existent server to appear on the network ProSoft Technology Inc Page 115 of 159 June 14 2011 Reference MVI56E MNETCR 4 ControlLogix Platform User Manual Modbus TCP IP Multi Client Enhanced Communications Module for Remote Chassis 5 4 Ethernet Cable Specifications The recommended cable is Category 5 or better A Category 5 cable has four twisted pairs of wires which are color coded and cannot be swapped The module uses only two of the four pairs The Ethernet port on the module is Auto Sensing You can use either a standard Ethernet straight through cable or a crossover cable when connecting the module to an Ethernet hub a 10 100 Base T Ethernet switch or directly to a PC The module will detect the cable type and use the appropriate pins to send and receive Ethernet signals Ethernet cabling is like U S telephone cables except that it has eight conductors Some hubs have one input that can accept either a straight through or crossover cable depending on a switch position In this case you must ensure that the switch position and cable type agree Refer to Ethernet cable configuration page 116 for a diagram of how to configure Ethernet cable 5 4 1 Ethernet Cable Configuration
107. explosion when they happen in a hazardous environment Verify that power is removed or the area is non hazardous before proceeding Repeated electrical arcing causes excessive wear to contacts on both the module and its mating connector Worn contacts may create electrical resistance that can affect module operation 1 Align the module with the top and bottom guides and then slide it into the rack until the module is firmly against the backplane connector MVI56E Module v 2 With a firm steady push snap the module into place 3 Check that the holding clips on the top and bottom of the module are securely in the locking holes of the rack Page 14 of 159 ProSoft Technology Inc June 14 2011 MVI56E MNETCR ControlLogix Platform Start Here Modbus TCP IP Multi Client Enhanced Communications Module for Remote Chassis User Manual 4 Make a note of the slot location You must identify the slot in which the module is installed in order for the sample program to work correctly Slot numbers are identified on the green circuit board backplane of the ControlL ogix rack 5 Turn power ON Note If you insert the module improperly the system may stop working or may behave unpredictably ProSoft Technology Inc Page 15 of 159 June 14 2011 Start Here MVI56E MNETCR ControlLogix Platform User Manual Modbus TCP IP Multi Client Enhanced Communications Module for Remote Chassis 1 6 Installing the Configuration Tools
108. f the OK LED on the front of the module turns RED for more than ten seconds a hardware problem has been detected in the module or the program has exited To clear the condition follow these steps 1 2 3 4 oo Turn off power to the rack Remove the card from the rack Verify that all jumpers are set correctly If the module requires a Compact Flash card verify that the card is installed correctly Re insert the card in the rack and turn the power back on Verify correct configuration data is being transferred to the module from the ControlLogix controller If the module s OK LED does not turn GREEN verify that the module is inserted completely into the rack If this does not cure the problem contact ProSoft Technology Technical Support ProSoft Technology Inc Page 83 of 159 June 14 2011 Diagnostics and Troubleshooting MVI56E MNETCR 4 ControlLogix Platform User Manual Modbus TCP IP Multi Client Enhanced Communications Module for Remote Chassis 4 2 Using the Diagnostics Menu in ProSoft Configuration Builder To connect to the module s Configuration Debug Ethernet port 1 In ProSoft Configuration Builder select the module and then click the right mouse button to open a shortcut menu gg Default Project 2 8 Default Location Demo Module 2 Onthe shortcut menu choose DIAGNOSTICS gg Default Project 8 Default Location Demo Module Delete Rename Copy Choose Module T
109. ftware launch the program configure ladder logic and transfer the ladder logic to the processor Microsoft Windows install and launch programs execute menu commands navigate dialog boxes and enter data Hardware installation and wiring install the module and safely connect Modbus TCP IP and ControlLogix devices to a power source and to the MVI56E MNETCR module s application port s ProSoft Technology Inc June 14 2011 Page 9 of 159 Start Here MVI56E MNETCR 4 ControlLogix Platform User Manual Modbus TCP IP Multi Client Enhanced Communications Module for Remote Chassis 1 1 What s New MVI56E products are backward compatible with existing MVI56 products ladder logic and module configuration files already in use Easily swap and upgrade products while benefiting from an array of new features designed to improve interoperability and enhance ease of use Web Server The built in web server and web page allow access to manuals and other tools previously provided only on a product CD ROM or from the ProSoft Technology web site ProSoft Configuration Builder PCB New Windows software for diagnostics connecting via the module s Ethernet port or to upload download module configuration information and access troubleshooting features and functions ProSoft Discovery Service PDS Utility software to find and display a list of MVI56E modules on the network and to temporarily change an IP ad
110. g Alpha Shows Module Version IP Application Port Numeric LED Display Setting Port Status and Error Information Debug Configuration Application Ethernet port E1 Ethernet Port 10 100 Base T RJ45 Connector for CAT5 cable Link and Activity LED indicators Auto crossover cable detection Shipped with Unit 5 foot Ethernet straight through cable Page 96 of 159 ProSoft Technology Inc June 14 2011 MVI56E MNETCR ControlLogix Platform Reference Modbus TCP IP Multi Client Enhanced Communications Module for Remote Chassis User Manual 5 2 Functional Overview 5 2 1 About the MODBUS TCP Protocol MODBUS is a widely used protocol originally developed by Modicon in 1978 Since that time the protocol has been adopted as a standard throughout the automation industry The original MODBUS specification uses a serial connection to communicate commands and data between client and server devices on a network Later enhancements to the protocol allow communication over Ethernet networks using TCP IP as a wrapper for the MODBUS protocol This protocol is known as MODBUS TCP MODBUS TCP is a client server protocol The client establishes a connection to the remote server When the connection is established the client sends the MODBUS TCP commands to the server The MVIS6E MNETCR module simulates up to 30 clients Aside from the benefits of Ethernet versus serial communications including performance distance
111. ge should be identical to the request Sub function Data Field Request Data Field Response 00 00 Any Echo Request Data Example and state diagram Here is an example of a request to remote device to Return Query Data This uses a sub function code of zero 00 00 hex in the two byte field The data to be returned is sent in the two byte data field A5 37 hex Request Response Field Name Hex Field Name Hex Function 08 Function 08 Sub function Hi 00 Sub function Hi 00 Sub function Lo 00 Sub function Lo 00 Data Hi A5 Data Hi A5 Data Lo 37 Data Lo 27 ProSoft Technology Inc Page 125 of 159 June 14 2011 Reference MVI56E MNETCR 4 ControlLogix Platform User Manual Modbus TCP IP Multi Client Enhanced Communications Module for Remote Chassis The data fields in responses to other kinds of queries could contain error counts or other data requested by the sub function code Page 126 of 159 ProSoft Technology Inc June 14 2011 MVI56E MNETCR ControlLogix Platform Reference Modbus TCP IP Multi Client Enhanced Communications Module for Remote Chassis User Manual 5 5 8 Force Multiple Coils Function Code 15 Query This message forces each coil in a consecutive block of coils to a desired ON or OFF state Any coil that exists within the controller can be forced to either state ON or OFF However because the controller is actively scanning unless the coils are disabled the
112. gister content from sequential scans In the example below the registers 40108 to 40110 have the decimal contents 555 0 and 100 respectively Adr Func ByteCnt LoData 10 HiData 10 08 Error Check Field 11 03 06 02 2B 00 00 00 64 CRC ProSoft Technology Inc Page 121 of 159 June 14 2011 Reference MVI56E MNETCR 4 ControlLogix Platform User Manual Modbus TCP IP Multi Client Enhanced Communications Module for Remote Chassis 5 5 4 Read Input Registers Function Code 04 Query Function code 04 obtains the contents of the controller s input registers at addresses 3xxxx These locations receive their values from devices connected to the structure and can only be referenced not altered from within the controller The addressing allows up to 125 registers to be obtained at each request however the specific Server device may have restrictions that lower this maximum quantity The registers are numbered for zero 30001 zero 30002 one and so on Broadcast mode is not allowed The example below requests the contents of register 3009 in Server number 11 Adr Func Data Start Reg Hi Data Start Reg Lo Data tof Regs Hi Data tof Regs Lo Error Check Field 11 04 00 08 00 01 CRC Response The addressed Server responds with its address and the function code followed by the information field The information field contains 1 byte describing the quantity of data bytes to be return
113. gram included with your MVIS6E MNETCR module contains predefined controller tags configuration information data types and ladder logic that allow the module to communicate between the ControlLogix processor and a network of Modbus TCP IP devices For most applications the sample program will work without modification ProSoft Technology Inc Page 145 of 159 June 14 2011 Reference MVI56E MNETCR ControlLogix Platform User Manual Modbus TCP IP Multi Client Enhanced Communications Module for Remote Chassis Page 146 of 159 ProSoft Technology Inc June 14 2011 MVI56E MNETCR 4 ControlLogix Platform Support Service amp Warranty Modbus TCP IP Multi Client Enhanced Communications Module for Remote Chassis User Manual 6 Support Service amp Warranty In This Chapter Contacting Technical 2 22 147 Return Material Authorization RMA Policies and Conditions 149 151 Contacting Technical Support ProSoft Technology Inc ProSoft is committed to providing the most efficient and effective support possible Before calling please gather the following information to assist in expediting this process 1 Product Version Number 2 System architecture 3 Network details If the issue is hardware related we will also need information regarding Module configuration and associated ladder files if any Modul
114. h the members of the MVI56E MNETCR Status object Page 88 of 159 ProSoft Technology Inc June 14 2011 MVI56E MNETCR ControlLogix Platform Diagnostics and Troubleshooting Modbus TCP IP Multi Client Enhanced Communications Module for Remote Chassis User Manual 4 2 4 Monitoring MNET Client Information Use the MNET CLIENT menu to view the configuration and status information for the MNET Client s Config Use the Configuration menu to view configuration settings for MNET Client x The information on this menu corresponds with the configuration information in the MNET Client x settings in ProSoft Configuration Builder Status Use the Status menu to view status for MNET Client x During normal operation the number of requests and responses should increment while the number of errors should not change Command List Use the Command List menu to view the command list settings for MNET Client x The information on this menu corresponds with the settings in the MNET Client x Commands settings in ProSoft Configuration Builder Use the scroll bar on the right edge of the window to view each MNET Client command Command Status Use the Command Status menu to view MNET Client x Command status A zero indicates no error A non zero value indicates an error Refer to Client Command Errors page 113 for an explanation of each value ProSoft Technology Inc Page 89 of 159 June 14 2011 Diagnostics and Troubleshooting
115. has read this Warranty understands it and is bound by its Terms Page 154 of 159 ProSoft Technology Inc June 14 2011 MVI56E MNETCR 4 ControlLogix Platform Support Service amp Warranty Modbus TCP IP Multi Client Enhanced Communications Module for Remote Chassis User Manual 6 2 10 Controlling Law and Severability This Warranty shall be governed by and construed in accordance with the laws of the United States and the domestic laws of the State of California without reference to its conflicts of law provisions If for any reason a court of competent jurisdiction finds any provisions of this Warranty or a portion thereof to be unenforceable that provision shall be enforced to the maximum extent permissible and the remainder of this Warranty shall remain in full force and effect Any cause of action with respect to the Product or Services must be instituted in a court of competent jurisdiction in the State of California ProSoft Technology Inc Page 155 of 159 June 14 2011 Support Service amp Warranty MVI56E MNETCR ControlLogix Platform User Manual Modbus TCP IP Multi Client Enhanced Communications Module for Remote Chassis Page 156 of 159 ProSoft Technology Inc June 14 2011 MVI56E MNETCR 4 ControlLogix Platform Modbus TCP IP Multi Client Enhanced Communications Module for Remote Chassis Index User Manual Index 0 00 Return Query Data 125 A About the MODBUS TCP Protocol 97 Adding Mult
116. he default values are RemoteENBT Slot6 1 and RemoteENBT Slot6 1 O so these require change Import Configuration Tags Data Types Add On Instructions Nams Alas For Data Type MNETCR AOISEMNETCR ADISEMNETC Use Existing MNETCRMOD Use Existing g j RemoteENBT 516 1 1 g Slot6 1 0 g z RemoteENBT Slot6 2 0 Controller Program Show Show All Import Configuration Tags Data Types Add On instructions AOIS6MNETCR MNETCR RemoteENBT_Slot6 2 1 RemoteENBT_Slot6 2 1 v g j RemoteENBT Slot6 2 C fJ x RemoteENBT 51016 2 1 P RemoteENBT Slote 2 0 8 4 RemoteENBT Slot I 8 j RemoteENBT 51016 0 Controller Program Show Show All 1756 AB 1756 MODULE INT 84Bytes 0 AB 1756 MODULE INT 84Bytes 0 0 1756 MODULE C O AB 1756 MODULE INT 84Bytes 0 AB 1756 MODULE INT 84Bytes 0 0 AOISEMNETC Use Existing Use Existing MNETCRMOD AB 1756 MOD 1756 MOD AB 1756 MODULE C 0 1756 MODULE INT 84 0 AB 1756 MODULE INT 84Bytes 0 0 1756 7SLOT LO 1756 7SLOT 0 0 1 Discard Use Existing Page 40 of 159 ProSoft Technology Inc June 14 2011 MVI56E MNETCR ControlLogix Platform Modbus TCP IP Multi Client Enhanced Communications Module for Remote Chassis 11 Change the default tags MNETCR and AOIS6MNETCR to avoid conflict with existing tags In
117. hich the failure of the product could lead directly or indirectly to death personal injury or severe physical or environmental damage collectively high risk activities ProSoft specifically disclaims any express or implied warranty of fitness for high risk activities Page 152 of 159 MVI56E MNETCR ControlLogix Platform Modbus TCP IP Multi Client Enhanced Communications Module for Remote Chassis ProSoft Technology Inc June 14 2011 MVI56E MNETCR ControlLogix Platform Support Service amp Warranty Modbus TCP IP Multi Client Enhanced Communications Module for Remote Chassis User Manual 6 2 4 Intellectual Property Indemnity Buyer shall indemnify and hold harmless ProSoft and its employees from and against all liabilities losses claims costs and expenses including attorney s fees and expenses related to any claim investigation litigation or proceeding whether or not ProSoft is a party which arises or is alleged to arise from Buyer s acts or omissions under these Terms or in any way with respect to the Products Without limiting the foregoing Buyer at its own expense shall indemnify and hold harmless ProSoft and defend or settle any action brought against such Companies to the extent based on a claim that any Product made to Buyer specifications infringed intellectual property rights of another party ProSoft makes no warranty that the product is or will be delivered free of any person s claiming of patent trademark
118. ing the MVIBGE MNETCR module in a remote rack follow these next few steps If you are installing the module in a local rack follow the steps in Create the Module Local Rack page 31 Page 26 of 159 ProSoft Technology Inc June 14 2011 MVI56E MNETCR ControlLogix Platform Modbus TCP IP Multi Client Enhanced Communications Module for Remote Chassis Start Here User Manual 1 11 1 Create the Remote Network 1 Right click I O CONFIGURATION and choose NEW MODULE Controller My Controller Controller Tags Controller Fault Handler Power Up Handler Tasks fa MainTask Cg MainProgram Z3 Unscheduled Programs 7 5 Motion Groups Ungrouped Axes Add On Instructions 7 3 Data Types 018 User Defined Strings Add On Defined E Predefined Eg Module Defined Trends 65 1 0 Configuration A4 2 Expand the COMMUNICATIONS module selections and then select the Ethernet Bridge module that matches your hardware This example uses a 1756 ENBT A module Select Module 1756 CNBRJE 1756 DHRIO B 1756 DHRIO C 1756 DHRIO D 1756 DNB 1756 EN2F A 1756 EN2T A 1756 ENBF A 1756 ENBT A 1756 ENET A 1756 ENET B 1756 EWEB A 1756 SYNCH A By Category Vendor len Bradi len Bradl len Bradl len Bradi len Bradl Description 1756 ControlNet Bridge Redundant Media 1756 DH Bridge RIO Scanner 1756 DH Bridge R
119. iple Modules Optional 37 Adding the Module to an Existing Project 2 Adjusting the Input and Output Array Sizes Optional 42 Allocation of Risks 154 ARP Timeout 53 Backplane Control Object MNETCRUTIL 72 77 Backplane Data Transfer 98 Backplane Status 88 Battery Life Advisory 3 Before You Begin 132 Block 9990 Set Module IP Address 99 108 Block 9991 Get Module IP Address 109 Block 9998 Warm Boot 99 109 Block 9999 Cold Boot 110 Block Request from Processor to Module 100 Block Response from Module to Processor 100 Block Statistics Object MNETCRBLOCKSTATS 75 76 Clearing a Fault Condition 83 Client Command Errors 89 113 Client Command List 113 Client Driver 76 91 112 Client Statistics Object MNETCRCLIENTSTATS 75 76 Client Status Data 76 91 105 Client Status Request Blocks 3000 to 3029 99 105 Client Status Response 105 Command Control Blocks 5001 to 5016 99 106 Command Control Data Object MNETCCONTROL 72 74 Command Control Data Object MNETCRCMDCONTROL 74 75 Command Entry Formats 55 Command Error Delay 54 Command Error Pointer 52 Command List 89 Command List Entry Errors 115 Command List Overview 54 Command Status 89 Commands Supported by the Module 55 Comment 59 Config 88 89 Configuring Module Parameters 49 Configuring the MVIbG6E MNETCR Module 45 Connecting to the Module s We
120. it but a long duration of time will be required to do so This response is returned to prevent a timeout error from occurring in the Client The Client can next issue a poll program complete message to determine if processing is completed 06 Slave Device Busy Specialized use in conjunction with programming commands The Server is engaged in processing a long duration program command The Client should retransmit the message later when the Server is free 08 Memory Parity Error Specialized use in conjunction with function codes 20 and 21 and reference type 6 to indicate that the extended file area failed to pass a consistency check The Server attempted to read record file but detected a parity error in the memory The Client can retry the request but service may be required on the Server device 0a Gateway Path Unavailable Specialized use in conjunction with gateways indicates that the gateway was unable to allocate an internal communication path from the input port to the output port for processing the request Usually means that the gateway is misconfigured or overloaded Page 130 of 159 ProSoft Technology Inc June 14 2011 MVI56E MNETCR ControlLogix Platform Reference Modbus TCP IP Multi Client Enhanced Communications Module for Remote Chassis User Manual Code Name Meaning Ob Gateway Target Device Failed To Respond Specialized use in conjunction with gateways indicat
121. itialize Output Data parameter in the configuration file to bring the module to a known state after a restart operation The following table describes the structure of the request block Offset Description Length 0 1000 to 1124 1 1 to 40 Spare 40 41 1000 to 1124 1 The block number in word 20 of the block determines the data set of up to 40 output words to transfer from the processor Ladder logic in the processor must recognize these blocks and place the correct information in the output image to be returned to the module The following table describes the structure of the response block Offset Description Length 0 1000 to 1124 1 1 to 40 Output Data to preset in module 40 41 Spare 1 5 2 8 Special Function Blocks Special function blocks are special optional blocks used to request special tasks from the module The MVIS56E MNETCR supports the following special function blocks Initialize Output Data Event Command Client Status request Client Status response Command Control Set new module IP address Get module IP address Warm boot Cold boot Important Each command defined in the command list is controlled by the ladder logic The Write Command Bits parameter must be set in ladder logic to allow the command to be sent out on the Modbus TCP IP network Page 102 of 159 ProSoft Technology Inc June 14 2011 MVI56E MNETCR 4 ControlLogix Platform Reference Modbus TCP IP Multi Client Enhan
122. le ProSoft Technology Inc Page 91 of 159 June 14 2011 Diagnostics and Troubleshooting MVI56E MNETCR 4 ControlLogix Platform User Manual Modbus TCP IP Multi Client Enhanced Communications Module for Remote Chassis Page 92 of 159 ProSoft Technology Inc June 14 2011 MVI56E MNETCR 4 ControlLogix Platform Modbus TCP IP Multi Client Enhanced Communications Module for Remote Chassis Reference User Manual 5 Reference In This Chapter Product Specifications esee 94 3 nennen 97 Data Flow between MVI56E MNETCR Module Processor and Ethernet Cable Specifications eene 116 Modbus Protocol 118 Using the Optional Add On Instruction Rung Import 132 Adding the Module to an Existing 142 Using the Sample Program RSLogix 5000 Version 15 and earlier 145 ProSoft Technology Inc June 14 2011 Page 93 of 159 Reference MVI56E MNETCR 4 ControlLogix Platform User Manual Modbus TCP IP Multi Client Enhanced Communications Module for Remote Chassis 5 1 Product Specifications The MVI56E Modbus TCP IP Multi Client Enhanced Communications Module for Remote Chassis allows Rockwell Automation ControlLogix Programmable Automation Controllers PACs to interface easily with multiple Modbus TCP IP server compatible instruments and devices
123. ll of the following items are present Qty Part Name Part Number Part Description 1 MVI56E MNETCR MVI56E MNETCR Modbus TCP IP Multi Client Enhanced Module Communications Module for Remote Chassis 1 Cable RL CBL025 5 foot Ethernet Straight Through Cable Gray 1 ProSoft Solutions CD 3 Contains configuration tools for the MVI56E MNETCR module 1 Insert MVI56E MNETCR Quick Start Guide If any of these components are missing please contact ProSoft Technology Support for replacement parts Page 12 of 159 ProSoft Technology Inc June 14 2011 MVI56E MNETCR 4 ControlLogix Platform Start Here Modbus TCP IP Multi Client Enhanced Communications Module for Remote Chassis User Manual 1 4 Setting Jumpers The Setup Jumper acts as write protection for the module s flash memory In write protected mode the Setup pins are not connected and the module s firmware cannot be overwritten Do not jumper the Setup pins together unless you are directed to do so by ProSoft Technical Support The following illustration shows the MVIS56E MNETCR jumper configuration SETUP SETUP SHUNT 0 NOT JUMPERED Note If you are installing the module in a remote rack you may prefer to leave the Setup pins jumpered That way you can update the module s firmware without requiring physical access to the module ProSoft Technology Inc Page 13 of 159 June 14 2011 Start Here MVI56E MNETCR 4 ControlLogix Platfo
124. ls Window Help amp sel 21 EH Path none amp Offline D p E OK No Forces 5 BAT No Edits ar 9 28 Controller My Controller Tasks MainTask 2 8 Program Tags E MainRoutine Unscheduled Programs amp Motion Groups Ungrouped Axes Add On Instructions Data Types Cg User Defined Strings Add On Defined Predefined Module Defined Trends 1 0 Configuration alal 4 eO ee 2 se Favorites 89200 K K Tmercounier Ki aelel CutRung Copy Rung Delete Rung Add Rung Edit Rung Edit Rung Comment Import Rung Export Rung Accept Pending Rung Edits Verify Rung Go To Add Ladder Element ainRoutine Ctrl G Alt Ins ProSoft Technology Inc June 14 2011 Page 33 of 159 MVI56E MNETCR 4 ControlLogix Platform Start Here User Manual Modbus TCP IP Multi Client Enhanced Communications Module for Remote Chassis Instruction for example My Documents or Desktop Select the MVIB6EMNETCR RuNGc 1 3 L5X file Import Rung Look in 8 Desktop 1 My Computer Documents Network Places Downloads MvrSe E MNETCR AddOn vi 3 Lsx Desktop File name MVISGEMNETCR AddOn Rung vl 315 Files of type
125. lues on this menu correspond with the contents of the module s Miscellaneous Status registers Config Use the Configuration menu to view backplane configuration settings for the MVI56E MNETCR module The information on this menu corresponds with the configuration information in the Module settings in ProSoft Configuration Builder NIC Status Use the Status Network Interface Card menu to view configuration and status information for the MVI56E MNETCR module s Ethernet application port The information on this menu is useful for troubleshooting Ethernet network connectivity problems Static ARP Use the Static ARP menu to view the list of IP and MAC addresses that are configured not to receive ARP Address Resolution Protocol messages from the module The Static ARP Table page 60 defines a list of static IP addresses that the module will use when an ARP is required 4 2 8 Monitoring Backplane Information Use the BACKPLANE menu to view the backplane status information for the MVI56E MNETCR module Backplane Status Use the Status menu to view current backplane status including Number of retries Backplane status Fail count Number of words read Number of words written Number of words parsed Error count Event count Command count During normal operation the read write and parsing values should increment continuously while the error value should not increment The status values on this menu correspond wit
126. mands 5 1 2 Functional Specifications Modbus data types overlap in the module s memory database so the same data can be conveniently read or written as bit level or register level data Configurable floating point data movement is supported including support for Enron or Daniel floating point formats Special functions Command Control Event Commands status etc are supported by message transfer unscheduled using the MSG instruction Configurable parameters for the Client including a minimum response delay of 0 to 65535 ms and floating point support Supports up to 30 Clients with up to 16 commands for each Client Error codes counters and module status available from module memory through the Clients or through the ladder logic and controller tags in RSLogix 5000 ProSoft Technology Inc Page 95 of 159 June 14 2011 Reference MVI56E MNETCR 4 ControlLogix Platform User Manual Modbus TCP IP Multi Client Enhanced Communications Module for Remote Chassis 5 1 3 Hardware Specifications Specification Description Backplane Current Load 800 mA 5 3 mA 24 Vdc Operating Temperature 0 C to 60 C 32 F to 140 F Storage Temperature 40 C to 85 C 40 F to 185 F Shock 30 g operational 50 g non operational Vibration 5 g from 10 to 150 Hz Relative Humidity 5 to 95 without condensation LED Indicators Battery Status ERR Application Status APP Module Status OK 4 Character Scrollin
127. menu Diagnostics Connection Log Module sale h MVI56E MNETCR Time 10 28 59 MODULE Select item within MVI56E MNETCR for diagnostic information Version Config 84 NIC Status G Static ARP aa BACKPLANE Lg Status asci Ld Decimal Hex Float MNET CLIENT 0 Config Status Ld Command List Command Status MNET CLIENT 1 Config Ll Status Command List Ld Command Status 3 MNET CLIENT 2 Path Ethernet 10 1 1 219 4 2 2 Monitoring Module Information Use the MODULE menu to view configuration and hardware information for the MVI56E MNETCR module s backplane and Ethernet application port Version Use the VERSION menu to view module hardware and firmware information MVI56E MNETCR gt MODULE gt Version PRODUCT NAME CODE SOFTWARE REVISION LEVEL 2 04 OPERATING SYSTEM REVISION 11109 RUN NUMBER 11201 PROGRAM SCAN COUNTER 143337 IP ADDRESS 120 1 3 195 ETHERNET ADDRESS MAC 00 0d 8d 00 3a 98 BACKPLANE DRIVER VERSION 2 06 BACKPLANE VERSION 3 01 MODULE NAME 5 VENDOR ID 309 DEVICE 12 PRODUCT CODE 15012 SERIAL NUMBER 000003E9 REVISION 12 04 SLOT 23 ProSoft Technology Inc Page 87 of 159 June 14 2011 Diagnostics and Troubleshooting MVI56E MNETCR 4 ControlLogix Platform User Manual Modbus TCP IP Multi Client Enhanced Communications Module for Remote Chassis The va
128. ming including but not limited to programs developed with any IEC 61131 3 C or any variant of C programming languages not furnished by ProSoft v use of the Product for purposes other than those for which it was designed vi any other abuse misapplication neglect or misuse by the Customer vii accident improper testing or causes external to the Product such as but not limited to exposure to extremes of temperature or humidity power failure or power surges or viii disasters such as fire flood earthquake wind and lightning c The information in this Agreement is subject to change without notice ProSoft shall not be liable for technical or editorial errors or omissions made herein nor for incidental or consequential damages resulting from the furnishing performance or use of this material The user guide included with your original product purchase from ProSoft contains information protected by copyright No part of the guide may be duplicated or reproduced in any form without prior written consent from ProSoft 6 2 3 Disclaimer Regarding High Risk Activities Product manufactured or supplied by ProSoft is not fault tolerant and is not designed manufactured or intended for use in hazardous environments requiring fail safe performance including and without limitation the operation of nuclear facilities aircraft navigation of communication systems air traffic control direct life support machines or weapons systems in w
129. mmunications Module for Remote Chassis User Manual Command Control Data Object MNETCRCMDCONTROL MVI56E MNETCR Command Control Name Data Type Description ClientIDreq INT Requested Client ID CmdQty INT Command Quantity for the Client Cmdlndex INT 16 Command Index per client 0 to 15 IP Address Object MNETCRIPADDRESS This object holds IP address status with set IP amp get IP triggers Name Data Type Description IPgetTrigger BOOL Triggers get IP address IPreceived INT 4 Displays received IP address IPsetTrigger BOOL Triggers set IP address IPrequested INT 4 Displays requested IP address 3 1 3 Status Object MNETCRSTATUS This object contains the status of the module The MNETCRSTATUS object is updated each time a read block is received by the processor Use this data to monitor the state of the module at a real time rate Name Data Type Description PassCnt INT Program cycle counter BlockStats MNETCRBLOCKSTATS Block Statistics page 76 CmaBits INT 30 Commands bits array to be used for 30 clients ClientStatsTrigger BOOL Get Client Status ClientlIDReq INT Client ID requested ClientStatus MNETCRCLIENTSTATS 30 Client Status requests page 76 ClientIDRec INT Client ID received CmakErrorList INT 16 Command Error List ClientStatsPending BOOL Allows Get Client Status ProSoft Technology Inc Page 75 of 159 June 14 2011 Ladder Logic User Ma
130. module by using an Ethernet crossover cable not included Allen Bradley ProSoft Technology Inc Page 17 of 159 June 14 2011 Start Here MVI56E MNETCR 4 ControlLogix Platform User Manual Modbus TCP IP Multi Client Enhanced Communications Module for Remote Chassis 1 8 Setting Temporary IP Address Important ProSoft Configuration Builder locates MVIS56E MNETCR modules through UDP broadcast messages These messages may be blocked by routers or layer 3 switches In that case ProSoft Discovery Service will be unable to locate the modules To use ProSoft Configuration Builder arrange the Ethernet connection so that there is no router layer 3 switch between the computer and the module OR reconfigure the router layer 3 switch to allow routing of the UDP broadcast messages 1 Click the START button and then navigate to PROGRAMS PROSOFT TECHNOLOGY Microsoft Update Set Program Access and Defaults W Windows Catalo Fi Accessories A Windows Update 5 3 Tools Programs ProSoft Technology ProSoft Configuration Builder B Documents e Internet Explorer e ProSoft Transport Path Editor Settings ProSoft Discovery Service 4 Search gt Windows Media Player Help and Support Run ShutDown sg Start 2 Click to start PROSOFT CONFIGURATION BUILDER If you have used other Windows configuration tools b
131. nformation required to interface to the Modbus TCP IP server device Command List Overview In order to interface the module with Modbus TCP IP Server devices you must construct a command list The commands in the list specify the server device to be addressed the function to be performed read or write the data area in the device to interface with and the registers in the internal database to be associated with the device data The Client command list supports up to 16 commands The command list is processed from top command 1 to bottom A poll interval parameter is associated with each command to specify a minimum delay time in tenths of a second between the issuance of a command If the user specifies a value of 10 for the parameter the command will be executed no more frequently than every 1 second Page 54 of 159 ProSoft Technology Inc June 14 2011 MVI56E MNETCR 4 ControlLogix Platform Configuring the MVI56E MNETCR Module Modbus TCP IP Multi Client Enhanced Communications Module for Remote Chassis User Manual Commands Supported by the Module The format of each command in the list depends on the Modbus Function Code being executed The following table lists the functions supported by the module Function Code Definition Read Coil Status Read Input Status Read Holding Registers Read Input Registers Force Write Single Coil Preset Write Single Register Force Write Multiple Coils Preset Write Multi
132. ng the number of commands added to the command queue for the port The following table describes the format for this block Offset Description Length 0 Write Block ID 1 1 Number of commands added to command queue 1 2 to 40 Spare 39 41 5001 to 5016 1 Reset Module Status Block 9971 This block allows the processor to reset all status values available from the module to the processor or through the PCB diagnostics menu This block is triggered through the following data type and controller tag elements MNETCREVENTCMD MNETCRCMDCONTROL BOOL BOOL MNETCRIPADDRESS INT 30 CmdConirol Cmd ConirolT ngger CmdConirolPending IPAddress WiteCmdBis MNETCR MNETCR DATA MNETCR CONTROL MNETCR CONTROL BootTimer MNETCR CONTROL W armBoot MNETCR CONTROL ColdBoot MNETCR CONTROL ResetStatus MNETCRCONTROL Description Values used by program for data operation between the module and the processor Members Data Type Size 164 byte s Decimal Decimal Decimal Decimal Decimal Decimal Decimal Decimal Decimal Bl Data Type MNETCRCONTROL Timer used to clear both cold and warm Partial rezet ol the Module Ful reset ol the Module Resets module status Event Command Allows Event Command ID to server with the Evert Con Holds E vent Comenand configuration Holds Command Control status Command Co
133. ntrol Allows Cm ConitolT nges IP 533655 statistics including triggers Selects individual to to activate mA mA 0 Decimal 0 Decimal 0 Decimal ProSoft Technology Inc June 14 2011 Page 107 of 159 Reference User Manual MVI56E MNETCR 4 ControlLogix Platform Modbus TCP IP Multi Client Enhanced Communications Module for Remote Chassis Set Module IP Adaress Block 9990 IP Set Request Write Block Offset Description Length 9990 First digit of dotted IP address Second digit of dotted IP address Third digit of dotted IP address Last digit of dotted IP address 4 4 0 1 2 3 4 5 to 41 Reserved IP Set Response Read Block Offset Description Length 0 Write Block ID First digit of dotted IP address Second digit of dotted IP address Third digit of dotted IP address Last digit of dotted IP address 4 2 gt gt 0 1 2 3 4 5 6 to 41 Spare data area Page 108 of 159 ProSoft Technology Inc June 14 2011 MVI56E MNETCR 4 ControlLogix Platform Reference Modbus TCP IP Multi Client Enhanced Communications Module for Remote Chassis User Manual Get Module IP Address Block 9991 IP Get Request Write Block Offset Description Length 0 9991 1 1 to 41 Spare data area 40 IP Get Response Read Block Offset Description Length
134. ntroller If Connection Fails While in Run Mode Module Fault Status Offline Cancel Help MVI56E MNETCR module is now visible the I O CONFIGURATION pane Controller My Controller Controller Tags Controller Fault Handler Power Up Handler Tasks E fa MainTask C MainProgram Unscheduled Programs 1 amp 3 Motion Groups Ungrouped Axes Add On Instructions 2 3 Data Types C amp User Defined oa Strings 18 Add On Defined i Predefined oe Module Defined Trends 7 5 1 0 Configuration 1756 Backplane 1756 A7 0 1756463 Controller 1756 CNB D Local CNBR1 ControlNet 8 11756 CNB D Local CNER1 8 2 1756 CNB D Remote CNBR2 9 1756 Backplane 1756 A17 fj 0 1756 CNB D Remote CNBR2 EE 1 1756 MODULE MNETCR Note If you are installing the MVI56E MNETCR module in a local rack follow these next few steps If you are installing the module in a remote rack follow the steps in Create the Module Remote Rack page 27 Page 30 of 159 ProSoft Technology Inc June 14 2011 MVI56E MNETCR ControlLogix Platform Start Here Modbus TCP IP Multi Client Enhanced Communications Module for Remote Chassis User Manual Create the Module Local Rack 1 CONTROLLER ORGANIZATION window expand the configuration node 2 Select the 1756 BACKPLANE node and then click the right mouse button to open a shortcut menu On the shortcut menu choose NEW MODULE
135. nu and then choose MODULE DOWNLOAD This action opens the Download dialog box Notice that the Ethernet address field contains the temporary IP address you assigned in the previous step ProSoft Configuration Builder will use this temporary IP address to connect to the module Download files from PC to module STEP 1 Select Communication Path Select Connection Type Ethernet v Browse Device s Ethernet 192 168 0 250 Use Default IP CIPconne ct STEP 2 Transfer File s DOWNLOAD Click TEST CONNECTION to verify that the temporary IP address is correct 3 If the connection succeeds click DOWNLOAD to transfer the Ethernet configuration to the module If the Test Connection procedure fails you will see an error message To correct the error follow these steps 1 Click OK to dismiss the error message 2 Onthe Download dialog box click BROWSE DEVICES to open ProSoft Discovery Service Prosoft Discovery Service Assign Temporary IP Device Details Remove Temporary IP View modules webpage Select For Click the search icon to begin the browse 3 Select the module and then click the right mouse button to open a shortcut menu On the shortcut menu choose SELECT FOR PCB 4 Close ProSoft Discovery Service 5 Click DOWNLOAD to transfer the configuration to the module Page 62 of 159 ProSoft Technology Inc June 14 2011 MVI56E MNETCR ControlLogix Platform
136. nual MVI56E MNETCR ControlLogix Platform Modbus TCP IP Multi Client Enhanced Communications Module for Remote Chassis Block Statistics Object MNETCRBLOCKSTATS This object contains a structure that includes the status information for the data transfer operations between the processor and the module The following table describes the structure of this object Name Data Type Description Read INT Total number of read block transfers Write INT Total number of write block transfers Parse INT Total number of blocks parsed Event INT Total number of event blocks received Cmd INT Total number of command blocks received Err INT Total number of block transfer errors Client Statistics Object MNETCRCLIENTSTATS This block also contains a structure that includes Client statistics The following table describes the structure of this object Name Data Type Description CmdReq INT Total number of command list requests sent CmdResp INT Total number of command list responses received CmdErr INT Total number of command list errors Requests INT Total number of requests for port Responses INT Total number of responses for port ErrSent INT Total number of errors sent ErrRec INT Total number of errors received CfgErrWord INT Configuration Error Word CurErr INT Current Error code LastErr INT Last recorded error code Refer MVIS6E MNETCR Status Data Definition page 105 page 1
137. o on the remote server Slave Node Address Command Type Read or Write up to 100 words per command Database Source and Destination Register Address Determines where data will be placed and or obtained Count Select the number of words to be transferred 1 to 100 Poll Delay 1 10 seconds 5 3 3 Client Command Errors You can use the configuration s MNET Client x Command Error Pointer which is separately configured for each Client to set the database offset register where all command error codes will be stored This means that the first register refers to command 1 and so on Offset Description 1 Command 1 Error 2 Command 2 Error 3 Command 3 Error For every command that has an error the module automatically sets the poll delay parameter to 30 seconds This instructs the module to wait 30 seconds until it attempts to issue the command again As the list is read in from the configuration file and as the commands are processed an error value is maintained in the module for each command This error list can be transferred to the processor The errors generated by the module are displayed in the following table ProSoft Technology Inc Page 113 of 159 June 14 2011 Reference MVI56E MNETCR 4 ControlLogix Platform User Manual Modbus TCP IP Multi Client Enhanced Communications Module for Remote Chassis Standard Modbus Exception Code Errors Code Description Illegal function Illegal
138. o the processor This process may take a few minutes 4 When the download is complete RSLogix 5000 will open another confirmation dialog box If the key switch is in the REM position click OK to switch the processor from PROGRAM mode to RUN mode RSLogix 5000 EN Done downloading Change controller mode back to Remote Run Yes Note If you receive an error message during these steps refer to your RSLogix documentation to interpret and correct the error Page 44 of 159 ProSoft Technology Inc June 14 2011 MVI56E MNETCR 4 ControlLogix Platform Configuring the MVI56E MNETCR Module Modbus TCP IP Multi Client Enhanced Communications Module for Remote Chassis User Manual 2 Configuring the MVIS6E MNETCR Module In This Chapter Using ProSoft Configuration Builder 46 gt Downloading the Project to the 62 Using ClPconnect to Connect to the 63 ProSoft Technology Inc Page 45 of 159 June 14 2011 Configuring the MVIBGE MNETCR Module MVI56E MNETCR ControlLogix Platform User Manual Modbus TCP IP Multi Client Enhanced Communications Module for Remote Chassis 2 1 Using ProSoft Configuration Builder Software ProSoft Configuration Builder PCB provides a quick and easy way to manage module configuration files customized to meet your application n
139. ogix Platform Modbus TCP IP Multi Client Enhanced Communications Module for Remote Chassis Index User Manual G General Specifications 94 H Hardware MAC Address 60 Hardware Specifications 96 How to Contact Us 2 Import Add On Instruction 33 Important Safety Information MVIS56E Modules 3 Initialize Output Data 51 102 Installing ProSoft Configuration Builder 16 Installing the Configuration Tools 16 Installing the Module in the Rack 14 Installing the Rung Import with Utility Add On Instruction 133 Intellectual Property Indemnity 153 Internal Address 56 IP Address 60 IP Address Object MNETCRIPADDRESS 74 75 L Ladder Logic 71 LED Status Indicators 80 Limitation of Remedies 4 LIMITED WARRANTY 149 151 MB Address in Device 59 MBAP Port Override 54 Minimum Command Delay 52 MNET Client Specific Errors 114 MNET Client x 52 MNET Client x Commands 54 Modbus Exception Codes 130 Modbus Exception Responses 129 Modbus Function 58 Modbus Protocol Specification 8 Modbus TCP IP Client Master 95 Module 50 Module Communication Error Codes 4 Module Data Object MNETCRMODULEDEF 72 Monitoring Backplane Information 88 Monitoring Database Information 90 Monitoring MNET Client Information 89 Monitoring Module Information 87 N NIC Status 88 No Other Warranties 154 Node IP Address 58 Non Scrolling LED Status Indi
140. on READETHERNETMSG Configuration Communication Tag Path MNETCR Browse Message Path Browser Path MNETCR 9 1 0 Configuration amp 1756 Backplane 1756 44 fa 0 1756 L63 ControlLogix 8 3 1756 ENBT A Local ENBT Ethemet B 1756ENBT A RemoteENBT_Slot6 1756 Backplane 1756 47 8 1 1756 MODULE MNETCR 8 B 1756 ENBT A RemoteENBT_Slot6 fJ 1756 Local ENBT Cancel Help ProSoft Technology Inc Page 137 of 159 June 14 2011 Reference MVI56E MNETCR 4 ControlLogix Platform User Manual Modbus TCP IP Multi Client Enhanced Communications Module for Remote Chassis 5 6 4 Heading the Ethernet Settings from the Module Expand the MVIS6EMNETCRETHERNET controller tag and move a value of 1 to MVIB6EMNETCRETHERNET READ MVIBBEMNETCRETHERNET I MVIBBEMNETCRETHERNET Read MVI56EMNETCRETHERNET Write MVI56EMNETCRETHERNET Config 1 MVIBBEMNETCRETHERNET Config IP ERE MVIBBEMNETCRETHERNET Config IP Q MVIBBEMNETCRETHERNET Config IP 1 MVIBBEMNETCRETHERNET Config IP 2 MVIBBEMNETCRETHERNET Config IP 3 MVIBBEMNETCRETHERNET Config Netmask Voss MVIBBEMNETCRETHERNET Config Netmask 0 MVIBBEMNETCRETHERNET Config Netmask 1 MVIBBEMNETCRETHERNET Config Netmask 2 MVIBBEMNETCRETHERNET Config Netmask 3 MVI56E MNETCRETHERNET Config Gateway 1 MVIBBEMNETCRETHERNET Config Gateway 0 MVIBBEMNETCRETHERNET Config Gateway 1 MVIBBEMNETCRETHER
141. ontroller Fault Handler Power Up Handler Tasks 8 MainTask E MainProgram 8 Program Tags MainRoutine A Scope ControlLogix WRITECLOCKMSG 2 gt Data Type WRITEETHERNETMSG MESSAGE RemoteENBT Slot amp 1 C READETHERNETMSG READCLOCKMSG 1 MESSAGE AB 1756_MODULE C 0 MESSAGE MESSAGE MNETCRMODULEDEF je Show MNETCRBLOCKSTATS MNETCRCLIENTSTATS MNETCRCMDCONTROL MNETCRCONT Descriptio Unscheduled Programs Motion Groups Ungrouped Axes AOIBEMNETCR ADIBEMNETCR GH Add On Instructions amp 53 Data Types 28 Trends amp 53l 1 0 Configuration Monitor Tags Edit Tags 4 3 In the Add On Instruction click the button next to each MSG tag to open the MESSAGE CONFIGURATION TAG 4 Click the COMMUNICATION tab and click the BROWSE button as follows Message Configuration READETHERNETMSG Configuration Communication Tag Ph Browse Enable Enable Waiting Stat Done Eror Code Extended Eror Code Eror Path Eror Text Done Length 0 Timed Out gt Page 136 of 159 ProSoft Technology Inc June 14 2011 MVI56E MNETCR 4 ControlLogix Platform Reference Modbus TCP IP Multi Client Enhanced Communications Module for Remote Chassis User Manual 5 Select the module to configure the message path Message Configurati
142. oose an unused IP within your subnet and then click OK 1 8 1 Using ClPconnect to Connect to the Module You can use ClPconnect to connect a PC to the MVIS6E MNETCR module over Ethernet using Rockwell Automation s 1756 ENBT EtherNet IP module This allows you to configure the module and network upload and download files and view network and module diagnostics from a PC RSLinx is not required when you use All you need are The addresses and slot numbers of any 1756 ENBT modules in the path ControlNet node numbers and slot numbers of any 1756 CNBx ControlNet Bridge modules in the path slot number of the MVI56E MNETCR in the destination ControlLogix chassis the last ENBT CNBx and chassis in the path To use follow these steps 1 Inthe Select Connection Type dropdown list choose 1756 ENBT The default path appears in the text box as shown in the following illustration Connection Setup Select Connection Type 1913 v Ethemet FEES EP ProSoft Discovery Service PDS CIPconnect t192 168 0 100 p 1 s 0 Path Edit Test Connection Cancel Page 22 of 159 ProSoft Technology Inc June 14 2011 MVI56E MNETCR ControlLogix Platform Start Here Modbus TCP IP Multi Client Enhanced Communications Module for Remote Chassis User Manual 2 Click CIP PATH EDIT to open the C Pconnect Path Editor dialog box
143. ooting MVI56E MNETCR ControlLogix Platform User Manual Modbus TCP IP Multi Client Enhanced Communications Module for Remote Chassis 3 If PCB is still unable to connect to the module click the BROWSE DEVICE S button to open the ProSoft Discovery Service Select the module then right click and choose SELECT FOR PCB Prosoft Discovery Service Assign Temporary IP Device Details Remove Temporary IP View modules webpage Select For Click the search icon to begin the browse Close ProSoft Discovery Service and click the CONNECT button again 4 Ifall of these troubleshooting steps fail verify that the Ethernet cable is connected properly between your computer and the module either through a hub or switch using the grey cable or directly between your computer and the module using the red cable If you are still not able to establish a connection contact ProSoft Technology for assistance Page 86 of 159 ProSoft Technology Inc June 14 2011 MVI56E MNETCR 4 ControlLogix Platform Diagnostics and Troubleshooting Modbus TCP IP Multi Client Enhanced Communications Module for Remote Chassis User Manual 4 2 1 The Diagnostics Menu The Diagnostics menu available through the Ethernet configuration port for this module is arranged as a tree structure with the Main menu at the top of the tree and one or more submenus for each menu command The first menu you see when you connect to the module is the Main
144. or authorization to use the purchase order submitted for evaluation fee The following is a list of non repairable units 3150 All 3750 3600 All 3700 3170 All 3250 1560 Can be repaired only if defect is the power supply 1550 Can be repaired only if defect is the power supply 3350 3300 1500 All OQ Ory Or so O9 Or Qi ouo 30 Page 150 of 159 ProSoft Technology Inc June 14 2011 MVI56E MNETCR 4 ControlLogix Platform Support Service amp Warranty Modbus TCP IP Multi Client Enhanced Communications Module for Remote Chassis User Manual 6 2 LIMITED WARRANTY This Limited Warranty Warranty governs all sales of hardware software and other products collectively Product manufactured and or offered for sale by ProSoft Technology Incorporated ProSoft and all related services provided by ProSoft including maintenance repair warranty exchange and service programs collectively Services By purchasing or using the Product or Services the individual or entity purchasing or using the Product or Services Customer agrees to all of the terms and provisions collectively the Terms of this Limited Warranty All sales of software or other intellectual property are in addition subject to any license agreement accompanying such software or other intellectual property 6 2 1 What Is Covered By This Warranty a Warranty On New Products ProSoft warrants to the original purchaser that
145. ple Registers 12 oc Each command list record has the same general format The first part of the record contains the information relating to the communication module and the second part contains information required to interface to the Modbus TCP IP server device Command Formats The following table shows the structure of the configuration data necessary for each of the supported commands 1 2 3 4 5 6 7 8 9 10 Enable Internal Poll Interval Count Swap IP Address Serv Slave Function Code Device Modbus Code Address Time Code Port Node Address Code Register 1 10th Seconds Bit 0 IP Address Port Address Read Coil 0x Register bit Count Code Register 1 10th Seconds Bit 0 IP Address Port Address Read Input 1x Register bit Count Code Register 1 10th Seconds Word Code IP Address Port Address Read Holding Register Count Registers 4x Code Register 1 10th Seconds Word 0 IP Address Port Address Read Input Registers Register Count 3x Code 1 bit 1 10th Seconds Bit 0 IP Address Port Address Force Write Single Register Count Coil 0x Code 1 bit 1 10th Seconds Word 0 IP Address Port Address Preset Write Single Register Count Register 4x Code Register 1 10th Seconds Bit 0 IP Address Port Address Force Write Register bit Count Multiple Coil 0x Code Register 1 10th Seconds Word 0 IP Address Port Address Preset Write Register Count
146. r bit of the first character contains the addressed coil and the remainder follow For coil quantities that are not even multiples of eight the last characters will be filled in with zeros at high order end The quantity of data characters is always specified as quantity of RTU characters that is the number is the same whether RTU or ASCII is used Because the Server interface device is serviced at the end of a controller s scan data will reflect coil status at the end of the scan Some Servers will limit the quantity of coils provided each scan thus for large coil quantities multiple PC transactions must be made using coil status from sequential scans Adr Func Byte Data Coil Data Coil Data Coil Data Coil Data Coil Error Count Status20to Status28to Status 36to Status44to Status 52to Check 27 35 43 51 56 Field 11 1 05 CD 6B B2 OE 1B CRC The status of coils 20 to 27 is shown as CD HEX 1100 1101 Binary Reading left to right this shows that coils 27 26 23 22 and 20 are all on The other coil data bytes are decoded similarly Due to the quantity of coil statuses requested the last data field which is shown 1B HEX 0001 1011 Binary contains the status of only 5 coils 52 to 56 instead of 8 coils The 3 left most bits are provided as zeros to fill the 8 bit format ProSoft Technology Inc Page 119 of 159 June 14 2011 Reference MVI56E MNETCR 4 ControlLogix Platform User Manual Modbus TCP IP Multi Clien
147. rm User Manual Modbus TCP IP Multi Client Enhanced Communications Module for Remote Chassis 1 5 Installing the Module in the Rack If you have not already installed and configured your ControlLogix processor and power supply please do so before installing the MVI56E MNETCR module Refer to your Rockwell Automation product documentation for installation instructions Warning You must follow all safety instructions when installing this or any other electronic devices Failure to follow safety procedures could result in damage to hardware or data or even serious injury or death to personnel Refer to the documentation for each device you plan to connect to verify that suitable safety procedures are in place before installing or servicing the device After you have checked the placement of the jumpers insert the MVI56E MNETCR into the ControlLogix chassis Use the same technique recommended by Rockwell Automation to remove and install ControlLogix modules You can install or remove ControlLogix system components while chassis power is applied and the system is operating However please note the following warning Warning When you insert or remove the module while backplane power is on an electrical arc can occur An electrical arc can cause personal injury or property damage by sending an erroneous signal to your system s actuators This can cause unintended machine motion or loss of process control Electrical arcs may also cause an
148. rom the Client s query server device receives the request without a communication error and can handle the query normally it returns a normal response If the server does not receive the request due to a communication error no response is returned The Client program will eventually process a timeout condition for the request If the server receives the request but detects a communication error parity LRC CRC no response is returned The Client program will eventually process a timeout condition for the request If the server receives the request without a communication error but cannot handle it for example if the request is to read a non existent output or register the server will return an exception response informing the Client of the nature of the error The exception response message has two fields that differentiate it from a normal response Function Code Field In a normal response the server echoes the function code of the original request in the function code field of the response All function codes have a most significant bit MSB of 0 their values are all below 80 hexadecimal In an exception response the server sets the MSB of the function code to 1 This makes the function code value in an exception response exactly 80 hexadecimal higher than the value would be for a normal response With the function code s MSB set the Client s application program can recognize the exception response and
149. s itt nr RE Rr ER EPOR n PUDE ed 87 4 2 2 87 4 2 3 Monitoring Backplane Information 001 1 88 4 2 4 Monitoring Client 0 89 4 2 5 Monitoring Database Information 90 4 3 Reading Status Data from the 91 5 Reference 93 5 1 Product 94 5 1 1 General nnne nnns 94 5 1 2 Functional Specifications 244 2 4 00 95 5 1 3 Hardware 96 5 2 97 5 2 1 About the MODBUS TCP 97 5 2 2 Backplane Data 98 5 2 3 Special Function 2044 011000000 entente nnne nnns nennen 102 5 3 Data Flow between MVI56E MNETCR Module Processor and Network 111 5 3 1 Client Driven aides Bier eles ole ethers 112 5 3 2 Client Command 113 5 3 3 Client Command 9 4 113 5 4 Ethernet Cable Specifications sesssssssssseseseeeeenenneneenne 116 5 4 1 Ethernet Cable Configuration 7 116 5 4 2 Ethernet
150. s or use the software other than as authorized in connection with use of Product f Additional Restrictions Relating To Software And Other Intellectual Property In addition to compliance with the Terms of this Warranty Customers purchasing software or other intellectual property shall comply with any license agreement accompanying such software or other intellectual property Failure to do so may void this Warranty with respect to such software and or other intellectual property 6 2 5 Disclaimer of all Other Warranties The Warranty set forth in What Is Covered By This Warranty page 151 are in lieu of all other warranties express or implied including but not limited to the implied warranties of merchantability and fitness for a particular purpose ProSoft Technology Inc Page 153 of 159 June 14 2011 Support Service amp Warranty MVI56E MNETCR ControlLogix Platform User Manual Modbus TCP IP Multi Client Enhanced Communications Module for Remote Chassis 6 2 6 Limitation of Remedies In no event will ProSoft or its Dealer be liable for any special incidental or consequential damages based on breach of warranty breach of contract negligence strict tort or any other legal theory Damages that ProSoft or its Dealer will not be responsible for include but are not limited to Loss of profits loss of savings or revenue loss of use of the product or any associated equipment loss of data cost of capital cost of any sub
151. sages Code Message Boot DDOK Module is initializing Ladd Module is waiting for required module configuration data from ladder logic to configure the application port s Waiting for Processor Connection Module did not connect to processor during initialization Sample ladder logic or AOI is not loaded on processor Module is located in a different slot than the one configured in the ladder logic AOl Processor is not in RUN or REM RUN mode Last config lt date gt Indicates the last date when the module changed its IP address You can update the module date and time through the module s web page or with the Optional MVIBGE Add On Instruction After power up and every reconfiguration the module will display the configuration of the application port s The information consists of Client 0002 C4 C29 Operation Messages After the initialization step the following message pattern will be repeated Backplane Status IP Address Backplane Status Port Status Code Message Backplane Status OK Module is communicating with processor ERR Module is unable to communicate with processor For this scenario the Port Status message above is replaced with Processor faulted or is in program mode IP Address Module IP address C0 OK Port is communicating without error Communication Errors port is having communication errors Refer to PCB diagnostics page 7
152. select printing options and then click OK ProSoft Technology Inc Page 49 of 159 June 14 2011 Configuring the MVIS56E MNETCR Module MVI56E MNETCR ControlLogix Platform User Manual Modbus TCP IP Multi Client Enhanced Communications Module for Remote Chassis 2 1 3 Module This section of the configuration describes the database setup and module level parameters This section provides the module with a unique name identifies the method of failure for the communications for the module if the processor is not in RUN mode and describes how to initialize the module upon startup Error Status Pointer 1 to 4955 Starting register location in virtual Modbus database for the error status table If a value of 1 is entered the error status data will not be placed in the database All other valid values determine the starting location of the data This data area includes the module version information and all error status data Read Register Start 0 to 4999 The Read Register Start parameter specifies the start of the Read Data area in module memory Data in this area will be transferred from the module to the processor Note Total user database memory space is limited to the first 5000 registers of module memory addresses 0 through 4999 Therefore the practical limit for this parameter is 4999 minus the value entered for Read Register Count so that the Read Data Area does not try to extend above address 4999 Read Data and Write Dat
153. st mode is not supported with this function code In addition to the Server address and function fields the message requires that the information field contain the initial coil address to be read Starting Address and the number of locations that will be interrogated to obtain status data The addressing allows up to 2000 coils to be obtained at each request however the specific Server device may have restrictions that lower the maximum quantity The coils are numbered from zero coil number 1 zero coil number 2 one coil number 3 two and so on The following table is a sample read output status request to read coils 0020 to 0056 from Server device number 11 Adr Func Data Start Data Start PtLo Data Of Pts Ho Data Of PtsLo Error Check Field 11 01 00 13 00 25 CRC Page 118 of 159 MVI56E MNETCR 4 ControlLogix Platform Modbus TCP IP Multi Client Enhanced Communications Module for Remote Chassis ProSoft Technology Inc June 14 2011 MVI56E MNETCR 4 ControlLogix Platform Reference Modbus TCP IP Multi Client Enhanced Communications Module for Remote Chassis User Manual Response An example response to Read Coil Status is as shown in Figure C2 The data is packed one bit for each coil The response includes the Server address function code quantity of data characters the data characters and error checking Data will be packed with one bit for each coil 1 2 ON 0 OFF The low orde
154. stitute equipment facilities or services downtime the claims of third parties including customers of the Purchaser and injury to property Some areas do not allow time limitations on an implied warranty or allow the exclusion or limitation of incidental or consequential damages In such areas the above limitations may not apply This Warranty gives you specific legal rights and you may also have other rights which vary from place to place 6 2 7 Time Limit for Bringing Suit Any action for breach of warranty must be commenced within 39 months following shipment of the Product 6 2 8 No Other Warranties Unless modified in writing and signed by both parties this Warranty is understood to be the complete and exclusive agreement between the parties suspending all oral or written prior agreements and all other communications between the parties relating to the subject matter of this Warranty including statements made by salesperson No employee of ProSoft or any other party is authorized to make any warranty in addition to those made in this Warranty The Customer is warned therefore to check this Warranty carefully to see that it correctly reflects those terms that are important to the Customer 6 2 9 Allocation of Risks This Warranty allocates the risk of product failure between ProSoft and the Customer This allocation is recognized by both parties and is reflected in the price of the goods The Customer acknowledges that it
155. sued when failure is recognized Response Timeout 0 to 65535 milliseconds This is the time in milliseconds that a Client will wait before re transmitting a command if no response is received from the addressed server The value to use depends upon the type of communication network used and the expected response time of the slowest device on the network Page 52 of 159 ProSoft Technology Inc June 14 2011 MVI56E MNETCR ControlLogix Platform Configuring the MVI56E MNETCR Module Modbus TCP IP Multi Client Enhanced Communications Module for Remote Chassis User Manual Count 0 to 10 This parameter specifies the number of times a command will be retried if it fails Float Flag YES or NO This flag specifies how the Server driver will respond to Function Code 3 6 and 16 commands read and write Holding Registers from a remote Client when it is moving 32 bit floating point data If the remote Client expects to receive or will send one complete 32 bit floating point value for each count of one 1 then set this parameter to YES When set to YES the Server driver will return values from two consecutive 16 bit internal memory registers 32 total bits for each count in the read command or receive 32 bits per count from the Client for write commands Example Count 10 Server driver will send 20 16 bit registers for 10 total 32 bit floating point values If however the remote Client sends a count of two 2 for ea
156. t Enhanced Communications Module for Remote Chassis 5 5 2 Read Input Status Function Code 02 Query This function allows the user to obtain the ON OFF status of discrete inputs in the addressed Server PC Broadcast mode is not supported with this function code In addition to the Server address and function fields the message requires that the information field contain the initial input address to be read Starting Address and the number of locations that will be interrogated to obtain status data The addressing allows up to 2000 inputs to be obtained at each request however the specific Server device may have restrictions that lower the maximum quantity The inputs are numbered form zero input 10001 zero input 10002 one input 10003 two and so on for a 584 The following table is a sample read input status request to read inputs 10197 to 10218 from Server number 11 Adr Func DataStartPtHi Data Start PtLo Data of Pts Hi Data ofPtsLo Error Check Field 11 02 00 C4 00 16 CRC Response An example response to Read Input Status is as shown in Figure C4 The data is packed one bit for each input The response includes the Server address function code quantity of data characters the data characters and error checking Data will be packed with one bit for each input 1 0 The lower order bit of the first character contains the addressed input and the remainder follow For input quantities that are not
157. ta Connection_Output RemoteENBT_Slot6 1 0 Data MNETCR MNETCR End Add On for MVI56 MNETCR and MVIS6E MNETCR Modules AOIS6MNETCR Add On for MVIS6 MNETCR and MVISGE MNETCR AOI56MNETCR 56 2 Connection Input RemoteENBT 8 Connection Output RemoteENBT_Slot6 2 0 Data MNETCR MNETCR 2 MainRoutine The setup procedure is now complete Save the project and download the application to your ControlLogix processor ProSoft Technology Inc June 14 2011 Page 41 of 159 _2 as shown in Start Here MVI56E MNETCR 4 ControlLogix Platform User Manual Modbus TCP IP Multi Client Enhanced Communications Module for Remote Chassis Adjusting the Input and Output Array Sizes Optional The module internal database is divided into two user configurable areas Read Data Write Data The Read Data area is moved from the module to the processor while the Write Data area is moved from the processor to the module The MVI56E MNETCR Add On Instruction rung is configured for 600 registers of Read Data and 600 registers of Write Data which is sufficient for most applications However you can configure the sizes of these data areas to meet the needs of your application 1 ProSoft Configuration Builder expand the Module icon in the tree view and double click MODULE to open an Edit window Change the READ REGISTER COUNT to contain the number of words for your R
158. ter Data 4999 Page 98 of 159 ProSoft Technology Inc June 14 2011 MVI56E MNETCR ControlLogix Platform Reference Modbus TCP IP Multi Client Enhanced Communications Module for Remote Chassis User Manual Data contained in this database is paged through the input and output images by coordination of the ControlLogix ladder logic and the MVIBbGE MNETCR module s program Up to 40 words of data can be transferred from the module to the processor at a time Up to 40 words of data can be transferred from the processor to the module Each image has a defined structure depending on the data content and the function of the data transfer The module uses the following block numbers Block Range Descriptions 1 Null block 0 Null block 1 to 125 Read or write data 1000 to 1124 Output Initialization Blocks 2000 to 2029 Event Command Block page 103 3000 to 3029 Client status request response blocks page 105 5001 to 5016 Command Control page 106 page 102 9990 Set new module IP address page 107 9991 Get module IP address 9998 Warm boot control block page 109 9999 Cold boot control block These block identification codes can be broken down into a few groups Normal data transfer blocks 1 to 125 Initialization blocks 1000 to 1124 and Command control blocks 2000 5000 to 5016 9998 and 9999 ProSoft Technology Inc June 14 2011 Page 99 of 159
159. the Product that is the subject of the sale will 1 conform to and perform in accordance with published specifications prepared approved and issued by ProSoft and 2 will be free from defects in material or workmanship provided these warranties only cover Product that is sold as new This Warranty expires three 3 years from the date of shipment for Product purchased on or after January 1st 2008 or one 1 year from the date of shipment for Product purchased before January 1st 2008 the Warranty Period If the Customer discovers within the Warranty Period a failure of the Product to conform to specifications or a defect in material or workmanship of the Product the Customer must promptly notify ProSoft by fax email or telephone In no event may that notification be received by ProSoft later than 39 months from date of original shipment Within a reasonable time after notification ProSoft will correct any failure of the Product to conform to specifications or any defect in material or workmanship of the Product with either new or remanufactured replacement parts ProSoft reserves the right and at its sole discretion may replace unrepairable units with new or remanufactured equipment All replacement units will be covered under warranty for the 3 year period commencing from the date of original equipment purchase not the date of shipment of the replacement unit Such repair including both parts and labor will be performed at ProSoft s e
160. the module s backplane and application port drivers restarts the program and resets all internal registers to zero Note In some cases the read section of the module database transferred from module to processor must keep its values after a reboot To repopulate the module s registers with the last values the module sent to the processor set the INITIALIZE OUTPUT DATA parameter in the module configuration to YES The following table describes the format of the control block Offset Description Length 0 9999 1 1 to 41 Spare 41 The module does not send a response block for this command Page 110 of 159 ProSoft Technology Inc June 14 2011 MVI56E MNETCR ControlLogix Platform Reference Modbus TCP IP Multi Client Enhanced Communications Module for Remote Chassis User Manual 5 3 Data Flow between MVI56E MNETCR Module Processor and Network The following topics describe the flow of data between the two pieces of hardware processor and MVI5GE MNETCR module and other nodes on the Modbus TCP IP network The module contains up to 30 clients which can generate either MBAP Modbus API for network communications or MNET requests dependent on the service port selected in the command Output from Module To Processor MOD BU S TCP DATABASE Processor EIE Module The following topics discuss the operation of the client drivers To Module Input from
161. the window When you first start PCB the tree view consists of folders for Default Project and Default Location with a Default Module in the Default Location folder The following illustration shows the PCB window with a new project f Untitled ProSoft Configuration Builder File View Project Tools Help Default Project Name Status Default Location Default Module Please Select Module Type EA Default Module Unknown Product Line Last Change Last Download Module Information Last Change Never Last Download Never Application Rev OS Rev Loader Rev MAC Address configedit version 2 2 0 Build 1 Module configuration module module Type module Name Default module Default Module Your first task is to add the MVI56E MNETCR module to the project 1 Use the mouse to select DEFAULT MODULE in the tree view and then click the right mouse button to open a shortcut menu ProSoft Technology Inc Page 47 of 159 June 14 2011 Configuring the MVIBGE MNETCR Module MVI56E MNETCR ControlLogix Platform User Manual Modbus TCP IP Multi Client Enhanced Communications Module for Remote Chassis 2 Onthe shortcut menu select CHOOSE MODULE TYPE This action opens the Choose Module Type dialog box Choose Module Type Product Line Filter Cl C PLX4000 PLx6000 6 C MVIS6 C MVI71 C 5000 PTQ C 169 MVIS6E Search Module Type STEP 1 Select Module Type Module
162. this procedure you will append the string the following illustration Import Configuration Tags Data Types Add On Instructions MNETCR 2 Create New Create New RemoteENBT Slot amp 21 AB 1756 MOD RemoteENBT Slot amp 20 AB 1756 MOD 12 Click OK to confirm Discard Discard 6 RSLogix 5000 ControlLogix in MVIS6EMNETCR_v16 ACD 1756 L63 MainProgram MainRoutine 6 Edit view Search Logic Communications Tools Window Help alsa amp jel jel MNETRUTL IntOutputDala Trig 18 aa Offline D RUN Path none No Forces gt _ amp OK m be Favorites Add 0 cd 4 H her bs Ed Controller ControlLogix A Controller Tags Controller Fault Handler Power Up Handler Tasks 5 MainTask amp MainProgram Program Tags MainRoutine 89 Unscheduled Programs Motion Groups Add On Instructions Data Types 3 Trends 1 1 0 Configuration 1756 Backplane 1756 A4 01 1756463 ControlLogix 1756 ENET A Local_ENBT 86 Ethernet B 1756 ENBT A RemoteENBT_slot 1756 Backplane 1756 A7 8 1 1756 MODULE MNETCR Bl sce oni iren Add On for MVI56 MNETCR and MVI56E MNETCR Modules AOIS6MNETCR Add On for MVIS6 MNETCR and MVISGE MNETCR AOI56MNETCR AOIS6MNETCR Connection_Input RemoteENBT_Slot6 1 1 Da
163. troller tag Set the new Clock value in MVIBGEMNETCRCLOCK CONFIG Move a value of 1 to MVIS6EMNETCRCLOCK WRITE MVIBBEMNETCRCLOCK MVIBBEMNETCRCLOCK Read MVIBBEMNETCRCLOCK Write MVIBBEMNETCRCLOCK Config MVIBBEMNETCRCLOCK Config Year MVIBBEMNETCRCLOCK Config Month MVIBBEMNETCRCLOCK Config D ay MVIBBEMNETCRCLOCK Config Hour MVI56EMNETCRCLOCK Config Minute MVI5GEMNETCRCLOCK Config Seconds The bit will be automatically reset to 0 MVIBBEMNETCRCLOCK MVIBBEMNETCRCLOCK Read MVI56EMNETCRCLOCK Write MVIBBEMNETCRCLOCK Config MVIBBEMNETCRCLOCK Config Y ear MVIBBEMNETCRCLOCK Config Month MVIBBEMNETCRCLOCK Config Day MVIBBEMNETCRCLOCK Config Hour MVIS6EMNETCRCLOCK Config Minute MVI5GEMNETCRCLOCK Config Seconds To check the status of the message refer to the WRITECLOCKMSG tag WRITECLOCKMSG WRITECLOCKMSG Flags WRITECLOCKMSG EW WRITECLOCKMSG ER WRITECLOCKMSG DN WRITECLOCKMSG ST WRITECLOCKMSG EN WRITECLOCKMSG TO WRITECLOCKMSG EN CC WRITECLOCKMSG ERR WRITECLOCKMSG EXERR WRITECLOCKMSG ERR_SRC WRITECLOCKMSG DN LEN WRITECLOCKMSG REQ LEN en 1680200 0 0 0 0 0 0 1 1680000 ProSoft Technology Inc June 14 2011 Page 141 of 159 Reference MVI56E MNETCR ControlLogix Platform User Manual Modbus TCP IP Multi Client Enhanced Communications Module for Remote Chassis 5 7 Adding the Module to an Existing Project 1 Add the MVI56E MNETCR mo
164. ual 5 5 7 Diagnostics Function Code 08 MODBUS function code 08 provides a series of tests for checking the communication system between a Client device and a server or for checking various internal error conditions within a server The function uses a two byte sub function code field in the query to define the type of test to be performed The server echoes both the function code and sub function code in a normal response Some of the diagnostics cause data to be returned from the remote device in the data field of a normal response In general issuing a diagnostic function to a remote device does not affect the running of the user program in the remote device Device memory bit and register data addresses are not accessed by the diagnostics However certain functions can optionally reset error counters in some remote devices A server device can however be forced into Listen Only Mode in which it will monitor the messages on the communications system but not respond to them This can affect the outcome of your application program if it depends upon any further exchange of data with the remote device Generally the mode is forced to remove a malfunctioning remote device from the communications system Sub function codes supported Only Sub function 00 is supported by the MVI56E MNETCR module 00 Return Query Data The data passed in the request data field is to be returned looped back in the response The entire response messa
165. uctions are provided Rung Import with Sample Program Add On Instruction MVISGEMNETCR AddOn Rung 3 L5X RESOURCES ProSoft Technology Rockwell Automation Modbus Organization Includes the user defined data types data objects and ladder logic required to configure the module Rung Import with Utility Add On Instruction Optional Optional Rung v1 0 L5X If your processor uses an earlier version of RSLogix 5000 see Using the Sample Program page 145 ProSoft Technology Inc June 14 2011 Page 25 of 159 Start Here MVI56E MNETCR ControlLogix Platform User Manual Modbus TCP IP Multi Client Enhanced Communications Module for Remote Chassis 1 11 Creating a New RSLogix 5000 Project 1 Open the FILE menu and then choose NEW f amp RSLogix 5000 Edit View Search Logic Communications Tools Wit Select your ControlLogix controller model Select REVISION 16 Enter a name for your controller such as My Controller Select your ControlLogix chassis type Select SLOT 0 for the controller Ooh WN New Controller Vendor Allen Bradley Type 1756153 ControlLogis5563 Controller Revision Cancel Redundancy Enabled Name My Controller Description Chassis Type 1756 4 4 Slot ControlLogix Chassis Slot 0 Create In C RSLogix 5000 Projects Note If you are install
166. une 14 2011 Reference MVI56E MNETCR 4 ControlLogix Platform User Manual Modbus TCP IP Multi Client Enhanced Communications Module for Remote Chassis 5 5 9 Preset Multiple Registers Function Code 16 Query Holding registers existing within the controller can have their contents changed by this message a maximum of 60 registers However because the controller is actively scanning it also can alter the content of any holding register at any time The values are provided in binary up to the maximum capacity of the controller 16 bit for the 184 384 and 584 unused high order bits must be set to zero Note Function codes 5 6 15 and 16 are the only messages that will be recognized as valid for broadcast Adr Hi Lo Add Quantity Byte Hi Lo Hi LoData Error Check Add Cnt Data Data Data Field 11 10 00 87 00 02 04 00 0A 01 02 CRC Response The normal response to a function 16 query is to echo the address function code starting address and number of registers to be loaded Adr Func Hi Addr Lo Addr Quantity Error Check Field 11 10 00 87 00 02 56 Page 128 of 159 ProSoft Technology Inc June 14 2011 MVI56E MNETCR ControlLogix Platform Reference Modbus TCP IP Multi Client Enhanced Communications Module for Remote Chassis User Manual 5 5 10 Modbus Exception Responses When a Modbus Client sends a request to a Server device it expects a normal response One of four possible events can occur f
167. uplex 10 MB speed Value 2 Full duplex 10 MB speed Value 3 Half duplex 100 MB speed Value 4 Full duplex 100 MB speed Value 0 Auto negotiate Auto negotiate is the default value for backward compatibility This feature is not implemented in older software revisions 2 1 4 MNET Client x This section defines general configuration for the MNET Client Master Error Status Pointer 1 to 4990 Starting register location in virtual database for the error status table for this Client If a value of 1 is entered the error status data will not be placed in the database All other valid values determine the starting location of the data Command Error Pointer 1 to 4999 This parameter sets the address in the internal database where the Command Error List data will be placed so that it may be moved to the processor and placed into the ReadData array Therefore the value entered should be a module memory address in the Read Data area If the value is set to 1 the Command Error List data will not be stored in the module s internal database and will not be transferred to the processor s 76802818 array Minimum Command Delay 0 to 65535 milliseconds This parameter specifies the number of milliseconds to wait between the initial issuances of a command This parameter can be used to delay all commands sent to Servers to avoid flooding commands on the network This parameter does not affect retries of a command as they will be is
168. urce Module Add Rack Delete Rack Construct CIP Path mm Cancel t 192 168 0 100 p 1 5 0 ProSoft Technology Inc Page 63 of 159 June 14 2011 Configuring the MVIBGE MNETCR Module MVI56E MNETCR ControlLogix Platform User Manual Modbus TCP IP Multi Client Enhanced Communications Module for Remote Chassis The Path Editor allows you to define the path between the PC and the MVI56E MNETCR module The first connection from the PC is always a 1756 ENBT Ethernet IP module Each row corresponds to a physical rack in the CIP path MVIBGE MNETCR module is located in the same rack as the first 1756 ENBT module select RACK No 1 and configure the associated parameters MVIS6E MNETCR is available in a remote rack accessible through ControlNet or Ethernet IP include all racks by using the ADD RACK button Parameter Description Source Module Source module type This field is automatically selected depending on the destination module of the last rack 1756 CNB or 1756 ENBT Source Module IP Address IP address of the source module only applicable for 1756 ENBT Source Module Node Address Node address of the source module only applicable for 1756 CNB Destination Module Select the destination module associated to the source module in the rack The connection between the source and destination modules is performed through the backplane Destination
169. will only execute commands with the Enable parameter set to one If the value is set to zero the command is skipped Commands may be placed in the command queue with an Enable parameter set to zero using this feature These commands can then be executed using the command control blocks One to six commands can be placed in the command queue with a single request The following table describes the format for this block Offset Description Length 0 5001 to 5016 1 1 Client to Utilize 1 2 Command index 1 3 Command index 1 4 Command index 1 5 Command index 1 6 Command index 1 7 Command index 1 8 Command index 1 9 Command index 1 10 Command index 1 11 Command index 1 12 Command index 1 13 Command index 1 14 Command index 1 15 Command index 1 16 Command index 1 17 Command index 1 18 to 41 Spare 24 The last digit in the block code defines the number of commands to process in the block For example a block code of 5003 contains 3 command indexes that are to be placed in the command queue The Command index parameters in the block have a range of 0 to 15 and correspond to the module s command list entries Page 106 of 159 ProSoft Technology Inc June 14 2011 MVI56E MNETCR ControlLogix Platform Modbus TCP IP Multi Client Enhanced Communications Module for Remote Chassis Reference User Manual The module responds to a command control block with a block containi
170. xpense All warranty service will be performed at service centers designated by ProSoft b Warranty On Services Materials and labor performed by ProSoft to repair a verified malfunction or defect are warranteed in the terms specified above for new Product provided said warranty will be for the period remaining on the original new equipment warranty or if the original warranty is no longer in effect for a period of 90 days from the date of repair ProSoft Technology Inc Page 151 of 159 June 14 2011 Support Service amp Warranty User Manual 6 2 2 What Is Not Covered By This Warranty a ProSoft makes no representation or warranty expressed or implied that the operation of software purchased from ProSoft will be uninterrupted or error free or that the functions contained in the software will meet or satisfy the purchaser s intended use or requirements the Customer assumes complete responsibility for decisions made or actions taken based on information obtained using ProSoft software b This Warranty does not cover the failure of the Product to perform specified functions or any other non conformance defects losses or damages caused by or attributable to any of the following i shipping ii improper installation or other failure of Customer to adhere to ProSoft s specifications or instructions iii unauthorized repair or maintenance iv attachments equipment options parts software or user created program
171. y is not an allowable action for the Server This may be because the function code is only applicable to newer devices and was not implemented in the unit selected It could also indicate that the Server is in the wrong state to process a request of this type for example because it is unconfigured and is being asked to return register values 02 Illegal Data Address The data address received in the query is not an allowable address for the Server More specifically the combination of reference number and transfer length is invalid For a controller with 100 registers a request with offset 96 and length 4 would succeed a request with offset 96 and length 5 will generate exception 02 03 Illegal Data Value A value contained in the query data field is not an allowable value for Server This indicates a fault in the structure of the remainder of a complex request such as that the implied length is incorrect It specifically does not mean that a data item submitted for storage in a register has a value outside the expectation of the application program because the Modbus protocol is unaware of the significance of any particular value of any particular register 04 Slave Device Failure An unrecoverable error occurred while the Server was attempting to perform the requested action 05 Acknowledge Specialized use in conjunction with programming commands The Server has accepted the request and is processing
172. y of status and diagnostics data in plain English no cryptic error or alarm codes to decipher ProSoft Discovery Service PDS software used to locate the module on the network and assign temporary IP address Personality Module a non volatile industrial grade Compact Flash CF card used to store network and module configuration for easy disaster recovery allowing quick in the field product replacement by transferring the CF card Page 94 of 159 ProSoft Technology Inc June 14 2011 MVI56E MNETCR ControlLogix Platform Reference Modbus TCP IP Multi Client Enhanced Communications Module for Remote Chassis User Manual Modbus TCP IP Client Master The MVI56E MNETCR is a Client only module that will operate on a local or remote rack This module was created to improve performance when controlling multiple servers on a Modbus TCP IP network The module supports up to 30 Clients with up to 16 commands for each Client Actively reads data from and writes data to Modbus TCP IP devices using MBAP or Encapsulated Modbus message formats Transmits Modbus Function Codes 1 2 3 4 5 6 7 15 and 16 Offers 30 Client connections with up to 16 commands each to talk to multiple servers ControlLogix processor can be programmed to use special functions to control the activity on the Client by actively selecting commands to execute from the command list Command Control or by issuing commands directly from the ladder logic Event Com
173. ype View Configuration Export Configuration File s Load Config File Download from PC to Device Upload from Device to PC This action opens the Diagnostics dialog box If there is no response from the module ProSoft Configuration Builder Cannot Connect to IP Address Page 84 of 159 ProSoft Technology Inc June 14 2011 MVI56E MNETCR ControlLogix Platform Diagnostics and Troubleshooting Modbus TCP IP Multi Client Enhanced Communications Module for Remote Chassis User Manual 1 Click the SET UP CONNECTION button to browse for the module s IP address Click to set up connection 2 Inthe Connection Setup dialog box click the TEST CONNECTION button to verify if the module is accessible with the current settings Connection Setup Select Connection Type Ethernet 192 168 0 250 ProSoft Discovery Service PDS Browse Device s CIPconnect Test Connection Cancel You can also use ClPconnect to connect to the module through a 1756 ENBT card Connection Setup Select Connection Type Zi Ethernet pu ProSoft Discovery Service PDS CIPconnect 192 168 0 100 1 2 0 Path Edit Test Connection Cancel Refer to Using ClPconnect to Connect to the Module page 63 page 22 for information on how to construct a CIP path ProSoft Technology Inc Page 85 of 159 June 14 2011 Diagnostics and Troublesh

MVI56E-MNETCR User Manual

Contents

Download Pdf Manuals

Related Search

Related Contents