ProSoft Technology MVI 56-MBP communication module User Manual
Publicité
Publicité
MVI56-MBP
ControlLogix Platform
Modbus Plus Communication Module
User Manual
July 23, 2008
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 product's 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 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 40%. 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°F)
Shock: 30g Operational; 50g non-operational; Vibration: 5 g from 10 to 150 Hz
Relative Humidity 5% to 95% (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:
II 3 G 0C <=Ta<= 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® 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 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.
Modbus Plus Communication Module
Contents
ProSoft Technology, Inc.
July 23, 2008
Page 5 of 96
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
1 Guide to the MVI56-MBP User Manual
Function
Introduction
(Must Do)
→
Verify Communication,
Diagnostic and
Troubleshooting
→
Reference
Product Specifications
Functional Overview
Glossary
→
Support, Service, and
Warranty
Index
→
Section to Read Details
This Section introduces the customer to the module. Included are: package contents, system requirements, hardware installation, and basic configuration.
Verifying
Communication
Diagnostics and
Troubleshooting
Functional Overview
Product
Specifications (page
Support, Service and Warranty (page
This section describes how to verify communications with the network. Diagnostic and Troubleshooting procedures.
These sections contain general references associated with this product, Specifications, and the Functional Overview.
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
Modbus Plus Communication Module
Guide to the MVI56-MBP User Manual
Page 8 of 96 ProSoft Technology, Inc.
July 23, 2008
Start Here MVI56-MBP ♦ ControlLogix Platform
Modbus Plus Communication Module
In This Chapter
Install the Module in the Rack ............................................................... 11
Connect your PC to the Processor ........................................................ 13
Download the Sample Program to the Processor.................................. 14
Connect your PC to the Module ............................................................ 16
Installing the MVI56-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.
Caution: 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.
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® II 450 MHz minimum. Pentium III 733 MHz (or better) recommended
Supported operating systems: o o o
Microsoft Windows XP Professional with Service Pack 1 or 2
Microsoft Windows 2000 Professional with Service Pack 1, 2, or 3
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
× 768 recommended)
ProSoft Technology, Inc.
July 23, 2008
Page 9 of 96
MVI56-MBP ♦ ControlLogix Platform
Modbus Plus Communication Module
CD-ROM
HyperTerminal or other terminal emulator program.
Start Here
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.
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
1 MVI56-MBP
Module
MVI56-MBP
1 Cable Cable #15, RS232
Null Modem
1 Cable Cable #14, RJ45 to
DB9 Male Adapter
1 ProSoft
Solutions CD
Part Description
Modbus Plus Communication Module
For RS232 Connection to the CFG Port
For DB9 Connection to the CFG Port
Contains sample programs, utilities and documentation for the MVI56-MBP module.
If any of these components are missing, please contact ProSoft Technology
Support for replacement parts.
The following illustration shows the MVI56-MBP jumper configuration:
Page 10 of 96
Not used Not used
ProSoft Technology, Inc.
July 23, 2008
Start Here MVI56-MBP ♦ ControlLogix Platform
Modbus Plus Communication Module
Do not change the position of the Setup jumper unless instructed to do so by
ProSoft Technical Support.
2.4 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.
July 23, 2008
Page 11 of 96
MVI56-MBP ♦ ControlLogix Platform
Modbus Plus Communication Module
2
Align the module with the top and bottom guides, and slide it into the rack until the module is firmly against the backplane connector.
Start Here
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
2.5 Connect your PC to the Processor
MVI56-MBP ♦ ControlLogix Platform
Modbus Plus Communication Module
1
Connect the right-angle connector end of the cable to your controller at the communications port.
2
Connect the straight connector end of the cable to the serial port on your computer.
ProSoft Technology, Inc.
July 23, 2008
Page 13 of 96
MVI56-MBP ♦ ControlLogix Platform
Modbus Plus Communication Module
2.6 Download the Sample Program to the Processor
Start Here
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.
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.
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 Platform
Modbus Plus Communication Module
If RSLogix is unable to establish communication with the processor, follow these steps:
1
Open RSLinx.
2
Open the Communications menu, and choose Configure Drivers.
This action opens the Configure Drivers dialog box.
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.
July 23, 2008
Page 15 of 96
MVI56-MBP ♦ ControlLogix Platform
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.
Start Here
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
This chapter 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.
ProSoft Technology, Inc.
July 23, 2008
Page 17 of 96
MVI56-MBP ♦ ControlLogix Platform
Modbus Plus Communication Module
This action opens the following dialog box.
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.
Page 18 of 96 ProSoft Technology, 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.
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.
ProSoft Technology, Inc.
July 23, 2008
Page 19 of 96
MVI56-MBP ♦ ControlLogix Platform
Modbus Plus Communication Module
Installing and Configuring the 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:
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.
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 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.
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.
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, depending on the operating modes to be supported.
Name Description Module
Register
Address
4370 to
4409
4410 to
4449
Functional
Modes
Affected
Global In
Global Out
Slave
Master
Global In
General Module
Configuration
This section of the configuration data contains the generic module configuration data, and must be configured for the module to operate.
4450 to
5089
5090 to
7089
Global In
Master
Master
Input File Map
If the module's Input File is to be used to transfer data from the module to the processor, then this section of configuration data must be set up.
Device Definition If the module's Global Input or Master Mode functionality is to be used, then this section of configuration data must be set up.
Master Command
List
If the module's Master Mode functionality is to be 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.
July 23, 2008
Page 21 of 96
MVI56-MBP ♦ ControlLogix Platform
Modbus Plus Communication Module
Installing and Configuring the 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 before the module can be used. This is done by declaring a variable of the data type in the Controller Tags Edit Tags dialog box. The structure of the object is displayed in the figure below:
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.
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 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)
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 evenly 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
This object defines the parameters for the operation of the Modbus Plus communication driver in the module.
Input File Map
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.
July 23, 2008
Page 23 of 96
MVI56-MBP ♦ ControlLogix Platform
Modbus Plus Communication Module
Device Definition
Installing and Configuring the Module
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 Route5.
The GlobalInLen 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 GlobalInLen words will be accepted and no error condition will be reported.
The GlobalInAddress parameter defines the location in the module's internal database where the input data will be placed. Valid entry for this parameter is 0 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 definition 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
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: 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 the PollInt 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 0 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= Write register data to a node.
DevAddress
: 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.
This object sends Modbus Plus commands directly from ladder logic to the
MVI56-MBP.
ProSoft Technology, Inc.
July 23, 2008
Page 25 of 96
MVI56-MBP ♦ ControlLogix Platform
Modbus Plus Communication Module
Installing and Configuring the Module
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".
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 stored in this object.
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.
The global input data (GlobalIn) 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 requires 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.
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. 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.
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.
July 23, 2008
Page 27 of 96
MVI56-MBP ♦ ControlLogix Platform
Modbus Plus Communication Module
Installing and Configuring the Module
Page 28 of 96 ProSoft Technology, Inc.
July 23, 2008
Ladder Logic MVI56-MBP ♦ ControlLogix Platform
Modbus Plus Communication Module
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.
July 23, 2008
Page 29 of 96
MVI56-MBP ♦ ControlLogix Platform
Modbus Plus Communication Module
Ladder Logic
Page 30 of 96 ProSoft Technology, Inc.
July 23, 2008
Diagnostics and Troubleshooting MVI56-MBP ♦ ControlLogix Platform
Modbus Plus Communication Module
In This Chapter
Reading Status Data from the Module .................................................. 31
LED Indicators............................................................................ 44
Clearing a Fault Condition .....................................................................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.
5.1 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
The Configuration and Debug menu for this module is arranged as a tree structure, with the Main Menu at the top of the tree, and one or more sub-menus for each menu command. The first menu you see when you connect to the module is the Main menu.
Because this is a text-based menu system, you enter commands by typing the command letter from your computer keyboard in the 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.
July 23, 2008
Page 31 of 96
MVI56-MBP ♦ ControlLogix Platform
Modbus Plus Communication Module
Diagnostics and Troubleshooting
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.
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 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
Windows 3.1
Windows 95/98
Windows NT/2000/XP
ProComm, as well as several other terminal emulation programs
Terminal
HyperTerminal
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
Start the 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
Software Handshaking
1
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 on 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:
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. For example, on US English keyboards, enter the [?] command as [Shift][/].
Also, take care to distinguish capital letter [I] from lower case letter [l] (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.
July 23, 2008
Page 33 of 96
MVI56-MBP ♦ ControlLogix Platform
Modbus Plus Communication Module
Diagnostics and Troubleshooting
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:
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.
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 Technology, 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.
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.
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.
July 23, 2008
Page 35 of 96
MVI56-MBP ♦ ControlLogix Platform
Modbus Plus Communication Module
Diagnostics and Troubleshooting
Viewing I/O File Data
Press [O] to view the module's global input and output data.
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 [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 Troubleshooting 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.
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 Configuration 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
-1
-2
-3
Error transferring module configuration data (block -9000)
Error transferring device definition data (blocks -9100 to -9103)
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.
July 23, 2008
Page 37 of 96
MVI56-MBP ♦ ControlLogix Platform
Modbus Plus Communication Module
Diagnostics and Troubleshooting
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.
Use this 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.
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 emulation 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:
(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:
(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:
(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:
(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.
ProSoft Technology, Inc.
July 23, 2008
Page 39 of 96
MVI56-MBP ♦ ControlLogix Platform
Modbus Plus Communication Module
Diagnostics and Troubleshooting
(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.
(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.
Returning to the Main Menu
Press [M] to return to the Main 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.
MVI56-MBP ♦ ControlLogix Platform
Modbus Plus Communication Module
Returning to the Main Menu
Press [M] to return to the Main 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.
Viewing Register Pages
To view sets of register pages, use the keys described below:
Command Description
[0]
[1]
[2]
Display registers 0 to 99
Display registers 1000 to 1099
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
Modbus Plus Communication Module
Displaying the Current Page of Registers Again
Diagnostics and Troubleshooting
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.
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
Returning to the Main Menu
Press [M] to return to the Main Menu.
MVI56-MBP ♦ ControlLogix Platform
Modbus Plus Communication Module
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.
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 previous 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.
July 23, 2008
Page 43 of 96
MVI56-MBP ♦ ControlLogix Platform
Modbus Plus Communication Module
5.2 LED Status Indicators
Diagnostics and Troubleshooting
The LEDs indicate the module's operating status as follows:
ProSoft
Module
Color Status Indication
APP
STATUS
Amber
Off terminal using the Configuration/Debug port.
No data is being transferred on the Configuration/Debug port.
Flashing Module is functioning normally
On Communication error or module malfunction
BP ACT
BATT
Amber
Red
MBP ACT Amber
Two
Flashes then OFF for two sec
Three
Flashes then OFF for 1.7 sec
Four
Flashes then OFF for 1.4 sec
On
Off
Off
On 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.
On
6 flashes per second
The card is not receiving any power and is not plugged securely into the rack.
The module is operating normally.
The MVI56-MBP is working normally in that it is successfully receiving and passing the token. All nodes on the link should be flashing this pattern.
1 flash per second
The LED is on when the module is performing a write operation on the backplane.
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.
The battery voltage is OK and functioning.
This node is off-line after just being powered up, or after exiting the four flashes per second mode. In this state, the 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.
The node is hearing the token being passed among other nodes, but is never receiving the token. Check the network for an open circuit or defective termination.
The node is not hearing any other nodes. It is periodically claiming the token but finding no other node to which to pass it. Check the network for an open circuit or defective termination.
The node has heard a valid message from another node that is using the same address as this node. The node remains in this state as long as it continues to hear the duplicate address.
If the duplicate address is not heard for five seconds, the node then changes to the pattern of one flash every second.
Page 44 of 96 ProSoft Technology, Inc.
July 23, 2008
Diagnostics and Troubleshooting
5.3 Clearing a Fault Condition
MVI56-MBP ♦ ControlLogix Platform
Modbus Plus Communication Module
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 flashes
This indicates a problem with backplane communications. Verify that all modules in the rack are configured in the ladder logic.
Module Errors
Problem Description Steps to take
BP ACT LED remains off or blinks slowly
This indicates that backplane transfer operations are failing. Connect to the module's Configuration/Debug port to check this.
To establish backplane communications, verify the following items:
The processor is in Run mode.
The backplane driver is loaded in the module.
The module is configured for read and write block data transfer.
The ladder logic handles all read and write block 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.
July 23, 2008
Page 45 of 96
MVI56-MBP ♦ ControlLogix Platform
Modbus Plus Communication Module
Diagnostics and Troubleshooting
Page 46 of 96 ProSoft Technology, Inc.
July 23, 2008
Modbus Plus Communication Module
6 Reference
In This Chapter
Modbus Connections..................................................................... 70
DB9 to RJ45 Adaptor (Cable 14)........................................................... 71
The MVI56 Modbus Plus Communication Module allows ControlLogix I/O compatible 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.
July 23, 2008
Page 47 of 96
MVI56-MBP ♦ ControlLogix Platform
Modbus Plus Communication Module
Reference
Communication parameters (Config port only) o
Baud: 57,600 (fixed) o o
Parity: none (fixed)
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 o o o o
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 o o
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
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 error codes returned to ladder logic on a per command basis
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
Modbus Plus Communication Module
Specification Description
Backplane Current Load
Operating Temperature
800 mA @ 5 V DC
3mA @ 24V DC
0 to 60°C (32 to 140°F)
Storage Temperature -40 to 85°C (-40 to 185°F)
Relative Humidity
LED Indicators
50g non-operational
Vibration: 5 g from 10 to 150 Hz
5% to 95% (non-condensing)
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 & PRT2)
Modbus Plus ports
Shipped with Unit
Dual DB9 Application ports for redundant operation
6-foot RS-232 configuration cable
This section provides an overview of how the MVI56-MBP module transfers data using the MBP protocol. You should understand the important concepts in this chapter before you begin installing and configuring the module.
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 o o
Initialize backplane driver
Test and Clear all RAM
Reset Modbus Plus Chipset
2
Wait for Module Configuration from processor
3
Initialize Module Register space
4
Initialize Modbus Plus Chipset
5
Enable Global Input task
6
Enable Global Output task
7
Enable Slave Driver
8
Enable Master Driver
ProSoft Technology, Inc.
July 23, 2008
Page 49 of 96
MVI56-MBP ♦ ControlLogix Platform
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.
Reference
Main Logic Loop
Upon completing the power up configuration process, the module enters an infinite loop that performs the following functions:
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 between the module and the processor.
Page 50 of 96 ProSoft Technology, Inc.
July 23, 2008
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.
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.
July 23, 2008
Page 51 of 96
MVI56-MBP ♦ ControlLogix Platform
Modbus Plus Communication Module
Reference
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.
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
ControlLogix processor. The structure of the input image used to transfer this data is shown in the following table:
0
1
2 to 201
202 to 217
218 to 249
Read Block ID
Write Block ID
Read Data
Status Data
Global Input Data
1
1
200
16
32
Page 52 of 96 ProSoft Technology, Inc.
July 23, 2008
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 through 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:
0
1 to 200
201 to 213
214 to 215
216 to 247
Write Block ID
Write Data
Command Event Enable Bits
Spare
Global Output Data
1
200
13
2
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 highspeed 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 structure of the block is displayed in the following table:
ProSoft Technology, Inc.
July 23, 2008
Page 53 of 96
MVI56-MBP ♦ ControlLogix Platform
Modbus Plus Communication Module
Reference
1 to 5
6 to 15
16 to 47
48 to 247
Backplane Parameters
Modbus Plus Configuration
Input file Map
Spare
5
10
32
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:
0
1 to 8
9 to 16
17 to 24
25 to 32
33 to 40
41 to 48
Page 54 of 96
0
1 to 8
9 to 16
17 to 24
25 to 32
33 to 40
41 to 48
49 to 86
57 to 64
65 to 72
73 to 80
81 to 88
89 to 96
97 to 104
105 to 112
121 to 128
9100 to 9103
Device Definition
Device Definition
Device Definition
Device Definition
Device Definition
Device Definition
Device Definition
Device Definition
Device Definition
Device Definition
Device Definition
Device Definition
Device Definition
Device Definition
Device Definition
8
8
8
8
8
8
8
8
8
8
8
8
8
8
1
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 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:
6000 to 6007
Command Definition
Command Definition
Command Definition
Command Definition
Command Definition
Command Definition
1
8
8
8
8
8
8
ProSoft Technology, Inc.
July 23, 2008
Modbus Plus Communication Module
49 to 86
57 to 64
65 to 72
73 to 80
81 to 88
89 to 96
97 to 104
105 to 112
121 to 128
129 to 136
137 to 144
145 to 152
153 to 160
161 to 168
169 to 176
177 to 184
185 to 192
193 to 200
Command Definition
Command Definition
Command Definition
Command Definition
Command Definition
Command Definition
Command Definition
Command Definition
Command Definition
Command Definition
Command Definition
Command Definition
Command Definition
Command Definition
Command Definition
Command Definition
Command Definition
Command Definition
8
8
8
8
8
8
8
8
8
8
8
8
8
8
8
8
8
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. Two 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:
1
2 to 71
72 to 101
102 to 171
172 to 249
Write Block ID
Global Input Status Data
Module Status Data
Global Input Counter Data
Spare
1
70
30
70
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:
1
2 to 201
201 to 249
ProSoft Technology, Inc.
July 23, 2008
Write Block ID
Command Status Data
Spare
1
200
48
Page 55 of 96
MVI56-MBP ♦ ControlLogix Platform
Modbus Plus Communication Module
Reference
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
boot
cold
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 priority in the module. The format of the block used for this control process is shown in the following figure:
1
2 to 11
12 to 21
22 to 31
32 to 41
42 to 51
52 to 61
62 to 247
Number of commands to add
User Command 1
User Command 2
User Command 3
User Command 4
User Command 5
User Command 6
Spare
1
10
10
10
10
10
10
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
0
Parameter
Module's Database Register Number
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
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 module has the following format:
1
2 to 61
62 to 247
Number of commands to add
List of command indexes
Spare
1
60
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:
1
2 to 61
62 to 247
Number of commands to disable 1
List of command indexes 60
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:
1
2 to 61
62 to 247
Number of commands to enable 1
List of command indexes 60
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:
1
2 to 61
62 to 247
ProSoft Technology, Inc.
July 23, 2008
Number of commands to enable 1
List of command indexes 60
Spare 186
Page 57 of 96
MVI56-MBP ♦ ControlLogix Platform
Modbus Plus Communication Module
Reference
Write Configuration
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:
2 to 6
7 to 16
17 to 48
49 to 247
Backplane Parameters
Modbus Plus Configuration
Input File Map
Spare
Blocks -9100 to -9103, Device Definition Data:
0
1
2 to 9
10 to 17
18 to 25
26 to 33
34 to 41
42 to 49
50 to 57
66 to 73
74 to 81
82 to 89
90 to 94
98 to 105
106 to 113
114 to 121
122 to 129
-9100 to -9103
-9100 to -9103
Device Definition
Device Definition
Device Definition
Device Definition
Device Definition
Device Definition
Device Definition
Device Definition
Device Definition
Device Definition
Device Definition
Device Definition
Device Definition
Device Definition
Device Definition
Blocks -6000 to -6007, Master Command List Data:
0
1
2 to 9
Page 58 of 96
-6000 to -6007
-6000 to -6007
Command Definition
1
1
8
8
8
8
8
8
8
8
8
8
8
8
8
8
8
1
1
8
5
10
32
200
ProSoft Technology, Inc.
July 23, 2008
Modbus Plus Communication Module
10 to 17
18 to 25
26 to 33
34 to 41
42 to 49
50 to 57
66 to 73
74 to 81
82 to 89
90 to 94
98 to 105
106 to 113
114 to 121
122 to 129
130 to 137
138 to 145
146 to 153
154 to 161
162 to 169
170 to 177
178 to 185
186 to 193
194 to 201
Command Definition
Command Definition
Command Definition
Command Definition
Command Definition
Command Definition
Command Definition
Command Definition
Command Definition
Command Definition
Command Definition
Command Definition
Command Definition
Command Definition
Command Definition
Command Definition
Command Definition
Command Definition
Command Definition
Command Definition
Command Definition
Command Definition
Command Definition
8
8
8
8
8
8
8
8
8
8
8
8
8
8
8
8
8
8
8
8
8
8
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 (software reset) operation.
This block is commonly sent to the module any time configuration data modifications are made in the controller tags data area. This will force the module to read the new configuration information and to restart. The structure of the control block is shown in the following table:
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
Modbus Plus Communication Module
1 to 249 Spare
Reference
249
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.
Global 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.
Step Description
1
2
3
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.
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.
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 23, 2008
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.
Step Description
1
2
3
4
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.
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.
After the data processing has been completed in Step 2, the response is issued to the originating node.
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.
July 23, 2008
Page 61 of 96
MVI56-MBP ♦ ControlLogix Platform
Modbus Plus Communication Module
Reference
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 data 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.
+---------+
enable -¦ ¦- active
¦ 40050 ¦
+---------¦
abort -¦ ¦- error
¦ 40060 ¦
+---------¦
¦ MSTR ¦- success
¦ 00020 ¦
+---------+
Contents of registers in the control block
40050 = 2 Read instruction
40051 = 0 Error code
40052 = 20 Length of the read
40053 = 50 slave register to read (module address 50)
40054 = 6 MVI56-MBP Node address to retrieve data from
40055 = 1 Slave Input Path for routing
40056 = 0 Routing Address 3
40057 = 0 Routing Address 4
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.
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 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
Modbus Plus Communication Module
+---------+
enable -¦ ¦- active
¦ 40001 ¦
+---------¦
abort -¦ ¦- error
¦ 40010 ¦
+---------¦
¦ MSTR ¦- success
¦ 00002 ¦
+---------+
Contents of registers in the control block
40001 = 1 Write instruction
40002 = 0 Error code
40003 = 30 Length of the write
40004 = 100 register to Write to in module
40005 = 6 MVI56-MBP Node address to write to
40006 = 1 Slave Input Path for routing
40007 = 0 Routing Address 3
40008 = 0 Routing Address 4
40009 = 0 Routing Address 5
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 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.
ProSoft Technology, Inc.
July 23, 2008
Page 63 of 96
MVI56-MBP ♦ ControlLogix Platform
Modbus Plus Communication Module
Reference
Step Description
1
2
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.
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 the command.
3
4
5
Presuming successful processing by the other nodes, responses are received into the Master driver for processing.
Data received from the other nodes on the network is passed into the module's internal database, assuming a read command.
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 Destination 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
Modbus Plus Communication Module
Database
Address
7170
7171
7172
7173
7174
7175
7176
7177
7178
7179
7180
7181
7182
Bit Offset in
Controller Tag for Event
Control
0 to 15
16 to 31
32 to 47
48 to 63
64 to 79
80 to 95
96 to 111
112 to 127
128 to 143
144 to 159
160 to 175
176 to 191
192 to 199
Name Description
Event Commands #1 to 16
Event Commands #17 to 32
Event Commands #33 to 48
Event Commands #49 to 64
Event Commands #65 to 80
Event Commands #81 to 96
Event Commands #97 to 112
Event Commands #113 to 128
Event Commands #129 to 144
Event Commands #145 to 160
Event Commands #161 to 176
Event Commands #177 to 192
Event Commands #193 to 200
This block of data consists of
13 words of bits that are mapped to individual commands in the Master
Command List.
Setting a bit will trigger the corresponding command and will set a one-shot bit for the command in the module. This bit must be reset before being set again in order for the command to execute again.
This data is transferred continuously to the module in the module's output image.
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
0
1
Name
Event Commands #1
Event Commands #2
4
5
2
3
Event Commands #3
Event Commands #4
Event Commands #5
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
Modbus Plus Communication Module
Reference
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 up 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.
Step Description
1
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.
2
3
4
5
6
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 accepted.
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
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-word 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:
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 highspeed Input File data using this map.
Unsuccessful Execution
If the command was unsuccessful (Status Code > 0x01), the status will be maintained until the command executes successfully. The ladder logic must 'resubmit' 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 present.
ProSoft Technology, Inc.
July 23, 2008
Page 67 of 96
MVI56-MBP ♦ ControlLogix Platform
Modbus Plus Communication Module
Reference
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.
6.3 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 communications on this port is shown in the following diagram:
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
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
Notice how the DF1 driver is opened, and the driver is looking for a processor on node 1. If the network is being browsed, then you will not be able to stop this driver. To stop the driver your RSWho screen should look like this:
Branches are displayed or hidden by clicking on the or the icons.
4
When you have verified that the driver is not being browsed, go to
Communications>Configure Drivers
You may see something like this:
ProSoft Technology, Inc.
July 23, 2008
Page 69 of 96
MVI56-MBP ♦ ControlLogix Platform
Modbus Plus Communication Module
Reference
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:
5
After you have stopped the driver you will see the following:
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, 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
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
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:
6.5 DB9 to RJ45 Adaptor (Cable 14)
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.
July 23, 2008
Page 71 of 96
MVI56-MBP ♦ ControlLogix Platform
Modbus Plus Communication Module
6.6.1 Module Memory Map
Reference
Overview
Access
R
R
R
R/W
R/W
O File
I File
Module Address Range Modbus Address Range Description
4000 4069 44001 44070
Block
Size
Global In Update Status
4000
70
Master Status 200
Misc Module Status 30 4270
4300
4370
4410
4299
4369
4409
4449
44271
44301
44371
44411
44300
44370
44410
44450
Global In Update Counters
Module Configuration Block
Global In File Map
70
40
40
640
7090
7130
7129
7169
47091
47131
47130
47170
Global Out Image
2000
40
Global In Image 40
Command 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 the 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. 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
Modbus Plus Communication Module
6.6.2 Status Data Definition
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
3
4
5
0
1
2
4000
4001
4002
4003
4004
4005
Global In Update Stat - Device #1
Global In Update Stat - Device #2
Global In Update Stat - Device #3
Global In Update Stat - Device #4
Global In Update Stat - Device #5
Global In Update Stat - Device #6
8
9
6
7
10
4006
4007
4008
4009
4010
Global In Update Stat - Device #7
Global In Update Stat - Device #8
Global In Update Stat - Device #9
Global In Update Stat - Device #10
Global In Update Stat - Device #11
- - -
- - -
- - -
60 4060 Global In Update Stat - Device #61
61
62
4061
4062
Global In Update Stat - Device #62
Global In Update Stat - Device #63
63 4063 Global In Update Stat - Device #64
64 4064 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 Global Update Timeout in milliseconds
0x10 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
Modbus Plus Communication Module
Array assignments for MstrCmd member of MBPStat object
Master Command Status
Reference
0
3
4
1
2
4070
4071
4072
4073
4074
Master Command Status: #1
Master Command Status: #2
Master Command Status: #3
Master Command Status: #4
Master Command Status: #5
7
8
5
6
4075
4076
4077
4078
Master Command Status: #6
Master Command Status: #7
Master Command Status: #8
Master Command Status: #9
9 4079 Master Command Status: #10
- - -
- - -
- - -
- - -
- - -
195 4265 Master Command Status: #196
196
197
4266
4267
Master Command Status: #197
Master Command Status: #198
198
199
4268
4269
Master Command Status: #199
Master Command Status: #200
Error Code Definition
High Byte
0x00
Low Byte
0x00
0x01
Description
Normal - Driver will reset when processing command
Command has completed successfully
0x02 Routing
0x01 No response received - Is addressed unit online
0x04
0x08
0x10
0x20
0x40
0x80 exception response received invalid node type in routing path slave rejected the Modbus command - invalid input path?? initiated transaction forgotten by slave unexpected master output path received unexpected response received
0x04 Configuration
0x01
0x02
Invalid Configuration for Command
Invalid Command Type - 1 = Write, 2 = Read , All other error
Page 74 of 96 ProSoft Technology, Inc.
July 23, 2008
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
4270
4272
4273
4274-H
4274-L
4275-H
4275-L
4276-H
4276-L
4277
4278
4279
4280
4281
4282
4283
4284
4285
4286
4287
4288
4289
0
8
9
10
11
12
6
7
5
6
2
4
5
3
4
16
17
18
19
13
14
15
Module Status - Software Reset Response
Token Pass Counter
Token Rotation Time in milliseconds
Communication Failed Error Counter
Communication Retry Counter
No Response Received Error Counter
Good Received Packet Success Counter
Unexpected Path Error Counter
Exception Response Received Error Counter
Data master output path 1 & 2 counter
Data master output path 3 & 4 counter
Data master output path 5 & 6 counter
Data master output path 7 & 8 counter
Data slave output path 1 & 2 counter
Data slave output path 3 & 4 counter
Data slave output path 5 & 6 counter
Data slave output path 7 & 8 counter
Global Out Update Status
Global Out Update Counter
Data transfer read counter
Data transfer write counter
Data parse counter
22 4292 Data transfer error counter
27 4297
ProSoft Technology, Inc.
July 23, 2008
MBP Update Processing Time
Page 75 of 96
MVI56-MBP ♦ ControlLogix Platform
Modbus Plus Communication Module
28
29
4298
4299
Global In Update Time
Global Out Update Time
Module Status Values
Normal Operation
Code Description
Interface Crash Codes
Code Description
0x02
0x03
0x04
0x05
0x06
0x07
0x08
0x09
0x0A
0X0B
Bad interface opcode
Interface data error
Interface test error
Interface x-fer done error
Bad interface path
Bad interface state
Bad interface length
Global data length error
Global data address error
Global data not present
Fatal Crash Codes
0x88
0x89
0x8A
0X8B
0X8C
0X8D
0X8E
0X8F
Code Description
0x81 PROM checksum error
0x82
0x83
Internal RAM data test error
External RAM data test error
0x84
0x85
0x86
0x87
External RAM address test error
Bad confidence test index
External Int0 event error
External Int1 event error
0X90
0X91
0X92
DMA Int0 event error
Comm. Int event error
Xmit-no good event error
No response timeout MAC State
No response timeout MAC idle
Receive OK MAC state
Transmit OK MAC state
No receive buffer free
Bad input transfer length
Reserved rev buffer error
Bad trans control state
Page 76 of 96
Reference
ProSoft Technology, Inc.
July 23, 2008
Code Description
0X93 Bad word request bit
0X94
0X95
0X96
0X97
0X98
Node queue overflow
Bad data queue error
Empty data path error
Bad path search index
Bad data slave path
Peer Status Codes
Code Description
0 Monitor link operation
32
64
Normal link operation
Never getting token
Modbus Plus Communication Module
Global Out Update Status
Code Description
0x01 Updating all OK
0x08
0x10
0x40
Global update timeout (not transmitted in 500 milliseconds)
Global data not configured (length set to zero)
Invalid Global Data Length (Length > 32 words)
Array assignments for InCntr member of MBPStat object
Global In Update Counters
2
3
4
0
1
4300
4301
4302
4303
4304
Global In Update Counter - Device #1
Global In Update Counter - Device #2
Global In Update Counter - Device #3
Global In Update Counter - Device #4
Global In Update Counter - Device #5
5
6
7
8
4305
4306
4307
4308
Global In Update Counter - Device #6
Global In Update Counter - Device #7
Global In Update Counter - Device #8
Global In Update Counter - Device #9
9
10
4309
4310
Global In Update Counter - Device #10
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
61
62
4361
4362
Global In Update Counter - Device #62
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
Reference
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
4370 44371 Module
Command Word
Description
This register controls the module from a remote device. The value placed in the register will be processed and then set to zero after the function 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
Plus Node
This value defines the Modbus Plus Node Address for the 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
Length (0 or 1 to
32)
This value defines the number of Global Output words to be placed on the Modbus Plus network. If the value is set to 0, no 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 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
(0 or 1 to 32)
This value defines the number of words to be transferred by 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
Timing
This parameter is not used by the MVI56-MBP module as the
In File data is updated with each new input image sent to the processor.
4376 44377 Global In Update
Timeout
This value defines the timeout period (0 to 65535 milliseconds) 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
Modbus Plus Communication Module
DB Address Modbus Address Parameter Description
4377 44378 Spare Not
4378 44379 Spare Not
4379 44380 Spare Not
4380 44381 Number of Nodes
Defined in the
Device Definition
File
This value specifies the number of devices to consider in the
Device Definition Table. Valid range for this parameter is 0 to
64 inclusive. These node definitions are used by several modes of operation of the module.
4381 44382 Number
Commands
This parameter specifies the number of commands to be 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
Data Paths
Maximum be made available to the module's Master Mode Driver by the
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
Timeout Preset
This parameter defines the number of milliseconds (0 to
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
Register
This parameter specifies the module's start address where 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
Register Count
This parameter specifies the number of registers to transfer from the module's database to the processor. This is a readonly value and can only be set in the processor.
4386 44387 Read
Maximum Count
This read-only value specifies the number of blocks of 200word data are to be transferred from the module to the processor.
4387 44388 Write Block Start
Register
This read-only parameter specifies the starting register in the module's database where data will be transferred from the processor to the module.
4388 44389 Write This read-only parameter specifies the number of registers to
Register Count set in the module's database from the processor.
4389 44390 Write 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 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
4410
4411
44411
44412
Word 0
Word 1
4412
4413
44413
44414
Word 2
Word 3
Description
Module's database register address for Word 0 of Input File Data.
Module's database register address for Word 1 of Input File Data.
Module's database register address for Word 2 of Input File Data.
Module's database register address for Word 3 of Input File Data.
4414
4439
4440
44415
- -
44440
44441
Word 4 Module's database register address for Word 4 of Input File Data.
Word 29
Word 30
Module's database register address for Word 29 of Input File
Data.
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.
4600
4610
4620
4630
4640
4650
4660
4670
4510
4520
4530
4540
4550
4560
4570
4580
4590
DB Address Modbus Address Parameter
4450 44451 Device Def ID 0
Description
Start register of device definition block for device index 0
4460
4470
4480
4490
4500
44461
44471
44481
44491
44501
Device Def ID 1 Start register of device definition block for device index 1
Device Def ID 2 Start register of device definition block for device index 2
Device Def ID 3 Start register of device definition block for device index 3
Device Def ID 4
Device Def ID 5
Start register of device definition block for device index 4
Start register of device definition block for device index 5
44511
44521
44531
44541
44551
44561
44571
44581
44591
Device Def ID 6
Device Def ID 7
Device Def ID 8
Start register of device definition block for device index 6
Start register of device definition block for device index 7
Start register of device definition block for device index 8
Device Def ID 9 Start register of device definition block for device index 9
Device Def ID 10 Start register of device definition block for device index 10
Device Def ID 11 Start register of device definition block for device index 11
Device Def ID 12 Start register of device definition block for device index 12
Device Def ID 13 Start register of device definition block for device index 13
Device Def ID 14 Start register of device definition block for device index 14
44601
44611
44621
44631
44641
44651
44661
44671
Device Def ID 15 Start register of device definition block for device index 15
Device Def ID 16 Start register of device definition block for device index 16
Device Def ID 17 Start register of device definition block for device index 17
Device Def ID 18 Start register of device definition block for device index 18
Device Def ID 19 Start register of device definition block for device index 19
Device Def ID 20 Start register of device definition block for device index 20
Device Def ID 21 Start register of device definition block for device index 21
Device Def ID 22 Start register of device definition block for device index 22
Page 80 of 96 ProSoft Technology, Inc.
July 23, 2008
Modbus Plus Communication Module
4950
4960
4970
4980
4990
5000
5010
5020
4850
4860
4870
4880
4890
4900
4910
4920
4930
4940
5030
5040
5050
5060
5070
5080
4720
4730
4740
4750
4760
4770
4780
4790
4800
4810
4820
4830
4840
DB Address Modbus Address Parameter
4680 44681
Description
Device Def ID 23 Start register of device definition block for device index 23
4690
4700
4710
44691
44701
44711
Device Def ID 24 Start register of device definition block for device index 24
Device Def ID 25 Start register of device definition block for device index 25
Device Def ID 26 Start register of device definition block for device index 26
44721
44731
44741
44751
44761
44771
44781
44791
44801
44811
44821
44831
44841
Device Def ID 27 Start register of device definition block for device index 27
Device Def ID 28 Start register of device definition block for device index 28
Device Def ID 29 Start register of device definition block for device index 29
Device Def ID 30 Start register of device definition block for device index 30
Device Def ID 31 Start register of device definition block for device index 31
Device Def ID 32 Start register of device definition block for device index 32
Device Def ID 33 Start register of device definition block for device index 33
Device Def ID 34 Start register of device definition block for device index 34
Device Def ID 35 Start register of device definition block for device index 35
Device Def ID 36 Start register of device definition block for device index 36
Device Def ID 37 Start register of device definition block for device index 37
Device Def ID 38 Start register of device definition block for device index 38
Device Def ID 39 Start register of device definition block for device index 39
44851
44861
44871
44881
44891
44901
44911
44921
44931
44941
44951
44961
44971
44981
44991
45001
45011
45021
45031
45041
45051
45061
45071
45081
Device Def ID 40 Start register of device definition block for device index 40
Device Def ID 41 Start register of device definition block for device index 41
Device Def ID 42 Start register of device definition block for device index 42
Device Def ID 43 Start register of device definition block for device index 43
Device Def ID 44 Start register of device definition block for device index 44
Device Def ID 45 Start register of device definition block for device index 45
Device Def ID 46 Start register of device definition block for device index 46
Device Def ID 47 Start register of device definition block for device index 47
Device Def ID 48 Start register of device definition block for device index 48
Device Def ID 49 Start register of device definition block for device index 49
Device Def ID 50 Start register of device definition block for device index 50
Device Def ID 51 Start register of device definition block for device index 51
Device Def ID 52 Start register of device definition block for device index 52
Device Def ID 53 Start register of device definition block for device index 53
Device Def ID 54 Start register of device definition block for device index 54
Device Def ID 55 Start register of device definition block for device index 55
Device Def ID 56 Start register of device definition block for device index 56
Device Def ID 57 Start register of device definition block for device index 57
Device Def ID 58 Start register of device definition block for device index 58
Device Def ID 59 Start register of device definition block for device index 59
Device Def ID 60 Start register of device definition block for device index 60
Device Def ID 61 Start register of device definition block for device index 61
Device Def ID 62 Start register of device definition block for device index 62
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
Reference
Device Definition Block Format
The structure of the data in each block is described in the following table:
DB Address Modbus Address Parameter Description
4450 44451
4451 44452
Route
Route
4452 44453 Route
These values determine the network route that a message will use to get from the module to a node on the network. The values are entered directly into the Modbus Plus message.
Note the following:
4453 44454 Route
4454 44455 Route
PLCs: When addressing these devices, the last non-zero byte 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 nonzero 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
Address
This parameter specifies the starting address in the module's database where the received global data will be placed. Valid locations are from 0 to 3999.
4458 44459 Spare Not
4459 44460 Spare Not
Master Command List
The next data set present in the module's database is the master command list.
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
5090 45091 Cmd # 0
5100
5110
45101
45111
Cmd # 1
Cmd # 2
5120
5130
45121
45131
5140 45141
- -
Cmd # 3
Cmd # 4
Cmd # 5
7060
7070
7080
47061
47071
47081
Cmd # 197
Cmd # 198
Cmd # 199
Description
Start of command block for command # 0
Start of command block for command # 1
Start of command block for command # 2
Start of command block for command # 3
Start of command block for command # 4
Start of command block for command # 5
Start of command block for command # 197
Start of command block for command # 198
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
DB Address Modbus Address
5090 45091
Parameter
Enable
5091 45092
5092
5093
5094
5095
5096
5097
45093
45094
45095
45096
45097
45098
Register Number
Polling Interval
Register Count
Swap Code
Device Index
Function Code
Register Address in
Device
Modbus Plus Communication Module
Description
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 the PollInt parameter; and 2=The command will only execute if the event control bit for the command is set. address to be associated with the command. Valid entry for this parameter is 0 to 3999.
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.
This parameter defines the number of registers to be considered by the command. Valid entry for this parameter is 1 to 100.
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.
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 node.
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
5099 45100
Spare
Spare
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
DB Address Modbus Address Parameter
7090 47091 Global Out 0
7091
7092
47092
47093
Global Out 1
Global Out 2
7093
7094
47094
47095
- -
7121 47122
Global Out 3
Global Out 4
Global Out 31
7122 47123 Spare
7123 47124 Spare
7124 47125 Spare
7125 47126 Spare
7126 47127 Spare
7127 47128 Spare
7128 47129 Spare
7129 47130 Spare
Description
Global output data for module word # 0
Global output data for module word # 1
Global output data for module word # 2
Global output data for module word # 3
Global output data for module word # 4
Global output data for module word # 31
Reference
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
7130 47131 In File Word 0
7131
7132
47132
47133
7133 47134
- -
In File Word 1
In File Word 2
In File Word 3
7161 47162
7162 47163
7163 47164
7164 47165
In File Word 31
Spare
Spare
Spare
7165 47166
7166 47167
7167 47168
Spare
Spare
Spare
Page 84 of 96
Description
Data from Input File Map index 0 for word 0
Data from Input File Map index 1 for word 1
Data from Input File Map index 2 for word 2
Data from Input File Map index 3 for word 3
Data from Input File Map index 31 for word 31
ProSoft Technology, Inc.
July 23, 2008
Modbus Plus Communication Module
DB Address Modbus Address Parameter
7168 47169 Spare
7169 47170 Spare
Description
6.6.6 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
7186
7187
7188
7189
7190
7191
7192
7193
7194
7195
7196
7197
7178
7179
7180
7181
7182
7183
7184
7185
DB Address Modbus Address Parameter
7170 47171 Event Control Word #0
7171 47172 Event Control Word #1
7172
7173
7174
7175
7176
7177
47173
47174
47175
47176
47177
47178
Event Control Word #2
Event Control Word #3
Event Control Word #4
Event Control Word #5
Event Control Word #6
Event Control Word #7
47179
47180
47181
47182
47183
47184
47185
47186
Event Control Word #8
Event Control Word #9
Description
Event control bits for commands 0 to 15
Event control bits for commands 16 to 31
Event control bits for commands 32 to 47
Event control bits for commands 48 to 63
Event control bits for commands 64 to 79
Event control bits for commands 80 to 95
Event control bits for commands 96 to 111
Event control bits for commands 112 to 127
Event control bits for commands 128 to 143
Event control bits for commands 144 to 159
Event Control Word #10 Event control bits for commands 160 to 175
Event Control Word #11 Event control bits for commands 176 to 191
Event Control Word #12 Event control bits for commands 192 to 199
Event Done Word #0 Event done bits for commands 0 to 15
Event Done Word #1
Event Done Word #2
Event done bits for commands 16 to 31
Event done bits for commands 32 to 47
47187
47188
47189
47190
47191
47192
47193
47194
47195
47196
47197
47198
Event Done Word #3
Event Done Word #4
Event Done Word #5
Event Done Word #6
Event Done Word #7
Event Done Word #8
Event Done Word #9
Event Done Word #10
Event Done Word #11
Event Done Word #12
Event Err Word #0
Event Err Word #1
Event done bits for commands 48 to 63
Event done bits for commands 64 to 79
Event done bits for commands 80 to 95
Event done bits for commands 96 to 111
Event done bits for commands 112 to 127
Event done bits for commands 128 to 143
Event done bits for commands 144 to 159
Event done bits for commands 160 to 175
Event done bits for commands 176 to 191
Event done bits for commands 192 to 199
Event error bits for commands 0 to 15
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
7215
7216
7217
7218
7219
7220
7221
7202
7203
7204
7205
7206
7207
7208
7209
7210
7211
7212
7213
7214
DB Address Modbus Address Parameter
7198 47199 Event Err Word #2
7199
7200
7201
47200
47201
47202
Event Err Word #3
Event Err Word #4
Event Err Word #5
47203
47204
47205
47206
47207
47208
47209
47210
47211
47212
47213
47214
47215
Event Err Word #6
Event Err Word #7
Event Err Word #8
Event Err Word #9
Event Err Word #10
Event Err Word #11
Event Err Word #12
Event One Shot #0
Event One Shot #1
Event One Shot #2
Event One Shot #3
Event One Shot #4
Event One Shot #5
47216
47217
47218
47219
47220
47221
47222
Event One Shot #6
Event One Shot #7
Event One Shot #8
Event One Shot #9
Event One Shot #10
Event One Shot #11
Event One Shot #12
Description
Event error bits for commands 32 to 47
Event error bits for commands 48 to 63
Event error bits for commands 64 to 79
Event error bits for commands 80 to 95
Event error bits for commands 96 to 111
Event error bits for commands 112 to 127
Event error bits for commands 128 to 143
Event error bits for commands 144 to 159
Event error bits for commands 160 to 175
Event error bits for commands 176 to 191
Event error bits for commands 192 to 199
Event one shot bits for commands 0 to 15
Event one shot bits for commands 16 to 31
Event one shot bits for commands 32 to 47
Event one shot bits for commands 48 to 63
Event one shot bits for commands 64 to 79
Event one shot bits for commands 80 to 95
Event one shot bits for commands 96 to 111
Event one shot bits for commands 112 to 127
Event one shot bits for commands 128 to 143
Event one shot bits for commands 144 to 159
Event one shot bits for commands 160 to 175
Event one shot bits for commands 176 to 191
Event one shot bits for commands 192 to 199
Reference
Page 86 of 96 ProSoft Technology, Inc.
July 23, 2008
Support, Service & Warranty MVI56-MBP ♦ ControlLogix Platform
Modbus Plus Communication Module
7 Support, Service & Warranty
In This Chapter
How to Contact Us: Technical Support.................................................. 87
Return Material Authorization (RMA) Policies and Conditions............... 88
ProSoft Technology, Inc. (ProSoft) is committed to providing the most efficient and effective support possible. Before calling, please gather the following information to assist in expediting this process:
1
Product Version Number
2
System architecture
3
Network details
If the issue is hardware related, we will also need information regarding:
1
Module configuration and contents of file o o o
Module Operation
Configuration/Debug status information
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.
7.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: [email protected]
(mailto:[email protected])
Asia Pacific
+603.7724.2080, [email protected]
(mailto:[email protected])
Languages spoken include: Chinese, English
Europe (location in Toulouse, France)
+33 (0) 5.34.36.87.20, [email protected]
(mailto:[email protected])
Languages spoken include: French, English
ProSoft Technology, Inc.
July 23, 2008
Page 87 of 96
MVI56-MBP ♦ ControlLogix Platform
Modbus Plus Communication Module
Support, Service & Warranty
North America/Latin America (excluding Brasil) (location in California)
+1.661.716.5100, [email protected] (mailto:[email protected])
Languages spoken include: English, Spanish
For technical support calls within the United States, an after-
hours answering
system allows pager access to one of our qualified technical and/or application support engineers at any time to answer your questions.
Brasil (location in Sao Paulo)
+55-11-5084-5178 , [email protected] (mailto:[email protected])
Languages spoken include: Portuguese, English
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 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 & 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.
• 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 sends unit in for evaluation b) If no defect is found, Customer will be charged the equivalent of $100
USD, plus freight charges, duties and taxes as applicable. A new purchase order will be required. 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. o o o o o o o o o o o
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
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:
• Additional 1 year = 10% of list price
• Additional 2 years = 20% of list price
• Additional 3 years = 30% of list price
ProSoft Technology, Inc.
July 23, 2008
Page 89 of 96
MVI56-MBP ♦ ControlLogix Platform
Modbus Plus Communication Module
Support, Service & Warranty
This Limited Warranty ("Warranty") governs all sales of hardware, software and other products (collectively, "Product") manufactured and/or offered for sale by
ProSoft, and all related services provided by ProSoft, including maintenance, repair, warranty exchange, and service programs (collectively, "Services"). By purchasing or using the Product or Services, the individual or entity purchasing or using the Product or Services ("Customer") agrees to all of the terms and provisions (collectively, the "Terms") of this Limited Warranty. All sales of software or other intellectual property are, in addition, subject to any license agreement accompanying such software or other intellectual property.
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 any defect in material or workmanship of the Product, with either new or used replacement parts. Such repair, including both parts and labor, will be performed at ProSoft's expense. All warranty service will be performed at service centers designated by ProSoft. 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 & 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 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.
Product manufactured or supplied by ProSoft is not fault tolerant and is not designed, manufactured or intended for use in hazardous environments requiring fail-safe performance including and without limitation: the operation of nuclear facilities, aircraft navigation of communication systems, air traffic control, direct life support machines or weapons systems in which the failure of the product could lead directly or indirectly to death, personal injury or severe physical or environmental damage (collectively, "high risk activities"). ProSoft specifically disclaims any express or implied warranty of fitness for high risk activities.
Buyer shall indemnify and hold harmless ProSoft and its employees from and against all liabilities, losses, claims, costs and expenses (including attorney's fees and expenses) related to any claim, investigation, litigation or proceeding
(whether or not ProSoft is a party) which arises or is alleged to arise from Buyer's acts or omissions under these Terms or in any way with respect to the Products.
Without limiting the foregoing, Buyer (at its own expense) shall indemnify and hold harmless ProSoft and defend or settle any action brought against such
Companies to the extent based on a claim that any Product made to Buyer specifications infringed intellectual property rights of another party. ProSoft makes no warranty that the product is or will be delivered free of any person's claiming of patent, trademark, or similar infringement. The Buyer assumes all risks (including the risk of suit) that the product or any use of the product will infringe existing or subsequently issued patents, trademarks, or copyrights.
ProSoft Technology, Inc.
July 23, 2008
Page 91 of 96
MVI56-MBP ♦ ControlLogix Platform
Modbus Plus Communication Module
Support, Service & Warranty a) Any documentation included with Product purchased from ProSoft is protected by copyright and may not be duplicated or reproduced in any form without prior written consent from ProSoft. b) ProSoft's technical specifications and documentation that are included with the Product are subject to editing and modification without notice. c) Transfer of title shall not operate to convey to Customer any right to make, or have made, any Product supplied by ProSoft. d) Customer is granted no right or license to use any software or other intellectual property in any manner or for any purpose not expressly permitted by any license agreement accompanying such software or other intellectual property. e) Customer agrees that it shall not, and shall not authorize others to, copy software provided by ProSoft (except as expressly permitted in any license agreement accompanying such software); transfer software to a third party separately from the Product; modify, alter, translate, decode, decompile, disassemble, reverse-engineer or otherwise attempt to derive the source code of the software or create derivative works based on the software; export the software or underlying technology in contravention of applicable US and international export laws and 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.
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 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 & Warranty
7.3.7 Time Limit for Bringing Suit
MVI56-MBP ♦ ControlLogix Platform
Modbus Plus Communication Module
Any action for breach of warranty must be commenced within 39 months following shipment of the Product.
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.
This Warranty allocates the risk of product failure between ProSoft and the
Customer. This allocation is recognized by both parties and is reflected in the price of the goods. The Customer acknowledges that it has read this Warranty, understands it, and is bound by its Terms.
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.
July 23, 2008
Page 93 of 96
MVI56-MBP ♦ ControlLogix Platform
Modbus Plus Communication Module
Support, Service & Warranty
Page 94 of 96 ProSoft Technology, Inc.
July 23, 2008
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
All Product Returns: • 88
Allocation of Risks • 93
Array assignments 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
B
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
ProSoft Technology, Inc.
July 23, 2008
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 Definition • 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
I
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
Page 95 of 96
MVI56-MBP ♦ ControlLogix Platform
Modbus Plus Communication Module
Limitation of Remedies ** • 92
LIMITED WARRANTY • 89, 90
M
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 Map • 72
Module Power Up • 49
Module Status Values • 76
Moving Back Through 5 Pages of Registers • 42
Navigation • 33
No Other Warranties • 93
Normal Data Transfer • 52
Normal Operation • 76
N
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 • 40, 41, 43
RS-232 Configuration/Debug Port • 68
S
Setting Jumpers • 10
Skipping 500 Registers of Data • 42
Page 96 of 96
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 & 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
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
Your Feedback Please • 4
Y
Index
ProSoft Technology, Inc.
July 23, 2008
Télécharger
Lien public mis à jour
Le lien public vers votre chat a été mis à jour. Vous pouvez afficher et gérer vos liens de chat après inscription ici.
Lien public du document
Publicité
