ProSoft Technology inRAx MVI56-BDW User Manual

MVI56-BDW

ControlLogix Platform

BARDAC Drive Web Interface

September 04, 2008

USER MANUAL

Please Read This Notice

Successful application of this module requires a reasonable working knowledge of the Rockwell Automation
ControlLogix hardware, the MVI56-BDW 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
[phone]
[phone] (Fax)
http://www.prosoft-technology.com

Copyright © ProSoft Technology, Inc. 2000 - 2008. All Rights Reserved.

MVI56-BDW User Manual
September 04, 2008

ProSoft Technology ®, ProLinx ®, inRAx ®, ProTalk® and RadioLinx ® are Registered Trademarks of ProSoft
Technology, Inc.

Contents MVI56-BDW ♦ ControlLogix Platform
BARDAC Drive Web Interface

Contents

Please Read This Notice 2

Warnings............................................................................................................................................. 2

Battery Life Advisory ...........................................................................................................................3

ProSoft® Product Documentation....................................................................................................... 3

Your Feedback Please........................................................................................................................3

Guide to the MVI56-BDW User Manual 7

1 Start Here 9

1.1 System Requirements............................................................................................... 9

1.2 Package Contents...................................................................................................10

1.3 Install ProSoft Configuration Builder Software........................................................ 10

1.4 Setting Jumpers ......................................................................................................12

1.5 Install the Module in the Rack .................................................................................12

1.6 Connect your PC to the Processor.......................................................................... 14

1.7 Open the Sample Ladder Logic ..............................................................................14

1.8 Download the Sample Program to the Processor................................................... 18

1.9 Connect your PC to the Module ..............................................................................19

2 Module Configuration 21

2.1 Installing and Configuring the Module..................................................................... 21

2.2 Modifying the Configuration File.............................................................................. 29

2.3 Download the Project to the Module ....................................................................... 37

3 Ladder Logic 39

4 Diagnostics and Troubleshooting 41

4.1 Reading Status Data from the Module.................................................................... 41

4.2 LED Status Indicators..............................................................................................52

5 Reference 55

5.1 Product Specifications.............................................................................................55

5.2 Functional Overview................................................................................................57

5.3 Cable Connections..................................................................................................67

5.4 MVI56-BDW Status Data Definition ........................................................................71

6 Support, Service & Warranty 73

6.1 How to Contact Us: Technical Support ................................................................... 73

6.2 Return Material Authorization (RMA) Policies and Conditions................................74

ProSoft Technology, Inc. Page 5 of 82
September 4, 2008

Contents MVI56-BDW ♦ ControlLogix Platform
BARDAC Drive Web Interface

6.3 LIMITED WARRANTY............................................................................................ 76

Index 81

Page 6 of 82 ProSoft Technology, Inc.
September 4, 2008

Start Here MVI56-BDW ♦ ControlLogix Platform
BARDAC Drive Web Interface

Guide to the MVI56-BDW User Manual

Function Section to Read Details

Introduction
(Must Do)

Verify Communication,
Diagnostic and
Troubleshooting

Reference
Product Specifications
Functional Overview
Glossary

Support, Service, and
Warranty

Index

→

→

→

→

Start Here (page 9)

Verifying
Communication
(page 52)

Diagnostics and
Troubleshooting
(page 41)

Reference (page 55)
Functional Overview

(page 57)
Product

Specifications (page

55)

Support, Service
and Warranty (page

73)

This Section introduces the customer to the
module. Included are: package contents,
system requirements, hardware installation, and
basic configuration.

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. Page 7 of 82
September 4, 2008

MVI56-BDW ♦ ControlLogix Platform Start Here
BARDAC Drive Web Interface

Page 8 of 82 ProSoft Technology, Inc.

September 4, 2008

Start Here MVI56-BDW ♦ ControlLogix Platform BARDAC Drive Web Interface

1 Start Here

In This Chapter

 System Requirements .............................................................................9

 Package Contents .................................................................................10

 Install ProSoft Configuration Builder Software.......................................10

 Setting Jumpers ....................................................................................12

 Install the Module in the Rack ...............................................................12

 Connect your PC to the Processor........................................................ 14

 Open the Sample Ladder Logic.............................................................14

 Download the Sample Program to the Processor.................................. 18

 Connect your PC to the Module ............................................................19

Installing the MVI56-BDW module requires a reasonable working knowledge of
the Rockwell Automation hardware, the MVI56-BDW Module and the application
in which they will be used.

Caution: It is important that those responsible for implementati on can complete the
application without exposing personnel, or equipment, to unsafe or inappropriate working
conditions. Safety, quality and experience ar e key factors in a successful installation.

1.1 System Requirements

The MVI56-BDW 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-BDW 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 Microsoft Windows XP Professional with Service Pack 1 or 2
o Microsoft Windows 2000 Professional with Service Pack 1, 2, or 3
o Microsoft Windows Server 2003

 128 Mbytes of RAM minimum, 256 Mbytes of RAM recommended

ProSoft Technology, Inc. Page 9 of 82
September 4, 2008

MVI56-BDW ♦ ControlLogix Platform Start Here
BARDAC Drive Web Interface

 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)

 CD-ROM drive
 HyperTerminal or other terminal emulator program.

Note: You can install the module in a local or remote rack. For remote rack installation, the modul e
requires EtherNet/IP or ControlNet communication with the processor.

1.2 Package Contents

The following components are included with your MVI56-BDW module, and are
all required for installation and configuration.

Important: Before beginning the installation, please verify that all of the following items are
present.

Qty. Part Name Part Number Part Description

1

1 Cable

1 Cable

1

MVI56-BDW
Module

inRAx
Solutions CD

MVI56-BDW BARDAC Drive Web Interface

Cable #15, RS232
Null Modem

RJ45 to DB9 Male
Adapter

For RS232 Connection to the CFG Port

For DB9 Connection to Module's Port

Contains sample programs, utilities and
documentation for the MVI56-BDW module.

If any of these components are missing, please contact ProSoft Technology
Support for replacement parts.

1.3 Install ProSoft Configuration Builder Software

You must install the ProSoft Configuration Builder (PCB) software in order to
configure the MVI56-BDW module. You can always get the newest version of
ProSoft Configuration Builder from the ProSoft Technology web site.

To install ProSoft Configuration Builder from the ProSoft Web Site

1 Open your web browser and navigate to http://www.prosoft-

technology.com/pcb

2 Click the Download Here link to download the latest version of ProSoft

Configuration Builder.

Page 10 of 82 ProSoft Technology, Inc.

September 4, 2008

Start Here MVI56-BDW ♦ ControlLogix Platform
BARDAC Drive Web Interface

3 Choose "Save" or "Save File" when prompted. The following illustrations

show the file download prompt for two of the most common web browsers.

4 Make a note of the location where you saved the file, for example "Desktop",

or "My Documents", so you can start the installation program.

5 When the download is complete, locate and open the file, and then follow the

instructions on your screen to install the program.

If you do not have access to the Internet, you can install ProSoft Configuration
Builder from the ProSoft Solutions CD-ROM, included in the package with your
MVI56-BDW module.

To install ProSoft Configuration Builder from the CD-ROM

1 Insert the ProSoft Solutions CD-ROM into the CD drive of your PC. Wait for

the startup screen to appear.

2 On the startup screen, click Product Documentation. This action opens an

explorer window.

3 Click to open the Utilities folder. This folder contains all of the applications

and files you will need to set up and configure your module.

4 Double-click the ProSoft Configuration Builder Setup program and follow the

instructions on your screen to install the software on your PC.

Note: Many of the configuration and maintenance procedures use files and other utilities on the
CD-ROM. You may wish to copy the files from the Utilities folder on the CD-ROM to a convenient
location on your hard drive.

ProSoft Technology, Inc. Page 11 of 82
September 4, 2008

MVI56-BDW ♦ ControlLogix Platform Start Here
BARDAC Drive Web Interface

1.4 Setting Jumpers

Note: The Setup Jumper acts as "write protection" for the module's flash memory. In "write
protected" mode, the Setup pins are not connected, and the module's firmware cannot be
overwritten. Do not jumper the Setup pins together unless you are directed to do so by ProSoft
Technical Support.

1.5 Install the Module in the Rack

If you have not already installed and configured your ControlLogix processor and
power supply, please do so before installing the MVI56-BDW 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 ar e in place before installing or servicing the
device.

After you have checked the placement of the jumpers, insert MVI56-BDW 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.

Page 12 of 82 ProSoft Technology, Inc.

September 4, 2008

Start Here MVI56-BDW ♦ ControlLogix Platform
BARDAC Drive Web Interface

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.

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-BDW with other modules c onnected 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.

ProSoft Technology, Inc. Page 13 of 82
September 4, 2008

MVI56-BDW ♦ ControlLogix Platform Start Here
BARDAC Drive Web Interface

1.6 Connect your PC to the Processor

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.

1.7 Open the Sample Ladder Logic

The sample program for your MVI56-BDW module includes custom tags, data
types and ladder logic for data I/O and status monitoring. For most applications,
you can run the sample ladder program without modification, or, for advanced
applications, you can incorporate the sample program into your existing
application.

The inRAx Solutions CD provides one or more versions of the sample ladder
logic. The version number appended to the file name corresponds with the
firmware version number of your ControlLogix processor. The firmware version
and sample program version must match.

Page 14 of 82 ProSoft Technology, Inc.

September 4, 2008

Start Here MVI56-BDW ♦ ControlLogix Platform
BARDAC Drive Web Interface

1.7.1 To Determine the Firmware Version of your Processor

Important: The RSLinx service must be installed and running on your computer in order for
RSLogix to communicate with the processor. Refer to your RSLinx and RSLogix documentation for
help configuring and troubleshooting these applications.

1 Connect an RS-232 serial cable from the COM (serial) port on your PC to the

communication port on the front of the processor.

2 Start RSLogix 5000 and close any existing project that may be loaded.
3 Open the Communications menu and choose Go Online. RSLogix will

establish communication with the processor. This may take a few moments.

4 When RSLogix has established communication with the processor, the

Connected To Go Online dialog box will open.

5 On the Connected To Go Online dialog box, click the General tab. This tab

shows information about the processor, including the Revision (firmware)
version. In the following illustration, the firmware version is 11.32

ProSoft Technology, Inc. Page 15 of 82
September 4, 2008

MVI56-BDW ♦ ControlLogix Platform Start Here
BARDAC Drive Web Interface

1.7.2 Select the Slot Number for the Module

The sample application is for a module installed in Slot 1 in a ControlLogix rack.
The ladder logic uses the slot number to identify the module. If you are installing
the module in a different slot, you must update the ladder logic so that program
tags and variables are correct, and do not conflict with other modules in the rack.

To change the slot number

1 In the Controller Organization list, select the module [1] 1756-MODULE

MVI56, and then click the right mouse button to open a shortcut menu.

2 On the shortcut menu, choose Properties. This action opens the Module

Properties dialog box.

3 In the Slot: field, use the spinners on the right side of the field to select the

slot number where the module will reside in the rack, and then click OK.

RSLogix will automatically apply the slot number change to all tags, variables
and ladder logic rungs that use the MVI56-BDW slot number for computation.

1.7.3 Configuring RSLinx

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.

Page 16 of 82 ProSoft Technology, Inc.

September 4, 2008

Start Here MVI56-BDW ♦ ControlLogix Platform
BARDAC Drive Web Interface

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 driv er type to choose for serial communicatio n with
the processor is "RS-232 DF1 Devices".

3 Click to select the driver, and then click Configure. This action opens the

Configure Allen-Bradley DF1 Communications Device dialog box.

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.

ProSoft Technology, Inc. Page 17 of 82
September 4, 2008

MVI56-BDW ♦ ControlLogix Platform Start Here
BARDAC Drive Web Interface

Note: If the auto-configuration procedure fails, verify that the cables are connected correc tly
between the processor and the serial port on your computer, and then try again. If you ar e still
unable to auto-configure the port, refer to yo ur RSLinx documentation for further troubleshooti ng
steps.

1.8 Download the Sample Program to the Processor

Note: The key switch on the front of the ControlLogix module must be in the REM position.

To download the sample program from RSLogix 5000 to the ControlLogix processor

1 If you are not already online to the processor, open the Communications

menu, and then choose Download. RSLogix will establish communication
with the processor.

2 When communication is established, RSLogix will open a confirmation dialog

box. Click the Download button to transfer the sample program to the
processor.

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 18 of 82 ProSoft Technology, Inc.

September 4, 2008

Start Here MVI56-BDW ♦ ControlLogix Platform
BARDAC Drive Web Interface

1.9 Connect your PC to the Module

With the module securely mounted, connect your PC to the
Configuration/Debug port using an RJ45-DB-9 Serial Adapter Cable and a Null
Modem Cable.

1 Attach both cables as shown.
2 Insert the RJ45 cable connector into the Configuration/Debug port of the

module.

3 Attach the other end to the serial port on your PC or laptop.

ProSoft Technology, Inc. Page 19 of 82
September 4, 2008

MVI56-BDW ♦ ControlLogix Platform Start Here
BARDAC Drive Web Interface

Page 20 of 82 ProSoft Technology, Inc.

September 4, 2008

Module Configuration MVI56-BDW ♦ ControlLogix Platform BARDAC Drive Web Interface

2 Module Configuration

In This Chapter

 Installing and Configuring the Module ...................................................21

 Modifying the Configuration File ............................................................ 29

 Download the Project to the Module......................................................37

This document contains the setup procedure, data and ladder logic requirements for successful application of the MVI56-BDW module. Each step in the setup procedure is defined in order to simplify the use of the module. Go to the Installing and Configuring the Module section to begin installing and configuring the module. Additionally, this document contains a discussion on configuring the module using the BARDACDW.CFG file. All configuration information used by the module is stored in this file. Go to the Configuration File section to begin setting up this file.

The document also contains a discussion of the data object defined for the
module. This single object completely encapsulates all the data required for
module operation. It is important to understand each element of the object for
proper application of the module. Go to the Module Data Object section for the
presentation of the object.

The ladder logic requirement section defines the minimum ladder logic required
to apply the module in a user application. The logic is simple to understand and
implement. Go to the Ladder Logic section for a complete discussion of the
ladder logic requirements.

2.1 Installing and Configuring the Module

The configuration process consists of the following steps.
1 Download the sample program to the processor.

Note: For most applications, the sample program will work without modification. We strongly
recommend setting up the module first with the s ample program, before attempting to add the
module to an existing application or create a custom application.

Modify the module's configuration files to meet the needs of your application, and
copy the updated configuration to the module. Example configuration files are
provided on the CD-ROM. Refer to Modifying the Configuration File (page 32) for
more information on the configuration files.

ProSoft Technology, Inc. Page 21 of 82
September 4, 2008

MVI56-BDW ♦ ControlLogix Platform Module Configuration
BARDAC Drive Web Interface

First, 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.

This action opens the following dialog box:

Page 22 of 82 ProSoft Technology, Inc.

September 4, 2008

Module Configuration MVI56-BDW ♦ ControlLogix Platform
BARDAC Drive Web Interface

Select the 1756- Module (Generic 1756 Module) from the list and click the OK
button. The following dialog box appears:

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 1 millisecond. Values between 1
and 10 milliseconds should work with most applications.

ProSoft Technology, Inc. Page 23 of 82
September 4, 2008

MVI56-BDW ♦ ControlLogix Platform Module Configuration
BARDAC Drive Web Interface

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:

Next, 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:

Next, 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 required for
the application. The MVI56-BDW module is defined in the example as BARDAC­DW1. 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.

Page 24 of 82 ProSoft Technology, Inc.

September 4, 2008

Module Configuration MVI56-BDW ♦ ControlLogix Platform
BARDAC Drive Web Interface

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.

It is now time to edit the BARDACDW.CFG file to set up the module for the
specific application. Refer to the Configuration File section of this document.
The module is now set up and ready to be used with your application. Insert the
module in the rack and attach the serial communication cable and the network
cable. Download the new application to the controller and place the processor in
run mode. Download the new BARDACDW.CFG file to the module using the
HyperTerminal program or any other terminal emulation program. If all the
configuration parameters are set correctly and the module is attached to a
network, the module's Application LED (APP LED) should remain off and the
backplane activity LED (BP ACT) should blink very rapidly. Refer to the Trouble
Shooting section of this manual if you encounter errors. Attach a computer or
terminal to Port 1 on the module and look at the status of the module using the
Configuration/Debug Menu in the module. Refer to the Configuration/Debug
section for a complete discussion of the use of this feature.

ProSoft Technology, Inc. Page 25 of 82
September 4, 2008

MVI56-BDW ♦ ControlLogix Platform Module Configuration
BARDAC Drive Web Interface

2.1.1 Module Data Object (BDDWModuleDef)

All data related to the MVI56-BDW 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 following illustration:

This object contains objects that define the configuration, user data, status and
command control data related to the module. Each of these object types is
discussed in the following topics of the document.

2.1.2 Backplane Control Object

This data object stores the variables required for the data transfer between the
processor and the MVI56-BDW module. The structure of the object is shown
below:

Page 26 of 82 ProSoft Technology, Inc.

September 4, 2008

Module Configuration MVI56-BDW ♦ ControlLogix Platform
BARDAC Drive Web Interface

2.1.3 User Data Objects

These objects hold data to be transferred between the processor and the MVI56­BDW module. The 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 Read
Register Count parameter of the BARDACDW.CFG file. For ease of use, this
array should be dimensioned as an 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 is responsible for placing the data received into the proper
position in the read data array. Use this data for status and control in the ladder
logic of the processor.

The write data (WriteData) is an array set to match the value entered in the
Write Register Count parameter of the BARDACDW.CFG file. For ease of use,
this array should be dimensioned as even increments of 200 words. This data is
paged up to 200 words at a time from the processor to the module. The
WriteData task is responsible for placing 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.

2.1.4 Status Data

This object views the status of the module. The BDDWInStat 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".

ProSoft Technology, Inc. Page 27 of 82
September 4, 2008

MVI56-BDW ♦ ControlLogix Platform Module Configuration
BARDAC Drive Web Interface

This object contains a structure that includes the status information for the data
transfer operations between the processor and the module. The structure of this
object is displayed below:

Additionally, the status object contains a structure for the BARDAC-DW clients.
The structure used for each is shown below:

Refer to the Reference chapter for a complete listing of the data stored in status
object.

Page 28 of 82 ProSoft Technology, Inc.

September 4, 2008

Module Configuration MVI56-BDW ♦ ControlLogix Platform
BARDAC Drive Web Interface

2.1.5 Event Command Data

The BDDWEvent object is not placed in the module definition object and is only
required when event commands are utilized in the application. This structure
holds the information required for an event command. An array of these objects
should be defined and hold the event command set to be employed in the
application. The structure of the object is shown below:

2.2 Modifying the Configuration File

2.2.1 ProSoft Configuration Builder

ProSoft Configuration Builder (PCB) provides a quick and easy way to manage
module configuration files customized to meet your application needs. PCB is not
only a powerful solution for new configuration files, but also allows you to import
information from previously installed (known working) configurations to new
projects.

ProSoft Technology, Inc. Page 29 of 82
September 4, 2008

MVI56-BDW ♦ ControlLogix Platform Module Configuration
BARDAC Drive Web Interface

Set Up the Project

To begin, start ProSoft Configuration Builder. If you have used other Windows
configuration tools before, you will find the screen layout familiar. ProSoft
Configuration Builder's window consists of a tree view on the left, an information
pane and a configuration pane on the right side of the window. When you first
start ProSoft Configuration Builder, the tree view consists of folders for Default
Project and Default Location, with a Default Module in the Default Location
folder. The following illustration shows the ProSoft Configuration Builder window
with a new project.

Your first task is to add the MVI56-BDW module to the project.
1 Use the mouse to select "Default Module" in the tree view, and then click the

right mouse button to open a shortcut menu.

Page 30 of 82 ProSoft Technology, Inc.

September 4, 2008

Module Configuration MVI56-BDW ♦ ControlLogix Platform
BARDAC Drive Web Interface

2 On the shortcut menu, choose "Choose Module Type". This action opens the

Choose Module Type dialog box.

3 In the Product Line Filter area of the dialog box, select MVI56. In the Select

Module Type dropdown list, select MVI56-BDW, and then click OK to save
your settings and return to the ProSoft Configuration Builder window.

The next task is to set the module parameters.

Adding a Project

To add a project to an existing project file:

1 Select the Default Project icon.
2 Choose Project from the Project menu, then choose Add Project. A new

project folder appears.

Adding a Module

To add a module to your project:

1 Double-click the Default Module icon to open the Choose Module Type dialog

box.

2 On the Choose Module Type dialog box, select the module type.
Or

1 Open the Project menu and choose Location.
2 On the Location menu, choose Add Module.

ProSoft Technology, Inc. Page 31 of 82
September 4, 2008

MVI56-BDW ♦ ControlLogix Platform Module Configuration
BARDAC Drive Web Interface

To add a module to a different location:

1 Right-click the Location folder and choose Add Module. A new module icon

appears.

Or

1 Select the Location icon.
2 From the Project menu, select Location, then select Add Module.

Set Module Parameters

Notice that the contents of the information pane and the configuration pane
changed when you added the MVI56-BDW module to the project.

At this time, you may wish to rename the "Default Project" and "Default Location"
folders in the tree view.

To rename an object:

1 Select the object, and then click the right mouse button to open a shortcut

menu. From the shortcut menu, choose Rename.

2 Type the name to assign to the object.
3 Click away from the object to save the new name.

Page 32 of 82 ProSoft Technology, Inc.

September 4, 2008

Module Configuration MVI56-BDW ♦ ControlLogix Platform
BARDAC Drive Web Interface

Module Entries

To configure module parameters

1 Click on the plus sign next to the icon

to expand module

information.

2 Double-click the

icon to open the Edit dialog box.

3 To edit a parameter, select the parameter in the left pane and make your

changes in the right pane.

4 Click OK to save your changes.

Comment Entries

To add comments to your configuration file:

1 Click the plus sign to the left of the

icon to expand the Module

Comments.

2 Double-click the

icon. The Edit - Module Comment dialog

appears.

3 Enter your comment and click OK to save your changes.

Printing a Configuration File

To print a configuration file:

1 Select the Module icon, and then click the right mouse button to open a

shortcut menu.

2 On the shortcut menu, choose View Configuration. This action opens the

View Configuration window.

3 On the View Configuration window, open the File menu, and choose Print.

This action opens the Print dialog box.

4 On the Print dialog box, choose the printer to use from the dropdown list,

select printing options, and then click OK.

ProSoft Technology, Inc. Page 33 of 82
September 4, 2008

MVI56-BDW ♦ ControlLogix Platform Module Configuration
BARDAC Drive Web Interface

2.2.2 MVI56-BDW Communication Module Configuration

[Section]/Item Value Range Description

[MODULE] Configuration header for general module information
Module Name: Up to 80

chars

Password: Up to 20

chars

Error/Status Pointer: -1 to 4955 Starting register location in virtual database for the

Write Register Start: 0 to 4999 This parameter specifies the starting register in the module

Write Register Count: 0 to 5000 This parameter specifies the number of registers to transfer

Read Register Start: 0 to 4999 This parameter specifies the starting register in the module

Read Register Count: 0 to 5000 This parameter specifies the number of registers to be

Failure Flag Count: 0 to 65535 This parameter specifies the number of successive transfer

Initialize Output Data: 0 or 1 This parameter determines if the output data for the module

[Section]/Item Value Range Description

[BARDAC DW CLIENT x] Start header for Client x (x=0 to 3)
Error/Status Pointer: -1 to 4990 Starting register location in virtual database for the

Name of the module for use on reports. Use this parameter
to identify your module in your system.

This parameter sets the password for the module. If the
parameter is not set, the module will not be password
protected. The module interprets the password as a case­sensitive string. Do not include spaces or special characters
in the password. Only alpha and numeric characters should
be used.

error/status table. If a value of -1 is entered, the error/status
data will not be placed in the database. All other valid
values determine the starting location of the data. This data
area includes the module version information and all server
error/status data.

where the data transferred from the processor will be
placed. Valid range for this parameter is 0 to 4999.

from the processor to the module. Valid entry for this
parameter is 0 to 5000.

where data will be transferred from the module to the
processor. Valid range for this parameter is 0 to 4999.

transferred from the module to the processor. Valid entry for
this parameter is 0 to 5000.

errors that must occur before the communication ports are
shut down. If the parameter is set to 0, the communication
ports will continue to operate under all conditions. If the
value is set larger than 0 (1 to 65535), communications will
cease if the specified number of failures occur.

should be initialized with values from the processor. If the
value is set to 0, the output data will be initialized to 0. If the
value is set to 1, the data will be initialized with data from
the processor. Use of this option requires associated ladder
logic to pass the data from the processor to the module.

error/status table for this client. If a value of -1 is entered,
the error/status data will not be placed in the database. All
other valid values determine the starting location of the
data.

Page 34 of 82 ProSoft Technology, Inc.

September 4, 2008

Module Configuration MVI56-BDW ♦ ControlLogix Platform
BARDAC Drive Web Interface

[Section]/Item Value Range Description

Minimum Command Delay: 0 to 65535 This parameter specifies the number of milliseconds to wait

between the initial issuance of a command. This parameter
can be used to delay all commands sent to slaves to avoid
"flooding" commands on the network. This parameter does
not affect retries of a command as they will be issued when
failure is recognized.

Command Error Pointer: -1 to 4999 This parameter sets the address in the internal database

where the command error data will be placed. If the value is
set to -1, the data will not be transferred to the database.

Response Timeout: 0 to 65535 This parameter represents the message response timeout

period in 1 ms increments. This is the time that a client will
wait before re-transmitting a command if no response is
received from the addressed slave. The value is set
depending upon the communication network used and the
expected response time of the slowest device on the
network.

Retry Count: 0 to 25 This parameter specifies the number of times a command

will be retried if it fails.

The command list for the client in the module is located in the [ ] section of the
file. The following table describes the functions supported by the module and the
format of each command:

Parameter Range Description

Enable 0 ,1,2 This field defines whether or not the command is to be executed and under

what conditions.

Value Description

0 The command is disabled and will not be executed in the

normal polling sequence.

1 The command is executed each scan of the command list if

the Poll Interval Time is set to zero. If the Poll Interval time is
set, the command will be executed, when the interval timer
expires.

2 The command will execute only if the internal data associated

with the command changes. This value is valid only for write
commands.

Internal Address 0 to 4999

This field specifies the internal database register to be associated with the
command.

- If the command is a read function, the data read from the Server device will
be placed starting at the register value entered in this field.

- If the command is a write function, the data written to the Server device will
be sourced from the address specified.

ProSoft Technology, Inc. Page 35 of 82
September 4, 2008

MVI56-BDW ♦ ControlLogix Platform Module Configuration
BARDAC Drive Web Interface

Parameter Range Description

Poll Interval 0 to 65535 This parameter specifies the minimum interval to execute continuous

commands (Enable code of 1). The parameter is entered in units of 1/10
seconds. Therefore, if a value of 10 is entered for a command, the command
will execute no more frequently than every 1 second.

Swap Code 0 or,1 This parameter defines if the data received from the Server is to be ordered

differently than received from the Server device. This parameter can be set to
order the register data received in an order useful by other applications. The
following table defines the values and their associated operations:

Swap Code Description

0 None - No Change is made in the byte ordering

(1234 = 1234)

1 Bytes - The bytes in each word are swapped

Node IP
Address
Function Code 0 or 1 This parameter specifies the BARDAC DW function to be executed by the

Device Address This parameter specifies the PIN value for the data value or parameter to be

xxx.xxx.xxx.xxx The IP address of the device being addressed by the command.

command. The following table defines the purpose of each function supported
by the module.

Function Code Description

0 Get (read data)
1 Set (write data)

considered by the command. Refer to the drive manual for a complete listing
of valid PIN's for your specific application.

(1234=2143)

th

2.2.3 Command List Overview

In order to interface the MVI56-BDW module with BARDAC-DW capable drives,
you must construct a command list for each of the four clients. The commands in
the list specify the Server device to be addressed, the function to be performed
(get or set), the data area in the device to interface with and the registers in the
internal database to be associated with the device data. The Client Command
List supports up to 100 commands for each client. The command list is
processed from top (command #0) to bottom independently by each client. A poll
interval parameter is associated with each command to specify a minimum delay
time in tenths of a second between the issuance of a command. If the user
specifies a value of 10 for the parameter, the command will be executed no more
frequently than every 1 second.

Write commands have a special feature, as they can be set to execute only if the
data in the write command changes. If the register data values in the command
have not changed since the command was last issued, the command will not be
executed. If the data in the command has changed since the command was last
issued, the command will be executed. Use of this feature can lighten the load on
the network. In order to implement this feature; set the enable code for the
command to a value of 2.

Page 36 of 82 ProSoft Technology, Inc.

September 4, 2008

Module Configuration MVI56-BDW ♦ ControlLogix Platform
BARDAC Drive Web Interface

2.2.4 Commands Supported by the Module

The format of each command in the list is dependent on the BARDAC DW
Function Code being executed. The tables below list the functions supported by
the module:

Function Code Definition Supported in Client

0 Get (read data) X
1 Set (write data) X

Each command list record has the same general format. The first part of the
record contains the information relating to the communication module and the
second part contains information required to interface to the BARDAC-DW
UDP/IP Server device.

2.3 Download the Project to the Module

In order for the module to use the settings you configured, you must download
(copy) the updated Project file from your PC to the module.

To Download the Project File

1 In the tree view in ProSoft Configuration Builder, click once to select the

MVI56-BDW module.

2 Open the Project menu, and then choose Module / Download. The program

will scan your PC for a valid com port (this may take a few seconds). When
PCB has found a valid com port, the following dialog box will open.

3 Choose the com port to use from the dropdown list, and then click the

Download button.

ProSoft Technology, Inc. Page 37 of 82
September 4, 2008

MVI56-BDW ♦ ControlLogix Platform Module Configuration
BARDAC Drive Web Interface

The module will perform a platform check to read and load its new settings.
When the platform check is complete, the status bar in ProSoft Configuration
Builder will be updated with the message "Module Running".

Page 38 of 82 ProSoft Technology, Inc.

September 4, 2008

Ladder Logic MVI56-BDW ♦ ControlLogix Platform BARDAC Drive Web Interface

3 Ladder Logic

Ladder logic is required for application of the MVI56-BDW module. Tasks that
must be handled by the ladder logic are module data transfer, special block
handling and status data receipt. Additionally, a power-up handler may be
needed to handle the initialization of the module's data and to clear any
processor fault conditions.

The sample ladder logic, on the ProSoft Solutions CD-ROM, is extensively
commented, to provide information on the purpose and function of each rung. For
most applications, the sample ladder will work without modification.

ProSoft Technology, Inc. Page 39 of 82
September 4, 2008

MVI56-BDW ♦ ControlLogix Platform Ladder Logic
BARDAC Drive Web Interface

Page 40 of 82 ProSoft Technology, Inc.

September 4, 2008

Diagnostics and Troubleshooting MVI56-BDW ♦ ControlLogix Platform BARDAC Drive Web Interface

4 Diagnostics and Troubleshooting

In This Chapter

 Reading Status Data from the Module ..................................................41

 LED Status Indicators............................................................................ 52

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.

4.1 Reading Status Data from the Module

The MVI56-BDW module returns a 47-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 a user set location. This data is transferred to the ControlLogix
processor continuously with each normal data read block. For a complete listing
of the status data object, refer to the Module Set Up section.

4.1.1 Required Hardware

You can connect directly from your computer's serial port to the serial port on the
module to view configuration information, perform maintenance, and send
(upload) or receive (download) configuration files.

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 UART hardware-based serial communications port available.

USB-based virtual UART systems (USB to serial port adapters) often do not
function reliably, especially during binary file transfers, such as when
uploading/downloading configuration files or module firmware upgrades.

 A null modem serial cable.

ProSoft Technology, Inc. Page 41 of 82
September 4, 2008

MVI56-BDW ♦ ControlLogix Platform Diagnostics and Troubleshooting
BARDAC Drive Web Interface

4.1.2 The Configuration/Debug Menu

The Configuration and Debug menu for this module is arranged as a tree
structure, with the Main Menu at the top of the tree, and one or more sub-menus
for each menu command. The first menu you see when you connect to the
module is the Main menu.

Because this is a text-based menu system, you enter commands by typing the
command letter from your computer keyboard in the diagnostic window in
ProSoft Configuration Builder (PCB). The module does not respond to mouse
movements or clicks. The command executes as soon as you press the
command letter — you do not need to press [Enter]. When you type a command
letter, a new screen will be displayed in your terminal application.

Using the Diagnostic Window in ProSoft Configuration Builder

To connect to the module's Configuration/Debug serial port:
1 Start PCB program with the application file to be tested. Right click over the

module icon.

2 On the shortcut menu, choose Diagnostics.

Page 42 of 82 ProSoft Technology, Inc.

September 4, 2008

Diagnostics and Troubleshooting MVI56-BDW ♦ ControlLogix Platform
BARDAC Drive Web Interface

3 This action opens the Diagnostics dialog box. Press "?" to display the Main

Menu.

Important: The illustrations of configuration/debug menus in this section are intended as a general
guide, and may not exactly match the configuration/debug menus in your own module.

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.

2 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, contact ProSoft Technology for
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:

ProSoft Technology, Inc. Page 43 of 82
September 4, 2008

MVI56-BDW ♦ ControlLogix Platform Diagnostics and Troubleshooting
BARDAC Drive Web Interface

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.

4.1.3 Main Menu

When you first connect to the module from your computer, your terminal screen
will be blank. To activate the main menu, press the [?] key on your computer's
keyboard. If the module is connected properly, the following menu will appear on
your terminal screen:

Caution: Some of the commands available to you from this menu ar e 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.

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.

Page 44 of 82 ProSoft Technology, Inc.

September 4, 2008

Diagnostics and Troubleshooting MVI56-BDW ♦ ControlLogix Platform
BARDAC Drive Web Interface

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.

Viewing Module Configuration

Press [C] to view the Module Configuration screen.
Use this command to display the current configuration and statistics for the

module.

Opening the Database Menu

Press [D] to open the Database View menu. Use this menu command to view the
current contents of the module's database.

Opening the Command Error List Menu

Press [E], [F], [G] or [H] to open the Command Error List for clients 1 through 4
respectively. This list consists of multiple pages of command list error/status
data. Press [?] to view a list of commands available on this menu.

Opening the Command List Menu

Press [I], [J], [K] or [L] to open the Command List menu for clients 1 through 4
respectively. Use this command to view the configured command list for the
module.

Transferring the Configuration File from PC to MVI56 module

Press [R] to send (upload) the configuration file from your PC to the module and
store the file on the module's Compact Flash Disk.

Press [Y] to confirm the file transfer, and then follow the instructions on the
terminal screen to complete the file transfer process.

After the file has been successfully downloaded, the module will restart the
program and load the new configuration information. Review the new
configuration using menu commands [6] and [0] to verify that the module is
configured correctly.

Transferring the Configuration File from MVI56 module to PC

Press [S] to receive (download) the configuration file from the module to your
PC.

Press [Y] to confirm the file transfer, and then follow the instructions on the
terminal screen to complete the file transfer process.

After the file has been successfully downloaded, you can open and edit the file to
change the module's configuration.

ProSoft Technology, Inc. Page 45 of 82
September 4, 2008

MVI56-BDW ♦ ControlLogix Platform Diagnostics and Troubleshooting
BARDAC Drive Web Interface

Resetting diagnostic data

Press [U] to reset the status counters for the client and/or servers in the module.

Viewing Version Information

Press [V] to view Version information for the module.
Use this command to view the current version of the software for the module, as

well as other important values. You may be asked to provide this information
when calling for technical support on the product.

Values at the bottom of the display are important in determining module
operation. The Program Scan Counter value is incremented each time a
module's program cycle is complete.

Tip: 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 ar e 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.

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.

Viewing Client Status

Press [1], [2], [3] or [4] to display the statistics of clients 1 through 4,
respectively.

Viewing Client Configuration

Press [5] to display the configuration information for the client.

Opening the Network Menu

Press [@] to open the network menu. The network menu allows you to send,
receive and view the WATTCP.CFG file that contains the IP, gateway and other
network specification information. You can find more information about the
commands on this menu in the Network Menu (page 51) section.

Page 46 of 82 ProSoft Technology, Inc.

September 4, 2008

Diagnostics and Troubleshooting MVI56-BDW ♦ ControlLogix Platform
BARDAC Drive Web Interface

Exiting the Program

Caution: Some of the commands available to you from this menu ar e 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.

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.

4.1.4 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 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. Page 47 of 82
September 4, 2008

MVI56-BDW ♦ ControlLogix Platform Diagnostics and Troubleshooting
BARDAC Drive Web Interface

Displaying the Current Page of Registers Again

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 48 of 82 ProSoft Technology, Inc.

September 4, 2008

Diagnostics and Troubleshooting MVI56-BDW ♦ ControlLogix Platform
BARDAC Drive Web Interface

Returning to the Main Menu

Press [M] to return to the Main Menu.

4.1.5 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.

Returning to the Main Menu

Press [M] to return to the Main Menu.

ProSoft Technology, Inc. Page 49 of 82
September 4, 2008

MVI56-BDW ♦ ControlLogix Platform Diagnostics and Troubleshooting
BARDAC Drive Web Interface

4.1.6 Master Command List Menu

Use this menu to view the command 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 50 Commands

Press [-] to view the previous 50 commands.

Viewing the Previous Page of Commands

Press [P] to display the previous page of commands.

Viewing the Next 50 Commands

Press [+] to view the next 50 commands from the master command list.

Viewing the Next Page of Commands

Press [N] to display the next page of commands.

Returning to the Main Menu

Press [M] to return to the Main Menu.

Page 50 of 82 ProSoft Technology, Inc.

September 4, 2008

Diagnostics and Troubleshooting MVI56-BDW ♦ ControlLogix Platform
BARDAC Drive Web Interface

4.1.7 Network Menu

The network menu allows you to send, receive and view the WATTCP.CFG file
that contains the IP and gateway addresses, and other network specification
information.

Transferring WATTCP.CFG to the module

Press [R] to transfer a new WATTCP.CFG file from the PC to the module. Use
this command to change the network configuration for the module (for example,
the module's IP address).

Press [Y] to confirm the file transfer, and then follow the instructions on the
terminal screen to complete the file transfer process.

Transferring WATTCP.CFG to the PC

Press [S] to transfer the WATTCP.CFG file from the module to your PC.
Press [Y] to confirm the file transfer, and then follow the instructions on the

terminal screen to complete the file transfer process.
After the file has been successfully transferred, you can open and edit the file to

change the module's network configuration.

Viewing the WATTCP.CFG file on the module

Press [V] to view the module's WATTCP.CFG file. Use this command to confirm
the module's current network settings.

Returning to the Main Menu

Press [M] to return to the Main Menu.

ProSoft Technology, Inc. Page 51 of 82
September 4, 2008

MVI56-BDW ♦ ControlLogix Platform Diagnostics and Troubleshooting
BARDAC Drive Web Interface

4.2 LED Status Indicators

The LEDs indicate the module's operating status as follows:

ProSoft
Module

CFG Green

BP ACT Amber

OK Red/

Color Status Indication

On

Off No data is being transferred on the Configuration/Debug port.
On Port not used P1 Green
Off Port not used
On Port not used P2 Green
Off Port not used
Off The MVI56-BDW is working normally. APP Amber
On

On

Off

Off

Green

Green The module is operating normally.
Red

Off The battery voltage is OK and functioning. BAT Red
On

Data is being transferred between the module and a remote
terminal using the Configuration/Debug port.

The MVI56-BDW module program has recognized a
communication error.

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 card is not receiving any power and is not securely
plugged into the rack.

The program has detected an error or is being configured. If
the LED remains red for over 10 seconds, the program has
probably halted. Remove the card from the rack and re-insert
the card to restart the module's program.

The battery voltage is low or battery is not present. Allow
battery to charge by keeping module plugged into rack for 24
hours. If BAT LED still does not go off, contact ProSoft
Technology, as this is not a user serviceable item.

If a configuration error is found for the client, the client configuration error word
will have a value other than zero. The configuration error word bits have the
following definitions:

Bit Description Value

0 0x0001
1 0x0002
2 0x0004
3 0x0008
4 Invalid retry count parameter 0x0010
5 0x0020
6 0x0040
7 0x0080
8 0x0100
9 0x0200
10 0x0400

Page 52 of 82 ProSoft Technology, Inc.

September 4, 2008

Diagnostics and Troubleshooting MVI56-BDW ♦ ControlLogix Platform
BARDAC Drive Web Interface

Bit Description Value

11 0x0800
12 0x1000
13 0x2000
14 0x4000
15 0x8000

Correct any invalid data in the configuration for proper module operation. When
the configuration contains a valid parameter set, all the bits in the configuration
word will be clear. This does not indicate that the configuration is valid for the
user application. Make sure each parameter is set correctly for the specific
application.

If the APP, BP ACT and OK LEDs blink at a rate of every one-second, this
indicates a serious problem with the module. Call ProSoft Technology support to
arrange for repairs.

4.2.1 Ethernet LED Indicators

LED State Description

Off No activity on the port. Data
Green Flash The port is either actively transmitting or receiving data.
Off No connection to hub or network is detected. Link
Green Solid

Connected to hub or network correctly. This is the normal
operating state.

4.2.2 Clearing a Fault Condition

Typically, if the OK LED on the front of the module turns red for more than ten
seconds, a hardware problem has been detected in the module, or the program
has exited.

To clear the condition, follow these steps:

1 Turn off power to the rack
2 Remove the card from the rack
3 Verify that all jumpers are set correctly
4 If the module requires a Compact Flash card, verify that the card is installed

correctly

5 Re-insert the card in the rack and turn the power back on
6 Verify the configuration data being transferred to the module from the

ControlLogix processor.

If the module's OK LED does not turn green, verify that the module is inserted
completely into the rack. If this does not cure the problem, contact ProSoft
Technology Support.

ProSoft Technology, Inc. Page 53 of 82
September 4, 2008

MVI56-BDW ♦ ControlLogix Platform Diagnostics and Troubleshooting
BARDAC Drive Web Interface

4.2.3 Troubleshooting

Use the following troubleshooting steps if you encounter problems when the
module is powered up. If these steps do not resolve your problem, please contact
ProSoft Technology Technical Support.

Processor Errors

Problem Description Steps to take

Processor Fault

Processor I/O LED
flashes

Module Errors

Problem Description Steps to take

BP ACT LED remains
off or blinks slowly

OK LED remains red

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.

This indicates a problem with backplane communications. Verify that all
modules in the rack are configured in the ladder logic.

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.

The program has halted or a critical error has occurred. Connect to the
Configuration/Debug port to see if the module is running. If the program
has halted, turn off power to the rack, remove the card from the rack and
re-insert the card in the rack, and then restore power to the rack.

Page 54 of 82 ProSoft Technology, Inc.

September 4, 2008

Reference MVI56-BDW ♦ ControlLogix Platform
BARDAC Drive Web Interface

5 Reference

In This Chapter

 Product Specifications........................................................................... 55

 Functional Overview.............................................................................. 57

 Cable Connections ................................................................................67

 MVI56-BDW Status Data Definition....................................................... 71

5.1 Product Specifications

The MVI56 Bardac Drive Interface Module allows ControlLogix I/O compatible
processors to interface easily with Bardac drive.web devices.

5.1.1 Features and Benefits

The MVI56-BDW module acts as a client collecting and controlling data in a
Bardac drive.web compatible device. Four independent clients are contained in
the module to interface with Bardac drives simultaneously. The data is passed
from the network to the ControlLogix backplane. The data transfer from the
processor is asynchronous from the actions on the UDP/IP network. A 5000-word
register space in the module exchanges data between the processor and the
network.

5.1.2 General Specifications

 Single Slot - 1756 backplane compatible
 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.

Sample ladder file included.

 Configuration data obtained from configuration text file downloaded to

module. Sample configuration file included

 Local or remote rack

ProSoft Technology, Inc. Page 55 of 82
September 4, 2008

MVI56-BDW ♦ ControlLogix Platform Reference
BARDAC Drive Web Interface

5.1.3 Hardware Specifications

Specification Description

Backplane Current Load

Operating Temperature 0 to 60°C (32 to 140°F)
Storage Temperature -40 to 85°C (-40 to 185°F)
Shock 30g Operational

Relative Humidity 5% to 95% (non-condensing)
LED Indicators Module Status

Application port (Ethernet)

Ethernet Port (Ethernet modules) 10/100 Base-T

Shipped with Unit RJ45 to DB-9M cables for each port

Debug/Configuration port (CFG)

CFG Port (CFG) RJ45 (DB-9M with supplied cable)

800 mA @ 5 V DC
3mA @ 24V DC

50g non-operational
Vibration: 5 g from 10 to 150 Hz

Backplane Transfer Status
Application Status
Serial Activity

RJ45 Connector
Link and activity LED indicators
Electrical Isolation 1500 V rms at 50 Hz to 60 Hz for 60 s,

applied as specified in section 5.3.2 of IEC 60950: 1991
Ethernet Broadcast Storm Resiliency = less than or equal

to 5000 [ARP] frames-per-second and less than or equal
to 5 minutes duration

6-foot RS-232 configuration cable

RS-232 only
No hardware handshaking

5.1.4 Functional Specifications

A client configured as a Bardac master device on the MVI56-BDW module will
actively issue Bardac-DW commands to other nodes on the Bardac-DW network.
One hundred commands are supported for each client. The ControlLogix
processor can be programmed to control the activity on the client by actively
selecting commands from the command list to execute, or issuing commands
directly from the ladder logic.

Some of the general specifications include:
 Support for the storage and transfer of up to 5000 registers to/from the

ControlLogix processor's controller tags

 User-definable module memory usage
 Ability for the user to define commands to set or get parameters from the

Bardac device

 10/100 Base-T Ethernet compatible interface

Page 56 of 82 ProSoft Technology, Inc.

September 4, 2008

Reference MVI56-BDW ♦ ControlLogix Platform
BARDAC Drive Web Interface

 Supports up to 100 user-defined read or write commands that can be sent to

a Bardac device

 Configurable parameters for the client include:

o Error/Status Pointer
o Command Error Pointer
o Response Timeout
o Retry Count

5.2 Functional Overview

This section provides an overview of how the MVI56-BDW module transfers data
using the BDW protocol. You should understand the important concepts in this
chapter before you begin installing and configuring the module.

5.2.1 General Concepts

The following discussion explains several concepts that are important for
understanding the operation of the MVI56-BDW module.

Module Power Up

On power up the module begins performing the following logical functions:
1 Initialize hardware components

o Initialize ControlLogix backplane driver
o Test and Clear all RAM
o Initialize the serial communication ports

2 Read configuration for module from BARDACDW.CFG file on Compact Flash

Disk

3 Initialize Module Register space
4 Enable Client Driver

After the module has received the configuration, the module will begin
communicating with other nodes on the network, depending on the configuration.

ProSoft Technology, Inc. Page 57 of 82
September 4, 2008

MVI56-BDW ♦ ControlLogix Platform Reference
BARDAC Drive Web Interface

Main Logic Loop

Upon completing the power up configuration process, the module enters an
infinite loop that performs the functions shown in the following diagram.

5.2.2 Backplane Data Transfer

The MVI56-BDW module communicates directly over the ControlLogix
backplane. Data is paged between the module and the ControlLogix processor
across the backplane using the module's input and output images. The update
frequency of the images is determined by the scheduled scan rate defined by the
user for the module and the communication load on the module. Typical updates
are in the range of 1 to 10 milliseconds.

This bi-directional transference of data is accomplished by the module filling in
data in the module's input image to send to the processor. Data in the input
image is placed in the Controller Tags in the processor by the ladder logic. The
input image for the module is set to 250 words. This large data area permits fast
throughput of data between the module and the processor.

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.

Page 58 of 82 ProSoft Technology, Inc.

September 4, 2008

Reference MVI56-BDW ♦ ControlLogix Platform
BARDAC Drive Web Interface

The following illustration shows the data transfer method used to move data
between the ControlLogix processor, the MVI56-BDW module and the network.

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. The following illustration shows the layout of the module's internal
database:

Module's Internal Database Structure

5000 registers for user data

Data contained in this database is paged through the input and output images by
coordination of the ControlLogix ladder logic and the MVI56-BDW 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. The module uses the following
block numbers:

Register Data

0

4999

ProSoft Technology, Inc. Page 59 of 82
September 4, 2008

MVI56-BDW ♦ ControlLogix Platform Reference
BARDAC Drive Web Interface

Block Range Descriptions

-1 Null block
0 Null block
1 to 25 Read or write data
1000 to 1024 Output Initialization Blocks
2000 Event Command Block
5001 to 5006 Command Control
9998 Warm-boot control block
9999 Cold-boot control block

These block identification codes can be broken down into a few groups: Normal
data transfer blocks (-1 to 25), Initialization blocks (1000 to 1024) and Command
control blocks (2000, 5000 to 5006, 9998 and 9999).

Normal Data Transfer

Normal data transfer includes the paging of the user data found in the module's
internal database in registers 0 to 4999 and the status data. These data are
transferred through read (input image) and write (output image) blocks. Refer to
the Module Set Up section 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 below:

Read Block

These blocks of data transfer information from the module to the ControlLogix
processor. The structure of the input image used to transfer this data is shown
below:

Offset Description Length

0 Reserved 1
1 Write Block ID 1
2 to 201 Read Data 200
202 Program Scan Counter 1
203 to 208 Block Transfer Status 6
209 to 218 Bardac DW Client 0 Status 10
219 to 228 Bardac DW Client 1 Status 10
229 to 238 Bardac DW Client 2 Status 10
239 to 248 Bardac DW Client 3 Status 10
249 Read Block ID 1

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 status data for the
module.

Page 60 of 82 ProSoft Technology, Inc.

September 4, 2008

Reference MVI56-BDW ♦ ControlLogix Platform
BARDAC Drive Web Interface

The Write Block ID associated with the block requests data from the ControlLogix
processor. Under normal, program operation, the module sequentially sends
read blocks and requests write blocks. For example, if 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 network or operator
control through the module's Configuration/Debug port.

Write Block

These blocks of data transfer information from the ControlLogix processor to the
module. The structure of the output image used to transfer this data is shown
below:

Offset Description Length

0 Write Block ID 1
1 to 200 Write Data 200
201 to 247 Spare 47

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.

Initialize Output Data

When the module performs a restart operation, it will request blocks of output
data from the processor to initialize the module's output data. This mode is
selected using the Initialize Output Data parameter in the configuration file. Use
the Initialize Output Data parameter in the configuration file to bring the module
to a known state after a restart operation. The structure of the block used to
request the data is displayed below:

Offset Description Length

0 Reserved 1
1 1000 to 1024 1
2 to 248 Spare 246
249 1000 to 1024 1

The block number in word 249 of the block determines the data set of up to 200
output words to transfer from the processor. Ladder logic in the processor must
recognize these blocks and place the correct information in the output image to
be returned to the module. The format of the returned write block is shown below:

Offset Description Length

0 1000 to 1024 1
1 to 200 Output Data to preset in module. 200
201 to 247 Spare 47

ProSoft Technology, Inc. Page 61 of 82
September 4, 2008

MVI56-BDW ♦ ControlLogix Platform Reference
BARDAC Drive Web Interface

Command Control Blocks

Command control blocks are special blocks used to control the module. The
current version of the software supports four command control blocks: event
command control, command control, warm boot and cold boot.

Event Command

Event command control blocks send commands directly from the ladder logic to
the client on the module. The format for these blocks is displayed below:

Offset Description Length

0 2000 1
1 to 4 IP Address 4
5 Internal DB Address 1
6 Swap Code 1
7 Bardac DW Function Code 1
8 Device Database Address 1
9 Client number (0 to 3) 1
10 to 247 Spare 238

The parameters passed with the block construct the command. The IP Address
for the node to reach on the network is entered in four registers (1 to 4). Each
digit of the IP address is entered an the appropriate register. For example, to
interface with node 192.168.0.100, enter the values 192, 168, 0 and 100 in
registers 1 to 4. The Internal DB Address parameter specifies the module's
database location to associate with the command. The Swap Code changes the
byte order in the command data area. The Bardac DW Function Code has one
of the following values 0 or 1. The Device Database Address is the PIN value
specific to the drive that is to be interfaced. Refer to the drive manual for a
complete listing of all valid PIN values. The Client Number specifies which of the
4 clients in the module is to handle the message. Values from 0 to 3 are
acceptable for this parameter. When the module receives the block, it will
process it and place it in the command queue. A detailed description of the block
is presented below:

Word Description

0

1 to 4

5

6

7

This word contains the block 2000 identification code to indicate that this block
contains a command to execute by the Client Driver.

These words contain the IP address for the server the message is intended. Each
digit (0 to 255) of the IP address is placed in one of the four registers. For
example, to reach IP address 192.168.0.100, enter the following values in words 1
to 4
address from the values entered. The values entered will be anded with the mask
0x00ff to insure the values are in the range of 0 to 255.

This word contains the internal database address in the module to be used with
the command. This word can contain a value from 0 to 4999.

The parameter specifies the swap type for the data. 0=Leave in CLX format (little­endian), 1=Swap bytes (big-endian).

This word contains the Bardac DW function code to be used with the command.
0=Get function to retrieve data from unit and 1=Set function to alter data in the
unit.

192, 168, 0 and 100. The module will construct the normal dotted IP

Page 62 of 82 ProSoft Technology, Inc.

September 4, 2008

Reference MVI56-BDW ♦ ControlLogix Platform
BARDAC Drive Web Interface

Word Description

8

9 Client index used with the block. This parameter has a value from 0 to 3.
10 to 247 Spare

This word contains the PIN value for the data value or parameter to consider with
the command. Refer to the drive manual for a complete list of all PIN values and
their meaning.

The module will respond to each event command block with a read block with the
following format:

Offset Description Length

0 Reserved 1
1 Write Block ID 1
2 0=Fail, 1=Success 1
3 Client number (0 to 3) 1
4 to 248 Spare 245
249 2000 1

Word two of the block can be used by the ladder logic to determine if the
command was added to the command queue of the module. The command will
only fail if the command queue for the client is full (the queue can handle up to
100 commands for each client).

Command Control

Command control blocks place commands in the command list into the command
queue. Each client has a command queue of up to 100 commands. The module
services commands in the queue before the user defined command list. This
gives high priority to commands in the queue. Commands placed in the queue
through this mechanism must be defined in the module's command list. Under
normal command list execution, the module will only execute commands with the
Enable parameter set to one or two. If the value is set to zero, the command is
skipped. Commands may be placed in the command queue with an Enable
parameter set to zero using this feature. These commands can then be executed
using the command control blocks.

One to six commands can be placed in the command queue with a single
request. The format of the block is displayed below:

Word Description

0 Command queue block identification code of 5001 to 5006.
1

2

3

4

5

This word contains the index in the command list for the first command to be
entered into the command queue.

This word contains the index in the command list for the second command to be
entered into the command queue.

This word contains the index in the command list for the third command to be
entered into the command queue.

This word contains the index in the command list for the fourth command to be
entered into the command queue.

This word contains the index in the command list for the fifth command to be
entered into the command queue.

ProSoft Technology, Inc. Page 63 of 82
September 4, 2008

MVI56-BDW ♦ ControlLogix Platform Reference
BARDAC Drive Web Interface

Word Description

6

7 Client index used with the block. This parameter has a value from 0 to 3.
8 to 247 Spare

This word contains the index in the command list for the sixth command to be
entered into the command queue.

The last digit in the block code defines the number of commands to process in
the block. For example, a block code of 5003 contains 3 command indexes that
are to be placed in the command queue. The Command index parameters in the
block have a range of 0 to 99 and correspond to the module's command list
entries.

The module responds to a command control block with a block containing the
number of commands added to the command queue for the port. The format of
the block is displayed below:

Word Description

0 Reserved
1 This word contains the next write block identification code.
2

3 Client index used with the block. This parameter has a value from 0 to 3.
4 to 248 Spare
249 This word contains the block 5001 to 5006 requested by the processor.

This word contains the number of commands in the block placed in the
command queue.

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 below:

Offset Description Length

0 9998 1
1 to 247 Spare 247

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 below:

Offset Description Length

0 9999 1
1 to 247 Spare 247

Page 64 of 82 ProSoft Technology, Inc.

September 4, 2008

Reference MVI56-BDW ♦ ControlLogix Platform
BARDAC Drive Web Interface

5.2.3 Data Flow Between the MVI56-BDW Module and the

ControlLogix Processor

The following topics describe the flow of data between the two pieces of
hardware (ControlLogix processor and MVI56-BDW module) and other nodes on
the network under the module's only mode. The module contains four
independent clients. Each client generates messages that are passed to
BARDAC-DW compatible drives for monitoring or control.

Client Driver

In the client driver, the MVI56-BDW module is responsible for issuing read (get)
or write (set) commands to servers on the network. These commands are user
configured in the module via the Client Command List received from the module's
configuration file (BARDACDW.CFG) or issued directly from the ControlLogix
processor (event command control). Command status is returned to the
processor for each individual command in the command list status block. The
location of this status block in the module's internal database is user defined. The
following flow chart and associated table describe the flow of data into and out of
the module.

Step Description

1

The client driver obtains configuration data from the BARDACDW.CFG file when the
module restarts. The configuration data obtained includes the timeout parameters and
the Command List. These values are used by the driver to determine the type of
commands to be issued to the other nodes on the network.

ProSoft Technology, Inc. Page 65 of 82
September 4, 2008

MVI56-BDW ♦ ControlLogix Platform Reference
BARDAC Drive Web Interface

Step Description

2

After configuration, the client driver begins transmitting read and/or write commands to
the other nodes on the network. If writing data to another node, the data for the write
command is obtained from the module's internal database to build the command.

3

Presuming successful processing by the node specified in the command, a response
message is received into the client driver for processing.

4

Data received from the node on the network is passed into the module's internal
database, assuming a read command.

5

Status data is returned to the ControlLogix processor for the client and a Command List
error table can be established in the module's internal database.

Client Command List

In order for the client to function, the module's Client Command Lists must be
defined. Up to 100 individual entries can be defined for each of the four clients,
with each entry containing the information required to construct a valid command.
This includes the following:

 Command enable mode ((0) disabled, (1) continuous or (2) conditional)
 IP address and service port to connect to on the remote server
 Command Type - Read or Write
 Database Source and Destination Register Address - Determines where data

will be placed and/or obtained

As the list is read in from the configuration file and as the commands are
processed, an error value is maintained in the module for each command. This
error list can be transferred to the processor. The errors generated by the module
are displayed below:

Standard BARDAC DW PL/X Series Errors

Code Description

0xA501 GET to invalid PIN
0xA702 SET to invalid PIN
0xA703 SET to read-only PIN
0xA704 SET to "restricted in run" PIN
0xA705 SET with out-of-range data
0xyy06 Setup source with invalid PIN
0xyy07 Setup source with invalid index
0xyy08 Setup destination with invalid PIN
0xyy09 Setup destination with invalid index
0xFFFD Device not ready (initializing)
0xFFFE Device lock timeout (serious problem with device)
0xFFFF Unable to obtain device lock (device servicing other transaction)
Others Refer to drive manual or contact Bardac.

Standard BARDAC DW E-Series Errors

Code Description

1 Illegal function
2 Illegal data address

Page 66 of 82 ProSoft Technology, Inc.

September 4, 2008

Reference MVI56-BDW ♦ ControlLogix Platform
BARDAC Drive Web Interface

Code Description

3 Illegal data value
6 Busy, reject
7 Negative acknowledge
10 Read-only variable
11 Index out of range
12 Invalid data type
13 Invalid variable address
14 Invalid modbus address
15 Connection not setup
16 Write-only variable
17 EEPROM write fail
0xFFFD Device not ready (initializing)
0xFFFE Device lock timeout (serious problem with device)
0xFFFF Unable to obtain device lock (device servicing other transaction)
Others Refer to drive manual or contact Bardac.

UDP Error Codes

Code Description

0xFFDF Could not find IP on network
0xFFDE Buffer for UDP socket could not be allocated
0xFFDC Command response timeout

Command List Entry Errors

Code Description

40 Too few parameters for command
41 Invalid type code
42 Invalid internal database address
45 Invalid function code
46 Invalid swap code

5.3 Cable Connections

The MVI56-BDW module has the following communication connections on the
module:

 One Ethernet port (RJ45 connector)
 One RS-232 Configuration/Debug port (RJ45 connector)

5.3.1 Ethernet Connection

The MVI56-BDW module has an RJ45 port located on the front of the module
labeled "Ethernet", for use with the TCP/IP network. The module is connected to
the Ethernet network using an Ethernet cable between the module's Ethernet
port and an Ethernet switch or hub.

ProSoft Technology, Inc. Page 67 of 82
September 4, 2008

MVI56-BDW ♦ ControlLogix Platform Reference
BARDAC Drive Web Interface

Note: Depending on hardware configuration, you may see more than one RJ45 port on the
module. The Ethernet port is labeled "Ethernet".
Warning: The MVI56-BDW module is NOT compatible with Power Over Ethernet (IEEE802.3af /
IEEE802.3at) networks. Do NOT connect the module to Ethernet devices, hubs, switches or
networks that supply AC or DC power over the Ethernet cable. Failure to observe this precaution
may result in damage to hardware, or injury to personnel.
Important: The module requires a static (fixed) IP address that is not shared with any other device
on the Ethernet network. Obtain a list of suitable IP addresses from your network administrator
BEFORE configuring the Ethernet port on this module.

Ethernet Port Configuration - wattcp.cfg

The wattcp.cfg file must be set up properly in order to use a TCP/IP network
connection. You can view the current network configuration using an ASCII
terminal by selecting "@" (Network Menu) and "V" (View) options when
connected to the Debug port.

# WATTCP.CFG FILE:
# ProSoft Technology.
my_ip=192.168.0.100
# Default class 3 network mask
netmask=255.255.255.0
# The gateway I wish to use
gateway=192.168.0.1

5.3.2 RS-232 Configuration/Debug Port

This port is physically an RJ45 connection. An RJ45 to DB-9 adapter cable is
included with the module. This port permits a 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:

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 82 ProSoft Technology, Inc.

September 4, 2008

Reference MVI56-BDW ♦ ControlLogix Platform
BARDAC Drive Web Interface

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

4 When you have verified that the driver is not being browsed, go to

Communications>Configure Drivers

You may see something like this:

or the icons.

ProSoft Technology, Inc. Page 69 of 82
September 4, 2008

MVI56-BDW ♦ ControlLogix Platform Reference
BARDAC Drive Web Interface

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.

5.3.3 DB9 to RJ45 Adaptor (Cable 14)

Page 70 of 82 ProSoft Technology, Inc.

September 4, 2008

Reference MVI56-BDW ♦ ControlLogix Platform
BARDAC Drive Web Interface

5.4 MVI56-BDW Status Data Definition

This section contains a description of the members present in the BDDWInStat
object. This data is transferred from the module to the processor as part of each
read block.

Offset Content Description

202 Program Scan Count This value is incremented each time a complete program cycle occurs in

the module.

203 Read Block Count This field contains the total number of read blocks transferred from the

module to the processor.

204 Write Block Count This field contains the total number of write blocks transferred from the

processor to the module.

205 Parse Block Count This field contains the total number of blocks successfully parsed that

were received from the processor.

206 Command Event Block

Count

207 Command Block Count This field contains the total number of command blocks received from the

208 Error Block Count This field contains the total number of block errors recognized by the

209 Client 0 Cmd Request This value is incremented each time a command request is issued.
210 Client Cmd Response This value is incremented each time a command response is received.
211 Client Cmd Error This value is incremented each time an error message is received from a

212 Client Request Count This value is incremented each time a request message is issued.
213 Client Response Count This value is incremented each time a response message is received.
214 Client Error Sent Count This value is incremented each time an error is sent from the client.
215 Client Error Received Count This value is incremented each time an error is received from a remote

216 Client Cfg Error Word This word contains a bit map that defines configuration errors in the

217 Client Current Error Code This value corresponds to the current error code for the client.
218 Client Last Error Code This value corresponds to the last error code recorded for the client.
219 Client 1 Cmd Request This value is incremented each time a command request is issued.
220 Client Cmd Response This value is incremented each time a command response is received.
221 Client Cmd Error This value is incremented each time an error message is received from a

222 Client Request Count This value is incremented each time a request message is issued.
223 Client Response Count This value is incremented each time a response message is received.
224 Client Error Sent Count This value is incremented each time an error is sent from the client.
225 Client Error Received Count This value is incremented each time an error is received from a remote

226 Client Cfg Error Word This word contains a bit map that defines configuration errors in the

227 Client Current Error Code This value corresponds to the current error code for the client.
228 Client Last Error Code This value corresponds to the last error code recorded for the client.
229 Client 2 Cmd Request This value is incremented each time a command request is issued.

This field contains the total number of comman d event blocks received
from the processor.

processor.

module.

remote unit or a local error is generated for a command.

unit.

configuration file for the client.

remote unit or a local error is generated for a command.

unit.

configuration file for the client.

ProSoft Technology, Inc. Page 71 of 82
September 4, 2008

MVI56-BDW ♦ ControlLogix Platform Reference
BARDAC Drive Web Interface

Offset Content Description

230 Client Cmd Response This value is incremented each time a command response is received.
231 Client Cmd Error This value is incremented each time an error message is received from a

remote unit or a local error is generated for a command.
232 Client Request Count This value is incremented each time a request message is issued.
233 Client Response Count This value is incremented each time a response message is received.
234 Client Error Sent Count This value is incremented each time an error is sent from the client.
235 Client Error Received Count This value is incremented each time an error is received from a remote

unit.
236 Client Cfg Error Word This word contains a bit map that defines configuration errors in the

configuration file for the client.
237 Client Current Error Code This value corresponds to the current error code for the client.
238 Client Last Error Code This value corresponds to the last error code recorded for the client.
239 Client 3 Cmd Request This value is incremented each time a command request is issued.
240 Client Cmd Response This value is incremented each time a command response is received.
241 Client Cmd Error This value is incremented each time an error message is received from a

remote unit or a local error is generated for a command.
242 Client Request Count This value is incremented each time a request message is issued.
243 Client Response Count This value is incremented each time a response message is received.
244 Client Error Sent Count This value is incremented each time an error is sent from the client.
245 Client Error Received Count This value is incremented each time an error is received from a remote

unit.
246 Client Cfg Error Word This word contains a bit map that defines configuration errors in the

configuration file for the client.
247 Client Current Error Code This value corresponds to the current error code for the client.
248 Client Last Error Code This value corresponds to the last error code recorded for the client.

Page 72 of 82 ProSoft Technology, Inc.

September 4, 2008

Support, Service & Warranty MVI56-BDW ♦ ControlLogix Platform
BARDAC Drive Web Interface

6 Support, Service & Warranty

In This Chapter

 How to Contact Us: Technical Support.................................................. 73

 Return Material Authorization (RMA) Policies and Conditions............... 74

 LIMITED WARRANTY........................................................................... 76

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 Module Operation
o Configuration/Debug status information
o LED patterns

2 Information about the processor and user data files as viewed through and

LED patterns on the processor.

3 Details about the serial devices interfaced, if any.

6.1 How to Contact Us: Technical Support

Internet Web Site: http://www.prosoft-technology.com/support

(http://www.prosoft-technology.com/support)
E-mail address: [e-mail]

(mailto:[e-mail])

Asia Pacific

+603.7724.2080, [e-mail]
(mailto:[e-mail])

Languages spoken include: Chinese, English

Europe (location in Toulouse, France)

+33 (0) 5.34.36.87.20, [e-mail]
(mailto:[e-mail])

Languages spoken include: French, English

ProSoft Technology, Inc. Page 73 of 82
September 4, 2008

MVI56-BDW ♦ ControlLogix Platform Support, Service & Warranty
BARDAC Drive Web Interface

North America/Latin America (excluding Brasil) (location in California)

+1.661.716.5100, [e-mail] (mailto:support@prosoft­technology.com)

Languages spoken include: English, Spanish

For technical support calls within the United States, an after-hours answering
system allows pager access to one of our qualified technical and/or application
support engineers at any time to answer your questions.

Brasil (location in Sao Paulo)

[phone] , [e-mail] (mailto:eduardo@prosoft­technology.com)

Languages spoken include: Portuguese, English

6.2 Return Material Authorization (RMA) Policies and Conditions

The following RMA Policies and Conditions (collectively, "RMA Policies") apply to
any returned Product. These RMA Policies are subject to change by ProSoft
without notice. For warranty information, see "Limited Warranty". In the event of
any inconsistency between the RMA Policies and the Warranty, the Warranty
shall govern.

6.2.1 All Product Returns:

a) In order to return a Product for repair, exchange or otherwise, the

Customer must obtain a Returned Material Authorization (RMA) number
from ProSoft and comply with ProSoft shipping instructions.

b) In the event that the Customer experiences a problem with the Product for

any reason, Customer should contact ProSoft Technical Support at one of
the telephone numbers listed above (page 73). 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 74 of 82 ProSoft Technology, Inc.

September 4, 2008

Support, Service & Warranty MVI56-BDW ♦ ControlLogix Platform
BARDAC Drive Web Interface

6.2.2 Procedures for Return of Units Under Warranty:

A Technical Support Engineer must approve the return of Product under
ProSoft's Warranty:

a) A replacement module will be shipped and invoiced. A purchase order will

be required.

b) Credit for a product under warranty will be issued upon receipt of

authorized product by ProSoft at designated location referenced on the
Return Material Authorization.

6.2.3 Procedures for Return of Units Out of Warranty:

a) Customer sends unit in for evaluation
b) If no defect is found, Customer will be charged the equivalent of $100

USD, plus freight charges, duties and taxes as applicable. A new
purchase order will be required.

c) If unit is repaired, charge to Customer will be 30% of current list price

(USD) plus freight charges, duties and taxes as applicable. A new
purchase order will be required or authorization to use the purchase order
submitted for evaluation fee.

The following is a list of non-repairable units:

o 3150 - All
o 3750
o 3600 - All
o 3700
o 3170 - All
o 3250
o 1560 - Can be repaired, only if defect is the power supply
o 1550 - Can be repaired, only if defect is the power supply
o 3350
o 3300
o 1500 - All

6.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 76)". 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. Page 75 of 82
September 4, 2008

MVI56-BDW ♦ ControlLogix Platform Support, Service & Warranty
BARDAC Drive Web Interface

6.3 LIMITED WARRANTY

This Limited Warranty ("Warranty") governs all sales of hardware, software and
other products (collectively, "Product") manufactured and/or offered for sale by
ProSoft, and all related services provided by ProSoft, including maintenance,
repair, warranty exchange, and service programs (collectively, "Services"). By
purchasing or using the Product or Services, the individual or entity purchasing or
using the Product or Services ("Customer") agrees to all of the terms and
provisions (collectively, the "Terms") of this Limited Warranty. All sales of
software or other intellectual property are, in addition, subject to any license
agreement accompanying such software or other intellectual property.

6.3.1 What Is Covered By This Warranty

a) Warranty On New Products: ProSoft warrants, to the original purchaser,

that the Product that is the subject of the sale will (1) conform to and
perform in accordance with published specifications prepared, approved
and issued by ProSoft, and (2) will be free from defects in material or
workmanship; provided these warranties only cover Product that is sold as
new. This Warranty expires three years from the 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.

6.3.2 What Is Not Covered By This Warranty

a) ProSoft makes no representation or warranty, expressed or implied, that

the operation of software purchased from 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 76 of 82 ProSoft Technology, Inc.

September 4, 2008

Support, Service & Warranty MVI56-BDW ♦ ControlLogix Platform
BARDAC Drive Web Interface

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.

6.3.3 Disclaimer Regarding High Risk Activities

Product manufactured or supplied by ProSoft is not fault tolerant and is not
designed, manufactured or intended for use in hazardous environments requiring
fail-safe performance including and without limitation: the operation of nuclear
facilities, aircraft navigation of communication systems, air traffic control, direct
life support machines or weapons systems in which the failure of the product
could lead directly or indirectly to death, personal injury or severe physical or
environmental damage (collectively, "high risk activities"). ProSoft specifically
disclaims any express or implied warranty of fitness for high risk activities.

6.3.4 Intellectual Property Indemnity

Buyer shall indemnify and hold harmless ProSoft and its employees from and
against all liabilities, losses, claims, costs and expenses (including attorney's
fees and expenses) related to any claim, investigation, 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. Page 77 of 82
September 4, 2008

MVI56-BDW ♦ ControlLogix Platform Support, Service & Warranty
BARDAC Drive Web Interface

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.

6.3.5 Disclaimer of all Other Warranties

The Warranty set forth in What Is Covered By This Warranty (page 76) 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.

6.3.6 Limitation of Remedies **

In no event will ProSoft or its Dealer be liable for any special, incidental or
consequential damages based on breach of warranty, breach of contract,
negligence, strict tort or any other legal theory. Damages that ProSoft or its
Dealer will not be responsible for included, but are not limited to: Loss of profits;
loss of savings or revenue; loss of use of the product or any associated
equipment; loss of data; cost of capital; cost of any substitute equipment,
facilities, or services; downtime; the claims of third parties including, customers of
the Purchaser; and, injury to property.

** Some areas 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 78 of 82 ProSoft Technology, Inc.

September 4, 2008

Support, Service & Warranty MVI56-BDW ♦ ControlLogix Platform
BARDAC Drive Web Interface

6.3.7 Time Limit for Bringing Suit

Any action for breach of warranty must be commenced within 39 months
following shipment of the Product.

6.3.8 No Other Warranties

Unless modified in writing and signed by both parties, this Warranty is
understood to be the complete and exclusive agreement between the parties,
suspending all oral or written prior agreements and all other communications
between the parties relating to the subject matter of this Warranty, including
statements made by salesperson. No employee of ProSoft or any other party is
authorized to make any warranty in addition to those made in this Warranty. The
Customer is warned, therefore, to check this Warranty carefully to see that it
correctly reflects those terms that are important to the Customer.

6.3.9 Allocation of Risks

This Warranty allocates the risk of product failure between ProSoft and the
Customer. This allocation is recognized by both parties and is reflected in the
price of the goods. The Customer acknowledges that it has read this Warranty,
understands it, and is bound by its Terms.

6.3.10 Controlling Law and Severability

This Warranty shall be governed by and construed in accordance with the laws of
the United States and the domestic laws of the State of California, without
reference to its conflicts of law provisions. If for any reason a court of competent
jurisdiction finds any provisions of this Warranty, or a portion thereof, to be
unenforceable, that provision shall be enforced to the maximum extent
permissible and the remainder of this Warranty shall remain in full force and
effect. Any cause of action with respect to the Product or Services must be
instituted in a court of competent jurisdiction in the State of California.

ProSoft Technology, Inc. Page 79 of 82
September 4, 2008

MVI56-BDW ♦ ControlLogix Platform Support, Service & Warranty
BARDAC Drive Web Interface

Page 80 of 82 ProSoft Technology, Inc.

September 4, 2008

Index MVI56-BDW ♦ ControlLogix Platform
BARDAC Drive Web Interface

F

Features and Benefits • 55

Index

Functional Overview • 7, 57
Functional Specifications • 56

G

A

Adding a Module • 31
Adding a Project • 31
All Product Returns: • 74
Allocation of Risks • 79

B

Backplane Control Object • 26
Backplane Data Transfer • 58
Battery Life Advisory • 3

C

Cable Connections • 67
Clearing a Fault Condition • 53
Client Command List • 66
Client Driver • 65
Cold Boot • 64
Command Control • 63
Command Control Blocks • 62
Command List Entry Errors • 67
Command List Overview • 36
Commands Supported by the Module • 37
Comment Entries • 33
Configuring RSLinx • 16
Connect your PC to the Module • 19
Connect your PC to the Processor • 14
Controlling Law and Severability • 79

D

Data Flow Between the MVI56-BDW Module and the

ControlLogix Processor • 65
Database View Menu • 47
DB9 to RJ45 Adaptor (Cable 14) • 70
Diagnostics and Troubleshooting • 7, 41
Disabling the RSLinx Driver for the Com Port on the

PC • 68
Disclaimer of all Other Warranties • 78
Disclaimer Regarding High Risk Activities • 77
Displaying the Current Page of Registers Again • 48
Download the Project to the Module • 37
Download the Sample Program to the Processor • 18

E

Ethernet Connection • 67
Ethernet LED Indicators • 53
Ethernet Port Configuration - wattcp.cfg • 68
Event Command • 62
Event Command Data • 29
Exiting the Program • 47

General Concepts • 57
General Specifications • 55
Guide to the MVI56-BDW User Manual • 7

H

Hardware Specifications • 56
How to Contact Us

Technical Support • 73, 74

I

Initialize Output Data • 61
Install ProSoft Configuration Builder Software • 10
Install the Module in the Rack • 12
Installing and Configuring the Module • 21
Intellectual Property Indemnity • 77

K

Keystrokes • 44

L

Ladder Logic • 39
LED Status Indicators • 7, 52
Limitation of Remedies ** • 78
LIMITED WARRANTY • 75, 76

M

Main Logic Loop • 58
Main Menu • 44
Master Command Error List Menu • 49
Master Command List Menu • 50
Modifying the Configuration File • 29
Module Configuration • 21
Module Data Object (BDDWModuleDef) • 26
Module Entries • 33
Module Power Up • 57
Moving Back Through 5 Pages of Registers • 48
MVI56-BDW Communication Module Configuration •

34

MVI56-BDW Status Data Definition • 71

N

Navigation • 43
Network Menu • 46, 51
No Other Warranties • 79
Normal Data Transfer • 60

O

Open the Sample Ladder Logic • 14
Opening the Command Error List Menu • 45
Opening the Command List Menu • 45
Opening the Database Menu • 45

ProSoft Technology, Inc. Page 81 of 82
September 4, 2008

MVI56-BDW ♦ ControlLogix Platform Index
BARDAC Drive Web Interface

Opening the Network Menu • 46

P

Package Contents • 10
Pinouts • 2, 67, 70
Please Read This Notice • 2
Printing a Configuration File • 33
Procedures for Return of Units Out of Warranty: • 75
Procedures for Return of Units Under Warranty: • 75
Product Specifications • 7, 55
ProSoft Configuration Builder • 29
ProSoft® Product Documentation • 3
Purchasing Warranty Extension: • 75

R

Read Block • 60
Reading Status Data from the Module • 41
Redisplaying the Current Page • 49, 50
Reference • 7, 55
Required Hardware • 41
Resetting diagnostic data • 46
Return Material Authorization (RMA) Policies and

Conditions • 74
Returning to the Main Menu • 49, 50, 51
RS-232 Configuration/Debug Port • 68

S

Select the Slot Number for the Module • 16
Set Module Parameters • 21, 32
Set Up the Project • 30
Setting Jumpers • 12
Skipping 500 Registers of Data • 48
Standard BARDAC DW E-Series Errors • 66
Standard BARDAC DW PL/X Series Errors • 66
Start Here • 7, 9
Status Data • 27
Support, Service & Warranty • 7, 73
System Requirements • 9

Viewing Block Transfer Statistics • 44
Viewing Client Configuration • 46
Viewing Client Status • 46
Viewing Data in ASCII (Text) Format • 48
Viewing Data in Decimal Format • 48
Viewing Data in Floating Point Format • 48
Viewing Data in Hexadecimal Format • 48
Viewing Module Configuration • 45
Viewing Register Pages • 47
Viewing the Next 100 Registers of Data • 48
Viewing the Next 20 Commands • 49
Viewing the Next 50 Commands • 50
Viewing the Next Page of Commands • 49, 50
Viewing the Previous 100 Registers of Data • 48
Viewing the Previous 20 Commands • 49
Viewing the Previous 50 Commands • 50
Viewing the Previous Page of Commands • 49, 50
Viewing the WATTCP.CFG file on the module • 51
Viewing Version Information • 46

Warm Boot • 64
Warm Booting the Module • 46
Warnings • 2
What Is Covered By This Warranty • 76, 78
What Is Not Covered By This Warranty • 76
Write Block • 61

Your Feedback Please • 3

V

W

Y

T

The Configuration/Debug Menu • 42
Time Limit for Bringing Suit • 79
To Determine the Firmware Version of your Processor

• 15

Transferring the Configuration File from MVI56 module

to PC • 45
Transferring the Configuration File from PC to MVI56

module • 45
Transferring WATTCP.CFG to the module • 51
Transferring WATTCP.CFG to the PC • 51
Troubleshooting • 54

U

UDP Error Codes • 67
User Data Objects • 27
Using the Diagnostic Window in ProSoft Configuration

Builder • 42

Page 82 of 82 ProSoft Technology, Inc.

September 4, 2008