Home

MVI56E-MNETR

1. 26 2 Configuring the MVIS56E MNETR Module 49 2 1 Using ProSoft Configuration Builder Software 49 2 2 Download the Project to the Module 67 2 8 Using ClPconnect to Connect to the Module 68 3 Ladder Logic 79 3 1 MNETRModuleDeef esses 79 3 2 Modbus Message ener ener 84 4 Diagnostics and Troubleshooting 85 4 1 Reading Status Data from the Module sse 85 4 2 The Diagnostics EEEE EEE IES nnne 86 4 3 Monitoring Module Information sese 89 4 4 Monitoring Backplane Information sss eene 90 4 5 Monitoring Database Information sssssssssseses eene 91 4 6 Monitoring MNET Client Information 92 4 7 Monitoring MNET Server Information 93 4 8 pK L 93 4 9 LED Status 97 _ oc c MH 5 1 Product Specifications 101 ProSoft Technology Inc Page 5 of 153 August 31 2009 MVISGE MNETR ControlLogix Platform Contents Modbus TCP IP Interface Module with Reduced Data Block User Manual 5 2 Functional Overview
2. nnne nnn nennen nennen 103 5 3 Ethernet Cable Specifications sssssssseseeseeeeeeen nnns 118 5 4 MVI56E MNETR Status Data 119 5 5 Modbus Protocol Specification 121 5 6 Using the Rung Import with Utility Add On Instruction sess 132 5 7 Adding the Module to an Existing Project 141 5 8 Using the Sample Program RSLogix Version 15 and earlier 144 6 Support Service amp Warranty 145 6 1 How to Contact Us Technical 5 145 6 2 Return Material Authorization RMA Policies and Conditions 146 6 3 FMETED WARRANTY ie i Mie dates o Have I ERREUR eda 147 Index Page 6 of 153 ProSoft Technology Inc August 31 2009 Start MVIS56E MNETR ControlLogix Platform User Manual Modbus TCP IP Interface Module with Reduced Data Block Guide to the MVIS6E MNETR User Manual Function Section to Read Details Introduction gt Start Here page 9 This Section introduces the customer to the Must Do module Included are package contents system requirements hardware installation and basic configuration Verify Communication Verifying This section describes how to verify Diagnostic and Communication communications with the network Diagnosti
3. Block Range Descriptions 1 Status block 0 Status block 1 to 125 Read or write data 1000 to 1124 Output Initialization Blocks 2000 Event Command Block 5001 to 5006 Command Control 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 9970 Function 99 indication block 9996 Unformatted Pass through block with raw Modbus message 9998 Warm boot control block 9999 Cold boot control block These block identification codes can be broken down into a few groups Normal data transfer blocks 1 to 125 Initialization blocks 1000 to 1124 Command control blocks 2000 5001 to 5006 9998 and 9999 and pass through function blocks 9956 to 9961 9970 and 9996 ProSoft Technology Inc Page 105 of 153 August 31 2009 MVI56E MNETR ControlLogix Platform Modbus TCP IP Interface Module with Reduced Data Block User Manual Normal Data Transfer Normal data transfer includes the paging of the user data found in the module s internal database in registers 0 to 4999 and the status data These data are transferred through read input image and write output image blocks The followi
4. ProSoft Technology Inc August 31 2009 Page 139 of 153 MVIS6E MNETR ControlLogix Platform Reference Modbus TCP IP Interface Module with Reduced Data Block User Manual The bit will be automatically reset and the current clock value will be copied to MVIB6MNETRCLOCK CoNFIG controller tag as follows MVIBBEMNETRClock MVISBEMNETRClock Read MVI56EMNETAClock write MVIBBEMNETRClock Config MVIBBEMNETRClock Config Y ear MVIBBEMNETRClock Config Month MVIBBEMNETRClock Config D ay MVIBBEMNETRClock Config Hour MVI56EMNETRClock Config Minute MVI56EMNETRClock Config Seconds N of we a ls m To check the status of the message refer to the READCLOCKMSG tag ed ReadClockMSG Flags 1640200 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 5 6 7 Writing the Clock Value to the Module Expand the MVIS6MNETRCLOCK controller tag Set the new Clock value in MVIBSGMNETRCLOCK CONFIG Move a value of 1 to MVIBSGMNETRCLOCK WRITE MVIBBEMNETRClock eal MVIBBEMNETRClock Read 0 MVIBBEMNE TRClock wirite 1 MVIBBEMNETRClock Config e MVIBBEMNETRClock Config Y ear 2009 MVIBBEMNETRClock Config Month 5 MVIBBEM
5. MVIBBEMNETREthemet ned MVIBBEMNETREthemet Riead 0 MVI56EMNETREthernet Write 0 MVIBBEMNETREthernet Config em MVIBBEMNETREthernet Config IP MVIBBEMNETREthermet Config IP U 105 MVIBBEMNETREthernet Config IP 1 102 MVIBBEMNETREthernet Config IP 2 0 MVIBBEMNETREthemet Config IP 3 32 MVISBEMNETRE thetret Curifiy Netiiask 1 MVIBBEMNETREthemet Config Netmask 0 255 MVIBBEMNETREtheret Config Netmask 1 255 MVIBBEMNETREthermet Config Netmask 2 255 MVIBBEMNETREthermet Config Netmask 3 0 MVIBBEMNETREthemet Config Gateway cod MVIBBEMNETREthermet Config G ateway U 192 MVIBBEMNETREthermet Config G ateway 1 168 MVIBBEMNETREthemet Config G ateway 2 0 MVIBBEMNETREthermet Config G ateway 3 1 ProSoft Technology Inc Page 137 of 153 August 31 2009 MVI56E MNETR ControlLogix Platform Reference Modbus TCP IP Interface Module with Reduced Data Block User Manual To check the status of the message refer to the READETHERNETMSG tag e ReadEthernetMSG Flags 1640200 ReadEthernetMSG Ew 0 ReadEthernetMSG ER 0 ReadEthernetMSG DN 0 ReadEthemetMSG ST 0 ReadEthernetMSG EN 0 ReadEthernetMSG TO 0 ReadEthernetMSG EN_CC 1 ReadEthemetMSG ERR 16 0000 ReadEthemetMSG EXERR 16 0000 0000 ReadEthemetMSG ERR SRC 0 ReadEthemetMSG DN LEN 0 ReadEthemetMSG REGQ LEN 0 5 6 5 Writing the Ethernet Settings to the Module Expand the MVIS6EMNETRETHERNET controller tag Set the
6. 2 Page 42 of 153 ProSoft Technology Inc August 31 2009 Start Here MVI56E MNETR ControlLogix Platform User Manual Modbus TCP IP Interface Module with Reduced Data Block 9 Select the file MVI56 E MNETR_AddOn_Rung_ lt Version gt L5X Import Rung Look in Desktop 2 Y My Computer My Documents My Recent amp gMy Network Places Decuments 3 Desktop My Computer a File name MVIBSEMNETR AddOn Rung vi LLEX v Import My Network Files of type RSLogix 5000 XML Files L5X Cancel Places This action opens the IMPORT CONFIGURATION dialog box showing the controller tags that will be created Import Configuration Tags Data Types Add On Instructions ADIBBMNETR Create New Local 1 1 AB 756 MOD Discard Locat1 0 1756 Discard MNETRModul Create New ProSoft Technology Inc Page 43 of 153 August 31 2009 MVISGE MNETR ControlLogix Platform Start Here Modbus TCP IP Interface Module with Reduced Data Block User Manual 10 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 Name Alias For Data Type AOISEMNETR Use Existing Local 2 B 1756_MOD Use Existing 8 Local 1 1 AB 1756 MODULE INT 84Bytes l 0 8 0 AB 1
7. Page 48 of 153 ProSoft Technology Inc August 31 2009 Configuring the MVIBGE MNETR Module MVI56E MNETR ControlLogix Platform User Manual Modbus TCP IP Interface Module with Reduced Data Block 2 Configuring the MVIS6E MNETR Module In This Chapter Using ProSoft Configuration Builder 49 Download the Project to the Module een 67 Using ClPconnect to Connect to the 68 2 1 Using ProSoft Configuration Builder Software ProSoft Configuration Builder PCB provides a quick and easy way to manage module configuration files customized to meet your application 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 to new projects Note The MVI56E MNETR module receives its protocol and backplane configuration information from the Personality Module Compact Flash Use ProSoft Configuration Builder to configure module settings and to download changes to the Personality Module 2 1 1 Set Up the Project To begin start PROSOFT CONFIGURATION BUILDER PCB M Microsoft Update Set Program Access and Defaults W Windows Catalog Accessories deus pde em Administrative Tools provers Prosoft 0 7 D Documents 6 Internet Explorer a ProSoft Transport Pa
8. 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 1 3 Package Contents The following components are included with your MVIbGE MNETR 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 lt ModelNumbeXTr gt Modbus TCP IP Interface Module with Reduced MNETR Data Block Module 1 Cable 5 5 foot Ethernet Straight Through Cable Gray 1 ProSoft CD 013 Contains configuration tools for the MVI56E Solutions CD MNETR module 1 Insert MVI56E MNETR Quick Start Guide If any of these components are missing please contact ProSoft Technology Support for replacement parts ProSoft Technology Inc Page 11 of 153 August 31 2009 MVISGE MNETR 4 ControlLogix Platform Start Here Modbus TCP IP Interface Module with Reduced Data Block 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 MVI56E MNETR jumper configuration SETUP S
9. Properties Alt Enter 6 Repeat steps 2 and 3 to add the second EtherNet IP module to the remote rack Page 28 of 153 ProSoft Technology Inc August 31 2009 Start Here MVI56E MNETR ControlLogix Platform User Manual Modbus TCP IP Interface Module with Reduced Data Block 1 11 2 Create the Module Remote Rack 1 Next select the remote 1756 BACKPLANE node in the Controller Organization pane underneath the remote rack EtherNet IP module you just created and click the right mouse button to open a shortcut menu On the shortcut menu choose NEW MODULE 1 0 Configuration 9 1756 Backplane 1756 A4 fa 0 1756 163 My Controller 1 1756 ENBT A Local ENET1 Ethernet 8 1756 ENBT A Local ENET1 8 1756 ENBT A Remote ENET2 11756 Backplane 1756 A17 2 Expand the OTHER modules selection and then select 1756 MODULE GENERIC 1756 MODULE Wil Select Module Module Analog Communications Controllers Digital Drives Motion Other 1756 MODULE Generic 1756 Module Allen Bradley Specialty Find Add Favorite By Category By Vendor Favorites Cancel ProSoft Technology Inc Page 29 of 153 August 31 2009 MVISGE MNETR ControlLogix Platform Start Here Modbus TCP IP Interface Module with Reduced Data Block User Manual 3 Set the Module Properties values as follows New Module Type 1756 MODULE Generi
10. 53 lt rR gt lt 0B gt lt 03 gt lt 04 gt lt 00 gt lt 00 gt lt 01 gt lt 85 gt lt 90 gt lt R gt 0B 03 02 00 00 20 45 lt R gt lt 0B gt lt 10 gt lt 04 gt lt 01 gt ELM ccu lt 01 gt lt 00 gt lt 01 gt lt D4 gt lt 50 gt lt R gt toa 1004 00 20 45 lt R gt lt 0B gt lt 10 gt lt 04 gt lt 02 gt lt 00 gt lt 01 gt lt 02 gt lt 00 gt lt 00 gt lt 9C gt lt D2 gt lt R gt 0B 10 04 02 00 01 41 93 lt R gt lt 0B gt lt 03 gt lt 04 gt lt 02 gt lt 00 gt 2 0 45 gt 8 lt gt 08 lt gt 10 lt gt 04 lt gt 03 lt gt 00 lt gt 01 lt gt 02 lt gt 00 lt lt 00 gt lt 9D gt lt 03 gt lt R gt 0B 10 04 03 00 01 FO 53 lt R gt lt 0B gt lt 03 gt lt 04 gt lt 03 gt lt 00 gt lt 01 gt lt 7 5 gt lt 90 gt lt R gt 0B 03 02 00 0C 20 45 lt R gt lt 0B gt lt 10 gt lt 04 gt lt 04 gt lt 00 gt lt 01 gt lt 02 gt lt 00 gt lt 00 gt lt 9C gt 08 lt gt lt 84 gt 10 04 04 0C 01 41 92 lt R gt lt 0B gt lt 03 gt lt 04 gt lt 04 gt lt 00 gt lt 01 gt lt C4 gt lt 51 gt lt R gt 03 02 00 00 20 45 lt R gt lt 0B gt lt 10 gt lt 04 gt lt 05 gt lt 00 gt lt 01 gt lt 02 gt lt 00 gt lt 00 gt lt 9D gt lt 65 gt lt R gt 08 10 04 05 00 01 1C 52 lt R gt lt 0B gt lt 03 gt lt 04 gt lt 05 gt lt 00 gt lt 01 gt lt 95 gt lt 91 gt lt R gt 0B 03 02 00 00 20 45 lt R gt lt 0
11. Character Definition Data enclosed in these characters represent data received on the port lt gt Data enclosed in these characters represent data transmitted on the port lt R gt These characters are inserted when the RTS line is driven high on the port lt R gt These characters are inserted when the RTS line is dropped low on the port lt CS gt These characters are displayed when the CTS line is recognized high _TT_ These characters are displayed when the Time Tick is set to any value other than No Ticks Page 94 of 153 ProSoft Technology Inc August 31 2009 Diagnostics and Troubleshooting MVI56E MNETR ControlLogix Platform User Manual Modbus TCP IP Interface Module with Reduced Data Block 4 8 3 Stopping the Data Analyzer cope Click to stop Data Analyzer Important When in analyzer mode program execution will slow down Only use this tool during a troubleshooting session Before disconnecting from the Config Debug port please stop the data analyzer This action will allow the module to resume its normal high speed operating mode 4 8 4 Data Analyzer Tips For most applications HEX is the best format to view the data and this does include ASCII based messages because some characters will not display in the Diagnostics window and by capturing the data in HEX we can figure out what the corresponding ASCII characters are supposed to be The Tick value is a timing mark The
12. 20 MNET Request Count This counter increments each time a MNET port 2000 request is received 21 MNET Response This counter is incremented each time a MNET port 2000 Count response message is sent 22 Reserved Not Used 23 Reserved Not Used 24 Reserved Not Used 25 Reserved Not Used 26 Reserved Not Used 27 Reserved Not Used 28 Reserved Not Used 29 Reserved Not Used ProSoft Technology Inc August 31 2009 Page 119 of 153 MVI56E MNETR ControlLogix Platform Reference Modbus TCP IP Interface Module with Reduced Data Block User Manual Offset Content Description 30 MBAP Request Count This counter increments each time a MBAP port 502 request is received 31 MBAP Response This counter is incremented each time a MBAP port 502 Count response message is sent 32 Reserved Not Used 33 Reserved Not Used 34 Reserved Not Used 36 Reserved Not Used 36 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 Client Request Count This value is incremented each time a request message is issued 243 Client Response Count This value is incremented each time a response messag
13. ControlLogix Platform User Manual Modbus TCP IP Interface Module with Reduced Data Block 1 8 1 ClPconnect You can use ClPconnect to connect a PC to the MVIS6E MNETR module over Ethernet using Rockwell Automation s 1756 ENBT EtherNet IP module This allows you to configure the MVIS6E MNETR 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 slot number of the MVIBG6E MNETR in the destination ControlLogix chassis the last ENBT CNBx and chassis in the path To use ClPconnect follow these steps 1 Inthe SET 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 v Ethernet eo ProSoft Discovery Service PDS CiPconnect 192 158 0 100 1 0 CIP Path Edit Test Connection Cancel ProSoft Technology Inc Page 21 of 153 August 31 2009 MVISGE MNETR ControlLogix Platform Start Here Modbus TCP IP Interface Module with Reduced Data Block User Manual 2 Click CIP PATH EDIT to open the CIPCONNECT PATH EDITOR dialog box CIPconnect Path Editor E Conn
14. Float afa MNET CLIENT 0 Command List Command Status Lg Config 9 Status Eaa MNET SERVER Contig Status 5 85 MODULE Config NIC Status Static ARP Version Path Ethemet 105 102 0 25 Time 12 49 33 03 FC 00 01 C1 17 lt R gt lt 0B gt lt 03 gt lt 03 gt lt FC gt lt 00 gt lt 01 gt lt 44 gt lt D4 gt lt R gt 0B 03 02 00 00 20 45 lt R gt lt 0B gt lt 10 gt lt 03 gt lt FD gt lt 00 gt lt 01 gt lt 02 gt lt 00 gt lt 00 gt lt FE gt lt 1D gt lt R gt 0B 10 03 FD 00 01 90 D7 lt R gt lt 0B gt lt 03 gt lt 03 gt lt FD gt lt 00 gt lt 01 gt lt 15 gt lt 14 gt lt R gt 0B 03 02 00 00 20 45 lt R gt lt 0B gt lt 10 gt lt 03 gt lt FE gt lt 00 gt lt 01 gt lt 02 gt lt 00 gt lt 00 gt lt FE gt lt 2E gt lt R gt 0B 10 03 FE 00 01 60 07 lt R gt lt 0B gt lt 03 gt lt 03 gt lt FE gt lt 00 gt lt 01 gt lt E 5 gt lt 14 gt lt R gt 0B 03 02 00 00 20 45 lt R gt lt 0B gt lt 10 gt lt 03 gt lt FF gt lt 00 gt lt 01 gt lt 02 gt lt 00 gt lt 00 gt lt FF gt lt FF gt lt R gt 0B 10 03 FF 00 01 31 17 lt R gt lt 0B gt lt 03 gt lt 03 gt lt FF gt lt 00 gt lt 01 gt lt B4 gt lt D4 gt lt R gt 0B 03 02 00 00 20 45 lt R gt lt 0B gt lt 10 gt lt 04 gt lt 00 gt lt 00 gt lt 01 gt lt 02 gt lt 00 gt lt 0C gt lt 9D gt lt 30 gt lt R gt 0B 10 04 00 00 01 00
15. For example if a value of 7000 is entered all requests for registers 7000 and above will be considered as floating point data Float Offset 0 to 9999 This parameter defines the start register for floating point data in the internal database This parameter is used only if the Float Flag is enabled For example if the Float Offset value is set to 3000 and the float start parameter is set to 7000 data requests for register 7000 will use the internal Modbus register 3000 ARP Timeout 1 to 60 This parameter specifies the number of seconds to wait for an ARP reply after a request is issued 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 O there will be no delay Page 56 of 153 ProSoft Technology Inc August 31 2009 Configuring the MVI56E MNETR Module MVI56E MNETR ControlLogix Platform User Manual Modbus TCP IP Interface Module with Reduced Data Block 2 1 5 MNET Client 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
16. 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 3 6 or 16 4X range for 40001 specify a value of 0 40001 40001 0 For01101 11101 31101 or 41101 specify a value of 1100 01101 00001 1100 11101 10001 2 1100 31101 30001 1100 41101 40001 1100 Note If the documentation for a particular Modbus slave 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 Page 62 of 153 ProSoft Technology Inc August 31 2009 Configuring the MVI56E MNETR Module MVI56E MNETR ControlLogix Platform User Manual Modbus TCP IP Interface Module with Reduced Data Block 2 1 6 MNET Servers This section contains database offset information used by the servers 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 2000 Output Offset 0 Bit Input Offset 0 Holding Register Offset
17. STEP 2 Transfer File s DOWNLOAD Abort Test Connection Cancel ProSoft Technology Inc Page 73 of 153 August 31 2009 MVI56E MNETR ControlLogix Platform Modbus TCP IP Interface Module with Reduced Data Block Configuring the MVIS6E MNETR Module User Manual 2 3 2 Example 2 Remote Rack Application For this example the MVIS6E MNETR module is located a remote rack accessible through ControlNet as shown in the following illustration 1756 ENBT 1756 CNB Ethernet ControlNet 1756 CNB MVIS6E 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 MNETR Page 74 of 153 ProSoft Technology Inc August 31 2009 MVI56E MNETR ControlLogix Platform Configuring the MVIS6E MNETR Module Modbus TCP IP Interface Module with Reduced Data Block User Manual 1 Inthe Download window click CIP PATH EDIT Download files from PC to module STEP 1 Select Communication Path Select Connection Type 1756 ENBT Ethernet ClPconnect t 192 168 0 100 p 1 s 0 CIP Path Edit STEP 2 Transfer File s DOWNLOAD Test Connection Cancel 2 Configure the path as shown in the following illustra
18. The following table describes the structure of this object Name Data Type Description CmdReq INT Total number of command list requests sent CmdResp INT Total number of command list responses received CmdErr INT Total number of command list errors Requests INT Total number of requests for port Responses INT Total number of responses for port ErrSent INT Total number of errors sent ErrRec INT Total number of errors received CfgErrWord INT Configuration Error Word CurErr INT Current Error code LastErr INT Last recorded error code Refer to MVIS6E MNETR Status Data Definition for a complete listing of the data stored in the status object 3 1 3 MNETRCONTROL Contains the data structure required for the processor to request special tasks from the module The command control task allows the processor to dynamically enable commands configured in the port command list The event command task allows the processor to dynamically build any commands to be sent by the MNET Client to a remote Server The following table describes the structure of this object Name Data Type Description BootTimer TIMER Timer to clear warmboot and coldboot WarmBoot BOOL Triggers a Cold Boot Command ColdBoot BOOL Triggers a Warm Boot Command ProSoft Technology Inc Page 81 of 153 August 31 2009 MVI56E MNETR ControlLogix Platform Ladder Logic Modbus TCP IP Interface Module with Reduce
19. gt Monitoring Database Information en 91 Monitoring MNET Client Information 92 Monitoring MNET Server Information 93 Data 93 gt EED Status Indicalors cr cce tte n e 97 The module provides information on diagnostics and troubleshooting in the following forms Status data values are transferred from the module to the processor Data contained in the module can be viewed in ProSoft Configuration Builder through the Ethernet port LED status indicators on the front of the module provide information on the module s status 4 1 Reading Status Data from the Module The MVI56E MNETR module returns a 47 word Status Data block page 119 that can be used to determine the module s operating status This data is located in the module s database at a user set location This data is transferred to the ControlLogix processor continuously The Configuration Debug port provides the following functionality Full view of the module s configuration data View of the module s status data Complete display of the module s internal database registers 0 to 4999 Version Information Control over the module warm boot cold boot transfer configuration Facility to upload and download the module s configuration file ProSoft Technology Inc Page 85 of 153 August 31 2009 MVI56E MNETR ControlLogix Platform Diagnostics and Troubl
20. the configuration contains a valid parameter set all the bits in the configuration word will be clear This does not indicate that the configuration is valid for the user application Make sure each parameter is set correctly for the specific application 4 9 2 Ethernet LED Indicators LED State Description Data Off No activity on the Ethernet port Green Flash The Ethernet port is actively transmitting or receiving data Link Off No physical network connection is detected No Ethernet communication is possible Check wiring and cables Green Solid Physical network connection detected This LED must be on solid for Ethernet communication to be possible 4 9 3 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 1 Turn off power to the rack 2 Remove the card from the rack 3 Verify that all jumpers are set correctly 4 Ifthe module requires a Compact Flash card verify that the card is installed correctly Re insert the card in the rack and turn the power back on Verity the configuration data being transferred to the module from the ControlLogix processor oo 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 S
21. 1 08282789 034 0 000000005 000 0 00000000E 000 0 00000000E 000 0 00000000E 000 0 00000000E 000 0 000000005 000 0 00000000E 000 0 00000000E 000 0 00000000E 000 0 000000005 000 0 00000000E 000 0 0 0 00000000E 000 0 00000000 000 0 00000000E 000 0 00000000E 000 0 00000000 000 0 00000000E 000 0 00000000E 000 0 00000000E 000 0 00000000 000 0 00000000E 000 0 000000005 000 0 0 000000005 000 0 000000005 000 0 00000000 000 0 0 Hexadecimal DATABASE DISPLAY 0 to 99 HEXADECIMAL Use the scroll bar on the right edge of the window to view each page 100 words of data ProSoft Technology Inc August 31 2009 Page 91 of 153 MVIS56E MNETR ControlLogix Platform Diagnostics and Troubleshooting Modbus TCP IP Interface Module with Reduced Data Block User Manual 4 6 Monitoring MNET Client Information Use the MNET CLIENT INFORMATION menu to view the configuration and status information for the MNET Client 4 6 1 Command List Use the COMMAND LIST menu to view the command list settings for MNET Client 0 The information on this menu corresponds with the settings in the MNET Client 0 Commands settings in ProSoft Configuration Builder page 57 Use the scroll bar on the right edge of the window to view each MNET Client command 4 6 2 Command Status Use the COMMAND STATUS menu to view MNET Client 0 Command status A zero indicates no error A non zero value indicates an error Refer to Error Codes for
22. 20 45 lt R gt lt 0B gt lt 10 gt lt 04 gt lt 0B gt 08 lt 00 lt gt 01 lt gt 02 lt gt 00 lt gt 00 lt gt 96 lt gt 48 lt gt 8 gt 10 04 0B 00 01 71 91 lt R gt lt 0B gt lt 03 gt lt 04 gt The lt R gt means that the module is transitioning the communications line to a transmit state All characters shown in lt gt brackets are characters being sent out by the module The lt R gt shows when the module is done transmitting data and is now ready to receive information back And finally all characters shown in the brackets is information being received from another device by the module After taking a minute or two of traffic capture stop the Data Analyzer zl Click to stop Data Analyzer Page 96 of 153 ProSoft Technology Inc August 31 2009 Diagnostics and Troubleshooting User Manual MVIS56E MNETR ControlLogix Platform Modbus TCP IP Interface Module with Reduced Data Block 4 9 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 Waiting for Processor Connection Module did not connect to processor during initialization Sample ladder logic or AOI is not loaded on processor Module is located in a d
23. 5 V DC 3mA 2 24V DC Operating Temperature 0 to 60 C 32 to 140 F Storage Temperature 40 to 85 C 40 to 185 F Shock 30g Operational 50g non operational Vibration 5 g from 10 to 150 Hz Relative Humidity 5 to 9596 non condensing All phase conductor sizes must be at least 1 3 mm squared and all earth ground conductors must be at least 4mm squared Markings ANSI ISA ISA 12 12 01 Class Division 2 GPs A B C D CSA cUL C22 2 No 213 M1987 CSA CB Certified IEC61010 ATEX EN60079 0 Category 3 Zone 2 EN60079 15 Ge rons 243333 E183151 CL Div 2 GP A B C D Temp Code T5 I3G Ex nA nL IIC T5 X 0 C lt Ta lt 60 C I Equipment intended for above ground use not for use in mines 3 Category 3 equipment investigated for normal operation only G Equipment protected against explosive gasses Battery Life Advisory The module uses a rechargeable Lithium Vanadium Pentoxide battery to backup the real time clock and CMOS settings The battery itself should last for the life of the module However if left in an unpowered state for 14 to 1 days the battery may become fully discharged and require recharging by being placed in a powered up ControlLogix chassis The time required to fully recharge the battery may be as long as 24hours Once it is fully charged the battery provides backup power for the CMOS setup and the real time clock for approximately 21 days Before you remove a module from i
24. Easily swap and upgrade products while benefiting from an array of new features designed to improve interoperability and enhance the user experience Web Page The web page allows access to manuals and other tools previously provided on a product CD ProSoft Configuration Builder PCB New Windows software for diagnostics connecting via the module s Ethernet port or 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 all MVI56E modules the network and to temporarily change the IP address to connect with the module s web page ClPconnect enabled Allows PC to module configuration and diagnostics from the Ethernet network through a ControlLogix 1756 ENBT EtherNet IP module Personality Card 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 English messages for status and alarm data and for processor and network communication status 1 2 System Requirements The MVI56E MNETR 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 MNETR mod
25. Entry Errors Code Description Too few parameters Invalid enable code Internal address gt maximum address Invalid node address lt 0 or gt 255 Count parameter set to 0 Invalid function code Invalid swap code ARP could not resolve MAC from IP bad IP address not part of a network invalid parameter to ARP routine Error during ARP operation the response to the ARP request did not arrive to the module after a user adjustable ARP Timeout Note When the client gets error 47 or 48 it uses the adjustable ARP Timeout 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 ProSoft Technology Inc Page 117 of 153 August 31 2009 MVI56E MNETR ControlLogix Platform Reference Modbus TCP IP Interface Module with Reduced Data Block User Manual 5 3 Ethernet Cable Specifications The recommended cable is Category 5 or better A Category 5 cable has four twisted pairs of wire which are color coded and cannot be swapped The module uses only two of the four pairs The Ethernet port on the module is Auto Sensing You can use either a standard Ethernet straight through cable or a crossover cable when connecting the module to an Ethernet hub a
26. IP Interface Module with Reduced Data Block 3 If PCB is still unable to connect to the module click the BROWSE DEVICE S button to open the PROSOFT DISCOVERY SERVICE Select the module then right click and choose SELECT FOR PCB 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 Close ProSoft Discovery Service and click the CONNECT button again 4 Ifall of these troubleshooting steps fail verify that the Ethernet cable is connected properly between your computer and the module either through a hub or switch using the grey cable or directly between your computer and the module using the red cable If you are still not able to establish a connection contact ProSoft Technology for assistance 4 3 Monitoring Module Information Use the MODULE menu to view configuration and hardware information for the MVI56E MNETR module s backplane and Ethernet application port 4 3 1 Version Use the VERSION menu to view module hardware and firmware information MVISGE MNETR gt MODULE gt version Product code Revision opsys Run Number IP Address MAC Address Program scan cnt BP Driver Version BP API Version 11 01 Module Name MVISG6E MNETR vendor ID 7309 Device Type 112 Product Code 75010 Serial Number 000003 BP Revision 12 01 slot UL The values on this menu corres
27. Inc August 31 2009 Configuring the MVI56E MNETR Module MVI56E MNETR ControlLogix Platform User Manual Modbus TCP IP Interface Module with Reduced Data Block Node IP Address The IP address of the device being addressed by the command Service Port 502 or other supported ports on server Use a value of 502 when addressing Modbus TCP IP servers that are compatible with the Schneider Electric MBAP specifications this will be most devices If a server implementation supports another service port enter the value here Slave Address 0 Broadcast to all nodes 1 to 255 Use this parameter to specify the slave address of a remote Modbus Serial device through a Modbus Ethernet to Serial converter Note Use the Node IP Address parameter page 61 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 slave device manufacturer to see if a particular slave can use addresses 248 255 If the value is set to zero the command will be a broadcast message on the network The Modbus protocol permits broadcast commands for write operations Do not use node address 0 for read operations Modbus Function 1 2 3 4 5 6 15 0r 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 sup
28. MainTask G C MainProgram Unscheduled Programs Motion Groups Ungrouped Axes Add On Instructions amp 3 Data Types 48 User Defined oe Strings oa Add On Defined Predefined Eg Module Defined Trends 1 0 Configuration acknlane ProSoft Technology Inc Page 141 of 153 August 31 2009 MVI56E MNETR ControlLogix Platform Reference Modbus TCP IP Interface Module with Reduced Data Block User Manual This action opens the SELECT MODULE dialog box E Select Module ule Analog Communications Controllers 9 Digital Drives Motion Other 1756 MODULE Generic 1756 Module Allen Bradley Specialty Find Add Favorite By Category Favorites Select the 1756 MODULE Generic 1756 Module from the list and click OK This action opens the NEW MODULE dialog box New Module Type 1756 MODULE Generic 1756 Module Parent Local Connection Parameters Assembly Instance Name Input Description Output EN Configuration Comm Format Data INT X Slot 1 Open Module Properties 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 over the backplane of the ControlLogix rack Click OK to continue Page 142 of 153 ProSoft Technology Inc August 31 2009 MVI56E MNETR ControlLogix Platform
29. Module with Reduced Data Block If there is no response from the module ProSoft Configuration Builder Cannot Connect to IP Address 1 Click the SET UP CONNECTION button to browse for the module s IP address zl mp Click to set up connection 2 On the CONNECTION SETUP dialog box click the TEST CONNECTION button to verify if the module is accessible with the current settings Connection Setup Select Connection NN Ethernet 192 168 0 250 ProSoft Discovery Service PDS Browse Device s ClPconnect Test Connection Cancel 3 If PCB is still unable to connect to the module click the BROWSE DEVICE S button to open the PROSOFT DISCOVERY SERVICE ProSoft Technology Inc Page 19 of 153 August 31 2009 MVISGE MNETR ControlLogix Platform Start Here Modbus TCP IP Interface Module with Reduced Data Block User Manual 4 Select the module then right click and choose ASSIGN TEMPORARY IP 4 Prosoft Discovery Service DAR 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 HA Assign Temporary IP Address DER Temporary IP 192 168 0 250 Network Mask 255 255 255 0 OK Cancel 6 Choose an unused IP within your subnet and then click OK Page 20 of 153 ProSoft Technology Inc August 31 2009 Start Here MVI56E MNETR
30. ReedEthernetMSG MNETRCONTRO WriteEthernetMSG WrteEthernetMSG METICATA ReadClockMSG ReadClockMSG WriteClockMSG WriteClockMSG MET ai rere atu MeTEreret MET MET Pass ru MNEXSTATUS End You will notice that new tags have been imported four MESSAGE tags MVIS6MNETRCLock and MVIS6MNETRETHERNET tags RSLogix 5000 MNETR 1756 L63 Controller Tags MNETR controller fe yes Seach Lege Communasons Toss Vidor Heb alsa amp AALl e vig AIS ZIP D Controle Fat ander MNETS teret oe ProSoft Technology Inc Page 135 of 153 August 31 2009 MVI56E MNETR ControlLogix Platform Reference Modbus TCP IP Interface Module with Reduced Data Block User Manual 4 1 Add On Instruction click the button next to each MSG tag to open the MESSAGE CONFIGURATION TAG 5 Click the COMMUNICATION tab and click the BROWSE button as follows Message Configuration ReadEthernetMSG Configuration Communication Tag Path Browse Enable Enable Waiting Start Done Done Length 0 Eror Code Extended Error Code Timed Out Eror Path Eror Text Cancel Help 6 Select the module to configure the message path Message Configuration ReadEthernetMSG Configuration Communication Tag Path MNETR MNETR lll Message Path Browser Path 11309 MNETR amp 1 0 Configuration 9 1756 Backp
31. Service amp Warranty Modbus TCP IP Interface Module with Reduced Data Block User Manual 6 3 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 included 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 00 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 3 7 Time Limit for Bringing Suit Any action for breach of warranty must be commenced within 39 months following shipment of the Product 6 3 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 mat
32. User Manual Modbus TCP IP Interface Module with Reduced Data Block 2 Edit the Module Properties 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 Wil Module Properties Local 1 1756 MODULE 1 1 General Connection Module Info Backplane Requested Packet Interval bo ms 0 2 750 0 ms Inhibit Module Major Fault On Controller Connection Fails While in Run Mode Module Fault Status Offline 3 Save the module Click OK to dismiss the dialog box The CONTROLLER ORGANIZATION window now displays the module s presence 65 Controller My Controller A Controller Tags Controller Fault Handler Power Up Handler 3 Tasks z a MainTask Cg MainProgram Unscheduled Programs amp Motion Groups Ungrouped Axes Add On Instructions e Data Types Cg User Defined Oa Strings Cg Add On Defined jh Predefined if Module Defined Z3 Trends Configuration 9 1756 Backplane 1756 A4 fa 0 1756 163 My_Controller 8 1 1756 MODULE Mv Copy the Controller Tags from the sample program Copy the User Defined Data Types from the sample program Copy the Ladder Rungs from the sample progr
33. 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 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 DataStartPtLo Data Of Pts Data Of PtsLo Error Check Field 11 01 00 13 00 25 CRC ProSoft Technology Inc Page 121 of 153 August 31 2009 MVI56E MNETR ControlLogix Platform Reference Modbus TCP IP Interface Module with Reduced Data Block Use
34. and choose NEW MODULE 3 6 Controller My Controller Controller Tags Controller Fault Handler Power Up Handler 5 3 Tasks fa MainTask C MainProgram Unscheduled Programs Motion Groups Z3 Ungrouped Axes Add On Instructions 3 Data Types gh User Defined oe Strings Cg Add On Defined Predefined Eg Module Defined Trends 1 0 Configuration T New Modde 2 Expand the COMMUNICATIONS module selections and then select the Ethernet Bridge module that matches your hardware This example uses a 1756 ENBT A module Select Module Description 1756 CNBR E 1756 ControlNet Bridge Redundant Media 1756 DHRIO B 1756 DH Bridge RIO Scanner 1756 DHRIO C 1756 DH Bridge RIO Scanner 1756 DHRIO D 1756 DH Bridge RIO Scanner 1756 DNB 1756 DeviceNet Scanner 1756 EN2F A 1756 10 100 Mbps Ethernet Bridge Fiber Media 1756 EN2T A 1756 10 100 Mbps Ethernet Bridge Twisted Pair Media 1756 ENBF A 1756 10 100 Mbps Ethernet Bridge Fiber Media len Bradley 1756 ENBT A 1756 10 100 Mbps Ethernet Bridge Twisted Pair Media Allen Bradley 1756 ENET A 1756 Ethernet Communication Interface Allen Bradley 1756 ENET B 1756 Ethernet Communication Interface Allen Bradley 1756 EWEB A 1756 10 100 Mbps Ethernet Bridge w Enhanced Web Serv Allen Bradley 1756 SYNCH A SynchLink Interface Allen Bradley gt Eind Add Favorite ley ey ien Bradley len Bradle
35. and ladder logic required to configure the MVI56E MNETR module RUNG IMPORT WITH UTILITY ADD ON INSTRUCTION OPTIONAL MVI56 E MNETR_Optional_AddOn_Rung_ lt version gt L5X which includes the data types and controller tags that allow you to update the IP address date and time on the module page 25 ProSoft Technology Inc Page 25 of 153 August 31 2009 MVI56E MNETR ControlLogix Platform Start Here Modbus TCP IP Interface Module with Reduced Data Block User Manual 1 11 Create a new RSLogix 5000 project 1 Open the FILE menu and then choose NEw f amp RSLogix 5000 XM Edit View Search Logic Communications Tools Wii B New Ctri N 0 7 o g 2 Select REVISION 16 New Controller Vendor Allen Bradley Type 175663 ControlLogi amp 5583 Controller Revision Cancel Redundancy Enabled Help Name My Controller Description Chassis Type 1756 4 4 Slot ControlLogix Chassis Y Slot gt Create In C RSLogix 5000 Projects Browse Note If you are installing the MVIBGE MNETR module in a remote rack follow these steps If you are installing the module in a local rack refer to Create the Module Local Rack page 31 Page 26 of 153 ProSoft Technology Inc August 31 2009 Start Here MVI56E MNETR ControlLogix Platform User Manual Modbus TCP IP Interface Module with Reduced Data Block 1 11 1 Create the Remote Network 1 Right click CONFIGURATION
36. command that has an error the module automatically sets the poll delay parameter to 30 seconds This instructs the module to wait 30 seconds until it attempts to issue the command again As the list is read in from the configuration file and as the commands are processed an error value is maintained in the module for each command This error list can be transferred to the processor The errors generated by the module are displayed in the following table Page 116 of 153 ProSoft Technology Inc August 31 2009 User Manual MVIS56E MNETR ControlLogix Platform Modbus TCP IP Interface Module with Reduced Data Block Standard Modbus Protocol Errors Code Description Illegal Function Illegal Data Address Illegal Data Value Failure in Associated Device Acknowledge AJO N Busy Rejected Message Module Communication Error Codes Code Description 1 CTS modem control line not set before transmit 2 Timeout while transmitting message 11 Timeout waiting for response after request 253 Incorrect slave address in response 254 Incorrect function code in response 255 Invalid CRC LRC value in response MNET Client Specific Errors Code Description Failed to connect to server specified in command MNET command response timeout TCP IP connection ended before session finished Command List
37. defined data type and controller tag For most applications the Import Rung with Add On Instruction will work without modification 3 1 MNETRModuleDef All data related to the MVIBGE MNETR is stored in a user defined data type An instance of the data type is required before the module can be used This is done by declaring a variable of the data type in the CONTROLLER TAGS EDIT TAGS dialog box The following table describes the structure of the object Name Data Type Description DATA MNETRDATA These objects hold data to be transferred between the processor and the MVI56E MNETR module STATUS MNETRSTATUS This object views the status of the module CONTROL MNETRCONTROL This object contains the data structure required for the processor to request special tasks from the module UTIL MNETRUTIL This data object stores the variables required for the data transfer between the processor and the module This object contains objects that define the configuration user data status and command control data related to the module Each of these object types is discussed in the following topics of the document ProSoft Technology Inc Page 79 of 153 August 31 2009 MVI56E MNETR ControlLogix Platform Ladder Logic Modbus TCP IP Interface Module with Reduced Data Block User Manual 3 1 1 MNETRDATA This object holds data to be transferred between the processor and the MVI56E MNETR module The user data is the read
38. 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 User logic like discrete and registers is not accessed by the diagnostics Certain functions can optionally reset error counters in the remote device A server device can however be forced into Listen Only Mode in which it will monitor the messages on the communications system but not respond to them This can affect the outcome of your application program if it depends upon any further exchange of data with the remote device Generally the mode is forced to remove a malfunctioning remote device from the communications system The following diagnostic functions are dedicated to serial line devices The normal response to the Return Query Data request is to loopback the same data The function code and sub function codes are also echoed Page 126 of 153 ProSoft Technology Inc August 31 2009 MVI56E MNETR 4 ControlLogix Platform User Manual Modbus TCP IP Inter
39. documentation is available for purchase Contact ProSoft Technology for pricing and availability North America 1 661 716 5100 Asia Pacific 603 7724 2080 Europe Middle East Africa 33 0 5 3436 87 20 Latin America 1 281 298 9109 Contents MVIS56E MNETR ControlLogix Platform User Manual Modbus TCP IP Interface Module with Reduced Data Block Contents Important Safety Information MVI56E 7 2 Battery Life Advis e a erra pe ta nae 3 Your Feedback Please elu i mite t e eel ed eu te a et e eee Ro eer ce nod 3 ProSoft Technology Product Documentation tette 3 Guide to the MVIS56E MNETR User Manual 7 1 Start Here 9 1 1 What s itr eet T tree etd d oed 10 1 2 System Requirements sessi e aaa aa oa tida nnns snnt enne 10 1 3 Package Contents ie tiated teet etd tete ai eet ee de 11 1 4 Setting J MperS ete A ee n te ete 12 1 5 Install the Module in the RaCk cor esiotsa anerer NEA b nennen nnns 12 1 6 7 14 1 7 Connect your PC to the Module sssssssssseeeeerennneeen enne 15 1 8 Set Temporary IP Address sess nen 15 1 9 Connect to the Module s Web Page sse 23 1 10 Upload the Add On Instruction from the 25 1 11 Create new RSLogix 5000
40. field The information field contains 1 byte 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 Page 124 of 153 ProSoft Technology Inc August 31 2009 MVIS56E MNETR ControlLogix Platform User Manual Modbus TCP IP Interface Module with Reduced Data Block 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 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
41. new Ethernet configuration in MVIBGEMNETRETHERNET CONFIG Move a value of 1 to MVIS6MNETRETHERNET WRITE MVIBBEMNETREthermet RT MVIBBEMNETREthemet Fiead 0 MVIS5GEMNE TRE themet Write L 4 MVIBBEMNETREthemet Config Pask MVIBBEMNETREthernet Config IP EE MVIBBEMNETREthemet Config IP U 105 MVIBBEMNETREthernet Config IP 1 102 MVIBBEMNETREthemet Config IP 2 0 MVIBBEMNETREthemet Config IP 3 32 MVISBEMNETRE Curifiu Nelinask Esae MVI5SSEMNE TREthermet Config Netmask 0 255 MVI56EMNETREthemet Config Netmask 1 255 MVI56EMNETRE thernet Config Netmask 2 255 MVISGEMNETRE thernet Config Netmask 3 0 MVI56EMNETREtheret Config Gateway P MVIBBEMNETREthemet Config G ateway U 192 MVIBBEMNETREthemet Config G ateway 1 168 MVIBBEMNETREthemet Config G ateway 2 0 MVIBBEMNETREthemet Config G ateway 3 1 Page 138 of 153 ProSoft Technology Inc August 31 2009 MVI56E MNETR ControlLogix Platform User Manual Modbus TCP IP Interface Module with Reduced Data Block After the message is executed the MVIS6MNETRETHERNET WRITE bit resets to 0 MVIBBEMNETREthemet MVISBEMNETREthemet Read MVISBEMNETREthemet Write MVIBBEMNETREthemet Config MVIBBEMNETREthemet Config IP MVIBBEMNETREthemet Config IP 0 MVIBBEMNETREthemet Config IP 1 MVIBBEMNETREthermet Config IP 2 MVIBBEMNETREthemet Config IP 3 MWVIGBEMNE TREU reir iet Curifiu
42. of 153 ProSoft Technology Inc August 31 2009 Start Here MVI56E MNETR ControlLogix Platform User Manual Modbus TCP IP Interface Module with Reduced Data Block Or in a Remote Rack application MNETR ACD 1756 163 MainProgram MainRoutine Edt Seach TM oss Window alsia xime Gig alc omno 7 P Bee 8 No forces 5 No Las Bew 4 a4 ate Controller My_Controller amp 4 For MVIS6 MNETR and MVIS6E MNETR modules f AOIS6MNETR Add On For MVIS6 MNETR and 5 AOIS6MNETR AOIS amp MNETR Connection Input Local 1 Data Connection Output Local 1 O Data MNETR MNETR Add On For MVI56 MNETR and MVIS6E MNETR modules IS6MNETR Add On For MVISG MNETR and MVISGE MNET AOISGMNETR AOISGMNETR 2 Connection Input Remote ENBT2 2 I Data Connecbon Output Remote ENBT2 2 0 Data MNETR MNETR 0 0 0 9 5 6 DOSTA Remote PT 57 Badge 1794 417 1796 087 Remote SST 0 9 9 5 78 Name Argument Value Description USP Enben 1 B00L Enable Input System Defined Parameter EnableDut 1 BooL Enable Output System Defined Parameter 10 Connection Input Remote_ENBT2 2 1 Data 3 INT 42 Input parameters Connection Output Remote ENBT2 2 0 Data tJ INT 42 17 MNETR MNETR C MNETRModuleDef Sort Parameters by Name The
43. of this object Name Data Type Description PassCnt INT Program cycle counter BlockStats MNETRBlockStats Status information for the data transfer operations between the processor and the module Reserved1 INT Reserved for future use Reserved2 INT Reserved for future use MNETReq INT The number of MNET Port 2000 requests received MNETResp INT The number of MNET Port 2000 responses sent MBAPReq INT The number of MBAP Port 502 requests received MBAPResp INT The number of MBAP Port 502 responses sent ClientStatus MNETRClientStats Client Status Data Page 80 of 153 ProSoft Technology Inc August 31 2009 Ladder Logic MVIS56E MNETR ControlLogix Platform User Manual Modbus TCP IP Interface Module with Reduced Data Block MNETRBlockStats This status object contains a structure that includes the status information for the data transfer operations between the processor and the module MNETRBLOCKSTATS The following table describes the structure of this object Name Data Type Description Read INT Total number of read block transfers Write INT Total number of write block transfers Parse INT Total number of blocks parsed Event INT Total number of event blocks received Cmd INT Total number of command blocks received Err INT Total number of block transfer errors MNETRClientStats The status object contains a structure for the MNET Client Status MNETRCLIENTSTATS
44. received data bytes are displayed Use of this feature is limited without a thorough understanding of the protocol 4 8 1 Configuring the Data Analyzer 5191915 MIT Click to configure Data Analyzer Select Timing Interval Time Ticks help you visualize how much data is transmitted on the port for a specified interval Select the interval to display or choose No Ticks to turn off timing marks Select the Communication Port to Analyze You can view incoming and outgoing data for one application port at a time Choose the application port to analyze Select the Data Format You can view incoming and outgoing data in Hexadecimal HEX or Alphanumeric ASCII format ProSoft Technology Inc Page 93 of 153 August 31 2009 MVI56E MNETR ControlLogix Platform Diagnostics and Troubleshooting Modbus TCP IP Interface Module with Reduced Data Block User Manual 4 8 2 Starting the Data Analyzer sal Click to start Data Analyzer The following illustration shows an example of the Data Analyzer output Li Diagnostics Connection Log Module 919191 MVISEE MNETR Time 12 49 33 aa BACKPLANE 03 Fc 00 01 C1 17 lt R gt lt 0B gt lt 03 gt lt 03 gt lt FC gt lt 00 gt lt 01 gt lt 44 gt lt D4 gt lt R gt 0B 03 02 00 Status 00 20 45 lt R gt lt 0B gt lt 10 gt lt 03 gt lt FD gt lt 00 gt lt 01 gt lt 02 gt lt 00 gt lt 00 gt lt FE gt lt 1D gt lt R gt 0B 10 03 FD
45. 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 Swap Code No Change Word Swap Word and Byte Swap Byte Swap 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 that do other manufacturers 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 This parameter can be set to rearrange the byte order of data received or sent into 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 Words amp Bytes The 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 Page 60 of 153 ProSoft Technology
46. setup procedure is now complete Save the project and download the application to your ControlLogix processor ProSoft Technology Inc Page 47 of 153 August 31 2009 MVISGE MNETR ControlLogix Platform Start Here Modbus TCP IP Interface Module with Reduced Data Block User Manual 1 11 7 Download 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 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 program to the processor A Download to the controller Name My_Controller Type 1756 L63 ControlLogix5563 Controller Path AB_DF1 1 Security None Cancel 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 If the keyswitch 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
47. specified in the Modbus protocol page 121 Each command list record has the same format The first part of the record contains the information relating to the MVIb6E MNETR 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 MVIBbGE MNETR module with Modbus TCP IP Server devices you must construct a command list The commands in the list specify the Server device to be addressed the function to be performed read or write the data area in the device to interface with and the registers in the internal database to be associated with the device data The Client command list supports up to 100 commands The command list is processed from top command 0 to bottom A poll interval parameter is associated with each command to specify a minimum delay time in tenths of a second between the issuance of a command If the user specifies a value of 10 for the parameter the command will be executed no more frequently than every 1 second 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 networ
48. the destination MVI56E module is located Page 22 of 153 ProSoft Technology Inc August 31 2009 Start Here User Manual MVI56E MNETR ControlLogix Platform Modbus TCP IP Interface Module with Reduced Data Block To use the ClPconnect Path Editor follow these steps 1 Configure the path between the 1756 ENBT connected to your PC and the MVI56E MNETR module o If the 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 1 9 Connect to the Module s Web Page 1 In ProSoft Discovery Service select the module to configure and then click the right mouse button to open a shortcut menu 2 Onthe shortcut menu choose VIEW MODULE S WEBPAGE JA Prosoft Discovery Service Assign Temporary IP Device Details Remove Temporary IP View module s webpage Select for Click the search icon to begin the browse ProSoft Technology Inc Page 23 of 153 August 31 2009 MVISGE MNETR ControlLogix Platform Start Here Modbus TCP IP Interface Module with Reduced Data Block User Manual The web page contains the product documentation and sample programs All manuals and configuration tools are available from the module s web page epe Modbus TCP IP Mod
49. to 40 Spare 39 41 5001 to 5006 1 Warm Boot 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 The following table describes the format of the control block Offset Description Length 0 9998 1 1 to 41 Spare 41 Page 110 of 153 ProSoft Technology Inc August 31 2009 MVIS56E MNETR ControlLogix Platform User Manual Modbus TCP IP Interface Module with Reduced Data Block Cold Boot 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 The following table describes the format of the control block Offset Description Length 0 9999 1 1 to 41 Spare 41 Pass Through Control Blocks If the module is set for pass through operation by placing a value of 1 to 3 in the configuration file parameter Pass Through Mode the module will send special blocks to the module when a write request is received from a client Any Modbus function 5 6 15 or 16 commands will be passed from the server to the processor using this block identification numbers 9956 to 9961 9970 and 9996 Ladder logic must handle the receipt of these blocks and to place the enclosed data into the prop
50. using this feature Two data objects are required for this mode a variable to hold the length of the message and a buffer to hold the message This information is passed from the module to the processor using a block identification code of 9996 if the unformatted pass through mode code 1 is selected as the pass through mode in the configuration file Word one 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 The Modbus protocol supports control of binary output coils functions 5 and 15 and registers functions 6 and 16 Additionally formatted message blocks can be sent from the module to the processor when the pass through option is selected using the format selection codes 2 or 3 in the MNET CFG file These blocks require less decoding than the unformatted blocks Refer to the user manual for a full discussion on utilizing the pass through option in an application The following table describes the structure of this object Name Data Type Description MBControl1 CONTROL Reserved MBControl2 CONTROL Reserved MBMsg SINT 500 The Modbus message received MBScratch INT 3 Reserved MBOffsetBit INT The starting bit address for the Modbus data set ProSoft Technology Inc Page 83 of 153 August 31 2009 MVIS56E MNETR ControlLogix Platform Ladder Logic Modbu
51. 10 100 Base T Ethernet switch or directly to a PC The module will detect the cable type and use the appropriate pins to send and receive Ethernet signals Ethernet cabling is like U S telephone cables except that it has eight conductors Some hubs have one input that can accept either a straight through or crossover cable depending on a switch position In this case you must ensure that the switch position and cable type agree Refer to Ethernet cable configuration page 118 for a diagram of how to configure Ethernet cable 5 83 1 Ethernet Cable Configuration Note The standard connector view shown is color coded for a straight through cable Crossover cable Pin 1 Straight through cable RJ 45 PIN RJ 45 PIN RJ 45 PIN 45 PIN 1 Rx 3 Tx 1 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 5 5 3 2 Ethernet Performance MVI56E Modules Ethernet performance on the MVIS56E MNETR module can affect the operation of the MNETR application ports in the following ways Accessing the web interface refresh the page download files etc may impact MNETR performance High Ethernet traffic may impact MNETR performance consider ClPconnect page 68 for these applications and disconnect the module Ethernet port from the network Page 118 of 153 ProSoft Technology Inc August 31 2009 User Manual MVIS56E MNETR ControlLogix Platform Modbus TC
52. 4 Important Safety Information MVIS56E Modules 2 Initialize Output Data 54 107 Install ProSoft Configuration Builder 4 Install the Configuration Tools 14 Install the Module in the Rack 12 Installing the Rung Import with Utility Add On Instruction 133 Intellectual Property Indemnity 9 Internal Address 59 IP Address 65 L Ladder Logic 79 LED Status Indicators 97 Limitation of Remedies 0 LIMITED WARRANTY 147 MB Address in Device 62 Minimum Command Delay 55 MNET Client Specific Errors 7 MNETRBlockStats 81 MNETRClientStats 81 MNETRCmdControl 82 MNETROoilArray 84 MNETRCONTROL 81 MNETRDATA 80 MNETREventCmd 82 MNETRModuleDef 9 MNETRPassThru 83 MNETRSTATUS 80 MNETRUTIL 84 Modbus Exception Codes 131 Modbus Exception Responses 129 Modbus Function 61 Modbus Message Data 84 Modbus Protocol Specification 57 121 Module Communication Error Codes 117 Module Power Up 103 Monitoring Backplane Information 90 Monitoring Database Information 91 Monitoring MNET Client Information 92 Monitoring MNET Server Information 93 Monitoring Module Information 89 MVI56E MNETR Client Status 6 MVI56E MNETR Status Data Definition 85 90 119 N NIC Status 0 No Other Warranties 0 Node IP Address 61 Normal Data Transfer 6 Output Offset 64 Overview 132 P Package Contents 11 Pass Through Control Blo
53. 7 00 01 90 D7 lt R gt lt 0B gt lt 03 gt lt 03 gt lt FD gt lt 00 gt lt 01 gt lt 15 gt lt 14 gt lt R gt 0B 03 02 00 00 20 DATABASE 45 lt R gt lt 0B gt lt 10 gt lt 03 gt lt FE gt lt 00 gt lt 01 gt lt 02 gt lt 00 gt lt 00 gt lt FE gt lt 2E gt lt R gt 0B 10 03 FE 00 01 ASCII 60 D7 lt R gt lt 0B gt lt 03 gt lt 03 gt lt FE gt lt 00 gt lt 01 gt lt E 5 gt lt 14 gt lt R gt 0B 03 02 00 00 20 45 lt R gt Decimal lt 0B gt lt 10 gt lt 03 gt lt FF gt lt 00 gt lt 01 gt lt 02 gt lt 00 gt lt 00 gt lt FF gt lt FF gt lt R gt 0B 10 03 FF 00 01 31 17 Float lt R gt lt 0B gt lt 03 gt lt 03 gt lt FF gt lt 00 gt lt 01 gt lt B4 gt lt D4 gt lt R gt 0B 03 02 00 00 20 45 lt R gt lt 0B gt lt 10 gt zi lt 04 gt lt 00 gt lt 00 gt lt 01 gt lt 02 gt lt 00 gt lt 00 gt lt 9D gt lt 30 gt lt R gt 0B 10 04 00 00 01 00 53 lt R gt lt 0B gt Hex lt 03 gt lt 04 gt lt 00 gt lt 00 gt lt 01 gt lt 85 gt lt 9C gt lt R gt 0B 03 02 00 00 20 45 lt R gt lt 0B gt lt 10 gt lt 04 gt lt 01 gt MNET CLIENT 0 lt 00 gt lt 01 gt lt 02 gt lt 00 gt lt 00 gt lt 9C gt lt E1 gt lt R gt 0B 10 04 o1 00 01 51 93 lt R gt lt 0B gt lt 03 gt lt 04 gt Command List lt 01 gt lt 00 gt lt 01 gt lt D4 gt lt 50 gt lt R gt 0B 03 02 00 00 20 45 lt R gt lt 0B gt l
54. 756 MODULE Generic 1756 Module Allen Bradley Specialty Add Favorite By Category By Vendor Favorites Cancel 2 Select the 1756 MODULE GENERIC 1756 MODULE from the list and click OK This action opens the NEW MODULE dialog box New Module Type 1756 MODULE Generic 1756 Module Parent Flemote 2 Connection Parameters Assembly Instance Size Name MNETR Input 42 zi 16 bit Description Output 42 zi 16 bit Configuration 4 p 8 bit Comm Format Daua NT Slot hou Open Module Properties Cancel Help 3 Set the Module Properties values as follows Parameter Value Name Enter a module identification string The recommended value is MNETR Description Enter a description for the module Example Modbus TCP IP Interface Module with Reduced Data Block Comm Format Select DATA INT Very Important Slot Enter the slot number in the rack where the MVIS6E MNETR module is to be installed Input Assembly Instance 1 Input Size 42 Output Assembly Instance 2 Page 32 of 153 ProSoft Technology Inc August 31 2009 Start Here MVI56E MNETR ControlLogix Platform User Manual Modbus TCP IP Interface Module with Reduced Data Block Parameter Value Output Size 42 Configuration Assembly Instance 4 Configuration Size 0 4 On the CONNECTION tab set the RPI value for your project Five 5 milliseconds i
55. 756 MODULE INT 84Bytes O 0 8 x Locat2 C AB 1756 MODULE C 0 AB 1756 MODULE 0 AB 1756 MODULE 0 Controller Program Show Show All Import Configuration Tags Data Types Add On Instructions AOISEMNETR Use Existing 756 MOD Discard AB1 756 MOD Use Existing 8 F Local 1 0 AB 1756_MODULE_INT_84Bytes 0 0 g Local 2 C AB 1756_MODULE C 0 f x Locat2 l AB 1756 MODULE 0 AB 1756_MODULE_INT_84Bytes 0 0 5 F MNETR MNETRModuleDef Controller Program Show Show All Page 44 of 153 ProSoft Technology Inc August 31 2009 Start Here User Manual MVI56E MNETR ControlLogix Platform Modbus TCP IP Interface Module with Reduced Data Block Change the default tags MNETR and AOIS6MNETR to avoid conflict with existing tags This procedure will append the string Import Configuration Tags Data Types Add On Instructions ADIBBMNETR 2 Local 2 l Local 2 ADISBMNETR 1756 MOD 1756 MOD 2 as follows Create New Discard Discard MNETRModul Or in a Remote Rack application Import Configuration Tags Data Types Add On Instructions ADISEMNETR 2 Create New Name AinsFor_ Data Type Remote ENBT221 8 FEj Remote ENBT2 1 1 8 Remote_ENBT2 1 0 5 Remote_ENBT22 0 Controller Program Show Show All Import Configuration Tags Data Types Add On Instructions ADISBMN
56. Address Preset Write Register Seconds Count Address Multiple Register 4x The first part of the record is the module Information which relates to the MVI56E module and the second part contains information required to interface to the Server device Page 58 of 153 ProSoft Technology Inc August 31 2009 Configuring the MVI56E MNETR Module MVI56E MNETR ControlLogix Platform User Manual Modbus TCP IP Interface Module with Reduced Data Block Command list example Edit MNet Client 0 Commands Enable Intemal amp ddress Pollinterval Reg Count SwapCode NodelP Address Serv Port Slave Addr ModBus Function 4 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 OK Cancel Enable Yes No or Conditional This field defines whether the command is to be executed and under what conditions Value Description 0 The command is disabled and will not be executed in the normal polling sequence 1 The command is executed each scan of the command list if the Poll Interval Time is set to zero If the Poll Interval time is set the command will be executed when the interval timer expires 2 The command will execute only if the internal data associated with the command changes This value is v
57. B gt lt 10 gt lt 04 gt lt 06 gt lt 00 gt lt 01 gt lt 02 gt lt 00 gt lt 00 gt lt 9D gt lt 56 gt lt R gt 0B 10 04 06 00 01 E0 52 lt R gt lt 0B gt lt 03 gt lt 04 gt lt 06 gt lt 00 gt lt 01 gt lt 65 gt lt 91 gt lt R gt 0B 03 02 00 00 20 45 lt R gt lt 0B gt lt 10 gt lt 04 gt lt 07 gt lt 00 gt lt 01 gt lt 02 gt lt 00 gt lt 00 gt lt 9C gt lt 87 gt lt R gt 0B 10 04 07 00 01 B1 92 lt R gt lt 0B gt lt 03 gt lt 04 gt lt 07 gt lt 00 gt lt 01 gt lt 34 gt lt 51 gt lt R gt 0B 03 02 00 00 20 45 lt R gt lt 0B gt lt 10 gt lt 04 gt lt 08 gt lt 00 gt lt 01 gt lt 02 gt lt 00 gt lt 00 gt lt 9C gt lt 78 gt lt R gt 0B 10 04 08 00 01 81 91 lt R gt lt 0B gt lt 03 gt lt 04 gt lt 08 gt lt 00 gt lt 01 gt lt 04 gt lt 52 gt lt R gt 0B 03 02 00 00 20 45 R lt 0B gt lt 10 gt lt 04 gt lt 09 gt lt 00 gt lt 01 gt lt 02 gt lt 00 gt lt 00 gt lt 9D gt lt A9 gt lt R gt 0B 10 04 09 00 01 D0 51 lt R gt lt 0B gt lt 03 gt lt 04 gt lt 09 gt lt 00 gt lt 01 gt lt 55 gt lt 92 gt lt R gt 0B 03 02 00 00 20 45 lt R gt lt 0B gt lt 10 gt lt 04 gt lt 0A gt lt 00 gt lt 01 gt lt 02 gt lt 00 gt lt 00 gt lt 9D gt lt 9A gt lt R gt 0B 10 04 0A 00 01 20 51 lt R gt lt 0B gt lt 03 gt lt 04 gt lt 0A gt lt 00 gt lt 01 gt lt A5 gt lt 92 gt lt R gt 0B 03 02 00 00
58. 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 If the server does not receive the request due to a communication error no response is returned The Client program will eventually process a timeout condition for the request ProSoft Technology Inc Page 129 of 153 August 31 2009 MVI56E MNETR ControlLogix Platform Reference Modbus TCP IP Interface Module with Reduced Data Block User Manual 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 If the server receives the request without a communication error but cannot handle it for example if the request is to read a non existent output or register the server will return an exception response informing the Client of the nature of the error The exception response message has two fields that differentiate it from a normal response Function Code Field In a normal response the server echoes the function code of the original request in the function code field of the response All function codes have a most significant bit MSB of 0 their values are all below 80 hexadecimal In an exception response t
59. Data Block User Manual 6 2 Return Material Authorization RMA Policies and Conditions The following RMA Policies and Conditions collectively RMA Policies apply to any returned Product These RMA Policies are subject to change by ProSoft without notice For warranty information see Limited Warranty In the event of any inconsistency between the RMA Policies and the Warranty the Warranty shall govern 6 2 1 All Product Returns a In order to return a Product for repair exchange or otherwise the Customer must obtain a Returned Material Authorization RMA number from ProSoft and comply with ProSoft 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 145 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 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 using a ship
60. ETR 2 AB 1756 MODULE INT 84 0 AB 1756 MODULE INT 84Bytes O 0 AB 1756_MODULE C 0 1756 MODULE INT 84Bytes L0 AB 1756 MODULE INT 84Bytes 0 0 AOISBMNETR Use Existing Discard Use Existing Remote ENBT2 2 I 48 1756 MOD Discard Remote ENBT2 2 0 gt AB 1 756_MOD Discard fJ Remote_ENBT2 1 1 8 6065 0 8 Remote ENBT2 2 C fJ zE Remote ENBT2 2 1 Remote ENBT2 2 0 Controller Program Show Show All AB 1756_MODULE_INT_84Bytes 0 AB 1756_MODULE_INT_84Bytes 0 0 AB 1756_MODULE C 0 AB 1756_MODULE_INT_84Bytes 0 AB 1756 MODULE INT 84Bytes 0 0 ProSoft Technology Inc August 31 2009 Page 45 of 153 MVI56E MNETR ControlLogix Platform Start Here Modbus TCP IP Interface Module with Reduced Data Block User Manual 11 Click OK to confirm alal gt a xila F 597 f 1 BAT No Ets lew 4 sepe op o Rasra a4 b fortes 4 HE w lalele Agd On For MVIS6 MNETR and MVIS6E MNETR modules AOI56MNE TR Add On MVIS6 MNETR and MVIS AOIS6MNETR AOIS6MNETR _ Connection Input Locat 11 Data Connection Output Local 1 0 Data MNETR Add On For MVISO MNETR and 5 T AOISGMNETR AOIS6MNETR 2 1756463 Controler Connection Input Local 2 I Data gium Connecthon Output Local 2 0 Data MNETR MNETR 2 Page 46
61. ETUP SHUNT 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 1 5 Install 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 MVIBbGE MNETR module Refer to your Rockwell Automation product documentation for installation instructions Warning You must follow all safety instructions when installing this or any other electronic devices Failure to follow safety procedures could result in damage to hardware or data or even serious injury or death to personnel Refer to the documentation for each device you plan to connect to verify that suitable safety procedures are in place before installing or servicing the device After you have checked the placement of the jumpers insert the MVI56E MNETR 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 Page 12 of 153 ProSoft Technology Inc August 31 2009 Start Here MVI56E MNETR ControlLogix Platform User Manual Modbus TCP IP Interface Module with Reduced Data Block Warni
62. I56E MNETR ControlLogix Platform User Manual Modbus TCP IP Interface Module with Reduced Data Block Your first task is to add the MVIS6E MNETR 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 2 Onthe shortcut menu choose 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 MVIS6 C MVI71 C PLXS000 C PTQ C MVI6S MVIS6E C MVIS4 Search Module Type STEP 1 Select Module Type Module Definition zi MVIS6E GSC MVIS6E MCM MVIS6E MCMR MVIS6E MNETR Action Required 3 In the PRODUCT LINE FILTER area of the dialog box select MVI56E In the SELECT MODULE TYPE dropdown list select MVIBbGE MNETR and then click OK to save your settings and return to the ProSoft Configuration Builder window ProSoft Technology Inc Page 51 of 153 August 31 2009 MVI56E MNETR ControlLogix Platform Configuring the MVI56E MNETR Module Modbus TCP IP Interface Module with Reduced Data Block User Manual 2 1 2 Set Module Parameters The next task is to configure module parameters Notice that the contents of the information pane and the configuration pane changed when you added the MVI56E MNETR module to the project Untitled ppf ProSoft Configuration Builder DER File View Project Tools Help Default Project N
63. Interface Module with Reduced Data Block User Manual 1 11 6 Adding Multiple Modules Optional Important If your application requires more than one MVI56 MNETR module into the same project follow the steps below 1 Inthe O Configuration folder click the right mouse button to open a shortcut menu and then choose NEW MODULE 3 6 1 0 Configuration ll EEE new modue a 0 17564 B 1 17564 Festi 2 Select 1756 MODULE Wil Select Module Modue Analog Communications Controllers 9 Digital Drives Motion Other 1756 MODULE Generic 1756 Module Allen Bradley Specialty Eind Add Favorite By Category Favorites OK Cancel Help This action opens the New Module dialog box New Module Type 1756 MODULE Generic 1756 Module Parent Local Connection Parameters Name MNETR_2 Input 1 42 16 bit Description Dutput 42 16 bit Configuration 4 0 a 8 bit Comm Format Data INT Slot 2 zi Open Module Properties Cancel Help Page 40 of 153 ProSoft Technology Inc August 31 2009 Start Here User Manual MVI56E MNETR ControlLogix Platform Modbus TCP IP Interface Module with Reduced Data Block 3 Fill in the module properties as follows Parameter Value Name Enter a module identification string Example MNETR 2 Description Enter a description for the module Example Modbus TCP IP Interface Module with Reduced Dat
64. MVIS6E MNETR Action Required 5 In the PRODUCT LINE FILTER area of the dialog box select MVI56E In the SELECT MODULE TYPE dropdown list select MVIS6E MNETR and then click OK to save your settings and return to the ProSoft Configuration Builder window 6 Right click over the module icon g Default Project Default Location Es ProSoft Technology Inc Page 17 of 153 August 31 2009 MVISGE MNETR ControlLogix Platform Start Here Modbus TCP IP Interface Module with Reduced Data Block User Manual 7 Onthe shortcut menu choose DIAGNOSTICS Default Project Default Location h 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 EI L This action opens the DIAGNOSTICS dialog box Diagnostics Connection Log Module asl olclale aly MVIBBE MNETR Time 17 44 59 5 48 MODULE Select item within MVISG6E MNETR for diagnostic information Version Config NIC Status Static ARP BACKPLANE Status 5285 MNET CLIENT 0 Config Status Command List Command Status 5 58 MNET SERVER Config Status 8 DATABASE ASCII Decimal Hex Float Path ClPconnect t 105 102 0 65 p 1 s 5 Page 18 of 153 ProSoft Technology Inc August 31 2009 Start Here MVI56E MNETR ControlLogix Platform User Manual Modbus TCP IP Interface
65. NETRClock Config D ay 4 MVIBBEMNETRClock Config Hour 15 MVIS56EMNETRClock Config Minute 38 MVIBBEMNETRClock Config Seconds 9 Page 140 of 153 ProSoft Technology Inc August 31 2009 MVI56E MNETR ControlLogix Platform User Manual Modbus TCP IP Interface Module with Reduced Data Block The bit will be automatically reset to 0 MVIBBEMNETRClock SE MVISBEMNETRClock Read 0 MVISGEMNETRClock Write MVI56EMNETRClock Contig T MVIBBEMNETRClock Config Y ear 2009 MVIBBEMNETRClock Config Month 5 MVIBBEMNETRClock Config D ay 4 MVIBBEMNETRClack Config Hour 15 MVIBBEMNETRClock Config Minute 38 MVIBBEMNETRClock Config Seconds 9 To check the status of the message refer to the WRITECLOCKMSG tag ed WiiteClockMSG Flags 1640200 WriteClockMSG EW 0 WriteClockMSG ER 0 WriteClockMSG DN 0 WriteClockMSG ST 0 WriteClockMSG EN 0 WriteClockMSG TO 0 WiiteClockMSG EN CC 1 WriteClockMSG ERR 16 0000 WiiteClockMSG EXERR 1640000 0000 WriteClockMSG ERR_SRC 0 WiiteClockMSG DN LEN 0 WiteClockMSG REQ LEN 24 5 7 Adding the Module to an Existing Project 1 Add the MVI56E MNETR module to the project Select the the 0 CONFIGURATION folder in the CONTROLLER ORGANIZATION window and then click the right mouse button to open a shortcut menu On the shortcut menu choose NEW MODULE Controller My Controller A Controller Tags Controller Fault Handler Power Up Handler 65 Tasks fa
66. NTROLTRIGGER is set in the example ladder logic the module will build a block 9901 with the number of commands set through MNETR CONTROL CMDCONTROL NUMBEROFCOMMANDS 0 The command indexes will be set through the controller tags starting from MNETR CONTROL CMDCONTROL CMDINDEX 0 to MNETR CONTROL CMDCONTROL CMDINDEX 5 Page 82 of 153 ProSoft Technology Inc August 31 2009 Ladder Logic MVIS56E MNETR ControlLogix Platform User Manual Modbus TCP IP Interface Module with Reduced Data Block For example in order to enable commands 0 2 and 5 the following values would be set MNETR CONTROL CMDCONTROL CMDINDEX 0 MNETR CONTROL CMDCONTROL CMDINDEX 1 0 MNETR CONTROL CMDCONTROL CMDINDEX 2 2 MNETR CONTROL CMDCONTROL CMDINDEX 3 5 The module will receive this block and build and send the command to the specified control device using a MSG block The following table describes the data for the command element in MNETRCmdCortrol Name Data Type Description INT 6 The position of the initial command to execute from the Client command list NumberOfCommands INT The number of commands to execute from the Client command list CommandsAddedtoQueue INT CmdControlTrigger BOOL MNETRPassThru During pass through operation write messages received at the MVIS6E MNETR server write messages through to the processor It is the responsibility of the ladder logic to process the message received
67. Netinask MVIBBEMNETREthernet Config Netmask 0 MVIBBEMNETREthemet Config Netmask 1 MVIBBEMNETREthemet Config Netmask 2 MVIBBEMNETREthernet Config Netmask 3 MVIBBEMNETREthemet Config G ateway MVIBBEMNETREtheret Config G ateway 0 MVIBBEMNETREthernet Config Gateway 1 MVIBBEMNETREthemet Config G ateway 2 MVIBBEMNETREthemet Config G ateway 3 as bie olols o ble th h t nanne FP oO MN To check the status of the message refer to the WRITEETHERNETMSG tag E WiiteE themetMSG WriteE thernetMSG Flags WriteEthernetMSG EW WiiteEthernetMSG ER WiiteEthernetMSG DN WiiteEthermetMSG ST WriteE thernetMSG EN WriteE thernetMSG TO WriteEthernetMSG EN_CC WiiteEthemetMSG ERR WriteEthemetMSG EXERR WiiteEthemetMSG ERR SRC WiiteEthernetMSG DN LEN WiiteEthemetMSG REG LEN I 1 1640200 0 0 0 0 0 0 1 16 0000 5 6 6 Reading the Clock Value from the Module Expand the MVIS6MNETRCLOCK controller tag and move a value of 1 to MVI56MNETRCLOCK READ MVIBBEMNETRClock MVIBSBEMNETRClock Read MVIBBEMNETRClock write MVIBBEMNETRClock Config MVIBBEMNETRClock Config Y ear MVIBBEMNETRClock Config Month MVIBBEMNETRClock Config D ay MVIBBEMNETRClock Config Hour MVI56EMNETRClock Config Minute MVI56EMNETRClock Config Seconds uj 0 0 24
68. P Address Important ProSoft Configuration Builder locates MVIS56E MNETR 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 the routing of the UDP broadcast messages 1 Click the START button and then navigate to PROGRAMS PROSOFT TECHNOLOGY WM Microsoft Update Set Program Access and Defaults W Windows Catalog Accessories de em Administrative Tools Z ProSoft Configurator Ber Documents gt Internet Explorer ProSoft Transport Path Editor Settings gt W Paint ProSoft Discovery Service 2 Search o Windows Media Player Help and Support Run ShutDown 2 Click to start PROSOFT CONFIGURATION BUILDER ProSoft Technology Inc Page 15 of 153 August 31 2009 MVISGE MNETR ControlLogix Platform Start Here Modbus TCP IP Interface Module with Reduced Data Block User Manual 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
69. P IP Interface Module with Reduced Data Block 5 4 MVI56E MNETR Status Data Definition This section contains a description of the members present in the MNETR STATUS object This data is transferred from the module to the processor as part of each read block Offset Content Description 0 Program Scan Count This value is incremented each time a complete program cycle occurs in the module 1 Read Block Count This field contains the total number of read blocks transferred from the module to the processor 2 Write Block Count This field contains the total number of write blocks transferred from the processor to the module 3 Parse Block Count This field contains the total number of blocks successfully parsed that were received from the processor 4 Command Event Block This field contains the total number of command event Count blocks received from the processor 5 Command Block Count This field contains the total number of command blocks received from the processor 6 Error Block Count This field contains the total number of block errors recognized by the module 7 Reserved Not Used 8 Reserved Not Used 9 Reserved Not Used 10 Reserved Not Used 11 Reserved Not Used 12 Reserved Not Used 13 Reserved Not Used 14 Reserved Not Used 15 Reserved Not Used 16 Reserved Not Used 17 Reserved Not Used 18 Reserved Not Used 19 Reserved Not Used
70. ProSoft TEEPNOEOGT Where Automation Connects inRAec MVI56E MNETR ControlLogix Platform Modbus TCP IP Interface Module with Reduced Data Block August 31 2009 USER MANUAL Important Safety Information MVI56E Modules North America Warnings A Warning Explosion Hazard Substitution of components may impair suitability for Class I Division 2 B Warning Explosion Hazard When in Hazardous Locations turn off power before replacing or rewiring modules Warning Explosion Hazard Do not disconnect equipment unless power has been switched off or the area is known to be nonhazardous C Suitable for use in Class Division 2 Groups A B C and D T5 Hazardous Locations or Non Hazardous Locations ATEX Warnings and Conditions of Safe Usage Power Input and Output I O wiring must be in accordance with the authority having jurisdiction A Warning Explosion Hazard When in hazardous locations turn off power before replacing or wiring modules B Warning Explosion Hazard Do not disconnect equipment unless power has been switched off or the area is known to be non hazardous C These products are intended to be mounted in an IP54 enclosure The devices shall provide external means to prevent the rated voltage being exceeded by transient disturbances of more than 40 This device must be used only with ATEX certified backplanes D DO NOT OPEN WHEN ENERGIZED Electrical Ratings Backplane Current Load 800 mA
71. R ControlLogix Platform User Manual Modbus TCP IP Interface Module with Reduced Data Block 5 Click DOWNLOAD to download the configuration files to the module through the path Download files from PC to module Running STEP 1 Select Communication Path Select Connection Type 1756 ENBT v Ethernet f CIPconnect t 192 168 0 100 p 1 s 2 p 2 STEP 2 Transfer File s DOWNLOAD Test Connection Cancel ProSoft Technology Inc Page 77 of 153 August 31 2009 MVI56E MNETR ControlLogix Platform Configuring the MVI56E MNETR Module Modbus TCP IP Interface Module with Reduced Data Block User Manual Page 78 of 153 ProSoft Technology Inc August 31 2009 Ladder Logic MVIS56E MNETR ControlLogix Platform User Manual Modbus TCP IP Interface Module with Reduced Data Block 3 Ladder Logic In This Chapter S MNETRModuleDe esesesesseseseeeeeeeene nnne 79 gt Modbus Message Data semen 84 Ladder logic is required for application of the MVIbGE MNETR module Tasks that must be handled by the ladder logic are module data transfer special block handling and status data receipt Additionally a power up handler may be needed to handle the initialization of the module s data and to clear any 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
72. Word Input Offset 0 Connection Timeout 60 Comment 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 Slave driver will respond to Function Code 3 6 and 16 commands read and write Holding Registers from a remote Master when it is moving 32 bit floating point data If the remote Master 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 especially if the Master must read or write from Modbus addresses above gateway address 3999 virtual Modbus address 44000 or 440000 When set to YES the Slave 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 Master for write commands Example Count 10 Slave driver will send 20 16 bit registers for 10 total 32 bit floating point values If however the remote Master 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 wh
73. a Block Comm Format Select DATA INT Slot Enter the slot number in the rack where the ModelNumber gt module is located Input Assembly 1 Instance Input Size 42 Output Assembly 2 Instance Output Size 42 Configuration 4 Assembly Instance Configuration Size 0 4 Click OK to confirm The new module is now visible 7 5 1 0 Configuration 1756 Backplane 1756 A4 fa 0 1756463 My Controller 8 1 1756 MODULE MNETR 8 2 1756 MODULE MNETR_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 7 Inthe New Routine dialog box enter the name and description of your routine and then click OK ProSoft Technology Inc August 31 2009 Page 41 of 153 MVI56E MNETR ControlLogix Platform Start Here Modbus TCP IP Interface Module with Reduced Data Block User Manual 8 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 Add On For MVI56 MNETR and MVIS6E MNETR modules f AOIS6MNETR Add On For MVI56 MNETR and 5 AOIS6MNETR AOIS6MNETR Connection Input Local 1 1 Data Connection Output Local 1 0 Data MNETR MNETR ji 89 UO Confguraton ED 179 55506 179688 seus My 1 oou 1 3 175600UL
74. age Write Data Ladder Logic Special Control Transfers Blocks Data from Outputimage Processor data areas to output image Backplane Driver Page 104 of 153 ProSoft Technology Inc August 31 2009 MVIS56E MNETR ControlLogix Platform User Manual Modbus TCP IP Interface Module with Reduced Data Block All data transferred between the module and the processor over the backplane is through the input and output images Ladder logic must be written in the ControlLogix processor to interface the input and output image data with data defined in the Controller Tags All data used by the module is stored in its internal database This database is defined as a virtual Modbus data table with addresses from 0 40001 Modbus to 4999 45000 Modbus The following illustration shows the layout of the database Module s Internal Database Structure 5000 registers for user data 0 Register Data 4999 Data contained in this database is paged through the input and output images by coordination of the ControlLogix ladder logic and the MVIS6E MNETR module s program Up to 40 words of data can be transferred from the module to the processor at a time Up to 40 words of data can be transferred from the processor to the module Each image has a defined structure depending on the data content and the function of the data transfer The module uses the following block numbers
75. alid only for write commands Internal Address 0 to 4999 for word level addressing or 0 to 65535 for bit 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 4 6 and 16 this parameter is interpreted as a word or register level address ProSoft Technology Inc Page 59 of 153 August 31 2009 MVI56E MNETR ControlLogix Platform Configuring the MVIS6E MNETR Module Modbus TCP IP Interface Module with Reduced Data Block User Manual Poll Interval 0 to 65535 This parameter specifies the minimum interval to execute continuous commands Enable code of 1 The parameter is entered in tenths of a second Therefore if a value of 100 is entered for a command the command executes no more frequently than every 10 seconds Reg Count Regs 1 to 125 Coils 1 to 800 This parameter specifies the number of 16 bit registers or binary bits to be transferred by the command Functions 5 and 6 ignore this field as they apply only to a single data point For functions 1 2 and 15 this parameter
76. alue from 0 to 41 7 This word contains the internal Modbus address in the module to be used with the command This word can contain a value from 0 to 4999 8 This word contains the count parameter that determines the number of digital points or registers to associate with the command 9 The parameter specifies the swap type for the data This function is only valid for function codes 3 and 4 10 This word contains the Modbus function code to be used with the command 11 This word contains the Modbus address in the slave device to be associated with the command 12 to 41 Spare The module will respond to each command block with a read block The following table describes the format of this block Offset Description Length 0 Write Block ID 1 1 0 Fail 1 Success 1 2 to 40 Spare 39 41 2000 1 Word two of the block can be used by the ladder logic to determine if the command was added to the command queue of the module The command will only fail if the command queue for the port is full 100 commands for each queue ProSoft Technology Inc Page 109 of 153 August 31 2009 MVIS56E MNETR ControlLogix Platform Reference Modbus TCP IP Interface Module with Reduced Data Block User Manual Command Control Command control blocks place commands in the command list into the command queue The client has a command queue of up to 100 commands The module services commands in the queue before the user defined comm
77. am Save and Download page 48 the new application to the controller and place the processor in run mode A ProSoft Technology Inc Page 143 of 153 August 31 2009 MVIS56E MNETR ControlLogix Platform Reference Modbus TCP IP Interface Module with Reduced Data Block User Manual 5 8 Using the Sample Program RSLogix Version 15 and earlier The sample program included with your MVI56E MNETR Module contains predefined controller tags configuration information data types and ladder logic that allow the module to communicate between the ControlLogix processor and a network of Modbus devices For most applications the sample program will work without modification Page 144 of 153 ProSoft Technology Inc August 31 2009 Support Service amp Warranty MVI56E MNETR ControlLogix Platform User Manual Modbus TCP IP Interface Module with Reduced Data Block 6 Support Service amp Warranty In This Chapter How to Contact Us Technical 145 Return Material Authorization RMA Policies and Conditions 146 gt lt LIMITED WARRANTY 147 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 Networ
78. ame Status Information Default Location MVIS6E MNETR Configured MVISGE MNETR 20 48 Module Module Values OK 3 MNET Client 0 MNet Client 0 Values OK gq MNet Servers MNet Servers Values OK 1g STATIC ARP TABLE STATIC ARP TABLE Values OK 6 t tu Commen Comment Values OK amp f Ethernet Configuration WATTCP Values OK Module Information Last Change 2009 06 09 13 01 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 t 0 gateway 192 168 0 1 Module configuration lt MVIS6E MNETR At this time you may wish to rename the Default Project and Default Location folders in the tree view To rename 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 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 plus sign next to the ae icon to expand module information 2 Double click the icon to open the EDIT dialog box 3 To edit a parameter select the parameter in the left pane and make your changes in the right pane 4 Click OK to save your changes Page 52 of 153 ProSoft Technology Inc August 31 2009 Configuring the MVI56E MNETR Module MVI56E MNETR Contr
79. an explanation of each value 4 6 3 Config Use the CONFIGURATION menu to view configuration settings for MNET Client O The information on this menu corresponds with the configuration information in the MNET Client 0 settings in ProSoft Configuration Builder page 55 4 6 4 Status Use the STATUS menu to view status for MNET Client 0 During normal operation the number of requests and responses should increment while the number of errors should not change Page 92 of 153 ProSoft Technology Inc August 31 2009 Diagnostics and Troubleshooting MVI56E MNETR ControlLogix Platform User Manual Modbus TCP IP Interface Module with Reduced Data Block 4 7 Monitoring MNET Server Information Use the MNET SERVER INFORMATION menu to view the configuration and status information for the MNET Server 4 7 1 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 63 4 7 2 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 4 8 Data Analyzer The Data Analyzer mode allows you to view all bytes of data transferred on each port Both the transmitted and
80. and list This gives high priority to commands in the queue Commands placed in the queue through this mechanism must be defined in the module s command list Under normal command list execution the module will only execute commands with the Enable parameter set to one or two If the value is set to zero the command is skipped Commands may be placed in the command queue with an Enable parameter set to zero using this feature These commands can then be executed using the command control blocks One to six commands can be placed in the command queue with a single request The following table describes the format for this block Offset Description Length 0 5001 to 5006 1 1 Command index 1 2 Command index 1 3 Command index 1 4 Command index 1 5 Command index 1 6 Command index 1 7 to 41 Spare 35 The last digit in the block code defines the number of commands to process in the block For example a block code of 5003 contains 3 command indexes that are to be placed in the command queue The Command index parameters in the block have a range of 0 to 99 and correspond to the module s command list entries The module responds to a command control block with a block containing the number of commands added to the command queue for the port The following table describes the format for this block Offset Description Length 0 Write Block ID 1 1 Number of commands added to command queue 1 2
81. and write data transferred between the processor and the module as pages of data up to 40 words long Name Data Type Description ReadData INT 600 Data read from module WriteData INT 600 Data to write to module The read data READDATA is an array set to match the value entered in the Read Register Count parameter of the MNET CFG file For ease of use this array should be dimensioned as an even increment of 40 words This data is paged up to 50 words at a time from the module to the processor The ReadData task places the data received into the proper position in the read data array Use this data for status and control in the ladder logic of the processor The write data WRITEDATA is an array set to match the value entered in the Write Register Count parameter of the MNET CFG file For ease of use this array should be dimensioned as even increments of 40 words This data is paged up to 40 words at a time from the processor to the module The WriteData task 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 3 1 2 MNETRSTATUS This object views the status of the module The MNETRSTATUS object shown below is updated each time a read block is received by the processor Use this data to monitor the state of the module at a real time rate The following table describes the structure
82. as one of the following values 1 2 3 4 5 6 15 or 16 The Device Database Address is the Modbus register or point in the remote slave device to be associated with the command When the module receives the block it will process it and place it in the command queue The following table describes the format of this block Word Description 0 This word contains the block 2000 identification code to indicate that this block contains a command to execute by the Client Driver 1 to 4 These words contain the IP address for the server the message is intended Each digit 0 to 255 of the IP address is placed in one of the four registers For example to reach IP address 192 168 0 100 enter the following values in words 1 to 4 192 168 0 and 100 The module will construct the normal dotted IP address from the values entered The values entered will be anded with the mask OxOOff to insure the values are in the range of 0 to 255 5 This word contains the TCP service port the message will be interfaced For example to interface with a MBAP device the word should contain a value of 502 To interface with a MNET device a value of 2000 should be utilized Any value from 0 to 65535 is permitted A value of 502 will cause a MBAP formatted message to be generated All other values will generate an encapsulated Modbus message 6 This word contains the Modbus node address to use with the message This field should have a v
83. ata Block Index MNET Client Commands 57 92 MNET Client x 55 92 MNET Servers 63 93 Module 90 Static ARP Table 65 90 0 00 Return Query Data 127 A About the MODBUS TCP IP Protocol 103 Adding Multiple Modules Optional 40 Adding the Module to an Existing Project 141 All Product Returns 146 Allocation of Risks 0 ARP Timeout 56 B Backplane Data Transfer 104 Backplane Status 90 Battery Life Advisory 3 Before you Begin 132 Bit Input Offset 64 0 ClPconnect 1 Clearing a Fault Condition 99 Client Command Errors 6 Client Command List 116 Client Driver 115 Cold Boot 111 Command Control 0 Command Control Blocks 108 Command Entry Formats 58 Command Error Delay 56 Command Error Pointer 55 Command List 92 Command List Entry Errors 117 Command List Overview 57 Command Status 92 Commands Supported by the Module 121 Comment 62 Config 90 92 93 Configuration Error Word 98 Configuring Module Parameters 52 Configuring the Data Analyzer 93 Configuring the MVIBGE MNETR Module 49 Connect to the Module s Web Page 23 Connect your PC to the ControlLogix Processor 39 Connect your PC to the Module 15 Controlling Law and Severability 0 Create a new RSLogix 5000 project 6 Create the Module Local Rack 26 31 Create the Module Remote Rack 9 Create the Remote Network 27 31 D Data Anal
84. ath Page 68 of 153 ProSoft Technology Inc August 31 2009 Configuring the MVI56E MNETR Module MVI56E MNETR ControlLogix Platform User Manual Modbus TCP IP Interface Module with Reduced Data Block To use ClPconnect follow these steps 1 In the SELECT PORT dropdown list choose 1756 ENBT The default path appears in the text box as shown in the following illustration Download files from PC to module STEP 1 Select Communication Path Select Connection Type 1756 ENBT Ethernet CIPconnect t 192 168 0 100 p 1 s 0 CIP Path Edit STEP 2 Transfer File s DOWNLOAD Test Connection 2 Click CIP PATH EDIT to open the CIPCONNECT PATH EDITOR dialog box CIPconnect Path Editor f Connect PATH EDITOR Destination Module Source Module IP Source Module Node Ad Slot Number No Source Module Destination Module I 1921680100 MEN ese v t 192 168 0 100 p 1 s 0 Add Rack Delete Rack Construct CIP Path The CIPCONNECT PATH EDITOR allows you to define the path between the PC and the MVI56E MNETR module The first connection from the PC is always a 1756 ENBT Ethernet IP module ProSoft Technology Inc Page 69 of 153 August 31 2009 MVI56E MNETR ControlLogix Platform Configuring the MVIS6E MNETR Module Modbus TCP IP Interface Module with Reduced Data Block User Manual Each row corresponds to a physical rac
85. ation 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 0 0 0000000000 0 e 0 6 3 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 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 3 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 years from the da
86. ators Battery Status ERR Application Status APP Module Status OK 4 Character Scrolling Alpha Numeric Shows Module Version IP Application Port Setting Port LED Display Status and Error Information Debug Configuration Application Ethernet port E1 Ethernet Port 10 100 Base T RJ45 Connector for CAT5 cable Link and Activity LED indicators Auto crossover cable detection Shipped with Unit 5 foot Ethernet straight through cable Page 102 of 153 ProSoft Technology Inc August 31 2009 MVIS56E MNETR ControlLogix Platform User Manual Modbus TCP IP Interface Module with Reduced Data Block 5 2 Functional Overview This section describes how the MVI56E MNETR module transfers data between itself and the processor and how it implements the Modbus TCP IP protocol 5 2 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 Wh
87. c Troubleshooting page 97 and Troubleshooting procedures Diagnostics and Troubleshooting page 85 Reference gt Reference page These sections contain general references 101 associated with this product Specifications and Product Specifications Functional Overview the Functional Overview page 103 Product Specifications page 101 Functional Overview Support Service and gt Support Service This section contains Support Service and Warranty and Warranty page Warranty information Index 145 Index of chapters ProSoft Technology Inc Page 7 of 153 August 31 2009 MVISGE MNETR ControlLogix Platform Start Here Modbus TCP IP Interface Module with Reduced Data Block User Manual Page 8 of 153 ProSoft Technology Inc August 31 2009 Start Here MVI56E MNETR 4 ControlLogix Platform User Manual Modbus TCP IP Interface Module with Reduced Data Block 1 Start Here In This Chapter What s 10 System Requirements sssssssssseeeeeeeneee nennen enne 10 Package Contents ssssssssssssseseeeeeeeneeeneeen eene nnne 0 2 11 Setting Jumpers nnne nnne nnne nnns 12 Install the Module 12 Install the Configuration Tools
88. c 1756 Module Parent Remote_ENBT2 Connection Parameters fane Size Name MNETR Input 42 Description Dutput 42 16 bit Configuration 4 8 bit Comm Format Data INT x sot Open Module Properties Em Help Parameter Value Name Enter a module identification string The recommended value is MNETR Description Enter a description for the module Example Modbus TCP IP Interface Module with Reduced Data Block Comm Format Select DATA INT Very Important Slot Enter the slot number in the rack where the MVIS6E MNETR module is or will be located Input Assembly Instance 1 Input Size 42 Output Assembly Instance 2 Output Size 42 Configuration Assembly Instance 4 Configuration Size 0 4 On the CONNECTION tab set the RPI value for your project Fifty 50 milliseconds is usually a good starting value Wil Module Properties Local 2 1756 MODULE 1 1 General Connection Module Info Backplane Requested Packet Interval 50 024 ms 0 2 750 0 ms Inhibit Module Major Fault On Controller If Connection Fails While in Run Mode Module Fault Status Offline Cancel Help Page 30 of 153 ProSoft Technology Inc August 31 2009 Start Here MVI56E MNETR ControlLogix Platform User Manual Modbus TCP IP Interface Module with Reduced Data Block The MVI56E MNETR module is now visible in the I O CONFIGURATION section Controller My Controller A Controller Tags Controller Fau
89. chnology Inc August 31 2009 User Manual MVIS56E MNETR ControlLogix Platform Modbus TCP IP Interface Module with Reduced Data Block 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 any particular value of any part
90. cks 84 111 Pass Through Mode 54 Pinouts 118 Poll Interval 60 Preset Multiple Registers Function Code 16 129 Preset Single Register Function Code 06 6 Printing a Configuration File 53 Procedures for Return of Units Out of Warranty 146 Procedures for Return of Units Under Warranty 146 Product Specifications 7 101 ProSoft Technology Product Documentation 3 R Read Block 106 Read Coil Status Function Code 01 121 Read Holding Registers Function Code 03 123 Read Input Registers Function Code 04 124 Read Input Status Function Code 02 122 Read Register Count 53 Read Register Start 53 Reading Status Data from the Module 85 Reading the Clock Value from the Module 139 Reading the Ethernet Settings from the Module 137 Reference 7 101 Reg Count 60 Response Timeout 55 Retry Count 55 Return Material Authorization RMA Policies and Conditions 146 5 Server Driver 114 Service Port 61 Set Module Parameters 52 Set Temporary IP Address 15 Set Up the Project 49 Setting Jumpers 12 Slave Address 61 Standard Modbus Protocol Errors 117 Start Here 9 Starting the Data Analyzer 94 Static ARP 90 Status 92 93 Status Read Data Block 106 Stopping the Data Analyzer 95 Sub function codes supported 7 Support Service amp Warranty 7 145 Swap Code 0 System Requirements 10 T The Diagnostics Menu 86 Time L
91. connected to that coil the output will be hot ProSoft Technology Inc Page 125 of 153 August 31 2009 MVI56E MNETR ControlLogix Platform Reference Modbus TCP IP Interface Module with Reduced Data Block User Manual 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 DataStartReg Data of Regs Hi Data ofRegsLo Error Check Field Hi Lo 11 06 00 01 00 03 CRC Response The response to a preset single register request is to re transmit the query message after the register has been altered Adr Func DataRegHi DataRegLo DatalnputRegHi DatalnputRegLo Error Check Field 11 06 00 01 00 03 CRC 5 5 8 Diagnostics Function Code 08 MODBUS function code 08 provides a series of tests for checking the communication system between a Client
92. 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 Untitled ProSoft Configuration Builder View Project Tools Help 8 Default Project Name Status Information Gl Default Location P Default Module Default Module Please Select Module Type Unknown Product Line 1 Last Change Never Last Download Never Module Information Last Change Never Last Download Never Application Rev OS Rev Loader Rev MAC Address ConfigEdit version 2 1 6 Build 4 Module configuration Module Module Type Module Name Default Module Default Module 3 Use the mouse to select DEFAULT MODULE in the tree view and then click the right mouse button to open a shortcut menu Page 16 of 153 ProSoft Technology Inc August 31 2009 Start Here MVI56E MNETR ControlLogix Platform User Manual Modbus TCP IP Interface Module with Reduced Data Block 4 On the shortcut menu choose CHOOSE MODULE TYPE This action opens the CHOOSE MODULE TYPE dialog box Choose Module Type Product Line Filter C All C PLX4000 PLx6000 MVI46 C MVIS6 C MVI71 C PLXs000 PTQ C MVI69 MVIS6E MVI94 Search Module Type STEP 1 Select Module Type Module Definition zl MVI56E GSC MVIS6E MCM MVIS6E MCMR MVISSE MNET MVISSE MNETC
93. ction 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 LoAdd Quantity Byte Data Coil Status Data Coil Status Error Check Cnt 20 to 27 28 to 29 Field 11 OOF 00 13 00 0 02 cD 00 CRC Page 128 of 153 ProSoft Technology Inc August 31 2009 MVIS56E MNETR ControlLogix Platform User Manual Modbus TCP IP Interface Module with Reduced Data Block 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 Err
94. d Data Block User Manual Name Data Type Description EventCmdTrigger BOOL Triggers the Event Command EventCmd MNETREventCmd This object contains the attributes to define a Master command An array of these objects is used for each port CmaControl MNETROCmaControl Controls the execution of the commands listed in the configuration under the MNET Client 0 Commands section PassThru MNETRPassThru Transferrs a remote Client s commands through the MNETR Module straight into the Processor s Controller tags MNETREventCmd The MNETREVENTCWD structure holds the information required for an event command An array of this object should be defined and should hold the event command set to be employed in the application The following table describes the structure of this object Name Data Type Description IPO INT First digit of IP address IP1 INT Second digit of IP address IP2 INT Third digit of IP address IP3 INT Last digit of IP address ServPort INT TCP Service Port number 0 65535 502 for MBAP 2000 for MNET Node INT Modbus slave node address 0 to 247 DBAddress INT Module internal database to use with message Count INT Register or data point count Swap INT Swap code to use with functions 3 and 4 Function INT Modbus function code for message Address INT Address to interface with in device Result INT MNETRCmaControl When the command bit MNETR CONTROL CMDCONTROL CMDCO
95. d the message This information is passed from the module to the processor using a block identification code of 9996 if the unformatted pass through mode code 1 is selected as the pass through mode in the configuration file Word one 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 The Modbus protocol supports control of binary output coils functions 5 and 15 and registers functions 6 and 16 Additionally formatted message blocks can be sent from the module to the processor when the pass through option is selected using the format selection codes 2 or 3 in the MNET CFG file These blocks require less decoding than the unformatted blocks Refer to Pass Through Control Blocks page 111 for a full discussion on utilizing the pass through option in an application Page 84 of 153 ProSoft Technology Inc August 31 2009 Diagnostics and Troubleshooting MVI56E MNETR ControlLogix Platform User Manual Modbus TCP IP Interface Module with Reduced Data Block 4 Diagnostics and Troubleshooting In This Chapter Reading Status Data from the Module 85 lt The Diagnostics 86 Monitoring Module Information esm 89 gt Monitoring Backplane Information eeee 90
96. e is received 244 Client Error Sent Count This value is incremented each time an error is sent from the client 245 Client Error Received This value is incremented each time an error is received Count from a remote unit 246 Client Cfg Error Word This word contains a bit map that defines configuration errors in the configuration file for the client 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 Page 120 of 153 ProSoft Technology Inc August 31 2009 MVIS56E MNETR ControlLogix Platform User Manual Modbus TCP IP Interface Module with Reduced Data Block 5 5 Modbus Protocol Specification The following pages give additional reference information regarding the Modbus protocol commands supported by the MVI56E MNETR 5 5 1 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 Detinition Supported in Client Supported in Server 1 Read Coil Status X X 2 Read Input 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 8 Diagnostics X 15 Multiple Coil Write X X 16 Multiple Register Write
97. ect PATH EDITOR No Source Module Source Module IP Source Module Node Address dress Destination Module Destination Module Slot Number B 1756 EneT 192168010 6 0 t 192 168 0 100 p 1 s 0 Add Rack Delete Rack Construct CIP Path j The CIPCONNECT PATH EDITOR allows you to define the path between the PC and the MVI56E MNETR 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 If the MVIS6E MNETR module is located in the same rack as the first 1756 ENBT module select RACK No 1 and configure the associated parameters If the MVIS56E MNETR is available in a remote rack accessible through ControlNet or Ethernet IP include all racks by using the ADD RACK button Parameter Description Source Module Source module type This field is automatically selected depending on the destination module of the last rack 1756 CNB or 1756 ENBT Source Module IP Address IP address of the source module only applicable for 1756 ENBT Source Module Node Address Node address of the source module only applicable for 1756 CNB Destination Module Select the destination module associated to the source module in the rack The connection between the source and destination modules is performed through the backplane Destination Module Slot Number The slot number where
98. en 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 2 1 7 Static ARP Table The Static ARP Table defines a list of static IP addresses that the module will use when an ARP Address Resolution Protocol is required The module will accept up to 40 static IP MAC address data sets Use the Static ARP table to reduce the amount of network traffic by specifying IP addresses and their associated MAC hardware addresses that the MVI56E MNETR 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 Address Hex Value This table contains a list of static MAC addresses that the module will use when an ARP is required The module wil
99. en the connection is established the client sends the MODBUS TCP IP commands to the server The MVIS6E MNETR 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 MNETR module acts as an input output module between devices on a MODBUS TCP IP network and the Rockwell Automation backplane The module uses an internal database to pass data and commands between the processor and the client and server devices on the MODBUS TCP IP network 5 2 2 Module Power Up On power up the module begins performing the following logical functions 1 Initialize hardware components o Initialize ControlLogix backplane driver o Testand Clear all RAM o Read configuration for module from MNET CFG file on Compact Flash Disk 2 Initialize Module Register space 3 Enable Server Drivers 4 Enable Client Driver When the module has received the configuration the module will begin communicating with other nodes on the network depending on the configuration ProSoft Technology Inc Page 103 of 153 August 31 2009 MVI56E MNETR ControlLogix Platform Reference Modbus TCP IP Interface Module wi
100. er controller tags in the module There are two basic modes of operation when the pass through feature is utilized Unformatted code 1 and Formatted code 2 or 3 The unformatted mode will pass the message received on the server directly to the processor without any processing The following table describes the format of the read block Unformatted Unformatted Pass Through Command Read Block Offset Description Length 0 9996 1 1 Number of bytes in Modbus msg 1 2 Reserved always 0 1 3 to 40 Modbus message received 38 41 9996 1 The ladder logic should copy and parse the received message and control the processor as expected by the master device The processor must respond to the pass through control block with a write block The following table describes the format of the write block Unformatted Pass Through Command Write Block Offset Description Length 0 9996 1 1 to 41 Spare 41 This informs the module that the command has been processed can be cleared from the pass through queue ProSoft Technology Inc Page 111 of 153 August 31 2009 MVI56E MNETR ControlLogix Platform Reference Modbus TCP IP Interface Module with Reduced Data Block User Manual 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 selec
101. ers accept TCP IP connections on service ports 502 MBAP 10 servers and 2000 MNET 10 servers The client can generate either MBAP or MNET requests dependent on the service port selected in the command vex To Processor Output from Module 7 na _ 9 ControlLogix NES MODBUS TCP Processor DATABASE Network Module To Module Input from Network A The following topics discuss the operation of the server and client drivers ProSoft Technology Inc Page 113 of 153 August 31 2009 MVIS56E MNETR ControlLogix Platform Reference Modbus TCP IP Interface Module with Reduced Data Block User Manual Server Driver The Server Driver allows the MVI56E MNETR module to respond to data read and write commands issued by clients on the Modbus TCP IP network The following illustration and associated table describe the flow of data into and out of the module Processor Memory Backplane Interface MNetR Module 1 ControlLogix i 1 Controller Tags 1 Database Modbus Addresses Addresses 1 0 1 Server Driver 1 S H Status gt 6 j from Module Status Status 1 e 1 1 Configuration H 1 i 1 The server driver receives the configuration information from the configuration file on the Compact Flash Disk and the module initializes the servers 2 Host device s
102. eseseeen 14 Connect your PC to the Module eeseenene 15 Set Temporary IP Address sesssseeeeneenenen 15 Connect to the Module s Web Page 23 Upload the Add On Instruction from the Module 25 Create a new RSLogix 5000 26 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 MNETR module s application port s You must be able to complete the application without exposing personnel equipment to unsafe or inappropriate working conditions ProSoft Technology Inc Page 9 of 153 August 31 2009 MVISGE MNETR ControlLogix Platform Start Here Modbus TCP IP Interface Module with Reduced Data Block User Manual 1 1 Whats Different Modbus TCP IP Interface Module with Reduced Data Block products are backward compatible with existing MVI56 products in the field including ladder logic and module configuration files
103. eshooting Modbus TCP IP Interface Module with Reduced Data Block User Manual 4 2 The Diagnostics Menu The Diagnostics menu for this module is arranged as a tree structure with the Main Menu at the top of the tree and one or more sub menus for each menu command The first menu you see when you connect to the module is the Main menu Ci Diagnostics Connection Log Module z oLale T MVIBBE MNETR Time MODULE Select item within MVI56E MNETR for diagnostic information Version F Config Ld NIC Status Ld Static ARP BACKPLANE Lg Status MNET CLIENT 0 Config Status Command List 4 Command Status MNET SERVER Lg Config Lg Status DATABASE ascii Decimal F Hex F Float Path ClPconnect t 105 102 0 65 p 1 s 5 4 2 1 Using the Diagnostics Menu in ProSoft Configuration Builder To connect to the module s Configuration Debug serial port 1 Start PCB program with the application file to be tested Right click over the module icon Eg Default Project 2 88 Default Location hE Page 86 of 153 ProSoft Technology Inc August 31 2009 Diagnostics and Troubleshooting MVI56E MNETR ControlLogix Platform User Manual Modbus TCP IP Interface Module with Reduced Data Block 2 Onthe shortcut menu choose DIAGNOSTICS Default Project 88 Default Location 5 h Delete Rename Copy Choose Module Type View Configura
104. face Module with Reduced Data Block Request Function code 1 Byte 0x08 Sub function 2 Bytes Data N x 2 Bytes Response Function code 1 Byte 0x08 Sub function 2 Bytes Data N x 2 Bytes Error Error code 1 Byte 0x88 Exception code 1 Byte 01 or 03 or 04 Sub function codes supported Only Sub function 00 is supported by the MVIS56E MNETR 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 5 Data Hi 5 Data Lo 37 Data Lo 27 ProSoft Technology Inc Page 127 of 153 August 31 2009 MVI56E MNETR ControlLogix Platform Reference Modbus TCP IP Interface Module with Reduced Data Block User Manual The data fields in responses to other kinds of queries could contain error counts or other data requested by the sub function code Data Value OK 5 5 9 Force Multiple Coils Fun
105. fset parameter ProSoft Technology Inc August 31 2009 Page 97 of 153 MVIS56E MNETR ControlLogix Platform Diagnostics and Troubleshooting Modbus TCP IP Interface Module with Reduced Data Block User Manual Operation Messages After the initialization step the following message pattern will be repeated lt Backplane Status gt lt IP Address gt lt Backplane Status gt lt Port Status gt Code Message lt Backplane Status gt OK Module is communicating with processor ERR Module is unable to communicate with processor For this scenario the lt Port Status gt message above is replaced with Processor faulted or is in program mode IP Address Module IP address C0 OK Port is communicating without error Communication Errors port is having communication errors Refer to PCB diagnostics for further information about the error The LEDs indicate the module s operating status as follows Module Color Status Indication APP Amber The MVI56E MNETR is working normally Off The MVI56E MNETR module program has recognized a communication error on its Application Port s OK Red Off The card 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 rac
106. g LED during module power up Important The Rung Import with Utility 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 data Page 132 of 153 ProSoft Technology Inc August 31 2009 MVI56E MNETR ControlLogix Platform User Manual Modbus TCP IP Interface Module with Reduced Data Block 5 6 3 Installing the Rung Import with Utility Add On Instruction 1 Right click on an empty rung in the main routine of your existing ladder logic and choose IMPORT RUNG Edt Search Lege Communications Toss Window Heb alsia amp xime 7 9 Gig 8 3 omne 7 No Forces ace 4 sepe a gt 33 2 0 Favorites Corer 1 f Add On MVIS6E Add On MVI56E MVI56E MVI58E Loca C Local 1 6 X Local 1 1 Data Local 1 0 Data MVI56E Rng fat Rung Edt Burg Comment hu r 9 01 1796900 o anp Export hung per amp ung Go To 6 BFS Dement Axes ProSoft Technology Inc Page 133 of 153 August 31 2009 MVI56E MNETR ControlLogix Platform Reference Modbus TCP IP Interface Module with Reduced Data Block User Manual 2 Navigate to the folder where you saved MVISe E MNETR Optional AddOn Rung version gt L5X and select the file I
107. gnore in the data set will have a value of 0 in the mask 41 9959 1 Formatted Pass Through Command Blocks Read Block Offset Description Length 0 9970 1 1 1 1 2 0 1 3 to 40 Spare data area 38 41 9996 1 The ladder logic should and parse the received message and control the processor as expected by the master device The processor must respond to the formatted pass through control blocks with a write block The following tables describe the format of the write blocks Page 112 of 153 ProSoft Technology Inc August 31 2009 MVIS56E MNETR ControlLogix Platform User Manual Modbus TCP IP Interface Module with Reduced Data Block Formatted Pass Through Response Write Block Offset Description Length 0 9956 9957 9958 9960 or 9961 1 1 to 41 Spare data area 41 Formatted Pass Through Response Write Block Offset Description Length 0 9959 1 1 to 41 Spare data area 41 Formatted Pass Through Response Write Block Offset Description Length 0 9970 1 1 to 41 Spare data area 41 5 2 4 Data Flow between MVI56E MNETR Module and ControlLogix Processor The following topics describe the flow of data between the two pieces of hardware ControlLogix processor and MVIS56E MNETR module and other nodes on the Modbus TCP IP network under the module s different operating modes The module contains both servers and a client The serv
108. he data will be placed in the ControlLogix processor controller tag array of module read data Each transfer can move up to 40 words block offsets 1 to 40 of data In addition to moving user data the block also contains status data for the module The Write Block ID associated with the block requests data from the ControlLogix processor Under normal program operation the module sequentially sends read blocks and requests write blocks For example if the application uses three read and two write blocks the sequence will be as follows R1W1 gt R2W2 gt R3W1 gt R1W2 gt R2W1 gt 5R38W2 gt R1W15 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 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 Offset Description Length 0 Write Block ID 1 1 to 40 Write Data 40 41 1 The Write Block ID is an index value used to determine the location in the module s database where the data will be placed Each transfer can move up to 40 words block offsets 1 to 40 of data Initialize Output Data When the module performs a restart operation it will request blocks of output data from the processor to initialize the module s outp
109. he Output Offset value is set to 3000 data requires 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 3999 This parameter defines the start register for Modbus command data in the internal database This parameter is enabled when a value greater than O 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 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 Page 64 of 153 ProSoft Technology Inc August 31 2009 Configuring the MVIBGE MNETR Module MVI56E MNETR ControlLogix Platform User Manual Modbus TCP IP Interface Module with Reduced Data Block Word Input Offset 0 to 4999 This parameter defines the start register for Modbus Command data in the internal database This parameter is enabled wh
110. he Server interface device is normally serviced at the end of the controller s scan the data will reflect the register content at the end of the scan Some Servers will limit the quantity of register content provided each scan thus for large register quantities multiple transmissions will be made using 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 10 2888 HiData LoData HiData LoData Error Check Field 11 03 06 02 2B 00 00 00 64 CRC 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 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
111. he 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 Al Quantity of Outputs 00 Quantity of Outputs Lo 1 In this example the Client addresses a request to server device The function code 01 is for a Read Output Status operation It requests the status of the output at address 1245 04A1 hex Note that only that one output is to be read as specified by the number of outputs field 0001 If the output address is non existent in the server device the server will return the exception response with the exception code shown 02 This specifies an illegal data address for the Server Page 130 of 153 ProSoft Te
112. her intellectual property e Customer agrees that it shall not and shall not authorize others to copy software provided by ProSoft except as expressly permitted in any license agreement accompanying such software transfer software to a third party separately from the Product modify alter translate decode decompile disassemble reverse engineer or otherwise attempt to derive the source code of the software or create derivative works based on the software export the software or underlying technology in contravention of applicable US and international export laws and 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 3 5 Disclaimer of all Other Warranties The Warranty set forth in What Is Covered By This Warranty page 147 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 149 of 153 August 31 2009 MVI56E MNETR ControlLogix Platform Support
113. ic 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 Functional Specifications The MVI56E MNETR transfers data in small I O blocks than the MVI56E MNET which makes it ideal for installations in remote racks or where bandwidth is limited Works well with redundant ControlLogix Programmable Automation Controllers PACs using ControlNet Module appears to the ControlLogix processor as an input output I O module 40 word scheduled I O image blocks used for data transfers require significantly less bandwidth than the MVIbGE MNET Retrieving module status and executing special functions command control event commands etc are supported in ladder logic by special block transfer codes 5 1 3 Hardware Specifications Specification Description Backplane Current Load 800 mA 5 V DC 3 mA 24V DC Operating Temperature 0 to 60 32 to 140 F Storage Temperature 40 to 85 C 40 to 185 F Shock 30g Operational 50g non operational Vibration 5 g from 10 to 150 Hz Relative Humidity 5 to 95 non condensing LED Indic
114. ich is shown 1B HEX 0001 1011 Binary contains the status of only 5 coils 52 to 56 instead of 8 coils The 3 left most bits are provided as zeros to fill the 8 bit format 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 Data Start PtLo Data of Pts Hi Data of Pts Lo Error Check Field 11 02 00 C4 00 16 CRC Page 122 of 153 ProSoft Technology Inc August 31 2009 MVIS56E MNETR ControlLogix Platform User Manual Modbus TCP IP Interface Module with Reduced Data Block Response An example response to Read Input Status is as shown in Figure C4 The data is packed one bit for each i
115. ich is the default setting You will also need to set the F oat Start and Float Offset parameters to appropriate values whenever the Float Flag parameter is set to YES ProSoft Technology Inc Page 63 of 153 August 31 2009 MVIS56E MNETR ControlLogix Platform Configuring the MVIS6E MNETR Module Modbus TCP IP Interface Module with Reduced Data Block User Manual Float Start 0 to 65535 This parameter defines the first register of floating point data All requests with register values greater than or equal to this value will be considered floating point data requests This parameter is only used if the Float Flag is enabled For example if a value of 7000 is entered all requests for registers 7000 and above will be considered as floating point data Float Offset 0 to 9999 This parameter defines the start register for floating point data in the internal database This parameter is used only if the Float Flag is enabled For example if the Float Offset value is set to 3000 and the float start parameter is set to 7000 data requests for register 7000 will use the internal Modbus register 3000 Output Offset 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 If t
116. icular 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 Server device 0 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 Device Failed To Resp
117. iety of instruments and devices This module uses a small I O data area for data transfer between the module and the ControlLogix processor making it ideal for ControlNet or Ethernet applications with the module in a remote rack The module exchanges up to 5000 words of data between the processor and the Modbus TCP IP network 5 1 1 General Specifications Backward compatible with previous MVI56 MNETR versions Single Slot 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 Reduced I O image size designed specifically to optimize remote rack implementations ProSoft Configuration Builder PCB software supported a Windows based graphical user interface providing simple product and network configuration Sample ladder logic and Add On Instructions AOls are used for data transfer between module and processor ProSoft Technology Inc Page 101 of 153 August 31 2009 MVIS56E MNETR ControlLogix Platform Reference Modbus TCP IP Interface Module with Reduced Data Block User Manual Internal web server provides access to product documentation module status diagnostics and firmware updates 4 character alpha numer
118. ifferent slot than the one configured in the ladder logic AOI Processor is not in RUN or REM RUN mode Last config lt date gt Indicates the last date when the module changed its IP address You can update the module date and time through the module s web page or with the optional MVI56E Utility Add On Instruction CO Client CmdCnt X MinDly X CmdOffs RespTmout X Retries X ErrOffs X ARPTmout X ErrDelay X FitFlag lt FItSt X 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 the application port s The information consists of Client CmdCnt number of commands configured for the client MinDly Minimum Command Delay parameter CmdaOffs Command Error Pointer parameter RespTmout Response Timeout parameter Retries Retry Count parameter ErrOffs Error Status Offset parameter AHPTmout ARP Timeout parameter ErrDelay Command Error Delay parameter FltFlag 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 offset parameter HoldOffs Holding Register offset parameter Float Flag parameter FIt St Float Start parameter FltOffs Float Of
119. imit for Bringing Suit 150 Troubleshooting 100 Page 152 of 153 ProSoft Technology Inc August 31 2009 Index MVIS56E MNETR ControlLogix Platform User Manual Modbus TCP IP Interface Module with Reduced Data Block U Unformatted 111 Upload the Add On Instruction from the Module 25 35 Using ClPconnect to Connect to the Module 68 88 118 Using ProSoft Configuration Builder Software 49 Using the Diagnostics Menu in ProSoft Configuration Builder 86 Using the Rung Import with Utility Add On Instruction 132 Using the Sample Program RSLogix Version 15 and earlier 144 V Version 89 W Warm Boot 110 What Is Covered By This Warranty 147 149 What Is Not Covered By This Warranty 148 What s Different 10 Word Input Offset 65 Write Block 7 Write Register Count 53 Write Register Start 53 Writing the Clock Value to the Module 140 Writing the Ethernet Settings to the Module 138 Y Your Feedback Please 3 ProSoft Technology Inc Page 153 of 153 August 31 2009
120. k In order to implement this feature set the enable code for the command to a value of 2 ProSoft Technology Inc Page 57 of 153 August 31 2009 MVIS56E MNETR ControlLogix Platform Modbus TCP IP Interface Module with Reduced Data Block Configuring the MVIS6E MNETR Module User Manual Command Entry Formats The following table shows the structure of the configuration data necessary for each of the supported commands Column 1 2 3 4 5 6 7 8 9 10 Function Enable Internal Poll Count Swap IP Serv Slave Function Device Code Code Address Interval Code Address Port Node Code Modbus Time Address fc Code Register 1 10 Bit 0 IP Port Address Read Coil Register bit Seconds Count Address 0x fc2 Code Register 1 10th Bit 0 IP Port Address Read Input Register bit Seconds Count Address 1x fc3 Code Register 1 10th Word Code Port Address Read Holding Register Seconds Count Address Registers 4x fc4 Code Register 1 10 Word 0 IP Port Address Read Input Register Seconds Count Address Registers 3x fc5 Code 1 bit 1 10th Bit 0 IP Port Address Force Write Register Seconds Count Address Single Coil 0x fc6 Code 1 bit 1 10th Word 0 IP Port Address Preset Write Register Seconds Count Address Single Register 4x fc15 Code Register 1 10th Bit 0 IP Port Address Force Write Register bit Seconds Count Address Multiple Coil 0x fc16 Code Register 1 10th Word 0 IP Port
121. k and re insert it to restart its internal program BAT Red Off The battery voltage is OK and functioning On The battery voltage is low or battery is not present Allow battery to charge by keeping module plugged into rack for 24 hours If BAT LED still does not go off contact ProSoft Technology as this is not a user serviceable item 4 9 1 Configuration Error Word If a configuration error is found for the Client the Client configuration error word will have a value other than zero The configuration error word bits have the following definitions Bit Description Value 0 0x0001 1 0x0002 2 0x0004 3 0x0008 4 Invalid retry count parameter 0x0010 5 The float flag parameter is not valid 0x0020 6 The float start parameter is not valid 0x0040 7 The float offset parameter is not valid 0x0080 Page 98 of 153 ProSoft Technology Inc August 31 2009 Diagnostics and Troubleshooting MVIS56E MNETR ControlLogix Platform User Manual Modbus TCP IP Interface Module with Reduced Data Block Bit Description Value 8 The ARP Timeout is not in range ARP Timeout parameter 0 or 0x0100 greater than 60000 milliseconds and will default to 5000 milliseconds 9 The Command Error Delay is gt 300 and will default to 300 0x0200 10 0x0400 11 0x0800 12 0x1000 13 0x2000 14 0x4000 15 0x8000 Correct any invalid data in the configuration for proper module operation When
122. k details If the issue is hardware related we will also need information regarding 1 Module configuration and contents of file o Module Operation o Configuration Debug status information o LED patterns 2 Information about the processor and user data files as viewed through and LED patterns on the processor 3 Details about the serial devices interfaced if any 6 1 How to Contact Us Technical Support Internet Web Site www prosoft technology com support E mail address support prosoft technology com Asia Pacific 603 7724 2080 support asia prosoft technology com Languages spoken include Chinese English Europe location in Toulouse France 33 0 5 34 36 87 20 support EMEA prosoft technology com Languages spoken include French English North America Latin America excluding Brasil location in California 1 661 716 5100 support prosoft technology com Languages spoken include English Spanish For technical support calls within the United States an after hours answering system allows pager access to one of our qualified technical and or application support engineers at any time to answer your questions Brasil location in Sao Paulo 55 11 5084 5178 eduardo prosoft technology com Languages spoken include Portuguese English ProSoft Technology Inc Page 145 of 153 August 31 2009 MVISGE MNETR ControlLogix Platform Support Service amp Warranty Modbus TCP IP Interface Module with Reduced
123. k in the CIP path If the MVIS6E MNETR module is located the same rack as the first 1756 ENBT module select RACK No 1 and configure the associated parameters If the MVIS6E MNETR 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 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 2 3 Configure the path between the 1756 ENBT connected to your PC and the MVI56E MNETR module o If the 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 The f
124. l 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 65 of 153 August 31 2009 MVI56E MNETR ControlLogix Platform Configuring the MVI56E MNETR Module Modbus TCP IP Interface Module with Reduced Data Block User Manual 2 1 8 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 192 168 0 250 my_ip netmask 255 255 255 0 gateway 192 168 0 1 EM 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 Whe
125. lane 1756 44 fa 0 1756 L63 My_Controller 8 1 1756 ENBT A Local ENBT1 Ethemet 1755 Local 1 1756 ENBT 4 Remote_ENBT2 1756 Backplane 1756 417 fJ D 1756 ENBT A Remote ENBT2 fJ 1 1756 MODULE MNETR 0 Cancel Help J Page 136 of 153 ProSoft Technology Inc August 31 2009 MVI56E MNETR ControlLogix Platform User Manual Modbus TCP IP Interface Module with Reduced Data Block 5 6 4 Reading the Ethernet Settings from the Module Expand the MVIS6MNETRETHERNET controller tag and move a value of 1 to MVIS6MNETRETHERNET READ MVIBBEMNETREthemet II MVISBEMNETREthemet Read 1 MVIBBEMNETREthemet write 0 MVIBBEMNETREthemet Config HT MVIBBEMNETREthermet Config IP 1 MVIBBEMNETREthemet Config IP U 0 MVIBBEMNETREthemet Config IP 1 0 MVIS6EMNETREthemet Contig IP 2 0 MVIBBEMNETREthemet Config IP 3 0 MVIBBEMNE TRE theri Curfiy Nelinask fse MVIBBEMNETREthemet Config Netmask 0 0 MVIBBEMNETREthermet Config Netmask 1 0 MVIBBEMNETREtheret Config Netmask 2 0 MVIBBEMNETREthemet Config Netmask 3 0 MVIBBEMNETREthemet Config Gateway IT MVIBBEMNETREthermet Config G ateway O 0 MVIBBEMNETREthemet Config G ateway 1 0 MVIBBEMNETREthemet Config G ateway 2 0 MVIBBEMNETREtheret Config G ateway 3 0 The bit will be automatically reset and the current Ethernet settings will be copied to MVIS6MNETRETHERNET controller tag as follows
126. lock User Manual 1 6 Install the Configuration Tools 1 6 1 Install ProSoft Configuration Builder To install ProSoft Configuration Builder from the CD ROM 1 Insert the ProSoft Solutions CD ROM into the CD drive of your PC Wait for the startup screen to appear T Enjoy easy connectivity with ProSoft Technology Powerful diagnostics features for you Install ProSoft to gather real time module status p Discovery Service and analyze the data stream moving through the module Use PCB to configure some modules amp Install ProSoft Configuration Builder 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 Page 14 of 153 ProSoft Technology Inc August 31 2009 Start Here MVI56E MNETR ControlLogix Platform User Manual Modbus TCP IP Interface Module with Reduced Data Block 1 7 Connect your PC to the Module With the module securely mounted connect one end of the Ethernet cable to the CoNFIG E1 Port and the other end to an Ethernet hub or switch accessible from the same network as your PC Or you can connect directly from the Ethernet Port on your PC to the CoNFIG E1 Port on the module 1 8 Set Temporary I
127. lt Handler Power Up Handler Tasks 7 5 Motion Groups Ungrouped Axes Add On Instructions Data Types Trends 1 0 Configuration 9 1756 Backplane 1756 A fa 0 1756 163 My_Cortroller 1 1756 ENBT A Local_ENBT1 gy Ethernet BJ 1756 ENBT A Local ENBT1 8 1756 ENBT ARemote ENET2 1756 Backplane 1756 A17 0 1756 ENBT A Remote ENET2 1 1756 MODULE MVIS6E_Remote_Rack Note If you are installing the MVIbGE MNETR module in a local rack follow these steps If you are installing the module in a remote rack refer to Create the Module Remote Rack page 27 1 11 3 Create the Module Local Rack 1 Add the MVI56E MNETR 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 3 6 1 0 Configuration 1756 Backplane 1756 A4 fa 0 1756463 My Controller 1 1756 CNBR D CNBR_Local ControlNet 8 11756 CNBR D CNBR_Local 8 2 1756 CNBR D CNBR_Remote 11756 Backplane 1756 0 1756 CNBR D 1 1756 MoDULE M ProSoft Technology Inc Page 31 of 153 August 31 2009 MVISGE MNETR ControlLogix Platform Start Here Modbus TCP IP Interface Module with Reduced Data Block User Manual This action opens the SELECT MODULE dialog box E Select Module Module Analog Communications Controllers Digital Drives Motion Other 1
128. ment method other than that specified by ProSoft or shipped without an RMA number will be returned to the Customer freight collect Contact ProSoft Technical Support for further information d A 1096 restocking fee applies to all warranty credit returns whereby a Customer has an application change ordered too many does not need and so on 6 2 2 Procedures for Return of Units Under Warranty A Technical Support Engineer must approve the return of Product under ProSoft 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 at designated location referenced on the Return Material Authorization 6 2 3 Procedures for Return of Units Out of Warranty a Customer sends unit in for evaluation 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 Page 146 of 153 ProSoft Technology Inc August 31 2009 Support Service amp Warranty MVI56E MNETR ControlLogix Platform User Manual Modbus TCP IP Interface Module with Reduced Data Block 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 evalu
129. module will print a TT for every xx milliseconds of no data on the line Usually 10milliseconds is the best value to start with To save a capture file of your Diagnostics session 1 After you have selected the Port Format and Tick we are now ready to start a capture of this data Click to capture the Diagnostics session to a log file 2 When you have captured the data you want to save click again to stop capturing data iy 91912 Click to stop capturing You have now captured and saved the file to your PC This file can now be used in analyzing the communications traffic on the line and assist in determining communication errors The log file name is PCB Log txt located in the root directory of your hard drive normally Drive C Now you have everything that shows up on the Diagnostics screen being logged to a file called PCB Log txt You can email this file to ProSoft Technical Support for help with issues on the communications network ProSoft Technology Inc Page 95 of 153 August 31 2009 MVI56E MNETR ControlLogix Platform Modbus TCP IP Interface Module with Reduced Data Block Diagnostics and Troubleshooting User Manual To begin the display of the communications data start the Data Analyzer When the Data Analyzer is running you should see something like this Li Diagnostics Connection Log Module S 1 DIN Alel T MVIBGE MNETR Eaa BACKPLANE Status 5 8 DATABASE ASCII Decimal
130. mport Rung Look in Desktop MVIS6 E MNETR_AddOn_Rung_v1_1 L5X EN MVIS6 E MNETR Optional AddOn Rung vi 0 L5X My Recent lt gt File name IMVI56 E MNETR_Optional_AddOn_Rung_v1_ Fies RSlogkS000XMLFlesCL59 Cancel px 3 In the IMPORT CONFIGURATION window click OK Import Configuration Tags Data Types Add On Instructions ADISEMNETR Create New MVISSEMNETRObck Create New MVISGEMNETREthemet MNETREthem Create New ReadCleckMSG MESSAGE Create New ReadEthemetMSG MESSAGE Create New WriteClockMSG MESSAGE Create New WiiteEthemetMSG MESSAGE Create New Page 134 of 153 ProSoft Technology Inc August 31 2009 MVI56E MNETR ControlLogix Platform User Manual Modbus TCP IP Interface Module with Reduced Data Block The Add On Instruction will be now visible in the ladder logic Observe that the procedure has also imported data types and controller tags associated to the Add On Instruction ICECE 8 28 a saa m a Cri BQ be 4 sem Ion 2 on ow Ow Ow al i MVISS MNETR Optional 6 Add aotseveem On MVIS6 MNETR Optional Add On Ethernet Clock METERS AOISEMNETR_Optional AOIS amp EMNETR Optional C MVIS amp MNETREthernet MVIS6EMNETREthernet MVISBMNETRCIock MVISBEMNETRClock ReedEthernetMSG
131. n 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 Transfer of title shall not operate to convey to Customer any right to make or have made any Product supplied by ProSoft d Customer is granted no right or license to use any software or other intellectual property in any manner or for any purpose not expressly permitted by any license agreement accompanying such software or ot
132. n you are finished editing click OK to save your changes and return to the ProSoft Configuration Builder window Page 66 of 153 ProSoft Technology Inc August 31 2009 Configuring the MVIBGE MNETR Module MVI56E MNETR ControlLogix Platform User Manual Modbus TCP IP Interface Module with Reduced Data Block 2 2 Download the Project to the Module In order for the module to use the settings you configured you must download copy the updated Project file from your PC to the module 1 In the tree view in ProSoft Configuration Builder click once to select the MVI56E MNETR module 2 Open the PROJECT menu and then choose MODULE DOWNLOAD This action opens the DOWNLOAD dialog box Notice that the Ethernet address field contains the temporary IP address you assigned in the previous step ProSoft Configuration Builder will use this temporary IP address to connect to the module Download files from PC to module STEP 1 Select Communication Path Select Connection Type Ethernet vj Browse Device s Ethernet 192 168 0 250 Use Default IP CIPconnect STEP 2 Transfer File s DOWNLOAD Test Connection Click TEST CONNECTION to verify that the temporary IP address is correct 3 If the connection succeeds click DOWNLOAD to transfer the Ethernet configuration to the module If the Test Connection procedure fails you will see an error message To correct the error follow these
133. ng 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 causing unintended machine motion or loss of process control causing an explosion 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 Slot 1 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 rack 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 ProSoft Technology Inc Page 13 of 153 August 31 2009 MVISGE MNETR ControlLogix Platform Start Here Modbus TCP IP Interface Module with Reduced Data B
134. ng topics describe the function and structure of each block Status Read Data Block This block is automatically copied from the module and contains status information about the module Offset Description Length 0 Write Block ID 1 1 Program Scan Counter 1 2to7 Block Transfer Status 6 8to9 Reserved Server Status 2 10 to 11 MNET Server Status 2 12 to 3 MBAP Server Status 2 14 to 23 MNET Client Status 10 24 to 40 Reserved 17 41 Read Block ID 1 or 0 1 MVI56E MNETR Client Status Offset Client Status 3 Total number of command list requests 4 Total number of command list responses 5 Total number of command list errors 6 Total number of requests of slave 7 Total number of responses 8 Total number of errors sent 9 Total number of errors received 10 Total number of Configuration Errors 11 Total number of Current Errors 12 Last Error 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 Offset Description Length 0 Write Block ID 1 1 to 40 Read Data 40 41 Read Block ID 1 Page 106 of 153 ProSoft Technology Inc August 31 2009 MVIS56E MNETR 4 ControlLogix Platform User Manual Modbus TCP IP Interface Module with Reduced Data Block The Read Block ID is an index value used to determine the location of where t
135. nput 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 bit 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 lef
136. nsequential 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 3 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 148 of 153 ProSoft Technology Inc August 31 2009 Support Service amp Warranty MVI56E MNETR ControlLogix Platform User Manual Modbus TCP IP Interface Module with Reduced Data Block 6 3 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 litigatio
137. oSoft 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 or viii disasters such as fire flood earthquake wind and lightning c The information in this Agreement is subject to change without notice ProSoft shall not be liable for technical or editorial errors or omissions made herein nor for incidental or co
138. ode Add No Source Module Destination Module 192 168 0 100 1 2 Add Rack Delete Rack Construct CIP Path OK cancel Click OK to close the CIP PATH EDITOR and return to the DOWNLOAD dialog box 3 Check the new path in the download text box Download files from PC to module STEP 1 Select Communication Path Select Connection Type 1756 ENBT Ethernet 1 t 192 168 0 100 p 1 s 2 STEP 2 Transfer File s DOWNLOAD Test Connection Cancel Page 72 of 153 ProSoft Technology Inc August 31 2009 Configuring the MVI56E MNETR Module MVI56E MNETR ControlLogix Platform User Manual Modbus TCP IP Interface Module with Reduced Data Block 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 evice s Ethernet t IF CIPconnect Successfully Connected STEP 2 Transfer File DOWNLOAD Connection 5 Click OK to close the Test Connection pop up and then click DOWNLOAD to download the configuration files to the module through the path Download files from PC to module Running r STEP 1 Select Communication Path Select Connection Type 1756 ENBT Devicet Ethernet Use fault IF CIPconnect t 192 168 0 100 p 1 s 2 m
139. olLogix Platform User Manual Modbus TCP IP Interface Module with Reduced Data Block Printing a Configuration 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 Onthe VIEW CONFIGURATION window open the FILE menu and choose PRINT This action opens the PRINT dialog box 4 Onthe PRINT dialog box choose the printer to use from the dropdown list select printing options and then click OK 2 1 3 Module This section of the configuration describes the database setup and module level parameters This section provides the module with a unique name identifies the method of failure for the communications for the module if the processor is not in run and describes how to initialize the module upon startup Error Status Pointer 1 to 4955 Starting register location in virtual Modbus database for the error status table If a value of 1 is entered the error status data will not be placed in the database All other valid values determine the starting location of the data This data area includes the module version information and all error status data Read Hegister Start 0 to 4999 This parameter specifies the starting register in the module where data will be transferred from the module to the processor Valid range for this parameter is O to 4999 Read Hegister Count 0 to 5000 This pa
140. ollowing examples should provide a better understanding on how to set up the path for your network Page 70 of 153 ProSoft Technology Inc August 31 2009 Configuring the MVI56E MNETR Module MVI56E MNETR ControlLogix Platform User Manual Modbus TCP IP Interface Module with Reduced Data Block 2 3 1 Example 1 Local Rack Application For this example the MVIS56E MNETR module is located in the same rack as the 1756 ENBT that is connected to the PC MVI56E Module 1756 ENBT Ethernet Rack 1 Slot Module Network Address 0 ControlLogix Processor 1 Any 2 MVI56E MNETR 3 1756 ENBT IP 192 168 0 100 1 Inthe Download window click CIP PATH EDIT Download files from PC to module STEP 1 Select Communication Path Select Connection Type 1756 ENBT id Ethernet CIPconnect t 192 168 0 100 p 1 s 0 CIP Path Edit STEP 2 Transfer File s DOWNLOAD Test Connection ProSoft Technology Inc Page 71 of 153 August 31 2009 MVI56E MNETR ControlLogix Platform Configuring the MVIS6E MNETR Module Modbus TCP IP Interface Module with Reduced Data Block User Manual 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 f Connect PATH EDITOR Destination Module Slot Number B vseener 192162010 MVI56 Module 2 Source Module IP Source Module N
141. om the ladder logic to one of the clients on the module The following table describes the format of these blocks Offset Description Length 0 2000 1 1to4 IP Address 4 5 Service Port 1 6 Slave Address 1 7 Internal DB Address 1 8 Point Count 1 9 Swap Code 1 10 Modbus Function Code 1 11 Device Database Address 1 12 to 41 Spare 30 Use the parameters passed with the block to construct the command The IP Address for the node to reach on the network is entered in four registers 1 to 4 Each digit of the IP address is entered in the appropriate register For example to interface with node 192 168 0 100 enter the values 192 168 0 and 100 in registers 1 to 4 The Service Port field selects the TCP service port on the server to connect If the parameter is set to 502 a standard MBAP message will be generated All other service port values will generate a Modbus command message encapsulated in a TCP IP packet Page 108 of 153 ProSoft Technology Inc August 31 2009 MVIS56E MNETR ControlLogix Platform User Manual Modbus TCP IP Interface Module with Reduced Data Block The Internal DB Address parameter specifies the module s database location to associate with the command The Point Count parameter defines the number of points or registers for the command The Swap Code is used with Modbus functions 3 and 4 requests to change the word or byte order The Modbus Function Code h
142. on in virtual database for the error status table for this client If a value of 1 is entered the error status data will not be placed in the database All other valid values determine the starting location of the data Command Error Pointer 1 to 4999 This parameter sets the address in the internal database where the command error data will be placed If the value is set to 1 the data will not be transferred to the database Minimum Command Delay 0 to 65535 This parameter specifies the number of milliseconds to wait between the initial issuance of a command This parameter can be used to delay all commands sent to slaves 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 Hesponse Timeout 0 to 65535 milliseconds This is the time in milliseconds that a client will wait before re transmitting a command if no response is received from the addressed server The value to use depends upon the type of communication network used and the expected response time of the slowest device on the network Retry Count 0 to 10 This parameter specifies the number of times a command will be retried if it fails Float Flag Yes or No This flag specifies how the Slave driver will respond to Function Code 3 6 and 16 commands read and write Holding Registers from a remote Master when it is moving 32 bit floating point data If the remote Master e
143. ond 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 ProSoft Technology Inc August 31 2009 Page 131 of 153 MVIS56E MNETR ControlLogix Platform Reference Modbus TCP IP Interface Module with Reduced Data Block User Manual 5 6 Using the Rung Import with Utility Add On Instruction 5 6 1 Before you Begin sure that you have installed RSLogix 5000 version 16 or later Download the Add On file MVI56 E MNETR_Optional_AddOn_Rung_ lt version gt L5X from the module s web page and copy it to a folder in your PC 5 6 2 Overview The Rung Import with Utility Add On Instruction contains optional logic for MVI56E MNETR applications to perform the following tasks Read Write Ethernet Configuration Allows the processor to read or write the module IP address netmask and gateway values Note This is an optional feature You can perform the same task through PCB ProSoft Configuration Builder Even if your PC is in a different network group you can still access the module through PCB by setting a temporary IP address Read Write Module Clock Value Allows the processor to read and write the module clock settings The module clock stores the last time that the Ethernet configuration was changed The date and time of the last Ethernet configuration change is displayed in the scrollin
144. or Check Field 11 OF 00 13 00 0A CRC The writing of coils via Modbus function 15 will be accomplished regardless of whether the addressed coils are disabled or not Coils that are unprogrammed 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 5 5 10 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 When specified registers with contents specified Note Function codes 5 6 15 and 16 are the only messages that will be recognized as valid for broadcast Adr Func Hi Lo Add Quantity Byte Hi Lo Hi Lo Error Check Add Cnt Data Data Data Data Field 11 10 00 87 00 02 04 00 OA 01 02 CRC Response The normal response to a function 16 query is to echo the address function code starting address and number of registers to be loaded Adr Func Hi Addr Lo Addr Quantity Error Check Field 11 10 00 87 00 02 56 5 5 11 Modbus Exception Responses When a Modbus
145. pond with the contents of the module s Miscellaneous Status registers ProSoft Technology Inc Page 89 of 153 August 31 2009 MVIS56E MNETR ControlLogix Platform Diagnostics and Troubleshooting Modbus TCP IP Interface Module with Reduced Data Block User Manual 4 4 4 3 2 Config Use the CONFIGURATION menu to view backplane configuration settings for the MVI56E MNETR module The information on this menu corresponds with the configuration information in the MODULE settings in ProSoft Configuration Builder page 53 4 3 3 NIC Status Use the NIC STATUS Network Interface Card menu to view configuration and status information for the MVIS6E MNETR module s Ethernet application port The information on this menu is useful for troubleshooting Ethernet network connectivity problems 4 3 4 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 65 defines a list of static IP addresses that the module will use when an ARP is required Monitoring Backplane Information Use the BACKPLANE menu to view the backplane status information for the MVI56E MNETR module 4 4 1 Backplane Status Click STATUS 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 Even
146. ported 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 OJJ AJOJN gt 15 Force Multiple Coils 16 Preset Multiple Registers ProSoft Technology Inc Page 61 of 153 August 31 2009 MVI56E MNETR ControlLogix Platform Configuring the MVI56E MNETR Module Modbus TCP IP Interface Module with Reduced Data Block User Manual MB Address in Device This parameter specifies the starting Modbus register or bit address in the slave to be used by the command Refer to the documentation of each Modbus slave device for the register and bit address assignments valid for that device The Modbus Function Code determines whether the address will be a register or bit level OFFSET address into a given data type range The offset will be the target data address in the slave minus the base address for that data type Base addresses for the different data types are 00001 or 000001 0x0001 for bit level Coil data Function Codes 1 5 and 15 10001 or 100001 1x0001 for bit level Input Status data Function Code 2 30001 or 300001 3x0001 for Input Register data Function Code 4 40001 or 400001 4x0001 for Holding Register data Function Codes 3 6 and 16 Address calculation examples
147. quires associated ladder logic to pass the data from the processor to the module Pass Through Mode 0 1 20r3 This parameter specifies the pass through mode for write messages 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 If avalue of 1 is entered write messages received will be sent to the processor as unformatted messages If a value of 2 is entered write messages received will be sent to the processor as formatted messages If a value 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 3or 4 This parameter allows you to force 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 Page 54 of 153 ProSoft Technology Inc August 31 2009 Configuring the MVI56E MNETR Module MVI56E MNETR ControlLogix Platform User Manual Modbus TCP IP Interface Module with Reduced Data Block 2 1 4 MNET Client x This section defines general configuration for the MNET Client Master Error Status Pointer 1 to 4990 Starting register locati
148. r ERE 2128 a xime rm BRIS gt wT eel Be ap 2 586 mnm Add On MVIS6 MNETR and MVIS6E MNETR modules AOIS6MNETR Add On For MVIS6 MNETR and 5 AOISGMNETR AOISOMNETR Connection Input Local 1 Data Connechbon Output Local 1 0 Data MNETR MNETR e e e e et e e e e e e The procedure has also imported new User Defined Data Types data objects and the Add On instruction for your project 4 l 4 Favortes A Add on Alarms 5t TmerCouner K Page 38 of 153 ProSoft Technology Inc August 31 2009 Start Here MVI56E MNETR ControlLogix Platform User Manual Modbus TCP IP Interface Module with Reduced Data Block 1 11 5 Connect 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 Refer to your Rockwell Automation documentation for information on other connection methods Connect the right angle connector end of the cable to your controller at the communications port 1 Communications BATTERY aate 2 Connect the straight connector end of the cable to the serial port on your computer Page 39 of 153 ProSoft Technology Inc August 31 2009 MVISGE MNETR ControlLogix Platform Start Here Modbus TCP IP
149. r Manual Response An example response to Read Coil Status is as shown in Figure C2 The data is packed one bit for each coil The response includes the Server address function code quantity of data characters the data characters and error checking Data will be packed with one bit for each coil 1 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 ByteCount Data Coil Data Coil Data Coil Data Coil Data Coil Error Check Status 20 Status28 Status36 Status 4410 Status52to Field to 27 to 35 to 43 51 56 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 wh
150. rameter specifies the number of registers to be transferred from the module to the processor Valid entry for this parameter is 0 to 5000 Write Register Start 0 to 4999 This parameter specifies the starting register in the module where the data will be transferred from the processor to the module Valid range for this parameter is 0 to 4999 Write Register Count 0 to 5000 This parameter specifies the number of registers to transfer from the processor to the module Valid entry for this parameter is 0 to 5000 words ProSoft Technology Inc Page 53 of 153 August 31 2009 MVI56E MNETR ControlLogix Platform Configuring the MVIS6E MNETR Module Modbus TCP IP Interface Module with Reduced Data Block User Manual 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 re
151. rnal database is user defined The following flow chart and table describe the flow of data into and out of the module Processor Memory Backplane Interface MNetR Memory Controller Ego Database Modbus Addresses Addresses 1 0 40001 a 1 Register Data storage Register 1 i 4999 i 1 Status lt Status gt Status from Module Client Configuratio Command List Event Cmd Event 1 Event Data 1 Data 1 Data B 3l i i Command gt commana Control 4 Control a Control i 1 1 Theclient driver obtains configuration data from the MNET CFG file when the module restarts The configuration data obtained 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 the other nodes on the Modbus TCP IP network ProSoft Technology Inc Page 115 of 153 August 31 2009 MVIS56E MNETR ControlLogix Platform Reference Modbus TCP IP Interface Module with Reduced Data Block User Manual 2 When configured the client driver begins transmitting read and or write commands to the other nodes on the network If writing data to another node the data for the write command is obtained from the module s internal database
152. s 0 0 Name Remote ENBT2 1 1 Data Type AB 1756 MODULE INT 84Bytes I 0 0 AOISBMNETR sj Remote_ENBT2 1 1 AB 1756_MOD Create New Discard Create New Discard FE Remote ENBT2 1 C FE Remote ENBT2 1 I 4 60 0 Remote_ENBT2 1 AB 1756_MOD AB 1756 MODULE C 0 AB 1756 MODULE 0 AB 1756 MODULE 20 AB 1756_ENET_17SLOT 1 0 Remote_ENBT2 qName Remote ENBT2 1 0 EL Data Type AB 1756 MODULE INT 84Bytes O 0 Description Program Show Show All Discard Page 36 of 153 ProSoft Technology Inc August 31 2009 Start Here MVI56E MNETR ControlLogix Platform User Manual Modbus TCP IP Interface Module with Reduced Data Block o Ifyou are installing the module in a Local Rack verify that the slot number is correct for the module Import Configuration Tags Data Types Add On Instructions 4 ADISEMNETR Create New 4B 1756_MOD Discard Local1 0 AB 1755 MOD Discard MNETRModul Create New Name Sf AlizsFor_ Data Type 5 Click OK to confirm the import RSLogix will indicate that the import is in progress Importing Creating routine Prescan ProSoft Technology Inc Page 37 of 153 August 31 2009 MVISGE MNETR ControlLogix Platform Start Here Modbus TCP IP Interface Module with Reduced Data Block User Manual When the import is complete you will see the new Add On Instruction rung in the ladde
153. s TCP IP Interface Module with Reduced Data Block User Manual Name Data Type Description MBOffset INT The starting word address for the Modbus data set MBMsgLen INT The length of the Modbus message in bytes mbdouble DINT Reserved MBCoil MNETROoilArray Conversion from Bool to INT data types MNETROCoilArray Name Data Type Description Boolean BOOL 416 Conversion from Bool to INT data types 3 2 3 1 4 MNETRUTIL This data object stores the variables required for the data transfer between the processor and the MVIS6E MNETR module The following table describes the structure of this object Name Data Type Description LastRead INT Index of last read block LastWrite INT Index of last write block Blocklndex INT Computed block offset for data table ReadDataSizeGet INT Gets ReadData Array Length WriteDataSizeGet INT Gets WriteData Array Length The LastRead tag stores the latest Read Block ID received from the module The LastWrite tag stores the latest Write Block ID to be sent to the module The Block Index tag is an intermediate variable used during the block calculation Modbus Message Data During pass through operation write messages received at the MVIS6E MNETR server write messages through to the processor It is the responsibility of the ladder logic to process the message received using this feature Two data objects are required for this mode a variable to hold the length of the message and a buffer to hol
154. s usually a good starting value Click OK to confirm Wil Module Properties Local 2 1756 MODULE 1 1 General Connection Module Info Backplane Requested Packet Interval RPI 5 024 ms 0 2 750 0 ms Inhibit Module Major Fault On Controller If Connection Fails While in Run Mode Module Fault Status Offline Cancel The MVI56E MNETR module is now visible in the I O CONFIGURATION section 1 0 Configuration 9 1756 Backplane 1756 A4 fa 0 1756463 My_Controller 1756 MODULE MNETR 1 ProSoft Technology Inc Page 33 of 153 August 31 2009 Start Here MVISGE MNETR ControlLogix Platform User Manual Modbus TCP IP Interface Module with Reduced Data Block 1 11 4 Import Add On Instruction 1 In the 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 00 My Controller 1756 L63 MaknProgram MainRoutine Ble Est View Search Lege Communications Toss Ddos 01218 amp 1318 1 gt Gig aa 1 M RUN Path crore z or ka 3 T NN 2 a gt fevernes K Auns 34 153 ProSoft Technolog
155. set the coil ON and the value zero will turn it OFF all other values are 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 In ProSoft products the coil is only affected if the necessary ladder logic is implemented Note The Modbus protocol does not include standard functions for testing or changing the DISABLE state of discrete inputs or outputs Where applicable this may be accomplished via device specific Program commands 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
156. steps 1 Click OK to dismiss the error message ProSoft Technology Inc Page 67 of 153 August 31 2009 MVI56E MNETR ControlLogix Platform Configuring the MVI56E MNETR Module Modbus TCP IP Interface Module with Reduced Data Block User Manual 2 Onthe DOWNLOAD dialog box click BROWSE DEVICES 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 4 Close ProSoft Discovery Service 5 Click DOWNLOAD to transfer the configuration to the module 2 3 Using ClPconnect to Connect to the Module You can use ClPconnect to connect a PC to the ProSoft Technology MVI56E MNETR module over Ethernet using Rockwell Automation s 1756 ENBT EtherNet IP module This allows you to configure the MVIBGE MNETR module and network upload and download files and view module diagnostics from a PC RSLinx is not required when you use ClPconnect All you need are The IP addresses and slot numbers of any 1756 ENBT modules in the path ControlNet node numbers and slot numbers of any 1756 CNBx ControlNet Bridge modules in the path slot number of the MVI56E MNETR in the destination ControlLogix chassis the last ENBT CNBx and chassis in the p
157. t lt 00 gt lt 00 gt lt 9C gt lt 87 gt lt R gt 0B 10 04 07 Config 00 01 B1 92 lt R gt lt 0B gt lt 03 gt lt 04 gt lt 07 gt lt 00 gt lt 01 gt lt 34 gt lt 51 gt lt R gt 0B 03 02 00 00 20 NIC Status 45 lt R gt lt 0B gt lt 10 gt lt 04 gt lt 08 gt lt 00 gt lt 01 gt lt 02 gt lt 00 gt lt 00 gt lt 9C gt lt 7 8 gt lt R gt 0B 10 04 08 00 01 81 91 lt R gt lt 0B gt lt 03 gt lt 04 gt lt 08 gt lt 00 gt lt 01 gt lt 04 gt lt 52 gt lt R gt 0B 03 02 00 00 20 45 R4 ea Static ARP lt 0B gt lt 10 gt lt 04 gt lt 09 gt lt 00 gt lt 01 gt lt 02 gt lt 00 gt lt 00 gt lt 9D gt lt A9 gt lt R gt 0B 10 04 09 00 01 00 51 Version lt R gt lt 0B gt lt 03 gt lt 04 gt lt 09 gt lt 00 gt lt 01 gt lt 55 gt lt 92 gt lt R gt 0B 03 02 00 00 20 45 lt R gt lt 0B gt lt 10 gt lt 04 gt lt 0A gt lt 00 gt lt 01 gt lt 02 gt lt 00 gt lt 0C gt lt 9D gt lt 9A gt lt R gt 0B 10 04 0A 00 01 20 51 lt R gt lt 0B gt lt 03 gt lt 04 gt lt 0A gt lt 00 gt lt 01 gt lt A5 gt lt 92 gt lt R gt 0B 03 02 00 00 20 45 gt lt gt 08 lt gt 10 lt gt 04 lt gt 08 lt lt 00 gt lt 01 gt lt 02 gt lt 00 gt lt 00 gt lt 9C gt lt 48 gt lt R gt 0B 10 04 0B 00 01 71 91 lt R gt lt 0B gt lt 03 gt lt 04 gt Path Ethernet 105 102 0 25 The Data Analyzer can display the following special characters
158. t 10 gt lt 04 gt lt 02 gt lt 00 gt lt 01 gt 2 22 d lt 01 gt lt 24 gt lt 50 gt lt gt lt R gt lt 0B gt lt 10 gt lt 04 gt lt 03 gt lt 00 gt lt 01 gt lt 02 gt lt 00 gt Config lt 00 gt lt 9D gt lt 03 gt lt R gt 0B 10 04 03 00 01 FO 53 lt R gt lt 0B gt lt 03 gt lt 04 gt lt 03 gt lt 00 gt lt 01 gt lt 7 5 gt Status lt 90 gt lt R gt 0B 03 02 00 0C 20 45 lt R gt lt 0B gt lt 1L0 gt lt 04 gt lt 04 gt lt 00 gt lt 01 gt lt 02 gt lt 00 gt lt 00 gt lt 9C gt lt B4 gt lt R gt 0B 10 04 04 00 01 41 92 lt R gt lt 0B gt lt 03 gt lt 04 gt lt 04 gt lt 00 gt lt 01 gt lt C4 gt lt 51 gt lt R gt MNET SERVER 08 03 02 00 00 20 45 lt R gt lt 0B gt lt 10 gt lt 04 gt lt 05 gt lt 00 gt lt 01 gt lt 02 gt lt 00 gt lt 00 gt lt 9D gt lt 65 gt lt R gt Config 10 04 05 00 01 1C 52 lt R gt lt 0B gt lt 03 gt lt 04 gt lt 05 gt lt 00 gt lt 01 gt lt 95 gt lt 91 gt lt R gt 0B 03 Status 02 00 00 20 45 lt R gt lt 0B gt lt 10 gt lt 04 gt lt 06 gt lt 00 gt lt 01 gt lt 02 gt lt 00 gt lt 00 gt lt 9D gt lt 56 gt lt R gt 0B 10 04 06 00 01 EO 52 08 lt 08 lt gt 03 lt gt 04 lt gt 06 lt gt 00 lt gt 01 lt gt 65 lt gt 91 lt gt 8 gt lt gt 03 02 00 Eaa MODULE 00 20 45 lt R gt lt 0B gt lt 10 gt lt 04 gt lt 07 gt lt 00 gt lt 01 gt lt 02 g
159. t 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 the members of the MVI56E MNETR Status object page 119 Page 90 of 153 ProSoft Technology Inc August 31 2009 Diagnostics and Troubleshooting User Manual MVI56E MNETR ControlLogix Platform Modbus TCP IP Interface Module with Reduced Data Block 4 5 Monitoring Database Information Use the DATABASE menu to view the contents of the MVIS56E MNETR module s internal database The data locations on this menu corresponds with the MVI56E MNETR Database Definition You can view data in the following formats 2 Refresh Counter 24 Refresh Counter 1 4 0 00000000E 000 0 00000000E 000 0 0 0 0 0 00000000E 000 00000000E 000 00000000E 000 00000000E 000 00000000E 000 DATABASE DISPLAY 0 to 99 ASCII ER2 0104092101 S iz asasas Decimal DATABASE DISPLAY 0 to 99 DECIMAL 5520 17229 21061 11826 12592 13360 14640 12594 12592 0 3566 3567 0 0 0 892 3567 0 0 0 28075 28074 28074 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 Float DATABASE DISPLAY 0 to 49 FLOAT 1 42363105 028 2 118094195 011 2 56376298E 009 1 68041093E 004 1 25976732E 042 1 71398323E 030 0 00000000E 000 0 00000000E 000 1 71398323E 030 0 000000005 000 0 00000000E 000
160. t most bits are provided as zeros to fill the 8 bit format 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 fof Regs Hi Data 401 Regs Lo Error Check Field 11 08 00 6B 00 03 CRC ProSoft Technology Inc Page 123 of 153 August 31 2009 MVI56E MNETR ControlLogix Platform Reference Modbus TCP IP Interface Module with Reduced Data Block User Manual 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 t
161. te of shipment 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 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 used replacement parts 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 ProSoft Technology Inc Page 147 of 153 August 31 2009 MVISGE MNETR ControlLogix Platform Support Service amp Warranty Modbus TCP IP Interface Module with Reduced Data Block User Manual 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 6 3 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 Pr
162. ted If code 2 is utilized no swap the data received in the message is presented in the order received by the module 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 9956 passes word type data for functions 6 and 16 Block 9957 passes a floating point message for functions 6 and 16 Block 9958 is utilized when Modbus function 5 data is received Block 9959 is employed when function 15 is recognized Block 9960 is used for function 22 and Block 9961 is used for function 23 requests Block 9970 is utilized for function 99 The following tables describe the format for the read blocks Formatted Formatted Pass Through Command Blocks Read Block Offset Description Length 0 9956 9957 9958 9960 or 9961 1 1 Number of word registers in Modbus data set 1 2 Starting address for Modbus data set 1 3 to 40 Modbus data set 38 41 9956 9957 9958 9960 or 9961 1 Formatted Pass Through Command Blocks Read Block Offset Description Length 0 9959 1 1 Number of word registers in Modbus data set 1 2 Starting word address for Modbus data set 1 3 to 21 Modbus data set 19 22 to 40 Bit mask to use with the data set Each bit to be considered 19 with the data set will have a value of 1 in the mask Bits to i
163. ter 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 3 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 6 3 10 Controlling Law and Severability This Warranty shall be governed by and construed in accordance with the laws of the United States and the domestic laws of the State of California without reference to its conflicts of law provisions If for any reason a court of competent jurisdiction finds any provisions of this Warranty or a portion thereof to be unenforceable that provision shall be enforced to the maximum extent permissible and the remainder of this Warranty shall remain in full force and effect Any cause of action with respect to the Product or Services must be instituted in a court of competent jurisdiction in the State of California Page 150 of 153 ProSoft Technology Inc August 31 2009 Index User Manual MVIS56E MNETR ControlLogix Platform Modbus TCP IP Interface Module with Reduced D
164. th Editor gt Settings Wy Paint Hc ProSoft Discovery Service Search 2 Windows Media Player Help and Support Run ShutDown 12 start ProSoft Technology Inc Page 49 of 153 August 31 2009 MVI56E MNETR ControlLogix Platform Configuring the MVIS6E MNETR Module Modbus TCP IP Interface Module with Reduced Data Block User Manual 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 Untitled ProSoft Configuration Builder 2 88 Default Location View Project Tools Help Default Project Name Status Default Module Please Select Module Type Unknown Product Line 1 Last Change Last Download Module Information Last Change Never Last Download Never Application Rev OS Rev Loader Rev MAC Address ConfigEdit Version 2 1 6 Build 4 Module Configuration Module Module Type Module Name Default Module Default Module Page 50 of 153 ProSoft Technology Inc August 31 2009 Configuring the MVIBGE MNETR Module MV
165. th Reduced Data Block User Manual 5 2 3 Backplane Data Transfer The MVI56E MNETR module communicates directly over the ControlLogix backplane Data is paged between the module and the ControlLogix processor across the backplane using the module s input and output images The update frequency of the images is determined by the scheduled scan rate defined by the user for the module and the communication load on the module Typical updates are in the range of 1 to 10 milliseconds This bi directional transference of data is accomplished by the module filling in data in the module s input image to send to the processor Data in the input image is placed in the Controller Tags in the processor by the ladder logic The input image for the module is set to 42 words This data is transferred in the scheduled I O timeslot The processor inserts data to the module s output image to transfer to the module The module s program extracts the data and places it in the module s internal database The output image for the module is set to 42 words This data is transferred in the scheduled I O timeslot The following illustration shows the data transfer method used to move data between the ControlLogix processor the MVISB6E MNETR module and the Modbus TCP IP Network ControlLogix Processor MVI56E MNETR Module ControlLogix Processor Controller Tags Ladder Logic Transfers Data from module s input image to data areas in the processor Input Im
166. tion Export Configuration File s Load Config File Download from PC to Device Upload from Device to PC This action opens the DIAGNOSTICS dialog box If there is no response from the module ProSoft Configuration Builder Cannot Connect to IP Address 1 Click the SET UP CONNECTION button to browse for the module s IP address sana Click to set up connection ProSoft Technology Inc Page 87 of 153 August 31 2009 MVI56E MNETR ControlLogix Platform Diagnostics and Troubleshooting Modbus TCP IP Interface Module with Reduced Data Block User Manual 2 On the CONNECTION SETUP dialog box click the TEST CONNECTION button to verify if the module is accessible with the current settings Connection Setup Select Connection Type Ethernet 182 168 0 250 ProSoft Discovery Service PDS Browse Device s ELM Test Connection Cancel You can also use ClPconnect to connect to the module through a 1756 ENBT card Connection Setup Select Connection Type 2 371 v Ethemet ETHER ProSoft Discovery Service PDS E CiPconnect 192 168 0 100 p 1 s 0 CIP Path Edit Test Connection Cancel Refer to Using ClPconnect to Connect to the Module for information on how to construct a CIP path page 68 Page 88 of 153 ProSoft Technology Inc August 31 2009 Diagnostics and Troubleshooting MVI56E MNETR ControlLogix Platform User Manual Modbus TCP
167. tion for this example and click CONSTRUCT CIP PATH to build the path in text format 1 Path Editor m C a T Connect PATH EDITOR Source Module IP Source Module Node Destination Module No Source Module PEE Address Destination Module Slot Number B cseener 12162010 1756 CNB EE UN aes 0 MVI56 Module 192 168 0 100 1 6 Add Rack Delete Rack Construct CIP Path OK Cancel Click OK to close the CIP PATH EDITOR and return to the DOWNLOAD dialog box ProSoft Technology Inc Page 75 of 153 August 31 2009 MVI56E MNETR ControlLogix Platform Configuring the MVI56E MNETR Module Modbus TCP IP Interface Module with Reduced Data Block User Manual 3 Check the new path in the download text box Download files from PC to module m STEP 1 Select Communication Path Select Connection Type 1756 ENBT v e Device s Ethernet 5 1 STEP 2 Transfer File s DOWNLOAD Abo Test Connection Ok Cancel 4 Click TEST CONNECTION to verify that the physical path is available The following message should be displayed upon success Download files from PC to module m STEP 1 Select Communication Path Select Connection Type 1756 ENBT v Ethernet CIPconnect Successfully Connected STEP 2 Transfer File DOWNLOAD Connection Ok Cancel Page 76 of 153 ProSoft Technology Inc August 31 2009 Configuring the MVI56E MNETR Module MVI56E MNET
168. tions The module is configured in the processor 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 Page 100 of 153 ProSoft Technology Inc August 31 2009 MVIS56E MNETR ControlLogix Platform User Manual Modbus TCP IP Interface Module with Reduced Data Block 5 Reference In This Chapter S 101 se Functional OVervIew 103 Ethernet Cable Specifications 118 gt MVI56E MNETR Status Data 119 Modbus Protocol Specification esee 121 Using the Rung Import with Utility Add On 132 gt Adding the Module to an Existing 141 Using the Sample Program RSLogix Version 15 and earlier 144 5 1 Product Specifications The MVI56E MNETR Modbus TCP IP Client Server Communication Module allows Rockwell Automation ControlLogix processors to interface easily with other Modbus TCP IP compatible devices Compatible devices include Modicon PAC s as well as a wide var
169. to build the command 3 Presuming successful processing by the node specified in the command a response message is received into the client driver for processing 4 Data received from the node on the network is passed into the module s internal database assuming a read command 5 Status data is returned to the processor for the client and a Command List error table can be established in the module s internal database Client Command List In order for the client to function the module s Client Command List must be defined 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 Select the number of words to be transferred 1 to 100 Poll Delay 1 10 seconds Client Command Errors You can use the MNET 0 Client Command Error Pointer in the MNET CFG file to set the database offset register where all command error codes will be stored This means that the first register refers to command 1 and so on Offset Description 1 Command 1 Error 2 Command 2 Error 3 Command 3 Error For every
170. ts power source ensure that the battery within the module is fully charged the BATT LED on the front of the module goes OFF when the battery is fully charged If the battery is allowed to become fully discharged the module will revert to the default BIOS and clock settings Note The battery is not user replaceable or serviceable 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 the product documentation or support please write or call 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 ProSoft Technology Inc 2009 All Rights Reserved MVI56E MNETR User Manual August 31 2009 ProSoft Technology ProLinx inRAx 9 ProTalk and RadioLinx are Registered Trademarks of ProSoft Technology Inc All other brand or product names are or may be trademarks of and are used to identify products and services of their respective owners ProSoft Technology Product Documentation In an effort to conserve paper ProSoft Technology no longer includes printed manuals with our product shipments User Manuals Datasheets Sample Ladder Files and Configuration Files are provided on the enclosed CD ROM and are available at no charge from our web site www prosoft technology com Printed
171. uch as a Modicon PLC or an HMI application issues a read or write command to the module s node address The server driver qualifies the message before accepting it into the module 3 When the module accepts the command the data is immediately transferred to or from the internal database in the module 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 pass through feature is utilized the write message is transferred directly to the processor and is not written to the module s database 4 When the data processing has been completed in Step 3 the response is issued to the originating master node 5 Counters are available in the Status Block that permit the ladder logic program to determine the level of activity of the Server Driver Register Register Data storage After the server socket is open it must receive messages within a one minute period or else it will close the socket After closing the socket will be reused An exception to this normal mode is when the pass through mode is implemented In this mode all write requests will be passed directly to the processor and will not be placed in the database This permits direct remote control of the processor without the intermediate database This mode is especiall
172. ule The module requires 800mA of available 5 VDC power Rockwell Automation RSLogix 5000 programming software o Version 16 or higher required for Add On Instruction o Version 15 or lower must use Sample Ladder available from www prosoft technology com Rockwell Automation RSLinx communication software version 2 51 or higher ProSoft Configuration Builder PCB included ProSoft Discovery Service PDS included in PCB Pentium Il 450 MHz minimum Pentium IIl 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 Page 10 of 153 ProSoft Technology Inc August 31 2009 Start MVI56E MNETR ControlLogix Platform User Manual Modbus TCP IP Interface Module with Reduced Data Block 128 Mbytes of RAM minimum 256 Mbytes of RAM recommended 100 Mbytes of free hard disk space or more based on application requirements 256 color VGA graphics adapter 800 x 600 minimum resolution True Color 1024 x 768 recommended CD ROM drive Note 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
173. ule for ControlLogix Hes MVISGE MNETR b User tanuels RESQURGES b Add On Software Module Nama 566 MNETR Prosoft Important The temporary IP address is only valid until the next time the module is initialized Please refer to the MVI56E MNETR User Manual for information on how to set the module s permanent IP address Page 24 of 153 ProSoft Technology Inc August 31 2009 Start Here MVI56E MNETR ControlLogix Platform User Manual Modbus TCP IP Interface Module with Reduced Data Block 1 10 Upload the Add On Instruction from the Module Configuration and control information for the MVI56E MNETR module is provided as an Add On Instruction for RSLogix 5000 version 16 or higher 5 7 DOWNLOADS MVIS6E MNETR Safety Info Add on Software Setup Guide RESOURCES User Manuals Pr n A ung Import with Sample Program Add On Instruction oue enim Rung Impert with Utility Add On instruction Optional Technology Software 9 gt How to install the Add On Instruction Rock 1 Datasheet eckwe Automation FUNCTIONS Click to upload Add On Instruction Modbus Firmware Organization Upgrade Set Date A Time Technical Support Homepage Lo Two Add On Instructions are provided RUNG IMPORT WITH SAMPLE PROGRAM ADD ON INSTRUCTION MVIBe EMNETR AddOn Rung Version gt L5X which includes the User Defined Data Types data objects
174. upport ProSoft Technology Inc Page 99 of 153 August 31 2009 MVIS56E MNETR ControlLogix Platform Modbus TCP IP Interface Module with Reduced Data Block Diagnostics and Troubleshooting User Manual 4 9 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 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 Verify that all modules in the rack are configured in the ladder logic Module Errors Problem Description Steps to take BP ACT LED remains off or blinks slowly MVI56E modules with scrolling LED display lt Backplane Status gt condition reads ERR This indicates that backplane transfer operations are failing Connect to the module s Configuration Debug port to check this To establish backplane communications verify the following items The processor is in Run mode The backplane driver is loaded in the module The module is configured for read and write block data transfer The ladder logic handles all read and write block situa
175. ut data Read Data Area Use the Initialize Output Data parameter in the configuration file to bring the module to a known state after a restart operation The following table describes the structure of the request block Offset Description Length 0 1000 to 1124 1 1 to 40 Spare 40 41 1000 to 1124 1 The block number in word 20 of the block determines the data set of up to 40 output words to transfer from the processor Ladder logic in the processor must recognize these blocks and place the correct information in the output image to be returned to the module ProSoft Technology Inc Page 107 of 153 August 31 2009 MVI56E MNETR ControlLogix Platform Reference Modbus TCP IP Interface Module with Reduced Data Block User Manual The following table describes the structure of the response block Offset Description Length 0 1000 to 1124 1 1 to 40 Output Data to preset in module 40 41 Spare 1 Command Control Blocks Command Control Blocks are special optional blocks used to request special tasks from the module The current version of the software supports four command control blocks event command control command control warm boot and cold boot Note Event Commands and Command Control are not needed for normal Modbus command list polling operations and are needed only occasionally for special circumstances Event Command Event command control blocks send Modbus TCP IP commands directly fr
176. xpects to receive or will send one complete 32 bit floating point value for each count of one 1 then set this parameter to YES especially if the Master must read or write from Modbus addresses above ProSoft Technology Inc Page 55 of 153 August 31 2009 MVI56E MNETR ControlLogix Platform Configuring the MVIS6E MNETR Module Modbus TCP IP Interface Module with Reduced Data Block User Manual gateway address 3999 virtual Modbus address 44000 or 440000 When set to YES the Slave 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 Master for write commands Example Count 10 Slave driver will send 20 16 bit registers for 10 total 32 bit floating point values If however the remote Master 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 Float Start and Float Offset parameters to appropriate values whenever the Float Flag parameter is set to YES Float Start 0 to 65535 This parameter defines the first register of floating point data All requests with register values greater than or equal to this value will be considered floating point data requests This parameter is only used if the Float Flag is enabled
177. y 2 2 2 2 2 lt By Category By Vendor Favorites Note If you are prompted to Select Major Revision choose the lower of the available revision numbers ProSoft Technology Inc Page 27 of 153 August 31 2009 MVISGE MNETR ControlLogix Platform Start Here Modbus TCP IP Interface Module with Reduced Data Block User Manual 3 Name the ENBT A module then set the IP Address and slot location in the local rack with the ControlLogix processor New Module Type Vendor Parent Name Description Slot Revision 1756 ENBT 4 1756 10 100 Mbps Ethemet Bridge Twisted Pair Media Allen Bradley Local LocalENBT1 PAddress 192 168 10 120 Address Host Name C Host Name 1 1 1 Electronic Keying Compatible Keying v Open Module Properties Cancel 4 Click OK 5 Next select the 1756 ENBT module that you just created in the Controller Organization pane and click the right mouse button to open a shortcut menu On the shortcut menu choose NEW MODULE 3 6 Controller My_Controller A Controller Tags Controller Fault Handler Power Up Handler Tasks Motion Groups Ungrouped Axes Add On Instructions Data Types 28 Trends 3 6 1 0 Configuration 9 1756 Backplane 1756 A4 fa 0 1756 163 Controller Ex 5 New Module Cut Ctrl x Copy Ctrl C Delete Del Cross Reference Ctrl4E
178. y Inc August 31 2009 Start Here MVI56E MNETR ControlLogix Platform User Manual Modbus TCP IP Interface Module with Reduced Data Block 4 Navigate to the location on your PC where you saved page 25 the Add On Instruction for example My Documents or Desktop Select the MVIB6 E MNETR ADDON RUNG VERSION gt L5xX file Import Rung Look in Desktop 2 9 My Computer My Documents amp 9 My Network Places MVI56 E MNETR_AddOn_Rung_v1_1 L5x My Computer File name WVISEMNETR AddOn Rung vi 115 My Network Files of type RSLogx 5000 XML Files L5X Places This action opens the IMPORT CONFIGURATION dialog box showing the controller tags that will be created ProSoft Technology Inc Page 35 of 153 August 31 2009 MVISGE MNETR ControlLogix Platform Modbus TCP IP Interface Module with Reduced Data Block Start Here User Manual o Ifyou are installing the module in a Remote Rack open the dropdown menus for the Input and Output tags and select the MNETR module in the remote rack Import Configuration Tags Data Types Add On Instructions 8 Remote_ENBT2 1 8 F Remote_ENBT2 1 1 jg Ei Remote ENBT2 1 0 g FEj Remote ENBT2 I g FEj Remote ENBT2 O Controller Program Show Show All Import Configuration Tags Data Types Add On Instructions g ADISEMNETR AB 1756_MODULE C 0 AB 1756_MODULE_INT_84Bytes 1 0 AB 1756_MODULE_INT_84Byte
179. y useful for Master devices that do not send both states of control For example a SCADA system may only send an on command to a digital control point and never send the clear state The SCADA system expects the local logic to reset the control bit Pass through must be used to simulate this mode The Page 114 of 153 ProSoft Technology Inc August 31 2009 MVIS56E MNETR 4 ControlLogix Platform User Manual Modbus TCP IP Interface Module with Reduced Data Block following illustration describes the data flow for a slave port with pass through enabled Processor Memory Backplane Interface MNetR Module comet teas Database Modbus Addresses Addresses 0 40001 el lt 1 Register Register Write Functions 1 Data qe storage 1 Read Functions Server Driver 4999 45000 PE trom Mong S Status e m Status Configuration Client Driver In the client driver the 56 module issues read or write commands to servers on the Modbus TCP IP network These commands are user configured in the module via the Client Command List received from the module s configuration file MNET CFG or issued directly from the ControlLogix processor event command control Command status is returned to the processor for each individual command in the command list status block The location of this status block in the module s inte
180. yzer 93 Data Analyzer Tips 95 Data Flow between MVIS6E MNETR Module and ControlLogix Processor 3 Diagnostics Function Code 08 6 Diagnostics and Troubleshooting 7 85 Disclaimer of all Other Warranties 149 Disclaimer Regarding High Risk Activities 148 Download the Project to the Module 67 Download the Sample Program to the Processor 48 143 Duplex Speed Code 54 E Enable 59 Error Status Pointer 53 55 Ethernet Cable Configuration 118 Ethernet Cable Specifications 8 Ethernet Configuration 66 Ethernet LED Indicators 99 Ethernet Performance MVI56E Modules 118 Event Command 108 Example 1 Local Rack Application 71 Example 2 Remote Rack Application 74 Example and state diagram 127 F Failure Flag Count 54 Float Flag 55 63 Float Offset 56 64 Float Start 56 64 Force Multiple Coils Function Code 15 128 Force Single Coil Function Code 05 5 Formatted 112 Functional Overview 7 103 Functional Specifications 102 G General Specifications 101 Guide to the MVIBGE MNETR User Manual 7 H Hardware MAC Address 65 Hardware Specifications 102 Holding Register Offset 64 How to Contact Us Technical Support 145 146 ProSoft Technology Inc August 31 2009 Page 151 of 153 MVI56E MNETR 4 ControlLogix Platform Modbus TCP IP Interface Module with Reduced Data Block Index User Manual Import Add On Instruction 3

MVI56E-MNETR

Contents

Download Pdf Manuals

Related Search

Related Contents