Home

MVI56E-MNET / MNETXT

1. Code Description 40 Too few parameters 41 Invalid enable code 42 Internal address maximum address 43 Invalid node address lt 0 or gt 255 44 Count parameter set to 0 45 Invalid function code 46 Invalid swap code 48 Could not establish a connection Note When the Client gets error 47 or 48 it uses the adjustable ARP Timeout parameter 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 Page 106 of 181 ProSoft Technology Inc April 23 2014 MVI56E MNET MNETXT ControlLogix Platform Reference Modbus TCP IP Interface Module User Manual 5 5 1 Reference In This Chapter S Product Specifications 107 Backplane Data Transfer 110 Data Flow between the MVIS6E MNET Module and ControlLogix PrOCGSSOL eue fe eR EHE abide 131 Ethernet Cable Specifications sseeeeneee 136 Modbus Protocol Specification eseeeeeeeeee 138 Using the Optional Add On Instruction Rung Import 151 Adding the Module to an Existing 160 Using the Sample Program sse 163 Product Specifications The MVI56E Modbus TCP IP Client Ser
2. 32 1 9 Downloading the Sample Program to the 33 2 Configuring the MVI56E MNET Module 35 2 1 Installing ProSoft Configuration Builder seen 35 2 2 Using ProSoft Configuration Builder Software 36 2 2 1 Upgrading from MVI56 MNET in ProSoft Configuration Builder 36 2 2 2 Setting Up the Project nnne 38 2 2 3 Setting Module enne nnne nene 40 2 2 4 MOGU 42 2 2 5 MNET Client ET 44 2 2 6 MNET Client x Commands sse eee entente enne 47 2 2 7 sic 54 2 2 8 Static ARP Table EE 57 2 2 9 Ethernet Configuration 58 2 3 Connecting Your PC to the Module sse 59 2 3 1 Setting Up a Temporary IP Address 60 24 Downloading the Project to the Module 63 2 4 1 Using ClPconnect to Connect to the Module 64 2 4 2 Using RSWho to Connect to the Module sss eee 73 3 Ladder Logic 75 3 1 Controllet Tags ccce erp Pede Gen al sov eee ee de e e e
3. Block Request from Processor to Module Word Offset Description Length 0 9990 1 First digit of dotted IP address 2 Second digit of dotted IP address 3 Third digit of dotted IP address 4 5 a ee ee ee ee Last digit of dotted IP address to 247 Reserved 243 Block Response from Module to Processor Word Offset Description Length 0 0 1 1 Write Block ID 1 2 First digit of dotted IP address 1 3 Second digit of dotted IP address 1 4 Third digit of dotted IP address 1 5 Last digit of dotted IP address 1 6 to 248 Spare data area 243 249 9990 1 Get Module IP Address Block 9991 Block Request from Processor to Module Word Offset Description Length 0 9991 1 1 to 247 Spare data area 247 Block Response from Module to Processor Word Offset Description Length 0 0 1 1 Write Block ID 1 2 First digit of dotted IP address 1 3 Second digit of dotted IP address 1 4 Third digit of dotted IP address 1 5 Last digit of dotted IP address 1 6 to 248 Spare data area 243 249 9991 1 ProSoft Technology Inc Page 129 of 181 April 23 2014 Reference MVI56E MNET MNETXT ControlLogix Platform User Manual Modbus TCP IP Interface Module Warm Boot Block 9998 This block is sent from the ControlLogix processor to the module output image when the module is required to perform a warm boot software reset operation This bl
4. ControlLogix Platform User Manual Modbus TCP IP Interface Module 1 8 X 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 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 2 Connect the straight connector end of the cable to the serial port on your computer Page 32 of 181 ProSoft Technology Inc April 23 2014 MVI56E MNET MNETXT ControlLogix Platform Start Here Modbus TCP IP Interface Module User Manual 1 9 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 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 commun
5. 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 STEP 1 Select Communication Path Select Connection Type 1756 ENBT v t Ethernet ProSoft Configuration Builder CIPconnect IP Path Edit Successfully Connected STEP 2 Transfer Fil DOWNLOAD J eSt Connection 5 Click DOWNLOAD to download the configuration files to the module through the path Download files from PC to module Module Running STEP 1 Select Communication Path Select Connection Type 1756 ENBT v e s Ethernet 192 168 1 250 _Use Default P CIPconnect t 192 168 0 100 p 1 5 0 56 CIP Path Edit RSWho STEP 2 Transfer File s DOWNLOAD Abor Test Connection OF Cancel Page 72 of 181 ProSoft Technology Inc April 23 2014 MVI56E MNET MNETXT ControlLogix Platform Configuring the MVI56E MNET Module Modbus TCP IP Interface Module User Manual 2 4 2 Using RSWho to Connect to the Module You need to have RSLinx installed on your PC to use this feature You also need an ENBT module set up in the rack For information on setting up the ENBT module see Using ClPconnect to Connect to the Module page 64 1 Inthe tree view in ProSoft Configuration Builder right click the MVI56E MNET module 2 From the shortcut menu choose DOWNLOAD FROM PC TO DEVICE 3 Inthe Download dialog box choose 1756 ENBT from the
6. Documentation is subject to change without notice Page 170 of 181 ProSoft Technology Inc April 23 2014 MVI56E MNET MNETXT ControlLogix Platform Modbus TCP IP Interface Module 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 173 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 contact ProSoft Technical Support at one of the telephone numbers listed above page 169 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 Techn
7. MVI56E MNET MNETXT ControlLogix Platform Start Here Modbus TCP IP Interface Module 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 MVIBGE MNET jumper configuration SETUP SETUP SHUNT d 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 15 of 181 April 23 2014 Start Here MVI56E MNET MNETXT ControlLogix Platform User Manual Modbus TCP IP Interface Module 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 MVIBb6E MNET 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 devic
8. 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 147 of 181 April 23 2014 Reference MVI56E MNET MNETXT ControlLogix Platform User Manual Modbus TCP IP Interface Module 5 5 11 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 Func Hi LoAdd 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
9. This feature can be used for applications that require some read blocks to be updated more frequently than other blocks The following illustrations show the effect of changing the value of the Select Priority Read Block register Write Block offset 247 In the following histogram curve the Select Priority Read Block is equal to 0 Bn State Transition Periodic 10 ms 005 4 02 16 540 PM 4 0 o 1 1 0 249 10 TESTMNET Tuesday March 08 21 j Local 1 0 Data 247 10 0 lt 4 02 15 544 02 15 740 4 02 15 940 40216140 4 02 16 34002 16 540 PM Local 1 0 Data 247 Select Priority Read Block local 1 l Data 249 Read Block ID In the example above all read blocks 1 to 10 are returned in sequential order ProSoft Technology Inc Page 117 of 181 April 23 2014 MVI56E MNET MNETXT ControlLogix Platform Reference Modbus TCP IP Interface Module User Manual Select Priority Read Block 5 If the ladder logic changes the value of Local 1 O Data 247 from 0 to 5 note that the Local 1 I Data 249 value begins to alternate between Block IDs 5 and 6 as long as Local 1 l Data 247 stays set to 5 5 6 5 6 5 6 5 6 5 6 n TESTMNET Tuesday March 08 2005 Local1 Data 249 10 0 Local1 0 Data 247 10 0 4 04 39 604 04 39 809 4 04 40 009 4 04 40 209 4 04 40 409 4 40 609 Select Prio
10. to connect to the module through a 1756 ENBT card Refer to Using ClPconnect to Connect to the Module page 64 for information on how to construct a CIP path Connection Setup Select Connection Type v Ethernet pe ProSoft Discovery Service PDS E ClPconnect t 132 158 0 100 p 1 5 0 CIP Path E dit Test Connection Cancel 5 Ifthe Test Connection is successful click CONNECT ProSoft Technology Inc Page 93 of 181 April 23 2014 Diagnostics and Troubleshooting MVI56E MNET MNETXT ControlLogix Platform User Manual Modbus TCP IP Interface Module If PCB is unable to connect to the module 1 Click the BROWSE DEVICE S button to open the ProSoft Discovery Service Select the module then right click and choose SELECT FOR PCB H Prosoft Discovery Service DER Assign Temporary IP Device Details Remove Temporary IP View modules webpage Select For PCB Click the search icon to begin the browse 2 Close ProSoft Discovery Service and click the CONNECT button again 3 If 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 94 of 181 ProSoft Technology Inc April 23 2014
11. 9959 9960 9961 or 9970 1 1 to 249 Spare data area 247 ProSoft Technology Inc April 23 2014 Page 127 of 181 Reference MVI56E MNET MNETXT ControlLogix Platform User Manual Modbus TCP IP Interface Module Unformatted Pass Through Blocks When the unformatted pass through mode code 1 is selected information is passed from the module to the processor with a block identification code of 9996 Word 2 of this block contains the length of the message and the message starts at word 3 Other controller tags are required to store the controlled values contained in these messages Pass Through Block 9996 from Module to Processor Word Offset Description Length 0 0 1 1 9996 1 2 Number of bytes in Modbus msg 1 3 Reserved always 0 1 4 to 248 Modbus message received 245 249 9996 1 The ladder logic should copy and parse the received message and control the processor as expected by the Client device The processor responds to the pass through block with a write block Response Block 9996 from Processor to Module Word Offset Description Length 0 9996 1 1 to 247 Spare 247 This informs the module that the command has been processed and can be cleared from the pass through queue Page 128 of 181 ProSoft Technology Inc April 23 2014 MVI56E MNET MNETXT ControlLogix Platform Reference Modbus TCP IP Interface Module User Manual Set Module IP Adaress Block 9990
12. Command Entry Formats 48 Command Error Delay 46 Command Error Pointer 45 101 Command List 98 Command List Entry Errors 106 Command List Overview 47 Command Status 98 Commands Supported by the Module 48 Comment 53 Config 97 98 99 Configuration Error Word 83 104 Configuring Module Parameters 40 Configuring the MVIBGE MNET Module 35 Connecting to the Module s Web Page 95 Connecting Your PC to the ControlLogix Processor 32 Connecting Your PC to the Module 59 Connection Timeout 56 Contacting Technical Support 169 171 Controller Tag Overview 80 Controller Tags 76 168 Controlling Law and Severability 177 Creating a New RSLogix 5000 Project 19 Creating Optional Comment Entries 41 Creating the Module 20 D Data Flow between the MVIS56E MNET Module and ControlLogix Processor 131 Diagnostics Function Code 08 145 Diagnostics and Troubleshooting 9 87 89 Disclaimer of all Other Warranties 175 Disclaimer Regarding High Risk Activities 174 Downloading the Project to the Module 31 63 Downloading the Sample Program to the Processor 33 167 168 Duplex Speed Code 44 E Enable 49 Ethernet Cable Configuration 136 Ethernet Cable Specifications 136 Ethernet Configuration 58 61 Ethernet LED Indicators 89 Ethernet Performance 137 Event Command Blocks 2000 120 Example 1 Local Rack Application 66 Example 2
13. MNETXT ControlLogix Platform User Manual Modbus TCP IP Interface Module 4 2 Using the Diagnostics Menu in ProSoft Configuration Builder Tip You can have a ProSoft Configuration Builder Diagnostics window open for more than one module at a time 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 Default Project Ga Default Location hse 2 Onthe shortcut menu choose DIAGNOSTICS gg Default Project Default Location h Demo Module 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 oe 3 Inthe Diagnostics window click the SET UP CONNECTION button to browse for the module s IP address A3 Mei Click to set up connection Page 92 of 181 ProSoft Technology Inc April 23 2014 MVI56E MNET MNETXT ControlLogix Platform Diagnostics and Troubleshooting Modbus TCP IP Interface Module User Manual 4 Inthe Connection Setup dialog box click the TEST CONNECTION button to verify that the module is accessible with the current settings Connection Setup Select Connection Type M Ethemet 192 168 0 253 ProSoft Discovery Service PDS Browse Device s CiPconnect He ELITS Test Connection Cancel You can also use ClPconnect
14. Remote Rack Application 69 Example and State Diagram 145 F Failure Flag Count 43 Float Flag 45 54 Float Offset 46 55 Float Start 46 55 Force Multiple Coils Function Code 15 147 Force Single Coil Function Code 05 143 G General Specifications 108 Get Module IP Address Block 9991 129 Guide to the MVI56E MNET User Manual 9 H Hardware MAC Address 57 Hardware Specifications 109 Holding Register Offset 56 How to Contact Us 2 Importing the Add On Instruction 22 Importing the Sample Add On Instruction 18 23 Initialize Output Data 43 Initialize Output Data Blocks 1000 to 1024 119 Installing ProSoft Configuration Builder 35 Installing the Module in the Rack 16 ProSoft Technology Inc April 23 2014 Page 179 of 181 Index User Manual MVI56E MNET MNETXT ControlLogix Platform Modbus TCP IP Interface Module Installing the Rung Import with Optional Add On Instruction 152 Intellectual Property Indemnity 175 Internal Address 50 IP Address 57 Ladder Logic 75 LED Status Indicators 88 Limitation of Remedies 176 LIMITED WARRANTY 171 173 Markings 3 MB Address in Device 53 Minimum Command Delay 45 MNET Client Specific Errors 106 MNET Client x 44 MNET Client x Commands 47 120 123 MNET Servers 54 99 MNET CONTROL 84 MNET DATA 80 MNET STATUS 83 MNET UTIL 85 Modbus Excep
15. The module is configured for read and write data block transfer The ladder logic handles all read and write block situations 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 the card in the rack and then restore power to the rack 4 1 5 Clearing a Fault Condition Typically if 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 correctly 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 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 April 23 2014 Page 91 of 181 Diagnostics and Troubleshooting MVI56E MNET
16. 1 10th Bit 0 IP Port Address Force Write Multiple Register bit Seconds Count Address Coil 0x Code Register 1 10th Word 0 IP Port Address Preset Write Register Seconds Count Address Multiple Register 4x Page 48 of 181 ProSoft Technology Inc April 23 2014 MVI56E MNET MNETXT ControlLogix Platform Configuring the MVI56E MNET Module Modbus TCP IP Interface Module User Manual 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 Command list example Wil Edit MNet Client 0 Commands Enable Intemal amp ddress Poll Interval Reg Count Swap Code NodelP Address Serv Slave Addr ModBus Function 1 1000 0 10 Change 1921680249 502 1 FC 3 Read Holding v 2 Yes 0 0 10 Change 192 168 0 249 502 1 FC 16 Preset Writ lt Enable Value Status OK Set to Defaults Add Row Insert Row Delete Row Move Up Move Down Edit Row Copy Row DK Cancel Enable No 0 YES 1 or CONDITIONAL 2 This field defines whether the command is to be executed and under what conditions 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
17. 10 of 181 ProSoft Technology Inc April 23 2014 MVI56E MNET MNETXT ControlLogix Platform Modbus TCP IP Interface Module Start Here User Manual 1 Start Here In This Chapter WLiat c iini hee et Rt Medina 12 System Requirements 13 Package Contents 5 tiu na E URB 14 Settifig Jumpers De cp deu Pe ridet 15 Installing the Module in the Rack se 16 Importing the Sample Add On Instruction 18 Creating New RSLogix 5000 19 Connecting Your PC to the ControlLogix Processor 32 Downloading the Sample Program to the Processor 33 To get the most benefit from this User Manual you should have the following skills Rockwell Automation RSLogix software 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 MNET module s application port s ProSoft Technology Inc April 23 2014 Page 11 of 181 Start Here MVI56E MNET MNETXT ControlLogix Platform User Manual Modbus TCP IP Interface Module 1 1 What s New
18. 18505 20561 21075 21589 22103 22617 24673 25187 25701 26215 26729 28785 29299 29813 30327 30841 32639 32125 31611 31097 30583 28527 28013 27499 26985 26471 1 515 1029 1543 2057 4113 4627 5141 5655 6169 8225 8739 9253 9767 10281 12337 12851 13365 13879 14393 16449 16963 17477 17991 18505 20561 21075 21589 22103 22617 24673 25187 25701 26215 26729 28785 29299 29813 30327 30841 32639 32125 31611 31097 30583 28527 28013 27499 26985 26471 Float DATABASE DISPLAY 0 to 49 FLOAT Refresh counter 5 1 FQNANOOOE 000 1 QNANOOOE 000 9 18354962E 041 2 75509291E 040 1 97747944E 024 21076282 018 5 79887491 016 6 44492959 010 1 68752010E 007 4 41579286E 005 88127480 001 1 27530674 004 1 40447017 010 3 66483682E 012 9 55859400 014 04858893 021 2 73179652 023 2 98848446 029 7 77852805 031 2 02388230 034 93224776E 037 5 09760759E 035 5 74027813E U29 1 51029685E U026 3 9701060299E 024 62436112E 038 2 53936311 035 2 86023979E 029 7 52614210E 027 1 97859390E 024 21076282bE 018 5 79887491bE 016 6 44492959 010 1 68752010E 007 4 41579286E 005 88127480 001 1 27530674E 004 1 40447017E 010 3 66483682E 012 9 55859400E 014 04858893E 021 2 73179652E 023 2 98848446E 029 7 77852805E 031 2 02388230E 034 93224776E 037 5 09760759E 035 5 74027813E 029 1 51029685E 026 3 97016299E 024 Hexadecimal DATABASE DISPLAY 0 to 99 HEXADECIMAL FFFE FFFD FFFC 0000 0001 0002 0003 2223 2425 2627 2829 3031 3233 343
19. Connection Output Local1 0 Data MNET Output parameters Fault Code value SV Get System Value Ladder Diagram Main Class Name Module Instance Name MNET Attribute Name FaultCode Dest MNET_2 CONTROL FaultCode 04 Add On MVIS6 MNET and MVISBE MNET modules 56 Add On MVIS6 MNET and MVISBE AOISEMNET AOISEMNET_2 zs Connection Input Local 2 l Data Connection Output Local 2 0 Data MNET MNET 2 MainRoutine Add Branch Level Rung of APP VER ProSoft Technology Inc April 23 2014 Page 29 of 181 Start Here MVI56E MNET MNETXT ControlLogix Platform User Manual Modbus TCP IP Interface Module Adjusting the Input and Output Array Sizes Note 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 from ProSoft Configuration Builder 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 MNET 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 t
20. Example Client sent illegal Modbus Data location address MnetServStats ErrRec INT This counter increments each time an MNet port 2000 receives a bad command Example Client sent illegal function command MnetServStats CfgErrWord INT Error Configuration Word Contains a bitmap that indicates Client and server configuration errors MnetServStats CurrErr INT Not used MnetServStats LastErr INT Not used MBAPServStats CmdReq INT Not used MBAPServStats CmdResp INT Not used MBAPServStats CmdErr INT Not used MBAPServStats Requests INT This counter increments each time an MBAP port 502 request is received MBAPServStats Responses INT This counter is incremented each time an MBAP port 502 response message is sent MBAPServStats ErrSent INT This counter increments each time an MBAP port 502 sends an exception response to Client Example Client sent illegal Modbus Data location address MBAPServStats ErrRec INT This counter increments each time an MBAP port 502 receives a bad command Example Client sent illegal function command MBAPServStats CfgErrWord INT Configuration Error Word Contains a bitmap that indicates Client and server configuration errors MBAPServStats CurErr INT Not used MBAPServStats LastErr INT Not used ClientStats CmdReq INT This value is incremented each time a command request is issued ClientStats CmdResp INT This value is incremented each tim
21. Field 11 10 00 87 00 02 56 Page 148 of 181 ProSoft Technology Inc April 23 2014 MVI56E MNET MNETXT ControlLogix Platform Reference Modbus TCP IP Interface Module User Manual 5 5 12 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 from the Client s query f the server device receives the request without a communication error and can handle the query normally it returns a normal response f 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 f 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 f 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 valu
22. File Cancel Help 6 Select the sample ladder logic file for your firmware version To open the sample program 1 Onthe Connected to Go Online dialog box click the SELECT FILE button 2 Choose the sample program file that matches your firmware version and then click the SELECT button 3 RSLogix will load the sample program The next step is to configure the correct controller type and slot number for your application Page 164 of 181 ProSoft Technology Inc April 23 2014 MVI56E MNET MNETXT ControlLogix Platform Reference Modbus TCP IP Interface Module User Manual 5 8 2 Choosing the Controller Type The sample application is for a 1756 L63 ControlLogix 5563 Controller If you are using a different model of the ControlLogix processor you must configure the sample program to use the correct processor model 1 Inthe Controller Organization list select the folder for the controller and then click the right mouse button to open a shortcut menu 2 Onthe shortcut menu choose PROPERTIES This action opens the Controller Properties dialog box f Controller Properties MVI56 GI x Date Time Advanced SFC Execution File Redundancy Nonvolatile Memory General Serial Port System Protocol User Protocol Major Faults Minor Faults Vendor Allen Bradley Type 1756 L55 ControlLogix5555 Controller Change Type Revision 11 25 Change Revision Name MVI56 Example Logic forthe MVI5
23. If the command is a read command the data is read out of the database and a response message is built If the command is a write command the data is written directly into the database and a response message is built If the command is a write command and the pass through feature is utilized the write message is transferred to the processor ladder logic and is not written directly into the module s database unless it is returned as a change in the output image that overwrites data in the WriteData area as a result of such ladder logic processing 4 After the data processing has been completed in Step 3 a response is issued to the originating Client node Page 132 of 181 ProSoft Technology Inc April 23 2014 MVI56E MNET MNETXT ControlLogix Platform Reference Modbus TCP IP Interface Module User Manual Counters are available in the Status Block that permit the ladder logic program to determine the level of activity of the server driver An exception to normal processing is when the pass through mode is implemented In this mode all write requests are passed directly to the processor and are not placed in the database This permits direct remote control of the processor without changes in the intermediate database This mode is especially useful for Client devices that do not send both states of control For example a SCADA system may only send a SET command to a digital control point and never send a CLEAR command to that sa
24. Instance 4 Configuration Size 0 ProSoft Technology Inc April 23 2014 Page 25 of 181 Start Here MVI56E MNET MNETXT ControlLogix Platform User Manual Modbus TCP IP Interface Module 4 Click OK to confirm The new module is now visible 3 8 1 0 Configuration 6 1756 Backplane 1756 44 fa 0 1756 L63 My Controller BJ 1 1756 MODULE MNET BJ 2 1756 MODULE MNET_2 5 Expand the Tasks folder and then expand the MainTask folder 6 Onthe MainProgram folder click the right mouse button to open a shortcut menu On the shortcut menu choose NEW ROUTINE As an alternative to creating a separate NEW ROUTINE you could skip to Step 8 and import the AOI for the second module into the same routine you created for the first module 7 Inthe New Routine dialog box enter the name and description of your routine and then click OK 8 Select an empty rung in the new routine or an existing routine and then click the right mouse button to open a shortcut menu On the shortcut menu choose IMPORT RUNG f amp RSLogix 5000 My Controller 1756 1 63 MainProgram MainRoutine DER amp File Edit View Search Logic Communications Tools Window Help ax alsa S ael sale le Gia alal Oftline f E RUN EZ Path lt none gt zi No Forces b is Nod 8 Af e 2 w HL Favorites Add On Alarms Bit Timer Counter 1 MI Controller My Controller Controller Tags 28 Controller Fau
25. Interface Module User Manual 3 4 2 MNET STATUS The MNET STATUS controller tag structure has several lower level controller tag structures A few of them are described below MNET STATUS PassCnt This is the Program Scan Counter value It is incremented by a count of 1 each time a module s program cycle is complete MNET STATUS ClientStats Controller Tag Description CmdReq This value in this tag is incremented each time a Command Request is issued by the Client CmdResp This value in this tag is incremented each time a Command Response is received by the Client CmdErr This value in this tag is incremented each time an error message is received from a remote unit or a local error is generated for a command Requests This value in this tag is incremented each time a request message is issued Responses This value in this tag is incremented each time a response message is received ErrSent Reserved ErrRec Reserved CfgErrWord Applicable to Clients and servers This word encodes several potential errors using a bitmap For more information on the meanings of the various bits when set see Configuration Error Word page 104 CurrErr Applicable to Clients and servers Current error code number detected by the module LastErr Applicable to Clients and servers Previous error detected by the module MNET STATUS BlockStats These tags display the backplane Block Transfer statistics Control
26. MNET Module MVI56E MNET MNETXT ControlLogix Platform User Manual Modbus TCP IP Interface Module 2 2 3 Setting Module Parameters Notice that the contents of the information pane and the configuration pane changed when you added the MVI56E MNET module to the project Untitled ppf ProSoft Configuration Builder DER View Project Tools Help Default Project Name Information Ga Default Location MVIS6E MNET Configured MVIS6E MNET h MVI56E MNES 2 00 Module Values OK MNet Client 0 Values OK MNet Servers Values OK STATIC ARP TABLE Values OK Comment Values OK WATTCP Values OK Module Information Last Change Never Last Download Never Application Rev OS Rev Loader Rev MAC Address configEdit version 2 1 6 Build 4 EtherNet Configuration my ip 192 168 0 250 netmask 5 255 255 255 0 gateway 192 168 0 1 Module configuration lt MVIS6E MNET At this time you may wish to rename the Default Project and Default Location folders in the tree view Renaming an Object 1 Select the object and then click the right mouse button to open a shortcut menu From the shortcut menu choose RENAME 2 Type the name to assign to the object 3 Click away from the object to save the new name Configuring Module Parameters 1 Click on the sign next to the module icon to expand module information 2 Click on the sign next to any amp amp icon to view module infor
27. MNETXT ControlLogix Platform User Manual Modbus TCP IP Interface Module 2 2 9 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 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 o IP address fixed IP required o 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 my_ip 192 168 0 250 my_ip 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 Page 58 of 181 ProSoft Technology Inc April 23 2014 MVI56E MNET MNETXT ControlLogix Platform Configuring the MVIBGE MNET Module Modbus TCP IP Interface Module User Manual 2 3 Connecting Your PC to the Module With the module securely mounted connect one end
28. Manual 5 5 4 Read Holding Registers Function Code 03 Query Read 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 of Regs Data fof Regs Lo Error Check Field 11 03 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 thu
29. Protocol Specification The following pages give additional reference information regarding the Modbus protocol commands supported by the MVI56E MNET 5 5 1 About the MODBUS TCP IP 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 IP MODBUS TCP IP 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 IP commands to the server The MVIS6E MNET module works both as a Client and as a server Aside from the benefits of Ethernet versus serial communications including performance distance and flexibility for industrial networks the MODBUS TCP IP protocol allows for remote administration and control of devices over a TCP IP network The efficiency scalability and low cost of a MODBUS TCP IP network make this an ideal solution for industrial applications The MVI56E MNET module acts as an input output module between devices on a MODBUS TCP IP network and the Rockwell Automation backplane The module uses an inte
30. Reserved 1 This word contains the next write request block identification code 2 This word contains the result of the event request If a value of one 1 is present the command was successfully added to the queue If a value of zero 0 is present no room was found in the command priority queue 3 to 248 Spare 249 This word contains the block identification code 2000 requested by the processor Word 2 of the block can be used by the ladder logic to determine whether or not the command was successfully added to the command priority queue The command will fail if the queue for the port is already full at the time when the Event Command block is received by the module ProSoft Technology Inc Page 121 of 181 April 23 2014 Reference User Manual MVI56E MNET MNETXT ControlLogix Platform Modbus TCP IP Interface Module Controller Tags The elements of the MNET UTIL EventCmd controller tag array contain all the values needed to build one Modbus TCP IP command have it sent to the module and control the processing of the returned response block Controller Tag Description EventCmdTrigger Set this tag to 1 to trigger the execution of the Event Command EventCmdPending Temporary variable used to prevent a new Event Command block from being sent to the module until the previously sent Event Command block has been completely processed and a response block has been returned IPAddress En
31. Select Connection Type dropdown box Download files from PC to module STEP 1 Select Communication Path Select Connection Type 1756 ENBT v Ethernet 1 t 192 168 0 100 p 1 5 0 56 CIP Path Edit RSWho STEP 2 Transfer File s DOWNLOAD Test Connection 4 Click RSWHO to display modules on the network The MVI56E MNET module will automatically be identified on the network Browse Device Autobrowse Lieren 2s z Browsing node 0 found kstation Linx Gateways Ethernet 0 4 AB ETH 1 Ethernet 00 01 06 10 1 2 221 1756 ENET B 1756 ENET B GSC v16 1756 ENBT A 10 1 2 254 1756 EN2T 1756 EN2T B 105 102 0 65 1756 ENBT A 1756 ENBT A 89 Backplane 1756 A7 A 00 1756 L55 A 1061 5555 GSC vit 01 1756 module MVIB6E GSC 06 1756 ENBT A AB ETH 4 Ethernet _ 1 Ethernet EompactLogix Ethernet EontrolLogix Ethernet si Cancel 5 Select the module and then click OK 6 Inthe Download dialog box click DOWNLOAD ProSoft Technology Inc Page 73 of 181 April 23 2014 Configuring the MVI56E MNET Module MVI56E MNET MNETXT ControlLogix Platform User Manual Modbus TCP IP Interface Module Page 74 of 181 ProSoft Technology Inc April 23 2014 MVI56E MNET MNETXT ControlLogix Platform Ladder Logic Modbus TCP IP Interface Module User Manual 3 Ladder Logic In This Chapter 0 X Gontroller Tags ie
32. Technology Inc Page 21 of 181 April 23 2014 Start Here User Manual MVI56E MNET MNETXT ControlLogix Platform Modbus TCP IP Interface Module 1 7 2 Importing the 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 My Controller 1756 L63 MainProgram MainRoutine E File Edit View Search Logic Communications Tools Window Help alsm S 4 86 1 gt selel 018 aa Offline 0 F RUN E Path lt none gt No Forces Lan m OK No Edits a hel 4 Ht ab wo gt 5 D Favorites lt acon K K X Tmertomier 1 28 Controller My Controller amp amp Tasks MainTask MainProgram abe ues v A Program Tags MainRoutine Unscheduled Programs CutRung x Motion Groups Copy Rung Ungrouped Axes Add On Instructions amp Data Types Delete Rung G User Defined res ig Strings 28 Add On Defined Edit Rung 8 i Predefined Edit Rung Comment Eh Module Defined Trends I O Configuration Export Rung Accept Pending Rung Edits Verify Rung Go To Ctrl G Add Ladder Element Alt Ins
33. YES 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 Output Offset 0 to 4999 This parameter defines the start register for the Modbus command data in the internal database This parameter is enabled when a value greater than 0 is set For example if the Output Offset value is set to 3000 data requests for Modbus Coil Register address 00001 will use the internal database register 3000 bit O If the Output Offset value is set to 3000 data requests for Modbus Coil register address 00016 will use the internal database register 3000 bit 15 Function codes affected are 1 5 and 15 Bit Input Offset 0 to 4999 This parameter defines the start register for Modbus command data in the internal database This parameter is enabled when a value greater than 0 is set For example if the Bit Input Offset value is set to 3000 data requests for Modbus Input Register address 10001 will use the internal database register 3000 bit O If the Bit Input Offset is set to 3000 data requests for Modbus Coil register address 10016 will use the internal database register 3000 bit 15 Function code 2 is affected ProSoft Technology Inc Page 55 of 181 Apr
34. associated to the source module in the rack The connection between the source and destination modules is performed through the backplane Destination Module Slot Number The 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 MNET module o Ifthe 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 The maximum number of supported racks is six Click CONSTRUCT CIP PATH to build the path in text format Click OK to confirm the configured path Example 1 Local Rack Application For this example the MVI56E MNET module is located in the same rack as the 1756 ENBT that is connected to the PC MVI56E Module 1756 ENBT Ethemet Page 66 of 181 ProSoft Technology Inc April 23 2014 MVI56E MNET MNETXT ControlLogix Platform Configuring the MVIBGE MNET Module Modbus TCP IP Interface Module User Manual Rack 1 Slot Module Network Address 0 ControlLogix Processor 1 Any 2 MVI56E MNET 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 Ethernet lPconnect 192 168 0 100 p 1 s 0 56 CIP
35. be found in the Read Data area of the module s database at the locations specified by the pointer configuration parameters For more information see Backplane Error Status Pointer page 42 Client Error Status Pointer page 44 and Command Error Pointer page 45 ProSoft Technology Inc Page 101 of 181 April 23 2014 Diagnostics and Troubleshooting User Manual MVI56E MNET MNETXT ControlLogix Platform Modbus TCP IP Interface Module 4 3 1 Status Data Definition The following is a description of the controller tags in the MNETR STATUS controller tag structure which contains module server and Client status data Controller Tag Data Type Description PassCnt INT This value is incremented each time a complete program cycle occurs in the module ProductVersion INT This register displays the module software version number in decimal values For example if the version number is 1 51 it will display as 151 ProductCode INT 2 Module product code MnetServStats CmdReq INT Not used MnetServStats CmdResp INT Not used MnetServStats CmdErr INT Not used MnetServStats Requests INT This counter increments each time an MNet port 2000 request is received MnetServStats Responses This counter is incremented each time an MNet port 2000 response message is sent MnetServStats ErrSent INT This counter increments each time an MNet port 2000 sends an exception response to Client
36. byte s Style DATA MNETDATA Data read from module ReadData INT 600 Decimal Data read from module Set array equal to the size set in th WriteD ata 600 Decimal Data to write to module Set array equal to the size set in t STATUS MNETSTATUS Client Server Status and blocks status CONTROL MNETCONTROL MNET Module control warmboot coldboot etc UTIL MNETUTIL command event control Notice that these UDTs are the data types used to declare the MNET DATA ReadData and MNET DATA WriteData controller tag arrays Each UDT is commented in the Description column 3 3 Using Controller Tags You can use controller tags to View read and write data that is being transferred between the module and the processor View status data for the module Setup and trigger special functions Initiate module restarts Warm Boot or Cold Boot ProSoft Technology Inc Page 79 of 181 April 23 2014 Ladder Logic MVI56E MNET MNETXT ControlLogix Platform User Manual Modbus TCP IP Interface Module 3 4 Controller Tag Overview Controller Tag Description MNET DATA MNET input and output data transferred between the processor and the module MNET STATUS Status information MNET CONTROL Governs the data movement between the PLC rack and the module MNET UTIL Generic tags used for internal ladder processing DO NOT MODIFY The following sections describe each of these controller tag structures i
37. generated All other values will generate an encapsulated Modbus serial type message 6 Slave Address This word contains the Modbus node address for the 1 message This field should have a value from 1 to 247 7 Internal DB Adaress This word contains the internal Modbus address in 1 the module to use with the command This word can contain a value from 0 to 4999 8 Point Count This word contains the count parameter that determines 1 the number of digital points or registers to associate with the command 9 Swap Code This parameter specifies the swap type for the data This 1 option is valid only for function codes 3 and 4 Page 120 of 181 ProSoft Technology Inc April 23 2014 MVI56E MNET MNETXT ControlLogix Platform Reference Modbus TCP IP Interface Module User Manual 10 Modbus Function Code This word contains the Modbus function code 1 for the command 11 Device Database Address This word contains the Modbus address in 1 the server device to be associated with the command 12 to 247 Spare 236 When the module receives this request block it builds the command places the command in the command priority queue if the queue is not already full maximum capacity is 100 commands and returns a response block to tell the ladder logic whether or not the command has been successfully added to the queue Block Response from Module to Processor Word Offset Description 0
38. however the remote Client sends a count of two 2 for each 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 F oat Flag parameter is set to YES Page 54 of 181 ProSoft Technology Inc April 23 2014 MVI56E MNET MNETXT ControlLogix Platform Configuring the MVI56E MNET Module Modbus TCP IP Interface Module User Manual Float Start 0 TO 65535 Whenever the Float Flag parameter is set to YES this parameter determines the lowest Modbus Address received in commands from a remote Client to consider as requests to read or write floating point data All commands with address values greater than or equal to this value will be considered floating point data requests All commands with address values less than this value will be considered normal 16 bit register data requests This parameter is used only if the Float Flag is set to YES For example if a value of 7000 is entered all commands received with addresses of 47001 or 407001 and above will be considered as requests for floating point data and 32 bits of data will be returned for each count of one in the command You will also need to set the Float Offset parameter to an appropriate value whenever the Float Flag parameter is set to
39. order if such an option might be required in special circumstances A single Command Control block request can place up to six commands from the MNET Client 0 Command List into the command priority queue ProSoft Technology Inc Page 123 of 181 April 23 2014 Reference MVI56E MNET MNETXT ControlLogix Platform User Manual Modbus TCP IP Interface Module Block Request from Processor to Module Word Offset Description 0 Command Control block identification code of 5001 to 5006 The rightmost digit indicates the number of commands 1 to 6 to add to the command priority queue 1 This word contains the Command Index for the first command to be entered into the queue 2 This word contains the Command Index for the second command to be entered into the queue 3 This word contains the Command Index for the third command to be entered into the queue 4 This word contains the Command Index for the fourth command to be entered into the queue 5 This word contains the Command Index for the fifth command to be entered into the queue 6 This word contains the Command Index for the sixth command to be entered into the queue 7 to 247 Spare The last digit in the block identification code indicates the number of commands to process For example a block identification code of 5003 indicates that three commands are to be placed in the queue In this case the first three of the six available Command Index
40. 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 42 of 181 ProSoft Technology Inc April 23 2014 MVI56E MNET MNETXT ControlLogix Platform Configuring the MVIBGE MNET Module Modbus TCP IP Interface Module 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 The Write Register Count parameter specifies the size of the Write Data
41. series also comes with conformal coating to protect module components from corrosive environmental elements Page 12 of 181 ProSoft Technology Inc April 23 2014 MVI56E MNET MNETXT ControlLogix Platform Start Here Modbus TCP IP Interface Module User Manual 1 2 System Requirements The MVI56E MNET module requires the following minimum hardware and 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 MNET module The module requires 800 mA of available 5 VDC power and 3 mA of available 24 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 PCB Pentium II 450 MHz minimum Pentium 1 733 MHz or better recommended Supported operating systems o Microsoft Windows Vista o Microsoft Windows XP Professional with Service Pack 1 or 2 o 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
42. set to a nonzero value the command will be executed when the interval timer expires CONDITIONAL 2 The command will execute only if the internal data associated with the command changes This value is valid only for write commands ProSoft Technology Inc Page 49 of 181 April 23 2014 Configuring the MVI56E MNET Module MVI56E MNET MNETXT ControlLogix Platform User Manual Modbus TCP IP Interface Module Internal Address 0 to 65535 for bit level addressing Or 0 to 4999 for word level addressing This field specifies the 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 word level or register level address Poll Interval 0 to 65535 This parameter specifies the minimum interval between issuances of a command during continuous command execution 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 Reg Count Regs 1 to 125 Coils 1 to
43. the Module 1 Add the MVI56E MNET module to the project In the Controller Organization window select I O CONFIGURATION and click the right mouse button to open a shortcut menu On the shortcut menu choose NEW MODULE 1 0 Configuration ie 1756 Backplane 1756 A fq 0 1756163 5 New Module This action opens the Select Module dialog box L Select Module Module Description Analog Communications Controllers Digital H Drives Motion Other 1756 MODULE Specialty By Category Generic 1756 Module By Vendor Vendor Allen Bradley Eind amp ddFavoie Favorites 2 Select the 1756 MODULE GENERIC 1756 MODULE from the list and click OK This action opens the New Module dialog box In the New Module dialog box enter the following values 3 Parameter Value Name Enter a module identification string Example MNET Description Enter a description for the module Example MopBus TCP IP INTERFACE MODULE Comm Format Select DATA INT Slot Enter the slot number in the rack where the MVIS6E MNET module is located Input Assembly Instance 1 Input Size 250 Output Assembly Instance 2 Output Size 248 Configuration Assembly Instance 4 Configuration Size 0 Page 20 of 181 ProSoft Technology Inc April 23 2014 MVI56E MNET MNETXT ControlLogix Platform Start Here Modbus TCP I
44. 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 has read this Warranty understands it and is bound by its Terms Page 176 of 181 ProSoft Technology Inc April 23 2014 MVI56E MNET MNETXT ControlLogix Platform Support Service amp Warranty Modbus TCP IP Interface Module 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 Warra
45. to an Existing Application 168 6 Support Service amp Warranty 169 Contacting Technical enne nnne nennen 169 6 1 Return Material Authorization RMA Policies and Conditions 171 6 1 Returning Any Product uhi tire ote 171 6 1 Returning Units Under Warranty sssseeeneeeen nennen 172 Returning Units Out of 1 2 2 172 6 2 LIMITED WARRANTY atu ertt tette etin og 173 6 2 1 What Is Covered By This enne 173 6 2 2 What Is Not Covered By This 174 6 2 3 Disclaimer Regarding High Risk Activities 174 6 2 4 Intellectual Property nennen 175 6 2 5 Disclaimer of all Other Warranties 175 6 2 6 Limitation of Remedies Ta nnne nnns 176 6 2 7 Time Limit for Bringing Suit 176 6 2 8 No Other Warranties seessssssssseseeeeeeene ennemis tenens 176 6 2 9 Allocation Ot RISKS te netten d te ee pe t 176 6 2 10 Controlling Law and Severability sees 177 Index 179 ProSoft Te
46. to new projects Note During startup and initialization the MVIS6E MNET 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 2 2 1 Upgrading from MVI56 MNET in ProSoft Configuration Builder MVI56E MNET modules are fully backward compatible with MVI56 MNET modules However you will need to convert your MVI56 MNET configuration in ProSoft Configuration Builder to a form that your new MVI56E MNET module will accept when you download it ProSoft Configuration Builder version 2 2 2 or later has an upgrade option that easily performs this conversion while preserving all your configuration settings and any name you may have given your module Important For this procedure you need to have ProSoft Configuration Builder version 2 2 2 or later installed on your PC You can download the latest version from www prosoft technology com Page 36 of 181 ProSoft Technology Inc April 23 2014 MVI56E MNET MNETXT ControlLogix Platform Modbus TCP IP Interface Module Configuring the MVI56E MNET Module User Manual 1 In ProSoft Configuration Builder s tree view click the MODULE icon and right click to open a shortcut menu Default Project ai Default Location Delete Rename Copy Choose Module Type View Configuration
47. transferred from the module to the processor read block input image or from the processor to the module write block output image in each block transfer The block structure of each block type depends on the data content and the data transfer function to be performed by the block The module uses the following block identification numbers Block ID Range Descriptions 4 Null block 0 For firmware versions earlier than 2 05 this is a null block For firmware versions 2 05 and newer block 0 contains the same data as block 1 This feature enhances performance especially when using less than 200 words of read write data f Read Register Count in the module configuration file is set gt 200 words Block ID 0 is not used f Read Register Count in the module configuration file is set gt 0 and lt 200 words Block ID contains the same data as block 1 both read data and status data 1 to 25 Read or Write blocks 1000 to 1024 Initialize Output Data blocks 2000 Event Command block 5001 to 5006 Command Control blocks 9956 Formatted Pass through block from function 6 or 16 with word data 9957 Formatted Pass through block from function 6 or 16 with floating point data 9958 Formatted Pass through block from function 5 9959 Formatted Pass through block from function 15 9960 Formatted Pass through block from function 22 9961 Formatted Pass through block from function 23 997
48. transmitting a command if no response is received from the addressed server The value to use depends on the type of communication network used and the expected response time of the slowest device on the network Retry Count 0to 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 Client driver will issue Function Code 3 6 and 16 commands read and write Holding Registers to a remote server when it is moving 32 bit floating point data If the remote server 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 Client driver will send values from two consecutive 16 bit internal memory registers 32 total bits for each count in a write command or receive 32 bits per count from the server for read commands Example Count 10 Client driver will send 20 16 bit registers for 10 total 32 bit floating point values ProSoft Technology Inc Page 45 of 181 April 23 2014 Configuring the MVI56E MNET Module MVI56E MNET MNETXT ControlLogix Platform User Manual Modbus TCP IP Interface Module If however the remote server expects to use a count of two 2 for each 32 bit floating point value it sends or receives 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 w
49. words are swapped then the bytes in each word are swapped 1234 4321 Swap BYTES 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 Node IP Address XXX XXX XXX XXX The IP address of the device being addressed by the command Service Port 502 or other port numbers supported on a 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 ProSoft Technology Inc Page 51 of 181 April 23 2014 Configuring the MVI56E MNET Module MVI56E MNET MNETXT ControlLogix Platform User Manual Modbus TCP IP Interface Module 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 IP Address parameter page 51 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 broad
50. 0 Force Multiple Coils Function Code 15 seen 147 5 5 11 Preset Multiple Registers Function Code 16 148 5 5 12 Modbus Exception 149 5 6 Using the Optional Add On Instruction Rung 151 5 6 1 Betore You Beg o ete E te arbe edes 151 5 6 2 Gi UR MEM 151 5 6 3 Installing the Rung Import with Optional Add On Instruction 152 5 6 4 Reading the Ethernet Settings from the Module 156 5 6 5 Writing the Ethernet Settings to the Module 157 5 6 6 Reading the Clock Value from the Module seen 158 5 6 7 Writing the Clock Value to the 2 159 5 7 Adding the Module to an Existing Project se 160 5 8 Using the Sample Program 163 5 8 1 Opening the Sample Program in RSLogix esses 163 5 8 2 Choosing the Controller Type ssssssssseseeenenneeeenen nnne 165 5 8 3 Selecting the Slot Number for the Module sse 166 5 8 4 Downloading the Sample Program to the 167 5 8 5 Adding the Sample Ladder
51. 0 Function 99 indication block 9990 Set Module IP Address block 9991 Get Module IP Address block 9996 Unformatted Pass through block with raw Modbus message 9998 Warm boot block 9999 Cold boot block ProSoft Technology Inc Page 111 of 181 April 23 2014 Reference MVI56E MNET MNETXT ControlLogix Platform User Manual Modbus TCP IP Interface Module These block identification codes can be broken down into two groups Normal data transfer blocks Read and Write blocks 1 to 25 Special function blocks Initialize Output Data blocks 1000 to 1024 Event Command block 2000 Command Control blocks 5001 to 5006 Pass through blocks 9956 to 9961 9970 and 9996 Module IP Address blocks 9990 and 9991 Warm boot and Cold boot blocks 9998 and 9999 Page 112 of 181 ProSoft Technology Inc April 23 2014 MVI56E MNET MNETXT ControlLogix Platform Reference Modbus TCP IP Interface Module User Manual 5 2 1 Normal Data Transfer Blocks Normal data transfer includes the paging of user data from the module s internal database registers 0 to 4999 as well as paging of status data These data are transferred through read input image and write output image blocks The following topics describe the function and structure of each block Read Block These blocks of data transfer information from the module to the ControlLogix processor The following table describes the structure of the input image Read Block
52. 181 ProSoft Technology Inc April 23 2014 MVI56E MNET MNETXT ControlLogix Platform Reference Modbus TCP IP Interface Module User Manual Modbus TCP IP Client Master Actively reads data from and writes data to Modbus TCP IP devices using MBAP or Encapsulated Modbus message formats Transmit Modbus Function Codes 1 2 3 4 5 6 7 15 and 16 Offers one Client connection with up to 100 commands 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 Commands Status Data Error codes counters and module status available from module memory through the server through the Client or through the ladder logic and controller tags in RSLogix 5000 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 Hz to 150 Hz Relative Humidity 5 to 95 without condensation LED Indicators Battery Status ERR Application Status APP Module Status OK 4 Character Scrolling Alpha Shows Module Version IP Application Port Numeric LED Display Setting P
53. 4 Close ProSoft Discovery Service 5 Click DOWNLOAD to transfer the configuration to the module 2 4 1 Using ClPconnect to Connect to the Module You can use ClPconnect to connect a to the MVIS6E MNET module over Ethernet using Rockwell Automation s 1756 ENBT EtherNet IP module This allows you to configure the MVI56E MNET module and network upload and download files and view network and 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 ControlNet node numbers and slot numbers of any 1756 CNBx ControlNet Bridge modules in the path The slot number of the MVI56E MNET in the destination ControlLogix chassis the last ENBT CNBx and chassis in the path To use ClPconnect follow these steps Page 64 of 181 ProSoft Technology Inc April 23 2014 MVI56E MNET MNETXT ControlLogix Platform Configuring the MVIBGE MNET Module Modbus TCP IP Interface Module User Manual 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 Si Ethernet ea ProSoft Discovery Service PDS CIPconnect t192 168 0 100 p 1 s 0 CIP Path E dit Test Connection Cancel 2 Click CIP PATH EDIT to open the C Pconnect Path Editor dialog box C
54. 5 4243 4445 4647 4849 5051 5253 5455 6263 6465 6667 6869 7071 7273 7475 8283 8485 8687 8889 9091 9293 9495 0203 0405 0607 0809 1011 1213 1415 2223 2425 2627 2829 3031 3233 3435 4243 4445 4647 4849 5051 5253 5455 6263 6465 6667 6869 7071 7273 7475 8283 8485 8687 8889 9091 9293 9495 Use the scroll bar on the right edge of the window to view each page 100 words of data Page 100 of 181 ProSoft Technology Inc April 23 2014 MVI56E MNET MNETXT ControlLogix Platform Diagnostics and Troubleshooting Modbus TCP IP Interface Module User Manual 4 3 Reading Status Data from the Module Module status information is useful for troubleshooting and can be accessed in several different ways In the ladder logic s MNET STATUS controller tag structure The MVI56E MNET module returns status data in the input image that can be used to determine the module s operating status This data is transferred from the module to the ControlLogix processor continuously as part of the normal data transfer block sequence page 113 You can view this data in the MNET STATUS controller tag structure in the ladder logic For more information see the Status Data Definition page 102 In ProSoft Configuration Builder s Diagnostics screens For more information see the section on PCB Diagnostics page 96 In database locations specified by Error Status Pointers optional If optional Error Status Pointers are enabled the status data can also
55. 6 module Description Chassis Type Slot Cancel Apply Help 3 Click the CHANGE TYPE or CHANGE CONTROLLER button This action opens the Change Controller dialog box Change Controller x Changing the controller type will change delete and or invalidate the controller properties and other project data that is not valid for the new controller type From Type 1256 63 ControlLogix5563 Controller Revision 13 25 Revision 1 s Cancel Help 4 Open the TYPE dropdown list and then select your ControlLogix controller 5 Select the correct firmware revision for your controller if necessary 6 Click OK to save your changes and return to the previous window ProSoft Technology Inc Page 165 of 181 April 23 2014 Reference MVI56E MNET MNETXT ControlLogix Platform User Manual Modbus TCP IP Interface Module 5 8 3 Selecting the Slot Number for the Module The sample application is for a module installed in Slot 1 in a ControlLogix rack The ladder logic uses the slot number to identify the module If you are installing the module in a different slot you must update the ladder logic so that program tags and variables are correct and do not conflict with other modules in the rack To change the slot number 1 Inthe Controller Organization list select the module and then click the right mouse button to open a shortcut menu 2 Onthe shortcut menu choose PROPER
56. 800 This parameter specifies the number of 16 bit registers or binary bits to be transferred by the command Functions 5 and 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 3 4 and 16 this parameter sets the number of registers to be transferred by the command Page 50 of 181 ProSoft Technology Inc April 23 2014 MVI56E MNET MNETXT ControlLogix Platform Configuring the MVI56E MNET Module Modbus TCP IP Interface Module User Manual 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 Wonps amp Bytes The
57. April 23 2014 Diagnostics and Troubleshooting MVI56E MNET MNETXT ControlLogix Platform User Manual Modbus TCP IP Interface Module 4 3 2 Configuration Error Word The Configuration Error Word contains Client and server configuration error indications in a bit mapped format Specific bits in the module s Configuration Error Word are turned on set to 1 to indicate various configuration errors The Configuration Error Word appears in three separate MNET STATUS controller tags Since there is only one Configuration Error Word for the whole module each of these tags contains exactly the same data even though the tag name might imply otherwise Multiple copies of the same module error data have been included in these different controller tag locations for your convenience when troubleshooting Bits set to 1 in the Configuration Error Word indicate the following errors Bit Description Hex Value 0 Reserved not currently used 0001h 1 Reserved not currently used 0002h 2 Reserved not currently used 0004h 3 Reserved not currently used 0008h 4 Invalid retry count parameter Client only 0010h 5 The float flag parameter is not valid Client or server 0020h 6 The float start parameter is not valid Client or server 0040h 7 The float offset parameter is not valid Client or server 0080h 8 The ARP Timeout is not in range ARP Timeout parameter 0 or 0100h greater than 60000 millise
58. BBMNET E MNET MNETMODULEDEF Output parameters m MNET DATA MNETDATA MNET DATA ReadData INT BOO MNET DATA WriteData INT BOO MNETSTATUS MNET CONTROL MNETCONTROL _ MNET UTIL MNETUTIL Each controller tag in the Add On Instruction is commented in the Description column Notice that the Data Type column displays the data types used to declare each controller tag controller tag array or controller tag structure Individual controller tags are declared with basic data types such as INT and BOOL Controller tag arrays are declared with arrays of basic data types Controller tag structures are declared with user defined data types UDTs ProSoft Technology Inc Page 77 of 181 April 23 2014 Ladder Logic MVI56E MNET MNETXT ControlLogix Platform User Manual Modbus TCP IP Interface Module 3 2 User Defined Data Types UDTs User defined data types UDTs allow users to organize collections of data types into groupings These groupings or data type structures can then be used to declare the data types for controller tag structures Another advantage of defining a UDT is that it may be re used in other controller tag structures that use the same data types The Add On Instruction Import Rung ladder logic for the module has pre defined UDTs You can find them in the User Defined subfolder located in the Data Types folder in the Controller Organizer pane of the main RSLog
59. CTION button to verify that the module is accessible with the current settings Connection Setup Select Connection Type v Ethernet 192 168 0 253 ProSoft Discovery Service PDS Browse Device s CiPconnect Test Connection Cancel 7 Ifthe Test Connection is successful click CONNECT The Diagnostics menu will display in the Diagnostics window Ci Diagnostics Connection Log Module ANAS MVISGE MNET_SLOT4 Time 09 03 MODULE Select item within MVIS6E MNET for diagnostic information Config NIC Status Static ARP aa BACKPLANE Status aa MNET CLIENT 0 Contig Status Command List Command Status sa MNET SERVER Config Status se DATABASE ASCII Decimal Hex Float Path Ethernet 105 102 0 25 Page 62 of 181 ProSoft Technology Inc April 23 2014 MVI56E MNET MNETXT ControlLogix Platform Configuring the MVI56E MNET Module Modbus TCP IP Interface Module User Manual 2 4 Downloading the Project to the Module Note For alternative methods of connecting to the module with your PC refer to Using ClPconnect to Connect to the Module page 64 or Using RSWho to Connect to the Module page 73 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 MNET module 2 Open the PROJECT men
60. Command List must be defined in the configuration This list contains up to 100 individual entries with each entry containing the information required to construct a valid command This includes the following Command enable mode o 0 disabled o 1 continuous o 2 conditional IP address and service port to connect to 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 Selects the number of words to be transferred 1 to 100 Poll Delay 1 10 seconds For information on troubleshooting commands see Client Command Errors page 105 ProSoft Technology Inc Page 135 of 181 April 23 2014 Reference MVI56E MNET MNETXT ControlLogix Platform User Manual Modbus TCP IP Interface Module 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 ports on the module are 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 li
61. D must be ON solid or Blinking for Ethernet communication to be possible ProSoft Technology Inc April 23 2014 Page 89 of 181 Diagnostics and Troubleshooting MVI56E MNET MNETXT ControlLogix Platform User Manual Modbus TCP IP Interface Module 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 The module is not receiving adequate power or is not securely Green plugged into the rack May also be OFF during configuration download GREEN The MVI56E MNET 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 The firmware is initializing during startup The firmware detects an on board hardware problem during startup Failure of application port hardware during startup module is shutting down module is rebooting due to a ColdBoot or WarmBoot request from the ladder logic or Debug Menu OK Redor OFF The module is not receiving adequate power or is not securely Green 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 i
62. Device Failed To Respond Specialized use in conjunction with gateways indicates that no response was obtained from the target device Usually means that the device is not present on the network Page 150 of 181 ProSoft Technology Inc April 23 2014 MVI56E MNET MNETXT ControlLogix Platform Reference Modbus TCP IP Interface Module User Manual 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 MVIS56EMNET Optional AddOn Rung v 0 15 from www prosoft technology com or copy it from the ProSoft Solutions DVD Save a copy a folder in your PC 5 6 2 Overview The Optional Add On Instruction Rung Import contains optional logic for MVI56E MNET 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
63. ETXT ControlLogix Platform Support Service amp Warranty Modbus TCP IP Interface Module 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 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 Januar
64. EthernetMSG ReadClockMSG WriteClockMSG MNETETHERNETTYPE MNETEVENTCMD MNETINITOUTDATA MNETIPADDRESS MNETMODULEDEF MNETPASSTHRU MNETSTATS MNETSTATUS MNETUTIL Cg Strings 19 22 2008 4 04 32 PM PSFTmrodrigues 1213 2008 5 16 00 PM Edited By PSF Tiakamal Source Protectio Source not available Viewable i lt MainRoutine AOIS6EMNET_Optional 4 Rung 0 of 2 ProSoft Technology Inc April 23 2014 Page 153 of 181 Reference MVI56E MNET MNETXT ControlLogix Platform User Manual Modbus TCP IP Interface Module You will notice that new tags have been imported four Message tags MVIS56MNETClock and MVIS6MNETEthernet tags fc RSLogix 5000 L63 1756 163 Controller Tags L63 controller ia File Edit View Search Logic Communications Tools Window Help alsa S asale 2018 215 9 Offline f m RUN EZ Path lt none gt gt amp No Forces b Bor No Edits e e Eos 50 e m a nee Aas AA 1 3 Controller L63 Scope fa L63 Show Show All Controller Tags e 3 Controller Fault Handler Force Mask Data Type Power Up Handler s c m ADIBEEMNET D Tasks ADIBEMNET EE v ADIBEMNET 68 MainTask aoe AB 1756 MODUL g MainProgram NT UN 1756 MODUL B Program Tags dem m AB 1756_MODUL EB MainRoutine 65 Unscheduled Programs EC TA MNETMODULED Out 27 29 Motio
65. Export Configuration File s Load Config File Change Module Type to MVIS6E MMET Download From PC to Device Upload From Device to PC Diagnostics 2 On the shortcut menu select CHANGE MODULE TYPE TO MVI56E MNET ProSoft Technology Inc April 23 2014 Page 37 of 181 Configuring the MVI56E MNET Module MVI56E MNET MNETXT ControlLogix Platform User Manual Modbus TCP IP Interface Module 2 2 2 Setting Up the Project To begin start PROSOFT CONFIGURATION BUILDER PCB Set Program Access and Defaults WA Windows Catalog A Windows Update M Microsoft Update e Accessories e Administrative Tools fi Programs faa ProSoft Technology c ProSoft Configuration Builder Documents gt e Internet Explorer e ProSoft Transport Path Editor E Settings gt W Paint ProSoft Discovery Service 4 Search Windows Media Player Help and Support Run ShutDown tg 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 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 Projec
66. Hacer Driver 2 i Data Data Storage Backplane 4999 45000 Configur ation Event Command Event 5 5 Control 1 The Client driver obtains configuration data when the module restarts This includes the timeout parameters and the Command List These values are used by the driver to determine the type of commands to be issued to servers on the Modbus TCP IP network 2 When configured the Client driver begins transmitting read and or write commands to servers on the network The data for write commands is obtained from the module s internal database 3 Assuming successful processing by the server specified in the command a response message is received into the Client driver for processing Command Control Page 134 of 181 ProSoft Technology Inc April 23 2014 MVI56E MNET MNETXT ControlLogix Platform Reference Modbus TCP IP Interface Module User Manual 4 Data received from the server is passed into the module s internal database if the command was a read command Status information is routinely returned to the processor in the input images Special functions such as Event Commands and Command Control options can be generated by the processor and sent to the Client driver for action Client Command List In order for the Client to function the module s MNET Client x
67. IBGEMNETEthernet Config IP 1 MVIBBEMNETEthernet Config IP 2 MVIBGEMNETEthernet Config IP 3 MVIBBEMNETEthemet Config Netmask MVIBBEMNETEthernet Config Netmask 0 MVIBBEMNETEthernet Config Netmask 1 cF MVIBBEMNETEthemet Config Netmask 2 MVIBBEMNETEthernet Config Netmask 3 MVIBBEMNETEthemet Config G ateway MVIBBEMNETEthemet Config G ateway O MVIBBEMNETEthernet Config G ateway 1 MVIBBEMNETEthernet Config Gateway 2 MVIBBEMNETEthemet Config G ateway 3 o om an le le fe Je fs Gt fe tn ed un tn un tn RI Ov ON eo P After the message is executed the MVISGMNETEthernet Write bit resets to 0 To check the status of the message refer to the WriteEthernetMSG tag MVIBBEMNETEthemet MVIBSBEMNETEthemet Riead MVIBBEMNETEtheret Write MVIBBEMNETEthemet Config MVI56EMNETEtheret Config IP MVIBBEMNETEthernet Config IP 0 MVIBBEMNETEthernet Config IP 1 MVIBBEMNETEthemet Config IP 2 MVIBGEMNETEthernet Config IP 3 MVIBBEMNETEthemet Config Netmask MVIBBEMNETEthemet Config Netmask MVIBBEMNETEthernet Config Netmask 1 MVIBBEMNETEthemet Config Netmask 2 MVIBBEMNETEthemet Config Netmask 3 MVIBBEMNETEtheret Config Gateway MVIBBEMNETEthernet Config G ateway 0 MVIBBEMNETEthemet Config Gateway 1 MVIBBEMNETEthernet Config Gateway 2 MVIBBEMNETEthermet Config G ateway 3 Wri
68. IPconnect Path Editor L C f Connect PATH EDITOR Source Module IP Source Module Node Destination Module dress Address Slot Number BE 1756 ENBT 1921620100 MVISEE Modile v 0 No Source Module Destination Module t 192 168 0 100 p 1 5 0 Add Rack J Delete Rack J Construct CIP Path The C Pconnect Path Editor allows you to define the path between the PC and the MVI56E MNET 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 ProSoft Technology Inc Page 65 of 181 April 23 2014 Configuring the MVI56E MNET Module MVI56E MNET MNETXT ControlLogix Platform User Manual Modbus TCP IP Interface Module MVI5GE MNET module is located in the same rack as the first 1756 ENBT module select RACK No 1 and configure the associated parameters If the 56 is available 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
69. IS6MNET Data Types Del Enter Delete Rung Add Rung Edit Rung Add On MVIS6 MNET MVIS6E MNET modules AOISEMNET Ctrl D Trends Edit Rung Comment J Configuration amp 1756 Backplane 1756 44 ff 0 1756 L63 My Controller f 1 1756 MODULE MNET Import Rung Export Rung MNET Add On MVI56 MNET and MVIS6E AOISBMNET Connection Input Connection Output Local1 O Data AOISBMNET Local1 Data MNET Type Ladder Diagram Main Description Verify Rung Go To Ctri G a Add Ladder Element Alt Ins 2 Navigate to the folder where you saved Rung 0 of 1 MVI56EMNET_Optional_AddOn_Rung_v1_0 L5X and select the file Import Rungs Look in O MVI56E_MNET E3 e amp rkt H MVIS amp E MNET AddOn Rung vi 4 L5X B MVIS6 E MNET Optional AddOn Rung v1 0 L5X My Recent Documents Desktop My Documents My Computer E amp E MNET Optional AddOn Rung v1_0LX v RSLoaix 5 Files containing 4 Pur Y Into File name My Network Files of type Places Overwrite Selected Rungs Cancel Help Page 152 of 181 ProSoft Technology Inc April 23 2014 MVI56E MNET MNETXT ControlLogix Platform Modbus TCP IP Interface Module Reference User Manual In the mport Configuration window click OK Import Configuration Tags Data Types Add On Inst
70. Inc Page 173 of 181 April 23 2014 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 programming 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 o
71. MVI56E MNET MNETXT ControlLogix Platform Modbus TCP IP Interface Module Diagnostics and Troubleshooting User Manual 4 2 1 Connecting to the Module s Web Page The module s internal web server provides access to general product information firmware download link and links to ProSoft Technology s Web site 1 In ProSoft Discovery Service select the module and then click the right mouse button to open a shortcut menu JA 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 2 Onthe shortcut menu choose VIEW MODULE S WEBPAGE FUNCTIONS Modbus TCP IP Module for ControlLogix gt Firmware T MVISGE MNET Upgrade gt Set Date amp Time Module Name MVIS6E MNET Ethernet Address MAC 00 iC b Technical Support IP Addre gt Homepage Product Revision Firmware Version Date Number 00 34 91 RESOURCES ProSoft Technology Rockwell Automation Modbus Organization ProSoft Technology Inc April 23 2014 Page 95 of 181 MVI56E MNET MNETXT ControlLogix Platform Modbus TCP IP Interface Module Diagnostics and Troubleshooting User Manual 4 2 2 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 submenu
72. 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 ProSoft Configuration Builder PCB New Windows software for diagnostics connecting via the module s Ethernet port ClPconnect 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 address 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 T 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 XT series for Extreme Environments The MVI56E MNETXT is part of the new XT series designed to work at extreme temperatures and in harsh or caustic environments XT series modules operate over a wider temperature range than the standard MVI56E series The XT
73. MainRoutine f 4 Page 22 of 181 ProSoft Technology Inc April 23 2014 MVI56E MNET MNETXT ControlLogix Platform Start Here Modbus TCP IP Interface Module User Manual 4 Navigate to the location on your PC where you saved page 18 the Add On Instruction for example My Documents or Desktop Select the 56 ADDON RuNG v1 4 L5X file Import Rung in E Desktop v e Y My Computer my Documents Quy Network Places downloads MVISS E MNET AddOn Rung vi 4 L5X File name wvis E MNET AddOn Rung vi 4LEX v Import Files of type RSLogix 5000 XML Files L5X Cancel This action opens the mport Configuration dialog box showing the controller tags that will be created Import Configuration Tags Data Types Add On Instructions ADISBMNET Create New Local 1 4B 1756_MOD Use Existing Local1 0 4B 1756_MOD Use Existing MNETMODUL Output parameters Create New 5 If you are using the module in a different slot or remote rack select the correct connection input and output variables that define the path to the module If your module is located in Slot 1 of the local rack this step is not required ProSoft Technology Inc Page 23 of 181 April 23 2014 Start Here MVI56E MNET MNETXT ControlLogix Platform User Manual Modbus TCP IP Interface Module 6 Click OK to confirm the import RSLogix 5000 will indicate that the import is in progress Importi
74. P Interface Module User Manual Important You must select the COMM FORMAT as DATA INT in the dialog box otherwise the module will not communicate over the backplane of the ControlLogix rack 4 Click OK to continue 5 Edit the Module Properties Select the REQUESTED PACKET INTERVAL value for scanning the I O on the module This value represents the minimum frequency at which 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 should work with most applications lil Module Properties Local 1 1756 MODULE 1 1 General Connection Module Info Backplane Requested Packet Interval RPI ms 0 2 750 0 ms P Inhibit Module Major Fault On Controller If Connection Fails while in Run Mode Module Fault Status Offline 6 Save the module Click OK to close the dialog box Notice that the module now appears in the Controller Organization window Controller My Controller A Controller Tags Controller Fault Handler Power Up Handler amp j Tasks z MainTask 28 MainProgram Unscheduled Programs Motion Groups Ungrouped Axes Add On Instructions amp Data Types Cj User Defined Ge Strings 18 Add On Defined Predefined 88 Module Defined Trends amp 1 0 Configuration 1756 Backplane 1756 A4 fa 0 1756 163 My Controller 8 1 1756 MODULE MNET ProSoft
75. Path Edit RSWho STEP 2 Transfer File s DOWNLOAD Test Connection 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 a C pconect PATH EDITOR Source Module IP Source Module Node Destination Module No Source Module ies Henen Destination Module Slot Number B oor 192 168 0100 MEI MVISE Module 2 t 192 168 0 100 p 1 5 2 Add Rack Delete Rack Construct CIP Path OK Cancel ProSoft Technology Inc Page 67 of 181 April 23 2014 Configuring the MVI56E MNET Module MVI56E MNET MNETXT ControlLogix Platform User Manual Modbus TCP IP Interface Module 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 ENST f Ethernet 168 50 ilt I CIPconnect t 192 168 0 100 p 1 5 0 56 CIP Path Edit RSWho STEP 2 Transfer File s DOWNLOAD i Test Connection 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 STEP 1 Select Communication Path Select Connection Type 1756 ENBT v SEIDEVICEIE Ethernet ProSoft Configuration Builder CIPconnect Successfully Connected STEP 2 Transfer Fil DO
76. ProSoft Where Automation Connects inRAec MVI5GE MNET MNETXT ControlLogix Platform Modbus TCP IP Interface Module April 23 2014 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 2014 ProSoft Technology Inc All rights reserved MVI56E MNET MNETXT User Manual April 23 2014 ProSoft Technology ProLinx 9 inRAx 9 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 DVD and are available at no charge from our web site www prosoft technology com Important Safety Information North America Warnings A B C D Warning Explosion Hazard Substitution of component
77. Processor Word Offset Description Length 0 Reserved 1 1 1000 to 1024 1 2 to 248 Spare 247 249 1000 to 1024 1 Ladder logic subtracts 1000 from the value contained in word 249 to determine a block index This bock index determines which 200 word block of data will be taken from the ReadData array and placed in the output image to be returned to the module Block Response from Processor to Module Word Offset Description Length 0 1000 to 1024 1 1 to 200 Output data to preset in module 200 201 to 247 Spare 47 ProSoft Technology Inc Page 119 of 181 April 23 2014 Reference MVI56E MNET MNETXT ControlLogix Platform User Manual Modbus TCP IP Interface Module Event Command Blocks 2000 Note Event Commands are not needed for normal Modbus command list polling operations and are needed only occasionally for special circumstances During routine operation the module continuously cycles through the user defined MNET Client 0 Command List page 47 examining commands in the order they are listed and sending enabled commands on the network However the module also has a special command priority queue which is an internal buffer that holds commands from special function blocks until they can be sent on the network When one or more commands appear in the command priority queue 1 The routine polling process is temporarily interrupted 2 commands in the command priority queue ar
78. STATUS controller tag structure in the ladder logic For more information see the Status Data Definition page 102 ProSoft Technology Inc April 23 2014 Page 115 of 181 Reference MVI56E MNET MNETXT ControlLogix Platform User Manual Modbus TCP IP Interface Module Write Block These blocks of data transfer information from the ControlLogix processor to the module The following table describes the structure of the output image Write Block from Processor to Module Word Offset Description Length 0 Write Block ID 1 1 to 200 Write Data 200 201 to 247 Spare 46 247 Select Priority Read Block 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 200 words block offsets 1 to 200 of data Page 116 of 181 ProSoft Technology Inc April 23 2014 MVI56E MNET MNETXT ControlLogix Platform Reference Modbus TCP IP Interface Module User Manual Select Priority Read Block Write Block Offset 247 Note The Select Priority Read Block feature is only available for firmware versions 1 36 000 and newer This register allows the processor to select which read blocks will be returned from the module If this register equals zero the module will return all read blocks in sequential order If this register has a non zero value the module will return the read block selected and the following one
79. TIES This action opens the Module Properties dialog box lil Module Properties Local 1 1756 MODULE 1 1 General Connection Module Info Backplane Type 1756 MODULE Generic 1756 Module Parent Local Connection Parameters Assembly Instance Size 250 H 16 bit Name Input 1 Description Output 2 248 E 16 bit Configuration 4 0 8 bit Comm Format 9 Slot Zz Status Offline Cancel Apply Help 3 Inthe SLOT field use the up and down arrows on the right side of the field to select the slot number where the module will reside in the rack and then click OK RSLogix will automatically apply the slot number change to all tags variables and ladder logic rungs that use the MVI56E MNET slot number for computation Page 166 of 181 ProSoft Technology Inc April 23 2014 MVI56E MNET MNETXT ControlLogix Platform Reference Modbus TCP IP Interface Module User Manual 5 8 4 Downloading the Sample Program to the Processor To download the sample program from RSLogix 5000 to the ControlLogix processor Note The key switch on the front of the ControlLogix module must be in the REM position 1 If you are not already online to the processor open the COMMUNICATIONS menu and then choose DOWNLOAD RSLogix will establish communication with the processor 2 When communication is established RSLogix will open a confirmation dialog box Click the DOWNLOAD button to transfer the sample progr
80. User Manual MVI56E MNET MNETXT ControlLogix Platform Modbus TCP IP Interface Module Status Data in the Read Block The following table describes in more detail the status information contained in the Read block Word Offset Content Description 202 Program Scan Count This value is incremented each time a complete program cycle occurs in the module 203 Read Block Count This field contains the total number of read blocks transferred from the module to the processor 204 Write Block Count This field contains the total number of write blocks transferred from the processor to the module 205 Parse Block Count This field contains the total number of blocks successfully parsed that were received from the processor 206 Command Event Block This field contains the total number of command event Count blocks received from the processor 207 Command Block Count This field contains the total number of command blocks received from the processor 208 Error Block Count This field contains the total number of block errors recognized by the module 209 Product Code 1 This register displays the first word of the product code in ASC format 210 Product Code 2 This register displays the second word of the product code in ASC format 211 Version number This register displays the version number in decimal values For example if the version number is 1 51 it
81. WNLOAD eSt Connection Cancel Page 68 of 181 ProSoft Technology Inc April 23 2014 MVI56E MNET MNETXT ControlLogix Platform Configuring the MVI56E MNET Module Modbus TCP IP Interface Module User Manual 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 Module Running STEP 1 Select Communication Path Select Connection Type 1756 ENBT Ethernet CIPconnect t 192 168 0 100 p 1 5 0 56 CIP Path Edit RSWho STEP 2 Transfer File s DOWNLOAD Test Connection poU Cancel Example 2 Remote Rack Application For this example the MVI56E MNET module is located in a remote rack accessible through ControlNet as shown in the following illustration Ethemet ControlNet ProSoft Technology Inc Page 69 of 181 April 23 2014 Configuring the MVIBGE MNET Module MVI56E MNET MNETXT ControlLogix Platform User Manual Modbus TCP IP Interface Module Rack 1 Slot Module Network Address 0 ControlLogix Processor 1 1756 CNB Node 1 2 1756 ENBT IP 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 2 6 MVI56E MNET 1 Inthe Download dialog box click CIP PATH EDIT Download files from PC to module STEP 1 Select Communication Path Sel
82. address for the server ProSoft Technology Inc Page 149 of 181 April 23 2014 Reference User Manual MVI56E MNET MNETXT ControlLogix Platform Modbus TCP IP Interface Module Modbus Exception Codes Code Name Meaning 01 Illegal Function The function code received in the query 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 an
83. alling ProSoft Configuration Builder To install ProSoft Confiquration Builder from the DVD 1 Insert the ProSoft Solutions DVD into the DVD drive of your PC Wait for the startup screen to appear e TECHNOLOGY Li g Install ProSoft Discovery Service Install ProSoft Configuration Builder g Documentation Enjoy easy connectivity with ProSoft Technology Powerful diagnostics features for you to gather real time module status and analyze the data stream moving through the module Use PCB to configure some modules Consult the product documentation to determine the correct configuration method for your product 2 On the 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 ProSoft Technology Inc April 23 2014 Page 35 of 181 Configuring the MVI56E MNET Module MVI56E MNET MNETXT ControlLogix Platform User Manual Modbus TCP IP Interface Module 2 2 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 needs PCB is not only a powerful solution for new configuration files but also allows you to import information from previously installed known working configurations
84. am to the processor Download Lx Download to the controller s Name Controller Type 1756 L63 4 17 6 M13 4 ControlLogix5563 Controller Path AB DriverName Security None A The controller is in Remote Run mode The mode will be changed to Remote Program prior to download Cancel Help 3 RSLogix will compile the program and transfer it to the processor This process may take a few minutes 4 When the download is complete RSLogix will open another confirmation dialog box Click OK to switch the processor from PROGRAM mode to RUN mode RSLogix 5000 Done downloading Change controller mode back to Remote Run J Note If you receive an error message during these steps refer to your RSLogix documentation to interpret and correct the error ProSoft Technology Inc Page 167 of 181 April 23 2014 Reference MVI56E MNET MNETXT ControlLogix Platform User Manual Modbus TCP IP Interface Module 5 8 5 Adding the Sample Ladder to an Existing Application Copy the Controller Tags page 76 from the sample program Copy the User Defined Data Types page 78 from the sample program Copy the Ladder Rungs from the sample program Save and Download page 33 page 167 the new application to the controller and place the processor in RUN mode kRON Page 168 of 181 ProSoft Technology Inc April 23 2014 MVI56E MNET MNETXT ControlLogix Platform Support Service amp Warr
85. anty Modbus TCP IP Interface Module User Manual 6 Support Service amp Warranty In This Chapter Contacting Technical 169 Return Material Authorization RMA Policies and Conditions 171 LIMITED WARRANT Yess re iE EE ERRORS 173 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 Module 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 gt LS Note For technical support calls within the United States ProSoft s 24 7 after hours phone support is available for urgent plant down issues Detailed contact information for all our worldwide locations is available on the following page ProSoft Technology Inc Page 169 of 181 April 23 2014 Support Service amp Warranty MVI56E MNET MNETXT ControlLogix Platform User Manual Modbus TCP IP Interface Module Internet Web Site www prosoft technology com support E mail addr
86. 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 0 through 65535 This parameter specifies the number of successive transfer errors that must occur before halting communication on the application port s If the parameter is set to 0 the application port s will continue to operate under all conditions If the value is set larger than 0 1 to 65535 communications will cease if the specified number of failures occur 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 43 of 181 April 23 2014 Configuring the MVI56E MNET Module MVI56E MNET MNETXT ControlLogix Platform User Manual Modbus TCP IP Interface Module Pass Through Mode 0 1 20r 3 This parameter specifies the pass through mode for write m
87. arged the module will revert to the default BIOS and clock settings Note The battery is not user replaceable MVI56E MNET MNETXT ControlLogix Platform Modbus TCP IP Interface Module Contents User Manual Contents Your Feedback Please e iier eit ee uei n ve ota E vag Eo e y Eten 2 How to Contact US tete oio ed iter t Pre bed rede trs erbe vl recetas 2 ProSoft Technology Product Documentation tente 2 MWY ATVI C M T 3 NU SIE M 3 Battery Life AdVISOLy tcd ite beni eer dre ni 4 Guide to the MVIS56E MNET User Manual 9 1 Start Here 11 1 1 What S N8W 12 1 2 System 1 ener nnne nene 13 1 3 Package 14 1 4 Setting J mp ers ips ienei 15 1 5 Installing the Module in the 16 1 6 Importing the Sample Add On Instruction seen 18 1 7 Creating a New RSLogix 5000 Project 19 Creating the Module sssssssssssssssesesesennene enne nnne enne nnns 20 1 Importing the Add On Instruction ssssseeneneneeneeenn nnns 22 1 8 Connecting Your to the ControlLogix
88. ata into the proper controller tags in the processor There are two basic modes of operation when the pass through feature is utilized Unformatted code 1 and Formatted code 2 or 3 In the unformatted mode messages received on the server are passed directly to the processor without any processing These unformatted blocks require more decoding than the formatted blocks The Modbus protocol supports control of binary output coils functions 5 and 15 and registers functions 6 and 16 Any Modbus function 5 6 15 or 16 commands will be passed from the server to the processor using the block identification numbers 9956 to 9961 9970 and 9996 Formatted Pass Through Blocks In formatted pass through mode the module processes the received write request and generates a special block dependent on the function received There are two modes of operation when the formatted pass through mode is selected If code 2 is utilized no swap the data received in the message is presented in the order expected by the processor If code 3 is utilized swap mode the bytes in the data area of the message will be swapped This selection is applied to all received write requests The block identification code used with the request depends on the Modbus function requested Block ID Modbus Function 9956 6 16 word type data 9957 6 16 floating point 9958 5 9959 15 9960 22 9961 23 9970 99 Pass Through Blocks 9956 9957 9958 9960 or 9961 f
89. atform User Manual Modbus TCP IP Interface Module 2 2 4 Module This section of the configuration describes the database setup and module level parameters Backplane Error Status Pointer 1 to 4955 This parameter sets the address in the internal database where the backplane error status data will be placed If you want the error status data to be moved to the processor and placed into the ReadData array the value entered should be a module memory address in the Read Data area If the value is set to 1 the error status data will not be stored in the module s internal database and will not be transferred to the processor s HeadData array Enabling the Error Status Pointer is optional The error status data is routinely returned as part of the input image which is continually being transferred from the module to the processor For more information see Normal Data Transfer Blocks page 113 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 Data Areas must be configured to occupy
90. be transferred to the processor s HeadData array Enabling the Error Status Pointer is optional The error status data is routinely returned as part of the input image which is continually being transferred from the module to the processor For more information see Normal Data Transfer Blocks page 113 Page 44 of 181 ProSoft Technology Inc April 23 2014 MVI56E MNET MNETXT ControlLogix Platform Configuring the MVI56E MNET Module Modbus TCP IP Interface Module User Manual Command Error Pointer 1 to 4999 This parameter sets the address in the internal database where the Command Error List data will be placed If you want the Command Error List data to be moved to the processor and placed into the ReadData array 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 HeaabData 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 issued when failure is recognized Response Timeout 0 to 65535 milliseconds This is the time in milliseconds that a Client will wait before re
91. bus TCP IP Interface Module 2 2 7 MNET Servers This section contains database offset information used by the server when accessed by external Clients These offsets can be utilized to segment the database by data type Edit MNet Servers Float Flag Float Start 7000 Float Offset Output Offset 0 Bit Input Offset 0 Holding Register Offset 0 Word Input Offset 0 Connection Timeout 60 Definition Yes or No This flag specifies if the floating point data access functionality is to be implemented If the float flag is set to Yes Modbus functions 3 6 and 16 will interpret floating point values for registers as specified by the two following parameters Reset Tag Reset All OK Cancel 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
92. c Page 143 of 181 April 23 2014 Reference MVI56E MNET MNETXT ControlLogix Platform User Manual Modbus TCP IP Interface Module 5 5 7 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 DataStartReg Data Start Reg Data tof 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 DatalnputRegLo Error Check Field 11 06 00 01 00 03 CRC 5 5 8 Read Exception Status Function Code 7 This function code is used to read the contents of eight Exception status outputs in a remote device Function code 7 provides a method for accessing this information because the Exception Ou
93. cast 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 Function Code Description Read Coil Status Read Input Status Read Holding Registers Read Input Registers Force Write Single Coil Preset Write Single Register Read Exception Status Force Multiple Coils Preset Multiple Registers Mojo Rom O Page 52 of 181 ProSoft Technology Inc April 23 2014 MVI56E MNET MNETXT ControlLogix Platform Configuring the MVI56E MNET Module Modbus TCP IP Interface Module 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 ty
94. ced on the Return Material Authorization i If 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 3096 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 C 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 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 OF Q OQ Q Q 0 Q OQ OQ Q O Page 172 of 181 ProSoft Technology Inc April 23 2014 MVI56E MNET MN
95. change is displayed in the scrolling LED during module power up Important The Optional Add 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 ProSoft Technology Inc Page 151 of 181 April 23 2014 Reference User Manual MVI56E MNET MNETXT ControlLogix Platform Modbus TCP IP Interface Module 5 6 3 Installing the Rung Import with Optional Add On Instruction 1 choose IMPORT RUNG fc RSLogix 5000 My Controller 1756 163 MainProgram MainRoutine Ef File Edit View Search Logic Communications Tools Window Help alsa S 1 91918 v amp alal Offine aJ w 1 Favorites Bit TimeriCounter D F RUN BAT F vo No Forces No Edits Right click an empty rung in the main routine of your existing ladder logic and mN MI Controller My Controller salele Controller Tags Controller Fault Handler C3 Power Up Handler Output parameters Fault Code value GSV Tasks E fa MainTask c MainProgram ia Program Tags E MainRoutine Ctriex Ctrl C Cut Rung Copy Rung 3 Unscheduled Programs Get System Value Class Name Module Instance Name MNET Attribute Name FaultCode Dest MNET CONTROL FaultCode 0e Motion Groups C3 Ungrouped Axes E Add On Instructions AO
96. chnology Inc April 23 2014 Page 7 of 181 Contents MVI56E MNET MNETXT ControlLogix Platform User Manual Modbus TCP IP Interface Module Page 8 of 181 ProSoft Technology Inc April 23 2014 MVI56E MNET MNETXT ControlLogix Platform Guide to the MVIS6E MNET User Manual Modbus TCP IP Interface Module User Manual Guide to the MVI56E MNET User Manual Function Section to Read Details Introduction Start Here page 11 This section introduces the customer to the Must Do module Included are package contents System requirements hardware installation and basic configuration Diagnostic and Diagnostics and This section describes Diagnostic and Troubleshooting Troubleshooting Troubleshooting procedures page 87 Reference Reference page These sections contain general references 107 associated with this product Specifications and Product Specifications the Functional Overview Product Specifications page Functional Overview 107 Functional Overview Support Service and Support Service This section contains Support Service and Warranty and Warranty page Warranty information 169 Index Index Index of chapters ProSoft Technology Inc Page 9 of 181 April 23 2014 Guide to the MVI56E MNET User Manual MVI56E MNET MNETXT ControlLogix Platform User Manual Modbus TCP IP Interface Module Page
97. ck Page 16 of 181 ProSoft Technology Inc April 23 2014 MVI56E MNET MNETXT ControlLogix Platform Start Here Modbus TCP IP Interface Module 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 ControlLogix rack 5 Turn power ON Note If you insert the module improperly the system may stop working or may behave unpredictably Note When using the MVIS6EMNETXT you must use the 1756 A5XT or 1756 A7LXT chassis In these chassis modules are spaced further apart than in standard ControlLogix chassis Blank spacers are inserted between active modules ProSoft Technology Inc Page 17 of 181 April 23 2014 Start Here MVI56E MNET MNETXT ControlLogix Platform User Manual Modbus TCP IP Interface Module 1 6 Importing the Sample Add On Instruction Note This section only applies if your processor is using RSLogix 5000 version 16 or higher If you have an earlier version please see Using the Sample Program page 163 Before You Begin Two Add On Instructions are provided for the 56 module The first is required for setting up the module the second is optional Copy the files from the ProSoft Solutions DVD or download them from www prosoft technology com Save them to a convenient location in your PC such as Deskto
98. conds and will default to 5000 milliseconds Client only 9 The Command Error Delay is 300 and will default to 300 0200h Client only 10 Reserved not currently used 0400h 11 Reserved not currently used 0800h 12 Reserved not currently used 1000h 13 Reserved not currently used 2000h 14 Reserved not currently used 4000h 15 Reserved not currently used 8000h Combinations of errors will result in more than one bit being set in the error word Correct any invalid data in the configuration for proper module operation A value of zero 0 in this word indicates all bits are clear which means that all module configuration parameters contain valid values However this does not mean that the configuration is valid for the user application Make sure each parameter is set correctly for the intended application Page 104 of 181 ProSoft Technology Inc April 23 2014 MVI56E MNET MNETXT ControlLogix Platform Diagnostics and Troubleshooting Modbus TCP IP Interface Module User Manual 4 3 3 Client Command Errors There are several different ways to view Client Command Errors Inthe MNET STATUS ClientStats CurErr and MNET STATUS ClientStats LastErr controller tags On the Client status data screens in the ProSoft Configuration Builder Diagnostics Ata module database location specified by the configuration s MNET Client Command Error Pointer if the Command Error Pointer is enabled This means that the fi
99. d after all the other parameters have been entered NumberOfCommands Enter a decimal value representing the quantity of commands to be requested in the Command Control block 1 to 6 Commandindex x Enter the ROW NUMBER of the command in the MNET Client 0 Command Listin Prosoft Configuration Builder minus 1 This is a six element array Each element holds one Command Index CmdsAddedToQueue Returned decimal value representing the quantity of commands added from the MNET Client 0 Command List to the command priority queue by the most recent Command Control block CmdControlBlockID Temporary variable that provides block ID of the Command Control block most recently processed by the module CmdCnirlPending Temporary variable used to prevent a new Command Control block from being sent to the module until the previously sent Command Control block has been completely processed and a response block has been returned ProSoft Technology Inc April 23 2014 Page 125 of 181 Reference MVI56E MNET MNETXT ControlLogix Platform User Manual Modbus TCP IP Interface Module Pass Through Blocks 9956 9961 9970 and 9996 In Pass Through mode write messages sent to a server port are passed directly through to the processor In this mode the module sends special blocks to the processor when a write request is received from a Client Ladder logic must handle the receipt of these blocks and place the enclosed d
100. d 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 MVIS56E MNET 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 message 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 145 of 181 April 23 2014 Reference MVI56E MNET MNETXT ControlLogix Platform User Manual Modbus TCP IP Interface Module The data fields in responses to other kinds of queries could contain error counts or other data requested by the sub function code MB Server Sends mb exception rsp Page 146 of 181 ProSoft Technology Inc Apri
101. de quantity of data characters the data characters and error checking Data will be packed with one bit for each coil 1 ON 0 OFF The low order 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 Status 20to Status 28to Status 36to Status 44to Status 52to Check 27 35 43 51 56 Field 11 01 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 2 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 forma
102. describing the quantity of data bytes to be returned 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 142 of 181 ProSoft Technology Inc April 23 2014 MVI56E MNET MNETXT ControlLogix Platform Reference Modbus TCP IP Interface Module User Manual 5 5 6 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 a
103. e amp Value Data Type 2 MNETDATA MNET DATAReadData INT 600 MNET DATA ReadData 0 6666 INT MNET DATA ReadData 1 7777 INT MNET DATA ReadData 2 8888 INT MNET DATA ReadData 3 9999 INT MNET DATA ReadData 4 1010 INT MNET DATA ReadData 5 0 INT MNET DATA ReadData 5 0 INT MNET DATA ReadData 7 0 INT 4 gt Monitor Tags Edit Tags 4 The ReadData array is related to the contents of the Read Data area of the module s internal database To view the actual registers in the module s internal database access the database display from ProSoft Configuration Builder s Diagnostics menu For more information see the section on PCB Diagnostics page 96 DATABASE DISPLAY 0 TO 99 DECINAL 6666 7777 8888 9999 1010 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 0 0 0 0 0 ProSoft Technology Inc Page 81 of 181 April 23 2014 Ladder Logic MVI56E MNET MNETXT ControlLogix Platform User Manual Modbus TCP IP Interface Module MNET DATA WriteData WriteData is a controller tag array that automatically adjusts to match the value entered in the Write Register Count page 43 parameter of the configuration For ease of use this array should be dimensioned as a multiple of 200 words This data is paged up to 200 words at a time from the processor to the m
104. e a command response is received Page 102 of 181 ProSoft Technology Inc April 23 2014 MVI56E MNET MNETXT ControlLogix Platform Diagnostics and Troubleshooting Modbus TCP IP Interface Module User Manual Controller Tag Data Type Description ClientStats CmdErr INT This value is incremented each time an error message is received from a remote unit or a local error is generated for a command ClientStats Requests INT Not used ClientStats Responses INT Not used ClientStats ErrSent INT Not used ClientStats ErrRec INT Not used ClientStats CfgErrWord INT Configuration Error Word Contains a bitmap that indicates Client and server configuration errors ClientStats CurErr INT Most recent error code recorded for the Client ClientStats LastErr INT Previous most recent error code recorded for the Client BlockStats Read INT Total number of read blocks transferred from the module to the processor BlockStats Write INT Total number of write blocks transferred from the processor to the module BlockStats Count INT Total number of blocks successfully parsed that were received from the processor BlockStats Event INT Total number of command event blocks received from the processor BlockStats Cmd INT Total number of command blocks received from the processor BlockStats Err INT Total number of block errors recognized by the module ProSoft Technology Inc Page 103 of 181
105. e executed until the queue is empty 3 Then the module goes back to where it left off on the MNET Client 0 Command List and continues routine polling Event Command blocks send Modbus TCP IP commands directly from controller tags by ladder logic to the Client command priority queue on the module Event Commands are not placed in the module s internal database and are not part of the MNET Client 0 Command List Block Request from Processor to Module Word Offset Description Length 0 Block ID This word contains block identification code 2000 to indicate 1 that the block contains a command to be executed by the Client driver 1to4 IP Address These four words contain the IP address of the destination 4 server Each octet value 0 to 255 of the destination server s 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 gt 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 ensure the values are in the range of 0 to 255 5 Service Port This word contains the TCP service port used in the 1 message 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 used Any value from 0 to 65535 is permitted A value of 502 will cause a MBAP formatted message to be
106. e internal database to be associated with the device data The Client command list supports up to 100 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 issuances 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 Write commands have a special feature as they can be set to execute only if the data in the write command changes If the register data values in the command have not changed since the command was last issued the command will not be executed If the data in the command has changed since the command was last issued the command will be executed Use of this feature can lighten the load on the network To implement this feature set the enable code for the command to CONDITIONAL 2 ProSoft Technology Inc Page 47 of 181 April 23 2014 Configuring the MVIBGE MNET Module User Manual MVI56E MNET MNETXT ControlLogix Platform Modbus TCP IP Interface Module 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 Supported in Client Supported in Server 1 Read Coil Status X X 2 Read Inp
107. e network However the module also has a special command priority queue which is an internal buffer that holds commands from special function blocks until they can be sent on the network When one or more commands appear in the command priority queue 1 The routine polling process is temporarily interrupted 2 commands in the command priority queue are executed until the queue is empty 3 Then the module goes back to where it left off on the MNET Client 0 Command List and continues routine polling Like Event Command blocks Command Control blocks place commands into the module s command priority queue Unlike Event Commands blocks which contain all the values needed for one command Command Control is only used with commands already defined in the MNET Client 0 Command List Commands in the MNET Client 0 Command List may be either enabled for routine polling or disabled and excluded from routine polling A disabled command has its Enable parameter set to NO 0 and is skipped during routine polling An enabled command has its Enable parameter set to YES 1 and is sent during routine polling However Command Control allows any command in the predefined MNET Client 0 Command List to be added to the command priority queue whether it is enabled for routine polling or not Command Control also gives you the option to use ladder logic to have commands from the MNET Client 0 Command List executed at a higher priority and out of routine
108. e 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 MVIS6E MNET 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 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 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 ra
109. ect Connection Type 1756 ENBT 4 Ethernet t 192 168 0 100 p 1 5 0 56 CIP Path Edit RSWho STEP 2 Transfer File s DOWNLOAD Test Connection Page 70 of 181 ProSoft Technology Inc April 23 2014 MVI56E MNET MNETXT ControlLogix Platform Configuring the MVI56E MNET Module User Manual Modbus TCP IP Interface Module 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 a il Connect PATH EDITOR Source Module IP Source Module Node Destination Module No Source Module Add Destination Module Slot Number ress B vscener 12162010 REESE 0 MVI56 Module t 192 168 0 100 p 1 5 2 p 2 c 0 p 1 s 6 Add Rack Delete Rack Construct Path OK Cancel 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 v Ethernet t 192 168 0 100 p 1 s 0 56 CIP Path Edit RSWho CIPconnect STEP 2 Transfer File s Test Connection DOWNLOAD ProSoft Technology Inc Page 71 of 181 April 23 2014 Configuring the MVI56E MNET Module MVI56E MNET MNETXT ControlLogix Platform User Manual Modbus TCP IP Interface Module
110. ect to Connect to the Module 63 64 T3 93 137 Using Controller Tags 79 Using ProSoft Configuration Builder Software 36 Using RSWho to Connect to the Module 63 73 Using the Diagnostics Menu in ProSoft Configuration Builder 92 Using the Optional Add On Instruction Rung Import 151 Using the Sample Program 18 163 V Version 96 Warm Boot Block 9998 130 Warnings 3 What Is Covered By This Warranty 173 175 What Is Not Covered By This Warranty 174 What s New 12 Word Input Offset 56 Write Block 116 Write Register Count 43 82 Write Register Start 43 Writing the Clock Value to the Module 159 Writing the Ethernet Settings to the Module 157 Y Your Feedback Please 2 ProSoft Technology Inc Page 181 of 181 April 23 2014
111. ee eels 76 3 1 1 MVI56 E MNET Controller Tags sse enne 76 3 2 User Defined Data Types UDTs es 78 3 2 1 MVI56 E MNET User Defined Data 78 ProSoft Technology Inc April 23 2014 Page 5 of 181 Contents User Manual MVI56E MNET MNETXT ControlLogix Platform Modbus TCP IP Interface Module 3 3 Using Controller Tags essen nennen nnne nennen neis 79 3 4 Controller Tag Overview ssssssssessseeneneneeen ene enne enne nnne nennen 80 3 4 1 MNETIDATA ee rite esit e ML eL e e 80 3 4 2 MNETZS TATIUS iei Ld EE 83 3 4 3 MANET CONTRO sieut ettet tete tende tees 84 3 4 4 Mee ne em ig UE LM beh 85 4 Diagnostics and Troubleshooting 87 4 1 LED Status Indicators aaa aa 88 4 1 1 Scrolling LED Status Indicators ssssssssseeeennen nens 88 4 1 2 Ethernet LED 89 4 1 3 Non Scrolling LED Status Indicators 90 4 1 4 Eden RE ada d 91 4 1 5 Clearing a Fault Condition 0 0 cccecececeeeeeceeceeeeeeeeceeeeeceaeeesaaeseeaeeseeeeesaeeeeaeseeeeeeaas 91 4 2 Using the Diagnostics Menu in ProSoft Configuration Builder 92 4 2 1 Connecting to
112. es 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 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 01 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 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
113. es will be used to determine exactly which three commands will be added to the queue and to set their order of execution Values to enter for the six Command Indexes range from 0 to 99 and correspond to the MNET Client 0 Command List entries which are numbered from 1 to 100 To determine the Command Index value subtract one 1 from the row number of the command in the MNET Client 0 Command List as seen in the Command Editor window of ProSoft Configuration Builder PCB The module responds to a Command Control block request with a response block indicating the number of commands added to the command priority queue Block Response from Module to Processor Word Offset Description 0 Reserved 1 This word contains the next write block identification code 2 This word contains the number of commands in the block added to the command priority queue 3 to 248 Spare 249 This word contains the block 5001 to 5006 requested by the processor Page 124 of 181 ProSoft Technology Inc April 23 2014 MVI56E MNET MNETXT ControlLogix Platform Reference Modbus TCP IP Interface Module User Manual Controller Tags The MNET UTIL CmdContro l controller tag array holds all the values needed to create one Command Control block have it sent to the module and control the processing of the returned response block Controller Tag Description TriggerCmdCnitrl Set this tag to 1 to trigger the execution of a comman
114. ess 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 location in China Tel 86 21 5187 7337 x888 E mail asiapc prosoft technology com Languages spoken include Chinese English Europe location in Toulouse France Tel 33 0 5 34 36 87 20 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 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 11 5083 3776 E mail brasil prosoft technology com Languages spoken include Portuguese English For complete details regarding ProSoft Technology s TERMS amp CONDITIONS OF SALE WARRANTY SUPPORT SERVICE AND RETURN MATERIAL AUTHORIZATION INSTRUCTIONS please see the documents on the Product DVD or go to www prosoft technology legal
115. essages received by the MNET and MBAP server ports parameter is set to 0 all write messages will be placed in the module s virtual database fa value of 1 is entered write messages received will be sent to the processor as unformatted messages lf avalue of 2 is entered write messages received will be sent to the processor as formatted messages lf avalue of 3 is entered write messages received will be sent to the processor with the bytes swapped in a formatted message Duplex Speed Code 0 1 2 3or4 This parameter allows you to cause the module to use a specific duplex and Speed setting Value 1 Half duplex 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 2 5 MNET Client x This section defines general configuration for the MNET Client Master Client Error Status Pointer 1 to 4990 This parameter sets the address in the internal database where the Client error status data will be placed If you want the error status data to be moved to the processor and placed into the ReadData array the value entered should be a module memory address in the Read Data area If the value is set to 1 the error status data will not be stored in the module s internal database and will not
116. et parameter HoldOffs Holding Register offset parameter FltFlag Float Flag parameter FItSt Float Start parameter FltOffs Float Offset parameter Page 88 of 181 ProSoft Technology Inc April 23 2014 MVI56E MNET MNETXT ControlLogix Platform Diagnostics and Troubleshooting Modbus TCP IP Interface Module User Manual Operation Messages After the initialization step the following message pattern will be repeated lt 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 Diagnostics and Troubleshooting page 87 for further information about the error 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 LE
117. evice Upload from Device to PC Page 60 of 181 ProSoft Technology Inc April 23 2014 MVI56E MNET MNETXT ControlLogix Platform Configuring the MVIBGE MNET Module Modbus TCP IP Interface Module User Manual 3 Inthe Diagnostics window click the SET UP CONNECTION button sl ely Click to set up connection 4 Inthe Connection Setup dialog box click the BROWSE DEVICE S button to open the ProSoft Discovery Service Select the module then right click and choose ASSIGN TEMPORARY IP JA Prosoft Discovery Service Device Details Remove Temporary IP View module s webpage Select for PCB Click the search icon to begin the browse 5 The module s default IP address is 192 168 0 250 Choose an unused IP within your subnet and then click OK tal Assign Temporary IP Address DER Temporary IP 192 168 0 253 0 Network Mask 255 255 255 Important The temporary IP address is only valid until the next time the module is initialized For information on how to set the module s permanent IP address see Ethernet Configuration page 58 ProSoft Technology Inc Page 61 of 181 April 23 2014 Configuring the MVI56E MNET Module MVI56E MNET MNETXT ControlLogix Platform User Manual Modbus TCP IP Interface Module 6 Close the ProSoft Discovery Service window Enter the temporary IP in the Ethernet address field of the Connection Setup dialog box then click the TEST CONNE
118. from Module to Processor Word Offset Description Length 0 Reserved 1 1 Write Block ID 1 2 to 201 Read Data 200 202 Program Scan Counter 1 203 to 208 Block Transfer Status 6 209 Product Code 1 1 210 Product Code 2 1 211 Version number 1 212 to 218 Not Used 7 219 to 221 Reserved 2 222 to 228 MNet Server Status 7 229 to 231 Reserved 2 232 to 238 MBAP Server Status 7 239 to 248 MNet Client Status 10 249 Read Block ID 1 The Read Block ID is an index value used to determine where the 200 words of data from module memory will be placed in the ReadData x controller tag array of the ControlLogix processor Each transfer can move up to 200 words block offsets 2 to 201 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 During 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 R1W15R2W2 5R3W 1 R1W25R2W1 R3W25R1W1 This sequence will continue until interrupted 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 ProSoft Technology Inc Page 113 of 181 April 23 2014 Reference
119. g D av 18 MVIBBEMNET Clock Contig Hour 10 MVIBBEMNET Clock Config Minute 44 MVIBBEMNET Clock Config Seconds 21 To check the status of the message refer to the WriteClockMSG tag e WiiteClackMSG Flaas 1640200 WriteClockMSG EW 0 WriteClockMSG ER 0 WiiteClockMSG DN 0 WiiteClockMSG ST 0 WiiteClockMSG EN 0 WriteClockMSG TO 0 WriteClockMSG EN_CC 1 WriteClockMSG ERR 16 0000 WiiteClockMSG EXERR 16 0000 0000 WriteClockMSG ERR_SRC 0 WiiteClockMSG DN LEN 0 WiiteClockMSG REQ LEN 24 ProSoft Technology Inc April 23 2014 Page 159 of 181 Reference MVI56E MNET MNETXT ControlLogix Platform User Manual Modbus TCP IP Interface Module 5 7 Adding the Module to an Existing Project 1 Select the O Configuration folder in the Controller Organization window of RSLogix 5000 and then click the right mouse button to open a shortcut menu On the shortcut menu choose NEW MODULE 3 6 Controller My Controller Controller Tags Controller Fault Handler Power Up Handler 3 6 Tasks 2 68 MainTask C MainProgram Unscheduled Programs 7 5 Motion Groups Ungrouped Axes Add On Instructions Data Types Cg User Defined oe Strings 18 Add On Defined E Predefined 18 Module Defined Trends 7 5 1 0 Configuration e 0 Em This action opens the Select Module dialog box L Select Module lodule Analog Communications Controllers Digital Drives Motio
120. g ladder logic You can find them in the Controller Tags subfolder located in the Controller folder in the Controller Organizer pane of the main RSLogix 5000 window This controller tag structure is arranged as a tree structure Individual controller tags are found at the lowest level of the tree structure Each individual controller tag is defined to hold data of a specific type such as integer or floating point data Controller tag structures are declared with user defined data types which are collections of data types 3 1 1 MVI56 E MNET Controller Tags The main controller tag structure MNET is broken down into four lower level controller tag structures MNET MNET DATA MNET STATUS MNET CONTROL MNET UTIL The four lower level controller tag structures contain other controller tags and controller tag structures Click the sign next to any controller tag structure to expand it and view the next level in the structure Page 76 of 181 ProSoft Technology Inc April 23 2014 MVI56E MNET MNETXT ControlLogix Platform Ladder Logic Modbus TCP IP Interface Module User Manual For example if you expand the MNET DATA controller tag structure you will see that it contains two controller tag arrays MNET DATA ReadData and MNET DATA WriteData which are 600 element integer arrays by default Scope 0 Controller Show Show All Name amp Value Data Type Description ADIBBMNET ADI
121. g the Ethernet Settings from the Module 156 Reference 9 107 Reg Count 50 Renaming an Object 40 Response Timeout 45 Retry Count 45 Return Material Authorization RMA Policies and Conditions 171 Returning Any Product 171 Returning Units Out of Warranty 172 Returning Units Under Warranty 172 S Scrolling LED Status Indicators 88 Select Priority Read Block Write Block Offset 247 117 Selecting the Slot Number for the Module 166 Server Driver 132 Service Port 51 Set Module IP Address Block 9990 129 Setting Jumpers 15 Setting Module Parameters 40 Setting Up a Temporary IP Address 60 Setting Up the Project 38 Slave Address 52 Special Function Blocks 85 119 Standard Modbus Exception Code Errors 105 Start Here 9 11 Static ARP 97 Static ARP Table 57 97 Status 98 99 Status Data in Read Block 83 97 101 102 114 115 Sub function Codes Supported 145 Support Service amp Warranty 9 169 Swap Code 51 System Requirements 13 T The Diagnostics Menu 81 82 96 101 Time Limit for Bringing Suit 176 Troubleshooting 91 Page 180 of 181 ProSoft Technology Inc April 23 2014 MVI56E MNET MNETXT ControlLogix Platform Index Modbus TCP IP Interface Module User Manual U Upgrading from MVI56 MNET in ProSoft Configuration Builder 12 36 User Defined Data Types UDTs 78 168 Using ClPconn
122. graphics adapter 800 x 600 minimum resolution True Color 1024 x 768 recommended DVD drive Note The Hardware and Operating System requirements in this list are 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 13 of 181 April 23 2014 Start Here MVI56E MNET MNETXT ControlLogix Platform User Manual Modbus TCP IP Interface Module 1 3 Package Contents The following components are included with your MVI56E MNET module and are all required for installation and configuration Important Before beginning the installation please verify that all of the following items are present Qty Part Name Part Number Part Description 1 MVI56E MNET MVI56E MNET Modbus TCP IP Interface Module MNETXT Module MNETXT 1 Cable RL CBL025 5 foot Ethernet Straight Through Cable Gray 1 ProSoft Solutions DVD 001 Contains configuration tools for the DVD MVI56E MNET module If any of these components are missing please contact ProSoft Technology Support for replacement parts Page 14 of 181 ProSoft Technology Inc April 23 2014
123. hange the default tags MNET and AOIS6MNET to avoid conflict with existing tags This procedure will append the string 2 as follows Import Configuration Tags Data Types Add On Instructions Local 2 1 Local 2 0 ADIBEMNET AB 1756 MOD AB 1756 MOD MNETMODUL Output parameters Create New Discard Discard Create New 12 Click OK to confirm fc RSLogix 5000 My Controller 1756 1 63 MainProgram MainRoutine Ef Ele Edit view Search Logic Communications Tools Window Help e x m e amp CIR ala Offline No Forces No Edits J Controller My Controller Controller Tags 28 Controller Fault Handler 8 Power Up Handler 3 Tasks 68 MainTask amp MainProgram ia Program Tags Lo vsnnoutne E Unscheduled Programs Motion Groups 9 Ungrouped Axes Add On Instructions AOTS6EMNET Data Types Trends 1 0 Configuration 1756 Backplane 1756 44 fa 0 1756 L63 My Controller BJ 1 1756 MODULE MNET 9 2 1756 MODULE MNET 2 kir stre m Aere Add O Bit 85 Output parameters Fault Code value GSV Get System Value Class Name Module Instance Name MNET Attribute Name FaultCode Dest MNET CONTROL FaultCode 04 Add On MVIS6 MNET and MVISBE MNET modules 56 Add On MVIS6 MNET and MVIS6E AOISBMNET AOISBMNET e Connection Input Local 1 1 Data
124. he command Output from Module ControlLogix MET F MODBUS TCP Processor Network Module To Module Input from Network ProSoft Technology Inc Page 131 of 181 April 23 2014 Reference MVI56E MNET MNETXT ControlLogix Platform User Manual Modbus TCP IP Interface Module 5 3 1 Server Driver The server driver allows the MVI56E MNET module to respond to data read and write commands issued by Clients on the Modbus TCP IP network The following illustration describes the flow of data into and out of the module Processor MVI56 E MNET Module ControlLogix Database Modbus 0 40001 Controller Tags Addresses Addresses Register Data _ Storage Register Data Backplane Configur ation i 4999 1 The server driver receives the configuration information from the configuration file on the Personality Module compact flash card and the module initializes the server 2 Ahost device such as a Modicon PLC or an HMI application issues a read or write command to the module s node address The server driver validates the message before accepting it into the module If the message is considered invalid an error response is returned to the originating Client node 3 After the module accepts the command the module processes the data contained in the command
125. ication is established RSLogix 5000 will open a confirmation dialog box Click the DOWNLOAD button to transfer the sample program to the processor Download to the controller Name My Controller Type 1756 L63 ControlLogix5563 Controller Path AB DF1 1 Security None Cancel 3 RSLogix 5000 will compile the program and transfer it to 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 A Done downloading Change controller mode back to Remote Run Yes No Note If you receive an error message during these steps refer to your RSLogix documentation to interpret and correct the error ProSoft Technology Inc Page 33 of 181 April 23 2014 Start Here MVI56E MNET MNETXT ControlLogix Platform User Manual Modbus TCP IP Interface Module Page 34 of 181 ProSoft Technology Inc April 23 2014 MVI56E MNET MNETXT ControlLogix Platform Modbus TCP IP Interface Module Configuring the MVI56E MNET Module User Manual 2 Configuring the MVIBGE MNET Module In This Chapter Installing ProSoft Configuration Builder Using ProSoft Configuration Builder Software Connecting Your PC to the Module lt Downloading the Project to the Module 2 1 Inst
126. ice amp Warranty Modbus TCP IP Interface Module 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 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 Tra
127. il 23 2014 Configuring the MVI56E MNET Module MVI56E MNET MNETXT ControlLogix Platform User Manual Modbus TCP IP Interface Module Holding Register Offset 0 to 4999 This parameter defines the start register for the Modbus Command data in the internal database This parameter is enabled when a value greater than 0 is set For example if the Holding Register Offset value is set to 4000 data requests for Modbus Word register 40001 will use the internal database register 4000 Function codes affected are 3 6 16 amp 23 Word Input Offset 0 to 4999 This parameter defines the start register for Modbus Command data in the internal database This parameter is enabled when a value greater than 0 is set For example if the Word Input Offset value is set to 4000 data requests for Modbus Word register address 30001 will use the internal database register 4000 Function code 4 is affected Connection Timeout 0 to 1200 seconds This is the number of seconds the server will wait to receive new data If the server does not receive any new data during this time it will close the connection Page 56 of 181 ProSoft Technology Inc April 23 2014 MVI56E MNET MNETXT ControlLogix Platform Configuring the MVI56E MNET Module Modbus TCP IP Interface Module User Manual 2 2 8 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 requ
128. ill also need to set the Float Start and Float Offset parameters to appropriate values whenever the Float Flag parameter is set to YES Float Start 0 to 65535 Whenever the Float Flag parameter is set to YES this parameter determines the lowest Modbus Address used in commands to a remote server to consider as commands to read or write floating point data All commands with address values greater than or equal to this value will be considered floating point data commands All commands with address values less than this value will be considered normal 16 bit register data commands This parameter is used only if the Float Flag is set to YES For example if a value of 7000 is entered all commands sent with addresses of 47001 or 407001 and above will be considered as floating point data commands and 32 bits of data will be sent or received for each count of one in the command You will also need to set the Float Offset parameter to an appropriate value whenever the Float Flag parameter is set to YES 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 af
129. ion and status information for the MNET server Config Use the Configuration menu to view configuration settings for MNET servers connected to the MNET Client The information on this menu corresponds with the configuration information in the MNET Servers settings in ProSoft Configuration Builder page 54 Status Use the Status menu to view the status of each MNET server connected to the MNET Client 0 During normal operation the number of requests and responses should increment while the number of errors should not change ProSoft Technology Inc Page 99 of 181 April 23 2014 Diagnostics and Troubleshooting MVI56E MNET MNETXT ControlLogix Platform User Manual Modbus TCP IP Interface Module 4 2 7 Monitoring Database Information Use the DATABASE menu to view the contents of the MVIS6E MNET module s internal database You can view data in the following formats ASCII DATABASE DISPLAY 0 to 99 ASCII A m M y E e QO we c lt 0 0 0 IIn ste c dh 1 451 4 t4ho 4 lt 40 RHO 88 cOUooooonodo e3mmuo eccCmoeccy lt lt lt lt ee de San OE e Qe c him Decimal DATABASE DISPLAY 0 to 99 DECIMAL Refresh counter 3 29404 2 3 4 0 1 2 3 4 6169 8225 8739 9253 9767 10281 12337 12851 13365 13879 14393 16449 16963 17477 17991
130. ired 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 MNET module will be communicating with regularly 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 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 Adaress 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 ProSoft Technology Inc Page 57 of 181 April 23 2014 Configuring the MVI56E MNET Module MVI56E MNET
131. ix Platform User Manual Modbus TCP IP Interface Module Page 86 of 181 ProSoft Technology Inc April 23 2014 MVI56E MNET MNETXT ControlLogix Platform Diagnostics and Troubleshooting Modbus TCP IP Interface Module User Manual 4 Diagnostics and Troubleshooting In This Chapter LED nd A OS 88 Using the Diagnostics Menu in ProSoft Configuration Builder 92 Reading Status Data from the Module 101 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 87 of 181 April 23 2014 Diagnostics and Troubleshooting User Manual MVI56E MNET MNETXT ControlLogix Platform Modbus TCP IP Interface Module 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 Messages 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 Wai
132. ix processor the MVI56E MNET module and the Modbus TCP IP Network ControlLogix Processor MVI56 E MNET Module ControlLogix Controller Module s Tags Internal Ladder Database Logic transfers data from module s input image to data areas in the processor TCP IP Stack To and Modbus Ethernet TCP IP Client Hard Ethernet ware Network Special Function Ladder Blocks Logic Interface transfers data from Driver Backplane Driver processor data areas to output 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 contained 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 Page 110 of 181 ProSoft Technology Inc April 23 2014 MVI56E MNET MNETXT ControlLogix Platform Reference Modbus TCP IP Interface Module User Manual Module s Internal Database Structure 5000 registers for user data 0 Register Data 4999 Data contained in this database is transferred in blocks or pages using the input and output images ControlLogix ladder logic and the MVI56E MNET module s program work together to coordinate these block transfers Up to 200 words of data can be
133. ix window Like the controller tags the UDTs are organized in a multiple level tree structure 3 2 1 MVI56 E MNET User Defined Data Types Twelve different UDTs are defined for the MVI56 E MNET Add On Instruction The main UDT MNETMODULEDEF contains all the data types for the module and was used to create the main controller tag structure MNET There are four UDTs one level below MNETMODULEDEF These lower level UDTs were used to create the MNET DATA MNET STATUS MNET CONTROL and MNET UTIL controller tag structures Name MNETMODULEDEF Description This defines the whole module which includes all tags used in the program Members Data Type Size byte s Description DATA MNETDATA Data read from module STATUS MNETSTATUS Client Server Status and blocks status CONTROL MNETCONTROL MNET Module control warmboot coldboot etc UTIL MNETUTIL command event control 1 0 1 Click the signs to expand the UDT structures and view lower level UDTs Page 78 of 181 ProSoft Technology Inc April 23 2014 MVI56E MNET MNETXT ControlLogix Platform Ladder Logic Modbus TCP IP Interface Module User Manual For example if you expand MNETDATA you will see that it contains two UDTs and WriteData Both of these are 600 element integer arrays by default Name MNETMODULEDEF Description This defines the whole module which includes all tags used in the program Members Data Type Size
134. ke 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 136 for a diagram of how to configure Ethernet cable 5 4 1 Ethernet Cable Configuration 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 Rx 3 Tx 1 Rx 1 Tx 2 Rx 6 Tx 2 Rx 2 Tx 3 TX 1 Rx 3 TX 3 Rx 6 Tx 2 Rx 6 Tx 6 Rx pin BIAS Page 136 of 181 ProSoft Technology Inc April 23 2014 MVI56E MNET MNETXT ControlLogix Platform Reference Modbus TCP IP Interface Module User Manual 5 4 2 Ethernet Performance Ethernet performance on the MVI56E MNET module can affect the operation of the MNET application ports in the following ways Accessing the web interface refreshing the page downloading files and so on may affect MNET performance High Ethernet traffic may impact MNET performance consider ClPconnect page 64 for these applications and disconnect the module Ethernet port from the network ProSoft Technology Inc Page 137 of 181 April 23 2014 Reference MVI56E MNET MNETXT ControlLogix Platform User Manual Modbus TCP IP Interface Module 5 5 Modbus
135. l 1 1756 MODULE 1 1 General Connection Module Info Backplane Requested Packet Interval RPI 504 ms 0 2 750 0 ms Inhibit Module Major Fault On Controller If Connection Fails while in Run Mode Module Fault Status Offline ProSoft Technology Inc Page 161 of 181 April 23 2014 Reference MVI56E MNET MNETXT ControlLogix Platform User Manual Modbus TCP IP Interface Module 5 Save the module Click to dismiss the dialog box The Controller Organization window now displays the module s presence amp Controller My Contraler A Controller Tags Controller Fault Handler Power Up Handler Tasks e MainTask Cg MainProgram Unscheduled Programs Motion Groups Ungrouped Axes Add On Instructions e Data Types Cg User Defined Ga Strings Cg Add On Defined Gi Predefined ji Module Defined Z3 Trends 3 6 1 0 Configuration 89 1756 Backplane 1756 A4 0 1756463 My Controller 1 1756 MODULE 6 Copy the User Defined Data Types from the sample program into your existing RSLogix 5000 project 7 Copy the Controller Tags from the sample program into your project 8 Copy the Ladder Rungs from the sample program into your project Page 162 of 181 ProSoft Technology Inc April 23 2014 MVI56E MNET MNETXT ControlLogix Platform Reference Modbus TCP IP Interface Module User Manual 5 8 Using the Sample Program If your proce
136. l 23 2014 MVI56E MNET MNETXT ControlLogix Platform Reference Modbus TCP IP Interface Module User Manual 5 5 10 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 controller can also alter the state of the coil Coils are numbered from zero coil 00001 zero coil 00002 one and 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 and 20 are to be forced on Adr Func HiAdd Lo 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
137. ler Tag Description Read This tag contains the total number of Read blocks transferred from the module to the processor Write This tag contains the total number of Write blocks transferred from the processor to the module Parse This tag contains the total number of blocks successfully parsed that were received from the processor Event This tag contains the total number of Event Command blocks received from the processor Cmd This tag contains the total number of Command Control blocks received from the processor Err This tag contains the total number of block Errors recognized by the module For amore complete description of the MNET STATUS controller tag structure refer to the Status Data Definition page 102 ProSoft Technology Inc Page 83 of 181 April 23 2014 Ladder Logic User Manual MVI56E MNET MNETXT ControlLogix Platform Modbus TCP IP Interface Module 3 4 3 MNET CONTROL These controller tags are a scratchpad area of intermediate data storage variables used by the ladder logic to keep track of various logic processing functions Controller Tag Description WarmBoot Setting this tag to 1 will cause the module to reload refreshing configuration parameters that must be set on program initialization Only use this command if you must cause the module to re boot ColdBoot Set this tag to 1 when the module is required to perfor
138. losive gasses lt cULus gt E183151 Class I DIV 2 groups A B C D T5 for all models 0 C to 60 C 25 C to 70 C XT models only Hardware Ratings Backplane Current Load 800 mA 5 VDC 3 mA 24 VDC Operating Temperature For standard MVI56E modules 0 C to 60 C 32 F to 140 F For MVI56E XT conformal coated 25 C to 70 C 13 F to 158 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 All phase conductor sizes must be at least 1 3 mm squared and all earth ground conductors must be at least 4mm squared MVI56E XT module comes with conformal coating installed Agency Approvals and Certifications Agency RoHS ATEX CSA CE CSA CB Safety cULus GOST R Lloyds s C CC amp pc O Battery Life Advisory Note Modules manufactured after April 1st 2011 do not contain a battery For modules manufactured before that date the following applies The MVI56E modules use a rechargeable Lithium Vanadium Pentoxide battery to backup the real time clock and CMOS The battery should last for the life of the module The module must be powered for approximately twenty hours before the battery becomes fully charged After it is fully charged the battery provides backup power for the CMOS setup and the real time clock for approximately 21 days When the battery is fully disch
139. lt Handler Output parameters Power Up Handler Fault Code value Tasks GSV 68 Get System Value in MainProgram Class Name Module ig Program Tags Cut Rung Instance Name MNET Attribute Name FaultCode MainRoutine Sopy Rung Dest MNET CONTROL FaultCode 5 Unscheduled Programs Motion Groups Ungrouped Axes Delete Rung Del Add On MVIS6 MNET 2e opel Instructions Add Rung and MVIS6E MNET AOIS6MNET modules Data Types Edi Rung Enter AOISEMNET Trends Edit Rung Comment Ctrl D Add On MVIS6 MNET and MVIS6E 55 9 Configuration AOISBMNET AOISBMNET 1756 Backplane 1756 A4 Connection Input Local1 I Data fh 0 1756 L63 My Control Export Rung Connection_Output Local 1 0 Data oe MNET MNET fJ 1 1756 MODULE MNET Type Ladder Diagram Main Description Verify Rung GoTo Ctrl G lt Add Ladder Element Alt Ins Rung 0 of 1 Page 26 of 181 ProSoft Technology Inc April 23 2014 MVI56E MNET MNETXT ControlLogix Platform Start Here Modbus TCP IP Interface Module User Manual 9 Select the file MVIBGEMNET ADDON RuNG v1 4 L5X Import Rung Look in Desktop P My Computer My Documents My Recent Network Places Documents _ C Downloads MVI56 E MNET_AddOn_Rung_v1_4 L5X 4 File name IMVI56 E MNET_AddOn_Rung_v1_4 L5X Files of type RSLogi
140. m the cold boot hardware reset operation Do this when the module is experiencing a hardware problem requiring a hardware reset BPLastRead This tag stores the latest Read Block ID received from the module This value changes frequently BPLastWrite This tag stores the latest Write Block ID to be sent to the module This value changes frequently Blocklndex This tag is an intermediate variable used during the block calculation WBPending Pending message CBPending Pending message ReadDataBlkCount Holds the value of the Block Counts of the Read Data Array Array size is the Read Register Count divided by 200 WriteDataBlkCount Holds the value of the Block Counts of the Write Data Array Array size is the Write Register Count divided by 200 RBTSremainder Holds remainder calculation value from the read array WBTSremainder Holds remainder calculation value from the write array ReadDataSizeGet Holds read data array size WriteDataSizeGet Holds write data array size IPAddress Getting and setting IP address to and from the module FaultCode Fault Code value Checklnitialization Check Initialization trigger 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 Blocklndex tag is an intermediate variable used during the block calculation Page 84 of 181 ProSoft Technology Inc April 23 2014 MVI56E MNET MNETXT Cont
141. mation and configuration options 3 Double click any B icon to open an Edit dialog box 4 To edit a parameter select the parameter in the left pane and make your changes in the right pane 5 Click OK to save your changes Page 40 of 181 ProSoft Technology Inc April 23 2014 MVI56E MNET MNETXT ControlLogix Platform Configuring the MVIBGE MNET Module Modbus TCP IP Interface Module User Manual Creating Optional Comment Entries 1 2 3 Click the to the left of the a commet icon to expand the module comments Double click the comment icon The Edit Module Comment dialog box appears Edit Module Comment Comment Put Comment Here Comment Comment Put Comment Here Definition Reset Tag Reset All OK Cancel Enter your comment and 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 select printing options and then click OK ProSoft Technology Inc Page 41 of 181 April 23 2014 Configuring the MVI56E MNET Module MVI56E MNET MNETXT ControlLogix Pl
142. me digital point address because it expects the processor logic to reset the control bit Pass through must be used to simulate this mode The following illustration shows the data flow for a server port with pass through enabled Processor MVI56 E MNET Module 3 ControlLogix i Database Modbus Controller Tags Addresses Addresses 0 40001 Modbus Write Ethernet functions Network Register T T Register Data Data Storage Read functions Backplane 4999 Configur ation ProSoft Technology Inc Page 133 of 181 April 23 2014 Reference MVI56E MNET MNETXT ControlLogix Platform User Manual Modbus TCP IP Interface Module 5 3 2 Client Driver In the Client driver the MVI56E MNET module issues read or write commands to servers on the Modbus TCP IP network The commands originate either from the module s user configured Client O Command List or directly from the processor as Event Commands The commands from the Client 0 Command List are executed either via routine polling or as a result of special Command Control block requests from the processor The following flowchart describes the flow of data into and out of the module I Processor MVI56 E MNET Module I ControlLogix I Controller Database Modbus Modbus TCP IP Tags l Addresses Addresses Ethernet 0 40001 Network I 4 3 peg j Clent Register
143. n Other 1756 MODULE Generic 1756 Module Allen Bradley Specialty Find Add Favorite By Category By Vendor Favorites OK Cancel 2 Select the 1756 MODULE GENERIC 1756 MODULE from the list and click OK This action opens the New Module dialog box 3 Enter the Name Description and Slot options for your application You must select the Comm Format as DATA INT in the dialog box otherwise the module will not communicate Click OK to continue Page 160 of 181 ProSoft Technology Inc April 23 2014 MVI56E MNET MNETXT ControlLogix Platform Reference Modbus TCP IP Interface Module User Manual Parameter Value Name Enter a module identification string Example MNET 2 Description Enter a description for the module Example MopBus TCP IP INTERFACE MODULE Comm Format Select DATA INT Slot Enter the slot number in the rack where the MVI56E MNET module is located Input Assembly Instance 1 Input Size 250 Output Assembly Instance 2 Output Size 248 Configuration Assembly Instance 4 Configuration Size 0 4 Select the Requested Packet Interval value for scanning the I O 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 should work with most applications lil Module Properties Loca
144. n Groups _ MVISEEMNETClock is ER MNETCLOCKTYPE E Ungrouped Axes MVIB amp EMNETEthemet rud e MNETETHERNE Add On Instructions _ ReadClockMSG n SER MESSAGE Gy AOISGEMNET Optional __ ReadEthemetMSG ES ax MESSAGE g pus and Loca Tes _ WhieClockMSG m ER MESSAGE R AOIS6MNET WiiteEthemetMSG I MESSAGE SJ Data Types 8 User Defined MNETBLKSTAT MNETCLOCKTYPE MNETCMDCONTROL MNETCONTROL i MNETDATA MNETDATETIME MNETETHERNET a T gt N Monitor Tags Edit Tags Create Output Energize instruction 3 Inthe 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 Path Browse MNET S Connected Q Enable Enable Waiting Q Start Q Done Done Length 0 Error Code Extended Error Code Timed Out Error Path Error Text Cancel Help Page 154 of 181 ProSoft Technology Inc April 23 2014 MVI56E MNET MNETXT ControlLogix Platform Reference Modbus TCP IP Interface Module User Manual 5 Select the module to configure the message path Message Configuration ReadEthernetMSG Wil Message Path Browser Path MNET MNET 5 6 1 0 Configuration 1756 Backplane 1756 417 0 1756 L63 L63 8 1 1756 MODULE MNET Error Path Erro
145. n menu to view backplane configuration settings for the MVI56E MNET module The information on this menu corresponds with the configuration information in the Module settings in ProSoft Configuration Builder NIC Status Use the NIC Status Network Interface Card menu to view configuration and status information for the MVI56E MNET 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 57 defines a list of static IP addresses that the module will use when an ARP is required 4 2 4 Monitoring Backplane Information Use the BACKPLANE menu to view the backplane status information for the MVI56E MNET 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 with members of the Status Data Definition page 102 ProSoft Technology Inc Page 97 of 181 April 23 2014 Diagnostics and Tro
146. n more detail 3 4 1 MNET DATA The controller tags in MNET DATA hold user data to be transferred between the processor and the MVI56E MNET module This read and write data is transferred between the processor and the module as pages or blocks of data up to 200 words long The data types for the MNET DATA ReadData and MNET DATA WriteData controller tag arrays are integer arrays containing variable numbers of elements Controller Tag Data Type Description ReadData INT x Data read from module Array size is equal to the size set in the configuration WriteData INT x Data to write to module Array size is equal to the size set in the configuration Page 80 of 181 ProSoft Technology Inc April 23 2014 MVI56E MNET MNETXT ControlLogix Platform Ladder Logic Modbus TCP IP Interface Module User Manual MNET DATA ReadData ReaaData is a controller tag array that automatically adjusts to match the value entered in the Read Register Count page 42 parameter of the configuration For ease of use this array should be dimensioned as a multiple of 200 words This data is paged up to 200 words at a time from the module to the processor The ladder logic places the received data into the proper position in the ReadData array This data is used for status and control in the processor ladder logic Controller Tags My_Controller controller DER Scope fa My Controle v Show MNETBLKSTATS MNETCLIENTSTATS MNE Nam
147. nfig IP 2 0 MVIBBEMNETEthemet Config IP 3 12 MVIBBEMNETEthemet Config Netmask IE MVIBBEMNETEthemet Config Netmask 0 255 MVIBBEMNETEthernet Config Netmask 1 255 MVIBBEMNETEthernet Config Netmask 2 255 MVIBBEMNETEthemet Config Netmask 3 0 MVIBBEMNETEthermet Config G ateway ESSI MVIBBEMNETEthemet Config G ateway 0 192 MVIBBEMNETEthemet Config G ateway 1 168 MVIBBEMNETEthemet Config G ateway 2 0 MVIBBEMNETEthernet Config G ateway 3 1 To check the status of the message refer to the ReadEthernetMSG tag TA ReadEthemetMSG Flags 164020 ReadEthemetMSG EW ReadEthemetMSG ER ReadEthemetMSG DN ReadEthemetMSG ST ReadEthemetMSG EN ReadEthemetMSG TO ReadEthemetMSG EN CC ReadEthemetMSG ERR 1640000 ReadEthemetMSG EXERR 1640000 0000 ReadEthemetMSG ERR SRC 0 ReadEthemetMSG DN LEN ReadEthemetMSG REG LEN ejojojojojojojo 5 ojo Page 156 of 181 ProSoft Technology Inc April 23 2014 MVI56E MNET MNETXT ControlLogix Platform Modbus TCP IP Interface Module Reference User Manual 5 6 5 Writing the Ethernet Settings to the Module Expand the MVI56EMNETEthernet controller tag Set the new Ethernet configuration in MVIS6EMNET Ethernet Config Move a value of 1 to MVI56MNET Ethernet Write MVIBBEMNETEthemet MVI56EMNETEthermet Read MVI56EMNETEthernet Write MVIS6EMNETEthernet Contig MVI56EMNETEthermet Config IP MVIBBEMNETEthernet Config IP 0 MV
148. ng Creating routine Prescan When the import is completed the new rung with the Add On Instruction will be visible as shown in the following illustration RSLogix 5000 My Controller 1756 L63 MainProgram MainRoutine Ef Eile Edit view Search Logic Communications Tools Window Help alsa S 21 158 IB All Offline f I RUN EZ Path knn eum Are d a 4 b 1 No Edits a Evo M Controller My Controller Controller Tags E Controller Fault Handler Power Up Handler Tasks 5 MainTask amp MainProgram A Program Tags rmm C Unscheduled Programs 3 Motion Groups Ungrouped Axes 9 Add On Instructions AOIS6MNET E Data Types 3 Trends Configuration amp 1756 Backplane 1756 44 Output parameters Fault Code value SV Get System Value Class Name Module Instance Name MNET Attribute Name FaultCode Dest MNET CONTROL FaultCode o Add On MVIS6 MNET and MVISBE MNET modules AOISBMNET Add On MVIS6 MNET and 5 AOISBMNET AOISBMNET Connection Input Local1 1 Data Connection Output Local1 0 Data ff 0 1756 L63 My Controller MNET fJ 1 1756 MODULE MNET Ladder Diagram Main MainRoutine Rung of APP VER The procedure has also imported new user defined data
149. ng simple product and network configuration Sample ladder logic and Add On Instructions AOI are used for data transfer between module and processor 4 character alpha numeric scrolling LED display 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 allowing quick in the field product replacement by transferring the CF card 5 1 2 Modbus TCP IP Specifications ProSoft Technology s Modbus TCP IP implementation MNET includes both Client Master and server slave capabilities 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 possible including support for Enron or Daniel floating point formats Modbus TCP IP Server Slave Supports ten independent server connections for Service Port 502 MBAP Supports ten independent server connections for Service Port 2000 Encapsulated Accepts Modbus Function Codes 1 2 3 4 5 6 7 8 15 16 17 22 and 23 Module data can be derived from other Modbus server devices on the network through the Client or from the ControlLogix processor Page 108 of
150. nsfer 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 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 regulations 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 se
151. nternal program ERR Not Used Page 90 of 181 ProSoft Technology Inc April 23 2014 MVI56E MNET MNETXT ControlLogix Platform Modbus TCP IP Interface Module Diagnostics and Troubleshooting User Manual 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 the processor and any installed I O module not just the MVI56E MNET Verify that all modules in the rack are correctly configured in the ladder logic Module Errors Problem Description Steps to take MVI56E modules with scrolling LED display Backplane Status 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 processor is in RUN or REM RUN mode The backplane driver is loaded in the module
152. nty 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 177 of 181 April 23 2014 Support Service amp Warranty MVI56E MNET MNETXT ControlLogix Platform User Manual Modbus TCP IP Interface Module Page 178 of 181 ProSoft Technology Inc April 23 2014 MVI56E MNET MNETXT ControlLogix Platform Modbus TCP IP Interface Module Index User Manual Index 0 00 Return Query Data 145 A About the MODBUS TCP IP Protocol 138 Adding Multiple Modules Optional 25 Adding the Module to an Existing Project 160 Adding the Sample Ladder to an Existing Application 168 Adjusting the Input and Output Array Sizes 30 Allocation of Risks 176 ARP Timeout 46 B Backplane Data Transfer 110 Backplane Error Status Pointer 42 101 Backplane Status 97 Battery Life Advisory 4 Before You Begin 151 Bit Input Offset 55 C Choosing the Controller Type 165 Clearing a Fault Condition 91 Client Command Errors 105 135 Client Command List 135 Client Driver 134 Client Error Status Pointer 44 101 Cold Boot Block 9999 130 Command Control Blocks 5001 to 5006 123
153. o meet the needs of your application 1 In 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 Read Data area Important Because the module pages data in blocks of 200 registers at a time you should configure your user data areas in multiples of 200 registers Edit Module Error Status Pointer 4500 Read Register Count Read Register Start 1000 1000 Write Register Start 0 Write Register Count 600 Failure Flag Count 0 Initialize Output Data No Sings Pass Through Mode 0 Duplex Speed Code Auto negotiate Fm Number of regs to read from module for processor Reset Tag Reset All OK Cancel 2 To modify the WriteData array follow the above steps substituting WriteData for ReadData Page 30 of 181 ProSoft Technology Inc April 23 2014 MVI56E MNET MNETXT ControlLogix Platform Start Here Modbus TCP IP Interface Module User Manual 3 Save and download the configuration to the module page 63 and reboot 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 Read Register Start parameter must be set to a value of 2000 or greater ProSoft Technology Inc Page 31 of 181 April 23 2014 Start Here MVI56E MNET MNETXT
154. ock is commonly sent to the module any time configuration data modifications are made in the controller tags data area This will cause the module to read the new configuration information and to restart Block Request from Processor to Module Word Offset Description Length 0 9998 1 1 to 247 Spare 247 Cold Boot Block 9999 This block is sent from the ControlLogix processor to the module output image when the module is required to perform the cold boot hardware reset operation This block is sent to the module when a hardware problem is detected by the ladder logic that requires a hardware reset Block Request from Processor to Module Word Offset Description Length 0 9999 1 1 to 247 Spare 247 Page 130 of 181 ProSoft Technology Inc April 23 2014 MVI56E MNET MNETXT ControlLogix Platform Reference Modbus TCP IP Interface Module User Manual 5 3 Data Flow between the MVI56E MNET Module and ControlLogix Processor The following topics describe the flow of data between the two pieces of hardware ControlLogix processor and MVIS56E MNET module and other nodes on the Modbus TCP IP network under the module s different operating modes The module contains a server and a Client The server accepts TCP IP connections on service ports 502 MBAP 10 server connections and 2000 MNET 10 server connections The Client can generate either MBAP or MNET requests dependent on the service port selected in t
155. odule The ladder logic places the write data into the output image for transfer to the module This data is passed from the processor to the module for status and control information for use in other nodes on the network Controller Tags My Controller controller BAR Scope fa My Controller v Show MNETBLKSTATS MNETCLIENTSTATS MNE Data Type E MNETMODULEDEF MNET DATA MNETDATA MNET DATA ReadData INT 600 MNET DATA WriteD ata INT 600 MNET DATA WriteD ata D 1111 INT MNET DATA WriteD 1 2222 INT MNET DATA WriteD ata 2 3333 INT MNET DATA WriteD ata 3 4444 INT MNET DATA WriteD ata 4 5555 INT MNET DATA WriteD ata 5 0 INT gt Monitor Tags AEdit Tags 4 The WriteData array is related to the contents of the Write Data area of the module s internal database To view the actual registers in the module s internal database access the database display from ProSoft Configuration Builder s Diagnostics menu For more information see the section on PCB Diagnostics page 96 DATABASE DISPLAY 1000 TO 1099 DECINAL 1111 2222 3333 4444 5555 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 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 Page 82 of 181 ProSoft Technology Inc April 23 2014 MVI56E MNET MNETXT ControlLogix Platform Ladder Logic Modbus TCP IP
156. 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 module by using an Ethernet crossover cable not included ProSoft Technology Inc Page 59 of 181 April 23 2014 Configuring the MVI56E MNET Module MVI56E MNET MNETXT ControlLogix Platform User Manual Modbus TCP IP Interface Module 2 3 1 Setting Up a Temporary IP Address Important ProSoft Configuration Builder locates MVIb6E MNET 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 Inthe tree view in ProSoft Configuration Builder select the MVI56E MNET module gg Default Project Default Location Demo Module 2 Click the right mouse button to open a shortcut menu On the shortcut menu choose DIAGNOSTICS gg Default Project Default Location Demo Module Delete Rename Copy Choose Module Type View Configuration Export Configuration File s Load Config File Download from PC to D
157. ology 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 A 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 April 23 2014 Support Service amp Warranty User Manual Page 171 of 181 Support Service amp Warranty MVI56E MNET MNETXT ControlLogix Platform User Manual Modbus TCP IP Interface Module 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 referen
158. onfig Month 6 MVIBBSEMNET Clock Config D ay 18 MYIS6EMNETClock Config Hour 10 MVI56EMNETClock Config Minute 44 MVIS6EMNETClock Config Seconds 21 To check the status of the message refer to the ReadClockMSG tag ed ReadClockMSG Flags 16 0200 ReadClockMSG EW 0 ReadClockMSG ER 0 ReadClockMSG DN 0 ReadClockMSG ST 0 ReadClockMSG EN 0 ReadClockMSG TO 0 ReadClockMSG EN CC 1 ReadClockMSG ERR 16 0000 ReadClockMSG EXERR 16 0000_0000 ReadClockMSG ERR_SRC 0 ReadClockMSG DN_LEN 0 ReadClockMSG REG LEN 0 Page 158 of 181 ProSoft Technology Inc April 23 2014 MVI56E MNET MNETXT ControlLogix Platform Reference Modbus TCP IP Interface Module User Manual 5 6 7 Writing the Clock Value to the Module Expand the MVIS6MNETClock controller tag Set the new Clock value in MVI56MNET Clock Config Move a value of 1 to MVI56MNETCIOock Write MVI56EMNETClock facii MVISBEMNETClock Read 0 MVIBBEMNETClock Write MVIBBEMNETClack Config eee MVIBBEMNET Clock Config Y ear 2009 MVIBBEMNET Clock Config Month 6 MVIBBEMNET Clock Config Day 18 MVIBBEMNET Clock Config Hour 10 MVIBBEMNET Clock Config Minute 44 MVIBBEMNET Clock Config Seconds 21 The bit will be automatically reset to O MVI5S6EMNETClock HAS MVI56EMNETClock Read 0 MVIBEEMNETClock Write MVIBBEMNET Clock Config ILI MVI5SSEMNE TClock Config Year 2009 MVIBBEMNET Clock Config Month 6 MVIBBEMNET Clock Confi
159. ort 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 ProSoft Technology Inc Page 109 of 181 April 23 2014 Reference MVI56E MNET MNETXT ControlLogix Platform User Manual Modbus TCP IP Interface Module 5 2 Backplane Data Transfer The MVI56E MNET 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 update times range from 1 to 10 milliseconds This bi directional transfer of data is accomplished by the module putting data in the input image to send to the processor Data in the input image is placed in the processor s controller tags by ladder logic The input image is set to 250 words Processor logic inserts data to the output image to be transferred to the module The module s firmware program extracts the data and places it in the module s internal database The output image is set to 248 words The following illustration shows the data transfer method used to move data between the ControlLog
160. p or My Documents File Name Description 56 AddOn Rung v 4 L5X L5X file containing Add On Instruction user defined data types controller tags and ladder logic required to configure the MVIS56E MNET module MVIS5G6EMNET Optional AddOn Rung v1 0 Optional L5X file containing additional Add On L5X Instruction with logic for changing Ethernet configuration and clock settings Page 18 of 181 ProSoft Technology Inc April 23 2014 MVI56E MNET MNETXT ControlLogix Platform Start Here Modbus TCP IP Interface Module User Manual 1 7 Creating a New RSLogix 5000 Project 1 Open the FILE menu and then choose NEW f amp RSLogix 5000 x Edit View Search Logic Communications Tools Wi 8 New Cirian 8 Open Ctrl 0 2 Select your ControlLogix controller model 3 Select REVISION 16 4 Enter a name for your controller such as My Controller 5 Select your ControlLogix chassis type 6 Select SLOT 0 for the controller New Controller Vendor Allen Bradley Type 1756 L63 ControlLogix5563 Controller Revision Cancel Redundancy Enabled Help Name My Controller Description Chassis Type 1756 A4 4SlotControlLogix Chassis Slot fo 4 Create In JCNASLogik5000 Proects 0000 Browse ProSoft Technology Inc Page 19 of 181 April 23 2014 Start Here User Manual MVI56E MNET MNETXT ControlLogix Platform Modbus TCP IP Interface Module 1 7 1 Creating
161. pe 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 For Coil address 00115 specify 114 00115 00001 114 For register read or write commands FC 6 or 16 4X 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 53 of 181 April 23 2014 Configuring the MVI56E MNET Module MVI56E MNET MNETXT ControlLogix Platform User Manual Mod
162. port 502 response message is sent 234 MBAP Errors Sent Count This counter increments each time an MNet port 502 sends an exception response to Client Example Client sent illegal Modbus Data location address 235 MBAP Errors Received This counter increments each time an MNet port 502 Count receives a bad command Example Client sent illegal function command 236 Configuration Error Word This word contains a bitmap that indicates Client and server configuration errors 237 Reserved Not used 238 Reserved Not used 239 Client Cmd Request This value is incremented each time a command request is issued 240 Client Cmd Response This value is incremented each time a command response is received 241 Client Cmd Error This value is incremented each time an error message is received from a remote unit or a local error is generated for a command 242 Reserved Not used 243 Reserved Not used 244 Reserved Not used 245 Reserved Not used 246 Configuration Error Word This word contains a bitmap that indicates Client and server configuration errors 247 Client Current Error This value corresponds to the current error code for the Code Client 248 Client Last Error Code This value corresponds to the last error code recorded for the Client 249 Read Block ID Current Read Block ID An initialization value of 11 will be present until module boot up completes Status information transferred in the Read block can be viewed in the MNET
163. r 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 which 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 174 of 181 MVI56E MNET MNETXT ControlLogix Platform Modbus TCP IP Interface Module ProSoft Technology Inc April 23 2014 MVI56E MNET MNETXT ControlLogix Platform Support Serv
164. r Text Cancel Help ProSoft Technology Inc Page 155 of 181 April 23 2014 Reference MVI56E MNET MNETXT ControlLogix Platform User Manual Modbus TCP IP Interface Module 5 6 4 Reading the Ethernet Settings from the Module Expand the MVIS6MNETEthernet controller tag and move a value of 1 to MVI56MNET Ethernet Read MVI56EMNETEthemet MVIBBEMNETEthemet Read MVISBEMNETEthemet write 0 MVI56EMNETE thernet Config et MVIBBEMNETEthemet Config IP Ie MVIBBEMNETEthernet Config IP 0 0 MVIBBEMNETEthemet Config IP 1 0 MVIBBEMNETEtheret Config IP 2 0 MVIBBEMNETEthemet Config IP 3 0 MVIBBEMNETEthernet Config Netmask edi MVIBBEMNETEthernet Config Netmask 0 0 MVIBBEMNETEthernet Config Netmask 1 0 MVIBBEMNETEthernet Config Netmask 2 MVIBBEMNETEthernet Config Netmask 3 MVIBBEMNETEtheret Config Gateway p MVIBBEMNETEthernet Config G ateway 0 MVIBBEMNETEthernet Config G ateway 1 MVIBBEMNETEthernet Config G ateway 2 MVIBBEMNETEthernet Config G ateway 3 lojo o The bit will be automatically reset and the current Ethernet settings will be copied to MVIS6MNETEthernet controller tag as follows MVIBBEMNETEthemet CSI MVI56EMNETEthernet Read 0 MVISBEMNETEthernet write 0 MVIBBEMNETEthernet Config rem MVIBBEMNETEthernet Config IP Tx MVIBBEMNETEthemet Config IP Q 105 MVIBBEMNETEthemet Config IP 1 102 MVIBBEMNETEthemet Co
165. re illegal and 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 Coil Lo Data On off Ind 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 Off 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 n 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 In ProSoft products this is only accomplished through ladder logic programming Coils that are reprogrammed in the controller logic program are 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 In
166. rity Read Block 0 After the ladder logic changes the value of Local 1 O Data 247 from 5 to 0 then the Local 1 l Data 249 value is updated as before by returning all blocks 1 through 10 in a repeating sequence O Locak1 l Data 249 0 E Locatt 0 Data 247 10 M or 4 09 53 659 PM 8 0 TESTMNET Tuesday March 08 2005 j lt 4 09 51 654 09 51 859 4 09 52 059 4 09 52 259 4 09 52 459 9 52 659 PM Page 118 of 181 ProSoft Technology Inc April 23 2014 MVI56E MNET MNETXT ControlLogix Platform Reference Modbus TCP IP Interface Module User Manual 5 2 2 Special Function Blocks Special function blocks are optional blocks used to request special tasks from the module Initialize Output Data Blocks 1000 to 1024 Use the nitialize Output Data parameter in the configuration to bring the module to a known state after a restart operation If the nitialize Output Data parameter is enabled when the module performs a restart operation it will request blocks of output data from the ReadData array in the processor to initialize the Read Data area of the module s internal database Normal Data transfer Initialize Output Data transfer CLX Processor MNET Hodule UCLXProcessor Module Read Local Hodbus Tags Output Local X1 Tags Write Tags LocalX O Write Tags Hodbus Input gt Local 0 Block Request from Module to
167. rnal database to pass data and commands between the processor and the Client and server devices on the MODBUS TCP IP network Page 138 of 181 ProSoft Technology Inc April 23 2014 MVI56E MNET MNETXT ControlLogix Platform Reference Modbus TCP IP Interface Module User Manual 5 5 2 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 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 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 PtHi Data Start PtLo Data Z Of Pts Ho Data Of PtsLo Error Check Field 11 01 00 13 00 25 CRC 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 co
168. rolLogix Platform Ladder Logic Modbus TCP IP Interface Module User Manual 3 4 4 MNET UTIL Controller Tag Description CmdControl This group of tags is used to control special or irregular execution of the commands listed in the configuration under the MNet Client 0 Commands section regardless of whether or not such commands are normally enabled or disabled EventCmd This group of tags is used to create and have the Client execute a special ladder logic constructed command that is not included in the MNet Client 0 Commands section of the configuration file InitOutputData This group of tags is used for setting up data values when the module performs a restart operation It will request the processor s output data and transfer it into the module s Modbus registers Use the Initialize Output Data parameter in the configuration file to bring the module to a known state after a restart operation PassThru This group of tags is used for transferring a remote Client s write commands through the MNET module straight into the processor s controller tags without first storing the data in the module s Modbus registers IPsetPending Allows setting module IP address IPgetPending Allows getting module IP address For more information refer to Special Function Blocks page 119 ProSoft Technology Inc April 23 2014 Page 85 of 181 Ladder Logic MVI56E MNET MNETXT ControlLog
169. rom Module to Processor Word Offset Description Length 0 0 1 1 9956 9957 9958 9960 or 9961 1 2 Number of word registers in Modbus data set 1 3 Starting address for Modbus data set 1 4 to 248 Modbus data set 245 249 9956 9957 9958 9960 or 9961 1 Page 126 of 181 ProSoft Technology Inc April 23 2014 MVI56E MNET MNETXT ControlLogix Platform Reference Modbus TCP IP Interface Module User Manual Pass Through Block 9959 from Module to Processor Word Offset Description Length 0 0 1 1 9959 1 2 Number of word registers in Modbus data set 1 3 Starting word address for Modbus data set 1 4 to 53 Modbus data set 50 54 to 103 Bit mask for the data set Each bit to be considered with the 50 data set will have a value of 1 in the mask Bits to ignore in the data set will have a value of 0 in the mask 104 to 248 Spare data area 145 249 9959 1 Pass Through Block 9970 from Module to Processor Word Offset Description Length 0 0 1 1 9970 1 2 1 1 3 0 1 4 to 248 Spare data area 245 249 9996 1 The ladder logic should copy and parse the received message and control the processor as expected by the Client device The processor responds to the formatted pass through blocks with a write block Response Blocks 9956 9957 9958 9959 9960 9961 or 9970 from Processor to Module Word Offset Description Length 0 9956 9957 9958
170. rst register refers to command 1 and so on Word 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 commands in the Client Command List are polled and executed an error value is maintained in the module for each command This error list can be transferred to the processor Standard Modbus Exception Code Errors Description Illegal function Illegal 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 same as 36 253 Incorrect slave server address in response 254 Incorrect function code in response 255 Invalid CRC LRC value in response ProSoft Technology Inc April 23 2014 Page 105 of 181 Diagnostics and Troubleshooting MVI56E MNET MNETXT ControlLogix Platform User Manual Modbus TCP IP Interface Module MNET Client Specific Errors Code Description 36 MNET command response timeout same as 11 37 TCP IP connection ended before session finished Command List Entry Errors
171. ructions ADIBBEMNET MVISBEMNET Clock MNETCLOCK Create New Create New MNETETHER EX MESSAGE MVIBBEMNETEthemet ReadClockMSG Create New Create New MESSAGE MESSAGE MESSAGE ReadEthemetMSG WiiteClockMSG WriteE thernetMSG Create New Create New Create New The Optional Add On Instruction will now be visible in the ladder logic Observe that the procedure has also imported data types and controller tags associated with the Optional Add On Instruction fe RSLogix 5000 L63 1756 L63 MainProgram MainRoutine Ef File Edit View Search Logic Communications Tools Window Help alsa S se s mig AA si sj Offline D m RUN y OK No Forces M BAT No Edits 4 se oj 41 Favorites Add Meinl 3 Motion Groups E Ungrouped Axes Add On Instructions 89 AOIS6EMNET_Optional Parameters and Local Tags Logic AOIS6MNET 1 69 Data Types User Defined MNETBLKSTAT MNETCLOCKTYPE MNETCMDCONTROL MNETCONTROL MNETDATA MNETDATETIME MNETETHERNET EE Path MVISBE MNET Optional Add On Ethernet Clock AOISBEMNET_Optional MVISBE MNET Optional Add On Ethernet Clock AOISBEMNET Optional AOISBEMNET Optional MVISBEMNETEthernet MVISBEMNETEthernet MVIS6EMNETClock MVISSEMNETClock ReadEthernetMSG ReadEthernetMSG WriteEthernetMSG ReadClockMSG WriteClockMSG White
172. s for large register quantities multiple transmissions will be made using register 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 Error Check Field 11 03 06 02 2B 00 00 00 64 CRC ProSoft Technology Inc Page 141 of 181 April 23 2014 Reference MVI56E MNET MNETXT ControlLogix Platform User Manual Modbus TCP IP Interface Module 5 5 5 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 I O 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
173. s for each menu command The first menu you see when you connect to the module is the Main menu Gj Diagnostics Connection Log Module af oaae 7 MVISBE MNET_SLOT4 Time 09 03 55 4 a MODULE Select item within MvIS6E MNET for diagnostic information version Config G NIC Status G Static ARP gf BACKPLANE Status CLIENT 0 Li Config Status Command List Command Status af MNET 5 Decimal F Hex Float Path Ethemet 105 102 0 25 4 2 3 Monitoring Module Information Use the MODULE menu to view configuration and hardware information for the MVI56E MNET module s backplane and Ethernet application port Version Use the Version menu to view module hardware and firmware information MVI56E MNET_SLOT4 gt MODULE gt Version PRODUCT NAME CODE SOFTWARE REVISION LEVEL OPERATING SYSTEM REVISION RUN NUMBER PROGRAM SCAN COUNTER IP ADDRESS ETHERNET ADDRESS MAC BACKPLANE DRIVER VERSION BACKPLANE API VERSION MODULE NAME VENDOR ID DEVICE TYPE PRODUCT CODE SERIAL NUMBER REVISION SLOT MNES 2 02 70609 10901 711849 105 102 0 4 00 0d 8d 00 3a 9d 72 06 71 01 MVIS6E MNET 309 12 5004 000003EC 2 02 1 96 181 ProSoft Technology Inc April 23 2014 MVI56E MNET MNETXT ControlLogix Platform Diagnostics and Troubleshooting Modbus TCP IP Interface Module User Manual Config Use the Configuratio
174. s may impair suitability for Class Division 2 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 Suitable for use in Class Division 2 Groups A C and D Hazardous Locations or Non Hazardous Locations ATEX IECEx 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 ATEX IECEx Certified tool secured IP54 enclosure The devices shall provide external means to prevent the rated voltage being exceeded by transient disturbances of more than 4096 This device must be used only with ATEX certified backplanes D Before operating the reset switch be sure the area is known to be non hazardous Ex II 3 G Ex nA T4 Gc 0 C lt Ta lt 60 C 25 C lt Ta lt 70 C XT models only 1 Equipment intended for above ground use not for use in mines 3 Category 3 equipment investigated for normal operation only G Equipment protected against exp
175. ssor uses RSLogix 5000 version 15 or earlier you will not be able to use the Add On Instruction for your module Follow the steps below to obtain and use a sample program for your application 5 8 1 Opening the Sample Program in RSLogix The sample program for your MVIS6E MNET module includes custom tags data types and ladder logic for data I O status and command control For most applications you can run the sample program without modification or for advanced applications you can incorporate the sample program into your existing application Download the manuals and sample program from the ProSoft Technology web site You can always download the latest version of the sample ladder logic and user manuals for the MVIBGE MNET module from the ProSoft Technology website at www prosoft technology com prosoft support downloads http www prosoft technology com prosoft support downloads From that link navigate to the download page for your module and choose the sample program to download for your version of RSLogix 5000 and your processor To determine the firmware version of your processor Important The RSLinx service must be installed and running on your computer in order for RSLogix to communicate with the processor Refer to your RSLinx and RSLogix documentation for help configuring and troubleshooting these applications 1 Connect an RS 232 serial cable from the COM serial port on your PC to the communication port on the front of
176. t ProSoft Technology Inc Page 139 of 181 April 23 2014 Reference MVI56E MNET MNETXT ControlLogix Platform User Manual Modbus TCP IP Interface Module 5 5 3 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 Data Start PtHi DataStartPtLo Data of Pts Hi Data of Pts Lo 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 12ON O OFF The lower order bi
177. t Tools Help Default Project Ga 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 Your first task is to add the MVIS6E MNET 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 Page 38 of 181 ProSoft Technology Inc April 23 2014 MVI56E MNET MNETXT ControlLogix Platform Configuring the MVIBGE MNET Module Modbus TCP IP Interface Module User Manual 2 Onthe shortcut menu select CHOOSE MODULE TYPE This action opens the Choose Module Type dialog box Choose Module Type Product Line Filter C all C PLX4000 C PLX6000 C MVI46 C MVI56 C MVI71 C PLX5000 C PTQ C MVI69 MVIS6E Search Module Type STEP 1 Select Module Type Module 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 MVIS56E MNET and then click to save your settings and return to the ProSoft Configuration Builder window ProSoft Technology Inc Page 39 of 181 April 23 2014 Configuring the MVI56E
178. t forth in What Is Covered By This Warranty page 173 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 175 of 181 April 23 2014 Support Service amp Warranty MVI56E MNET MNETXT ControlLogix Platform User Manual Modbus TCP IP Interface Module 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 substitute 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
179. t of the first character contains the addressed input and the remainder follow For input 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 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 140 of 181 ProSoft Technology Inc April 23 2014 MVI56E MNET MNETXT ControlLogix Platform Reference Modbus TCP IP Interface Module User
180. teEthemetMSG WriteEthernetMSG Flags WriteE themetMSG EW WiiteEthemetMSG ER WiiteEthemetMSG DN WiiteEthemetMSG S T WriteE thernetMSG EN WriteE themetMSG TO WiriteEthemetMSG EN CC WriteEthemetMSG ERR WiiteEthemetMSG EXERR WriteEthernetMSG ERR_SRC WiiteEthemetMSG DN LEN WiiteEthemetMSG REQ LEN o ale fe my o fo Oe NO P s f e e ioo n o t t m INE 164020 olo P 1640000 1640000 0000 ProSoft Technology Inc April 23 2014 Page 157 of 181 Reference MVI56E MNET MNETXT ControlLogix Platform User Manual Modbus TCP IP Interface Module 5 6 6 Reading the Clock Value from the Module Expand the MVIS6MNETClock controller tag and move a value of 1 to MVI56MNET Clock Read MVI5S6EMNETClock es MVI56EMNE TClock Read MVI56EMNETClock Write 0 MVIBBEMNETClack Config DI MVIBBEMNET Clock Config Y ear 0 MVI5S6EMNETClock Confia Month 0 MVIBBSEMNET Clock Config D ay 0 MYIS6EMNETClock Config Hour 0 MVI56EMNETClock Config Minute 0 MVIBBEMNET Clock Config Seconds 0 The bit will be automatically reset and the current clock value will be copied to MVI56MNET Clock Config controller tag as follows ed MVISBEMNETClock Riead 0 MVISBEMNET Clock write 0 MVIBBEMNETClack Config e MVIBBEMNET Clock Config Y ear 2009 MVIBBEMNETClack C
181. ter a request is issued Command Error Delay 0 to 300 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 Page 46 of 181 ProSoft Technology Inc April 23 2014 MVI56E MNET MNETXT ControlLogix Platform Configuring the MVI56E MNET Module Modbus TCP IP Interface Module User Manual 2 2 6 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 MVIBGE MNET communication module and the second part contains information required to interface to the Modbus TCP IP server device Command List Overview In order to interface the MVI56E MNET 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 th
182. ter the four octet IP address numbers of the target Modbus server into this array tag ServicePort Enter 502 for a MBAP message or 2000 for a MNET message SlaveAddress Enter the Modbus Node Address Enter 0 if not needed InternalDBAddress Enter the database address for the Client PointCount Enter the number of words or bits to be transferred by the Client SwapCode Enter the swap type for the data This function is only valid for function codes 3 and 4 ModbusFunctionCode Enter the Modbus function code for the command DeviceDBAddress Enter the database address for the server EventCmdStatusReturned Temporary variable that provides status indication of whether or not the Event Command was successfully added to the command priority queue EventBlockID Temporary variable that provides the identification code number of the Block ID just executed Page 122 of 181 ProSoft Technology Inc April 23 2014 MVI56E MNET MNETXT ControlLogix Platform Reference Modbus TCP IP Interface Module User Manual Command Control Blocks 5001 to 5006 Note Command Control is not needed for normal Modbus command list polling operations and are needed only occasionally for special circumstances During routine operation the module continuously cycles through the user defined MNET Client O Command List page 47 examining commands in the order they are listed and sending enabled commands on th
183. the Module s Web Page 95 4 2 2 The Diagnostics 96 4 2 3 Monitoring Module Information eesseeeeeenenene enne 96 4 2 4 Monitoring Backplane Information seessseeeeeneeennennn 97 4 2 5 Monitoring MNET Client 98 4 2 6 Monitoring MNET Server Information 99 4 2 7 Monitoring Database Information eeseeeeeeene 100 4 3 Reading Status Data from the Module sse 101 4 3 1 Status Data Definition x wie aia terit tee ine etl e in t patera 102 4 3 2 Configuration Error Word dene tn ette inre mette E e eben 104 4 3 3 Glient Commadnd Errots sem tne at eb nee ade eee Lh e peter 105 5 Reference 107 5 1 Product Specifications anon te be ed ete hito 107 5 1 1 General Specifications iis tact thu edit Adi eet i 108 5 1 2 Modbus TCP IP Specifications sse 108 551 Hardware Specifications nnns 109 5 2 Backplane Data Transfer entente 110 5 2 1 Normal Data Transfer 113 5 2 2 Special Function Blocks sssssssssssesseeeee ener 119 5 3 Data Flow between the MVIS6E MNET Module and Con
184. the processor 2 Start RSLogix 5000 and close any existing project that may be loaded 3 Open the COMMUNICATIONS menu and choose GO ONLINE RSLogix will establish communication with the processor This may take a few moments ProSoft Technology Inc Page 163 of 181 April 23 2014 Reference MVI56E MNET MNETXT ControlLogix Platform User Manual Modbus TCP IP Interface Module 4 When RSLogix has established communication with the processor the Connected To Go Online dialog box will open Minor Faults Redundancy Nonvolatile Memory Options General Date Time Major Faults Condition The project file Controller ACD was not found in your project directory Connected Controller Controller Name Controller Controller Type 1756 L55 A 1756 M13 A ControlLogix5555 Controller Comm Path AB_DF1 1 Security lt None gt Offline Project Controller troller Type Cancel Help 5 Inthe Connected To Go Online dialog box click the GENERAL tab This tab shows information about the processor including the Revision firmware version In the following illustration the firmware version is 11 32 Connected To Go Online x Minor Faults Redundancy Nonvolatile Memory Options General Date Time Major Faults Vendor Allen Bradley Type 1756 L55 A 1756 M13 A ControlLogix5555 Controller Change Revision 11 32 Name Controlle Description Chassis Type Select
185. ting 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 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 MVI56E Advanced Add On Instruction CO Client CmdCnt X MinDly X CmdOffs X RespTmout X Retries X ErrOffs X ARPTmout X ErrDelay X FitFlag FItSt FltOffs X SVR server BIOffs X WIOffs X OutOffs X HoldOffs X FitFlag FItSt X FItSt X CommTmout X After power up and every reconfiguration the module will display the configuration of the application port s The information consists of Client CmdCnt number of commands configured for the Client MinDly Minimum Command Delay parameter CmdOffs Command Error Pointer parameter RespTmout Response Timeout parameter Retries Retry Count parameter ErrOffs Error Status Offset parameter ARPTmout ARP Timeout parameter ErrDelay Command Error Delay parameter FitFlag Float Flag parameter Fit St Float Start parameter FltOffs Float Offset parameter Server BlOffs Bit Input Offset parameter WIOffs Word Input Offset parameter OutOffs Output offs
186. tion Codes 150 Modbus Exception Responses 149 Modbus Function 52 Modbus Protocol Specification 138 Modbus TCP IP Specifications 108 Module 42 Module Communication Error Codes 105 Monitoring Backplane Information 97 Monitoring Database Information 100 Monitoring MNET Client Information 98 Monitoring MNET Server Information 99 Monitoring Module Information 96 MVI56 E MNET Controller Tags 76 MVI56 E MNET User Defined Data Types 78 N NIC Status 97 No Other Warranties 176 Node IP Address 51 52 Non Scrolling LED Status Indicators 90 Normal Data Transfer Blocks 42 44 101 113 Opening the Sample Program in RSLogix 163 Output Offset 55 Overview 151 P Package Contents 14 Pass Through Blocks 9956 9961 9970 and 9996 126 Pass Through Mode 44 Pinouts 108 109 136 Poll Interval 50 Preset Multiple Registers Function Code 16 148 Preset Single Register Function Code 06 144 Printing a Configuration File 41 Product Specifications 9 107 ProSoft Technology Product Documentation 2 R Read Block 113 Read Coil Status Function Code 01 139 Read Holding Registers Function Code 03 141 Read Input Registers Function Code 04 142 Read Input Status Function Code 02 140 Read Register Count 42 81 Read Register Start 42 Reading Status Data from the Module 101 Reading the Clock Value from the Module 158 Readin
187. tput references are known no output reference is needed in the function The normal response contains the status of the eight Exception Status outputs The outputs are packed into one data byte with one bit per output The status of the lowest output reference is contained in the least significant bit of the byte Page 144 of 181 ProSoft Technology Inc April 23 2014 MVI56E MNET MNETXT ControlLogix Platform Reference Modbus TCP IP Interface Module User Manual 5 5 9 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 respon
188. trolLogix Processor 131 5 3 1 gimp E 132 5 3 2 Client DrIVBE ee pepe ieee Te rer eee 134 5 4 Ethernet Cable Specifications esses eee 136 5 4 1 Ethernet Cable Configuration essssssseseseseeee eene 136 5 4 2 Ethernet a KAEN ANa ARA E 137 5 5 Modbus Protocol Specification sss 138 5 5 1 About the MODBUS TCP IP Protocol sssssseeeeneeenens 138 5 5 2 Read Coil Status Function Code 01 139 5 5 3 Read Input Status Function Code 02 sse 140 5 5 4 Read Holding Registers Function Code 03 141 5 5 5 Read Input Registers Function Code 04 142 5 5 6 Force Single Coil Function Code 05 143 5 5 7 Preset Single Register Function Code 06 144 5 5 8 Read Exception Status Function Code 7 144 5 5 9 Diagnostics Function Code 08 0 ccccceseeeeeneeceeeeeeeaeeeeeaeeeeeeeseeeeseaeeeeaeeeeeeeseas 145 Page 6 of 181 ProSoft Technology Inc April 23 2014 MVI56E MNET MNETXT ControlLogix Platform Contents Modbus TCP IP Interface Module User Manual 5 5 1
189. types data objects and the Add On instruction for your project gt 4 Favortes Add On Alarms Bit i Timer Counter Fi 7 SAVE the application and then download the sample ladder logic into the processor ProSoft Technology Inc Page 24 of 181 April 23 2014 MVI56E MNET MNETXT ControlLogix Platform Modbus TCP IP Interface Module Start Here User Manual Adding Multiple Modules Optional 1 Inthe O Configuration folder click the right mouse button to open a shortcut menu and then choose NEW MODULE 1 0 Configuration 9 1756 Backplane 1756 Ba 0 175663 wy New Module B 1 1756 MoDULE rrr 2 Select 1756 MODULE L Select Module Module Analog Communications Controllers Digital Drives Motion Other 1756 MODULE Specialty By Category By Vendor Generic 1756 Module Allen Bradley Add Favorite Favorites Cancel 3 Fillthe module properties as follows Parameter Value Name Enter a module identification string Example MNET 2 Description Enter a description for the module Example MopBus TCP IP INTERFACE MODULE Comm Format Select DATA INT Slot Enter the slot number in the rack where the MVIbGE MNET module is located Input Assembly Instance 1 Input Size 250 Output Assembly Instance 2 Output Size 248 Configuration Assembly
190. u 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 previously 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 CIPconnect STEP 2 Transfer File s DOWNLOAD Test Connection Cancel Click TEST CONNECTION to verify that the IP address allows access to the module 3 If the connection succeeds click DOWNLOAD to transfer the Ethernet configuration to the module ProSoft Technology Inc Page 63 of 181 April 23 2014 Configuring the MVI56E MNET Module MVI56E MNET MNETXT ControlLogix Platform User Manual Modbus TCP IP Interface 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 Inthe Download dialog box click BROWSE DEVICE S to open ProSoft Discovery Service H Prosoft Discovery Service Assign Temporary IP Device Details Remove Temporary IP View modules webpage Select for PCB 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
191. u n e en B RD 76 User Defined Data Types UDTS 78 Using Controller Tags nennen 79 Controller Tag Overview nennen 80 Ladder logic is required for managing communication between the MVI56E MNET module and the processor The ladder logic handles tasks such as Module backplane data transfer 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 75 of 181 April 23 2014 Ladder Logic MVI56E MNET MNETXT ControlLogix Platform User Manual Modbus TCP IP Interface Module 3 1 Controller Tags Data related to the MVI56E MNET is stored in the ladder logic in variables called controller tags Individual controller tags can be grouped into collections of controller tags called controller tag structures A controller tag structure can contain any combination of Individual controller tags Controller tag arrays Lower level controller tag structures The controller tags for the module are pre programmed into the Add On Instruction Import Run
192. ubleshooting MVI56E MNET MNETXT ControlLogix Platform User Manual Modbus TCP IP Interface Module 4 2 5 Monitoring MNET Client Information Use the MNET CLIENT x 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 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 For an explanation of each value refer to Client Command Error page 105 Page 98 of 181 ProSoft Technology Inc April 23 2014 MVI56E MNET MNETXT ControlLogix Platform Diagnostics and Troubleshooting Modbus TCP IP Interface Module User Manual 4 2 6 Monitoring MNET Server Information Use the MNET SERVER menu to view the configurat
193. ut Status X X 3 Read Holding Registers X X 4 Read Input Registers X X 5 Set Single Coil X X 6 Single Register Write X X 7 Read Exception Status X X 8 Diagnostics X 15 Multiple Coil Write X X 16 Multiple Register Write X X 22 Mask Write 4X X 23 Read Write X 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 Entry 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 PollInterval Count Swap IP Serv Slave Function Code Device Modbus Code Address Time Code Address Port Node Address Code Register 1 10th Bit 0 IP Port Address Read Coil 0x Register bit Seconds Count Address Code Register 1 10th Bit 0 IP Port Address Read Input 1x Register bit Seconds Count Address Code Register 1 10th Word Code IP Port Address Read Holding Register Seconds Count Address Registers 4x Code Register 1 10th Word 0 IP Port Address Read Input Registers Register Seconds Count Address 3x Code 1 bit 1 10th Bit 0 IP Port Address Force Write Single Register Seconds Count Address Coil 0x Code 1 bit 1 10th Word 0 IP Port Address Preset Write Single Register Seconds Count Address Register 4x Code Register
194. ver Communication Module allows Rockwell Automation ControlLogix processors to interface easily with other Modbus compatible devices Compatible devices include Modicon Programmable Automation Controllers PACs as well as a wide variety of instruments and devices A 5000 word register space in the module exchanges data between the processor and the Modbus TCP IP network The MVI56E MNET and MVI56E MNETXT are functionally the same The MVI56E MNET is designed for standard process applications The MVI56E MNETXT is designed for the Logix XT control platform allowing it to operate in extreme environments and at higher operating temperatures It has a conformal coating to protect it from harsh or caustic conditions ProSoft Technology Inc Page 107 of 181 April 23 2014 Reference MVI56E MNET MNETXT ControlLogix Platform User Manual Modbus TCP IP Interface Module 5 1 1 General Specifications Backward compatible with previous MVI56 MNET 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 and EtherNet IP pass through communication ProSoft Configuration Builder PCB software supported a Windows based graphical user interface providi
195. will display as 151 212 Reserved Not used 213 Reserved Not used 214 Reserved Not used 215 Reserved Not used 216 Reserved Not used 217 Reserved Not used 218 Reserved Not used 219 Reserved Not used 220 Reserved Not used 221 Reserved Not used 222 MNet Request Count This counter increments each time an MNet port 2000 request is received 223 MNet Response Count This counter is incremented each time an MNet port 2000 response message is sent 224 MNet Errors Sent Count This counter increments each time an MNet port 2000 sends an exception response to Client Example Client sent illegal Modbus Data location address 225 MNet Errors Received This counter increments each time an MNet port 2000 Count receives a bad command Example Client sent illegal function command 226 Configuration Error Word This word contains a bit map that indicates Client and server configuration errors 227 Reserved Not used 228 Reserved Not used Page 114 of 181 ProSoft Technology Inc April 23 2014 MVI56E MNET MNETXT ControlLogix Platform Reference Modbus TCP IP Interface Module User Manual Word Offset Content Description 229 Reserved Not used 230 Reserved Not used 231 Reserved Not used 232 MBAP Request Count This counter increments each time a MBAP port 502 request is received 233 MBAP Response Count This counter is incremented each time a MBAP
196. x 5000 XML Files L5X ADIBBMNET Create New Local 1 1 4B 1756 MOD Use Existing Local 1 0 AB 756 MOD Use Existing MNETMODUL Output parameters Create New ProSoft Technology Inc Page 27 of 181 April 23 2014 Start Here User Manual MVI56E MNET MNETXT ControlLogix Platform Modbus TCP IP Interface Module 11 Associate the I O connection variables to the correct module The default values are LOCAL 1 l and LOCAL 1 O so these require change Import Configuration Tags Data Types Add On Instructions AOISEMNET Local 2 1 3g FE Local 1 l g Local 1 0 3g 41 2 0 Controller Program Show Show All Import Configuration Tags Data Types Add On Instructions AOISEMNET AB 1756_MODULE_INT_SOOBytes I 0 AB 1756 MODULE INT 496Bytes 0 0 AB 1756_MODULE C 0 AB 1756 MODULE INT SO0Bytes L0 AB 1756 MODULE INT 496Bytes 0 0 ADIBEMNET Local 2 1 AB 756 MOD Discard Local2 0 FELocal1 0 fe Local 2 C Bj mjLocat2 Local 2 0 f EMNET Controller Program Show Show All AB 1 756 M D Use Existing Data Type AB 1756 MODULE INT 496Bytes 0 0 AB 1756 MODULE C 0 AB 1756 MODULE INT 500Bytes I 0 AB 1756 MODULE INT 496Bytes 0 0 MNETMODULEDEF Page 28 of 181 ProSoft Technology Inc April 23 2014 MVI56E MNET MNETXT ControlLogix Platform Modbus TCP IP Interface Module Start Here User Manual C
197. y 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 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 Ob Gateway Target
198. y 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 expense 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

MVI56E-MNET / MNETXT

Contents

Download Pdf Manuals

Related Search

Related Contents