Rockwell Automation 2706-MB1 User Manual

Allen-Bradley

MessageBuilder
Configuration

User

Software

(Catalog No. 2706-MB1)

Manual

Important User Information

Solid state equipment has operational characteristics differing from
those of electromechanical equipment. “Safety Guidelines for the
Application, Installation and Maintenance of Solid State Controls”
(Publication SGI-1.1) describes some important differences between
solid state equipment and hard–wired electromechanical devices.
Because of this difference, and also because of the wide variety of
uses for solid state equipment, all persons responsible for applying
this equipment must satisfy themselves that each intended
application of this equipment is acceptable.

In no event will the Allen-Bradley Company be responsible or liable
for indirect or consequential damages resulting from the use or
application of this equipment.

The examples and diagrams in this manual are included solely for
illustrative purposes. Because of the many variables and
requirements associated with any particular installation, the
Allen-Bradley Company cannot assume responsibility or liability for
actual use based on the examples and diagrams.

No patent liability is assumed by Allen-Bradley Company with
respect to use of information, circuits, equipment, or software
described in this manual.

Reproduction of the contents of this manual, in whole or in part,
without written permission of the Allen-Bradley Company 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.

Attentions help you:

• identify a hazard

• avoid the hazard

• recognize the consequences

Important: Identifies information that is especially important for

successful application and understanding of the product.

MessageBuilder and MessageView are trademarks of Alen-Bradley Company, Inc.
PLC and PLC–5 are registered trademarks of Allen-Bradley Company, Inc.
SLC 5/03, SLC 5/04, Dataliner and AdaptaScan are trademarks of Allen-Bradley Company, Inc.
INTERCHANGE is a trademark of Rockwell Software Inc.
Intel is a registered trademark of Intel Corporation.
MS-DOS and Microsoft Windows are registered trademarks of Microsoft Corporation.

Preface

Table of Contents

Introducing MessageBuilder Configuration Software

Installing MessageBuilder Software

MessageBuilder Basics

Chapter 1

What is MessageBuilder? 1–1. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

MessageBuilder Software Features 1–2. . . . . . . . . . . . . . . . . . . . . . . .

Typical Messages in an Application 1–5. . . . . . . . . . . . . . . . . . . . . . . .

Typical Message Contents 1–6. . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Chapter 2

System Requirements 2–1. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Installing MessageBuilder Software 2–2. . . . . . . . . . . . . . . . . . . . . . . .

INTERCHANGE Device Configuration Utility 2–7. . . . . . . . . . . . . . . . .

Troubleshooting the Installation Procedure 2–12. . . . . . . . . . . . . . . . . . .

Chapter 3

Windows Environment 3–1. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

MessageBuilder Window 3–2. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Message Editor Table View 3–4. . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Opening and Closing Menus 3–7. . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Status Bar and Toolbars 3–8. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Message Editor Terminal View 3–10. . . . . . . . . . . . . . . . . . . . . . . . . . .

Dialogs 3–11. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Getting Help 3–14. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Planning an Application

Chapter 4

Design Checklist 4–1. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Safety Considerations 4–2. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Applications and Projects 4–3. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Messages 4–4. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Controlling Devices 4–7. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Triggering a Message 4–9. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Slaving 4–15. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Slave Device 4–18. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Historical Event Stack 4–19. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Function Keys 4–20. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Function Key Types 4–23. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

LED Indicators 4–25. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Handshaking 4–26. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Publication 2706-817

Table of Contentstoc–ii

Tags 4–31. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Data Types 4–33. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Address Worksheet 4–35. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Defining Tags 4–36. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Scaling Data Display Variables 4–37. . . . . . . . . . . . . . . . . . . . . . . . . . .

Scaling Data Entry Variables 4–38. . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Precision and Rounding 4–41. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Communications Overview

Working with Application Files

Creating Messages

Chapter 5

MessageView 421 Terminal Ports 5–1. . . . . . . . . . . . . . . . . . . . . . . . .

RS-232 Port Communication 5–3. . . . . . . . . . . . . . . . . . . . . . . . . . . .

ASCII Triggering Commands 5–8. . . . . . . . . . . . . . . . . . . . . . . . . . . .

Remote I/O Communication 5–12. . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Discrete I/O 5–15. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Block Transfer 5–17. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Chapter 6

Starting MessageBuilder 6–1. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Creating a New Application 6–2. . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Opening an Existing Application 6–4. . . . . . . . . . . . . . . . . . . . . . . . . .

Saving an Application 6–6. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Renaming and Describing an Application 6–8. . . . . . . . . . . . . . . . . . . .

Closing an Application 6–10. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Exiting MessageBuilder 6–10. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Chapter 7

The Message Editor Dialog 7–1. . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Working with Messages 7–2. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Selecting Messages 7–3. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Editing Messages 7–5. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Set Preferences 7–14. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Message Editor Terminal View 7–16. . . . . . . . . . . . . . . . . . . . . . . . . . .

Embedded V ariables and Graphics 7–18. . . . . . . . . . . . . . . . . . . . . . . .

Numeric V ariable Display 7–23. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

ASCII V ariable Display 7–26. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Numeric V ariable Entry 7–27. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

ASCII V ariable Entry 7–30. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Message Attributes 7–33. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Slaving 7–41. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Function Keys 7–48. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

LED Attributes 7–52. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Special Messages 7–54. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Publication 2706-817

Table of Contents toc–iii

Working with Tags

Managing Projects

Terminal and Communication Setup

Chapter 8

Using the Tag Editor 8–1. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Validating Tag Addresses 8–4. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Defining Tags 8–5. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Working With Tags 8–8. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Finding Tags 8–11. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Sorting Tags 8–12. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Printing Tags 8–13. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Tag Import/Export Utility 8–17. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Chapter 9

About Projects 9–1. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Managing Projects 9–2. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Managing Devices in Projects 9–5. . . . . . . . . . . . . . . . . . . . . . . . . . . .

Loading/Replacing Tags or Devices in a Project 9–7. . . . . . . . . . . . . . .

Restoring a Project 9–9. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Chapter 10

Overview of Terminal Setup 10–1. . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Changing the Terminal Type 10–3. . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Remote I/O Communications 10–4. . . . . . . . . . . . . . . . . . . . . . . . . . . .

Block Transfers 10–7. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

RS-232 Main Port Communications 10–9. . . . . . . . . . . . . . . . . . . . . . . .

Setting Advanced Terminal Options 10–12. . . . . . . . . . . . . . . . . . . . . . . .

Setting Format for Time and Date 10–18. . . . . . . . . . . . . . . . . . . . . . . . .

Defining Control Tags 10–21. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Defining Status Tags 10–25. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Auxiliary Port Setup 10–27. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Validating Applications and Transferring Files

Chapter 11

Helpful Hints 11–1. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

V alidating Applications 11–2. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Transfer Utilities 11–5. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Downloading an Application to a Terminal 1 1–6. . . . . . . . . . . . . . . . . . .

Downloading to a DOS file 1 1–8. . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Downloading Date/Time to Real Time Clock 1 1–9. . . . . . . . . . . . . . . . . .

Uploading an Application from a Terminal 11–10. . . . . . . . . . . . . . . . . . .

Uploading the Historical Event Stack 1 1–13. . . . . . . . . . . . . . . . . . . . . . .

Using the MessageView File Transfer Utility 1 1–15. . . . . . . . . . . . . . . . . .

Terminal Upgrade 11–18. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Publication 2706-817

Table of Contentstoc–iv

Creating Reports

Menus and Commands Summary

Tool Summary

Configuration Software Error and Warning Messages

Validation Error Messages

Chapter 12

Types of Reports 12–1. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Creating and Printing a Report 12–2. . . . . . . . . . . . . . . . . . . . . . . . . . .

Changing the Report Setup 12–3. . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Previewing a Report 12–5. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Setting up a Printer 12–6. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Sending a Report to a File 12–7. . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Appendix A

Appendix B

Appendix C

Appendix D

Upload/Download Error Messages

Global Configuration Parameters

Tags and Data Types

Tag Address Worksheet

ASCII and Extended ASCII Characters

Glossary

Appendix E

Appendix F

Appendix G

Appendix H

Appendix I

Index

Publication 2706-817





Welcome to MessageBuilder Configuration Software. You can use
this software to create control panel applications for MessageView
421 Operator Terminals.

MessageBuilder software allows you to create applications designed
specifically to control processes in your plant. When you load a
MessageBuilder application in a MessageV iew terminal, the terminal
displays messages that:

• give information about the operation

• ask for input to control the operation.

Registering Your Copy of MessageBuilder Software

Intended Audience

Your software registration card is located in the envelope with the
software disks. To register your software, mail the card to this
address:

Allen-Bradley
Global Technical Support
6680 Beta Drive
Mayfield Village, Ohio 44143.

Or fax the card to [phone].

This manual is a resource to help you design message display
applications that will run in a MessageView 421 terminal. Since
there are many options designed to give a smooth-running operation
under any circumstances, you should become familiar with the
choices to be made.

MessageBuilder Configuration Software runs under Microsoft
Windows. You should know how to use a mouse, choose commands,
and work with windows and dialog boxes. To learn basic windows
techniques, read the User’s Guide that came with your Microsoft
Windows package.

PLC and SLC logic controllers and ASCII Triggering devices are
an important part of the systems that MessageBuilder applications
control. You should understand how controllers work, especially the
program and data files. See the user manuals for the controllers used
in your operation.

Publication 2706-817

PrefaceP–2

Software Package

Conventions

The MessageBuilder Configuration Software package (Catalog No.
2706-MB1) comes with:

• 4 (3

1

/2 inch) installation disks

– 3 MessageBuilder Software disks (including

INTERCHANGE utility)

– 1 A-B Utilities disk.

• This manual: MessageBuilder Configuration Software manual

(Publication No. 2706-817).

• MessageView 421 Display Terminal user manual (Publication

No. 2706-816).

This manual uses the following conventions:

• Software or MessageBuilder software refers to the

MessageBuilder Configuration Software.

• Terminal refers to a MessageView 421 terminal.

• Windows (with a capital “W”) refers to Microsoft Windows or to

the Window menu in MessageBuilder. MessageBuilder windows
are written with a small “w”.

• Keys on the keyboard appear in boldface small capital letters:

– the Shift key (on the computer) appears as SHIFT in the text
– the Acknowledge key (on the terminal) appears as ACK.

☞ The Release.txt and Readmekt.txt

files contain the most recent
installation information.

Key combinations

• A hand with italicized text in the left margin gives helpful hints.

MessageBuilder software often gives a choice of methods for
selecting a command. Use the most convenient one.

• Select a tool on the toolbar.

A toolbar is displayed along the top of the screen specific to what
you are doing. Simply click on the appropriate tool and it is
activated. Appendix B illustrates all tools in all the toolbars.

• Use a key combination.

Certain commands in the File and Edit menus have a key
combination. Use it instead of selecting the command.

• Select a menu command.

Click the menu name and then the command name. Or press the

ALT key and the underlined letter of the menu name to drop the

menu, then type the underlined letter of the command. Appendix
A describes all commands in all the menus.

For example, to open an application from the initial MessageBuilder
screen, do one of the following:

– click on the Open File tool, or
– press CTRL + O, or
– type ALT + F then type O, to select Open from the File menu,

Publication 2706-817

and the File Open dialog appears.

Preface P–3

Contents of the Manual

This manual is organized as follows:

Chapter Title Description

Preface

1

2

3 MessageBuilder Basics

4 Planning an Application

5

6

7 Creating Messages

Introducing

MessageBuilder Software

Installing MessageBuilder

Software

Communications

Overview

Working with Application

Files

Describes the purpose and contents of the
manual, and its intended audience.

Describes MessageBuilder Configuration
Software and some of its features.

Explains how to install MessageBuilder and
INTERCHANGE software on a personal
computer.

Explains how to use MessageBuilder
software’s menus, tools and dialogs. Also how
to use the Help system.

Gives guidelines for designing an application,
including safety considerations.

Gives guidelines for setting up MessageView
terminal communications.

Explains how to open and close
MessageBuilder software, and how to open,
close and save application files.

Shows how to create messages and set their
attributes. Also how to embed variables and
graphics in a message, and how function
keys work.

Related Publications

Explains how to use the Tag Editor feature of

8 Working with Tags

9 Managing Projects

10

11

12 Creating Reports Tells how to design a report and print it.

Terminal and

Communication Setup

Validating Applications
and Transferring Files

MessageBuilder software. Tags specify the
addresses in which variable data are stored.

Tells how to link a project to an application,
and how to copy, rename or delete projects.
Also shows how to work with devices in
projects.

Tells how to set operating and runtime
communication parameters for the
MessageView 421 terminal and a logic
controller.

Tells how to validate an application. Explains
several methods that transfer it between a
computer and a terminal or a disk file.

You should have the MessageView Display Terminal User Manual
(Publication No. 2706-816) at hand while creating an application.
Also refer as needed to the manual(s) for the controller the system
will be using.

Information and procedures relating to INTERCHANGE Software
and Microsoft Windows are given in this manual. For further details,
refer to the manuals for these products.

Publication 2706-817

PrefaceP–4

Allen-Bradley Support

Local Product Support

Contact your local Allen-Bradley representative for:

• sales and order support

• product technical training

• warranty support

• support service agreements.

Technical Product Assistance

If you have questions about MessageBuilder Configuration software:

• check online Help

• review information on the subject in this manual

• review the release notes: these are separate icons in the

MessageBuilder Group in the Windows Program Manager

• review any technical notes on the subject that you have received

from Allen-Bradley.

If you still have a question, call your local Allen-Bradley
representative.

If you need more help, call:

Allen-Bradley
Global Technical Support
6680 Beta Drive
Mayfield Village, Ohio 44143.

Phone numbers:

• In the USA and Canada, call 1-800-289-2279.

• Outside the USA and Canada, call your local Allen-Bradley

office, or call USA [phone].

• Fax number: [phone].

Note: If you need to call Allen-Bradley for technical assistance,
please have the serial number of your software available. It may be
found in three places:

• on the software registration card

• on the welcome screen that appears when MessageBuilder starts

• in the main Help menu, choose About MessageBuilder to see the

About MessageBuilder dialog, which has:

– the release date and version number of MessageBuilder

software

– the release date and version number of the Allen-Bradley

Utilities software.

Publication 2706-817

What is MessageBuilder?

Chapter

1

Introducing MessageBuilder
Configuration Software

This chapter covers the following topics:

• What is MessageBuilder?

• MessageBuilder software features

• Typical messages in an application

• Typical message contents.

MessageBuilder is a Microsoft Windows software package. An
application designer can use it to create custom applications for
MessageView 421N, 421F and 421D terminals.

MessageBuilder software makes creating an application as easy as
possible, by supplying dialog boxes, toolbars and menus. These
include:

• menus and toolbars keyed to the current situation

• dialogs to set up the computer workstation, the MessageView

terminal and the interface to controllers used in the process.

• dialogs in which applications and projects are created and edited

• the Message Editor Table View, in which messages are created

and edited

• the Message Editor Terminal View, which previews individual

messages

• the Tag Editor, in which tags are created and edited

• validation of the application before it is downloaded to a terminal,

and on command while the application is being created

• printer dialogs for making permanent records of specific or

general aspects of the application

• on-line and context-sensitive help.

Publication 2706-817

1–2 Introducing MessageBuilder Configuration Software

MessageBuilder Software Features

MessageBuilder software has a number of features that make
designing an application easier.

Tool or Menu Operation

MessageBuilder software runs under Microsoft Windows. Many
functions can be performed using tools, keystrokes, or menu
commands. Use any or all, whichever you find most convenient.

Selectable Preferences

MessageBuilder lets you set features of the workspace window to
those you prefer. Options such as the Standard Toolbar and the Status
Bar can be toggled on or off, and remain in that state until you
change them. See Page 7–14 for other preferences. When you create
a new application or when you start a new session, MessageBuilder
uses the latest settings.

Status Bar Information

The Status Bar at the bottom of the screen explains what is
happening at the moment. See Page 3–8.

• If you hold the left mouse button down while the cursor is over a

tool, the status bar explains what it does.

• If a process is going on, the status bar reports on how it is doing.

The three spaces at the right end of the status bar give the status of
the keyboard

Help

The Help tools and commands provide a quick way to find
information about any part of MessageBuilder software. See Page
3–14 for a summary of the Help function. To access Help:

CAPS LOCK, NUM LOCK, and SCROLL LOCK keys.

• Click on the Help Question tool and then on an item or command

to get context–sensitive help.

• Press F1 to get specific help on a subject.

• The Help Contents tool displays an index to Help topics.

• Select Contents, Search For Help On, or How To Use Help on the

elp menu, depending on what you need to know.

H

• Select About MessageBuilder to find the copyright date and

version number of MessageBuilder software if you need to call
Allen-Bradley for assistance.

Publication 2706-817

MessageView 421D

1–3Introducing MessageBuilder Configuration Software

Message Editor Table View

Use this dialog to create and edit messages and their attributes used
in the application program.

The Message Editor Table View contains the menu commands and
tools needed to bring up all other dialogs, the Terminal View and the
Tag Editor.

Message Editor Terminal View

Use this view to view the current message, approximately as it will
appear in the MessageView terminal. An application is designed for
a certain type of terminal. The Terminal View displays the face of
that terminal type.

Tag Editor

Use the Tag Editor to enter, update, print, and import/export
application tags. See Chapter 8. Each variable requires a tag, which
defines how the variable interacts with a controller address.

PLC Controller MessageView 421 Terminal

✓

Enter all the tags at once in the Tag Editor Table View before starting
to create any messages. If a tag needs further editing when it is
assigned to a variable, use the Tag Editor Form View.

Terminal and Communication Setup

Access all operating and runtime communication parameters for the
MessageView 421 terminal from the Terminal Setup dialog. See
Chapter 10. These include:

• Remote I/O and RS-232 runtime communication parameters

• power-up defaults

• time/date display format

• control and status tags

• display settings, handshake timeout and trigger priority

• set up slaving or a slave device

• ASCII triggering.

Application Validation

Use validation to check all elements of the application for correct
input. See Chapter 11. When an application is downloaded to a
terminal, MessageBuilder software validates it automatically. You
can also validate the application at any time using the Validate menu
option. View warnings or errors detected during validation, or send
them to a printer or file.

Publication 2706-817

1–4 Introducing MessageBuilder Configuration Software

Application Upload/Download Capabilities

Transfer applications between a MessageView 421 terminal and a
computer running either:

• MessageBuilder Configuration software

• MessageView File Transfer Utility.

See the section starting on Page 11–6.

Upload Historical Event Stack

The MessageView terminal maintains a running log of triggered
messages in a Historical Event Stack file. Upload this file from the
terminal to a computer that has either MessageBuilder software or
the File Transfer Utility installed. See the section starting on Page
4–19 for information on the Historical Event Stack, and on Page
11–13 for information on how to upload it to the computer for
analysis.

Reports

Use the report function to create customized reports for an
application. See Chapter 12. Reports may include any or all of the
following:

• application description

• messages

• message attributes

• terminal settings

• tags and their attributes

• function keys

• LED indicators.

Send reports to a printer supported by Microsoft Windows.
In addition to the report function, you may print information on tags

and their attributes via the Tag Editor (see Page 8–13).

Terminal Upgrade

Use the Upgrade Terminal command to upgrade the firmware in your
MessageView terminal(s). See Page 11–18.

Publication 2706-817

1–5Introducing MessageBuilder Configuration Software

Typical Messages in an Application

An application contains messages. Messages may contain embedded
data variables, graphical symbols, and when designed for
MessageView 421F terminals, may have function keys enabled.

This example of a 421N Terminal View has a message that contains:

• a graphic symbol

• an ASCII Variable Display.

This example of a 421F Terminal View has a message that contains:

• a Time Variable

• a Numeric Variable Display

• enabled Function Keys.

Note: One message may occupy more than one line in the Terminal
View if the Line attribute is selected as “All”.

Publication 2706-817

1–6 Introducing MessageBuilder Configuration Software

Typical Message Contents

Time or Date Display

Time is 16:23 CST.

Date is 06/24/96.

Pressure is 300 PSI.

Temperature Too High.

Enter Flow Rate:

Time Displays indicate the current time (hours, minutes and
seconds) according to the terminal’s Real Time Clock. Specify the
format of the display using the Terminal Setup dialog.

Date Displays indicate the current date (day, month and year)
according to the terminal’s Real Time Clock. Specify the format of
the display using the Terminal Setup dialog.

Set the Real Time Clock using the RTC Download command in the
Application menu.

Display Variables
Numeric Variable Displays shows the current value at a specific

controller address: binary, BCD or signed/unsigned integer. Scaling
(y = mx + b) may be used.

ASCII Variable Displays present status information to the terminal
operator according to the current character array at a specific
controller address.

Entry Variables
Numeric Variable Entries may be used in applications designed for

MessageView 421N and 421F terminals. These variables allow the
terminal operator to enter a numeric value from the terminal keypad.
Scaling (y = mx + b) may be used.

Bar Code Reading:

Publication 2706-817

V alve is open.

ASCII Variable Entries may be used in applications designed for
MessageView 421D, 421N and 421F terminals if the terminal
firmware can support these variables. These variables allow the
terminal operator to enter ASCII characters from an ASCII Input
device via the RS-232 port, or via the numeric keypad on the
terminal.

Graphics
Graphics consist of a set of 32 ISA symbols illustrating

manufacturing components such as motors and containers.

1–7Introducing MessageBuilder Configuration Software

Function Keys

MessageView 421F terminals can use applications that have
Function keys enabled. An enabled function key is assigned to one of
these types:

A Momentary Function Key changes state when pressed and
changes back to the original state when its hold time has expired
after it is released.

A Maintained Function Key changes state when pressed and
remains in the changed state when released. It changes back to the
original state when the Function Key is pressed and released again.

A Latched Function Key changes state when pressed and remains
in that state until the controller unlatches it.

ATTENTION: Function Keys are active only when
they are enabled for a message currently displayed by

!

the terminal. All other Function Keys are non-active.

Example

Suppose a message has function keys F1, F5, and F9 enabled.
Whenever that message is displayed by the MessageView terminal,
these three keys are activated, but the 13 other Function keys remain
inactive.

When the message is terminated, the three Function keys are
inactivated at once.

Note: A Latched Function key remains in its changed state until the
controller unlatches it, but it is not active after its message is
terminated.

Publication 2706-817

System Requirements

Chapter

Installing MessageBuilder
Software

This chapter covers the following topics:

• System requirements

• Installing MessageBuilder software

• INTERCHANGE Device Configuration Utility

• Troubleshooting the installation procedure.

The minimum hardware requirements for installing and running
MessageBuilder software are:

• a personal computer using Intel 386 or 486 processor or

equivalent

• a minimum 4 MB of memory (8 MB recommended) with

minimum of 10 MB permanent swap under virtual memory

• a hard disk with 12 MB of free space

• a 3.5 inch high-density (1.44 MB) disk drive

• a VGA or better monitor that is supported by Windows

• an RS-232 communications port

• a cable for downloading/uploading applications between the

computer and the RS-232 port of a MessageView 421 terminal.
Order Catalog No. 2706-NC13.

2

Also highly recommended are:

• a mouse compatible with Windows

• a printer that supports graphics, compatible with Windows.

The minimum software requirements for installing and running
MessageBuilder software are:

• MS-DOS operating system version 3.31 or later (MS-DOS

version 5.0 or later recommended)

• Microsoft Windows version 3.1 or later, or Windows for

Workgroups version 3.11 or later.

Note: MessageBuilder software utilizing INTERCHANGE V6.1
or later, is compatible with Microsoft Windows 95.

Publication 2706-817

2–2 Installing MessageBuilder Software

Installing MessageBuilder Software

To install MessageBuilder Configuration Software:

1. Insert MessageBuilder software disk 1 in the appropriate

high-density floppy disk drive.

2. Start Windows (if necessary) by typing win at the DOS command

prompt and pressing

3. To start installing MessageBuilder:

ENTER.

• with Windows 3.1x, in the Program Manager window choose Run

from the F

ile menu (ALT + F, R)

• with Windows 95, in the Start menu choose Run (MS key + R)

4. In the command line box, type the drive letter of the drive

containing the MessageBuilder Software disk 1, followed by a
colon and the word setup. For example, type:

a:setup.

Then select OK or press

5. You are prompted to begin the MessageBuilder installation.

Select:

ENTER.

• Yes to continue

• No to cancel.

6. The installation software checks your system for AB Utilities

software.
If it detects an older version of AB Utilities software, it warns

you that the previous version will be deleted before the new
version is installed.

If it detects the same or a newer version of AB Utilities software,
it notifies you that there is no need to upgrade it.

7. If installation of AB Utilities is required, you are prompted to

install the AB Utilities Software:

• Insert the AB Utilities disk.

• Enter target drive and directory for installing files.

Recommended drive and directory is C:\AB.

The files are copied to the target directory.

8. Re-insert MessageBuilder software disk 1 to continue installing

the MessageBuilder software.

Publication 2706-817

2–3Installing MessageBuilder Software

9. You are prompted to begin the MessageBuilder installation. The

installation software checks your system for MessageBuilder
software.

If it detects a previous

version of MessageBuilder software, it
warns you that the previous version will be deleted before the
new version is installed.

If it detects the same

version of MessageBuilder software, it gives

you the option of re-installing or deleting the files.

– Re-install writes over existing files
– Delete removes the files; you must then run the installation

again to install the new software.

10. Enter registration information: name, company name, and

product serial number. The serial number is on your registration
card.

11. Enter target drive and directory for installing files. Recommended

drive and directory is C:\AB.
The files are copied to the target directory.

12. Insert MessageBuilder disk 2 to install the remaining files.

13. You are prompted to install the INTERCHANGE software. Enter

target drive and directory for installing files.

Recommended drive and directory is C:\RSI\IC.

The files are copied to the target directory.

• If the installation detects a previous version of

INTERCHANGE, the procedure replaces existing components
with new components. The procedure will not overwrite
configuration files.

• If the installation detects the same version of

INTERCHANGE, you are allowed to reinstall the
components.

14. Insert MessageBuilder Disk 3 to install the remaining

INTERCHANGE files.

Publication 2706-817

2–4 Installing MessageBuilder Software

15. The installation prompts you to update the AUTOEXEC.BAT

file. It adds:

– C:\AB\BIN to the path.
– C:\RSI\IC\BIN to the path.
– SHARE.EXE to the file (Windows 3.1x only).
– Environment variable ABIC_CONFIG=C:\RSI\IC\BIN.
– ABICRUN.BAT (starts INTERCHANGE software).

Important: MessageBuilder Configuration software and

Note: If you do not update your AUTOEXEC.BAT file during

MessageBuilder installation, MessageBuilder software writes the
changes to the file AUTOEXEC.EXM for future reference.

16. The INTERCHANGE Device Configuration Utility opens. Use

this utility to select and configure the “DF1 on COM Port”
communication drivers that your computer (workstation) will use
to transfer MessageView applications. See Page 2–8.

INTERCHANGE Software will not run without these
lines.

17. Review the release note that appears at the end of the installation

procedure.

18. When the installation is complete, you must exit Windows and

reboot your computer.

Publication 2706-817

Installation Summary

MessageBuilder installation:

• copies MessageBuilder files to the hard disk under the target

drive and directory (C:\AB) or the location specified during
installation

• copies the AB Utilities files to disk under the target drive and

directory (C:\AB) or the location specified during installation

• copies INTERCHANGE files to disk under the target drive and

directory (C:\RSI\IC) or the location specified during installation

• adds SHARE.EXE to AUTOEXEC.BAT file (Windows 3.1x

only)

• adds C:\AB\BIN and C:\RSI\IC\BIN to path

• adds ABIC_CONFIG=C:\RSI\IC\BIN to AUTOEXEC.BAT,

which defines the location of the INTERCHANGE file
CFG_KT.INI

• adds MBWIN.INI and ISP.INI to the Windows directory

• creates a MessageBuilder group in the Program Manager

containing icons for MessageBuilder Software, the MessageView
File Transfer Utility, INTERCHANGE Device Config. Utility,
and the release notes.

2–5Installing MessageBuilder Software

Online Release Notes

Online release notes are available for the MessageBuilder
Configuration Software. These files contain the most recent
information on software and new functionality, proper configuration
and work arounds, and the organization of MessageBuilder files.

Publication 2706-817

2–6 Installing MessageBuilder Software

Refer to: For:

C:\AB\MBWIN\RELEASE.TXT MessageBuilder Configuration Software
C:\RSI\IC\READMEKT.TXT INTERCHANGE Software
C:\AB\README.TXT AB Utilities Software

The same MessageBuilder and INTERCHANGE software text files
are available through the MessageBuilder Group icon.

The RELEASE.TXT file or icon contains:

• last-minute updates to the manual

• installation notes

• a list of any known problems involving MessageBuilder software

• a list of all files installed in the default directories.

Or if you chose not to use the default directories during
installation, a list of all files installed in the directories you
selected.

The READMEKT.TXT file or icon contains:

• information on software and hardware compatibility with

INTERCHANGE software

• new and changed features in Release 1.00 and later

• a list of all files installed in C:\RSI\IC directory

• a list of problems, and of problems in previous releases that have

been fixed

• application notes.

Installing with Windows 95

The installation procedure is the same when the operating system is
Windows 95.

Note: The version of INTERCHANGE must be 6.1 or later to allow
you to perform application uploads and downloads.

Registering Your Copy of MessageBuilder software

Please take time to complete and send in the registration card you
received with MessageBuilder Configuration Software packet.
Registration entitles you to:

• automatic notification of upgrades and revisions to

MessageBuilder Configuration Software

• technical assistance.

Publication 2706-817

2–7Installing MessageBuilder Software

INTERCHANGE Device Configuration Utility

The INTERCHANGE Device Configuration Utility configures
communication drivers that the computer will use to transfer
applications. It allows you to:

• view active communication drivers

• select and configure a communication driver

• edit a communication driver

• remove a communication driver

• access advanced driver parameters.

This utility automatically updates the file CFG_KT.INI when drivers
are added, configured and removed.

If you intend to transfer applications using an RS-232, DH–485 or
Pass-Through connection you must first configure the appropriate
drivers. MessageView uses only RS-232. However other
Allen-Bradley products such as PanelView 900 might use other
communication drivers.

Access the INTERCHANGE Device Configuration Utility in one of
three ways:

• automatically as the final step in the MessageBuilder installation.

• as a separate icon in the MessageBuilder Group icon

Note: If Interchange was installed via another programming
software, such as AB PanelBuilder, the Interchange icon will be
found in that software’s group.

• through the Workstation Setup command in the MessageBuilder

File menu.

Publication 2706-817

2–8 Installing MessageBuilder Software

To select and configure an INTERCHANGE driver on your
computer:

1. Double-click the utility icon in the MessageBuilder group icon, or

choose W
Note: At the end of the MessageBuilder installation procedure,

the INTERCHANGE Device Configuration dialog opens
automatically.

Configured Devices

orkstation Setup from the MessageBuilder File menu.

NAME
DEVICE
PORT

STATUS

Refers to driver name
Refers to selected driver
Refers to unique number assigned to

INTERCHANGE driver
Shows whether driver is enabled or

disabled

DF1 on COM Port

1784-KL on DH+ ➀

1784-KT or 1784-KT2
on DH+ ➀

1784-KTC on
ControlNet ➀

1784-KTX on DH485

➀

1784-KTX on DH+ ➀

1784-PCMK on DH+

➀

PIC on COM Port ➀

➀

Not used by MessageBuilder Software.

2. Select a driver from the Available Drivers: list. The selection

depends on the type of MessageView terminal and the
communication card installed in your computer.

Select: For MessageView Terminal: To:

2706-M1D1, -M1N1, -M1F1;
2706-M1D, -M1N, -M1F.

Transfer applications between the RS-232 port of a MessageView
terminal and a computer using DF1 (RS-232) communications.

Transfer applications between a computer on the DH+ link using a
1784-KL communications card and the Remote I/O port of a
MessageView Terminal on a Remote I/O network.

Transfer applications between a computer on the DH+ link using a
1784-KT/B or -KT2 communications card and the Remote I/O port of a
MessageView Terminal on a Remote I/O network.

Transfer applications between a computer on the DH-485 network
using a 1784-KTX communications card and the DH-485 port of a
MessageView Terminal.

Transfer applications between a computer on the DH+ link using a
1784-KTX communications card and the Remote I/O port of a
MessageView Terminal on a Remote I/O network.

Transfer applications between a computer on the DH+ link using a
1784-PCMK communications card and the Remote I/O port of a
MessageView Terminal on a Remote I/O network.

Transfer applications between a computer on the DH-485 network and
the DH-485 port of a MessageView terminal using a 1747-PIC
interface converter, or between a computer and the RS-232 port of a
MessageView terminal.

Publication 2706-817

2–9Installing MessageBuilder Software

3. Select the Add Device button to add and open the configuration

dialog for the selected driver.
For example, if you select DF1 on COM Port this dialog opens:

Unique number assigned to

(This is not the computer’s COM port.)

DF1 parameters must be set to:

Baud:
Parity:
Error Detect:

Typical:
COM Port = 1 and Interrupt = 4, or

COM Port = 2 and Interrupt = 3

19200
None
CRC

INTERCHANGE driver

Default Driver Name
(can be edited)

Disables driver configuration
without removing it from
Configured Drivers list.

Note: Consult your personal computer’s user manual for COM
Port Interrupt settings.

4. Edit parameters and select OK when done.

The parameters are specific to the communications card installed
in your computer, or to the type of connection you will be using
to transfer files.

The configured driver appears under the Configured Devices: list
in the Driver Configuration dialog.

Important: Do not configure more than one driver for the same

communication port.

5. Reboot your computer to load the driver and its configuration.

Important: You must reboot your computer any time you add or

remove a driver or change configuration parameters of a
driver.

Exiting Windows and re-entering will not load the
driver.

Publication 2706-817

2–10 Installing MessageBuilder Software

To configure an existing INTERCHANGE driver:

1. Select the driver from the Configured Devices: list.

2. Select the Edit Device button to open the configuration dialog for

the selected driver.

3. Edit parameters and select OK when done.

4. Reboot your computer to load the driver and its configuration.

To remove a current driver:

1. Select a driver from the Configured Devices: list.

2. Select the Remove Device button.

3. A dialog asks for confirmation of the removal. Choose OK.

4. Reboot your computer to unload the driver.

To specify advanced parameters for drivers:

1. Select the Advanced button from the INTERCHANGE Device

Configuration dialog.

2. Modify the settings as needed. See below.

3. Select the OK button to save the settings

Or select the Cancel button to return to the Configuration menu
without changing the parameters.

Publication 2706-817

2–11Installing MessageBuilder Software

Memory Manager Options
Load drivers high when enabled (checked) loads INTERCHANGE

drivers (executables) into high memory. Drivers are not loaded until
you reboot the computer. If this option is disabled, drivers are loaded
into the base 640K memory.

MessageBuilder recommends: Either enabled or disabled.
Memory Manager Selection allows you to specify the memory

manager in use on your system. Select one of the radio buttons.
MessageBuilder recommends: EMM386.

Driver Self-Test

When enabled this option requires KT devices to run self-diagnostics
before loading driver configuration.

MessageBuilder recommends: Perform the tests.

RNA Parameters
Use upper memory for packet buffers when enabled places packet

buffer space in upper MS-DOS memory.
MessageBuilder recommends: Use upper memory.

Number of solicited buffers allocates the number of packet buffers
(1 to 200). Each buffer uses 300 bytes of memory. The default is 20.

MessageBuilder recommends: 20 buffers.
Number of unsolicited data items allocates space for unsolicited

messages (0 to 200).
MessageBuilder recommends: 0 data items, which allocates no

space.

PCMK Enabler Selection

Specifies the Enabler to use for the 1784-PCMK on the DH+ Device
Driver.

Specific Enabler uses PCMKINIT or RSIPCMK. This Enabler
requires you to enter the socket number containing the card in the
driver dialog. The INTERCHANGE socket numbers are (0 to 7). In
Windows 95, the sockets are numbered (0 to 8).

Generic Enabler uses PCENABLE. This Enabler requires that you
enter a Memory address and IRQ (Interrupt).

MessageBuilder recommends: (Ignores).

Publication 2706-817

2–12 Installing MessageBuilder Software

Troubleshooting the Installation Procedure

Possible difficulties with installation

• If you used the default installation procedure, the Path in your

AUTOEXEC.BAT file now includes the \AB\BIN and
\RSI\IC\BIN directories. In Windows 3.1x the AUTOEXEC.BAT
file also includes SHARE.EXE. If you edit this file yourself,
MessageBuilder software requires these modifications.

• If the computer has Windows for Workgroups installed, it has a

virtual device driver (VxD) called VSHARE.386. If Windows for
Workgroups uses this share driver, remove the SHARE.EXE file
from the AUTOEXEC.BAT file. The Windows for Workgroups
manual has details on using VSHARE.386.

Note: Windows 95 does not need the SHARE.EXE file. It has its
own virtual device driver installed.

Possible difficulties with INTERCHANGE drivers

The INTERCHANGE drivers may cause conflicts with other drivers
sharing common interrupts or memory areas in the system. Here are
some problems that may occur and what to do about them.

• If you are using a special Windows video driver, try using the

standard Windows VGA driver; you may also have to edit the
EMM386 line in the CONFIG.SYS file to remove specific
memory exclusions added by the special video driver.

Exit Windows and run ABICSTOP (see below). If ABICSTOP is
not successful, comment out the ABICRUN line in the
AUTOEXEC.BAT file and reboot, then run ABICSTOP again.

• If you are experiencing lockups when using a serial mouse in a

DOS application, try waiting several seconds for the mouse to
initialize. If mouse operation is still a problem, run ABICSTOP.

It may be necessary to create a dual boot environment to manage
conflicting drivers. Refer to the DOS user manual for information
on this.

• If you experience error messages during a system reboot, they

may indicate an incomplete or incorrect configuration of the
INTERCHANGE drivers. See Page 2–8 for instructions on
configuring the drivers.

Publication 2706-817

For more details on INTERCHANGE Software, refer to the
INTERCHANGE Software user manuals and the MessageBuilder
online release notes.

2–13Installing MessageBuilder Software

Possible conflicts in using communication ports

If you plan to run other software on your computer that uses the
same communication ports as MessageBuilder and INTERCHANGE
Software (such as APS software), follow these steps.

1. Exit from Windows if necessary. Make sure that

INTERCHANGE is not running.

2. Type ABICSTOP at the DOS prompt. For example, type:

C:\> ABICSTOP.

3. If ABICSTOP is not successful, comment out ABICRUN in the

AUTOEXEC.BAT file:

REM CALL ABICRUN.BAT

Reboot the computer and run ABICSTOP again.

4. Run the other software.

Publication 2706-817