Home

MVI56-MBP User Manual

1. DB Address Modbus Address Parameter Description 4680 44681 Device Def ID 23 Start register of device definition block for device index 23 4690 44691 Device Def ID 24 Start register of device definition block for device index 24 4700 44701 Device Def ID 25 Start register of device definition block for device index 25 4710 44711 Device Def ID 26 Start register of device definition block for device index 26 4720 44721 Device Def ID 27 Start register of device definition block for device index 27 4730 44731 Device Def ID 28 Start register of device definition block for device index 28 4740 44741 Device Def ID 29 Start register of device definition block for device index 29 4750 44751 Device Def ID 30 Start register of device definition block for device index 30 4760 44761 Device Def ID 31 Start register of device definition block for device index 31 4770 44771 Device Def ID 32 Start register of device definition block for device index 32 4780 44781 Device Def ID 33 Start register of device definition block for device index 33 4790 44791 Device Def ID 34 Start register of device definition block for device index 34 4800 44801 Device Def ID 35 Start register of device definition block for device index 35 4810 44811 Device Def ID 36 Start register of device definition block for device index 36 4820 44821 Device Def ID 37 Start register of devic
2. ProSoft Technology Inc Page 39 of 96 July 23 2008 MVI56 MBP ControlLogix Platform Diagnostics and Troubleshooting Modbus Plus Communication Module 0x0080 Interface Diagnostics Press 8 to display any interface diagnostic messages processed by the module 0x0100 Software Reset Press 9 to display any software reset commands sent from the module to the Modbus Plus Chipset 0x0200 Put Global Data Press A to display any global output messages processed by the module The following illustration shows an example of the output nor Tut Global Data Response 167 HDT ut Global Data 24 28 DZ 41 J alt 1 4 8 5 CE am 1 E ES Su du da VEL RE q D u ua B da H is 2 t 4 H HU H H H E u MBP Put Cyobat Data Hespanae db AEP Fut Global Data 44 ZH DJ 21 2 3Y 3 R59 d KER 1 ER 2 am a a a a fa aon Busen 0x0400 Get Global Data Press B to display any global input messages processed by the module The following illustration shows an example of the output Global Data Get Global Data Hcapons3c A PATO 2 74 R ER ea WPA FE 94 A FA 24 AR AER mA Ba Pa Pn hio o P Ba 29 O F B3 32 8 FO HZ 39 4 FB H2 39 D FA B2 39 8 FB B2 39 O MBP Gat Global Data 22 MBP Get Global Data Response amp p 74 B TB EE 74 B TB 24 AD 8 I8 m P4 a Pa Da i Mx 2 39 O FG B2 39 6 P B2 39 FB H2 39 D Fa E 39 d FE B2 39 H rH Returning to the Main Menu Press M to return to the Main Menu 5 1 7 Device
3. 4370 44371 h onfiguratior infiguration onfiguratioi Data 7089 47090 Step Description 1 A Host device such as a Modicon PLC or an HMI application issues a read or write command to the module s node address The Modbus Plus chipset qualifies the message before accepting it into the module 2 After the module accepts the command the data is immediately transferred to or from the internal database in the module If the command is a Read command the data is read out of the database and appended to the response and if the command is a Write command the data is written directly into the database 3 After the data processing has been completed in Step 2 the response is issued to the originating node 4 Several counters are available in the Status Block that permit the ladder logic program to determine the level of activity of the Slave Driver ProSoft Technology Inc Page 61 of 96 July 23 2008 MVI56 MBP ControlLogix Platform Reference Modbus Plus Communication Module There are no special module configuration requirements to place the module in the Slave Operating Mode When the module is operating in the slave mode external devices act as masters by polling for data from the module or writing to the module As such the module needs to only respond to read and write commands transferring data to from the module s database depending on the command type In order for a Modicon PLC to read dat
4. AL I H H A A n a B a n a H H A A 4 a a a H H A A n a 4 EH n a The Status data area displays the current status of each node on the network The Counters section displays the number of Global Input data messages received from the device Opening the Device Definition List Menu Press L to open the Device Definition List This list consists of multiple pages of device definition data Press to view a list of commands available on this menu ProSoft Technology Inc Page 35 of 96 July 23 2008 MVI56 MBP ControlLogix Platform Diagnostics and Troubleshooting Modbus Plus Communication Module Viewing VO File Data Press O to view the module s global input and output data iUo 1HHb 18H 1H 10M n Kal 1 42 4275 427n 4277 427R 4279 4388 4281 4232 42 4284 4285 1285 4287 4288 4297 4298 4277 IN FILE DATA dYa 1bb52 YEYE 51471H FS 15652 299243 b134H 27734 b51713H 2 45 T 1426 ul al 1828 a a L 18281 37666 37567 OUT FILE PATA 1334 789 12345 5 456 567 oo 89H 78 B B B H k The In File Address Map values represent the data set for selecting the registers in the module s database to transfer to the In File Data area The In File Data section displays the current values transferred from the module to the ControlLogix processor The Out File Data section contains the values used for Global Output Data to be transferred from the module to the Modbus Plus network Viewing Version Information Press
5. Viewing Data in Decimal Format Press D to display the data on the current page in decimal format Viewing Data in Hexadecimal Format Press H to display the data on the current page in hexadecimal format Viewing Data in Floating Point Format Press F from the Database View menu Use this command 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 they are not displayed properly Viewing Data in ASCII Text Format Press A to display the data on the current page in ASCII format This is useful for regions of the database that contain ASCII data Page 42 of 96 ProSoft Technology Inc July 23 2008 Diagnostics and Troubleshooting MVI56 MBP ControlLogix Platform Modbus Plus Communication Module Returning to the Main Menu Press M to return to the Main Menu 5 1 9 Master Command Error List Menu Use this menu to view the command error list for the module Press to view a list of commands available on this menu Display Menu Show Again 7 Prewious Page 7 Next Page 7 Main Menu Redisplaying the Current Page Press S to display the current page of data Viewing the Previous 20 Commands Press to display data for the previous 20 commands Viewing the Previous Page of Commands Press P to display the prev
6. ControlLogix processor The structure of the input image used to transfer this data is shown in the following table Offset Description Length 0 Read Block ID 1 1 Write Block ID 1 2 to 201 Read Data 200 202 to 217 Status Data 16 218 to 249 Global Input Data 32 Page 52 of 96 ProSoft Technology Inc July 23 2008 Reference MVI56 MBP ControlLogix Platform Modbus Plus Communication Module The Read Block ID is an index value used to determine the location of where the data will be placed in the ControlLogix processor controller tag array of module read data Each transfer can move up to 200 words block offsets 2 to 201 of data In addition to moving user data the block also contains a short list of status data for the module and the global input data Input File Data This last set of data is transferred with each new block of data and is used for high speed data movement The Write Block ID associated with the block is used to request data from the ControlLogix processor Under normal program operation the module sequentially sends read blocks and requests write blocks For example if three read and two write blocks are used with the application the sequence will be as follows R1W1 R2W2 R3W1 R1W2 R2W1 R3W2 R1W1 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 Plus network or operator control t
7. F Shock 30g Operational 50g non operational Vibration 5 g from 10 to 150 Hz Relative Humidity 596 to 9596 non condensing All phase conductor sizes must be at least 1 3 mm squared and all earth ground conductors must be at least 4mm squared Markings I 3 G OC lt Ta lt 60C EEx nA IIC T4 DEMKO 07ATEX0710717X Battery Life Advisory All modules in the MVI series use a rechargeable Lithium Vanadium Pentoxide battery to backup the 512K SRAM memory 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 it becomes fully charged After it is fully charged the battery provides backup power for the CMOS setup and configuration data the real time clock and the 512K SRAM memory for approximately 21 days Before you remove a module from its power source ensure that the battery within the module is fully charged A fully charged battery will hold the BIOS settings after being removed from its power source for a limited number of days When the battery is fully discharged the module will revert to the default BIOS settings Note The battery is not user replaceable ProSoft amp 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 and are available at
8. Install the Module in the Rack If you have not already installed and configured your ControlLogix processor and power supply please do so before installing the MVI56 MBP module Refer to your Rockwell Automation product documentation for installation instructions Warning You must follow all safety instructions when installing this or any other electronic devices Failure to follow safety procedures could result in damage to hardware or data or even serious injury or death to personnel Refer to the documentation for each device you plan to connect to verify that suitable safety procedures are in place before installing or servicing the device After you have checked the placement of the jumpers insert MVI56 MBP 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 ProSoft Technology Inc Page 11 of 96 July 23 2008 MVI56 MBP ControlLogix Platform Start Here Modbus Plus Communication Module 2 Align the mo
9. ProSoft and all related services provided by ProSoft including maintenance repair warranty exchange and service programs collectively Services By purchasing or using the Product or Services the individual or entity purchasing or using the Product or Services Customer agrees to all of the terms and provisions collectively the Terms of this Limited Warranty All sales of software or other intellectual property are in addition subject to any license agreement accompanying such software or other intellectual property 7 3 1 What Is Covered By This Warranty a Warranty On New Products ProSoft warrants to the original purchaser that the Product that is the subject of the sale will 1 conform to and perform in accordance with published specifications prepared approved and issued by ProSoft and 2 will be free from defects in material or workmanship provided these warranties only cover Product that is sold as new This Warranty expires three years from the date of shipment the Warranty Period If the Customer discovers within the Warranty Period a failure of the Product to conform to specifications or a defect in material or workmanship of the Product the Customer must promptly notify ProSoft by fax email or telephone In no event may that notification be received by ProSoft later than 39 months Within a reasonable time after notification ProSoft will correct any failure of the Product to conform to specifications or a
10. infringe existing or subsequently issued patents trademarks or copyrights ProSoft Technology Inc Page 91 of 96 July 23 2008 MVI56 MBP ControlLogix Platform Support Service amp Warranty Modbus Plus Communication Module a Any documentation included with Product purchased from ProSoft is protected by copyright and may not be duplicated or reproduced in any form without prior written consent from ProSoft b ProSoft s technical specifications and documentation that are included with the Product are subject to editing and modification without notice c Transfer of title shall not operate to convey to Customer any right to make or have made any Product supplied by ProSoft d Customer is granted no right or license to use any software or other intellectual property in any manner or for any purpose not expressly permitted by any license agreement accompanying such software or other intellectual property e Customer agrees that it shall not and shall not authorize others to copy software provided by ProSoft except as expressly permitted in any license agreement accompanying such software transfer software to a third party separately from the Product modify alter translate decode decompile disassemble reverse engineer or otherwise attempt to derive the source code of the software or create derivative works based on the software export the software or underlying technology in contravention of applicable US and internati
11. 23 2008 Reference MVI56 MBP ControlLogix Platform Modbus Plus Communication Module To enable the Global Output Mode set the Global Output Length parameter to a value between 1 and 32 To disable this feature set the parameter to a value of zero Status information about the global output data is found in the status block transferred from the module to the ControlLogix processor Slave Driver Mode The Slave Driver Mode allows the MVI56 MBP module to respond to data read and write commands issued by other nodes on the Modbus Plus network Two aspects of the module s operation must be kept in mind when considering using this mode 1 The module supports MSTR Type 1 and Type 2 commands issued from a Modicon processor or another device acting in a similar capacity 2 The module is a Modbus Plus Host type of node therefore any device wishing to read or write data from the module must be able to define a Data Slave Input Path in the Routing Path The module supports all 8 Data Slave Input paths but a Data Slave Path of 0 zero will cause the command to be rejected The following flow chart and associated table describe the flow of data into and out of the module Processor Memory Backplane Interface MBP Module ControlLogix Controller Tags Database Modbus Addresses i LI i i I Register i i i 1 i 1 I Status from Module 1 4369 44370 U
12. 5 Cable Assembly lt 9 E3 J1 J2 E og o RS 232 RS 485 RS 422 J1 Vv Xo Vv J2 EN DCD 4 i SD em Y S i DTR Te e GND GND GND o e ee He DD CTS TXRXD TXD by iS Jne w up Wiring Diagram 6 6 Database Definition This section contains a listing of the internal database of the MVI56 MBP module This information can be used to interface other devices to the data contained in the module ProSoft Technology Inc Page 71 of 96 July 23 2008 MVI56 MBP ControlLogix Platform Modbus Plus Communication Module 6 6 1 Module Memory Map Reference Overview Access Module Address Range Modbus Address Range Description Block Low High Low High Size R W 0 3999 40001 44000 Data Registers 4000 R 4000 4069 44001 44070 Global In Update Status 70 R 4070 4269 44071 44270 Master Command Status 200 R 4270 4299 44271 44300 Misc Module Status 30 R 4300 4369 44301 44370 Global In Update Counters 70 R W 4370 4409 44371 44410 Module Configuration Block 40 R W 4410 4449 44411 44450 Global In File Map 40 R W 4450 5089 44451 45090 Device Definition 640 R W 5090 7089 45091 47090 Master Command List 2000 O File 7090 7129 47091 47130 Global Out Image 40 File 7130 7169 47131 47170 Global In Image 40 R 7170 7221 47171 47222 Command Event Data 52 The Data Registers area holds data collected from other nodes on the network master read commands or global input data or data received from th
13. Each bit in the data area corresponds to a command in the master command list When the bit is set high the command will be issued When the bit is clear the command will not execute Event command control bits apply only to commands that have a value of two for their Enable parameter in the master command list Page 72 of 96 ProSoft Technology Inc July 23 2008 Reference 6 6 2 Status Data Definition MVI56 MBP ControlLogix Platform Modbus Plus Communication Module This section contains a description of the members present in the MBPStat object This data is transferred from the module to the processor approximately every second Array assignments for InUpdate member of MBPStat object Global In Update Status Element DB Address Description 0 4000 Global In Update Stat Device 1 1 4001 Global In Update Stat Device 2 2 4002 Global In Update Stat Device 3 3 4003 Global In Update Stat Device 4 4 4004 Global In Update Stat Device 5 5 4005 Global In Update Stat Device 6 6 4006 Global In Update Stat Device 7 7 4007 Global In Update Stat Device 8 8 4008 Global In Update Stat Device 9 9 4009 Global In Update Stat Device 10 10 4010 Global In Update Stat Device 11 60 4060 Global In Update Stat Device 61 61 4061 Global In Update Stat Device 62 62 4062 Global In Update Stat Device 63 63 4063 Global In Update Stat Device 64 64 40
14. Event Done Word 11 Event done bits for commands 176 to 191 7195 47196 Event Done Word 12 Event done bits for commands 192 to 199 7196 47197 Event Err Word 0 Event error bits for commands 0 to 15 7197 47198 Event Err Word 1 Event error bits for commands 16 to 31 ProSoft Technology Inc July 23 2008 Page 85 of 96 MVI56 MBP ControlLogix Platform Modbus Plus Communication Module Reference DB Address Modbus Address Parameter Description 7198 47199 Event Err Word 2 Event error bits for commands 32 to 47 7199 47200 Event Err Word 3 Event error bits for commands 48 to 63 7200 47201 Event Err Word 4 Event error bits for commands 64 to 79 7201 47202 Event Err Word 5 Event error bits for commands 80 to 95 7202 47203 Event Err Word 6 Event error bits for commands 96 to 111 7203 47204 Event Err Word 7 Event error bits for commands 112 to 127 7204 47205 Event Err Word 8 Event error bits for commands 128 to 143 7205 47206 Event Err Word 9 Event error bits for commands 144 to 159 7206 47207 Event Err Word 10 Event error bits for commands 160 to 175 7207 47208 Event Err Word 11 Event error bits for commands 176 to 191 7208 47209 Event Err Word 12 Event error bits for commands 192 to 199 7209 47210 Event One Shot 0 Event one shot bits for commands 0 to 15 7210 47211 Event One Shot 1 Event one shot bits for commands 16 to 31 7211 47212 Event One Shot
15. Network details If the issue is hardware related we will also need information regarding 1 Module configuration and contents of file o Module Operation o Configuration Debug status information o LED patterns 2 Information about the processor and user data files as viewed through and LED patterns on the processor 3 Details about the serial devices interfaced if any 7T 1 How to Contact Us Technical Support Internet Web Site http www prosoft technology com support http www prosoft technology com support E mail address support prosoft technology com mailto support prosoft technology com Asia Pacific 603 7724 2080 support asia prosoft technology com mailto support asia prosoft technology com Languages spoken include Chinese English Europe location in Toulouse France 33 0 5 34 36 87 20 support EMEA prosoft technology com mailto support emea prosoft technology com Languages spoken include French English ProSoft Technology Inc Page 87 of 96 July 23 2008 MVI56 MBP ControlLogix Platform Support Service amp Warranty Modbus Plus Communication Module 7 2 North America Latin America excluding Brasil location in California 1 661 716 5100 support prosoft technology com mailto support prosoft technology com Languages spoken include English Spanish For technical support calls within the United States an after hours answering system allows pager access to one of
16. These bits can be controlled by ladder logic to cause the module to issue a master port command on the Modbus Plus network These bits are located in the EventCtrl member of the MBPlusModuleDef data type and should be displayed as shown below in the Controller Tags Edit Tags dialog box EventCti INTR Binary JEvent Command Control Flags commands per word Event command control bits apply only to commands that have a value of two for their Enable parameter in the master command list ProSoft Technology Inc Page 27 of 96 July 23 2008 MVI56 MBP ControlLogix Platform Installing and Configuring the Module Modbus Plus Communication Module Page 28 of 96 ProSoft Technology Inc July 23 2008 Ladder Logic MVI56 MBP ControlLogix Platform Modbus Plus Communication Module 4 Ladder Logic Ladder logic is required for application of the MVI56 MBP module Tasks that must be handled by the ladder logic are module data transfer special block handling and status data receipt Additionally a power up handler may be needed to handle the initialization of the module s data and to clear any processor fault conditions The sample ladder logic on the ProSoft Solutions CD ROM is extensively commented to provide information on the purpose and function of each rung For most applications the sample ladder will work without modification ProSoft Technology Inc Page 29 of 96 July 23 2008 MVI56 MBP ControlLogix Platform Lad
17. Transfer successful 1 Error transferring module configuration data block 9000 2 Error transferring device definition data blocks 9100 to 9103 3 Error transferring master command list data blocks 6000 to 6007 After successful data transfer the module will perform a warm boot operation to read in the new data Viewing Communication Status Press 1 to view the communication status and statistics of the Modbus Plus Network for the module s node address This command is useful for troubleshooting purposes Exiting the 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 other failures Only use these commands if you are specifically directed to do so by ProSoft Technology Technical Support staff Some of these command keys are not listed on the menu but are active nevertheless Please be careful when pressing keys so that you do not accidentally execute an unwanted command ProSoft Technology Inc Page 37 of 96 July 23 2008 MVI56 MBP ControlLogix Platform Diagnostics and Troubleshooting Modbus Plus Communication Module 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 ROM to configure the module 5 1 6 Data Analyzer Use this
18. amp Slave Drivers Call Serial Port Driver Rx and Tx buffer routines are interrupt driven Call to serial port routines check to see if there is any data in the buffer and depending on the value will either service the buffer or wait for more characters Call Network Master amp Slave Drivers Generate messages and respond to messages received Processor Not in Run Whenever the module detects that the processor has gone out of the Run mode that is Fault or PGM the Modbus Plus port can be shut down as prescribed in the user configuration When the processor is returned to a running state the module will resume communications on the network Backplane Data Transfer The MVI56 MBP 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 frequency of update of the images is determined by the scheduled scan rate defined by the user for the module and the communication load on the module Typical updates are in the range of 2 5 to 10 milliseconds This bi directional transference of data is accomplished by the module filling in data in the module s input image to send to the processor Data in the input image is placed in the Controller Tags in the processor by the ladder logic The input image for the module is set to 250 words This large data area permits fast throughput of data
19. 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 Page 92 of 96 ProSoft Technology Inc July 23 2008 Support Service amp Warranty MVI56 MBP ControlLogix Platform Modbus Plus Communication Module 7 3 7 Time Limit for Bringing Suit Any action for breach of warranty must be commenced within 39 months following shipment of the Product 7 3 8 No Other Warranties Unless modified in writing and signed by both parties this Warranty is understood to be the complete and exclusive agreement between the parties suspending all oral or written prior agreements and all other communications between the parties relating to the subject 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 7 3 9 Allocation of Risks This Warranty allocates the risk of product failure between ProSoft and the Customer This allocation is recognized by both parties and is reflected in the price of the goods The Customer acknowledges that it has read this Warranty understan
20. are connecting from a machine running DOS you must obtain and install a compatible communication program The following table lists communication programs that have been tested by ProSoft Technology DOS ProComm as well as several other terminal emulation programs Windows 3 1 Terminal Windows 95 98 HyperTerminal Windows NT 2000 XP HyperTerminal 5 1 4 Using the Configuration Debug Port To connect to the module s Configuration Debug port 1 Connect your computer to the module s port using a null modem cable 2 Startthe communication program on your computer and configure the communication parameters with the following settings Baud Rate 57 600 Parity None Data Bits 8 Stop Bits 1 Software Handshaking None 3 Open the connection When you are connected press the key on your keyboard If the system is set up properly you will see a menu with the module name followed by a list of letters and the commands associated with them If there is no response from the module follow these steps 1 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 Page 32 of 96 ProSoft Technology Inc July 23 2008 Diagnostics and Troubleshooting MVI56 MBP ControlLogix Platform Modbus Plus Communication Module 2 Verify that RSLinx is not controlling the COM port Refer to Disabling the RSLinx Driver for the Com Port o
21. be made at any time These changes will be made periodically to correct technical inaccuracies or typographical errors Warnings UL Warnings A Warning Explosion Hazard Substitution of components may impair suitability for Class I Division 2 B Warning Explosion Hazard When in Hazardous Locations turn off power before replacing or rewiring modules Warning Explosion Hazard Do not disconnect equipment unless power has been switched off or the area is known to be nonhazardous C Suitable for use in Class I 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 IP54 enclosure The devices shall provide external means to prevent the rated voltage being exceeded by transient disturbances of more than 4096 This device must be used only with ATEX certified backplanes D DO NOT OPEN WHEN ENERGIZED Electrical Ratings Backplane Current Load 800 mA 5 V DC 3mA 24V DC Operating Temperature 0 to 60 C 32 to 140 F Storage Temperature 40 to 85 C 40 to 185
22. ea ee dee ned gen ehe ends 47 6 2 Functional OVerview 4 sesion re DD e HERD PE 49 6 3 RS 232 Configuration Debug POE ao aa Ea AEA E EE EATE EER 68 6 4 Modbu us Plus GonnectlOls iore os e dtt queer Aa e eee A e a ed 70 6 5 DB9 to RJ45 Adaptor Cable 14 ttt een tet sarai aii tet eed 71 6 6 Database Definition te core t c e EP to na teet Pie reed Feet eee ete 71 7 SUPPORT SERVICE amp WARRANTY ere re Eee nnn nn anna sinn nnn tn insita sas a ses n nnn nn nis 87 7 1 How to Contact Us Technical Support ssssssssssssssssseeeeen enne 87 7 2 Return Material Authorization RMA Policies and Conditions seesssssss 88 7 3 LIMITED WARRANTY caeiie eana gta e Pla eret be nud c eae 90 IND EX EE T 95 ProSoft Technology Inc Page 5 of 96 July 23 2008 Contents MVI56 MBP ControlLogix Platform Modbus Plus Communication Module Page 6 of 96 ProSoft Technology Inc July 23 2008 Guide to the MVI56 MBP User Manual MVI56 MBP ControlLogix Platform Modbus Plus Communication Module Guide to the MVI56 MBP User Manual Function Section to Read Details Introduction Start Here page 9 This Section introduces the customer to the Must Do module Included are package contents system requirements hardware installation and basic configuration Verify Communication Diagnostic and Troubleshooting Verifying Communication page 44 Diagno
23. installation or other failure of Customer to adhere to ProSoft s specifications or instructions iii unauthorized repair or maintenance iv attachments equipment options parts software or user created programming including but not limited to programs developed with any IEC 61131 3 C or any variant of C programming languages not furnished by ProSoft v use of the Product for purposes other than those for which it was designed vi any other abuse misapplication neglect or misuse by the Customer vii accident improper testing or causes external to the Product such as but not limited to exposure to extremes of temperature or humidity power failure or power surges or viii disasters such as fire flood earthquake wind and lightning c The information in this Agreement is subject to change without notice ProSoft shall not be liable for technical or editorial errors or omissions made herein nor for incidental or 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 7 3 3 Disclaimer Regarding High Risk Activities Product manufactured or supplied by ProSoft is not fault tolerant and is not designed manufactured or intended for use in hazardous environments requiri
24. menu to display Modbus Plus messages generated and received by the module This tool is extremely useful in determining the operation of the module and nodes on the network Press to view the list of commands available on this menu In the following illustration master command status errors can be resolved A1 Rer dirg Requests oa Put Haster Comnand tn Gutput Path cixenib Get Slave Gonmand Iron Input Poth 4 OvO008 gt Put Slave Response to Input Pat S CHxHBMLED Got Master Hespones Erom Uutgut Path amp COxBG 203 lwe Transact i ic On onan eee Wine statue eFace Dia COn ag i t Reget R CasBz a gt Put Global Dato d d Get Global Data H Main Menu Currant Debug Level B BH Use the commands on this menu to choose the type of data to view You can view more than one type of data at the same time For example to view the master command processing of messages from the MVI56 MBP module to other nodes on the network press 2 and then press 5 All master Put and Get messages handled by the module will be displayed on the screen The Current Debug Level parameter displayed at the bottom of the display shows the current debug level being monitored by the analyzer A value of 0000 indicates that the analyzer is not monitoring any messages 0x0000 Turn Debug off Press 0 zero to turn the analyzer off This is useful to freeze the analyzer screen with the last values displayed If you are using a terminal emulat
25. no charge from our web site http www prosoft technology com Printed documentation is available for purchase Contact ProSoft Technology for pricing and availability Asia Pacific 603 7724 2080 Europe Middle East Africa 33 5 34 36 87 20 Latin America 1 281 298 9109 North America 1 661 716 5100 Your Feedback Please We always want you to feel that you made the right decision to use our products If you have suggestions comments compliments or complaints about the product documentation or support please write or call us ProSoft Technology 1675 Chester Avenue Fourth Floor Bakersfield CA 93301 1 661 716 5100 1 661 716 5101 Fax http www prosoft technology com Copyright ProSoft Technology Inc 2000 2008 All Rights Reserved MVI56 MBP User Manual July 23 2008 PSFT MBP MVI56 UM 08 07 23 ProSoft Technology ProLinx inRAx ProTalk and RadioLinx are Registered Trademarks of ProSoft Technology Inc Contents MVI56 MBP ControlLogix Platform Modbus Plus Communication Module Contents PLEASE READ THIS NOTIGE 21 eeicc codice ci ieu ze coed ueste zac oe 2ioc ca oco odas a D aoaaa iaiu Sioni diaas 2 WarnhligS een Ah este Pateat 2 Battery Life AdVISOLy eso abies meu pam aaa UM 3 ProSoft Product Documentation ssssesssssseenene eene nennen nennen nnne 3 Your Feedback Please wei tieni eerte e e Lap ee be ye cits ortae dee acier d teen det ERE 4 1 GU
26. not used by the MVI56 MBP module as the Timing In File data is updated with each new input image sent to the processor 4376 44377 Global In Update This value defines the timeout period 0 to 65535 milliseconds Timeout for receiving Global Input Data from other nodes on the network After the timeout period has been exceeded the Timeout Error will be returned in the Global In Update Status data set A value of 0 will result in the default value of 1000 milliseconds 1 second Page 78 of 96 ProSoft Technology Inc July 23 2008 Reference MVI56 MBP ControlLogix Platform Modbus Plus Communication Module DB Address Modbus Address Parameter Description 4377 44378 Spare Not used 4378 44379 Spare Not used 4379 44380 Spare Not used 4380 44381 Number of Nodes This value specifies the number of devices to consider in the Defined in the Device Definition Table Valid range for this parameter is 0 to Device Definition 64 inclusive These node definitions are used by several File modes of operation of the module 4381 44382 Number of Master This parameter specifies the number of commands to be Commands processed in the Master Command List The module will only process this many commands starting with the first one in the list If the value is set to zero the Master Command Mode will be disabled Valid values for this parameter are 0 to 200 4382 44383 Number of Master This value define
27. our qualified technical and or application support engineers at any time to answer your questions Brasil location in Sao Paulo 55 11 5084 5178 eduardo prosoft technology com mailto eduardo prosoft technology com Languages spoken include Portuguese English Return Material Authorization RMA Policies and Conditions The following RMA Policies and Conditions collectively RMA Policies apply to any returned Product These RMA Policies are subject to change by ProSoft without notice For warranty information see Limited Warranty In the event of any inconsistency between the RMA Policies and the Warranty the Warranty shall govern 7 2 1 All Product Returns a In order to return a Product for repair exchange or otherwise the Customer must obtain a Returned Material Authorization RMA number from ProSoft and comply with ProSoft shipping instructions b In the event that the Customer experiences a problem with the Product for any reason Customer should contact ProSoft Technical Support at one of the telephone numbers listed above page 87 A Technical Support Engineer will request that you perform several tests in an attempt to isolate the problem If after completing these tests the Product is found to be the source of the problem we will issue an RMA C All returned Products must be shipped freight prepaid in the original shipping container or equivalent to the location specified by ProSoft and be accompanied
28. protocol You should understand the important concepts in this chapter before you begin installing and configuring the module 6 2 1 General Concepts The following discussion explains several concepts that are important for understanding the operation of the MVI56 MBP module Module Power Up On power up the module begins performing the following logical functions 1 Initialize hardware components o Initialize backplane driver o Test and Clear all RAM o Reset Modbus Plus Chipset Wait for Module Configuration from processor Initialize Module Register space Initialize Modbus Plus Chipset Enable Global Input task Enable Global Output task Enable Slave Driver Enable Master Driver ONO BR WN ProSoft Technology Inc July 23 2008 Page 49 of 96 MVI56 MBP ControlLogix Platform Reference Modbus Plus Communication Module After the module has received the Module Configuration Block from the processor the Modbus Plus chipset will be enabled presuming valid configuration values were received and will begin communicating with other nodes on the network depending on the configuration Main Logic Loop Upon completing the power up configuration process the module enters an infinite loop that performs the following functions From P ower Up Logic Call 1 0 Handler Call I O Handler Transfers data between the module and processor user status etc Call CFG DEBUG Port Driver Call Network Master
29. specifies the number of registers to Register Count set in the module s database from the processor 4389 44390 Write Block This read only value specifies the number of blocks of 200 Maximum Count word data are to be transferred from the processor to the module 4390 44391 Block Transfer This read only parameter specifies the number of successive Failure Count transfer errors must occur before the Modbus Plus network communications ceases If the value is set to zero communications will never be disabled A value from 1 to 65535 indicates the number of successive errors that will result in the communications shutdown 4391 44392 Spare These registers are not assigned for use in the MVI56 MBP database 4409 44410 Spare ProSoft Technology Inc July 23 2008 Page 79 of 96 MVI56 MBP ControlLogix Platform Modbus Plus Communication Module Reference Global In File Map DB Address Modbus Address Parameter Description 4410 44411 Word 0 Module s database register address for Word 0 of Input File Data 4411 44412 Word 1 Module s database register address for Word 1 of Input File Data 4412 44413 Word 2 Module s database register address for Word 2 of Input File Data 4413 44414 Word 3 Module s database register address for Word 3 of Input File Data 4414 44415 Word 4 Module s database register address for Word 4 of Input File Data 4439 44440 Word 29 Module s database register address for Word 2
30. stored in this object i eela ae Mp SDDDEDEEEE InUpdate INT 7O a x of Global Input status data for devices MstrCmd INT 200 Hex Array of command list error codes Misc INT 30 Decimal Miscellaneous status data InCntr INT 70 Decimal Array of Global Input counters for devices 3 2 4 User Data Objects These objects hold data to be transferred between the processor and the MVI56 MBP module The first set of user data is the global input and output data Globalln INT 32 Decimal Global Input Data GlobalOut INT 32 Decimal Global Output Data The global input data Globalln is transferred to the processor each time a new data read block is received This data area is used for data that requires the highest update frequency for use in the ladder logic Data placed in the input file image is determined by the values entered into the InMap data object MBPInputFileMap object Page 26 of 96 ProSoft Technology Inc July 23 2008 Installing and Configuring the Module MVI56 MBP ControlLogix Platform Modbus Plus Communication Module The global output data GlobalOut is transferred from the module to other nodes on the network each time it generates a Put Global Output command This data is set in the ladder logic by the user and is transferred from the process to the module each time a new write block is constructed and sent to the module This data area is used for data that requir
31. 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 terminal application for example HyperTerminal 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 ProSoft Technology Inc Page 31 of 96 July 23 2008 MVI56 MBP ControlLogix Platform Diagnostics and Troubleshooting Modbus Plus Communication Module 5 1 2 Required Hardware You can connect directly from your computer s serial port to the serial port on the module to view configuration information and perform maintenance ProSoft Technology recommends the following minimum hardware to connect your computer to the module 80486 based processor Pentium preferred 1 megabyte of memory At least one serial communications port available A null modem serial cable 5 1 3 Required Software In order to send and receive data over the serial port COM port on your computer to the module you must use a communication program terminal emulator A simple communication program called HyperTerminal is pre installed with recent versions of Microsoft Windows operating systems If you
32. 1 A 2 A 6 8 aa 0x0008 Put Slave Response to Input Path Press 4 to display slave response messages sent to requests made by other nodes on the network to the module Example output of this option is shown below MTP Tut Slave Response 4H TT 2 24 d D A d 4224 A A A AIA 59 TD B 14 MIT Tut Slave fommand Response 722 MTP Tut Slave Response AA TT 2 24 ih 12 a n 8 a 4 B 8 1 F6 24 gH i A 2 B b A Add AAS A AAA nn nn OA OA AA OA AOA AH R MM AA M MEP Put Slave Command Responce 722 MBP Put Slave Recponea 48 BF 2 24 16 D A 11374 A A A AAA RC H 14 0x0010 Get Master Response from Output Path Press 5 to display master response messages received from other nodes on the network in response to command requests made by the module Example output of this option is shown below MAP Get Hasier Regie 5 MHP Ced Master Rexpgpiuxe h FF 24 2 98 D Af 13 20 4 i 28h A A MOP Get Master Response 75 MUT Get Master Response VIF 24 2 6 iE B 7 1 3 2 0 68 8 8H 314 El L a 2 3 0 4 B 5 B 5 B 7 B uU 6 4 B bb MAP Gel Maxler Rexpuuxe CA MAP Oed Mader Respinse i 3 2 8686 860860314 142484 3 44 B 56 R FF 24 2 96 1F AR 1 B 6 D 7 B 8 B6 4 HB 0x0020 Abort Transaction Press 6 to display any abort transaction messages processed on the Modbus Plus network by the module 0x0040 Configuration Status Press 7 to display any configuration status messages processed by the module
33. 1 Data slave output path 1 amp 2 counter 12 4282 Data slave output path 3 amp 4 counter 13 4283 Data slave output path 5 amp 6 counter 14 4284 Data slave output path 7 amp 8 counter 15 4285 Global Out Update Status 16 4286 Global Out Update Counter 17 4287 Data transfer read counter 18 4288 Data transfer write counter 19 4289 Data parse counter 20 4290 Spare 21 4291 Spare 22 4292 Data transfer error counter 23 4293 Product ID 24 4294 Product ID 25 4295 Revision Level 26 4296 Batch Number 27 4297 MBP Update Processing Time ProSoft Technology Inc July 23 2008 Page 75 of 96 MVI56 MBP ControlLogix Platform Reference Modbus Plus Communication Module Element DB Address Description 28 4298 Global In Update Time 29 4299 Global Out Update Time Module Status Values Normal Operation Code Description 0x00 Interface operational Interface Crash Codes Code Description 0x01 2 second interface timeout 0x02 Bad interface opcode 0x03 Interface data error 0x04 Interface test error 0x05 Interface x fer done error 0x06 Bad interface path 0x07 Bad interface state 0x08 Bad interface length 0x09 Global data length error Ox0A Global data address error 0X0B Global data not present Fatal Crash Codes Code Description 0x81 PROM checksum error 0x82 Internal RAM data test error 0x83 External RA
34. 2 Event one shot bits for commands 32 to 47 7212 47213 Event One Shot 3 Event one shot bits for commands 48 to 63 7213 47214 Event One Shot 4 Event one shot bits for commands 64 to 79 7214 47215 Event One Shot 5 Event one shot bits for commands 80 to 95 7215 47216 Event One Shot 6 Event one shot bits for commands 96 to 111 7216 47217 Event One Shot 7 Event one shot bits for commands 112 to 127 7217 47218 Event One Shot 8 Event one shot bits for commands 128 to 143 7218 47219 Event One Shot 9 Event one shot bits for commands 144 to 159 7219 47220 Event One Shot 10 Event one shot bits for commands 160 to 175 7220 47221 Event One Shot 11 Event one shot bits for commands 176 to 191 7221 47222 Event One Shot 12 Event one shot bits for commands 192 to 199 Page 86 of 96 ProSoft Technology Inc July 23 2008 Support Service amp Warranty MVI56 MBP ControlLogix Platform Modbus Plus Communication Module 7 Support Service amp Warranty In This Chapter How to Contact Us Technical Support seseseeeeee 87 Return Material Authorization RMA Policies and Conditions 88 LIMITED WARRANTY sssssseeeeeeeeeeeen nennen rennen enses 90 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
35. 2 program access denied 0x04 exception response received 0x08 invalid node type in routing path 0x10 slave rejected the Modbus command invalid input path 0x20 initiated transaction forgotten by slave 0x40 unexpected master output path received 0x80 unexpected response received 0x04 Configuration Errors 0x01 Invalid Configuration for Command 0x02 Invalid Command Type 1 Write 2 Read All other error Page 74 of 96 ProSoft Technology Inc July 23 2008 Reference MVI56 MBP ControlLogix Platform Modbus Plus Communication Module High Byte Low Byte Description 0x04 0x08 0x10 0x20 0x40 0x80 Array assignments for Misc member of MBPStat object Miscellaneous Module Status Element DB Address Description 0 4270 Module Status Software Reset Response 1 4271 Peer Status 2 4272 Token Pass Counter 3 4273 Token Rotation Time in milliseconds 4 4274 H Communication Failed Error Counter 4 4274 L Communication Retry Counter 5 4275 H No Response Received Error Counter 5 4275 L Good Received Packet Success Counter 6 4276 H Unexpected Path Error Counter 6 4276 L Exception Response Received Error Counter 7 4277 Data master output path 1 amp 2 counter 8 4278 Data master output path 3 amp 4 counter 9 4279 Data master output path 5 amp 6 counter 10 4280 Data master output path 7 amp 8 counter 11 428
36. 3 Start register of device definit ion block for device index 14 Start register of device definit ion block for device index 15 Start register of device definit ion block for device index 16 Start register of device definit ion block for device index 17 Start register of device definit ion block for device index 18 Start register of device definit ion block for device index 19 Start register of device definit ion block for device index 20 Start register of device definit ion block for device index 21 DB Address Modbus Address Parameter 4450 44451 Device Def ID 0 4460 44461 Device Def ID 1 4470 44471 Device Def ID 2 4480 44481 Device Def ID 3 4490 44491 Device Def ID 4 4500 44501 Device Def ID 5 4510 44511 Device Def ID 6 4520 44521 Device Def ID 7 4530 44531 Device Def ID 8 4540 44541 Device Def ID 9 4550 44551 Device Def ID 10 4560 44561 Device Def ID 11 4570 44571 Device Def ID 12 4580 44581 Device Def ID 13 4590 44591 Device Def ID 14 4600 44601 Device Def ID 15 4610 44611 Device Def ID 16 4620 44621 Device Def ID 17 4630 44631 Device Def ID 18 4640 44641 Device Def ID 19 4650 44651 Device Def ID 20 4660 44661 Device Def ID 21 4670 44671 Device Def ID 22 Start register of device definit ion block for device index 22 Page 80 of 96 ProSoft Technology Inc July 23 2008 Reference MVI56 MBP ControlLogix Platform Modbus Plus Communication Module
37. 4990 44991 Device Def ID 54 Start register of device definition block for device index 54 5000 45001 Device Def ID 55 Start register of device definition block for device index 55 5010 45011 Device Def ID 56 Start register of device definition block for device index 56 5020 45021 Device Def ID 57 Start register of device definition block for device index 57 5030 45031 Device Def ID 58 Start register of device definition block for device index 58 5040 45041 Device Def ID 59 Start register of device definition block for device index 59 5050 45051 Device Def ID 60 Start register of device definition block for device index 60 5060 45061 Device Def ID 61 Start register of device definition block for device index 61 5070 45071 Device Def ID 62 Start register of device definition block for device index 62 5080 45081 Device Def ID 63 Start register of device definition block for device index 63 ProSoft Technology Inc July 23 2008 Page 81 of 96 MVI56 MBP ControlLogix Platform Modbus Plus Communication Module Device Definition Block Format Reference The structure of the data in each block is described in the following table DB Address Modbus Address Parameter Description 4450 44451 Route 1 These values determine the network route that a message will 4451 44452 Route 2 use to get from the module to a node on the network The values are entered directly into the Modbus Plus message 4452 444
38. 53 Route 3 Note the following 4453 44454 Route 4 PLCs When addressing these devices the last non zero byte 4454 44455 Route 5 in the routing list specifies the network node address For example to reach node 7 on the network enter 7 0 0 0 0 ModConnect Type Devices When addressing these devices including other MVI56 MBP modules the next to last non zero values specifies the node address and the last non zero value specifies the slave data path to use 1 to 8 If the slave path is set incorrectly the message will fail For example to reach slave path 1 on node 6 enter values of 6 1 0 0 0 4455 44456 Device Type This parameter is ignored in the current version of the software It may be required in future releases to customize communication for non compliant devices 4456 44457 Global In Length This parameter sets the length of global data accepted from the specified node If a value of zero is entered no global data will be accepted from this node A value of 1 to 32 indicate that global data is to be expected from the module and the length of data to accept is set in this parameter 4457 44458 Global In Storage This parameter specifies the starting address in the module s Address database where the received global data will be placed Valid locations are from 0 to 3999 4458 44459 Spare Not used 4459 44460 Spare Not used Master Command List The next data set present in the module s database is the master command list
39. 64 Spare 65 4065 Spare 66 4066 Spare 67 4067 Spare 68 4068 Spare 69 4069 Spare Status Code Definitions Code Definition 0x01 Updating All okay 0x02 0x04 0x08 0x10 Global Update Timeout in milliseconds Global Data Not Configured 0x20 0x40 Invalid Global Data Length 0x80 ProSoft Technology Inc July 23 2008 Page 73 of 96 MVI56 MBP ControlLogix Platform Reference Modbus Plus Communication Module Array assignments for MstrCmd member of MBPStat object Master Command Status Element DB Address Description 0 4070 Master Command Status 1 1 4071 Master Command Status 2 2 4072 Master Command Status 3 3 4073 Master Command Status 4 4 4074 Master Command Status 5 5 4075 Master Command Status 6 6 4076 Master Command Status 7 7 4077 Master Command Status 8 8 4078 Master Command Status 9 9 4079 Master Command Status 10 195 4265 Master Command Status 196 196 4266 Master Command Status 197 197 4267 Master Command Status 198 198 4268 Master Command Status 199 199 4269 Master Command Status 200 Error Code Definition High Byte Low Byte Description 0x00 0x00 Normal Driver will reset when processing command 0x01 Command has completed successfully 0x02 Routing Errors 0x01 No response received Is addressed unit online 0x0
40. 8 98 to 105 Device Definition 8 106 to 113 Device Definition 8 114 to 121 Device Definition 8 122 to 129 Device Definition 8 Blocks 6000 to 6007 Master Command List Data Offset Description Length 0 6000 to 6007 1 1 6000 to 6007 1 2to9 Command Definition 8 Page 58 of 96 ProSoft Technology Inc July 23 2008 Reference MVI56 MBP ControlLogix Platform Modbus Plus Communication Module Offset Description Length 10 to 17 Command Definition 8 18 to 25 Command Definition 8 26 to 33 Command Definition 8 34 to 41 Command Definition 8 42 to 49 Command Definition 8 50 to 57 Command Definition 8 66 to 73 Command Definition 8 74 to 81 Command Definition 8 82 to 89 Command Definition 8 90 to 94 Command Definition 8 98 to 105 Command Definition 8 106 to 113 Command Definition 8 114 to 121 Command Definition 8 122 to 129 Command Definition 8 130 to 137 Command Definition 8 138 to 145 Command Definition 8 146 to 153 Command Definition 8 154 to 161 Command Definition 8 162 to 169 Command Definition 8 170 to 177 Command Definition 8 178 to 185 Command Definition 8 186 to 193 Command Definition 8 194 to 201 Command Definition 8 Each of these blocks must be handled by the ladder logic for proper module operation Warm Boot This block is sent from the ControlLogix processor to the module output image when the module is required to perform a warm boot sof
41. 9 of Input File Data 4440 44441 Word 30 Module s database register address for Word 30 of Input File Data 4441 44442 Word 31 Module s database register address for Word 31 of Input File Data 4442 44443 Spare 4449 44450 Spare Device Definition The Device Definition table consists of 64 blocks of data with each block containing the information for a single device to interface with on the network The following table describes the starting addresses of each block of data Description Start register of device definit ion block for device index 0 Start register of device definit Start register of device definit ion block for device index 1 ion block for device index 2 Start register of device definit ion block for device index 3 Start register of device definit ion block for device index 4 Start register of device definit ion block for device index 5 Start register of device definit ion block for device index 6 Start register of device definit ion block for device index 7 Start register of device definit ion block for device index 8 Start register of device definit ion block for device index 9 Start register of device definit ion block for device index 10 Start register of device definit ion block for device index 11 Start register of device definit ion block for device index 12 Start register of device definit ion block for device index 1
42. Count NT Decimal 0 32 number of devices in device table 1 CommandCnt NT Decimal 0 100 max number of commands in list ix MaxDataPaths INT Decima 1 8 max number of master data paths E CmdTimeout NT Decima 0 655535 mSec timeout fro receive This object defines the parameters for the operation of the Modbus Plus communication driver in the module Input File Map Le DD Data Type Reg INT 32 m e of Madbus registers in the module to associate with the input file data This object defines the list of registers in the module s internal database to be associated with the input image transferred from the module to the processor The number of entries processed in the list is determined by the InputFileLen parameter in the MBPConfig object Each position in the Reg array corresponds to the associated word in the input image and contains a register value valid for the module Refer to the MVI56 MBP database layout chart in Database Definition ProSoft Technology Inc Page 23 of 96 July 23 2008 MVI56 MBP ControlLogix Platform Installing and Configuring the Module Modbus Plus Communication Module Device Definition deg i i ata Type Routel INT SR s address Fiuule2 INT Decimal Fiuule address Route3 JINT Decimal Route address I Route4 INT Decimal Route address FH Route5 INT Decimal Route address Fi DevType INT Decimal Reserved for future use FE GloballnLen INT Decimal 0 32 number of Globa
43. Definition List Menu This list consists of multiple pages of device definition data Press to view a list of commands available on this menu Redisplaying the Current Page Press S to display the current page of data Viewing the Previous Page of Commands Press P to display the previous page of commands Page 40 of 96 ProSoft Technology Inc July 23 2008 Diagnostics and Troubleshooting Viewing the Next Page of Commands Press N to display the next page of commands Returning to the Main Menu Press M to return to the Main Menu 5 1 8 Database View Menu MVI56 MBP ControlLogix Platform Modbus Plus Communication Module Press D from the Main Menu to open the Database View menu Use this menu command to view the current contents of the module s database Press to view a list of commands available on this menu M Main Menu D Database Menu Display Menu Redisplays refeshes this menu O 3 Pages D to 3000 Selects page D 1000 2000 or 3000 Show Again Redisplays last selected page ofdata Back 5 Pages Goes back five pages of data P Previous Page Goes back one page of data Skip 5 Pages Goes forward five pages ofdata N Next Page Goes forward one page ofdata D Decimal Display Displays data in decimal format H Hexadecimal Display Displays data in hex format F Float Display Displays data in float
44. Each command requires a block of ten registers in the database to describe the command There are 200 commands that can be defined in the module Therefore this data occupies 2000 registers The starting locations for the commands is shown in the following table DB Address Modbus Address Parameter Description 5090 45091 Cmd 0 Start of command block for command 0 5100 45101 Cmd 1 Start of command block for command 1 5110 45111 Cmd 2 Start of command block for command 2 5120 45121 Cmd 3 Start of command block for command 3 5130 45131 Cmd 4 Start of command block for command 4 5140 45141 Cmd 5 Start of command block for command 5 7060 47061 Cmd 197 Start of command block for command 197 7070 47071 Cmd 198 Start of command block for command 198 7080 47081 Cmd 199 Start of command block for command 199 The data structure associated with each command block is described in the following table Page 82 of 96 ProSoft Technology Inc July 23 2008 Reference MVI56 MBP ControlLogix Platform Modbus Plus Communication Module DB Address Modbus Address Parameter Description 5090 45091 Enable This parameter is used define if the command will be executed or will be disregarded The following values are valid 0 Disables the command and it will not execute 1 The command will be considered for execution each scan of the command list and will be controlled by
45. I56 MBP module requires a reasonable working knowledge of the Rockwell Automation hardware the MVI56 MBP Module and the application in which they will be used A It is important that those responsible for implementation can complete the application without exposing personnel or equipment to unsafe or inappropriate working conditions Safety quality and experience are key factors in a successful installation 2 1 System Requirements The MVI56 MBP 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 MBP module The module requires 800mA of available power Rockwell Automation RSLogix 5000 programming software version 2 51 or higher Rockwell Automation RSLinx communication software Pentium Il 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 x 768 recommended ProSoft Technology Inc Page 9 of 96 July 23 2008 MVI56 MBP ControlLogix Platform Start Here Mo
46. IDE TO THE MVI56 MBP USER MANUAL eeeseeeneeen enne nenne nnne nn nn nn ann nn nennt nnn nnn 7 2 START THER Ea e a eerte cesta tese eine DEDE coe d iere sue emen bee a sna sot alata dr 9 2 1 System Regulremkents soy x ieee fs tebe Selle chads RR t n m o D ERE 9 2 2 Package Corltents t deed euet tetur 10 2 3 Setting Jurmpers mm into imm emnt 10 24 Install the Module in the Rack ao n a DE ene enne nnns 11 2 5 Connect your PC to the Processor eene ennemis 13 2 6 Download the Sample Program to the Processor ssssseee 14 2 7 Connect your PC to the Module sssssssssee enm nennen 16 3 INSTALLING AND CONFIGURING THE MODULE reen reen 17 3 1 Module Configuration essct si nh Ae eee agente e metu egeta ge 21 3 2 Module Data ObJeCt 3 het ntt mt EN tr PED ad Hob urb He dead HE decent 22 LADDER EOGIC 4 Sate chase caste ALAS ED ES LIMES 29 DIAGNOSTICS AND TROUBLESHOOTING eeeseeeeeeeneeee ense enne nennen nn nn nasa nennt nnn nnns 31 5 1 Reading Status Data from the Module sssssseeeeeee een 31 5 2 LED Status Indicators x5 nee tel ains uet ain tuse 44 5 3 Clearing a Fault Gondition eterne e te er a es 45 5 4 Troubleshooting ss etm eda pR It eaa ununi 45 6 gt REFERENCE c 47 6 1 Product Specificatioris 5 idet tote eite ie oet loe ede Ia Ee Pee aa i
47. M data test error 0x84 External RAM address test error 0x85 Bad confidence test index 0x86 External IntO event error 0x87 External Int1 event error 0x88 DMA Into event error 0x89 Comm Int event error 0x8A Xmit no good event error 0X8B No response timeout MAC State 0X8C No response timeout MAC idle 0X8D Receive OK MAC state OX8E Transmit OK MAC state OX8F No receive buffer free 0X90 Bad input transfer length 0X91 Reserved rev buffer error 0X92 Bad trans control state Page 76 of 96 ProSoft Technology Inc July 23 2008 Reference MVI56 MBP ControlLogix Platform Modbus Plus Communication Module Code Description 0X93 Bad word request bit 0X94 Node queue overflow 0X95 Bad data queue error 0X96 Empty data path error 0X97 Bad path search index 0X98 Bad data slave path Peer Status Codes Code Description 0 Monitor link operation 32 Normal link operation 64 Never getting token 96 Sole station 128 Duplicate station Global Out Update Status Code Description 0x01 Updating all OK 0x02 Not assigned 0x04 Not assigned 0x08 Global update timeout not transmitted in 500 milliseconds 0x10 Global data not configured length set to zero 0x20 Not assigned 0x40 Invalid Global Data Length Length gt 32 words 0x80 Not assigned Array assignments for InCntr member of MBPStat object Global In Update Counters E
48. MVI56 MBP ControlLogix Platform Modbus Plus Communication Module User Manual July 23 2008 TVEC HN OLOGY Please Read This Notice Successful application of this module requires a reasonable working knowledge of the Rockwell Automation ControlLogix hardware the MVI56 MBP Module and the application in which the combination is to be used For this reason it is important that those responsible for implementation satisfy themselves that the combination will meet the needs of the application without exposing personnel or equipment to unsafe or inappropriate working conditions This manual is provided to assist the user Every attempt has been made to ensure that the information provided is accurate and a true reflection of the products installation requirements In order to ensure a complete understanding of the operation of the product the user should read all applicable Rockwell Automation documentation on the operation of the Rockwell Automation hardware Under no conditions will ProSoft Technology be responsible or liable for indirect or consequential damages resulting from the use or application of the product Reproduction of the contents of this manual in whole or in part without written permission from ProSoft Technology is prohibited Information in this manual is subject to change without notice and does not represent a commitment on the part of ProSoft Technology Improvements and or changes in this manual or the product may
49. Platform Modbus Plus Communication Module 2 6 1 Configuring RSLinx If RSLogix is unable to establish communication with the processor follow these steps 1 OpenRSLinx 2 Open the Communications menu and choose Configure Drivers Communications Station DDE OPC RSWho Confiqure Drivers Configure Shortcuts Configure Client Applications Configure CIP Options Driver Diagnostics CIP Diagnostics This action opens the Configure Drivers dialog box r Available Driver Types Close RS 232 DF1 Devices Add New Help Configured Drivers Name and Description Status O Configure Startup Start Stop Delete Note If the list of configured drivers is blank you must first choose and configure a driver from the Available Driver Types list The recommended driver type to choose for serial communication with the processor is RS 232 DF1 Devices ProSoft Technology Inc Page 15 of 96 July 23 2008 MVI56 MBP ControlLogix Platform Start Here Modbus Plus Communication Module 3 Click to select the driver and then click Configure This action opens the Configure Allen Bradley DF1 Communications Device dialog box Configure Allen Bradley DF1 Communications Device Device Name AB DF1 1 Comm Port COM1 bd Device Logix 5550 Serial Port Baud Rate 13200 va ES ctal Parity None Error Checking CRC R Stop B
50. User Data Objects 26 Using the Configuration Debug Port 32 V Viewing Block Transfer Statistics 34 Viewing Communication Status 37 Viewing Data in ASCII Text Format 42 Viewing Data in Decimal Format 42 Viewing Data in Floating Point Format 42 Viewing Data in Hexadecimal Format 42 Viewing Global In Data 35 Viewing I O File Data 36 Viewing Module Configuration 35 Viewing Register Pages 41 Viewing the Event Command Enable List 37 Viewing the Next 100 Registers of Data 42 Viewing the Next 20 Commands 43 Viewing the Next Page of Commands 41 43 Viewing the Previous 100 Registers of Data 42 Viewing the Previous 20 Commands 43 Viewing the Previous Page of Commands 40 43 Viewing Version Information 36 W Warm Booting the Module 36 Warnings 2 What Is Covered By This Warranty 90 92 What Is Not Covered By This Warranty 90 Y Your Feedback Please 4 Page 96 of 96 ProSoft Technology Inc July 23 2008
51. 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 Repeat this command at one second intervals to determine the frequency of program execution Warm Booting the Module 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 other failures Only use these commands if you are specifically directed to do so by ProSoft Technology Inc Technical Support staff Some of these command keys are not listed on the menu but are active nevertheless Please be careful when pressing keys so that you do not accidentally execute an unwanted command 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 re boot Page 36 of 96 ProSoft Technology Inc July 23 2008 Diagnostics and Troubles
52. a from the MVI56 MBP module a MSTR Type 2 instruction must be entered in the Modicon s ladder program This instruction initiates a Modbus Plus network transaction between the PLC and the module In the configuration of the command the programmer can specifically choose the location and amount of data to be read from the module and returned to the Modicon s memory The following diagram details an example configuration for a MSTR Type 2 command Contents of registers in the control block S E 40050 2 Read instruction active 40051 7 0 Error code 40052 20 Length of the read ducere 40053 50 slave register to read module address 50 error 40054 6 MVI56 MBP Node address to retrieve data from preti ll 40055 1 Slave Input Path for routing success 40056 0 Routing Address 3 40057 0 Routing Address 4 FOR POPE UNE 40058 0 Routing Address 5 40060 Destination address in the Modicon PLC for the data from the MVI56 MBP module The MSTR 2 instruction shown above reads 20 words from the MVI56 MBP module beginning at address 50 and places the data in the Modicon PLC beginning at address 40060 E a 4 5i Note that the Slave Input Path value must be entered in order for the command to execute successfully Valid values are from 1 to 8 Any other values will cause the command to fail In order for a Modicon PLC to write data to the module a MSTR Type 1 instruction must be entered in the Modicon s ladder program This
53. ap 72 Module Power Up 49 Module Status Values 76 Moving Back Through 5 Pages of Registers 42 N Navigation 33 No Other Warranties 93 Normal Data Transfer 52 Normal Operation 76 O Opening the Data Analyzer Menu 34 Opening the Device Definition List Menu 35 Overview 72 P Package Contents 10 Peer Status Codes 77 Please Read This Notice 2 Power Up 67 Procedures for Return of Units Out of Warranty 89 Procedures for Return of Units Under Warranty 89 Processor Not in Run 50 Product Specifications 7 47 ProSoft Product Documentation 3 Purchasing Warranty Extension 89 R Reading Status Data from the Module 31 Redisplaying the Current Page 40 43 Reference 7 47 Required Hardware 32 Required Software 32 Return Material Authorization RMA Policies and Conditions 88 Returning to the Main Menu e 40 41 43 RS 232 Configuration Debug Port 68 S Setting Jumpers 10 Skipping 500 Registers of Data 42 Index Slave Driver Mode 61 Start Here 7 9 Status Blocks 55 Status Code Definitions 73 Status Data Definition 72 73 Status Objects 26 Successful Execution 65 Support Service amp Warranty 7 87 System Requirements 9 T The Configuration Debug Menu 31 Time Limit for Bringing Suit 93 Transferring Module Configuration to the Processor 37 Troubleshooting 45 U Unsuccessful Execution 67
54. atible processors to interface easily with other Modbus Plus protocol compatible devices The Modbus Plus module is a powerful module designed with both Master and Slave support enabling easy connection to other Modbus devices Modicon processors and many others 6 1 1 Features and Benefits Compatible devices include not only Modicon PLCs which all support the Modbus Plus protocol but also a wide assortment of end devices licensed through the Collaborative Automation Partner Program The MVI56 MBP module acts as an input output module between the Modbus Plus network and the ControlLogix processor The data transfer from the ControlLogix processor is asynchronous from the actions on the Modbus Plus network A 4000 word register space in the module exchanges data between the processor and the Modbus Plus network These modules allow ControlLogix processors to connect directly on Modbus Plus networks as a peer In addition the modules act as slaves to processors that must read write data from the module s memory Crossing all industrial boundaries potential applications include the connection of ControlLogix processors to Modicon processors and the connection of Modbus Plus speaking devices such as drives relays and power monitor hardware to the ControlLogix backplane ProSoft Technology Inc Page 47 of 96 July 23 2008 MVI56 MBP ControlLogix Platform Reference Modbus Plus Communication Module 6 1 2 Functional Specification
55. between the module and the processor Page 50 of 96 ProSoft Technology Inc July 23 2008 Reference MVI56 MBP ControlLogix Platform Modbus Plus Communication Module The processor inserts data to the module s output image to transfer to the module The module s program extracts the data and places it in the module s internal database The output image for the module is set to 248 words This large data area permits fast throughput of data from the processor to the module The following illustration shows the data transfer method used to move data between the ControlLogix processor the MVI56 MBP module and the Modbus Plus network ControlLogix Processor MVI56 MBP Module ControlLogix Processor Controller Tags Dota frem module s input imago to data awas in the Data from Output image Procassar date arene As shown in the previous diagram all data transferred between the module and the processor over the backplane is through the input and output images Ladder logic must be written in the ControlLogix processor to interface the input and output image data with data defined in the Controller Tags All data used by the module is stored in its internal database This database is defined as a virtual Modbus data table with addresses from 0 40001 Modbus to 7221 47222 Modbus The following illustration shows the layout of the database ProSoft Technology Inc Page 51 of 96 July 23 2008 MVI56 MBP ControlLogix Platf
56. by proof of purchase and receipt date The RMA number is to be prominently marked on the outside of the shipping box Customer agrees to insure the Product or assume the risk of loss or damage in transit Products shipped to ProSoft using a shipment method other than that specified by ProSoft or shipped without an RMA number will be returned to the Customer freight collect Contact ProSoft Technical Support for further information d A 10 restocking fee applies to all warranty credit returns whereby a Customer has an application change ordered too many does not need etc Page 88 of 96 ProSoft Technology Inc July 23 2008 Support Service amp Warranty MVI56 MBP ControlLogix Platform Modbus Plus Communication Module 7 2 2 Procedures for Return of Units Under Warranty A Technical Support Engineer must approve the return of Product under ProSoft s Warranty a A replacement module will be shipped and invoiced A purchase order will be required b Credit for a product under warranty will be issued upon receipt of authorized product by ProSoft at designated location referenced on the Return Material Authorization e If a defect is found and is determined to be customer generated or if the defect is otherwise not covered by ProSoft s Warranty there will be no credit given Customer will be contacted and can request module be returned at their expense 7 2 3 Procedures for Return of Units Out of Warranty a Customer s
57. ccepted After the data is accepted the data is transferred into the module s internal database The user via configuration in the Device Definition File determines the location of the data As data is read from the other nodes on the network into the module an asynchronous process moves the data from the database into the module s input image The values to be moved are user determined via configuration of the Input File Map Up to 32 words of data can be transferred in this fashion Status is monitored for each device in the Device Definition File that is expected to return Global In data to the module This status is updated on an on going basis and is transferred to the ControlLogix processor for processing This data includes the node status value and a counter incremented each time global input data is received Page 66 of 96 ProSoft Technology Inc July 23 2008 Reference MVI56 MBP ControlLogix Platform Modbus Plus Communication Module In order for the Global Data In mode to operate the minimum configuration includes setting the Device Definition File and the Global Input Timeout values If this or other data is to transfer to the ControlLogix processor using the Input File the Input File Map Input File Size and Input File Update parameters must also be set It is important to understand how the Input File Map determines what data is transferred from the module to the processor The Input File Map is a 32 w
58. commands are user configured in the module via the Master Command List received from the ControlLogix processor Command status is returned to the processor for each individual command in the command list status block The module emulates the MSTR Type 1 and Type 2 commands in terms of data read and write functionality The following flow chart and associated table describe the flow of data into and out of the module Processor Memory Backplane Interface MBP Memory ControlLogix Database Modbus Controll cdi Addresses Addresses i i i Register Register Event Cmd er Er Data ProSoft Technology Inc Page 63 of 96 July 23 2008 MVI56 MBP ControlLogix Platform Reference Modbus Plus Communication Module Step Description 1 The Master driver obtains configuration data from the ControlLogix processor The configuration data obtained includes the number of commands the Device Definition File and the Master Command List These values are used by the Master driver to determine the type of commands to issue to the other nodes on the Modbus Plus network In addition Event Command control bits are available to control individual commands from ladder logic 2 After configuration the Master driver begins transmitting read and or write commands to the other nodes on the network If writing data to another node the data for the write command is obtained from the module s internal database to build
59. dbus Plus Communication Module 2 2 2 3 CD ROM drive 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 ControlNet communication with the processor Package Contents The following components are included with your MVI56 MBP 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 MBP MVI56 MBP Modbus Plus Communication Module Module 1 Cable Cable 15 RS232 For RS232 Connection to the CFG Port Null Modem 1 Cable Cable 14 RJ45 to For DB9 Connection to the CFG Port DB9 Male Adapter 1 ProSoft Contains sample programs utilities and Solutions CD documentation for the MVI56 MBP module If any of these components are missing please contact ProSoft Technology Support for replacement parts Setting Jumpers The following illustration shows the MVI56 MBP jumper configuration fe WET LET CHOE ALM CLR SEU j f PRT PRT O Not used Not used Page 10 of 96 ProSoft Technology Inc July 23 2008 Start Here MVI56 MBP ControlLogix Platform 2 4 Modbus Plus Communication Module Do not change the position of the Setup jumper unless instructed to do so by ProSoft Technical Support
60. de 5097 45098 Register Address in Device This parameter defines the starting address in the device being considered by the command Values entered in this field are dependent on the node s database definition Refer to the specific manufacture s database definition for the device to determine the location of the data to be interfaced 5098 45099 Spare Not used 5099 45100 Spare Not used 6 6 4 Global Output Data Global Output Data transmitted from the MVI56 MBP module to the network is located at registers 7090 to 7121 in the module s database This data is globally broadcast to all active nodes on the network Destination nodes can be configured to accept or ignore incoming data from specific source nodes Data is transferred from the processor to the module in each new output image block The following table shows the database registers used by this data ProSoft Technology Inc July 23 2008 Page 83 of 96 MVI56 MBP ControlLogix Platform Modbus Plus Communication Module Global Out Image Reference DB Address Modbus Address Parameter Description 7090 47091 Global Out 0 Global output data for module word 0 7091 47092 Global Out 1 Global output data for module word 1 7092 47093 Global Out 2 Global output data for module word 2 7093 47094 Global Out 3 Global output data for module word 3 7094 47095 Global Out 4 Global outp
61. der Logic Modbus Plus Communication Module Page 30 of 96 ProSoft Technology Inc July 23 2008 Diagnostics and Troubleshooting MVI56 MBP ControlLogix Platform 5 1 Modbus Plus Communication Module Diagnostics and Troubleshooting In This Chapter Reading Status Data from the Module sssssssssesss 31 LED Status Indicators as ii dr rn ad emm eee 44 Clearing a Fault Condition sssssssseeeeeneeee 45 roubleshootirig ee REESE Dee REDE HR CER 45 The module provides information on diagnostics and troubleshooting in the following forms Status data values are transferred from the module to the processor Data contained in the module can be viewed through the Configuration Debug port attached to a terminal emulator LED status indicators on the front of the module provide information on the module s status Reading Status Data from the Module The MVI56 MBP module returns a 365 word Status Data block that can be used to determine the module s operating status This data is located in the module s database at registers 4000 to 4365 This data is transferred to the ControlLogix processor approximately every second Nodes on the Modbus Plus network can read this data area through the issuance of read commands to the module 5 1 1 The Configuration Debug Menu The Configuration and Debug menu for this module is arranged as a tree structure with the Main Menu at the
62. dered by the command Values entered in this field are dependent on the node s database definition Refer to the specific manufacture s database definition for the device to determine the location of the data to be interfaced 3 2 2 MBP User Cmd This object sends Modbus Plus commands directly from ladder logic to the MVI56 MBP a oo Eem Internal de datahase address in module f tui HUL Decima Number of registers for command SwapCode INT Decimal Swap code 0 to 3 EF Device INT Decimal Device index from configured list A Func INT Decimal Function Code 3 or 16 fi DevDB INT Decimal Register address in device Spae 1 INT Decimal Spare 2 INT Decimal Spare 3 INT Decimal Spare 4 INT Decimal ProSoft Technology Inc Page 25 of 96 July 23 2008 MVI56 MBP ControlLogix Platform Installing and Configuring the Module Modbus Plus Communication Module 3 2 3 Status Objects These objects view the status of the module The MBPInStat object shown below is updated each time a read block is received by the processor Use this data to monitor the state of the module at a real time rate Name DataType Style Description MBPErr INT Hex MBP Error Status Peer INT Hex Peer Status TokenPass INT Decimal Token Pass Counter TokenTime INT Decimal To
63. ds it and is bound by its Terms 7 3 10 Controlling Law and Severability This Warranty shall be governed by and construed in accordance with the laws of the United States and the domestic laws of the State of California without reference to its conflicts of law provisions If for any reason a court of competent jurisdiction finds any provisions of this Warranty or a portion thereof to be unenforceable that provision shall be enforced to the maximum extent permissible and the remainder of this Warranty shall remain in full force and effect Any cause of action with respect to the Product or Services must be instituted in a court of competent jurisdiction in the State of California ProSoft Technology Inc Page 93 of 96 July 23 2008 MVI56 MBP ControlLogix Platform Support Service amp Warranty Modbus Plus Communication Module Page 94 of 96 ProSoft Technology Inc July 23 2008 Index Index 0x0000 Turn Debug off 38 0x0001 Service Requests 38 0x0002 Put Master Command to Output Path 39 0x0004 Get Slave Command from Input Path 39 0x0008 Put Slave Response to Input Path 39 0x0010 Get Master Response from Output Path 39 0x0020 Abort Transaction 39 0x0040 Configuration Status 39 0x0080 Interface Diagnostics 40 0x0100 Software Reset 40 0x0200 Put Global Data 40 0x0400 Get Global Data 40 A ped All Product Returns 88 Allocation of Risks 93 Array assignmen
64. dule has the following format Offset Description Length 0 9003 1 1 Number of commands to add 1 2 to 61 List of command indexes 60 62 to 247 Spare 186 Word 1 of the block is used to set the number of commands listed in the block Up to 60 commands can be sent to the command queue using this block Words 2 to 61 contain the command indexes to be added to the queue Command Enable Disable Blocks Block codes 9010 9011 and 9012 are used to alter the enable code for a set of commands in the module s command list Word 1 in each block is used to define the number of commands to be considered by the module in the list of command indexes provided Block 9010 is used to disable one or more commands in the command list by setting the enable code to a value of zero The format of the block is as follows Offset Description Length 0 9010 1 1 Number of commands to disable 1 2 to 61 List of command indexes 60 62 to 247 Spare 186 Block 9011 is used to set the enable code for the commands in the list to a value of one The format of the block is as follows Offset Description Length 0 9011 1 1 Number of commands to enable 1 2 to 61 List of command indexes 60 62 to 247 Spare 186 Block 9012 is used to set the enable code for the commands in the list to a value of two The format of the block is as follows Offset Description Length 0 9012 1 1 Number of commands
65. dule with the top and bottom guides and slide it into the rack until the module is firmly against the backplane connector Slot 1 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 will need to identify the slot in which the module is installed in order for the sample program to work correctly Slot numbers are identified on the green circuit board backplane of the ControlLogix rack 6 Turn power ON Note If you insert the module improperly the system may stop working or may behave unpredictably Note If you are installing MVI56 MBP with other modules connected to the PCI bus the peripheral modules will not have holding clips Make sure all of the modules are aligned with their respective slots before you snap them into place Page 12 of 96 ProSoft Technology Inc July 23 2008 Start Here MVI56 MBP ControlLogix Platform Modbus Plus Communication Module 2 5 Connect your PC to the Processor 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 13 of 96 July 23 2008 MVI56 MBP ControlLogix Pla
66. e processor write blocks Additionally this data area is used as a data source for the processor read blocks or other nodes on the network master write commands Detailed definition of the status data area can be found in Status Data Definition page 73 These areas include the following Global In Update Status Master Command Status Misc Module Status and Global In Update Counters Definition of the configuration data areas can be found in Configuration Data Definition These data areas include the following Module Configuration Block Global In File Map Device Definition Master Command List The Global Out Image is a data area of 40 words Only the first 32 words are filled with data This data is transferred from the processor to the module on each write block command and placed on the Modbus Plus network This data area is used for high speed data that must be passed to other nodes on the network at a high frequency The Global In Image is a data area of 40 words Only the first 32 words are filled with data This data is transferred from the module to the processor on each block read command Data in the block is determined by the Global In File Map data set This data area is used for high speed data that must be passed to the processor at the highest frequency The Command Event Data area controls master commands under processor control This data area is updated on each write block transfer from the processor to the module
67. e command will be considered for execution each scan of the command list and will be controlled by the Polllnt parameter and 2 The command will only execute if the event control bit for the command is set IntAddress This parameter specifies the starting internal register address to be associated with the command Valid entry for this parameter is O to 3999 Pollint This parameter defines the minimum number of seconds to wait between the execution of continuous commands Enable 1 This poll interval command can be used to lighten the communications load on a busy network Valid entry for this parameter is 0 to 65535 Count This parameter defines the number of registers to be considered by the command Valid entry for this parameter is 1 to 100 Swap This parameter is used to swap the bytes in the data read or written by the command The codes used are as follows 0 No swapping 1 Swap words 2 Swap words and bytes 3 Swap bytes Device This parameter associates the command with a device defined in the device definition table Device in the MBPlusModuleDef object The index defined in this parameter sets the route path defined for the device in the Modbus Plus message Func This parameter specifies the function to be performed by the command Valid entries are 3 Read register data from a node and 16 2 Write register data to a node DevAddress This parameter defines the starting address in the device being consi
68. e definition block for device index 37 4830 44831 Device Def ID 38 Start register of device definition block for device index 38 4840 44841 Device Def ID 39 Start register of device definition block for device index 39 4850 44851 Device Def ID 40 Start register of device definition block for device index 40 4860 44861 Device Def ID 41 Start register of device definition block for device index 41 4870 44871 Device Def ID 42 Start register of device definition block for device index 42 4880 44881 Device Def ID 43 Start register of device definition block for device index 43 4890 44891 Device Def ID 44 Start register of device definition block for device index 44 4900 44901 Device Def ID 45 Start register of device definition block for device index 45 4910 44911 Device Def ID 46 Start register of device definition block for device index 46 4920 44921 Device Def ID 47 Start register of device definition block for device index 47 4930 44931 Device Def ID 48 Start register of device definition block for device index 48 4940 44941 Device Def ID 49 Start register of device definition block for device index 49 4950 44951 Device Def ID 50 Start register of device definition block for device index 50 4960 44961 Device Def ID 51 Start register of device definition block for device index 51 4970 44971 Device Def ID 52 Start register of device definition block for device index 52 4980 44981 Device Def ID 53 Start register of device definition block for device index 53
69. ed 5 6 1 0 Configuration BJ 1 1756 MODULE MBP 1 jio jene 3 ES ESESESESESE The next step in module setup is to define the data to be used to interface with the module and the ladder logic Open the Controller Tags Edit Tags dialog box and enter the values shown in the following example The MVI56 MBP module is defined in the example as MBP1 You can set the tag name to any valid tag name you desire If you are using the example ladder logic this step has already been performed Controller Tags CP Sample controller OF xi Scope CIP Sample controli v Show Show All v Sot Tag Name x P Tag Name X Alias For Descriptic 2 ColdBoot BOOL Binary H Local1 C B 1756 MODUL Local 1 1 4B 1756_MODUL HH Local1 0 4B 1756_MODUL MBP1 MBPlusModuleD ef MJFAULTS DINT 12 Decimal WarmBoot BOOL Binary X BE a DA At this point take the time to fill in the configuration values in the MBP1 data table and adjust array sizes Refer to the Module Data Object section of this document for information on configuring the module Page 20 of 96 ProSoft Technology Inc July 23 2008 Installing and Configuring the Module MVI56 MBP ControlLogix Platform Modbus Plus Communication Module The last step in the module setup is to add the ladder logic If you are using the example ladder logic adjust the ladder to
70. efore the module can be used This is done by declaring a variable of the data type in the Controller Tags Edit Tags dialog box The structure of the object is displayed in the figure below Name DataType Se Description ModDef MBPModule Backplane operation characteristics Cfg MBPConfig MBPlus settings for module H InMap MBPlnputFileM ap Input file register map H Device MBPDeviceDef 64 Device Definition Table rj Cmd MBPCmd 200 Master Command List H BP MBPlusBackplane Backplane runtime variables H Stat MBPStat Module Status Data Globalln INT 32 Decimal Global Input Data GlobalOut INT 32 Decimal Global Output Data InStat MBPlInStat Status information in each read block ReadData INT 600 Decimal Data read from module WriteData INT 600 Decimal Data to write to module EventCti INT T3 Binary Event Command Control Flags commands per word This object contains objects that define the configuration user data status and command control data related to the module Each of these object types is discussed in the following sections of the document 3 2 1 Configuration Objects Configuration of the module is performed by filling in the values in the module object defined in the Controller Tags Edit Tags dialog Each parameter required by the module has a defined location in the object The tables and discussions below describe
71. ends unit in for evaluation b If no defect is found Customer will be charged the equivalent of 100 USD plus freight charges duties and taxes as applicable A new purchase order will be required c If unit is repaired charge to Customer will be 30 of current list price USD plus freight charges duties and taxes as applicable A new purchase order will be required or authorization to use the purchase order submitted for evaluation fee The following is a list of non repairable units 3150 All 3750 3600 All 3700 3170 All 3250 1560 Can be repaired only if defect is the power supply 1550 Can be repaired only if defect is the power supply 3350 3300 1500 All O 000 00 00 0 0 0 7 2 4 Purchasing Warranty Extension a ProSoft s standard warranty period is three 3 years from the date of shipment as detailed in Limited Warranty page 90 The Warranty Period may be extended at the time of equipment purchase for an additional charge as follows e Additional 1 year 10 of list price e Additional 2 years 20 of list price e Additional 3 years 30 of list price ProSoft Technology Inc Page 89 of 96 July 23 2008 MVI56 MBP ControlLogix Platform Support Service amp Warranty Modbus Plus Communication Module 7 3 LIMITED WARRANTY This Limited Warranty Warranty governs all sales of hardware software and other products collectively Product manufactured and or offered for sale by
72. er describes how to install and configure the module to work with your application The configuration process consists of the following steps 1 Use RSLogix 5000 to identify the module to the processor and add the module to a project Note The RSLogix 5000 software must be in offline mode to add the module to a project 2 Modify the example ladder logic to meet the needs of your application and copy the ladder logic to the processor Example ladder logic files are provided on the CD ROM Note If you are installing this module in an existing application you can copy the necessary elements from the example ladder logic into your application The rest of this chapter describes these steps in more detail The first step in setting up the module is to define the module to the system Right click the mouse button on the I O Configuration option in the Controller Organization window to display a pop up menu Select the New Module option from the I O Configuration menu a Controller CIP Sample A Controller Tags Z3 Controller Fault Handler Power Up Handler Tasks H E MainTask Z3 Unscheduled Programs 5 6 Motion Groups GI Ungrouped Axes H E Trends E1 3 Data Types 4 4 User Defined H Cs Strings H E Predefined H E Module Defined um o Ct c ProSoft Technology Inc Page 17 of 96 July 23 2008 MVI56 MBP ControlLogix Platform Modbus Plus Communication Module This action opens the following dialog b
73. er for the 7178 128 to 143 Event Commands 129 to 144 command to execute again 7179 144 to 159 Event Commands 145 to 160 This data is transferred continuously to the module in 7180 160 to 175 Event Commands 161 to 176 the module s output image 7181 176 to 191 Event Commands 177 to 192 7182 192 to 199 Event Commands 193 to 200 There is a one to one relationship between each bit in the table and a command in the Master Command List based on the bit position in the table The following table details this relationship Bit Position Name Event Commands 1 Event Commands 2 Event Commands 3 Event Commands 4 Event Commands 5 OR QINI IO Event Commands 6 199 Event Commands 200 Execution status can be monitored in the same fashion as other commands in the Master Command List via the Master Command Status block Successful Execution If the command was successful Status Code 0x01 the status will be maintained as long as the Event Command bit is set After the enable bit is cleared the Status Code field will go to zero 0 ProSoft Technology Inc July 23 2008 Page 65 of 96 MVI56 MBP ControlLogix Platform Reference Modbus Plus Communication Module Global Data In Mode When the Global Data In mode is operational the MVI56 MBP module is receiving Global Input data from up to 64 other nodes on the Modbus Plus network Each node is capable of transferring u
74. error codes returned to ladder logic on a per command basis 6 1 3 General Specifications Single Slot 1756 backplane compatible Local or remote rack The module is recognized as an Input Output module and has access to processor memory for data transfer between processor and module Ladder Logic is used for data transfer between module and processor Configuration data obtained through user defined ladder Sample ladder file included Page 48 of 96 ProSoft Technology Inc July 23 2008 Reference 6 2 MVI56 MBP ControlLogix Platform Modbus Plus Communication Module 6 1 4 Hardware Specifications Specification Description Backplane Current Load 800 mA 5 V DC 3mA 24V DC Operating Temperature 0 to 60 C 32 to 140 F Storage Temperature 40 to 85 C 40 to 185 F Shock 30g Operational 50g non operational Vibration 5 g from 10 to 150 Hz Relative Humidity 5 to 95 non condensing LED Indicators Module Status Backplane Transfer Status Application Status Serial Activity Debug Configuration port CFG CFG Port CFG RJ45 DB 9M with supplied cable RS 232 only Application ports PRT1 amp PRT2 Modbus Plus ports Dual DB9 Application ports for redundant operation Shipped with Unit 6 foot RS 232 configuration cable Functional Overview This section provides an overview of how the MVI56 MBP module transfers data using the MBP
75. es the highest update frequency on the Modbus Plus Network The second set of user data is the read and write data transferred between the processor and the module as pages of data up to 200 words long ReadData INT EO0 Decimal Data read from module WriteD ata INT 600 Decimal Data to write to module The read data ReadData is an array set to match the value entered in the ReadRegCnt parameter of the MBPModule object For ease of use this array should be dimensioned as even increment of 200 words This data is paged up to 200 words at a time from the module to the processor The ReadData task places the data received into the proper position in the read data array Use this data for status and control in the ladder logic of the processor The write data WriteData is an array set to match the value entered in the WriteRegCnt parameter of the MBPModule object For ease of use this array should be dimensioned as even increment of 200 words This data is paged up to 200 words at a time from the processor to the module The WriteData task places the write data into the output image for transfer to the module This data is passed from the processor to the module for status and control information for use in other nodes on the network 3 2 5 Command Control Object This object contains the current states of the event command control bits Each command in the command list has an associated event bit in this object
76. fit your application If you are not using the ladder example copy the ladder logic shown in the Controller Organization window below to your application Controller CIP Sample gt Controller Tags E Controller Fault Handler Ei 3 PowerUp Handler 3 48 StartUp A Program Tags E PowerUp 5 Tasks fa MainT ask MainProgram A Program Tags E MainRoutine E ReadData E writeData A J Unscheduled Programs x The module is now set up and ready to be used with your application Insert the module in the rack and attach the Modbus Plus cable Download the new application to the controller and place the processor in run mode If all the configuration parameters are set correctly and the module is attached to a Modbus Plus network the module s Application LED APP LED should blink six times per second Refer to the Diagnostics and Trouble Shooting section if you encounter errors Attach a computer or terminal to Port 1 on the module and check the status of the module using the resident debugger in the module Refer to the Diagnostics and Troubleshooting section for a complete discussion of the use of this feature 3 1 Module Configuration In order for the MVI56 MBP module to function in any of its possible modes a minimum amount of configuration data must be transferred to the module The following table provides an overview of the different types of configuration data that the module will require depend
77. hooting MVI56 MBP ControlLogix Platform Modbus Plus Communication Module Viewing the Event Command Enable List Press X to view the Event Command Enable List Use this command to display the status of each of the event command enable bits received from the ControlLogix processor SDspsssssescss LEE IC EE 222253552223 SUS ONUS CU SS CUOCUCO US EJ mronocucnccnzez mmomccomomomzm m Iz mmm mmmmmmemmm mir SEJESTE m EzZanXamcomomezeoes 2 Pxa amp xmumSmSSSES kd TIDLLDLDORLIELS TRENDS NUS CO ER DOE SO UST USE d ar zomocmomomezuu S28 Xin Co Ea SO E SO S X ia BEDES E If the event command bit is set a value of 1 will be displayed A value of 0 indicates the command event bit is clear Each bit in the table corresponds to an associated command in the master command table The bits displayed are shown with the high bits in the word on the left side and the least significant bit on the right side Therefore bit 15 command 16 is the first bit displayed in the upper right of the list and bit 0 command 1 is the last bit of the first row of data Transferring Module Confiquration to the Processor Press Y to transfer the module s configuration data to the processor Ladder logic is required in the processor to receive and implement the updated configuration You will be prompted to confirm the transfer If the operation is not successful an error code will be returned Code Description 0
78. hrough the module s Configuration Debug port Write Block These blocks of data are used to transfer information from the ControlLogix processor to the module The structure of the output image used to transfer this data is shown below Offset Description Length 0 Write Block ID 1 1 to 200 Write Data 200 201 to 213 Command Event Enable Bits 13 214 to 215 Spare 2 216 to 247 Global Output Data 32 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 In addition to the user data the block also contains the command event enable bits and the global output data This last set of data is transferred with each new block of data and is used for high speed data movement Configuration Data Transfer When the module performs a restart operation it will request configuration information from the ControlLogix processor This data is transferred to the module in specially formatted write blocks output image The module will poll for each block by setting the required write block number in a read block input image The format of the blocks for configuration is given in the following sections Module Configuration Data This block sends general configuration information from the processor to the module The data is transferred in a block with an identification code of 9000 The struct
79. ing on the operating modes to be supported Module Functional Name Description Register Modes Address Affected 4370 to Global In General Module This section of the configuration data contains the 4409 Global Out Configuration generic module configuration data and must be Slave configured for the module to operate Master 4410 to Global In Input File Map If the module s Input File is to be used to transfer 4449 data from the module to the processor then this section of configuration data must be set up 4450 to Global In Device Definition If the module s Global Input or Master Mode 5089 Master functionality is to be used then this section of configuration data must be set up 5090 to Master Master Command If the module s Master Mode functionality is to be 7089 List used then he Master Command List must be set up Important Note The module will not function correctly until the Module Configuration Data is received from the processor with at least the Local Modbus Plus Node Address set to a valid value ProSoft Technology Inc Page 21 of 96 July 23 2008 MVI56 MBP ControlLogix Platform Installing and Configuring the Module Modbus Plus Communication Module The MVI56 MBP module must be configured at least once when the card is first powered and any time thereafter when the parameters must be changed 3 2 Module Data Object All data related to the MVI56 MBP is stored in a user defined data type An instance of the data type is required b
80. ing point format A ASCII Display Displays data in text format Se de se de de se de de LE L Goes up one level to main menu 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 configuration ProSoft Technology Inc July 23 2008 Page 41 of 96 MVI56 MBP ControlLogix Platform Diagnostics and Troubleshooting Modbus Plus Communication Module Displaying the Current Page of Registers Again DATABASE DISPLAY TO 99 lt DECIMAL gt 164 i i 182 4 11 12 13 14 Cacmc m cc mm mom mmmommem Cam cm coc memo mmmmcemumuao mmm cmm 5 5 a a a a g g a a This screen displays the current page of 100 registers in the database Moving Back Through 5 Pages of Registers Press from the Database View menu to skip back to the previous 500 registers of data Viewing the Previous 100 Registers of Data Press P from the Database View menu to display the previous 100 registers of data Skipping 500 Registers of Data Hold down Shift and press to skip forward to the next 500 registers of data Viewing the Next 100 Registers of Data Press N from the Database View menu to select and display the next 100 registers of data
81. instruction initiates a Modbus Plus network transaction between the PLC and the module In the configuration of the command the programmer can specifically choose the destination address and the amount of data to be written to the module from the Modicon s memory The following diagram details an example configuration for a MSTR Type 1 command Page 62 of 96 ProSoft Technology Inc July 23 2008 Reference MVI56 MBP ControlLogix Platform Modbus Plus Communication Module Contents of registers in the control block qocecco 40001 1 Write instruction active 40002 0 Error code 40003 30 Length of the write USER ERE i 40004 100 register to Write to in module i gt error 40005 6 MVI56 MBP Node address to write to 40006 1 Slave Input Path for routing hse SSeS i 40007 0 Routing Address 3 MSTR iT success 40008 0 Routing Address 4 i 40009 0 Routing Address 5 LM UE REC RR 40010 Source of the data in the Modicon PLC to send to the MVI56 MBP module This instruction will write 30 words from 40010 to 40039 in the PLC to the MVI56 MBP module s database beginning at Data Register address 100 Note that the Slave Input Path value must be entered in order for the command to execute successfully Valid values are from 1 to 8 Any other values will cause the command to fail Master Driver Mode In the Master mode the MVI56 MBP module issues read or write commands to other devices on the Modbus Plus network These
82. ion program that buffers previously received data you can scroll through the acquired data to view the transactions that occurred on the Modbus Plus interface by the module 0x0001 Service Requests Press 1 to view all service request operations performed After selecting the option the screen should scroll very rapidly as these messages are trapped An example display is shown below Page 38 of 96 ProSoft Technology Inc July 23 2008 Diagnostics and Troubleshooting MVI56 MBP ControlLogix Platform Modbus Plus Communication Module 0x0002 Put Master Command to Output Path Press 2 to display master command requests sent from the module to the network Example output of this option is shown below NEP Pul Maslee Command 4 FF 2 2411 22 O 4 D G 2 O B 8910 2 BA u n 11 U 1 U 2 U 3 U 2104 5 BU 6 H 7 Bb 9S MU 617 MU 55 NEP Put Master Conmand Response 4 MBP Put Master Command 5 FF 2 24 11 D bb bw Z U bw B 3 2B un MBP Put Haster Command 6 FF 2 2411 D z UR M A 0x0004 Get Slave Command from Input Path Press 3 to display slave request messages received for the module Example output of this option is shown below ABE Get Slave Conmand 72 MBP 8 6 224 b Dp B B 3 ABE Gct Slave Conmand 472 MBP A 5 AFF 24 A A A AJA 2 A 14 3 A 4 Rn S A 08 664 465 0000 B B P BP BO G8 G8 08 8 O O O O uot ee Comnand Hesponse 4H FE 24 22 11 V Get blavc Comnand Hesponse 4H FF 24 2 11 3b RG R A
83. ious page of commands Viewing the Next 20 Commands Press to display data for the next 20 commands Viewing the Next Page of Commands Press N to display the next page of commands ProSoft Technology Inc Page 43 of 96 July 23 2008 MVI56 MBP ControlLogix Platform Diagnostics and Troubleshooting Modbus Plus Communication Module 5 2 LED Status Indicators The LEDs indicate the module s operating status as follows ProSoft Color Status Indication Module 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 APP Amber Flashing Module is functioning normally STATUS On Communication error or module malfunction Off Communication error or module malfunction 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 BATT 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 OK Green Off The card is not receiving any power and is no
84. ition should exist for each node on the network to receive global input data from and to interact with using the command list Modbus Plus Master Commands Lee 3 Data Type Enable INT Em O Disable 1 Continuous 2 E vent Command Int amp ddress INT Decimal Madule s internal address associated with the command i Pollint INT Decimal Minimum number of seconds between issuance of command 0 65535 Sec ru Count INT Decimal Number of registers associated with the command E Swap TINT Decimal Swap code used with command Iren Device INT Decimal Device index in Device Table to associate with the command rz Func INT Decimal Function code for the command m Dev ddress INT Decimal Address in device associated with the command This object defines the parameters for each command in the master command list The MBPlusModuleDef object contains an array of these objects that define the complete list The parameter CommandCnt in the MBPConfig object determines the number of elements in the array to process The definition of each parameter required for each command is given below Page 24 of 96 ProSoft Technology Inc July 23 2008 Installing and Configuring the Module MVI56 MBP ControlLogix Platform Modbus Plus Communication Module Enable This parameter is used define if the command will be executed or will be disregarded The following values are valid O Disables the command and it will not execute 12 Th
85. its 1 Protocol FulDuplex Auto Configure Use Modem Dialer Configure Dialer Ok Cancel Delete Help oox 4 Click the Auto Configure button RSLinx will attempt to configure your serial port to work with the selected driver 5 When you see the message Auto Configuration Successful click the OK button to dismiss the dialog box Note If the auto configuration procedure fails verify that the cables are connected correctly between the processor and the serial port on your computer and then try again If you are still unable to auto configure the port refer to your RSLinx documentation for further troubleshooting steps 2 7 Connect your PC to the Module With the module securely mounted connect your PC to the Configuration Debug port using the RJ45 DB 9 Serial Adapter Cable and the Null Modem Cable included in the package with the MVI56 MBP module 1 Connect the RJ45 DB 9 Serial Adapter Cable to the Null Modem Cable 2 Insert the RJ45 cable connector from the RJ45 DB 9 cable into the Configuration Debug port of the module 3 Attach the other end to the serial port on your PC or laptop Page 16 of 96 ProSoft Technology Inc July 23 2008 Installing and Configuring the Module MVI56 MBP ControlLogix Platform Modbus Plus Communication Module 3 Installing and Configuring the Module In This Chapter Module Configuration seee mnn 21 Module Data Object 22 This chapt
86. its for commands 48 to 63 7174 47175 Event Control Word 4 Event control bits for commands 64 to 79 7175 47176 Event Control Word 5 Event control bits for commands 80 to 95 7176 47177 Event Control Word 6 Event control bits for commands 96 to 111 7177 47178 Event Control Word 7 Event control bits for commands 112 to 127 7178 47179 Event Control Word 48 Event control bits for commands 128 to 143 7179 47180 Event Control Word 9 Event control bits for commands 144 to 159 7180 47181 Event Control Word 10 Event control bits for commands 160 to 175 7181 47182 Event Control Word 11 Event control bits for commands 176 to 191 7182 47183 Event Control Word 12 Event control bits for commands 192 to 199 7183 47184 Event Done Word 0 Event done bits for commands 0 to 15 7184 47185 Event Done Word 1 Event done bits for commands 16 to 31 7185 47186 Event Done Word 2 Event done bits for commands 32 to 47 7186 47187 Event Done Word 3 Event done bits for commands 48 to 63 7187 47188 Event Done Word 4 Event done bits for commands 64 to 79 7188 47189 Event Done Word 5 Event done bits for commands 80 to 95 7189 47190 Event Done Word 6 Event done bits for commands 96 to 111 7190 47191 Event Done Word 7 Event done bits for commands 112 to 127 7191 47192 Event Done Word 8 Event done bits for commands 128 to 143 7192 47193 Event Done Word 9 Event done bits for commands 144 to 159 7193 47194 Event Done Word 10 Event done bits for commands 160 to 175 7194 47195
87. ken Rotation Time CFail SINT Decimal Communication Failed Error Counter CRetry SINT Decimal Communication Retry Counter NoResp SINT Decimal No 3esponse Received Error Counter GoodRec SINT Decimal Good Received Packet Success Counter PathErr SINT Decimal Unexpected Path Error Counter ExRec SINT Decimal Exception Response Received Error Counter OPath1 SINT Decimal Data master output path 1 counter OPath2 SINT Decimal Dats master output path 2 counter OPath3 SINT Decimal Data master output path 3 counter OPath4 SINT Decimal Dats master output path 4 counter OPath5 SINT Decimal Dats master output path 5 counter OPath6 SINT Decimal Dats master output path 6 counter OPath SINT Decimal Data master output path 7 counter Path8 SINT Decimal Data master output path 8 counter IPath1 SINT Decimal Dats Slave input counter path 1 IPath2 SINT Decimal Data Slave input counter path 2 IPath3 SINT Decimal Data Slave input counter path 3 IPath4 SINT Decimal Data Slave input counter path 4 IPath5 SINT Decimal Data Slave input counter path 5 IPath6 SINT Decimal Dats Slave input counter path 6 IPath SINT Decimal Data Slave input counter path 7 IPath8 SINT Decimal Data Slave input counter path 8 In addition to the MBPInStat data the module provides more detailed and complete status information in the MBPStat object The structure of the object is displayed below Refer to Database Definition for a complete listing of the data
88. l Input words to accept from device Globalln ddress INT Decimal Module s database address where Global Input data stored This object defines the parameters for each node to be considered on the network by the module The route address entered in the Route1 to Route5 parameters correspond to the route a message must take to reach its final destination These values will be entered directly into the Modbus Plus route portion of each message to the device The route list will be processed until a value of zero is reached in the list For example to reach node 7 on the local segment enter a value of 7 for Route1 and 0 for Route2 to Routed The GloballnLen parameter defines how many words of global input data the module will be expecting from the device If less data is returned than expected an error code is returned for the device in the status table and the data is rejected If more data is received than expected the first GloballnLen words will be accepted and no error condition will be reported The GloballnAddress parameter defines the location in the module s internal database where the input data will be placed Valid entry for this parameter is O to 3999 An array of these objects is defined in the MBPlusModuleDef object to hold multiple device definitions for the module The index of each device in the array is used in the master port command definitions to define the destination for the command Therefore a device defin
89. lement DB Address Description 0 4300 Global In Update Counter Device 1 1 4301 Global In Update Counter Device 2 2 4302 Global In Update Counter Device 3 3 4303 Global In Update Counter Device 4 4 4304 Global In Update Counter Device 5 5 4305 Global In Update Counter Device 6 6 4306 Global In Update Counter Device 7 7 4307 Global In Update Counter Device 8 8 4308 Global In Update Counter Device 9 9 4309 Global In Update Counter Device 110 10 4310 Global In Update Counter Device 11 60 4360 Global In Update Counter Device 61 ProSoft Technology Inc July 23 2008 Page 77 of 96 MVI56 MBP ControlLogix Platform Modbus Plus Communication Module Reference Element DB Address Description 61 4361 Global In Update Counter Device 62 62 4362 Global In Update Counter Device 63 63 4363 Global In Update Counter Device 64 64 4364 Spare 65 4365 Spare 66 4366 Spare 67 4367 Spare 68 4368 Spare 69 4369 Spare 6 6 3 Configuration Data This section contains listings of the MVI56 MBP module s database that is related to the module s configuration This data is available to any node on the network General Configuration DB Address Modbus Address Parameter Description 4370 44371 Module This register controls the module from a remote device The Command Word value placed in the register will be processed and then set to zero after the fu
90. logy Inc July 23 2008 Installing and Configuring the Module MVI56 MBP ControlLogix Platform Modbus Plus Communication Module Fill in the dialog boxes as shown adjusting the Name Description and Slot options for your application You must select the Comm Format as Data INT in the dialog box Failure to set the Assembly Instance and Size values correctly will result in a module that will not communicate over the backplane of the ControlLogix rack Click Next to display the next dialog box Module Properties Local 1 1756 MODULE 1 1 x Requested Packet Interval RPI 502 ms 0 2 750 0 ms Inhibit Module Major Fault On Controller If Connection Fails While in Run Mode Module Fault Cancel lt Back Next gt Help Select the Request Packet Interval value for scanning the I O on the module This value represents the minimum frequency the module will handle scheduled events This value should not be set to less than 5 milliseconds Values between 5 0 and 10 0 milliseconds should work with most applications After completing the module setup the Controller Organization window will display the module s presence The data required for the module will be defined to the application and objects will be allocated in the Controller Tags data area An example of the Controller Organization window is shown below E Controller CIP_Sample I Controller Tags ER Controller Fault Handler H E Power Up Handler C3 Tasks Eg Mai
91. ly divisible by 200 special handling of the last block of data must developed as it must transfer fewer than 200 words It is recommended that the count values always be set to values evenly divisible by 200 The BPFail parameter determines if the module should continue communicating on the Modbus Plus network when the backplane transfer operation fails A value of zero indicates that the module should continue communicating when the backplane is not operational If the value is greater than zero the backplane will be retried the entered number of times before a failure will be reported and communication will cease on the Modbus Plus network When backplane communication is restored the module will start communicating on the network For example if you enter a value of 10 for the parameter the module will stop all Modbus Plus communications if 10 successive backplane errors are recognized When a successful transfer is recognized the module will resume communications on the network Modbus Plus Parameters desde ata Type LocalNode NT ES i 64 Network address for the module GlobalOutlen INT Decimal 0 32 number of output words from PLC to DB EN GlobalOutUpdate INT Decimal 0 55535 mSec update delay time InputFileLen NT Decimal 0 32 number of input words from DB to PLC InputFileUpdate INT Decimal 0 655535 mSec update delay time amp GloballnTimeout INT Decimal 0 655535 mSec receive timeout E Node
92. n 74 Event Command Control 64 Exiting the Program 37 F Fatal Crash Codes 76 Features and Benefits 47 Functional Overview 7 49 Functional Specifications 48 G General Concepts 49 General Configuration 78 General Specifications 48 Global Data In Mode 66 Global Data Out Mode 60 Global In File Map 80 Global In Image 84 Global In Update Counters 77 Global In Update Status 73 Global Out Image 84 Global Out Update Status 77 Global Output Data 83 Guide to the MVI56 MBP User Manual 7 H Hardware Specifications 49 How to Contact Us Technical Support 87 88 Input File Data 84 Input File Map 23 Install the Module in the Rack 11 Installing and Configuring the Module 17 Intellectual Property Indemnity 91 Interface Crash Codes 76 K Keystrokes 33 L Ladder Logic 29 LED Status Indicators 7 44 ProSoft Technology Inc July 23 2008 Page 95 of 96 MVI56 MBP ControlLogix Platform Modbus Plus Communication Module Limitation of Remedies 92 LIMITED WARRANTY 89 90 Main Logic Loop 50 Main Menu 34 Master Command Error List Menu 43 Master Command List 64 82 Master Command Status 74 Master Driver Mode 63 MBP User Cmd 25 Miscellaneous Module Status 75 Modbus Plus Connections 70 Modbus Plus Master Commands 24 Modbus Plus Parameters 23 Module Configuration 21 Module Data Object 22 Module Memory M
93. n the PC page 68 3 Verify that your communication software is using the correct settings for baud rate parity and handshaking 4 On computers with more than one serial port verify that your communication program is connected to the same port that is connected to the module If you are still not able to establish a connection you can contact ProSoft Technology Technical Support for further assistance Navigation All of the sub menus for this module contain commands to redisplay the menu or return to the previous menu You can always return from a sub menu 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 Menu B Child Sub Menu 1 Child Menu C Child Sub Menu 1 Child Sub Menu 2 Child Sub Menu 1 Child Sub Menu 2 Child Sub Menu 3 The remainder of this section shows you the menus available for this module and briefly discusses the commands available to you Keystrokes The keyboard commands on these menus are almost always non case sensitive You can enter most commands in lower case or capital 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 F
94. nTask E1 E MainProgram A Program Tags Ed MainRoutine B ReadData B WriteData E Unscheduled Programs E1 3 Motion Groups FH Ungrouped Axes FH Trends J Data Types H E User Defined Cg Strings m E Predefined Module Defined R AB 1756_MODULE C 0 R AB 1756_MODULE_INT_248Bytes 0 0 ll AB 1756_MODULE_INT_496Bytes 0 0 i AB 1756_MODULE_INT_S00Bytes 1 0 amp 1 0 Configuration BJ 1 1756 MODULE MBP 1 ProSoft Technology Inc Page 19 of 96 July 23 2008 MVI56 MBP ControlLogix Platform Installing and Configuring the Module Modbus Plus Communication Module The next step in the module s setup is to define the User Defined Data Types to be used with the module Copy these data types from the example ladder logic if you are not using the example They will be defined if you are starting from the example ladder logic The Controller Organization window should display the User Defined Data Types shown below B Controller CIP Sample A Controller Tags Z3 Controller Fault Handler H E Power Up Handler E3 Tasks B fa MainTask Bg amp MainProgram E Program Tags En MainRoutine B ReadData B writeData Z3 Unscheduled Programs 1 3 Motion Groups EH Ungrouped Axes Trends x Data Types Ej 8g User Defined R MBPCmd MBPConfig MBPDeviceDef MBPInputFileMap MBPInStat MBPlusBackplane MBPlusModuleDef MBPModule g MBPStat f MBPUsercmd Ej ER Strings E Predefined fg Module Defin
95. nction requested has been performed The following function codes are currently supported 9997 transfer module configuration to processor 9998 warm boot module and 9999 cold boot module 4371 44372 Local Modbus This value defines the Modbus Plus Node Address for the Plus Node module A valid node address must be entered for the module Address 1 to 64 to operate and the address must be unique on the network Valid values are between 1 and 64 inclusive 4372 44373 Global Output File This value defines the number of Global Output words to be Length 0 or1to placed on the Modbus Plus network If the value is set to 0 no 32 global output data will be placed on the network Values of 1 to 32 represent the number of words to be used by the module This data must be transferred from the processor to the module 4373 44374 Global Out This parameter determines the frequency of update of the Update Timing Global Output Data from the processor to the Modbus Plus Chipset This value should be set to zero to provide the fastest possible update of this data from the processor to the network Valid values for this parameter are 0 to 65535 milliseconds 4374 44375 Input File Length This value defines the number of words to be transferred by 0 or 1 to 32 the module to the processor in the In File section of the input image Valid values for this parameter are 0 to 32 For most applications a value of 32 is used 4375 44376 Input File Update This parameter is
96. ng 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 7 3 4 Intellectual Property Indemnity Buyer shall indemnify and hold harmless ProSoft and its employees from and against all liabilities losses claims costs and expenses including attorney s fees and expenses related to any claim investigation litigation or proceeding whether or not ProSoft is a party which arises or is alleged to arise from Buyer s acts or omissions under these Terms or in any way with respect to the Products Without limiting the foregoing Buyer at its own expense shall indemnify and hold harmless ProSoft and defend or settle any action brought against such Companies to the extent based on a claim that any Product made to Buyer specifications infringed intellectual property rights of another party ProSoft makes no warranty that the product is or will be delivered free of any person s claiming of patent trademark or similar infringement The Buyer assumes all risks including the risk of suit that the product or any use of the product will
97. ny defect in material or workmanship of the Product with either new or used replacement parts Such repair including both parts and labor will be performed at ProSoft s expense All warranty service will be performed at service centers designated by ProSoft 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 7 3 2 What Is Not Covered By This Warranty a ProSoft makes no representation or warranty expressed or implied that the operation of software purchased from 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 Page 90 of 96 ProSoft Technology Inc July 23 2008 Support Service amp Warranty MVI56 MBP ControlLogix Platform Modbus Plus Communication Module 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
98. obal Data Out Mode When the MVI56 MBP module s Global Output capability is enabled up to 32 words of data can be transferred onto the Modbus Plus network by the module This data typically reserved for high speed data such as for application control data is transmitted each time the module receives the network token The number of words transferred to the Modbus Plus network is user determined through the Module Configuration Block The following flow chart and associated table describe the flow of data into and out of the module i Processor Memory Backplane Interface MBP Module i lk Database Modbus Controller Tags Step Description 1 The Global Output driver reads configuration data from the ControlLogix processor This data consists of the number of words to be transmitted by the module each time the module has the token In addition timing data on the update rate for the Global Out transmission is also obtained from the configuration data 2 The Global Out data image is updated from the processor through the module s output image Based on the update rate configured by the user the Global Out image in the Modbus Plus chipset will also be updated 3 The Global Output driver in the Modbus Plus chipset will transmit the Global Out data each time the token is received by the module 4 The Global Output driver status is updated in the module s database Page 60 of 96 ProSoft Technology Inc July
99. ogy Inc July 23 2008 Diagnostics and Troubleshooting MVI56 MBP ControlLogix Platform Modbus Plus Communication Module Viewing Module Configuration Press C to view the Module Configuration screen Use this command to display the current configuration and statistics for the module Database View Menu Press D from the Main Menu to open the Database View menu Use this menu command to view the current contents of the module s database Press to view a list of commands available on this menu M Main Menu D Database Menu Display Menu gt Redisplays reteshes this menu L 0 3 Pages D to 3000 p Selects page 0 1000 2000 or 3000 J z gt z Show Again E Redisplays last selected page ofdata Goes back five pages of data Goes back one page of data Goes forward five pages ofdata Goes forward one page ofdata Displays data in decimal format Back 5 Pages T P Previous Page Skip 5 Pages 3L N Next Page D Decimal Display AE Xp H Hexadecimal Display Displays data in hex format F Float Display FEE Displays data in floating point format Displays data in text format Goes up one level to main menu A ASCII Display M Main Menu be op Viewing Global In Data Press G to view Global Input Status and Counter data for each Modbus Plus Node defined in the Device Definition Table
100. ome of these command keys are not listed on the menu but are active nevertheless Please be careful when pressing keys so that you do not accidentally execute an unwanted command Opening the Data Analyzer Menu Press A to open the Data Analyzer Menu Use this command to view all bytes of data transferred on each port Both the transmitted and received data bytes are displayed Refer to Data Analyzer for more information about this menu Important When in analyzer mode program execution will slow down Only use this tool during a troubleshooting session Before disconnecting from the Config Debug port please be sure to press M to return to the main menu and disable the data analyzer This action will allow the module to resume its normal operating mode 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 34 of 96 ProSoft Technol
101. ommunications on this port is shown in the following diagram RS 232 Config Debug Port Cable DB 9 Male Config Debug Port Ro 2 J vo to 3 ro com s cow 6 3 1 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 RSWho Page 68 of 96 ProSoft Technology Inc July 23 2008 Reference MVI56 MBP ControlLogix Platform Modbus Plus Communication Module 2 Make sure that you are not actively browsing using the driver that you wish to stop The following shows an actively browsed network 3 loxi Browsing node 10 found IV Autobrowse 83 Workstation PSFT VAIO 1 E a Linx Gateways Ethernet se AB DF1 1 DH 485 H 3 01 SLC 5 05 UNTITLED DF1 COM1 UNTITLED 10 Workstation DF1 COM1 3 Notice how the DF 1 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 screen should look like this Not Browsing IV Autobrowse Hefresh LE Workstation PSFT VAIO 1 wm Linx Ga
102. onal 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 7 3 5 Disclaimer of all Other Warranties The Warranty set forth in What Is Covered By This Warranty page 90 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 7 3 6 Limitation of Remedies In no event will ProSoft or its Dealer be liable for any special incidental or consequential damages based on breach of warranty breach of contract negligence strict tort or any other legal theory Damages that ProSoft or its Dealer will not be responsible for included but are not limited to Loss of profits loss of savings or revenue loss of use of the product or any associated equipment loss of data cost of capital cost of any substitute equipment facilities or services downtime the claims of third parties including customers of the Purchaser and injury to property Some areas do not allow time limitations on
103. or example on US English keyboards enter the command as Shift Also take care to distinguish capital letter I from lower case letter I L and number 1 likewise for capital letter O and number 0 Although these characters look nearly the same on the screen they perform different actions on the module ProSoft Technology Inc Page 33 of 96 July 23 2008 MVI56 MBP ControlLogix Platform Diagnostics and Troubleshooting Modbus Plus Communication Module 5 1 5 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 on your terminal screen B Backplane Statistics C Module Cont iguration D Dotabase View E Haster Command List Errors G Global In bata T Haxier Cun maani Tisi L Pavice Dafinition List I70 Tile Da M Morn Boot Module K Event Command Enable List Teanzfer module cfr ta processor i Gommunication ttatus Feaz Fx fk Peay rain 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 other failures Only use these commands if you are specifically directed to do so by ProSoft Technology Inc Technical Support staff S
104. ord data block that selects the module s internal data registers to transfer to the Input File The Input File Map is copied to the module during module configuration The structure of this data block is as follows Word Input File Input File Map Module Database ot o p Register Data 1 LLL 1 i 2 100 3 101 m 3 x 5 201 6 202 TA 200 202 2 405 4141 30 LLL 3 4142 a 31 4143 405 e The Input File Map acts as a data routing table NAA allowing the user to configure the source of data 3890 Configuration and for the Input File data transferred to the Ar an Status Data processor on a high priority basis 4141 4143 Each time the module enters a new read block into the input image it uses this Input File Map to select data out of the module s database and places it in the input image Any data in the module s database can be assigned to the high speed Input File data using this map Unsuccessful Execution If the command was unsuccessful Status Code gt 0x01 the status will be maintained until the command executes successfully The ladder logic must re submit the command clear the enable bit and set it again in order for the command to execute again Power Up On power up the module enters into a logical loop waiting to receive configuration data from the processor Upon receipt the module will begin execution of the command list if
105. orm Reference Modbus Plus Communication Module Module s Internal Database Structure 4000 registers for user data 9 3999 3089 words of configuration 4000 and status data 7089 0 to 32 words of high speed 7090 Output data from processor to File module 7129 0 to 32 words high speed 7130 data from module to processor 7169 7170 iS Event Control Event Data 7221 Data contained in this database is paged through the input and output images by coordination of the ControlLogix ladder logic and the MVI56 MBP module s program Up to 248 words of data can be transferred from the module to the processor at a time Up to 247 words of data can be transferred from the processor to the module Each image has a defined structure depending on the data content and the function of the data transfer as defined in the following sections Input File Normal Data Transfer Normal data transfer includes the paging of the user data found in the module s internal database in registers 0 to 3999 a portion of the status data input file data and global output data These data are transferred through read input image and write output image blocks Refer to Module Configuration for a description of the data objects used with the blocks and the ladder logic required The structure and function of each block is discussed in the following sections Read Block These blocks of data are used to transfer information from the module to the
106. ox Select Module Type x Type Major Revision 1756 MODULE fi x Description 1755 RBl 6 Channel Isolated RTD Analog Input 1756 IT 61 6 Channel Isolated Thermocouple Analog Input 1755 1 ControlLogi 5550 Programmable Controller 1 756 MO24E 2 Axis Analog Encoder Servo 1756 MODULE Generic 1756 Module 1756 0416 16 Point 74V 265V AC Output 1756 04161 16 Point 74V 265V AC Isolated Output li 1756 048 8 Point 74V 265V AC Output 1 756 048D 8 Point 74V 132V AC Diagnostic Output 1756 0A8E 8 Point 74V 132V AC Electronically Fused Output 1755 0B15D 16 Point 19 2 30 DC Diagnostic Output 1 756 OB16E 16 Point 10V 31 2V DC Electronically Fused Output Vendor All F IV Other Select All ET IV Analog IV Digital IV Communication M Motion IV Processor Clear All Cancel Help Installing and Configuring the Module Select the 1756 Module Generic 1756 Module from the list and click OK The following dialog box will be displayed Module Properties Local 1756 MODULE 1 1 x Type 1756 MODULE Generic 1756 Module Parent Local r Connection Parameters Assembly Instance Size 250 16 bit Name wee Input Description MVI56 MBP Module in Slot 1 Output 248 16 bit Configuration 4 Comm Format Data INT Status Input Slot f a Status Output 8 bit A IS Cancel Next gt Finish gt gt Finish gt gt Help Page 18 of 96 ProSoft Techno
107. p to 32 words and therefore the MVI56 MBP module is capable of accepting up to 2048 words in this manner The amount of data and from which slaves to collect it from are all user defined through the Device Definition File The following flow chart and associated table describe the flow of data into and out of the module Processor Memory Backplane Interface MBP Memory ControlLogi Processor i ere E Controller A dresses Addresses 3099 4000 jub Status 4369 ng 4370 onfsigur ratio M e a 7089 7130 47130 5 2 Input Pile input File Fie Data Map 7161 ana Y Step Description The Global In driver reads configuration data from the processor This data includes the Device Definition File that includes the node address data the number of Global In words and where to put this data in the module s internal database During the configuration process the Input File Map is updated out of the configuration file The Input File Map informs the module which data registers in the internal database to feed into the module s input image This operational mode is independent of the Global In mode but is commonly used to transfer global input data from other nodes directly to the processor The Global In Driver monitors Global In data from other nodes on the network If the data matches one of the node addresses in the Device Definition File and is qualified in terms of length etc the data is a
108. present ProSoft Technology Inc Page 67 of 96 July 23 2008 MVI56 MBP ControlLogix Platform Reference Modbus Plus Communication Module 6 3 Changing Parameters During Operation Changing values in the configuration table can be done at any time Because the module is operating using the live data in the internal database any changes made to the database will become immediately active This permits remote programming of the module by any node on the Modbus Plus network Care must be taken when altering the parameters in an order that will not disturb any running processes New configuration data can be downloaded from the database to the ControlLogix processor by executing a write command with a value of 9997 to register 4370 in the module s internal database To force the module to perform a warm boot or cold boot operation write to register 4370 with values of 9998 and 9999 respectively The only parameters that must be set through a restart of the module are related to the read and write data sizes and registers for data transfer These parameters cannot be changed while the module is operating as it could place the module in an inoperable mode 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 PC based terminal emulation program to view configuration and status data in the module and to control the module The cable for c
109. rm Modbus Plus Communication Module 5 3 Clearing a Fault Condition Typically if the OK LED on the front of the module becomes illuminated red for more than ten seconds a hardware problem has been detected in the module or the program has exited To attempt to clear the condition 1 Remove the card from the rack and re insert the card in the rack 2 Verify the configuration data being transferred to the module from the ControlLogix processor If the module s OK LED does not turn green make sure the module is inserted completely into the rack If this does not cure the problem contact ProSoft Technology Inc Support 5 4 Troubleshooting Use the following troubleshooting steps if you encounter problems when the module is powered up If these steps do not resolve your problem please contact ProSoft Technology Technical Support Processor Errors Problem Description Steps to take Processor Fault Verify that the module is plugged into the slot that has been configured for the module Verify that the slot in the rack configuration has been set up correctly in the ladder logic Processor I O LED This indicates a problem with backplane communications Verify that all flashes modules in the rack are configured in the ladder logic Module Errors Problem Description Steps to take BP ACT LED remains This indicates that backplane transfer operations are failing Connect to off or blinks slowly the module s Configuration Deb
110. rom the processor Ladder logic must handle each and every one of the data transfers The structure of each block is shown in the following table Offset Description Length 0 6000 to 6007 1 1to 8 Command Definition 8 9 to 16 Command Definition 8 17 to 24 Command Definition 8 25 to 32 Command Definition 8 33 to 40 Command Definition 8 41 to 48 Command Definition 8 Page 54 of 96 ProSoft Technology Inc July 23 2008 Reference MVI56 MBP ControlLogix Platform Modbus Plus Communication Module Offset Description Length 49 to 86 Command Definition 8 57 to 64 Command Definition 8 65 to 72 Command Definition 8 73 to 80 Command Definition 8 81 to 88 Command Definition 8 89 to 96 Command Definition 8 97 to 104 Command Definition 8 105 to 112 Command Definition 8 121 to 128 Command Definition 8 129 to 136 Command Definition 8 137 to 144 Command Definition 8 145 to 152 Command Definition 8 153 to 160 Command Definition 8 161 to 168 Command Definition 8 169 to 176 Command Definition 8 177 to 184 Command Definition 8 185 to 192 Command Definition 8 193 to 200 Command Definition 8 Status Blocks Status blocks are used to send status data from the module to the processor This data can be used to determine the health of the module and the Modbus Plus network These data are transferred from the module to the processor approximately every second T
111. s Communication parameters Config port only o Baud 57 600 fixed o Parity none fixed o Stop 1 fixed Modbus Plus ports o Memory usage is user definable o Support for the storage and transfer of up to 4 000 registers across the backplane 100 word reads and writes max allowed Supports all five levels of Modbus Plus routing Software configurable parameters Node address 1 to 64 Global out size 0 to 32 words Global in size 0 to 32 words Module data transfer 0 to 4 000 words o Master command count 0 to 100 commands Function codes accepted as a Slave 1 2 3 4 5 6 15 16 Function codes transmitted as a Master 3 16 O 000 0 0 Global Data Specifications The MBP module actively exchanges global in 32 words max per node and global out 32 words max data on the Modbus Plus network Priority is given to these data types to provide a high speed mechanism for the transfer of control data Modbus Slave Mode Specifications Supports broadcast commands from host Communication error codes returned to ladder logic Modbus Master Mode Specifications Command list support of up to 100 commands Conditional and continuous command list polling Each command list entry is fully configurable for function register to from addressing and word bit count word and byte swap Event driven bit and register write commands ladder logic controlled Supports sending of broadcast commands Communication status
112. s the number of Master Data Paths that will Data Paths be made available to the module s Master Mode Driver by the Maximum Modbus Plus Chipset Valid values for this parameter are 1 to 8 A value of zero will result in the default value of 8 4383 44384 Master Command This parameter defines the number of milliseconds 0 to Timeout Preset 65535 to wait for a response to a master command issued by the module on the network If a timeout condition exists for a command it will be reflected in the Master Command List Status data area A value of 0 will result in a value of 1000 1 second for the parameter 4384 44385 Read Block Start This parameter specifies the module s start address where Register data will be read from and transferred to the processor Valid values for this parameter are 0 to 3999 This is a read only value and can only be set in the processor 4385 44386 Read Block This parameter specifies the number of registers to transfer Register Count from the module s database to the processor This is a read only value and can only be set in the processor 4386 44387 Read Block This read only value specifies the number of blocks of 200 Maximum Count word data are to be transferred from the module to the processor 4387 44388 Write Block Start This read only parameter specifies the starting register in the Register module s database where data will be transferred from the processor to the module 4388 44389 Write Block This read only parameter
113. stics and Troubleshooting page 31 This section describes how to verify communications with the network Diagnostic and Troubleshooting procedures Reference Product Specifications Functional Overview Glossary Reference page 47 Functional Overview page 49 Product Specifications page 4T These sections contain general references associated with this product Specifications and the Functional Overview Support Service and Warranty Index Support Service and Warranty page 87 This section contains Support Service and Warranty information Index of chapters ProSoft Technology Inc July 23 2008 Page 7 of 96 MVI56 MBP ControlLogix Platform Guide to the MVI56 MBP User Manual Modbus Plus Communication Module Page 8 of 96 ProSoft Technology Inc July 23 2008 Start Here MVI56 MBP ControlLogix Platform Modbus Plus Communication Module 2 Start Here In This Chapter System Requirements ssesssseeee enm enm nemen 9 3 Package Contents err rr ERHPRERERITE REESE SEER 10 Setting J mbpers erret tert rt eterne rne tri Ea EE 10 Install the Module in the Rack seem e 11 Connect your PC to the Processor ssssee ee 13 Download the Sample Program to the Processor s 14 Connect your PC to the Module sse 16 Installing the MV
114. stination Register Address Determines where data will be placed and or obtained Count Select the number of words to be transferred 1 to 100 Event Command Control Commands can be entered in the command list to operate either continuously or under ladder logic control The operating mode is selected when entering the command in the Master Command List If a command is configured as an Event Command then the module will look to the Event Command Control words received from the ControlLogix processor to determine when to execute The following describes the structure of the Control words Page 64 of 96 ProSoft Technology Inc July 23 2008 Reference MVI56 MBP ControlLogix Platform Modbus Plus Communication Module Database Bit Offset in Name Description Address Controller Tag for Event Control 7170 0 to 15 Event Commands 1 to 16 This block of data consists of 7171 16 to 31 Event Commands 17 to 32 19 words of bits that are mapped to individual 7172 32 to 47 Event Commands 33 to 48 commands in the Master 7173 48 to 63 Event Commands 49 to 64 Command List 7174 64 to 79 Event Commands 65 to 80 Setting a bit will trigger the corresponding command and 7175 80 to 95 Event Commands 81 to 96 will seta one shot bit for the 7176 96 to 111 Event Commands 97 to 112 command in the module This bit must be reset before being 7177 112 to 127 Event Commands 113 to 128 set again in ord
115. t plugged securely into the rack On The module is operating normally MBP ACT Amber 6flashes The MVI56 MBP is working normally in that it is successfully per receiving and passing the token All nodes on the link should second be flashing this pattern 1 flash This node is off line after just being powered up or after per exiting the four flashes per second mode In this state the second node monitors the network and builds a table of active nodes and token holding nodes It remains in this state for five seconds then attempts to go to its normal operating state Two The node is hearing the token being passed among other Flashes nodes but is never receiving the token Check the network for then OFF an open circuit or defective termination for two Sec Three The node is not hearing any other nodes It is periodically Flashes claiming the token but finding no other node to which to pass then OFF it Check the network for an open circuit or defective for 1 7 termination sec Four The node has heard a valid message from another node that Flashes is using the same address as this node The node remains in then OFF this state as long as it continues to hear the duplicate address for 1 4 If the duplicate address is not heard for five seconds the node sec then changes to the pattern of one flash every second Page 44 of 96 ProSoft Technology Inc July 23 2008 Diagnostics and Troubleshooting MVI56 MBP ControlLogix Platfo
116. t used 7164 47165 Spare Not used 7165 47166 Spare Not used 7166 47167 Spare Not used 7167 47168 Spare Not used Page 84 of 96 ProSoft Technology Inc July 23 2008 Reference MVI56 MBP ControlLogix Platform Modbus Plus Communication Module DB Address Modbus Address Parameter Description 7168 47169 Spare Not used 7169 47170 Spare Not used 6 6 06 Command Event Data The command event data controls the master command list If a command is set to be controlled by events then the status of the bits contained in this data set enable the command for a single instance Each bit in the event data set is associated with an individual command When the bit is set the command will be issued once The bit must be cleared and set again for the command to be issued again The first thirteen words of data area associated with the event command data set contain these control bits The remainder of the data area holds data associated with each event The following table describes the event data area Command Event Control DB Address Modbus Address Parameter Description 7170 47171 Event Control Word 40 Event control bits for commands 0 to 15 7171 47172 Event Control Word 1 Event control bits for commands 16 to 31 7172 47173 Event Control Word 2 Event control bits for commands 32 to 47 7173 47174 Event Control Word 3 Event control b
117. teways Ethernet as AB_DF1 1 DH 485 Linx AB DF1 1 Gatew DH 485 Branches are displayed or hidden by clicking on the or the icons E a AB_DF1 1 DH 485 4 When you have verified that the driver is not being browsed go to Communications gt Configure Drivers You may see something like this Configure Drivers Available Driver Types Configured Drivers Status Name and Description AB _DF1 1 DH485 Sta 10 COM1 RUNNING ProSoft Technology Inc Page 69 of 96 July 23 2008 MVI56 MBP ControlLogix Platform Reference Modbus Plus Communication Module 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 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 13 Available Driver Types I Ada Ne Configured Drivers Name and Description Status AB_DF1 1 DH485 Sta 10 COM1 STOPPED Stopped 6 Upon seeing this you may now use that 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 followed all of the above steps and it will not stop the driver
118. tform Start Here Modbus Plus Communication Module 2 6 Download the Sample Program to the Processor Note The key switch on the front of the ControlLogix module must be in the REM position To download the sample program from RSLogix 5000 to the ControlLogix processor 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 Lx Download to the controller AN Name Controller Type 1756 L55 4 17 6 M13 A4 ControlLogix5555 Controller Path AB_DF1 1 Security None A The controller is in Remote Run mode The mode will be changed to Remote Program prior to download 3 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 t Done downloading Change controller mode back to Remote Run e jw Note If you receive an error message during these steps refer to your RSLogix documentation to interpret and correct the error Page 14 of 96 ProSoft Technology Inc July 23 2008 Start Here MVI56 MBP ControlLogix
119. the Polllnt parameter and 2 The command will only execute if the event control bit for the command is set 5091 45092 Module s Database Register Number This parameter specifies the starting internal register address to be associated with the command Valid entry for this parameter is 0 to 3999 5092 45093 Polling Interval This parameter defines the minimum number of seconds to wait between the execution of continuous commands Enable 1 This poll interval command can be used to lighten the communications load on a busy network Valid entry for this parameter is 0 to 65535 5093 45094 Register Count This parameter defines the number of registers to be considered by the command Valid entry for this parameter is 1 to 100 5094 5095 45095 45096 Swap Code Device Index This parameter is not implemented in the current version of the software but will be used in the future to swap the bytes of word and double word values when floating point data is required This parameter associates the command with a device defined in the device definition table Device in the MBPlusModuleDef object The index defined in this parameter sets the route path defined for the device in the Modbus Plus message 5096 45097 Function Code This parameter specifies the function to be performed by the command Valid entries are 3 Read register data from a node and 16 Write register data to a no
120. the command 3 Presuming successful processing by the other nodes responses are received into the Master driver for processing 4 Data received from the other nodes on the network is passed into the module s internal database assuming a read command 5 Status is returned to the ControlLogix processor for each command in the Master Command List In order for the MVI56 MBP module to operate in the Master Mode actively reading writing data with other nodes on the network several user configurable parameters must be received from the ControlLogix processor The following sections describe these configuration requirements Device Definition File An entry must be made in the Device Definition File for each node on the network which is to be addressed by the module s Master Command List The entry in the Device Definition File must consist of at least the Routing Path including a valid Data Slave Input path if the device is not a Modicon PLC Master Command List In order to function in the Master Mode the module s Master Command List must be defined This list contains up to 200 individual entries with each entry containing the information required to construct a valid command This includes the following Command enable mode disabled continuous or event control Node Route Path From Device Definition File index in Device Definition File Command Type Read or Write up to 100 words per command Source and De
121. the parameters set in dialog box You can view these tables by opening the data type under the User Defined Data Type option in the Controller Organization list Data Transfer Parameters MBPModule Members Data Type Size 12 byte s Name Data Type Style Description ReadDataStartReg Decimal Start reg to transfer from module to PLC ReadD ata ReadDataRegCnt INT Decimal Number of registers from module for ReadData WriteDataStartReg INT Decimal Start reg to transfer from PLC to module WriteD ata WriteDataRegCnt INT Decimal Number of registers from PLC for WriteData 5 BPFail INT Decimal Determines module operation if BP fails continue 0 number of retries before comm shutdown This object defines the parameters for data movement between the module and the processor Values entered determine the ladder logic and data size required in the application The ReadData and WriteData arrays must be sized to or larger than the count values entered The ladder logic must process the number of blocks of data to be transferred The number of blocks is computed as follows BlockCnt INT RegCnt 200 if MOD RegCnt 200 1 0 Page 22 of 96 ProSoft Technology Inc July 23 2008 Installing and Configuring the Module MVI56 MBP ControlLogix Platform Modbus Plus Communication Module If the register count is evenly divisible by 200 the number of blocks is easy to compute and the ladder is much simpler to write If the number is not even
122. 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 6 4 Modbus Plus Connections The MVI56 MBP module has one or two physical Modbus Plus connectors depending on hardware configuration with a DB 9 Female plug located on the front of the module Modicon provides two different Modbus Plus connectors to ease installation These connectors are as follows Modicon Part Number Description AS MBKT 085 Inline Connector AS MBKT 185 Terminating Connector The actual cable installation and the wiring of the cable to the connectors is fully documented in the Modicon publication Modicon Modbus Plus Network Planning and Installation Guide Pub No GM Modbus Plus L 001 Page 70 of 96 ProSoft Technology Inc July 23 2008 Reference MVI56 MBP ControlLogix Platform Modbus Plus Communication Module If the Modicon connectors are not available during installation the following pin out applies to the DB 9 Modbus Plus port connections O Modbus Plus O Connector 1o t A o ProSoft Module AS MBKT 085 185 o i Femal s Male e 1 Signal B Female o o 2 Ground 1 Ground 2t 1 Ground s 3 Signal A 2 Signal A o 2 Signal A o 3 Signal B 3 Signal B i 6 5 DB9 to RJ45 Adaptor Cable 14 18 0 gt
123. to enable 1 2 to 61 List of command indexes 60 62 to 247 Spare 186 ProSoft Technology Inc Page 57 of 96 July 23 2008 MVI56 MBP ControlLogix Platform Modbus Plus Communication Module Write Configuration Reference This block is sent from the ControlLogix processor to the module to force the module to write its current configuration back to the processor This function is used when the module s configuration has been altered remotely using database write operations The format for the block on the write block is shown below The module will respond with blocks containing the module configuration data Ladder logic must be written to handle the receipt of these blocks The blocks transferred from the module are as follows Block 9000 General Configuration Data Offset Description Length 0 9000 1 1 9000 1 2to6 Backplane Parameters 5 7 to 16 Modbus Plus Configuration 10 17 to 48 Input File Map 32 49 to 247 Spare 200 Blocks 9100 to 9103 Device Definition Data Offset Description Length 0 9100 to 9103 1 1 9100 to 9103 1 2to9 Device Definition 8 10 to 17 Device Definition 8 18 to 25 Device Definition 8 26 to 33 Device Definition 8 34 to 41 Device Definition 8 42 to 49 Device Definition 8 50 to 57 Device Definition 8 66 to 73 Device Definition 8 74 to 81 Device Definition 8 82 to 89 Device Definition 8 90 to 94 Device Definition
124. ts for InCntr member of MBPStat object 77 Array assignments for InUpdate member of MBPStat object 73 Array assignments for Misc member of MBPStat object 75 Array assignments for MstrCmd member of MBPStat object 74 Backplane Data Transfer 50 Battery Life Advisory 3 C Changing Parameters During Operation 68 Clearing a Fault Condition 45 Command Control Blocks 56 Command Control Object 27 Command Event Control 85 Command Event Data 85 Configuration Data 78 Configuration Data Transfer 53 Configuration Objects 22 Configuring RSLinx 15 Connect your PC to the Module 16 Connect your PC to the Processor 13 Controlling Law and Severability 93 D Data Analyzer 38 Data Flow between MVI56 MBP Module and ControlLogix Processor 60 Data Transfer Parameters MBPModule 22 Database Definition 71 Database View Menu 35 41 MVI56 MBP ControlLogix Platform Modbus Plus Communication Module DB9 to RJ45 Adaptor Cable 14 71 Device Definition 24 80 Device Definition Block Format 82 Device Definition File 64 Device Definition List Menu 40 Diagnostics and Troubleshooting 7 31 Disabling the RSLinx Driver for the Com Port on the PC 33 68 Disclaimer of all Other Warranties 92 Disclaimer Regarding High Risk Activities 91 Displaying the Current Page of Registers Again 42 Download the Sample Program to the Processor 14 E Error Code Definitio
125. tware 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 force the module to read the new configuration information and to restart The structure of the control block is shown in the following table Offset Description Length 0 9998 1 1 to 249 Spare 249 Cold Boot This block is sent from the ControlLogix processor to the module output image when the module is required to perform the cold boot hardware reset operation This block is sent to the module when a hardware problem is detected by the ladder logic that requires a hardware reset The structure of the control block is shown in the following table ProSoft Technology Inc July 23 2008 Page 59 of 96 MVI56 MBP ControlLogix Platform Reference Modbus Plus Communication Module Offset Description Length 0 9999 1 1 to 249 Spare 249 6 2 2 Data Flow between MVI56 MBP Module and ControlLogix Processor The following topics describe the flow of data between the two pieces of hardware ControlLogix processor and MVI56 MBP module and other nodes on the Modbus Plus network under the module s different operating modes Note that all four modes can operate effectively simultaneously if desired Under most likely operating cases the Global Input and Global Output tasks will be operating in conjunction with either the Master or the Slave driver Gl
126. ug port to check this To establish backplane communications verify the following items The processor is in Run mode The backplane driver is loaded in the module The module is configured for read and write block data transfer The ladder logic handles all read and write block situations The module is configured in the processor OK LED remains red The program has halted or a critical error has occurred Connect to the Configuration Debug port to see if the module is running If the program has halted turn off power to the rack remove the card from the rack and re insert the card in the rack and then restore power to the rack ProSoft Technology Inc Page 45 of 96 July 23 2008 MVI56 MBP ControlLogix Platform Diagnostics and Troubleshooting Modbus Plus Communication Module Page 46 of 96 ProSoft Technology Inc July 23 2008 Reference MVI56 MBP ControlLogix Platform Modbus Plus Communication Module 6 Reference In This Chapter Product Specifications sssssssssee keen nnne 47 Functional Overview 22 cz sa i ae i Sa nad Mr nen NA 49 RS 232 Configuration Debug Port XW u u u sssseceeeeeeree renerne ennen nn enes 68 Modbus Plus Connections seseseee mee 70 DB9 to RJ45 Adaptor Cable 14 71 Database Definition ie te tee tcd eoa de s 71 6 1 Product Specifications The MVI56 Modbus Plus Communication Module allows ControlLogix I O comp
127. ure of the block is displayed in the following table ProSoft Technology Inc Page 53 of 96 July 23 2008 MVI56 MBP ControlLogix Platform Modbus Plus Communication Module Reference Offset Description Length 0 9000 1 1to5 Backplane Parameters 5 6 to 15 Modbus Plus Configuration 10 16 to 47 Input file Map 32 48 to 247 Spare 200 Device Definition Data Four blocks are used Write Block ID s of 9100 to 9103 to transfer the device definition data from the processor to the module The module will sequentially poll for each block from the processor Ladder logic must handle each and every one of the data transfers The structure of each block is shown in the following table Offset Description Length 0 9100 to 9103 1 1to 8 Device Definition 8 9 to 16 Device Definition 8 17 to 24 Device Definition 8 25 to 32 Device Definition 8 33 to 40 Device Definition 8 41 to 48 Device Definition 8 49 to 86 Device Definition 8 57 to 64 Device Definition 8 65 to 72 Device Definition 8 73 to 80 Device Definition 8 81 to 88 Device Definition 8 89 to 96 Device Definition 8 97 to 104 Device Definition 8 105 to 112 Device Definition 8 121 to 128 Device Definition 8 Master Command List Data Eight blocks are used Write Block ID s 6000 to 6007 to transfer the master command list data from the processor to the module The module will sequentially poll for each block f
128. ut data for module word 4 7121 47122 Global Out 31 Global output data for module word 31 7122 47123 Spare Not used 7123 47124 Spare Not used 7124 47125 Spare Not used 7125 47126 Spare Not used 7126 47127 Spare Not used 7127 47128 Spare Not used 7128 47129 Spare Not used 7129 47130 Spare Not used 6 6 5 Input File Data The MVI56 MBP module transfers up to 32 words of data in each new input image block sent to the processor Incoming data from each source node can be indexed into up to eight fields for delivery into separate data destinations in the receiving node Nodes configured for global input can request up to 32 words from each node up to a maximum of 500 words The data used to construct is block is determined by the Input File Map data set The data transferred to the processor is located in the module s database at registers 7130 to 7161 The following table describes the register locations for this data in the module s database Global In Image DB Address Modbus Address Parameter Description 7130 47131 In File Word 0 Data from Input File Map index 0 for word 0 7131 47132 In File Word 1 Data from Input File Map index 1 for word 1 7132 47133 In File Word 2 Data from Input File Map index 2 for word 2 7133 47134 In File Word 3 Data from Input File Map index 3 for word 3 7161 47162 In File Word 31 Data from Input File Map index 31 for word 31 7162 47163 Spare Not used 7163 47164 Spare No
129. wo separate blocks are required to send all the status data contained in the module The first block of data contains the global input status and general module status data The structure of this block is shown in the following table Offset Description Length 0 9500 1 1 Write Block ID 1 2 to 71 Global Input Status Data 70 72 to 101 Module Status Data 30 102 to 171 Global Input Counter Data 70 172 to 249 Spare 78 The second block contains the status value for each master command list entry This is a list of 200 status values each one corresponding to a master command list entry The structure of this block is shown below Offset Description Length 0 9501 1 1 Write Block ID 1 2 to 201 Command Status Data 200 201 to 249 Spare 48 ProSoft Technology Inc Page 55 of 96 July 23 2008 MVI56 MBP ControlLogix Platform Reference Modbus Plus Communication Module Command Control Blocks Command control blocks are special blocks used to request specific tasks from the module The current version of the software supports the following command control blocks user command block Command execution block command enable disable event blocks warm boot Cold boot User Command Block This block is sent from the ControlLogix processor to the module to execute up to six commands generated from the ladder logic These commands are placed in the command queue and executed at a high priorit
130. y in the module The format of the block used for this control process is shown in the following figure Offset Description Length 0 9002 1 1 Number of commands to add 1 2to 11 User Command 1 10 12 to 21 User Command 2 10 22 to 31 User Command 3 10 32 to 41 User Command 4 10 42 to 51 User Command 5 10 52 to 61 User Command 6 10 62 to 247 Spare 186 Word 1 of the block is used to set the number of commands present in the block This word should be set to a value from 1 to 6 The format of each command in the block is shown in the following figure Word Offset Parameter 0 Module s Database Register Number 1 Register Count 2 Swap Code 3 Device Index 4 Function Code 5 Register Address in Device 6 Spare 7 Spare 8 Spare 9 Spare The definition of each parameter is that given in the command list description in this manual Page 56 of 96 ProSoft Technology Inc July 23 2008 Reference MVI56 MBP ControlLogix Platform Modbus Plus Communication Module Command Execution Block This command block is used to insert commands in the command list into the module s command queue The command queue is executed at a high priority Commands that have their enable code set to zero can be executed by the module using this feature There is no response block issued by the module for this block to the ControlLogix processor The format of the block sent by the processor to the mo

MVI56-MBP User Manual

Contents

Download Pdf Manuals

Related Search

Related Contents