Home

MVI56-MNETC User Manual

1. SSSS555588 Add Ladder Element Alt Ins Rung 0 of 1 Page 28 of 153 ProSoft Technology Inc October 26 2011 MVI56 MNETC ControlLogix Platform Configuring the MVI56 MNETC Module Modbus TCP IP Multi Client Communication Module User Manual 8 Select the MVIS6MNETC_ADDON_RUNG_V1_5 L5X file and then click IMPORT Import Rung Look in Desktop amp ex FEY p My Computer My Documents Quy Network Places Downloads MVI56 E MNETC_AddOn_Rung_v1_5 L5X lt File name MVI56 E MNETC_AddOn_Rung_v1_5 L5X v My Network Files of type RSLogix 5000 XML Files L5X X Places 9 This action opens the Import Configuration window which shows the tags that will be imported Import Configuration Tags Data Types Add On Instructions AOISBMNETC Create New Local 1 1 AB 1756_MOD Use Existing Local1 0 AB 1756_MOD Use Existing MNETC MNETCMODU Create New ProSoft Technology Inc Page 29 of 153 October 26 2011 Configuring the MVI56 MNETC Module User Manual MVI56 MNETC ControlLogix Platform Modbus TCP IP Multi Client Communication Module 10 Associate the I O connection variables to the correct module The default values are Local 1 I and Local 1 O so these require change Import Configuration Tags Data Types Add On Instructions ADISEMNETC_2 E k Local 1 g F Local 1 0 j Local 2 0 Co
2. ccccecesceceeeeeeeeeeeeeeeeeneeeseaeeseeeeseaeeseaeeeseaeeseeeeseeeseas 69 4 1 3 TOUDICSNOOUNG asena locate seg Mace Sees eek Loe ee Lee ee este 69 4 2 Using ProSoft Configuration Builder PCB for Diagnostics ccceeeeeeeeeeees 71 4 2 1 Using the Diagnostic Window in ProSoft Configuration Builder c ceee 71 4 2 2 Malin Menus meien east iett chiens ee ea eee ie ee 74 4 2 3 Modbus Database View MeNnu cccccceeeseeeeeeenneeeeteeeeeetenaeeeesenaeeeeeenaeeeesenaeeeeee 77 4 2 4 Network M nUis i eis testovert ivcevet feitpeer ixectis E Goer aiiiateeriiivasititiees ied 78 4 3 Reading Status Data from the Module c ccceceeeeeeeeeeeeeseeeeeeeeeeaeeseneeeseeeseaees 80 4 3 1 Status Data Detinitthons ayes irai ae eana ea aaa ara Ea E EAREN aa 81 4 3 2 Configuration Error Word c cccccceceseeeeeeeeeeeeceeeeeeeeeeeaeeseaeeeseaeeseaeeeseaeeseeeeesaeesaas 83 4 3 3 Client Command Errors cc cccecceeeeeeeeeeeeeeeeeeeeaeeeeeeeeeeaeeeeaeeeseaeeseaeeesaeeseueeeseaeesaas 84 5 Reference 87 5 1 Product Specifications a a a a aa a a ar a a atA 88 5 1 1 General Specifications ccccceecceceeceeeneeeeeeeeeeaeeeeeeeeseaeeteaneeseaeeseaeeeeeaeeseaeesseaeeseas 88 5 1 2 MOdbUSHTG RIP Ait NEA sts Gedte chi A R E 1 adele tale ct A 88 5 1 3 Functional Specifications cccccceceeceeeeeeeneeeeeeeeeeeeeceaeeeseaeeseeeeeeeeseaeeeseaeessueeeeaaes 89 5 1 4 Hardware Specifications
3. Page 42 of 153 ProSoft Technology Inc October 26 2011 MVI56 MNETC ControlLogix Platform Configuring the MVI56 MNETC Module Modbus TCP IP Multi Client Communication Module User Manual 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 0 there will be no delay MBAP Port Override YES or No If this parameter is set to YES all messages generated by the Client driver will be MBAP format messages to all Service Port values If this parameter is set to No default value or is omitted from the configuration file all messages sent to Service Port 502 will be MBAP format messages and all other Service Ports values will use the encapsulated Modbus message format MNET Each Client is configured independently in the configuration file This parameter applies to firmware version 1 05 and above For downward compatibility you may omit this parameter from the Client s configuration 2 4 5 MNET Client x Commands The MNET Client x Commands section of the configuration sets the Modbus TCP IP Client command list This command list polls Modbus TCP IP server devices attached to the Modbus TCP IP Client port The module supports numerous commands This
4. 3 Ladder Logic In This Chapter se CONTOIEr E e EEE ch ees teak scence NUS a os ae 56 User Defined Data Types UDTS 0 eee eeseeeeesneeeeeeneeeeseneeeeesnaeetenea 58 S Using Controller Tags s m iein ideiei o aaia aaas 60 Controller Tag OvervieW ssseeeseessseseessreseessitsrnstrnrinntinntnnstnnstnnsrnnee 61 Ladder logic is required for managing communication between the MVI56 MNETC module and the processor The ladder logic handles tasks such as Module backplane data transfer Special block handling Status data receipt Additionally a power up handler may be needed to initialize the module s database and may clear some processor fault conditions The sample Import Rung with Add On Instruction is extensively commented to provide information on the purpose and function of each user defined data type and controller tag For most applications the Import Rung with Add On Instruction will work without modification ProSoft Technology Inc Page 55 of 153 October 26 2011 Ladder Logic MVI56 MNETC ControlLogix Platform User Manual Modbus TCP IP Multi Client Communication Module 3 1 Controller Tags Data related to the MVI56 MNETC is stored in the ladder logic in variables called controller tags Individual controller tags can be grouped into collections of controller tags called controller tag structures A controller tag structure can contain any combination of Individual controller tag
5. 5 7 4 Downloading the Sample Program to the Processor To download the sample program from RSLogix 5000 to the ControlLogix processor Note The key switch on the front of the ControlLogix module must be in the REM position 1 If you are not already online to the processor open the COMMUNICATIONS menu and then choose DOWNLOAD RSLogix will establish communication with the processor 2 When communication is established RSLogix will open a confirmation dialog box Click the DOWNLOAD button to transfer the sample program to the processor Download Eg Download to the controller z Name Controller Type 1756 L63 4 17 6 M13 4 ControlLogix5563 Controller Path AB_ lt DriverName Security lt None gt A The controller is in Remote Run mode The mode will be changed to Remote Program prior to download Cancel Help 3 RSLogix will compile the program and transfer it to the processor This process may take a few minutes 4 When the download is complete RSLogix will open another confirmation dialog box Click OK to switch the processor from PROGRAM mode to RUN mode RSLogix 5000 Done downloading Change controller mode back to Remote Run Note If you receive an error message during these steps refer to your RSLogix documentation to interpret and correct the error Page 140 of 153 ProSoft Technology Inc October 26 2011 MVI56 MNETC ControlLogix Platform Reference Modbus TCP IP Multi Client C
6. MNETCCLIENTSTATS Connection_Input Local 1 1 Data MNETCCMDCONTROL Connection_Output Local1 0 Data if MNETCCONTROL MNETC MNETC E MNETCDATA a E MNETCINITOUTDATA 2 MNETCIPADDRESS i MNETCMODULEDEF MNETCSTATUS MNETCUTIL Gi Strings Add On Defined Og Predefined jg Module Defined Trends 4 gMainRoutine m Rung End of 1 The procedure has also imported new user defined data types data objects and the Add On Instruction for your project C H tot gt cai Favortes Add On Alarms amp Ba A timer counter 7 Save the application and then download the sample ladder logic to the processor Page 26 of 153 ProSoft Technology Inc October 26 2011 MVI56 MNETC ControlLogix Platform Modbus TCP IP Multi Client Communication Module Configuring the MVI56 MNETC Module User Manual Adding Multiple Modules Optional Important If your application requires more than one MVI56 MNETC module in the same project follow the steps below 1 In the I O CONFIGURATION folder click the right mouse button to open a shortcut menu and then choose NEW MODULE 1 0 Configuration SE 31756 Backplane 175644 a fa 0 1756163 My_ New Module f 1 1756 MoDULE 2 Select 1756 MODULE E Select Module Module Vendor Analog Communications Controllers Digital Drives Motion Other 1756 MODULE Specialty Descripti
7. Cancel This field defines whether or not the command is to be executed Value Description No 0 The command is disabled and will not be executed in the normal polling sequence Yes 1 The command is executed each scan of the command list if the Poll Interval Time is set to zero 0 If the Poll Interval time is set the command will be executed when the interval timer expires Important The commands must also be enabled in the ladder logic in order for them to be executed The MNETC CONTROL CmdControl WriteCmaBits x controller tag array holds 16 command bit arrays for each Client If a bit fora specific command is set to zero 0 in the WriteCmaBits x controller tag the command will not be executed regardless of its enabled or disabled state in the configuration For more information see Command Control Blocks page 105 Page 46 of 153 ProSoft Technology Inc October 26 2011 MVI56 MNETC ControlLogix Platform Configuring the MVI56 MNETC Module Modbus TCP IP Multi Client Communication Module User Manual Internal Address 0 to 65535 for bit level addressing or 0 to 4999 for word level addressing This field specifies the database address in the module s internal database to use as the destination for data brought in by a read command or as the source for data to be sent out by a write command The database address is interpreted as a bit address or a 16 bit word register address d
8. 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 Agency Approvals and Certifications Agency Applicable Standards RoHS ATEX EN60079 15 2003 CSA IEC61010 CE EMC EN61326 1 2006 EN61000 6 4 2007 CSA CB Safety CA 10533 CSA IEC 61010 1 Ed 2 CB 243333 2056722 2090408 cULus UL508 UL1604 CSA 22 2 No 142 amp 213 GOST R EN61010 243333 E183151 ME06 MVI56 MNETC ControlLogix Platform Contents Modbus TCP IP Multi Client Communication Module User Manual Contents Your Feedback Please cerisier a eea eaaa T raa revbebsecacdetderedeleters 2 HOw to CONTAC E AEE E E EE EA E 2 ProSoft Technology Product Documentation ccscccsccsessessesseseessesessessessssessessessessessessessesaesseeseeeeens 2 WANING Ssi rea a EE rE OEE EE 3 Battery Lilo AOVISO V eretier e aa aa EE EEEN EEEE AE OEE a EE 3 MAKINO S erotaan ea Aa a E E aE AEA EA A AS RN as 3 Guide to the MVI56 MNETC User Manual 9 1 Start Here 11 1 1 System Requirements cccccccceceeececeneeeeeeeeceaeeeeeaeeseaeeseaeeeseaeeseaeeseeesseaeeseneeeneneess 12 1 2 Package ContentSir i iniia a a a E a Te a T a 13 1 3 Installing ProSoft Configuration Builder Software esseeeseeeseeeseeesreeseerreererereeens 14 1 4 Setting JUMpeErSs cece ceccceeecceeeceeeneeeeeaee cence eeaeeeeaeensaeeeeeeeeseaeeseeeeseaeessaeete
9. Index Support Service and Warranty page 143 Index This section contains Support Service and Warranty information Index of chapters ProSoft Technology Inc October 26 2011 Page 9 of 153 Guide to the MVI56 MNETC User Manual MVI56 MNETC ControlLogix Platform User Manual Modbus TCP IP Multi Client Communication Module Page 10 of 153 ProSoft Technology Inc October 26 2011 MVI56 MNETC ControlLogix Platform Modbus TCP IP Multi Client Communication Module Start Here User Manual 1 Start Here In This Chapter System Requirements Package Content ceeeceeeseeeeseeteneeeeaeeseseeseaeeseeeeeeetaes Installing ProSoft Configuration Builder Software Setting Jumpers Installing the Module in the Rack 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 MVI56 MNETC module s application port s ProSoft Technology Inc October 26 2011 Page 11 of 153 Start Here MVI56 MNETC ControlLogix Platform User Manua
10. The sample application is for a module installed in Slot 1 in a ControlLogix rack The ladder logic uses the slot number to identify the module If you are installing the module in a different slot you must update the ladder logic so that program tags and variables are correct and do not conflict with other modules in the rack To change the slot number 1 Inthe Controller Organization list select the module and then click the right mouse button to open a shortcut menu 2 On the shortcut menu choose PROPERTIES This action opens the Module Properties dialog box E Module Properties Local 1 1756 MODULE 1 1 General Connection Module Info Backplane Type 1756 MODULE Generic 1756 Module Parent Local Connection Parameters Assembly Instance Size 16 bit Name mvi Input 1 0 Description Dutput 2 248 H 16 bit Configuration 4 0 8 bit Comm Format el Slot 1 H aan Status Offline Cancel Apply Help 3 Inthe SLOT field use the up and down arrows on the right side of the field to select the slot number where the module will reside in the rack and then click OK RSLogix will automatically apply the slot number change to all tags variables and ladder logic rungs that use the MVI56 MNETC slot number for computation ProSoft Technology Inc Page 139 of 153 October 26 2011 Reference MVI56 MNETC ControlLogix Platform User Manual Modbus TCP IP Multi Client Communication Module
11. Data Coil Data On off Data Error Check Field Hi Lo Ind 11 05 00 AC FF 00 CRC Page 124 of 153 ProSoft Technology Inc October 26 2011 MVI56 MNETC ControlLogix Platform Reference Modbus TCP IP Multi Client Communication Module User Manual 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 Data Coil Data On Data Error Check Field Hi Lo Off 11 05 00 AC FF 00 CRC The forcing of a coil via MODBUS function 5 will be accomplished regardless of whether the addressed coil is disabled or not n ProSoft products the coil is only affected if the necessary ladder logic is implemented Note The Modbus protocol does not include standard functions for testing or changing the DISABLE state of discrete inputs or outputs Where applicable this may be accomplished via device specific Program commands In ProSoft products this is only accomplished through ladder logic programming Coils that are reprogrammed in the controller logic program are not automatically cleared upon power up Thus if such a coil is set ON by function Code 5 and even months later an output is connected to that coil the output will be hot 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 cont
12. North America Warnings Power Input and Output I O wiring must be in accordance with Class Division 2 wiring methods Article 501 4 b of the National Electrical Code NFPA 70 for installation in the U S or as specified in Section 18 1J2 of the Canadian Electrical Code for installations in Canada and in accordance with the authority having jurisdiction The following warnings must be heeded 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 C Warning Explosion Hazard Do not disconnect equipment unless power has been switched off or the area is known to be non hazardous Avertissement Risque d explosion Avant de d connecter l quipement couper le courant ou s assurer que l emplacement est d sign non dangereux D Suitable for use in Class Division 2 Groups A B C and D 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 I
13. 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 on the type of communication network used and the expected response time of the slowest device on the network ProSoft Technology Inc Page 41 of 153 October 26 2011 Configuring the MVI56 MNETC Module MVI56 MNETC ControlLogix Platform User Manual Modbus TCP IP Multi Client Communication Module 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 Client driver will issue Function Code 3 6 and 16 commands read and write Holding Registers to a remote server when it is moving 32 bit floating point data If the remote server expects to receive or will send one complete 32 bit floating point value for each count of one 1 then set this parameter to YES When set to YES the Client driver will send values from two consecutive 16 bit internal memory registers 32 total bits for each count in a write command or receive 32 bits per count from the server for read commands Example Count 10 Client driver will send 20 16 bit registers for 10 total 32 bit floating point values If however the remote server expects to use a count of two 2 for each 32 bit floating point value it sends or receives or if you do not plan to use floatin
14. 2011 MVI56 MNETC ControlLogix Platform Configuring the MVI56 MNETC Module Modbus TCP IP Multi Client Communication Module User Manual 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 P Address parameter page 48 to address commands to a remote Modbus TCP IP device Note Most Modbus devices accept an address in the range of only 1 to 247 so check with the slave device manufacturer to see if a particular slave can use addresses 248 to 255 If the value is set to zero the command will be a broadcast message on the network The Modbus protocol permits broadcast commands for write operations Do not use node address 0 for read operations Modbus Function 1 2 3 4 5 6 15 or 16 This parameter specifies the Modbus Function Code to be executed by the command These function codes are defined in the Modbus protocol The following table lists the purpose of each function supported by the module More information on the protocol is available from www modbus org Modbus Function Code Description Read Coil Status Read Input Status Read Holding Registers Read Input Registers Force Write Single Coil Preset Write Single Register O ay yR oO rm 15 Force Multiple Coils 16 Preset Multiple Registers ProSoft Technology Inc Page 49 of
15. 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 2 10 Controlling Law and Severability This Warranty shall be governed by and construed in accordance with the laws of the United States and the domestic laws of the State of California without reference to its conflicts of law provisions If for any reason a court of competent jurisdiction finds any provisions of this Warranty or a portion thereof to be unenforceable that provision shall be enforced to the maximum extent permissible and the remainder of this Warranty shall remain in full force and effect Any cause of action with respect to the Product or Services must be instituted in a court of competent jurisdiction in the State of California Page 150 of 153 ProSoft Technology Inc October 26 2011 MVI56 MNETC ControlLogix Platform Modbus TCP IP Multi Client Communication Module Index User Manual Index 0 00 Return Query Data 126 A About the MODBUS TCP Protocol 119 Adding Multiple Modules Optional 27 Adding the Module to an Existing Project 132 Adding the Sample Ladder to an Existing Application 141 Adjusting the Input and Output Array Sizes 32 Allocation of Risks 150 ARP Timeout 43 Backplane Data Transfer 91 Backplane Error Status Pointer 38 80 Battery Life Advisory 3 Bl
16. Module configuration and associated ladder files if any Module operation and any unusual behavior Configuration Debug status information LED patterns Details about the serial Ethernet or fieldbus devices interfaced to the module if any akhoON Note For technical support calls within the United States an after hours answering system allows 24 hour 7 days a week pager access to one of our qualified Technical and or Application Support Engineers Detailed contact information for all our worldwide locations is available on the following page ProSoft Technology Inc Page 143 of 153 October 26 2011 Support Service amp Warranty MVI56 MNETC ControlLogix Platform User Manual Modbus TCP IP Multi Client Communication Module Internet Web Site www prosoft technology com support E mail address support prosoft technology com Asia Pacific Tel 603 7724 2080 E mail asiapc prosoft technology com location in Malaysia Languages spoken include Chinese English Asia Pacific location in China Tel 86 21 5187 7337 x888 E mail asiapc prosoft technology com Languages spoken include Chinese English Europe location in Toulouse France Tel 33 0 5 34 36 87 20 E mail support EMEA prosoft technology com Languages spoken include French English Europe location in Dubai UAE Tel 971 4 214 6911 E mail mea prosoft technology com Languages spoken include English Hindi
17. USD plus freight charges duties and taxes as applicable A new purchase order will be required or authorization to use the purchase order submitted for evaluation fee The following is a list of non repairable units ScanPort Adapters O O O 1500 All 1550 Can be repaired only if defect is the power supply 1560 Can be repaired only if defect is the power supply inRAx Modules Q GO O Or Or G O O 3150 All 3170 All 3250 3300 3350 3600 All 3700 3750 3800 MNET ProLinx Standalone Gateways O 4xxx All No hardware available to do repairs Page 146 of 153 ProSoft Technology Inc October 26 2011 MVI56 MNETC ControlLogix Platform Support Service amp Warranty Modbus TCP IP Multi Client Communication Module User Manual 6 2 LIMITED WARRANTY This Limited Warranty Warranty governs all sales of hardware software and other products collectively Product manufactured and or offered for sale by ProSoft Technology Incorporated ProSoft and all related services provided by ProSoft including maintenance repair warranty exchange and service programs collectively Services By purchasing or using the Product or Services the individual or entity purchasing or using the Product or Services Customer agrees to all of the terms and provisions collectively the Terms of this Limited Warranty All sales of software or other intellectual property are in addition subject to a
18. 1 1 First digit of dotted IP address 1 2 Second digit of dotted IP address 1 3 Third digit of dotted IP address 1 4 Last digit of dotted IP address 1 5 to 247 Reserved 243 Page 108 of 153 ProSoft Technology Inc October 26 2011 MVI56 MNETC ControlLogix Platform Reference Modbus TCP IP Multi Client Communication Module User Manual Block Response from Module to Processor Word Offset Description Length 0 0 1 1 Write Block ID 1 2 First digit of dotted IP address 1 3 Second digit of dotted IP address 1 4 Third digit of dotted IP address 1 5 Last digit of dotted IP address 1 6 to 248 Spare data area 243 249 9990 1 Get Module IP Address Block 9991 Block Request from Processor to Module Word Offset Description Length 0 9991 1 1 to 247 Spare data area 247 Block Response from Module to Processor Word Offset Description Length 0 0 1 1 Write Block ID 1 2 First digit of dotted IP address 1 3 Second digit of dotted IP address 1 4 Third digit of dotted IP address 1 5 Last digit of dotted IP address 1 6 to 248 Spare data area 243 249 9991 1 ProSoft Technology Inc Page 109 of 153 October 26 2011 Reference MVI56 MNETC ControlLogix Platform User Manual Modbus TCP IP Multi Client Communication Module Warm Boot Block 9998 This block is sent from the ControlLogix processor to the module output image when the module is requi
19. 1 The routine polling process is temporarily interrupted 2 The commands in the command priority queue are executed until the queue is empty 3 Then the module goes back to where it left off on the MNET Client x Command List and continues routine polling Event Command blocks send Modbus TCP IP commands directly from controller tags by ladder logic to the Client command priority queue on the module Event Commands are not placed in the module s internal database and are not part of the MNET Client x Command List Block Request from Processor to Module Word Offset Description Length 0 2000 to 2029 last digits indicate which Client to utilize 1 1 to 4 IP Address 4 5 Service Port 1 6 Slave Address 1 7 Internal DB Address 1 8 Point Count 1 9 Swap Code 1 10 Modbus Function Code 1 11 Device Database Address 1 12 to 247 Spare 236 The module will use the parameters passed in this block to construct the command The P 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 ProSoft Technology Inc Page 99 of 153 October 26 2011 Reference User Manual MVI56 MNETC ControlLogix Platform Modbus TCP IP Multi Client Communication Module The Service Port field selects the TCP ser
20. 24 Vdc Operating Temperature 32 F to 140 F 0 C to 60 C Storage Temperature 40 F to 185 F 40 C to 85 C Shock 30 g operational 50 g non operational Vibration 5 g from 10 Hz to 150 Hz Relative Humidity 5 to 95 with no condensation LED Indicators Module Status Backplane Transfer Status Application Status Serial Activity Application port Ethernet Ethernet Port Ethernet modules 10 100 Base T RJ45 Connector Link and activity LED indicators Electrical Isolation 1500 V rms at 50 Hz to 60 Hz for 60 s applied as specified in section 5 3 2 of IEC 60950 1991 Ethernet Broadcast Storm Resiliency less than or equal to 5000 ARP frames per second and less than or equal to 5 minutes duration Shipped with Unit RJ45 to DB 9M cables for each port 6 foot RS 232 configuration cable Debug Configuration port CFG CFG Port CFG RJ45 DB 9M with supplied cable No hardware handshaking Page 90 of 153 ProSoft Technology Inc October 26 2011 MVI56 MNETC ControlLogix Platform Reference Modbus TCP IP Multi Client Communication Module User Manual 5 2 Backplane Data Transfer The MVI56 MNETC 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 schedul
21. 4 Error MNETC STATUS EventSeqCmd Client 1 Cma 5 MNETC STATUS EventSeqCmd Client 1 Cmd 5 Sequence MNETC STATUS EventSeqCmd Client 1 Cmaf 5 E rror MNETC STATUS EventSeqCmd Client 1 Cmd 6 MNETC STATUS EventSeqCmd Client 1 Cmd 6 Sequence MNETC STATUS EventSeqCmd Client 1 Cmd 6 Error at Page 102 of 153 ProSoft Technology Inc October 26 2011 MVI56 MNETC ControlLogix Platform Modbus TCP IP Multi Client Communication Module Reference User Manual Other changes The MNETC Control tags were changed from MNETC CONTROL MNETC CONTROL BootTimer MNETC CONTROL ColdBoot MNETC CONTROL WarmBoot MNETC CONTROL ResetStatus MNETC CONTROL EventCmdT rigger MNETC CONTROL ClientID 10 q MNETC CONTROLEventCmd MNETC CONTROL CmdlD MNETC CONTROL CmdControl MNETC CONTROL CmdControlPending MNETC CONTROL CmdControlT rigger MNETC CONTROL PAddress MNETC CONTROL EventSeqCmdT rigger MNETC CONTROL ClientSeqID MNETC CONTROL EventSEQCmd The eventcmd trigger and client ID were moved inside the EventCmd section in turn moving down the entire section to be next to new eventSeqCmd MNETC CONTROL MNETC CONTROL BootTimer MNETC CONTROL ColdBoot MNETC CONTROL WarmBoot MNETC CONTROL ResetStatus MNETC CONTROL CmdlD MNETC CONTROL CmdControl MNETC CONTROL CmdControlPending MNETC CONTROL CmdControlT rigger MNETC CONTROLIPAddress MNETC CONTROLEventCmd MNETC C
22. 40 Too few parameters 41 Invalid enable code 42 Internal address gt maximum address 43 Invalid node address lt 0 or gt 255 44 Count parameter set to 0 45 Invalid function code 46 Invalid swap code 47 ARP could not resolve MAC from IP bad IP address not part of a network invalid parameter to ARP routine 48 Error during ARP operation the response to the ARP request did not arrive to the module after a user adjustable ARP Timeout Note When the Client gets error 47 or 48 it uses the adjustable ARP Timeout 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 85 of 153 October 26 2011 Diagnostics and Troubleshooting MVI56 MNETC ControlLogix Platform User Manual Modbus TCP IP Multi Client Communication Module Page 86 of 153 ProSoft Technology Inc October 26 2011 MVI56 MNETC ControlLogix Platform Reference Modbus TCP IP Multi Client Communication Module User Manual 5 Reference In This Chapter Product Specifications cceeceeeceeeseeeseeceaeeesaeeseaeeesaeeseaeeesaeeseaeeesaees 88 Backplane Data Transfer eeeseeeeeeseeeenneeeeeeneeeeeeeaeeeseneeeereneeeeene 91 Data Flow between MVI56 MNETC Mo
23. Client 0 Values OK MNet Client 1 Values OK MNet Client 2 Values OK Module Information Last Change Never Last Download Never Application Rev OS Rev Loader Rev MAC Address ConfigEdit version 2 1 8 Build 8 EtherNet Configuration my_ip 192 168 0 100 netmask 2 255 255 255 0 gateway 1292 168 0 1 Module Configuration lt MVIS6 MNETC At this time you may wish to rename the Default Project and Default Location folders in the tree view Renaming an Object 1 Select the object and then click the right mouse button to open a shortcut menu From the shortcut menu choose RENAME 2 Type the name to assign to the object 3 Click away from the object to save the new name Configuring Module Parameters 1 Click the sign next to the module icon to expand module information 2 Click the sign next to any amp a icon to view module information and configuration options 3 Double click any B icon to open an Edit dialog box 4 To edit a parameter select the parameter in the left pane and make your changes in the right pane 5 Click OK to save your changes ProSoft Technology Inc Page 37 of 153 October 26 2011 Configuring the MVI56 MNETC Module MVI56 MNETC ControlLogix Platform User Manual Modbus TCP IP Multi Client Communication Module Creating Optional Comment Entries 1 Click the to the left of the comment icon to expand the module comments 2 Double cli
24. Client x Command List page 43 for each Client examining commands in the order they are listed and sending enabled commands on the network However the module also has a special command priority queue which is an internal buffer that holds commands from special function blocks until they can be sent on the network When one or more commands appear in the command priority queue 1 The routine polling process is temporarily interrupted 2 The commands in the command priority queue are executed until the queue is empty 3 Then the module goes back to where it left off on the MNET Client x Command List and continues routine polling Like Event Command blocks Command Control blocks place commands into the module s command priority queue Unlike Event Command blocks which contain all the values needed for one command Command Control is used with commands already defined in the MNET Client x Command List Commands in the MNET Client x Command List may be either enabled for routine polling or disabled and excluded from routine polling A disabled command has its bit in the MNETC CONTROL CmdControl WriteCmaBits controller tag set to zero 0 and is skipped during routine polling An enabled command has its bit in the WriteCmaBits controller tag set to one 1 and is sent during routine polling However Command Control allows any command in the predefined MNET Client x Command List to be added to the command priority queue whether it is ena
25. LastErr INT Previous most recent error code recorded for the Client CmdErrorList x INT Command error code for each command 0 15 on the specified Client s command list Page 82 of 153 ProSoft Technology Inc October 26 2011 MVI56 MNETC ControlLogix Platform Modbus TCP IP Multi Client Communication Module Diagnostics and Troubleshooting User Manual 4 3 2 Configuration Error Word The Configuration Error Word contains Client configuration error indications in a bit mapped format Specific bits in the module s Configuration Error Word are turned on set to 1 to indicate various configuration errors The Configuration Error Word appears in the MNETC STATUS ClientStatus x controller tag array Bits set to 1 in the Configuration Error Word indicate the following errors Bit Description Hex Value 0 Reserved not currently used 0001h 1 Reserved not currently used 0002h 2 Reserved not currently used 0004h 3 Reserved not currently used 0008h 4 Invalid retry count parameter 0010h 5 The float flag parameter is not valid 0020h 6 The float start parameter is not valid 0040h 7 The float offset parameter is not valid 0080h 8 The ARP Timeout is not in range ARP Timeout parameter Oor 0100h greater than 60000 milliseconds and will default to 5000 milliseconds 9 The Command Error Delay is gt 300 and will default to 300 0200h 10 Reserved not currently used 04
26. Modbus TCP IP Multi Client Communication Module To determine the firmware version of your processor Important The RSLinx service must be installed and running on your computer in order for RSLogix to communicate with the processor Refer to your RSLinx and RSLogix documentation for help configuring and troubleshooting these applications 1 Connect an RS 232 serial cable from the COM serial port on your PC to the communication port on the front of the processor 2 Start RSLogix 5000 and close any existing project that may be loaded 3 Open the COMMUNICATIONS menu and choose GO ONLINE RSLogix will establish communication with the processor This may take a few moments 4 When RSLogix has established communication with the processor the Connected To Go Online dialog box will open Connected To Go Online xi Minor Faults Redundancy Nonvolatile Memory Options General Date Time Major Faults Condition The project file Controller ACD was not found in your project directory Connected Controller Controller Name Controller Controller Type 1756 L55 A 1756 M13 A ControlLogix5555 Controller Comm Path AB_DF1 1 Security lt None gt Offline Project Controller Nar Controller Type File Cancel Help Page 136 of 153 ProSoft Technology Inc October 26 2011 MVI56 MNETC ControlLogix Platform Reference Modbus TCP IP Multi Client Communication Module User Manual 5 Inthe Connected To Go On
27. North America location in California Tel 1 661 716 5100 E mail support prosoft technology com Languages spoken include English Spanish Latin America Oficina Regional Tel 1 281 2989109 E Mail latinam prosoft technology com Languages spoken include Spanish English Latin America location in Puebla Mexico Tel 52 222 3 99 6565 E mail soporte prosoft technology com Languages spoken include Spanish Brasil location in Sao Paulo Tel 55 1 1 5083 3776 E mail brasil prosoft technology com Languages spoken include Portuguese English Page 144 of 153 ProSoft Technology Inc October 26 2011 MVI56 MNETC ControlLogix Platform Support Service amp Warranty Modbus TCP IP Multi Client Communication Module User Manual 6 1 Return Material Authorization RMA Policies and Conditions The following Return Material Authorization RMA Policies and Conditions collectively RMA Policies apply to any returned product These RMA Policies are subject to change by ProSoft Technology Inc without notice For warranty information see Limited Warranty page 147 In the event of any inconsistency between the RMA Policies and the Warranty the Warranty shall govern 6 1 1 Returning Any Product a In order to return a Product for repair exchange or otherwise the Customer must obtain a Return Material Authorization RMA number from ProSoft Technology and comply with ProSoft Technology
28. Status block page 104 outside of the normal data transfer block sequence The status data contained in the Client Status block is different from the status data in the normal data transfer blocks It can also be viewed in the MNETC STATUS controller tag structure For more information about status data contained in MNETC STATUS see the Status Data Definition page 81 In ProSoft Configuration Builder s Diagnostics screens For more information see the section on PCB Diagnostics page 71 In database locations specified by Error Status Pointers optional If optional Error Status Pointers are enabled the status data can also be found in the Read Data area of the module s database at the locations specified by the pointer configuration parameters For more information see Backplane Error Status Pointer page 38 Client Error Status Pointer page 41 and Command Error Pointer page 41 Via the Configuration Debug port Use a terminal program such as HyperTerminal 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 Page 80 of 153 ProSoft Technology Inc October 26 2011 MVI56 MNETC Cont
29. TCP IP Multi Client Communication Module User Manual For example if you expand MNETC DATA you will see that it contains two UDTs ReadData and WriteData Both of these are 600 element integer arrays by default Name MNETCMODULEDEF Description This defines the whole module which includes all tags used in the program Members Data Type Size 4012 byte s Description DATA MNETCDATA Data read from module ReadData INT 600 Decimal Data read from module Set array equal to the size WriteData INT 600 Decimal Data to write to module Set array equal to the size CONTROL MNETCCONTROL Client Server Status and blocks status STATUS MNETCSTATUS MNETC Module control UTIL MNETCUTIL Block statistics Notice that these UDTs are the data types used to declare the MNETC DATA ReadData and MNETC DATA WriteData controller tag arrays Each UDT is commented in the Description column ProSoft Technology Inc Page 59 of 153 October 26 2011 Ladder Logic MVI56 MNETC ControlLogix Platform User Manual Modbus TCP IP Multi Client Communication Module 3 3 Using Controller Tags You can use controller tags to View read and write data that is being transferred between the module and the processor View status data for the module Set up and trigger special functions Initiate module restarts Warm Boot or Cold Boot Page 60 of 153 ProSoft Technology Inc October 26 2011 MVI56 MNETC ControlLogix Plat
30. The MVI56 MNETC is working normally ON The MVI56 MNETC module program has recognized a communication error BP ACT Amber ON The LED is ON when the module is performing a write operation on the backplane OFF The LED is OFF when the module is performing a read operation on the backplane Under normal operation the LED should blink rapidly ON and OFF OK Red OFF The card is not receiving any power and is not securely plugged Green into the rack GREEN The module is operating normally RED The program has detected an error or is being configured If the LED remains RED for more than 10 seconds the program has probably halted Remove the card from the rack and re insert the card to restart the module s 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 If the APP BP ACT and OK LEDs blink at a rate of every one second this indicates a serious problem with the module Call ProSoft Technology support to arrange for repairs Page 68 of 153 ProSoft Technology Inc October 26 2011 MVI56 MNETC ControlLogix Platform Diagnostics and Troubleshooting Modbus TCP IP Multi Client Communication Module User Manual 4 1 1 Ethernet LED Indicators LED State Description D
31. Using a Serial COM Port 32 54 Downloading the Sample Program to the Processor 34 140 141 Duplex Speed Code 40 E Enable 46 Ethernet Configuration 52 Ethernet Connection 114 Ethernet LED Indicators 69 Ethernet Port Configuration wattcp cfg 115 Event Command Blocks 2000 to 2029 99 Example and State Diagram 127 Exiting the Program 76 F Failure Flag Count 40 Float Flag 42 Float Offset 42 Float Start 42 Force Multiple Coils Function Code 15 128 Force Single Coil Function Code 05 124 Functional Specifications 89 G General Specifications 88 Get Module IP Address Block 9991 109 Guide to the MVI56 MNETC User Manual 9 H Hardware MAC Address 51 Hardware Specifications 90 How to Contact Us 2 Importing the Add On Instruction 24 Importing the Sample Add On Instruction 20 Initialize Output Data 40 ProSoft Technology Inc October 26 2011 Page 151 of 153 Index User Manual MVI56 MNETC ControlLogix Platform Modbus TCP IP Multi Client Communication Module Initialize Output Data Blocks 1000 to 1024 98 Installing ProSoft Configuration Builder Software 14 Installing the Module in the Rack 16 Intellectual Property Indemnity 149 Internal Address 47 IP Address 51 K Keystrokes 73 L Ladder Logic 55 LED Indicators 68 Limitation of Remedies 150 LIMITED WARRANTY 145 147 M
32. WriteData which are 600 element integer arrays by default Scope fq My_Controller v Show Show All Name amp Value Data Type Description ADISEMNETC ADI5SEMNETC Local 1 C AB 1756_MODULE C 0 Local 1 I AB 1756_MODULE_IN Local 1 0 AB 1756_MODULE_IN MNETC MNETCMODULEDEF MNETCDATA o MNETCDATA MNETC DATA ReadData INT 600 MNETC DATA WwriteData INT 600 MNETC CONTROL MNETCCONTROL _ MNETC STATUS MNETCSTATUS _ MNETC UTIL MNETCUTIL Each controller tag in the Add On Instruction is commented in the Description column Notice that the Data Type column displays the data types used to declare each controller tag controller tag array or controller tag structure Individual controller tags are declared with basic data types such as INT and BOOL Controller tag arrays are declared with arrays of basic data types Controller tag structures are declared with user defined data types UDTs ProSoft Technology Inc Page 57 of 153 October 26 2011 Ladder Logic MVI56 MNETC ControlLogix Platform User Manual Modbus TCP IP Multi Client Communication Module 3 2 User Defined Data Types UDTs User defined data types UDTs allow users to organize collections of data types into groupings These groupings or data type structures can then be used to declare the data types for controller tag structures Another ad
33. and 21 and reference type 6 to indicate that the extended file area failed to pass a consistency check The server attempted to read record file but detected a parity error in the memory The Client can retry the request but service may be required on the server device 0a Gateway Path Unavailable Specialized use in conjunction with gateways indicates that the gateway was unable to allocate an internal communication path from the input port to the output port for processing the request Usually means that the gateway is misconfigured or overloaded Ob Gateway Target Device Failed To Respond Specialized use in conjunction with gateways indicates that no response was obtained from the target device Usually means that the device is not present on the network ProSoft Technology Inc October 26 2011 Page 131 of 153 Reference MVI56 MNETC ControlLogix Platform User Manual Modbus TCP IP Multi Client Communication Module 5 6 Adding the Module to an Existing Project 1 Select the I O Configuration folder in the Controller Organization window of RSLogix 5000 and then click the right mouse button to open a shortcut menu On the shortcut menu choose NEW MODULE Controller My_Controller Controller Tags Controller Fault Handler Power Up Handler Tasks 5 tal MainTask amp MainProgram Unscheduled Programs Motion Groups G Ungrouped Axes Add On Instructions Sj Data Types i User De
34. area will be transferred in from the processor Note Total user database memory space is limited to the first 5000 registers of module memory addresses 0 through 4999 Therefore the practical limit for this parameter is 4999 minus the value entered for Write Register Count so that the Write Data Area does not try to extend above address 4999 Read Data and Write Data Areas must be configured to occupy separate address ranges in module memory and should not be allowed to overlap ProSoft Technology Inc Page 39 of 153 October 26 2011 Configuring the MVI56 MNETC Module MVI56 MNETC ControlLogix Platform User Manual Modbus TCP IP Multi Client Communication Module Write Register Count 0 to 5000 The Write Register Count parameter specifies the size of the Write Data area of module memory and the number of registers to transfer from the processor to this memory area up to a maximum value of 5000 words Note Total Read Register Count and Write Register Count cannot exceed 5000 total registers Read Data and Write Data Areas must be configured to occupy separate address ranges in module memory and should not be allowed to overlap Failure Flag Count If this value is greater than zero the protocol communication will be interrupted once a backplane failure is detected or communication with the processor fails A value of zero will disable this feature Initialize Output Data 0 No 1 Yes This parameter is used to determin
35. button to open a shortcut menu 2 On the shortcut menu choose PROPERTIES This action opens the Controller Properties dialog box 5 Controller Properties MVI56 ioj x Date Time Advanced SFC Execution File Redundancy Nonvolatile Memory General Serial Port System Protocol User Protocol Major Faults Minor Faults Vendor Allen Bradley Type 1756 L55 ControlLogix5555 Controller Change Type Revision 11 25 Change Revision Name MVI56 Example Logic for the MVI56 module Description Chassis Type Slot Cancel Apply Help 3 Click the CHANGE TYPE or CHANGE CONTROLLER button This action opens the Change Controller dialog box N Changing the controller type will change delete and or invalidate the controller properties and other project data that is not valid for the new controller type m From Type 1756 L63 ControlLogix5563 Controller Revision 13 25 m To Type Revision 13 7 pal Cancel Help 4 Open the TYPE dropdown list and then select your ControlLogix controller 5 Select the correct firmware revision for your controller if necessary 6 Click OK to save your changes and return to the previous window Page 138 of 153 ProSoft Technology Inc October 26 2011 MVI56 MNETC ControlLogix Platform Reference Modbus TCP IP Multi Client Communication Module User Manual 5 7 3 Selecting the Slot Number for the Module
36. ccccccccecceeeeeeeeeeceneeeeeeeeeeaeeseaeeeseaeeseaeeeseaeessueeeseieeseaaes 90 5 2 Backplane Data Trans Or ienai arn a R ATAA 91 5 2 1 Normal Data Transfer BIOCKS cccceseceeeeeseeeeeeeeeeeeeteaeeeeeeaeeeeseaeeeesesaeeeesenaaeeeens 93 5 2 2 Special Function BIOCKS c cceccceceeeeeeeeeeeeaeeeeeeeeseneeseaeeesaeeseaeeeseeeteaeeeseaeeseaeetas 97 5 3 Data Flow between MVI56 MNETC Module and Processor ccccceeeeeee 111 5 3 1 Client Drivers cvccitveesteeendhee dienes Wiad daveeeed dy a a vibe e danas Mine eed A ee Mia e a 112 5 3 2 Client Command Listenin enairada i evi Senedd osce seve eae Ka aa aiaa 113 5 4 Cable Gonnections sainia eee ede eevee el lieve ated 114 5 4 1 Ethernet COmme ction ccccccecesceceeeeeeeeeeeeeeeseaeeceaeeseaaeeseaeeeseaeeseaeessaeeseueesseaeenaas 114 5 4 2 RS 232 Configuration DebuUg PoOrt cccccececseeeseeeeeeeeseeeeeseaeeseaeeeeeaeeteueeeseneeseas 115 5 4 3 DB9 to RJ45 Adaptor Cable 14 0 c cecccceccceceeeeeeeeeeeeeeeseeeeseaeeseaeeeeaeesseeeeeeeeeeas 118 5 5 Modbus Protocol Specification cccecccceececeeeeeeeeeeeeneeeeeeeeseeeseeeeeseaeeseueeeseaeeseas 119 5 5 1 About the MODBUS TCP Protocol c ccceceeeeeeeeeeeeeeeeeeeceaeeeeeeeeseaeeseeeeseaeeseaees 119 5 5 2 Read Coil Status Function Code 01 ccccccscceceeeeseneeeeeeeeseeeeeneeeseaeeeeeeeeseaeeseas 120 5 5 3 Read Input Status Function Code 02 cccceccceeeeeeeeeeeeeeeeeseeeeseaeeeenaee
37. 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 Pt Data Start Pt Data of Pts Data of Pts Error Check Field Hi Lo Hi Lo 11 02 00 C4 00 16 CRC ProSoft Technology Inc Page 121 of 153 October 26 2011 Reference MVI56 MNETC ControlLogix Platform User Manual Modbus TCP IP Multi Client Communication Module Response An example response to Read Input Status is as shown in Figure C4 The data is packed one bit for each input The response includes the server address function code quantity of data characters the data characters and error checking Data will be packed with one bit for each input 1 ON 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
38. 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 MVI56 MNETC ControlLogix Platform Modbus TCP IP Multi Client Communication Module ProSoft Technology Inc October 26 2011 MVI56 MNETC ControlLogix Platform Support Service amp Warranty Modbus TCP IP Multi Client Communication Module User Manual 6 2 4 Intellectual Property Indemnity Buyer shall indemnify and hold harmless ProSoft and its employees from and against all liabilities losses claims costs and expenses including attorney s fees and expenses related to any claim investigation litigation or proceeding whether or not ProSoft is a party which arises or is alleged to arise from Buyer s acts or omissions under these Terms or in any way with respect to the Products Without limiting the foregoing Buyer at its own expense shall indemnify and hold harmless ProSoft and defend or settle any action brought against such Companies to the extent based on a claim that any Product made to Buyer specifications infringed intel
39. for firmware versions 1 36 000 and newer This register allows the processor to select which read blocks will be returned from the module If this register equals zero the module will return all read blocks in sequential order If this register has a non zero value the module will return the read block selected and the following one This feature can be used for applications that require some read blocks to be updated more frequently than other blocks The following illustrations show the effect of changing the value of the Select Priority Read Block register Write Block offset 247 In the following histogram curve the Select Priority Read Block is equal to 0 lt a 40215 544 02 15 740 40215940 40216 140 4 02 16 3402 16 540 PM Local 1 0 Data 247 Select Priority Read Block Local 1 1 Data 249 Read Block ID In the example above all read blocks 1 to 10 are returned in sequential order Page 96 of 153 ProSoft Technology Inc October 26 2011 MVI56 MNETC ControlLogix Platform Reference Modbus TCP IP Multi Client Communication Module User Manual Select Priority Read Block 5 If the ladder logic changes the value of Local 1 0 Data 247 from 0 to 5 note that the Local 1 Il Data 249 value begins to alternate between Block IDs 5 and 6 as long as Local 1 1 Data 247 stays set to 5 5 6 5 6 5 6 5 6 5 6 6 a TESTMNET Tuesday March 08 2005 o Local 1 I D
40. information about this submenu see Network Menu page 78 Exiting the Program Press ESC to restart the module and force all drivers to be loaded The module will use the configuration stored in the module s flash memory to configure the module Page 76 of 153 ProSoft Technology Inc October 26 2011 MVI56 MNETC ControlLogix Platform Diagnostics and Troubleshooting Modbus TCP IP Multi Client Communication Module User Manual 4 2 3 Modbus Database View Menu Press D to open the Modbus Database View menu Use this command to view the module s internal database values Press to view a list of commands on this menu DATABASE UIEW MEHU f Display Menu H 4 Pages 4 to 4668 Show Again Back 5 Pages P Previous Page 8kip 5 Pages H Next Page D Decimal Display H Hexadecimal Display F Float Display A ASCII Display M Main Menu All data contained in the module s database is available for viewing using the commands Refer to the Modbus Protocol Specification page 119 for information on the structure of Modbus messages Each option available on the menu is discussed in the following topics Viewing Register Pages To view sets of register pages use the keys described below Command Description 0 Display registers 0 to 99 1 Display registers 1000 to 1099 2 Display registers 2000 to 2099 And so on The total number of register pages available to view depends on your module s conf
41. permits the module to interface with a wide variety of Modbus TCP IP protocol devices The function codes used for each command are those specified in the Modbus protocol Each command list record has the same format The first part of the record contains the information relating to the MVI56 MNETC communication module and the second part contains information required to interface to the Modbus TCP IP server device ProSoft Technology Inc Page 43 of 153 October 26 2011 Configuring the MVI56 MNETC Module MVI56 MNETC ControlLogix Platform User Manual Modbus TCP IP Multi Client Communication Module Command List Overview In order to interface the module with Modbus TCP IP server devices you must construct a command list The commands in the list specify the server device to be addressed the function to be performed read or write the data area in the device to interface with and the registers in the internal database to be associated with the device data The Client command list supports up to 16 commands The command list is processed from top command 1 to bottom A poll interval parameter is associated with each command to specify a minimum delay time in tenths of a second between the issuances of a command If the user specifies a value of 10 for the parameter the command will be executed no more frequently than every 1 second Commands Supported by the Module The format of each command in the list depends on the Mod
42. processor A Download to the controller Name My_Controller Type 1756 L63 ControlLogix5563 Controller Path AB_DF1 1 Security lt None gt Cancel Help 3 RSLogix 5000 will compile the program and transfer it to the processor This process may take a few minutes 4 When the download is complete RSLogix 5000 will open another confirmation dialog box If the key switch is in the REM position click OK to switch the processor from PROGRAM mode to RUN mode RSLogix 5000 A Done downloading Change controller mode back to Remote Run Yes No Note If you receive an error message during these steps refer to your RSLogix documentation to interpret and correct the error Page 34 of 153 ProSoft Technology Inc October 26 2011 MVI56 MNETC ControlLogix Platform Configuring the MVI56 MNETC Module Modbus TCP IP Multi Client Communication Module User Manual 2 4 Using ProSoft Configuration Builder ProSoft Configuration Builder PCB provides a convenient 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 2 4 1 Setting Up the Project To begin start PROSOFT CONFIGURATION BUILDER PCB WW Microsoft Update Set Program Access and Defaults W Windows Catalog Accessories gt e
43. 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 143 A Technical Support Engineer will request that you perform several tests in an attempt to isolate the problem If after completing these tests the Product is found to be the source of the problem we will issue an RMA c All returned Products must be shipped freight prepaid in the original shipping container or equivalent to the location specified by ProSoft Technology and be accompanied by proof of purchase and receipt date The RMA number is to be prominently marked on the outside of the shipping box Customer agrees to insure the Product or assume the risk of loss or damage in transit Products shipped to ProSoft Technology using a shipment method other than that specified by ProSoft Technology or shipped without an RMA number will be returned to the Customer freight collect Contact ProSoft Technical Support for further information d A 10 restocking fee applies to all warranty credit returns whereby a Customer has an application change ordered too many does not need etc Returns for credit require that all accessory parts included in the original box i e antennas cables be returned Failure to return these items will result in a deduction from the total credit due for each missing item ProSoft Technology
44. that the module is plugged into the slot that has been configured for the module in the I O Configuration of RSLogix Verify that the slot location in the rack has been configured correctly in the ladder logic Processor I O LED This indicates a problem with backplane communications A problem flashes could exist between the processor and any installed I O module not just the MVI56 MNETC Verify that all modules in the rack are correctly configured in the ladder logic ProSoft Technology Inc Page 69 of 153 October 26 2011 Diagnostics and Troubleshooting User Manual MVI56 MNETC ControlLogix Platform Modbus TCP IP Multi Client Communication Module Module Errors Problem description Steps to take BP ACT LED not present on MVI56E modules remains OFF or blinks slowly MVI56E modules with scrolling LED display lt Backplane Status gt condition reads ERR This indicates that backplane transfer operations are failing Connect to the module s Configuration Debug port to check this To establish backplane communications verify the following items The processor is in RUN or REM RUN mode The backplane driver is loaded in the module The module is configured for read and write data block transfer The ladder logic handles all read and write block situations The module is properly configured in the processor I O configuration and ladder logic OK LED remains RED The program has halted or a
45. 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 E Module Properties Local 1 1756 MODULE 1 1 General Connection Module Info Backplane Requested Packet Interval RPI 50 4 ms 0 2 750 0 ms Inhibit Module I Major Fault On Controller If Connection Fails While in Run Mode Module Fault Status Offline Cancel Help ProSoft Technology Inc Page 133 of 153 October 26 2011 Reference MVI56 MNETC ControlLogix Platform User Manual Modbus TCP IP Multi Client Communication Module 5 Save the module Click OK to dismiss the dialog box The Controller Organization window now displays the module s presence amp Controller My_Controller A Controller Tags Controller Fault Handler Power Up Handler 3 6 Tasks fa MainTask G MainProgram Unscheduled Programs Motion Groups Ungrouped Axes Add On Instructions amp Data Types Gp User Defined oe Strings ip Add On Defined Gf Predefined Module Defined Trends 5 6 1 0 Configuration 1756 Backplane 1756 A4 fa 0 1756 163 My_Controller fi 1 1756 MODULE Mvi 6 Copy the User Defined Data Types from the sample program into your existing RSLogix 5000 project 7 Copy the Controller Tags from the sample program into y
46. the 3 year period commencing from the date of original equipment purchase not the date of shipment of the replacement unit Such repair including both parts and labor will be performed at ProSoft s expense All warranty service will be performed at service centers designated by ProSoft b Warranty On Services Materials and labor performed by ProSoft to repair a verified malfunction or defect are warranteed in the terms specified above for new Product provided said warranty will be for the period remaining on the original new equipment warranty or if the original warranty is no longer in effect for a period of 90 days from the date of repair ProSoft Technology Inc Page 147 of 153 October 26 2011 Support Service amp Warranty User Manual 6 2 2 What Is Not Covered By This Warranty a ProSoft makes no representation or warranty expressed or implied that the operation of software purchased from ProSoft will be uninterrupted or error free or that the functions contained in the software will meet or satisfy the purchaser s intended use or requirements the Customer assumes complete responsibility for decisions made or actions taken based on information obtained using ProSoft software b This Warranty does not cover the failure of the Product to perform specified functions or any other non conformance defects losses or damages caused by or attributable to any of the following i shipping ii improper install
47. to match the value entered in the Read Register Count page 39 parameter of the configuration For ease of use this array should be dimensioned as a multiple of 200 words This data is paged up to 200 words at a time from the module to the processor The ladder logic places the data received into the proper position in the ReadData array This data is used for status and control in the processor ladder logic 5 RSLogix 5000 My Controller 1756 163 Controller Tags My Control EBR A File Edit View Search Logic Communications Tools Window Help Scope My Controller _Show _ MNETCBLOCKSTATS MNETCCLIENTSTATS MNETCCMD Name 8 se Data Type al MNETC MNETCMODULEDEF MNETC DATA an MNETC DATA ReadData a MNETC DATA ReadData 0 abey HEIS v MNETCDATA INT 600 INT INT INT MNETC DATA ReadData 1 MNETC DATA ReadData 2 INT INT INT INT MNETC DATA ReadData 4 MNETC DATA ReadDatal 5 MNETC DATA ReadDatal6 MNETC DATA ReadData 3 0 0 0 MNETC DATA ReadData 3 0 INT 0 0 0 0 The ReadData array is related to the contents of the Read Data area of the module s internal database To view the actual registers in the module s internal database access the database display from ProSoft Configuration Builder s Diagnostics menu For more information see the section on PCB Diagnostics page 71 DATABASE DISPLAY 0 TO 99 CDECIVAL 6666 7777 8888 9999 1010 0 0 0 0 0 0 0
48. use when an ARP is required The module will accept up to 40 static IP MAC address data sets Important If the device in the field is changed this table must be updated to contain the new MAC address for the device and downloaded to the module If the MAC is not changed no communications with the module will occur Hardware MAC Address Hex value This table contains a list of static MAC addresses that the module will use when an ARP is required The module will accept up to 40 static IP MAC address data sets Important If the device in the field is changed this table must be updated to contain the new MAC address for the device and downloaded to the module If the MAC is not changed no communications with the module will occur ProSoft Technology Inc Page 51 of 153 October 26 2011 Configuring the MVI56 MNETC Module MVI56 MNETC ControlLogix Platform User Manual Modbus TCP IP Multi Client Communication Module 2 4 7 Ethernet Configuration Use this procedure to configure the Ethernet settings for your module You must assign an IP address subnet mask and gateway address After you 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 i
49. 0 0 0 0 ia a 0 ia ia 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 Page 62 of 153 ProSoft Technology Inc October 26 2011 MVI56 MNETC ControlLogix Platform Ladder Logic Modbus TCP IP Multi Client Communication Module User Manual MNETC DATA WriteData WriteData is a controller tag array that automatically adjusts to match the value entered in the Write Register Count page 40 parameter of the configuration For ease of use this array should be dimensioned as a multiple of 200 words This data is paged up to 200 words at a time from the processor to the module The ladder logic places the write data into the output image for transfer to the module This data is passed from the processor to the module for status and control information for use in other nodes on the network F RSLogix 5000 My Controller 1756 163 Controller Tags My_Controll EBR A File Edit Yiew Search Logic Communications Tools Window Help Scope ffqMy_Controller MNETCBLOCKSTATS MNETCCLIENTSTATS MNETCCMD L MNETCMODULEDEF MNETCDATA INT 600 INT 600 INT INT INT INT INT INT INT abed UEIS w ay MNETC DATA Hope MNETC DATA ReadData diese MNETC DATAWriteD ata hoon MNETC DATA WriteD ata O MNETC DATA WriteD ata 1 MNETC DATA WriteD ata 2 MNETC DATA WriteD ata 3 MNETC DATA WriteD ata 4 MNETC DATA WriteD ata 5 MNET
50. 00 registers of Write Data which is sufficient for most applications However you can configure the sizes of these data areas to meet the needs of your application 1 In ProSoft Configuration Builder expand the Module icon in the tree view and double click MODULE to open an Edit window Change the READ REGISTER Counr to contain the number of words for your Read Data area Important Because the module pages data in blocks of 200 registers at a time you should configure your user data areas in multiples of 200 registers Edit Module Read Register Count 1000 Comment Outp ata Pass Through Mode Duplex Speed Code Definition Number of regs to read from module for processor 2 To modify the WriteData array follow the above steps substituting WriteData for ReadData 3 Save and download the configuration to the module page 54 and reboot Make sure that the ReadData and WriteData arrays do not overlap in the module memory For example if your application requires 2000 words of WriteData starting at register 0 then your Read Register Start parameter must be set to a value of 2000 or greater Page 32 of 153 ProSoft Technology Inc October 26 2011 MVI56 MNETC ControlLogix Platform Configuring the MVI56 MNETC Module Modbus TCP IP Multi Client Communication Module User Manual 2 2 Connecting Your PC to the ControlLogix Processor There are several ways to establish communic
51. 00h 11 Reserved not currently used 0800h 12 Reserved not currently used 1000h 13 Reserved not currently used 2000h 14 Reserved not currently used 4000h 15 Reserved not currently used 8000h Combinations of errors will result in more than one bit being set in the error word Correct any invalid data in the configuration for proper module operation A value of zero 0 in this word indicates all bits are clear which means that all module configuration parameters contain valid values However this does not mean that the configuration is valid for the user application Make sure each parameter is set correctly for the intended application ProSoft Technology Inc October 26 2011 Page 83 of 153 Diagnostics and Troubleshooting MVI56 MNETC ControlLogix Platform User Manual Modbus TCP IP Multi Client Communication Module 4 3 3 Client Command Errors There are several different ways to view Client Command Errors Inthe MNETC STATUS CmaErrorList controller tag array On the Client status data screens in the ProSoft Configuration Builder Diagnostics Ata module database location specified by the configuration s MNET Client x Command Error Pointer if the Command Error Pointer is enabled This means that the first register refers to command 1 and so on Word Offset Description 0 Command 0 Error 1 Command 1 Error 2 Command 2 Error 3 Command 3 Error 15 Command 15 Error 16 Command 16 Err
52. 1 3 to 12 Client status data 10 13 to 28 Command error list data for Client 16 29 to 248 Reserved 220 249 3000 to 3029 1 Client Status Data Word Offset Client Status 3 Total number of command list requests 4 Total number of command list responses 5 Total number of command list errors 6 Not used 7 Not used 8 Not used 9 Not used 10 Configuration Error Word 11 Current Error 12 Last Error Status information transferred in the Client Status block can be viewed in the MNETC STATUS controller tag in the ladder logic For more information see Status Data Definition page 81 Page 104 of 153 ProSoft Technology Inc October 26 2011 MVI56 MNETC ControlLogix Platform Reference Modbus TCP IP Multi Client Communication Module User Manual Controller Tags To issue a Client Status block request enter the appropriate values in the following members of the MNETC STATUS controller tag in the ladder logic Controller Tag Data Type Description ClientID INT Enter the Client 0 29 to request status data for ClientStatsTrigger BOOL Set the value of this tag to 1 to trigger the Client Status block request Command Control Blocks 5001 5016 Note Command Control is not needed for normal Modbus command list polling operations and is needed only occasionally for special circumstances During routine operation the module continuously cycles through the user defined MNET
53. 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 On the shortcut menu choose CHOOSE MODULE TYPE This action opens the Choose Module Type dialog box Choose Module Type Product Line Filter C PLx4000 PLx6000 C MVI46 MVIS6 C MVI71 C all C PLxs000 C PTQ C mvI69 C MVIS6E Search Module Type STEP 1 Select Module Type Module Definition MVI5S6 101S MVIS6 104S MVIS6 BDW MVIS6 BSAPS MVIS6 DH485 MVIS6 DH485R Action Required MVIS6 DNP MVIS6 DNPSNET MVIS6 EGD MVIS6 FLN MVIS6 GEC MVIS6 HART MVIS6 KOS MVIS6 MCMR MVIS6 MDA4 MVIS6 MDA16 3 Inthe Product Line Filter area of the dialog box select MVI56 In the Select Module Type dropdown list select MVI56 MNETC and then click OK to save your settings and return to the ProSoft Configuration Builder window Page 36 of 153 ProSoft Technology Inc October 26 2011 MVI56 MNETC ControlLogix Platform Configuring the MVI56 MNETC Module Modbus TCP IP Multi Client Communication Module User Manual 2 4 2 Setting Module Parameters Notice that the contents of the information pane and the configuration pane changed when you added the MVI56 MNETC module to the project Untitled ProSoft Configuration Builder DER File View Project Tools Help Default Project Ga Default Location MVI56 MNETC Configured MVI56 MNETC h ME MVIS6 MTCS 1 12 Module Values OK MNet
54. 1100 31101 30001 1100 41101 40001 1100 Note If the documentation for a particular Modbus server device lists data addresses in hexadecimal base16 notation you will need to convert the hexadecimal value to a decimal value to enter in this parameter In such cases it is not usually necessary to subtract 1 from the converted decimal number as this addressing scheme typically uses the exact offset address expressed as a hexadecimal number Comment 0 to 35 alphanumeric characters Page 50 of 153 ProSoft Technology Inc October 26 2011 MVI56 MNETC ControlLogix Platform Configuring the MVI56 MNETC Module Modbus TCP IP Multi Client Communication Module User Manual 2 4 6 Static ARP Table The Static ARP Table defines a list of static IP addresses that the module will use when an ARP Address Resolution Protocol is required The module will accept up to 40 static IP MAC address data sets Use the Static ARP table to reduce the amount of network traffic by specifying IP addresses and their associated MAC hardware addresses that the MVI56 MNETC 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
55. 153 October 26 2011 Configuring the MVI56 MNETC Module MVI56 MNETC ControlLogix Platform User Manual Modbus TCP IP Multi Client Communication Module MB Address in Device This parameter specifies the starting Modbus register or bit address in the server to be used by the command Refer to the documentation of each Modbus server device for the register and bit address assignments valid for that device The Modbus Function Code determines whether the address will be a register level or bit level OFFSET address into a given data type range The offset will be the target data address in the server minus the base address for that data type Base addresses for the different data types are 00001 or 000001 0x0001 for bit level Coil data Function Codes 1 5 and 15 10001 or 100001 1x0001 for bit level Input Status data Function Code 2 30001 or 300001 3x0001 for Input Register data Function Code 4 40001 or 400001 4x0001 for Holding Register data Function Codes 3 6 and 16 Address calculation examples For bit level Coil commands FC 1 5 or 15 to read or write a Coil OX address 00001 specify a value of 0 00001 00001 0 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 For 01101 11101 31101 or 41101 specify a value of 1100 01101 00001 1100 11101 10001
56. C DATA WriteD ata 6 Monitor Tags AEdit Tags 4 0 0 0900 o o S The WriteData array is related to the contents of the Write Data area of the module s internal database To view the actual registers in the module s internal database access the database display from ProSoft Configuration Builder s Diagnostics menu For more information see the section on PCB Diagnostics page 71 DATABASE DISPLAY 1000 To 1099 CDECINMALJ 1111 2222 3333 4444 5555 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 a 0 A 0 a 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 ProSoft Technology Inc Page 63 of 153 October 26 2011 Ladder Logic User Manual MVI56 MNETC ControlLogix Platform Modbus TCP IP Multi Client Communication Module 3 4 2 MNETC CONTROL This controller tag structure is used to request special tasks from the module For more information see Special Function Blocks page 97 Controller Tag Data Type Description BootTimer TIMER Timer used to clear both cold and warm boot requests ColdBoot BOOL Hardware reset of the module WarmBoot BOOL Configuration data reset in the module EventCmdTrigger BOOL Event Command trigger ClientID INT Client ID to poll status on remote server EventCmd MNETCEVENTCMDJ 80 Holds Event Command configuration CmdID INT Command ID from 1 to 16 CmdControl MN
57. C based terminal emulation program to view configuration and status data in the module and to control the module The cable pinout for communications on this port is shown in the following diagram RS 232 Config Debug Port Cable DB 9 Male Config Debug Port Ro 2 c to To 3 ro com 5 com ProSoft Technology Inc Page 115 of 153 October 26 2011 Reference MVI56 MNETC ControlLogix Platform User Manual Modbus TCP IP Multi Client Communication Module Disabling the RSLinx Driver for the Com Port on the PC The communication port driver in RSLinx can occasionally prevent other applications from using the PC s COM port If you are not able to connect to the module s configuration debug port using ProSoft Configuration Builder PCB HyperTerminal or another terminal emulator follow these steps to disable the RSLinx driver 1 Open RSLinx and go to COMMUNICATIONS gt RSWHO 2 Make sure that you are not actively browsing using the driver that you wish to stop The following shows an actively browsed network 15 x Browsing node 10 found Workstation PSFT VAIO 1 gs Linx Gateways Ethernet gs AB_DF1 1 DH 485 E 01 SLC 5 05 UNTITLED DF1 COM1 UNTITLED i 10 Workstation DF1 COM1 3 Notice how the DF1 driver is opened and the driver is looking for a processor on node 1 If the network is being browsed then you will not be able to stop this driver To stop the driver your RSWho s
58. Code Register 1 10th Word 0 IP Port Address Read Input Register Seconds Count Address Registers 3x Code 1 bit 1 10th Bit 0 IP Port Address Force Register Seconds Count Address Write Single Coil 0x Code 1 bit 1 10th Word 0 IP Port Address Preset Register Seconds Count Address Write Single Register 4x Code Register 1 10th Bit 0 IP Port Address Force Register bit Seconds Count Address Write Multiple Coil 0x Code Register 1 10th Word 0 IP Port Address Preset Register Seconds Count Address Write Multiple Register 4x The first part of the record is the module information which relates to the MVI56 module and the second part contains information required to interface to the server device ProSoft Technology Inc Page 45 of 153 October 26 2011 Configuring the MVI56 MNETC Module User Manual MVI56 MNETC ControlLogix Platform Modbus TCP IP Multi Client Communication Module Command list example W Edit MNet Client 0 Commands Enable Internal Address Poll Interval Reg Count Swap Code Node IP Address Ser v Port Slave Addr ModBus Function v1 1000 0 No Change 192 168 0 249 502 1 FC 3 Read Holding x2 Yes 0 0 lt Enable Value Status OK Set to Defaults Add Row Insert Row No Change Delete Row Move Up 192 168 0 249 Move Down 502 1 FC 16 Preset Writ Edit Row Copy Row Enable No 0 or YES 1 OK
59. ETCCMDCONTROL Holds Command Control statistics CmdControlPending BOOL Halts rung until module is ready CmdControlTrigger BOOL Command Control Trigger IPAddress MNETCIPADDRESS Getting and setting IP address to and from module 3 4 3 MNETC STATUS This controller tag structure contains module and Client status data For a more complete description of the MNETC STATUS controller tag structure refer to the Status Data Definition page 81 Name Data Type Description PassCnt INT Program cycle counter ProductVersion INT This is used to pass the product version to the processor ProductCode INT 2 This is used to pass the product code to the processor BlockStats MNETCBLOCKSTATS Block transfer statistics CmaBits INT 30 Command bits array to be used for 30 Clients ClientStats Trigger BOOL Get Client status ClientID INT Client ID to get status from ClientStatus MNETCCLIENTSTATS 30 Client status data CmadErrorList INT 16 Command Error List Page 64 of 153 ProSoft Technology Inc October 26 2011 MVI56 MNETC ControlLogix Platform Ladder Logic Modbus TCP IP Multi Client Communication Module User Manual 3 4 4 MNETC UTIL This controller tag structure stores the variables required for the data transfer between the processor and the MVI56 MNETC module Name Data Type Description LastRead INT Index of last read block LastWrite INT Index o
60. F 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 Pt Data Start Pt Data Of Pts Data OfPts Error Check Hi Lo Ho Lo Field 11 01 00 13 00 25 CRC Page 120 of 153 ProSoft Technology Inc October 26 2011 MVI56 MNETC ControlLogix Platform Reference Modbus TCP IP Multi Client Communication Module User Manual Response An example response to Read Coil Status is as shown in Figure C2 The data is packed one bit for each coil The response includes the server address function code quantity of data characters the data characters and error checking Data will be packed with one bit for each coil 1 ON 0 OFF The low order bit of the first character contains the addressed coil and the r
61. G 150 6 2 7 Time Limit for Bringing Suit cccecccececeeceneeeeneeeeeeeeeeeeeeeeeeseaeeseaeeeseaeesseeeseaeesaas 150 6 2 8 No Other WeatrantieS ER A ieventsneaietestefeast aac aet dderecsneeuatt seas 150 6 2 9 AllOCatiON OT RISKS ak AE AEE E A A 150 6 2 10 Controlling Law and Severability c cccsceceeceeeeeeeseeeeeeeeeeseaeeseeeeeeaeessueeeseeeessas 150 Index 151 ProSoft Technology Inc October 26 2011 Page 7 of 153 Contents MVI56 MNETC ControlLogix Platform User Manual Modbus TCP IP Multi Client Communication Module Page 8 of 153 ProSoft Technology Inc October 26 2011 MVI56 MNETC ControlLogix Platform Modbus TCP IP Multi Client Communication Module Guide to the MVI56 MNETC User Manual User Manual Guide to the MVI56 MNETC User Manual Function Section to Read Details Introduction Must Do Start Here page 10 This section introduces the customer to the module Included are package contents system requirements hardware installation and basic configuration Diagnostic and Troubleshooting Diagnostics and Troubleshooting page 67 This section describes Diagnostic and Troubleshooting procedures Reference Product Specifications Reference page 87 Product Specifications page 88 These sections contain general references associated with this product and its Specifications Support Service and Warranty
62. Inc Page 145 of 153 October 26 2011 Support Service amp Warranty MVI56 MNETC ControlLogix Platform User Manual Modbus TCP IP Multi Client Communication Module 6 1 2 Returning Units Under Warranty A Technical Support Engineer must approve the return of Product under ProSoft Technology s Warranty a b A replacement module will be shipped and invoiced A purchase order will be required Credit for a product under warranty will be issued upon receipt of authorized product by ProSoft Technology at designated location referenced on the Return Material Authorization i If a defect is found and is determined to be customer generated or if the defect is otherwise not covered by ProSoft Technology s warranty there will be no credit given Customer will be contacted and can request module be returned at their expense ii If defect is customer generated and is repairable customer can authorize ProSoft Technology to repair the unit by providing a purchase order for 30 of the current list price plus freight charges duties and taxes as applicable Returning Units Out of Warranty Customer sends unit in for evaluation to location specified by ProSoft Technology freight prepaid If no defect is found Customer will be charged the equivalent of 100 USD plus freight charges duties and taxes as applicable A new purchase order will be required If unit is repaired charge to Customer will be 30 of current list price
63. ONTROL EventSeqlmd Block 4200 ee Before we ew OOK Holo ole S When the client sends this block the module will display the Queue count which is the command queue count and the waiting msgs which correspond to the event sequence messages waiting packed MNETC STATUS EventSeqCmdPending MNETC STATUS EventSeqCmdPending Trigger MNETC STATUS EventSeqCmdPending Client0_QueueCount MNETC STATUS EventSeqCmdPending Client0_ WaitingMsas MNETC STATUS EventSeqCmdPending Clientl_QueueCount MNETC STATUS EventSeqCmdPending Client1_ waitingMsgs MNETC STATUS EventSeqCmdPending Client2_QueueCount MNETC STATUS EventSeqCmdPending Client2_ WaitingMsgs ProSoft Technology Inc October 26 2011 Page 103 of 153 Reference MVI56 MNETC ControlLogix Platform User Manual Modbus TCP IP Multi Client Communication Module Client Status Blocks 3000 to 3029 Client status data for a specific Client can be requested and returned in a special Client Status block The status data contained in the Client Status block is different from the status data contained in the normal data transfer blocks Block Request from Processor to Module Word Offset Description Length 0 3000 to 3029 last digits indicate which Client to consider 1 1 to 247 Spare 247 Block Response from Module to Processor Word Offset Description Length 0 0 1 1 Write Block ID 1 2 3000 to 3029 number requested
64. On Instructions amp Data Types GB User Defined G Strings R Add On Defined E Predefined ER Module Defined Trends 1 0 Configuration 65 1756 Backplane 1756 A4 fa 0 1756 163 My_Controller f 1 1756 MODULE MNETC ProSoft Technology Inc Page 23 of 153 October 26 2011 Configuring the MVI56 MNETC Module User Manual MVI56 MNETC ControlLogix Platform Modbus TCP IP Multi Client Communication Module 2 1 3 Importing the Add On Instruction 1 Inthe Controller Organization window expand the TASKS folder and subfolder until you reach the MAINPROGRAM folder 2 Inthe MAINPROGRAM folder double click to open the MAINROUTINE ladder 3 Select an empty rung in the new routine and then click the right mouse button to open a shortcut menu On the shortcut menu choose IMPORT RUNG f RSLogix 5000 My_Controller 1756 L63 MainProgram Mai E File Edit View Search Logic Communications Tools Window Help inRoutine alsm S 4 2 e SoH e GIB alal Offline j E RUN No Forces m Ok a E Controller My_Controller a aael Tasks 5 8 MainTask B MainProgram Fe Path lt none gt gt amp gt No Edits wa a Hftatfic ar ft of oO gt i D lt gt J Favorites Add On X Alarms K Bi K Timericounter Program Tags EB MainRoutine Unscheduled Programs Motion Groups Gi Ungrouped Axes End Add On Instructions amp CutRung Copy Rung e Data Types GR U
65. P54 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 Battery Life Advisory The MV146 MVI56 MVI56E MVI69 and MVI71 modules use a rechargeable Lithium Vanadium Pentoxide battery to backup the real time clock and CMOS The battery should last for the life of the module The module must be powered for approximately twenty hours before the battery becomes fully charged After it is fully charged the battery provides backup power for the CMOS setup and the real time clock for approximately 21 days When the battery is fully discharged the module will revert to the default BIOS and clock settings Note The battery is not user replaceable Markings Hardware Ratings Backplane Current Load 800 mA 5 Vdc 3 mA 24 Vdc Operating Temperature 0 C to 60 C 32 F to 140 F Storage Temperature 40 C to 85 C 40 F to 185 F Shock 30 g operational 50 g non operational Vibration 5 g from 10 Hz to 150 Hz Relative Humidity 5 to 95 without condensation All phase conductor sizes must be at least 1 3 mm squared and all earth ground conductors must be at least 4mm squared Label Markings lt cULus gt E183151 CLI Div 2 GPA B C D Temp Code T6 30 C lt Ta lt 60 C lt Ex gt 3G EEx nA IIC T6 0 C lt Ta lt 60 C Il
66. ProSoft TESERO Ee G8 Where Automation Connects MVI56 MNETC ControlLogix Platform Modbus TCP IP Multi Client Communication Module ProSof ETHERNET in X oo P v KN October 26 2011 USER MANUAL Your Feedback Please We always want you to feel that you made the right decision to use our products If you have suggestions comments compliments or complaints about our products documentation or support please write or call us How to Contact Us ProSoft Technology 5201 Truxtun Ave 3rd Floor Bakersfield CA 93309 1 661 716 5100 1 661 716 5101 Fax www prosoft technology com support prosoft technology com Copyright 2011 ProSoft Technology Inc all rights reserved MVI56 MNETC User Manual October 26 2011 ProSoft Technology ProLinx inRAx 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 in Adobe Acrobat Reader file format PDFs These product documentation files may also be freely downloaded from our web site www prosoft technology com Warnings
67. WATTCP CFG File on the module Press V to view the module s WATTCP CFG file Use this command to confirm the module s current network settings WATIGP CFG FILE ProLinx Communication Gateways Inc name server 1 up to may be included NAMES PUB P KHM MMM MMM MXM name server NAME SE FUE F XMK KKK KKK KM The gateway I wish to use gateway 192 168 4 1 some networks lt class 29 require all three parameters gateway network subnetmas gateway 192 168 6 1 192 168 8 6 255 255 2554 The name of my networ domains list nynetwork name Returning to the Main Menu Press M to return to the Main menu ProSoft Technology Inc Page 79 of 153 October 26 2011 Diagnostics and Troubleshooting MVI56 MNETC ControlLogix Platform User Manual Modbus TCP IP Multi Client Communication Module 4 3 Reading Status Data from the Module Module status information is useful for troubleshooting and can be accessed in several different ways In the ladder logic s MNETC STATUS controller tag structure The MVI56 MNETC module returns status data in the input image that can be used to determine the module s operating status This data is transferred from the module to the processor continuously as part of the normal data transfer block sequence page 93 You can view this data in the MNETC STATUS controller tag structure in the ladder logic Client status data can also be requested and returned in a special Client
68. aeesseeees 15 1 5 Installing the Module in the Rack ceeccccesesseeeeeeeneeeeseeeeeeseeaeeeeseeaeeeeeenaeeeeneeaaees 16 2 Configuring the MVI56 MNETC Module 19 2 1 Importing the Sample Add On Instruction cccecceeeeeeeeseeeeeeeseneeeeeeeeseteeeteneeeeas 20 2 1 1 Creating a New RSLogix 5000 Project cccccceceeeeeeeeeeeeeeeeeaeeseeeseeeeeseaeeseeeeeseaeess 20 2 1 2 Creating the Module irssi ieira sopassa aietan asai inaa AE AAi aak aaia 21 2 1 3 Importing the Add On Instruction ccccceeeseeeeeeeeeeeeeeaeeeeeeeeseaeeseeeeseaeeseieeeseneeseas 24 2 2 Connecting Your PC to the ControlLogix ProC SSOl c cccceceeeeeeeeeeeeeteneeeeeeeees 33 2 3 Downloading the Sample Program to the Processor cccccceeeseeseeeeteteeeeeteesens 34 2 4 Using ProSoft Configuration Builder cccceeccceeeceeeeeeeeeeeeeeeeeeeeeeeseaeeeeeeeeseeeseas 35 2 4 1 Setting Up the Project raiar a a aaea Ni aa E ARAE aa 35 2 4 2 Setting Module Parameters cccccccesceceeeeceeeeeceeeeeeeeeeeeaeeseaeeeseneeseaeeseeneeseueeeneneens 37 2 4 3 NOGU a na na O A EA 38 2 4 4 MNET CIENt X siia aa aa a a a a a ea a aA 41 2 4 5 MNET Client x COMmMAnds ccccceecceeeceeeeneeeeneeeseaeeseaeeeeeaeeseaeeeeeeeeseaeeseneeeseeeseeeess 43 2 4 6 static ARP Tableti ai a iiaei iissa aii ia eee a iania ieii ein ia iaaa 51 2 4 7 Ethernet Configuration cccccccceccceseneeceneeeeeneeceaeeeeeeeeseneeseeeeeseaeeseaee
69. ain Menu 74 Markings 3 MB Address in Device 50 MBAP Port Override 43 Minimum Command Delay 41 MNET Client Specific Errors 85 MNET Client x 41 MNET Client x Commands 43 99 105 MNETC CONTROL 64 MNETC DATA 61 MNETC STATUS 64 MNETC UTIL 65 Modbus Database View Menu 75 77 Modbus Exception Codes 131 Modbus Exception Responses 130 Modbus Function 49 Modbus Protocol Specification 77 119 Modbus TCP IP 88 Module 38 Module Communication Error Codes 85 Moving Back Through 5 Pages of Registers 77 Moving Forward Through 5 Pages of Registers 78 MVI56 E MNETC Controller Tags 56 MVI56 E MNETC User Defined Data Types 58 N Navigation 73 Network Menu 76 78 No Other Warranties 150 Node IP Address 48 49 Normal Data Transfer Blocks 38 80 81 93 O Opening the Command Error List Menu 75 Opening the Command List Menu 75 Opening the Database View Menu 75 Opening the Network Menu 76 Opening the Sample Program in RSLogix 135 P Package Contents 13 Pinouts 3 114 118 Poll Interval 47 Preset Multiple Registers Function Code 16 129 Preset Single Register Function Code 06 125 Printing a Configuration File 38 Product Specifications 9 88 ProSoft Technology Product Documentation 2 R Read Block 93 Read Coil Status Function Code 01 120 Read Holding Registers Function C
70. alid for broadcast The following example forces 10 coils starting at address 20 13 HEX The two data fields CD 1100 and 00 0000 000 indicate that coils 27 26 23 22 and 20 are to be forced on Adr Func HiAdd Lo Quantity Byte Data Coil Data Coil Error Check Add Cnt Status 20 to Status 28to Field 27 29 11 OF 00 13 00 0A 02 CD 00 CRC Response The normal response will be an echo of the server address function code starting address and quantity of coils forced Adr Func Hi Addr Lo Addr Quantity Error Check Field 11 OF 00 13 00 0A CRC The writing of coils via Modbus function 15 will be accomplished regardless of whether the addressed coils are disabled or not Coils that are 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 Page 128 of 153 ProSoft Technology Inc October 26 2011 MVI56 MNETC ControlLogix Platform Reference Modbus TCP IP Multi Client Communication Module User Manual 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 t
71. ata 249 10 0 Local 1 0 Data 247 10 i 4 04 39 604 04 39 809 4 04 40 009 4 04 40 209 4 04 40 40904 40 609 PM Select Priority Read Block 0 After the ladder logic changes the value of Local 1 O0 Data 247 from 5 to 0 then the Local 1 I Data 249 value is updated as before by returning all blocks 1 through 10 in a repeating sequence 4 09 53 659 PM 8 0 O Locait lData 249 10 TESTMNET Tuesday March 08 2005 i Local1 0 Data 247 10 ia lt 2 4 09 51 654 09 51 859 4 09 52 059 4 09 52 259 4 09 52 45909 52 659 PM 5 2 2 Special Function Blocks Special function blocks are optional blocks used to request special tasks from the module ProSoft Technology Inc Page 97 of 153 October 26 2011 Reference MVI56 MNETC ControlLogix Platform User Manual Modbus TCP IP Multi Client Communication Module Initialize Output Data Blocks 1000 to 1024 Use the nitialize Output Data parameter in the configuration to bring the module to a known state after a restart operation If the nitialize Output Data parameter is enabled when the module performs a restart operation it will request blocks of output data from the ReadData array in the processor to initialize the Read Data area of the module s internal database Normal Data transfer Initialize Output Data transfer CLX Processor MNET Module CLX Processor MNET Module Modbus Modbus Out
72. ata 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 1 2 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 Verify correct configuration data is being transferred to the module from the ControlLogix controller If the module s OK LED does not turn GREEN verify that the module is inserted completely into the rack If this does not cure the problem contact ProSoft Technology Technical Support oo 4 1 3 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
73. ation between your PC and the ControlLogix processor The following steps show how to establish communication through the serial interface It is not mandatory that you use the processor s serial interface You may access the processor through whatever network interface is available on your system Refer to your Rockwell Automation documentation for information on other connection methods 1 Connect the right angle connector end of the cable to your controller at the communications port Communications Port 2 Connect the straight connector end of the cable to the serial port on your computer ProSoft Technology Inc Page 33 of 153 October 26 2011 Configuring the MVI56 MNETC Module MVI56 MNETC ControlLogix Platform User Manual Modbus TCP IP Multi Client Communication Module 2 3 Downloading the Sample Program to the Processor Note The key switch on the front of the ControlLogix processor must be in the REM or PROG position 1 If you are not already online with the processor open the Communications menu and then choose DOWNLOAD RSLogix 5000 will establish communication with the processor You do not have to download through the processor s serial port as shown here You may download through any available network connection 2 When communication is established RSLogix 5000 will open a confirmation dialog box Click the DOWNLOAD button to transfer the sample program to the
74. ation 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 consequential damages resulting from the furnishing performance or use of this material The user guide included with your original product purchase from ProSoft contains information protected by copyright No part of the guide may be duplicated or reproduced in any form without prior written consent from ProSoft 6 2 3 Disclaimer Regarding High Risk Activities Product manufactured or supplied by ProSoft is not fault tolerant and is not designed manufactured or intended for use in hazardous environments requiring
75. bled for routine polling or not Command Control also gives you the option to use ladder logic to have commands from the MNET Client x Command List executed at a higher priority and out of routine order if such an option might be required in special circumstances ProSoft Technology Inc Page 105 of 153 October 26 2011 Reference MVI56 MNETC ControlLogix Platform User Manual Modbus TCP IP Multi Client Communication Module A single Command Control block request can place up to 16 commands from the MNET Client x Command List into the command priority queue Block Request from Processor to Module Word Offset Description Length 0 Command Control block identification code of 5001 to 5016 The 1 rightmost digit indicates the number of commands 1 to 16 to add to the command priority queue 1 Client index 1 2 This word contains the Command Index for the first command to 1 be entered into the queue 3 Command Index 2 1 4 Command Index 3 1 5 Command Index 4 1 6 Command Index 5 1 7 Command Index 6 1 8 Command Index 7 1 9 Command Index 8 1 10 Command Index 9 1 11 Command Index 10 1 12 Command Index 11 1 13 Command Index 12 1 14 Command Index 13 1 15 Command Index 14 1 16 Command Index 15 1 17 Command Index 16 1 18 to 247 Spare 230 The last digit in the block identification code indicates the number of commands to process For example a block identification co
76. bus Function Code being executed The following table lists the functions supported by the module Function Code Definition Read Coil Status Read Input Status Read Holding Registers Force Write Single Coil Preset Write Single Register 15 Force Write Multiple Coils 16 Preset Write Multiple Registers 1 2 3 4 Read Input Registers 5 6 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 Page 44 of 153 ProSoft Technology Inc October 26 2011 MVI56 MNETC ControlLogix Platform Configuring the MVI56 MNETC Module Modbus TCP IP Multi Client Communication Module User Manual Command Entry Formats The following table shows the structure of the configuration data necessary for each of the supported commands 1 2 3 4 5 6 7 8 9 10 Enable Internal Poll Count Swap IP Serv Slave Function Device Code Address Interval Code Address Port Node Code Modbus Time Address Code Register 1 10th Bit 0 IP Port Address Read Coil Register bit Seconds Count Address Ox Code Register 1 10th Bit 0 IP Port Address Read Input Register bit Seconds Count Address 1x Code Register 1 10th Word Code IP Port Address Read Register Seconds Count Address Holding Registers 4x
77. ck the 8 Modiecomment icon The Edit Module Comment dialog box appears Edit Module Comment 3 Enter your comment and click OK to save your changes Printing a Configuration File 1 Select the module icon and then click the right mouse button to open a shortcut menu 2 On the shortcut menu choose VIEW CONFIGURATION This action opens the View Configuration window 3 Inthe View Configuration window open the FILE menu and choose PRINT This action opens the Print dialog box 4 Inthe Print dialog box choose the printer to use from the drop down list select printing options and then click OK 2 4 3 Module This section of the configuration describes the database setup and module level parameters Backplane Error Status Pointer 1 to 4955 This parameter sets the address in the internal database where the backplane error status data will be placed If you want the error status data to be moved to the processor and placed into the ReadData array the value entered should be a module memory address in the Read Data area If the value is set to 1 the error status data will not be stored in the module s internal database and will not be transferred to the processor s ReadData array Enabling the Error Status Pointer is optional The error status data is routinely returned as part of the input image which is continually being transferred from the module to the processor For more information see Normal Data T
78. click the right mouse button to open a shortcut menu On the shortcut menu choose IMPORT RUNG N OO fe RSLogix 5000 My_Controller 1756 L63 MainProgram MainRoutine DR amp File Edit View Search Logic Communications Tools Window Help alsa S e lt gt z amp lslH le w alal 0 E RUN Path lt nane gt z gt ok m Brio 4 HI tot ab 4 gt ur xu gt D gt J Favorites Add On K Alarms K Bt K Tmerlcounter Ki Controller My_Controller it R 5 5 Controller Tags Controller Fault Handler This defines the Power Up Handler whole module which Tasks includes all tags 2 fa MainTask used in the program Fault Code value O MainProgram aay A Program Tags Get System Value EB MainRoutine Class Name Module E Unscheduled Programs Instance Name MNETC amp Motion Groups Attribute Name FaultCode Ungrouped Axes Cut Rung Ctri x Dest MNETC Ui eho d F m a Ba Copy Rung Ctrl C Parameters and Local Tags e Add On for FB Logic MVISB MNETC and E Prescan Delete Rung Del WYRE METS a g Types aa Rung Ctrl Pen PRETCCLUENTSTATS Edit Rung Comment Ctrl D Cae Gus oct bes MNETCCMDCONTROL Import Rung ection_Output Local 1 0 Data MNETCCONTROL Export Rung jc MNETC MNETCDATA MNETCEVENTCMD MNETCINITOUTDATA MNETCIPADDRESS MNETCMODULEDEF MNETCSTATUS W MNETCUTIL Gi Strings Oy Add On Defined Op Predefined Verify Rung Gj Module Defined Trends GoTo Ctrl G
79. controller with 100 registers a request with offset 96 and length 4 would succeed a request with offset 96 and length 5 will generate exception 02 03 Illegal Data Value A value contained in the query data field is not an allowable value for server This indicates a fault in the structure of the remainder of a complex request such as that the implied length is incorrect It specifically does not mean that a data item submitted for storage in a register has a value outside the expectation of the application program because the Modbus protocol is unaware of the significance of any particular value of any particular register 04 Slave Device Failure An unrecoverable error occurred while the server was attempting to perform the requested action 05 Acknowledge Specialized use in conjunction with programming commands The server has accepted the request and is processing 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
80. creen should look like this Not Browsing E ea Linx Gateways Ethernet gs AB_DF1 1 DH 485 Linx AB_DF1 1 Gatew DH 485 Branches are displayed or hidden by clicking on the or the E icons E AB_DF1 1 DH 485 4 When you have verified that the driver is not being browsed go to COMMUNICATIONS gt CONFIGURE DRIVERS Page 116 of 153 ProSoft Technology Inc October 26 2011 MVI56 MNETC ControlLogix Platform Reference Modbus TCP IP Multi Client Communication Module User Manual You may see something like this Configure Drivers 7 l Available Driver Types m Configured Drivers Status Name and Description AB _DF1 1 DH485 Sta 10 COM1 RUNNING If you see the status as running you will not be able to use this com port for anything other than communication to the processor To stop the driver press the STOP button on the side of the window Configure Startup Start Stop Delete 5 After you have stopped the driver you will see the following Configure Drivers a Available Driver Types Name and Description Status AB_DF1 1 DH485 Sta 10 COM1 STOPPED Stopped Configured Drivers 6 You may now use the com port to connect to the debug port of the module Note You may need to shut down and restart your PC before it will allow you to stop the driver usually only on Windows NT machines If you have fol
81. cribes the structure of the input image Read Block from Module to Processor Word Offset Description Length 0 Reserved 1 1 Write Block ID 1 2 to 201 Read Data 200 202 Program Scan Counter 1 203 to 208 Block Transfer Status 6 209 to 238 Command bit data for Clients 30 239 to 240 Product Code 2 241 Product Version 1 242 to 248 Reserved 7 249 Read Block ID 1 ProSoft Technology Inc Page 93 of 153 October 26 2011 Reference User Manual MVI56 MNETC ControlLogix Platform Modbus TCP IP Multi Client Communication Module The Read Block ID is an index value used to determine where the 200 words of data from module memory will be placed in the ReadData x controller tag array of the ControlLogix processor Each transfer can move up to 200 words block offsets 2 to 201 of data In addition to moving user data the block also contains status data for the module The Write Block ID associated with the block requests data from the ControlLogix processor During normal program operation the module sequentially sends read blocks and requests write blocks For example if the application uses three read and two write blocks the sequence will be as follows Riw10R2W20R3W10RiW20R2W1 R3W20R1W1 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 ne
82. critical error has occurred Connect to the Configuration Debug port to see if the module is running If the program has halted turn off power to the rack remove the card from the rack and re insert it and then restore power to the rack Page 70 of 153 ProSoft Technology Inc October 26 2011 MVI56 MNETC ControlLogix Platform Diagnostics and Troubleshooting Modbus TCP IP Multi Client Communication Module User Manual 4 2 Using ProSoft Configuration Builder PCB for Diagnostics The Configuration and Debug 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 Because this is a text based menu system you enter commands by typing the command letter from your computer keyboard in the Diagnostic window in ProSoft Configuration Builder PCB The module does not respond to mouse movements or clicks The command executes as soon as you press the COMMAND LETTER you do not need to press ENTER When you type a COMMAND LETTER a new screen will be displayed in your terminal application 4 2 1 Using the Diagnostic Window in ProSoft Configuration Builder Tip You can have a ProSoft Configuration Builder Diagnostics window open for more than one module at a time To connect to the module s Configquration Debug serial port 1 Start PCB and then select the m
83. de of 5003 indicates that three commands are to be placed in the queue In this case the first three of the 16 available Command Indexes will be used to determine exactly which three commands will be added to the queue and to set their order of execution Values to enter for the 16 Command Indexes range from 0 to 15 and correspond to the MNET Client x Command List entries which are numbered from 1 to 16 To determine the Command Index value subtract one 1 from the row number of the command in the MNET Client x Command List as seen in the Command Editor window of ProSoft Configuration Builder PCB The module responds to a Command Control block request with a response block indicating the number of commands added to the command priority queue Page 106 of 153 ProSoft Technology Inc October 26 2011 MVI56 MNETC ControlLogix Platform Reference Modbus TCP IP Multi Client Communication Module User Manual Block Response from Module to Processor Offset Description Length 0 Reserved 1 1 Write Block ID 1 2 Number of commands added to command queue 1 3 to 248 Spare 246 249 5001 to 5016 1 Controller Tags The MNETC CONTROL controller tag array holds all the values needed to create one Command Control block have it sent to the module and control the processing of the returned response block Controller Tag Description CmdID Enter a decimal value representing the quantity of commands to be req
84. derivative works based on the software export the software or underlying technology in contravention of applicable US and international export laws and regulations or use the software other than as authorized in connection with use of Product f Additional Restrictions Relating To Software And Other Intellectual Property In addition to compliance with the Terms of this Warranty Customers purchasing software or other intellectual property shall comply with any license agreement accompanying such software or other intellectual property Failure to do so may void this Warranty with respect to such software and or other intellectual property 6 2 5 Disclaimer of all Other Warranties The Warranty 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 October 26 2011 Support Service amp Warranty MVI56 MNETC ControlLogix Platform User Manual Modbus TCP IP Multi Client Communication Module 6 2 6 Limitation of Remedies In no event will ProSoft or its Dealer be liable for any special incidental or consequential damages based on breach of warranty breach of contract negligence strict tort or any other legal theory Damages that ProSoft or its Dealer will not be responsible for include but are not limited to Loss of prof
85. download the latest version of ProSoft Configuration Builder 3 Choose SAVE or SAVE FILE when prompted 4 Save the file to your Windows Desktop so that you can find it easily when you have finished downloading 5 When the download is complete locate and open the file and then follow the instructions on your screen to install the program If you do not have access to the Internet you can install ProSoft Configuration Builder from the ProSoft Solutions Product CD ROM included in the package with your module To install ProSoft Configuration Builder from the Product CD ROM 1 Insert the ProSoft Solutions Product CD ROM into the CD ROM drive of your PC Wait for the startup screen to appear 2 On the startup screen click PRODUCT DOCUMENTATION This action opens a Windows Explorer file tree window 3 Click to open the UTILITIES folder This folder contains all of the applications and files you will need to set up and configure your module 4 Double click the SETUP CONFIGURATION TOOL folder double click the PCB _ EXE file and follow the instructions on your screen to install the software on your PC The information represented by the character in the file name is the PCB version number and therefore subject to change as new versions of PCB are released Note Many of the configuration and maintenance procedures use files and other utilities on the CD ROM You may wish to copy the files from the Utilities folder on the CD ROM to a co
86. dule and Processot 111 Cable Connections ceceeeccececeeeeeeeceeeeeeeeseeeeeseeeeseeseeeeseeseeeenieeeeaes 114 Modbus Protocol Specification ecceecceseeeeeeeeeeeeeeeeeeeeeeeeeneeeeeeeeeeas 119 Adding the Module to an Existing Project 132 Using the Sample Program ccceeseeseeeeeeeeeeeeeeeeeeseeeseeeeesaeesseeenaas 135 ProSoft Technology Inc Page 87 of 153 October 26 2011 Reference MVI56 MNETC ControlLogix Platform User Manual Modbus TCP IP Multi Client Communication Module 5 1 Product Specifications The MVI56 Modbus TCP IP Client Communication Module allows Rockwell Automation ControlLogix processors to interface easily with other Modbus compatible devices Compatible devices include Modicon PACs as well as a wide variety of instruments and devices The module acts as an input output module between the Modbus network and the Rockwell Automation backplane The data transfer from the processor is asynchronous from the actions on the Modbus Client controlled network A 5000 word register space in the module exchanges data between the processor and the Modbus network 5 1 1 General Specifications Single Slot 1756 backplane compatible 10 100 MB Ethernet port Module I O data memory mapping supports up to 5000 registers and is user definable ProSoft Configuration Builder PCB software supported a Windows based graphical user interface providing simple product a
87. e 2 1 2 Creating the Module 1 Add the MVI56 MNETC module to the project In the Controller Organization window select I O CONFIGURATION and click the right mouse button to open a shortcut menu On the shortcut menu choose NEW MODULE 1 0 Configuration im 31756 Backplane 1756 A fq 0 1756 163 My_Cor New Module ProSoft Technology Inc October 26 2011 Page 21 of 153 Configuring the MVI56 MNETC Module User Manual MVI56 MNETC ControlLogix Platform Modbus TCP IP Multi Client Communication Module This action opens the Select Module dialog box E Select Module Module Description Vendor Analog Communications Controllers Digital Drives Motion Other 1756 MODULE Generic 1756 Module Allen Bradley Specialty Find Add Favorite By Category By Vendor Favorites J OK Cancel Help 2 Select the 1756 MODULE GENERIC 1756 MODULE from the list and click OK This action opens the New Module dialog box In the New Module dialog box enter the following values 3 Parameter Value Name Enter a module identification string Example MNETC Description Enter a description for the module Example Mopsus TCP IP MULTI CLIENT COMMUNICATION MODULE Comm Format Select DATA INT Slot Enter the slot number in the rack where the MVI56 MNETC module is located Input Assembly Instance 1 Input Size 250 Output Assembly Instance 2 Output S
88. e This section only applies if your processor is using RSLogix 5000 version 16 or higher If you have an earlier version please see Using the Sample Program page 135 Before You Begin The following file is required before you start this procedure Copy the file from the ProSoft Solutions CD ROM or download it from www prosoft technology com File Name Description MVI56MNETC_AddOn_Rung_v1_5 L5X L5X file containing Add On instruction user defined data types data objects and ladder logic required to set up the MVI56 MNETC module 2 1 1 Creating a New RSLogix 5000 Project 1 Open the FILE menu and then choose NEw f RSLogix 5000 faim Edit View Search Logic Communications Tools Wit B New Ctri N fa Open Ctri 0 2 Select your ControlLogix controller model 3 Select REVISION 16 4 Enter a name for your controller such as My_Controller 5 Select your ControlLogix chassis type Page 20 of 153 ProSoft Technology Inc October 26 2011 MVI56 MNETC ControlLogix Platform Modbus TCP IP Multi Client Communication Module Configuring the MVI56 MNETC Module User Manual 6 Select SLOT 0 for the controller New Controller Vendor Type Revision Name Description Chassis Type Slot Create In Allen Bradley 1756 L63 ControlLogix5563 Controller Tl Redundancy Enabled M y_Controller 1756 44 4 Slot ControlLogix Chassis X 0 a CARSLogix 5000 Projects Brows
89. e Sample Ladder to an Existing Application cccceseeeseeeeteeeetees 141 Page 6 of 153 ProSoft Technology Inc October 26 2011 MVI56 MNETC ControlLogix Platform Contents Modbus TCP IP Multi Client Communication Module User Manual 6 Support Service amp Warranty 143 Contacting Technical SUPPOMt cccccececeeeeneeeeeeeeeeeeeeeaeeeeeaeeseaeeeseaeeseaeeseaaeeseaeeseaeesseaeeseeeeseaeeseas 143 6 1 Return Material Authorization RMA Policies and Conditions cceeee 145 6 1 1 Returning Any Produttori a a a e RE E T T 145 6 1 2 Returning Units Under Warranty ccccceeeeeneeeeeeeneeeeeeeneeeeeeeeeeeeeeeeeeeteeeeeeneaes 146 6 1 3 Returning Units Out of Warranty cccccceceeeeceeeeeeeeeeeeeeeseeeeeeeeeseaeeseeeeseeeseeeeees 146 6 2 LIMITED WARRANT Yerimi e e Ai p a a a T aa e a a e 147 6 2 1 What Is Covered By This Warranty c cccccceceeeeeeeeeeeeeeeseeeseneeeseaeessaneeseeeesaas 147 6 2 2 What Is Not Covered By This Warranty cccccccsceceeeeeeeeeeceeeeeeeeeeeeaeeseneeeseeeeeaas 148 6 2 3 Disclaimer Regarding High Risk Activities 0 cc eeeeeeeeeeeeeeeeeeneeeeeeeaeeeeeenaeeeeeenas 148 6 2 4 Intellectual Property Indemnity eee eee eeeeeneeeeeeeeeeeeeeaeeeeeeeaeeeeeeeeeeeeteeeeeetaes 149 6 2 5 Disclaimer of all Other Warranties c cccccceeeseeceeeeeeeeeseneeeeeeeeseaeeseeeeteaeeeeeeeess 149 6 2 6 Limitation Of Remedies rer ona AT A AE
90. e conditional write command 10 100 MB Ethernet Application port Supports Enron version of Modbus protocol for floating point data transactions PCB includes a powerful Modbus network analyzer Special functions Event Commands Command Control status etc are supported by message transfer unscheduled using the MSG instruction Configurable parameters for the Client including a minimum response delay of 0 to 65535 ms and floating point support Supports up to 30 Clients with up to 16 commands for each Client All data mapping begins at Modbus register 40001 Error codes network error counters and port status data available in user data memory Client Specifications A port configured as a virtual Modbus Client device on the MVI56 MNETC module actively issues Modbus commands to other nodes on the Modbus network Additionally the Client ports have an optimized polling characteristic that polls servers with communication problems less frequently The ControlLogix processor can be programmed to control the activity on the port by actively selecting commands from the command list to execute or issuing commands directly from the ladder logic ProSoft Technology Inc Page 89 of 153 October 26 2011 Reference User Manual MVI56 MNETC ControlLogix Platform Modbus TCP IP Multi Client Communication Module 5 1 4 Hardware Specifications Specification Description Backplane Current Load 800 mA 5 Vdc 3 mA
91. e if the output data for the module should be initialized with values from the processor If the value is set to 0 the output data will be initialized to O If the value is set to 1 the data will be initialized with data from the processor Use of this option requires associated ladder logic to pass the data from the processor to the module Duplex Speed Code 0 1 2 30r4 This parameter allows you to cause the module to use a specific duplex and speed setting Value 1 Half duplex 10 MB speed Value 2 Full duplex 10 MB speed Value 3 Half duplex 100 MB speed Value 4 Full duplex 100 MB speed Value 0 Auto negotiate Auto negotiate is the default value for backward compatibility This feature is not implemented in older software revisions Page 40 of 153 ProSoft Technology Inc October 26 2011 MVI56 MNETC ControlLogix Platform Configuring the MVI56 MNETC Module Modbus TCP IP Multi Client Communication Module User Manual 2 4 4 MNET Client x This section defines general configuration for the MNET Client Master Client Error Status Pointer 1 to 4990 This parameter sets the address in the internal database where the Client error status data will be placed If you want the error status data to be moved to the processor and placed into the ReadData array the value entered should be a module memory address in the Read Data area If the value is set to 1 the error status data will not be stored in t
92. e to observe this precaution may result in damage to hardware or injury to personnel Important The module requires a static fixed IP address that is not shared with any other device on the Ethernet network Obtain a list of suitable IP addresses from your network administrator BEFORE configuring the Ethernet port on this module Page 114 of 153 ProSoft Technology Inc October 26 2011 MVI56 MNETC ControlLogix Platform Reference Modbus TCP IP Multi Client Communication Module User Manual Ethernet Port Configuration wattcp cfg The wattcp cfg file must be set up properly in order to use a TCP IP network connection You can view the current network configuration in ProSoft Configuration Builder PCB as shown Edit WATTCP my ip 192 168 0 100 my_ip netmask 255 255 255 0 gateway 192 168 0 1 192 Comment peoo o oo Definition Default private class 3 address Reset Tag Reset All OK Cancel You may also view the network configuration using a PC serial port connection and an ASCII terminal program like Windows HyperTerminal by selecting Network Menu and V View options when connected to the Debug port For more information on serial port access see the chapter on Diagnostics and Troubleshooting page 67 5 4 2 RS 232 Configuration Debug Port This port is physically an RJ45 connection An RJ45 to DB 9 adapter cable is included with the module This port permits a P
93. ed scan rate defined by the user for the module and the communication load on the module Typical update times range from 1 to 10 milliseconds This bi directional transfer of data is accomplished by the module putting data in the input image to send to the processor Data in the input image is placed in the processor s controller tags by ladder logic The input image is set to 250 words Processor logic inserts data to the output image to be transferred to the module The module s firmware program extracts the data and places it in the module s internal database The output image is set to 248 words The following illustration shows the data transfer method used to move data between the ControlLogix processor the MVI56 MNETC module and the Modbus TCP IP Network ControlLogix Processor MV1I56 E MNETC Module ControlLogix Controller Module s Internal Ladder Database Logic transfers data from module s input image to data areas in the processor TCP IP Stack and Ethernet Client Hard Driver ware Special Function Ladder Blocks Logic Interface transfers data from Backplane Driver processor data areas to output image ProSoft Technology Inc Page 91 of 153 October 26 2011 Reference MVI56 MNETC ControlLogix Platform User Manual Modbus TCP IP Multi Client Communication Module All data transferred between the module and the processor over the backplane is through the input and output images Ladder lo
94. emainder 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 Ad Func Byte Data Coil Data Coil Data Coil Data Coil Data Coil Error r Coun Status 20 Status 28 Status 36 Status 44 Status52 Check t to 27 to 35 to 43 to 51 to 56 Field 11 01 05 CD 6B B2 OE 1B CRC The status of coils 20 to 27 is shown as CD HEX 1100 1101 Binary Reading left to right this shows that coils 27 26 23 22 and 20 are all on The other coil data bytes are decoded similarly Due to the quantity of coil statuses requested the last data field which is shown 1B HEX 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
95. ents 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 Data Start Data Start Data of Regs Data of Regs Error Check Reg Hi Reg Lo Hi Lo Field 11 06 00 01 00 03 CRC ProSoft Technology Inc Page 125 of 153 October 26 2011 Reference MVI56 MNETC ControlLogix Platform User Manual Modbus TCP IP Multi Client Communication Module Response The response to a preset single register request is to re transmit the query message after the register has been altered Adr Func DataReg Data Reg Data Input Reg Data Input Reg Error Check Field Hi Lo i Lo 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 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 f
96. epending on the Modbus Function Code used in the command For Modbus functions 1 2 5 and 15 this parameter is interpreted as a bit level address For Modbus functions 3 4 6 and 16 this parameter is interpreted as a word level or register level address Poll Interval 0 to 65535 This parameter specifies the minimum interval between issuances of a command during continuous command execution Enable code of 1 The parameter is entered in tenths of a second Therefore if a value of 100 is entered for a command the command executes no more frequently than every 10 seconds Reg Count Regs 1 to 125 Coils 1 to 800 This parameter specifies the number of 16 bit registers or binary bits to be transferred by the command Functions 5 and 6 ignore this field as they apply only to a single data point For functions 1 2 and 15 this parameter sets the number of bits inputs or coils to be transferred by the command For functions 3 4 and 16 this parameter sets the number of registers to be transferred by the command ProSoft Technology Inc Page 47 of 153 October 26 2011 Configuring the MVI56 MNETC Module MVI56 MNETC ControlLogix Platform User Manual Modbus TCP IP Multi Client Communication Module Swap Code NONE SwaP WORDS SwaP WORDS amp BYTES SwaP BYTES This parameter defines if and how the order of bytes in data received or sent is to be rearranged This option exists to allow for the fact
97. er an Administrative Tools gt B Documents Ee Internet Explorer a ProSoft Transport Path Editor O Settings gt W Paint A ProSoft Discovery Service Search gt Windows Media Player Help and Support Run Shut Down 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 Gi Untitled ProSoft Configuration Builder File View Project Tools Help Default Project Name Status Ga Default Location A Default Module Please Select Module Type Default Module Unknown Product Line Last Change Last Download module Information Last Change Never Last Download Never Application Rev OS Rev Loader Rev MAC Address Configedit version 2 2 0 Build 1 Module Configuration Module Module Type Module Name Default Module Default Module ProSoft Technology Inc Page 35 of 153 October 26 2011 Configuring the MVI56 MNETC Module MVI56 MNETC ControlLogix Platform User Manual Modbus TCP IP Multi Client Communication Module Adding the MVI56 MNETC module to the project
98. ery Data This uses a sub function code of zero 00 00 hex in the two byte field The data to be returned is sent in the two byte data field A5 37 hex Request Response Field Name Hex Field Name Hex Function 08 Function 08 Sub function Hi 00 Sub function Hi 00 Sub function Lo 00 Sub function Lo 00 Data Hi A5 Data Hi A5 Data Lo 37 Data Lo 27 The data fields in responses to other kinds of queries could contain error counts or other data requested by the sub function code ProSoft Technology Inc October 26 2011 Page 127 of 153 Reference MVI56 MNETC ControlLogix Platform User Manual Modbus TCP IP Multi Client Communication Module 5 5 9 Force Multiple Coils Function Code 15 Query This message forces each coil in a consecutive block of coils to a desired ON or OFF state Any coil that exists within the controller can be forced to either state ON or OFF However because the controller is actively scanning unless the coils are disabled the controller can also alter the state of the coil Coils are numbered from zero coil 00001 zero coil 00002 one and so on The desired status of each coil is packed in the data field one bit for each coil 1 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 v
99. esaeeseeesseaeesaas 52 2 5 Connecting your PC to the Module c ccceesceceeeeeeeeeeeeeeeeeeeseeeeseaeeeseeeeseeeseeeeess 53 2 6 Downloading the Project to the Module Using a Serial COM Port ceeesees 54 3 Ladder Logic 55 3 1 Controller Tags niisiis tidra tank deen ea E eee Pee 56 3 1 1 MVI56 E MNETC Controller Tags ccccccccecceceeeeeeeeeeeeeeeeneeeseaeeseaeeeseaeeteneeeseaeess 56 3 2 User Defined Data Types UDTS eeecceeeeeneeeeeeeeeeeeeeeeeeeeenaeeeeeeaeeeeeeeaeeeeeeaeees 58 3 2 1 MVI56 E MNETC User Defined Data Types c cccecceeeeeeeeeeeeseeeteneeeteieeseneeess 58 3 3 Using Controller Tags rise ses uses nies ete cessed leew Wheel a deen een aa inset aa ia 60 3 4 Controller Tag OV rview ccccccceeeeceneeeeeeeeceaeeeeneeseaeeseaeeesaeeseaeeseaeessneeseeeeeseaeess 61 3 4 1 MNET GC DATA rini ei aae ea paa We eat ial aiid ee tla 61 3 4 2 MNETG GONTROEL niii ean eine ee need eee eee 64 3 4 3 MNETG STATUS 238 aiara aare ara ener is aee i never ieee a a Ea 64 3 4 4 MINE TG UTILA e Aena a aa ee aeaaea a sae ar aiee eena tebe aE A 65 ProSoft Technology Inc October 26 2011 Page 5 of 153 Contents User Manual MVI56 MNETC ControlLogix Platform Modbus TCP IP Multi Client Communication Module 4 Diagnostics and Troubleshooting 67 4 1 WED INGICALOIS 4 seth eet Band ait Gee ice eae 68 4 1 1 Ethernet LED Indicators nesca a A A R A 69 4 1 2 Clearing a Fault Condition
100. ess Hi 04 Exception Code 02 Starting Address Lo Al Quantity of Outputs Hi 00 Quantity of Outputs Lo 01 In this example the Client addresses a request to server device The function code 01 is for a Read Output Status operation It requests the status of the output at address 1245 04A1 hex Note that only that one output is to be read as specified by the number of outputs field 0001 Page 130 of 153 ProSoft Technology Inc October 26 2011 MVI56 MNETC Co ntrolLogix Platform Reference Modbus TCP IP Multi Client Communication Module User Manual If the output address is non existent in the server device the server will return the exception response with the exception code shown 02 This specifies an illegal data address for the server Modbus Exception Codes Code Name Meaning 01 Illegal Function The function code received in the 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
101. f last write block BlockIndex INT Computed block offset for data table StatusIndex INT Computed block offset for status data ReadDataSizeGet INT Gets ReadData array length WriteDataSizeGet INT Gets WriteData array length ReadDataBlkCount INT Holds the value of the block counts of the ReadData array WriteDataBlkCount INT Holds the value of the block counts of the WriteData array RBTSremainder INT Holds remainder calculation value from the read array WBTSremainder INT Holds remainder calculation value from the write array IPsetPending BOOL Allows setting module IP address IPgetPending BOOL Allows getting module IP address InitOutputData MNETCINITOUTDATA Used to bring the module into a known state after a restart operation FaultCode INT Fault Code value Checklnitialization BOOL Check initialization trigger The LastRead tag stores the latest Read Block ID received from the module The LastWrite tag stores the latest Write Block ID to be sent to the module The BlockIndex tag is an intermediate variable used during the block calculation ProSoft Technology Inc Page 65 of 153 October 26 2011 Ladder Logic MVI56 MNETC ControlLogix Platform User Manual Modbus TCP IP Multi Client Communication Module Page 66 of 153 ProSoft Technology Inc October 26 2011 MVI56 MNETC ControlLogix Platform Diagnostics and Troubleshooting Modbus TCP IP Multi Client Communication Module User Manual 4 Diagnostics and Troubleshoot
102. fined oa Strings i Add On Defined ER Predefined Ep Module Defined Trends 1 0 Configuration EJ fas This action opens the Select Module dialog box E Select Module Module Analog Communications Controllers Digital Drives Motion Other 1756 MODULE Generic 1756 Module Allen Bradley Specialty Find Add Favorite By Category Favorites OK Cancel Help 2 Select the 1756 MODULE GENERIC 1756 MODULE from the list and click OK This action opens the New Module dialog box Page 132 of 153 ProSoft Technology Inc October 26 2011 MVI56 MNETC ControlLogix Platform Reference Modbus TCP IP Multi Client Communication Module User Manual 3 Enter the Name Description and Slot options for your application You must select the Comm Format as DATA INT in the dialog box otherwise the module will not communicate Click OK to continue Parameter Value Name Enter a module identification string Example MNETC_2 Description Enter a description for the module Example MopBus TCP IP Mutt CLIENT COMMUNICATION MODULE Comm Format Select DATA INT Slot Enter the slot number in the rack where the MVI56 MNETC module is located Input Assembly Instance 1 Input Size 250 Output Assembly Instance 2 Output Size 248 Configuration Assembly Instance 4 Configuration Size 0 4 Select the Requested Packet Interval value for scanning the I O on
103. form Ladder Logic Modbus TCP IP Multi Client Communication Module User Manual 3 4 Controller Tag Overview Controller Tag Description MNETC DATA MNET input and output data transferred between the processor and the module MNETC CONTROL Governs the data movement between the PLC rack and the module MNETC STATUS Status information MNETC UTIL Block statistics and generic tags used for internal ladder processing DO NOT MODIFY The following sections describe each of these controller tag structures in more detail 3 4 1 MNETC DATA The controller tags in MNETC DATA hold data to be transferred between the processor and the MVI56 MNETC module This read and write data is transferred between the processor and module as pages or blocks of data up to 200 words long The data types for the MNETC DATA ReadData and MNETC DATA WriteData controller tag arrays are integer arrays containing variable numbers of elements Controller Tag Data Type Description ReadData INT x Data read from module Array size is equal to the size set in the configuration WriteData INT x Data to write to module Array size is equal to the size set in the configuration MNETC DATA ReaadData ProSoft Technology Inc Page 61 of 153 October 26 2011 Ladder Logic MVI56 MNETC ControlLogix Platform User Manual Modbus TCP IP Multi Client Communication Module ReadDatais a controller tag array that automatically adjusts
104. g 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 Whenever the Float Flag parameter is set to YES this parameter determines the lowest Modbus Address used in commands to a remote server to consider as commands to read or write floating point data All commands with address values greater than or equal to this value will be considered floating point data commands All commands with address values less than this value will be considered normal 16 bit register data commands This parameter is used only if the Float Flag is set to YES For example if a value of 7000 is entered all commands sent with addresses of 47001 or 407001 and above will be considered as floating point data commands and 32 bits of data will be sent or received for each count of one in the command You will also need to set the Float Offset parameter to an appropriate value whenever the Float Flag parameter is set to YES Float Offset 0 to 9999 This parameter defines the start register for floating point data in the internal database This parameter is used only if the Float Flag is enabled For example if the Float Offset value is set to 3000 and the Float Start parameter is set to 7000 data requests for register 7000 will use the internal Modbus register 3000
105. gic 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 Module s Internal Database Structure 5000 registers for user data 0 Register Data 4999 Data contained in this database is transferred in blocks or pages using the input and output images ControlLogix ladder logic and the MVI56 MNETC module s program work together to coordinate these block transfers Up to 200 words of data can be transferred from the module to the processor read block input image or from the processor to the module write block output image in each block transfer The block structure of each block type depends on the data content and function of the block The module uses the following block identification numbers Block ID Range Descriptions 1 Null block 0 For firmware versions earlier than 2 05 this is a null block For firmware versions 2 05 and newer block 0 contains the same data as block 1 This feature enhances performance especially when using less than 200 words of read write data f Read Register Count in the module configuration file is set gt 200 words Block ID 0 is not used f Read Register Count in the module configuration file is set gt 0 and l
106. h includes all tags used in the program Fault Code value SV Get System Value Class Name Module Instance Name MNETC Attribute Name FauttCode Dest MNETC_2 UTIL FaultCode o Add On for MVISB MNETC and MVISBE MNETC modules AOISEMNETC Add On for MVIS6 MNETC and MVISB AOISEMINETC AOIS6MNETC_2 _ Connection_Input Locat2 1 Data Connection_Output Locat2 0 Data MINETC MNETC_2 gt Sylvia and Matlan Sn 43 3 Author t Editor _ amp RSLogix 5000 My_C The setup procedure is now complete Save the project and download the application to your ControlL Ogix processor ProSoft Technology Inc October 26 2011 Page 31 of 153 Configuring the MVI56 MNETC Module MVI56 MNETC ControlLogix Platform User Manual Modbus TCP IP Multi Client Communication Module Adjusting the Input and Output Array Sizes Note It is unnecessary to manually edit the ReadData and WriteData user defined data types in the ladder logic as these are automatically updated to match the changed array sizes from ProSoft Configuration Builder The module internal database is divided into two user configurable areas Read Data Write Data The Read Data area is moved from the module to the processor while the Write Data area is moved from the processor to the module The MVI56 MNETC Add On Instruction rung is configured for 600 registers of Read Data and 6
107. he maximum capacity of the controller 16 bit for the 184 384 and 584 unused high order bits must be set to zero Note Function codes 5 6 15 and 16 are the only messages that will be recognized as valid for broadcast Adr Func Hi 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 ProSoft Technology Inc Page 129 of 153 October 26 2011 Reference MVI56 MNETC ControlLogix Platform User Manual Modbus TCP IP Multi Client Communication Module 5 5 11 Modbus Exception Responses When a Modbus Client sends a request to a server device it expects a normal response One of four possible events can occur from the Client s query If 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 If the server receives the request but detects a communication error parity LRC CRC no response is returned The Client program will eventually process a timeout condition for
108. he module s internal database and will not be transferred to the processor s ReadData array Enabling the Error Status Pointer is optional Alternatively the error status data for a specific Client can be requested by the processor and returned in a special Client Status block For more information see Client Status Blocks page 104 Command Error Pointer 1 to 4999 This parameter sets the address in the internal database where the Command Error List data will be placed If you want the Command Error List data to be moved to the processor and placed into the ReadData array the value entered should be a module memory address in the Read Data area If the value is set to 1 the Command Error List data will not be stored in the module s internal database and will not be transferred to the processor s ReadData array Enabling the Command Error Pointer is optional Alternatively the Command Error List data for a specific Client can be requested by the processor and returned in a special Client Status block For more information see Client Status Blocks page 104 Minimum Command Delay 0 to 65535 milliseconds This parameter specifies the number of milliseconds to wait between the initial issuances of a command This parameter can be used to delay all commands sent to servers to avoid flooding commands on the network This parameter does not affect retries of a command as they will be issued when failure is recognized Response Timeout
109. he same port that is connected to the module If you are still not able to establish a connection contact ProSoft Technology for assistance Page 72 of 153 ProSoft Technology Inc October 26 2011 MVI56 MNETC ControlLogix Platform Diagnostics and Troubleshooting Modbus TCP IP Multi Client Communication Module User Manual Navigation All of the submenus for this module contain commands to redisplay the menu or return to the previous menu You can always return from a submenu to the next higher menu by pressing M on your keyboard The organization of the menu structure is represented in simplified form in the following illustration Main Menu Child Menu A Child Sub Menu 1 Child Sub Menu 2 Child Sub Menu 3 Child Menu B Child Sub Menu 1 Child Menu C Child Sub Menu 1 Child Sub Menu 2 The remainder of this section shows the menus available for this module and briefly discusses the commands available to you Keystrokes The keyboard commands on these menus are usually not case sensitive You can enter most commands in lowercase or uppercase letters The menus use a few special characters that must be entered exactly as shown Some of these characters will require you to use the SHIFT CTRL or ALT keys to enter them correctly For example on US English keyboards enter the command as SHIFT and Also take care to distinguish the different use
110. iguration Redisplaying the Current Page Press S to display the current page of data Moving Back Through 5 Pages of Registers Press from the Database View menu to skip five pages back in the database to see the 100 registers of data starting 500 registers before the currently displayed page Viewing the Previous Page of Registers Press P from the Database View menu to display the previous page of data ProSoft Technology Inc Page 77 of 153 October 26 2011 Diagnostics and Troubleshooting MVI56 MNETC ControlLogix Platform User Manual Modbus TCP IP Multi Client Communication Module Moving Forward Through 5 Pages of Registers Press from the Database View menu to skip five pages ahead in the database to see 100 registers of data 500 registers ahead of the currently displayed page Viewing the Next Page of Registers Press N from the Database View menu to display the next page of data Viewing Data in Decimal Format Press D from the Database View menu to display the data on the current page in decimal format Viewing Data in Hexadecimal Format Press H from the Database View menu to display the data on the current page in hexadecimal format Viewing Data in Floating Point Format Press F from the Database View menu to display the data on the current page in floating point format The program assumes that the values are aligned on even register boundaries If floating point values are not aligned as such
111. 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 6 Turn power ON Note If you insert the module improperly the system may stop working or may behave unpredictably ProSoft Technology Inc Page 17 of 153 October 26 2011 Start Here MVI56 MNETC ControlLogix Platform User Manual Modbus TCP IP Multi Client Communication Module Page 18 of 153 ProSoft Technology Inc October 26 2011 MVI56 MNETC ControlLogix Platform Modbus TCP IP Multi Client Communication Module Configuring the MVI56 MNETC Module User Manual 2 Configuring the MVI56 MNETC Module In This Chapter Importing the Sample Add On INStructiOn ccceeeeeteeeeeeteneeeeneereaees 20 Connecting Your PC to the ControlLogix ProceSSOl ccseeeeeee 33 Downloading the Sample Program to the Processot c ccceseees 34 Using ProSoft Configuration Builder eeeeseeeseeeeteeeeeeeeseeteeeeenees 35 Connecting your PC to the MOdule cccceeeceeeeceeeeeeeeseeeeeeeeeneeeeeeeeeaes 53 Downloading the Project to the Module Using a Serial COM Poort 54 ProSoft Technology Inc October 26 2011 Page 19 of 153 Configuring the MVI56 MNETC Module MVI56 MNETC ControlLogix Platform User Manual Modbus TCP IP Multi Client Communication Module 2 1 Importing the Sample Add On Instruction Not
112. ing In This Chapter se LED IMGiGators ss csstscccscteiee 2 Silents oes adeedeeana ished Sleanicdechadieesaneadiaiees 68 Using ProSoft Configuration Builder PCB for Diagnostics 71 Reading Status Data from the Module eecceeeeeeeeeeeeeeeteeeeneeeeaees 80 The module provides information on diagnostics and troubleshooting in the following forms LED status indicators on the front of the module provide general information on the module s status Status data contained in the module can be viewed through the Configuration Debug port using the troubleshooting and diagnostic capabilities of ProSoft Configuration Builder PCB Status data values can be transferred from the module to processor memory and can be monitored there manually or by customer created logic ProSoft Technology Inc Page 67 of 153 October 26 2011 Diagnostics and Troubleshooting User Manual MVI56 MNETC ControlLogix Platform Modbus TCP IP Multi Client Communication Module 4 1 LED Indicators The LEDs indicate the module s operating status as follows LED Color Status Indication CFG Green ON Data is being transferred between the module and a remote terminal using the Configuration Debug port OFF No data is being transferred on the Configuration Debug port P1 Green ON Port not used OFF Port not used P2 Green ON Port not used OFF Port not used APP Amber OFF
113. is command to display the current configuration and statistics for the module Opening the Database View Menu Press D to open the Database View menu Use this menu command to view the current contents of the module s database For more information about this submenu see Database View Menu page 77 Opening the Command Error List Menu Press E to open the Command Error List This list consists of multiple pages of command list error status data Press to view a list of commands available on this menu Opening the Command List Menu Press I to open the Command List menu Use this command to view the configured command list for the module Receiving the Configuration File Press R to download receive the current configuration file from the module Sending the Configuration File Press S to upload send a configuration file from the module to your PC Resetting Diagnostic Data Press U to reset the status counters for the Client in the module Viewing Version Information Press V to view version information for the module Use this command to view the current version of the software for the module as well as other important values You may be asked to provide this information when calling for technical support on the product Values at the bottom of the display are important in determining module operation The Program Scan Counter value is incremented each time a module s program cycle is complete Tip Repea
114. is located in Slot 1 of the local rack this step is not required ProSoft Technology Inc Page 25 of 153 October 26 2011 Configuring the MVI56 MNETC Module MVI56 MNETC ControlLogix Platform User Manual Modbus TCP IP Multi Client Communication Module 6 Click OK to confirm the import RSLogix will indicate that the import is in progress Importing Creating routine Prescan When the import is completed the new rung with the Add On Instruction will be visible as shown in the following illustration f RSLogix 5000 My_Controller 1756 L63 MainProgram MainRoutine BAE amp File Edit Yiew Search Logic Communications Tools Window Help alsa S e gt 7 BIS e LI Aal Offline J E RUN z5 m Epa rr No Forces a er No Edits a mo m x ENE Java ed EE EE A ja Py Si Controller My_Controller it Jl I f l 3 El A Controller Tags Controller Fault Handler This defines the Power Up Handler whole module which 5 6 Tasks includes all tags Ez MainTask used in the program amp MainProgram coe as sae Program Tags Get System Value MainRoutine Class Name Module Unscheduled Programs Instance Name MNETC amp Motion Groups Attribute Name FaultCode Ungrouped Axes Dest MNETC UTIL FaulttCode Add On Instructions g 8 AOIS6MNETC Parameters and Local Tags Add On for E Logic MVI56 MNETC and E Prescan oe we EE ie AOKENNETC Add On for MVI56 MNETC and MVI56 MRETCELOCKSTATS AOISEMNETC AOISEMNETC
115. is parameter it tells the customer that there are events waiting on that specific client In this case it would be events on client 1 0 29 Block 4100 Sending this block will display the result of each command sent customer needs to input what client he wants to poll from and trigger the block as shown The response will be the event count and error code for each event A value of 0 in the error code means there was no error detected MNETC STATUS EventSeqCmd MNETC STATUS EventS eq MNETC STATUS EventSeqCmd ClientID MNETC STATUS EventSeqCmd Client MNETC STATUS EventSeqCmd Client 0 MNETC STATUS EventSeqCmd Client 1 MNETC STATUS EventSeqCmd Client 1 Count MNETC STATUS EventSeqCmd Client 1 Cmd MNETC STATUS EventSeqCmd Client 1 Cmd 0 MNETC STATUS EventSeqCmd Client 1 Cmd 0 Sequence MNETC STATUS EventSeqCmd Client 1 Cmd 0 Error MNETC STATUS EventSeqCmd Client 1 Cmd 1 MNETC STATUS EventSeqCmd Client 1 Cmdf1 Sequence MNETC STATUS EventSeqCmd Client 1 Cmdf1 Error MNETC STATUS EventSeqCmd Client 1 Cma 2 MNETC STATUS EventSeqCmd Client 1 Cmd 2 Sequence MNETC STATUS EventSeqCmd Client 1 Cma 2 E rror MNETC STATUS EventS eqCmd Client 1 Cmd 3 MNETC STATUS EventSeqCmd Client 1 Cmd 3 Sequence MNETC STATUS EventSegCmd Client 1 Cmd 3 Error MNETC STATUS EventSeqCmd Client 1 Cmad 4 MNETC STATUS EventSeqCmd Client 1 Cmd 4 Sequence MNETC STATUS EventSeqCmd Client 1 Cmd
116. its loss of savings or revenue loss of use of the product or any associated equipment loss of data cost of capital cost of any substitute equipment facilities or services downtime the claims of third parties including customers of the Purchaser and injury to property Some areas do not allow time limitations on an implied warranty or allow the exclusion or limitation of incidental or consequential damages In such areas the above limitations may not apply This Warranty gives you specific legal rights and you may also have other rights which vary from place to place 6 2 7 Time Limit for Bringing Suit Any action for breach of warranty must be commenced within 39 months following shipment of the Product 6 2 8 No Other Warranties Unless modified in writing and signed by both parties this Warranty is understood to be the complete and exclusive agreement between the parties suspending all oral or written prior agreements and all other communications between the parties relating to the subject matter of this Warranty including statements made by salesperson No employee of ProSoft or any other party is authorized to make any warranty in addition to those made in this Warranty The Customer is warned therefore to check this Warranty carefully to see that it correctly reflects those terms that are important to the Customer 6 2 9 Allocation of Risks This Warranty allocates the risk of product failure between ProSoft and the
117. ize 248 Configuration Assembly Instance 4 Configuration Size 0 Important You must select the Comm Format as DATA INT in the dialog box otherwise the module will not communicate over the backplane of the ControlLogix rack 4 Click OK to continue Page 22 of 153 ProSoft Technology Inc October 26 2011 MVI56 MNETC ControlLogix Platform Configuring the MVI56 MNETC Module Modbus TCP IP Multi Client Communication Module User Manual 5 Edit the Module Properties Select the Requested Packet Interval value for scanning the I O on the module This value represents the minimum frequency at which the module will handle scheduled events This value should not be set to less than 1 millisecond The default value is 5 milliseconds Values between 1 and 10 milliseconds should work with most applications W Module Properties Local 1 1756 MODULE 1 1 General Connection Module Info Backplane Requested Packet Interval RPI 5 0 ms 0 2 750 0 ms I Inhibit Module I Major Fault On Controller If Connection Fails While in Run Mode Module Fault Status Offline Cancel Help 6 Save the module Click OK to close the dialog box Notice that the module now appears in the Controller Organization window amp Controller My_Controller Controller Tags Controller Fault Hander Power Up Handler amp Tasks 5 a MainTask G MainProgram Unscheduled Programs amp Motion Groups Ungrouped Axes Add
118. k allows the processor to reset all status values available from the module to the processor or through the PCB diagnostics menu This block is triggered through the following data type and controller tag elements BB Data Type MNETCCONTROL Neco MNETCOONTROL Description Values used by program foe data trancler operation between the module 4nd the processor Members Data Type Size 954 byte s Tienet used to clear both cold and warm boot requests Hardware reset of the Module Configurahon data reset in the Module 5 Event Command Trigger ChenlD INT Decmal Chent IO to poll status on remote server EvertCind MNETCEVENTCMD 30 Holds Even Command configuration Cmad INT Decma Coerenand ID from 1 to 16 CmdCortrot MNETCOMDCONTROL Holds Comenand Control statistics CmdCortsclPending B00L Decms Halts rung urtl Module i ready CmaCortsolT ngger BOOL Decmal Coermnand Control Trigger IP ddess MNETCIPADDRESS Getting and Setting IP address to and hom Modde gt age Morena ca ES MNETC ERS MNETCMO MNETC DATA ES MNETCDA fes MNETCCO MNETC CONTROL BootT imer 25 gt TIMER MNETC CONTROL ColdBoot 0 Decimal BOOL MNETC CONTROL WarmBoot 0 Decimal BOOL MNETC CONTROL ResetStatus 0 Decimal BOOL MNETC CONTROL EventCmdT rigger 0 Decimal BOOL MNETC CONTROL ChertiD 10 Decimal INT Set Module IP Address Block 9990 Block Request from Processor to Module Word Offset Description Length 0 9990
119. l Modbus TCP IP Multi Client Communication Module 1 1 System Requirements The MVI56 MNETC module requires the following minimum hardware and software components Rockwell Automation ControlLogix processor with compatible power supply and one free slot in the rack for the MVI56 MNETC module The module requires 800 mA of available power Rockwell Automation RSLogix 5000 programming software version 2 51 or higher Rockwell Automation RSLinx communication software Pentium II 450 MHz minimum Pentium III 733 MHz or better recommended Supported operating systems o Microsoft Windows XP Professional with Service Pack 1 or 2 o Microsoft Windows 2000 Professional with Service Pack 1 2 or 3 o Microsoft Windows Server 2003 128 Mbytes of RAM minimum 256 Mbytes of RAM recommended 100 Mbytes of free hard disk space or more based on application requirements 256 color VGA graphics adapter 800 x 600 minimum resolution True Color 1024 O 768 recommended CD ROM drive ProSoft Configuration Builder HyperTerminal or other terminal emulator program Note You can install the module in a local or remote rack For remote rack installation the module requires EtherNet IP or ControlINet communication with the processor Page 12 of 153 ProSoft Technology Inc October 26 2011 MVI56 MNETC ControlLogix Platform Start Here Modbus TCP IP Multi Client Communication Module User Manual 1 2 Package Conten
120. lectual 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 other intellectual property e Customer agrees that it shall not and shall not authorize others to copy software provided by ProSoft except as expressly permitted in any license agreement accompanying such software transfer software to a third party separately from the Product modify alter translate decode decompile disassemble reverse engineer or otherwise attempt to derive the source code of the software or create
121. line dialog box click the GENERAL tab This tab shows information about the processor including the Revision firmware version In the following illustration the firmware version is 11 32 Connected To Go Online xi Minor Faults Redundancy Nonvolatile Memory Options General Date Time Major Faults Vendor Allen Bradley Type 1756 L55 A 1756 M13 A ControlLogix5555 Controller Revision 11 32 Name Description Chassis Type Slot Mode Select File Cancel Help 6 Select the sample ladder logic file for your firmware version To open the sample program 1 Onthe Connected to Go Online dialog box click the SELECT FILE button 2 Choose the sample program file that matches your firmware version and then click the SELECT button 3 RSLogix will load the sample program The next step is to configure the correct controller type and slot number for your application ProSoft Technology Inc Page 137 of 153 October 26 2011 Reference MVI56 MNETC ControlLogix Platform User Manual Modbus TCP IP Multi Client Communication Module 5 7 2 Choosing the Controller Type The sample application is for a 1756 L63 ControlLogix 5563 Controller If you are using a different model of the ControlLogix processor you must configure the sample program to use the correct processor model 1 Inthe Controller Organization list select the folder for the controller and then click the right mouse
122. lowed all of the above steps and it will not stop the driver then make sure you do not have RSLogix open If RSLogix is not open and you still cannot stop the driver then reboot your PC ProSoft Technology Inc Page 117 of 153 October 26 2011 Reference MVI56 MNETC ControlLogix Platform User Manual Modbus TCP IP Multi Client Communication Module 5 4 3 DB9 to RJ45 Adaptor Cable 14 Cable Assembly o GOGO ol QBOG0 qj J1 Vv Vv Vv J2 5 EN DCD D TXD E re oe i RXD RXD 5 AE TXD SH HS GY i GND GND GND i 5 DSR RXD gt a i f RTS i i o E CTS TXRXD TXD yog nie T Y Wiring Diagram Page 118 of 153 ProSoft Technology Inc October 26 2011 MVI56 MNETC ControlLogix Platform Reference Modbus TCP IP Multi Client Communication Module User Manual 5 5 Modbus Protocol Specification The following pages give additional reference information regarding the Modbus protocol commands supported by the MVI56 MNETC 5 5 1 About the MODBUS TCP Protocol MODBUS is a widely used protocol originally developed by Modicon in 1978 Since that time the protocol has been adopted as a standard throughout the automation industry The original MODBUS specification uses a serial connection to communicate commands and data between Client and server devices on a network Later enhance
123. mage 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 MVI56 MNETC into the ControlLogix chassis Use the same technique recommended by Rockwell Automation to remove and install ControlLogix modules Warning When you insert or remove the module while backplane power is on an electrical arc can occur This could cause an explosion in hazardous location installations 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 Turn power OFF 2 Align the module with the top and bottom guides and slide it into the rack until the module is firmly against the backplane connector Page 16 of 153 ProSoft Technology Inc October 26 2011 MVI56 MNETC ControlLogix Platform Start Here Modbus TCP IP Multi Client Communication Module User Manual 3 With a firm but steady push snap the module into place 4 Check that the holding clips on the top and bottom of the module are securely in the locking holes of the rack 5 Make a note of the slot location You must identify the slot
124. ments to the protocol allow communication over Ethernet networks using TCP IP as a wrapper for the MODBUS protocol This protocol is known as MODBUS TCP MODBUS TCP is a Client server protocol The Client establishes a connection to the remote server When the connection is established the Client sends the MODBUS TCP commands to the server The MVI56 MNETC module simulates up to 30 Clients Aside from the benefits of Ethernet versus serial communications including performance distance and flexibility for industrial networks the MODBUS TCP protocol allows for remote administration and control of devices over an Internet connection It is important to note that not all Internet protocols are implemented in the module for example HTTP and SMTP protocols are not available Nevertheless the efficiency scalability and low cost of a MODBUS TCP network make this an ideal solution for industrial applications The MVI56 MNETC module acts as an input output module between devices on a MODBUS TCP network and the Rockwell Automation backplane The module uses an internal database to pass data and commands between the processor and the server devices on the MODBUS TCP network ProSoft Technology Inc Page 119 of 153 October 26 2011 Reference MVI56 MNETC ControlLogix Platform User Manual Modbus TCP IP Multi Client Communication Module 5 5 2 Read Coil Status Function Code 01 Query This function allows the user to obtain the ON OF
125. nd network configuration Sample Ladder Logic and Add On Instructions AOI are used for data transfer between module and processor and module configuration Personality Module non volatile CF card used to store configuration allowing for quick in the field product replacement Remote or local rack 5 1 2 Modbus TCP IP 10 100 MB Ethernet port Module I O data memory mapping supports up to 5000 registers and is user definable ProSoft Configuration Builder PCB software supported a Windows based graphical user interface providing simple product and network configuration Sample Ladder Logic and Add On Instructions AOI are used for data transfer between module and processor and module configuration Personality Module non volatile CF card used to store configuration allowing for quick in the field product replacement Page 88 of 153 ProSoft Technology Inc October 26 2011 MVI56 MNETC ControlLogix Platform Reference Modbus TCP IP Multi Client Communication Module User Manual 5 1 3 Functional Specifications The MVI56 MNETC will operate on a local or remote rack This module was created to improve the performance when servers are not needed on a Modbus TCP IP network The module supports up to 30 Clients with up to 16 commands for each Client making it easy to enable disable the commands from the ladder logic The Client command control word contains one bit for each command This module does not support th
126. ntroller Program Show Show All Import Configuration Tags Data Types Add On Instructions ADISEMNETC_2 Local2 gt AOIS6MNETC AB 1756_MOD AB 1756_MODULE_INT_SOOBytes 0 AB 1756_MODULE_INT_496Bytes 0 0 AB 1756_MODULE C 0 AB 1756_MODULE_INT_S00Bytes 1 0 AB 1756_MODULE_INT_496Bytes 0 0 Local 2 1 ABA 756_MOD Discard Local 2 0 xl j Local 1 0 g Local 2 C S Local 2 MNETC Controller J Program Show Show All ABA 756_MOD Use Existing AB 1756_MODULE_INT_496Bytes 0 0 AB 1756_MODULE C 0 AB 1756_MODULE_INT_SOOBytes 1 0 AB 1756_MODULE_INT_496Bytes 0 0 MNETCMODULEDEF Page 30 of 153 ProSoft Technology Inc October 26 2011 MVI56 MNETC ControlLogix Platform Configuring the MVI56 MNETC Module Modbus TCP IP Multi Client Communication Module User Manual 11 Change the default tags MNETC and AOJS6MNETC to avoid conflict with existing tags In this step you should append a string to the default tag names such as _2 as shown in the following illustration Import Configuration Tags Data Types Add On Instructions AOISEMNETC Create New Nams A AlissFor Data Type AOISEMNETC_2 Local 2 1 Local 2 0 MNETC_2 12 Click OK to confirm 4B 1756_MOD AB 1756_MOD MNETCMODU F RSLogix 5000 My Controller 1756 1 63 MainProgram MainRoutine Ef Ele Edit view Search Logic Communications Tools Window Help alsel S
127. nvenient location on your hard drive Page 14 of 153 ProSoft Technology Inc October 26 2011 MVI56 MNETC ControlLogix Platform Start Here Modbus TCP IP Multi Client Communication Module User Manual 1 4 Setting Jumpers The Setup Jumper acts as write protection for the module s flash memory In write protected mode the Setup pins are not connected and the module s firmware cannot be overwritten Do not jumper the Setup pins together unless you are directed to do so by ProSoft Technical Support The following illustration shows the MVI56 MNETC jumper configuration SETUP SETUP SHUNT A Qo NOT JUMPERED Note If you are installing the module in a remote rack you may prefer to leave the Setup pins jumpered That way you can update the module s firmware without requiring physical access to the module ProSoft Technology Inc Page 15 of 153 October 26 2011 Start Here MVI56 MNETC ControlLogix Platform User Manual Modbus TCP IP Multi Client Communication Module 1 5 Installing the Module in the Rack If you have not already installed and configured your ControlLogix processor and power supply please do so before installing the MVI56 MNETC 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 da
128. ny license agreement accompanying such software or other intellectual property 6 2 1 What Is Covered By This Warranty a Warranty On New Products ProSoft warrants to the original purchaser that the Product that is the subject of the sale will 1 conform to and perform in accordance with published specifications prepared approved and issued by ProSoft and 2 will be free from defects in material or workmanship provided these warranties only cover Product that is sold as new This Warranty expires three 3 years from the date of shipment for Product purchased on or after January 1st 2008 or one 1 year from the date of shipment for Product purchased before January 1st 2008 the Warranty Period If the Customer discovers within the Warranty Period a failure of the Product to conform to specifications or a defect in material or workmanship of the Product the Customer must promptly notify ProSoft by fax email or telephone In no event may that notification be received by ProSoft later than 39 months from date of original shipment Within a reasonable time after notification ProSoft will correct any failure of the Product to conform to specifications or any defect in material or workmanship of the Product with either new or remanufactured replacement parts ProSoft reserves the right and at its sole discretion may replace unrepairable units with new or remanufactured equipment All replacement units will be covered under warranty for
129. o determine the types of commands to be issued to servers on the Modbus TCP IP network 2 When configured the Client driver begins transmitting read and or write commands to servers on the network The data for write commands is obtained from the module s internal database 3 Assuming successful processing by the server specified in the command a response message is received into the Client driver for processing Page 112 of 153 ProSoft Technology Inc October 26 2011 MVI56 MNETC ControlLogix Platform Reference Modbus TCP IP Multi Client Communication Module User Manual 4 Data received from the server is passed into the module s internal database if the command was a read command General module status information is routinely returned to the processor in the input images Status data for a specific Client can be requested by the processor and returned in a special Client Status block Special functions such as Event Commands and Command Control options can be generated by the processor and sent to the Client driver for action 5 3 2 Client Command List In order for the Client to function the module s Client Command List must be defined in the MNET Client x Commands section of the configuration This list contains up to 16 individual entries with each entry containing the information required to construct a valid command This includes the following Command enable mode 0 disabled or 1 continuous IP address and
130. 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 Ad Fun Data Start Reg Data Start Reg Data of Data of Regs Error Check r c Hi Lo Regs Hi Lo Field 11 03 00 6B 00 03 CRC Page 122 of 153 ProSoft Technology Inc October 26 2011 MVI56 MNETC ControlLogix Platform Reference Modbus TCP IP Multi Client Communication Module 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 the server interface device is normally serviced at the end of the controller s scan the data will reflect the register content at the end of the scan Some servers will limit the quantity of register content provided each scan thus for large register quantities multiple transmissions will be made using register content from sequential scans In the example below the registers 40108 to 40110 have the decimal c
131. ock 4000 101 Block 4100 102 Block 4200 103 Cc Cable Connections 114 Choosing the Controller Type 138 Clearing a Fault Condition 69 Client Command Errors 84 113 Client Command List 113 Client Driver 112 Client Error Status Pointer 41 80 Client Status Blocks 3000 to 3029 41 80 81 104 Cold Boot Block 9999 110 Command Control Blocks 5001 5016 46 105 Command Entry Formats 45 Command Error Delay 43 Command Error Pointer 41 80 Command List Entry Errors 85 Command List Overview 44 Commands Supported by the Module 44 Comment 50 Configuration Error Word 83 Configuring Module Parameters 37 Configuring the MVI56 MNETC Module 19 Connecting Your PC to the ControlLogix Processor 33 Connecting your PC to the Module 53 Contacting Technical Support 143 145 Controller Tag Overview 61 Controller Tags 56 141 Controlling Law and Severability 150 Creating a New RSLogix 5000 Project 20 Creating Optional Comment Entries 38 Creating the Module 21 D Data Flow between MVI56 MNETC Module and Processor 111 DB9 to RJ45 Adaptor Cable 14 118 Diagnostics Function Code 08 126 Diagnostics and Troubleshooting 9 67 115 Disabling the RSLinx Driver for the Com Port on the PC 116 Disclaimer of all Other Warranties 149 Disclaimer Regarding High Risk Activities 148 Downloading the Project to the Module
132. ode 03 122 Read Input Registers Function Code 04 123 Read Input Status Function Code 02 121 Read Register Count 39 62 Read Register Start 39 Reading Status Data from the Module 80 Receiving the Configuration File 75 Redisplaying the Current Page 77 Reference 9 87 Reg Count 47 Renaming an Object 37 Reset Module Status Block 9971 MNETC 108 Resetting Diagnostic Data 75 Response Timeout 41 Retry Count 42 Return Material Authorization RMA Policies and Conditions 145 Returning Any Product 145 Returning to the Main Menu 78 79 Returning Units Out of Warranty 146 Returning Units Under Warranty 146 RS 232 Configuration Debug Port 115 S Select Priority Read Block Write Block Offset 247 96 Selecting the Slot Number for the Module 139 Sending the Configuration File 75 Service Port 48 Set Module IP Address Block 9990 108 Setting Jumpers 15 Setting Module Parameters 37 Setting Up the Project 35 Slave Address 49 Page 152 of 153 ProSoft Technology Inc October 26 2011 MVI56 MNETC ControlLogix Platform Index Modbus TCP IP Multi Client Communication Module User Manual Special Function Blocks 64 97 Standard Modbus Exception Code Errors 84 Start Here 9 11 Static ARP Table 51 Status Data Definition 64 80 81 94 104 Status Data in Read Block 94 Sub function Codes Supported 126 Supp
133. odule This data is set in the output image WriteBlock from the ladder logic 239 to 240 Product Code The product ID code for the module 241 Product Version The firmware version number for the module Status information transferred in the Read block can be viewed in the MNETC STATUS controller tag in the ladder logic For more information see the Status Data Definition page 81 Page 94 of 153 ProSoft Technology Inc October 26 2011 MVI56 MNETC ControlLogix Platform Reference Modbus TCP IP Multi Client Communication Module User Manual Write Block These blocks of data transfer information from the ControlLogix processor to the module The following table describes the structure of the output image Write Block from Processor to Module Word Offset Description Length 0 Write Block ID 1 1 to 200 Write Data 200 201 to 230 Command bit data for Clients set 30 231 to 246 Spare 16 247 Select Priority Read Block 1 The Write Block ID is an index value used to determine the location in the module s database where the data will be placed Each transfer can move up to 200 words block offsets 1 to 200 of data ProSoft Technology Inc Page 95 of 153 October 26 2011 Reference MVI56 MNETC ControlLogix Platform User Manual Modbus TCP IP Multi Client Communication Module Select Priority Read Block Write Block Offset 247 Note The Select Priority Read Block feature is only available
134. odule to test Click the right mouse button to open a shortcut menu Default Project lt Default Location h BEES 2 On the shortcut menu choose DIAGNOSTICS Default Project GJ Default Location a h EELEE Delete Rename Copy Choose Module Type View Configuration Export Configuration File s Load Config File Download from PC to Device Upload from Device to PC This action opens the Diagnostics dialog box ProSoft Technology Inc Page 71 of 153 October 26 2011 Diagnostics and Troubleshooting MVI56 MNETC ControlLogix Platform User Manual Modbus TCP IP Multi Client Communication Module 3 Press to open the Main menu 4 Diagnostics Connection Log Module i OF O Time 14 41 43 Main Menu selected What Appears Here Varies by Product Type Path Serial Com 3 If there is no response from the module follow these steps 1 Click to configure the connection On the Connection Setup dialog box select a valid com port or other connection type supported by the module sas Connection Setup Select Connection Type Com 1 X Ethernet m ProSoft Discovery Service PDS oa ClPconnect i Cancel 2 Verify that the null modem cable is connected properly between your computer s serial port and the module A regular serial cable will not work 3 On computers with more than one serial port verify that your communication program is connected to t
135. ommunication Module 2 6 Downloading the Project to the Module Using a Serial COM Port For the module to use the settings you configured you must download copy the updated Project file from your PC to the module To download the project file 1 Inthe tree view in ProSoft Configuration Builder click once to select the module 2 Right click the module icon to open a shortcut menu From the shortcut menu choose DOWNLOAD FROM PC TO DEVICE The program will scan your PC for a valid com port this may take a few seconds When PCB has found a valid COM port the Download dialog box will open Download files from PC to module STEP 1 Select Communication Path Select Connection Type Com 3 Ethernet CIPconnect STEP 2 Transfer File s DOWNLOAD 3 Choose the COM port to use from the dropdown list and then click the DOWNLOAD button The module will perform a platform check to read and load its new settings When the platform check is complete the status bar in the Download dialog box will display the message Module Running Download files from PC to module Module Running STEP 1 Select Communication Path Select Connection Type Com 3 kl Ethernet f CIPconnect STEP 2 Transfer File s DOWNLOAD Test Connection Page 54 of 153 ProSoft Technology Inc October 26 2011 MVI56 MNETC ControlLogix Platform Ladder Logic Modbus TCP IP Multi Client Communication Module User Manual
136. ommunication Module User Manual 5 7 5 Adding the Sample Ladder to an Existing Application 1 Copy the Controller Tags page 56 from the sample program 2 Copy the User Defined Data Types page 58 from the sample program 3 Copy the Ladder Rungs from the sample program 4 Save and Download page 34 page 140 the new application to the controller and place the processor in RUN mode ProSoft Technology Inc Page 141 of 153 October 26 2011 Reference MVI56 MNETC ControlLogix Platform User Manual Modbus TCP IP Multi Client Communication Module Page 142 of 153 ProSoft Technology Inc October 26 2011 MVI56 MNETC ControlLogix Platform Support Service amp Warranty Modbus TCP IP Multi Client Communication Module User Manual 6 Support Service amp Warranty In This Chapter Contacting Technical Support 0 02 eeeeeeceeeeeeteneeeeeeeteaeeteaeeteaeeseeeenaas 143 Return Material Authorization RMA Policies and Conditions 145 LIMITED WARRANTY cc ccecceecceeeeeeeeeeeeeeeececeeecaeesaeeneeeeeeeseetnees 147 Contacting Technical Support ProSoft Technology Inc ProSoft is committed to providing the most efficient and effective support possible Before calling please gather the following information to assist in expediting this process 1 Product Version Number 2 System architecture 3 Network details If the issue is hardware related we will also need information regarding
137. on De Generic 1756 Module Allen Bradley Eind Add Favorite By Vendor Favorites By Category Cancel Help 3 Fill the module properties as follows Parameter Value Name Enter a module identification string Example MNETC_2 Description Enter a description for the module Example Mopgus TCP IP MULTI CLIENT COMMUNICATION MODULE Comm Format Select DATA INT Slot Enter the slot number in the rack where the MVI56 MNETC module is located Input Assembly Instance 1 Input Size 250 Output Assembly Instance 2 Output Size 248 Configuration Assembly Instance 4 Configuration Size 0 ProSoft Technology Inc October 26 2011 Page 27 of 153 Configuring the MVI56 MNETC Module MVI56 MNETC ControlLogix Platform User Manual Modbus TCP IP Multi Client Communication Module 4 Click OK to confirm The new module is now visible Controller My_Controller A Controller Tags Controller Fault Handler Power Up Handler amp Tasks MainTask Unscheduled Programs Motion Groups Add On Instructions Data Types Trends amp 1 0 Configuration 6 1756 Backplane 1756 A4 fa 0 1756 163 My_Controller 1 1756 MODULE MNETC fi E 2 1756 MODULE MNETC_2 Expand the TASKS folder and then expand the MAINTASK folder In the MAINPROGRAM folder double click to open the MAINROUTINE ladder Select an empty rung in the routine and then
138. ontents 555 0 and 100 respectively Adr Func ByteCn Hi Data Lo Hi Data Lo Hi Data Lo Error Check t Data Data Data 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 Ad Fun Data Start Data Start Reg Data ofRegs Data ofRegs Error Check r c Reg Hi Lo Hi Lo Field 11 04 00 08 00 01 CRC ProSoft Technology Inc Page 123 of 153 October 26 2011 Reference MVI56 MNETC ControlLogix Platform User Manual Modbus TCP IP Multi Client Communication Module 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 2 bytes each with the binary content right justified within each pair of characters The firs
139. or For every command that has an error the module automatically sets the poll delay parameter to 30 seconds This instructs the module to wait 30 seconds until it attempts to issue the command again As the commands in the Client Command Last are polled and executed an error value is maintained in the module for each command This error list can be transferred to the processor Standard Modbus Exception Code Errors Code Description Illegal function Illegal data address Illegal data value Failure in associated device Acknowledge O an R oO rm Busy message was rejected Page 84 of 153 ProSoft Technology Inc October 26 2011 MVI56 MNETC ControlLogix Platform Diagnostics and Troubleshooting Modbus TCP IP Multi Client Communication Module User Manual Module Communication Error Codes Code Description 2 Timeout while transmitting message 11 Timeout waiting for response after request Same as 36 253 Incorrect slave server address in response 254 Incorrect function code in response 255 Invalid CRC LRC value in response MNET Client Specific Errors Code Description 33 Failed to connect to server specified in command 35 Invalid length of response message 36 MNET command response timeout Same as 11 37 TCP IP connection ended before session finished Command List Entry Errors Code Description
140. 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 Data Discrete Data Discrete Error Check Count Input 10197 to Input10205to Input 10213to Field 10204 10212 10218 11 02 03 AC DB 35 CRC The status of inputs 10197 to 10204 is shown as AC HEX 10101 1100 binary Reading left to right this show that inputs 10204 10202 and 10199 are all on The other input data bytes are decoded similar Due to the quantity of input statuses requested the last data field which is shown as 35 HEX 0011 0101 binary contains the status of only 6 inputs 10213 to 102180 instead of 8 inputs The two left most bits are provided as zeros to fill the 8 bit format 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
141. ort Service amp Warranty 9 143 Swap Code 48 System Requirements 12 T Time Limit for Bringing Suit 150 Transferring WATTCP CFG to the Module 78 Transferring WATTCP CFG to the PC 79 Troubleshooting 69 U User Defined Data Types UDTs 58 141 Using Controller Tags 60 Using ProSoft Configuration Builder 35 Using ProSoft Configuration Builder PCB for Diagnostics 62 63 71 80 Using the Diagnostic Window in ProSoft Configuration Builder 71 Using the Sample Program 20 135 V Viewing Block Transfer Statistics 74 Viewing Client Configuration 76 Viewing Client Status 76 Viewing Data in ASCII Text Format 78 Viewing Data in Decimal Format 78 Viewing Data in Floating Point Format 78 Viewing Data in Hexadecimal Format 78 Viewing Module Configuration 75 Viewing NIC Status 76 Viewing Register Pages 77 Viewing the Next Page of Registers 78 Viewing the Previous Page of Registers 77 Viewing the Static ARP Table 76 Viewing the WATTCP CFG File on the module 79 Viewing Version Information 75 Ww Warm Boot Block 9998 110 Warm Booting the Module 76 Warnings 3 What Is Covered By This Warranty 147 149 What Is Not Covered By This Warranty 148 Write Block 95 Write Register Count 40 63 Write Register Start 39 Y Your Feedback Please 2 ProSoft Technology Inc Page 153 of 153 October 26 2011
142. our project 8 Copy the Ladder Rungs from the sample program into your project Page 134 of 153 ProSoft Technology Inc October 26 2011 MVI56 MNETC ControlLogix Platform Reference Modbus TCP IP Multi Client Communication Module User Manual 5 7 Using the Sample Program If your processor uses RSLogix 5000 version 15 or earlier you will not be able to use the Add On Instruction for your module Follow the steps below to obtain and use a Sample program for your application 5 7 1 Opening the Sample Program in RSLogix The sample program for your MVI56 MNETC module includes custom tags data types and ladder logic for data I O status and command control For most applications you can run the sample program without modification or for advanced applications you can incorporate the sample program into your existing application Download the manuals and sample program from the ProSoft Technology web site You can always download the latest version of the sample ladder logic and user manuals for the MVI56 MNETC module from the ProSoft Technology website at www prosoft technology com support downloads http www prosoft technology com support downloads From that link navigate to the download page for your module and choose the sample program to download for your version of RSLogix 5000 and your processor ProSoft Technology Inc Page 135 of 153 October 26 2011 Reference MVI56 MNETC ControlLogix Platform User Manual
143. p code for the data This function is only valid for function codes 3 and 4 Function Enter the Modbus function code for the command Address Enter the database address for the server When these values have been entered set the bit in MNETC CONTROL EventCmdTrigger to one 1 to trigger the execution of the Event Command Block 4000 Functionality of block 4000 is identical to block 2000 with the exception that an extra parameter is added Sequence number MNETC CONTROLEventSeqCmd MNETC CONTROL EventSeqCmd Trigger MNETC CONTROL EventSeqCmd ClientID MNETC CONTROL EventSeqCmd IPO MNETC CONTROL EventSeqCmd P1 MNETC CONTROL EventSeqCmd IP2 MNETC CONTROL EventSeqCmd IP3 MNETC CONTROL EventSeqCmd ServPort MNETC CONTROL EventSeqCmd Node MNETC CONTROL EventSeqCmd DBAddress MNETC CONTROL EventSeqCmd Count MNETC CONTROL EventSeqlmd Swap MNETC CONTROL EventSeqCmd Function MNETC CONTROL EventSeqCmd Address MNETC CONTROL EventSeqCmd Sequence 2001 ProSoft Technology Inc Page 101 of 153 October 26 2011 Reference User Manual MVI56 MNETC ControlLogix Platform Modbus TCP IP Multi Client Communication Module When the event is sent it will also trigger the event sequence ready bit shown below MNETC STATUS CmdErrorList MNETC STATUS EventSeqlmdPending MNETC STATUS EventSeglmd MNETC STATUS EventSeqReady 1 2 0000_0000_0000_0000_0000_0000_0000 When a bit is on th
144. put Output Modbus Modbus Input Input Block Request from Module to Processor Word Offset Description Length 0 Reserved 1 1 1000 to 1024 1 2 to 248 Spare 247 249 1000 to 1024 1 Ladder logic subtracts 1000 from the value contained in word 249 to determine a block index This bock index determines which 200 word block of data will be taken from the ReadData array and placed in the output image to be returned to the module Block Response from Processor to Module Word Offset Description Length 0 1000 to 1024 1 1 to 200 Output data to preset in module 200 201 to 247 Spare 47 Page 98 of 153 ProSoft Technology Inc October 26 2011 MVI56 MNETC ControlLogix Platform Reference Modbus TCP IP Multi Client Communication Module User Manual Event Command Blocks 2000 to 2029 Note When using the Event Command Block 2000 amp 4000 for polling operations at least one command needs to be cconfigured in client even if the command is disabled During routine operation the module continuously cycles through the user defined MNET Client x Command List page 43 for each Client examining commands in the order they are listed and sending enabled commands on the network However the module also has a special command priority queue which is an internal buffer that holds commands from special function blocks until they can be sent on the network When one or more commands appear in the command priority queue
145. ransfer Blocks page 93 Page 38 of 153 ProSoft Technology Inc October 26 2011 MVI56 MNETC ControlLogix Platform Configuring the MVI56 MNETC Module Modbus TCP IP Multi Client Communication Module User Manual Read Register Start 0 to 4999 The Read Register Start parameter specifies the start of the Read Data area in module memory Data in this area will be transferred from the module to the processor Note Total user database memory space is limited to the first 5000 registers of module memory addresses 0 through 4999 Therefore the practical limit for this parameter is 4999 minus the value entered for Read Register Count so that the Read Data Area does not try to extend above address 4999 Read Data and Write Data Areas must be configured to occupy separate address ranges in module memory and should not be allowed to overlap Read Register Count 0 to 5000 The Read Register Count parameter specifies the size of the Read Data area of module memory and the number of registers to transfer from this area to the processor up to a maximum of 5000 words Note Total Read Register Count and Write Register Count cannot exceed 5000 total registers Read Data and Write Data Areas must be configured to occupy separate address ranges in module memory and should not be allowed to overlap Write Register Start 0 to 4999 The Write Register Start parameter specifies the start of the Write Data area in module memory Data in this
146. red to perform a warm boot software reset operation This block is commonly sent to the module any time configuration data modifications are made in the controller tags data area This will cause the module to read the new configuration information and to restart Block Request from Processor to Module Offset Description Length 0 9998 1 1 to 247 Spare 247 Cold Boot Block 9999 This block is sent from the ControlLogix processor to the module output image when the module is required to perform the cold boot hardware reset operation This block is sent to the module when a hardware problem is detected by the ladder logic that requires a hardware reset Block Request from Processor to Module Word Offset Description Length 0 9999 1 1 to 247 Spare 247 Page 110 of 153 ProSoft Technology Inc October 26 2011 MVI56 MNETC ControlLogix Platform Reference Modbus TCP IP Multi Client Communication Module User Manual 5 3 Data Flow between MVI56 MNETC Module and Processor The following topics describe the flow of data between the two pieces of hardware processor and MVI56 MNETC module and other nodes on the Modbus TCP IP network The module contains up to 30 Clients which can generate either MBAP Modbus API for network communications or MNET requests dependent on the service port selected in the command 2 A g oe AN To Processor Output from Module Sea 5 a j Proce
147. rocessor BlockStats Write INT Total number of write blocks transferred from the processor to the module BlockStats Parse INT Total number of blocks successfully parsed that were received from the processor BlockStats Event INT Total number of Event Command blocks received from the processor BlockStats Cmd INT Total number of Command Control blocks received from the processor BlockStats Err INT Total number of block errors recognized by the module CmdBits x INT Displays enabled or disabled status of all 16 commands in the Client x Command List for each Client ClientStatsTrigger BOOL Initiates request for Client Status block from module when set to 1 ClientID INT Specifies Client 0 29 to request status data from ClientStatus x CmdReq INT Total number of command list requests sent from Client ClientStatus x CmdResp INT Total number of command list responses received by Client ClientStatus x CmdErr INT This value is incremented each time an error message is received from a remote unit or a local error is generated for a command ClientStatus x Requests INT Not used ClientStatus x Responses INT Not used ClientStatus x ErrSent INT Not used ClientStatus x ErrRec INT Not used ClientStatus x CfgErrWord INT Configuration Error Word This word contains a bitmap that indicates general module configuration errors ClientStatus x CurErr INT Most recent error code recorded for the Client ClientStatus x
148. rolLogix Platform Diagnostics and Troubleshooting Modbus TCP IP Multi Client Communication Module User Manual 4 3 1 Status Data Definition This section contains a description of the controller tags in the MNETC STATUS controller tag structure which contains module and Client status data The first ten controller tags contain status data routinely transferred from the module to the processor in the normal data transfer block sequence page 93 The remaining controller tags are used to request and receive Client status data via the Client Status block functionality page 104 Note In order to access up to date status data from these remaining controller tags you must ensure that a Client Status block was recently received from the module Client Status blocks are not routinely sent from the module they are returned on a once per request basis as a response to a Client Status block request from the processor ProSoft Technology Inc Page 81 of 153 October 26 2011 Diagnostics and Troubleshooting MVI56 MNETC ControlLogix Platform User Manual Modbus TCP IP Multi Client Communication Module Controller Tag Data Type Description PassCnt INT This value is incremented each time a complete program cycle occurs in the module ProductVersion INT Product version ProductCode INT 2 Product code BlockStats Read INT Total number of read blocks transferred from the module to the p
149. s Controller tag arrays Lower level controller tag structures The controller tags for the module are pre programmed into the Add On Instruction Import Rung ladder logic You can find them in the Controller Tags subfolder located in the Controller folder in the Controller Organizer pane of the main RSLogix 5000 window This controller tag structure is arranged as a tree structure Individual controller tags are found at the lowest level of the tree structure Each individual controller tag is defined to hold data of a specific type such as integer or floating point data Controller tag structures are declared with user defined data types which are collections of data types 3 1 1 MVI56 E MNETC Controller Tags The main controller tag structure MNETC is broken down into four lower level controller tag structures MNETC MNETC DATA MNETC CONTROL MNETC STATUS MNETC UTIL The four lower level controller tag structures contain other controller tags and controller tag structures Click the sign next to any controller tag structure to expand it and view the next level in the structure Page 56 of 153 ProSoft Technology Inc October 26 2011 MVI56 MNETC ControlLogix Platform Ladder Logic Modbus TCP IP Multi Client Communication Module User Manual For example if you expand the MNETC DATA controller tag structure you will see that it contains two controller tag arrays MNETC DATA ReadData and MNETC DATA
150. s for uppercase letter eye I lowercase letter el L and the number one 1 Likewise uppercase letter oh O and the number zero 0 are not interchangeable Although these characters look alike on the screen they perform different actions on the module and may not be used interchangeably ProSoft Technology Inc Page 73 of 153 October 26 2011 Diagnostics and Troubleshooting MVI56 MNETC ControlLogix Platform User Manual Modbus TCP IP Multi Client Communication Module 4 2 2 Main Menu When you first connect to the module from your computer your terminal screen will be blank To activate the main menu press the key on your computer s keyboard If the module is connected properly the following menu will appear MY I MNETC COMMUNICATION MODULE MENU Display Menu B Block Transfer Statistics C Module Configuration D Modbus Database View E Client Command List Errors I Client Command List R Transfer Configuration from PC to MYI Unit S Transfer Configuration from MYI Unit to PC U Reset diagnostic data Y Version Information W Warm Boot Module Communication Status Client 4 NIC Status 9 Client Configuration 7 Static ARP Table Network Menu Esc Exit Program Caution Some of the commands available to you from this menu are designed for advanced debugging and system testing only and can cause the module to stop communicating with the processor or with other devices resulting in potential data loss or o
151. s not required for networks that do not use a default gateway 2 Double click the ETHERNET CONFIGURATION icon This action opens the Edit dialog box Edit WATTCP my_ip 192 168 0 250 my_ip netmask 255 255 255 0 gateway 192 168 0 1 192 Comment Definition Default private class 3 address Reset Tag Reset All OK Cancel 3 Edit the values for my_ip netmask subnet mask and gateway default gateway 4 When you are finished editing click OK to save your changes and return to the ProSoft Configuration Builder window Page 52 of 153 ProSoft Technology Inc October 26 2011 MVI56 MNETC ControlLogix Platform Configuring the MVI56 MNETC Module Modbus TCP IP Multi Client Communication Module User Manual 2 5 Connecting your PC to the Module With the module securely mounted connect your PC to the Configuration Debug port using an RJ45 DB 9 Serial Adapter Cable and a Null Modem Cable 1 Attach both cables as shown 2 Insert the RJ45 cable connector into the Configuration Debug port of the module 3 Attach the other end to the serial port on your PC Allen Bradley Null Modem Cable to PC RJ45 to DB9 Pigtail Cable gt ProSoft Technology Inc Page 53 of 153 October 26 2011 Configuring the MVI56 MNETC Module MVI56 MNETC ControlLogix Platform User Manual Modbus TCP IP Multi Client C
152. sale ojo D RUN gt ok BAT J Controller My_Controller Controller Tags Controller Fault Handler Power Up Handler Gl Tasks MainTask MainProgram Program Tags EB Mainkoutine Unscheduled Programs Motion Groups Ungrouped Axes amp Add On Instructions J AOIS6MNETC Parameters and Local Tags Logic E Prescan i Data Types Gil User Defined E MNETCBLocKsTATS R MNETCCLIENTSTATS R MNETCCMDCONTROL MNETCCONTROL MNETCDATA A MNETCEVENTCMO A MNETCINITOUTDATA K MNETCIPADORESS R MNETCMODULEDEF MNETCSTATUS MNETCUTIL G Strings s E Add On Defined G Predefined E Module Defined Gi Trends Description This object is usedto store th Size 12 Bytes 7 Untitled ProSoft Co TE inbox Microsoft Out i305 w aal my L Af Hitet ici ae 4 of o gt ID lt gt f Favorites K Aaron K Alarms K i K Teoma AT J EECEA Discard Discard Create New mea This defines the whole module which includes all tags used in the program Fault Code value GSV Get System Value Class Name Module Instance Name MNETC Attribute Name FaultCode Dest MNETC UTIL FaultCode 0e Add On for MVISE MINETC and MVISGE MNETC modules AOISBMINETC Add On for MVI56 MNETC and MVI56 AOISEMNETC AOISBMNETC Connection_Input Loca Data Connection_Output Local t 0 Data MINETC MINETC This defines the whole module whic
153. ser Defined Gy Strings R Add On Defined Op Predefined E Module Defined Trends 5 I O Configuration Delete Rung Add Rung Edit Rung Edit Rung Comment Import Rung Export Rung Accept Pending Rung Edits Verify Rung GoTo Ctri G Add Ladder Element Alt Ins J MainRoutine Page 24 of 153 ProSoft Technology Inc October 26 2011 MVI56 MNETC ControlLogix Platform Configuring the MVI56 MNETC Module Modbus TCP IP Multi Client Communication Module User Manual 4 Navigate to the location on your PC where you saved the Add On Instruction for example My Documents or Desktop Select the MVI56MNETC_ADDON_RUNG_V1_5 L5xX file Import Rung Look in B Desktop p My Computer My Documents Quy Network Places Downloads MVI56 E MNETC_AddOn_Rung_v1_5 L5X My Documents File name MVI56 E MNETC_AddOn_Rung_v1_5 L5X we My Network Files of type RSLogix 5000 XML Files L5X X 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 AOISEMNETC Create New Local 1 1 4B 1756_MOD Use Existing Local 1 0 4B 1756_MOD Use Existing MNETCMODU Create New 5 If you are using the module in a different slot or remote rack select the correct connection input and output variables that define the path to the module If your module
154. 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 For information on troubleshooting commands see Client Command Errors page 84 ProSoft Technology Inc Page 113 of 153 October 26 2011 Reference MVI56 MNETC ControlLogix Platform User Manual Modbus TCP IP Multi Client Communication Module 5 4 Cable Connections The MVI56 MNETC module has the following functional communication connections installed One Ethernet port RJ45 connector One RS 232 Configuration Debug port RJ45 connector 5 4 1 Ethernet Connection The MVI56 MNETC module has an RJ45 port located on the front of the module labeled Ethernet for use with the TCP IP network The module is connected to the Ethernet network using an Ethernet cable between the module s Ethernet port and an Ethernet switch or hub Note Depending on hardware configuration you may see more than one RJ45 port on the module The Ethernet port is labeled Ethernet Warning The MVI56 MNETC module is NOT compatible with Power Over Ethernet IEEE802 3af IEEE802 3at networks Do NOT connect the module to Ethernet devices hubs switches or networks that supply AC or DC power over the Ethernet cable Failur
155. ssor DATABASE Module f Rane l _ gt SS To Module jJ Input from Network N ON Z 2 ProSoft Technology Inc Page 111 of 153 October 26 2011 Reference MVI56 MNETC ControlLogix Platform User Manual Modbus TCP IP Multi Client Communication Module 5 3 1 Client Driver In the Client driver the MVI56 MNETC module issues read or write commands to servers on the Modbus TCP IP network using up to 30 simulated Clients The commands originate either from the module s user configured Client x Command List for each Client or directly from the processor as Event Commands The commands from the Client x Command List are executed either via routine polling or as a result of special Command Control block requests from the processor Client status data is returned to the processor in special Client Status blocks The following flowchart describes the flow of data into and out of the module I Processor i MVI56 E MNETC Module a I ControlLogix l 1 Controller 1 Database Modbus Modbus TCP IP Tags l Addresses Addresses Ethernet 0 40001 Network l l 4 l u RN ee Client Register Data Driver Register 2 Data Storage Backplane Client Status Event Command l Command i Command Control i I Control I 1 The Client driver obtains configuration data when the module restarts This includes the timeout parameters and the Command List These values are used by the driver t
156. t 200 words Block ID contains the same data as block 1 both read data and status data 1 to 25 Read or Write blocks 1000 to 1024 Initialize Output Data blocks 2000 to 2029 Event Command blocks 3000 to 3029 Client Status blocks 5001 to 5016 Command Control blocks 9990 Set Module IP Address block 9991 Get Module IP Address block 9998 Warm boot block 9999 Cold boot block Page 92 of 153 ProSoft Technology Inc October 26 2011 MVI56 MNETC ControlLogix Platform Reference Modbus TCP IP Multi Client Communication Module User Manual These block identification codes can be broken down into two groups Normal data transfer blocks Read and Write blocks 1 to 25 Special function blocks Initialize Output Data blocks 1000 to 1024 Event Command blocks 2000 to 2029 Client Status blocks 3000 to 3029 Command Control blocks 5001 to 5016 Module IP Address blocks 9990 and 9991 Warm boot and Cold boot blocks 9998 and 9999 5 2 1 Normal Data Transfer Blocks Normal data transfer includes the paging of user data from the module s internal database registers 0 to 4999 as well as paging of status data These data are transferred through read input image and write output image blocks The following topics describe the function and structure of each block Read Block These blocks of data transfer information from the module to the ControlLogix processor The following table des
157. t byte includes the high order bits and the second the low order bits Because the server interface is normally serviced at the end of the controller s scan the data will reflect the register content at the end of the scan Each PC will limit the quantity of register contents provided each scan thus for large register quantities multiple PC scans will be required and the data provided will be form sequential scans In the example below the register 3009 contains the decimal value 0 Adr Func Byte Data Input Reg Hi Data Input Reg Lo Error Check Field Count 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 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
158. t this command at one second intervals to determine the frequency of program execution ProSoft Technology Inc Page 75 of 153 October 26 2011 Diagnostics and Troubleshooting MVI56 MNETC ControlLogix Platform User Manual Modbus TCP IP Multi Client Communication Module Warm Booting the Module Press W from the Main menu to warm boot restart the module This command will cause the program to exit and reload refreshing configuration parameters that must be set on program initialization Only use this command if you must force the module to reboot Viewing Client Status Press 0 zero to display the statistics of the Client Viewing NIC Status Press 4 to view NIC status Use this command to view the communication status for the Network Interface Card Viewing Client Configuration Press 5 to display the configuration information for the Client Viewing the Static ARP Table Press 7 to view the Static ARP Table Use this command to view the list of IP and MAC addresses that are configured not to receive ARP messages from the module STATIC ARP TABLE ae Count 4 105 102 0 15 00 0D 8D B0 0A 16 105 102 0 16 00 0D 8D B0 0A 16 105 162 0 17 00 00 8D B0 0A 16 105 102 0 18 00 00 8D B0 0A 16 Opening the Network Menu Press to open the Network menu The Network menu allows you to send receive and view the WATTCP CFG file that contains the IP gateway and other network specification information For more
159. teneeeseneeseas 121 5 5 4 Read Holding Registers Function Code 08 ccccceceeceseeeeeeeeeeeeeeeeneeeseeeeseas 122 5 5 5 Read Input Registers Function Code 04 ececeeeeeeeceneeeseteeseneeeeeeeeteneeeseeeeseas 123 5 5 6 Force Single Coil Function Code 05 c ceccccceseeeeeeeeeeeeeeeceaeeeeeeeseeeeeeeeeseeetas 124 5 5 7 Preset Single Register Function Code 06 ccc ccceceeeeeeeseeeeeeeeeeeeaeeteneeeseeeeseas 125 5 5 8 Diagnostics Function Code 08 ecceceeececeeeeeeeeeeeeaeeeeeaeeseaeeseeeeseaeeseeeeeeeaeesas 126 5 5 9 Force Multiple Coils Function Code 15 ccccccscceseceeeeeeeeseeeeseeeeeeneeeteneeeseeeeteas 128 5 5 10 Preset Multiple Registers Function Code 16 cccccsseeeseeeeeeeeeeeeeeteneeeseeeeteas 129 5 5 11 Modbus Exception Responses ccccceeeeseeeeeeeeeeeeeeeeeeeeeeeaeeeeeeaeeeesenaeeeesenaeees 130 5 6 Adding the Module to an Existing Project cececseeeeseeeeeeeeneeeeeeneeeeeeenaeeeeeeaas 132 5 7 Using the Sample Programista nisan ee ee reter aaen eae oaeiai 135 5 7 1 Opening the Sample Program in RSLOQIX ccecceeeeeeeeeeeeeeeeeseeeeeeeeeseneeeeeeeees 135 5 7 2 Choosing the Controller Type c cccceeeeeeeeeeeeeeeeneeeeeeeeseeeeseaeeseaeeeeseeeseeeeeneeess 138 5 7 3 Selecting the Slot Number for the MOdUIe c cceeceeeeeeeeeeeeeeeeeeeneeeteteeeeeneess 139 5 7 4 Downloading the Sample Program to the Processor 140 5 7 5 Adding th
160. that different manufacturers store and transmit multi byte data in different combinations This parameter is helpful when dealing with floating point or other multi byte values as there is no one standard method of storing these data types The parameter can be set to rearrange the byte order of data received or sent into an order more useful or convenient for other applications The following table defines the valid Swap Code values and the effect they have on the byte order of the data Swap Code Description NONE No change is made in the byte ordering 1234 1234 Swap Worps The words are swapped 1234 341 2 Swap Worps 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 2148 These swap operations affect 4 byte or 2 word groups of data Therefore data swapping using these Swap Codes should be done only when using an even number of words such as when 32 bit integer or floating point data is involved Node IP Address XXX XXX XXX XXX The IP address of the device being addressed by the command Service Port 502 or other port numbers supported on a server Use a value of 502 when addressing Modbus TCP IP servers that are compatible with the Schneider Electric MBAP specifications this will be most devices If a server implementation supports another service port enter the value here Page 48 of 153 ProSoft Technology Inc October 26
161. the block identification code 2000 to 2029 requested by the processor Word 2 of the block can be used by the ladder logic to determine if the command was successfully added to the command priority queue The command will fail if the queue for the Client is already full at the time when the Event Command block is received by the module Page 100 of 153 ProSoft Technology Inc October 26 2011 MVI56 MNETC ControlLogix Platform Reference Modbus TCP IP Multi Client Communication Module User Manual Controller Tags The elements of the MNETC CONTROL EventCmad x controller tag array contain all the values needed to build one Modbus TCP IP command have it sent to a specific Client on the module and control the processing of the returned response block Controller Tag Description IPO Enter the first octet of the IP address of the target Modbus server IP1 Enter the second octet of the IP address of the target Modbus server IP2 Enter the third octet of the IP address of the target Modbus server IP3 Enter the fourth octet of the IP address of the target Modbus server ServPort Enter 502 for a MBAP message or 2000 for a MNET message Node Enter the Modbus slave node address Enter 1 to 247 Enter 0 if not needed DBAddress Enter the module internal database address to associate with the command Count Enter the number of words or bits to be transferred by the Client Swap Enter the swa
162. the request If the server receives the request without a communication error but cannot handle it for example if the request is to read a non existent output or register the server will return an exception response informing the Client of the nature of the error The exception response message has two fields that differentiate it from a normal response Function Code Field In a normal response the server echoes the function code of the original request in the function code field of the response All function codes have a most significant bit MSB of 0 their values are all below 80 hexadecimal In an exception response the server sets the MSB of the function code to 1 This makes the function code value in an exception response exactly 80 hexadecimal higher than the value would be for a normal response With the function code s MSB set the Client s application program can recognize the exception response and 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 Addr
163. ther communication failures Use these commands only if you fully understand their potential effects or if you are specifically directed to do so by ProSoft Technology Technical Support Engineers There may be some special command keys that are not listed on the menu but that may activate additional diagnostic or debugging features If you need these functions you will be advised how to use them by Technical Support Please be careful when pressing keys so that you do not accidentally execute an unwanted command Viewing Block Transfer Statistics Press B from the Main menu to view the Block Transfer Statistics screen Use this command to display the configuration and statistics of the backplane data transfer operations between the module and the processor The information on this screen can help determine if there are communication problems between the processor and the module Tip To determine the number of blocks transferred each second mark the numbers displayed at a specific time Then some seconds later activate the command again Subtract the previous numbers from the current numbers and divide by the quantity of seconds passed between the two readings Page 74 of 153 ProSoft Technology Inc October 26 2011 MVI56 MNETC ControlLogix Platform Diagnostics and Troubleshooting Modbus TCP IP Multi Client Communication Module User Manual Viewing Module Configuration Press C to view the Module Configuration screen Use th
164. they are not displayed properly Viewing Data in ASCII Text Format Press A from the Database View menu to display the data on the current page in ASCII format This is useful for regions of the database that contain ASCII data Returning to the Main Menu Press M to return to the Main menu 4 2 4 Network Menu From the Main menu press to display the Network menu The Network menu allows you to send receive and view the WATTCP CFG file that contains the IP and module addresses and other network information Transferring WATTCP CFG to the Module Press R to transfer a new WATTCP CFG file from the PC to the module Use this command to change the network configuration for the module for example the module s IP address Press Y to confirm the file transfer and then follow the instructions on the terminal screen to complete the file transfer process Page 78 of 153 ProSoft Technology Inc October 26 2011 MVI56 MNETC ControlLogix Platform Diagnostics and Troubleshooting Modbus TCP IP Multi Client Communication Module User Manual Transferring WATTCP CFG to the PC Press S to transfer the WATTCP CFG file from the module to your PC Press Y to confirm the file transfer and then follow the instructions on the terminal screen to complete the file transfer process After the file has been successfully transferred you can open and edit the file to change the module s network configuration Viewing the
165. ts The following components are included with your MVI56 MNETC 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 MVI56 MNETC MVI56 MNETC Modbus TCP IP Multi Client Communication Module Module 1 Cable Cable 15 RS232 For RS232 between a Personal Computer Null Modem PC and the CFG port of the module 1 Cable Cable 14 RJ45 For connecting the module s port to Cable to DB9 Male 15 for RS 232 connections Adapter 1 inRAx Solutions CD Contains sample programs utilities and documentation for the MVI56 MNETC module If any of these components are missing please contact ProSoft Technology Support for replacement parts ProSoft Technology Inc Page 13 of 153 October 26 2011 Start Here MVI56 MNETC ControlLogix Platform User Manual Modbus TCP IP Multi Client Communication Module 1 3 Installing ProSoft Configuration Builder Software You must install the ProSoft Configuration Builder PCB software to configure the module You can always get the newest version of ProSoft Configuration Builder from the ProSoft Technology website To install ProSoft Configuration Builder from the ProSoft Technology website 1 Open your web browser and navigate to http www prosoft technology com pcb 2 Click the link at the Current Release Version section to
166. twork or operator control through the module s Configuration Debug port Status Data in Read Block The following table describes in more detail the status information found in the Read Block Word Offset Content Description 202 Program Scan Count This value is incremented each time a complete program cycle occurs in the module 203 Read Block Count This field contains the total number of read blocks transferred from the module to the processor 204 Write Block Count This field contains the total number of write blocks transferred from the processor to the module 205 Parse Block Count This field contains the total number of blocks successfully parsed that were received from the processor 206 Command Event Block This field contains the total number of command Count event blocks received from the processor 207 Command Block Count This field contains the total number of command blocks received from the processor 208 Error Block Count This field contains the total number of block errors recognized by the module 209 Client 0 command Each bit in this word enables disable the commands execution word for Client 0 If the bit is set the command will execute If the bit is clear the command will be disabled This data is set in the output image WriteBlock from the ladder logic 210 to 238 Client 1 to Client 29 These 29 words are used for each of the other 29 command execution words Clients in the m
167. uested in the Command Control block 1 to 16 This value is used by the ladder logic to generate the Command Control Block ID The rightmost digits of the Command Control Block ID are the number of commands requested by the block CmdControl ClientID Enter the Client to issue the commands to 0 to 29 CmdControl CMDaty Not used CmdControl CmdIndex Enter the ROW NUMBER of the command in the MNET Client x Command List in Prosoft Configuration Builder minus 1 This is a 16 element array Each element holds one Command Index CmdControl WriteCmdBits Enter a 1 enable or a 0 disable to select which commands on the configuration s Client x Command List will be executed during routine polling There is one 16 bit word for each of the 30 Clients Each of the 16 bits corresponds to one of the 16 commands available to each Client The state of these WriteCmaBits overrides whatever value may be assigned to the Enable parameter in the configuration Note This parameter only affects routine polling It has no effect on Command Control blocks CmdControlPending Not used CmdControlTrigger Set this tag to 1 to trigger the execution of a Command Control block after all the other parameters have been entered ProSoft Technology Inc Page 107 of 153 October 26 2011 Reference MVI56 MNETC ControlLogix Platform User Manual Modbus TCP IP Multi Client Communication Module Reset Module Status Block 9971 MNETC This bloc
168. unction code in a normal response Some of the diagnostics cause data to be returned from the remote device in the data field of a normal response In general issuing a diagnostic function to a remote device does not affect the running of the user program in the remote device Device memory bit and register data addresses are not accessed by the diagnostics However certain functions can optionally reset error counters in some remote devices A server device can however be forced into Listen Only Mode in which it will monitor the messages on the communications system but not respond to them This can affect the outcome of your application program if it depends upon any further exchange of data with the remote device Generally the mode is forced to remove a malfunctioning remote device from the communications system Sub function Codes Supported Only Sub function 00 is supported by the MVI56 MNETC 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 Page 126 of 153 ProSoft Technology Inc October 26 2011 MVI56 MNETC ControlLogix Platform Modbus TCP IP Multi Client Communication Module Reference User Manual Example and State Diagram Here is an example of a request to remote device to Return Qu
169. vantage of defining a UDT is that it may be re used in other controller tag structures that use the same data types The Add On Instruction Import Rung ladder logic for the module has pre defined UDTs You can find them in the User Defined subfolder located in the Data Types folder in the Controller Organizer pane of the main RSLogix window Like the controller tags the UDTs are organized in a multiple level tree structure 3 2 1 MVI56 E MNETC User Defined Data Types Eleven different UDTs are defined for the MVI56 E MNETC Add On Instruction The main UDT MNETCMODULEDEF contains all the data types for the module and was used to create the main controller tag structure MNETC There are four UDTs one level below MNETCMODULEDEF These lower level UDTs were used to create the MNETC DATA MNETC CONTROL MNETC STATUS and MNETC UTIL controller tag structures Name MNETCMODULEDEF This defines the whole module which includes all tags used in the program Description Members Data Type Size 4012 byte s Name Data Type Style Description DATA MNETCDATA Data read from module CONTROL MNETCCONTROL Client Server Status and blocks status STATUS MNETCSTATUS MNETC Module control z UTIL MNETCUTIL Block statistics 1t mo Click the signs to expand the UDT structures and view lower level UDTs Page 58 of 153 ProSoft Technology Inc October 26 2011 MVI56 MNETC ControlLogix Platform Ladder Logic Modbus
170. vice port on the server to connect If the parameter is set to 502 a standard MBAP Modbus API for network communications message will be generated All other service port values will generate a Modbus command message encapsulated in a TCP IP packet The Slave Address is the Modbus node address for the message The Internal DB Address parameter specifies the module s database location to associate with the command The Point Count parameter defines the number of points or registers for the command The Swap Code is used with Modbus functions 3 and 4 requests to change the word or byte order The Modbus Function Code has one of 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 server device to be associated with the command The module then places the command in the command priority queue if the queue is not already full maximum capacity is 16 commands and returns a response block to tell the ladder logic whether or not the command has been successfully added to the queue Block Response from Module to Processor Word Offset Description 0 Reserved 1 This word contains the next read request block identification code 2 This word contains the result of the event request If a value of one is present the command was issued If a value of zero is present no room was found in the command priority queue 3 to 248 Spare 249 This word contains

MVI56-MNETC User Manual

Contents

Download Pdf Manuals

Related Search

Related Contents