ProSoft Technology inRax MVI56-DH485R User Manual

Download

MVI56-DH485R

ControlLogix Platform

DH485 Interface Module for Remote Chassis

August 27, 2009

USER MANUAL

Important Installation Instructions

Power, Input and Output (I/O) wiring must be in accordance with Class I, Division 2 wiring methods, Article 501-4 (b) of the National Electrical Code, NFPA 70 for installation in the U.S., or as specified in Section 18-1J2 of the Canadian Electrical Code for installations in Canada, and in accordance with the authority having jurisdiction. The following warnings must be heeded:

A WARNING - EXPLOSION HAZARD - SUBSTITUTION OF COMPONENTS MAY IMPAIR SUITABILITY FOR

CLASS I, DIV. 2;

B WARNING - EXPLOSION HAZARD - WHEN IN HAZARDOUS LOCATIONS, TURN OFF POWER BEFORE

REPLACING OR WIRING MODULES

C WARNING - EXPLOSION HAZARD - DO NOT DISCONNECT EQUIPMENT UNLESS POWER HAS BEEN

SWITCHED OFF OR THE AREA IS KNOWN TO BE NONHAZARDOUS.

D THIS DEVICE SHALL BE POWERED BY CLASS 2 OUTPUTS ONLY.

MVI (Multi Vendor Interface) Modules

WARNING - EXPLOSION HAZARD - DO NOT DISCONNECT EQUIPMENT UNLESS POWER HAS BEEN SWITCHED OFF OR THE AREA IS KNOWN TO BE NON-HAZARDOUS.

AVERTISSEMENT - RISQUE D'EXPLOSION - AVANT DE DÉCONNECTER L'EQUIPMENT, COUPER LE COURANT OU S'ASSURER QUE L'EMPLACEMENT EST DÉSIGNÉ NON DANGEREUX.

CL I Div 2 GPs A, B, C, D

Temp Code T5

II 3 G

Ex nA IIC T5 X

0° C <= Ta <= 60° C

II - Equipment intended for above ground use (not for use in mines).

3 - Category 3 equipment, investigated for normal operation only.

G - Equipment protected against explosive gasses.

Warnings

North America Warnings

A Warning - Explosion Hazard - Substitution of components may impair suitability for Class I, Division 2. B Warning - Explosion Hazard - When in Hazardous Locations, turn off power before replacing or rewiring

modules. Warning - Explosion Hazard - Do not disconnect equipment unless power has been switched off or the area is known to be nonhazardous.

C Suitable for use in Class 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:

ANSI / ISA ISA 12.12.01 Class I Division 2, GPs A, B, C, D CSA/cUL C22.2 No. 213-1987 CSA CB Certified IEC61010 ATEX EN60079-0 Category 3, Zone 2

EN60079-15

243333

Battery Life Advisory

MVI46, MVI56, MVI69 and MVI71 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.

Your Feedback Please

We always want you to feel that you made the right decision to use our products. If you have suggestions, comments, compliments or complaints about the product, documentation, or support, please write or call us.

ProSoft Technology 5201 Truxtun Ave., 3rd Floor Bakersfield, CA 93309 +1 (661) 716-5100 +1 (661) 716-5101 (Fax) www.prosoft-technology.com support@prosoft-technology.com

MVI56-DH485R User Manual August 27, 2009

ProSoft Technology Technology, Inc. All other brand or product names are or may be trademarks of, and are used to identify products and services of, their respective owners.

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

ProSoft Technology® Product Documentation

In an effort to conserve paper, ProSoft Technology no longer includes printed manuals with our product shipments. User Manuals, Datasheets, Sample Ladder Files, and Configuration Files are provided on the enclosed CD-ROM, and are available at no charge from our web site: www.prosoft-technology.com

Printed documentation is available for purchase. Contact ProSoft Technology for pricing and availability.

North America: +1.661.716.5100

Asia Pacific: +603.7724.2080

Europe, Middle East, Africa: +33 (0) 5.3436.87.20

Latin America: +1.281.298.9109

Contents MVI56-DH485R ♦ ControlLogix Platform User Manual DH485 Interface Module for Remote Chassis

Contents

Important Installation Instructions .......................................................................................................2

MVI (Multi Vendor Interface) Modules ................................................................................................2

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

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

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

ProSoft Technology® Product Documentation....................................................................................4

Guide to the MVI56-DH485R User Manual 7

1 Start Here 9

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

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

1.3 Install ProSoft Configuration Builder Software........................................................11

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

1.5 Install the Module in the Rack .................................................................................13

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

1.7 Download the Sample Program to the Processor................................................... 15

1.8 Connect your PC to the Module ..............................................................................18

2 Module Configuration 19

2.1 Using ProSoft Configuration Builder .......................................................................19

2.2 [Module]...................................................................................................................24

2.3 [DH485 Port x].........................................................................................................26

2.4 [DH485 Port x Commands] .....................................................................................29

2.5 [DH485 Port x Maps]............................................................................................... 32

2.6 Download the Project to the Module .......................................................................34

3 Ladder Logic 35

3.1 Module Data Object (DH485ModuleDef) ................................................................35

3.2 Adding the Module to an Existing Project ...............................................................38

4 Diagnostics and Troubleshooting 41

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

4.2 Configuration/Debug Port........................................................................................ 41

4.3 LED Status Indicators..............................................................................................53

5 Reference 55

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

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

5.3 DH485 Communication Ports..................................................................................75

5.4 MVI56-DH485R Status Data ...................................................................................81

5.5 Maximum Element Counts For Read/Write Commands......................................... 84

ProSoft Technology, Inc. Page 5 of 97 August 27, 2009

MVI56-DH485R ♦ ControlLogix Platform Contents DH485 Interface Module for Remote Chassis User Manual

5.6 Command Definition Form...................................................................................... 86

5.7 File Override Map Definition Form.......................................................................... 87

6 Support, Service & Warranty 89

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

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

6.3 LIMITED WARRANTY............................................................................................ 91

Index 95

Page 6 of 97 ProSoft Technology, Inc. August 27, 2009

Start Here MVI56-DH485R ♦ ControlLogix Platform User Manual DH485 Interface Module for Remote Chassis

Guide to the MVI56-DH485R User Manual

Function Section to Read Details

Introduction (Must Do)

Verify Communication, Diagnostic and Troubleshooting

Reference Product Specifications Functional Overview

Support, Service, and Warranty

Index

→

Start Here (page 9)

Verifying Communication (page 53)

Diagnostics and Troubleshooting (page

41)

Reference (page 55) Functional Overview

(page 57) Product

Specifications (page

55)

Support, Service and Warranty (page

89)

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 97 August 27, 2009

MVI56-DH485R ♦ ControlLogix Platform Start Here DH485 Interface Module for Remote Chassis User Manual

Page 8 of 97 ProSoft Technology, Inc.

August 27, 2009

Start Here MVI56-DH485R ♦ ControlLogix Platform User Manual DH485 Interface Module for Remote Chassis

1 Start Here

In This Chapter

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



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

 Install ProSoft Configuration Builder Software.......................................11



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

 Install the Module in the Rack ...............................................................13



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

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



Connect your PC to the Module ............................................................18

To get the most benefit from this User Manual, you should have the following skills:

 Rockwell Automation

ladder logic, and transfer the ladder logic to the processor

 Microsoft Windows: install and launch programs, execute menu commands,

navigate dialog boxes, and enter data.

 Hardware installation and wiring: install the module, and safely connect

and ControlLogix devices to a power source and to the MVI56-DH485R module’s application port(s).

RSLogix™ software: launch the program, configure

Caution: You must be able to complete the application without exposing personnel or

equipment to unsafe or inappropriate working conditions.

1.1 System Requirements

The MVI56-DH485R 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-DH485R 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

recommended

ProSoft Technology, Inc. Page 9 of 97 August 27, 2009

II 450 MHz minimum. Pentium III 733 MHz (or better)

MVI56-DH485R ♦ ControlLogix Platform Start Here DH485 Interface Module for Remote Chassis User Manual

 Supported operating systems:

o Microsoft Windows XP Professional with Service Pack 1 or 2 o Microsoft Windows 2000 Professional with Service Pack 1, 2, or 3 o Microsoft Windows Server 2003

 128 Mbytes of RAM minimum, 256 Mbytes of RAM recommended  100 Mbytes of free hard disk space (or more based on application

requirements)

 256-color VGA graphics adapter, 800 x 600 minimum resolution (True Color

1024 × 768 recommended)

 CD-ROM drive  ProSoft Configuration Builder, HyperTerminal or other terminal emulator

program.

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

1.2 Package Contents

The following components are included with your MVI56-DH485R 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 Cable

3 Cable

2 Adapter 1454-9F

MVI56DH485R Module

ProSoft Solutions CD

MVI56-DH485R DH485 Interface Module for Remote Chassis

Cable #15, RS232 Null Modem

Cable #14, RJ45 to DB9 Male Adapter cable

For RS232 Connection to the CFG Port

For DB9 Connection to Module’s Port

Two Adapters, DB9 Female to Screw Terminal. For RS422 or RS485 Connections to Port 1 and 2 of the Module

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

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

Page 10 of 97 ProSoft Technology, Inc.

August 27, 2009

Start Here MVI56-DH485R ♦ ControlLogix Platform User Manual DH485 Interface Module for Remote Chassis

1.3 Install ProSoft Configuration Builder Software

You must install the ProSoft Configuration Builder (PCB) software in order to configure the 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 D

Configuration Builder.

3 Choose "S 4 Save the file to your Windows Desktop, so that you can find it easily when

you have finished downloading.

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

instructions on your screen to install the program.

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

To install ProSoft Configuration Builder from the Product CD-ROM

1 Insert the ProSoft Solutions Product CD-ROM into the CD-ROM drive of your

PC. Wait for the startup screen to appear.

2 On the startup screen, click P

Windows Explorer file tree window.

3 Click to open the U

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

4 Double-click the S

"PCB_*.

software on your PC. The information represented by the "*" character in the file name is the PCB version number and, therefore, subject to change as new versions of PCB are released.

OWNLOAD HERE link to download the latest version of ProSoft

AVE" or "SAVE FILE" when prompted.

RODUCT DOCUMENTATION. This action opens an

TILITIES folder. This folder contains all of the applications

ETUPCONFIGURATIONTOOL folder, double-click the

EXE" file and follow the instructions on your screen to install the

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 97 August 27, 2009

MVI56-DH485R ♦ ControlLogix Platform Start Here DH485 Interface Module for Remote Chassis User Manual

1.4 Setting Jumpers

Changing from RS-232 to RS-485 requires that you change the jumper on the module to the appropriate settings. To do so, use a pair of needle-nose pliers to move the jumper shunt to the appropriate pins as shown in the following diagram:

Note: The RS-422 jumper setting shown in the diagram is not used with this module configuration.

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.

Page 12 of 97 ProSoft Technology, Inc.

August 27, 2009

Start Here MVI56-DH485R ♦ ControlLogix Platform User Manual DH485 Interface Module for Remote Chassis

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-DH485R module. Refer to your Rockwell Automation product documentation for installation instructions.

Warning: You must follow all safety instructions when installing this or any other electronic devices. Failure to follow safety procedures could result in damage to hardware or data, or even serious injury or death to personnel. Refer to the documentation for each device you plan to connect to verify that suitable safety procedures are in place before installing or servicing the device.

After you have checked the placement of the jumpers, insert MVI56-DH485R into the ControlLogix chassis. Use the same technique recommended by Rockwell Automation to remove and install ControlLogix modules.

Warning: When you insert or remove the module while backplane power is on, an electrical arc can occur. This could cause an explosion in hazardous location installations. Verify that power is removed or the area is non-hazardous before proceeding. Repeated electrical arcing causes excessive wear to contacts on both the module and its mating connector. Worn contacts may create electrical resistance that can affect module operation.

1 Turn power OFF. 2 Align the module with the top and bottom guides, and slide it into the rack

until the module is firmly against the backplane connector.

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.

ProSoft Technology, Inc. Page 13 of 97 August 27, 2009

MVI56-DH485R ♦ ControlLogix Platform Start Here DH485 Interface Module for Remote Chassis User Manual

5 Make a note of the slot location. You must identify the slot in which the

module is installed in order for the sample program to work correctly. Slot numbers are identified on the green circuit board (backplane) of the ControlLogix rack.

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-DH485R with other modules connected to the PCI bus, the peripheral modules will not have holding clips. Make sure all of the modules are aligned with their respective slots before you snap them into place.

1.6 Connect your PC to the ControlLogix Processor

There are several ways to establish communication between your PC and the ControlLogix processor. The following steps show how to establish communication through the serial interface. Refer to your Rockwell Automation documentation for information on other connection methods.

1 Connect the right-angle connector end of the cable to your controller at the

communications port.

Page 14 of 97 ProSoft Technology, Inc.

August 27, 2009

Start Here MVI56-DH485R ♦ ControlLogix Platform User Manual DH485 Interface Module for Remote Chassis

2 Connect the straight connector end of the cable to the serial port on your

computer.

1.7 Download the Sample Program to the Processor

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

1 If you are not already online with the processor, open the COMMUNICATIONS

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

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

box. Click the D

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

ProSoft Technology, Inc. Page 15 of 97 August 27, 2009

MVI56-DH485R ♦ ControlLogix Platform Start Here DH485 Interface Module for Remote Chassis User Manual

4 When the download is complete, RSLogix will open another confirmation

dialog box. If the keyswitch is in the REM position, click OK processor from P

ROGRAM mode to RUN mode.

to switch the

Note: If you receive an error message during these steps, refer to your RSLogix documentation to interpret and correct the error.

1.7.1 Configuring the RSLinx Driver for the PC COM Port

If RSLogix is unable to establish communication with the processor, follow these steps

1 Open RSL 2 Open the C

INX.

OMMUNICATIONS menu, and choose CONFIGURE DRIVERS.

This action opens the C

ONFIGURE DRIVERS dialog box.

Page 16 of 97 ProSoft Technology, Inc.

August 27, 2009

Start Here MVI56-DH485R ♦ ControlLogix Platform User Manual DH485 Interface Module for Remote Chassis

Note: If the list of configured drivers is blank, you must first choose and configure a driver from the Available Driver Types list. The recommended driver type to choose for serial communication with the processor is RS-232 DF1 DEVICES.

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

ONFIGURE ALLEN-BRADLEY DF1 COMMUNICATIONS DEVICE dialog box.

4 Click the A

UTO-CONFIGURE button. RSLinx will attempt to configure your

serial port to work with the selected driver.

5 When you see the message A

UTO CONFIGURATION SUCCESSFUL, click the OK

button to dismiss the dialog box.

Note: If the auto-configuration procedure fails, verify that the cables are connected correctly between the processor and the serial port on your computer, and then try again. If you are still unable to auto-configure the port, refer to your RSLinx documentation for further troubleshooting steps.

ProSoft Technology, Inc. Page 17 of 97 August 27, 2009

MVI56-DH485R ♦ ControlLogix Platform Start Here DH485 Interface Module for Remote Chassis User Manual

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

Page 18 of 97 ProSoft Technology, Inc.

August 27, 2009

Module Configuration MVI56-DH485R ♦ ControlLogix Platform User Manual DH485 Interface Module for Remote Chassis

2 Module Configuration

In This Chapter

 Using ProSoft Configuration Builder...................................................... 19



[Module].................................................................................................24

 [DH485 Port x].......................................................................................26



[DH485 Port x Commands]....................................................................29

 [DH485 Port x Maps] .............................................................................32



Download the Project to the Module...................................................... 34

This section contains the setup procedure, data, and ladder logic for successful application of the MVI56-DH485R module. Each step in the setup procedure is defined in order to simplify the use of the module.

2.1 Using 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.

2.1.1 Set Up the Project

To begin, start PROSOFT CONFIGURATION BUILDER (PCB).

ProSoft Technology, Inc. Page 19 of 97 August 27, 2009

MVI56-DH485R ♦ ControlLogix Platform Module Configuration DH485 Interface Module for Remote Chassis User Manual

If you have used other Windows configuration tools before, you will find the screen layout familiar. PCB’s window consists of a tree view on the left, and an information pane and a configuration pane on the right side of the window. When you first start PCB, the tree view consists of folders for D

EFAULT LOCATION, with a DEFAULT MODULE in the Default Location folder. The

EFAULT PROJECT and

following illustration shows the PCB window with a new project.

Page 20 of 97 ProSoft Technology, Inc.

August 27, 2009

Module Configuration MVI56-DH485R ♦ ControlLogix Platform User Manual DH485 Interface Module for Remote Chassis

Your first task is to add the MVI56-DH485R module to the project.

1 Use the mouse to select D

EFAULT MODULE in the tree view, and then click the

right mouse button to open a shortcut menu.

2 On the shortcut menu, choose C

HOOSE MODULE TYPE. This action opens the

CHOOSE MODULE TYPE dialog box.

3 In the P

S OK

RODUCT LINE FILTER area of the dialog box, select MVI56. In the

ELECT MODULE TYPE dropdown list, select MVI56-DH485R, and then click

to save your settings and return to the ProSoft Configuration Builder

window.

ProSoft Technology, Inc. Page 21 of 97 August 27, 2009

MVI56-DH485R ♦ ControlLogix Platform Module Configuration DH485 Interface Module for Remote Chassis User Manual

2.1.2 Set Module Parameters

The next task is to configure module parameters. Notice that the contents of the information pane and the configuration pane changed when you added the MVI56-DH485R 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 R

ENAME.

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

Configuring Module Parameters

1 Click on the plus sign next to the 2 Double-click the

icon to open the EDIT dialog box.

icon to expand module information.

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

changes in the right pane.

4 Click OK

to save your changes.

Page 22 of 97 ProSoft Technology, Inc.

August 27, 2009

Module Configuration MVI56-DH485R ♦ ControlLogix Platform User Manual DH485 Interface Module for Remote Chassis

Comment Entries

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

1 Select the M

ODULE icon, and then click the right mouse button to open a

shortcut menu.

2 On the shortcut menu, choose V

IEW CONFIGURATION window.

3 On the V

RINT. This action opens the PRINT dialog box.

4 On the P

IEW CONFIGURATION window, open the FILE menu, and choose

RINT dialog box, choose the printer to use from the dropdown list,

IEW CONFIGURATION. This action opens the

select printing options, and then click OK.

ProSoft Technology, Inc. Page 23 of 97 August 27, 2009

MVI56-DH485R ♦ ControlLogix Platform Module Configuration DH485 Interface Module for Remote Chassis User Manual

2.2 [Module]

This section provides the module with a unique name, identifies the method of failure for the communications for the module if the PLC is not in run, and describes how to initialize the module upon startup.

The following example shows a sample [Module] section:

Modify each of the parameters based on the needs of your application.

2.2.1 Module Name

0 to 80 characters This parameter assigns a name to the module that can be viewed using the

configuration/debug port. Use this parameter to identify the module and the configuration file.

2.2.2 Error / Status Pointer

-1 to 3999 Starting register location in virtual database for the error/status table. If a value of

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

Page 24 of 97 ProSoft Technology, Inc.

August 27, 2009

Module Configuration MVI56-DH485R ♦ ControlLogix Platform User Manual DH485 Interface Module for Remote Chassis

2.2.3 Read Register Start

Range 0 to 3999 This parameter specifies the starting register in the module where data will be

transferred from the module to the processor. Valid range for this parameter is 0 to 3999.

2.2.4 Read Register Count

Range 0 to 3999 This parameter specifies the number of registers to be transferred from the

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

2.2.5 Write Register Start

0 to 3999 This parameter specifies the starting register in the module where the data will be

transferred from the processor to the module.

2.2.6 Write Register Count

Range 0 to 3999 This parameter specifies the number of registers to transfer from the processor to

the module. Valid entry for this parameter is 0 to 3999.

2.2.7 Initialize Output Data

Yes or No This parameter determines if the output data for the module should be initialized

with values from the processor. If the value is set to No (0), the output data will be initialized to 0. If the value is set to Yes (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.

2.2.8 Failure Flag Count

0 through 65535 This parameter specifies the number of successive transfer errors that must

occur before halting communication on the application port(s). If the parameter is set to 0, the application port(s) will continue to operate under all conditions. If the value is set larger than 0 (1 to 65535), communications will cease if the specified number of failures occur.

ProSoft Technology, Inc. Page 25 of 97 August 27, 2009

MVI56-DH485R ♦ ControlLogix Platform Module Configuration DH485 Interface Module for Remote Chassis User Manual

2.3 [DH485 Port x]

General configuration information for the specified DH-485 port on the module

2.3.1 Baud Rate

Range 1200 to 19200 This is the baud rate to use for the DH485R network. Select one of the listed

baud rates.

2.3.2 Node Address

Range 0 to 31 This is the node address to be utilized by the DH-485 driver for this port on the

network. Enter a value not already used on the network in the range of 0 to 31. If a value of 255 is utilized or set by the module, the port is disabled. Note: All nodes on the network should be set to the lowest set of values in the range of 1 to 4).

2.3.3 Maximum Node Address

Range 0 to 31 Enter the maximum address that the initiator searches for before wrapping to

zero. The default is 31. This parameter should be set to the maximum node address set in the DH-485 network.

Page 26 of 97 ProSoft Technology, Inc.

August 27, 2009

Module Configuration MVI56-DH485R ♦ ControlLogix Platform User Manual DH485 Interface Module for Remote Chassis

2.3.4 Token Hold Factor

Range 0 to 31 Enter the number of transmissions (plus retries) that a node holding a token can

send onto the data link each time that it receives the token. Enter a value between 0 and 31. The default is 1.

2.3.5 Response Timeout

Range 1 to 50 This parameter sets the number of 100 millisecond time intervals to wait for a

response to a request from the module. If the module does not receive the response with in the time period specified, a timeout condition will be set for the command.

2.3.6 Status DB Offset

Range -1 to 3980 This parameter sets the location of the status data for the port in the module’s

internal database. If the parameter is set to -1, the data is not placed in the database. If a valid value is entered, the module’s status data will be placed in the database starting at the location indicated.

2.3.7 Command Error DB Offset

Range -1 to 3900 This parameter sets the location of the command error list data for the port in the

module's internal database. If the parameter is set to -1, the data is not placed in the database. If a valid value is entered, the module's error list data will be placed in the database starting at the location indicated.

2.3.8 CIF Read DB Offset

Range -1 to 7500 (Only even values) This parameter sets the starting byte location in the module's database where the

CIF file Read will be placed. This data is passed from CIF memory area to the set location in the module's database. If this parameter is set to -1, no CIF read data will be utilized. When the CIF Read Area is disabled (CIF Read DB Offset =

-1) or CIF Read Count = 0, the Debug menu shows this parameter as 65535.

2.3.9 CIF Read Count

Range 0 to 242 This parameters sets the number of bytes to transfer from the CIF file to the

database. The CIF write count will be calculated as (244 - CIF Read Count)

ProSoft Technology, Inc. Page 27 of 97 August 27, 2009

MVI56-DH485R ♦ ControlLogix Platform Module Configuration DH485 Interface Module for Remote Chassis User Manual

2.3.10 CIF Write DB Offset

Range -1 to 7500 (Only even values) This parameter sets the starting byte location in the module's database where the

CIF file Write data will be read from. This data is passed to the CIF memory area from the set location in the module's database. If this parameter is set to -1, no CIF write data will be utilized. When the CIF Write Area is disabled (CIF Write DB Offset = -1) or CIF Write Count = 0, the Debug menu shows this parameter as

65535.

2.3.11 First File

Range 0 to 255 This parameter sets the file number for the first file to be emulated by the

module.

2.3.12 File Size

Range 1 to 1000 This parameter sets the word size of all the files emulated in the module

2.3.13 File Offset

Range 1 to 999 This parameter sets the word offset into the module’s database where the file

emulation will start.

2.3.14 Min Command Delay

Range 0 to 10000 This parameter sets the minimum number of milliseconds to wait before issuing

each command. This parameter is utilized to keep the network from being flooded with requests from the module.

Page 28 of 97 ProSoft Technology, Inc.

August 27, 2009

Module Configuration MVI56-DH485R ♦ ControlLogix Platform User Manual DH485 Interface Module for Remote Chassis

2.4 [DH485 Port x Commands]

The [DH485 Port x Commands] section for each port defines the commands to be issued by the module to other devices on the network. These commands can be used for data collection and/or control.

2.4.1 Command List Overview

In order to interface the MVI56-DH485R module to act as a master device, you must construct a command list for each port. The commands in the list specify the node to be addressed, the function to be performed (read or write), the data area in the device to interface with and the registers in the internal database to be associated with the device data. The command list supports up to 100 commands. The command list is processed from top (command #0) to bottom. A poll interval parameter is associated with each command to specify a minimum delay time in seconds 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 10 seconds.

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.

ProSoft Technology, Inc. Page 29 of 97 August 27, 2009

MVI56-DH485R ♦ ControlLogix Platform Module Configuration DH485 Interface Module for Remote Chassis User Manual

2.4.2 Command Entry Format

Each command entered in the command list section has the same format. The following is an example section for Port 0:

The first part of each record in the section relates to the module interface and the last part relates to the node to be interfaced with. The following topics describe each field required for a user command

2.4.3 Enable Type Code

This field defines if the command is enabled and when it should be executed. The following codes are recognized by the application:

0 = Command is disabled 1 = Command is executed at the polling interval specified 2 = The write command is only executed when data changes

2.4.4 Database Start Address

This field defines the starting address in the module’s internal database to associate with the command. This field can have a value from 0 to 3999. The address supplied is a word address in the database.

2.4.5 Element Count

This field defines the number of elements to be used with the command. If the command is interfacing with CIF data, this parameter represents a byte count. For data file access, the data size utilized depends on the file type used.

Page 30 of 97 ProSoft Technology, Inc.

August 27, 2009

Module Configuration MVI56-DH485R ♦ ControlLogix Platform User Manual DH485 Interface Module for Remote Chassis

2.4.6 Swap Code

This field changes the order of the bytes and/or words used when sending or receiving the data. The following codes are utilized:

Swap Code Description

0 None - No Change is made in the byte ordering (1234 = 1234) 1 Words - The words are swapped (1234=3412) 2

3 Bytes - The bytes in each word are swapped (1234=2143)

Words & Bytes - The words are swapped then the bytes in each word are swapped (1234=4321)

2.4.7 Poll Interval

This field sets the time interval between successive execution of the command. This parameter is specified in seconds. If the field is set to 10, the command will not be executed more frequently than every 10 seconds.

2.4.8 Node Number

This field defines the node address of the DH-485 node to send the command request. This field should be set to a value from 0 to 31.

2.4.9 Function Code

This field defines the function to be executed by the command. The module uses the following codes:

0 = Read 1 = Write

2.4.10 File Type

This field defines the file type to be interfaced with in the other DH-485 node. The program utilizes the following codes for this field:

0 = Status File (2 bytes per element) 1 = Bit File (2 bytes per element) 2 = Timer File (6 bytes per element) 3 = Counter File (6 bytes per element) 4 = Control File (6 bytes per element) 5 = Integer File (2 bytes per element) 6 = Floating-point File (4 bytes per element) 10 = CIF File (1 byte per element)

ProSoft Technology, Inc. Page 31 of 97 August 27, 2009

MVI56-DH485R ♦ ControlLogix Platform Module Configuration DH485 Interface Module for Remote Chassis User Manual

2.4.11 File Number

This field defines the file number to access. This field is ignored for CIF file access and should be set to 0. For Bit, Timer, Counter, Control, Integer, and Float data types, a maximum value of 255 is valid.

2.4.12 Element Number

This field defines the first element in the file specified to be associated with the command. For a CIF file, this parameter is given as the byte location. For Bit, Timer, Counter, Control, Integer, and Float data types, the maximum value is

255. For CIF data types the maximum value is 510.

Maximum Element Counts for Read/Write Commands

The maximum number of elements requested from a remote node is determined by the file type and function code utilized in the command. The following table lists the maximum element count for each file type:

File Type Bytes/Elements Read Result Write Result

Status 2 83 83 Bit 2 118 115 Timer 6 39 38 Counter 6 39 38 Control 6 39 38 Integer 2 118 115 Float 4 59 57 CIF 1 236 234

2.5 [DH485 Port x Maps]

Note: This section applies only when the DH485 module is operating in Slave mode.

The [DH485 Port x Maps] section for each port defines file override mappings for the module. Use of these maps provides flexibility defining the file emulation supported in the slave driver of the module. Up to 50 maps can be defined in the module to override the fixed file-mapping feature of the module.Each file map entered in the configuration file has the same format.

Page 32 of 97 ProSoft Technology, Inc.

August 27, 2009

Module Configuration MVI56-DH485R ♦ ControlLogix Platform User Manual DH485 Interface Module for Remote Chassis

The following is an example section for Port 0:

These file maps are searched first when a node on the network makes a request. If the requested data area is found in the map list, the database area associated with the command will be used. If the requested data area is not found in the map list, the fixed mapping data configuration will be used.

The following topics describe each field required for an override map.

2.5.1 Database Start Address

This field defines the starting address in the module’s database for the file emulation. This parameter can be assigned a value of 0 to 3999.

2.5.2 File Number

This field defines the file number to be emulated at the database location specified.

2.5.3 Element

This field specifies the first element in the file to be emulated. This element number corresponds to the database start address set for the record.

2.5.4 Word Count (Length)

This field defines the number of word registers to be emulated in the file.

ProSoft Technology, Inc. Page 33 of 97 August 27, 2009

MVI56-DH485R ♦ ControlLogix Platform Module Configuration DH485 Interface Module for Remote Chassis User Manual

2.6 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-DH485R module.

2 Open the P

ROJECT 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 D

OWNLOAD dialog box will open.

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

OWNLOAD button.

The module will perform a platform check to read and load its new settings. When the platform check is complete, the status bar in the D

OWNLOAD dialog

box with the message "Module Running".

Page 34 of 97 ProSoft Technology, Inc.

August 27, 2009

Ladder Logic MVI56-DH485R ♦ ControlLogix Platform User Manual DH485 Interface Module for Remote Chassis

3 Ladder Logic

In This Chapter

 Module Data Object (DH485ModuleDef)............................................... 35



Adding the Module to an Existing Project.............................................. 38

Ladder logic is required for application of the MVI56-DH485R 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.

3.1 Module Data Object (DH485ModuleDef)

All status and variable data related to the MVI56-DH485R module is stored in a user defined data type. An instance of the data type is required before the module can be used. This is done by declaring a variable of the data type in the Controller Tags Edit Tags dialog box. The following table describes the structure of this object.

Name Data Type Description

InStat DH485InStat Status information in each read block ReadData INT[600] Data read from module WriteData INT[600] Data to write to module BP DH485Backplane Data to handle backplane logic Port1CmdsProcessed INT Port2CmdsProcessed INT DH485_1Port1CmdControl BOOL[32] DH485_1Port2CmdControl BOOL[32]

This object contains objects that define variables to be used with the module and status data related to the module. Each of these object types is discussed in the following topics of the document.

ProSoft Technology, Inc. Page 35 of 97 August 27, 2009

MVI56-DH485R ♦ ControlLogix Platform Ladder Logic DH485 Interface Module for Remote Chassis User Manual

3.1.1 Status Object (DH485InStat)

This object stores the status data of the module. The DH485InStat object shown below is updated each time a read block is received by the processor with an identification code of 0 or -1. Use this data to monitor the state of the module at a "real-time rate".

Name Data Type Description

PassCnt INT Program cycle counter Product INT[2] Product Name Rev INT[2] Revision Level Number OP INT[2] Operating Level Number Run INT[2] Run Number BlkErrs DH485BlkStat Block transfer statistics Port0_Stat DH485PortErrors Port 0 status data Port1_Stat DH485PortErrors Port 1 status data

The DH485BlkStat object stores the status information for the backplane data transfer operation.

Name Data Type Description

Read INT Total number of read block transfers Write INT Total number of write block transfers Parse INT Total number of blocks parsed Event INT Total number of event blocks received Cmd INT Total number of command blocks received Err INT Total number of block transfer errors

The following table describes the structure of the DH485PortErrors object.

Name Data Type Description

Active_Nodes DINT Active node bits for each station on network Online_Status INT Online status (0=offline, 1=online) Node_address INT Node address assigned to this port Cur_Cmd INT Current command index being executed Requests INT Total number of command requests Responses INT Total number of response messages Cmd_Err INT

Cfg_Err_Word INT Configuration error word Reserved_18_19 INT Reserved for future use Rec_Packets INT Total number of packets received Trans_Packets INT Total number of packets transmitted Retry_Cnt SINT Total retry count Retry_Fail SINT Total retry failure NAK_rx SINT NAK’s because of no memory for reception NAK_tx SINT

Bad_Packets SINT Bad packets

Total number of command error messages received

NAK’s because of no memory for transmission

Page 36 of 97 ProSoft Technology, Inc.

August 27, 2009

Ladder Logic MVI56-DH485R ♦ ControlLogix Platform User Manual DH485 Interface Module for Remote Chassis

Name Data Type Description

Bad_Cntl SINT Bad control packets CRC_err SINT Packets rec with a bad CRC value Parity_err SINT Parity errors Frame_err SINT Framing errors Overrun_err SINT Overrun errors Unexp_err SINT Unexpected bytes received Bad_LSAP_rx SINT Bad LSAP’s received

Refer to MVI56-DH485R Status Data (page 81) for a complete list of the data stored in this object. This data is passed in blocks 0 and -1.

3.1.2 User Data Objects

These objects hold data to be transferred between the processor and the MVI56DH485R module and to aid in the generation of the ladder logic. The user data is the read and write data transferred between the processor and the module as "pages" of data up to 40 words long.

Name Data Type Description

ReadData INT[600] Data read from module WriteData INT[600] Data to write to module

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

The DH485Backplane object is utilized by the ladder logic to store the variables used in the backplane transfer operation. The structure of the object is shown in the following diagram:

Name Data Type Description

LastRead INT Index of last read block LastWrite INT Index of last write block BlockIndex INT Computed block offset for data table

Other data objects can be added to the DH485ModuleDef object as required for specific applications. It is recommended to only add objects or members to the DH485ModuleDef object that relate to the module.

ProSoft Technology, Inc. Page 37 of 97 August 27, 2009

MVI56-DH485R ♦ ControlLogix Platform Ladder Logic DH485 Interface Module for Remote Chassis User Manual

3.2 Adding the Module to an Existing Project

1 Add the MVI56-DH485R module to the project. Select the I/O

CONFIGURATION folder in the CONTROLLER ORGANIZATION window, and then

click the right mouse button to open a shortcut menu. On the shortcut menu, choose N

EW MODULE.

This action opens the

SELECT MODULE dialog box:

Page 38 of 97 ProSoft Technology, Inc.

August 27, 2009

Ladder Logic MVI56-DH485R ♦ ControlLogix Platform User Manual DH485 Interface Module for Remote Chassis

Select the

1756-MODULE (Generic 1756 Module) from the list and click OK.

This action opens the NEW MODULE dialog box.

Parameter Value

Name

Description

Comm Format Slot

Input Assembly Instance 1 Input Size 42 Output Assembly Instance 2 Output Size 42 Configuration Assembly Instance 4 Configuration Size 0

Enter a module identification string. The recommended value is DH485R.

Enter a description for the module. Example: DH485 Interface Module for Remote Chassis.

Select D Enter the slot number in the rack where the MVI56-DH485R

module is or will be located.

ATA-INT (Very Important)

Enter the Name, Description and Slot options for your application. You must select the C

OMM FORMAT AS DATA - INT in the dialog box, otherwise the

module will not communicate over the backplane of the ControlLogix rack. Click OK to continue.

ProSoft Technology, Inc. Page 39 of 97 August 27, 2009

MVI56-DH485R ♦ ControlLogix Platform Ladder Logic DH485 Interface Module for Remote Chassis User Manual

2 Edit the Module Properties. Select the R

EQUESTED PACKET INTERVAL value

for scanning the I/O on the module. This value represents the minimum frequency that the module will handle scheduled events. This value should not be set to less than 1 millisecond. The default value is 5 milliseconds. Values between 1 and 10 milliseconds should work with most applications.

3 Save the module. Click OK

to dismiss the dialog box. The CONTROLLER

ORGANIZATION window now displays the module's presence.

4 Copy the Controller Tags from the sample program. 5 Copy the User Defined Data Types from the sample program. 6 Copy the Ladder Rungs from the sample program. 7 Save and Download (page

15) the new application to the controller and place

the processor in run mode.

Page 40 of 97 ProSoft Technology, Inc.

August 27, 2009

Diagnostics and Troubleshooting MVI56-DH485R ♦ ControlLogix Platform User Manual DH485 Interface Module for Remote Chassis

4 Diagnostics and Troubleshooting

In This Chapter

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



Configuration/Debug Port ...................................................................... 41

 LED Status Indicators............................................................................ 53

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-DH485R module returns status data normal read block (input image) with identification codes of -1 and 0 that can be used to determine the module’s operating status. On each cycle of data transfer to the processor, the module will pass blocks 0 and -1. These blocks contain the status data for each port and the general module status data. For a complete listing of the status data object, refer to the Reference chapter.

4.2 Configuration/Debug Port

The module contains a configuration/debug port that transfers the configuration between the module and a remote PC and to view all the configuration and status data of the module. The sections below discuss the facilities offered on this interface.

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

ProSoft Technology, Inc. Page 41 of 97 August 27, 2009

MVI56-DH485R ♦ ControlLogix Platform Diagnostics and Troubleshooting DH485 Interface Module for Remote Chassis User Manual

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

4.2.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 [E letter, a new screen will be displayed in your terminal application.

NTER]. When you type a command

Using the Diagnostic Window in ProSoft Configuration Builder

To connect to the module’s Configuration/Debug serial port, 1 Start PCB, and then select the module to test. Click the right mouse button to

open a shortcut menu.

2 On the shortcut menu, choose D

IAGNOSTICS.

Page 42 of 97 ProSoft Technology, Inc.

August 27, 2009

Diagnostics and Troubleshooting MVI56-DH485R ♦ ControlLogix Platform User Manual DH485 Interface Module for Remote Chassis

This action opens the DIAGNOSTICS dialog box.

3 Press [?]

to open 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 Click to configure the connection. On the Connection Setup dialog box, select

a valid com port or other connection type supported by the module.

2 Verify that the null modem cable is connected properly between your

computer’s serial port and the module. A regular serial cable will not work.

3 On computers with more than one serial port, verify that your communication

program is connected to the same port that is connected to the module.

ProSoft Technology, Inc. Page 43 of 97 August 27, 2009

MVI56-DH485R ♦ ControlLogix Platform Diagnostics and Troubleshooting DH485 Interface Module for Remote Chassis User Manual

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:

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 ([?], exactly as shown. Some of these characters will require you to use the [S

[-], [+], [@]) that must be entered

HIFT],

[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] number [1];

likewise for capital letter [O] and number [0]. Although these

from lower case letter [L] (L) and

characters look nearly the same on the screen, they perform different actions on the module.

Page 44 of 97 ProSoft Technology, Inc.

August 27, 2009

Diagnostics and Troubleshooting MVI56-DH485R ♦ ControlLogix Platform User Manual DH485 Interface Module for Remote Chassis

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

Caution: Some of the commands available to you from this menu are designed for advanced debugging and system testing only, and can cause the module to stop communicating with the processor or with other devices, resulting in potential data loss or other failures. Only use these commands if you are specifically directed to do so by ProSoft Technology Technical Support staff. Some of these command keys are not listed on the menu, but are active nevertheless. Please be careful when pressing keys so that you do not accidentally execute an unwanted command.

Viewing Block Transfer Statistics

Press [B]

from the Main Menu to view the Block Transfer Statistics screen.

Use this command to display the configuration and statistics of the backplane data transfer operations between the module and the processor. The information on this screen can help determine if there are communication problems between the processor and the module.

Tip: To determine the number of blocks transferred each second, mark the numbers displayed at a specific time. Then some seconds later activate the command again. Subtract the previous numbers from the current numbers and divide by the quantity of seconds passed between the two readings.

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.

ProSoft Technology, Inc. Page 45 of 97 August 27, 2009

MVI56-DH485R ♦ ControlLogix Platform Diagnostics and Troubleshooting DH485 Interface Module for Remote Chassis User Manual

Opening the DH-485 Port x Menu

Press [E] (port 1) or [F] (port 2) to view the configuration and status data related to the DH-485 driver for each of the application ports.

Transferring the Configuration File from PC to MVI56 module

Press [S]

to send (download) 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 [R] Press [Y]

to receive (upload) the configuration file from the module to your PC. 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.

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

Page 46 of 97 ProSoft Technology, Inc.

August 27, 2009

Diagnostics and Troubleshooting MVI56-DH485R ♦ ControlLogix Platform User Manual DH485 Interface Module for Remote Chassis

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.

Exiting the Program

Press [ESC] to restart the module and force all drivers to be loaded. The module will use the configuration stored in the module's Flash memory to configure the module.

4.2.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 [?] view a list of commands available on this menu.

M = Main Menu

D = Database Menu

? = Display Menu Redisplays (refreshes) this menu

0 – 3 = Pages 0 to 3000

S = Show Again Redisplays last selected page of data

– = Back 5 Pages

P = Previous Page

+ = Skip 5 Pages

N = Next Page

D = Decimal Display

H = Hexadecimal Display

F = Float Display

A = ASCII Display

M = Main Menu Goes up one level to main menu

Selects page 0, 1000, 2000 or 3000

Goes back five pages of data

Goes back one page of data

Goes forward five pages of data

Goes forward one page of data

Displays data in decimal format

Displays data in hex format

Displays data in floating point format

Displays data in text format

ProSoft Technology, Inc. Page 47 of 97 August 27, 2009

MVI56-DH485R ♦ ControlLogix Platform Diagnostics and Troubleshooting DH485 Interface Module for Remote Chassis User Manual

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.

Displaying the Current Page of Registers Again

Press [S]

from the Database View menu to show 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 five pages back in the database

to see the previous 100 registers of data.

Moving Forward Through 5 Pages of Registers

Press [+]

from the Database View menu to skip five pages ahead in the database

to see the next 100 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.

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.

Page 48 of 97 ProSoft Technology, Inc.

August 27, 2009

Diagnostics and Troubleshooting MVI56-DH485R ♦ ControlLogix Platform User Manual DH485 Interface Module for Remote Chassis

Viewing Data in Hexadecimal Format

Press [H]

Viewing Data in Floating Point Format

Press [F]

to display the data on the current page in hexadecimal format.

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.

Returning to the Main Menu

Press [M]

to return to the Main Menu.

4.2.5 DH485 Port x Menu

Use these commands to view the configuration and status data related to the DH-485 driver for each of the application ports. After selecting one of the commands, press the [?] key to display the following menu:

Select one of the options from the menu to perform one of the operations available on the menu. Each command is discussed in the following topics:

Viewing Port Configuration

Press [C] to view configuration information for the application port. Use this command to display detailed configuration information for the port.

Opening the Command Error List Menu

Press [E]

to open the Command Error List. This list consists of multiple pages of

command list error/status data. Press [?]

to view a list of commands available on

this menu.

Opening the Command List Menu

Press [L]

to open the Command List menu. Use this command to view the

configured command list for the module.

ProSoft Technology, Inc. Page 49 of 97 August 27, 2009

MVI56-DH485R ♦ ControlLogix Platform Diagnostics and Troubleshooting DH485 Interface Module for Remote Chassis User Manual

Opening the Override File Map List Menu

Press [O] to view the Override File Map List. Use this command to view the user defined file map configuration data.

Viewing Port Status Data

Press [S] to view detailed status information for the application port. The Cfg Error: parameter displayed will have a value of 0x0000 if there are no

configuration errors for the driver. This is a bit mapped value (displayed in hexadecimal format) with each bit representing a configuration error. The following table lists the bits used by the module:

Bit Code Description

0 0x0001 Invalid baud rate 1 0x0002 Invalid node address 2 0x0004 Invalid maximum node address 3 0x0008 Invalid token hold factor 4 0x0010 Invalid response timeout 5 0x0020 Invalid status or command error DB offset 6 0x0040 Invalid CIF read count or DB offset 7 0x0080 Invalid CIF write DB offset 8 0x0100 Invalid file size 9 0x0200 Invalid file offset 10 0x0400 11 0x0800 12 0x1000 13 0x2000 14 0x4000 15 0x8000

Viewing Version Information

Press [V]

to view Version information for the module.

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.

Returning to the Main Menu

Press [M]

to return to the Main Menu.

Page 50 of 97 ProSoft Technology, Inc.

August 27, 2009

Diagnostics and Troubleshooting MVI56-DH485R ♦ ControlLogix Platform User Manual DH485 Interface Module for Remote Chassis

4.2.6 Command List Menu

Use this menu to view the configured command list for the module. Press [?] to view a list of commands available on this menu.

M = Main Menu

Protocol Menu

Command List Menu

Redisplaying the Menu

Press [?]

to display the current menu. Use this command when you are looking

? = Display Menu

S = Show Again

P = Previous Page

N = Next Page

M = Main Menu

Redisplays (refreshes) this menu

Redisplays last selected page of data

Goes back one page of data

Goes forward one page of data

Goes up one level to main menu

at a screen of data, and want to view the menu choices available to you.

Redisplaying the Current Page

Press [S] to redisplay the current page of data. Use this command to display the current page of commands. Ten commands are

displayed on each page. If an enabled command has an error, the EN field will contain a value of -1. This

indicates that the command will be re-issued every 30 seconds.

Viewing the Previous Page of Commands

Press [P]

Viewing the Next Page of Commands

Press [N]

Returning to the Main Menu

Press [M]

to display the previous page of commands.

to display the next page of commands.

to return to the Main Menu.

ProSoft Technology, Inc. Page 51 of 97 August 27, 2009

MVI56-DH485R ♦ ControlLogix Platform Diagnostics and Troubleshooting DH485 Interface Module for Remote Chassis User Manual

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

M = Main Menu

Protocol Menu

Command List Menu

? = Display Menu

S = Show Again

P = Previous Page

N = Next Page

M = Main Menu

Redisplaying the Current Page

Press [S]

to display the current page of data.

Viewing the Previous 20 Commands

Press [-]

to display data for the previous 20 commands.

Viewing the Previous Page of Commands

Press [P]

Viewing the Next 20 Commands

Press [+]

Viewing the Next Page of Commands

to display the previous page of commands.

to display data for the next 20 commands.

Redisplays (refreshes) this menu

Redisplays last selected page of data

Goes back one page of data

Goes forward one page of data

Goes up one level to main menu

Press [N]

Returning to the Main Menu

Press [M]

to display the next page of commands.

to return to the Main Menu.

Page 52 of 97 ProSoft Technology, Inc.

August 27, 2009

Diagnostics and Troubleshooting MVI56-DH485R ♦ ControlLogix Platform User Manual DH485 Interface Module for Remote Chassis

4.3 LED Status Indicators

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

Module Color Status Indication

CFG Green

P1 Green

P2 Green

BP ACT Amber

OK Red/

Green

Off No data is being transferred on the Configuration/Debug port. On

Off No data is being transferred on the port. On

Off No data is being transferred on the port. Off The MVI56-DH485R module is working normally. APP Amber On

Off

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.

Data is being transferred between the module and the DH-485 network on Port 0.

Data is being transferred between the module and the DH-485 network on Port 1.

The MVI56-DH485R 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.

During module configuration, the OK will be red and the APP and BP ACT LEDs are on.

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.

ProSoft Technology, Inc. Page 53 of 97 August 27, 2009

MVI56-DH485R ♦ ControlLogix Platform Diagnostics and Troubleshooting DH485 Interface Module for Remote Chassis User Manual

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

4.3.2 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

Verify that the module is plugged into the slot that has been configured for the module.

Verify that the slot location in the rack has been configured correctly in the ladder logic.

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

Module Errors

Problem Description Steps to take

BP ACT LED remains off or blinks slowly

MVI56E modules with scrolling LED display: <Backplane Status> condition reads ERR

OK LED remains red

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

August 27, 2009

Reference MVI56-DH485R ♦ ControlLogix Platform User Manual DH485 Interface Module for Remote Chassis

5 Reference

In This Chapter

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



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

 DH485 Communication Ports................................................................ 75



MVI56-DH485R Status Data .................................................................81

 Maximum Element Counts For Read/Write Commands........................84



Command Definition Form.....................................................................86

 File Override Map Definition Form.........................................................87

5.1 Product Specifications

The MVI56 DH-485 Communication Module allows ControlLogix compatible processors to interface easily with other DH-485 protocol compatible devices. Compatible devices include not only Rockwell Automation PLCs (which support the DH-485 protocol) but also a wide assortment of end devices.

The MVI56-DH485 module actively issues DH-485 commands to other nodes on the DH-485 network. One hundred user-defined commands are supported by the module on each port. The ControlLogix processor can be programmed to control the activity on the port by actively enabling or disabling each command directly from the ladder logic.

The module also accepts DH-485 commands from an attached DH-485 master unit (for example, ControlLogix processor ladder logic MSG instruction). The module permits a remote master to interact with all data contained in the module. This data can be derived from other DH-485 slave devices on the network through a master port or from the ControlLogix processor.

5.1.1 General Specifications

 Single Slot - ControlLogix backplane compatible  Designed especially for remote rack implementations  The module is recognized as an Input/Output module and has access to

processor memory for data transfer

 Ladder Logic is used for data transfer between module and processor.

Sample Ladder File included

 Configuration data obtained from configuration file downloaded to module.

Sample configuration file included

ProSoft Technology, Inc. Page 55 of 97 August 27, 2009

MVI56-DH485R ♦ ControlLogix Platform Reference DH485 Interface Module for Remote Chassis User Manual

5.1.2 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

Debug/Configuration port (CFG)

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

Application ports (PRT1 & PRT2)

Full hardware handshaking control, providing radio, modem and multi-drop support Software configurable communication

parameters

App Ports (P1, P2) (Serial modules) RJ45 (DB-9M with supplied cable)

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

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

RS-232 only

Baud rate: 110 to 115,200 baud, depending on protocol RS-232, 485 and 422 Parity: none, odd or even Data bits: 5, 6, 7, or 8 Stop bits: 1 or 2 RTS on/off delay: 0 to 65535 milliseconds

RS-232 handshaking configurable 500V Optical isolation from backplane

6-foot RS-232 configuration cable

Page 56 of 97 ProSoft Technology, Inc.

August 27, 2009

Reference MVI56-DH485R ♦ ControlLogix Platform User Manual DH485 Interface Module for Remote Chassis

5.1.3 Functional Specifications

The MVI56-DH485R module acts as an input/output module between the DH-485 network and the ControlLogix processor. The data transfer from the ControlLogix processor is asynchronous from the actions on the DH-485 network. A 4000word register space in the module exchanges data between the processor and the DH-485 network.

This module uses a small I/O data area for data transfer between the module and the ControlLogix processor.

 The module has a Common Interface File (CIF) with 244 words that can be

accessed by remote DH-485 nodes

 Read and write commands can be sent associated to the following file types:

status, bit, timer, counter, control, integer, float, and CIF

 User-definable module memory usage  Two ports emulate the DH-485 devices (peer-to-peer) with distinct node

addresses

 All configuration information contained in a single, user-defined text file  ControlLogix backplane interface  All module-related data is contained in an internal database  Ability to add or remove nodes without disruption of the network  Baud rates: 9600 or 19200 baud

5.2 Functional Overview

This section describes how the MVI56-DH485R module transfers data between itself and the processor, and how it implements the protocol.

5.2.1 Introduction

The MVI56-DH485R ("DH485 Communication Reduced Data Block Module") allows Rockwell Automation ControlLogix I/O compatible processors to interface easily with other DH-485 protocol compatible devices using a Reduced Data Block area. This module is designed for applications that require the module to be located in a remote rack from the processor. Compatible DH-485 devices include not only Rockwell Automation PLCs and SLCs (which support the DH485 protocol) but also a wide assortment of end devices.

The MVI56-DH485R module acts as an input/output module between the DH-485 network and the Rockwell Automation backplane. The data transfer from the ControlLogix processor is asynchronous from the actions on the DH-485 network. A 4000-word register space in the module exchanges data between the processor and the DH-485 network.

The module can send and receive commands from other nodes on the DH-485 network. Each port works as an independent DH-485 node.

ProSoft Technology, Inc. Page 57 of 97 August 27, 2009

MVI56-DH485R ♦ ControlLogix Platform Reference DH485 Interface Module for Remote Chassis User Manual

5.2.2 Backplane Data Transfer

The MVI56-DH485R 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 for the input and output images. Typical updates are in the range of 5 to 10 milliseconds.

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

The processor inserts data in the module's output image to transfer to the module. The module's program extracts the data and places it in the module's internal database. The output image for the module is set to 42 words. This data area permits fast throughput of data from the processor to the module.

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

ControlLogix Processor

ControlLogix Pro cessor

Controller Tags

Status

Read Data

Write Data

Special Control Blocks

Ladder

Logic

Transfers

Data from

module’s input

image to data

areas in the

processor

Ladder

Logic

Transfers Data from Processor data areas

to output image

Input Image

Output image

MVI56-DH485R M odule

Module’s

Internal

Database

Master

Driver

Driver Logic

Logic

Slave

Slave Driver

Driver Logic

Logic

DH485

Port

Driver

To DH485 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.

Page 58 of 97 ProSoft Technology, Inc.

August 27, 2009

Reference MVI56-DH485R ♦ ControlLogix Platform User Manual DH485 Interface Module for Remote Chassis

The following illustration shows the layout of the database.

Module’s Internal Database Structure

4000 registers for user data

3999

Data contained in this database is paged through the input and output images by coordination of the ControlLogix ladder logic and the MVI56-DH485R module's program. Up to 42 words of data can be transferred from the module to the processor at a time. Up to 42 words of data can be transferred from the processor to the module. The read and write block identification codes in each data block determine the function to be performed or the content of the data block. The module uses the following block numbers:

Block Range Descriptions

0 to -1 Status Blocks 1 to 100 Read or write data 1000 to 1099 Read data initialization blocks 3000 Port 0 command disable block 3001 Port 0 command enable block 3002 Port 0 command conditional block 3100 Port 1 command disable block 3101 Port 1 command enable block 3102 Port 1 command conditional block 9998 Warm-boot control block 9999 Cold-boot control block

Each image has a defined structure depending on the data content and the function of the data transfer.

Normal Data Transfer

Normal data transfer includes the transferring of data received by, or to be transmitted to, the DH-485 drivers and the status data. This data is transferred through read (input image) and write (output image) blocks. Refer to Module Configuration for a description of the data objects used with the blocks and the ladder logic required. The following topics discuss the structure and function of each block.

ProSoft Technology, Inc. Page 59 of 97 August 27, 2009

MVI56-DH485R ♦ ControlLogix Platform Reference DH485 Interface Module for Remote Chassis User Manual

Read Block

These blocks of data transfer information from the module to the ControlLogix processor. The structure of the input image used to transfer data from the module’s database to the processor is shown in the following table.

Offset Description Length

0 Write Block ID (1 to 100) 1 1 to 40 Read Data 40 41 Read Block ID (1 to 100) 1

The Block Identification Code (word 41) is used to signal to the ControlLogix processor that a new block is ready for processing and informs the processor of the contents of the block. If the value of the code is set to 1, the block contains the first 40 words of data contained in the database of the module.

The block also contains the block identification code the module expects to receive from the processor (word 0 in the block). Under normal data transfer conditions, the ladder logic should use the code to build the appropriate block for the module in the output image.

In addition to the transfer of data from the module’s database to the processor, the module also transfers status data to the processor. This is performed using blocks with read block identification codes of -1 and 0. The format block -1 status data is as follows:

Offset Description Length

0 Write Block ID 1 1 to 20 Port 0 Status 20 21 to 40 Port 1 Status 20 41 Read Block ID -1 1

The block format for the 0 status data block is as follows:

Offset Description Length

0 Write Block ID 1 1 Program Scan Counter 1 2 to 3 Product Code 2 4 to 5 Product Version 2 6 to 7 Operating System 2 8 to 9 Run Number 2 10 to 15 Data Transfer Status 6 16 to 40 Spare 25 41 Read Block ID 0 1

Ladder logic should be written to store these data sets into controller tags to monitor the "health" of the module. Refer to the Reference chapter for a detailed listing of the content of these data blocks.

Page 60 of 97 ProSoft Technology, Inc.

August 27, 2009

Reference MVI56-DH485R ♦ ControlLogix Platform User Manual DH485 Interface Module for Remote Chassis

Write Block

These blocks of data transfer information from the ControlLogix processor to the module. The following table describes the structure of the output image.

Offset Description Length

0 Write Block ID (1 to 100) 1 1 to 40 Write Data 40 41 Spare 1

The Write Block ID is an index value used to determine the location in the module’s database where the data will be placed. Each transfer can move up to 40 words.

Command Control Blocks

Command control blocks are special blocks used to control the module or perform special operations. The current version of the software supports four different command control blocks: initialize the read data, change command type control, warm boot, and cold boot:

Initialize Output Data

Note: In order to use this feature, change the "Initialize Output Data" parameter to "Yes" in the

configuration file.

Blocks 1000 to 1099 initialize the read data when the module starts. This is the data passed from the module’s internal database to the processor during normal operation. This optional function can be used to set the read data area to the values last read from the module before the first transfer of data from the module to the processor. The module will request this data from the processor using a block with the following format:

Offset Description Length

0 1000 to 1099 1 1 to 40 Spare 40 41 1000 to 1099 1

The block number utilized represents the 40-word offset of data requested. Therefore, when the module request block 1000, the processor should return the first 40 words of read data. For block 1001, the processor should return the second 40 words of read data. The format of the response block built by the module is as follows:

Offset Description Length

0 1000 to 1099 1 1 to 40 Data to place in output area 40 41 Spare 1

ProSoft Technology, Inc. Page 61 of 97 August 27, 2009

MVI56-DH485R ♦ ControlLogix Platform Reference DH485 Interface Module for Remote Chassis User Manual

The number of blocks requested by the module from the processor depends on the number of read registers configured for the module. If the module is configured for 600 registers, 15 blocks (1000 to 1014) will be requested. This data will be placed in the module’s internal database starting at the read register configured for the module.

Use of this feature requires ladder logic to process the blocks requested. The example ladder logic displays a rung that will handle this optional feature.

Change Command Type Control Block

Blocks 3000, 3001, 3002, 3100, 3101 and 3102 alter the command type for entries in the user command list. When commands are processed during the startup of the module, the command type is set to the value specified in the configuration file. These control blocks alter the configured command type.

Each block contains a command index list. The values entered in this list correspond to the indices of the commands configured by the user. The first command in the user command list has an index of 0 and the second has in index of 1. Therefore, to alter the command type of commands 3 and 5, set the number of command indexes (word 1) to 2 and enter the values 3 and 5 in words 2 and 3. Each block can handle up to 40 commands in the list.

Block 3000 and 3100 requests change the commands listed in the block to the disable type (type = 0). Block 3000 is used for Port 0 and 3100 is used for Port 1 commands. The format for the request block from the ladder logic is as follows:

Offset Description Length

0 3000 or 3100 1 1 Number of command indexes 1 2 to 41 Command index list 40

The response block from the module to the processor has the following format:

Offset Description Length

0 Write Block ID 1 1 Number of commands processed 1 2 to 40 Spare 39 41 3000 or 3100 1

Block 3001 and 3101 requests change the commands listed in the block to the enable type (type = 1). Block 3001 is used for Port 0 and 3101 is used for Port 1 commands. The format for the request block from the ladder logic is as follows:

Offset Description Length

0 3001 or 3101 1 1 Number of command indexes 1 2 to 41 Command index list 40

The response block from the module to the processor has the following format:

Offset Description Length

0 Write Block ID 1 1 Number of commands processed 1

Page 62 of 97 ProSoft Technology, Inc.

August 27, 2009

Reference MVI56-DH485R ♦ ControlLogix Platform User Manual DH485 Interface Module for Remote Chassis

Offset Description Length

2 to 40 Spare 39 41 3001 or 3101 1

Block 3002 and 3102 requests change the commands listed in the block to the conditional type (type = 2). Block 3002 is used for Port 0 and 3102 is used for Port 1 commands. This type code should only be utilized for write commands. The format for the request block from the ladder logic is as follows:

Offset Description Length

0 3002 or 3102 1 1 Number of command indexes 1 2 to 41 Command index list 40

The response block from the module to the processor has the following format:

Offset Description Length

0 Write Block ID 1 1 Number of commands processed 1 2 to 40 Spare 39 41 3002 or 3102 1

Warm Boot Block

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 the configuration file is modified. This will force the module to read the new configuration information and to restart. The following table describes the format of the control block.

Offset Description Length

0 9998 1 1 to 41 Spare 41

Cold Boot Block

Block 9999 performs a cold-boot operation on the module. The following table describes the format of the block constructed by the processor.

Offset Description Length

0 9999 1 1 to 41 Spare 41

5.2.3 ControlLogix Processor Not in Run

Whenever the module detects that the processor has gone out of the Run mode (that is, Fault or PGM), the DH-485 ports can be shut down as prescribed in the user configuration. When the processor is returned to a running state, the module will resume communications on the network.

ProSoft Technology, Inc. Page 63 of 97 August 27, 2009

MVI56-DH485R ♦ ControlLogix Platform Reference DH485 Interface Module for Remote Chassis User Manual

5.2.4 Master Driver

Master mode of the MVI56-DH485R module is responsible for issuing read or write commands to other remote devices on the DH-485 network. These commands are user configured in the module via the Master Command List received from the configuration file. Command status is returned to the processor for each individual command in the command list status data area. 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

The Master driver obtains configuration data from the configuration file on the compact flash disk in the module. This information is used by the Master driver to determine the type of commands to be issued to the other nodes on the DH-485 network.

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

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

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

Status is returned to the ControlLogix processor for each command in the Master Command List.

Refer to the Modifying The Configuration Data section for a complete description of the parameters required to define the virtual DH-485 master port. Care must be taken in constructing each command in the list for predictable operation of the module. If two commands write to the same internal database address of the module, the results will not be as desired. All commands containing invalid data will be ignored by the module.

Page 64 of 97 ProSoft Technology, Inc.

August 27, 2009

Reference MVI56-DH485R ♦ ControlLogix Platform User Manual DH485 Interface Module for Remote Chassis

5.2.5 Slave Driver

The Slave Driver Mode allows the MVI56-DH485R module to respond to CIF and data read and write commands issued by a remote node on the DH-485 network. The following flow chart and associated table describe the flow of data into and out of the module.

Processor Memory

ControlLogix

Controller T ags

Data

storage

Status

from Module

Step Description

The DH-485 slave port driver receives the configuration information from the configuration file on the compact flash disk. This information configures the serial port and define the slave node characteristics. The module simulates N-files and CIF to permit remote access of the database.

A Host device, such as the Rockwell Automation SLC or an HMI application issues a read or write command to the module’s node address. The port driver qualifies the message before accepting it into the module.

After the module accepts the command, the data is immediately transferred to or from the internal database in the module or the CIF data area. If the command is a read command, the data is read out of the database and a response message is built. If the command is a write command, the data is written directly into the database and a response message is built.

After the data processing has been completed in Step 3, the response is issued to the originating master node.

Counters are available in the Status Block that permit the ladder logic program to determine the level of activity of the Slave Driver.

Backplane Interface

Database

Addresses

Data

3999

Status

Configuration

DH485R Module

Slave Mode

Driver

Review the Modifying The Configuration Data section for a complete list of the parameters that must be defined for a slave port. The slave driver supports the following DH-485 command set:

TYPE ACCESS Description

CIF Read 485CIF, Peer-to-Peer, Read MSG requests CIF Write 485CIF, Peer-to-Peer, Write MSG requests Data Table Read 500CPU, Peer-to-Peer, Read MSG requests Data Table Write 500CPU, Peer-to-Peer, Write MSG requests

ProSoft Technology, Inc. Page 65 of 97 August 27, 2009

MVI56-DH485R ♦ ControlLogix Platform Reference

DH485 Interface Module for Remote Chassis User Manual

The Data table commands require the use of files. These files are emulated in the module. The user configuration of the module defines how these files are emulated in the module. Two file mappings are available. The first sets the first file number and file size for each file. Using this mapping, the files are set as contiguous files overlaying the database. For example, if the user sets the file size to 200 and sets the first file number as 7, the files will overlay the database as shown in the following diagram:

Database

Registe

N7:0 ------------> 0 N8:0 ------------> 200 N9:0 ------------> 400 N10:0 ------------> 600 N11:0 ------------> 800 N12:0 ------------> 1000 N13:0 ------------> 1200 N14:0 ------------> 1400 N15:0 ------------> 1600 N16:0 ------------> 1800 N17:0 ------------> 2000 N18:0 ------------> 2200 N19:0 ------------> 2400 N20:0 ------------> 2600 N21:0 ------------> 2800 N22:0 ------------> 3000 N23:0 ------------> 3200 N24:0 ------------> 3400 N25:0 ------------> 3600 N26:0 ------------> 3800

In addition to the fixed file emulation, the module also supports user defined mapping of files. With this mapping, the user defines the database offset, file number, the starting element number and the length. This data is entered in the [DH485 Port x Maps] section of the configuration file for each port (x=0 for Port 0 and 1 for Port 1. The following is an example for Port 0:

[DH485R Port 0 Maps] # DB_Address File_Number Element Length START 0 10 0 100 100 12 100 100 END

Page 66 of 97 ProSoft Technology, Inc.

August 27, 2009

Reference MVI56-DH485R ♦ ControlLogix Platform User Manual DH485 Interface Module for Remote Chassis

With the configuration displayed above, requests for file 10 elements 0 to 99 will be associated with the module’s internal data registers 0 to 99 and file 12 elements 100 to 199 will be associated with the data base registers 100 to 199. The module supports up to 50 of these data mappings. When a request is made of the slave driver, the mapping defined in this override section will first be searched first. If the data area in the request is found in the list, that data mapping will be utilized. If the data area in the request is not found in the list, the fixed data area mapping will be used.

5.2.6 CIF Data

The module supports the common interface file (CIF) of the DH-485 protocol. A separate data area can be defined for each application port. This data area is divided into read and write data and is mapped into the module's internal database. The module's application constantly transfers the read CIF data from the CIF database to the module database and the write CIF data from the module to the CIF database. The parameters used to define the CIF database are contained in the configuration file. This optional feature of the module should only be utilized if required by a remote master on the network. Otherwise, the data file functions (500CPU message) instructions should be used to access and control the module's data. The following diagram shows the relationship of the DH-485 drivers, the CIF database and the module's database:

Master Driver

Write

Function

Read

Function

Slave Driver

Write

Function

Read

Function

Write Database

Read Database

Write CIF Request

Read CIF Request

Module

Database

CIF

Database

CIF Read Data

CIF Write Data

Request

Response

Request

Response

Request

Response

Request

Response

Important: The user can configure the size of the CIF Read area through the "CIF Read Count" parameter. The size of the CIF write area is given by following parameters"

CIF Write Count = 244 - CIF Read Count.

ProSoft Technology, Inc. Page 67 of 97 August 27, 2009

MVI56-DH485R ♦ ControlLogix Platform Reference DH485 Interface Module for Remote Chassis User Manual

In order to clarify the direction of data flow, the following shows an example:

Parameter Value Format

Read Register Start 600 Word Read Register Count 600 Word Write Register Start 0 Word Write Register Count 600 Word CIF Read DB Offset 1200 Byte CIF Read Count 144 Byte CIF Write DB Offset 0 Byte

This configuration will imply that the data will be transferred as shown in the following diagram:

As shown in the diagram, the CIF area is split into the Read and Write areas. The CIF Read area always starts at an offset in the CIF file, except when the CIF Read Count is equal to 0. In this case, the CIF Read Area will not exist.

The diagram shows how the CIF area should interact with the backplane read and write area in order to achieve the correct flow of data.

If a Write MSG from a remote SLC processor is sent to byte addresses 0 and 1 in the module's CIF area, the data would be copied to word address 600 in the database and would then be read to the ControlLogix processor.

Page 68 of 97 ProSoft Technology, Inc.

August 27, 2009

Reference MVI56-DH485R ♦ ControlLogix Platform User Manual DH485 Interface Module for Remote Chassis

The following illustration shows four different uses and configurations of the CIF data area:

Example 1 only uses CIF read data and utilizes the maximum read data area. Example 2 only uses the CIF write data and utilizes the maximum write data area. Example 3 uses both CIF read and write data. 124 bytes of read data are used and 120 bytes of write data are used. Example 4 does not use the CIF data in the application.

ProSoft Technology, Inc. Page 69 of 97 August 27, 2009

MVI56-DH485R ♦ ControlLogix Platform Reference DH485 Interface Module for Remote Chassis User Manual

5.2.7 SLC Interface

The DH-485 driver is written for peer-to-peer operation on the DH-485 network. Therefore, the driver can both execute commands (master role) and respond to commands (slave role). If the driver contains no commands, ladder logic is required in the other DH-485 nodes in order to control or access the data in the module containing the driver. If the driver is configured with user defined commands, these commands will control or monitor data in other nodes on the network without the ladder logic requirement. The driver is developed to support both modes of operation simultaneously.

The section first describes the SLC configuration required for the DH-485 protocol and the cabling required. Following this discussion, the section contains example ladder logic to interface with the module’s database.

The ladder logic required in an SLC to interface with the DH-485 Driver uses the MSG instruction. The DH-485 driver supports two data access options. You can interface to a module containing the DH-485 driver using the CIF (Common Interface File) or normal SLC data file access. Use of the CIF access is limited to a data area of 244 bytes and is offered for backwards compatibility to older processors and should be used only when the data access method is not available. The preferred method of data access to the driver is through the use of the SLC data files. This access method permits full access to the data contained in the module’s internal database.

SLC Communication Set Up

In order to use the DH-485 port on the SLC, channel 0 or 1 must be configured as a DH-485 port. Select Channel Configuration from the RSLogix 500 software to display the following dialog box.

Page 70 of 97 ProSoft Technology, Inc.

August 27, 2009

Reference MVI56-DH485R ♦ ControlLogix Platform User Manual DH485 Interface Module for Remote Chassis

Select one of the tabs in the dialog box to select the channel to configure with the DH-485 protocol. The following figure displays an example configuration for channel 1.

Select the correct baud rate used on the DH-485 network. Next select the node address for the SLC on the network. Each node on the network must have a unique node address. Next set the Token Hold Factor and Maximum Node Address for the SLC. Select the Apply button to apply the settings configured. If you require help setting up the channel, select the Help button on the form. After configuring the channel, download the new configuration to the SLC processor.

Ladder Logic: Remote SLC

If the SLC will be used to monitor and control data in the DH-485 driver device, ladder logic is required. No ladder logic is required if user commands are defined in the DH-485 driver module to handle all data requirements. The examples below describe the two data access methods: CIF and Data File.

CIF Data Access

CIF data access permits up to 244 bytes of data in the DH-485 driver module to be monitored and controlled for each port. Due to the extreme limit on the data size, this method should only be used if the data file access method is not offered on the monitoring and controlling device. The driver supports both read and write access to this data area.

ProSoft Technology, Inc. Page 71 of 97 August 27, 2009

MVI56-DH485R ♦ ControlLogix Platform Reference DH485 Interface Module for Remote Chassis User Manual

Read Access

In order to monitor data contained in the DH-485 driver module, a read command message must be executed from the ladder logic. To access the CIF data area in the module, select the 485CIF option for the Target Device in the MSG instruction. The following is an example rung that displays a CIF method MSG instruction:

You must allocate a unique area in the SLC’s data file area for the Control Block area used by the MSG instruction. Failure to provide this area will result in unpredictable behavior. Select the Setup Screen area in the MSG instruction to display the following dialog box:

This example reads 10 words of data from the CIF data file in the module starting at byte offset 0 in node 2 and places the response data in the data file N10:0 to

9. Note that the Data Table Offset value is a byte offset and not a word offset. The size of data read is determined by the number of elements times the size of each element. For a N-type file, the size is 1 word (2 bytes). For a F-type file, the size is 2 words (4 bytes).

Page 72 of 97 ProSoft Technology, Inc.

August 27, 2009

Reference MVI56-DH485R ♦ ControlLogix Platform User Manual DH485 Interface Module for Remote Chassis

Write Access

In order to control data contained in the DH485R driver module, a write command message must be executed from the ladder logic. 242 bytes are available in the CIF Read Data area (address 0 to 241). To alter the CIF data area in the module, select the 485CIF option for the Target Device in the MSG instruction. The following is an example rung that displays a CIF method MSG instruction:

You must allocate a unique area in the ControlLogix’s data file area for the Control Block area used by the MSG instruction. Failure to provide this area will result in unpredictable behavior. Select the Setup Screen area in the MSG instruction to display the following dialog box:

This example will place the 10 words from the ControlLogix data file N9:0 to 9 in the CIF data area starting at byte offset 100 in node 2. Note that the Data Table Offset value is a byte offset and not a word offset. The size of data written is determined by the number of elements times the size of each element. For a Ntype file, the size is 1 word (2 bytes). For a F-type file, the size is 2 words (4 bytes).

Data File Access

The data file access method permits full access to the full internal database of the DH-485 driver module. This access method supports normal SLC file read and write access to the data in the module.

ProSoft Technology, Inc. Page 73 of 97 August 27, 2009

MVI56-DH485R ♦ ControlLogix Platform Reference DH485 Interface Module for Remote Chassis User Manual

Read Access

In order to monitor data contained in the DH-485 driver module, a read command message must be executed from the ladder logic. To read the data area in the module, select the 500CPU option for the Target Device in the MSG instruction. The following is an example rung that displays a data file access method MSG instruction:

This example will read 10 words from the module and place the data in the SLC data file area N10:0 to 9. N-files are emulated on the module containing the DH485 driver. If the module is configured for the first N file of N7, a file size of 200 and a file offset value of 0, the module will respond with the words held in the module’s internal database registers 200 to 209 for this command. Refer to the DH-485 driver database documentation for a full explanation of the module’s internal database.

Page 74 of 97 ProSoft Technology, Inc.

August 27, 2009

Reference MVI56-DH485R ♦ ControlLogix Platform User Manual DH485 Interface Module for Remote Chassis

Write Access

In order to control data contained in the DH-485 driver module, a write command message must be executed from the ladder logic. To alter the data area in the module, select the 500CPU option for the Target Device in the MSG instruction. The following is an example rung that displays a data file access method MSG instruction:

This example will write 10 words from the ControlLogix data file area N9:0 to 9 to the module. N-files are emulated on the module containing the DH-485 driver. If the module is configured for the first N file of N7, a file size of 200 and a file offset value of 0, the module will place the 10 words of data received in the module’s internal database registers 200 to 209. Refer to the DH-485 driver database documentation for a full explanation of the module’s internal database.

5.3 DH485 Communication Ports

The application ports on the MVI56-DH485R module support RS-232 and RS485 interfaces. Please ensure that the jumpers on the module are set correctly for the type of interface you are using.

ProSoft Technology, Inc. Page 75 of 97 August 27, 2009

MVI56-DH485R ♦ ControlLogix Platform Reference DH485 Interface Module for Remote Chassis User Manual

Note: When using RS-232 with radio modem applications, some radios or modems require hardware handshaking (control and monitoring of modem signal lines). Enable this in the configuration of the module by setting the UseCTS parameter to 1.

5.3.1 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 2 Make sure that you are not actively browsing using the driver that you wish to

stop. The following shows an actively browsed network:

Page 76 of 97 ProSoft Technology, Inc.

August 27, 2009

Reference MVI56-DH485R ♦ ControlLogix Platform User Manual DH485 Interface Module for Remote Chassis

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:

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:

or the icons.

ProSoft Technology, Inc. Page 77 of 97 August 27, 2009

MVI56-DH485R ♦ ControlLogix Platform Reference DH485 Interface Module for Remote Chassis User Manual

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.2 Cable Connections

ProSoft provides a single RJ45 to male DB-9 adapter to permit simpler interfacing to other devices for each port. The module's DH485 ports can be configured to operate in RS-232 or RS-485 mode. The interface to be associated with each port is set with jumpers on the module. The following sections describe each interface.

RS-232

When the RS-232 interface is selected, you must use an AIC+ to connect the port to a DH485. The cable required for this connection is shown in the following illustration:

Page 78 of 97 ProSoft Technology, Inc.

August 27, 2009

Reference MVI56-DH485R ♦ ControlLogix Platform User Manual DH485 Interface Module for Remote Chassis

RS-485

The RS-485 uses a single two or three wire cable. The use of the ground is optional and dependent on the RS-485 network. The cable required for this interface is shown in the following diagram:

When connecting to port 3 of an AIC+ module, the following is the correct wiring:

When connecting to a 1747-AIC module, the following is the correct wiring:

ProSoft Technology, Inc. Page 79 of 97 August 27, 2009

MVI56-DH485R ♦ ControlLogix Platform Reference DH485 Interface Module for Remote Chassis User Manual

The following illustration shows an example DH-485 network.

DH485

Port RS-485

AIC+

DB-9 Male

AIC+

1747 - AIC

Chassis Gnd Shield Common

A Termination

Port 2

Port 1

ProSoft DH485

RS-232

1 2 3 4 5 6

ProSoft DH485

RS-232

1 2 3 4 5 6

MicroLogix

1000

1 2 3 4 5 6

Workstation

1747-PIC

To SLC 5/03

Channel 1

This network displays the two different methods to configure the module for a DH-485 network. Please note there is no place on the module’s RS-485 to land the shield, and when used in the configuration shown, it must be wired externally. Verify that the RS interface jumper on the module is set to the correct position: RS-232 or RS-485.

Note: Terminating resistors are generally not required on the RS-485 network, unless you are experiencing communication problems that can be attributed to signal echoes or reflections. In this case, install a 120 ohm terminating resistor on the RS-485 line.

5.3.3 DB9 to RJ45 Adaptor (Cable 14)

Page 80 of 97 ProSoft Technology, Inc.

August 27, 2009

Reference MVI56-DH485R ♦ ControlLogix Platform User Manual DH485 Interface Module for Remote Chassis

5.4 MVI56-DH485R Status Data

This section contains a listing status data presented to the processor by the module. The following table lists the data returned in identification code 0 read blocks:

Word# Description

1 Scan Counter 2 to 3 Product Name (ASCII) 4 to 5 Revision (ASCII) 6 to 7 Operating System Revision (ASCII) 8 to 9 Production Run Number (ASCII) 10 Read Block Count 11 Write Block Count 12 Parse Block Count 13 Reserved 14 Reserved 15 Number of Block Errors

The user can also copy this data block to the module using the Error/Status Pointer parameter in the configuration file.

The following table lists the status data passed from the module to the ControlLogix processor in blocks with an identification code of -1:

Port 0

Word# Byte# Description

1 to 2 0 to 3 Active node bits for stations 0 to 31 3 4 to 5 Online status (0=Offline, 1=Online) 4 6 to 7 Node address of the unit/port emulated 5 8 to 9 Current command index being issued 6 10 to 11 Total number of request messages 7 12 to 13 Total number of response messages received 8 14 to 15 Total number of command list errors 9 16 to 17

10 18 to 19 Reserved for future use. 11 20 to 21 Total number of packets received 12 22 to 23 Total number of packets transmitted

24 Total retry count 13 25 Retry failure counter 26 Total number of NAKs because of no memory for reception 14 27 Total number of NAKs because of no memory for transmission 28 Total number of bad packets 15 29 Total number of bad control packets

Configuration error word. Each bit represent a configuration error condition.

ProSoft Technology, Inc. Page 81 of 97 August 27, 2009

MVI56-DH485R ♦ ControlLogix Platform Reference DH485 Interface Module for Remote Chassis User Manual

Word# Byte# Description

30 Total number of packets received with a bad CRC value 16 31 Total number of parity errors 32 Total number of framing errors 17 33 Total number of overrun errors 34 Total number of unexpected bytes received 18

35 Total number of bad LSAPs received

19 to 20 Reserved for future use.

Port 1

21 to 22 0 to 3 Active node bits for stations 0 to 31 23 4 to 5 Online status (0=Offline, 1=Online) 24 6 to 7 Node address of the unit/port emulated 25 8 to 9 Current command index being issued 26 10 to 11 Total number of request messages 27 12 to 13 Total number of response messages received 28 14 to 15 Total number of command list errors 29 16 to 17

30 18 to 19 Reserved for future use. 31 20 to 21 Total number of packets received 32 22 to 23 Total number of packets transmitted 33 24 Total retry count 25 Retry failure counter

26 Total number of NAKs because of no memory for reception 34 27 Total number of NAKs because of no memory for transmission 28 Total number of bad packets 35 29 Total number of bad control packets 30 Total number of packets received with a bad CRC value 36 31 Total number of parity errors 32 Total number of framing errors 37 33 Total number of overrun errors 34 Total number of unexpected bytes received 38 35 Total number of bad LSAPs received

39 to 40 Reserved for future use.

Configuration error word. Each bit represent a configuration error condition.

The data in words 9 and 29 (Configuration Error Word) are bit-mapped values with the following definition:

Bit Code Description

0 0x0001 Invalid baud rate 1 0x0002 Invalid node address 2 0x0004 Invalid maximum node address

Page 82 of 97 ProSoft Technology, Inc.

August 27, 2009

Reference MVI56-DH485R ♦ ControlLogix Platform User Manual DH485 Interface Module for Remote Chassis

Bit Code Description

3 0x0008 Invalid token hold factor 4 0x0010 Invalid response timeout 5 0x0020 Invalid status or command error DB offset 6 0x0040 Invalid CIF read count or DB offset 7 0x0080 Invalid CIF write DB offset 8 0x0100 Invalid file size 9 0x0200 Invalid file offset 10 0x0400 11 0x0800 12 0x1000 13 0x2000 14 0x4000 15 0x8000

When no configuration errors are present, the words will have a value of 0x0000 (hexadecimal). Configuration errors should be corrected to have the module perform as required by the application.

Additionally, each command in the user command list contains an error status data area. This data can be viewed through the debug/configuration port. This data can be configured to be placed in the module's database with each register containing an error value for each command for each port as shown in the following diagram:

Word# Description

0 Error code for command index 0. 1 Error code for command index 1.

-- -99 Error code for command index 99.

The error codes placed in this data area have the following definitions:

5.4.1 DH485 General Error Codes

Error # Description

0 Operation successful 1 Invalid parameter 2 Device is already open 3 Device is not present 4 Invalid access 5 The function has timed out 6 7 Unable to configure the requested port 8 Unable to allocate memory for DH-485 driver

ProSoft Technology, Inc. Page 83 of 97 August 27, 2009

MVI56-DH485R ♦ ControlLogix Platform Reference DH485 Interface Module for Remote Chassis User Manual

5.4.2 DH485 API Specific Error Codes

Error # Description

0x0800 Command only permitted in master mode 0x0801 Command already active on the port 0x0802 Response to request timed out 0x0803 Unable to allocate memory for the request 0x0804 Illegal command or format 0x0805 Host could not complete request (hardware fault) 0x0806 Out of memory, file or rung does not exist 0x0807 Field has an illegal value 0x0808 Not enough fields in request message 0x0809 Too many fields in request message 0x080A Symbol not found 0x080B Symbol 0 or greater than maximum characters permitted in message 0x080C Does not exist, illegal size 0x080D File wrong size, address past end of file 0x080E Data or file too large (memory not available) 0x080F Request too large to transmit message (size+address > max message) 0x0810 Access denied 0x0811 Command cannot be executed 0x0812 Illegal data type information 0x0813 Illegal parameter, invalid data in search or command block 0x0814 File open by another node 0x0815 Program owned by another node 0x0816 Unknown error returned from host 0x0817 No message active on the port

5.5 Maximum Element Counts For Read/Write Commands

File Type Code File Type Bytes/ Element

0 Status 2 1 Bit 2 2 Timer 6 3 Counter 6 4 Control 6 5 Integer 2 6 Float 4 10 CIF 1

Page 84 of 97 ProSoft Technology, Inc.

August 27, 2009

Reference MVI56-DH485R ♦ ControlLogix Platform User Manual DH485 Interface Module for Remote Chassis

5.5.1 Timer, Counter, and Control Data Types

Timer Data Type

The Timer data type uses its 3 words (6 bytes) as described below (for example, T4:0):

Word 0:

Bit 9: timebase selection Bit 13: T4:0.DN Bit 14: T4:0.TT Bit 15: T4:0.EN

Word 1:

T4:0.PRE

Word 2:

T4:0.ACC

Counter Data Type

The Counter data type uses its 3 words (6 bytes) as described below (for example, C5:0)

Word 0:

Bit 10:UA Bit 11:UN Bit 12:OV Bit 13:DN Bit 14:CD

Bit 15:CV Word 1: C5:0.PRE Word 2: C5:0.ACC

Control Data Type

The Control Data Type uses its three words (6 bytes) as shown in the following example. For example, R6:0.

Word 0:

Bit 8: FD

Bit 9: IN

Bit 10: UL

Bit 11: ER

Bit 12: EM

Bit 13: DN

Bit 14: EU

Bit 15: EN Word 1: R6:0.LEN Word 2: R6:.0.POS

ProSoft Technology, Inc. Page 85 of 97 August 27, 2009

MVI56-DH485R ♦ ControlLogix Platform Reference DH485 Interface Module for Remote Chassis User Manual

5.6 Command Definition Form

The following is a form for setting up the command list:

Enable Type Code

Database Start Address

Element Count

Swap Code

Poll Interval

Node Number

Function Code

File Type File

Number

Element Number

Page 86 of 97 ProSoft Technology, Inc.

August 27, 2009

Reference MVI56-DH485R ♦ ControlLogix Platform User Manual DH485 Interface Module for Remote Chassis

The following table lists the fields required for each record in the [DH485 Port x Maps] section:

Field Definition

Database Start Address

File Number

Element

Word Count (Length)

This field defines the starting address in the module’s database for the file emulation. This parameter can be assigned a value of 0 to 4999.

This field defines the file number to be emulated at the specified database location.

This field specifies the first element in the file to be emulated. This element number corresponds to the database start address set for the record.

This field defines the number of word registers to be emulated in the file.

5.7 File Override Map Definition Form

The following is a form for setting up the override map list:

Database Start Address

File Number Element Number Word Count (Length)

ProSoft Technology, Inc. Page 87 of 97 August 27, 2009

MVI56-DH485R ♦ ControlLogix Platform Reference DH485 Interface Module for Remote Chassis User Manual

Database Start Address

File Number Element Number Word Count (Length)

Page 88 of 97 ProSoft Technology, Inc.

August 27, 2009

Support, Service & Warranty MVI56-DH485R ♦ ControlLogix Platform User Manual DH485 Interface Module for Remote Chassis

6 Support, Service & Warranty

In This Chapter

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



Return Material Authorization (RMA) Policies and Conditions...............90

 LIMITED WARRANTY........................................................................... 91

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

Asia Pacific

+603.7724.2080, support.asia@prosoft-technology.com Languages spoken include: Chinese, English

Europe (location in Toulouse, France)

+33 (0) 5.34.36.87.20, support.EMEA@prosoft-technology.com Languages spoken include: French, English

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

+1.661.716.5100, support@prosoft-technology.com Languages spoken include: English, Spanish

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

Brasil (location in Sao Paulo)

+55-11-5084-5178, eduardo@prosoft-technology.com Languages spoken include: Portuguese, English

Web Site: www.prosoft-technology.com/support E-mail address: support@prosoft-technology.com

ProSoft Technology, Inc. Page 89 of 97 August 27, 2009

MVI56-DH485R ♦ ControlLogix Platform Support, Service & Warranty DH485 Interface Module for Remote Chassis User Manual

6.2 Return Material Authorization (RMA) Policies and Conditions

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

6.2.1 All Product Returns:

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

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

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

any reason, Customer should contact ProSoft Technical Support at one of the telephone numbers listed above (page 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, and so on.

89). A Technical Support

6.2.2 Procedures for Return of Units Under Warranty:

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

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

be required.

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

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

6.2.3 Procedures for Return of Units Out of Warranty:

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

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

Page 90 of 97 ProSoft Technology, Inc.

August 27, 2009

Support, Service & Warranty MVI56-DH485R ♦ ControlLogix Platform User Manual DH485 Interface Module for Remote Chassis

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

ProSoft Technology, Inc. Page 91 of 97 August 27, 2009

MVI56-DH485R ♦ ControlLogix Platform Support, Service & Warranty DH485 Interface Module for Remote Chassis User Manual

b) Warranty On Services: Materials and labor performed by ProSoft to repair

a verified malfunction or defect are warranteed in the terms specified above for new Product, provided said warranty will be for the period remaining on the original new equipment warranty or, if the original warranty is no longer in effect, for a period of 90 days from the date of repair.

6.3.2 What Is Not Covered By This Warranty

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

the operation of software purchased from ProSoft will be uninterrupted or error free or that the functions contained in the software will meet or satisfy the purchaser’s intended use or requirements; the Customer assumes complete responsibility for decisions made or actions taken based on information obtained using ProSoft software.

b) This Warranty does not cover the failure of the Product to perform

specified functions, or any other non-conformance, defects, losses or damages caused by or attributable to any of the following: (i) shipping; (ii) improper 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.

Page 92 of 97 ProSoft Technology, Inc.

August 27, 2009

Support, Service & Warranty MVI56-DH485R ♦ ControlLogix Platform User Manual DH485 Interface Module for Remote Chassis

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.

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 91) are in lieu of all other warranties, express or implied, including but not limited to the implied warranties of merchantability and fitness for a particular purpose.

ProSoft Technology, Inc. Page 93 of 97 August 27, 2009

MVI56-DH485R ♦ ControlLogix Platform Support, Service & Warranty DH485 Interface Module for Remote Chassis User Manual

6.3.6 Limitation of Remedies **

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

** Some areas do not allow time limitations on an implied warranty, or allow the exclusion or limitation of incidental or consequential damages. In such areas, the above limitations may not apply. This Warranty gives you specific legal rights, and you may also have other rights which vary from place to place.

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

Page 94 of 97 ProSoft Technology, Inc.

August 27, 2009

Index MVI56-DH485R ♦ ControlLogix Platform User Manual DH485 Interface Module for Remote Chassis

DH485 Communication Ports • 75 DH485 General Error Codes • 83 DH485 Port x Menu • 49

Index

[

[DH485 Port x Commands] • 29 [DH485 Port x Maps] • 32 [DH485 Port x] • 26 [Module] • 24

Adding the Module to an Existing Project • 38 All Product Returns: • 90 Allocation of Risks • 94

Backplane Data Transfer • 58 Battery Life Advisory • 3 Baud Rate • 26

Cable Connections • 78 Change Command Type Control Block • 62 CIF Data • 67 CIF Data Access • 71 CIF Read Count • 27 CIF Read DB Offset • 27 CIF Write DB Offset • 28 Clearing a Fault Condition • 54 Cold Boot Block • 63 Command Control Blocks • 61 Command Definition Form • 86 Command Entry Format • 30 Command Error DB Offset • 27 Command List Menu • 51 Command List Overview • 29 Comment Entries • 23 Configuration/Debug Port • 41 Configuring Module Parameters • 22 Configuring the RSLinx Driver for the PC COM Port •

16 Connect your PC to the ControlLogix Processor • 14 Connect your PC to the Module • 18 Control Data Type • 85 Controlling Law and Severability • 94 ControlLogix Processor Not in Run • 63 Counter Data Type • 85

Data File Access • 73 Database Start Address • 30, 33 Database View Menu • 47 DB9 to RJ45 Adaptor (Cable 14) • 80 DH485 API Specific Error Codes • 84

Diagnostics and Troubleshooting • 7, 41 Disabling the RSLinx Driver for the Com Port on the

PC • 76 Disclaimer of all Other Warranties • 93 Disclaimer Regarding High Risk Activities • 92 Displaying the Current Page of Registers Again • 48 Download the Project to the Module • 34 Download the Sample Program to the Processor • 15,

Element • 33 Element Count • 30 Element Number • 32 Enable Type Code • 30 Error / Status Pointer • 24 Exiting the Program • 47

Failure Flag Count • 25 File Number • 32, 33 File Offset • 28 File Override Map Definition Form • 87 File Size • 28 File Type • 31 First File • 28 Function Code • 31 Functional Overview • 7, 57 Functional Specifications • 57

General Specifications • 55 Guide to the MVI56-DH485R User Manual • 7

Hardware Specifications • 56 How to Contact Us

Technical Support • 89, 90

Important Installation Instructions • 2 Initialize Output Data • 25, 61 Install ProSoft Configuration Builder Software • 11 Install the Module in the Rack • 13 Intellectual Property Indemnity • 93 Introduction • 57

Keystrokes • 44

Ladder Logic • 35

Remote SLC • 71

LED Status Indicators • 7, 53

ProSoft Technology, Inc. Page 95 of 97 August 27, 2009

MVI56-DH485R ♦ ControlLogix Platform Index DH485 Interface Module for Remote Chassis User Manual

Limitation of Remedies ** • 94 LIMITED WARRANTY • 91

Main Menu • 45 Master Command Error List Menu • 52 Master Driver • 64 Maximum Element Counts for Read/Write Commands

• 32

Maximum Element Counts For Read/Write Commands

• 84 Maximum Node Address • 26 Min Command Delay • 28 Module Configuration • 19 Module Data Object (DH485ModuleDef) • 35 Module Name • 24 Moving Back Through 5 Pages of Registers • 48 Moving Forward Through 5 Pages of Registers • 48 MVI (Multi Vendor Interface) Modules • 2 MVI56-DH485R Status Data • 37, 81

Navigation • 44 No Other Warranties • 94 Node Address • 26 Node Number • 31 Normal Data Transfer • 59

Opening the Command Error List Menu • 49 Opening the Command List Menu • 49 Opening the Database Menu • 45 Opening the DH-485 Port x Menu • 46 Opening the Override File Map List Menu • 50

Package Contents • 10 Pinouts • 2, 78, 79, 80 Poll Interval • 31 Printing a Configuration File • 23 Procedures for Return of Units Out of Warranty: • 90 Procedures for Return of Units Under Warranty: • 90 Product Specifications • 7, 55 ProSoft Technology® Product Documentation • 4

Read Access • 72, 74 Read Block • 60 Read Register Count • 25 Read Register Start • 25 Reading Status Data from the Module • 41 Redisplaying the Current Page • 51, 52 Redisplaying the Menu • 51 Reference • 7, 55 Required Hardware • 41 Response Timeout • 27 Return Material Authorization (RMA) Policies and

Conditions • 90

Returning to the Main Menu • 49, 50, 51, 52 RS-232 • 78 RS-232 Configuration/Debug Port • 76 RS-485 • 79

Set Module Parameters • 22 Set Up the Project • 19 Setting Jumpers • 12 Slave Driver • 65 SLC Communication Set Up • 70 SLC Interface • 70 Start Here • 7, 9 Status DB Offset • 27 Status Object (DH485InStat) • 36 Support, Service & Warranty • 7, 89 Swap Code • 31 System Requirements • 9

The Configuration/Debug Menu • 42 Time Limit for Bringing Suit • 94 Timer Data Type • 85 Timer, Counter, and Control Data Types • 85 Token Hold Factor • 27 Transferring the Configuration File from MVI56 module

to PC • 46

Transferring the Configuration File from PC to MVI56

module • 46

Troubleshooting • 54

User Data Objects • 37 Using ProSoft Configuration Builder • 19 Using the Diagnostic Window in ProSoft Configuration

Builder • 42

Viewing Block Transfer Statistics • 45 Viewing Data in ASCII (Text) Format • 49 Viewing Data in Decimal Format • 48 Viewing Data in Floating Point Format • 49 Viewing Data in Hexadecimal Format • 49 Viewing Module Configuration • 45 Viewing Port Configuration • 49 Viewing Port Status Data • 50 Viewing Register Pages • 48 Viewing the Next 100 Registers of Data • 48 Viewing the Next 20 Commands • 52 Viewing the Next Page of Commands • 51, 52 Viewing the Previous 100 Registers of Data • 48 Viewing the Previous 20 Commands • 52 Viewing the Previous Page of Commands • 51, 52 Viewing Version Information • 46, 50

Warm Boot Block • 63 Warm Booting the Module • 46

Page 96 of 97 ProSoft Technology, Inc.

August 27, 2009

Index MVI56-DH485R ♦ ControlLogix Platform User Manual DH485 Interface Module for Remote Chassis

Warnings • 2 What Is Covered By This Warranty • 91, 93 What Is Not Covered By This Warranty • 92 Word Count (Length) • 33 Write Access • 73, 75 Write Block • 61 Write Register Count • 25 Write Register Start • 25

Your Feedback Please • 3

ProSoft Technology, Inc. Page 97 of 97 August 27, 2009

ProSoft Technology inRax MVI56-DH485R User Manual

Specifications and Main Features

Frequently Asked Questions

User Manual

Start Here MVI56-DH485R ♦ ControlLogix Platform User Manual DH485 Interface Module for Remote Chassis

1.3 Install ProSoft Configuration Builder Software

To install ProSoft Configuration Builder from the ProSoft Web Site

To install ProSoft Configuration Builder from the Product CD-ROM

1.5 Install the Module in the Rack

1.6 Connect your PC to the ControlLogix Processor

1.7 Download the Sample Program to the Processor

If RSLogix is unable to establish communication with the processor, follow these steps

1.8 Connect your PC to the Module

Module Configuration MVI56-DH485R ♦ ControlLogix Platform User Manual DH485 Interface Module for Remote Chassis

2.1 Using ProSoft Configuration Builder

To rename an object:

Configuring Module Parameters

Comment Entries

Printing a Configuration File

2.3 [DH485 Port x]

2.4 [DH485 Port x Commands]

Swap Code Description

Maximum Element Counts for Read/Write Commands

2.5 [DH485 Port x Maps]

To Download the Project File

Ladder Logic MVI56-DH485R ♦ ControlLogix Platform User Manual DH485 Interface Module for Remote Chassis

3.1 Module Data Object (DH485ModuleDef)

3.2 Adding the Module to an Existing Project

4.1 Reading Status Data from the Module

Using the Diagnostic Window in ProSoft Configuration Builder

Navigation

Keystrokes

Viewing Block Transfer Statistics

Viewing Module Configuration

Opening the Database Menu

Opening the DH-485 Port x Menu

Transferring the Configuration File from PC to MVI56 module

Transferring the Configuration File from MVI56 module to PC

Viewing Version Information

Warm Booting the Module

Exiting the Program

Viewing Register Pages

Displaying the Current Page of Registers Again

Moving Back Through 5 Pages of Registers

Moving Forward Through 5 Pages of Registers

Viewing the Previous 100 Registers of Data

Viewing the Next 100 Registers of Data

Viewing Data in Decimal Format

Viewing Data in Hexadecimal Format

Viewing Data in Floating Point Format

Viewing Data in ASCII (Text) Format

Returning to the Main Menu

Viewing Port Configuration

Opening the Command Error List Menu

Opening the Command List Menu

Opening the Override File Map List Menu

Viewing Port Status Data

Viewing Version Information

Returning to the Main Menu

Command List Menu

Redisplaying the Menu

Redisplaying the Current Page

Viewing the Previous Page of Commands

Viewing the Next Page of Commands

Returning to the Main Menu

Redisplaying the Current Page

Viewing the Previous 20 Commands

Viewing the Previous Page of Commands

Viewing the Next 20 Commands

Viewing the Next Page of Commands

Returning to the Main Menu

4.3 LED Status Indicators

Normal Data Transfer

Read Block

Write Block

Command Control Blocks

Initialize Output Data

Change Command Type Control Block

Warm Boot Block

Cold Boot Block