Rockwell Automation 2711E User Manual

Allen-Bradley

PanelBuilder1400e

Configuration

Modbus

Software for Windows

(Cat. No. 2711E–UMOD)



User Manual

Important User Information

Because of the variety of uses for the products described in this publication, those responsible for the application and use of this control equipment must satisfy themselves that all necessary steps have been taken to assure that each application and use meets all performance and safety requirements, including any applicable laws, regulations, codes and standards.

The illustrations, charts, sample programs and layout examples shown in this guide are intended solely for purposes of example. Since there are many variables and requirements associated with any particular installation, Allen-Bradley does not assume responsibility or liability (to include intellectual property liability) for actual use based upon the examples shown in this publication.

Allen-Bradley publication SGI-1.1, Safety Guidelines for the

Application, Installation, and Maintenance of Solid-State Control

(available from your local Allen-Bradley office), describes some important differences between solid-state equipment and electromechanical devices that should be taken into consideration when applying products such as those described in this publication.

Reproduction of the contents of this copyrighted publication, in whole or in part, without written permission of Allen-Bradley Company, Inc., is prohibited.

Throughout this manual we use notes to make you aware of safety considerations:

ATTENTION: Identifies information about practices or circumstances that can lead to personal injury or

death, property damage or economic loss.

Attention statements help you to:

• identify a hazard

• avoid the hazard

• recognize the consequences

Important: Identifies information that is critical for successful

application and understanding of the product.

PanelBuilder, PanelView, Data Highway Plus, ControlNet, DH+, and SLC are trademarks, and PLC, PLC-2, and PLC-3 are registered trademarks of Allen-Bradley Company, Inc. RSView is a trademark of Rockwell Software, Inc. IBM, PC, PS/2, VGA, and PC-DOS are registered trademarks of International Business Machines Corporation. Epson is a registered trademark of Seiko Epson Corporation. Microsoft, Windows, MS, and MS-DOS are registered trademarks of Microsoft Corporation. Mouse Systems is a trademark of MSC Technologies, Inc. AutoCAD is a registered trademark of Autodesk, Inc. Taylor, and ProWORXPLUS are registered trademarks of Taylor Industrial Software, Inc. MODICON, MODSOFT, Quantum, and Modbus are registered trademarks of AEG Schneider Automation, Inc. All other brand and product names are trademarks of their respective companies and are hereby acknowledged.

  

Preface

About this Manual P–1. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Registering Your Copy of PanelBuilder 1400e P–1. . . . . . . . . . . . . . . .

Other Documentation P–1. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

What’s in This Manual? P–2. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Who Should Read This Manual P–3. . . . . . . . . . . . . . . . . . . . . . . . .

Terminology P–4. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Conventions Used P–4. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Mouse Conventions P–4. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Selection Conventions P–4. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Selection Conventions in Dialog Boxes P–5. . . . . . . . . . . . . . . . .

Key Conventions P–5. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Command Conventions P–5. . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Before You Begin P–6. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Supported Devices P–6. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Technical Support Services P–6. . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Overview of PanelBuilder 1400e with Modbus Connectivity

Planning an Application for Modbus

Basic Application Operations

Chapter 1

About PanelBuilder 1400e 1–1. . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

PanelBuilder , PanelView Terminals, and the Controller or Other Modbus

Slave Device 1–1. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

PanelBuilder 1400e 1–2. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

PanelView Operator Terminals 1–2. . . . . . . . . . . . . . . . . . . . . . . . .

The Controller or Other Modbus Slave Device 1–5. . . . . . . . . . . . . .

Understanding the Modbus Network 1–5. . . . . . . . . . . . . . . . . . . . .

Chapter 2

Defining Nodes and Scan Classes 2–1. . . . . . . . . . . . . . . . . . . . . . . .

Defining the Nodes 2–2. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Recording Node Information 2–2. . . . . . . . . . . . . . . . . . . . . . . . . . .

About Scanning 2–3. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Recording Tag Information 2–3. . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Chapter 3

Creating a New Application 3–1. . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Creating Reports 3–1. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Additional Report on Options 3–2. . . . . . . . . . . . . . . . . . . . . . . . . .

Publication 2711E-6.12 – November 1997

Table of Contentstoc–ii

Defining Communications

Changing the Network Type

Defining Tags

Chapter 4

Configuring Communications 4–1. . . . . . . . . . . . . . . . . . . . . . . . . . . .

Setting up Terminal Communications 4–2. . . . . . . . . . . . . . . . . . . . .

Setting the Driver Parameters 4–2. . . . . . . . . . . . . . . . . . . . . . . .

Configuring Nodes 4–2. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Configuring Scan Classes 4–5. . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Chapter 5

Converting from DH+ to Modbus 5–1. . . . . . . . . . . . . . . . . . . . . . . . . .

Converting from Remote I/O to Modbus 5–2. . . . . . . . . . . . . . . . . . . . .

Converting from ControlNet to Modbus 5–4. . . . . . . . . . . . . . . . . . . . .

Converting from Modbus to DH+ 5–5. . . . . . . . . . . . . . . . . . . . . . . . . .

Converting from Modbus to Remote I/O 5–6. . . . . . . . . . . . . . . . . . . . .

Converting from Modbus to ControlNet 5–7. . . . . . . . . . . . . . . . . . . . .

Chapter 6

Tag Types 6–1. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Read and Write Tags 6–1. . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Data Sources 6–2. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Device 6–2. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Configuring Tag Type 6–2. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Configuring an Analog Tag 6–3. . . . . . . . . . . . . . . . . . . . . . . . . . . .

Modbus Address Space 6–6. . . . . . . . . . . . . . . . . . . . . . . . . . . .

Addressing Syntax 6–7. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Configuring a Digital Tag 6–8. . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Addressing Syntax 6–9. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Configuring a String Tag 6–10. . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Addressing Syntax 6–12. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Configuring a Block Tag 6–13. . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Addressing Syntax 6–14. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Specifying a Data Source 6–15. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Device Data Source 6–16. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Validation 6–16. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Specifying Device as the Data Source 6–16. . . . . . . . . . . . . . . . . . . .

Tag Database Import and Export 6–17. . . . . . . . . . . . . . . . . . . . . . . . . .

Database Formats Supported 6–17. . . . . . . . . . . . . . . . . . . . . . . . . .

CSV File Column Ordering 6–23. . . . . . . . . . . . . . . . . . . . . . . . . . . .

Creating a New Tag Database 6–24. . . . . . . . . . . . . . . . . . . . . . . . . . .

Publication 2711E-6.12 – November 1997

Table of Contents toc–iii

Configuring the PanelView Terminal for Modbus Communications

Transferring Applications

Troubleshooting for Modbus Applications

Sample Worksheets

Chapter 7

Configuring the Modbus Communication Interface Card 7–1. . . . . . . . .

Installing Modbus Firmware in the PanelView Terminal 7–3. . . . . . . . . .

Configuring the Terminal Network Setup Screen 7–5. . . . . . . . . . . . . . .

Chapter 8

V alidating Applications 8–1. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

About Application File Transfers and Modbus 8–1. . . . . . . . . . . . . . . . .

Chapter 9

Modbus Communication Errors 9–1. . . . . . . . . . . . . . . . . . . . . . . . . . .

Appendix A

Index

Publication 2711E-6.12 – November 1997



About this Manual

Registering Your Copy of PanelBuilder 1400e

Terminology

Conventions Used

The term PanelBuilder refers to PanelBuilder 1400e Configuration Software for Windows. Where confusion may arise between the current and previous versions of the software, the current release of the software is “PanelBuilder 1400e, Version 3.”

Similarly, the terms terminal and PanelView terminal refer to a PanelView 1000e or 1400e terminal. Where confusion may arise between the 1000e and 1400e terminals and previous revisions, specific series and revision names will be used.

Note: PanelView 1200 and 1200e terminals do not support Modbus communications.

The terms programmable controller and controller refer to the Modicon line of Programmable Logic Controllers or any other controlling device.

Information is provided in a consistent way throughout the entire PanelBuilder user documentation set. There are mouse selection, shortcut key, and command conventions.

Mouse Conventions

You can use a mouse with one or two buttons. This manual assumes that if you have a multiple-button mouse, the left mouse button is configured as the primary mouse button. Procedures that require you to click a secondary button refer to it as the right mouse button.

Selection Conventions

This word or phrase Means

Choose

Choose OK Either click on the OK button with the mouse or press Enter

Select Either highlight the piece of text you want your next action to

Click Position the mouse pointer on the object, area, or field, and

Double-click Position the mouse pointer on the object, area, or field, and

Carry out a menu command or a command button in a dialog box or Help window. Choose also means to double-click an icon.

on the keyboard to carry out the action.

affect, or select a specific dialog box option.

click the left button once.

click twice quickly.

Publication 2711E-6.12 – November 1997

Preface P–5

Selection Conventions in Dialog Boxes

Dialog boxes contain standard Windows fields that require different selection conventions. Refer to your Windows user documentation for information on the selection conventions.

The following shortcut keys allow you to complete dialog boxes faster:

This key or key combination

Tab

Shift+Tab Moves the cursor to the previous field, option, or command

Alt+underlined letter Selects an option, or displays a drop-down list. Alt+ Displays a drop-down list. Spacebar Turns check boxes on or off.

Does this

Moves the cursor to the next field, option, or command button.

button.

Key Conventions

This key combination Means

Key1+Key2

Shift+click Press and hold the Shift key while you click an object with

Press and hold the first key while you press the second key. For example, press “Ctrl+A” means to press the Ctrl key, and while pressing it, press the A key. Then release both keys.

the pointer.

Command Conventions

Following are three methods for carrying out commands. Instructions in this manual don’t always outline each method.

• choosing a menu command

• choosing an icon on the toolbar

• using a key combination

For example:

Use any of these commands to open an application:

Choose “Open Application” in the File menu. Choose from the toolbar.

Press Ctrl+O.

Publication 2711E-6.12 – November 1997

PrefaceP–6

Before You Begin

Supported Devices

Before you begin, you should already have installed and know how to operate this equipment and software:

• a personal computer with at least a 486, 25-MHz microprocessor

and at least 8 MB Random Access Memory (RAM) (16 MB recommended), and SVGA monitor with 256 colors (recommended). For users working with imported .dxf files, at least 16 MB RAM is required.

If you want to resize graphic images in PanelBuilder, set your display adapter to 65,536 colors.

• Microsoft Windows 3.1 operating system and above, or

Windows 95

• the family of programmable logic controllers you’ll be

monitoring and controlling

PanelView terminals have been tested and verified to work with the following Modbus-capable devices:

• Quantum 140 CPU 113 02

• Quantum 140 CPU 113 03

• Compact PC-A984-145

• Modicon 984X

• BM85 Bridge Multiplexer

• LD485A-MP line driver

Technical Support Services

The PanelView terminal is always a master device on the Modbus network, never a slave.

If you have questions about PanelBuilder, please consult the manuals or Help first. If you can’t find the answer, take advantage of our Technical Support Fax Back system, available 24 hours a day, 7 days a week at 1-216-646-5436, or browse through our technical support document library at http://www.ab.com/mem/prodserv/services/ technotes/techmain.html on the World Wide Web.

Alternatively, contact: Allen-Bradley

Technical Support 1 Allen Bradley Drive Mayfield Heights, Ohio 44124-6118

or call 1-216-646-6800 or fax 1-216-646-6890 for technical support between the hours of 8

AM and 5 PM (EST), Monday to Friday.

Publication 2711E-6.12 – November 1997

Preface P–7

Please have the serial number for your software ready when you call, or include it on your fax. You can find this number in three places:

• on the Software Registration card that was shipped with your

software

• on the screen that appears when you start up PanelBuilder

• in the main Help menu, when you choose “About”

If you have questions about your Modbus controller or device, contact the manufacturer directly.

Publication 2711E-6.12 – November 1997

 

Overview of PanelBuilder 1400e with Modbus Connectivity

This chapter provides an overview of PanelBuilder 1400e. It describes these topics:

• what PanelBuilder is

• how PanelBuilder interacts with the PanelView terminal and the

controller or other Modbus slave device

• important new PanelBuilder features

About PanelBuilder 1400e

PanelBuilder, PanelView Terminals, and the Controller or Other Modbus Slave Device

PanelBuilder 1400e is a software package that runs under Microsoft Windows 3.1 and Windows 95. With it you create and design control panel applications for PanelView operator terminals.

As human-machine interfaces, these control panel applications enable an operator to monitor and control automated plant processes.

Important: To create applications for Modbus networks, you need

PanelBuilder Version 3 or later.

The relationship between PanelBuilder, the PanelView terminal, and the controller or other Modbus slave device is as follows:

• PanelBuilder—The Modbus application is created in

PanelBuilder on the personal computer, and downloaded to the PanelView terminal.

• Controller or other Modbus slave device—When

communicating over a Modbus network, the controller or other Modbus slave device can respond to queries from the PanelView terminal and other input or output devices.

• PanelView terminal—The PanelView terminal displays the

process status information sent from the controller. This enables the operator to make decisions about the process. The operator provides input back to the controller. The PanelView terminal is a master on the Modbus network, never a slave. In addition:

• the PanelView 1200/1400e Transfer Utility is used to transfer

Modbus applications from the development computer to the terminal.

• the PanelView Serial Firmware Upgrade Utility is used to

install or upgrade firmware in the PanelView terminal. You need to install Modbus-capable firmware in all PanelView terminals you intend to connect to the Modbus network.

Publication 2711E-6.12 – November 1997

1–2 Overview of PanelBuilder 1400e with Modbus Connectivity

Note: The development computer doesn’t need to be connected to the controller or the PanelView terminal to run the process. It must be connected only when you’re installing or upgrading firmware in the PanelView terminal, using the PanelView Serial Firmware Upgrade Utility, or when downloading or uploading the application serially. To upload or download the application you can also install the PanelView 1200/1400e Transfer Utility on a portable computer, transfer the application to the portable computer, and then upload or download it from the portable computer. See the PanelView 1200/1400e Transfer Utility User Manual for details. For information about installing or upgrading the terminal’s firmware, see Chapter 7, “Configuring the PanelView Terminal for Modbus Communications,” in this manual, or see the Readme file on the PanelView Serial Firmware Upgrade Utility diskette.

PanelBuilder 1400e

PanelBuilder is the development software package you use to create and configure control panel application screens. Applications developed with PanelBuilder software on a personal computer are downloaded to PanelView terminals, where they are run.

PanelBuilder 1400e Software

Development Computer

PanelView Operator Terminals

The following terminals will run PanelBuilder 1400e applications on the Modbus network:

• PanelView 1000e terminals, Series A and above, running

Version 3 and later firmware

• PanelView 1400e terminals, Series A and above, running Version 3

and later firmware

Publication 2711E-6.12 – November 1997

1–3Overview of PanelBuilder 1400e with Modbus Connectivity

Note: To communicate over a Modbus network, you must use a PanelView 1000e or 1400e terminal that has been upgraded to include a supported Modbus ISA communications card and Version 3 firmware with the Modbus communications driver. The PanelView Serial Firmware Upgrade Utility must be used to install Modbus-capable firmware in the terminal. For details about installing and configuring a Modbus communications device (serial card), and installing Modbus-capable firmware, see Chapter 7, “Configuring the PanelView Terminal for Modbus Communications.”

See the PanelView Enhanced Modbus Communications Option Kit Release Note, Publication Number 2711E-6.12.1, for a list of currently-supported Modbus communications cards.

The application screens created in PanelBuilder appear on the PanelView terminal, replacing traditional hard-wired control panels. They provide the physical interface between the controller and the human operator.

Application screens contain objects that function like control panel components. By using these objects to enter data or carry out commands, the operator can monitor and control the process.

For information about installing and running PanelBuilder, see

Getting Started with PanelBuilder 1400e Configuration Software for Windows, Publication Number 2711E-818. This manual also contains

a tutorial that guides you through enhancing an existing application and running it on the PanelView terminal. A Modbus version of this tutorial is also provided. The following .pvc files in the Tutorial directory are the Modbus versions, which need to be enhanced:

• Mkctutor.pvc

• Mtctutor.pvc

The following .pvc files in the Tutorial directory are the Modbus versions which have been enhanced:

• Mtutork.pvc

• Mtutort.pvc

The program for Modicon controllers is called “Tutorial,” and it is located in the Tutorial directory.

Publication 2711E-6.12 – November 1997

1–4 Overview of PanelBuilder 1400e with Modbus Connectivity

PanelView 1000e Terminals

PanelView 1400e Terminals

Touch Screen Terminals

Keypad Terminals

Publication 2711E-6.12 – November 1997

The Controller or Other Modbus Slave Device

When communicating over a Modbus network, the controller can respond to queries from the PanelView terminal and other input or output devices.

Modicon Controller

24762

1–5Overview of PanelBuilder 1400e with Modbus Connectivity

The PanelView terminal can be connected to a controller, or other slave device on the Modbus network. The terminal can control and monitor coils, inputs, and registers in these devices on the network.

Understanding the Modbus Network

The following illustration shows the relationship between PanelBuilder, the PanelView terminal, and the controller. In the following illustration, the PanelView terminal is connected over Modbus:

Publication 2711E-6.12 – November 1997

1–6 Overview of PanelBuilder 1400e with Modbus Connectivity

The application is created in PanelBuilder on the personal computer, and downloaded to the PanelView operator terminal.

Development Computer

Serial Connection

PanelView

The PanelView terminal queries the controller for process or machine status information.

Operator input to the terminal is sent to the controller. The controller uses this information to control the machine or process.

PanelView 1000e/1400e

Terminal

(Touch Screen)

Modem

Modbus

Programmable

Controller

Machine or Process

Modem

Modbus

Programmable

Controller

Machine or Process

24717

Publication 2711E-6.12 – November 1997

 

Planning an Application for Modbus

This chapter provides information about planning a Modbus application, including defining nodes. For details about assigning scan classes and assigning tags, refer to Chapter 2, “Planning Applications,” in the PanelBuilder 1400e Configuration Software for Windows User Manual, publication 2711E-819.

To plan a Modbus application, use the Modbus Communications Worksheet and the Device Tags Worksheet (included in Appendix A). They help you identify the devices with which your application will be communicating and the device addresses relevant to your application.

Use the information you record in these worksheets when assigning tags to objects in the Tag Database editor and defining communications using the Nodes editor and Scan Classes editor.

Defining Nodes and Scan Classes

Record node and scan class information on the Modbus Communications worksheet to help keep track of terminal communication information. Use these worksheets as a reference when configuring nodes in the Nodes editor, and when assigning scan classes to tags in the Tag Database editor. See Chapter 4, “Defining Communications,” for details about working with these editors.

Publication 2711E-6.12 – August 1997

2–2 Planning an Application for Modbus

Defining the Nodes

A node is a Modbus slave device with which your application will be communicating on a network. For each node, you must identify the type of addressing the device uses (5- or 6-digit addressing), its station address, and the timeout value. Each node must be given a name to be used when defining tags.

Recording Node Information

For each node, fill in:

• Node Name: A user-defined node name. The name can be up to

40 characters long, and can include letters, numbers, dash ( – ), and the underscore character ( _ ). You cannot use spaces.

Tip: Use a name that will help you to identify your Modbus device when you are assigning tags later in your application. For example, you could name your Modbus devices according to their locations or the machine or part of the process they will be controlling or monitoring.

Note: The node name “Unsolicited_Msgs is reserved for system use in DH+ applications and cannot be assigned to a node defined by the user. It allows the terminal to support unsolicited messages to and from the controller. You cannot use a node with this name in Modbus applications.

• Device: The type of controller or Modbus device. Specify a 5- or

6-digit addressable device.

• Channel: The Channel number is 1 by default. The application

network type determines this channel. You cannot change this value.

• Station: The address that identifies the Modbus device’s location

on the network. Valid station addresses are between 1 and 247 (decimal).

Publication 2711E-6.12 – August 1997

2–3Planning an Application for Modbus

About Scanning

Note: The PanelView terminal communicates with local Modbus stations or with remote, bridged devices if a BM85 module is connected and configured for the network.

• Enabled: If a node is enabled, the terminal will communicate

with the device at the node. If the node is not enabled, the terminal will not communicate with the device. Instead, the PanelView terminal stores values to be written to the device. This allows system designers to test their applications without setting up communications, and to avoid communication errors at the terminal during testing.

• Timeout: The number of seconds the PanelView terminal should

wait before reporting a communication error. Three seconds is the default when a new node is created.

Scanning works the same way for Modbus as it does for Data Highway Plus. For information about scanning, refer to Chapter 2, “Planning Applications,” in the PanelBuilder 1400e Configuration Software for Windows User Manual, publication 2711E-819.

Recording Tag Information

Assigning tags to objects for the Modbus release of PanelBuilder is similar to assigning tags to objects for DH+. You assign tags with the Data Source type Device for Modbus applications. Analog, digital, string, and block tags can all be used in Modbus applications. Where differences exist between DH+ and Modbus applications, with respect to assigning tags, they are highlighted in Chapter 6, “Defining Tags.”

For generic information about assigning tags, see Chapter 2, “Planning Applications,” in the PanelBuilder 1400e Configuration Software for Windows User Manual, publication 2711E-819.

Note: You can use the Device Tags Worksheet to record tag information for each dynamic object in a PanelBuilder application for Modbus.

Note: For Modbus Device tags, the Tag Database editor supports the full addressing syntax and range supported by the 5- and 6-digit addressable devices.

Publication 2711E-6.12 – August 1997

 

Basic Application Operations

This chapter supplements the information in the PanelBuilder 1400e Configuration Software for Windows User Manual, publication 2711E-819. It describes only changes to basic application operations for the Modbus network. For detailed information about other basic application operations, consult Chapter 3, “Working with Applications,” in the PanelBuilder 1400e Configuration Software for Windows User Manual, publication 2711E-819.

This chapter describes how to create a new application, and some changes to report options.

Creating a New Application

Note: PanelView 1200 and 1200e terminals do not support Modbus communications.

To create a new application for Modbus:

1. Select the Application Type and highlight the Modbus option in

the Network Type list box.

Creating Reports

2. Choose OK.

Creating reports for a Modbus application is the same as for DH+ and Remote I/O applications. The only difference is the PLC Communications report.

For detailed information about creating reports, see “Creating Application Reports” in Chapter 3, “Working with Applications,” in the PanelBuilder 1400e Configuration Software for Windows User Manual, publication 2711E-819.

Publication 2711E-6.12 – November 1997

3–2 Basic Application Operations

Additional Report on Options

You can generate a PLC Communications report for a Modbus application that will display the following information:

• communications setup information

• node and scan class definitions

Publication 2711E-6.12 – November 1997

+ 53 hidden pages