2711-6.0, PanelBuilder Software User Manual

2711-6.0, PanelBuilder Software User Manual
Allen-Bradley
PanelBuilder
Software
(Cat. No 2711-ND3)
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, FontTool, PanelView 550, PanelView 600, PanelView 900, PanelView 1400, SLC, SLC 500, SLC 5/01, SLC
5/02, SLC 5/03, SLC 5/04, MicroLogix, Data Highway Plus are trademarks of Allen-Bradley Company, Inc.
PLC and PLC-5 are registered trademarks of Allen-Bradley Company, Inc.
RSLinx and INTERCHANGE are trademarks of Rockwell Software Inc.
Microsoft, Windows, and MS-DOS are registered trademarks, and Windows NT is a trademark of Microsoft Corporation.
Preface
Intended Audience . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Software Package . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Contents of Manual . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Conventions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Related Publications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Technical Support Services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Software/Firmware Upgrades . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Overview of PanelBuilder
Chapter 1
Chapter Objectives . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
What is PanelBuilder? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
What is an Application? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
What is a Project? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
PanelBuilder Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Typical Application Screens . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Screen Objects . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Installation
P–1
P–1
P–2
P–3
P–3
P–4
P–4
1–1
1–1
1–1
1–1
1–2
1–5
1–6
Chapter 2
Chapter Objectives . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
2–1
System Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
2–1
Installing PanelBuilder . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
2–2
RSLinx Lite Software . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
2–7
INTERCHANGE Device Configuration Utility . . . . . . . . . . . . . . . . . 2–10
INTERCHANGE Notes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2–16
Planning an Application
Chapter 3
Chapter Objectives . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
3–1
Design Checklist . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
3–1
Applications and Projects . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
3–2
Steps for Creating an Application . . . . . . . . . . . . . . . . . . . . . . . . .
3–3
Safety Considerations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
3–4
Screen Worksheets . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
3–4
Linking Screen Objects to Controller Data . . . . . . . . . . . . . . . . . . .
3–6
Controller Data Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3–7
Data Types . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
3–8
Data Formats . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
3–9
Review Addressing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3–12
Defining Tags . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3–13
Memory Requirements/Tips . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3–14
i
ii
Table of Contents
Communications Overview
Chapter 4
Chapter Objectives . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
PanelView Terminal Ports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
DH-485 Communications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
DH+ Communications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
DF1 Communications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
DH-485/DH+/DF1 Communication Considerations . . . . . . . . . . . . .
Remote I/O Communications . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Discrete I/O . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Block Transfers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
PanelBuilder Basics
Chapter 5
Chapter Objectives . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Windows Environment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
PanelBuilder Windows . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Menus . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Tool Bar . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Status Bar . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Format Bar . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Toolboxes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Keypad Display . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Color Palette . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Dialog Boxes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Spreadsheet Editors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
PanelBuilder Defaults . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Getting Help . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Working with
Applications and Screens
Publication 2711-6.0
4–1
4–1
4–2
4–3
4–4
4–5
4–6
4–9
4–11
5–1
5–1
5–2
5–4
5–5
5–5
5–6
5–7
5–7
5–8
5–9
5–10
5–13
5–14
Chapter 6
Chapter Objectives . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Helpful Hints . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Starting PanelBuilder . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Creating a New Application . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Opening an Existing Application . . . . . . . . . . . . . . . . . . . . . . . . . .
Renaming and Describing an Application . . . . . . . . . . . . . . . . . . . .
Opening a New Screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Opening an Existing Screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Opening Multiple Screens . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Closing Screens . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Changing Screen Attributes . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Deleting Screens . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Copying Screens within an Application . . . . . . . . . . . . . . . . . . . . .
Copying Screens to Another Application . . . . . . . . . . . . . . . . . . . .
Moving Screens to Another Application . . . . . . . . . . . . . . . . . . . . .
Saving an Application . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Closing an Application . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Exiting PanelBuilder . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
6–1
6–1
6–2
6–3
6–5
6–8
6–10
6–11
6–12
6–14
6–14
6–15
6–15
6–16
6–17
6–20
6–21
6–21
Table of Contents
Working with Objects
Chapter 7
Chapter Objectives . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Accessing Objects . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Draw Pointer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Creating Objects in Display Area . . . . . . . . . . . . . . . . . . . . . . . . . .
Aligning Objects . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Creating Objects on Function Keys . . . . . . . . . . . . . . . . . . . . . . . .
Selecting Objects . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Sizing Objects . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Moving Objects . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Grouping and Ungrouping Objects . . . . . . . . . . . . . . . . . . . . . . . .
Stacking Objects . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Zooming In and Out . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Object Inner Text . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Formatting Objects . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Setting Default Colors for Objects . . . . . . . . . . . . . . . . . . . . . . . . .
Editing Object Attributes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Configuring States of Multistate or List Objects . . . . . . . . . . . . . . . .
Entering a Description for an Object . . . . . . . . . . . . . . . . . . . . . . .
Hiding an Object . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Copying/Cutting and Pasting Objects . . . . . . . . . . . . . . . . . . . . . . .
Deleting Objects . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Reversing an Operation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Creating Push Buttons
7–1
7–2
7–3
7–4
7–5
7–7
7–8
7–9
7–9
7–10
7–11
7–11
7–12
7–13
7–13
7–14
7–15
7–18
7–19
7–20
7–22
7–22
Chapter 8
Chapter Objectives . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Helpful Hints . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Push Button Types . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Contact Types . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Push Button Text and Graphics . . . . . . . . . . . . . . . . . . . . . . . . . . .
Creating Push Buttons . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Setting Properties of a Push Button . . . . . . . . . . . . . . . . . . . . . . . .
Configuring Push Button States . . . . . . . . . . . . . . . . . . . . . . . . . .
Creating
Control List Selectors
iii
8–1
8–1
8–2
8–2
8–3
8–4
8–4
8–8
Chapter 9
Chapter Objectives . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Helpful Hints . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Standard Control Lists . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Piloted Control Lists . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Control List Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Creating a Control List Selector . . . . . . . . . . . . . . . . . . . . . . . . . . .
Setting Properties of a Control List Selector . . . . . . . . . . . . . . . . . .
Configuring States for a Control List Selector . . . . . . . . . . . . . . . . .
Creating List Keys . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
9–1
9–1
9–2
9–2
9–4
9–5
9–6
9–10
9–12
Publication 2711-6.0
iv
Table of Contents
Creating
Data Entry Controls
Chapter 10
Creating Screen Selectors
Chapter 11
Chapter Objectives . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Helpful Hints . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Numeric Entry Controls . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Keypad Enable Button . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Entry Cursor Point . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Scratchpad . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Numeric Entry Examples . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Data Entry Scaling . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Creating a Numeric Entry Object . . . . . . . . . . . . . . . . . . . . . . . .
Setting Properties of a Numeric Entry Object . . . . . . . . . . . . . . .
ASCII Entry Controls . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Keypad Enable Button . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Entry Cursor Point . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
ASCII Scratchpad – Keypad or Keypad/Touch Screen Terminals .
ASCII Scratchpad – 550 Touch Screen Terminals . . . . . . . . . . . .
ASCII Scratchpad – 900/1000/1400 Touch Screen Terminals . . . .
Scratchpad in other Languages . . . . . . . . . . . . . . . . . . . . . . . . .
Creating an ASCII Entry Object . . . . . . . . . . . . . . . . . . . . . . . . .
Setting Properties of an ASCII Entry Object . . . . . . . . . . . . . . . .
Chapter Objectives . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Helpful Hints . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Goto Screen Button . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Goto Config Screen Button . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Return Screen Button . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Screen List Selector . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Creating Screen Buttons . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Setting Properties of Screen Buttons . . . . . . . . . . . . . . . . . . . . . . .
Creating a Screen List Selector . . . . . . . . . . . . . . . . . . . . . . . . . . .
Setting Properties of a Screen List Selector . . . . . . . . . . . . . . . . . .
Configuring Entries in a Screen List Selector . . . . . . . . . . . . . . . . .
Creating List Keys . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
PLC/SLC Controlled Screen Changes . . . . . . . . . . . . . . . . . . . . . .
Creating Bar Graphs,
Indicators and
Numeric Displays
Publication 2711-6.0
10–1
10–1
10–2
10–2
10–2
10–2
10–3
10–4
10–7
10–7
10–12
10–12
10–12
10–13
10–14
10–15
10–16
10–16
10–17
11–1
11–1
11–2
11–2
11–2
11–2
11–3
11–4
11–5
11–6
11–7
11–9
11–9
Chapter 12
Chapter Objectives . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Helpful Hints . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Scaling Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Error States . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Bar Graphs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Types of Bar Graphs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Creating a Bar Graph . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Setting Properties of a Bar Graph . . . . . . . . . . . . . . . . . . . . . . .
Creating a Bar Graph Scale . . . . . . . . . . . . . . . . . . . . . . . . . . .
12–1
12–1
12–2
12–3
12–4
12–4
12–5
12–5
12–7
Table of Contents
Creating Tick-Mark Labels . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Numeric Data Displays . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Types of Numeric Data Displays . . . . . . . . . . . . . . . . . . . . . . . .
Creating a Numeric Data Display . . . . . . . . . . . . . . . . . . . . . . .
Setting Properties of a Numeric Data Display . . . . . . . . . . . . . . .
Multistate Indicators . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Types of Multistate Indicators . . . . . . . . . . . . . . . . . . . . . . . . . .
Triggering an Indicator State . . . . . . . . . . . . . . . . . . . . . . . . . . .
Creating a Multistate Indicator . . . . . . . . . . . . . . . . . . . . . . . . . .
Setting Properties of a Multistate Indicator . . . . . . . . . . . . . . . . .
Configuring States for a Multistate Indicator . . . . . . . . . . . . . . . .
List Indicators . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Types of List Indicators . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Triggering a List Entry . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Creating a List Indicator . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Setting Properties of a List indicator . . . . . . . . . . . . . . . . . . . . .
Configuring Entries of a List indicator . . . . . . . . . . . . . . . . . . . . .
Creating Message Displays
v
12–8
12–9
12–9
12–10
12–10
12–12
12–12
12–13
12–14
12–14
12–16
12–18
12–18
12–19
12–20
12–20
12–22
Chapter 13
Chapter Objectives . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13–1
Helpful Hints . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13–1
Types of Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13–2
Triggering Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13–4
Error State . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13–5
Creating a Message Display . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13–6
Setting Properties of a Message Display . . . . . . . . . . . . . . . . . . . . 13–6
Configuring Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13–8
Creating an Object to Print Messages . . . . . . . . . . . . . . . . . . . . . 13–10
Using Global Objects
Chapter 14
Chapter Objectives . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
What is a Global Object? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Defining a Global Object . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Using a Global Object . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Moving and Resizing a Global Object . . . . . . . . . . . . . . . . . . . . . .
Creating Alarms
14–1
14–1
14–4
14–5
14–6
Chapter 15
Chapter Objectives . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15–1
Overview of Alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15–1
Creating the Alarm Banner . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15–6
Creating an Alarm List . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15–9
Configuring Global Parameters for Alarms . . . . . . . . . . . . . . . . . . . 15–12
Defining Alarm Triggers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15–14
Creating Alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15–16
Defining Optional Trigger Tags . . . . . . . . . . . . . . . . . . . . . . . . . . . 15–22
Defining Remote Tags used by Controller . . . . . . . . . . . . . . . . . . . 15–26
Alarm Examples . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15–28
Publication 2711-6.0
vi
Table of Contents
Adding Graphics
Chapter 16
Chapter Objectives . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16–1
Helpful Hints . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16–1
Graphic Objects . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16–2
Graphic Tools . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16–2
Drawing a Line . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16–3
Drawing Connected Lines . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16–4
Drawing Shapes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16–5
Freeform Drawings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16–6
Adding ISA Symbols . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16–7
Adding Background Text . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16–8
Importing/Exporting Bitmap Graphics . . . . . . . . . . . . . . . . . . . . . . . 16–10
Using Background Graphics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16–16
Formatting Objects
and Text
Publication 2711-6.0
Chapter 17
Chapter Objectives . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Format Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Changing the Appearance of Objects . . . . . . . . . . . . . . . . . . . . . .
Changing Object Shape . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Changing Line Type . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Changing Fill Pattern . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Using the Blink Option . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Setting Foreground/Background Colors . . . . . . . . . . . . . . . . . . .
Reversing Foreground/Background Colors . . . . . . . . . . . . . . . . .
Working with Inner Text . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Editing Inner Text . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Inserting Time or Date . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Inserting a Numeric Variable . . . . . . . . . . . . . . . . . . . . . . . . . .
Inserting an ASCII Variable . . . . . . . . . . . . . . . . . . . . . . . . . . .
Working with Inner Graphics . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Adding Inner Graphic . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Setting Foreground/Background Colors . . . . . . . . . . . . . . . . . . .
Reversing Foreground/Background Colors . . . . . . . . . . . . . . . . .
Removing an Inner Graphic . . . . . . . . . . . . . . . . . . . . . . . . . . .
Editing Graphics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Changing the Appearance of Text . . . . . . . . . . . . . . . . . . . . . . . . .
Sizing Text . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Aligning Text . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Underlining Text . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Using the Blink Option . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Setting Foreground/Background Colors . . . . . . . . . . . . . . . . . . .
Reversing Foreground/Background Colors . . . . . . . . . . . . . . . . .
17–1
17–2
17–3
17–4
17–5
17–6
17–7
17–8
17–9
17–10
17–11
17–13
17–14
17–16
17–19
17–20
17–21
17–22
17–23
17–23
17–24
17–25
17–26
17–27
17–28
17–29
17–30
Table of Contents
Using the Text Editor
vii
Chapter 18
Chapter Objectives . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18–1
Opening the Text Editor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18–2
Entering New Text . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18–3
Editing Text . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18–4
Inserting Variables in Text . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18–5
Sorting Text . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18–6
Filtering Text . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18–6
Printing Text . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18–7
Deleting Unused Text . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18–8
Renumbering Text . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18–9
Moving Text . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18–9
Copying Text into Objects . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18–10
Working with Tags
Chapter 19
Chapter Objectives . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Using the Tag Editor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Table View . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Form View . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Opening the Tag Editor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Navigating through the Tag Editor . . . . . . . . . . . . . . . . . . . . . . .
Validating Tag Addresses . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Defining Tags . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Saving Tags . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Viewing Tags . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Inserting and Deleting Tags . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Copying Tags . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Duplicating Tags . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Finding Tags . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Sorting Tags . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Printing Tags . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Using Tools . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Tag Import/Export Utility . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Importing Tags . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Handling Data Collisions . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Exporting Tags . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Examining the Results of an Import/Export . . . . . . . . . . . . . . . . .
Interpreting Error Messages . . . . . . . . . . . . . . . . . . . . . . . . . . .
19–1
19–1
19–1
19–1
19–2
19–3
19–4
19–5
19–7
19–7
19–7
19–8
19–9
19–10
19–11
19–12
19–15
19–15
19–16
19–17
19–18
19–19
19–20
Publication 2711-6.0
viii
Table of Contents
Terminal and
Communication Setup
Chapter 20
Managing Projects
Chapter 21
Chapter Objectives . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Terminal Setup Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Defining DH-485 Communications . . . . . . . . . . . . . . . . . . . . . . . . .
Defining DH+ Communications . . . . . . . . . . . . . . . . . . . . . . . . . . .
Defining DF1 Communications . . . . . . . . . . . . . . . . . . . . . . . . . . .
Defining Remote I/O Communications . . . . . . . . . . . . . . . . . . . . . .
Defining Block Transfers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Configuring the Printer Port . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Changing the Terminal Type . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Setting Power-Up Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Setting Time/Date Format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Setting Advanced Terminal Options . . . . . . . . . . . . . . . . . . . . . . . .
Setting a Display Maintenance Schedule . . . . . . . . . . . . . . . . . . . .
Defining PLC/SLC Control Tags . . . . . . . . . . . . . . . . . . . . . . . . . .
Defining Status Tags . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
20–1
20–2
20–3
20–5
20–7
20–9
20–11
20–13
20–15
20–17
20–19
20–21
20–23
20–24
20–26
Chapter Objectives . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21–1
About Projects . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21–1
Managing Projects . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21–2
Managing Devices in Projects . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21–4
Copying a Project to Another Computer . . . . . . . . . . . . . . . . . . . . . 21–6
Restoring a Project . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21–7
Moving an Application to Another Computer . . . . . . . . . . . . . . . . . . 21–7
Replacing Duplicate Tags and Devices in a Project . . . . . . . . . . . . . 21–8
Adding Unknown Tags or Devices to a Project . . . . . . . . . . . . . . . . 21–9
Setting Preferences for Replacing or Adding Tags and Devices . . . . 21–10
Restoring a Project Created with a Restricted PanelBuilder Release . 21–11
Multilingual Support
Chapter 22
Chapter Objectives . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
What You Will Learn? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
System Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Terminology . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
What is FontTool? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Input Method Editor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Using FontTool . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Creating Font Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Viewing Sample Text . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Opening Font Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Saving Font Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Printing Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Creating an Application Using a Font File . . . . . . . . . . . . . . . . . . . .
Troubleshooting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Translating Application Text in Excel . . . . . . . . . . . . . . . . . . . . . . .
Publication 2711-6.0
22–1
22–2
22–2
22–2
22–3
22–4
22–5
22–6
22–8
22–8
22–9
22–10
22–11
22–15
22–16
Table of Contents
Validating and
Transferring Applications
Chapter 23
Creating Reports
Chapter 24
Chapter Objectives . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Helpful Hints . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Validating Applications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Correcting Validation Errors . . . . . . . . . . . . . . . . . . . . . . . . . . .
Printing Validation Messages . . . . . . . . . . . . . . . . . . . . . . . . . .
Sending Validation Messages to File . . . . . . . . . . . . . . . . . . . . .
Transfer Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
PanelView Terminal . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Memory Card . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
DOS File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Transfer Utilities . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
PanelBuilder Application Menu . . . . . . . . . . . . . . . . . . . . . . . . .
Application File Transfer Utility . . . . . . . . . . . . . . . . . . . . . . . . .
PanelView DOS File Transfer Utility . . . . . . . . . . . . . . . . . . . . . .
Internal DF1 Driver . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Downloading Directly to a Terminal . . . . . . . . . . . . . . . . . . . . . . . .
Downloading on a Local DH+ Link . . . . . . . . . . . . . . . . . . . . . . . . .
Downloading to a Terminal Using Pass-Through . . . . . . . . . . . . . . .
Remote I/O Pass-Through Setup . . . . . . . . . . . . . . . . . . . . . . .
DH-485 Pass-Through Setup . . . . . . . . . . . . . . . . . . . . . . . . . .
Downloading to a DOS Memory Card . . . . . . . . . . . . . . . . . . . . . .
Downloading to a DOS File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Uploading Directly from a Terminal . . . . . . . . . . . . . . . . . . . . . . . .
Uploading on a Local DH+ Link . . . . . . . . . . . . . . . . . . . . . . . . . . .
Uploading from a Terminal Using Pass-Through . . . . . . . . . . . . . . .
Using the Application File Transfer Utility . . . . . . . . . . . . . . . . . . . .
Verifying an Application . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Downloading to a PanelView Terminal . . . . . . . . . . . . . . . . . . . .
Uploading from a PanelView Terminal . . . . . . . . . . . . . . . . . . . .
Decreasing Size of Application for Downloads . . . . . . . . . . . . . . . .
Exceeding RAM Memory in Terminal . . . . . . . . . . . . . . . . . . . . . . .
Chapter Objectives . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Types of Reports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Connecting a Printer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Creating and Printing a Report . . . . . . . . . . . . . . . . . . . . . . . . . . .
Changing the Report Setup . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Setting up a Printer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Sending the Report to a File . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
ix
23–1
23–1
23–2
23–3
23–4
23–5
23–6
23–6
23–7
23–7
23–8
23–8
23–8
23–8
23–9
23–10
23–12
23–13
23–14
23–15
23–16
23–18
23–19
23–21
23–22
23–23
23–24
23–25
23–27
23–28
23–28
24–1
24–1
24–1
24–2
24–3
24–5
24–6
Publication 2711-6.0
x
Table of Contents
Appendix A – Command Summary
Appendix B – Tool Summary
Appendix C – PanelBuilder Worksheets
Appendix D – Software Error and Warning Messages
Appendix E – Validation Messages
Appendix F – Troubleshooting
Appendix G – Internal Read Only Tags
Appendix H – Using Extended ASCII Characters
Glossary
Index
Publication 2711-6.0
Preface
Preface
This manual is a reference guide for the PanelBuilder
Configuration Software. It describes features and procedures used to
create control panel applications for the family of PanelView
Operator Terminals.
Because this is a reference manual it covers all the features of the
software. You may not use or need to use all the features, so use the
manual as needed.
If you’re just getting started, you might want to read the Getting
Started Manual first. It takes you through all the steps of creating a
sample application including how to download and run the
application in the terminal.
Intended Audience
This manual is for the individual responsible for designing control
panel applications that will run in a PanelView terminal.
The PanelBuilder Configuration Software runs in Microsoft
Windows . You should know how to use a mouse, choose
commands, and work with windows and dialog boxes.
You should also have a basic understanding of:
• PLC and SLC logic controllers, especially the controller’s
program and data files.
• communication network on which application will run.
Software Package
The PanelBuilder Configuration Software package includes:
• 3 1/2 inch installation disks to install
– PanelBuilder Software
– INTERCHANGE or RSLinx Lite Software
– AB Utilities Software
•
•
•
•
PanelBuilder Configuration Software user manual
PanelView Operator Terminal user manual
Getting Started manual
PanelView File Transfer Utility manual
Publication 2711-6.0
P–2
Preface
Contents of Manual
Chapter
This manual is organized as follows:
Title
Preface
1
Overview of PanelBuilder
Description
Describes the purpose and contents of the manual, the intended audience and
conventions used.
Describes PanelBuilder and product features.
2
Installation
3
Planning an Application
4
Communications Overview
5
PanelBuilder Basics
6
Working with
Application Files and Screens
Shows how to open, close and save application files and screens. Also tells how to
exit PanelBuilder.
7
Working with Objects
Describes how to access, create and edit objects. Also describes basic operations
such as how to select, size, move, group and zoom objects.
8
Creating Push Buttons
Shows how to create and configure momentary, maintained, latched and multistate
push button controls.
9
Creating Control
List Selectors
Creating
Data Entry Controls
10
Tells how to install PanelBuilder on a personal computer.
Gives guidelines for planning an application. Also describes worksheets for
application planning.
Gives an overview of DH-485, DH+, and Remote I/O communications.
Covers some basics on using PanelBuilder.
Shows how to create and configure standard and piloted control lists.
Shows how to create objects that open a scratchpad for numeric or ASCII data
entry.
11
Creating Screen Selectors
Shows how to create screen selectors for navigating between screens in an
application. Screen selectors include goto/goto config screen/return screen buttons
and a screen list.
12
Creating Bar Graphs,
Indicators and Numeric Displays
Shows how to create and configure multistate indicators, list indicators, bar graphs
and numeric data displays.
13
Creating Message Displays
14
Using Global Objects
15
Creating Alarms
Describes alarm components (Alarm Banner display, Alarm buttons, Alarm List,
global alarm parameters, alarm and trigger definitions) and how to use those
components to trigger alarm conditions.
16
Adding Graphics
Shows how to add lines, shapes, ISA symbols and background text to screens.
Also shows how to import bitmap graphics from other programs such as
Paintbrush.
17
Formatting Objects and Text
18
Using the Text Editor
19
Working with Tags
20
Terminal and Communication
Setup
21
Managing Projects
Tells how to link a project to an application and how to copy, rename, delete
projects or devices in projects.
22
Multi-Lingual Support
Shows how to use the FontTool utility to create and use font files (in specific
languages) for PanelBuilder applications.
23
Validating and
Transferring Applications
24
Creating Reports
Publication 2711-6.0
Shows how to create message displays and print only message devices which
present status information or instructions to the operator.
Tells how to flag an object for global use and access global objects.
Shows how to use formatting options to change the visual appearance of objects
and text, including how to add inner text/graphics to objects.
Describes how to use the application Text Editor to create, edit, sort, filter and print
application text, as well as how to reuse text.
Shows how to use the tag editor to enter/edit
tag information, print tags, and import/export tags.
Tells how to set operating and runtime communication parameters for the
PanelView terminal and how to convert applications from one terminal type to
another.
Describes how to validate and transfer a PanelBuilder application between a
personal computer and a PanelView terminal, PCMCIA memory card or disk file.
Tells how to create and print application reports.
Preface
Conventions
Related Publications
P–3
The following conventions are used throughout this manual:
• PanelBuilder refers to the PanelBuilder Configuration Software.
• PanelView or terminal refers to any one of the PanelView
terminals unless specifically stated.
• Windows refers to Windows 95, Windows NT, or Windows 3.1 or
higher.
• Keys on the keyboard appear in small capital letters. For
example, the Ctrl key appears as CTRL in the text, the Alt key as
ALT, and so on.
• When keys are to be pressed in combination, you’ll see them
connected by a +. For example, ALT+F4 means hold down the ALT
key while you press F4.
• Procedures begin with bold text followed by a semicolon.
To open an application file:
• A solid right cursor in the left margin indicates a tip or hint.
Anchor point is the handle opposite the handle you choose. The
anchor point doesn’t move when sizing objects.
The following table lists publications related to the PanelBuilder
Configuration Software and the PanelView Operator Terminals.
Publication Title
Publication No.
PanelView Terminal User Manual
2711-6.1
PanelBuilder Getting Started Manual
2711-6.2
DeviceNet Communications for PanelView Terminals
2711-6.0.4
ControlNet Communications for PanelView Terminals
2711-6.10
PanelView File Transfer Utility
2711-805
For information relating to your logic controller, INTERCHANGE
or RSLinx Lite Software, or Microsoft Windows, refer to the
appropriate documentation.
Publication 2711-6.0
P–4
Preface
Technical Support Services
If you have any questions about PanelBuilder, please consult the
manuals or the online help first. If you can’t find the answer, contact
Rockwell Automation International Support:
Rockwell International
Technical Support
6680 Beta Drive
Mayfield Village, Ohio 44143
Or call 1–440–646–7800 or fax 1–440–646–7801 for technical
support between 8 AM and 5 PM (EST), Monday to Friday.
Please have the serial number of your software ready when you call.
You can find this number in three places:
• on the registration card you received with the software
• on the screen that appears when you start the PanelBuilder
• in the main Help menu, when you choose About
Documents answering frequently asked questions are available from
the Allen-Bradley:
• AutoFax service at 1–440-646-5436
This service provides an index of available documents and will
automatically fax a document 24 hours a day, 7 days a week.
• website www.ab.com on the Technical Support/FAQ menu
Software/Firmware
Upgrades
As new features and enhancements become available, you may want
to upgrade your PanelBuilder software and PanelView firmware.
To automatically receive free software upgrades, complete and send
in your software registration card to Rockwell Software. You can
also receive software upgrades by contacting:
• local Allen-Bradley sales office
• Rockwell Software at 1–440-646-7700 or fax 1–440–646–7701
• access the website www.software.rockwell.com. Under Support,
select Software Updates and search for PanelBuilder or
2711ND3.
To receive firmware upgrades:
• contact Rockwell Software at 1–440-646-7700
• access the Allen-Bradley website www.ab.com and download the
upgrade by selecting Rockwell Automation Technical Support
and then file download.
Publication 2711-6.0
Overview of PanelBuilder
Chapter Objectives
This chapter contains the following sections:
Section
Page
What is PanelBuilder?
1–1
What is an Application?
1–1
What is a Project?
1–1
PanelBuilder Features
1–2
Typical Application Screens
1–5
Screen Objects
1–6
What is PanelBuilder?
PanelBuilder is a Microsoft Windows based package that lets you
design control panel applications for PanelView terminals. To
simplify application design, the software uses menus, dialog boxes
and tools which are standard in Windows.
What is an Application?
A PanelBuilder application is a logical arrangement of screens
containing objects such as push buttons, indicators, control lists, bar
graphs and alarms. When the application is downloaded to a
terminal, the operator interacts with these objects by pressing
function keys or touching the terminal screen.
Applications are transferred between your computer and a
PanelView terminal using a serial connection, memory card or
Pass-Through.
PanelBuilder applications communicate with logic controllers on a
variety of networks including: DH-485, DH+, DF1, Remote I/O,
DeviceNet and ControlNet.
The ports on the PanelView terminal determine the communication
protocol used.
What is a Project?
Each PanelBuilder application (.PBA file) is associated with a
project. The project identifies:
• controller addresses, called tags, that PanelBuilder objects write
to or read from. (Tags defined in the Tag Editor.)
• runtime communication parameters for the PanelView terminal
and controller (Devices defined in Terminal Setup.)
Different applications can use the same project tags if the
applications use the same communication protocol.
Publication 2711-6.0
1–2
Overview of PanelBuilder
PanelBuilder Features
This section gives an overview of PanelBuilder features.
Tool or Menu Operation
PanelBuilder runs under Microsoft Windows. Tools, keystrokes or
menu commands are used to perform most functions. Use any or all,
whichever you find most convenient.
Spreadsheet Editors
Spreadsheets are used to simplify many editing operations, for
example to:
• edit states of multistate or list objects
• edit application text
• edit alarms and alarm triggers
Many formatting options for text and objects can be configured
directly from cells in the spreadsheet.
Selectable Preferences
✓ Tool Bar
✓ Status Bar
✓ Toolbox
✓ ISA Symbols
✓ Color Palette
✓ Keypad
Set features of the workspace window to those you prefer or like to
use often. Options like the tool bar and toolboxes can be toggled on
or off depending on their usage. PanelBuilder uses the last settings
when a new application is created or when you start a new session.
Help and Status Bar Information
Status bar and help options provide immediate online assistance.
Predefined Objects and Drawings
ST 0
To simplify application development, PanelBuilder provides a set of
predefined objects (such as push buttons, bar graphs, ISA symbols).
Additional graphics are available to create your own drawings or to
enhance screens. You can also import bitmap graphics (monochrome
or color) created with other programs. A variety of format options
are available to change the appearance of objects and text.
Global Objects
A global object references an object that appears multiple times in an
application. Any non-graphic object can be designated as a global
object. You can access a global object from any screen. When
modifying a global object, PanelBuilder automatically updates all
links to it. The PanelView terminal stores one copy of a global
object regardless of the number of links to it.
Publication 2711-6.0
Overview of PanelBuilder
1–3
Tag Editor
The Tag Editor is used to enter, update, print, import/export
application tags. Each tag has attributes defining how an object
interacts with a controller address. Enter all tags at once using the
table view or one tag at a time using the tag form dialog.
Color Palette
A fixed color palette is available for creating color or grayscale
applications. For color terminals, the palette supports 16 standard
EGA colors. For grayscale terminals, the palette supports 4 colors.
Use the palette to apply colors to the foreground and background of
objects, text and graphics. Color and grayscale applications support
both monochrome and color bitmaps.
Foreground and background colors are accessed from the Format
menu, the color palette, or the State tab of multistate/list objects.
Alarms
The Alarm System includes:
• Alarm Banner display that pops up over the current screen to
notify the operator when an alarm occurs.
• Alarm Buttons to allow the operator to act on an alarm.
• Alarm List displays information on the last 100 alarms including
whether they have been acknowledged.
• Alarm List buttons to print or clear alarms in an alarm list.
• Alarm Setup dialog that provides a set of tabs to configure
alarms, triggers and global alarm parameters.
Reports
Create customized reports for an application including:
• application description
• object attributes
• application text
• terminal settings
• tags
• alarm definitions
• screen images and alarm banner display
Print reports to a file or a graphic printer supported by Microsoft
Windows.
Publication 2711-6.0
1–4
Overview of PanelBuilder
PLC Controller
PanelView Terminal
Terminal and Communication Setup
Operating and runtime communication parameters for the PanelView
terminal and logic controller are accessed from the Terminal Setup
dialog, including:
• RS-232 printer port setup
• power-up defaults
• time/date display format
• font file selection (for a specific language)
• PLC/SLC controlled options (screen and time/date changes)
• auto repeat settings for terminal keys/touch cells, display settings,
language setting for terminal messages, and handshake timeout
Application Validation
Use the validation feature to check an application for correct
operation. An application is validated automatically when it is
downloaded to a terminal. You can also validate an application at
any time using a menu command. Warnings or errors detected
during validation can be viewed or printed to a printer or file.
Application Upload / Download Capabilities
Transfer applications between the computer running PanelBuilder
and a PanelView terminal using a:
• serial connection
• Pass-Through from a computer on the DH+ network
• memory card
• DOS file
Computers with a DataBook TMB-240 or TMB-250 card drive can
transfer applications to/from Allen-Bradley’s flash memory cards
(Catalog No. 2711-NM11, -NM12, -NM13, -NM14).
Computers with a PCMCIA/ATA card drive can transfer applications
to/from Allen-Bradley’s ATA memory cards (Catalog No.
2711-NM22, -NM24, -NM26). Laptops are compatible with the
ATA memory cards, supporting Windows 95 Plug and Play devices.
Publication 2711-6.0
Overview of PanelBuilder
Typical Application Screens
1–5
Application screens can contain a variety of control, display or
graphic objects. The following screens show examples of:
• Control list selector
• Numeric entry cursor points
• Bar graphs
• Goto screen button
Numeric Entry
Cursor Points
Goto
Screen Button
Bar Graphs
Control List Selector
On touch screen terminals, the operator activates input functions by
touching a screen object. For example, to view the main menu
screen, the operator touches the MENU button.
Numeric Entry
Cursor Points
F6
F7
F6
Bar Graphs
Goto
Screen Button
F8
Control List Selector
On keypad terminals, the operator activates input functions by
pressing the function key assigned to the object. For example, to
view the main menu screen, the operator presses the F8 or MENU
function key. To activate the cursor point objects, the operator
presses the function keys labeled F6 or F7 (SP or CV).
Publication 2711-6.0
1–6
Overview of PanelBuilder
Screen Objects
The table below lists objects you can place on a screen. An object is
either dynamic or static.
• Dynamic objects interact with a controller address.
• Static objects do not interact with a controller address.
Screen Objects
Description
Type
Changes state when pressed and returns to original state when released.
Changes state when pressed and remains in this state when released.
Press and release again to return push button to its original state.
Changes state when pressed and remains in state until unlatched by
controller.
Supports 2 - 16 states. Changes state each time button is pressed. After
the last state, the button returns to its initial state and repeats cycle.
Allows operator to select a control option from a scrolling list of up to 255
options. The terminal’s up and down arrow keys are used to move
through the list. The selected option is sent to the controller immediately
ey iss pressed.
ressed. Pressing
Press n Enter iss an option
o t on selected
se e ted
or when the Enter key
during application configuration.
Restricts control list access to the controller, operator or both. A piloted
control list allows the controller to select a state from the list.
Dynamic
Dynamic
Displays current value at controller address in a data box. When
selected, the scratchpad opens allowing you to change the value using
the keypad.
When pressed, opens the scratchpad and activates the terminal keypad
or touch screen keypad for numeric data entry.
Displays current string at controller address in a data box. When
selected, the scratchpad opens allowing you to change the character
string using the keypad.
When pressed, opens the scratchpad and activates the terminal keypad
or touch screen keypad for ASCII data entry.
Displays one of up to 2,000 unique states. The value at a controller
address determines which state to display.
Highlights a state in a scrolling list supporting up to 255 states. The value
at a controller address determines which state to highlight.
Monitors changing conditions such as temperature, pressure or fluid
levels. Create bar graphs with or without scales.
Shows current value at a controller address (binary, BCD, integer, float).
Use scaling (y=mx+b) to display value in appropriate units.
Presents status information or instructions to operator. The controller
triggers messages from a predefined list of up to 2,000 messages.
Similar to a message display but messages print out on the connected
printer when triggered rather than display on the terminal screen.
Dynamic
Time
Date
ASCII Variable
Inserts a time variable within a text string.
Inserts a date variable within a text string.
Inserts an ASCII variable within a text string.
Static
Static
Dynamic
Numeric Variable
Inserts a numeric variable within a text string.
Dynamic
Goto Screen Button
Goto Config Screen Button
Return Screen Button
Moves to a specific application screen.
Displays the PanelView terminal’s Configuration Mode menu.
Returns to previous screen.
Displays a screen selected from a list of screens. The terminal’s up and
down arrow keys are used to move through the list.
Static
Static
Static
Static
Momentary Push Button
Maintained Push Button
Push Button Controls
Latched Push Button
Multistate Push Button
Standard Control List➀
ist Selectors
electors
Control List
Piloted Control List➀
Cursor Point
Numeric Data Entry
Keypad Enable Button
Cursor Point
ASCII Data Entry
Keypad Enable Button
Multistate Indicator
List Indicator
Indicators and
Data Displays
Bar Graph
Numeric Data Display
Message Display
Print Only Message Object
Varia les
Variables
Screen
creen Selectors
electors
Screen List Selector➀
Publication 2711-6.0
Dynamic
Dynamic
Dynamic
Dynamic
Dynamic
Dynamic
Dynamic
Dynamic
Dynamic
Dynamic
Dynamic
Dynamic
Dynamic
Overview of PanelBuilder
Screen Objects
List
ist Keys➀
e s
Move Up
Move Down
Home
End
Page Up
Page Down
Backspace
Enter
Acknowledge Button
Clear Button
Alarms
Print Button
Acknowledge All Button
Alarm List ➀
Print Alarm List Button
Clear Alarm List Button
Graphics
raphics
Line/Connected Line
Rectangle
Circle/Ellipse
Freeform
Scale
Background Text
ISA Symbols
Imported Graphics
Description
1–7
Type
Moves cursor up one item in a control list or screen list selector.
Moves cursor down one item in a control list or screen list selector.
Moves cursor to the first item in a control list or screen list selector.
Moves cursor to the last item in a control list or screen list selector.
Moves cursor up one page in a scrolling control list or screen list.
Moves cursor down one page in a scrolling control list or screen list.
Returns cursor to currently highlighted selection in a control or screen list.
Displays screen selected from a screen list selector or confirms a control
list selection and sends that selection to the controller.
Acknowledges the alarm displayed in the Alarm Banner and removes the
Alarm Banner from the terminal display.
Clears the Alarm Banner from the terminal display without acknowledging
the alarm.
Prints the current message displayed in the Alarm Banner.
Acknowledges all alarms (current and pending) and removes the Alarm
Banner from the terminal display.
Displays a list of triggered alarms. The operator can acknowledge alarms
in the list, clear the list or print the list
Prints all alarms in the Alarm List.
Clears the Alarm List. Also clears the Alarm Banner even though the
alarm condition may still exist.
Creates a line or connected lines.
Creates a rectangle or square.
Creates a circle or ellipse.
Creates a freehand drawing.
Creates scale with tick marks for bar graph or other purpose.
Creates screen titles or background text not linked to object.
Select one of 32 predefined drawings such as a valve to place in an
object or on the screen.
Imports/exports bitmaps created with other programs.
Static
Static
Static
Static
Static
Static
Static
Static
Dynamic
Static
Static
Dynamic
Dynamic
Static
Static
Static
Static
Static
Static
Static
Static
Static
Static
➀ PanelView 900, 1000 and 1400 Touch Screen terminals require list keys to move the cursor through a control list, screen list selector, or alarm
list. The list keys are also supported on the keypad versions of these terminals.
Publication 2711-6.0
Installation
Chapter Objectives
This chapter contains the following sections:
Section
System Requirements
Page
System Requirements
2–1
Installing PanelBuilder Software
2–2
RSLinx Lite Software
2–7
INTERCHANGE Device Configuration Utility
2–10
INTERCHANGE Notes
2–16
The minimum hardware and software requirements for installing and
running PanelBuilder are:
• personal computer using a 386 or higher processor
• MS-DOS operating system version 5.0 or later
• Windows 3.1 or later (Windows for Workgroups version 3.11 or
later), Windows 95, or Windows NT 4.0.
The RAM requirements for each operating system are as follows:
Software
3.X
95
NT 4.0
NT 4.0/486
PanelBuilder
8 MB
16MB
32 MB
32 MB
External Font Support
8 MB
8 MB
16 MB
32 MB
RSLinx Lite ➀
N/A
16 MB
16 MB
32 MB
➀ RSLinx Lite only runs in Windows 95 or Windows NT 4.0.
Note: To determine the RAM required to run PanelBuilder with
other components use the maximum specified. For example, to
run PanelBuilder and RSLinx in NT 4.0, 32 MB is required.
•
•
•
•
•
500K free conventional memory
at least 40 MB available hard disk space
VGA or other high-resolution display supported by Windows
Mouse or other Windows pointing device
One of the following for downloading or uploading applications:
– Personal Computer Interface Converter (Catalog No.
1747-PIC) and cable (Catalog No. 1747-C10,-C11,-C20) for
transferring applications between a computer and a DH-485
PanelView terminal.
– Cable (Catalog No. 2711-NC13, -NC14, 2706-NC13) for
transferring applications directly between a computer and the
RS-232/DF1 port of a PanelView terminal.
– ATA card drive or DataBook TMB240/TMB250 (Windows
3.x or 95 only) card drive for transferring applications to/from
a memory card.
– Appropriate communications card and cables if transferring
applications using Pass-Through over a DH+ network.
Publication 2711-6.0
2–2
Installation
Optional Equipment
• Graphic printer that’s supported by Windows
• Power Supply (Catalog No. 1747-NP1) for desktop transfers
between a personal computer and a DH-485 PanelView terminal.
Provides power to Personal Computer Interface Converter when
terminal isn’t connected to controller.
Installing PanelBuilder
The PanelBuilder installation installs:
• PanelBuilder Software
• AB Utilities Software
• INTERCHANGE or RSLinx Lite Software
INTERCHANGE or RSLinx Lite Software
To download applications to a PanelView terminal, the appropriate
communication driver must be configured on your system. You can
configure a driver using:
• RSLinx Lite Software (Windows 95 or Windows NT 4.0) or
• INTERCHANGE Software (Windows 95 or Windows 3.x)
INTERCHANGE is a common set of real mode DOS TSR
communication drivers that can be shared by different Windows
programs. INTERCHANGE may already be installed on your
computer. The APS and 6200 Programming Software use
INTERCHANGE in DOS or Windows.
To check the version of INTERCHANGE running on your computer,
type DTLVER at the DOS prompt.
RSLinx Lite provides a set of communication drivers that can be
shared by Windows programs. To check the version of RSLinx on
your computer, select About RSLinx from the Help menu.
Installation Notes
• Before installing PanelBuilder on a computer running Windows
95, check the C:\Windows\System folder for these files:
– VDF1.386
– V485.386
If these files exist, delete them.
• Check that your computer has sufficient system resources and
memory available.
• Close all Windows applications before installing PanelBuilder.
Press ALT+TAB to check for open applications.
Publication 2711-6.0
Installation
2–3
Installation Setup
The setup options available when installing the PanelBuilder are:
• Typical Setup – installs all components listed under the custom
setup except External Font File Support and either
INTERCHANGE or RSLinx communication software.
Note that on Windows 95/NT systems, RSLinx is the default
communication software installed.
• Compact Setup – installs all communication protocols, all
terminal types, and the PanelBuilder Software.
• Custom Setup – installs only specific components that you select
and the PanelBuilder Software. Enable/disable options by
selecting/deselecting check boxes. The custom setup lists the disk
space used by each component with available disk space.
Custom Components
Description
PanelBuilder Main
Installs all the files necessary to run PanelBuilder. The
target folder for installing files is C:\AB.
Terminal Types
Load all or specific terminal types. You must select at
least one terminal type.
To select all terminal types, click the Terminal Types
check box.
To access the list of terminals, click the Terminal Types
check box and then the Change button.
Communication Protocols
Loads all or specific communication protocols. You
must select at least one protocol.
To select all communication protocols, click the
Communication Protocols check box.
To access the list of protocols, click the Communication
Protocols check box and then the Change button.
External Font File Support
Loads the FontTool utility which is used to create font
files for PanelBuilder applications. Font files are created
in \AB\PBWIN\FONT.
Getting Started
Installs sample applications referenced in the Getting
Started manual. Files are copied to \AB\PBWIN\GS.
Bitmap Library
Installs .BMP files used by the Import/Export Graphics
function in \AB\PBWIN\PBLIB.
Demo Files
Installs demo application files for the PanelView
terminals. Demo files are copied to
\AB\PBWIN\DEMOS.
INTERCHANGE
RSLinx
Loads INTERCHANGE software which allows you to
configure communication drivers for transferring
applications. Files are copied to C:\RSI.
INTERCHANGE is the default selection in Windows 3.x.
You can load INTERCHANGE or RSLinx, not both.
Loads RSLinx software which allows you to configure
communication drivers for transferring applications.
Files are copied to Program Files\Rockwell Software.
RSLinx is the default selection in Windows 95/NT.
You can load RSLinx or INTERCHANGE, not both (in
Windows 95).
Publication 2711-6.0
2–4
Installation
Installation Procedure
If the installation procedure detects the same version of
PanelBuilder, AB Utilities, INTERCHANGE or RSLinx Lite
software, you are given the option of reinstalling these components.
If the installation detects a newer version of software than what you
are installing, you are given the option of downgrading.
If you try to install RSLinx in Windows 95, and INTERCHANGE is
installed, you are warned of the conflict. The same is true if you try
to install INTERCHANGE and RSLinx is already installed.
To install PanelBuilder in Windows 95 or Windows NT:
1. Insert PanelBuilder disk 1 in Drive A: or Drive B:.
2. Click the Start button, click Settings and then click the Control
Panel.
3. Double-click the Add/Remove Programs icon.
4. On the Install/Uninstall tab, click the Install button.
5. Follow the install instructions on the screen.
To install PanelBuilder in Windows 3.x:
1. Insert PanelBuilder disk 1 in Drive A: or Drive B:.
2. In Program Manager, choose Run from the File menu (ALT+F, R).
3. Type the location you’re installing from plus the word setup.
For example, type a:setup
4. Click OK and follow the install instructions on the screen.
PanelBuilder setup with INTERCHANGE
To successfully transfer applications using INTERCHANGE drivers,
you must install PanelBuilder with INTERCHANGE. You cannot
install PanelBuilder and INTERCHANGE as separate components.
1. Enter and verify registration information. The serial number is on
your registration card.
2. Select setup option. Typical or Custom will install PanelBuilder
with INTERCHANGE.
3. Select destination folder for files.
• Default for PanelBuilder and AB Utility files is C:\AB.
• Default for INTERCHANGE files is C:\RSI.
Publication 2711-6.0
Installation
2–5
4. Installation files are copied to the appropriate folders.
5. Specify whether you want to update your AUTOEXEC.BAT file.
The CALL ABICRUN.BAT statement must be correctly placed.
The file may contain multiple configurations which require
updating. Below is a sample AUTOEXEC.BAT file.
SET ABIC_CONFIG=C:\RSI\IC\BIN
.
.
PATH= C:\DOS;C:\WINDOWS
SET PATH= C:\AB\BIN;%PATH%;C:\RSI\IC\BIN
.
.
SHARE.EXE (Windows 3.x only)
.
.
➀ CALL ABICRUN.BAT
WIN
➀ CALL statement ensures that the remaining lines of AUTOEXEC.BAT execute (used only with
DOS version 5.0 or later). The CALL statement (CALL ABICRUN.BAT) must be the last driver
(TSR) loaded before running Windows (WIN).
6. In Windows 95, select the PanelBuilder folder for storing
program icons.
In Windows 3.x, program icons are stored in the PanelBuilder
group under Program Manager.
7. The INTERCHANGE Device Configuration utility opens.
Optionally, select and configure the communication driver that
your computer will use to transfer PanelView applications.
8. Review the release note that appears at the end of the installation.
9. When the installation is complete, you must exit Windows and
reboot your computer.
When the setup utility finishes:
• In Windows 95, PanelBuilder programs and INTERCHANGE
appear on the Start menu under ProgramsPanelBuilder.
• In Windows 3.x, PanelBuilder programs and INTERCHANGE
appear as icons in the PanelBuilder group.
Publication 2711-6.0
2–6
Installation
PanelBuilder Setup with RSLinx
1. PanelBuilder setup utility
• Enter and verify registration information. The serial number
is on your registration card.
• Select setup option. Typical or Custom will install
PanelBuilder with RSLinx.
• Select destination folder for installing PanelBuilder files and
the AB Utilities software. The default is C:\AB.
• PanelBuilder files are copied to the appropriate folders.
• Select the PanelBuilder folder (\Windows\Start
Menu\Programs) for storing program icons.
When the setup utility finishes, PanelBuilder programs will
appear on the Start menu under ProgramsPanelBuilder.
2. RSLinx setup utility
• Select destination folder for RSLinx files. The default is
C:\Program Files\Rockwell Software\RSLinx\.
• Select the Rockwell Software folder (\Windows\Start
Menu\Programs\) for storing program icons.
• RSLinx files are copied to appropriate folders.
When the setup utility finishes, RSLinx programs will appear on
the Start menu under ProgramsRockwell Software.
PanelBuilder Programs
In Windows 95, PanelBuilder programs are accessed using the Start
button. In Windows 3.1 program icons are accessed from the
PanelBuilder group icon.
PanelBuilder includes the following components:
• Application File Transfer Utility – transfers converted
applications (.PVA files) between a computer and PanelView
terminal within Windows, but outside of PanelBuilder.
• Font Tool (optional) – creates font files for specific languages
which can be accessed within PanelBuilder.
• PanelBuilder – creates applications for PanelView terminals.
• PanelBuilder Release Notes – displays the most updated
information, including problems and workarounds for the
PanelBuilder software.
• PBUninstall – uninstalls PanelBuilder from your system.
If INTERCHANGE was installed, the INTERCHANGE Device
Config. Utility and release notes will also appear.
Publication 2711-6.0
Installation
RSLinx Lite Software
2–7
In Windows 95 or Windows NT, use the RSLinx Lite software to
configure communication drivers that your computer requires to
transfer PanelBuilder applications.
To transfer applications using a serial connection (Internal DF1
driver), memory card or DOS file (using the PanelView File Transfer
Utility for DH-485 terminals), RSLinx is not required.
To access RSLinx Lite:
• In Windows 95 or Windows NT, click the Start button, click
Programs, click Rockwell Software, click the RSLinx submenu
and select RSLinx.
• Or choose the Workstation Setup command from the File menu of
the PanelBuilder software.
→
Configuring RSLinx Communication Drivers
PanelBuilder’s File Menu
The following procedures show how to configure a DF1 or 1747-PIC
driver for transferring PanelBuilder applications. For details on how
to configure other RSLinx drivers, refer to RSLinx documentation.
To configure a DF1 or 1747-PIC (DH-485) driver:
1. From the Communications menu, click Configure Drivers.
For Direct Transfers Select:
For These Terminals:
To Transfer Applications:
RS–232 DF1 Devices➀
DF1, Remote I/O, DH+,
DeviceNet, ControlNet
between the RS-232/DF1 port of a Remote I/O PanelView terminal and a computer
using DF1 (RS232) communications.
RS-232 (DH-485)
DH-485
between a computer and the RS-232 port of an RS-232 PanelView terminal.
between a computer on the DH-485 network and the DH-485 port of a DH-485
PanelView terminal using a 1747-PIC interface converter.
1747-PIC Device
➀ Driver is not required. PanelBuilder has an Internal DF1.
Publication 2711-6.0
2–8
Installation
2. From the Available Drivers List, click the desired driver by
double-clicking it or by clicking it and then clicking Add New.
The configuration dialog for the selected driver opens.
DF1 Driver
Default name
given to driver
Serial COM port on computer
Device Type of
DF1 driver on computer
DF1 parameters for a PanelView
terminal must be set to:
Baud: 19200
Parity: None
Error Detect: CRC
Stop Bits: 1
Protocol: Full Duplex
Automatically detects the settings of the
DF1 driver on the serial COM port (when
connected to a PanelView terminal).
1747-PIC Driver
Default name
assigned to driver
Serial COM port on computer
Station address
of computer is
typically 0.
3. Edit the driver parameters and click OK.
The driver appears in the Configured Drivers list. Click Close to
exit the Configure Devices dialog.
Publication 2711-6.0
Installation
2–9
To assign a communication driver to a port:
After configuring a driver, you must map the driver to one of driver
ports.
1. From the Communications menu, choose Configure Client
Applications.
Maps the configured
DF1 driver to 1KT:0.
2. On the Port Mapping tab, assign the communication driver to one
of the logical ports (1KT:0, 2KT:0, ... , 8KT:0).
You can assign the driver to any one of the port mappings and it
will still operate on COM1 (port configured in Device dialog).
If you map the same driver to more than one logical port (1KT:0,
... , 8KT:0) these ports are viewable in the PanelBuilder
Download/Upload dialog when clicking the Setup button.
Important:
If you do not configure the Client Application,
RSLinx drivers will not be accessible from the
Download/Upload dialogs in PanelBuilder.
Publication 2711-6.0
2–10
Installation
INTERCHANGE Device
Configuration Utility
In Windows 95 or Windows 3.x, use the INTERCHANGE Device
Configuration Utility to configure communication drivers that your
computer requires to transfer applications using Pass-Through. This
utility lets you:
• View active communication drivers
• Select and configure a communication driver
• Edit a communication driver
• Remove a communication driver
• Access advanced driver parameters
The utility automatically updates the CFG_KT.INI, ABICRUN.BAT,
ABICSTOP.BAT, and the SYSTEM.INI files when drivers are
added, configured and removed.
To transfer applications using a Pass-Through connection, you must
first configure the appropriate driver.
To transfer applications using a serial connection (Internal DF1
driver), memory card or DOS file (using the PanelView File Transfer
Utility for DH-485 terminals), INTERCHANGE software is not
required.
To access the INTERCHANGE Device Configuration Utility:
• In Windows 95, click the Start button, click Programs, click
PanelBuilder, then click INTERCHANGE Device Config. Utility.
In Windows 3.x, double-click the INTERCHANGE Device
Config. Utility icon in the PanelBuilder Group.
• Or choose the Workstation Setup command from the File menu of
the PanelBuilder software.
• The utility also opens at the end of the PanelBuilder installation.
→
The INTERCHANGE Device Configuration dialog shown on the
next page opens.
PanelBuilder’s File Menu
Publication 2711-6.0
Installation
2–11
Configuring an INTERCHANGE Driver
To select and configure an INTERCHANGE driver:
1. Select a driver from the Available Drivers list.
Use the table below as a guide in selecting a driver.
The PanelView terminal type
and the communication card
installed in your computer
determines the driver selection.
For Direct Transfers Select:
For These Terminals:
To Transfer Applications:
DF1 on COM Port➀
Remote I/O, DF1, DH+,
ControlNet, DeviceNet
between the RS-232/DF1 port of a PanelView terminal and a computer using DF1
(RS232) communications.
RS-232 (DH-485)
DH-485
between a computer and the RS-232 port of an RS-232 PanelView terminal.
between a computer on the DH-485 network and the DH-485 port of a DH-485
PanelView terminal using a 1747-PIC interface converter.
1747-PIC (DH485)
H485
on COM Port
➀ Driver is not required. PanelBuilder has an Internal DF1.
For Pass-Through Select:
1784-KL on DH+
For These Terminals:
To Transfer Applications:
Remote I/O
between a computer on the DH+ link using a 1784-KL communications card and the
Remote I/O port of a PanelView terminal on a Remote I/O network.
between a computer on the DH+ link using a 1784-KL communications card and the
RS-232 port of a DH-485 PanelView connected to Port 0 of an SLC 5/04.
between a computer on the DH+ link using a 1784-KL communications card and the
DH+ port of a PanelView terminal on the DH+ link.
between a computer on the DH+ link using a 1784-KT/B, -KT2 communications card
and the Remote I/O port of a PanelView terminal on a Remote I/O network.
between a computer on the DH+ link using a 1784-KT/B, -KT2 communications card
and the RS-232 port of a PanelView terminal, connected to Port 0 of an SLC 5/04.
between a computer on the DH+ link using a 1784-KT/B, -KT2 communications card
and the DH+ port of a PanelView terminal on the DH+ link.
between a computer on the ControlNet network using a 1784-KTC communications
card and the ControlNet port of a PanelView terminal.
RS232 (DH-485)
DH+
Remote I/O
1784-KT/1784-KT2 on DH+
RS-232 (DH-485)
DH+
1784-KTC on ControlNet
ControlNet
1784-KTX on DH485
DH-485
between a computer on the DH-485 network using a 1784-KTX communications
card and the DH-485 port of a PanelView terminal.
Publication 2711-6.0
2–12
Installation
For Pass-Through Select:
For These Terminals:
To Transfer Applications:
Remote I/O
between a computer on the DH+ link using a 1784-KTX communications card and
the Remote I/O port of a PanelView terminal on a Remote I/O network.
between a computer on the DH+ link using a 1784-KTX communications card and
the RS-232 port of a PanelView terminal, connected to Port 0 of an SLC 5/04.
between a computer on the DH+ link using a 1784-KTX communications card and
the DH+ port of a PanelView terminal on the DH+ link.
between a computer on the DH+ link using a 1784-PCMK communications card and
the Remote I/O port of a PanelView terminal on a Remote I/O network.
between a computer on the DH+ link using a 1784-PCMK communications card and
the RS-232 port of a PanelView terminal, connected to Port 0 of an SLC 5/04.
between a computer on the DH+ link using a 1784-PCMK communications card and
the DH+ port of a PanelView terminal on the DH+ link.
between a computer on the DH-485 network using a 1784-PCMK communications
card and the DH-485 port of a PanelView terminal.
RS-232 (DH-485)
1784-KTX on DH+
DH+
Remote I/O
1784-PCMK on DH+
RS-232 (DH-485)
DH+
1784-PCMK on DH-485
DH-485
2. Click the Add Device button.
A configuration dialog opens for the selected driver.
The following dialog opens for the DF1 (RS-232) on COM Port
driver.
Unique number assigned
to INTERCHANGE driver
(This is not the computer’s COM port.)
Default Driver Name
(can be edited)
DF1 parameters for a PanelView
terminal must be set to:
Baud: 19200
Parity: None
Error Detect: CRC
COM Port Parameters should be set to:
COM Port 2 typically uses Interrupt (IRQ) 3
or
COM Port 1 typically uses Interrupt (IRQ) 4
Disables driver configuration
temporarily without removing
it from Configured Devices
list.
If you change the COM Port setting, change the Interrupt to the
appropriate setting.
Publication 2711-6.0
Installation
2–13
This dialog opens for the 1747-PIC (DH485) on COM Port
driver.
Unique number assigned
to INTERCHANGE driver
(This is not the computer’s COM port.)
Default Driver Name
(can be edited)
DH-485 Station Address (or Node
Address) of the Computer is typically 0.
COM Port Parameters should be set to:
COM Port 2 typically uses Interrupt (IRQ) 3
or
COM Port 1 typically uses Interrupt (IRQ) 4
Disables driver configuration
temporarily without removing
it from Configured Devices
list.
3. Edit parameters and click OK when done.
The parameters are specific to the communications card installed
in your computer or the type of connection you will be using to
transfer files.
Important:
You must set Interrupts for all INTERCHANGE
drivers.
The configured driver appears under the Configured Devices list.
Configured Devices:
NAME
Refers to driver name
DEVICE Refers to selected driver
PORT
Refers to unique number assigned
to INTERCHANGE driver
STATUS Shows whether driver is enabled/disabled
Important:
Do not configure more than one driver for the
same communication port.
Publication 2711-6.0
2–14
Installation
4. Click OK to exit the dialog.
5. Exit Windows and reboot the 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.
After rebooting the computer, messages display indicating that the
INTERCHANGE driver was successfully configured and loaded.
For example, the following messages appear for the DF1 driver.
CFG_DF1 (001A) Reading device configuration from
C:\RSI\IC\BIN\CFG_KT.INI.
CFG_DF1 (0000) TSR configured, no errors detected
Important:
Errors that occur during a reboot indicate an incomplete
or incorrect configuration of the INTERCHANGE
drivers. Reconfigure the drivers.
Editing INTERCHANGE Driver Parameters
To edit the configuration parameters of an active driver:
1. Select the driver from the Configured Devices list.
2. Click the Edit Device button.
3. Edit configuration parameters in the driver’s dialog.
4. Click OK to close dialogs.
5. Reboot your computer to load the new configuration.
Removing INTERCHANGE Driver
To remove a current driver configuration:
1. Select the driver from the Configured Devices list.
2. Click the Remove Device button.
You are prompted to confirm the operation. If you click Yes, the
driver is removed from the Configured Devices list.
3. Click OK to close dialog.
4. Reboot your computer to unload the driver.
Publication 2711-6.0
Installation
2–15
Setting Advanced INTERCHANGE Parameters
To specify advanced parameters for drivers:
1. Click the Advanced button from the INTERCHANGE Device
Configuration dialog.
Specifies whether to load INTERCHANGE drivers
(executables) into high memory. Drivers are not
loaded until you reboot computer.
Specifies whether self-diagnostics are run
on KT devices before loading driver
configuration. The default is to perform test.
Specifies whether to use upper MS-DOS
memory for packet buffer space. The
default is to use upper memory.
Specifies the
memory manager
in use on your
system.
Allocates number of packet buffers
(1 to 200). Each buffer uses 300
bytes of memory. The default is 20.
Allocates space for the number of
unsolicited messages (0 to 200). The
default is 0, which indicates no space.
Specifies Enabler to use for the 1784-PCMK on 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-7). In Windows 95, the sockets are numbered (0 – 8).
Generic Enabler uses PCENABLE.
This enabler requires that you enter a Memory address and
an IRQ (Interrupt).
2. Edit parameters and click OK.
Publication 2711-6.0
2–16
Installation
INTERCHANGE Notes
Conflicts with INTERCHANGE Drivers
The INTERCHANGE drivers may cause conflicts with other drivers
sharing common interrupts or memory areas of 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.
• If you experience lockups when using a serial mouse in a DOS
application, wait several seconds for the mouse to initialize. If
mouse operation is still a problem, run ABICSTOP.
1. Exit Windows.
2. Type ABICSTOP at the DOS prompt.
C:\> ABICSTOP
If ABICSTOP is not successful, comment out ABICRUN in
AUTOEXEC.BAT and reboot. Then run ABICSTOP again.
• Error messages during a system reboot may indicate an
incomplete or incorrect configuration of the INTERCHANGE
driver. Reconfigure the driver.
For more details on INTERCHANGE Software, refer to the
INTERCHANGE Software user manuals. Allen-Bradley
publications are available through Allen-Bradley local distributors.
Disabling INTERCHANGE
INTERCHANGE Software uses 40 to 80K of base memory. The
AUTOEXEC.BAT file is configured to automatically load
INTERCHANGE drivers at system reboot.
To disable INTERCHANGE, place REM before the CALL
statement in the AUTOEXEC.BAT file. For example:
REM CALL ABICRUN.BAT
Disabling INTERCHANGE frees up base memory and also makes
the computer’s COM port available to other applications.
Publication 2711-6.0
Installation
2–17
Other Software that Uses INTERCHANGE
To run other software (such as APS) that uses a different
INTERCHANGE driver on the same communication port as
PanelBuilder software, follow the steps below.
Note: If the software packages use the same INTERCHANGE driver
on a communication port (except for the DF1 driver), you can ignore
these steps.
1. Exit from Windows if necessary.
2. Type ABICSTOP at the DOS prompt, for example:
C:\> ABICSTOP
3. Run the other software.
Before running PanelBuilder software again, or other software that
uses different INTERCHANGE drivers:
1. Exit from Windows if necessary.
2. Type ABICRUN at the DOS prompt
Adding or Updating Communication Card
Update the CONFIG.SYS file when you add or modify a hardware
configuration for a communication card such as the KT or PCMK
card. Refer to the INTERCHANGE README and CFG_KT.TXT
files for details on how to do this. The memory manager you use
determines the type of, and syntax of, the (communications card)
entry required in CONFIG.SYS.
Publication 2711-6.0
Planning an Application
Chapter Objectives
This chapter contains the following sections:
Section
Design Checklist
Page
Design Checklist
3–1
Applications and Projects
3–2
Steps for Creating an Application
3–3
Safety Considerations
3–4
Screen Worksheets
3–4
Linking Screen Objects to Controller Data
3–6
Data Types
3–8
Data Formats
3–9
Review Addressing
3–12
Defining Tags
3–13
Memory Requirements/Tips
3–14
Before creating an application, check the following:
n Plan and document application
n Consider safety requirements
n Design screens
n Review data types
n Review data formats
n Review addressing of objects
n Review memory requirements
Publication 2711-6.0
3–2
Planning an Application
Applications and Projects
An application is the basic unit of PanelBuilder software. It is
designed to be loaded in a specific type of PanelView terminal and
run using a specific type of logic controller. It includes:
• screens with controls, indicators, graphics, text and screen
controls
• tags, which are named references to data addresses in a logic
controller
• alarm controls
• runtime communication parameters
• operating parameters of terminal
A project is assigned or created when an application is created. It
links the application to:
• tag database
• specific devices – PanelView terminal and controller– that the
application will interact with
PanelBuilder software can convert an application to run in a different
PanelView terminal or different type of controller by assigning it to a
different application. See page 21–2. In this case, some of the tags
and objects may have to be edited.
An application is validated for correct operation before it can be
downloaded to a terminal. All incompatibilities are caught during
validation.
Publication 2711-6.0
Planning an Application
Steps for Creating an
Application
3–3
The general steps for creating an application are:
1. Document the application carefully including:
• purpose of the application
• information the operator needs to make good decisions
• choices the operator will have to make
Review this document with the operator before the application is
run.
2. Create the application including:
• screens (each screen may include controls, indicators graphics,
text and screen controls).
• alarm controls
• runtime communication parameters
• operating parameters of terminal
The application is associated with a project when the application
is created. The project database is a collection of tags and
devices (PanelView terminal and logic controller) that are used by
the application. A project can support more than one application,
provided that they are all designed for the same type of terminal
and the same type of logic controller.
3. Values associated with alarms, objects and variables are stored in
controller memory addresses, and are referenced by the
application via named tags. Enter tags in the Tag Editor using:
• Table View of the Tag Editor before the application is created
• Tag Form dialog when creating objects
4. Validate and download the application to the PanelView terminal.
5. Run the application.
While the application is running, triggered alarms are added to
the Alarm List.
Publication 2711-6.0
3–4
Planning an Application
Safety Considerations
When placing push buttons on a screen:
!
ATTENTION: Don’t place emergency stop buttons
or controls critical for safe operation on a screen. Use
separate hard-wired operator interface devices. The
inside cover of this manual references appropriate
standards.
• Don’t place important buttons in the center of touch screens
where they may be blocked temporarily by terminal messages,
the Alarm Banner, or the scratchpad.
• Don’t place push buttons in the same area on screens that follow
one another. An operator may press the same position, mistaking
a stop button on one screen for a start button on another.
!
ATTENTION: Don’t press multiple touch screen
objects at the same time. Pressing multiple objects
simultaneously may result in unintended operation.
• Place touch screen objects far enough apart so the operator would
naturally lift a finger to move to the next object. Touch screens
are intended for a single object press.
Push buttons are disabled for 1/2 second after a screen change.
Also, when a new screen appears, push buttons from the previous
screen must be released before the terminal responds to push buttons
on the new screen.
Screen Worksheets
Figures 3.1 – 3.2 show the Keypad and Touch Screen Worksheets for
the PanelView 900 terminals. Worksheets for other terminals are in
Appendix C. Use these worksheets to draw your application screens.
At the top of each screen, enter the application name, screen
name/number and project name that you want to link to the
application. The project defines tag addresses and devices
(PanelView terminal and controller) that will communicate.
The number and size of objects you can place on a screen is limited
only by screen space. On touch screen terminals, each input control
should occupy at least 1 touch cell. The number of available touch
cells depends on the terminal size. The PanelView 900/1000/1400
Touch Screen terminal has 384 touch cells. The PanelView 550/600
Keypad & Touch Screen terminal has 128 touch cells.
Each screen must contain a screen selector allowing the operator to
navigate between screens in an application. You can assign a screen
selector to a touch cell and/or a function key.
Review Chapters 7 – 14 on screen objects before completing the
worksheets. Also review memory requirements (at end of chapter)
for hints on reducing the byte size of an application.
Publication 2711-6.0
Planning an Application
3–5
Figure 3.1
PanelView 900 Keypad Terminal Worksheet
Project Name:
Application Name:
Screen Name / Number:
F1
F2
F3
F4
F5
F6
F7
F8
F9
F10
F11
F12
F13
F14
F15
F16
Figure 3.2
PanelView 900 Touch Screen Terminal Worksheet
Project Name:
Application Name:
▲
▼
Screen Name / Number:
Touch screen push
buttons must occupy at
least one touch cell.
Touch Cell
Publication 2711-6.0
3–6
Planning an Application
Linking Screen Objects
to Controller Data
Each dynamic screen object must be linked to a controller data table.
(This is not always true for DeviceNet. See publication DeviceNet
Communications for PanelView Terminals). The PanelView terminal
either reads data for indicators such as bar graphs or writes data for
controls like push buttons.
Values in the logic controller data table are updated on a regular
basis. This process is called scanning. In each scan:
• the logic controller and the terminal write data to specific
addresses updating values
• the logic controller reads the entire data table and updates values
at other addresses according to the PanelBuilder application
PanelView 900 Application
PLC/SLC Data Tables
Level
Full
3/4
1/2
Empty
Input Table
Output Table
Integer Table
Counters, Timers,
Status, Controls
PanelBuilder uses read and write tags to link objects with specific
controller addresses. Each tag has a unique name and specifies
attributes such as the location and size of an address, the type of data
to read from or write to the address and scaling parameters.
Publication 2711-6.0
Planning an Application
Controller Data Files
3–7
A tag can be assigned to any file type that the PLC, SLC or
MicroLogix 1000 supports.
PLC-5 File Types
ile Type
pe
File
Output
ea / Write
Read
I entifier
Identifier
ile Number
um er
File
lement
Element
Read
O
0
0-277➀
Integer
u lement
Sub-Element
NA
it Number
um er
Bit
0-17➀
Input
Read➁
I
1
0-277➀
NA
0-17➀
Status
Read / Write
S
2
0-127
NA
0-15
Bit (Binary)
Read / Write
B
3-999
0-999
NA
0-15999
Timer
Read / Write
T
3-999
0-999
PRE, ACC
EN, TT, DN
Counter
Read / Write
C
3-999
0-999
PRE, ACC
Control
Read / Write
R
3-999
0-999
LEN, POS
Integer
Read / Write
N
3-999
0-999
NA
0-15
BCD
Read / Write
D
3-999
0-999
NA
0-15
Float
Read / Write
F
3-999
0-999
NA
0-31
ASCII
Read / Write
A
3-999
0-999
NA
NA
String
Read / Write
ST
3-999
0-999
LEN
NA
CU, CD, DN.
OV, UN
EN, EU,
DN, EM, ER,
UL, IN, FD
➀ Octal format, all other values are decimal.
➁ Remote I/O allows the PanelView to write its own output words.
➂ ControlNet terminals do not support the reading/writing of input/output tags.
SLC File Types
A tag can be assigned to any file type the SLC controller supports,
except M0 and M1.
Read
ea / Write
I entifier
Identifier
File
ile Number
um er
Element
lement
Output
Read
O
0
1-31
Integer
Sub-Element
u lement
0-255
Input
Read
I
1
1-31
0-255
Status
Read / Write
S
2
➀
NA
0-15
Bit (Binary)
Read / Write
B
3, 9-255
0-255
NA
0-4095
Timer
Read / Write
T
4, 9-255
0-255
Counter
Read / Write
C
5, 9-255
0-255
PRE,ACC,
1, 2
PRE, ACC,
1, 2
Control
Read / Write
R
6, 9-255
0-255
LEN, POS,
1, 2
13-15, EN, TT,
DN
11-15, CU, CD,
DN, OV, UN
8-15, EN, EU,
DN, EM, ER,
UL, IN, FD
Integer
Read / Write
N
7, 9-255
0-255
NA
Float
Read / Write
F
8-255
0-255
NA
NA
ASCII
Read / Write
A
9-255
0-255
NA
0-15
String
Read / Write
ST
9-255
0-255
LEN, 0-41
0-15
File
ile Type
pe
Bit
it Number
um er
0-15
0-15
0-15
➀ Number of Status File elements depends on controller (e.g., SLC 5/03 has 0-99 and SLC 5/04 has 0-163).
Publication 2711-6.0
3–8
Planning an Application
MicroLogix 1000 File Types
ea / Write
Read
I entifier
Identifier
ile Number
um er
File
lement
Element
Output
Read
O
0
0
Integer
u lement
Sub-Element
0-4
Input
Read
I
1
0
0-7
Status
Read / Write
S
2
0–32
NA
0-15
Bit (Binary)
Read / Write
B
3
0-31
NA
0-511
Timer
Read / Write
T
4
0-39
Counter
Read / Write
C
5
0-31
PRE,ACC,
1, 2
PRE, ACC,
1, 2
Control
Read / Write
R
6
0-15
LEN, POS,
1, 2
13-15, EN, TT,
DN
11-15, CU, CD,
DN, OV, UN
8-15, EN, EU,
DN, EM, ER,
UL, IN, FD
Integer
Read / Write
N
7
0-104
NA
ile Type
pe
File
Data Types
it Number
um er
Bit
0-15
0-15
0-15
The PanelView terminal can read or write a single bit or value.
Bit Data
Bit data occupies a single bit and represents an On (closed) or
Off (open) condition.
DH-485 or DH+ Address B3/10
1
= On
0
= Off
Remote I/O Address B20:0/0
1
= On
0
= Off
Bit addresses greater than 15 (B3/24) are not valid when a DH+
PanelView terminal is communicating with a PLC-5.
Least Significant Bit
Least Significant Bit (LSB) triggering is available for multistate
indicators, list indicators, message displays and alarms. If priority is
important in triggering a series of states or messages, use Least
Significant Bit triggering:
• Triggering for messages or states are assigned a word of memory
(or more than one word if more than 16 messages or states are to
be prioritized). Each message or state trigger corresponds to a
specific bit, starting from the right (least significant bit).
• When the word or sequence of words is read right to left by the
terminal, it ignores bits that are not set (0) and displays the
message or state corresponding to the first bit that is set (1). The
controller clears/sets this bit, the terminal only reads the bit.
• The next time the word is read, a different bit is the first one set
(1), then its message or state displayed.
Publication 2711-6.0
Planning an Application
3–9
Value Data
Value data occupies a word (2 bytes or 16 bits) that represents a
numeric value. No matter how large or small the value, a whole
word must be assigned unless it is a bit array.
32768 16384 8192 4096
Address N7:2
= 277
0
0
0
0
2048 1024
0
0
512
256
128
64
32
16
8
4
2
1
0
1
0
0
0
1
0
1
0
1
Floating point values occupy 4 bytes or 32 bits.
Data Formats
PanelView (Tag) Formats
The PanelView terminal recognizes and transfers 7 data formats.
Data Format
Range
Bit
0 or 1
Unsigned Integer
0 to 65535
Signed Integer
-32768 to +32767
IEEE Floating Point
–99,999,997,952 to 999,999,995,904
4BCD
0 to 9999
Bit Array
0 to 65535
Character Array
Protocol Dependent
Bit
A bit data type occupies one bit of memory. Its address is given not
as a word (N7:2), but as a bit (N7:2/10). A bit is a location, and
depends on its position in the word. It can be set or reset.
Signed and Unsigned Integers
Signed and unsigned integer values occupy one word (2 bytes or 16
bits) of memory, no matter how small the value.
Every bit has a value that depends on its position in the word. The
value encoded is the sum of the bits that are sent.
Signed Integer
(-277)
32768 16384 8192 4096 2048 1024
1
1
1
1
1
1
Sign Bit
1 = Negative
0 = Positive
Unsigned Integer
(277)
0
256
128
64
32
16
8
4
2
1
1
0
1
1
1
0
1
0
1
1
-1 + -256 + -16 + -4 = -277 (2’s Complement)
32768 16384 8192 4096 2048 1024
0
512
0
0
0
0
512
256
128
64
32
16
8
4
2
1
0
1
0
0
0
1
0
1
0
1
256
16
4
Data entered as 277
Publication 2711-6.0
1
3–10
Planning an Application
Floating Point
The 32-bit floating point format supports IEEE single precision
formatted values in the range -99,999,997,952 to 999,999,995,904.
The floating point range is limited by the number of display and data
entry character positions available (12) or by the processor. The
PLC-5, SLC 5/03 and SLC 5/04 suppport 7 digits.
The maximum decimal point precision is 9 places for negative values
(-0.000000001) and 10 places for positive values (0.0000000001).
The negative sign occupies 1 character position, values without a
sign are positive. Decimal point values are entered or displayed with
at least one digit to the left of the decimal point.
When large numbers are entered, values to the right of the decimal
may be changed because of the 32-bit floating representation. For
example, if you enter 1.1111111801, PanelBuilder displays
1.1111111641. PanelBuilder uses the closest approximation to
represent your input.
4 BCD
Data in BCD format (also called 4-BCD) occupy one word of
memory. Every four bits encodes a single digit 0 9.
Each value occupies one word even if it is less than 9999.
8
4BCD
(277)
0
4
2
0
0
0
Publication 2711-6.0
1
0
8
0
4
0
2
2
1
8
1
0
0
4
1
7
2
1
8
4
1
1
0
1
7
2
1
1
1
Planning an Application
3–11
Bit Array
A bit array is an unsigned integer format that is assigned to part of a
word. You can assign the rest of the word to other bits or bit arrays.
The length of the array is from 1 to 16 bits. The maximum value
stored in a bit array varies from 1 (1-bit array) to 65,535 (16-bit
array). This format allows you to specify the actual number of bits
to be assigned to an object. Unused bits can then be assigned to
other object(s).
Array Size
Range
Array Size
Range
1
0 or 1
9
0 to 511
2
0 to 3
10
0 to 1023
3
0 to 7
11
0 to 2047
4
0 to 15
12
0 to 4095
5
0 to 31
13
0 to 8191
6
0 to 63
14
0 to 16383
7
0 to 127
15
0 to 32767
8
0 to 255
16
0 to 65535
For example, a value that will never be greater than 277 is assigned a
bit array with length = 9. Other bits or bit arrays could then be
assigned to locations starting at N7:2/9.
Address
N7:2/0
277
Important:
64
32
16
8
4
2
1
0
0
0
0
0
0
0
256
128
64
32
16
8
4
1
0
0
0
1
0
1
256
+
16 +
2
4
1
0
+
1
1
A bit array can occupy only one word. The length of a
bit array starting at N7:2/9 must be 7 or less.
Character Array
Data in a character array are assigned to ASCII variables. The
length of the character array is protocol dependent.
Publication 2711-6.0
3–12
Planning an Application
Review Addressing
Before entering tags in the Tag Editor, you may want to record tag
addresses using the Address Worksheet in Appendix C. For proper
address formats, refer to your controller’s user manual. The
illustration below shows an example of recording addresses.
PUMP PRESSURE
200
150
100
50
PUMP CONTROL
0
F1
F2
ON
OFF
Tag Name = PRESSBG2
F5
MENU
Tag Name = PB2
Tag Name = PB1
Function Keys
PUMP CONTROL
ON
=
F1
= Address I:020/01
OFF
=
F2
= Address I:020/00
=
MENU
F5
Controller
Address
Address Worksheet
Word Address
Tag Name
Octal
17
16
15
14
13
12
11
10
7
6
5
4
3
2
1
0
Decimal
15
14
13
12
11
10
9
8
7
6
5
4
3
2
1
0
I:020
PB2 PB1
I:021
Word Address
Tag Name
N:027
N:028
Publication 2711-6.0
Octal
17
16
15
14
13
12
11
10
7
6
5
4
3
2
1
0
Decimal
15
14
13
12
11
10
9
8
7
6
5
4
3
2
1
0
PRESSBG2
Planning an Application
Defining Tags
3–13
Read/write tags that define controller addresses for objects are
entered in the Tag Editor. A tag has the following attributes.
Tag Attributes
Description
Tag Name➀
Unique name identifying tag address
Data Type
Bit, 4BCD, Unsigned/Signed Integer, Bit Array,
Character Array, Float
Array Size
Number of bits in a bit array
Description
General description of tag
Node Name
Name of controller associated with tag
Tag Address
Specifies data table word or bit
Initial Value➁
Value stored at tag address on powerup
Update Frequency
Rate at which tag address value is updated
Scaling➁
Scale and offset scale values
Data Entry Limits➁
High and low limits of data stored at tag address
➀ The tag name appears in the object’s dialog and in the Tag Editor.
➁ Usage dependent on object.
The Tag Editor supports two different ways for entering tags:
• table view to enter and edit multiple tags
• form view to enter a single tag
Tags are stored in a database that is referenced by a project name.
The project name is entered when creating a new application file.
The tag name entered in an object’s dialog links the object to the tag
name entered in the Tag Editor.
Table View
Form View
Publication 2711-6.0
3–14
Planning an Application
Memory
Requirements/Tips
The memory available for applications varies for the PanelView
terminals.
Screen Tips on Reducing Memory
Review the following list for hints on ways to reduce the size of an
application.
• For DH-485, DH+ or DF1 applications, group tag addresses for
each screen in the same 40 word block.
• For multistate or list objects, create the exact number of states or
entries required by the application.
• Don’t use multistate indicators, list indicators, or message
displays if a numeric data display can provide the same function.
Likewise, don’t use a control list selector if a numeric entry
object is sufficient.
• If a multistate indicator uses the same text for all states, use a
solid indicator with outer text instead of inner text for each state.
• Reuse text that exists in the application rather than creating the
same string multiple times. See Chapter 18 for details on how to
copy existing text into objects or object states.
• Limit the amount of text in screen names, messages and objects.
• When drawing rectangles, use a shape instead of individual lines.
Each line requires the same amount of memory as a single shape.
• Freeform drawings are memory intensive.
• Rectangular objects or graphics of the same size use less memory
because the terminal uses the same data to display the objects. If
2 push buttons are the exact same size, the terminal (keypad or
touch) uses the same data to display the rectangle of both buttons.
• Use a global object if the application requires the same object on
several screens. A global object can be accessed from any screen.
The PanelView stores only 1 copy of the object. See Chapter 14.
• Limit the use of bitmap graphics.
• Use multiple embedded variables within a single text string rather
than using multiple numeric data displays.
• Maximum number of screens is 255.
• Maximum number of tags and objects is unlimited but must not
exceed runtime memory.
• Maximum number of bitmaps and text is unlimited but must not
exceed application memory.
Publication 2711-6.0
Communications Overview
Chapter Objectives
This chapter contains the following sections:
Section
PanelView Terminal Ports
Page
PanelView Terminal Ports
4–1
DH-485 Communications
4–2
DH+ Communications
4–3
DF1 Communications
4–4
DH-485/DH+/DF1 Communication Considerations
4–5
Remote I/O Communications
4–6
Discrete I/O
4–9
Block Transfers
4–11
The PanelView terminals have ports that support a variety of
communication options, including:
• Remote I/O communications
• DH-485 communications
• DH+ communications
• DF1 communications
• DeviceNet communications
• ControlNet communications
For details on how to configure a PanelView terminal to
communicate on a DeviceNet network, see publication DeviceNet
Communications for PanelView Terminals.
For details on how to configure a PanelView terminal to
communicate on a ControlNet network, see publication ControlNet
Communications for PanelView Terminals.
The catalog number of the terminal determines the physical ports and
communication protocol supported by that terminal. Many of the
terminals have an additional RS-232 port which is used for printing
and/or transferring applications.
The PanelView terminal type and communication parameters are
selected and configured as a part of the application.
• PanelView terminal is defined when the application is created
(New Application dialog) and is also accessed from the Terminal
Setup dialog. See Chapter 6.
• Communication parameters for the logic controller and terminal
are defined in the Communication Setup dialog (Comms. Setup
button on Terminal Setup dialog). See Chapter 20.
Publication 2711-6.0
4–2
Communications Overview
DH-485 Communications
The following PanelView terminals communicate on a DH-485 link:
• DH-485 PanelView terminals communicate with an SLC
controller using a point-to-point or network connection.
• RS-232 PanelView terminals communicate point-to-point with
the Channel 0 port of an SLC 5/03 or 5/04 controller using
DH-485 protocol.
The PanelView terminal operates as a unique DH-485 node (0 to 31).
DH-485 parameters for the PanelView DH-485/RS-232 terminal and
controller are defined in the Communication Setup dialog (accessed
from the Terminal Setup dialog).
Terminal Name is stored in Project
with Catalog Number information.
PanelView 900
DH-485 Terminal
with RS-232 Printer Port
Node Type
5/00
5/01
5/02
5/03 - OS 300
5/03 - OS 301
5/03 - OS 302
5/04 - OS 400
5/04 - OS 401
MicroLogix 1000
Must match Node
Name in Tag Editor.
The following table defines DH-485 parameters and defaults for a
PanelView DH-485 or RS-232 Terminal and controller.
DH-485 Device
Pane
V ew Terminal
Term na
PanelView
DH-485 Parameter
Node Address
Maximum Node
Address
Baud Rate
Network Node
Publication 2711-6.0
Node Name
Node Address
Node Type
Options
Default
0 – 31
1 – 31
2
31
1200, 2400,
9600, 19.2K
User supplied
0 – 31
See above figure
19.2K
None
1
None
Communications Overview
DH+ Communications
4–3
The DH+ PanelView terminals communicate with a PLC or SLC
5/04 controller on the Allen-Bradley DH+ link.
Addressing for a DH+ application is similar to a DH-485 application
except the DH+ link supports 64 nodes (0 - 77 octal) and higher baud
rates. The DH-485 link supports 32 nodes.
The DH+ parameters for the terminal and controller are defined in
the Communication Setup dialog (accessed from Terminal Setup
dialog).
Terminal Name is stored in
Project with Catalog Number
information.
PanelView 900
DH+Terminal
with RS-232 Printer Port
Network Node
SLC 5/04
PLC-5/10
PLC-5/11
PLC-5/12
PLC-5/15
PLC-5/20
Must match Node
Name in Tag Editor.
PLC-5/25
PLC-5/30
PLC-5/40
PLC-5/60
PLC-5/80
The following table defines DH+ parameters and defaults for a
PanelView DH+ terminal and logic controller.
DH+ Device
DH+ Parameter
Pane V ew Term
PanelView
Terminal
na
Node Address
Baud Rate
Network Node
Node Name
Node Address
Node Type
Options
Default
0 – 77 octal
57.6K, 115.2K, 230.4K
User supplied
0 – 77 octal
See above figure
2
57.6 K
None
1
None
Publication 2711-6.0
4–4
Communications Overview
DF1 Communications
The DF1 PanelView terminals communicate with an SLC, PLC or
MicroLogix 1000 controller over a point-to-point DF1 link or using
DF1 network communications. The DF1 terminals support full
duplex communications.
The DF1 parameters for the terminal and controller are defined in the
Communication Setup dialog (accessed from Terminal Setup dialog).
Terminal Name is stored in
Project with Catalog Number
information.
PanelView 900
DF1 Terminal
with RS-232 Printer Port
Select only when
using DF1 network
communications.
Must match Node
Name in Tag Editor.
MicroLogix 1000
SLC 5/03, 5/04, 5/05
PLC-5/10, 5/12, 5/15, 5/25 via bridge
PLC-5/11, 5/20, 5/26, 5/40, 5/46, 5/60, 5/80 via Channel 0 Port
PLC-5/20C, 5/40C, 5/60C, 5/80C via Channel 0 Port
PLC-5/20E, 5/40E, 5/80E via Channel 0 Port
The following table defines DF1 parameters and defaults for a DF1
PanelView terminal and logic controller.
DF1 Device
DF1 Parameter
Node Address
Baud Rate
Parity/Stop Bits
PanelView Terminal
Errror Detection
Handshaking
Network Node
Publication 2711-6.0
Node Name
Node Address
Node Type
Options
Default
0 – 254 decimal
1200, 2400, 4800,
9600, 19.2K
Odd/1
Even/1
None/1
None/2
BCC or CRC
On (CTS/RTS
enabled)
Off (CTS/RTS
disabled)
User supplied
0 – 254 decimal
See above figure
64
9600
None/1
CRC
Off
None
None
Communications Overview
DH-485/DH+/DF1
Communication
Considerations
4–5
The PanelView terminal writes information (write tags) to the
processor only when a change of state occurs. The terminal reads
information (read tags) from the processor continually. The read and
write tags can use the same address.
Scan Group
A scan group consists of 40 consecutive words within the same data
file and processor. The group starts at the lowest address in the data
file. The scan group must have the same update frequency. For an
application with tag addresses: N7:0, N7:39, N7:40, N11:0, N12:5
and N12:40, the scan groups are:
• N7:0 – N7:39
• N7:40
• N11:0
• N12:5 – N12:40
Minimize the number scan groups per screen. Maintain the same
update frequency for each 40 word block.
Publication 2711-6.0
4–6
Communications Overview
Remote I/O
Communications
On a Remote I/O network, the PanelView Remote I/O terminals
appear like a Remote I/O rack. The PanelView terminal can occupy
all of or part of a single rack (128 I/O). You can assign 2 types of
addresses to objects on a Remote I/O network:
• Discrete - a single input or output bit address
• Block transfer - a series of contiguous word addresses
Data is transferred over a remote I/O link as either a:
• Read or Input = data to the PLC from the PanelView
• Write or Output = data from the PLC to the PanelView
The processor continually scans the PanelView terminal for inputs
and updates the outputs. Read and write tags must have different
discrete I/O addresses and are not linked in the terminal.
Rack Sizes and Module Groups
The PanelView I/O can occupy a 1/4, 1/2, 3/4, or Full rack. Each 1/4
rack contains two module groups (32 input and 32 output bits). An
entire rack contains 8 module groups that are numbered from 0 to 7.
Rack #
Four 1/4
Rack Sizes
PanelView I/O
1/4
1/4
1/4
1/4
Input
0 1
2 3
4 5
6 7
Output
0 1
2 3
4 5
6 7
16 Bits each Module Group
Eight Input/Output
Module Groups
If a PanelView terminal does not occupy a complete I/O rack, you
can assign another PanelView or other devices to the same rack.
Parameter
1st PanelView
Other Rack Device
Rack Number
1
1
Starting Module Group
0
6
Rack Size
3/4
1/4
Last Chassis
No
Yes
The PLC type determines the maximum rack number for the
PanelView.
Publication 2711-6.0
Communications Overview
4–7
Remote I/O Scan Group
A Remote I/O scan groups consists of words or address contained
within a discrete I/O rack or within a block transfer. For example, an
application with a full rack, block transfer read N7:0, length 64 and a
block transfer write N7:128, length 62 has these scan groups:
• O:010 – O:017
• I:010 – I:017
• N7:0 – N7:63
• N7:64 – N7:127
• N7:128 – N7:190
Controller Types
The PanelView Remote I/O terminals communicate with the
controllers below. For each controller, the table lists supported rack
numbers and support for Pass-Through and block transfers.
Lowest
Rack #
Highest
Rack #
Pass-Through Support
Block Transfer Support
IBM PC 6008-SI
VME
V
E 6008-SV
DEC
EC QBUS
S 6008-SQ
6008-S
0
7
No
Yes
PLC 5/11
3
3
All Series, All Revisions
Yes
PLC 5/15
1
3
Series B, Revision N or later
Yes
PLC 5/20
1
3
All Series, All Revisions
Yes
PLC 5/25
1
7
Series A, Revision J or later
Yes
PLC 5/30
1
7
Series A, Revision B or later
Yes
PLC 5/40
1
17octal
Series A, Revision E or later
Series B, Revision B or later
Yes
PLC 5/60
PLC 5/80
1
27octal
Series A, Revision E or later
Series B, Revision B or later
Yes
SLC 1747-SN Series A
0
3
No
No
SLC 1747-SN Series B
0
3
Yes
Yes
Other 1771-SN Subsystem
1
7
No
No
Controller/Scanner
Publication 2711-6.0
4–8
Communications Overview
Remote I/O Communication Parameters
Remote I/O communication parameters are defined in the
Communication Setup dialog which is accessed from the Terminal
Setup dialog.
Terminal Name is stored in Project
with Catalog Number information.
PanelView 900
Remote I/O Terminal
with RS-232 Printer Port
Must match Node
Name in Tag Editor.
The table below defines Remote I/O communication parameters for
the PanelView terminal.
Remote I/O
Device
Remote I/O
Parameter
Type
PLC/S anner
PLC/Scanner
Name
Rack Address
Module Group
PanelView
Pane
V ew
Terminal
Baud Rate
Last Chassis
Publication 2711-6.0
Description
Type of PLC controller/scanner that will
communicate with the PanelView
Remote I/O terminal.
Unique name assigned to controller.
This name is also used in the Node
Name field in the Tag Editor.
Unique address of PanelView terminal
on Remote I/O link.
Module groups occupied by PanelView
terminal in the rack. The Module groups
must be contiguous.
The baud rate of the Remote I/O link
determines the maximum cable length.
Options
See table on
page 4–7.
User supplied
0 – 27octal
0,1 2,3 4,5 6,7
57.6K
115.2K
230.4K
Specifies whether the terminal occupies Yes, No
the last module group (no higher module
groups assigned) within the rack.
10,000 feet
5,000 feet
2,500 feet
Communications Overview
Discrete I/O
4–9
Discrete I/O addresses communicate directly with the controller and
provide faster updates than block transfers. Discrete I/O is
recommended for:
• Push buttons (for rapid response times)
• Any critical values that you want updated immediately
A PLC rack has 128 discrete I/O points (8 input words/8 output
words). If additional rack space is needed for an application, use
block transfers.
You must assign a read or display tag to an output address. If you
assign a read tag to an input address, a validation error occurs. The
read and write tags must have different tag names and reference
different addresses.
Discrete I/O Addressing for 1771-SN Scanners
The I/O addressing syntax for the 1771-SN Scanner (Series A) is:
I:YYW/BB
O:YYW/BB
where:
YY
=
Rack number
W
=
Word or group address
BB
=
Bit address, 0-7, 10-17 octal
For example:
I:024/10
addresses input bit 10, Rack 2, Module 4.
Discrete Addressing for 1747-SN Scanner, Series A and B
The addressing syntax for the 1747-SN Scanner (Series A and B) is:
I:X.WW/BB
O:X.WW/BB
where:
X
=
Slot where 1747-SN is installed in rack
WW
=
Word address, 0 - 31 decimal
BB
=
Bit address, 0-15 decimal
For example:
I:1.7/13
addresses input bit 13 of Word 7, Slot 1 (where 1747-SN Scanner
resides).
Publication 2711-6.0
4–10
Communications Overview
Discrete I/O Example
The PanelView terminal occupies rack #3 in which its starting
module group is 0. An On/Off push button object is addressed as
I:032/03 and a corresponding indicator as O:032/00.
➀ The PanelView monitors the status of the 8 input
words in its rack assignment.
Rack #3
PanelView I/O
0 1 2 3 4 5 6 7 0 1 2 3 4 5 6 7
8 Input Words
8 Output Words
➁ The PLC ladder program monitors address I:032/03.
032
I:032
00
03
➂ The operator presses the object push button, the PanelView
terminal sets the corresponding address bit.
Pump
CONTROL
ON
OFF
PUMP OFF
PUMP ON
➃ The ladder program determines input bit 03 is On.
17 16 15 14 13 12 11 10 7 6 5 4 3 2 1 0
I:032 0 0 0 0 0 0 0 0 0 0 0 0 1 0 0 0
Input Word
➅ The PanelView terminal reads the indicator address and
displays the new state.
➄ The controller ladder program moves the input bit to the
output bit.
17 16 15 14 13 12 11 10 7 6 5 4 3 2 1 0
O:032 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 1
Output Word
Pump
CONTROL
ON
OFF
Publication 2711-6.0
PUMP OFF
PUMP ON
Communications Overview
Block Transfers
4–11
Remote I/O links allow the transfer of blocks (up to 64 words)
between a PLC and a PanelView terminal. Block transfers are
assigned to a single byte of input data (module control byte) and
output data (module status byte) in the PanelView rack. These two
bytes control the operation of the block transfer and are no longer
available for discrete I/O.
The status and control byte always occupy the low byte of the lowest
module group in the PanelView rack assignment. For example, if the
starting module group is 0:
PanelView I/O
Rack 03
0
1
2
3
4
17
5
16 15
7 Starting Module
6
14
Group 0
13
12
11 10
7
6
5
4
3
2
1
0
2
1
0
Status Byte
Output Word
17
16 15
14
13
12
11 10
7
6
5
4
3
Module Control Byte
Input Word
No matter how many block transfers are assigned (1 to 10), only one
byte is reserved in the input rack and one in the output rack.
Block transfer directions are in reference to the PLC:
• Block Transfer Reads (BTR) are inputs to the PLC and transfer
data from control devices such as push buttons on the PanelView.
• Block Transfer Writes (BTW) are outputs from the PLC and
transfer data to indicators such as bar graphs on the PanelView.
Block Transfer Write
PLC
PanelView Terminal
Block Transfer Read
Publication 2711-6.0
4–12
Communications Overview
Setting Up a Block Transfer
Configure PanelView block transfers using the Block Transfer
dialog, which is accessed from the Communication Setup dialog.
For each block transfer (1 - 10), specify the parameters below:
Parameters
Description
Enabled
Enables or disables the block transfer.
Address
Specifies starting address for the block transfer read or write.
Mode
Specifies R for a Read operator or W for a Write operation.
Length
Specifies the number of words (1 to 64 ) to transfer. The
length 63 is reserved for Pass-Through.
Each block transfer read must be a unique length and each
block transfer write must be a unique length. However, a read
and write block transfer can be the same length.
The PanelView uses the length to identify data blocks.
Pass-Through
Enables or disables Pass-Through for application transfers
between a computer on the DH+ network and a PanelView
terminal on the Remote I/O network.
Pass-Through is a dedicated block transfer fixed at 63 words
in length.
Block Transfer Timeout
Specifies a timeout value for block transfers. A value of 0
disables the timeout.
Each block transfer requires a corresponding Block Transfer Write
(BTW) or Block Transfer Read (BTR) instruction in the ladder
program for the controller. The Address and Length settings must
match the Data File and Length settings in the instructions.
BTR or BTW
BLOCK TRANSFER READ/WRITE
Rack
03
Group
0
Module
0
Control Block
N36:0
Data File
N37:1
Length
4
Continuous
N
Publication 2711-6.0
PanelView Rack Assignment
Group No. 0 7
High or Low Byte (Always 0 for PanelView)
File that controls the operation of the instruction
Address in data file to write or read.
Must match address in Block Transfer dialog.
Length of the data being transferred. Must match
length in Block Transfer dialog.
Operating mode of the transfer.
Communications Overview
4–13
Helpful Hints for Block Transfers
• Read and write blocks can use the same addresses.
• Read and Write Blocks may overlap partially or completely.
• Improve response times by compacting the data into the fewest
possible blocks (no unused bits) or keep all data for a screen in a
single block. Remote I/O scanners generally perform one block
transfer in a single I/O scan.
• Ladder logic can use the PanelView’s current screen tag (status
tag) to enable block transfers as necessary. The screen data is
automatically updated when an operator selects the screen. See
Chapter 20 for a description of the status tags.
• Minimize the number of block transfers.
Block Transfer Read Example
The following example illustrates a block transfer read. The
PanelView terminal is assigned to rack #3, starting module group 0.
One of the PanelView objects, a numeric entry display addressed as
N7:2, writes to a part of the data block being transferred.
➀ The operator enters the data into the numeric
entry display.
123
➁ Using information in the Block Transfer dialog,
the PanelView determines the position of the
data and the block size.
Numeric Entry Cursor Point with
Tag Name = Motor_Speed
Tag Address = N7:2
➂ The PanelView terminal places the data in the
first word of a 4 word block.
Word 1
Word 2
Word 3
Word 4
123
➄ The value entered on the PanelView is now
stored at N7: 2 = 123.
➃ The PLC reads the 4 word block of data and
stores it at the Data File address.
BTR
BLOCK TRANSFER READ
Rack
Group
Module
Control Block
Data File
Length
Continuous
(EN)
03
0
0
N36:0
N7:2
4
N
Read From
PanelView
Data To PLC
Publication 2711-6.0
4–14
Communications Overview
Block Transfer Write Example
The following example illustrates a block transfer write. The
PanelView terminal is assigned to rack #3, starting module group 0.
One of the PanelView objects, a bar graph display addressed as N7:0,
reads a portion of the data block being transferred.
➀ The PLC receives and stores data from an
input device, in this example a flow sensor.
➁ The PLC ladder logic program initiates a
block transfer of a data block (10 words)
containing the screen display data.
Flow Rate
Transducer
BTW
BLOCK TRANSFER WRITE
Rack
Group
Module
Control Block
Data File
Length
Continuous
N7:5
Tag Name = Flow Rate
03
0
0
N16:1
N7:0
10
N
➂ The PanelView terminal receives the data and
determines the starting address for the write
operation by matching the block size with the
address entered in the Block Transfer dialog.
N7:0
W
10
➃ The PanelView now carries a copy of that
segment of the logic controllers data table.
10 WORDS
➄ The PanelView updates the bar graph display
using the data from the controller.
Bar Graph Object with
Tag Name ’Flow Rate’ = Address N7:5
Publication 2711-6.0
N7:0
N7:1
N7:2
N7:3
N7:4
N7:5
N7:6
N7:7
N7:8
N7:9
Flow Rate Data
(EN)
Data
From
PLC
Communications Overview
4–15
Transferring Multiple Blocks
Multiple block transfers use a single channel (single Module Control
and Status Bytes defined). Each block transfer read or write must be
a unique length since the PanelView terminal uses the block size to
determine the starting location of the read or write. The following
example illustrates a block transfer write of two blocks.
➀ The PLC ladder logic program initiates multiple block
transfers of 2 data blocks (7 words and 60 words).
BTW
BLOCK TRANSFER WRITE
Rack
Group
Module
Control Block
Data File
Length
Continuous
BTW
BLOCK TRANSFER WRITE
Rack
Group
Module
Control Block
Data File
Length
Continuous
03
0
0
N16:1
N7:0
7
N
(EN)
➁ The PanelView terminal receives the first data block and
Data From
PLC
determines the starting address N7:0 for the write
operation by matching the block size with the address
entered in the Block Transfer dialog.
The PanelView handles the second block in the same
manner.
03
0
0
N16:6
N90:10
60
N
(EN)
N7:0
N90:10
W
W
7
60
Data From
PLC
➂ The PanelView carries a copy of the logic
controller data tables N7:0 to N7:6.
N7:0
N7:1
N7:2
N7:3
N7:4
N7:5
N7:6
N7:7
N7:8
N7:9
➃ The PanelView carries a copy of the logic
controller data tables N90:10 to N90:69.
Block 1 Transfer
N90:8
N90:9
N90:10
N90:11
N90:12
...
N90:67
N90:68
N90:69
N90:70
N90:71
Block 2 Transfer
➄ The PanelView screen objects are updated
using the new data.
Publication 2711-6.0
4–16
Communications Overview
Remote I/O Communication Loss
When communication fails on a Remote I/O network:
• Object states are maintained and the message “No PLC
Communication” is displayed on the terminal screen.
• If Block Transfers are defined for the application, but no BTR or
BTW instructions are received, another message is displayed
when the Block Transfer Timeout occurs.
These messages continue to display until communications is
established. If a write operation is attempted to the logic program
controlling the PanelView objects, the terminal will display the
message “Error: Write to Logic Controller failed.
If a PanelView object is activated during a communication loss, the
object retains its new state and sends this state value to the controller
when communications is established.
Publication 2711-6.0
PanelBuilder Basics
Chapter Objectives
This chapter covers basics on using PanelBuilder Software.
Section
Windows Environment
Page
Windows Environment
5–1
PanelBuilder Windows
5–2
Menus
5–4
Tool Bar
5–5
Status Bar
5–5
Format Bar
5–6
Toolboxes
5–7
Keypad Display
5–7
Color Palette
5–8
Dialog Boxes
5–9
Spreadsheet Editors
5–10
PanelBuilder Defaults
5–13
Getting Help
5–14
PanelBuilder runs in the Microsoft Windows environment. You
should be familiar with window operations. That is, you should
know how to use the mouse, choose menu commands, and work with
windows and dialogs.
If you use a mouse, here are the basic terms used:
Term
Means
Click
Position the mouse pointer on the object, area or field, then
press and release the left mouse button once.
Double-click
Position the mouse pointer on the object, area, or field and
then click the left mouse button twice quickly.
Select item or command
Click to highlight the item to be affected by the next
command, or click on a dialog box option.
Choose item or command
Click on a tool, menu command or an item in a dialog box or
Help window.
Drag
Click where to start a selection and hold down the left
mouse button. Move pointer to end of selection and release
the mouse button. Use drag to highlight a text string.
If you prefer to use the keyboard:
Term
Means
Choose menu command
Press the ALT key and type the underlined letter in the
menu name . Then type the letter underlined in the
command name.
Select item or command
Use the arrow keys (or in a dialog, both the TAB and arrow
keys) to move to the item.
Choose item or command
Highlight an item, then press the ENTER key.
Publication 2711-6.0
5–2
PanelBuilder Basics
PanelBuilder Windows
Each time you start PanelBuilder, a PanelBuilder window opens.
This is where you create an application. Window elements are
described below.
Control-Menu
Title Bar
Maximize Button
Minimize Button
Close Button
Menu Bar
Tool Bar
Format Bar *
Command
Border
⇐⇒ Resizes
Window
Mouse Pointer
Status Bar
Publication 2711-6.0
Feature
How to use it
Menu Bar
Click a name on the menu bar to open a menu and display its
commands.
Or press ALT-X, where X is the underlined letter in the menu name.
Command
Click a command to choose it or carry out its action.
Or type the underlined letter in the command name.
Title Bar
Drag to move a window.
Tool Bar
Click a tool to carry out a frequently used command. The tool bar
toggles on and off from the View menu.
*Format Bar
Click a tool to format an object or text. The format bar doesn’t
appear until you open an application.
Status Bar
Shows what PanelBuilder is doing at the moment. The status bar
toggles on and off from the View menu.
Control-Menu
Click to open the Control menu. Double-click to close a window.
Minimize button
Click to reduce window to an icon.
Maximize button
Click to enlarge a window.
Close button
Closes the window.
Border
Drag to change the size of a window.
Mouse pointer
Use to select an item or object.
PanelBuilder Basics
5–3
Application File Window
When you open an application, the application file window opens
listing all screens in the application by number and name.
Close Button
Maximize Button
Minimize Button
Title Bar
Control-menu
Border
Application File Window
⇐⇒
Resizes
Window
Application Screen Window
Each application screen looks like the PanelView terminal (touch,
keypad, or keypad and touch) for which you are creating the
application. Objects are placed inside the display area. On keypad
terminals, you can also place objects on function keys. Screens are
moved and sized like any other window. Multiple screens can be
open at one time.
Title Bar
Display Area
Application Screen
Publication 2711-6.0
5–4
PanelBuilder Basics
Menus
The menu bar dynamically updates when application files and
application screens are opened. Each name on the menu bar is a
menu with its own set of commands.
To open a menu:
• Point to a name on the menu bar and click the left mouse button.
(To move directly to a menu command, drag the pointer down the
menu until the command is highlighted, then release the mouse.)
• Or press ALT and then press the underlined letter in the menu
name. For example, to open the File menu, press ALT+F.
To choose a menu command:
• Click the command name.
• Or type the underlined letter in the command name.
• Or use the UP and DOWN ARROW keys to select an item; then
press ENTER.
Menu conventions are listed below.
Menu convention
What it means
Dimmed command name
The command is unavailable.
An ellipsis (...) after the name
Opens a dialog box that contains
options you need to select before
PanelBuilder can carry out the command.
A check mark (n) next to the name
The command is a toggle that is activated
(turned on). A toggle command alternately
turns on or off each time you select it. When
turned off, the check mark is removed.
A key combination after the name
A shortcut for the command. You can use the
key combination to choose the command.
A triangle (") at the right side a
of a menu command
Opens another menu of choices.
To close a menu:
• Click the menu name or anywhere outside the menu.
• Or press ALT or F10 to cancel and move back to the workspace.
• Or press ESC to cancel the menu but remain on the menu bar.
Publication 2711-6.0
PanelBuilder Basics
Tool Bar
5–5
The tool bar appears at the top of the PanelBuilder window and
provides tools for frequently used menu commands. You click a tool
to carry out an action. Some tools complete the action immediately;
others place you in a mode to complete the action.
To toggle the tool bar on or off:
Choose Tool Bar from the View menu.
A check mark (n) appears next to the Tool Bar command when it’s
active. To turn the tool bar off, choose the command again.
Status Bar
The status bar appears at the bottom of the PanelBuilder window and
indicates what PanelBuilder is doing at the moment. When placing
and selecting objects, the right element of the status bar shows the
object type.
To toggle the status bar on or off:
Choose Status Bar from the View menu.
A check mark (n) appears next to the Status Bar command when it’s
active. To turn the status bar off, choose the command again.
Publication 2711-6.0
5–6
PanelBuilder Basics
Format Bar
The format bar appears near the top of the PanelBuilder window and
provides easy access to commonly used formatting commands.
Format tools change the appearance of objects and text.
Most format tools toggle on and off. Click the tool once to turn it
on, click it again to turn it off. The same settings are accessed from
the Format menu.
The format bar has different views depending on what mode you’re
in. Each view is shown below.
Format Bar in Object Mode
Format Bar in Inner Text Mode
Format Bar in Inner Graphic Mode
Publication 2711-6.0
PanelBuilder Basics
Toolboxes
5–7
PanelBuilder provides toolboxes, in addition to menu commands, to
create screen objects. The main toolbox contains controls, displays,
list keys and graphics. The ISA Symbols toolbox contains standard
ISA symbols. Appendix B describes each tool. To choose an object,
click the appropriate tool in the toolbox.
The toolboxes can be moved like any other window.
To toggle a toolbox on or off:
Choose Toolbox or ISA Symbols from the View menu.
A check mark (n) appears next to the command when the toolbox is
active. To close a toolbox, choose the appropriate command again.
Keypad Display
You can view application screens with or without the numeric
keypad.
To toggle the keypad on or off:
Choose Keypad from the View menu.
A check mark (✓) appears next to the command when the keypad is
active. Select the command again to turn off the keypad.
Publication 2711-6.0
5–8
PanelBuilder Basics
Color Palette
Applications developed for color and grayscale terminals use a color
palette to define the colors of objects and text. For color terminals,
the palette supports 16 standard EGA colors. For grayscale
terminals, the palette supports 4 colors (shades of gray).
To toggle the color palette on or off:
Choose Color Palette from the View menu.
A check mark (n) next to the command means the palette is active.
To turn the palette off, choose the command again.
The palette moves like other windows. Click the right mouse button
in the palette to switch between a vertical or horizontal format.
Palette for Color Terminals
Selected Foreground Color
View Box updates as Foreground
and Background colors are selected
Selected Background Color
Palette for Grayscale Terminals
Use the palette to set the foreground and background colors of
objects, text and graphics. On color terminals, the default
background color is blue and the foreground color is white. On
grayscale terminals, default background color is black and the
foreground color is white.
Foreground colors are located on the top row of the palette,
background colors on the bottom row. To select a color, just click on
a cell. A box around the cell indicates the selected color.
The view box on the left of the palette updates as you change the
foreground and background colors.
Foreground colors are used for:
• all text (text, background text, list text)
• lines
• borders of shapes (rectangle, circle, ellipse)
• borders of control objects
• list cursor
• fill pattern
Publication 2711-6.0
PanelBuilder Basics
5–9
Background colors are used for:
• area containing text string
• solid fill area of objects (buttons and lists)
You can also set foreground/background colors for monochrome
bitmaps.
Dialog Boxes
The default screen background is black but can be changed using the
Attributes command on the Screen menu.
PanelBuilder uses dialog boxes to request information it needs to
carry out a command. After supplying the requested information,
click a command button to carry out the command.
Some dialog boxes provide sets of options, each on a separate tab.
You click on a tab to work with a specific set of options.
Dialog boxes also display additional information and warnings, or
explain why a requested task could not be accomplished.
An ellipses (...) after a menu command means a dialog box will open
when you choose that command. Below is a sample dialog.
Closes
dialog
Tab
Drop-down List Box
Check Box
Option Buttons
Command Buttons
Exits dialog without saving changes
Saves all changes and exits dialog
To move around a dialog box:
• Move mouse pointer to field and click the left mouse button.
• Or press TAB to move forward through fields and SHIFT+TAB to
move backward through fields.
• Or press the ALT key and the underlined letter of a field name.
For example, to move to the Terminal Name field, press ALT+T.
Publication 2711-6.0
5–10
PanelBuilder Basics
Spreadsheet Editor
PanelBuilder uses a spreadsheet editor to:
• edit states of multistate and list objects
• view and edit all text in the application
• edit alarms and triggers
The conventions of using the spreadsheet are the same regardless of
what PanelBuilder operation you are performing.
Each row defines data for one state of a multistate or list object, one
alarm, one trigger or one text string in the application. Each cell
represents one field of data in a row.
Some cells require you to:
• enter text
• select an option from a drop-down list
• click a box to toggle an option on (✕) or off
Column
Row
Drag to shrink
row height or column width
Each spreadsheet has a
popup menu to perform
operations.
↕
Cell or Field
Cursor
Scroll
Bars
Selecting Rows, Cells, or Columns
To select a cell:
Click on the cell, or press TAB or the arrow keys.
A gray border around the cell indicates the cell is selected.
To select a block of cells:
1. Select a cell in one corner of the block you want to select.
2. Hold down the left mouse button and drag the mouse until the
desired selection is highlighted.
Or hold down the SHIFT key and use the arrow keys to highlight
the block.
Publication 2711-6.0
PanelBuilder Basics
5–11
To select a single row:
Click on the row number at the left edge of the worksheet.
The row is highlighted, indicating it is selected.
To select more than one row:
1. Click on the row number of the first row you want to select, hold
down the left mouse button and drag the mouse to the last row
you want to include in the selection.
2. Release the mouse button.
Selected rows are highlighted.
To select a single column:
Click on the column header at the top of the spreadsheet.
The column is highlighted, indicating that it is selected.
To select more than one column:
1. Click on the column header of the first column you want to select,
hold down the left mouse button and drag the mouse to the last
column you want to include in the selection.
2. Release the mouse button.
Selected columns are highlighted.
To select the entire spreadsheet:
Click the empty box in the upper left corner of the spreadsheet.
Changing Column Width and Row Height
The spreadsheet opens with default column and row settings. While
working in the spreadsheet, you can shrink or stretch the width of the
columns and the height of the rows.
To change the width of a column:
1. Place the cursor on the line dividing the columns.
↕
The cursor changes to a double arrow
2. Hold the left mouse button down and drag the cursor to stretch or
shrink the column width.
You can hide a column by shrinking it until it disappears. To
show the column, stretch it.
Publication 2711-6.0
5–12
PanelBuilder Basics
To change the height of all rows:
1. Place the cursor on the line dividing the rows.
The cursor changes to a double arrow ↕
2. Hold the left mouse button down and drag the cursor to stretch or
shrink the height of all rows.
You can hide all rows by shrinking them until they disappear. To
show the rows, stretch them.
Changing Order of Columns
To change the order of columns:
1. Select the column you want to move.
2. Hold down the SHIFT key and drag the column to a new location.
Columns are reordered.
The column order is maintained when you exit the spreadsheet.
Cutting or Copying and Pasting Selections
To copy or cut and paste cells, rows or columns:
1. Select the area you want to copy.
2. Hold down the right mouse button and choose Cut (Ctrl+X) or
Copy (Ctrl+C) from the popup menu.
The data is placed on the clipboard, replacing the clipboard’s
previous contents.
3. Select the area in which you want to paste the contents of the
clipboard, or click on a single cell.
4. Click the right mouse button and choose Paste (Ctrl+V) from the
popup menu.
The contents of the clipboard are pasted into the selected area.
Or, if you selected a single cell, the contents are pasted into the
area starting with the cell.
Publication 2711-6.0
Cells, rows and columns can be copied/cut/pasted to and from Excel
using commands (or keys) on the popup menu.
PanelBuilder Basics
5–13
Adding, Inserting and Deleting Rows
Regardless of what operation you are performing, rows are added,
inserted and deleted in the same way. Select a row and choose the
appropriate command from the spreadsheet popup menu.
To add a new row:
Click the right mouse button and choose Append from the menu.
A new row is added after the last row. The row is created with
defaults from the last row.
To insert a row:
1. Click the row number below where you want to insert a new row.
2. Click the right mouse button and choose Insert from the popup
menu.
A new row is inserted above the selected row.
To delete a row:
1. Click the row number you want to delete.
2. Click the right mouse button and choose Delete from the menu.
The row is permanently deleted.
PanelBuilder Defaults
When you exit PanelBuilder, it remembers if the window bars and
toolboxes are on or off and shows them in that same condition the
next time you start PanelBuilder.
Publication 2711-6.0
5–14
PanelBuilder Basics
Getting Help
Help for PanelBuilder is available by choosing a command from the
Help menu or pressing the F1 key. The following help window opens
when you choose Index from the Help menu.
Help feature
How to use it
Contents button
Choose to see a list of topics.
Search button
Choose to search for topics by keywords.
Back button
Choose to view the previous topic. Continue to choose the button
to step back through all the topics.
>>
Choose to display the next topic in a series of topics.
<<
Choose to display the previous topic in a series of topics.
When Calling for Technical Assistance
When calling Rockwell International Technical Services for
assistance, you’ll need to provide the release date and version
number of the PanelBuilder software and the AB Utilities software.
This information is available by choosing About PanelBuilder from
the Help menu. Below is an example of what the dialog looks like.
XX.XX.XX
XX.XX.XX.XX
XXX XX XXXX
Jane Brown
Publication 2711-6.0
Working with Applications and
Screens
Chapter Objectives
This chapter contains the following sections:
Section
Page
Helpful Hints
6–1
Starting PanelBuilder
6–2
Creating a New Application
6–3
Opening an Existing Application
6–5
Renaming and Describing an Application
6–8
Opening a New Screen
6–10
Opening an Existing Screen
6–11
Opening Multiple Screens
6–12
Closing Screens
6–14
Changing Screen Attributes
6–14
Deleting Screens
6–15
Copying Screens within an Application
6–15
Copying Screens to Another Application
6–16
Moving Screens to Another Application
6–17
Saving an Application
6–20
Closing an Application
6–21
Exiting PanelBuilder
6–21
Helpful Hints
• PanelBuilder applications use these file types:
– .PBA – PanelBuilder application
– .BAK – Backup of PanelBuilder application
– .PVA – Translated .PBA file that is downloaded to terminal
• To make a copy of a PanelBuilder application, copy the .PBA file
to a new file name.
• To save the previous version of an application each time you
close it, place the following line in the [Files] section of the
C:\WINDOWS\PB550.INI file:
BackupPBAFiles=1
The application is saved with the same file name and the .BAK
file type.
Publication 2711-6.0
6–2
Working with Applications and Screens
Starting PanelBuilder
PanelBuilder opens like any other Windows application.
To start PanelBuilder:
• For computer running Windows 3.x:
– At the DOS prompt, type win and press ENTER.
– Double-click the PanelBuilder group icon in the Program
Manager. Or use the Run command in the File menu of the
Program Manager or File Manager.
– Double-click the PanelBuilder icon.
900
• For computers running Windows 95:
– Click the Start button.
– Click on Programs. You will see the Programs submenu.
– Click PanelBuilder to open the PanelBuilder submenu.
– Click the PanelBuilder icon.
The startup screen opens showing copyright and release information.
xx.xx.xx
xxx xx xxxx
xxxx–xxxx
The PanelBuilder window opens ready for you to open a new or
existing application file.
Publication 2711-6.0
Working with Applications and Screens
Creating a
New Application
6–3
A PanelBuilder application is a set of screens with associated tags
and devices (terminal and controller). When creating an application,
you define:
• application name
• project name containing tag and device information
• terminal in which the application will run
To create and open a new application file:
1. Click the New File tool on the tool bar
Or choose New from the File menu.
Dimmed until you enter a valid
project name.
Opens a dialog to
enter a description
of the application.
Selected terminal type
Selected catalog
number of terminal
Communication ports and
protocols of selected terminal
2. In the Application Name box, enter a 1 to 32 character name for
the application.
When saving the application, PanelBuilder uses the first 8
characters of the application name as the default file name (with
the .PBA file type).
3. In the Project Name box, enter a 1 to 32 character name for the
project. The name can’t start with a number or contain spaces.
The Project Name list box contains the names of all existing
projects. Select one of these if the new application will use the
same tag definitions and devices as another application.
The Project Name links the application with a database of tag
definitions and device (terminal and controller) information.
Publication 2711-6.0
6–4
Working with Applications and Screens
4. In the Terminal Name box, enter a 1 to 32 character name for the
terminal. This name identifies the terminal to the project.
If the selected project contains existing terminal devices, you can
select the name of a terminal from the Terminal Name box.
To copy, rename or delete devices from a project, see page 21–4.
5. Under Terminal Type Information, define the PanelView terminal
in which the application will run, by selecting:
– Terminal option from the PV Type box
– Keypad, Touch, or Keypad & Touch (PV550/PV600 only)
– Catalog number and firmware version installed in the terminal
from the Catalog and Version list. The list is filtered based on
the previous two selections.
The Ports area displays the physical ports and protocols of the
selected terminal.
If you selected an existing terminal from the Terminal Name box, the
dialog displays the defined terminal information.
6. Click the OK button.
The application file window opens showing the name of the
application and the selected terminal. Because the file does not
contain any screens the Screens box is empty.
Application Name
You are ready to create a new application screen. See page 6–10.
Publication 2711-6.0
Working with Applications and Screens
Opening an
Existing Application
6–5
To open an existing application file:
The bottom of the file menu lists the 4 most recently opened
applications. To reopen one of these files, choose a file.
1. Click the Open File tool on the tool bar.
Or choose Open from the File menu.
The File Name list box shows all PanelBuilder application (.pba)
at the current location.
• To locate a file on another drive, select the drive name in the
Drives list box.
• To locate a file in another folder, select a folder from the
Folders list. Scroll through the filenames until you find the
one you’re looking for.
2. From the File Name list box, select the file you want to open and
click the OK button.
Or double-click on the file name.
3. A dialog opens to verify a one-to-one correspondence between
tags/devices in the application and tags/devices in the project.
You can perform the verification without displaying this dialog.
For details on how to hide the dialog, see the next page.
The dialog displays the name of the first application tag in the
project.
Publication 2711-6.0
6–6
Working with Applications and Screens
Respond as follows:
Click:
To:
Yes
Replace the project tag with the application tag. Select Yes, if
you know that a specific tag has been modified and you want to
update the project database.
No
Ignore the application tag. Do not replace the tag in the project
database with the application tag.
Replace All
Replace all project tags with the application tags.
Replace None
Ignore all application tags. Do not replace any tags in the
project.
Cancel Open
Cancel the open.
After processing the tags, the dialog opens again to verify a
one-to-one correspondence between the devices in the application
and the devices in the project.
4. When the application is loaded, the application file window opens
with a list of screens (by number and name) in the file.
Open a screen in the application file window as described on
page 6–11 or open a new screen as described on page 6–10.
Publication 2711-6.0
Working with Applications and Screens
6–7
Setting Preferences for Opening Applications
You can control the behavior of PanelBuilder when opening an
application. Choose Preferences from the Application menu.
Shows information
about this dialog
Show Project Database Restore Dialog
Select this check box to display the Project Database Restore dialog
each time you an open an application. This dialog prompts you to:
• replace duplicate tags and devices in the project database with
those in the application.
• add application tags and devices to the project database if they are
missing.
This is the default option. To add missing tags and replace duplicate
tags in the project database without showing the Project Database
dialog, disable this check box and select the other two boxes.
Always Add Missing Tags & Devices
Select this check box and disable the first check box to add missing
tags and devices to the project data database without opening the
Project Database dialog. This option is equivalent to clicking the
Add All button on the Project Database dialog.
Always Replace Duplicate Tags & Devices
Select this check box and disable the first check box to replace
duplicate tags and devices in the project database without opening
the Project Database dialog. This option is equivalent to clicking the
Replace All button on the Project Database dialog.
Important:
If you disable all check boxes, the verification process
will not occur and you may lose tag or device data.
Publication 2711-6.0
6–8
Working with Applications and Screens
Renaming and Describing
an Application
Use the Description command on the Application menu to:
• Rename an application
• Enter an application description which you can include in a report
• View the version number and last save date of an application
To open the Application Description dialog:
• Choose Description from the Application menu.
• Or click the Description button from the New Application dialog.
If entering a description from the New Application dialog, the
Application Name and Project Name do not appear.
Appears in Title Bar
of Application File Window
Project Associated with Application
Insertion Point
I-Beam Pointer
When the Application was Saved
Version Number Increments with Each Save
To change the application name:
1. Click in the Application Name box to rename the application.
Drag pointer over text to highlight it, then type a new name.
2. Click OK to close dialog.
The new application name appears in the Application File Window
and the title bar of the PanelBuilder workspace.
Publication 2711-6.0
Working with Applications and Screens
Important:
6–9
The description is downloaded to the terminal with the
application which means it uses terminal memory.
To enter or edit an application description:
1. Enter a description in the Description box. The text automatically
wraps.
To change the location of the insertion point in the Description
box, move the I-beam pointer or use the arrow keys. When using
the scroll bar, the insertion point remains where it is until you
move it.
– To start a new line, press CTRL+ENTER.
– To delete text, drag pointer over text to highlight it, then
press BACKSPACE or DELETE.
– To replace text, drag pointer over text to highlight it, then
type the new text.
– To add text, position cursor where you want to insert text and
then type the new text.
Use any of the standard Window editing functions to edit text.
2. When done, click the OK button.
Publication 2711-6.0
6–10
Working with Applications and Screens
Opening a New Screen
To create a new screen in the application:
1. Click the New Screen tool on the tool bar or choose New from
the Screen menu.
Appears only for Color and
Grayscale Terminals
PanelBuilder assigns a default number starting with 1 and a
default name to each screen (Screen 1, Screen 2, Screen 3,...).
The maximum number of screens in a file is 255. The actual
number allowed depends on available memory in the terminal.
2. Accept the name or enter a unique name (up to 32 characters) in
the Name box. Use descriptive names to identify screens.
3. Accept the number, representing the screen’s position in the
application file window, or enter a number in the Number box.
4. In the Background box, select the screen background color. The
default is black. This field applies only to color and grayscale
terminals.
5. Click the OK button.
A blank PanelView screen opens showing the screen number and
name in the title bar.
An * after the application file name in the title bar means the
application has been modified but not saved.
Project Name
Application File Name after Save
Screen Number and Name
You are ready to create screen objects. The next chapter provides an
overview on working with screen objects.
Publication 2711-6.0
Working with Applications and Screens
Opening an
Existing Screen
6–11
To open an existing screen in the application:
• Double-click a screen name in the application file window.
• Or select a screen from the application file window and click the
Open Screen tool on the tool bar.
• Or select a screen from the application file window and choose
Open from the Screen menu.
The screen opens with its name and number in the title bar.
Project Name
Application File Name
Screen Number/Name
Publication 2711-6.0
6–12
Working with Applications and Screens
Opening
Multiple Screens
Multiple screens can be open in the workspace. You might want to
copy or move objects from one screen to another or you might need
to access information on another screen.
Each screen opened overlaps the previous screen and PanelBuilder
adds the screen name to the Windows menu. The last opened screen
becomes the active screen. A check mark (✓) appears next to the
active screen. The title bar of the active screen is also highlighted.
To open multiple screens in an application:
1. Click the first screen you want to select in the application file
window, then drag the pointer to the last screen.
To cancel the selection, click any screen in the list.
Or click the first screen, press and hold down the SHIFT key, and
click the last screen you want to select.
To cancel the selection, release the SHIFT key and click on any
screen.
2. Click the Open Screen tool on the tool bar.
Or Choose Open from the Screen menu.
The selected screens open.
Important:
Publication 2711-6.0
Too many open screens may result in a Windows
resource or low memory message, and slow screen
updates. Close the application file and any open
Windows programs. Open the screens one at a time.
Working with Applications and Screens
6–13
Activating a Screen
When multiple screens are open only one screen is active and that is
the screen with the highlighted title bar.
To activate a screen:
• Choose a screen from the lower portion of the Windows menu.
• Or click anywhere inside the screen.
A check mark (✓) appears next to a screen name when it is active
and the title bar is highlighted.
Arranging Open Screens
Overlap screens diagonally across the workspace with the title bar of
each screen visible, or line them as horizontal or vertical tiles.
Cascade
Tile Horizontally
Tile Vertically
To arrange open screens:
Choose Cascade, Tile Horizontally or Tile Vertically from the
Window menu.
Reducing Screens to Icons
You can reduce an application file and screens to icons leaving more
space in the workspace but still making them available.
To reduce an open file or screen to an icon:
Click the Minimize button on the window.
Minimize
Button
The application file and screens reduce to icons as shown below.
To reopen a file or screen,
double-click the icon.
To evenly space icons across the bottom of the workspace, choose
Arrange Icons from the Window menu.
Publication 2711-6.0
6–14
Working with Applications and Screens
Closing Screens
When you are finished with an application screen, close it. Screens
are automatically saved when you save the application.
To close an application screen:
• Choose Close from the Screen menu.
• Or double-click the control-menu box on the screen.
The screen closes leaving you in the PanelBuilder workspace.
To close all open application screens:
Choose Close All from the Window menu.
Changing
Screen Attributes
Use the Attributes command on the Screen menu to:
• rename a screen
• renumber a screen
• change the background color of the screen (color terminals only)
To change the attributes of a screen:
1. From the application file window, select a screen to rename.
Or activate an open screen.
2. Choose Attributes from the Screen menu.
Appears only for
Grayscale and Color Terminal
3. In the Name box, type a new screen name (32 characters
maximum).
4. Accept the number in the Number box or enter a new one.
5. In the Background box, select another color for the screen
background. The current color is shown.
6. Click the OK button.
The new screen name and number will appear in the title bar of
the screen and in the application file window.
Publication 2711-6.0
Working with Applications and Screens
Deleting Screens
6–15
Use the Delete Screen command to remove screens from an
application file without placing them on the clipboard.
To delete screens:
1. From the application file window, select the screens to delete.
2. Choose Delete Screen from the Edit menu.
The screens are removed from the Application File window.
Numbers of deleted screens are used when new screens are created.
Copying Screens
within an Application
This section shows how to copy screens within an application using
the Copy and Paste commands on the Edit menu.
To copy a screen within an application:
1. Select the screen you want to copy from the application file
window.
2. Click the Copy tool on the tool bar or Choose Copy Screen from
the Edit menu.
PanelBuilder copies the screen to the clipboard.
3. Click the Paste tool on the tool bar or choose Paste Screen from
the Edit menu.
4. PanelBuilder pastes the screen into the application file window at
the lowest available screen number.
In the following example, screen 2 – Feed Pump is copied to screen
5 with the same screen name.
Use the Attributes command on the Screen menu to change the name
of the copied screen.
Publication 2711-6.0
6–16
Working with Applications and Screens
Copying Screens to
Another Application
This section shows how to copy screens from one application to
another using the Copy and Paste commands on the Edit menu.
Only one application can be open in the workspace but you can run
multiple sessions of PanelBuilder.
See page 6–18 for details on what to do when copying or moving a
screen to an application that was created for a different type of
terminal.
To copy screens from one application to another:
1. Select the screens you want to copy from the application file
window.
2. Click the Copy tool on the tool bar or Choose Copy Screen from
the Edit menu.
PanelBuilder copies the screens to the clipboard.
3. Save the application file (if necessary).
4. Close the application file.
Or start another session of PanelBuilder.
5. Open the application file to receive the screen.
6. Click the Paste tool on the tool bar or choose Paste Screen from
the Edit menu.
7. PanelBuilder pastes the screen into the application file window
of the target application with the same name and number.
If the screen number exists in the target application, the screen is
assigned the next available number.
In the following example, the Feed Pump screen is copied from the
Sample application file to the Test application file.
Publication 2711-6.0
Working with Applications and Screens
Moving Screens to
Another Application
6–17
This section shows how to move screens from one application to
another using the Cut and Paste commands on the Edit menu. Only
one application can be open in the workspace but you can run
multiple sessions of PanelBuilder.
See page 6–18 for details on what to do when copying or moving a
screen to an application that was created for a different type of
terminal.
To move screens from one application to another:
1. Select the screens to move from the application file window.
2. Click the Cut tool on the tool bar or choose Cut Screen from the
Edit menu.
PanelBuilder removes the screen from the file and puts it
on the clipboard.
3. Save the application file (if necessary).
4. Close the application file.
Or start another session of PanelBuilder.
5. Open the application file to receive the screen.
6. Click the Paste tool on the tool bar or choose Paste Screen from
the Edit menu.
7. PanelBuilder pastes the screen into the application file window
of the target application with the same name and number.
If the screen number exists in the target application, the screen is
assigned the next available number.
In the example below, the Feed Pump screen is moved from the
Sample to the Test application using the lowest available number.
Test
Publication 2711-6.0
6–18
Working with Applications and Screens
Converting Copied Screens
Converting from Touch Screen to Keypad
If copying or moving a screen from a touch screen to a keypad
application, you must assign function key input to screen objects.
Converting to another Terminal Type
If copying or moving a screen to an application created for a
different terminal type (for example, 900 to 550), you may need to
resize or adjust the location of objects on the pasted screen.
Converting to another Communication Protocol
If copying or moving a screen to an application that uses a different
communication protocol (for example, Remote I/O to DH-485), you
must update the terminal setup and tags appropriately.
Converting Monochrome to Color or Grayscale
If copying or moving a screen from a monochrome application to a
color or grayscale application, the following dialog opens.
You are asked to supply the following colors:
• background color of screen (default is black)
• foreground color of objects (default is white)
• background color of objects (default is black)
Select the colors you want and click OK. The screen is pasted into
the color or grayscale application using the selected colors.
Publication 2711-6.0
Working with Applications and Screens
6–19
Converting Color to Monochrome
If copying or moving a screen from a color application to a
monochrome application, all colors are removed from the screen.
• screen background is converted to white
• brighter colors are converted to white
• darker colors are converted to black
• color bitmaps are converted to monochrome bitmaps
Also, text sizes are converted to the closest matching font in the new
application. You may want to resize the text.
Converting Color to Grayscale
If copying or moving a screen from a color application to a grayscale
application, all colors are removed from the screen.
• colors are converted to the closest shade of gray
• color bitmaps are converted to grayscale bitmaps
Also, text sizes are converted to the closest matching font in the new
application. You may want to resize the text.
Publication 2711-6.0
6–20
Working with Applications and Screens
Saving an Application
The File menu provides two commands for saving an application.
• Use the Save command to save the application to the default
drive and folder overwriting the previous version.
• Use the Save As command to save a revised application with a
new name so the previous version is not overwritten.
The first time an application is saved, the Save As dialog opens so
the file can be named.
To save an existing application file:
• Click the Save File tool on the tool bar.
• Or choose Save from the File menu.
PanelBuilder replaces the previous version of the application on disk
with the new version. A backup file is also created
To save a new or existing application with a new name:
1. Choose Save As from the File menu.
The first time you save the application, the default file name is the
the first 8 characters of the application name.
2. In the File Name box, accept the default or enter another 1 to 8
character name. PanelBuilder automatically adds the .PBA file
type to the name.
Note: You can save the file with another file type. Do not use
.PVA which is the translated file that runs in the terminal.
To save the file to another location, select a folder. To select
another drive, click a drive name in the Drives box.
3. Click the OK button.
The name under which you save the application becomes the default
for the next save operation (Save or Save As command). A backup
file is also created with the same file name and the .BAK file type.
PanelBuilder tracks the date/time and version of an application when
it is saved. This information is available by choosing Description
from the Application menu.
Publication 2711-6.0
Working with Applications and Screens
Closing an Application
6–21
The Close command on the File menu closes the application file but
leaves you in the PanelBuilder workspace.
To close an application file:
• Choose Close from the File menu.
• Or double-click the control-menu box on the application file
window.
If you’ve made changes to the application since the last save,
PanelBuilder gives you the option of saving the file before closing it.
Exiting PanelBuilder
The Exit command on the File menu quits PanelBuilder and returns
you to the Windows desktop. All opened applications are closed.
To quit PanelBuilder:
• Choose Exit from the File menu.
• Or double-click the control-menu box on the application file
window.
If any applications are open and unmodified, they are closed
automatically.
If you’ve made changes to the application since the last save,
PanelBuilder gives you the option of saving the file before closing it.
Publication 2711-6.0
Working with Objects
Chapter Objectives
This chapter contains the following sections:
Section
Page
Accessing Objects
7–2
Draw Pointer
7–3
Creating Objects in Display Area
7–4
Aligning Objects
7–5
Creating Objects on Function Keys
7–7
Selecting Objects
7–8
Sizing Objects
7–9
Moving Objects
7–9
Grouping and Ungrouping Objects
7–10
Stacking Objects
7–11
Zooming In and Out
7–11
Object Inner Text
7–12
Formatting Objects
7–13
Setting Default Colors for Objects
7–13
Editing Object Attributes
7–14
Configuring States of Multistate or List Objects
7–15
Entering a Description for an Object
7–18
Hiding the View of an Object
7–19
Copying/Cutting and Pasting Objects
7–20
Deleting Objects
7–22
Reversing an Operation
7–22
Publication 2711-6.0
7–2
Working with Objects
Accessing Objects
All objects (controls, displays, graphics, ISA symbols) are accessed
from the Objects menu or a toolbox.
The toolboxes toggle on and off from the View menu.
Controls, Displays, List Keys
Graphics
Selection
Tool
Momentary
Push Button
Maintained
Push Button
Latched
Push Button
Multistate
Push Button
Go To Screen
Button
Numeric
Cusor Point
Keypad
Enable Button
Control List
Selector
Multistate
Indicator
List
Indicator
Message
Display
Global
Object
Move
Up
Move
Down
Page
Up
Page
Down
Backspace
Enter
Line
Connected
Line
Rectangle
Screen List
Selector
Ellipse
Freeform
Text
Numeric
Data Display
Scale
Import
Graphics
Graphic
Image
Home
Bar
Graph
End
Return Screen
Button
Selection
Tool
Horizontal Valve
with Actuator
Publication 2711-6.0
Horizontal Valve
Horizontal Valve
Throttling
Manual Actuator
Actuator
Vertical Valve
with Actuator
Vertical Valve
Throttling
Actuator
Vertical Valve
Manual Actuator
Butterfly
Valve
Check
Valve
Relief
Valve
Liquid
Filter
Vacuum
Filter
Electrical
Motor
Electrical
Transformer
Vessel
Reactor
Storage Bin
Distillation
Tower
Pressure
Storage Vessel
Weigh
Hopper
Pump
Turbine
Blower
Compressor
Agitator
Conveyor
Screw
Conveyor
Inline
Mixer
Rotary
Feeder
Exchanger
Rotary Kiln
Cyclone
Separator
Left
Arrowhead
Up
Arrowhead
Right
Arrowhead
Down
Arrowhead
Furnace
Working with Objects
Draw Pointer
7–3
You can place objects in the display area of the application screen or
on a function key, depending on the terminal type.
When selecting an object and moving the mouse into either of these
areas, the mouse pointer changes to a crosshair (+). The crosshair
indicates where an object appears when you place it and also aids in
positioning and aligning the object.
The pointer changes back to
after exiting the object mode.
If moved to an illegal area of the screen, the crosshair changes to
Display Area
Draw Pointer
Publication 2711-6.0
.
7–4
Working with Objects
Creating Objects
in Display Area
Objects are created in the display area using the same technique.
To create an object in the display area:
1. Choose an object from the Objects menu.
Or click the appropriate tool in the toolbox.
2. Position the pointer (+) where you want to place the object.
3. Click the left mouse button to place the default size.
Or hold down the left mouse button and drag the pointer to size
the object. Release the mouse when the object is the right size.
The object is automatically selected.
Object
Drag Pointer
to Size Object
4. To place another object of the same type, move the pointer to a
new location and repeat step 3.
5. Click the right mouse button to exit the object mode.
Or click the selection tool in the toolbox.
Or press the ESC key.
For each object placed on the screen, the status bar shows:
• Object ID number (assigned by PanelBuilder)
• X and Y coordinates of upper left corner of object (in pixels).
Coordinates are referenced from upper left corner of display
(x=0, y=0).
• Width and height of object (in pixels)
• Object type (right element of status bar)
Publication 2711-6.0
Working with Objects
Aligning Objects
7–5
Two grids are available for sizing and aligning objects:
• Touch grid (available only on touch screen terminals)
• Screen grid
Touch Grid
Touch screen terminals use a touch grid to align control objects (push
button controls, screen buttons, keypad enable button) with the touch
cells. Push button objects are moved and sized in increments of
touch cells. The default push button occupies 4 (2 x 2) touch cells
but can be sized differently.
The touch grid is present in every screen but isn’t visible unless
turned on.
The touch grid does not control the placement of graphics or display
objects; they can be placed anywhere on the screen. Use the screen
grid to align graphics and displays.
To show the touch grid:
Choose Touch Grid from the Align menu.
A check mark (n) appears next to Touch Grid when it’s active.
Choosing Touch Grid again hides the grid.
On PanelView 900/1000/1400 Touch Screen terminals, the touch
grid has 384 (24 x 16) touch cells. On PanelView 550/600 Touch
Screen & Keypad terminals, the touch grid has 128 (16 x 8) touch
cells.
Touch Cell Grid Point
Default Push Button Size
Publication 2711-6.0
7–6
Working with Objects
Screen Grid
Keypad terminals use a screen grid to size and position objects. You
can turn the grid on or off and size the grid in increments of pixels.
The Snap to Grid feature forces each object to the nearest
intersection of the grid.
On touch screen terminals, use the screen grid to position graphics
and displays. Control objects are aligned using the touch grid.
To show the grid:
Choose Grid from the Align menu. The grid displays with the
current grid attributes.
A check mark (n) appears next to Grid when it’s active. Choose
Grid again to hide the grid.
To snap objects to the grid:
Choose Snap to Grid from the Align menu.
A check mark (n) appears next to the command when it’s active.
Choose Snap to Grid again to turn the feature off.
To resize the grid:
1. Choose Grid Attributes from the Align menu.
The Grid Spacing dialog box opens showing the current grid size
in pixels on the X and Y-axis.
•
•
•
•
Default grid for PV550 terminal is 8 x 8.
Default grid for PV600 terminal is 10 x 29.
Default grid for PV900 monochrome terminal is 13 x 25.
Default grid for PV900/PV1000 color and grayscale terminals
is 13 x 30.
• Default grid for PV1400 color terminal is 33 x 37.
2. To increase or decrease the spacing of the grid lines on the
X-axis, click the up or down arrow next to the X box.
Or type a number in the box. A value of 13 creates horizontal
grid lines every 13 pixels.
3. To increase or decrease the spacing of the grid on the Y-axis,
click the up or down arrow next to the Y box.
Or type a number in the box. A value of 25 creates vertical grid
lines every 25 pixels.
4. Click the OK button.
Publication 2711-6.0
Working with Objects
Creating Objects
on Function Keys
7–7
If screen space is limited, you can place button objects on function
keys. You can relegend the function keys using the Function Key
Legend Kit available for your terminal.
The following objects can be placed on a function key:
• Push button controls (momentary, maintained, latched, multistate)
• Screen selector buttons (Go To and Return)
• Keypad enable button
• Alarm buttons, Alarm History and Print History buttons
• List keys
To create an object on a function key:
1. Choose an object from the Objects menu.
Or click the appropriate tool in the toolbox.
2. Position the pointer (+) over a function key and click the left
mouse button.
If the function key is already assigned to an object, the pointer
changes to . Reposition pointer over another key.
Pointer over Function Key
A graphic appears on the function key showing the object type.
An asterisk also appears next to the key number.
*F1
Asterisk
Graphic
3. Click the right mouse button to exit the object mode.
Or click the selection tool in the toolbox.
Publication 2711-6.0
7–8
Working with Objects
Selecting Objects
Before you can move, size or format an object you must first select
the object. A selected object has handles.
To select an object:
Position the mouse pointer anywhere on the object and press the left
mouse button. Handles appear on the object.
A line has one handle at each end. Rectangles and squares have
handles around their edges. Other objects (ellipses and circles) have
handles around an invisible bounding box.
To deselect an object:
• Position pointer outside the object and press the left mouse
button.
• Or select another object.
To select multiple objects:
1. Position pointer above and to the left of the objects you want to
group.
2. Press the left mouse button and drag a selection rectangle around
the objects.
Selection Rectangle
3. Release the mouse button.
The other way to select multiple objects is to hold down the SHIFT
key and click on each object. To add or remove an object from the
selection, hold down the SHIFT key and click on the object.
To select all objects:
Choose Select All from the Edit menu.
Handles appear on all objects to show that they’re all selected.
Publication 2711-6.0
Working with Objects
Sizing Objects
7–9
To size an object:
1. Select the object by clicking anywhere on the object.
Handles appear on the object.
Handle
2. Position the pointer over one of the handles.
The pointer changes to show the direction you can size the object.
Size Diagonally
Size Horizontally
Size Vertically
3. Press the left mouse button and drag the handle.
The object stretches from the anchor point to the position of the
pointer, expanding and contracting as you move the mouse.
The anchor point is the handle opposite the handle you choose. It
does not move when objects are sized.
4. Release the mouse button when the object is the right size.
Objects with inner graphics can’t be sized smaller than the graphic.
You might have to move or delete the inner graphic to size the object
appropriately.
Moving Objects
To move an object:
1. Move the pointer anywhere inside the object.
2. Hold down the left mouse button and drag the object to its new
location. The pointer changes to show that you are moving the
object. An outline appears as you drag the object.
Old Location
New Location
3. Release the mouse button.
Publication 2711-6.0
7–10
Working with Objects
Grouping and
Ungrouping Objects
You can group objects so they can be moved or edited as a single
unit. When moving objects in a group, they maintain their positions
relative to each other. Grouped objects remain together until
ungrouped.
A global object can consist of grouped objects. For example, you
can group a bar graph, scale and tick-mark labels, and then define the
group as a global object by double-clicking the group. This opens
the Options dialog which lets you create a global object.
To group a set of objects:
1. Select the objects you want to group.
Handles appear on all objects that are selected.
2. Click the Group tool on the tool bar.
Or choose Group from the Edit menu.
An outline appears around the objects that are grouped.
Selecting any one of the objects selects the entire group. When a
group is selected you can move, cut/copy/paste or delete objects in a
single operation. You can also size a selected object while
maintaining its group status.
To ungroup a set of grouped objects:
1. Select the group.
2. Click the Ungroup tool on the tool bar.
Or choose Ungroup from the Edit menu.
The objects are now separate again. Deselect the group before
selecting an individual object.
PanelBuilder remembers the last assembled group. To reassemble a
former group of objects choose Regroup from the Edit menu.
Publication 2711-6.0
Working with Objects
Stacking Objects
7–11
You can change the stacking order of objects that overlap. You can
stack objects on top of each other and then change the order in which
they appear.
ÇÇÇÇ ÇÇÇ
ÇÇÇÇ ÇÇÇ
ÇÇÇÇ ÇÇÇ
Bring to Front
Original Stack
ÇÇÇÇ
ÇÇÇÇ
ÇÇÇÇ
ÇÇÇÇ
Send to Back
To bring an object to the front of the object stack:
1. Select the object.
2. Click the Bring to Front tool on the format bar.
Or choose Bring To Front from the Edit menu.
To send an object to the back of the object stack:
1. Select the object.
2. Click the Send to Back tool on the format bar.
Or choose Send To Back from the Edit menu.
Use the Bring Dynamic Objects To Front command to move all
objects that interact with a controller address in front of other objects
on the screen.
Zooming In and Out
You can increase or decrease the view of the screen so that objects
look larger or smaller than their actual size. Changing the view
affects only the appearance of objects, not their actual size.
To zoom in or enlarge the view of the screen:
• Click the Zoom In tool on the tool bar.
• Or choose Zoom In from the View menu.
You can increase the view several times. If starting from Full Size,
the view increases each time you click Zoom In.
To zoom out or reduce the view of the screen:
• Click the Zoom Out tool on the tool bar.
• Or choose Zoom Out from the View menu.
You can decrease the view several times. If starting from Full Size,
the view decreases each time you click Zoom Out.
To return the screen to its normal size, choose Full Size from the
View menu.
Publication 2711-6.0
7–12
Working with Objects
Object Inner Text
Most objects, when created, have default inner text. The text varies
depending on the object type.
Inner text can be edited and can include a time, date or numeric
variable. In addition, you can replace the text with an inner graphic
or include a graphic with the text.
Object
Inner Text
Push Buttons
Notes
Inner text for 2-state push buttons is ST 0 (State 0) and ST 1 (State 1).
For multistate push buttons, the text can increment to ST 15 (State 15).
For multistate indicators, the text can increment from ST 0 (State 0) to ST
1999 (State 1999).
Multistate Indicator
List Indicator
Inner text for list indicators can increment from ST 0 (State 0) to ST 254
(State 254).
Control List Selector
Standard
Piloted
Inner text for control list selectors can increment from ST 0 (State 0) to
ST 254 (State 254). The asterisk * means the text exceeds the size of
the object. Resize object.
Numeric Entry Objects
Numeric Data Display
Inner text for numeric entry and display objects is a numeric variable
placeholder (######). You can add text before or after the variable.
ASCII Entry Object
Inner text for an ASCII entry objects is a variable placeholder (#). You can
add text before or after the variable.
Message Display
Inner text for message displays can increment from MSG 0 (Message 0)
to MSG 1999 (Message 1999).
Goto Screen Button
Inner text is GoTo.
Goto Config Screen Button
Inner text is Goto Config Screen. The asterisk * means the text exceeds
the size of the object. Resize object.
Return Button
Inner text is Return.
Screen List Selector
Inner text for screen list selectors can increment from ST 0 (State 0) to
ST 254 (State 254). The asterisk * means the text exceeds the object
size. Resize object.
Print Alarm Button
Inner text is Print.
Clear Alarm Button
Clear
Acknowledge Alarm Button
Acknowledge All Button
Inner text is Clear.
Inner text is Ack.
Ack
Inner text is Ack All.
All
Clear Alarm List Button
Print Alarm List Button
Publication 2711-6.0
Clear Alarm
List
Print Alarm
List
Inner text is Clear Alarm List.
Inner text is Print Alarm List.
Working with Objects
Formatting Objects
7–13
In addition to adding inner text and graphics to objects, you can
apply different formatting options to objects and text including color.
For objects, you can:
• change shape
• change border
• change fill pattern
• toggle blinking on/off
• change foreground/background colors
• toggle foreground/background colors
For text, you can:
• change text size
• change text alignment (left, right, center)
• toggle blinking on/off
• change foreground/background colors
• toggle foreground/background colors
Formatting options are applied to objects and states from the:
• Format menu or Format bar (see Chapter 17).
• State tab of object’s dialog (see page 7–15).
Setting Default Colors
for Objects
On color and grayscale terminals, you can apply color defaults to
objects of the same type. For example, you might want all push
buttons in the application to use the same colors. Create one push
button, edit it, and then use the Set Object Color Defaults command.
All new push buttons will be created with the default colors.
1. Create the object that you want to use as the default for others.
2. Edit the object. Change the line or border, colors and size. If the
object has several states, configure the different states. You
cannot add text as the default.
3. Select the object and choose Set Object Color Defaults from the
Edit menu.
Every new object of this type that you create will appear like the one
just created.
Or if you want to apply defaults using an object that already exists,
select the object and choose the Set Object Color Defaults command.
Color defaults are maintained across applications and across sessions
of PanelBuilder.
Publication 2711-6.0
7–14
Working with Objects
Editing Object Attributes
Each object (except for graphics) has attributes that define its
operation. View or edit the attributes by opening the object’s dialog.
To view or edit the attributes of an object:
• Double-click the object.
• Or select object and click the Object Attributes tool.
• Or select object and choose Object Attributes from the Edit menu.
The dialog that opens has 2 or 3 tabs depending on whether the
object is a multistate or list object.
Use this tab:
To:
Properties
Configure the operating parameters of an object.
States
Configure the states of a multistate object or list object. Does not
appear for other objects.
Options
Enter a description for the object, flag the object for global selection,
or hide the view of the object.
Opens
Tag Dialog
Each object dialog has the same command buttons. Objects that do
not interact with the controller will not have the Edit Tag button.
Publication 2711-6.0
Press:
To:
OK
Save changes and exit the dialog.
Cancel
Exit the dialog without saving any changes.
Edit Tag
Open dialog to view or enter attributes for a data tag.
Working with Objects
Configuring States of
Multistate or List Objects
7–15
States are configured for multistate and list objects from the States
tab of the object’s dialog.
When you click the States tab in an object’s dialog, a spreadsheet
opens. Each object state is entered as a separate row in the
spreadsheet. The fields or cells in each row configure text for each
state and other visual attributes.
• to select a row, click the row number.
• to select a column, click the column header.
• to select a cell, click on the cell, or press TAB or arrow keys.
Row
Most state operations are performed
by clicking a row number and then
choosing a command from this menu.
Cell or Field
The fields that appear in each row depend on whether the object is a
multistate object or a list object.
The multistate objects are:
• 2-state and multistate push buttons
• multistate indicator
• message display
The list objects are:
• control list selector
• screen list selector
• list indicator
Publication 2711-6.0
7–16
Working with Objects
The table below shows the fields that appear for multistate and list
objects. When you open the States tab, the fields are arranged in
order of importance. Fields that require editing will appear first.
Optional fields appear later.
Fields that are unique to a specific object are discussed in the chapter
describing the object.
Multistate
Objects
List
Objects
Use this Field:➀
To:
Object
Fill
Select a fill pattern (from a list) for the state. The Fill field does not appear for
objects that are not rectangular.
✓
Blink
Toggle blinking on or off for the state. Click the box to turn blinking on or off.
An ✕ in the box indicates the blink option is active. The default is off.
✓
Object Foreground
Select a foreground color (from a list) for the object state. The default is white.
✓
Object Background
Select a background color (from a list) for the state. The default is blue.
✓
Select a graphic to appear for the state. The list of graphics includes ISA
symbols and imported bitmaps. Chapter 17 shows how to position a graphic.
✓
Graphic Foreground
Select a foreground color for the inserted graphic. The default is white.
✓
Graphic Background
Select a background color for the inserted graphic. The default is blue.
✓
Text ID
Unique number assigned to text string. The number is automatically generated
when a new state is created.
✓
✓
Text
Define the inner text string for the object state. Default text appears for each
state (ST 0, ST 1, ST 2). You can insert a time, date or numeric variable in the
text string.
✓
✓
Text Size
Select the size of the text string. The default size depends on the terminal
type. For list objects, the selection applies to all states in the list.
✓
✓
✓
✓
✓
✓
✓
✓
Graphic
Toggle blinking on or off for the text string. Click the box to turn blinking on or
off. The default is off. An ✕ in the box indicates the blink option is active.
Toggle underlining on or off for the text string. Click the box to turn underlining
on or off. The default is off. An ✕ in the box indicates underlining is active.
Text Blink
Underline
Select whether the text will align left, right, or center in the object. For list
objects, the selection applies to the entire list. The default is left.
Align Text
Toggle word wrap on or off for the text string. Click the box to turn word wrap
on or off. The default is on. An ✕ in the box indicates word wrap is active.
Word Wrap
With word wrap on, text wraps at the end a word rather than breaking in the
middle.
✓
Text Foreground
Select a foreground color (from a list) for the inner text. For list objects, the
selection applies to the entire list. The default is white.
✓
Text Background
Select a background color (from a list) for the area containing the text string.
The default is blue.
✓
✓
➀ Cells that are unique to an object do not appear in this list.
ÎÎÎÎ
ÎÎÎÎ
ÎÎÎÎ
Graphic
Foreground Color
Foreground Color
RESET
Background Color
Publication 2711-6.0
Fill
Graphic
Background Color
Text
Foreground Color
ÏÏÏÏ
ÏÏÏÏ
Fill
Text
Foreground Color
Off
STOP
Text
Background Color
Low
Align Text Left
Medium
High
Working with Objects
7–17
State Operations
Operations you can perform on states are accessed from a popup
menu. To open the menu, hold down the right mouse button or type
CTRL+M.
Select:
To:
Cut
Cut the selected state to the clipboard.
Copy
Copy the selected state to the clipboard.
Paste
Paste the previously cut or copied row from the
clipboard.
Insert and Paste
Paste the copied or cut state above the current row.
Append State
Add a new state after the last state. The new state
is created with the defaults from state 0.
Insert State
Insert a state above the current row.
Delete State
Permanently remove the selected state.
Move State Up
Moves the selected state up one row.
Move State Down
Move the selected state down one row.
Open a submenu for inserting a time, date, numeric
or ASCII variable in the Text field.
A placeholder is inserted in the text for the variable.
/*T*/
Time placeholder
/*D*/
Date placeholder
/*A:12 */
ASCII placeholder
/*V:12 NOFILL FIX:0*/ Numeric placeholder
Embedded Variable
The time and date are formatted according to
settings in the Terminal Setup dialog.
A dialog opens when Variable or ASCII is selected,
allowing you to format the variable. The placeholder
is updated with the specified format (/*V:6 NOFILL
FIX:0*/ or /*A8 */).
To edit a numeric or ASCII variable, select the
placeholder and choose Edit Variable from the
Embedded Variable menu.
Use Existing Text
Open the Use Existing Text dialog (in read only
mode) allowing you to use a message that already
exists in the application. See Chapter 18 for details.
New Text ID
Change the message number associated with the
text for the current row to the next available number.
Publication 2711-6.0
7–18
Working with Objects
Entering a Description
for an Object
You can enter a description for an object from the Options tab of the
Object’s dialog. Descriptions can be entered for all objects except
graphics. The description appears in the application report.
To enter a description for an object:
1. Click the Options tab from the dialog of the selected object.
Insertion Point
I-Beam Pointer
The insertion point appears at the beginning of the Description
box. You can move the insertion point by moving the I-beam
pointer or using the arrow keys. When using the scroll bar, the
insertion point remains where it is until you move it.
2. Enter text in the Description box. The text automatically wraps.
To start a new line, press CTRL+ENTER.
Use standard Window editing and cursor functions to edit text.
3. When done, click the OK button.
Publication 2711-6.0
Working with Objects
Hiding an Object
7–19
You can hide the view of an object to reduce the number of objects
on a screen. Only input objects assigned to a function key or touch
cell can have the view turned off. These objects are:
• Push button controls
• Screen selector buttons
• Keypad enable button
When the view is off, the object isn’t displayed. However, the
object’s function key or touch cell is still active.
!
ATTENTION: When turning off the view of a touch
cell object, you must place a graphic on that area of the
screen. Otherwise, an operator could inadvertently
touch that screen area and activate the function.
To hide the view of an object:
1. Click the Options tab from the dialog of the selected object.
2. Click the Turn Object View On box to show the object view.
When the view shows, the box contains an X. To hide the view,
clear the check box.
3. When done, click OK to exit the dialog.
Publication 2711-6.0
7–20
Working with Objects
Copying/Cutting
and Pasting Objects
Use the Copy/Cut and Paste commands on the Edit menu to:
• copy an object on the screen
• copy/cut an object to another screen
• copy/cut an object to another application
An object retains all attributes during copy and cut operations unless
the target application was created for a different terminal type. See
page 7–21.
Global objects cannot be copied/cut and pasted. To use an object
globally, you must use the Global Objects command (Chapter 14).
To copy an object on the screen:
1. Select the object you want to copy.
2. Click the Copy tool or choose Copy from the Edit menu.
PanelBuilder copies the object to the clipboard.
3. Click the Paste tool or choose Paste from the Edit menu.
An outline of the object appears.
4. Move the outline to a new location and click the left mouse
button to paste the object.
To change the attributes of the pasted object, double-click the object.
To copy or cut an object from one screen to another:
1. Select the object you want to copy or cut.
2. Click the Copy or Cut tool from the tool bar.
Or choose Copy or Cut from the Edit menu.
PanelBuilder copies/cuts the object to the clipboard.
3. Open the screen to receive the object.
If already open, activate the screen by selecting the screen name
from the Window menu.
4. Click the Paste tool or choose Paste from the Edit menu.
An outline of the object appears.
5. Move the outline to a new location and click the left mouse
button to paste the object.
To change the attributes of the pasted object, double-click the object.
Publication 2711-6.0
Working with Objects
7–21
To copy or cut an object from one application to another:
1. Select the object you want to copy or cut.
2. Click the Copy or Cut tool from the tool bar.
Or choose Copy or Cut from the Edit menu.
PanelBuilder copies/cuts the object to the clipboard.
3. Close the application screen.
4. Save the application file (if necessary).
5. Close the application file.
Or start another session of PanelBuilder.
6. Open the application file to receive the object.
7. Open the screen on which you want to paste the object.
8. Click the Paste tool or choose Paste from the Edit menu.
An outline of the object appears.
9. Move the outline to a new location and click the left mouse
button to paste the object.
To change the attributes of the pasted object, double-click the object.
When Copying/Cutting Objects to a Different Application Type
When copying or moving objects to an application that was created
for a different terminal type, you will need to update the pasted
objects appropriately.
Monochrome to Color or Grayscale Application
When copying/moving objects from a monochrome to a color or
grayscale application, a dialog opens asking you to select:
• foreground color for the pasted objects (default is white)
• background color for the pasted objects (default is black)
Color to Monochrome Application
When copying or moving an object from a color to a monochrome
application, objects are pasted as follows:
• brighter colors of objects are converted to white
• darker colors of objects are converted to black
• color bitmaps are converted to monochrome bitmaps
Publication 2711-6.0
7–22
Working with Objects
Color to Grayscale Application
When copying or moving an object from a color to a grayscale
application, objects are pasted as follows:
• colors of objects are converted to the closest shade of gray
• color bitmaps are converted to grayscale bitmaps
Touch Screen to Keypad Application
When copying/moving objects from a touch screen to a keypad
application, you must assign function keys to the pasted objects.
Different Communication Protocol
When copying/moving objects to an application that uses a different
communication protocol, you must update the tags appropriately for
the pasted objects.
Deleting Objects
Use the Delete command to remove objects from an application
screen without placing them on the clipboard.
To delete objects from a screen:
1. Select the objects you want to delete.
2. Choose Delete from the Edit menu.
To delete all objects from a screen:
1. Choose Select All from the Edit menu.
2. Choose Delete from the Edit menu.
To delete an object from a function key:
1. Select the function key.
2. Choose Delete from the Edit menu.
PanelBuilder deletes the object and graphic from the function key.
Reversing an Operation
PanelBuilder lets you cancel the previous editing operation. If an
operation cannot be canceled, PanelBuilder lets you know. You
cannot cancel the previous screen operation if the screen is closed.
To cancel the previous editing operation:
• Click the Undo tool on the tool bar.
• Or choose Undo from the Edit menu.
The Edit menu shows the name of the operation that will be undone.
For example, lets say you delete an object and then want to cancel
the delete. When you open the Edit menu, choose Undo Cut/Delete.
Publication 2711-6.0
Creating Push Buttons
Chapter Objectives
This chapter shows how to create push button controls. It contains
the following sections:
Section
Helpful Hints
Page
Helpful Hints
8–1
Push Button Types
8–2
Contact Types
8–2
Push Button Text and Graphics
8–3
Creating Push Buttons
8–4
Setting Properties of a Push Button
8–4
Configuring Push Button States
8–8
When creating push button controls, consider:
• On touch screen terminals, each push button aligns with a default
of 4 (2h x 2w) touch cells.
• Use a global object if the same button will appear on one or more
screens. The PanelView terminal only stores one copy of a global
button regardless of the number of links to it.
• Multistate push buttons support 16 states (numbered 0 to 15).
Use only the number of states required.
• Push buttons can have unique inner text and/or a graphic for each
state as well as other formatting options.
• Configure push button states from the States tab on the Push
Buttons dialog or using the procedures described in Chapter 17.
!
ATTENTION: Some combinations of format options
could result in a control object not being visible (object
blends into screen background). All touch screen
controls must be visible or have a graphic which shows
the location of the object. Failure to do so may result
in accidental or unpredictable operation.
Publication 2711-6.0
8–2
Creating Push Buttons
Push Button Types
Push buttons can function like mechanical push buttons. A logic
value of 0 represents open contacts and a logic value of 1 represents
closed contacts. Push buttons can also have a numeric value for
pressed, released or multiple states. The terminal sends the value to
the controller for each change of state.
Each push button state can have unique visual characteristics such as
inner text or graphic, fill pattern and line type.
Momentary Push Buttons change state (close or open contacts)
when pressed and return to their initial (0) state when released.
Maintained Push Buttons change state (close or open contacts)
when pressed and remain in this state when released. Pressing and
releasing the push button a second time returns the button to its
selected initial state. Maintained push buttons retain their state
following screen changes. The state of a maintained push button
after a power-up is determined by the powerup option selected in the
Terminal Setup dialog.
Latched Push Buttons change state (close or open contacts) when
pressed and remain in this state when released. The button does not
return to its initial (0) state until unlatched by a handshake bit or
value in the controller. The latched status is not maintained after a
power-up but is retained following a screen change.
Multistate Push Buttons have between 2 and 16 states. Each state
sets a bit or value at a controller address. Every time the push button
is pressed and released, it changes to the next state. After the last
state, the push button returns to its selected initial state. Multistate
push buttons retain their current state following screen changes. The
state after a powerup is determined by the powerup option selected
in the Terminal Setup dialog.
State 0
OFF
OFF
Contact Types
Publication 2711-6.0
State 1
Button Pressed
LOW
State 2
Button Pressed
MEDIUM
State 3
Button Pressed
HIGH
Momentary, maintained and latched push buttons can have either
normally open or normally closed contacts. You also assign
normally open or normally closed contacts to a multistate push
button with two states.
• Normally Open Contacts have a logic value of 0 as the initial
push button state. Pressing the button changes the value to 1.
• Normally Closed Contacts have a logic value of 1 as the initial
push button state. Pressing the button changes the value to 0.
Creating Push Buttons
Push Button
Text and Graphics
8–3
Push buttons can have inner text and/or an inner graphic. Both
appear inside the push button and can change with each state. The
inner text or graphic is attached to the button. When you move or
delete the button, the inner text or graphic is also moved or deleted.
Push buttons are created with ST 0 as the default inner text. For
example, the default inner text for on/off push buttons is ST 0 and
ST 1. For multistate push buttons, the default inner text increments
from ST 0 to ST 15.
ST 0
Default Inner Text
ON
Inner Text
Inner Graphic
Inner text can also include a date, time or numeric variable.
Push buttons can have a variety of visual appearances. In addition to
text and graphics, you can format the button using options such as:
• Fill pattern
• Border type
• Toggle foreground/background colors
• Blinking
• Shape
You can format each push button state directly from the States tab of
the object’s dialog or using the formatting procedures in Chapter 17.
Possible combinations are shown below.
ÏÏÏÏ
ÏÏÏÏ
ÏÏÏÏ
Inner Graphic
Fill Pattern
ÎÎÎÎ
ÎÎÎÎ
ÎÎÎÎ
Inner Graphic
Toggle Foreground/Background
MANUAL
Inner Text
Circular Button
STOP
Inner Text
Fill Pattern
RESET
Inner Text
No Border
White Fill Pattern
MANUAL
Inner Text
Circular Button
Toggle Foreground/Background
Publication 2711-6.0
8–4
Creating Push Buttons
Creating Push Buttons
All push buttons look the same when placed on a screen. On touch
screen terminals, push buttons align with the touch grid even when
it’s not visible.
To create a push button:
1. Choose a push button from the Objects Push Buttons submenu.
Or click the appropriate tool in the toolbox.
2. Position the pointer (+) and click the left mouse button to place
the default button size. Or drag the pointer to size the button.
Momentary Maintained
Latched
Multistate
3. To place another button of the same type, move the pointer to a
new location and click again.
4. Click the right mouse button to exit push button mode.
Or click the selection tool on the toolbox.
Setting Properties
of a Push Button
To set properties of a push button:
1. Double-click the push button object.
Depending on the push button type, some options are dimmed.
Opens
Tag Dialog
2. On the Properties tab, set the operating parameters of the button.
The descriptions that follow define properties of momentary,
maintained and latched push buttons.
Publication 2711-6.0
Creating Push Buttons
8–5
Type
Changes the push button type without having to create a new object.
Write
Specifies the type of data to send to controller: Single Bit or Value.
• For Single Bit, the terminal writes to a bit address.
• For Value, the terminal writes to a word address.
Select the format of the data from the Data Format list box. The
data type of the write tag must be compatible with the selected
format for the application to validate.
Use this Format
With this Tag Data Type
Signed Integer
Signed Integer
4-BCD
4BCD
Binary
Hexadecimal
Octal
Unsigned Integer
Unsigned
ns ned Integer
Inte er
or Bit Array
Contacts
If Single Bit was selected in the Write area, select Normally Open or
Normally Closed contacts for the 2-state push button. Momentary
and latched push buttons have a default initial state of 0.
Select
To
Normally Open
Send value of 0 when push button is in state 0
and value of 1 when push button is in state 1.
Normally Closed
Send value of 1 when push button is in state 0
and value of 0 when push button is state 1.
The Contacts area is dimmed if Value was selected in the Write area.
Initial State
Specifies the initial state of a maintained or multistate push button
and the initial value sent to the write tag address. The value of the
initial state overrides the initial value in the Tag Editor.
Hold Time
Specifies the length of time a momentary push button remains in the
next state after being released. The hold time should exceed the scan
time of the controller to insure that each state change is read by the
controller at least once. Hold time values are: 0, 50, 250, 500, 750 or
1000 milliseconds. The default is 500.
Publication 2711-6.0
8–6
Creating Push Buttons
Write Tag
Specifies the name of the tag address to write the single bit or value.
Edit the tag definition using the Edit Tag button or the Tag Editor.
Indicator Tag
Specifies the name of a tag address that controls when the push
button changes appearance with each state. Each state can have
unique visual characteristics (inner text, inner graphic, fill). Edit the
tag definition using the Edit Tag button or the Tag Editor.
This Option
Means
No Indicator Tag (default)
Push button changes to next state when pressed.
Indicator Tag
same as Write Tag
Push button changes state after bit or value is written
to the Write Tag address.
Indicator Tag
different from Write Tag
Push button changes state after:
• bit or value is written to the Write Tag address and
• state value is read from Indicator Tag address.
Same Write Tag
& Indicator Tag
➀
Different Write Tag
& Indicator Tag
➀
INITIAL
STATE
INITIAL
STATE
No Indicator Tag
➀
➁
INITIAL
STATE
ÎÎÎ
ÎÎÎ
ÎÎÎ
ÎÎÎÎ
ÎÎÎÎ
ÎÎÎÎ
➂
➁
NEXT
STATE
NEXT
STATE
Step Description
Step
Description
Step
➀
➁
➀
➁
Button pressed
➀
➁
Button pressed
Button changes to
next state
Important:
Bit or value written
to Write Tag address
Button changes to
next state based on value
read from Write Tag address
ÎÎÎ
ÎÎÎ
ÎÎÎ
➃
NEXT
STATE
➂
Publication 2711-6.0
➁➂
➂
➃
Description
Button pressed
Bit or value written
to Write Tag address
Bit or value written
to Indicator Tag address
Button changes to
next state based on value
read from Indicator Tag
address
If the indicator tag and write tag are different, the
indicator state is controlled by the controller program
regardless of the push button state. For example, the
indicator tag address may specify that push button state
1 is displayed while the write tag address is at state 0.
Creating Push Buttons
8–7
Handshake Tag (Required for Latched Push Button)
Specifies the name of a tag address that unlatches a latched push
button. The button is unlatched when the value at the handshake tag
address is set to a non zero value by your controller program. Edit
the tag definition using the Edit Tag button or the Tag Editor.
Button Initial State
OFF
Handshake Bit = 0
Data Bit = 0
Controller Program Sets
Handshake Bit to 1
Button Pressed
Button Released
ON
ON
OFF
Handshake Bit = 0
Data Bit = 1
Handshake Bit = 1
Data Bit = 0
Handshake Bit = 0
Data Bit = 1
Controller Program Sets
Handshake Bit to 0
The handshake tag applies only to latched push buttons, not other
push buttons.
Input
Specifies whether the operator presses a function key or a touch cell
to operate the push button.
• For a keypad terminal, select a function key from the list box.
• For a touch screen terminal, touch cell is automatically enabled.
PanelView 550/600 Keypad & Touch Screen terminals support
function key and touch cell input.
The selected function key displays a graphic of the push button and
an asterisk next to the key number, indicating the key is used.
*F1
Asterisk
Push Button Graphic
Publication 2711-6.0
8–8
Creating Push Buttons
Configuring
Push Button States
Use the States tab to:
• edit text for each state
• enter a value for each state (if required)
• insert a graphic for each state
• edit format options for each state
• add or delete states for a multistate push button
To configure the states of a push button:
1. Click the States tab on the Push Buttons dialog.
A spreadsheet opens for state editing. Each row represents a push
button state (row 0 represents state 0, row 1 represents state 1).
– For 2-state push buttons, 2 rows appear (states 0 and 1)
– For a multistate push button, 4 rows appear (states 0 – 3)
Each row has fields which define the visual characteristics of
each state.
2. Edit the fields as necessary.
3. Click OK to exit the Push Buttons dialog.
The Value field appears only if
Value was selected in the Write
area of the Properties tab.
Publication 2711-6.0
For a description of all the fields for a state, see page 7–15.
Creating Push Buttons
8–9
Editing Number of States for a Multistate Push Button
A multistate push button supports a maximum of 16 states. Use only
the number of states required.
To add states to a multistate push button:
1. Hold down the right mouse button and choose Append State from
the popup menu.
A new row is added after the last row with the next available state
number.
2. Repeat step 1 for each state you want to add.
Each state you add is created with the defaults from State 0 and
default text (ST 0, ST 1, ..., ST 15).
To delete states from a multistate push button, select a row number
and choose Delete State from the popup menu.
Editing State Text
The Text field contains the text that will appear for each state. The
default text is the state number (ST 0). Double-click in the cell and
edit the text.
On/Off Type
Push Button
Multistate
Push Button
State 0 Text
ON
OFF
LOW
State 0 Text
State 1 Text
OFF
OFF
NORMAL
State 1 Text
HIGH
State 2 Text
Other text fields control how the text is formatted for each state.
Publication 2711-6.0
8–10
Creating Push Buttons
Entering State Values
If Value was selected in the Write area of the Properties tab, the
Value field appears for each state.
The Value field specifies a numeric value to send to the write tag
address for each push button state. The default value for each state is
the state number (0 to 15).
The value you enter must be within the range of the Data Format
selected on the Properties tab.
Data Format
Range
Binary➀
0000 0000 0000 0000 to
1111 1111 1111 1111
Unsigned Integer
0 to 65535
Signed Integer
-32768 to +32767
4-BCD
0 to 9999
Hexadecimal➀
0 to FFFF
Octal➀
0 to 177777
➀ Formats provided for data entry. The terminal does not display or
transfer these formats.
The value is converted when a different data format is selected.
Publication 2711-6.0
Creating Control List Selectors
Chapter Objectives
This chapter describes how to create list type controls. It contains
the following sections:
Section
Page
Helpful Hints
9–1
Standard Control Lists
9–2
Piloted Control Lists
9–2
Control List Options
9–4
Creating a Control List Selector
9–5
Setting Properties of a Control List Selector
9–6
Configuring States of a Control List Selector
9–10
Creating List Keys
9–12
Control list selectors can perform some of the same functions as push
buttons, including set value and on/off controls.
Helpful Hints
When creating list type controls, consider:
• Configure entries for a control list from the States tab of the
Control List Selector dialog or using the procedures described in
Chapter 17.
• A control list selector supports a maximum of 255 states
(numbered 0 to 254). Use only the number of states required.
• Each state in a control list is limited to one line of text.
• Changing the text size applies to the entire list.
• On color and grayscale terminals each item can have a different
color, but the background color is the same for the entire list.
• On keypad terminals, the operator moves the cursor through a
control list using the terminal’s up
and down
arrow
keys. The selection is sent to the controller immediately or when
the Enter
key is pressed on the terminal.
• Touch screen only terminals require list keys on the screen,
enabling the operator to move the cursor through the control list.
List keys are similar to the arrow keys on keypad terminals.
• A screen can contain multiple control lists. On standard control
lists, the operator selects a list by pressing a function key or touch
cell (touch screen terminals). Another way to activate a list is to
press the left or right arrow keys on the terminal until the list is
selected.
Publication 2711-6.0
9–2
Creating Control List Selectors
Standard Control Lists
On Standard control lists, the operator moves a cursor to select an
item. On keypad terminals, the up
and down
arrow keys
are used to move the selection cursor. The currently selected item is
highlighted. The selection is sent to the controller immediately or
when Enter
key is pressed on the terminal.
➁ Terminal writes item value to controller.
➀ Operator selects
control list item.
On touch screen only terminals, you must place list keys on the
screen, enabling the operator to move the selection cursor through
the list. The Move Up and Move Down list keys look similar to the
up and down arrow keys on keypad terminals.
Piloted Control Lists
Piloted control lists can be controlled by the logic controller. To
select a control list item, the logic controller sets the control tag
value to 1 and writes the value of the item to a search tag address.
The PanelView terminal reads the search tag data and then highlights
the corresponding item on the control list. The terminal then writes
the same value to the control list write tag(s).
➀ Controller writes value of list item
to search tag address.
➁ Terminal reads the search tag data and
highlights the corresponding item on
the control list.
➂ Terminal writes item value to control list write tag(s).
Publication 2711-6.0
Creating Control List Selectors
9–3
Piloted control lists have additional options:
• Block Write
• Inactive States
Block Write Tag
If a block write tag is assigned, the terminal writes the values of all
items displayed in the control list to a block of addresses starting
with the block write start tag address. The maximum number of
items supported by the block write tag varies for each terminal:
• 15 values for PanelView 550 terminals
• 25 values for PanelView 600 terminals
• 24 values for PanelView 900 monochrome and
1000 grayscale terminals
• 29 values for PanelView 900/1000/1400 color terminals
CONTROL LIST
Stage 1
(100)
Stage 2
(200)
Stage 3
(300)
Stage 4
(400)
Stage 5
(500)
Stage 6
(600)
Stage 7
(700)
Stage 8
(800)
Stage 9
Stage 10
(900)
(1000)
Displayed Portion
of Control List
Block Write Data
Sent to Controller
400
500
600
700
800
Block Write Start Tag
Up to 29 Sequential
Addresses
Inactive States
Inactive states are states that appear on the control list but cannot be
selected by an operator. The cursor appears as a hollow head cursor
when moved to an inactive state. An operator cannot highlight or
select an inactive item. Inactive states are included as part of the
data sent with a block write of the displayed list items (see above).
Active
State
State 1
State 2
State 3
State 4
State 5
Cursor at state 2,
an active state
Inactive
State
State 1
State 2
State 3
State 4
State 5
Active
State
Operator selects inactive state 3.
Cursor becomes hollow and highlight
remains in original position.
State 1
State 2
State 3
State 4
State 5
Operator selects active state 4.
Cursor returns to solid fill state
and highlight moves to selection.
Publication 2711-6.0
9–4
Creating Control List Selectors
Control List Options
A control list can contain up to 255 operations.
Control List with Value Data
The following example shows a control list used to input set values
into a controller address. The fluid level of a tank is varied by a
control list.
TANK LEVEL CONTROL
Empty Tank
1/4 Fill Level
1/2 Fill Level
Full Tank
1800 = 1/4 Full
= Value 1800
Address N7:2
Controller
TANK LEVEL CONTROL
Empty Tank
1/4 Fill Level
1/2 Fill Level
Full Tank
3600 = 1/2 Full
= Value 3600
Address N7:2
Controller
Control List with Bit Data
The next example shows a control list used for on/off type controls.
The list controls the opening and closing of a feed hopper.
HOPPER CONTROL
Open Hopper 1
Close Hopper 1
Hopper 1
= Value 0
Address B3:2/0
0 = Close
Controller
HOPPER CONTROL
Open Hopper 1
Close Hopper 1
Hopper 1
= Value 1
Address B3:2/0
1 = Open
Controller
Publication 2711-6.0
Creating Control List Selectors
9–5
Multiple Control Lists
You can assign a standard control list to a function key or touch cell
to activate the list for operator input. Multiple control lists can
appear on the same screen. Another way to select a standard control
list is to use the left
or right
arrow keys on the terminal.
TANK LEVEL CONTROL
HOPPER CONTROL
Empty Tank
Open Hopper 1
1/4 Fill Level
Close Hopper 1
1/2 Fill Level
Full Tank
Assigned Function Key F2
Indicator Bar
Shows Active List
Creating a
Control List Selector
Assigned Function Key F1
This section shows how to create a control list selector. On touch
screen terminals, the control list aligns with the touch grid even if it’s
not visible.
To create a control list selector
1. Choose Standard or Piloted from the Objects Control List
Selectors submenu.
Or click the Control List Selector tool from the toolbox.
2. Position the pointer (+) and click the left mouse button to place
the default size. Or drag the pointer to size the control list.
default size
dragged diagonally
3. To place another control list, move the pointer to a new location
and click again.
4. Click the right mouse button to exit control list selector mode.
Or click the selection tool on the toolbox.
Publication 2711-6.0
9–6
Creating Control List Selectors
Setting Properties
of a Control List Selector
To set properties of a control list selector:
1. Double-click the control list selector object.
Opens
Tag Dialog
2. On the Properties tab, set the operating parameters of the Control
List Selector.
The following descriptions define properties of a control list selector.
Type
Specifies the type of control list: Standard or Piloted.
• For a Standard list, control list items are selected by an operator.
• For a Piloted list, control list items are selected by either the
operator or the logic controller writing to the search tag address.
Initial State
Specifies the control list selection on initial powerup of the terminal
and the initial value sent to the write tag address. The value of the
initial state overrides the initial value in the Tag Editor.
Publication 2711-6.0
Creating Control List Selectors
9–7
Write
Specifies the type of data to send to controller: Single Bit or Value.
• For Single Bit (2-state control list selector only), the terminal
writes to a bit address.
To enable Single Bit as an option, you must reduce the number of
states to 2 on the States tab.
• For Value, the terminal writes to a word address.
Select the format of the data from the Data Format list box. The
data type of the write tag must be compatible with the selected
format for the application to validate.
Use this Format
With this Tag Data Type
Signed Integer
Signed Integer
4-BCD
4BCD
Binary
Hexadecimal
Octal
Unsigned Integer
Unsigned
ns ned Inte
Integer
er
or Bit Array
Contacts
If Single Bit was selected in the Write area, select Normally Open or
Normally Closed contacts for the 2-state selector.
Select
To
Normally Open
Send value of 0 when control list is in state 0
and value of 1 when control list is in state 1.
Normally Closed
Send value of 1 when control list is in state 0
and value of 0 when control list is in state 1.
The Contact area is dimmed if Value was selected in the Write area.
Write Tag
Specifies the name of the tag address to write the single bit or value.
If the tag doesn’t exist, enter a tag name. Edit the tag definition
using the Edit Tag button or the Tag Editor.
Publication 2711-6.0
9–8
Creating Control List Selectors
Search Tag (Piloted Control Lists only)
Specifies the name of the tag address to which the controller writes
to select an item on a control list. A control list item is selected
when the value assigned to the item equals the value at the search tag
address.
Control Tag (Piloted Control Lists only)
Only applies to Piloted Control Lists with “User and Controller” or
“Controller Only” selected in the Access box. The controller uses
this tag to determine whether the control list is controlled by an
operator or a controller. When the value at this tag address is 0, the
operator has control of the control list. A value other than 0 enables
the controller to select items on the control list.
Note on “User and Controller” Access
When the operator has control of the list, the write tag is updated in
the logic controller, but the search tag retains the same value present
when the logic controller relinquished control. When the controller
regains control of the list, it uses the value in the search tag to update
the write tag value, which changes the selected state. This behavior
is appropriate when the controller is operating as a master device.
To bypass this behavior, add the following rung of ladder logic for
each search tag address.
Control Tag Address
MOV
MOVE
Source
Destination:
Write Tag Address
Search Tag Address
Block Write Start Tag (Piloted Control Lists only)
Specifies the starting point for the block write data. The block write
data contains all values for items currently displayed on the control
list. The maximum number of entries supported by the block write
tag varies for each terminal.
• 15 values for PanelView 550 terminals
• 25 values for PanelView 600 terminals
• 24 values for PanelView 900 monochrome and
1000 grayscale terminals
• 29 values for PanelView 900/1000/1400 color terminals
When using block write data, do not assign functions to the
addresses following the Block Write Start Tag. Reserve an address
for each visible row on a control list.
Publication 2711-6.0
Creating Control List Selectors
9–9
Input
Specifies whether the operator presses a function key or a touch cell
to activate a control list.
• For a keypad terminal, select a function key from the list.
• For a touch screen terminal, touch cell is automatically enabled.
PanelView 550/600 Keypad & Touch Screen terminals support
function key and touch cell input.
The selected function key displays a graphic of a control list and an
asterisk next to the key number, indicating the key is used.
*F1
Control List
Asterisk
Wrap Around
Specifies whether the selection cursor moves to the top or bottom of
the list when the operator presses the down
or up
arrow
key on the last or first item in the control list.
Click the check box to activate wrap around. To disable wrap
around, clear the check box.
Write on Enter
Specifies whether the list selection is sent to the controller
key is pressed.
immediately or when the terminal’s Enter
By default, the operator is required to press the Enter
To disable Write on Enter, clear the check box.
key.
Publication 2711-6.0
9–10
Creating Control List Selectors
Configuring States for
a Control List Selector
Use the States tab on the Control List Selector dialog to:
• edit and format the text for each state
• enter a value for each control list state
• restrict access to states in a Piloted Control List
• add or delete states as necessary
To configure the states of a control list selector:
1. Click the States tab on the Control List Selector dialog.
Each row in the spreadsheet represents a state in the control list
selector. The fields in each row define the text and visual
characteristics for each state.
The initial default is 16 states (row 0 to row 15).
2. Edit the fields as necessary.
3. Click OK to exit Control List Selector dialog.
Value field appears only if Value
was selected in the Write area of
the Properties tab.
Access field appears only
for a Piloted Control List.
Editing Number of States
A Control List Selector supports a maximum of 255 states (0 to 254
rows). Use only the number required.
To add states to a control list selector:
1. Hold down the right mouse button and choose Append State from
the popup menu.
A row is added at the end with the next available state number.
2. Repeat step 1 for each state you want to add.
Each state you add is created with the defaults from State 0 and
default text (ST 0, ST 1, ..., ST 254).
To delete states, select a row number and choose Delete State from
the popup menu.
Publication 2711-6.0
Creating Control List Selectors
9–11
Editing State Text
The Text field defines the text that will appear for each state in the
Control List Selector. Double-click the cell and edit the text.
Other text fields control how the text is formatted for each state:
• text size (selection applies to entire list)
• underline
• text blink
• alignment (left, right, center)
• foreground color
Entering State Values
If Value was selected on the Properties tab, the Value field appears
for each state. This field specifies a numeric value to send to the
word address for each state. The default value is the state number.
The value you enter must be within the range of the Data Format
selected on the Properties tab. The default value is the state number.
Data Format
Range
Binary➀
0000 0000 0000 0000 to 1111 1111 1111 1111
Unsigned Integer
0 to 65535
Signed Integer
-32768 to +32767
4-BCD
0 to 9999
Hexadecimal➀
0 to FFFF
Octal➀
0 to 177777
➀ Formats allowed for data entry. The terminal does not display/transfer these formats.
The value is converted when a different data format is selected.
Restricting Access to States (Piloted Control Lists only)
The Access field appears only for Piloted Control Lists. This field
allows you to specify who can access the control list state.
Select
To
User and Controller
Allow the operator and controller to select the control list state.
User Only
Allow only the operator to select the control list state.
Controller Only
Allow only the controller to select the control list state.
None
Create an inactive state.
Important:
Do not select “Controller Only” or “None” for the
initial state defined on the States tab. These settings will
result in a validation error. One state must allow user
access or the application will fail to validate
Publication 2711-6.0
9–12
Creating Control List Selectors
Creating List Keys
Touch screen only terminals require List keys on the screen, enabling
the operator to move the cursor in a Control List and select a list
item. List keys are also supported on keypad terminals.
The available List Keys and functions are listed below.
List Key
Type
Description
Move Up
Moves the cursor to the previous item in the list.
Required.
Move Down
Moves the cursor to the next item in the list. Required.
Home
Moves the cursor to the first item in the list. Optional.
End
Moves the cursor to the last item in the list. Optional.
Page Up
Moves the cursor up a page in a scrolling list. Optional.
Page Down
Moves the cursor down a page in a scrolling list.
Optional.
Backspace
Returns the cursor to the currently highlighted selection.
Optional.
Enter
Confirms a selection and sends the item value to the
controller. Required if Write on Enter was configured as
a control list attribute.
To create a list key:
1. Click a List Key tool in the toolbox.
Or choose a List Key from the Objects List Keys submenu.
2. Position the pointer (+) and click the left mouse button.
3. Click the right mouse button to exit List Key mode.
Or click the selection tool on the toolbox.
To access the properties of a list key:
1. Double-click the list key object.
2. Under Input, specify how the operator will activate the list key.
• For keypad terminals, select a function key from the list.
• For touch screen terminals, touch cell is automatically
enabled.
3. When done, click OK.
Publication 2711-6.0
Creating Data Entry Controls
Chapter Objectives
This chapter describes how to create objects that activate a
scratchpad for numeric or ASCII data entry including the keypad
enable button and the cursor point.
Section
10–1
Numeric Entry Controls
10–2
Keypad Enable Button
10–2
Cursor Point
10–2
Scratchpad
10–2
Numeric Entry Examples
10–3
Data Entry Scaling
10–4
Creating a Numeric Entry Object
10–7
Setting Properties for a Numeric Entry Object
10–7
ASCII Entry Controls
Helpful Hints
Page
Helpful Hints
10–12
Keypad Enable Button
10–12
Cursor Point
10–12
Scratchpad – Keypad or Keypad/Touch Screen Terminals
10–13
Scratchpad – 550 Touch Screen Terminals
10–14
Scratchpad – 900/1000/1400 Touch Screen Terminals
10–15
ASCII Scratchpad for other Languages
10–16
Creating an ASCII Entry Object
10–16
Setting Properties for an ASCII Entry Object
10–17
When creating numeric entry objects, consider:
• You can add inner text and/or an inner graphic to keypad enable
buttons and cursor point objects as well as other formatting
options. See Chapter 17 for formatting details.
• An application screen can have more than one cursor point object.
To activate a cursor point, the operator presses a function key or
touch cell. Another way to activate a cursor point is to press the
left/right arrow keys on the terminal until the cursor point is
selected.
• When the keypad enable button is pressed or the cursor point is
activated, the scratchpad opens in the center of the terminal
screen.
Publication 2711-6.0
10–2
Creating Data Entry Controls
Numeric Entry Controls
Keypad Enable Button
A keypad enable button is a momentary push button which can
display a value at a controller address. The initial value on power-up
is set from the Tag Editor. When pressed, this button opens the
scratchpad and enables the terminal keypad for data entry.
ENTER PSI
120
You can create keypad enable buttons with inner text and/or an inner
graphic and other formatting options. See Chapter 17.
Cursor Point
A cursor point is a data box that can display a value at a controller
address. The initial value on power-up is set from the Tag Editor.
key or a
When the cursor point is selected and the Enter
numeric key is pressed, the scratchpad opens and the terminal
keypad is enabled for data entry.
Each cursor point can be assigned a function key or touch cell to
activate the object for operator input. Multiple cursor point objects
can appear on the screen. Another way to select a cursor point is to
use the left
or right
arrow keys on the terminal.
8961
543
Assigned Function Key F1
Indicator Bar
Shows Active Cursor Point
Assigned Function Key F2
Scratchpad
The scratchpad opens in the center of the terminal screen when the
operator presses the keypad enable button or activates a cursor point.
Current Value
entered in scratchpad
550 Touch Screen only
Terminal Scratchpad
Keypad and Keypad/Touch Screen
Terminal Scratchpad
900/1000/1400 Touch Screen
Terminal Scratchpad
The top of the scratchpad shows the current value entered. Below the
current value is the range of values the operator can enter. The range
is set by supplying data entry limits in the Tag Editor.
The operator enters a value and presses the Enter
Publication 2711-6.0
key.
Creating Data Entry Controls
10–3
Numeric Entry Examples
The following examples show how numeric entry objects are used to
adjust the temperature and inflow of a tank.
Cursor Point Example
The operator selects one of the cursor point objects in the EDIT box
using a function key, touch cell or left/right arrow keys on the
terminal and then presses
Cursor Point
Objects
The scratchpad opens in the center of the screen. The operator enters
a new value using the terminal keypad.
Entered Value
Keypad Enable Example
The operator selects the Enter Temp or Enter Deg keypad enable
button using a function key or touch cell.
Keypad
Enable Buttons
The scratchpad opens in the center of the screen. The operator enters
a new value using the terminal keypad.
Entered Value
Publication 2711-6.0
10–4
Creating Data Entry Controls
Data Entry Scaling
Data entered by an operator can be scaled from engineering units
such as gallons or pounds per square inch to machine control values.
Terminal values are scaled using the formula:
y = mx + b
y = scaled value (entered by operator)
m = scale (multiplier)
x = controller value
b = offset
To calculate value (x) stored at the controller address, use:
y-b
x= m
Entered Value - Offset
Scale
=
The scale and offset values are entered in the Tag Editor. Scaled
values affect the controller value as follows:
• Scale (m) value >1 generates an x value smaller than y-b.
• Scale (m) value <1 generates an x value larger than y–b.
Example: Scaling a Data Entry Variable
The operator enters 30 (pounds) for (y). The offset (b) value is 2.
The scale (m) value is .01.
y-b
x= m
=
30 - 2
= 2800
.01
The terminal provides a controller match value of 2,800 for a weigh
scale transducer:
➃
Weigh Scale Value (2,800)
Matches Input Value (2,800)
Package is Accepted
➂
Value from
Weigh Scale= 2,800
➁
PanelView Terminal
Scales Value to 2,800
for Match Code
G
➀
Operator Inputs
Weight of 30 Pounds
The value displayed in a numeric entry object may or may not be
scaled. The displayed value may be assigned a tag name independent
of the value written to the controller (write tag) address.
Publication 2711-6.0
Creating Data Entry Controls
10–5
Data Limits for a Scaled Value
If a scaled value exceeds the range for the selected data type, the
terminal will display a ‘Value Not In Range’ warning. When using
scaling, we recommend that you limit the minimum and maximum
values an operator can enter. These values are set in the Tag Editor
form view. (see page 19–5 ).
Calculate the range for scaled values before entering values in the
Tag Editor. Use the following formulas to determine scaled
minimum and maximum values:
Maximum Input Value = (Maximum Value for Data Type x Scale) + Offset
Minimum Input Value = (Minimum Value for Data Type x Scale) + Offset
For example:
• Scale = 1.8 and Offset = 32 (Fahrenheit to Celsius conversion)
• Data type is Signed Integer (-32,768 to +32,767)
The minimum / maximum values an operator can enter without
truncating:
Maximum Input Value = 32,767 x 1.8 + 32 = 59012
Minimum Input Value = -32,768 x 1.8 + 32 = -58950
Initial Value of a Scaled Value
The initial value specified in the Tag Editor is written to the
controller on powerup or reset. This initial value is not scaled, so it
must be entered in units used by the logic controller.
For example, the terminal uses _C and the controller uses _F. To
initialize the terminal to a value of 32_F, the initial value in the Tag
Editor needs to be 32, not 0.
The terminal does not scale the initial value before sending it to the
controller if the specified tag has an:
• initial value and
• a scale and/or
• offset
The value stored in the terminal may be different than the value sent
to the controller because of rounding that occurs during pre-scaling.
A warning message is displayed during validation if this occurs. If
the scaled initial value exceeds the range limits (because of a
rounding error), an error message is displayed.
Publication 2711-6.0
10–6
Creating Data Entry Controls
Precision and Rounding
Except for floating point values, the logic controller stores values as
integers, rounding off any digits to the right of the decimal point.
However, the terminal can scale decimal values to or from integer
values.
In this illustration, the entered value of 7.5 is rounded up to 8. When
this value is displayed, or used in a mathematical formula, the result
may be incorrect.
Entered Value = 7.5
Displayed Value = 8
Controller Value = 8
(rounded)
If decimal precision is needed, select appropriate values for scale and
offset.
Example
Use scaling to convert a decimal value from degrees Fahrenheit to
degrees Celsius. The precision is determined by the value the
operator enters and the decimal position of the scale.
Fixed Decimal
Decimal Position = 2
Field Width = 6
Equations for Scaling Example
Controller Value =
Entered Value – Offset
Scale
PanelView
Displayed Value = Controller Value x Scale + Offset
Fixed Decimal
Stored Value =
121.36 – 32
= 4964.44 = 4964
0.018
4964.44
Offset=32
Scale=.018
Displayed Value
121.35
Rounded
4964
4964
Controller
Keypad Controlled Decimal
Decimal Position = Operator Entered
Field Width = 6
Displayed Value = (4964 x 0.018) + 32 = 121.35
Keypad Controlled Decimal
122.9 – 32
= 50.5 = 51
Stored Value =
1.8
Displayed Value = (51 x 1.8) + 32 = 123.8
Scale
Entered Value
121.36
Scale
Entered Value
122.9
Displayed Value
123.8
50.5
Offset=32
Scale=1.8
123.8
Rounded
51
51
Controller
The decimal point is positioned to provide a display appropriate to the scaled value.
The terminal stores the full precision value and the controller stores
the rounded value (if writing to an integer file).
Publication 2711-6.0
Creating Data Entry Controls
10–7
Creating a Numeric Entry Object
This section shows how to create a cursor point or keypad enable
button. On touch screen terminals, both objects are aligned with the
touch grid even if it’s not visible.
To create a Cursor Point or Keypad Enable button:
1. Click the appropriate tool in the toolbox.
Or choose Cursor Point or Keypad Enable from the Objects
Numeric Entry submenu.
2. Position the pointer (+) and click the left mouse button to place
the default object size. Or drag the pointer to size the object.
Cursor Point
Keypad Enable
3. To place another object of the same type, move the pointer to a
new location and click again.
4. Click the right mouse button to exit numeric entry mode.
Or click the selection tool on the toolbox.
Setting Properties of a Numeric Entry Object
This section shows how to set the properties for a Keypad Enable
button or a Cursor Point Object.
To set properties of a Cursor Point or Keypad Enable button:
1. Double-click the numeric entry object.
Opens
Tags Dialog
2. On the Properties tab, set operating parameters for the numeric
entry objects (as defined on following pages).
3. When done, click OK.
Publication 2711-6.0
10–8
Creating Data Entry Controls
Type
Changes the type of numeric entry object.
Input
Specifies whether the operator presses a function key or a touch cell
to activate the numeric entry object.
• For keypad terminals, select a function key from the list.
• For touch screen terminals, touch cell is automatically enabled.
The PanelView 550/600 Keypad & Touch screen terminal supports
function key and touch cell input.
The selected function key displays a graphic of the numeric entry
object and an asterisk next to the key number.
*F1
*F1
Asterisk
Keypad Enable
Asterisk
Cursor Point
Write Tag
Specifies the name of the tag address where the terminal writes the
entered value. If the tag doesn’t exist, enter a tag name. Edit the tag
definition (including data entry limits, scale values, initial value)
using the Edit Tag button or the Tag Editor.
Valid data types for the write tag are unsigned/signed integer, 4BCD
or floating point.
Publication 2711-6.0
Creating Data Entry Controls
10–9
Display
The Display area defines properties of the data that displays in the
numeric entry object.
Display Tag specifies the name of the tag address from which to read
the display data. Usually, the write tag and display tag are the same.
One-directional protocols, such as DeviceNet, however, require
different addresses for the Display tag and Write tag. The Write tag
is an input and the Display tag is an output.
Data displayed in a numeric entry object may or may not be scaled.
• To display the entered value regardless of the value stored at the
controller, don’t enter a display tag (leave field blank).
• To display a non-scaled value (not the entered value), use
different tag names for the display and write tags. Both tags
should have the same tag address but the display tag shouldn’t
have scaling.
• To display an entered value based on the value stored at the
controller, use the same tag name for the display and write tags.
Because of rounding, the displayed value may not be identical to
the entered value.
Entered Value = 5
Displayed Value = 6
Scaled (x - (-10)) .5
Scaled ((2) (8) + ( -10))
scale = 2
offset = -10
scale = 2
offset = -10
Terminal Value = 8
(rounded)
Except for floating point values, the controller only stores integer
values, the scaled result of 7.5 is rounded to 8. The same scale
used for data entry is used to convert the rounded value for
display.
Fill with Zeroes specifies whether zeroes are entered in unused entry
positions to the left and right of the decimal point. For example, if
the value 32100 is entered (fixed decimal point position = 2):
Zero Filled
000321.00
No Fill
___321.00
Publication 2711-6.0
10–10
Creating Data Entry Controls
Format
Field Width specifies the maximum number of digits that can be
entered. The default is 6.
If the entered value is a decimal, it may be scaled or rounded to an
integer or both, before it is sent to the controller. See page 10–4.
Decimal Point specifies whether the decimal is fixed (formatted) or
keypad controlled (floating) for display and entry values.
• Select Fixed to fix the decimal point in the data display and the
scratchpad. As an operator enters values in the scratchpad the
numbers are shifted to the left of the decimal point.
The Position box specifies the position of the decimal point for
fixed decimal point values. You can position the decimal 0 to 10
places to the left of the rightmost character.
Select
For this position
Select
For this position
0
97
6
97.276767
1
97.2
7
97.2767676
2
97.27
8
97.27676767
3
97.276
9
97.276767676
4
97.2767
10
9.7276767676
5
97.27676
Note: If Position is 0, then the field width must be 2 > decimal
position for positive numbers. One position is used for the digit to
the left of the decimal and one for the decimal point. If the
decimal position is 2 and the field width is 6, an entered value of
225 is displayed as 225.00 not 2.25.
For negative numbers the field width must be 3 > decimal
position. For example, to display the number –0.1234, set the
field width to 7 and the decimal position to 4.
• Select Keypad Controlled to allow the operator to enter the
decimal point using the terminal keypad. Data is displayed as a
floating point.
The terminal stores the full precision value and the controller stores
the rounded value (if writing to an integer file).
Publication 2711-6.0
Creating Data Entry Controls
10–11
Notification and Handshake Tags
Notification and handshake tags are options to ensure that data is
written to the write tag address before the scratchpad is closed.
The notification tag address is set to 1 when an operator presses the
enter key. The scratchpad remains open until the controller program
checks for notification that the value was written to the tag address
and then sets the handshake tag address to 1.
The terminal automatically clears the notification bit when the
handshake bit is set by the controller. The controller’s ladder logic
must set the handshake bit before a timeout occurs. The default
handshake timeout is 4 seconds (valid range is 1 – 60 seconds). See
page 20–21 to adjust the handshake timeout.
➀
Operator initiates data entry.
➄ Terminal removes scratchpad.
Terminal then clears Notification Tag.
Controller program should set Handshake Tag to 0.
➁
Notification Tag = 0
Handshake Tag = 0
Operator enters
value in scratchpad.
Notification Tag = 0
Handshake Tag = 0
Notification Tag = 0
Handshake Tag = 0
➂
➃
Operator presses
Enter key.
Controller ladder logic program
–Verifies notification address set to 1.
–Sets handshake tag to 1 when new value present.
Notification Tag
B3
0
B3
1
Handshake Tag
Notification Tag = 1
Controller Sets Handshake Tag = 1
Terminal sends value to Controller
Terminal sets Notification Tag = 1
Handshake Tag = 0
Select tags from the appropriate list boxes. If the tags don’t exist,
enter tag names. Edit definitions of the tags using the Edit Tag
button or the Tag Editor.
Publication 2711-6.0
10–12
Creating Data Entry Controls
ASCII Entry Controls
The ASCII Entry object allows the operator to send an alphanumeric
string (up to 128 characters) to a controller.
Like numeric entry objects, the ASCII Entry object can appear on an
application screen as a keypad enabled button or a cursor point.
Keypad Enable Button
The keypad enable button is a momentary push button which
displays an ASCII character string at a controller address. The
button’s initial value is sent to the controller when the application is
first run and may also be displayed in the button. When pressed, this
button opens the ASCII scratchpad allowing the operator to enter and
send a new character string to the controller.
Cursor Point
The cursor point is a data box that displays an ASCII character string
at a controller address. The object’s initial value is sent to the
controller when the application is first run. The initial value may also
be displayed in the box. When the cursor point is selected and the
Enter key is pressed, the ASCII scratchpad opens allowing the
operator to enter and send a new character string to the controller.
Publication 2711-6.0
Creating Data Entry Controls
10–13
ASCII Scratchpad – Keypad or Keypad/Touch ScreenTerminals
Display Area
Character Keyboard
Controls
The operator selects characters from the Character Keyboard by
moving the cursor (with the keypad arrows) over a character and
pressing the SEL-F1 function key. The character appears in the
Display Area. This area scrolls so the operator can enter a character
string that is longer than the Display Area. All characters are sent to
the controller even if not visible.
After entering all the characters, the operator sends the string to the
controller by pressing ENTER ↵ on the keypad. The leftmost
character is placed in the high byte of the first word (of the write tag
address), the next character in the low byte and so on.
Note: DeviceNet ASCII Entry allows for byte swapping.
Controls
A
"
B
Y
Location
Function
Terminal Keypad
Moves the cursor up, down, left, or right in the Character Keyboard.
Terminal Keypad
Deletes the character to the left of the cursor in the Display Area. If the cursor is at the leftmost
position when you press , the scratchpad closes.
Sends the character string to the assigned write tag address in the controller.
↵
Terminal Keypad
SEL F1
Function Keys
When opening the ASCII scratchpad, the character string is highlighted. If the operator selects a
character immediately, the terminal clears the Display Area and displays the selected character. If the
operator presses a control key, the terminal continues to display the existing string, allowing the
operator to edit it.
Selects the highlighted character and places it at the cursor position in the Display Area.
Toggles between Insert and Overstrike mode. The overstrike mode appears in reverse video.
In Insert mode, the character selected is inserted before the cursor in the Display Area. If the
maximum number of characters has been entered in the Display area, new characters are ignored.
INS F2
Function Keys
<<
F3
Function Keys
In Overwrite mode, the selected character replaces the character at the cursor in the Display Area.
Moves the cursor one character to the left in the Display Area.
>>
F4
Function Keys
Moves the cursor one character to the right in the Display Area.
ESC F5
Function Keys
Closes the scratchpad without making any changes.
CLR F6
Function Keys
Clears the string in the Display Area.
Publication 2711-6.0
10–14
Creating Data Entry Controls
ASCII Scratchpad – 550 Touch Screen Terminals
Character Keyboard
Cursor
Display Area
Cursor Control Keys
Controls
To select characters from the Character Keyboard, the operator
presses the cursor control keys to move the cursor over a character
and then presses the SEL key. The character is entered in the Display
Area. This area scrolls so the operator can enter a character string
that is longer than the Display Area. All characters are sent to the
controller even if not visible.
After entering all the characters, the operator sends the string to the
controller by pressing ↵. The leftmost character is placed in the high
byte of the first word (of the write tag address), the next character in
the low byte and so on.
Note: DeviceNet ASCII Entry allows for byte swapping.
Controls
A
"
Function
B
Y
SEL
Moves the cursor up, down, left, or right in the Character Keyboard.
Selects the highlighted character and places it at the cursor position in the Display Area.
Toggles between Insert and Overwrite modes. The overstrike mode appears in reverse video.
INS
In Insert mode, the character selected is inserted before the cursor in the Display Area. If the maximum number of
characters has been entered in the Display Area, new characters are ignored.
<<
In Overwrite mode, the selected character replaces the character at the cursor in the Display Area.
Moves the cursor one character to the left in the Display Area.
>>
Moves the cursor one character to the right in the Display Area.
ESC
Closes the scratchpad without making any changes.
CLR
Clears the string in the Display Area.
Deletes the character to the left of the cursor in the Display Area.
Sends the character string to the assigned write tag address in the remote device.
↵
Publication 2711-6.0
After pressing ↵ to open the ASCII scratchpad, the character string is highlighted. If the operator selects a character
immediately, the terminal clears the Display Area and displays the selected character. If the operator presses a control key,
the terminal continues to display the existing string, allowing the operator to edit it.
Creating Data Entry Controls
10–15
ASCII Scratchpad – 900/1000/1400Touch Screen Terminals
Display Area
Character Keyboard
Controls
The operator selects characters by touching the Character Keyboard
on the screen. The character is entered in the Display Area. This
area scrolls so the operator can enter a character string that is longer
than the Display Area. All characters are sent to the controller even
if not visible.
After entering all the characters, the operator sends the string to the
controller by pressing ENTER ↵ on the touch screen keypad. The
leftmost character is placed in the high byte of the first word (of the
write tag address), the next character in the low byte and so on.
Note: DeviceNet ASCII Entry allows for byte swapping.
Controls
Function
SHF
(Shift)
By default this function is off and keys appear in unshifted state. When you press SHF, the button appears in reverse video. All
character keys, including numbers and symbols, appear in their shifted state. For example, a becomes A; 2 becomes @.
CAPS
By default this function is off and keys appear in lowercase. When you press CAPS, the button appears in reverse video. Letters
appear and are entered in uppercase but numbers and symbols are not shifted. The state is maintained across power cycles.
Toggles between Insert and Overwrite modes. The overstrike mode appears in reverse video.
INS
<<
In Insert mode, the character selected is inserted before the cursor in the Display Area. If the maximum number of characters has
been entered in the Display Area, new characters are ignored.
In Overwrite mode, the selected character replaces the character at the cursor in the Display Area.
Moves the cursor one character to the left in the Display Area.
>>
Moves the cursor one character to the right in the Display Area.
ESC
Closes the scratchpad without making any changes.
CLR
Clears the string in the Display Area.
Deletes the character to the left of the cursor in the Display Area.
Sends the character string to the assigned write tag address in the remote device.
↵
After pressing ↵ to open the ASCII scratchpad, the character string is highlighted. If the operator selects a character immediately,
the terminal clears the Display Area and displays the selected character. If the operator presses a control key, the terminal
continues to display the existing string, allowing the operator to edit it.
Publication 2711-6.0
10–16
Creating Data Entry Controls
ASCII Scratchpads in Other Languages
The ASCII Scratchpad is available with Character Keyboards in:
• French
• German
• Italian
• Spanish
If the PanelView terminal is configured for operation in one of these
languages, the ASCII scratchpad will display the Character
Keyboard appropriate to the language.
The SHF control toggles between SHF/SHF2. In SHF mode, the
Character Keyboard displays the shifted state characters (e.g. a to A
and 3 to #). In the SHF2 mode, the Character Keyboard displays
additional characters available for the desired language.
The values of the extended ASCII characters match those in
Appendix H.
Creating an ASCII Entry Object
1. Choose Cursor Point or Keypad Enable from the Objects ASCII
Entry menu.
2. Click the left mouse button to place the default object size or drag
the crosshair to size the object.
3. To place another object of the same type, move the pointer to a
new location and click again.
4. Click the right mouse button to exit ASCII entry mode.
Or click the selection tool on the toolbox.
Publication 2711-6.0
Creating Data Entry Controls
10–17
Setting the Properties of an ASCII Entry Object
1. Double-click the object to access its dialog parameters.
2. On the Properties tab, set the operating parameters of the ASCII
Entry object (as defined below).
3. When the dialog is closed, the object appears with # characters to
match the string width.
If you select Format Inner Text while the object is selected, the
inner text box contains an ASCII placeholder /* Z:10 */, where 10 is
the specified string width for the object.
Like other objects, you can add inner text around the placeholder or
change the appearance of the object using formatting options. See
Chapter 17 for details.
Type
Changes the ASCII entry object to Keypad Enable or Cursor Point.
Input
Specifies whether the operator presses a function key or a touch cell
to activate the ASCII entry object.
• For keypad terminals, select a function key from the list.
• For touch screen terminals, touch cell is automatically enabled.
The PanelView 550/600 Keypad & Touch screen terminal supports
function key and touch cell input.
The selected function key displays a graphic of the object and an
asterisk next to the key number.
Publication 2711-6.0
10–18
Creating Data Entry Controls
Write Tag
Specifies the name of the tag address where the terminal writes the
ASCII string. The data type of the write tag must be Character
Array. You can write the tag data to any data file that supports the
Character Array data type. The Array Size must be the same size as
the String Width field.
Edit the tag definition using the Edit Tag button or the Tag Editor.
Reserve word block addresses for each ASCII Entry object.
Notification and Handshake Tags
Optional tags that ensure data is written to the write tag address
before the scratchpad closes.
When the operator presses the Enter key to send the ASCII string to
the write tag address, the notification tag is set to 1.
The scratchpad remains open until the controller checks for
notification that the value was written to the write tag address and
then sets the handshake tag address to 1. The terminal clears the
notification bit when the handshake bit is set by the controller.
String Width
The maximum number of characters that can be entered in the ASCII
scratchpad. You must enter an even integer.
For
Maximum String Width
DH+/DH-485/DF1
80
Remote I/O
128
DeviceNet
128
If the ASCII string is less than the string width, the NULL character
is appended before the string is sent to the controller. The NULL
character does not affect the display of the string.
Display Tag
Specifies the source of the data displayed in the ASCII scratchpad. If
a display tag is not defined, the scratchpad displays the last value
entered. The data type of the display tag must be Character Array.
The Array Size must be the same size as the String Width.
Show Current String on ASCII Scratchpad
If selected, the ASCII scratchpad displays the character string stored
at the write tag address. If not selected, the string is not displayed.
Mask Characters
A security feature that prevents the display of characters entered in
the ASCII scratchpad. The mask character # replaces each ASCII
character. For example, the characters PASSWORD would appear as
######## in the scratchpad.
Publication 2711-6.0
Creating Screen Selectors
Chapter Objectives
This chapter shows how to create screen selectors allowing an
operator to navigate between screens in an application. You can
create screen buttons or a screen list. The chapter sections are:
Section
Helpful Hints
Page
Helpful Hints
11–1
Goto Screen Button
11–2
Goto Config Screen Button
11–2
Return Screen Button
11–2
Screen List Selector
11–2
Creating Screen Buttons
11–3
Setting Properties of Screen Buttons
11–4
Creating a Screen List Selector
11–5
Setting Properties of a Screen List Selector
11–6
Configuring Entries in a Screen List Selector
11–7
Creating List Keys
11–9
PLC/SLC Controlled Screen Changes
11–9
When creating screen selectors, consider:
• A screen list can have a maximum of 255 entries (numbered 0 to
254). Use only the number of entries required by the application.
• Each entry in a screen list is limited to a single line.
• On keypad terminals, the cursor is moved through the screen list
using the terminal’s up
and down
arrow keys. The
screen displays when the operator presses Enter
.
• Touch screen only terminals require list keys on the screen,
•
•
•
•
•
•
enabling the operator to move cursor through a list.
An application screen can have more than one screen list. To
activate a screen list, the operator presses a function key or touch
cell. Another way to activate a list is to press the left/right arrow
keys on the terminal until the list is selected.
Screen list can be used on a main menu screen. A screen button
on each application screen returns the operator to the main menu.
When screen space is limited, use screen buttons.
Place screen buttons in same position on each screen. This allows
an operator to quickly locate and navigate between screens.
Create screen buttons with inner text and/or inner graphic.
Changing the text size applies to the entire screen list.
Publication 2711-6.0
11–2
Creating Screen Selectors
Goto Screen Button
The Goto screen button, when pressed, displays a specific screen.
MAIN
MENU
Goto Config Screen Button
The Goto Config Screen button, when pressed, displays the
PanelView Terminal Configuration Mode menu.
CONFIG
SCREEN
Return Screen Button
The Return screen button, when pressed, displays the previous
screen. This button doesn’t provide a continuous link back to the
first screen.
PREVIOUS
SCREEN
Screen List Selector
A Screen List Selector contains a menu or list of screens from which
the operator can make a selection. A cursor indicates the current
selection. The operator uses the up
and down
arrow keys
key to
on the terminal to move the cursor and the Enter
enter the selection.
Touch screen only terminals require list keys on the screen, enabling
the operator to move the cursor through the list.
Conveyor Controls
Conveyor Controls
Pump Controls
Pump Controls
Heater Controls
List Keys
Heater Controls
Each screen list selector is assigned a function key or touch cell to
activate the list for operator input. This allows multiple lists to
appear on a screen. Another way to activate a screen list selector on
or right
arrow keys on
keypad terminals is to use the left
the terminal’s keypad.
Pump Controls
Preloader
Tank 1
Heater Controls
Heat Loop
Conveyor Controls
Indicator Bar Shows
Active Screen List
Assigned Function Key F1
Publication 2711-6.0
Assigned Function Key F2
Creating Screen Selectors
Creating Screen Buttons
11–3
This section shows how to create a Goto, Goto Config Screen or
Return screen button. All appear the same when positioned on a
screen. On touch screen terminals, screen buttons are aligned with
the touch grid even if it’s not visible.
To create a Goto, Goto Config Screen or Return button:
1. Click the appropriate tool on the toolbox.
Or choose Goto, Goto Config Screen or Return from the Objects
Screen Selectors submenu.
2. Position the pointer (+) and click the left mouse button to place
the default button size. Or drag the pointer to size the button.
3. To place another screen button of the same type, move the pointer
to a new location and click again.
4. Click the right mouse button to exit screen button mode.
Or click the selection tool on the toolbox.
Publication 2711-6.0
11–4
Creating Screen Selectors
Setting Properties
of Screen Buttons
To set properties of a screen selector button:
1. Double-click the screen button object.
2. From the Screen List box, select the screen that you want to
display when the screen button is pressed.
3. Under Input:
• For keypad terminals, select a function key from the list.
• For touch screen terminals, touch cell is automatically
enabled.
PanelView 550/600 Touch Screen & Keypad terminals support
function key and touch cell input.
4. When done, click OK.
The selected function key displays a graphic of the screen button and
an asterisk next to the key number, indicating the key is used.
*F1
*F1
Goto Button
Publication 2711-6.0
Asterisk
Return Button
Asterisk
Creating Screen Selectors
Creating a
Screen List Selector
11–5
This section shows how to create and edit properties of a screen list
selector. On touch screen terminals, the screen list aligns with the
touch grid even if it’s not visible.
To create a Screen List Selector:
1. Click the Screen List Selector tool from the toolbox.
Or choose Screen List Selector from Objects Screen Selectors
submenu.
2. Position the pointer (+) and click the left mouse button to place
the default size. Or drag the pointer to size the screen list.
default size
dragged horizontally
3. To place another Screen List Selector, move the pointer to a new
location and click again.
4. Click the right mouse button to exit screen list selector mode.
Or click the selection tool on the toolbox.
Publication 2711-6.0
11–6
Creating Screen Selectors
Setting Properties
of a Screen List Selector
To set properties of a Screen List Selector:
1. Double-click the screen list selector object.
2. Under Input, specify whether the operator presses a function key
or a touch cell to activate the screen list.
• For keypad terminals, select a function key from the list.
• For touch screen terminals, touch cell is enabled.
PanelView 550/600 Touch Screen & Keypad terminals support
function key and touch cell input.
When exiting the dialog, the selected function key displays a
graphic of a screen list selector and an asterisk next to the key
number.
*F1
Screen List
Asterisk
3. Select the Wrap Around check box to enable or disable wrap
around for the selection cursor. The default is disabled.
Wrap around moves the selection cursor to the top or bottom of
the list when the down
or up
arrow keys are pressed on
the last or first screen in the list.
Publication 2711-6.0
Creating Screen Selectors
Configuring Entries
in a Screen List Selector
11–7
Use the States tab to:
• select a screen to associate with each entry
• edit text to display for each entry
• edit text formatting options (text size, underlining, blinking,
alignment and foreground color)
• add or delete screen list entries
To configure the entries in a Screen List Selector:
1. Click the States tab on the Screen List Selector dialog.
A spreadsheet opens. Each row represents an entry in the screen
list. The initial default is 16 entries (row 0 to row 15).
2. Edit the fields as necessary.
3. Click OK to exit dialog.
The Screen field links
an application screen
to the entry in the list.
The Text field defines
the text to appear for
each entry in the list.
Editing Number of Screen List Entries
A Screen List Selector supports a maximum of 255 entries (0 to 254
rows). Use only the number required.
To add states to a Screen List Selector:
1. Hold down the right mouse button and choose Append State from
the popup menu.
A new row is added after the last row.
2. Repeat step 1 for each state you want to add.
Each state you add is created with the defaults from Row 0 and
default text (ST 0, ST 1, ..., ST 254).
Publication 2711-6.0
11–8
Creating Screen Selectors
To delete states from a Screen List Selector:
1. Select the row number you want to delete.
2. Hold down the right mouse button and choose Delete State from
the popup menu.
3. Repeat steps 1 and 2 for each state you want to delete.
Selecting Screen Names
The Screen field contains a list of screens in the application. Select a
screen to associate with each entry in the screen list.
Editing Text Entries
The Text field specifies the text that will actually appear in the list
for the assigned screen. The row number indicates the position of the
text in the list.
The default text assigned for each list entry is ST and the row
number. Double-click in the cell and edit the text.
Other text fields control how the text is formatted for each entry:
• text size (changes to text size apply to entire list)
• underline
• text blink
• alignment (left, right, center)
• foreground color
Publication 2711-6.0
Creating Screen Selectors
Creating List Keys
11–9
Touch screen only terminals require List keys on the screen, enabling
the operator to move the cursor in a Screen List Selector and to
select a screen. List keys are also supported on keypad terminals.
The available List Keys and functions are listed below.
List Key
Type
Description
Move Up
Moves the cursor to the previous screen in the list.
Required.
Move Down
Moves the cursor to the next screen in the list. Required.
Home
Moves the cursor to the first screen in the list. Optional.
End
Moves the cursor to the last screen in the list. Optional.
Page Up
Moves the cursor up a page in a scrolling list. Optional.
Page Down
Moves the cursor down a page in a scrolling list.
Optional.
Backspace
Returns the cursor to the currently highlighted screen.
Optional.
Enter
Confirms a selection and displays the selected screen.
Required.
To create a list key:
1. Click a List Key tool in the toolbox.
Or choose a List Key from the Objects List Keys submenu.
2. Position the pointer (+) and click the left mouse button.
3. Click the right mouse button to exit List Key mode.
Or click the selection tool on the toolbox.
To access the properties of a list key:
1. Double-click the list key object.
2. Under Input, specify how the operator will activate the list key.
• For keypad terminals, select a function key from the list.
• For touch screen terminals, touch cell is enabled.
3. When you’re done, click OK.
PLC/SLC Controlled
Screen Changes
The SLC or PLC can control screen changes and return the current
screen value to the controller. Chapter 20 shows how to use control
and status tags to perform these controller functions.
Publication 2711-6.0
Creating Bar Graphs, Indicators,
Numeric Displays
Chapter Objectives
Bar graphs, indicators and numeric data displays show a numeric
value or a graphic representation of data stored at a controller tag
address. This chapter contains the following sections:
Section
Helpful Hints
Page
Helpful Hints
12–1
Scaling Data
12–2
Error States
12–3
Bar Graphs
12–4
Numeric Data Displays
12–9
Multistate Indicators
12–12
List Indicators
12–18
When creating bar graphs, indicators and displays, consider:
• Indicators reading a value do not have a “dead band” in which a
range of values are interpreted as a single state. For most
applications, the controller ladder logic should allow a range of
values above and/or below the specified value for each state to be
interpreted as the same state.
• Multistate indicators support up to 2,000 states or entries
(numbered 0-1,999).
• List indicators support up to 255 states or entries (numbered
0-254).
• For multistate or list indicators, use only the number of states or
entries required by the application.
• Multistate indicators include an error state (State E). The error
state notifies an operator that the data read isn’t within the
expected ranges.
Publication 2711-6.0
12–2
Creating Bar Graphs, Indicators, Numeric Displays
Scaling Data
Standard Data Displays
Standard data and bar graph displays show a numeric value stored at
a controller tag address.
Controller
Package Detect
Controller
Counter
Value
20
20
Scaled Data Displays
Scaled data and bar graph displays take raw numeric values and
mathematically manipulate them so that values are shown in standard
units such as gallons, feet per second, and pounds per square inch.
Values from the logic controller are scaled using the formula:
y=mx+b
y=scaled (displayed) value
m=scale (multiplier)
x=controller value
b=offset
The scale and offset values are entered in the Tag Editor. The
following example shows the use of a scaled data display.
13
Scaling
(x 0.0059 + 10)
Valve #1
Flow Rate
Transducer
Flow Rate
Transducer
Value
510
510
Controller
Publication 2711-6.0
Creating Bar Graphs, Indicators, Numeric Displays
Error States
12–3
Multistate Indicators
Multistate indicators have an error state to notify an operator when
data is out of range or when multiple states are triggered. The error
state (State E) is accessed from the States tab of the dialog or from
the State box on the tool bar. The inner text for State E is Error. You
can assign different inner text or display attributes to the error state.
State 0
State 1
State 2
Error
State E
Default Inner Text
for Error (E) State
Bar Graphs
A bar graph is either empty or filled if a value is not within the
allowable range of values.
100
100
75
75
50
50
25
25
0
0
Value Equals or Exceeds
Maximum Range
Value Below
Minimum Range
List Indicators
No list entry is highlighted if the data is outside of the allowable
range or if multiple states are triggered.
OFF
TEMPERATURE LOW
NORMAL
TEMPERATURE HIGH
Error=No state highlighted
Numeric Data Displays
If a value exceeds the specified field width for the numeric data
display, the overflow value is replaced with asterisks.
Publication 2711-6.0
12–4
Creating Bar Graphs, Indicators, Numeric Displays
Bar Graphs
Bar graphs monitor changing conditions such as temperature or fluid
levels. You can create various types of bar graphs.
Types of Bar Graphs
Create bar graphs as individual displays or in a cluster. You can
orient bar graphs either vertically or horizontally. A variety of fill
patterns and options allow for a variety of appearances.
9
8
0 lbs
10 lbs
7
6
20 lbs
5
30 lbs
4
40 lbs
3
2
50 lbs
1
Vertical Bar Graph
Fill from Top, Scale Left, Border On
Vertical Bar Graph
Fill from Bottom, Scale Right, Border Off
100
75
Full
High
Low
Empty
50
25
0_
0
10_ 20_
30_ 40_ 50_
Horizontal Bar Graph
Fill from Left, Scale Bottom,
Border On
Clustered Bar Graphs
Horizontal Bar Graph
Fill from Right, Scale Top,
Border Off
Use stacked bar graphs to create the effect of bidirectional graphs,
graphs with multiple fill patterns, or graphs showing relative values
to a total.
–30
–20
–10 0 10 20
30
–30
–20
–10 0 10 20
30
Two Bar Graphs Creating Bidirectional Effect.
100
100
100
75
75
75
50
50
50
25
25
25
0
0
0
Three Bar Graphs with Different Fill Patterns
(When bottom graphs fill, upper graphs begin to fill)
Publication 2711-6.0
Creating Bar Graphs, Indicators, Numeric Displays
12–5
Creating a Bar Graph
This section shows how to create a bar graph. You can create a bar
graph with or without a scale. The scale is a separate object.
To create a bar graph:
1. Click the Bar Graph tool in the toolbox.
Or choose Bar Graph from the Objects menu.
2. Position the pointer (+) and click the left mouse button to place
the default size. Or drag the pointer to size the bar graph.
3. To place another bar graph, move the pointer to a new location
and click again.
4. Click the right mouse button to exit bar graph mode.
Or click the selection tool on the toolbox.
Setting Properties of a Bar Graph
To set bar graph properties:
1. Double-click the bar graph object.
Opens Tag Dialog
2. Set the bar graph properties as defined on the next page.
3. When done, click OK.
Publication 2711-6.0
12–6
Creating Bar Graphs, Indicators, Numeric Displays
The following descriptions define properties of a bar graph.
Fill From
Sets the direction for filling the bar graph. Click the arrow at the
right of the box to list and select an option.
Select
To Fill
Left
Left to right
Right
Right to left
Top
Top to bottom
Bottom
Bottom to top
The bar graph fills with black on monochrome displays and white on
color displays. You can select a fill pattern from the Format Fill
Pattern submenu and turn the bar graph border off from the
Format Line Type submenu.
Range
Sets the minimum and maximum values the bar graph can display.
The range of values you can enter in the Min/Max boxes depends on
the data type of the read tag.
Min to Max Value Range
For this Data Type
0 to 9,999
4BCD
-32768 to +32767
Signed Integer
0 to 65535
Unsigned Integer
-99,999,997,952 to +999,999,995,904
Floating Point
If the value exceeds the maximum, the entire bar graph fills. If the
value is below the minimum, the bar graph appears as an empty box.
Read Tag
Specifies the name of the tag address to read for filling the bar graph.
If the tag doesn’t exist, enter a tag name. Edit the tag definition
using the Edit Tag button or the Tag Editor.
Publication 2711-6.0
Creating Bar Graphs, Indicators, Numeric Displays
12–7
Creating a Bar Graph Scale
This section shows how to create a bar graph scale.
To create a bar graph scale:
1. Click the Scale tool in the toolbox.
Or choose Scale from the Objects menu.
2. Position the pointer (+) and click the left mouse button to place
the default size. Or drag the pointer to size the bar scale.
3. To place another scale, move the pointer to a new location
and click again.
4. Click the right mouse button to exit scale mode.
Or click the selection tool on the toolbox.
To set scale properties:
1. Double-click the scale object.
2. From the Location box, select the orientation of the scale relative
to the bar graph.
Right
Left
Top
Bottom
3. In the Number box, enter the number of tick marks for the scale.
The number of tick marks allowed depends on the size of the
scale. Tick marks are spaced evenly along the scale.
4. When done, click OK.
Publication 2711-6.0
12–8
Creating Bar Graphs, Indicators, Numeric Displays
Creating Tick-Mark Labels
Use the graphics text tool to add tick-mark labels to the bar graph
scale. The labels aren’t attached to the scale but are handled as
separate objects.
Tick-mark Labels
100
0 lbs
10 lbs
0_
10_ 20_
30_ 40_ 50_
20 lbs
75
50
30 lbs
25
40 lbs
0
50 lbs
You can group the bar graph, scale and tick-mark labels so that
they’re handled as a single unit.
To create a tick-mark label:
1. Click the Text tool in the toolbox.
Or choose Text from the Objects "Graphics submenu.
2. Position the pointer and drag the text block to the size you want.
The text block is selected and you are placed in inner text mode.
3. Enter the label in the Text box.
As you enter the label, it’s also entered in the text block. An
asterisk (*) appears if the text exceeds the size of the block.
4. To create another label, repeat steps 2 and 3.
5. Click the right mouse button to exit background text mode.
Or click the selection tool in the toolbox.
6. When done, click to exit inner text mode.
7. Resize the text blocks, if necessary, to fit all text.
When you deselect the text object, the border becomes invisible.
Publication 2711-6.0
Creating Bar Graphs, Indicators, Numeric Displays
Numeric Data Displays
12–9
Numeric data displays provide a numeric readout of a value stored at
a controller tag address.
Types of Numeric Data Displays
Numeric data displays can display an actual value or a scaled value.
In addition, numeric displays can have:
• fixed or floating decimal point
• zero fill
• text
• time or date
If a value exceeds the specified field width for the numeric data
display, the overflow value is replaced with asterisks. Here are some
typical examples:
Pressure is
90 PSI
Pressure is
090 PSI
Pressure is
90.25
PSI
Value without zero fill
Value with zero fill
Value with decimal point
To add a date, time or text to a numeric data display, see Chapter 17.
Creating a Numeric Data Display
This section shows how to create a numeric data display.
To create a numeric data display:
1. Click the Numeric Data Display tool in the toolbox.
Or choose Numeric Data Display from the Objects menu.
2. Position the pointer (+) and click the left mouse button to place
the default size. Or drag the pointer to size the numeric display.
The object is automatically selected and contains # characters
representing a numeric variable.
3. To place another numeric data display, move the pointer to a new
location and click again.
4. Click the right mouse button to exit numeric data display mode.
Or click the selection tool on the toolbox.
Publication 2711-6.0
12–10
Creating Bar Graphs, Indicators, Numeric Displays
Setting Properties of a Numeric Data Display
To set the properties of a numeric data display:
1. Double-click the object.
Opens
Tag Dialog
2. Set the numeric display properties as defined on the next page.
3. When done, click OK.
Digits
The Field Width box specifies the maximum number of characters
(including 0-9 + - . ) that can appear in the display. The default is
6. If the value from the logic controller exceeds the specified field
width, the field on the terminal display fills with asterisks **** .
Unfilled data positions are left blank. To fill empty data positions
with zeroes, click the Fill with Zeroes check box.
Value to Display
65,932
Publication 2711-6.0
00065932
65932
8 Digit Maximum
Zero Fill
5 Digit Maximum
No Zero Fill
Creating Bar Graphs, Indicators, Numeric Displays
12–11
Decimal Point
A value may be stored as an integer, then scaled by the terminal so it
can be displayed as a decimal. See page 12–2 on scaling.
The Decimal Point area specifies whether a scaled value displays
with a fixed or floating point decimal.
SCALE
Scale = .0001
Offset = 94
Terminal Value=32767
32767 x (.0001) +94 =
Displayed Value=97.2767
• Select Fixed Point to position the decimal point 0 to 10 places to
the left of the rightmost character. A value of 0 displays a value
without a decimal point.
Select
For this position
Select
For this position
0
97
6
97.276767
1
97.2
7
97.2767676
2
97.27
8
97.27676767
3
97.276
9
97.276767676
4
97.2767
10
9.7276767676
5
97.27676
Note: If Position is 0, then the field width must be 2 > decimal
position for positive numbers. One position is used for the digit to
the left of the decimal and one for the decimal point. For negative
numbers the field width must be 3 > decimal position.
For example, to display the number –0.1234, set the field width to
7 and the decimal position to 4.
• Select Floating Point to have the terminal position the decimal.
Read Tag
Specifies the name of the tag address from which to read the display
data. If the tag doesn’t exist, enter a tag name. Edit the tag
definition using the Edit Tag button or the Tag Editor.
Valid data types for the read tag are unsigned/signed integer, 4BCD
and floating point.
Publication 2711-6.0
12–12
Creating Bar Graphs, Indicators, Numeric Displays
Multistate Indicators
Multistate indicators can show up to 2,000 states (including error
state). Each state can have unique inner text and/or a graphic with
different fill patterns.
Types of Multistate Indicators
Use multistate indicators for a variety of effects including limited
animation of displays.
OFF
LOW
FUEL
10 RPM
RUNNING
20 RPM
TEMP
CAUTION
HIGH
CAUTION
ÇÇÇ
ÇÇÇ
Standard Indicators
Multistate Indicator Using Different
Fill Patterns and Text for Each State
Multistate Indicator Using Different
Inner Graphics for Each State
Multistate Indicator Graphics and Text used to
Create an Animated Production Sequence
Inner text and/or graphics for multistate indicators are entered the
same as for multistate push buttons. For details on how to do this
and use other formatting options, see Chapter 17.
Publication 2711-6.0
Creating Bar Graphs, Indicators, Numeric Displays
12–13
Triggering an Indicator State
One of 3 data types can trigger the display of an indicator state:
• Single Bit
• Least Significant Bit
• Value
Single Bit
Single Bit is only valid for 2-state multistate indicators. The state is
controlled by the status of a single bit. Turning the tag address bit on
or off toggles the indicator display between state 0 and state 1.
Least Significant Bit
The terminal displays the state corresponding to the Least Significant
Bit (LSB) at the tag address data words (0 to 1,999 bits). More than
one bit may be set at the tag address allowing states to display in a
priority sequence (state 0 displays when bit 0 is ON, state 1 displays
when bit 1 is ON, ..., state 1,999 displays when bit 1,999 is ON).
An error state occurs when all bits are OFF (low). The message
defined for the error state (State E) displays, if defined. The default
message is “Error”.
The controller program must clear the last bit displayed. The next
time the terminal reads the tag address, the state corresponding to the
next least significant bit is displayed. The following example shows
what happens if bits 1 and 24 are set at tag address N7:2.
1
24
Tag Address N7:3=256 0 0 0 0 0 0 0 1 0 0 0 0 0 0 0 0
Tag Address N7:2=2 0 0 0 0 0 0 0 0 0 0 0 0 0 0 1 0
State #1 Displayed
1
24
Tag Address N7:3=256 0 0 0 0 0 0 0 1 0 0 0 0 0 0 0 0
Tag Address N7:2=0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
Controller Program Clears Bit 1
24
Tag Address N7:3=256 0 0 0 0 0 0 0 1 0 0 0 0 0 0 0 0
Tag Address N7:2=0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
State #24 Displayed
Value
The controller triggers a state when the tag address contains a
specific value. The specified state is displayed until the value at the
tag address is changed.
Publication 2711-6.0
12–14
Creating Bar Graphs, Indicators, Numeric Displays
Creating a Multistate Indicator
This section shows how to create a multistate indicator and edit its
properties.
To create a multistate indicator:
1. Click the Multistate Indicator tool in the toolbox.
Or choose Multistate from the Objects Indicators submenu.
2. Position the pointer (+) and click the left mouse button to place
the default size. Or drag the pointer to size the indicator.
3. To place another multistate indicator, move the pointer to a new
location and click again.
4. Click the right mouse button to exit multistate indicator mode.
Or click the selection tool on the toolbox.
Setting Properties of a Multistate Indicator
To set properties of a multistate indicator:
1. Double-click the indicator object.
Dimmed if terminal
does not have an
RS-232 printer port.
Opens
Tag Dialog
2. On the Properties tab, set operating parameters of the indicator.
Publication 2711-6.0
Creating Bar Graphs, Indicators, Numeric Displays
12–15
Read
Specifies the type of data that triggers the display of a state.
Select
To
Single Bit
Trigger a 2-state indicator by setting or clearing a bit at the
read tag address. The number of states must be set to 2
before the single bit option is available.
Least Significant Bit
Trigger multiple states. Entries display in a sequence
corresponding to bits set at word address(es) starting with the
read tag address. The read tag data type is unsigned integer.
Value
Trigger a state based on a value at the read tag address.
Each state is linked to a different value.
Note: If using more than 16 states for the Least Significant Bit
(LSB) trigger, reserve up to 124 consecutive word addresses after the
tag address. Every 16 states = 1 word address, with up to 2,000
total states. The LSB will only use up to the word of the last state.
For the Value option, you must select the format of the data from the
Data Format list box. The data type of the read tag must be
compatible with the selected format for the application to validate.
Use this Format
With this Tag Data Type
Signed Integer
Signed Integer
4-BCD
4BCD
Binary
Hexadecimal
Octal
Unsigned Integer
ns ned Inte
er
Unsigned
Integer
or Bit Array
Trigger State 0 When:
If Single Bit was selected in the Read area, you must specify whether
State 0 triggers on Bit 0 or Bit 1.
Select
To
Bit 0
Trigger state 0 when bit is set to 0 and trigger state 1 when bit is set to 1
Bit 1
Trigger state 0 when bit is set to 1 and trigger state 1 when bit is set to 0
Read Tag
Specifies the name of the tag address that triggers the display of a
state. If the tag does not exist, enter a tag name. Edit the tag
definition using the Edit Tag button or the Tag Editor.
Print
Select the Print check box to print states as they are triggered. When
a state is triggered, the text associated with the state is printed on the
connected printer.
Publication 2711-6.0
12–16
Creating Bar Graphs, Indicators, Numeric Displays
Configuring States for a Multistate Indicator
Use the States tab to:
• edit text for each state
• enter a value for each state (if required)
• edit format options for each state
• insert a graphic for a state
• add or delete states as required
To configure states for a multistate indicator:
1. Click the States tab on the Multistate Indicator dialog.
A spreadsheet opens. Each row indicates an indicator state. The
default is 4 states (row 0 to row 3) and an error state (row E).
The fields in each row define visual characteristics for each state.
2. Edit the states as necessary.
3. Click OK to exit the Multistate Indicator dialog.
The Value field appears only if
Value was selected under
Read on the Properties tab.
Error State
Editing Number of States
A multistate indicator supports a maximum of 2,000 states (0 to
1,999). Use only the number of states required.
To add states to a multistate indicator:
1. Choose Append State from the popup menu.
A new state is added after the last state but before the error state.
2. Repeat step 1 for each state you want to add.
Each state you add is created with values from the last state. New
states are added without default text in the Text field.
Publication 2711-6.0
To delete states, select the row number and choose Delete State from
the popup menu.
Creating Bar Graphs, Indicators, Numeric Displays
12–17
Editing State Text
The Text field contains the text that will appear for each state. The
default text is the state number (ST 0). Double-click in the cell to
edit the text.
Other text fields control how the text is formatted for each state.
Entering State Values
If Value was selected in the Read area of the Properties tab, the Value
field appears for each state. This field defines the numeric value at
the read tag address that triggers the state to display.
The range of the value you enter must be within the range of the
Data Format selected on the Properties tab. The default value for
each state is the state number (0 to 1,999).
Data Format
Range
Binary➀
0000 0000 0000 0000 to
1111 1111 1111 1111
Unsigned Integer
0 to 65535
Signed Integer
-32768 to +32767
4-BCD
0 to 9999
Hexadecimal➀
0 to FFFF
Octal➀
0 to 177777
➀ Formats provided for data entry. The terminal does not display/transfer these formats.
Publication 2711-6.0
12–18
Creating Bar Graphs, Indicators, Numeric Displays
List Indicators
A list indicator is a scrolling list containing up to 255 entries with the
current list entry highlighted.
Types of List Indicators
List indicators are controlled by a bit or value at a controller address.
List Indicator Using Value Data
This example shows an indicator list using values from a tank level
sensor to display the status of a tank.
TANK LEVEL
1800 = 1/4 Full Display
Address N7:2
= Value 1800
Empty
1/4
1/2
Full
Controller
TANK LEVEL
Empty
Address N7:2
= Value 3600
3600 = 1/2 Full Display
Controller
1/4
1/2
Full
List Indicator With Bit Data
This example shows a list indicator used to display conditions
associated with on/off type controls such as limit switches. The list
displays the status of a robot arm based on the condition of four
proximity switches.
Sensor 4 = Off
Sensor 3 = Off
Arm Position
Controller
Full Extend
2/3 Extend
1/3 Extend
Retracted
Controller
Full Extend
2/3 Extend
1/3 Extend
Retracted
Sensor 2 = Off
Sensor 1 = On
Arm Position
Sensor 4 = On
Sensor 3 = Off
Sensor 2 = Off
Sensor 1 = Off
Publication 2711-6.0
Creating Bar Graphs, Indicators, Numeric Displays
12–19
Triggering a List Entry
One of 3 data types can trigger the display of a list indicator entry:
• Single Bit
• Least Significant Bit
• Value
Single Bit
Single Bit is only valid for a 2-entry indicator list. The highlighted
entry in a list is controlled by the status of a single bit. Turning the
tag address bit on/off toggles the highlight between the 2 list entries.
Least Significant Bit
The terminal highlights the entry corresponding to the Least
Significant Bit (LSB) at the tag address data words (0 to 254 bits).
Setting more than one bit at the tag address allows entries to display
in a priority sequence (state 0 is highlighted when bit 0 is ON, state 1
is highlighted when bit 1 is ON,..., state 254 is highlighted when bit
254 is ON).
An error state occurs when all bits are OFF (low). No entry in the
list is highlighted when an error occurs.
The controller program must clear the last bit displayed. The next
time the terminal reads the tag address, the list entry corresponding
to the next least significant bit is highlighted. The example below
shows what happens if bits 1 and 24 are set at tag address N7:2.
24
1
Tag Address N7:3=256 0 0 0 0 0 0 0 1 0 0 0 0 0 0 0 0
Tag Address N7:2=2 0 0 0 0 0 0 0 0 0 0 0 0 0 0 1 0
State 0
State 1
State 2
State 3
State #1 Displayed
24
Tag Address N7:3=256 0 0 0 0 0 0 0 1 0 0 0 0 0 0 0 0
1
Tag Address N7:2=0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
Controller Program Clears Bit 1
24
Tag Address N7:3=256 0 0 0 0 0 0 0 1 0 0 0 0 0 0 0 0
Tag Address N7:2=0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
State 24
State 25
State 26
State 27
State #24 Displayed
Value
The controller triggers a list entry when the tag address contains a
specific value. The entry is highlighted until the value at the tag
address changes.
Publication 2711-6.0
12–20
Creating Bar Graphs, Indicators, Numeric Displays
Creating a List indicator
This section shows how to create a list indicator.
To create a list indicator:
1. Click the List Indicator tool in the toolbox.
Or choose List from the Objects Indicators submenu.
2. Position the pointer (+) and click the left mouse button to place
the default size. Or drag the pointer to size the indicator.
3. To place another list indicator, move the pointer to a new location
and click again.
4. Click the right mouse button to exit list indicator mode.
Or click the selection tool on the toolbox.
Setting Properties of a List Indicator
To set properties of a list indicator:
1. Double-click the list indicator object.
Opens
Tag Dialog
2. On the Properties tab, set the operating parameters of the
indicator.
Publication 2711-6.0
Creating Bar Graphs, Indicators, Numeric Displays
12–21
Read
Specifies the type of data that triggers the display of a list entry.
Select
Single Bit
Least Significant Bit
To
Trigger a 2-entry list indicator by setting or clearing a bit at the
read tag address. The number of states must be set to 2
before the single bit option is available.
Trigger multiple entries. Entries display in a sequence
corresponding to bits set at word address(es) starting with the
read tag address.
The tag data type for least significant bit is unsigned integer.
Trigger a list entry based on a value at the read tag address.
Each entry is linked to a different value.
Value
Note: If using more than 16 entries for the Least Significant Bit
(LSB) trigger, reserve up to 15 consecutive word addresses after the
tag address. Every 16 entries = 1 word address, with up to 255 total
entries. The LSB will only use up to the word of the last entry.
For the Value option, you must select the format of the data from the
Data Format list box. The data type of the read tag must be
compatible with the selected format for the application to validate.
Use this Format
Signed Integer
4-BCD
IEEE Float
Binary
Hexadecimal
Octal
Unsigned Integer
With this Tag Data Type
Signed Integer
4BCD
IEEE Float
Unsigned
ns ned Integer
Inte er
or Bitt Array
rray
Trigger State 0 When:
If Single Bit was selected in the Read area, you must specify whether
entry 0 triggers on Bit 0 or Bit 1.
Select
Bit 0
Bit 1
To
Trigger entry 0 when bit is set to 0 and trigger entry 1 when bit is set to 1
Trigger entry 0 when bit is set to 1 and trigger entry 1 when bit is set to 0
Read Tag
Specifies the name of the tag address the terminal reads to highlight
a displayed entry. If the tag does not exist, enter a tag name. Edit the
tag definition using the Edit Tag button or the Tag Editor.
Publication 2711-6.0
12–22
Creating Bar Graphs, Indicators, Numeric Displays
Configuring Entries of a List Indicator
Use the States tab to:
• edit and format text for each list entry
• enter a value for each list entry (if required)
• add or delete entries as required
To configure entries of a list indicator:
1. Click the States tab on the List Indicator dialog.
A spreadsheet opens. Each row indicates an entry in the indicator
list. The default is 16 entries (row 0 to row 15).
The fields in each row define the text that will appear for each
entry and how it will be formatted.
2. Edit the entries as necessary.
3. Click OK to exit the List Indicator dialog.
The Value field appears only if
Value was selected under
Read on the Properties tab.
Editing Number of Entries
A list indicator supports a maximum of 255 entries (0 to 254). Use
only the number of entries required.
To add entries to a list indicator:
1. Choose Append State from the popup menu.
A new entry is added after the last entry.
2. Repeat step 1 for each entry you want to add.
Each entry you add is created with the defaults from Entry 0.
Publication 2711-6.0
To delete entries, select the row number and choose Delete State
from the popup menu.
Creating Bar Graphs, Indicators, Numeric Displays
12–23
Editing List Text
The Text field contains the text that will appear for each entry in the
List Indicator. Double-click on the field and edit the text.
Other text fields control how the text is formatted for each state:
• text size (the default varies for each terminal type, the selection
applies to entire list)
• underline (default is off)
• text blink (default is off)
• left, right or center alignment (default is left)
• foreground color (default is white for color and grayscale
terminals, black for monochrome terminals)
Entering State Values
If Value was selected in the Read area of the Properties tab, the Value
field appears for each state. This field defines the numeric value at
the read tag address that triggers a specific entry to be highlighted.
The range of the value you enter must be within the range of the
Data Format selected on the Properties tab. The default value for
each entry is the entry number (0 to 254).
Data Format
Range
Binary①
0000 0000 0000 0000 to 1111 1111 1111 1111
Unsigned Integer
0 to 65535
Signed Integer
-32768 to +32767
IEEE Float
-99,999,997,952 to +999,999,995,904
4-BCD
0 to 9999
Hexadecimal①
0 to FFFF
Octal①
0 to 177777
① Formats provided for data entry. The terminal does not display/transfer these formats.
Publication 2711-6.0
Creating Message Displays
Chapter Objectives
It contains the following sections:
Section
Helpful Hints
Page
Helpful Hints
13–1
Types of Messages
13–2
Triggering Messages
13–4
Error State
13–5
Creating a Message Display
13–6
Setting Properties of a Message Display
13–6
Configuring Messages
13–8
Creating an Object to Print Messages
13–10
When creating message displays:
• Messages should not cover control objects when displayed.
• Message displays support up to 2,000 messages (numbered 0 to
1999).
• Create message displays with the exact number of messages
required by the application. Don’t create blank messages.
• Message text is formatted and edited like other objects with inner
text.
• Message displays include an error state (State E) to notify the
operator when an error occurs while triggering a message.
• If screen space is limited, create a Print Only object. When
messages are triggered, they are printed rather than displayed on
the screen.
Publication 2711-6.0
13–2
Creating Message Displays
Types of Messages
Message displays present status information or instructions to an
operator.
Message displays can show different types of information including
the status of a process, operator prompts, time, date, numeric or
ASCII variable.
The following examples show status information for Tank #1.
*** TANK #1 LEVEL HIGH ***
*** TANK #1 LEVEL HIGH ***
*** TANK #1 LEVEL LOW ***
*** TANK #1 LEVEL LOW ***
Publication 2711-6.0
Creating Message Displays
13–3
Message displays can contain variable data. For details on how to
insert a variable in a message display, see Chapter 17.
*** TANK #1 LEVEL = 20 Gallons ***
*** TANK #1 LEVEL = 20 Gallons
Message displays can contain time and date information based on the
terminal’s real time clock. For details on how to insert a time/date
variable in a message display, see Chapter 17.
Automatic Shutdown at 12:30 AM
Automatic Shutdown at 12:30 PM
Publication 2711-6.0
13–4
Creating Message Displays
Triggering Messages
The 3 types of data that can trigger a message to display are:
• Single Bit
• Least Significant Bit
• Value
Single Bit
Single Bit is valid only for 2-state message displays. The display is
controlled by the status of a single bit. Turning the tag address bit on
or off toggles the display between message 0 and message 1.
Least Significant Bit
When Least Significant Bit is selected, the terminal displays the
message corresponding to the Least Significant Bit (LSB) at the tag
address data words (0 to 1,999 bits). More than one bit may be set at
the tag address allowing messages to display in a priority sequence
(message 0 displays when bit 0 is ON, message 1 displays when bit 1
is ON, ..., message 1,999 displays when bit 1,999 is ON.)
An error state occurs when all bits are OFF (low). The message
defined for the error state (State E) displays, if defined. The default
message is “Error”.
The controller must clear the last bit displayed. The next time the
terminal reads the tag address, the message corresponding to the next
least significant bit is displayed. The following example shows what
happens if bits 1 and 24 are set at tag address N7:2.
Tag Address N7:3 = 256
24
0 0 0 0 0 0 0 1 0 0 0 0 0 0 0 0
1
Tag Address N7:2 = 2 0 0 0 0 0 0 0 0 0 0 0 0 0 0 1 0
Automatic Shutdown at 13:33
Message #1 Displayed
Tag Address N7:3 = 256
24
0 0 0 0 0 0 0 1 0 0 0 0 0 0 0 0
Tag Address N7:2 = 0
1
0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
Controller Program Clears Bit 1
Tag Address N7:3 = 256
24
0 0 0 0 0 0 0 1 0 0 0 0 0 0 0 0
Tag Address N7:2 = 0
0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
Pump 3 Overload
Message #24 Displayed
Value
When Value is selected, the controller triggers a message when the
tag address contains a specific value. The message is displayed until
the value at the tag address is changed.
Publication 2711-6.0
Creating Message Displays
Error State
13–5
Message displays have an error state to notify an operator when data
is out of range or unavailable.
You cannot delete the error state. The only way to access the error
state is to select the object and then select state E from the State box
on the tool bar. The inner text that appears in the object for state E is
Error. You can assign different inner text or display attributes to the
error state.
State 0
TANK LEVEL HIGH
State 1
TANK LEVEL LOW
State E
ERROR
Default Inner Text
for Error (E) State
Publication 2711-6.0
13–6
Creating Message Displays
Creating a Message Display
This section shows how to create a message display.
To create a message display:
1. Click the Message Display tool in the tool box.
Or choose Message Display from the Objects submenu.
2. Position the pointer (+) and click the left mouse button to place
the default size. Or drag the pointer to size the display.
3. To place another message display, move the pointer to a new
location and click again.
4. Click the right mouse button to exit message display mode.
Or click the selection tool on the toolbox.
Setting Properties
of a Message Display
To set properties of a message display:
1. Double-click the message display object.
Dimmed if terminal
does not have an
RS-232 port.
Opens
Tag Dialog
2. On the Properties tab, set the operating parameters of the message
display.
Publication 2711-6.0
Creating Message Displays
13–7
Read
Specifies the type of data that triggers a message to display.
Select
To
Single Bit
Trigger a 2-message display by setting or clearing a bit at the
read tag address. The number of states must be set to 2
before the single bit option is available.
Least Significant Bit
Trigger multiple messages. Messages display in a sequence
corresponding to bits set at word address(es) starting with the
read tag address.
The tag data type for least significant bit is unsigned integer.
Trigger a message based on a value at the read tag address.
Each message is linked to a different value.
Value
Note: If using more than 16 messages for the Least Significant Bit
(LSB) trigger, reserve up to 124 consecutive word addresses after the
tag address. Every 16 messages=1 word address (maximum of 2,000
messages). The LSB only uses up to the word of the last message.
For the Value option, you must select the format of the data from the
Data Format list box. The data type of the read tag must be
compatible with the selected format for the application to validate.
Use this Format
With this Tag Data Type
Signed Integer
Signed Integer
4-BCD
4BCD
Binary
Hexadecimal
Octal
Unsigned Integer
ns ned Integer
Inte er
Unsigned
or Bitt Array
rray
Trigger
If Single Bit was selected in the Read area, you must specify whether
message 0 (state 0) triggers on Bit 0 or Bit 1.
Select
To Trigger
Bit 0
Message 0 when bit is set to 0 and trigger message 1 when bit is set to 1.
Bit 1
Message 0 when bit is set to 1 and trigger message 1 when bit is set to 0.
Read Tag
Specifies the name of the tag address that triggers a message. If the
tag doesn’t exist, enter a tag name. Edit the tag definition using the
Edit Tag button or the Tag Editor.
Print
Select the Print check box to print messages as they are triggered.
When a state is triggered, the text associated with the state is printed
on the connected printer.
Publication 2711-6.0
13–8
Creating Message Displays
Configuring Messages
Use the States tab to:
• edit and format text for each message
• enter a value to trigger each message (if required)
• insert a graphic for each message
• edit format options for the the message display
• add or delete the number of messages for the display
To configure messages:
1. Click the States tab on the Message Display dialog.
A spreadsheet opens. Each row represents a message. The default
is 2 messages (row 0 and row 1) and an error state (row E).
The fields in each row define the message text and the visual
characteristics of each message.
2. Edit message fields as necessary
3. Click OK when done to exit the Message Display dialog.
The Value field appears only
if Value was selected under
Read on the Properties tab.
Error State
Editing Number of Messages
A message display supports a maximum of 2,000 messages (0 to
1,999). Use only the number of messages required.
To add messages to a message display:
Choose Append State from the popup menu for each message you
want to add.
A new message is added after the last message but before the error
state. Each state you add is created with the defaults of message 0.
To delete a message, select the row number of the message you want
to delete and choose Delete State from the popup menu.
Publication 2711-6.0
Creating Message Displays
13–9
Entering Message Text
The Text field contains the text that will display for each message.
Double-click in the cell and replace the default text (Msg 0) with the
new message text.
Other text fields control how the text is formatted.
• text size (default size varies for each terminal type)
• underline (default is off)
• text blink (default is off)
• left, right or center alignment (default is left)
• foreground color
To insert variables in a message:
1. Position the cursor in the text where you want to insert the
variable.
2. From the popup menu, choose Time, Date, Variable, or ASCII
from the Embedded Variable submenu.
A placeholder is inserted in the message for the time and date
variable (/*T*/ for time or /*D*/ for date). The time and date are
formatted using the settings in the Terminal Setup dialog.
A dialog opens when Variable or ASCII is selected, allowing you
to format how the numeric or ASCII variable will display (see
page 17–14 and 17–16). When you exit this dialog a placeholder
is inserted in the message with embedded formatting details.
Entering State Values
If Value was selected in the Read area of the Properties tab, the Value
field appears for each message. This field defines the numeric value
at the read tag address that will trigger the message to display.
The range of the value you can enter must be within the range of the
Data Format selected on the Properties tab. The default value for
each message is the row number (0 to 1,999).
Data Format
Range
Binary➀
0000 0000 0000 0000 to 1111 1111 1111 1111
Unsigned Integer
0 to 65535
Signed Integer
-32768 to +32767
4-BCD
0 to 9999
Hexadecimal➀
0 to FFFF
Octal➀
0 to 177777
➀ Formats provided for data entry. The terminal does not display/transfer these formats.
Publication 2711-6.0
13–10
Creating Message Displays
Creating an Object
to Print Messages
You can create an object to send all triggered messages to a printer
rather than displaying them in a Message Display. Any variables
embedded within the message also print.
A print object has the same properties as a message display.
However, when configuring the message you enter only the text that
will print, no formatting options.
Print objects are not linked to specific screens like display objects.
Therefore, messages can be triggered any time an application is
running.
The print object is only supported on terminals equipped with an
RS-232 serial printer port.
To create an object that will only print messages:
1. Choose Print Only Object Setup from the Application menu.
2. Click the New button.
3. In the Create text box, enter a unique name (1 to 32 characters)
for the print object. The name can include spaces and symbols.
4. Click OK to open a dialog to configure the print object.
Print Only Messages do
not support Internal tags.
Publication 2711-6.0
Creating Message Displays
13–11
5. Configure the properties for triggering print messages. They are
identical to the Message Display on page 13–6.
6. Click the States tab.
Initially a Print Only Object is created with 2 messages and one
error state.
The Value field appears only
if Value was selected under
Read on the Properties tab.
7. Choose Append State from the popup menu for each message you
want to add to the print object. Use the exact number required.
8. If the Value field appears for each message, enter the value that
will trigger the message to print.
9. In the Text field, enter the text that will print when the message is
triggered. To insert a time, date or numeric variable in a message,
choose an Embedded Variable option from the popup menu.
10. Click OK when done to exit dialog.
The Print Only Object Setup dialog reopens. The print object just
created now appears in the Existing Objects list.
11. Click OK to exit dialog.
Publication 2711-6.0
13–12
Creating Message Displays
Managing Print Objects
To:
Do this:
Edit a print object
1. From the list of Existing Objects, select the print object
you want to edit.
2. Click the Edit button to open the print object’s dialog.
3. Edit the Properties tab (if necessary).
4. Click the States tab to edit the text (and variables)
associated with the print object.
5. Click OK to exit the print object dialog.
Rename a print object
1. From the Existing Objects list, select the name of the print
object you want to rename.
2. Click the Rename button.
3. In the dialog that opens, enter a new 1 to 32 character
name for the print object. The name can include spaces
and symbols.
4. Click the OK button.
The print object appears in the Existing Objects list under the
new name; not the old.
Copy a print object
1. From the Existing Objects list, select the name of the print
object you want to copy.
2. Click the Copy button.
3. In the dialog that opens, enter a new 1 to 32 character
name for the copied print object. The name can include
spaces and symbols.
4. Click the OK button.
Two versions of the print object now exist; one under the
original name and one under the new name.
Delete a print object
Edit the properties of the copied print object as described
above.
1. From the list of Existing Objects, select the print object you
want to delete.
2. Click the Delete button. You are asked to confirm the
deletion.
3. Click Yes.
All tag definitions associated with the print object are
permanently removed.
Publication 2711-6.0
Using Global Objects
Chapter Objectives
This chapter contains the following sections:
Section
What is a Global Object?
Page
What is a Global Object?
14–1
Defining a Global Object
14–4
Using a Global Object
14–5
Moving and Resizing a Global Object
14–6
A global object is a single object that can be referenced on multiple
screens in an application. A global object is created and stored once
regardless of the number of times it is used.
For example, if you want to use the same control or display object on
different screens, define the object as a global object. You can
reference a global object from any screen (without recreating it).
The benefits of using a global object are:
• reduced development time
Reference a global object on multiple screens without having to
recreate the object. When properties of a global object are edited,
all instances of that object are automatically updated.
• reduced application size
Global objects reduce memory because they are stored once
regardless of the number of links to it. Only one copy of a global
object is downloaded to the terminal.
Publication 2711-6.0
14–2
Using Global Objects
Each object placed on an application screen has a corresponding:
• device object – defines the properties of the object.
• screen object – defines the screen position and input type (touch
cell or function key) of the object.
Application
Screen 1
Screen 2
Screen
Object 1
Screen
Object 2
Device
Object
Device
Object
The following illustration shows how an object is reused globally.
Application
Screen 1
Screen 2
Screen 3
Screen
Object 1
Screen
Object 2
Screen
Object 3
Object
• Object on Screen 1 was initially created with a device object
(defining object properties) and a screen object (defining screen
location and input type).
• Object on Screen 1 was defined as a global object by clicking the
Mark for Global Selection in the object’s Options dialog.
• Global object is reused on Screen 2. Global objects are accessed
from Global Objects dialog. A screen device was created linking
the global object to the new screen.
• Global object is reused again on Screen 3. Another screen device
was created linking the global object to the new screen.
If the properties of a global object are changed, all other links to that
object are also updated.
Publication 2711-6.0
Using Global Objects
14–3
Copying an Object
When copying an object to another screen, a new object is created
with the same properties and also updated screen information. The
original object and the copied object are two unique objects.
Changes to the original object do not affect the copied object.
Application
Screen 1
Screen
Object 1
Device
Object
Screen 2
Screen 3
Screen
Object 2
Screen
Object 2
Device
Object
Device
Object
Publication 2711-6.0
14–4
Using Global Objects
Defining a Global Object
This section shows how to define an object for global use. Defining
an object for global use adds it to the Global Object dialog. From
this dialog, you select a global object and place it on a screen.
Note: Each control object must have a unique write tag unless the
object is defined as a global object. If you create separate but
identical control objects on different screens with the same write tag,
the application will not validate.
To define an object for global use:
1. Click the Options tab from the dialog of the selected object.
2. Check the Mark for Global Selection check box, indicating the
object is available for global selection. The object is added to a
list of objects available for global use. The next section shows
how to access global objects.
To disable the global setting, clear the check box.
3. When done, click OK to exit the object’s dialog.
To define a group of objects available for global use:
1. Group the objects.
2. Double-click the group or select the group and press ENTER to
open the Options dialog.
3. Check the Mark for Global Selection check box, identifying the
group as available for global selection. To disable the global
setting, clear the check box.
4. Click OK to exit the dialog.
Note: The first few characters of the Description text will appear in
the Global Objects list to help identify the grouped global selection.
However, from screen to screen, you can enter a unique description
for each instance of a grouped global object.
Publication 2711-6.0
Using Global Objects
Using a Global Object
14–5
This section shows how to access a global object. Remember, you
can access a global object from any screen in an application.
You cannot use the same global object more than once on a screen.
You can, however, use different global objects on a screen.
Global objects cannot be copied and pasted. You must place a global
object on a screen using the Global Object command.
To select and place a global object:
1. Click the Global Object tool in the toolbox.
Or Choose Global Object from the Objects menu.
The Global Object dialog opens. The Control box lists all objects
marked for global use from the Options dialog. Each global
object is identified by its tag name, object ID and object type.
Objects without tag names are listed by object type.
Tag Name
Object ID
Object Type
2. Select a global object from the Control list box and click OK.
Or double-click the global object.
3. Position the pointer (+) where you want to place the object.
Global objects can have different locations on different screens.
4. Click the left mouse button.
5. Click the right mouse button to exit global object mode.
Or click the selection tool on the toolbox.
Any changes to a global object, except for screen location and
function key assignment, apply to all instances of that object. A
global object can have different function key and/or touch cell
assignments from screen to screen.
Publication 2711-6.0
14–6
Using Global Objects
Moving and
Resizing a Global Object
This section shows the effects of moving and sizing a global object.
You can change the location of a global object on one screen without
affecting its location on another screen. Location is not a global
attribute. When you resize a global object on one screen, it is resized
on all other screens because size is a global attribute.
Resizing a global object
When the global object on Screen 1 is resized, it is also resized on
Screen 2.
Screen 1
Screen 2
Moving a global object
When the global object on Screen 1 is moved, the object on Screen 2
retains its original position.
Screen 1
Screen 2
Resizing and moving a global object.
When the global object on Screen 1 resized and moved, the object on
Screen 2 retains its original location (as defined by the upper left
corner) but is resized.
Screen 1
Publication 2711-6.0
Screen 2
Creating Alarms
Chapter Objectives
This chapter contains the following sections:
Section
Overview of Alarms
Page
Overview of Alarm System
15–1
Creating the Alarm Banner
15–6
Creating an Alarm List
15–9
Configuring Global Alarm Parameters
15–12
Defining Alarm Triggers
15–14
Creating Alarms
15–16
Defining Optional Tags for Triggers
15–22
Defining Remote Tags used by Controller
15–26
Alarm Examples
15–28
The alarm system in PanelView notifies an operator when specific
trigger values appear at specific controller addresses.
Before the terminal can display alarms, you must:
• define the alarms in your application
• program the logic controller to generate the alarms
!
ATTENTION: Do not rely on your terminal as a
primary warning device in applications that could
result in physical injury, product damage or significant
process down time.
All critical alarm indications and any critical logic
controller responses must employ redundant and
hard-wired or mechanical interlocks.
In PanelBuilder, you define a series of alarms. For each alarm, you
define a message and a trigger value. You can also specify whether
the alarm must be acknowledged, displayed and/or printed.
You must also define the trigger tag that links the alarm messages
and the controller program. The program monitors values for alarm
conditions. When the program detects an alarm condition, it sets the
bit or value at the address defined by the trigger tag. The terminal
reads this value and triggers the corresponding alarm.
For example, to monitor the level of a tank, define an alarm with a
trigger value of 1 and the message text “Tank too Full”. Then
program the controller to set the bit (1) at the trigger address when
the tank is full. This triggers the message “Tank too Full”.
Publication 2711-6.0
15–2
Creating Alarms
Alarm Banner
The Alarm Banner is an optional display that pops up over the
current screen when an alarm is triggered. The banner contains a
message describing the alarm condition and alarm buttons
(acknowledge alarm, clear alarm) which allow the operator to act on
the alarm.
When alarms are triggered, they are added to an Alarm List. When
the alarm in the banner is acknowledged or cleared, the next alarm is
displayed. The banner displays messages in chronological order
(oldest triggered alarm to most recent triggered alarm).
The Alarm Banner is a global display that is created once in an
application, but appears in the same place on every screen. Only
alarms configured to display, when triggered, appear in this popup.
You can configure which objects are disabled when the Alarm
Banner is displayed. The options are:
• all screen objects are disabled (default) or
• only covered objects are disabled
Below is a sample Alarm Banner with all of the alarm objects.
Sample Alarm Banner
Alarm Message
(Required)
Oven Temperature too High
Clear
Ack
Alarm Buttons
(Optional)
Alarm Banner
(Optional)
Print
Clear
Ack
Alarm
Alarm
List
Alarm
List
All
06/19/96
16:55
Oven T*
06/19/96
16:30
LS101 *
✓ 06/18/96
✓
Print
06/18/96
15:00 06/18/96
15:03
Oven T*
15:10 06/18/96
15:13
Tank O*
Alarm List
(Optional)
Screen
Background
Clearing the Alarm Banner
The Alarm Banner remains on the terminal display until:
• the operator presses the Acknowledge button
• the operator presses the Clear button
• the operator presses the Ack All button
• the controller acknowledges the alarm
• the controller clears the alarm
• the terminal enters Configuration Mode
Publication 2711-6.0
Creating Alarms
15–3
Alarm Buttons
You can place alarm buttons in the Alarm Banner which allow the
operator to act on the alarm. Some of the buttons appear only in the
Alarm Banner, while others can also appear on other screens.
This button:
Ack
Does This:
Any
Screen
Acknowledges receipt of the alarm currently displayed in
the Alarm Banner.
Pressing the Ack button removes the Alarm Banner from
the terminal display but does not clear the alarm
condition. The alarm is marked acknowledged in the
Alarm List.
Clear
Alarm
Banner
Note: The highlighted alarm in the Alarm List is not the
acknowledged alarm, but the most recent alarm. The
acknowledged alarm may not be visible.
Clears the Alarm Banner from the terminal display without
acknowledging the alarm. Pressing the Clear button does
not clear the alarm condition.
✓
✓
If no alarms are configured for acknowledgement, then the
Alarm Banner must contain a Clear button.
Print
Prints the current message in the Alarm Banner. This
button operates on a single alarm. With each message,
you can print:
• alarm date and time
• acknowledge date and time
• trigger value
✓
Only terminals equipped with an RS-232 printer port
support the Print Alarm button.
Ack
All
You can also configure an alarm message to automatically
print when triggered.
Acknowledges all alarms in the Alarm List that have not
been acknowledged.
Pressing the Ack All button removes the Alarm Banner
from the terminal display but does not clear the alarm
conditions. Each alarm is marked acknowledged in the
Alarm List.
Clear
Alarm
List
Clears the Alarm List. Also clears the Alarm Banner even
though the alarm condition may still exist. The Alarm List is
automatically cleared when an application is downloaded.
✓
✓
✓
✓
✓
✓
A warning message is displayed asking the operator to
confirm or abort the clear operation.
Print
Alarm
List
Prints all alarms in the Alarm List. With each alarm
message, you can print:
• alarm date and time
• acknowledge date and time
• trigger value
Only terminals equipped with an RS-232 printer port
support the Print Alarm List button.
Publication 2711-6.0
15–4
Creating Alarms
Alarm List
06/19/96
16:55 Oven Temp High
06/19/96
16:30 LS101 Triggered
✓ 06/18/96
✓
06/17/96
15:00 Oven Temp High
15:00 Tank Overflow !!!!
The Alarm List records information on triggered alarms. The
maximum number is 100 or as many alarms (up to 100) the terminal
can hold in nonvolatile RAM. You can set the number of alarms
stored in the Alarm List (1-100). The default is 25.
The Alarm List can be used multiple times in an application. It can
appear in the Alarm Banner and on other application screens.
Each time an alarm is triggered, it is added to the Alarm List. The
most recent alarm is displayed at the top of the list.
Each alarm can be configured to occupy multiple lines in the Alarm
List. The following data displays for each alarm, in the order shown:
• acknowledge indicator (required)
✓ = Acknowledged Alarm
= Unacknowledged Alarm
= No Acknowledgement Required
•
•
•
•
alarm date and time (optional)
acknowledge date and time (optional)
alarm trigger value (optional)
alarm text including variables (required)
If the Alarm List is full when an alarm is triggered, the most recent
alarm is added to the top of the list and:
• the oldest alarm not requiring acknowledgement is removed from
the list (this includes alarms that have been acknowledged or
alarms that do not require acknowledgement).
• if all alarms not requiring acknowledgement have been removed,
then the oldest alarm is removed.
If a permanent Alarm List is required, use the Print Alarm List
button to print the Alarm List on a regular basis, or configure alarms
to print on occurrence.
The operator can acknowledge an alarm in the Alarm List by using
the up or down arrow keys on the terminal to select an alarm and
then pressing the Enter key.
Touch screen terminals require List keys to move the cursor up and
down the Alarm List. You can optionally use the Enter list key to
enable the operator to acknowledge an alarm in the list.
06/19/96
16:55 Oven Temp High
06/19/96
16:30 LS101 Triggered
✓ 06/18/96
optional
✓
06/17/96
15:00 Oven Temp High
15:00 Tank Overflow !!!!
List keys are accessed from the Objects List Keys submenu.
Publication 2711-6.0
Creating Alarms
15–5
Alarm List Examples
ACK Indicator
✓ = Acknowledged Alarm
= Unacknowledged Alarm
= No Acknowledgement Required
Cursor
06/19/96
06/19/96
✓ 06/18/96
✓ 06/18/96
16:55
16:30
15:00 06/18/96 15:03
15:00 06/18/96 15:03
ACK Indicator
Trigger Time and Date
16:55
16:30
✓ 15:00
✓ 15:00
ACK Time and Date
123456789.1
2001
400.00
600000
Oven T*
LS101 *
Oven T*
Tank O*
Alarm Message
Oven Temp High
LS101 Triggered
Oven Temp High
Tank Overflow !!!!
Trigger Value
Trigger Time
Alarm Message
123456789.1
2001
✓
400.00
✓
600000
Trigger Value
Oven Temp High 16:50
LS101 Triggered
Oven Temp High
Tank Overflow !!!!
Time Variable in Alarm Text
Alarm Message
2-Line Alarm List
06/19/96 16:55
Oven
Temp too High
06/19/96 16:30
LS101
Event Triggered due to Blockage
✓ 06/18/96 15:00 06/18/96 15:03 Oven
Temp too High
Alarm Text
wraps to second line
✓ 06/18/96 15:00 06/18/96 15:03 Tank
Overflow at Station 1
Trigger Time and Date
ACK Time and Date
Publication 2711-6.0
15–6
Creating Alarms
Creating the Alarm Banner
This section shows how to create the Alarm Banner for an
application. The alarm banner is created as a separate screen that is
global to all screens in the application. Control objects covered by
the banner are disabled when the banner displays on the terminal.
To create the Alarm Banner:
1. Choose Create Alarm Banner from the Screen menu.
The Alarm Banner screen opens. The default banner appears at
the top of the screen and is created with:
• one line alarm message display (cannot be deleted)
• Clear button
On color terminals, the default background color of the Alarm
Banner and alarm objects is red and the foreground color is white.
On grayscale terminals, the background is black and the foreground
is white. You can change these colors using the Color Palette.
Alarm Message Display
(Cannot be deleted)
Alarm Button
Screen
Background
The Alarm Banner can be moved and sized but cannot be sized
smaller than the objects on the banner itself.
2. Create other alarm buttons you want to appear in the Alarm
Banner by choosing the appropriate objects from the Objects Alarm Buttons submenu.
If the Alarm Banner is selected, you must deselect it before
selecting an object inside the banner. To deselect the banner,
click anywhere outside the banner.
3. On keypad terminals, double-click each Alarm object to open its
dialog and select the function key that will activate the button.
Touch cell input is automatically selected for touch screens.
Publication 2711-6.0
Creating Alarms
15–7
4. Choose Close from the Screen menu to Close the Alarm Banner
screen or double-click the Control-menu box on the screen.
The Alarm Banner appears in the Application File window as a
separate screen. It cannot be renamed like other screens.
Alarm Message Display
With the Alarm Message Display selected in the Alarm Banner, you
can access other alarm text in the application.
To scroll through alarm text in the application:
1. Select Alarm Message Display in the Alarm Banner.
2. Press the up and down arrow keys to scroll through available
alarm text.
To select alarm text to appear in the Alarm Message Display:
1. Double-click the Alarm Message Display in the Alarm Banner.
The Alarms tab (Alarm Setup dialog) opens.
2. Select the row number of the alarm text you want to appear in the
display.
3. Click OK to exit the Alarm tab.
The Alarm Message Display is updated with the selected text.
You can also create and edit alarm text directly from the Alarm
Message Display.
Publication 2711-6.0
15–8
Creating Alarms
Showing Alarm Banner Position
You can show the location of the Alarm Banner from any screen in
the application. By showing the banner, you can see which objects
are covered and which are not. This is important if you want to
disable only those objects that are covered by the banner or
to place objects on the screen where they will not be covered.
To toggle the Alarm Banner on or off:
Choose Alarm Banner Position from the View menu. A check mark
(n) next to the command indicates the banner is active.
The banner appears as a rectangle (white on color/grayscale
terminals and black on monochrome terminals). You cannot move or
size the banner unless you are in the Alarm Banner screen.
Publication 2711-6.0
Creating Alarms
Creating an Alarm List
15–9
The Alarm List operates like a control list selector. The Alarm List
can appear in the Alarm Banner or on another application screen.
Touch screen terminals require List keys to move the cursor up and
down the Alarm List. You can optionally use the Enter list key to
enable the operator to acknowledge an alarm in the list. The List
keys are accessed from the Objects List Keys submenu.
To create an Alarm List:
1. Choose Alarm List from the Objects menu.
2. Place and size the object.
The format of the entries in the Alarm List does not appear until
you create alarm text (Alarms tab/Alarm Setup dialog).
3. Double-click the object to open its dialog.
4. Under Display Fields, select:
• fields to display for each alarm. The fields are displayed in
the order shown with the alarm text appended to the fields.
• text size of the characters in the list (the text sizes vary for the
PanelView terminals).
• number of lines (1 to 9) to display for each alarm entry. The
maximum number of lines varies depending on the text size
and the size of the Alarm List object.
Publication 2711-6.0
15–10
Creating Alarms
5. Under Alarm Display Options, specify the alarm conditions and
acknowledge statuses to appear in the list.
Initially, all options are enabled. This means all alarms are
displayed regardless of their condition or state providing the
terminal buffer has space.
Important:
Each Alarm List must display at least one alarm
condition and one acknowledge status. If you
deselect all check boxes, an error message
appears.
For Alarm Conditions, you can display:
• active alarms – whose trigger conditions have been met. This
option is only appropriate for bit triggered alarms.
• inactive alarms – that were triggered but no longer meet their
trigger condition or were cleared.
For Acknowledge Status, you can display the following statuses
of alarms (in the terminal):
• acknowledged alarms
• unacknowledged alarms
• no acknowledgement required
The next page shows examples of Alarm List configurations.
6. Under Input:
• select the function key to activate the list on keypad terminals
• disable or enable wrap around for the list cursor
Wrap around specifies whether the selection cursor moves to the
top or bottom of the list when the operator presses the up or down
arrow key on the first or last item in the list.
Publication 2711-6.0
Creating Alarms
15–11
Alarm List Examples
You can create multiple alarm lists to display specific types of
information for alarms.
• Active Alarms that have not been acknowledged.
When a bit triggered alarm is acknowledged in the terminal, the
alarm is automatically removed from the list.
If an active alarm is cleared or no longer meets its trigger
condition, it becomes inactive and is removed from the list. If the
alarm is triggered again, the original alarm is not reactivated. A
new instance of the alarm is created.
• Active Alarms that have been acknowledged.
When a bit triggered alarm in the terminal is acknowledged, the
alarm is automatically added to the list.
• Inactive Alarms that have been acknowledged.
When an unacknowledged alarm in the terminal is acknowledged,
the alarm is automatically added to the list.
For Alarm Lists with active alarms, when an active alarm becomes
inactive, it is automatically removed from the list.
Publication 2711-6.0
15–12
Creating Alarms
Configuring Global
Parameters for Alarms
This section shows how to configure global parameters that apply
to all alarms and alarm objects including:
• which screen objects to disable when Alarm Banner is displayed
• size of Alarm List and whether to clear the list on powerup
• data to print with alarm text when an alarm is printed
• acknowledge hold time and snapshot timeout
To configure global parameters for alarms:
1. Choose Alarm Setup from the Application menu.
2. Select the Setup tab.
Remote tags are used by the Controller
to acknowledge and clear all alarms.
The Remote Tags are enabled when
the Use Optional Fields box is checked.
This check box enables the
Remote tags and optional tag
fields on the Alarm Triggers tab.
See page 15–22.
3. Under Banner Popup, specify whether:
• covered objects or partially covered objects are disabled when
the Alarm Banner is displayed.
• all screen objects are disabled when the Alarm Banner is
displayed. This is the initial default.
Publication 2711-6.0
Creating Alarms
15–13
4. Under Alarm Lists, specify:
Clear Lists on Powerup
Select this option to clear all entries in Alarm Lists
when the terminal is reset or power cycled.
Size
Specify the maximum number of alarms to store in
the Alarm List. Select a value between 1 and 100.
The default is 25.
The maximum number of alarms actually stored
depends on nonvolatile RAM available in terminal.
5. Under Print Items, select the data to print with alarm text when:
• Print Alarm button is pressed
• Alarm is configured to automatically print when triggered
• Print Alarm List button is pressed
The print items are:
•
•
•
•
•
alarm date
alarm time
alarm acknowledge date
alarm acknowledge time
alarm trigger value
The items are printed in the order listed, with the alarm text
appended to the items.
To print alarms, your terminal must be equipped with an RS-232
printer port.
6. Under Time Values specify:
ACK Hold Time
Length of time the terminal holds the trigger value at
the address defined by the Acknowledge tag. The
hold time should exceed the scan time of the
controller to ensure that it is read at least once.
Hold time values are 0, 50, 250, 500, 750, or 1,000
milliseconds. The initial default is 500.
Length of time the terminal waits for the controller to
complete I/O scans when an alarm is triggered.
If the message contains embedded variables, the
controller may have to complete several scans.
Snapshot Timeout
Variables appear in the alarm message as ???? until
the data is read. If the data is not read before the
timeout occurs, the variable appears as **** .
The timeout is entered in seconds. The initial
default is 2 seconds.
7. Click OK to exit.
Publication 2711-6.0
15–14
Creating Alarms
Defining Alarm Triggers
This section shows how to define triggers for alarms. For each
trigger, you must define a:
• trigger tag (Controller address the terminal monitors for an alarm
trigger value. Most application use only one alarm trigger tag.)
• trigger type (Bit, LSBit, or Value)
Triggers are assigned to alarms in the Alarm Setup tab.
To create or edit alarm triggers:
1. Choose Alarm Setup from the Application menu.
Or double-click the Alarm Message Display in the Alarm Banner.
2. Select the Alarm Triggers tab.
Each alarm trigger is entered as a separate row in a spreadsheet.
The cells in each row define specific information for each trigger.
• to select a row, click the row number.
• to select a cell, click on the cell, or press TAB or arrow keys.
Some cells require you to enter text and some have drop-down
lists to select options.
Row
Cell or Field
Most operations are performed by clicking a row number and then choosing a
command from this menu.
3. Click the Trigger Tag field.
Select or enter a name for the address where the controller will
write a bit or value to trigger an alarm condition
While in the Trigger Tag field, choose Edit Tag from the popup
menu to edit the tag definitions. The Tag Form dialog opens.
When done, click OK to close the dialog.
The controller address of trigger tag must be the lowest address of
the corresponding alarms.
Publication 2711-6.0
Creating Alarms
15–15
4. In the Trigger Type field, select the type of trigger associated with
the Trigger Tag address.
Trigger Type
Description
Trigger an alarm as it occurs. Multiple alarms can be triggered at once.
The bit position can be within:
• a word (bit 0 to bit 15)
• a block of consecutive words. Reserve up to 16 consecutive words (bit
Bit
0 to bit 255) after the tag address.
Each bit that changes from 0 to 1 will trigger an alarm whose trigger value
corresponds to that bit. The controller program must reset each bit (0)
after the corresponding alarm is displayed.
Trigger an alarm in a priority sequence (least significant bit to most
significant bit) based on its bit position within:
LSBit
(Least Significant Bit)
• a word (bit 0 to bit 15)
• a block of consecutive words. Reserve up to 16 consecutive words (bit
0 to bit 255) after the tag address.
The lowest order bit that changes from 0 to 1 will trigger an alarm whose
trigger value corresponds to that bit. Higher order bits are ignored until
the lower order bit is cleared by the controller program.
Trigger an alarm based on a value at the Trigger Tag address. Trigger
values for alarms are defined on the Alarms tab.
Only one alarm can be triggered at a time for each trigger.
Value
5. To add additional triggers, choose Append Trigger from the
popup menu for each trigger you want to add.
Repeat steps 3 and 4 to define each trigger.
6. Select the Alarms tab to assign the triggers to alarm messages.
Trigger Operations
Many trigger operations are accessed from a menu. To open the
menu, hold down the right mouse button or type CTRL+M.
Select:
To:
Cut
Cut the selected trigger to the clipboard.
Copy
Copy the selected trigger to the clipboard
Paste
Paste the contents of the clipboard at the current row.
Insert and Paste
Paste the copied or cut trigger above the current row.
Append Trigger
Add a new trigger after the last trigger.
Insert Trigger
Insert a new trigger above the current trigger.
Delete Trigger
Permanently remove the current trigger.
Edit Tag
Open the Form View dialog while in the Trigger Tag field to
enter or edit a tag definition for the selected tag.
Move Trigger Up
Move the current trigger up one row.
Move Trigger Down
Move the current trigger down one row.
Use Optional Fields
Display additional tag fields that can be assigned to a trigger.
You can also enable the optional fields from the Setup tab.
Publication 2711-6.0
15–16
Creating Alarms
Creating Alarms
This section shows how to create alarms for an application. Each
alarm has the following attributes:
• alarm text (including time, date, numeric, or ASCII variable)
• value or bit to trigger alarm
• trigger tag (predefined on Alarm Triggers tab)
• whether alarm requires acknowledgement
• whether alarm is printed and/or displayed in the Alarm Banner
when triggered
• background/foreground colors of alarm text
The trigger tag, variables in text, and other alarm tags (if used) must
be in the same scan group.
To create or edit alarms:
1. Choose Alarm Setup from the Application menu.
Or double-click the Alarm Message Display in the Alarm Banner.
2. Select the Alarms tab.
Each alarm is entered as a row in a spreadsheet. Each row
contains cells or fields which define the attributes of the alarm.
• to select a row, click the row number.
• to select a cell, click on the cell, or press TAB or arrow keys.
Some cells require you to enter text, some have drop-down lists
and others have check boxes to enable/disable an option.
Filters alarms
by Trigger field.
Row
Opens the Use
Existing Text
dialog in Read
Only mode
Cell or Field
Most operations are performed by clicking a row number and then choosing a
command from this menu.
Sorts the
selected field
alphabetically
or numerically
3. Edit the alarm fields as necessary.
4. Add alarms by choosing Append Alarm from the popup menu for
each alarm you want to add.
5. When done, click OK to exit dialog or select another tab.
Publication 2711-6.0
Creating Alarms
15–17
Alarm Fields
Alarm Fields
Text
Description
Notes:
Enter the alarm text that will appear in the Alarm
Banner and Alarm List when the alarm is triggered.
Maximum characters = 255.
Value/Bit
Specify the value or bit offset the controller writes to
the Trigger Tag address when it detects an alarm
condition. This causes the alarm text to appear in the
Alarm Banner or Alarm List.
Trigger
Select the name of the trigger tag to associate with
the alarm text.
For Bit or LSBit, enter the bit offset from the trigger tag address that will trigger the alarm.
• valid range is 0 to 255 for bit, unsigned/signed
integer, or BCD data types. For bit array, the range
is the array size.
• 0 is a valid alarm message
For Value:
• valid range depends on data type of the trigger tag.
• 0 is reserved.
The trigger tag and its attributes are defined on the
Alarm Triggers tab.
Ack
Specifies whether the alarm text displayed in the
Alarm Banner must be acknowledged by an operator
or the controller.
Select the box to enable or disable the Ack option. An
X in the box enables acknowledgement. The Display
box must also be checked to acknowledge an alarm.
The text can include time, date or numeric variables.
Embedded variables must be in the same scan group
as the alarm tags.
The initial default is Ack disabled.
Print
Specifies whether the alarm text prints when the alarm
is triggered. The alarm text is printed with the print
options selected on the Alarms Setup tab.
Select the box to enable or disable the Print option.
An X in the box enables the Print option.
Display
Specifies whether the alarm text displays in the Alarm
Banner when the alarm is triggered.
Select the box to enable or disable the Display option.
An X in the box enables the display option. To
acknowledge an alarm, you must enable this option.
Foreground
Defines the foreground color of the alarm message.
• black is the default for monochrome terminals
• white is the default for color/grayscale terminals
Background
Defines the background color of the message.
• white is the default for monochrome terminals
• red is the default for color terminals
• black is the default for grayscale terminals
Text ID
Unique number assigned to alarm text.
The next available number is automatically generated
each time new alarm text is created.
The initial default is Print disabled.
The initial default is Display enabled.
Publication 2711-6.0
15–18
Creating Alarms
Value Triggered Alarms
This section shows an alarm setup using a Value type trigger.
Trigger values must not exceed the range of the data type selected for
the trigger tag (signed/unsigned integer, BCD).
The following setup shows 3 alarms (A,B,C) assigned to the alm_tag
trigger. The Trigger Type is Value. The Value/Bit field shows a
different trigger value (1, 2, 3) for each alarm. The value 0 is
reserved.
In the Tag Editor, the tag definition for alm_tag is:
Tag Name
Data Type
Tag Address
Node Name
alm_tag
Unsigned Integer
N15:0
SLC_1
When the value 1 is entered in N15:0, Alarm C is triggered. When
the value 2 is entered in N15:0, Alarm B is triggered and when the
value 3 is entered in N15:0, Alarm A is triggered.
Publication 2711-6.0
Creating Alarms
15–19
Bit or LSBit Triggered Alarms
This section shows an alarm setup using a Bit type trigger. The
value/bit range for a bit trigger is 0 – 255 (bit, signed/unsigned
integer, BCD data types). For bit array, the range is the array size.
If using the Ack tag, the value/bit range begins with 1, instead of 0.
The following setup shows 3 alarms (A,B,C) assigned to the alm_tag
trigger. The Trigger Type is Bit. In this case, the Value/Bit field is a
bit offset from the Trigger Tag address (not a value).
In the Tag Editor, the trigger tag definition for alm_tag is:
Tag Name
Data Type
Tag Address
Node Name
alm_tag
Bit
N15:0/0
SLC_1
This tag handles up to 256 consecutive bits/alarms (0 – 255),
N:15:0/0 to N15:15/15.
The controller address of the alarm trigger bit is the number in the
Value/Bit field plus the Trigger Tag address.
Trigger Tag Address + Value/Bit = Trigger Bit Address
• Alarm C triggers when N15:0/1 changes from 0 to 1.
1 + N15:0/0 = N15:0/1
• Alarm B triggers when N15:0/2 changes from 0 to 1.
2 + N15:0/0 = N15:0/2
• Alarm A triggers when N15:0/3 changes from 0 to 1.
3 + N15:0/0 = N15:0/3
For the LSBit trigger, an alarm triggers when the trigger bit changes
from 0 to 1 and all other bits between the Trigger Tag address and
the trigger bit address are cleared. If the Trigger Tag address is
N7:12/4 and the Value/Bit is 6, an alarm is triggered when N7:12/10
changes from 0 to 1. It is the only bit set between N7:12/4 and
N7:12/10 inclusive.
If N7:12/4 is 1 when N7:12/10 changes to 1, the alarm corresponding
to N7:12/10 will not trigger until N7:12/4 is reset to 0.
Publication 2711-6.0
15–20
Creating Alarms
Alarm Operations
Operations you can perform on alarms are accessed from a menu. To
open the menu, hold down the right mouse button or type CTRL+M.
Select:
To:
Cut
Cut selected cells, rows or columns to the clipboard.
Copy
Copy the selected cells, rows or columns to the clipboard
Paste
Paste the previously cut or copied cells, rows or columns to a
spreadsheet area.
Insert and Paste
Paste the copied or cut alarm above the current row.
Append Alarm
Add a new alarm after the last alarm. The alarm is created with
the next available number.
Insert Alarm
Insert a new alarm above the current alarm. The alarm is
created with the next available number.
Delete Alarm
Permanently remove the selected alarm.
Embedded Variable
Opens a submenu to insert a time, date or numeric variable in
the alarm Text. To edit a numeric variable, select Edit Variable.
Use Existing Text
Opens the Use Existing Text dialog allowing you to copy a
message to the current row.
New Text ID
Changes the ID number of the text to the next available
number.
Using Existing Text
When creating alarm text, you can create new text or reuse text that
already exists in the application.
Reusing text saves time and memory. Text is only stored once
regardless of the number times it is used.
To use existing text:
1. Select the row number of the alarm in which you want to copy
existing text.
2. Click the right mouse button and choose Use Existing Text from
the popup menu.
The Existing Text dialog opens (in Read Only mode).
3. Select the row number of the text you want to copy.
4. Click the Apply button.
5. Click Close.
Both the Text and Text ID number are copied to the row of the
selected alarm.
Publication 2711-6.0
You can also enter the number of an existing text string in the Text
ID field and the text will be copied.
Creating Alarms
15–21
Adding Variables to Alarm Text
In the Text field, you enter alarm text including a time, date or
numeric variable. Embedded variables must be within the same scan
group (40 words of the alarm tags).
To insert a time, date, numeric variable in a text string:
1. Double-click the Text field in which you want to insert a variable.
2. Position the cursor where you want to insert the variable.
3. From the popup menu, choose Embedded Variable Time, Date,
Variable, or ASCII.
For the Time and Date variable, a placeholder is inserted in the
text (/*T*/ for time, /*D*/ for date). The format of the time and date
is set in the Terminal Setup dialog.
A dialog opens when Variable (p. 17–14) or ASCII (p. 17–17) is
selected. The dialog defines the format of the variable in the text
string. When you exit the dialog, a placeholder is inserted within
the text with embedded formatting details.
To edit a numeric or ASCII variable:
1. Double-click the Text field of the alarm containing the variable.
2. Click on the numeric /*V:12 NOFILL FIX:0*/ or ASCII /*A:12 */
variable placeholder.
The embedded data within the placeholder will vary depending
on the options you selected in the Variable dialog.
3. From the popup menu, choose Embedded Variable Edit Variable.
4. Edit the settings in the Variable dialog.
5. When done, click OK to exit dialog.
The placeholder is updated with the new formatting details.
Important:
The tag which updates the numeric or ASCII variable
should be scanned with the alarm trigger.
To delete a variable:
Click on the placeholder and choose Cut from the popup menu, or
press BACKSPACE or DELETE.
Publication 2711-6.0
15–22
Creating Alarms
Defining Optional
Tags for Triggers
The Alarm Triggers tab has optional tag fields that you can enable
for each trigger:
• acknowledge (Ack) tag
• handshake tag used with trigger tag
• remote acknowledge (Ack) tag
• remote (Ack) handshake tag
• acknowledge all value
To define optional tags:
1. Enable the optional fields.
• On the Setup tab, select the Use Optional Fields check box (X
in box).
• Or on the Alarm Triggers tab, hold down the right mouse
button and choose Use Optional Fields from the popup menu.
Both the Remote tags on the Setup tab and the optional tag fields
on the Alarm Triggers tab are enabled.
If the Use Optional Fields check box is cleared, all of the optional
fields (and the Remote Tags on the Setup dialog) are disabled.
PanelBuilder ignores any data in these fields.
Optional Fields
2. In the tag fields, enter the tag names you want to use for each
optional function.
To edit the definition for each tag, select the tag name and click
the Edit Tag button. The Tag Form dialog opens. Edit the tag
definition and close the dialog.
3. In the Acknowledge All Value field, enter a value that will be
used when acknowledging multiple alarms for a trigger (or when
the controller acknowledges all active alarms).
4. Click another Setup tab or OK to exit Alarm Setup dialog.
Publication 2711-6.0
Creating Alarms
Optional Fields
Ack Tag
15–23
Tag Direction
Description
PanelView ➾ Controller
Name of address where the terminal writes a
value to notify the controller when an alarm
has been acknowledged.
The terminal writes the trigger value or bit
position value (Value/Bit field) of the trigger to
the Ack tag address when:
• operator presses Ack button
• operator presses Enter key to acknowledge
alarm in Alarm List
• controller writes a value or triggers a bit at
the Remote Ack tag address
The terminal writes the Acknowledge All value
to this address when:
• Ack All button is pressed
• Controller acknowledges all active alarms
using the Ack. All Alarm tag (Setup tab).
This tag is ignored if the Ack option is
disabled on the Alarms tab.
Notes:
The terminal clears the value at the Ack
tag address when the Ack or Ack All
button is released or the Acknowledge
Hold time has expired, whichever is longer.
Handshake Tag
(for Trigger)➀
PanelView ➾ Controller
Name of address where the terminal toggles
a bit to indicate that it received new Alarm
Trigger data from the controller.
This field is used in conjunction with the Trigger Tag.
Remote Ack Tag
Controller ➾ PanelView
Name of address where the controller
acknowledges one or all alarms for a trigger.
For Value Triggers, the controller writes the
alarm’s trigger value to the Remote Ack
address to acknowledge a single alarm.
The controller writes the Acknowledge All
value to the Remote Ack address to
acknowledge all alarms for a trigger.
If the controller is acknowledging alarms, it
is the responsibility of the controller
program to reset/clear the value at the
Remote Ack address. If the value is not
reset/cleared, the operator will not be able
to acknowledge alarms locally (at the
terminal).
Remote (Ack)
Handshake Tag ➀
Acknowledge All
Value
PanelView ➾ Controller
For Bit/LSBit triggers:
Remote Ack tag uses the same bit pattern as
the trigger tag. To acknowledge all alarms for
a trigger, the controller writes a 1 to the bit
position that is one greater than the last
trigger bit used (in the Value/Bit field).
If the Ack tag is not used, the controller can
acknowledge more than one alarm at a time.
If the Ack tag is used, the controller can only
acknowledge one alarm and must reset the
bit before acknowledging the next alarm.
Name of address where the terminal toggles
a bit to indicate that it received a new Remote
Acknowledge value from the controller.
Value written to the Ack tag or Remote Ack
tag address when all alarms are
acknowledged for a trigger.
• operator presses the Ack All button
• controller acknowledges all active alarms
using the Ack. All Alarm tag (Setup tab).
• controller acknowledges all alarms for a
trigger by writing the Acknowledge All Value
to the Remote Ack tag address.
For Value triggers, the value is written to the
Ack tag by the PanelView or Remote tag
address by the controller.
For Bit/LSBit triggers, the value is written to
the Ack tag address only.
The Remote Ack tag must be in the same
scan group as the alarm trigger.
This tag is used only in conjunction with
the Remote Ack tag.
The Acknowledge All Value can be any
value except for the trigger value assigned
to alarms. Do not use the value 0 since
PanelBuilder uses 0 as a reset value.
Each trigger may have a different
Acknowledge All Value.
➀ The PanelView terminal sets all handshake bits to 1 on powerup, regardless of whether an alarm is triggered or not.
Publication 2711-6.0
15–24
Creating Alarms
Using the Remote Ack Tag with Value Triggered Alarms
This section shows how the controller acknowledges one or all value
triggered alarms using the Remote Ack tag.
The following setup shows 3 alarms (A,B,C) assigned to the alm_tag
trigger. The Trigger Type is Value. The Value/Bit field shows a
different trigger value (1,2,3) for each alarm. The value 0 is reserved.
In the Tag Editor, alarm tag definitions are:
Tag Name
Data Type
Tag Address
Node Name
alm_tag
Unsigned Integer
N15:0
SLC_1
ack_tag
Unsigned Integer
N16:0
SLC_1
rem_ack
Unsigned Integer
N15:1
SLC_1
When the value 2 is entered at N15:0, Alarm B is triggered. When
the controller returns this trigger value to N15:1 (rem_ack tag
address), Alarm B is acknowledged. When the value 3 is entered at
N15:0, Alarm A is triggered. When the controller returns this value
to N15:1, Alarm A is acknowledged.
The Ack Tag must be a value/word address and returns the value of
the alarm. The PanelView will input a value when you or the
controller acknowledges an alarm.
Publication 2711-6.0
Creating Alarms
15–25
Using the Remote Ack Tag with Bit Triggered Alarms
This section shows how the controller acknowledges one or all bit
triggered alarms using the Remote Ack tag.
The following setup shows 3 alarms (A,B,C) assigned to the alm_tag
trigger. The Trigger Type is Bit. The contents of the Value/Bit field
is a bit offset from the Trigger Tag address.
One tag handles up to 256 consecutive bits/alarms (0 – 255), for
example, N:15:0/0 to N15:15/15.
In the Tag Editor, alarm tag definitions are:
Tag Name
Data Type
Tag Address
Node Name
alm_tag
Bit
N15:0/0
SLC_1
ack_tag
Unsigned Integer
N16:0
SLC_1
rem_ack
Bit
N15:16/0
SLC_1
When N15:0/2 changes from 0 to 1, Alarm B is triggered. Based on
the contents of the Value/Bit field, this is a 2 bit offset from the
Trigger Tag address (N15:0/0). When the controller writes a 1 to
N15:16/2 (rem_ack tag address), Alarm B is acknowledged.
To acknowledge all alarms for the alm_tag trigger, the controller
must write 1 to the bit position that is one greater than the highest
value in the Value/Bit field. For example, setting N15:0/4 to 1
acknowledges all alarms. If the highest value in the Value/Bit field
is 239 (N15:14/15), setting N15:15/0 to 1 acknowledges all alarms.
If you use the Ack Tag, the controller must acknowledge one alarm
at a time and reset the bit (0) before acknowledging the next alarm. If
you do not use the Ack Tag, the controller can acknowledge more
than one alarm at a time.
The Ack Tag must be a value/word address and returns the value of
the alarm, not the bit pattern. The PanelView will input a value
when you or the controller acknowledges an alarm.
Publication 2711-6.0
15–26
Creating Alarms
Defining Remote Tags
used by Controller
You can define optional tags that the controller will use to:
• acknowledge all active alarms
• clear all alarms in the terminal
These tags affect the alarm displayed in the Alarm Banner and
alarms in the Alarm List.
To define remote tags:
1. Select the Setup tab from the Alarm Setup dialog.
2. Select the Use Optional Fields check box (X in box).
The Remote Tags area of the dialog is made available for editing.
This check box also enables the display of optional tag fields on
the Alarm Triggers tab.
If the Use Optional Fields check box is cleared, the Remote tags and
the optional fields on the Alarm Triggers tab are disabled.
PanelBuilder ignores any data in these fields.
Check this box to enable the Remote
tags in this dialog and optional tags
on the Alarm Triggers tab.
3. Under Remote Tags, enter the tag names that you want the
controller to use to acknowledge or clear all alarms.
To edit the tag definition for each tag, select the tag name and
click the Edit Tag button. The Tag Form dialog opens. Edit the
tag definition and close the dialog.
4. When done, select another tab or click OK to exit dialog.
Publication 2711-6.0
Creating Alarms
Remote Tags
Ack. All Alarms Tag
Tag Direction
Controller ➾ Terminal
15–27
Description
Notes
Name of address where the controller sets
a bit (1) or value to acknowledge all active
alarms regardless of the trigger. The
terminal monitors this address for a
nonzero value.
The Ack tag and Acknowledge All Value for
alarm triggers are defined on the Alarm
Triggers tab.
When the terminal sees a nonzero value, it
writes the Acknowledge All Value defined
for each trigger to the Ack tag address
defined for each trigger.
While the Ack All Alarms address contains
a nonzero value, the operator cannot
acknowledge alarms locally (at the
terminal) if the Ack tag is defined.
The Alarm Banner is removed from the
terminal display and all alarms not
acknowledged in the Alarm List are flagged
as acknowledged.
The value is held at the Ack tag address
until the Acknowledge Hold Time expires
and the controller has cleared the Ack All
Alarms tag. It is the responsibility of the
controller’s program to clear the value.
Ack. All Handshake Tag
Terminal ➾ Controller
Name of address where the terminal
toggles a bit to indicate that it received the
Ack All Alarms value from the controller.
Clear All Alarms Tag
Controller ➾ Terminal
Name of address where the controller sets
a bit or nonzero value to clear all alarms in
the terminal.
This tag is optional and used only in conjunction with the Ack. All Alarms tag.
The Alarm Banner is removed from the
terminal display and all alarms are
removed from the Alarm List.
Clear All
Alarms Handshake Tag
Terminal ➾ Controller
Name of address where the terminal
toggles a bit to indicate that it received the
Clear All Alarms value from the controller.
This tag is optional and used only in conjunction with the Clear All Alarms tag.
Publication 2711-6.0
15–28
Creating Alarms
Alarm Examples
This section provides examples of different alarm configurations
ranging from simple to more complex.
Operator Acknowledges Alarm
In the example below, the operator presses the Ack button to
acknowledge an alarm. Because the Acknowledge tag is not defined
for the trigger, the controller is not notified. Optional Fields are not
enabled for the alarm triggers.
Alarm Configuration
– Four alarms are assigned to the Pump trigger tag, each with a different trigger value
– All alarm messages are configured to display in the Alarm Banner and must be acknowledged
➃ Operator presses Ack button
–Alarm Msg B is flagged acknowledged in the Alarm List
–Alarm Banner is cleared from display
➀ The PanelView reads the value 15 from the Trigger
(Pump) address in the controller. This value triggers alarm Msg B.
Msg B
Ack
➁ Alarm Msg B is placed in the List
Alarm List
Pump
Msg B
➂ Alarm Banner displays alarm text.
Msg B
Ack
Publication 2711-6.0
Creating Alarms
15–29
Operator Acknowledges Alarm and Notifies Controller
The operator presses the Ack button to acknowledge an alarm. The
terminal notifies the controller by writing the alarm’s trigger value to
the Ack address defined for the trigger. Optional Fields are enabled
for the alarm triggers.
Alarm Configuration
– Four alarms are assigned to the Pump trigger tag, each with a different trigger value
– All alarm messages are configured to display in the Alarm Banner and must be acknowledged
➄ The PanelView notifies the controller by writing the
alarm’s trigger value (15) to the Ack address (PumpAck)
defined for the trigger.
➀ The PanelView reads the value 15 from the Trigger
(Pump) address in the controller. This value triggers
alarm Msg B.
➃ Operator presses Ack button
–Alarm Msg B is flagged acknowledged in the Alarm List
–Alarm Banner is cleared from display
➁ Alarm Msg B is placed in the Alarm List
Msg B
Alarm List
Pump
Ack
Msg B
➂ Alarm Banner displays alarm text.
Msg B
Ack
Publication 2711-6.0
15–30
Creating Alarms
Controller Acknowledges a Single Alarm for a Specific Trigger
The controller acknowledges a single alarm activated twice by the
same trigger. The controller writes the alarm’s trigger value to the
Remote Ack address defined for the trigger. The terminal notifies
the controller that it acknowledged the alarm by writing the alarm’s
trigger value to the Ack address.
Optional Fields are enabled and defined for the alarm triggers.
Alarm Configuration
– 4 alarms are assigned to the Extruder1 trigger, each with a different trigger value
– 6 alarms are assigned to the Extruder2 trigger, each with a different trigger value
– All alarms messages are configured to display and must be acknowledged
– A Remote Ack tag and Ack tag are defined for each trigger
➃ The PanelView writes the trigger value 15 to the Ack
address (Ex1Ack) defined for the Extruder1 trigger.
➀ The controller acknowledges Msg B activated by the
➂ Both occurrences of Msg B activated by the Extruder 1
trigger are acknowledged in the Alarm List.
Extruder1 trigger by writing the alarm’s trigger value 15
to the Remote Ack address (Ex1RemoteAck) of the
trigger.
Alarm List
Extruder1
Extruder2
Extruder2
Extruder1
Extruder1
Extruder1
Extruder2
Publication 2711-6.0
Msg B – Acknowledged
Msg B
Msg E
Msg A
Msg D
Msg B – Acknowledged
Msg A
➁ The PanelView reads the value 15 from the Remote
Ack address in the controller.
Creating Alarms
15–31
Controller Acknowledges All Alarms for a Specific Trigger
The controller acknowledges all alarms activated by the same trigger.
The controller writes the Acknowledge All Value defined for the
trigger to the trigger’s Remote Ack address. The terminal notifies the
controller that it acknowledged all alarms for the trigger by writing
the Acknowledge All Value to the trigger’s Ack address.
Optional Fields are enabled and defined for the alarm triggers.
Alarm Configuration
– 6 alarms are assigned to the Extruder2 trigger, each with a different trigger value
– All alarm messages are configured to display and must be acknowledged
– A Remote Ack tag, Ack tag, and Acknowledge All Value are defined for each trigger
– 4 alarms are assigned to the Extruder1 trigger, each with a different trigger value
➃ The PanelView writes the Acknowledge All Value 99 to
the trigger’s Ack address (Ex1Ack).
➀ The controller acknowledges all alarms activated by the
Extruder1 trigger by writing the trigger’s Acknowledge All
Value 99 to the Remote Ack address (Ex1RemoteAck) of
the trigger.
➂ All alarms activated by the Extruder1 trigger are
acknowledged in the Alarm List.
Alarm List
Extruder1
Extruder2
Extruder2
Extruder1
Extruder1
Extruder1
Extruder2
Msg B – Acknowledged
Msg B
Msg E
Msg A – Acknowledged
Msg D – Acknowledged
Msg B – Acknowledged
Msg A
➁
The PanelView reads the value 99 from the Remote
Ack address in the controller.
Publication 2711-6.0
15–32
Creating Alarms
Controller Acknowledges All Alarms for all Triggers
The controller acknowledges all alarms in the terminal by setting a
bit or value at the Ack. All Alarms tag address. The terminal sees a
nonzero value at this address and then writes the Acknowledge All
Value for each trigger to the Ack address for each trigger.
Optional Fields are enabled on the Alarm Setup tab and the Alarm
Triggers tab.
Alarm Configuration
– 4 alarms are assigned to the Extruder1 trigger, each with a different trigger value
– 6 alarms are assigned to the Extruder2 trigger, each with a different trigger value
– All alarm messages are configured to display and must be acknowledged
– A Remote Ack tag, Ack tag, and Acknowledge All Value are defined for each trigger
– An Ack. All tag is defined on the Alarm Setup dialog. The controller uses this tag to acknowledge all alarms in the terminal
➃
The PanelView notifies the controller by writing
– Acknowledge All Value 99 for the Extruder1 trigger to the trigger’s Ack address (Ex1Ack)
– Acknowledge All Value 100 for the Extruder2 trigger to the trigger’s Ack address (Ex2Ack)
➀ The controller sets a bit at the Ack. All tag address
(RemoteAckAll), defined on the Alarm Setup tab, to
acknowledge all active alarms for all triggers.
➂ All alarms activated by the Extruder1 and Extruder2
triggers are acknowledged in the Alarm List.
Alarm List
Extruder1
Extruder2
Extruder2
Extruder1
Extruder1
Extruder1
Extruder2
Publication 2711-6.0
Msg B – Acknowledged
Msg B – Acknowledged
Msg E – Acknowledged
Msg A – Acknowledged
Msg D – Acknowledged
Msg B – Acknowledged
Msg A – Acknowledged
➁ The PanelView reads a nonzero value at the
RemoteAckAll address.
Adding Graphics
Chapter Objectives
This chapter shows how to add graphics and background text to
screens. It contains the following sections:
Section
Helpful Hints
Page
Helpful Hints
16–1
Graphic Objects
16–2
Graphic Tools
16–2
Drawing a Line
16–3
Drawing Connected Lines
16–4
Drawing Shapes
16–5
Freeform Drawings
16–6
Adding ISA Symbols
16–7
Adding Background Text
16–8
Importing/Exporting Bitmap Graphics
16–10
Using Background Graphics
16–16
When creating graphics, consider the following:
• Freehand drawings are memory intensive. For complicated
drawings, create a bitmap graphic of the drawing with another
source program and then import the graphic.
• Circles process more efficiently in the terminal than ellipses. Use
circles whenever possible.
• Imported bitmaps are handled like global objects. The terminal
stores only one copy of a bitmap image regardless of the number
of links to it in an application.
• Imported bitmaps cannot exceed the number of pixels supported
by the terminal display. Larger bitmaps are cropped.
• You can import/export monochrome or color bitmaps.
• On color terminals, full color bitmaps are imported as standard 16
EGA color images. If the bitmap contains more colors, each color
is mapped to one of the 16 standard colors.
• On grayscale terminals, full color bitmaps are imported as 4 color
(shades of gray) images.
• Color bitmaps are exported as they are stored in PanelBuilder. If
a full color bitmap was reduced to 16 or 6 colors when imported,
it is exported in the same format.
• When using graphics with control objects, use the Move Dynamic
Objects Front command after completing an application screen.
The screen will then appear the same as it would on the
PanelView terminal.
Publication 2711-6.0
16–2
Adding Graphics
Graphic Objects
PanelBuilder provides tools for drawing a variety of shapes: lines,
ellipses, circles, rectangles, squares, polygons (connected lines) and
freeform drawings.
Line
Circle
Polygon
Rectangle
Ellipse
Freeform
In addition, you can import bitmap graphics created with other
programs, use standard ISA symbols, and add text to screens.
The text tool lets you add text to a screen that’s not linked to an
object.
Graphics are created similar to control and display objects. Unlike
control and display objects, however, graphics can overlap.
Inside the display area of the screen, the pointer appears as a + to
indicate where a line or shape appears when you start drawing.
Graphic Tools
Graphics are created by selecting commands from the Objects
Graphics submenu or by selecting a tool from the toolbox.
Tool
Function
Draws a straight line.
Draws open connected lines or simple
polygons using connected straight lines.
Draws a rectangle or square.
Draws an ellipse.
Draws a freehand drawing.
Adds background text.
Adds a bar graph scale.
Opens a dialog for importing or exporting bitmap
graphics.
Places a background graphic image.
Publication 2711-6.0
Adding Graphics
Drawing a Line
16–3
Use the Line command or Line tool to draw straight lines. As you
draw a line, you can drag it to any size or angle.
To draw a line:
1. Click the Line tool in the toolbox.
Or choose Line from the Objects Graphics submenu.
2. Position the pointer (+) where you want to start the line.
3. Hold down the left mouse button and drag.
A line stretches from the starting point to the position of the
pointer, changing length and position as you move the mouse.
4. When the line is the right size, release the mouse button.
5. To draw another line, move the pointer to a new location and
repeat steps 3 and 4.
6. Click the right button to exit line mode.
Or click the selection tool on the toolbox.
Use foreground colors when applying color to lines.
Publication 2711-6.0
16–4
Adding Graphics
Drawing Connected Lines
Use the Connected Line command or tool to draw open connected
lines or shapes such as triangles and other simple polygons.
To draw connected lines:
1. Click the Connected Line tool in the toolbox.
Or choose Connected Line from the Objects Graphics submenu.
2. Position the pointer (+) where you want to anchor one end of the
first line and click the left mouse button.
3. Move the pointer where you want to end the line and start the
next line, and click the left mouse button.
You can adjust the position of the line before clicking.
4. Repeat step 3 for each line you want to draw.
5. After drawing the last line, double-click.
6. Click the right mouse button to exit connected line mode.
Or click the selection tool on the toolbox.
Publication 2711-6.0
Adding Graphics
Drawing Shapes
16–5
When drawing a shape you can drag it to any size, width or height.
Note: Circles process more efficiently than ellipses in the terminal.
Whenever possible use circles.
To create a shape:
1. Click the appropriate tool from the toolbox.
Creates a rectangle or square
Creates an ellipse or circle
Or choose Rectangle, Ellipse or Circle from the Objects
Graphics submenu.
2. Position the pointer (+) where you want to start drawing one
corner of the shape.
3. Hold down the left mouse button and drag the pointer to size the
shape. Release the mouse button when the shape is the right size.
When drawing a circle or ellipse, an imaginary rectangle
surrounds the object.
4. To draw another shape, move the pointer to a new location and
repeat step 3.
5. Click the right mouse button to exit shape mode.
Or click the selection tool on the toolbox.
To draw a square, hold down the
SHIFT key as you drag.
To draw a circle, hold down the
SHIFT key as you drag.
Publication 2711-6.0
16–6
Adding Graphics
Freeform Drawings
You can create your own freehand drawings.
To create a freeform drawing:
1. Click the Freeform tool in the toolbox
Or choose Freeform from the Objects Graphics submenu.
2. Position the pointer where you want to start drawing.
3. Hold down the left mouse button and drag the mouse while
drawing. When done drawing, release the left mouse button.
4. Click the right mouse button to exit freeform mode.
Or click the selection tool on the toolbox.
Freehand drawings are memory intensive. For complicated
drawings, create a bitmap graphic of the drawing with another source
program and then import the graphic.
Publication 2711-6.0
Adding Graphics
Adding ISA Symbols
16–7
PanelBuilder provides a set of standard ISA symbols that you can
add to a screen. They are accessed from the ISA Symbols toolbox.
See Appendix B for a description of each symbol.
ISA symbols can be moved but not sized.
To add an ISA symbol to a screen:
1. Click the symbol you want from the ISA Symbols toolbox.
2. Position the pointer (+) and click the left mouse button to place
the symbol.
The symbol is automatically selected.
3. Click the right mouse button to exit ISA Symbol mode.
Or click the selection tool on the toolbox.
You can also place ISA symbols inside a button or multistate object.
See Chapter 17 for details.
You can apply foreground and background colors to an ISA symbol.
Publication 2711-6.0
16–8
Adding Graphics
Adding Background Text
The text tool lets you add text to a screen that’s unattached or not
linked to an object. This is called background text. Examples of
background text are tick-mark labels for bar graph scales, outer text
for push buttons or control lists, time and date stamps, variable read
outs, screen titles and so on.
Background Text
0 lbs
10 lbs
TANK LEVEL CONTROL
Pump #3
F9
Off at 9:45 AM
20 lbs
30 lbs
ON
MOTOR
ON
40 lbs
Empty Tank
1/4 Fill Level
1/2 Fill Level
Fill Tank
50 lbs
Background text is handled as a separate object unless you group it
with other objects.
Background text can contain up to 255 characters using the default
text size and can appear anywhere on the screen. You can resize text
and use different types of emphasis such as underlining, blinking, or
toggling the foreground/background colors.
Text is entered using the same technique that’s used for objects that
contain inner text.
To create background text:
1. Click the Text tool in the toolbox.
Or choose Text from the Objects Graphics submenu.
2. Position the pointer and click the left mouse button to place the
default text block size. Or drag the pointer to size the text block.
The text object is selected and you are placed in inner text mode.
3. Enter text in the Text box.
As you enter text, it’s also entered in the block. If word wrap is
on, text wraps at the beginning of a word, not in the middle.
(Word Wrap is set from the Format menu.) An asterisk (*)
appears if the text exceeds the object size.
Publication 2711-6.0
Adding Graphics
16–9
– To delete text, drag the pointer over the text to highlight it,
then press BACKSPACE or DELETE.
– To replace text, drag the pointer over the text to highlight it,
then type the new text.
– To add text, position the cursor where you want to insert text
and then type the new text.
Press ENTER to start a new line. This character /∗ is inserted to
indicate a new line.
4. To create another text block, repeat steps 2 and 3.
5. Click the right mouse button to exit text mode.
Or click the selection tool in the toolbox.
6. When done, click the Inner Text tool to exit inner text mode.
When you deselect the text block, the border becomes invisible.
7. Resize the text blocks, if necessary, so that all text fits inside.
You can use formatting commands to change the appearance of text
while entering text or at a later time. For details on how to format
text or insert a time, date, or variable in a text block see Chapter 17.
To edit background text:
1. Select the text block.
2. Click the Inner Text tool on the tool bar.
Or choose Inner Text from the Format menu.
The format bar shows this view.
3. Edit the text in the Text box.
4. Resize the text block, if necessary, so that all text fits inside.
5. When done, click the Inner Text tool to exit inner text mode.
To apply color to background text:
1. Select the text block.
2. Choose a color from the Format Foreground Color submenu.
Or select a foreground color from the top row of the Color
Palette.
Publication 2711-6.0
16–10
Adding Graphics
Importing/Exporting
Bitmap Graphics
The Import/Export Graphics command lets you import bitmap
graphics from other programs including:
• monochrome bitmaps
• color bitmaps
Imported graphics can be used as inner graphics for button objects or
as background screen objects.
Bitmap graphics are handled like global objects. If an application
uses the same bitmap several times, the terminal only stores one
copy of the graphic. Any changes to a bitmap affect all other
instances of that graphic.
Size of Bitmaps
An imported bitmap cannot exceed the number of pixels supported
by the terminal display. Larger bitmaps are cropped when imported.
Editing Bitmaps
You cannot edit an imported graphic in PanelBuilder. To edit a
graphic, you must export the graphic to a file or the clipboard, edit
the graphic using another program and then re-import the graphic.
When a bitmap is edited and re-imported, PanelBuilder updates all
instances of that image in the application.
About Color Bitmaps
Color terminals support the 16 standard EGA colors. If you import a
full color bitmap, each color is mapped to one of the 16 EGA colors.
A color bitmap, reduced to 16 colors on import, is exported as a 16
color bitmap.
Grayscale terminals support 4 colors (shades of gray). If you import
a full color bitmap, each color is mapped to one of 4 colors. A color
bitmap, reduced to 4 colors on import, is exported as a 4 color
bitmap.
Publication 2711-6.0
Adding Graphics
16–11
From the Import/Export Graphics dialog you can:
• Import a bitmap graphic from a file (*.BMP) or the clipboard.
• View a bitmap graphic.
• Export a bitmap graphic to a file or the clipboard.
• Delete a bitmap graphic.
To open the Import/Export Graphics dialog:
• Click the Import Graphics tool in the toolbox.
• Or choose Import/Export Graphics from the File menu.
List of imported bitmaps
and standard ISA symbols
Press
To
Import a bitmap graphic (.BMP) from a file.
See Appendix B for a list of bitmaps that PanelBuilder
provides in the C:\AB\PBWIN\PBLIB folder.
Paste a bitmap graphic from the clipboard.
Export an imported graphic to a file.
Copy an imported graphic to the clipboard.
Delete an imported graphic. ISA symbols can’t be
deleted from the graphic list.
Publication 2711-6.0
16–12
Adding Graphics
To import a bitmap graphic from a file:
1. Click the Import button from the Import/Export Graphics dialog.
The Open dialog appears.
The File List box shows all files in the current folder of the
selected type (.BMP). You can change to another drive or folder
before selecting a file.
See Appendix B for a list of bitmaps that PanelBuilder provides
in the C:\AB\PBWIN\PBLIB folder..
2. Select the file you want to import and click the OK button.
Or double-click on the file name.
3. The Graphic Name dialog opens showing the name of the
selected file.
The Color Format area is
dimmed if you are importing a
monochrome bitmap.
The option on Grayscale
terminals is 4 Colors
4. In the Name box, enter a unique name for the graphic.
5. Under Color Format, specify whether you want to import the
color graphic as a monochrome bitmap or 16-color bitmap.
• If importing a monochrome bitmap, the Color Format area is
dimmed.
• If importing a color bitmap on a grayscale terminal, the Color
Format area is reduced to 4 colors.
6. Click OK to exit the Graphic Name dialog.
You return to the Import/Export Graphics dialog. The graphic
appears in the list of Currently Imported Graphics.
7. Click Done to exit the Import/Export Graphics dialog.
Publication 2711-6.0
Adding Graphics
16–13
To paste a bitmap graphic from the clipboard:
1. Copy or cut the graphic to the clipboard from the source program.
2. Run PanelBuilder and open the Import/Export Graphics dialog
from the File menu.
3. Click the Paste button to import the graphic from the clipboard.
The Graphic Name dialog opens.
The Color Format area is
dimmed if you are pasting a
monochrome bitmap.
The option on Grayscale
terminals is 4 Colors
4. In the Name box, enter a unique name for the graphic.
5. Under Color Format, specify whether you want to paste the color
graphic as a monochrome bitmap or 16-color bitmap.
If you are pasting a monochrome bitmap, the Color Format area
is dimmed.
• If pasting a monochrome bitmap, the Color Format area is
dimmed.
• If pasting a color bitmap on a grayscale terminal, the Color
Format area is reduced to 4 colors.
6. Click the OK button.
You return to the Import/Export Graphics dialog. The name
appears in the list of Currently Imported Graphics.
7. When finished, click the Done button.
Publication 2711-6.0
16–14
Adding Graphics
To view an imported graphic:
1. From the list of Currently Imported Graphics, select the graphic
you want to view. The graphic appears in the Sample area.
Selected graphic
View of selected graphic
2. Select another graphic. The new view replaces the previous view.
You can also use the UP and DOWN arrow keys to view other
graphics. Each time you press a key the view changes to another.
3. When finished, click the Done button.
To copy an imported graphic to the clipboard:
1. Select the name of the graphic you want to copy to the clipboard.
2. Click the Copy button.
The graphic is copied to the clipboard.
3. When finished, click the Done button.
You can now exit PanelBuilder and paste the graphic from the
clipboard into another program such as Paintbrush.
Publication 2711-6.0
Adding Graphics
16–15
To export an imported graphic to a file:
1. Select the name of the graphic you want to export.
Color bitmaps are exported in the format they are stored in
PanelBuilder. If a full color bitmap was reduced to 16 colors
when imported, it is exported as a 16 color bitmap.
2. Click the Export button.
The Save As dialog opens.
3. In the File Name box, enter a file name for saving the graphic. If
you omit the file type, PanelBuilder adds .BMP.
You can change the drive and folder before entering the
file name.
4. Click OK.
You return to the Import/Export Graphics dialog.
5. When finished, click the Done button.
To delete an imported graphic:
1. Select the graphic you want to delete from the list of Currently
Imported Graphics. ISA symbols can’t be deleted.
2. Click the Delete button.
The file is removed from the list.
3. When finished, click the Done button.
Publication 2711-6.0
16–16
Adding Graphics
Using
Background Graphics
Imported bitmap graphics can appear inside a button object or as a
background object on the screen. This section shows how to use an
imported graphic as a background object.
To place an imported graphic on the screen:
1. Click the Graphic Image tool in the toolbox.
Or choose Graphic Image from the Objects Graphics submenu.
2. Position the pointer where you want to place the graphic and click
the left mouse button.
The image border is selected and you’re placed in inner graphic
mode.
3. Select a graphic from the Graphics list box.
You can import graphics by clicking the icon on the format bar.
The border is sized to the graphic and becomes invisible. The
image is automatically selected.
Imported Graphic
While the image is selected (Graphics list box is reverse video)
you can view other graphics using the UP and DOWN arrow keys.
Each time you press a key the current view is replaced with
another.
4. Exit graphic image mode by clicking the selection tool in the
toolbox.
Or click the right mouse button.
5. Click to exit inner graphic mode.
Or choose Inner Graphic from the Format menu.
Publication 2711-6.0
Formatting Objects and Text
Chapter Objectives
This chapter shows how to change the appearance of objects and
text. It contains the following sections:
Section
Page
Format Options
17–2
Changing the Appearance of Objects
17–3
Changing Object Shape
17–4
Changing Line Type
17–5
Changing Fill Pattern
17–6
Using the Blink Option
17–7
Setting Foreground/Background Colors
17–8
Reversing Foreground/Background Colors
Working with Inner Text
17–9
17–10
Editing Inner Text
17–11
Inserting Time or Date
17–13
Inserting a Numeric Variable
17–14
Inserting an ASCII Variable
17–16
Working with Inner Graphics
17–19
Adding Inner Graphic
17–20
Setting Foreground/Background Colors
17–21
Reversing Foreground/Background Colors
17–22
Removing Inner Graphic
17–23
Editing Graphics
17–23
Changing the Appearance of Text
17–24
Sizing Text
17–25
Aligning Text
17–26
Underlining Text
17–27
Using the Blink Option
17–28
Setting Foreground/Background Colors
17–29
Reversing Foreground/Background Colors
17–30
!
ATTENTION: Some combinations of format options
could result in a control object not being visible (object
blends into screen background). All touch screen
controls must be visible or have a graphic showing the
location of the object. Failure to do so may result in
accidental or unpredictable operation.
Publication 2711-6.0
17–2
Formatting Objects and Text
Format Options
You can change the visual characteristics of objects and text from the
Format menu or the Format bar.
The Format bar has different views depending on what mode you’re
in. The views are shown below.
Format Bar in Object Mode
Format Bar in Inner Text Mode
Format Bar in Inner Graphic Mode
Publication 2711-6.0
For multistate objects, many of the formatting options can be set
directly from the State tab of the object’s dialog.
Formatting Objects and Text
Changing the
Appearance of Objects
Objects have visual characteristics that you can change such as:
• shape
• line type
• fill pattern
• blinking
• setting foreground/background colors
• toggling foreground/background
VALVE 1
OPEN
No Fill
Object
Formatting
17–3
ÎÎÎÎ
ÎÎÎ
ÎÎ ÎÎÎ
ÎÎÎÎ
ÎÎ ÎÎÎ
ÎÎÎÎ
VALVE 1
OPEN
Fill Pattern
VALVE 1
OPEN
No Border
VALVE 1
OPEN
Toggle
Fore/Background
Shape
When an object is selected the Format bar changes to show this view.
or
To change an object’s appearance, select the object and then choose a
command from the Format menu or click a tool on the Format bar.
Some of the options toggle on and off, others open a menu. To
toggle a setting from the Format bar, click the tool once to turn it on,
click it again to turn it off. The new setting remains active until you
change it.
A check mark (n) appears next to the active settings on the menu.
Publication 2711-6.0
17–4
Formatting Objects and Text
Changing Object Shape
You can change the shape of a button or the shape of a graphic using
the shape tools. For example, you can change the shape of a push
button to a circle or the shape of a rectangle to an ellipse.
Circles require less memory and process more efficiently than
ellipses in the terminal.
STOP
ÌÌÌ
ÌÌÌ
ÌÌÌ
ÌÌÌ
ÌÌÌ
STOP
ÌÌÌ
ÌÌÌ
ÌÌÌ
ÌÌÌ
ÌÌÌ
To change a shape:
1. Select the object.
2. Click the Shape tool from the Format bar.
Or choose Shape from the Format menu.
The Shape submenu opens.
3. Choose the shape you want for the selected object.
The object changes shape but maintains all other characteristics
such as border type, foreground/background colors and so on.
When changing an ellipse to a rectangle, the rectangle fits inside
the same rectangular area as the original shape. When changing a
rectangle or ellipse to a circle, the circle is resized to fit inside the
rectangular area.
The only fill patterns retained when changing the shape to a circle
or ellipse are white, black or none.
If you select an object that can’t be shaped, the Format commands
appear dimmed to show the shape can’t be changed.
Publication 2711-6.0
Formatting Objects and Text
17–5
Changing Line Type
You can change the border or edge of an object using the Line Type
command.
• On monochrome terminals, the line type options are:
– black
– white
– none (invisible)
• On color and grayscale terminals, the line type options are:
– solid
– none (invisible)
ÓÓÓ
ÓÓÓ
ÓÓÓ
ÑÑÑ
ÑÑÑ
ÑÑÑ
RESET
RESET
Push Button
with Border
Push Button
with No Border
STOP
Push Button
with Border and Fill
ÑÑÑÑ
ÑÑÑÑ
ÑÑÑÑ
STOP
Push Button
with No Border and Fill
Bar Graph
with Border
Bar Graph
with No Border
To change the line type:
1. Select the object.
2. Click the Line Type tool on the Format bar.
Or choose Line Type from the Format menu.
The Line Type submenu opens.
3. Choose the line type you want for the selected object.
The line type changes but the object maintains all other
characteristics such as shape, fill pattern and so on.
If you select an object that can’t have an invisible border, the line
type commands are dimmed to show the line type can’t be changed.
Publication 2711-6.0
17–6
Formatting Objects and Text
Changing Fill Pattern
The interior of rectangular objects can be filled with a solid color or
a pattern. You can apply a different fill pattern to each state of a
multistate object so that the fill pattern changes with each state. The
default fill pattern is white.
Multistate Push Button
with Different Fill Patterns
ÎÎÎÎ
ÎÎÎÎ
ÎÎÎÎ
ÔÔÔÔ
ÔÔÔÔ
ÔÔÔÔ
ÖÖÖÖ
ÖÖÖÖ
ÖÖÖÖ
Low
State 0 Fill
Normal
State 1 Fill
High
State 2 Fill
ÎÎ
ÎÎ
ÎÎ
ÎÎ
ÏÏÏÏ
ÏÏÏÏ
ÏÏÏÏ
Bar Graphs
with Different Fill Patterns
Push Button
with Inner Graphic and Fill
On color or grayscale terminals, you can not assign fill patterns to
circles or ellipses. On monochrome monitors, valid fill patterns for
circles and ellipses are black, white or none.
To add a fill pattern:
1. Select the object.
2. If the object is a multistate object, select a state.
• From the tool bar, select a state from the State box.
• Or choose Next State or Previous State from the Format menu.
3. Click the Fill tool on the Format bar.
Or choose Fill Pattern from the Format menu.
The Fill submenu opens.
4. Choose a fill option.
After selecting the fill pattern, the pattern appears in the object.
If you select an object that can’t be filled, the fill commands
appear dimmed to show the fill can’t be changed.
The fill changes but the object maintains all other characteristics
such as shape, line type and so on.
Publication 2711-6.0
For multistate objects, you can set the fill pattern for a state directly
from the State tab of the object’s dialog.
Formatting Objects and Text
17–7
Using the Blink Option
You can toggle blinking on or off for an object (including fill pattern
and border). For multistate objects you can toggle blinking on or off
for each state. The blink option is not valid for list objects.
The blink rate is approximately .5 seconds and is activated when the
application is running in the PanelView terminal. Blinking isn’t
activated for an object during application design.
Text within the object does not blink. To activate blinking for text,
enter inner text mode and then select the blink option.
To toggle blinking for an object:
1. Select the object.
2. If the object is a multistate object, select a state.
• From the tool bar, select a state from the State box.
• Or choose Next State or Previous State from the Format menu.
3. Click the Blink tool on the Format bar.
Or choose Blink from the Format menu.
Blinking is set for the object but the object maintains all other
characteristics such as fill pattern, line type and so on.
If blinking is invalid for an object, the command is dimmed.
For multistate objects, you can activate blinking for a state directly
from the State tab of the object’s dialog.
Publication 2711-6.0
17–8
Formatting Objects and Text
Setting Foreground/Background Colors
For color and grayscale terminals, you can change the foreground
and background colors of objects from the Format menu or the color
palette. The palette has either 16 colors (for color terminals) or 4
colors (for grayscale terminals).
On color terminals, the initial background color of objects is blue
and the foreground is white. On grayscale terminals, the initial
background color of objects is black and the foreground white.
Selected
Foreground Color
View Box updates as Foreground
and Background colors are selected
Selected
Background Color
To set the foreground and background colors of an object:
1. Select the object.
2. If the object is a multistate object, select a state.
• From the tool bar, select a state from the State box.
• Or choose Next State or Previous State from the Format menu.
3. To change the foreground color:
• Click a color on the top row of the color palette.
• Or choose a color from the Format Foreground Color menu.
The foreground color changes to the selected color.
4. To change the background color:
• Click a color on the bottom row of the color palette.
• Or choose a color from the Format Background Color menu.
The background color changes to the selected color.
You can also set foreground/ background colors for:
• inner text
• inner graphics (monochrome bitmaps only)
If you want the background of the object to match the text or
graphic, you must set the background colors separately.
Publication 2711-6.0
For multistate objects, you can set the foreground/background colors
for each state of an object from the State tab of the object’s dialog.
For list objects, the background color applies to the entire list.
Formatting Objects and Text
17–9
Reversing Foreground/Background Colors
You can reverse the foreground/background colors of objects. For
multistate objects, you can reverse the foreground/background of
each state.
• On monochrome terminals, the background and foreground
colors of an object toggles between black and white.
MANUAL
MANUAL
• On color and grayscale terminals, the background and foreground
colors of an object toggle between the set colors.
You cannot reverse the foreground/background colors of a list object.
To reverse the foreground and background colors:
1. Select the object.
2. If the object is a multistate object, select a state.
• From the tool bar, select a state from the State box.
• Or choose Next State or Previous State from the Format menu.
3. Click the Toggle Foreground/Background tool on the Format bar.
Or choose Toggle Fore/Background from the Format menu.
The object colors (including fill pattern, inner text and/or inner
graphic) are reversed.
You can reverse the foreground/ background colors separately for:
• inner text
• inner graphics (monochrome bitmaps only)
Publication 2711-6.0
17–10
Formatting Objects and Text
Working with Inner Text
Most objects are created with default inner text that can be edited
and formatted. The inner text appears inside the object and is linked
to the object. When you move or delete the object, the inner text is
also moved or deleted.
Keypad Enable Button
Enter
Pressure
Control List
Return Screen Button
Previous
Screen
Screen List Selector
Off
Conveyor Controls
Low
Pump Controls
Medium
High
Heater Controls
Data Entry
Push buttons and multistate objects can have different inner text for
each state. The text appears when the object is in the specified state.
On / Off Type
Push Button
Publication 2711-6.0
Multistate
Push Button
State 0 Text
ON
OFF
LOW
State 0 Text
State 1 Text
OFF
OFF
NORMAL
State 1 Text
HIGH
State 2 Text
Formatting Objects and Text
17–11
Editing Inner Text
This section shows how to edit inner text for an object. Remember, if
the object is multistate, the text appears only for the specified state.
Editing inner text for objects without states is somewhat different
than for multistate or list objects. The procedures that follow
describe both options.
To edit inner text for an object without states:
1. Select the object.
2. Click the Inner Text tool on the tool bar.
Or choose Inner Text from the Format menu.
The Format bar shows the current text with the insertion point
following the text.
For numeric data display or numeric entry objects, you’ll see a
variable placeholder /*V*/ with formatting details in the text box.
You can’t delete this variable but you can add text before or after.
/*V:6 NOFILL FIX:0*/ |
Text string number
A number is automatically assigned to each text string in an
application. This number appears to the left of the Text box.
3. Edit the text.
As you edit text, it‘s also entered in the object. If word wrap is
on, text wraps at the beginning of a word, not the middle. (Word
Wrap is set from the Format menu.) An asterisk (*) appears if the
text exceeds the object size.
– To delete text, drag the pointer over the text to highlight it,
then press BACKSPACE or DELETE.
– To replace text, drag the pointer over the text to highlight it,
then type the new text.
– To add text, position the cursor where you want to insert text
and then type the new text.
Press ENTER to start a new line. The characters /*R*/ are inserted
to indicate a new line.
4. Resize the object, if necessary, to fit all the text.
5. When done, click the Inner Text tool to exit inner text mode.
Publication 2711-6.0
17–12
Formatting Objects and Text
To edit inner text for a multistate or list object:
1. Select the object.
2. Click the Inner Text tool on the tool bar.
Or choose Inner Text from the Format menu.
The Format bar shows the current text with the insertion point
following the text.
Text string number
A number is automatically assigned to each text string in an
application. This number appears to the left of the Text box.
3. Select the state or entry you want to edit.
• From the tool bar, select a state from the State box.
• Or choose Next State or Previous State from the Format menu.
4. Edit the text.
As you edit the text, it’s also entered in the object. If word wrap
is on, text wraps at the beginning of a word, not than the middle.
(Word Wrap is set from the Format menu). An * appears if the
text exceeds the object size.
– To delete text, drag the pointer over the text to highlight it,
then press BACKSPACE or DELETE.
– To replace text, drag the pointer over the text to highlight it,
then type the new text.
– To add text, position the cursor where you want to insert text
and then type the new text.
Press ENTER to start a new line (except for list objects). The
characters /*R*/ are inserted to indicate a new line.
5. Repeat steps 3 and 4 to edit text for another state or entry.
6. Resize the object, if necessary, to fit all the text.
When done, click the Inner Text tool to exit inner text mode.
Publication 2711-6.0
For multistate or list objects, you can edit the text for each state
directly from the State tab of the object’s dialog.
Formatting Objects and Text
17–13
Inserting Time or Date
You can insert time or date in an object or within the text of an
object. The format of the time or date is adjusted from the Terminal
Setup dialog. The time displays in 12 hour or 24 hour format. The
date can display in various forms of MM/DD/YY.
The time or date format is downloaded with the application to the
PanelView terminal. When the application is running, the terminal
displays the actual time or date.
To insert the time or date in an object or text string:
1. Select the object.
2. For a multistate object, select the state in which you want to insert
the time or date.
• From the tool bar, select a state from the State box.
• Or choose Next State or Previous State from the Format menu.
3. Click the Inner Text tool on the tool bar.
Or choose Inner Text from the Format menu.
The Format bar shows the current text.
4. Click where you want to insert the time or date or use the arrow
keys to position the insertion point.
To display only the time or date, delete the text first by dragging
the pointer over the text to highlight it, then press BACKSPACE or
DELETE.
5. Click the Embedded Variable tool on the Format bar and choose
Time or Date from the popup menu.
Or choose Time or Date from the Format Embedded Variable
menu.
The time /*T*/ or date /*D*/ placeholder is inserted in the text box
and the time or date format is inserted in the object.
6. Resize the object, if necessary, to fit all the text.
7. Click the Inner Text tool to exit inner text mode.
For multistate objects, you can add a time or date variable to the text
of a specific state from the State tab of the Object’s dialog.
Publication 2711-6.0
17–14
Formatting Objects and Text
Inserting a Numeric Variable
You can insert a numeric variable (associated with a tag address) in
an object or text string. The variable can appear with a fixed or
floating point decimal, with or without zero fill.
When the application is running, the PanelView terminal reads the
value stored at the tag address and displays the value.
To insert a numeric variable in an object or text string:
1. Select the object.
2. For a multistate object, select the state in which you want to insert
a variable.
• From the tool bar, select a state from the State box.
• Or choose Next State or Previous State from the Format menu.
3. Click the Inner Text tool on the tool bar.
Or choose Inner Text from the Format menu.
The format bar shows the current text.
4. Click where you want to insert the variable or use the arrow keys
to position the insertion point.
If you want to display the variable without text, delete the text
first by dragging the pointer over the text to highlight it, then
press BACKSPACE or DELETE.
5. Click the Embedded Variable tool on the Format bar and choose
Variable from the popup menu.
Or choose Variable from the Format Embedded Variable menu.
Publication 2711-6.0
Formatting Objects and Text
17–15
6. Set the properties of the variable.
Use
To
Field Width
Specify the maximum number of digits (1 to 12)
allowed in the variable.
If the Fixed Point Decimal Position is not 0, then the
field width must be 2 > Position value for positive
numbers. One position is for the decimal point and
one position is for the digit to the left of the decimal.
For negative numbers, the field width must be
3 > Position. For example, to display –0.1234, the
field width must be 7 and decimal position 4.
Fill with Zeroes
Fill empty data positions with zeroes. Otherwise
empty positions are left blank.
Zero Filled
No Zero Fill
000321
_ _ _ 321
Fixed Point Decimal
Specify the position of the decimal point 0 to 10
places to the left of the rightmost character. Use 0
to display the value without a decimal point.
Floating Point Decimal
Have the controller position the decimal point.
Read Tag
Specify the tag name address from which to read
the variable data.
7. Click OK when done.
A placeholder /*V:12 NOFILL FIX:0*/ is inserted in the text with
embedded formatting details.
A string of characters ####### (the length of the field width) is
inserted in the object as a placeholder for the variable.
8. Resize the object, if necessary, to fit the variable.
9. Click the Inner Text tool to exit inner text mode.
For multistate objects, you can add a numeric variable to the text of a
specific state from the State tab of the Object’s dialog.
To edit a numeric variable:
1. Select the object.
2. For a multistate object, select the state containing the variable.
3. Click the Inner Text tool on the tool bar.
4. Select the /*V:12 NOFILL FIX:0*/ placeholder.
5. Click the Embedded Variable tool and choose Edit Variable to
open the Variable dialog.
6. Edit the formatting options, then click OK to exit the dialog.
The /*V:6 NOFILL FIX:0*/ placeholder is updated with the new
formatting details.
For multistate objects, you can edit the numeric variable directly
from the State tab (Text field) of the Object’s dialog.
Publication 2711-6.0
17–16
Formatting Objects and Text
Inserting an ASCII Variable
You can insert an ASCII variable in an object or text string. The
ASCII variable is used to display a character string sent from a
controller directly on the PanelView terminal. The variable is
updated whenever the string changes.
The ASCII variable can display any character in the extended
character set. The characters displayed are controlled exactly as
specified in the data string. Characters are processed sequentially
until a null character (all bits 0) is received. Any characters after a
null character are ignored.
The ASCII string is stored in the data table as a series of consecutive
characters. The format of the string must be as shown below.
Bit
15
8
7
1st word
1st character
2nd character
2nd word
3rd character
4th character
...
...
0
To insert an ASCII variable in an object or text string:
1. Select the object.
2. For a multistate object, select the state in which you want to insert
the ASCII variable.
• From the tool bar, select a state from the State box.
• Or choose Next State or Previous State from the Format menu.
3. Click the Inner Text tool on the tool bar or choose Inner Text
from the Format menu.
The format bar shows the current text.
4. Click where you want to insert the ASCII variable or use the
arrow keys to position the insertion point.
If you want to display the variable without text, delete the text
first by dragging the pointer over the text to highlight it, then
press BACKSPACE or DELETE.
Publication 2711-6.0
Formatting Objects and Text
17–17
5. Click the Embedded Variable tool on the Format bar and choose
ASCII from the popup menu.
Or choose ASCII from the Format Embedded Variable menu.
6. Set the properties of the variable.
Use
To
Field Width
Specify the maximum number of ASCII characters
(1 to 128) allowed in the variable.
The maximum field width depends on the
communication protocol used by the application.
For:
DH-485/DH+/DF1
Remote I/O
Maximum Field Width is:
80 characters
128 characters
The maximum number of characters supported by
a text string including the embedded ASCII variable
is 255. If the number of characters is > 255, the
string is truncated and an asterisk (*) appears.
To display fewer ASCII characters than the
specified field width, you must append the ASCII
NULL character to the string in the controller.
Read Tag
Specify the name of the tag address in the
controller from which to read the ASCII characters.
The data type of the read tag must be Character
Array. The Array Size of the tag must match the
field width or a validation error will occur.
Publication 2711-6.0
17–18
Formatting Objects and Text
7. Click OK when done.
A placeholder /*A:5 ASCII_Data*/ is inserted in the text with the
specified field width and the name of the read tag.
Read Tag
Field Width
A refers to ASCII Variable
Text precedes and
follows ASCII variable
A string of characters ##### (the length of the field width) is
inserted in the object as a placeholder for the variable.
8. Resize the object, if necessary, to fit the variable.
9. Click the Inner Text tool to exit inner text mode.
For multistate objects, you can add an ASCII variable to the text of a
specific state from the State tab of the Object’s dialog.
Example ASCII Strings
The following table provides examples of characters that are
embedded in an ASCII variable of a text string on the PanelView
terminal. The ASCII variable is configured with a field width of 6.
If the ASCII string stored in the controller does not have the same
number of characters as the field width:
• use the ASCII SP (space) character to pad a string that is less than
the field width.
• use the NULL (\0) character to terminate a string that is less than
the field width (or the string will not display)
Data from Logic Controller
0
2
3
4
5
M
E
D
I
U
M
textMEDIUMtext
SP
H
I
G
H
SP
text HIGH text
SP
SP
L
O
W
SP
text
SP
L
O
W
SP
\0
text LOW text
L
O
W
\0
E
X
C
E
E
D
SP
1
.
2
5
SP
text 1.25 text
SP
SP
3
4
5
SP
text
345 text
SP
SP
SP
SP
SP
SP
text
text
\0
Publication 2711-6.0
1
6
ASCII Characters Displayed on PanelView
7
8
9
LOW text
textLOWtext
S
textEXCEEDtext
texttext
Formatting Objects and Text
17–19
To edit an ASCII variable:
1. Select the object.
2. For a multistate object, select the state containing the variable.
3. Click the Inner Text tool on the tool bar.
4. Select the /*A:6 ASCII_Data*/ placeholder.
5. Click the Embedded Variable tool and choose Edit Variable to
open the Variable dialog.
6. Edit the formatting options, then click OK to exit the dialog.
The /*A:7 ASCII_Data*/ placeholder is updated.
Working with
Inner Graphics
For multistate objects, you can edit the ASCII variable directly from
the State tab (Text field) of the Object’s dialog.
You can add an inner graphic to a button or multistate object (not list
objects). For multistate objects, you can enter a different graphic for
each state.
The graphic appears only when the object is in the specified state.
The inner graphic appears inside the object and is linked to the
object. When you move or delete the object, the inner graphic is also
moved or deleted.
On / Off Type Push Button
State 0
Inner Graphic
State 1
Inner Graphic
The inner graphic can be an ISA symbol or a bitmap graphic created
with another program. Appendix B defines the ISA symbols. For
details on how to import bitmap graphics, see Chapter 16.
Publication 2711-6.0
17–20
Formatting Objects and Text
Working with
Inner Graphics
Adding Inner Graphic
To insert an imported bitmap or ISA symbol in an object:
1. Select the object.
2. For a multistate object, select the state to insert the graphic.
• From the tool bar, select a state from the State box.
• Or choose Next State or Previous State from the Format menu.
3. To display a graphic without text, get into inner text mode and
delete the text, then exit inner text mode.
4. Click the Inner Graphic tool on the tool bar.
Or choose Inner Graphic from the Format menu.
List of available graphics
5. Select a graphic or ISA symbol from the Graphics list box.
The graphic is inserted in the object.
ISA symbols are also available from the ISA Symbols toolbox.
Click a symbol while in inner graphic mode to insert in object.
Bitmap graphic
ISA Symbol
Button Border
Toggle through views of graphics while the Graphics list box is
highlighted using the UP and DOWN arrow keys. Each time you
press a key the current graphic is replaced with another view.
6. Position the graphic in the object by selecting and moving it.
7. Click the Inner Graphic tool to exit inner graphic mode.
Or click the left mouse button outside the push button.
8. Resize the object (not graphic), if necessary. The graphic retains
its relative position in the object anchored by the top left corner.
For multistate objects, you can assign a graphic to a specific state
from the State tab of the Object’s dialog.
To reposition a graphic:
1. Select the object.
2. For a multistate object, select the state containing the graphic.
3. Click the Inner Graphic tool on the tool bar.
4. Select the graphic and move it.
5. Click the Inner Graphic tool to exit inner graphic mode.
Publication 2711-6.0
Formatting Objects and Text
17–21
Setting Foreground/Background Colors
On color and grayscale terminals, you can set the foreground and
background colors of an inner graphic from the Format menu or the
color palette. The background is the area containing the graphic.
On color terminals, the initial default is a blue background and a
white foreground. On grayscale terminals, the initial default is a
black background and a white foreground.
You can adjust the foreground/background colors of monochrome
bitmaps, not color bitmaps.
To set the foreground/background colors of a graphic:
1. Select the object.
2. If the object is a multistate object, select a state.
• From the tool bar, select a state from the State box.
• Or choose Next State or Previous State from the Format menu.
3. Click the Inner Graphic tool on the tool bar.
Or choose Inner Graphic from the Format menu.
4. To change the foreground color:
• Click a color on the top row of the color palette.
• Or choose a color from the Format Foreground Color menu.
5. To change the background color:
• Click a color on the bottom row of the color palette.
• Or choose a color from the Format Background Color menu.
The background color changes to the selected color.
6. Click the Inner Graphic tool to exit Inner Graphic mode.
If you want the background of the graphic to blend in with the
background of the object, set the background colors for the object
and graphic to the same color.
For multistate objects, you can select foreground/background colors
for a graphic from the State tab of the object’s dialog.
Publication 2711-6.0
17–22
Formatting Objects and Text
Reversing Foreground/Background Colors
You can reverse the foreground/background of an inner graphic.
Foreground and Background of Graphic are Reversed
k
You can reverse the foreground/background colors of monochrome
bitmaps, not color bitmaps.
To reverse the foreground and background of a graphic:
1. Select the object.
2. Click the Inner Graphic tool on the tool bar.
3. If the object is multistate, select the state containing the graphic.
4. Click the Toggle Foreground/Background tool on the Format bar.
Or choose Toggle Fore/Background from the Format menu.
The color of the graphic and the area containing the graphic are
reversed.
5. To exit inner graphic mode, click the Inner Graphic tool.
Publication 2711-6.0
Formatting Objects and Text
17–23
Removing an Inner Graphic
To remove an inner graphic or ISA symbol from an object:
1. Select the object.
2. For a multistate object, select the state containing the graphic.
• From the tool bar, select a state from the State box.
• Or choose Next State or Previous State from the Format menu.
3. Click the Inner Graphic tool on the tool bar.
Or choose Inner Graphic from the Format menu.
The Format bar appears.
4. Select (None) from the Graphics list box.
The graphic is removed.
5. Click the Inner Graphic tool to exit inner graphic mode.
Editing Graphics
The size and content of an inner graphic (bitmap or ISA symbol)
cannot be changed in PanelBuilder. You must export the graphic,
revise it with another program such as Paintbrush and then re-import
it. You can export the graphic directly from the Format bar.
Bitmaps are handled like global objects. A bitmap image is stored
once, regardless of the number of links to it. When an image is
updated, PanelBuilder updates all instances of the image.
To edit a bitmap graphic or an ISA symbol:
1. Click the Import/Export Graphics tool on the Format bar.
Or choose Import/Export Graphics from the File menu.
2. Export the graphic to a disk file or the clipboard. Chapter 16 tells
how to export a graphic from the Import/Export Graphics dialog.
3. Use Paintbrush or another program to edit the bitmap graphic.
4. Import the revised image from the Import/Export Graphics
dialog. It’s recommended that you change the name to
differentiate the new image from the old image.
Important:
Bitmaps cannot exceed the pixel size of the terminal.
5. Re-insert the graphic in object as described on page 17–20.
Publication 2711-6.0
17–24
Formatting Objects and Text
Changing the
Appearance of Text
Text
Formatting
&
Alignment
You can change the way text looks on a screen using various
combinations of size, emphasis and alignment. From the Format
menu or Format bar you can:
• size text
• align text left, right or center
• underline text
• toggle blinking on or off
• set text foreground/background colors
• toggle foreground/background colors
Text format and alignment options are applied to entire text strings
not individual letters or words.
When you select an object and choose Inner Text from the Format
menu or click the Inner Text tool on the tool bar the Format bar
changes to this view.
Most options toggle on and off, others open a menu. To toggle a
setting from the Format bar, click the tool once to turn it on, click it
again to turn it off. The new setting remains active until changed.
A check mark (n) indicates active settings for the selected text.
"
Publication 2711-6.0
For multistate objects, text formatting options can be set directly
from the State tab of the object’s dialog.
Formatting Objects and Text
17–25
Sizing Text
When sizing text, you can select from a variety of sizes. If working
with multistate objects you can size the text for each state. In list
objects, changes to text size affect all entries in the list.
To size text:
1. Select the object whose text you want to size.
2. Click the Inner Text tool on the tool bar.
Or choose Inner Text from the Format menu.
3. If the object is multistate, select a state.
• From the tool bar, select a state from the State box.
• Or choose Next State or Previous State from the Format menu.
4. Click the Text Size tool on the Format bar and choose a size from
the popup menu.
Or choose a size from the Format Text Size menu.
If an external font is selected, a second set of font sizes will
appear in parenthesis below the regular PanelBuilder fonts.
1400 Text Sizes
1000/900
Text Sizes
600 Text Sizes
550 Text Sizes
External Font
The entire text string is resized.
5. To set foreground/background colors, blinking, underlining or
text alignment, click the appropriate tools on the Format bar.
6. To exit inner text mode, choose the Inner Text command or tool.
For multistate and list objects, you can adjust the text size from the
State tab of the object’s dialog.
Publication 2711-6.0
17–26
Formatting Objects and Text
Aligning Text
You can align screen text or inner text of an object in three ways: left
align, right align or center align.
Align
Text
to the Left
Center
Text
Align
Text
to the Right
For multistate and list objects, you can align the text differently for
each state.
To change text alignment:
1. Select the object whose text you want to align.
2. Click the Inner Text tool on the tool bar.
Or choose Inner Text from the Format menu.
3. If the object is multistate, select a state.
• From the tool bar, select a state from the State box.
• Or choose Next State or Previous State from the Format menu.
4. Choose an alignment option from the FormatAlign Text
submenu.
Or click the appropriate align tool on the Format bar.
Left
Center
Right
The entire text string is realigned.
5. To resize, underline, set colors or activate blinking for the text,
click the appropriate tools on the Format bar.
6. To exit inner text mode, choose the Inner Text command or tool.
Publication 2711-6.0
For multistate and list objects, you can change text alignment from
the State tab of the object’s dialog.
Formatting Objects and Text
17–27
Underlining Text
You can toggle underlining on or off for screen text or inner text of
an object. For multistate or list objects, you can toggle underlining
on or off for each state.
The underline option applies to an entire text string not individual
letters or words in the string.
The entire
test string
is underlined
To underline text:
1. Select the object with text you want to underline.
2. Click the Inner Text tool on the tool bar.
Or choose Inner Text from the Format menu.
3. If the object is multistate, select a state.
• From the tool bar, select a state from the State box.
• Or choose Next State or Previous State from the Format menu.
4. Click the Underline tool on the Format bar.
Or choose Underline from the Format menu.
The entire text string is underlined.
5. To resize, align, set colors or activate blinking for the text, click
the appropriate tools on the Format bar.
6. To exit inner text mode, choose the Inner Text command or tool.
Underlining remains active until you turn it off.
For multistate and list objects, you can underline text for a specific
state from the State tab of the object’s dialog.
Publication 2711-6.0
17–28
Formatting Objects and Text
Using the Blink Option
You can toggle blinking on or off for screen text, inner text or the
inner graphic of an object. Blinking applies to an entire text string
not individual letters or words in the string. The blink option isn’t
available for list objects.
The blink rate is approximately .5 seconds and is activated when the
application is running in the PanelView terminal. Blinking isn’t
activated for text during application design.
Only the text blinks, not the object. To activate blinking for the
object, select the object and then choose Blink from the Format
menu or click the Blink tool.
To toggle blinking for text:
1. Select the object with text you want to blink.
2. Click the Inner Text tool on the tool bar.
Or choose Inner Text from the Format menu.
3. If the object is multistate, select a state.
• From the tool bar, select a state from the State box.
• Or choose Next State or Previous State from the Format menu.
4. Click the Blink tool on the Format bar.
Or choose Blink from the Format menu.
The entire text string blinks.
5. To resize, align, underline or set colors for the text, click the
appropriate tools on the Format bar.
6. To exit inner text mode, choose the Inner Text command or tool.
Blinking remains active until you turn it off.
Publication 2711-6.0
For multistate objects, you can activate blinking for a specific state
directly from the State tab of the object’s dialog.
Formatting Objects and Text
17–29
Setting Foreground/Background Colors
On color and grayscale terminals, you can set the foreground and
background colors of text from the Format menu or the color palette.
You cannot adjust the background color for text in list objects.
Selected
Foreground Color
View Box updates as Foreground
and Background colors are selected
Selected
Background Color
To set the foreground and background colors of text:
1. Select the object.
2. Click the Inner Text tool on the tool bar.
Or choose Inner Text from the Format menu.
3. If the object is a multistate object, select a state.
• From the tool bar, select a state from the State box.
• Or choose Next State or Previous State from the Format menu.
4. To change the foreground color:
• Click a color on the top row of the color palette.
• Or choose a color from the Format Foreground Color menu.
The foreground color changes to the selected color.
5. To change the background color:
• Click a color on the bottom row of the color palette.
• Or choose a color from the Format Background Color menu.
The background color changes to the selected color.
6. Click the Inner Text tool to exit Inner Text mode.
If you want the text background to blend in with the object
background, set the background colors for the object and text to the
same color.
Background Color for Text
k
and Object are different.
Background Colors for Text
and Object are the same.
ON
OFF
ON
OFF
For multistate objects, you set the text foreground and background
colors for each state from the State tab of the object’s dialog or from
the color palette when the state is visible.
Publication 2711-6.0
17–30
Formatting Objects and Text
Reversing Foreground/Background Colors
You can reverse the background/foreground colors of screen text or
the inner text of an object. For multistate objects, you can toggle the
foreground/background colors of the inner text for each state. This
option is not valid for list objects.
The Toggle Foreground/Background option applies to an entire text
string not individual letters or words in the string.
The foreground/background colors of text toggle independently of
the foreground/background colors set for the object or object state.
Foreground and Background
Colors of Text are Reversed
k
ON
OFF
ON
OFF
To reverse the foreground and background colors of text:
1. Select the object.
2. Click the Inner Text tool on the tool bar.
Or choose Inner Text from the Format menu.
3. If the object is multistate, select a state.
• From the tool bar, select a state from the State box.
• Or choose Next State or Previous State from the Format menu.
4. Click the Toggle Foreground/Background tool on the Format bar.
Or choose Toggle Fore/Background from the Format menu.
The color of the text string and the area containing the text string
are reversed.
5. To resize, align, underline or activate blinking for the text, click
the appropriate tools on the Format bar.
6. To exit inner text mode, choose the Inner Text command or tool.
Publication 2711-6.0
Using the Text Editor
Chapter Objectives
This chapter contains the following sections:
Section
Page
Opening the Text Editor
18–2
Entering New Text
18–3
Editing Text
18–4
Inserting Variables in Text
18–5
Sorting Text
18–6
Filtering Text
18–6
Printing Text
18–7
Deleting Text
18–8
Renumbering Text
18–9
Moving Text
18–9
Copying Text into Objects
18–10
Publication 2711-6.0
18–2
Using the Text Editor
Opening the Text Editor
The Text Editor contains a list of all text defined for the application
including object text, background text, and alarm messages. Use the
Text Editor to:
• enter new text (with embedded variables)
• edit text
• delete unused text
• copy text into objects
• renumber text
• filter and sort text
• print application text
To open the Text Editor:
Choose Text Editor from the Application menu.
Row
Cell
Many text operations are performed
clicking a row number and choosing
a command from this menu.
The Text Editor uses a spreadsheet to simplify text editing
operations. Each row identifies the following fields for a text string:
Publication 2711-6.0
Text Field
Description
Text ID
Specifies a unique number for a text string.
Count
Specifies how many times the text string is used in the application. A
count of 0 means the string is not used. This is a read only field.
Type
Specifies whether the text is used in an object or as an alarm
message. This is a read only field.
Text
Defines a text string with or without embedded variables (time, date,
or numeric variable).
Using the Text Editor
Entering New Text
18–3
The Text Editor lets you create new text strings which can then be
used by objects in the application. This also includes text from an
external font file. You can also insert variables within the text
including a time, date or numeric variable.
The last row in the Text Editor contains an asterisk (*). This row is
reserved for creating a new text string.
To add a new text string as the last row in the spreadsheet:
1. Locate the last row which contains an asterisk (*).
2. Double-click the Text field.
The default text “New text” is highlighted.
3. Type in the new text.
To enter a carriage return, press ENTER. The characters /*R*/ are
inserted to indicate a new line.
4. Click anywhere outside of the field.
The Text ID field is updated with the next available number. The
Count field remains 0 until the text string is used by the
application.
To insert a new text string at a specific location:
1. Select the row number where you want to insert a text string.
2. Choose Insert Text Item from the popup menu.
A row is inserted above the selected row with the next available
Text ID number.
3. Double-click the Text field.
The default text “New text” is highlighted.
4. Type in the new text.
To enter a carriage return, press ENTER. The characters /*R*/ are
inserted to indicate a new line.
5. Click anywhere outside of the field.
The Count field remains 0 until the text string is used by the
application.
Publication 2711-6.0
18–4
Using the Text Editor
Editing Text
If you edit text in the Text Editor, PanelBuilder will update all
occurrences of the text in the application.
To edit a text string:
1. Locate the text you want to edit.
2. Click in the Text field and edit the text.
• To delete text, click once to highlight all the text and press
BACKSPACE
or DELETE.
• To add text, position the cursor and type new text.
• To insert a carriage return /*R*/, press ENTER.
3. When done, click anywhere outside of the cell.
The text is updated wherever it is used in the application.
To cut/copy and paste text:
1. Click the Text field containing the text you want to copy .
2. Choose Copy or Cut from the popup menu.
All text in the cell is placed on the clipboard.
3. Click the Text field where you want to paste the text.
4. Choose Paste from the popup menu.
The text is pasted from the clipboard.
5. When done, click anywhere outside of the cell.
The text is updated wherever it is used in the application.
Publication 2711-6.0
Using the Text Editor
Inserting Variables in Text
18–5
You can insert a time, date or numeric variable within a text string.
The variables are downloaded to the terminal with the application.
To insert a time, date, numeric, ASCII variable in a text string:
1. Locate the text in which you want to insert a variable.
2. Double-click the Text field.
3. Position the cursor where you want to insert the variable.
4. From the popup menu, choose Embedded Variable Time, Date,
Variable (for Numeric), or ASCII.
For the Time and Date variable, a placeholder is inserted in the
message (/*T*/ for time, /*D*/ for date). The format of the time and
date is set in the Terminal Setup dialog.
A dialog opens when Variable (p. 17–14) or ASCII ( p. 17–17)
is selected. The dialog defines the format of the variable in the
text string. When you exit this dialog, a placeholder is inserted
within the text with embedded formatting details.
To edit a numeric or ASCII variable:
1. Double-click the Text field containing the variable.
2. Click the numeric /*V:12 NOFILL FIX:0*/ or ASCII /*A:12* / variable.
3. From the popup menu, choose Embedded Variable Edit Variable.
4. Edit the settings in the Variable dialog.
5. When done, click OK to exit dialog.
The placeholder is updated with the new format.
To delete a variable:
Click on the placeholder and choose Cut from the popup menu, or
press BACKSPACE or DELETE.
Publication 2711-6.0
18–6
Using the Text Editor
Sorting Text
Sorting organizes data in columns, alphabetically or numerically.
When you sort a column, rows are rearranged according to the
contents of the column. For example, if you sort the Text field, all
rows are rearranged alphabetically. Identical text strings appear
together.
The Sort By list box lets you sort the data in these columns:
• None (no sort column)
• Text ID (numeric sort)
• Count (numeric sort)
• Type (object or alarm message)
• Text (alphabetical sort)
To sort a column or field of data:
From the Sort By list box, select a column you want to sort.
The column is sorted numerically or alphabetically depending on the
contents of the column.
Filtering Text
You can filter text to display or work with only a subset of text
strings in the application. You can sort or print a filtered list.
To filter or select a subset of text strings:
1. Click the Filter button in the Text Editor.
Selects all check boxes
Clears all check boxes
The dialog displays a list of all instances where text is used in an
application. Initially all options are selected.
Publication 2711-6.0
Using the Text Editor
18–7
2. Click the Clear All button to clear all check boxes.
3. Click the check boxes of the options you want in the subset.
For example, to create a subset that includes all text used by
Alarms and Print Only Devices, check those boxes only. To
create a subset of all unused text strings, select the Unused check
box. All other boxes are cleared.
4. Click OK to exit the Filter dialog.
The Text Editor has filtered out all text except for the options
selected in the Filter dialog.
Printing Text
You can print all text or a range of text stored in the Text Editor.
Create a subset of text to print using the filter option. You can also
sort a filtered list or range of text before printing.
The following information prints for each text string in a list format.
• Text ID (or number)
• Text
A header prints at the top of each page.
To print application text:
1. Select the text you want to print.
• To select a single item, click the row number of the text string.
• To select a block of text, click the row number of the first text
item, hold down the left mouse button and drag the mouse
until the last text item in the block is highlighted.
• To select all text, click the Select All button.
2. Click the Print button.
The standard Windows Print dialog opens.
3. Under Print Range, select the range of text items to print (All or
Selection).
Click the Print Setup button to set the default printer or to change the
printer options.
4. Click OK to close the dialog.
Publication 2711-6.0
18–8
Using the Text Editor
Deleting Unused Text
You can delete text that is not used by the application. An unused
text string has a 0 in the Count field.
To display all unused text in a group:
• From the Sort By list box, select Count to sort the Count field
numerically. All text strings with a count of 0 will appear in a
block at the end of the spreadsheet.
• Create a subset of all unused text by clearing all check boxes in
the Filter dialog and then selecting the Unused check box.
To delete all unused text:
1. Click the Select All button.
2. Click the Purge button or choose Purge Text Item from the popup
menu.
All unused text (count of 0) is permanently removed from the
application. A popup shows the number of text items deleted.
To delete one or several unused text strings:
1. Select the rows (with a Count value of 0) to delete.
2. Click the Purge button or choose Purge Text Item from the popup
menu.
Publication 2711-6.0
Using the Text Editor
Renumbering Text
18–9
To consolidate memory, renumber text strings to eliminate gaps in
the numbering sequence.
To check for numbering gaps, select Text ID from the Sort By list
box. All Text ID numbers are sorted numerically.
To renumber a single text string:
1. Double-click the Text ID field of the text string you want to
renumber.
2. Type a unique number.
When you exit the Text Editor, a warning message will display if
duplicate numbers are detected. The message indicates the row
numbers containing the duplicate Text ID numbers. You must
renumber the text strings before exiting the Text Editor.
To renumber all text strings:
1. Click the Select All button.
2. Click the Renumber button.
All text strings are automatically renumbered starting at 1.
To renumber a block of text strings:
1. Select the row number of the first text string in the block, hold
down the left mouse button and drag the mouse until all rows in
the block are highlighted.
2. Click the Renumber button.
All text strings in the block are renumbered starting with the
number of the first text string. For example, a block of text
numbered 80, 84, 85, 88, 89 would be renumbered 80, 81, 82,
83, 84.
Moving Text
You can rearrange the order of text by moving a text string up/down
a row or to a specific location:
To move a text item up or down one row:
1. Select the row number of the text you want to move.
2. Choose Move Text Item Up or Move Text Item Down from the
popup menu.
The text is moved up or down one row.
Publication 2711-6.0
18–10
Using the Text Editor
To move a text string to a specific location:
1. Select the row number of the text string you want to move.
2. Choose Move Text Item To: from the popup menu.
A dialog opens prompting you to enter the row number where
you want to move the text. The dialog shows the range of row
numbers before and after the selected text.
3. In the Row Number box, type a number.
The selected text is moved to the specified location and the rest of
the rows are renumbered.
Copying Text into Objects
Text stored in the Text Editor can be copied to:
• objects
• print only message objects
• alarm messages
You can reuse the same text multiple times in an application. Only
one copy of the text is stored regardless of the number of links to it.
You can access the Text Editor from the:
• Format bar while in Inner Text mode
• Alarm tab of the Alarm Editor
• State tab of a multistate or list object’s dialog
To copy text into an object while in Inner Text mode:
1. Select the object in which you want to copy the text.
2. Click the Inner Text tool on the tool bar.
Or choose Inner Text from the Format menu.
3. For multistate objects, select the state in which you want to copy
the text.
4. Click the Use Existing Text tool on the Format bar.
Or choose Use Existing Text from the Edit menu.
The Use Existing Text dialog opens in Read Only mode.
5. From the dialog, select the row number of the text you want to
copy.
Use the Sort By or Filter options to help you locate text.
6. Click the Apply button.
The object text is replaced with the selected text and the Use
Existing Text dialog closes.
Publication 2711-6.0
Using the Text Editor
18–11
To copy text from the State tab of an object’s dialog:
1. Select the object in which you want to copy the text.
2. Double-click the object.
3. Select the State tab.
4. Select the row number of the text you want replace with text in
the Text Editor.
5. Choose Use Existing Text from the popup menu.
The Use Existing Text dialog opens in Read Only mode.
6. From the dialog, select the row number of the text you want to
copy.
Use the Sort By or Filter options to help you locate the text.
7. Click the Apply button and then the Close button.
The Text ID and Text fields are updated with data from the copied
text and the Use Existing Text dialog closes.
8. Click OK to exit the object’s dialog.
To copy text from the Alarm tab (Alarm Setup dialog):
1. Choose Alarm Setup from the Application menu.
2. Select the Alarms tab.
3. Select the row number of the text you want to replace with text in
the Text Editor.
4. Choose Use Existing Text from the popup menu.
The Use Existing Text dialog opens in Read Only mode.
5. From the dialog, select the row number of the text you want to
copy.
6. Click the Apply button and then the Close button.
The Text ID and Text fields are updated with data from the copied
text and the Use Existing Text dialog closes.
7. Click OK to exit the Alarm Setup dialog.
Publication 2711-6.0
Working with Tags
Chapter Objectives
This chapter shows how to enter tag information for an application
project using the Tag Editor. It contains the following sections:
Section
Using the Tag Editor
Page
Using the Tag Editor
19–1
Validating Tag Addresses
19–4
Defining Tags
19–5
Saving Tags
19–7
Viewing Tags
19–7
Inserting and Deleting Tags
19–7
Copying Tags
19–8
Duplicating Tags
19–9
Finding Tags
19–10
Sorting Tags
19–11
Printing Tags
19–12
Using Tools
19–15
Tag Import/Export Utility
19–15
Importing Tags
19–16
Handling Data Collisions
19–17
Exporting Tags
19–18
Examining Results of an Import/Export
19–19
Interpreting Error Messages
19–20
You can enter tag information in either of two ways:
Table View
Enter several tags at the same time in a table which has its own tool
bar and columns for tag attributes. This is called the Summary View.
Form View
Enter a single tag from a dialog in PanelBuilder, or change from the
table view to the form view.
Publication 2711-6.0
19–2
Working with Tags
Opening the Tag Editor
To open the table view of the Tag Editor:
Choose Tag Editor from the Application menu.
Table (Summary) View
name of
this window
Status Icons
This tag is stored
in your project
Error on row (in
this case, duplicate
tag name)
Currently editing
this row
Tool bar
Publication 2711-6.0
project
name
the type
of view
Working with Tags
19–3
To open the form view:
• From the table view, choose Form from the View menu.
• From a PanelBuilder dialog, enter or select a tag name and select
the Edit Tag button.
Form View
Certain fields appear or disappear
based on the data type of the tag
you are creating in the form view.
For example, if the data type is Bit,
the Scaling and Data Entry Limits
fields are not displayed.
If you enter data in the form view, it
does not appear in the table view
until you choose Refresh from the
Window menu.
Navigating through the Tag Editor
To move between fields in form view or table view:
• Move the mouse pointer to the field and click the left button.
• Or press TAB to move forward through fields and SHIFT+TAB to
move backward.
To change from table view to form view:
• Click the Form tool on the tool bar.
• Or choose Form from the View menu.
• Or choose Form Editor from the Tools menu.
To change from form view to table view:
• Click the Tag Editor button in the tag form view.
• Or choose Summary from the View menu.
• Or choose List Editor from the Tools menu.
Note: If you enter data in the form view, it will not appear in the
table view when you switch views. Choose Refresh from the
Window menu to display the new data.
To exit the Tag Editor:
Double-click the Control-menu box at the top left of the window.
• Or in the table view, choose Exit from the Project menu.
• Or in the form view, click the OK or Cancel button.
Publication 2711-6.0
19–4
Working with Tags
Validating Tag Addresses
Activate address validation before entering or modifying tags. Only
those tags entered or modified after the option has been selected are
validated. Addresses for existing tags are not validated.
Table View only
To activate address validation:
Choose Address Validation from the Options menu. A check mark
next to the menu item indicates that the option is activated.
Note: Address validation is always active in the form view.
The Tag Editor validates each address against the type of device
specified in the Node Name field. If the address is invalid, the Tag
Editor displays the following warning:
Click:
To:
Return to the invalid address in the table view.
Save the tag in the database with the invalid address.
For information on valid addresses for a specific type of controller,
refer to the user manual for that controller.
Note: If you select the IEEE Float data type for a tag and enter an
incorrect address (e.g., S2:4), the tag editor does not validate the
error. You may need to copy the floating point data into an integer
file before downloading the application to the terminal.
Publication 2711-6.0
Working with Tags
19–5
Defining Tags
Table View
Form View
To move to a specific field on the Form View, press the ALT key an
type the letter that is underlined in the field name.
Field
Description
Valid Characters
Notes
Tag Name ➀➁
The name of the tag
Maximum characters = 32
•A – Z, a – z, 0 – 9
•hyphen (–), underscore(_),
percent (%)
•if you type an invalid character, the Tag Editor beeps and
does not display it
•the tag name must be unique within a project
•cannot begin with 0 – 9, hyphen (–), or percent (%)
•tag names are not case-sensitive
•do not use blanks, tabs, carriage returns, non-printable
characters
Data Type
The data format for
the tag
Select one of the following:
•bit
•4BCD
•unsigned integer
•signed integer
•IEEE Float
•bit array
•character array
•the data type must be compatible with the data format
selected in the object’s dialog.
Object Dialog
Tag Editor
Alternate Methods:
Type the first letter of the data type. For
example, type b for the bit data type.
Use the TAB key to move to the Data Type
field and press ALT+↓ to display the list of
available formats.
Array Size
The size of the array
Maximum characters = 16
•Bit Array is 1 - 16
•Character Array is protocol
dependent
•the array size must be an integer.
•do not use blanks, tabs, carriage returns, non-printable
characters
Description
The description of the
tag
Maximum characters = 255
•any printable
•do not use tabs, carriage returns, non-printable
characters
•you can type the information in this field, or use the
description editor. To access the description editor:
• Place the cursor in the description field.
• Click the right mouse button.
• Choose Editor from the menu.
• When finished typing/editing your description, click OK.
Publication 2711-6.0
19–6
Working with Tags
Field
Description
Valid Characters
Notes
Node Name ➀➁
The node with which
you want this tag
associated
Maximum characters = 32
•A – Z, a – z, 0 – 9
•hyphen (–), underscore(_),
percent (%)
•if you type an invalid character, the Tag Editor beeps and
does not display it
•node name cannot be identical to a tag name or terminal
name
•the node name must match the controller name entered
in the Communication Setup dialog (Terminal Setup)
•node name cannot begin with 0 – 9, hyphen, or percent
•node names are not case-sensitive
•do not use blanks, tabs, carriage returns, non-printable
characters
Address ➀➁
The data table
address within the
processor for the tag
Maximum characters = 32
For more information on valid
addresses, refer to your
processor’s user manual.
•do not use blanks, tabs, carriage returns, non-printable
characters
Initial Value
The starting value for
the current tag in
engineering units
Maximum characters = 24
•0 – 9
•e, E, +, – and period
•if the Data Type is bit, enter
either 0 or 1
•do not use blanks, tabs, carriage returns, non-printable
characters
•maximum precision is 6 places to the right of the decimal
point for non-floating point values
•if present, a sign (+ or –) for the number must be first (+
is the default)
•if present, a sign for the exponent must immediately
follow the e or E
•provides a preset value for numeric entry objects only
•no entry = default of 0
Update Frequency
The rate at which you
want the terminal to
obtain data
•1 – 9
where 1 is the fastest update
rate
Scaling ➂
Scale:
‘m’ in y = mx + b
Offset:
‘b’ in y = mx + b
The values you want
to use to convert the
current tag’s
processor integer
value (‘x’) to
engineering units (‘y’)
Maximum characters = 12
•0 – 9
•e, E, +, – and period
Data Entry Limits ➂
Minimum
Maximum
The minimum and
maximum values that
can be assigned to
the tag
Maximum characters = 12
•0 – 9
•e, E, +, – and period
does not apply to remote I/O
Alternate Methods:
Type the update frequency, 1 to 9.
Use the TAB key to move to the Update
Frequency field and press ALT+↓ to display
the list of available formats.
•do not use blanks, tabs, carriage returns, non-printable
characters
•maximum precision for scale is 6 places to right of
decimal point
•maximum precision for offset is 6 places to right of
decimal point
•if present, a sign (+ or –) for the number must be first (+
is default)
•if present, a sign for the exponent must immediately
follow the e or E
•do not use blanks, tabs, carriage returns, non-printable
characters
•maximum precision is 6 places to the right of the decimal
point
•if present, a sign (+ or –) for the number must be first (+
is the default)
•if present, a sign for the exponent must immediately
follow the e or E
➀ Required fields for the Table View
➁ Required fields for the Form View
➂ These fields appear only when the data type is 4BCD, signed integer, unsigned integer, IEEE Float.
Publication 2711-6.0
Working with Tags
Saving Tags
19–7
Form View
To save a tag definition in the form view:
• Click OK.
• Or press ENTER.
• Or press the Tag Editor button.
To close the form without saving anything, click the Cancel button.
Table View
To save a tag definition in the table view:
•
•
•
•
Press ENTER at the end of the row.
Or move the cursor to a different (existing) row.
Or double-click in the Status Column for that tag.
Or use the scroll bar or PageUp or PageDown keys to move to a
different row.
• Or change to the form view.
Viewing Tags
Table View only
To display:
Do this:
all tags in the project
choose Summary from the View menu.
choose BCD/Integer from the View menu.
only data types of 4BCD, unsigned
or signed integer, or word array
another copy of current view
Inserting and Deleting Tags
click
or choose New from Window menu.
To select a row, use the left mouse button to click in the Status
Column for that row.
To:
Do this:
insert a tag
click
or choose Insert from Edit menu.
delete a tag
click
or choose Delete from Edit menu.
The tag is deleted from the current
project and cannot be retrieved.
cut a tag
click
or choose Cut from Edit menu.
The tag is deleted from the current
project but can be retrieved with
the Paste command.
Publication 2711-6.0
19–8
Working with Tags
Copying Tags
Table View only
Many tags in the table view have the same data type, node name, or
other attributes. Tags may be selected, copied and pasted with all
their fields, or individual fields may be copied.
Since tags or their fields are copied to the Microsoft Windows
clipboard, they can be pasted in another application, even an
application in another project.
When a tag is copied, the new tag’s name is the same as the original
tag’s name in the Tag Editor table view. An X appears in the Status
column for the new tag’s row until its name is changed.
To:
Do this:
select a field
use the left mouse button and click in the field.
select a single row
use the left mouse button and click in the Status column for
that row.
select several contiguous
rows
use the left mouse button, click in the Status column and
drag the mouse down the column or hold the SHIFT key and
press PAGE DOWN or PAGE UP.
select several
discontiguous rows
use the left mouse button and click in the Status column for
the first row. Press PAGE DOWN or PAGE UP. Press and
hold the CTRL key and click in the Status column of the
other rows that you want to select.
To copy and paste tag information:
1. Select the field or row that you want to copy.
2. Click the Copy tool on the tool bar or choose Copy from the Edit
menu.
3. Move the cursor to the new position.
4. Click the Paste tool on the tool bar or choose Paste Row or Paste
Field from the Edit menu.
If a row was copied or pasted, it is inserted above the current row.
If a field was copied or pasted, it replaces the contents of the field in
the current row. Be careful to paste it in a field in the same column.
To copy tags to another application:
1. Copy the tag(s) and exit the Tag Editor.
2. Open the target application in the same or another project.
3. Open the Tag Editor table view and paste the tags in it.
Publication 2711-6.0
Working with Tags
Duplicating Tags
Table View only
19–9
Use this option when a number of tags have similar attributes but are
assigned to different variables in the application. Create one tag and
duplicate it as many times as needed. Then change the name and
address on each new tag to suit the variable it will be assigned to.
To duplicate a tag once:
1. Select the tag name to duplicate.
2. Click the Duplicate Once tool on the tool bar or choose Duplicate
Once from the Edit menu.
The Tag Editor duplicates the row and places it after the current row.
The tag name is incremented according to the options specified in
the Duplication dialog under the Options menu.
To duplicate several tags:
1. Select the tag name to duplicate.
2. Click the Duplicate Several tool on the tool bar or choose
Duplicate Several from the Edit menu.
The Tag Editor duplicates the current row and increments
the tag names according to options specified in the Duplication
dialog under the Options menu.
To set the number of duplicates:
1. Choose Duplication on the Options menu.
2. Select the Increment Name check box to specify whether or not to
distinguish names of duplicated tags by adding a number to the
name. The default is to add a number.
3. Select a separator from the Separator list box to use between the
name and number of duplicated tags.
4. Select a number (1 to 4) from the Number of Digits list box to
specify the number of characters to the right of the separator.
Publication 2711-6.0
19–10
Working with Tags
5. Highlight the value in the Number of Duplicates text box and
type a number.
The number of duplicates is also displayed in the Duplications
text box on the tool bar. You can highlight and change this value
without entering the Duplication dialog.
Finding Tags
Use this tool or command to locate any tag or tags in the Tag Editor
by name. Other attributes cannot be used in the Find dialog.
Important:
Table View only
If the active View is BCD/Integer, the Find command
cannot locate tags with bit addresses.
To find a tag:
1. Click the Find tool on the tool bar or choose Find from the Edit
menu.
2. In the Tag Name box, type the name of the tag to find and press
ENTER.
The Find command locates all tag names containing the
characters that you type (it is not case sensitive). For example, if
you enter switch, the Find command locates: switch, Switch,
SWITCH, Switch_5, Limit_switch, LimitSwitch, etc.
3. Click on the appropriate button to move among the occurrences
of the tag name.
Click:
To:
Move to first occurrence in current view.
Move to previous occurrence.
Move to next occurrence.
Move to last occurrence in current view.
4. When done, click the Cancel button or press ESC.
Publication 2711-6.0
Working with Tags
19–11
Sorting Tags
Tags may be sorted on any field or any number of fields in a
user-selected order. Sorted tags are rearranged in the table so editing
similar tags may be done more easily.
Table View only
To sort tags:
1. Choose Sort from the View menu.
2. Under Column, select which field(s) to sort by.
• Double-click on a field name in the Column box.
• Or highlight a field and then select Add.
The Tag Editor moves the field name to the Sort Order box. You
can specify any number of fields in your sort. The default (no
fields in the Sort Order box) is to sort by Tag Name.
3. When all fields for the sort are entered, click OK.
The Tag Editor sorts and displays the tags in the table view.
Fields are sorted in the order they are added to the Sort Order box.
To change the sort order:
1. Highlight a field or fields in the Sort Order box.
2. Select Remove to delete them.
3. Highlight a field or fields in the Column box.
4. Select Add to append them to the end of the Sort Order list.
Or select Cancel and start over.
Publication 2711-6.0
19–12
Working with Tags
Printing Tags
Table View only
Tags may be printed if the computer is connected to a printer and the
correct drivers are installed. See the manual for the printer and the
Windows manual. Make sure your printer is connected and online.
Important:
The Print command is not active if a row is being edited
(indicated by a pencil in the Status column). Select a
different row (which stores the edited row) before
choosing the Print command.
To print tags:
1. Click the Print tool on the tool bar or choose Print from the
Project menu.
Opens Print Setup dialog
Opens Page Setup dialog
Name of current printer that will be used.
See the next section to select a different
printer. This field is reset to the default
printer each time you print.
Note: The name of the current printer is displayed. To change to
a different printer, see the next section.
2. Under Print What, specify whether you want to print All Rows in
the current tag view or only selected rows.
If selecting specific rows, see page 19–8 for details on how to
select contiguous or noncontiguous rows.
3. Select the Print The Cover Page box to print the cover page. The
cover page includes product (Allen-Bradley Tag Editor), project
and view name, date and time.
4. Click OK.
Print Details
• The column width of the printed output is based on the width of
the column in the Tag Editor.
• The Tag Editor prints as many columns that fit on the width of the
page (minus the margins); columns that do not fit are printed on
the next page. The Tag Editor does not print a column if it is less
than one character wide.
• If the entire height of a row does not fit on the page, then the row
is printed on the next page (each row is only one text line high).
Publication 2711-6.0
Working with Tags
19–13
Setting Up the Printer
To set up the printer:
1. Click the Printer Setup button from the Print dialog.
The standard Microsoft Print Setup dialog opens. Dialog entries
are based on your system configuration and installation options.
2. Select printer and determine settings.
Important:
Check your Microsoft Windows user manual to make
sure settings are correct for your printer.
3. Click the Options button to open a dialog and select options
specific to the selected printer.
4. Click OK to the Print dialog.
Setting Up the Page
To set up the page:
1. Click the Page Setup button from the Print dialog or choose Page
Setup from the Project menu.
2. Under Margins, specify page margins (Top, Bottom, Left, Right).
Enter a number for each margin. The measurements are in inches.
Publication 2711-6.0
19–14
Working with Tags
Printing Tags
3. Select the Show Gridlines box to show gridlines in the printed
copy.
4. Select the Use Maximum Width for Each Column box to use the
maximum width for each field.
Clear the box if you want the printed output based on the size of
the columns on the screen. The number of characters that fit in a
column on the screen may be different from the printed output
depending on the fonts available.
5. Enter Line 1 and Line 2 of the Header. Each line supports up to
255 characters. Use the information below to enter text.
6. Click OK to return to the Print dialog.
Entering Header Information
To enter header text:
type text (this text is printed as is)
For example:
if you want to print this:
This is the header.
type one of the following character
sequences:➀➁
&D =
current date ➂
&N =
page number
&T =
current time ➂
&V =
view name
&P =
project name
&B =
space (use to print a blank line)
&A =
product name
(Allen-Bradley Tag Editor)
➀ Character sequences are not case sensitive.
type This is the header.
if you want to print this:
2/2/95 Project 1
type &D &P
If you want to print a blank line, type &B.
If you want to print an &, type &&.
If you enter a character sequence that is not
defined, it is printed as is. For example, if
you enter &Z, then &Z is printed.
➁ If the expanded text is larger than 255 characters, the printed output may look distorted or cut off.
➂ These values are based on Control Panel Settings. See the Microsoft Windows manual for details.
Aligning Header Information
To:
Type:
For example:
left justify text
text or character sequence
(header information is left
justified by default)
For example, if you want to print this:
center text
right justify
text
Publication 2711-6.0
&| before the text or
character sequence
a second &| before text or
character sequence
Project 1
2
2/3/95
type &P&|&N&|&D
text after this text after this
se ond
character
hara ter second
sequence is character
sequence is
centered
right justified
If alignment is specified in part of a header line, make sure the text
does not overlap. For example, if left aligned text runs to the center
of the page, it overlaps centered text.
Working with Tags
19–15
Using Tools
If the Status column or Tag Name column for a specific tag is
selected, the Tools menu gives a list of available tools. From the list
select the tool needed.
Table View only
In some cases, the Tools list may also depend on what software is
installed on the computer system. For example:
• List Editor is the same as the Summary command on the View
menu. It brings up a new Tag Editor table view.
• Form Editor is the same as the Form command on the View
menu. It brings up the Tag Form dialog for the selected tag.
• Import and Export access the Tag Import/Export Utility.
Tag Import/Export Utility
The Tag Import/Export utility copies SLC and PLC-5 tag
information from a supported file format to a project and vice versa.
The supported ASCII file formats are:
This file format:
Is:
Advanced Programming
Software (APS)
the ASCII documentation file produced by the APSIE utility.
This file format is for the SLC processor only. For more
information, see the APS Import/Export Utility User
Manual, publication 1747-6.7.
Advanced Interface (AI)
series software
the WINtelligent series version of the CSV format.
Comma Separated
Value (CSV)
the comma separated value format used by software
packages such as Excel. For more information, see your
user manual for the software package you are using.
Important:
The Import function does not import files created
without keywords or files created with annotations.
Publication 2711-6.0
19–16
Working with Tags
Importing Tags
To import tags:
1. Choose Import from the Tools menu.
2. Select an Input Format (APS ASCII, AI, or CSV).
When you import from APS ASCII format, the Import function
automatically translates special characters in address comments
(AC) used by the APS software as follows:
• backslash (\) is changed to carriage return (<cr>)
• double quotation marks (“”) are changed to a single (”)
• tilde preceding a backslash ( ∼\) is changed to a backslash (\)
AI software does not add the .AI extension on an exported
comment and symbol file. PanelBuilder will not recognize an AI
file without the .AI extension.
3. In the File box, type a source file or click Browse to search for a
source file.
4. Under Destination, select a project and controller used by the
project.
5. Click OK.
The Reading Source File dialog opens followed by the Importing
Tags to Project dialog as the tags are imported. These dialogs
display the percentage complete.
When the Import function is finished importing the tags, the
Summary Report dialog opens.
Click to View the full report.
Click to save the report to a file.
If you want to print the report,
you must save it to a file.
6. Click OK to return to the table view.
Publication 2711-6.0
Working with Tags
19–17
Handling Data Collisions
If two or more tags have the same name, this dialog opens.
Important:
Click:
The Import function does not check for duplicate
addresses, only duplicate names.
To:
Ignore conflicting tags. The tags in the project remain and the
conflicting tags in the input source file are discarded.
Rename the conflicting tags. The Import function adds the following
extension to the duplicate tags:
_# (where # is 1, 2, or 3)
The Import function renames duplicate tag names up to 3 times.
After that, if you try to import a tag with the same name, the
imported tag is discarded.
Update the tags in the project with the data from the imported tags.
Exit the Import/Export utility and return to the Tag Editor.
Publication 2711-6.0
19–18
Working with Tags
Exporting Tags
To export tags:
1. Choose Export from the Tools menu.
2. Select an Output Format (APS ASCII, AI, or CSV).
• When you export to an APS ASCII file:
– If the tag name is longer than 10 characters, the Export
function truncates the name.
– If the description is longer than 50 characters, the Export
function truncates the description.
– If the special characters in the description are equivalent to
those used by APS, the Export function translates them:
carriage return (<cr>) to backslash (\)
quotation mark (”) to double quotation marks (“”)
backslash (\) to tilde-backslash ( ∼\)
– If the tag name contains other special characters, the Export
function deletes them.
• When you export to an AI file:
– If the tag name is longer than 15 characters, the Export
function truncates the name.
– If the description is longer than 75 characters, the Export
function truncates the description.
• When you export to an CSV file:
– If the comment (description) field contains quotation marks,
commas or carriage returns, the Export function puts quotation
marks around the comment field.
– If the comment field contains embedded quotation marks, the
Export function changes them to double quotation marks (“”).
Publication 2711-6.0
Working with Tags
19–19
3. Under Source, select a project and the controller associated with
the project.
4. Under Destination, type a destination file in the File box or click
Browse to search for a destination file.
5. Click OK.
The Exporting Tags From Project dialog opens followed by the
Writing Destination File dialog as the tags are exported. These
dialogs display the percentage complete.
When the Export function is finished exporting the tags, the
Summary Report dialog opens.
Click to View the full report.
Click to save the report to a file.
If you want to print the report,
you must save it to a file.
6. Click OK to return to the table view.
Examining the Results of an Import/Export
To examine detailed results of an import or export, select the View
Report button on the Summary Report dialog. For example, after
importing a file and selecting View Report, this window appears with
the results:
Publication 2711-6.0
19–20
Working with Tags
Interpreting Error Messages
You get this error:
device error – device
does not exist
device error – no device
specified
device error – device not
an SLC processor
parse error ➀
If you:
request a device that does not exist
forget to specify a device
select a device that is not an SLC processor (if
you are importing an APS ASCII file)
try to import one of the following:
• a corrupted file
• an unsupported file type or a file type other than
the type you selected
• a file that has been manually edited with mistakes
file error – file does not
exist ➀
file error – file already
exists ➁
project error
➀
➁
Import only
Export only
Publication 2711-6.0
Work around:
Click No to select or enter another device.
Click Yes to create the device.
This dialog box opens
Select the type of device, enter the device address,
and then click OK.
Click OK, then select or enter a device.
Click OK and then select an SLC device.
Click OK to abort the Tag Import/Export utility.
Choose Import from the Tools menu again and select another file
or fix the bad file and reselect it.
select a source file that does not exist
Click OK. Select another source file or cancel.
select a destination file that does exist
Click Yes to replace the file or No to cancel the operation.
enter a project that does not exist
Click OK. Select another project or cancel.
Terminal and Communication
Setup
Chapter Objectives
This chapter describes how to set communication and operating
parameters for the PanelView terminal. It contains the following
sections:
Section
Page
Terminal Setup Overview
20–2
Defining DH-485 Communications
20–3
Defining DH+ Communications
20–5
Defining DF1 Communications
20–7
Defining Remote I/O Communications
20–9
Defining Block Transfers
20–11
Configuring the Printer Port
20–13
Changing the Terminal Type
20–15
Setting Power-up Options
20–17
Setting Time/Date Format
20–19
Setting Advanced Terminal Options
20–21
Setting a Display Maintenance Schedule
20–23
Defining PLC/SLC Control Tags
20–24
Defining Status Tags
20–26
Note: For details on configuring DeviceNet and ControlNet
communications, see the following publications:
• DeviceNet Communications for PanelView terminals
Publication 2711–6.0.4
• ControlNet Communications for PanelView terminals
Publication 2711–6.10
Publication 2711-6.0
20–2
Terminal and Communication Setup
Terminal Setup Overview
The Terminal Setup command on the Application menu opens the
Terminal Setup dialog. This dialog defines both operating
parameters and communication parameters for runtime operation.
Terminal Name is defined
when application is created.
Appears only if the selected
terminal is equipped with an
RS-232 serial printer port.
The port can be used for
downloading or printing.
The Terminal Setup dialog uses tabs to organize operations by
function.
Select this tab:
To:
Setup
• define run-time communication parameters for terminal and
controller (accessed via Comms. Setup button)
• change the terminal type of a PanelView device
• specify whether to use the RS-232 serial port of the terminal for
printing or downloading applications
• configure communication and printing parameters for those
terminals equipped with an RS-232 printer port
• enable external font support (See Chapter 22)
Power-Up
Advanced
Time/Date
Publication 2711-6.0
Define terminal power-up defaults including:
• startup application screen
• preset values (initial or last state values) to write to controller
• screen to display on a restart (last user screen displayed or the
startup screen)
• whether to load application from memory card
• whether to use downloaded configuration settings
Set other terminal options including:
• auto repeat settings for terminal keys or touch cells.
• display options
• language in which to display terminal firmware messages.
• timeout setting
• time to condition the display of a PV900 monochrome or degauss
the display of a PV1400 color terminal.
Specify how the time and date will display in the terminal.
Control Tags
Define tags for PLC/SLC controlled screen changes and time/date
changes.
Status Tags
Define tags for PanelView terminal controlled screen changes and
time/date changes.
Terminal and Communication Setup
Defining DH-485
Communications
20–3
This section shows how to define runtime parameters for a
PanelView terminal and an SLC controller that will communicate on
a DH-485 network.
DH-485 Network Using RS-485 Connection
A PanelView terminal with a DH-485 port is connected to an SLC
controller using a multidrop or point-to-point connection. You will
define DH-485 parameters for two devices:
• DH-485 PanelView Terminal
• SLC Controller (or MicroLogix 1000)
DH-485 (RS-485) Connection
1747-AIC
Link Coupler
1747-AIC
Link Coupler
DH1–485 Network
SLC Controller – Node 3
SLC Controller – Node 1
PanelView - Node 2
with DH-485 Port
DH-485 Network Using RS-232 Connection
A PanelView terminal with an RS-232 port is connected to the
Channel 0 port of an SLC 5/03 or 5/04 controller providing a
dedicated DH-485 connection for high priority data. You will define
DH-485 parameters for two devices:
• RS-232 (DH-485) PanelView Terminal
• SLC 5/03 or 5/04 Controller
DH-485 (RS-232) Connection
SLC Controller 5/03 or 5/04 - Node 1
DH-485 Network Connection
Channel 0
RS-232 Port
PanelView - Node 2
with RS-232 Port (DH-485 Protocol)
Publication 2711-6.0
20–4
Terminal and Communication Setup
To configure DH-485 communications:
1. Choose the Setup tab from the Terminal Setup dialog.
2. Verify the terminal name entered in the Terminal Name field.
3. Click the Comms. Setup button.
The Communication Setup dialog shows the current DH-485
settings for the PanelView terminal and controller. The first time
you open this dialog, default settings appear.
The terminal name was defined when the application was created.
DH-485 Communications Dialog
Terminal Name
from Setup tab.
Node Types
5/00, 01, 02
5/03 - OS 300
5/03 - OS 301
5/03 - OS 302
5/04 - OS 400
5/04 - OS 401
MicroLogix 1000
Must match Node
Name in Tag Editor.
4. Under Terminal, edit parameters for the PanelView terminal.
Use:
To:
Node Address
Specify the unique address (0 - 31) of the PanelView terminal on the
DH-485 network. The default is 2.
Maximum
Node Address
Specify the highest node address on the network. The default is 31.
A low Maximum Node Address improves network performance.
Baud Rate
Specify the baud rate of the DH-485 network. The options are 1200,
2400, 9600, 19.2K (default).
5. Under Network Nodes, edit the node parameters of the controller.
To insert a node, right-click in any field and select Insert Node
from the shortcut menu. Click in any field to edit it.
Use:
To:
Node Name
Enter a unique name for the controller that will communicate with
the PanelView terminal on the DH-485 network.
• If you enter a new name/address, a device is added to the project.
• If you select the name of an existing device, the node address and
node type automatically appear for that device.
Select the node address (0 to 31) of the controller on the DH-485
network. The default is 1.
Node Address
Node Type
Select the type of controller.
To delete a node, right-click in a node field and select Delete
Node from the shortcut menu. From this menu, you can also sort
multiple nodes by name, address, type or only modified nodes.
To copy, rename or delete devices from a project, see page 21–4
6. Click OK to exit and return to Terminal Setup dialog.
Publication 2711-6.0
Terminal and Communication Setup
Defining DH+
Communications
20–5
This section shows how to define runtime parameters for a
PanelView terminal and a PLC or SLC 5/04 controller that will
communicate on a DH+ link.
You will define parameters for these two devices:
• DH+ PanelView Terminal
• PLC 5 or SLC 5/04 Controller
PLC 5 Controller
PanelView Terminal
SLC 5/04 Controller
or
DH+ Port
DH+ Link
Addressing for a DH+ application is similar to DH-485 applications
except the DH+ link supports 64 nodes (0 - 77 octal); the DH-485
link supports 32 nodes. The DH+ link supports higher baud rates.
To configure DH+ communications:
1. Choose the Setup tab from the Terminal Setup dialog.
2. Verify the terminal name entered in the Terminal Name field.
3. Click the Comms. Setup button.
The Communication Setup dialog shows the current DH+ settings
for the PanelView terminal and controller. The first time you
open this dialog, default settings appear.
The terminal name was defined when the application was created.
Terminal Name
from Setup tab.
Node Types
Must match Node
Name in Tag Editor.
SLC 5/04
PLC-5/10
PLC-5/11
PLC-5/12
PLC-5/15
PLC-5/20
PLC-5/25
PLC-5/30
PLC-5/40
PLC-5/60
PLC-5/80
Publication 2711-6.0
20–6
Terminal and Communication Setup
4. Under Terminal, edit the following parameters.
Use:
To:
Node Address
Select the station number (0 to 77 octal) of the
PanelView terminal on the DH+ link.
Baud Rate
Select the baud rate of the DH+ link. The baud
rates and maximum cable lengths for each rate
are:
57.6K
3,048 m (10,000 ft)
115.2K 1,524 m (5,000 ft)
230.4K 762 m (2,500 ft)
5. Under Network Nodes, edit the node parameters of the controller.
To insert a network node, right–click in the Node Name field and
select Insert Node from the menu. Click in a field to edit it.
Use:
To:
Node Name
Enter a unique name for the logic controller that
will communicate with the PanelView terminal on
the DH+ link.
Node Address
Select the station number (0 to 77 octal) of the
logic controller on the DH+ link.
Node Type
Select the type of logic controller that will
communicate with the PanelView terminal.
To delete a node, right-click in a node field and select Delete
Node from the shortcut menu. From this menu, you can also sort
multiple nodes by name, address, type or only modified nodes.
To copy, rename or delete devices from a project, use the Project
Management command. See page 21–4
6. Click OK to exit and return to the Terminal Setup dialog.
Publication 2711-6.0
Terminal and Communication Setup
Defining DF1
Communications
20–7
This section shows how to define runtime parameters for a
PanelView terminal and a controller that will communicate using
DF1 full duplex communications over a point-to-point link or DF1
network.
You define parameters for these two devices:
• DF1 PanelView Terminal
• SLC, PLC or MicroLogix controller
PLC 5 Controller
PanelView
SLC
or
DF1 Port
DF1 Port
AIC+
1761–NET–AIC
PanelView
MicroLogix 1000
DF1 Port
DF1 Port
To configure DF1 communications:
1. Choose the Setup tab from the Terminal Setup dialog.
2. Verify the terminal name entered in the Terminal Name field.
3. Click the Comms. Setup button.
The Communication Setup dialog shows the current DF1 settings
for the PanelView terminal and controller. The first time you
open this dialog, default settings appear.
The terminal name was defined when the application was created.
Terminal Name
from Setup tab.
Select only when using DF1
network communications.
Must match Node
Name in Tag Editor.
MicroLogix 1000
SLC 5/03, 5/04, 5/05
PLC-5/10, 5/12, 5/15, 5/25 via bridge
PLC-5/11, 5/20, 5/26, 5/40, 5/46, 5/60, 5/80 via Channel 0 Port
PLC-5/20C, 5/40C, 5/60C, 5/80C via Channel 0 Port
PLC-5/20E, 5/40E, 5/80E via Channel 0 Port
Publication 2711-6.0
20–8
Terminal and Communication Setup
4. Under Terminal, edit the following parameters.
Use:
To:
Node Address
Specify the node address (0 to 254 decimal) of
the terminal for DF1 network communications. For
network communications, click the Use
Networking check box.
For point–to–point communications with an SLC,
PLC, MicroLogix 1000 or 1761–NET DNI module,
the default node address of 64 is used.
Baud Rate
Select the baud rate of the terminal on the DF1
link. The baud rate must match the baud rate of
the target device.
Valid baud rates are: 1200, 2400, 4800, 9600,
19200. The default is 9600.
Parity/Stop Bits
Select the parity and number of stop bits used by
the DF1 port on the terminal. The number of data
bits is always 8. Your selection must match the
settings of the target device.
PLC controllers allow a parity of Even or None.
For SLC controllers the parity is fixed at None.
Error Detect
Select the type of error detection performed on
data. The options are CRC (Cyclic Redundancy
Check) and BCC (Block Check Character). The
default is CRC.
Handshake
Specify whether handshaking is used by the DF1
port. The default is Off or no handshaking.
If handshaking is On, the CTS and RTS lines are
enabled.
5. Under Network Nodes, edit the node parameters of the controller.
To insert a network node, right–click in the Node Name field and
select Insert Node from the menu. Click in a field to edit it.
Use:
To:
Node Name
Enter a unique name for the logic controller that
will communicate with the PanelView terminal on
the DF1 link.
Node Address
Select the node address (0 to 254 decimal) of the
controller on the DF1 link.
Node Type
Select the type of controller that will communicate
with the PanelView terminal.
To delete a node, right-click in a node field and select Delete
Node from the shortcut menu. From this menu, you can also sort
multiple nodes by name, address, type or only modified nodes.
To copy, rename or delete devices from a project, use the Project
Management command. See page 21–4
6. Click OK to exit and return to the Terminal Setup dialog.
Publication 2711-6.0
Terminal and Communication Setup
Defining Remote I/O
Communications
20–9
This section shows how to define runtime parameters for a
PanelView terminal and PLC or SLC that will communicate on a
Remote I/O link.
The PanelView terminal operates as a single rack on the network.
You will define parameters for these two devices:
• Remote I/O PanelView Terminal
• PLC or SLC (with 1747-SN Scanner) Controller
SLC Controller
with 1747-SN Scanner
PLC Controller
PanelView Terminal
or
RIO Port
Remote I/O Network
The following table defines the PLC/Scanner types with options
supported by the Remote I/O PanelView terminal.
Lowest
Rack #
Highest
Rack #
Pass-Through Support
Block Transfer Support
IBM PC 6008-SI
VME
V
E 6008-SV
DEC
EC QBUS
S 6008-SQ
6008-S
0
7
No
Yes
PLC 5/11
3
3
All Series, All Revisions
Yes
PLC 5/15
1
3
Series B, Revision N or later
Yes
PLC 5/20
1
3
All Series, All Revisions
Yes
PLC 5/25
1
7
Series A, Revision J or later
Yes
PLC 5/30
1
7
Series A, Revision B or later
Yes
PLC 5/40
1
17octal
Series A, Revision E or later
Series B, Revision B or later
Yes
PLC 5/60
PLC 5/80
1
27octal
Series A, Revision E or later
Series B, Revision B or later
SLC 1747-SN Series A
0
3
No
No
SLC 1747-SN Series B
0
3
Yes
Yes
Other 1771-SN Subsystem
1
7
No
No
Controller/Scanner
Yes
To configure Remote I/O communications:
1. Select the Setup tab from the Terminal Setup dialog.
2. Verify the terminal name entered in the Terminal Name field
The terminal name was defined when the application was created.
Publication 2711-6.0
20–10
Terminal and Communication Setup
3. Click the Comms. Setup button.
The Communication Setup dialog shows Remote I/O parameters
for the PanelView terminal and the PLC/Scanner.
Remote I/O Communications Dialog
Terminal Name
from Setup tab.
Must match Node
Name in Tag Editor.
Settings are automatically
validated for the selected
PLC/Scanner type.
If you get an error message,
clear the Rack field.
4. Under PLC/Scanner, edit Remote I/O parameters for the PLC.
Use:
To:
Type
Specify the type of PLC controller that will communicate with the
terminal on the Remote I/O network. See Table 20.A.
Name
Enter a unique name for the PLC/Scanner.
• If you enter a new name/address, a device is added to the project.
• If you select the name of an existing PLC/Scanner device, the
Rack address and PLC/Scanner Type automatically appear for
that device.
To copy, rename or delete devices from a project, use the Project
Management command. See page 21–4.
5. Under Terminal, edit Remote I/O parameters for the PanelView
terminal.
Use:
To:
Rack
Specify the unique address (0 - 76 octal) of the
PanelView terminal on the remote I/O link.
The options are limited to the rack addresses supported by the
controller/scanner.
Module Group
Specify the module groups used by the terminal in the rack.
Each box represents 2 module groups. The module groups
must be contiguous.
Last Chassis
Specify whether the terminal occupies the last module group
(no higher module groups assigned) within the rack.
Baud Rate
Specify the baud rate used on the Remote I/O link. The
options (and maximum cable lengths) are:
57.6K
10,000 feet (default)
115.2K 5,000 feet
230.4K 2,500 feet
6. Click OK to save the settings and return to Terminal Setup.
Publication 2711-6.0
Terminal and Communication Setup
Defining Block Transfers
20–11
Use block transfers on a Remote I/O link to transfer:
• data or
• applications from a computer on the DH+ network to a terminal
on the Remote I/O network using Pass-Through
You can create up to 10 block transfer channels, numbered 1 – 10.
Each channel is associated with a block transfer read or write
instruction (BTR or BTW) in the controller ladder logic.
To define block transfers:
1. Click the Block Transfer button from the Communication Setup
dialog.
If the controller/scanner does not support block transfers, the
Block Transfer button is dimmed.
2. Enter the block transfer parameters starting with 1.
Use:
To:
Enabled
Enable or disable the block transfer. The default is disabled.
Address
Specify the starting address of the block transfer in a native
SLC or PLC (Remote I/O) link.
Mode
Specify Read or Write.
Length
Specify the number of words (1–64) required by a block
transfer. The default is 64. A length of 63 is reserved for
Pass-Through.
Each block transfer must use a different starting address, length
and read/write mode.
3. Repeat step 2 for each additional block transfer required.
4. If downloading applications from a computer on the DH+
network, you must select the Pass-Through check box.
Note: If Pass-Through is not supported by controller, the check
box is dimmed.
Publication 2711-6.0
20–12
Terminal and Communication Setup
5. Select a Block Transfer Timeout value (0–60 seconds).
A value of 0 disables the timeout which means the terminal will
not generate Block Transfer timeout warnings.
6. Click OK to return to the Communication Setup dialog.
The dialog below shows 2 block transfer assignments. It also shows
that Pass-Through is enabled for application transfers from a DH+
network.
Publication 2711-6.0
Terminal and Communication Setup
Configuring
the Printer Port
20–13
This section shows how to configure:
• communication parameters
• print parameters
for those terminals equipped with an RS-232 serial port.
The Setup tab of the Terminal Setup dialog indicates whether the
terminal has an RS-232 port. If Printing is selected in the Serial Port
Usage area, the serial port is configured with the settings below.
The printer port settings are downloaded with the application if the
“Use downloaded configuration settings” option is enabled on the
Power-Up tab of the Terminal Setup dialog.
To configure the printer port of the PanelView terminal:
1. The selected PanelView terminal must have an RS-232 port.
2. Click the Printer Setup button from the Setup tab of the Terminal
Setup dialog.
3. Specify the communication parameters for the serial printer port.
Use:
To:
Baud Rate
Set the baud rate of the printer port. The baud rate must match
the printer’s baud rate. The options are 1200, 2400, 4800,
9600, 19200. The default is 9600.
Parity
Specify Even, Odd or No parity. The default is None.
Data Bits
Specify 7 or 8 data bits. The default is 8.
Stop Bits
Specify 1 or 2 stop bits. The default is 1.
Handshaking
Specify how handshaking is handled. The options are
Software, Hardware, or None. The default is None.
Refer to your printer’s user manual for details on how to set
communication parameters for the printer.
Publication 2711-6.0
20–14
Terminal and Communication Setup
4. Configure print parameters for the printer.
Use:
To:
Left Margin
Specify the left page margin for printing. The left margin
must be < than the page width.
Page Width
Specify the number of characters to print per line. Valid
settings are 20–132. The default is 80 characters.
Perforation Skip Value
Specify the number of blank lines at the top and bottom of
each page. The default is 6. The value must be < the page
length. A value of 0 disables this parameter.
If the page length is 66 and the skip value is 5, the page is
formatted as 2 blank lines, 61 printed lines, and 3 blank
lines. The extra line is always at the bottom.
EOL Char
Specify the End of Line Character. The options are CR
(Carriage Return) and CR+LF (Carriage Return and Line
Feed). The default is CR.
Page Length
Specify the number of lines to print per page. Valid
settings are 0–255. The default is 66 lines. The value of 0
indicates continuous printing with no page breaks.
New Page Control
Specify what controls a page break. The options are Form
Feed or blank lines. The default is Form Feed.
5. Type the characters in the Printer Initialization String box that
will initialize the printer after communications is established.
The initialization string can contain a maximum of 20 characters.
The default is a Null string. Use these rules when entering string:
• to enter control characters (decimal values 0 – 31), type ^
before the character. Upper or lowercase is accepted (c or C).
To Enter:
Decimal Value
Type:
CTRL @
0
^@
CTRL A – CTRL Z
1 – 26
^A – ^Z
CTRL [
27
^[
CTRL \
28
^\
CTRL ]
29
^]
CTRL^
30
^^
CTRL_
31
^_
• to enter a literal character, precede the character with a
backslash \. For example, to enter ^, type \^.
• to enter decimal values between 126 – 256, precede the
decimal value with the backslash \. For example, to enter the
decimal equivalent of 255, type \255.
• each sequence preceded with ^ or \ represents a single
character in the initialization string. For example, \255 and \^
each represent one character in the 20 character string.
6. Click the Save as Defaults button to save the settings.
7. Click OK to exit and return to the Setup tab.
Publication 2711-6.0
Terminal and Communication Setup
Changing the
Terminal Type
20–15
You can convert an application from one terminal type to another
terminal. However, you may need to modify properties of the
application to make it compatible with the terminal.
Converting Application from Touch Screen to Keypad
If converting an application from a Touch (or Keypad & Touch) to a
Keypad, you must assign function key input to screen objects.
Converting Application to another Terminal Type
If converting an application to a different terminal type (for example,
900 to 600), you may need to reduce the number of objects on the
screen, adjust the location/size of objects, or change the grid spacing.
Converting Application to another Communication Protocol
If converting an application to a different communication protocol,
(for example, Remote I/O to DH-485), you must update the terminal
setup and tags appropriately.
• update the communication parameters for the PanelView terminal
and controller in the Communication Setup dialog.
• update the tags (address and node name) in the Tag Editor.
Converting Application from Monochrome to Color or Grayscale
If converting a monochrome application to a color or grayscale
application, the following dialog open.
Select the colors to use when converting the application.
• background color of screen (default is black)
• foreground color of objects (default is white)
• background color of objects (default is black)
If the background/foreground colors of objects were reversed, the
above colors would be the opposite.
Converting Application from Color to Grayscale
If converting a color application to a grayscale application:
• screen background is converted to black
• colors are converted to the closest shade of gray
• color bitmaps are converted to grayscale bitmaps
Also, text sizes are converted to the closest matching font in the new
application. You may want to resize the text.
Publication 2711-6.0
20–16
Terminal and Communication Setup
Converting Application from Color to Monochrome
If converting a color application to a monochrome application, all
colors are removed from the screen.
• screen background is converted to white
• brighter colors of objects are converted to white
• darker colors of objects are converted to black
• color bitmaps are converted to monochrome bitmaps
Also, the text sizes are converted to the closest matching size in the
new application. You may want to resize the text.
Converting Application to a Terminal without Printer Support
If converting an application that supports printing (terminal has
RS-232 printer port) to an application that does not support printing:
• the print attribute is removed from appropriate objects.
• an error message is generated for Print Only Objects that are used
by the application (the message indicates the specific object).
To change the terminal type of a PanelView device:
1. Choose Terminal Setup from the Application menu.
2. Select the Setup tab.
The dialog shows information associated with the terminal name
when the application was first created.
3. From the Terminal Name list box, select another name if the
application is to run in a different terminal.
4. Under Terminal Type Information, define the terminal in which
the application will run, by choosing options in this order:
• select a terminal from PV Type box
• select Keypad, Touch or Keypad & Touch
• select a Catalog number and firmware Version (only the
options that fit the selected terminal type are displayed)
The Ports area shows the ports on the selected terminal. If the
terminal has an RS-232 port, the Serial Port Usage area shows
whether the port is used for printing or downloading.
5. Click OK.
If the selected terminal does not use the same communication
protocol as the application, you are asked if you want to convert
the application to match the terminal’s protocol.
Publication 2711-6.0
Terminal and Communication Setup
Setting Power-up Options
20–17
The Power-Up tab in the Terminal Setup dialog defines default
operating parameters for the PanelView terminal on power-up:
• startup screen for application
• whether to write object preset values (initial presets or last
terminal state values) to controller
• screen to display on power-up
• memory card load conditions
• configuration settings to use on first power-up after download
To set or change power-up defaults for the terminal:
1. Select the Power-Up tab in the Terminal Setup dialog.
2. From the Startup Screen list box, select the first screen to display
when the application starts in the terminal.
3. Select the Write to Controller on Startup check box if you want to
write preset values for objects to the controller on startup. The
default is to not write values to the controller.
Note: Remote I/O and DeviceNet terminals always write preset
values to the controller on startup. The Write to Controller on
Startup check box is always selected for these terminals.
4. If you select Write to Controller on Startup, you can choose either
Use Terminal Presets or Use Last Terminal States.
Select:
To:
Use Terminal Presets
Write initial values set by application.
Use Last Terminal States
Write values present prior to power-up. This is the
default.
Publication 2711-6.0
20–18
Terminal and Communication Setup
Note: Terminal presets for control objects are set in the object’s
dialog. These values override initial values entered in the Tag
Editor except for numeric entry objects. Initial values for
numeric entry objects are set in the Tag Editor.
5. Specify whether to display the Last user screen on restart or the
startup screen. The default is to display the last user screen.
To display the startup screen, clear the check box.
6. Under Memory Card, specify what action the terminal should
automatically take on a restart if a memory card is loaded in the
terminal. The memory card stores only one application.
Select:
To:
Always Load from Card
Always load the application on the memory card.
Never Load from Card
Require the operator to load a specific
application from the memory card using the
Memory Card Transfers option in the
Configuration Mode menu.
Load from Card if Invalid
Application Detected
Load the application on the memory card only if
the current application in the terminal is invalid.
If a memory card isn’t loaded or if the card contains more than
one file, the terminal restarts with the application that was
running before the restart.
From the terminal, you can also manually download a memory
card application to the terminal by selecting Memory Card from
the Configuration Screen and then the Restore From Card option.
7. Specify whether or not to Use downloaded configuration settings
on the first restart after a download. The default is to use the
configuration settings downloaded with the application.
To use the current settings in the terminal on a restart, click the
check box until the X disappears.
8. Click OK to save the settings and exit the dialog.
Publication 2711-6.0
Terminal and Communication Setup
Setting Time/Date Format
20–19
The Time/Date tab in the Terminal Setup dialog specifies how the
time and date are displayed on the PanelView terminal.
With dates, you can vary the order of the month, day and year or
change the punctuation used to separate parts of the date. You can
display times in 12-hour or 24-hour format with different suffix
notations such as AM for morning or PST for Pacific Standard Time.
Date Formats
Time Formats
Month/Day/Year
7/3/99
With Leading Zeroes
07/03/99
12-Hour Format
2:56
Day/Month/Year
3/7/99
With 4-digit Year
7/3/1999
24-Hour Format
14:56
Year/Month/Day
99/7/3
With User
Defined Separator
7*3*99
With Seconds
14:56:29
With Time Zone & Time
Standard Designations
2:56 PM CST
With Leading Zeroes
02:56
With User
Defined Separator
14*56*29
To activate the time/date settings in the PanelView terminal, you
must enable the “Use downloaded configuration settings” option in
the Power–Up tab on the Terminal Setup dialog.
To change the time or date format used by the terminal:
1. Select the Time/Date tab from the Terminal Setup dialog.
2. Set the options you want for the date format. The Sample area
displays the format as you select options.
Publication 2711-6.0
20–20
Terminal and Communication Setup
The following table describes the options.
Use:
To:
Order
Specify the order of the month (M), day (D), and year (Y). The
initial default is MDY.
Separator
Specify the character to separate the month, day and year. You
can enter any character as the separator. The default is the
slash (/).
Day/Month
Leading Zero
Specify that the day or month appears as two digits. For
example, February 7 appears as 02–07. By default leading
zeros are not displayed, 2-7.
Year
Specify the year as two digits or four digits. For example, the
year 1994 can display as 94 or 1994.
3. Set the options you want for the time format. The Sample area
displays the format as you select options.
The following table describes the options.
Use:
To:
12-Hour
Display the time in numbers representing hours between 0 and
11 (00:00 – 11:59).
The boxes to the right specify AM or PM, or other notations
such as CST, PST or EST.
24-Hour
Display the time in numbers representing hours between 0 and
23. (00:00 - 23:59).
The box to right specifies a notation such as CST, PST or EST.
Separator
Specify a character to separate the hours, minutes, and
seconds. The default separator is the colon (:).
Leading Zero
Display the hours before ten as a two digit number with a
leading zero. For example, 3:15 would display as 03:15. By
default, the leading zero is not displayed.
Display
Seconds
Display seconds. The default is to display seconds.
4. Click OK to save the settings and exit the dialog.
Publication 2711-6.0
Terminal and Communication Setup
Setting Advanced
Terminal Options
20–21
The Advanced tab in the Terminal Setup dialog sets advanced
options on the PanelView terminal, including how to:
• set auto repeat settings for the terminal keys and touch cells
• set terminal display and options
• set language for terminal messages
• set timeout for objects with handshake tags
• set time to perform display maintenance of terminal
To activate the Advanced terminal options in the PanelView
terminal, you must enable the “Use downloaded configuration
settings” option in the Power-Up tab on the Terminal Setup dialog.
To set advanced options for the PanelView terminal:
1. Select the Advanced tab from the Terminal Setup dialog.
PanelView 550
Other PanelView Terminals
On monochrome terminals, Reverse Video replaces Background Blink.
Gray scale terminals do have the Display Intensity setting.
2. Under Touch & Key Auto Repeat, set auto repeat settings for the
terminal keys and touch cells. These settings are used only by the
up and down arrow keys to move the cursor in control lists and
screen lists.
Use:
To:
Rate
Specify how fast a key or touch cell repeats when it’s pressed and
held. Valid rates are 0 to 5 Hz, where:
0 = no repeat
1 = repeats every second
2 = repeats every 1/2 second
3 = repeats every 1/3 second
4 = repeats every 1/4 second
5 = repeats every 1/5 second
Delay
Specify how long the terminal waits after a key or touch cell is pressed
before it repeats. Options are .2, .4, .6, .8, 1.0, 1.5, 2.0, 2.5 seconds.
The default is .4 second.
Publication 2711-6.0
20–22
Terminal and Communication Setup
3. Set Terminal Display parameters.
For PanelView 550
Use:
To:
Reverse Video
Enable/disable reverse video. Default is disabled.
Indicator Bar Blink
Enables/disables blinking of the indicator bar on the terminal.
By default, the indicator bar does not blink.
Backlight
Set the state of the terminal backlight at startup. Select On to
turn the backlight on; select Off to turn the backlight off.
Use:
To:
Background Blink
(Color)
Enable/disables blinking using the background color of the
screen. By default, background blinking is disabled.
Reverse Video
(monochrome &
grayscale)
Enable/disable reverse video (dark text/graphics on light
background). The default is normal video (light text/graphics on
dark background).
For other PanelView Terminals
For PV900 monochrome terminals, sets the intensity of the
display. Options are 35, 40, 50, 60, 70, 80, 90, 100. The
default is 100 (highest intensity).
Display Intensity
Indicator Bar Blink
Screen Saver
On or Off
Timeout
Display
Intensity
Graphic
For color terminals, sets the intensity of the display.
PV900 settings: 50, 60, 70, 80, 90, 100 (default, highest
setting). PV600/1000 settings: 10 to 100, in 10 step
increments. PV1400 settings: 25, 50, 75, 100.
Enables/disables blinking of the indicator bar on the terminal.
By default, the indicator bar does not blink.
Turn the screen saver on or off. The default is off.
The On setting reduces the screen intensity if user input or
controller changes are not received within the specified timeout.
Set the period of time before an inactive screen enters screen
saver mode. Settings: 5, 10, 15, 20, 25, 30 (minutes).
For PV900 monochrome terminals, sets the display intensity in
screen saver mode. Settings: 0, 35, 40, 50, 60, 70, 80, 90, 100.
For color and grayscale terminals, sets the display intensity in
screen saver mode. PV600/1000C settings: 0 – 100, in
increments of 10. PV900C settings: 0, 50, 60, 70, 80, 90, 100.
PV1000G settings: 0, 100. PV1400 settings: 0, 25, 50, 75, 100.
Lists the available screen savers. The screen saver starts
automatically if your terminal is inactive for a specified time.
4. From the System Language box, select the language in which the
terminal displays error messages. The options are: French,
German, Italian, Spanish, English. The default is English.
5. From the Handshake Timeout list box, select a timeout value (in
seconds). For objects with handshake tags, this timeout specifies
the length of time the controller has to set a handshake bit before
an error message is displayed.
Handshake timeout values range from 1 to 60 seconds. The
default is 4 seconds.
6. Click OK to save settings and exit dialog.
Publication 2711-6.0
Terminal and Communication Setup
Setting a Display
Maintenance Schedule
20–23
The Display Maintenance Setup dialog allows you to set a daily
schedule for:
• conditioning the display of a PanelView 900 monochrome
terminal to prevent image burn in.
• degaussing (or demagnetizing) the display of a PanelView 1400.
Default maintenance for these terminals occurs at 12:00 am every
day. The maintenance will not start until the terminal is inactive.
Conditioning of the PV900 takes approximately 30 minutes;
degaussing of the PV1400 takes a few seconds.
The display maintenance schedule is downloaded with the
application if the “Use downloaded configuration settings” option is
enabled on the Power-Up tab of the Terminal Setup dialog.
To set a daily schedule for display maintenance:
1. Click the Maintenance button from the Advanced tab of the
Terminal Setup dialog.
This button is only available for PV900 monochrome and
PV1400 color terminals.
2. Select the Enable Display Maintenance check box to
enable/disable display maintenance. The default is enabled.
3. From the Hour list box, select the hour (0 – 23) at which to start
the display maintenance. The hour is defined in 24-hour military
time. The default is 0 or 12:00 am.
4. From the Minute list box, select the minute (0 – 59) of the hour at
which to start the display maintenance.
5. Click OK to exit and return to the Advanced tab.
Publication 2711-6.0
20–24
Terminal and Communication Setup
Defining PLC/SLC
Control Tags
The PLC/SLC uses control tags to display specific screens and to
control the time/date on the PanelView terminal. The time and date
are updated every minute. The screen that the controller selects will
override the current PanelView screen and take the operator to the
current screen for that state of the operation.
To create or edit control tags:
1. Select the Control Tags tab in the Terminal Setup dialog.
2. Enter or select tag names for one or more control options. The
table below defines each option.
To clear a tag name field, highlight the text and press DELETE.
3. Click the Edit Tag button to edit the definition of a tag name or
edit the definition later using the Tag Editor.
4. Click OK to save the settings and exit the dialog.
Terminal
Control Tags
Description
Valid
Data Types
Screen
Number
Name of tag address where the controller writes a screen
number to control a screen change.
For operator controlled screen changes, the Screen Number
tag address must contain a 0.
Unsigned Integer
Date
Names of tag addresses where the controller writes the current
year, month and day for date displays.
The value at the Year tag address must be 2 digits (90–99 for
1990–1999 or 00–89 for 2000–2089).
Unsigned Integer
To maintain Y2 compliance, the ladder logic must perform the
following conversions before sending the value to the terminal:
– If the year is 1999, subtract 1900
– If the year is > 1999, subtract 2000
Time
Publication 2711-6.0
Names of tag addresses where the controller writes the current
hour, minutes and seconds for time displays.
Unsigned Integer
Terminal and Communication Setup
20–25
Control Tags Example
In the following example, a screen control tag is used to display
caution and operator information screens. The controller writes a
screen number to the PanelView whenever operating parameters
exceed predefined limits. The PanelView is configured with the
following screen and control tag information:
Screen Number Tag:
Tag Name = Screen
Tag Address = N7:10
Screen 10:
Configured as Information Screen
Screen 11:
Configured as Caution Screen
➀ The Controller monitors an automatic sorting process. A bar
code reader signals the presence of a package requiring an
operator’s attention. The controller logic program writes a
value of 10 to address N7:10.
➁ The PanelView reads the value (10) at the Screen
tag (N7:10). Screen number 10 is displayed.
➅ The PanelView reads the value (11) at the Screen
tag (N7:10). Screen number 11 is displayed.
Verify Label Content
Label
Approved
New
Package Screen
Removed
Value 10 to N7:10
Conveyor Overload!
Conveyor
Stopped
Restart
Screen 10 displayed.
Screen 11 displayed.
➂ The controller writes a value of 0 to the control tag
N7:10 to return control of the displayed screen back to
the operator. If the control tag contains any address
other than 0, the operator can not change the screen.
➄ The Controller continues to monitor the process.
A jam on a conveyor requires immediate attention
by the operator. The controller writes a value of
11 to address N7:10.
➃ The operator responds and selects another screen.
The PanelView continues to monitor the process.
Value 0 to N7:10
Value 11 to N7:10
System Status
500 Processed
10 Rejected
New
Screen
System monitoring screen displayed.
Publication 2711-6.0
20–26
Terminal and Communication Setup
Defining Status Tags
The controller uses status tags to read the status of the current screen
number and date/time. The time and date are updated every minute.
To edit or create terminal status tags:
1. Select the Status Tags tab in the Terminal Setup dialog.
2. Enter or select tag names for each status option. The table below
defines each option.
To clear a tag name field, highlight the text and press DELETE.
3. Click the Edit Tag button to edit the definition of a tag name or
edit the definition later using the Tag Editor.
4. If desired, change Time/Date Output Interval (Min). Values range
from 1 to 60 minutes. The default is 1 minute.
Setting the interval to 60 minutes reduces traffic on the network
but also reduces the accuracy of the displayed time.
If you detect a problem with screen changes on a busy network,
increase the output interval.
5. Click OK to save the settings and exit the dialog.
Terminal
Status Tags
Publication 2711-6.0
Description
Valid
Data Types
Screen Number
Name of the tag address to which the
PanelView writes the current screen number.
Unsigned Integer
Date
Names of tag addresses where the PanelView writes the
current year, month and day.
The value at the Year tag address must be 2 digits (90–99
for 1990–1999 or 00–89 for 2000–2089).
The ladder logic must perform the following conversions
before sending the values to the controller:
– If the year is 1999, add 1900
– If the year is > 1999, add 2000
Unsigned Integer
Time
Names of tag addresses to which the PanelView writes
the current hour, minutes and seconds.
Unsigned Integer
Managing Projects
Chapter Objectives
This chapter contains these sections:
Sections
About Projects
Page
About Projects
21–1
Managing Projects
21–2
Managing Devices in Projects
21–4
Copying a Project to Another Computer
21–6
Restoring a Project
21–7
Moving an Application to Another Computer
21–7
Verifying Tags and Devices in a Project
21–8
Adding Unknown Tags or Devices to a Project
21–9
Setting Preferences for Verifying Tags and Devices
21–10
Restoring a Project Created with a Restricted Release
of PanelBuilder
21–11
Each PanelBuilder application (.PBA file) is associated with a
project, located in the C:\AB\PROJECTS folder. The project
contains:
• tag definitions
• device information (terminal type and controller)
required for the terminal to communicate with data table addresses in
the controller.
Tags and devices are specific to the communication protocol used by
the terminal (for example, DH-485 or Remote I/O). Different
applications can share a project if they use the same communication
protocol.
For example, a project for a Remote I/O application requires a
Remote I/O PanelView terminal, a valid PLC controller and tags
with PLC formatted addresses (or SLC with SN Scanner and tags
with SLC formatted addresses). A project for a DH-485 application
requires a DH-485 PanelView terminal, an SLC controller and tags
with SLC formatted addresses.
You can change the project associated with an application from the
Project Management dialog. From this dialog, you can also copy,
rename or delete projects and devices.
Publication 2711-6.0
21–2
Managing Projects
Managing Projects
The Project tab in the Project Management dialog lets you:
• view the current project for an open application
• change the current project for an application
• create a new project
• rename a project
• make a copy of an existing project
• delete a project
An application must be open to change the project associated with
the application. For all other project operations, however, the
application does not have to be open.
To manipulate projects:
1. Choose Project Management from the Application menu.
The Project Management dialog opens.
2. Select the Projects tab.
The Project tab shows the project that is currently used by the
application and a list of existing projects.
If an application is not opened, the Current Project field is blank.
3. Perform an operation as defined in the table on the next page.
4. Click Done.
Publication 2711-6.0
Managing Projects
21–3
Project Operations
To:
Do this:
Change the
current project
An application must be opened, to view or change the current
project associated with the application.
1. From the Current Project box, select the project you want
to associate with the opened application.
2. Click Done. You are asked to confirm the change.
PanelBuilder validates the project for a valid terminal type and
controller device.
Create a new project
1. Click the New button.
2. In the dialog that opens, enter a unique 1 to 32
character name for the new project. The name cannot start
with a number or contain spaces.
3. Click the OK button.
The project appears in the Existing Projects list under the new
name.
Rename a project
1. From the Existing Devices list, select the project you want
to rename.
2. Click the Rename button.
3. In the dialog that opens, enter a new 1 to 32 character
name for the project. The name cannot start with a number
or contain spaces.
4. Click the OK button.
The project appears in the Existing Devices list under the new
name; not the old.
Copy a project
1. From the Existing Devices list, select the project you want
to copy.
2. Click the Copy button.
3. In the dialog that opens, enter a new 1 to 32 character
name for the copied project. The name cannot start with a
number or contain spaces.
4. Click the OK button.
Two versions of the project now exist; one under the original
name and one under the new name.
Delete a project
1. From the list of Existing Projects, select the project you
want to delete. You cannot select the project currently
used by the application.
2. Click the Delete button. You are asked to confirm the
deletion.
3. Click Yes to delete the project.
If more than one project is to be deleted, click Yes for each
project or Yes to All.
All tag definitions associated with the project are permanently
removed.
Important: Do not use DOS or Windows tools to delete
projects.
Publication 2711-6.0
21–4
Managing Projects
Managing Devices
in Projects
The Devices tab in the Project Management dialog lets you:
• view PanelView terminal devices and PLC/SLC devices that are
currently defined for a project
• rename a device
• make a copy of an existing device
• delete a device
You cannot create new devices from the Project Management dialog.
• PanelView terminal devices are added to a project when an
application is first created using the New Application dialog.
• Controller devices are added to a project using the Comms. Setup
button on the Terminal Setup dialog.
To manipulate devices:
1. Choose Project Management from the Application menu.
The Project Management dialog opens.
2. Select the Devices tab.
The Devices tab shows devices currently defined in a project.
3. Perform an operation as defined in the table on the next page.
4. Click Done.
Publication 2711-6.0
Managing Projects
21–5
Device Operations
To:
Do this:
View or edit devices
for a project
From the Current Project box, select a project name.
The Existing Devices list shows all devices (PanelView
terminals and controllers) defined for the selected project.
Rename a device
1. From the Existing Devices list, select the device you want
to rename.
2. Click the Rename button.
3. In the dialog that opens, enter a new 1 to 32 character
name for the device. The name cannot start with a number
or contain spaces.
4. Click the OK button.
The device appears in the Existing Devices list under the new
name; not the old.
Copy of a device
1. From the Existing Devices list, select the device you want
to copy.
2. Click the Copy button.
3. In the dialog that opens, enter a new 1 to 32 character
name for the copied device. The name cannot start with a
number or contain spaces.
4. Click the OK button.
Two versions of the device now exist; one under the original
name and one under the new name.
Delete a device
1. From the list of Existing Devices, select the device you
want to delete.
2. Click the Delete button. You are asked to confirm the
deletion.
3. Click Yes.
If more than one device is to be deleted, click Yes for each
device or Yes to All.
The device is permanently removed from the project. All
occurrences of that device name are removed from the
application.
Publication 2711-6.0
21–6
Managing Projects
Copying a Project
to Another Computer
Because applications can share the same project, projects are
portable. They can be copied from one computer to another. You
may have an application on another computer that uses all or some of
the tags in an existing project.
Each project and its files are stored as a separate folder in
C:\AB\PROJECTS. For example, the project files for a project
named PV900PRJ are stored as follows:
C:\ab\projects\PV900PRJ
appdata.db
appdata.mb
appdata.px
element.db
element.mb
element.px
To copy a project from one computer to another:
1. Copy the project folder and all of its files to a disk.
2. Insert the disk in the drive on the target computer.
3. Copy the project files on disk to the C:\AB\Projects.
4. Start PanelBuilder.
5. Choose Project Management from the Application menu.
6. From the Current Project list, select the name of the project just
copied to the computer.
7. Click Done.
When you open the application, the copied project will become the
current project for the application.
Note: Translated applications (.PVA files) are downloaded to the
terminal with only those project tags used by the application. When
copying .PBA files to another computer, only those tags used by the
application are copied with the application.
Publication 2711-6.0
Managing Projects
Restoring a Project
21–7
If a project is deleted accidentally, an application associated with it
may be used to recreate the project.
1. Open the application.
A dialog opens indicating that a project does not exist for the
application. You are asked if the project should be recreated.
2. Select Yes. The project is recreated with all the device and tag
data required by the application.
Moving an Application
to Another Computer
Projects with the same name can reside on different computers.
However, even though the name is the same, the projects may
contain different tags or share only some tags.
Before moving an application to another computer, verify whether
the project used by the application exists on the target computer.
• Search C:\AB\Projects\ for a folder with the same project name
• Choose the Project Management command on the Application
menu and search for the project name in the Existing Projects list.
If the project does not exist, open the .PBA file normally.
If the project does exist, determine if you want to use the project
already on the computer or the tag information in the .PBA file.
• To use the project on the computer, select Replace None from the
window below.
• To copy the tag information from the .PBA file to the computer,
select Replace All.
Publication 2711-6.0
21–8
Managing Projects
Replacing Duplicate Tags
and Devices in a Project
Whenever you open an application (.PBA file), the dialog below
opens to verify a one-to-one correspondence between the tags in the
application and the tags in the project. The dialog then reopens to
verify the devices in the application with the devices in the project.
It is possible that the application tags or devices are different than
those in the project.
For example:
1. You transfer an application (.PBA file) from a computer to a
laptop. Tag information is stored in the .PBA file. When you open
the application, a project containing all the tags is created on the
hard drive.
2. You edit the definition of a tag on the laptop and then save the
application (.PBA file). The project on the laptop is now
different than the original project copied from the computer.
3. You transfer the application (.PBA file) back to the computer.
The updated project is transferred with the application.
4. When you open the application (.PBA file) on the computer, a
dialog opens allowing you to update the original project.
This dialog does not open
if you are creating a new
application that is not yet
associated with a project.
The dialog displays the name of the first application device or tag
that is different than the project. You have the following options:
Click:
To:
Yes
Replace the project tag or device with the application tag or device.
Select Yes, if you know that a specific tag or device has been
modified and you want to update the project database.
No
Ignore the application tag or device. Do not replace the tag or
device in the project database with the application tag or device.
Replace All
Replace all project tags or devices with the application tags or
devices.
Replace None
Ignore all application tags or devices. Do not replace any tags or
devices in the project.
Cancel Open
Cancel the open.
If you select No or Replace None, a dialog opens reminding you that
the application may not validate because of the differences.
Publication 2711-6.0
Managing Projects
Adding Unknown
Tags or Devices to a Project
21–9
When you open an existing application it is possible that the
application devices or tags are not in the project. This section shows
how to load unknown tags or devices in a project.
PanelBuilder displays the following dialog if the application you are
opening contains devices (terminal/controller) or tags that do not
exist in the application’s project.
The dialog displays the name of the first device or tag not found in
the project. You must tell PanelBuilder what to do with unknown
tags. The options are:
Click:
To:
Yes
Add named device or tag to project database.
No
Ignore device or tag, not adding it to the
project database.
Add All
Add all unknown devices or tags to the project database.
Add None
Ignore all unknown devices or tags and open the application.
Cancel Open
Cancel the open.
Publication 2711-6.0
21–10
Managing Projects
Setting Preferences
for Replacing or Adding
Tags and Devices
You can control the behavior of PanelBuilder when opening an
application. Choose Preferences from the Application menu.
Shows information
about this dialog
Show Project Database Restore Dialog
Select this check box to display the Project Database Restore dialog
each time you an open an application. This dialog prompts you to:
• replace duplicate tags and devices in the project database with
those in the application.
• add application tags and devices to the project database if they are
missing.
This is the default option. To add missing tags and replace duplicate
tags in the project database without showing the Project Database
dialog, disable this check box and select the other two boxes.
Always Add Missing Tags & Devices
Select this check box and disable the first check box to add missing
tags and devices to the project data database without opening the
Project Database dialog. This option is equivalent to clicking the
Add All button on the Project Database dialog.
Always Replace Duplicate Tags & Devices
Select this check box and disable the first check box to replace
duplicate tags and devices in the project database without opening
the Project Database dialog. This option is equivalent to clicking the
Replace All button on the Project Database dialog.
Important:
Publication 2711-6.0
If you disable all check boxes, the verification process
will not occur and you may lose tag or device data.
Managing Projects
Restoring a Project
Created with a Restricted
Release of PanelBuilder
21–11
If you open an application that is linked to a project created with a
Restricted or Beta release of PanelBuilder, this dialog opens.
You must delete the project and then re-open the application to
ensure that the project is current. All application data is retained in
the process.
To restore the project:
1. Click OK to close the above dialog.
2. Choose Project Management from the Application menu.
3. Select the Projects tab.
4. Under Existing Projects, select the project to delete.
5. Click the Delete button. You are asked to confirm the deletion.
6. Click the Done button to exit the Project Management dialog.
7. Re-open the application.
The project is recreated with all device and tag data.
Publication 2711-6.0
Multilingual Support
Chapter Objectives
This chapter describes how to use the FontToolt utility to create
font files for PanelBuilder applications. You can access these font
files in PanelBuilder to create applications for specific languages.
Section
What You Will Learn?
Page
What You Will Learn?
22–1
System Requirements
22–2
Terminology
22–2
What is FontTool?
22–3
Input Method Editor
22–4
Using FontTool
22–5
Creating Font Files
22–6
Viewing Sample Text
22–8
Opening Font Files
22–8
Saving Font Files
22–9
Previewing and Printing Font Files
22–10
Creating an Application Using a Font File
22–11
Select Terminal Supporting External Fonts
22–11
Enable External Fonts
22–12
Create Application
22–13
Copy Font File to Memory Card
22–14
Download and Run Application
22–14
Troubleshooting
22–15
Translating Application Text in Excel
22–16
Using Windows Standard Fonts to Enter
Western European Characters
22–18
The chapter describes the procedures required to create an
application in a specific language. You will learn how to:
• Create a font file (containing the character set) for a specific
language.
• Copy the font file to a memory card. This card will be inserted
into the card slot of the PanelView terminal and remain in the slot
while the application is running.
• Create the application using the character set in the font file.
• Download the application to the PanelView terminal.
• Insert the memory card, containing the font file, into the card slot
of the PanelView terminal and secure the card using the Memory
Card Retainer (Catalog No. 2711-NMCC, -NMCD).
• Run the application on the PanelView terminal.
Publication 2711-6.0
22–2
Multilingual Support
System Requirements
Items required to create applications in a specific language are:
• PanelBuilder V2.30 Software installed with External Font
Support (loads the FontTool Utility).
• PanelView terminals running firmware V3.0 (or later).
• International Version of Windows for a specific language or Input
Method Editor to enter characters for double-byte languages.
• Personal Computer with ATA or TMB240/TMB250 card drive
• PC Memory Card
TMB-240/250 Card Drives support these cards:
– 256K flash memory card (Catalog No. 2711-NM11)
– 1M flash memory card (Catalog No. 2711-NM12)
– 2M flash memory card (Catalog No. 2711-NM13)
– 4M flash memory card (Catalog No. 2711-NM14)
ATA Card Drives support these cards:
– 2M flash ATA card (Catalog No. 2711-NM22)
– 4M flash ATA card (Catalog No. 2711-NM24)
– 6M flash ATA card (Catalog No. 2711-NM26)
ATA memory cards are recommended for laptop computers.
!
ATTENTION: Do not format an ATA card in a
DataBook card drive or the card may be unusable.
• Memory Card Retainer (Catalog No. 2711-NMCC, -NMCD)
Terminology
The following terms are used in this chapter.
Code Page
An ordered set of characters that has a numerical index (code point
value) associated with each character. The term code page is
generally used in the context of code pages defined by Windowst
and may also be called character set or char set.
Input Method Editor (IME)
A program that performs the conversion, usually by user-guided
dictionary lookup, between keystrokes and ideographic or other
characters.
Single-Byte Character Set
A character encoding where each character is represented by one
byte. Single Byte Character Sets are mathematically limited to 256
characters, English, for example.
Publication 2711-6.0
Multilingual Support
22–3
Double-Byte Character Set
Double-byte character sets are a specific form of multi-byte
character sets, where some characters consist of two bytes, Chinese,
for example.
Glyph
The actual shape (bit pattern, outline, etc.) of a character image, for
example, an italic ‘a’ and a roman ‘a’ are 2 different glyphs
representing the ‘a’ character.
What is FontTool?
The FontToolt utility lets you create font files which are used by:
• PanelBuilder software to display text whose character glyphs
reside in a font file.
The font file must reside in the \PBWIN\FONT folder. The
default installation creates an \AB\PBWIN\FONT folder.
• PanelView terminal to display the characters on the screen when
the application is running. The font file must reside on a memory
card inserted into a PanelView terminal.
We recommend that you use the ATA flash cards for double-byte
languages because these languages require more space.
Font Files
FontTool can create font files for any of the installed set of languages
(or code pages) supported by Windows. The code page for many
languages is 1252.
PanelView font files have an .OTF (Operator Terminal Font)
extension and reside in the \PBWIN\FONT folder. A font file
contains a set of characters in one or more sizes of the same style.
The character set (or code page) of the language you want to use
must reside on your computer.
Publication 2711-6.0
22–4
Multilingual Support
Input Method Editor
Languages that use a double-byte character set require you to run an
Input Method Editor (IME) on your computer (unless you are
running an International version of Windows.)
The Input Method Editor is a software utility that runs in Windows.
The IME lets you enter foreign character sets in PanelBuilder as well
as other applications, such a Microsoft Word or Power Point.
UnionWayt is one example of an IME. The tool bar and input
dialog for the IME is shown below.
The language you select in the IME must match the code page of the
font file you create in FontTool.
For this Font File:
Select this IME Option:
Chinese (Traditional)
Big5
Chinese (Simplified)
GB
Japanese
S-JIC or EUC
Korean (Johab)
Korean (Wansung)
KSC
Korean (Wansung-Full)
Note: We recommend that you select a fixed width font instead of a
proportional font. A fixed width font will not interfere with the
cursor when you are editing text in PanelBuilder.
If your system is not running an international version of Windows,
you must run the IME to:
• select a font style when creating a font file in FontTool.
• enter/edit text while when creating a PanelBuilder application.
If the IME is not running or the code page is not available for the
particular language, FontTool will generate high ASCII characters
without the desired glyph characters (essentially unreadable text).
Publication 2711-6.0
Multilingual Support
Using FontTool
22–5
This section shows how to use FontTool to create, open, save and
print font (.OTF) files.
To run FontTool:
• In Windows 95, click the Start button, click Programs, click
PanelBuilder, then click FontTool.
• In Windows 3.x, double-click the FontTool icon in the
PanelBuilder group.
The FontTool workspace opens. Most operations are accessed from
the File menu.
File Menu Commands
Description
New Font
Creates a new font file.
Open
Opens an existing font file.
Save
Saves the font file to disk with the same name.
Save As
Saves the font file to disk under a new file name and/or
location.
Save to Memory Card
Saves the font file to a memory card.
Print
Prints a font file.
Print Setup
Selects a printer and settings.
Exit
Exits FontTool and returns to Windows.
View Menu Commands
Description
Tool Bar
Turns the view of tool bar on or off.
Status Bar
Turns the view of the status bar on or off.
View Sample Text
Turns the view on or off for sample text.
Change Sample Text
Opens a dialog allowing you to change the sample text
for a font file.
Underline Adjustment
Turns the underline adjustment on or off to allow for
underlining in double-byte languages.
Help Menu Commands
Description
About
Displays copyright and release information for FontTool.
Publication 2711-6.0
22–6
Multilingual Support
Creating Font Files
To create a font file:
1. Click the New Font tool on the tool bar or choose New Font from
the File menu.
The Locale list box contains a list of font available definitions.
Available character sizes change with the font selection.
Each font definition has a name. If the font has a subtype its
name appears in parentheses, for example, Chinese (Simplified).
Similar to the standard text sizes in
PanelBuilder, the width of the
available sizes are multiples of 8.
The sizes you select will be
available in PanelBuilder (within
parentheses), in addition to the
standard text sizes.
2. From the Locale list, select a font definition.
3. Under Available Sizes, select (or deselect) the character sizes you
want to store in the font file and make available in your
PanelBuilder application.
Deselecting character sizes will reduce the amount of storage
required for the font file on the computer and memory card.
4. Click OK.
The Font dialog opens, allowing you to select a style for the font.
You must select a style that is compatible with the font definition.
For example, if you selected Chinese (Simplified):
• a Chinese font must reside on the computer
• the appropriate code page must reside on the system.
• run the IME program with the appropriate Chinese language
selected.
If your system is running a Chinese version of Windows, an IME
is not required; the correct code page is automatically available.
Publication 2711-6.0
Multilingual Support
22–7
Note: For the following
single-byte languages, select
MS LineDraw under Font.
– English
– French
– Italian
– German
– Spanish
5. Select a font style.
6. Click OK to generate the font file.
The time it takes to generate the file depends on the number of
characters and sizes in the definition, and your computer’s speed.
Sample text is defined for each font definition. The sample text is
displayed for the font definition in the selected style. Verify that
the text looks okay.
At this point, the font file is resident in memory but not on disk.
The status bar located at the bottom of the FontTool window
shows the size of the font file.
You must save the font file to:
• \PBWIN\FONT folder to access the file when creating an
application with the PanelBuilder software.
• memory card, which will be inserted in the card slot of the
PanelView where the application will run.
See the section on Saving Font files.
Publication 2711-6.0
22–8
Multilingual Support
Viewing Sample Text
You can view and/or change the sample text of a font definition
before saving the font file.
1. Choose Change Sample Text from the View menu.
2. Enter new sample text.
3. Click OK. The sample text is changed for the font definition.
Opening Font Files
Font (.OTF) files are located in \PBWIN\FONT. You can open a
font file to view/edit the sample text.
To open a font (.OTF) file:
1. Click the Open tool on the tool bar or choose Open from the File
menu.
2. Select a file from the \PBWIN\FONT folder and click OK.
Or double-click on the file name you want to open.
The sample text appears for the file you open. If you don’t see
any text, choose Sample Text from the View menu. This
command turns the view of the text on or off.
Publication 2711-6.0
Multilingual Support
22–9
Saving Font Files
FontTool provides 3 commands for saving files.
Save Commands
Description
Save
Saves a file that was previously opened to the same file
name and location. If you are saving a new file, the Save
As dialog opens, asking you to confirm the file name and
location.
Save As
Saves the file with a new name and/or location, leaving
the original intact.
Save to Memory Card
Saves the font file to a memory card located in the card
drive on the computer.
To save a font file to the same location with the same file name:
Click the Save tool on the tool bar or choose Save from the File
menu.
To save a font file under a new name and/or location:
1. Choose Save As from the File menu.
The File Save As dialog shows the current file name and location
of the font file.
2. In the File Name box, enter a descriptive file name (up to 8
characters) with the .OTF extension.
PanelBuilder expects to find all font .OTF files in the
\PBWIN\FONT folder.
3. Click OK.
Publication 2711-6.0
22–10
Multilingual Support
To save a font file to a memory card:
1. Load an ATA Flash card (Catalog No. 2711-NM22, -NM24,
-NM26) in the card drive on your computer.
Important: To write the font file to a memory card directly from
FontTool, you must use an ATA Flash card.
2. Click the Save to Memory Card tool on the tool bar or choose
Save to Memory Card from the File menu.
The dialog shows a list of Memory Card Drives detected on the
computer.
3. Select the font .(OTF) file from the \PBWIN\FONT folder you
want to save to a memory card.
4. Select the Memory Card Drive.
5. Click OK to save the font file to the memory card.
Note: You can also save a font file to an ATA card using the Save
As dialog by selecting the memory card drive from the Drive’s list.
Printing Font Files
You can print the sample text associated with a font file.
To print the sample text for a font (.OTF) file:
1. Open the font file you want to print. (Choose Open command
from File menu.)
2. Click the Print on the tool bar.
Or choose Print from the File menu.
Use the Print Setup command on the File menu to select a different
printer or change printer settings.
Publication 2711-6.0
Multilingual Support
Creating an Application
using a Font File
22–11
This section shows the steps necessary to use a font file in a
PanelBuilder application.
The font file you want to use in PanelBuilder must be located in
\PBWIN\FONT. For details on how to create a font file see the first
section of this document.
Using font files requires:
• PanelBuilder Software V2.3 (or later). Systems running earlier
versions of PanelBuilder, require an upgrade.
• PanelView terminals running firmware V3.0 (or later). Terminals
with earlier firmware versions, will require a firmware upgrade.
To check the firmware running on your terminal, choose Terminal
Info from the Configuration Mode menu on the terminal.
Step 1 – Select a Terminal Supporting External Fonts
From the New Application or Terminal Setup dialog (Application
menu), select a PanelView terminal that supports external fonts.
Any terminal running firmware version 3.0 (or later) supports
external fonts.
This button is only
enabled for
PanelView terminals
running Firmware
Version 3.0 or later.
Publication 2711-6.0
22–12
Multilingual Support
Step 2 – Enable External Font Support
The External Font Setup dialog allows you to:
• enable a font file for the PanelBuilder application.
• translate (and edit) the default text that appears in the Numeric
Scratch Pad of the PanelView terminal so that it appears in the
correct language.
To enable external font support:
1. Choose Terminal Setup From the Application menu
2. Click the Font Setup button.
Check this box to translate (and
edit) the text that appears in the
numeric scratch pad on the
PanelView terminal.
Click this button to set
the Numeric Scratch
Pad Prompt to the
default text in English.
If you clear the check box, the
Numeric Scratch Pad
Customization Area is dimmed.
3. Check the External Font Support box to enable external fonts.
4. From the External Font File list, select a font file.
The selected font file determines the character sizes available and
the characters available for display in objects.
5. Check the Use Custom Text box to translate the English text that
appears in the Numeric Scratch Pad of the PanelView terminal to
the selected language. Checking this box allows you to change
the wording of the prompt, if desired.
If you do not translate the Numeric Scratch Pad prompt, it will
appear in English on the terminal.
6. Click OK to exit and return to the Terminal Setup dialog.
Publication 2711-6.0
Multilingual Support
22–13
Step 3 – Create the Application
Create your PanelBuilder application.
Internal Font sizes
in PanelBuilder
Text sizes for an external font file appear in parentheses on:
• Text Size menu accessed from the Format menu or the tool bar
• Text Size list in Alarm History List dialog
• Text Size field in spreadsheet editor for multistate objects
External Font
sizes in
PanelBuilder
If you select a text size in parentheses, PanelBuilder uses the external
font file to generate glyphs for a language on the application screen.
If you select a text size without parentheses, PanelBuilder uses its
default internal font to display text on application screens.
Important:
You cannot use external fonts and internal fonts in the
same text string. However, you can use both in the
same application.
PanelBuilder always uses the default internal font to display text
entered in the Text Edit box on the toolbar, Text Editor, and
spreadsheet editor for multistate devices. The operating system is
responsible for formatting and displaying the text.
To enter text in PanelBuilder, using the character set of the external
font file (for example double-byte Asian characters), you must run
either an:
• International Version of Windows, or
• IME with the correct language (code page) selected.
If you are not running an IME, the operating system will display
double-byte glyph characters as 2 single-byte characters.
Publication 2711-6.0
22–14
Multilingual Support
Step 4 – Copy Font File to Memory Card
To run the application on the PanelView terminal, the font file must
reside on a memory card loaded in the terminal.
To copy a font file to an ATA flash card:
(Catalog No. 2711-NM22, -NM24, -NM26)
• In FontTool, choose Save to Memory Card from File menu.
• In PanelBuilder, choose Copy Font File from File menu.
• In the Application File Transfer Utility, download an .OTF file to
a DOS memory card. Click the Setup button to enter a COPY
command, for example:
copy \ab\pbwin\font\china_s.otf m:
where the file china_s.otf is copied to memory card drive m:
• In DOS, use the COPY command as shown above.
To save a font file to a flash memory card :
(Catalog No. 2711-NM11, -NM12, -NM13, -NM14)
• In the Application File Transfer Utility, you can download a
specific .OTF file to a DOS memory card. Click the Setup button
to enter the appropriate command string to download the file.
See page 23–17 for details on the command string.
• In DOS, use the appropriate command string to copy the file to a
memory card. See page 23–17 for details on the command string.
Step 5 – Download and Run the Application
To run a PanelBuilder application using a font file:
• download the PanelBuilder application to a PanelView terminal.
• insert the memory card, containing the font file, in the card slot
on the PanelView terminal.
• use the memory card retainer (Catalog No. 2711-NMCC,
-NMCD) to prevent accidental removal of the card from card slot.
Important:
Publication 2711-6.0
The application will not run properly unless the
memory card containing the font file is inserted in the
PanelView terminal.
Multilingual Support
Troubleshooting
22–15
Detecting Problems with FontTool
This section covers problems you may encounter when using
FontTool. If the font file is generated but the sample text does not
appear, consider the following causes.
Specified code page not available
When a font file is generated, the code page for that font must be
available on the computer. FontTool uses this code page to generate
the characters for the font file.
The code page may not be available for the following reasons:
• English version of the Windows operating system is running but
an appropriate Input Method Editor (IME) is not active.
• IME is active but the wrong language is selected (some Input
Method Editors support multiple languages).
• International version of the Windows is running but is not the
correct version. For example, Windows 3.1 has separate
distributions for Simplified Chinese (code page=936) and
Traditional Chinese (code page=950).
Selected font does not contain specified characters
If the font style (selected in the Font dialog) does not contain the
correct characters, either:
• characters will not appear or
• each double-byte character appears as 2, single-byte characters.
Detecting Problems with External Fonts in PanelBuilder
This section covers problems you may encounter when using
external font files with PanelBuilder.
Characters may not appear correctly in PanelBuilder for the
following reasons:
• If you enter a character not in the font file, PanelBuilder displays
asterisks to indicate an invalid character.
• If the code page for the font file is not available through the
operating system, characters will appear correctly on the
application screen, but not in the Text Edit box on the tool bar, the
Text Editor, or spreadsheet editors for multistate devices.
The code page may not be available because:
– international version of Windows does not match the code
page of the font file.
– language selected in the Input Method Editor does not match
the code page of the font file.
– external font was not selected or supported by the PanelView.
Publication 2711-6.0
22–16
Multilingual Support
Translating
Application Text in Excel
This section shows how to translate the text for an application in
Excel rather than in PanelBuilder. This may be helpful if the
individual translating the text is not familiar with PanelBuilder
software or PanelView terminals. Translating the application text
outside of PanelBuilder simplifies the translation process.
The procedures that follow assume that the application was
developed in the default PanelBuilder language. After following the
procedures, the memory card containing the font file can be inserted
in the terminal and the application downloaded to the terminal.
To select/copy the text to translate:
1. Open PanelBuilder.
2. Open the Text Editor by choosing Text Editor from the
Application menu.
3. Purge all text not used by the application.
• Click the Select All button.
• Click the Purge button.
4. Click Select All again to select all the text to translate.
5. Copy the text to the clipboard.
• Click the right mouse button.
• Choose Copy from the popup menu.
To paste/select the text in Excel:
1. Without closing PanelBuilder, open Excel.
2. Paste the text into the Excel spreadsheet.
3. Translate the text.
To copy the translated text into PanelBuilder:
1. In Excel, copy the translated text to the clipboard.
2. Return to PanelBuilder.
3. Paste the translated text into the Text Editor.
• Select all lines
• Click the right mouse button.
• Choose Paste from the popup menu.
4. Click OK to exit the Text Editor.
Publication 2711-6.0
Multilingual Support
22–17
To create and save the font file:
1. Open FontTool.
2. From the File menu, choose New Font.
3. Select the appropriate language, sizes, and font style.
4. After the font file is generated, choose Save As from the File
menu to save the font file (.OTF) in the \PBWIN\FONT folder.
5. From the File menu, choose Save to Memory Card to save the
font file (.OTF) to a memory card.
6. Close FontTool.
To enable the font in PanelBuilder:
The characters will not appear correctly in the application until after
you enable the font file in PanelBuilder.
1. In PanelBuilder, choose Terminal Setup from the Application
menu.
2. Click the Font Setup button.
3. Select the External Fonts Enabled check box.
4. From the External Font File list, select the font file.
5. Click OK until you exit the Terminal Setup dialog.
Publication 2711-6.0
22–18
Multilingual Support
Using Windows Standard
Fonts to enter Western
European Characters
Microsoft Windows standard fonts support Western European
characters. You can add a language or keyboard on Windows 95 or
Windows NT systems and then enter international characters directly
from your keyboard.
To add a keyboard layout:
1. On the Start menu, click Settings Control Panel.
2. Double-click the Keyboard icon.
3. Click the Language tab (Windows 95) or the Input Locales tab (
Windows NT).
4. Change keyboard from US-101 (Windows 95) or US (Windows
NT) to US International.
For more details on adding keyboard layouts refer to Keyboard
Layouts in the online Index of Windows Help.
To enter international characters:
To enter this character:
Press:
!(,28
Ctrl+ ‘, (accent grave) the letter
")-39<
Ctrl+’ (apostrophe), the letter
â*.4:
Ctrl+Shift+^ (caret), the letter
#15
Ctrl+Shift+~ (tilde), the letter
$+/6;=A
Ctrl+Shift+: (colon), the letter
%
[email protected], a or A
&
Ctrl+Shift+&, a or A
?>
Ctrl+Shift+&, o or O
'
Ctrl+Shift+, (comma), c or C
0
Ctrl+Shift+’ (apostrophe), d or D
7
Ctrl+Shift+/, o or O
Alt+Ctrl+Shift+?
@
Alt+Ctrl+Shift+!
Ctrl+Shift+&,s
For more details on entering international characters refer to
International Characters in the online Index of Windows Help.
Publication 2711-6.0
Validating and Transferring
Applications
Chapter Objectives
This chapter contains the following sections:
Section
Helpful Hints
Page
Helpful Hints
23–1
Validating Applications
23–2
Transfer Options
23–6
Transfer Utilities
23–8
Internal DF1 Driver
23–9
Downloading Directly to a Terminal
23–10
Downloading on a Local DH+ Link
23–12
Downloading to a Terminal using Pass-Through
23–13
Downloading to a DOS Memory Card
23–16
Downloading to a DOS File
23–18
Uploading Directly from a Terminal
23–19
Uploading on a Local DH+ Link
23–21
Uploading from a Terminal Using Pass-Through
23–22
Using the Application File Transfer Utility
23–23
Decreasing Size of Application for Downloads
23–28
Exceeding RAM Memory in Terminal
23–28
S PanelBuilder applications are saved to .PBA files. When
•
•
•
•
•
•
•
•
downloading to a PanelView terminal or a DOS file, the .PBA file
is automatically translated and saved to a .PVA file.
PanelView terminal must be physically connected to the computer
through a direct or network connection before transferring files.
Use the internal DF1 driver to transfer applications over a serial
link to a terminal with an RS–232 /DF1 port.
If downloading applications directly to a DH-485 terminal using
the 1747-PIC converter, configure the appropriate RSLinx or
INTERCHANGE driver.
If downloading applications locally over a DH+ link or using
Pass-Through, you must configure the appropriate RSLinx or
INTERCHANGE driver on your computer.
Applications are automatically validated (checked for errors)
during the download process. You can also validate applications
and correct any errors before a download.
You can’t download a keypad application to a touch screen
terminal, or a touch screen application to a keypad terminal.
Unused text strings and tags are not downloaded with application.
If problems occur during a transfer, refer to Appendix F for
troubleshooting tips.
Publication 2711-6.0
23–2
Validating and Transferring Applications
Validating Applications
PanelBuilder validates and checks applications for errors when
downloading. You can also check the accuracy of an application
before downloading using one of these commands:
• Validate Changes
Checks only changes to the application since the last validate.
Changes are validated screen by screen.
• Validate All
Validates the entire application.
Applications must validate successfully before you can download
them to a terminal. See Appendix E for validation error messages.
To validate an application:
Choose Validate All or Validate Changes from the Application menu.
• If the application passes validation, the following dialog opens.
• If the application does not pass validation, the Exceptions dialog
opens listing:
– errors – must be corrected before downloading the
application.
– warnings – do not have to be corrected before downloading
the application. Warnings are optional changes.
As a convenience, you can open the Exceptions dialog from the
Windows menu while correcting application errors.
Press:
To:
Close the dialog.
Opens the dialog and screen associated with highlighted error.
Send validation messages to printer or file.
Define printer settings.
Publication 2711-6.0
Validating and Transferring Applications
23–3
Correcting Validation Errors
To correct validation errors:
1. Select an error in the Exceptions dialog by clicking on it.
2. Click the Goto button.
PanelBuilder opens the dialog associated with the error or the
screen containing the object with an error.
If PanelBuilder cannot navigate to the source of the selected error
the GoTo button is dimmed.
The Exceptions dialog is minimized to an icon.
3. Correct the error and close the dialog.
Note: If the message indicates an undefined function key even
though the object dialog shows a selected key, clicking OK to
close the dialog resolves the error.
4. Double-click the Exceptions icon to open the Exceptions dialog .
Or choose Exceptions from the Window menu
5. Repeat steps 1 – 4 to correct other errors.
The following example shows how to navigate from an error in
the Exceptions dialog to the dialog or screen containing the error.
Select error
Click GoTo Button
Opens Object Dialog
Enter Missing Write Tag
and Close Dialog
Double-click icon to
open Exceptions Dialog
Publication 2711-6.0
23–4
Validating and Transferring Applications
Printing Validation Messages
To send validation messages to a printer:
• a printer must be connected to your computer
• the computer must recognize the printer as a valid printer
See the Microsoft Windows User’s Guide for details on installing
printers.
To set up the printer:
1. Click the Print Setup button from the Exceptions dialog.
The standard Microsoft Print Setup dialog opens.
2. If the default printer is not the one in use, select a printer from the
Specific Printer list box. If it is not listed see below.
3. Set appropriate attributes for your printer.
4. Click the Options button to enter options specific to the printer
you are using. The Options dialog is different for each printer.
5. When done, click the OK button.
6. Click the Print button from the Exceptions dialog to print the
validation messages.
7. Click Close to exit the Exceptions dialog.
If your printer is not listed:
• Check for hardware compatibility between your printer and one
of the printers listed.
• Check if your printer has an emulation mode that is compatible
with one of the printers listed.
• You may need to install a print driver for your printer. Refer to
the Microsoft Windows User’s Guide.
Publication 2711-6.0
Validating and Transferring Applications
23–5
Sending Validation Messages to File
To send validation messages to a file, you must:
• add the Generic/Text Only printer to the Installed Printer list
• assign the printer to a File: port
For details on how to add Generic / Text Only on FILE: to the
Installed Printers list on your computer, see the Microsoft Windows
User’s Guide. This print option allows you to print text, not graphics.
To send validation messages to a file:
1. Click the Print Setup button from the Exceptions dialog.
The standard Microsoft Print Setup dialog opens.
2. Verify that Generic / Text Only on FILE: is the selected printer
under Specific Printer.
If your application uses large text sizes, open the Options dialog and
enable the Wide Carriage option.
3. Click OK to exit the Printer Setup dialog.
4. Click the Print button from the Exceptions dialog.
5. In the Output File Name box, enter the file name in which to save
the validation messages.
6. Click OK to output messages to the file.
If the file name already exists, you are given the option of
overwriting it or entering another file name.
7. Click Close to exit the Exceptions dialog.
Publication 2711-6.0
23–6
Validating and Transferring Applications
Transfer Options
You can transfer applications between a computer running
PanelBuilder and one of the following:
• PanelView terminal
• Memory card
• DOS file
PanelView Terminal
Direct Connection
Downloads applications from the RS-232 connection on your
computer or workstation. For connection details, see Publication
2711-6.1.
Use the Internal DF1 Driver to transfer applications directly to a
PanelView terminal using the terminal’s RS-232/DF1 port.
To transfer an application directly to a DH-485 or RS-232 (DH485
protocol) terminal using the 1747-PIC converter, you must configure
the 1747-PIC driver using RSLinx or INTERCHANGE software.
DH+ Local Connection
Downloads applications from a computer or workstation on the
Allen-Bradley Data Highway Plus (DH+) link to a DH+
PanelView terminal on the link. For connection details, see
Publication 2711-6.1.
A DH+ RSLinx or INTERCHANGE driver must be installed on the
computer.
Pass-Through Connection
Pass-Through lets you transfer applications between a computer or
workstation on a DH+ link and a terminal on a Remote I/O link or
DH-485 link. Data passes through a controller, which is a bridge
between the two networks. For connection details, see Publication
2711-6.1.
A DH+ RSLinx or INTERCHANGE driver must be installed on the
computer.
Publication 2711-6.0
Validating and Transferring Applications
23–7
Memory Card
Computers with an ATA card drive or DataBook TMB240/TMB250
card drives allow you to transfer applications using memory cards.
• ATA card drives use these Allen-Bradley cards: Catalog No.
2711-NM22, -NM24, -NM26. PanelView terminals running
firmware 3.0 (or higher) support ATA cards.
• DataBook card drives use these Allen-Bradley cards: Catalog No.
2711-NM11, -NM12, -NM13, -NM14.
DataBook TMB240 or TMB250 card drives cannot be set up in the
Windows 95 Control Panel. Follow the instructions in the DataBook
User’s Guide for details on how to install the card drive.
You can also transfer applications in a terminal to a memory card
using the terminal’s memory card slot. See the PanelView Terminal
user manual for details. This method doesn’t require a separate card
drive on your computer. Use the memory card to download
applications to multiple terminals without a computer.
DOS File
You can transfer PanelBuilder applications to/from DOS files. The
application is downloaded to a DOS file in a .PVA format.
Use the PanelView File Transfer (PFT) Utility to transfer DOS
application files (*.PVA) between a DH-485 PanelView terminal and
a computer that does not have Windows installed. PanelBuilder
includes a copy of the (PFT) Utility.
Note: The PFT utility only works with DH-485 terminals. To
download to a Remote I/O terminal, you must use a DF1 driver.
Before transferring files using the PFT utility, disable all serial port
drivers (including the mouse and INTERCHANGE or RSLinx) that
are using the same COM port as PFT.
To use PFT on a computer that does not have PanelBuilder Software
installed, copy the following files from the C:\AB\PBWIN directory
to a floppy disk for transport to a DOS computer:
PFT.EXE
PanelView File Transfer DOS Utility
DEFAULT.STP
PanelView File Transfer configuration file
PIC485.EXE
PanelView File Transfer PIC Module driver
KR.EXE
PanelView File Transfer KR Card driver
<APP>.PVA
User PanelView application file
Refer to the User Guide (Publication 2711-805) for instructions on
using the PanelView File Transfer Utility to upload/download
applications between the PanelView terminal and a personal
computer in the DOS environment.
Publication 2711-6.0
23–8
Validating and Transferring Applications
Transfer Utilities
PanelBuilder Application Menu
Most application transfers are initiated from the Application menu of
the PanelBuilder software. Choose the Download or Upload
command from the Application menu.
Use the Download command to download an application to a:
• PanelView terminal
• memory card
• DOS file
Use the Upload command to upload an application from a terminal.
Application File Transfer Utility
Use the Application File Transfer Utility (WINPFT.EXE or
WINPFT32.EXE) to transfer applications in the Windows
environment, outside of PanelBuilder. This utility is available as an
icon in the PanelBuilder group. The dialogs are identical to the
Download/Upload dialogs on the PanelBuilder Application menu.
Use tools or File menu commands to:
• download a .PVA application to a PanelView terminal.
Create a .PVA file by downloading a .PBA application to a DOS
file from the PanelBuilder Application menu.
• upload a .PVA application from a PanelView terminal.
• verify the application you want to download against the
application loaded in the terminal
PanelView DOS File Transfer Utility
Refer to Publication 2711-805 for details on using the PanelView
File Transfer (PFT) Utility to transfer applications between a
computer and a PanelView terminal in the DOS environment.
Publication 2711-6.0
Validating and Transferring Applications
Internal DF1 Driver
23–9
PanelBuilder has an Internal DF1 driver for transferring applications
over a serial link to:
• PanelView terminals with an RS-232 (DF1 protocol) port, for
example, DH+, DF1 or Remote I/O terminal.
• Remote I/O terminal with RS-232 (DF1 protocol) port configured
for Pass-Through communications with a PLC using DF1.
The PLC 5 must be configured with the DF1 settings shown
below to activate communications.
The Internal DF1 driver uses the following settings which match the
fixed DF1 settings on the PanelView terminal.
Parity = None
Baud Rate = 19200
Error Detect = CRC
Using the Internal Drivers
The Download/Upload Application dialogs include a
Communication Drivers list from which you select either:
• Internal DF1 driver or
• RSLinx or INTERCHANGE driver
To use the DF1 driver, you must unload INTERCHANGE from your
system. (Exit Windows and type ABICSTOP at the DOS prompt).
If an RSLINX driver is configured for a COM port (even if the
driver is not mapped for a client application), the internal DF1 driver
is disabled to avoid conflicts. Delete the RSLinx driver and the
internal DF1 driver becomes available.
If you select Internal DF1 driver for a terminal that does not have an
RS-232/DF1 port (such as a DH-485 terminal), this message appears:
Incompatible or no communication drivers active, cannot
perform file transfer operations with Operator Terminal
and Operator Terminal is removed as an option under Destination.
The Setup button on the Download/Upload dialogs is active if more
than one COM port is available for the internal drivers.
If you select a COM port used by another Windows application, the
port is locked. Systems running Windows 3.1, display this message:
The requested COM port is not available because a
hardware interrupt conflict has been detected. You must
change your hardware configuration to be able to use
this COM port from Windows applications.
Because the port is locked by another Windows application, this
message appears in the dialog showing the download/upload status:
Error! Selected communication port not configured, in
use by another Windows application, or port hardware
does not exist.
Publication 2711-6.0
23–10
Validating and Transferring Applications
Downloading
Directly to a Terminal
This section shows how to download an application directly to a
PanelView terminal over a serial link. Before starting the download:
• check cable connections (see Publication 2711-6.1).
• use the Internal DF1 driver to download applications to terminals
with an RS-232/DF1 port.
• use the 1747-PIC (INTERCHANGE or RSLinx) driver to
download applications to DH-485 terminals or RS-232 (DH-485
protocol) terminals.
To download an application using the Internal DF1 Driver:
➀ Open the application you want to download.
➁ Choose Download from the Application menu.
➂ Select Download parameters.
Select Operator Terminal
Select Internal DF1 Driver
Click OK to start
download.
Setup button is
active if more than
one COM port is
available.
Shows COM port on
which DF1 driver is active
Enter name of .PVA file in which to
save the translated .PBA file or click
Browse to search for a file.
The internal DF1 driver is assigned to COM2.
➃ Application is validated and translated to a .PVA file.
If errors or warnings are detected, the Exceptions dialog opens.
You must correct errors before download can proceed.
Warnings should be corrected, but the download will proceed.
➄ PanelBuilder software and terminal display status of download.
➅ Terminal resets, verifies and starts application.
Publication 2711-6.0
Validating and Transferring Applications
23–11
To download an application using a DH485 Driver:
➀ Open the application you want to download.
➁ Choose Download from the Application menu.
➂ Select the Download parameters.
Select Operator Terminal
Click OK to start
download.
Select RSLinx or
INTERCHANGE Driver
Shows DH485
as active driver
Enter name of .PVA file in which to
save the translated .PBA file or click
Browse to search for a file.
For DH-485 or RS-232 (DH485 protocol)
terminals, click Setup to verify node
address of terminal.
➃ Application is validated and translated to a .PVA file.
If errors or warnings are detected, the Exceptions dialog opens.
You must correct errors before download can proceed.
Warnings should be corrected, but the download will proceed.
➄ PanelBuilder software and terminal display status of download.
’TEST.PVA’
➅ Terminal resets, verifies and starts application.
Publication 2711-6.0
23–12
Validating and Transferring Applications
Downloading on a
Local DH+ Link
This section shows how to download an application from a computer
on the DH+ link to a DH+ terminal on the link. The computer and
terminal are each a separate station on the DH+ link.
Before downloading application:
• check cable connections. See Publication 2711-6.1
• configure the DH+ driver using RSLinx or INTERCHANGE.
Note: The computer runs at 57.6K baud forcing the DH+ link and
terminal to use the same rate. Set the terminal’s DH+ network to this
baud rate before downloading an application.
To download an application on a local DH+ link:
➀ Open the application you want to download.
➁ Choose Download from the Application menu.
➂ Select the Download parameters.
Select Local Network Operator Terminal
Click OK to start
download.
DOS File
Memory Card
Select RSLinx or
INTERCHANGE Driver
DH+ is active driver
Enter name of .PVA file in which to
save the translated .PBA file or click
Browse to search for a file.
➃ Application is validated and translated to a .PVA file.
If errors or warnings are detected, the Exceptions dialog opens.
You must correct errors before download can proceed.
Warnings should be corrected, but the download will proceed.
➄ PanelBuilder software and terminal display status of download.
’TEST.PVA’
➅ Terminal resets, verifies and starts application.
Publication 2711-6.0
Click Setup to verify node address of the
PanelView. The address must match the
address in the Communication Setup dialog.
Drivers are
mapped to
ports in the
RSLinx
Software.
Validating and Transferring Applications
Downloading to a
Terminal using Pass-Through
23–13
This section shows how to download an application from a computer
on the DH+ link to a terminal on a Remote I/O or DH-485 link.
Before downloading an application:
• check cable connections.
• enable Pass-Through in the Block Transfer dialog (page 20–11).
• configure the DH+ driver using RSLinx or INTERCHANGE.
!
ATTENTION: If downloading with the processor in
run mode, verify the rack address of the target terminal.
Downloading to an incorrect rack address may result in
unexpected operation or damage to equipment.
To download an application to a terminal using Pass-Through:
➀ Open the application you want to download.
➁ Choose Download from the Application menu.
➂ Select the Download parameters.
Select Operator Terminal via Pass-Through
DOS File
Memory Card
Select RSLinx or
INTERCHANGE Driver
DH+ is active driver
Click OK to start
download.
Click Setup to configure
Remote I/O or DH-485
Pass-Through parameters
(pages 23–14, 23–15).
Enter name of .PVA file in which to
save the translated .PBA file or click
Browse to search for a file.
➃ Application is validated and translated to a .PVA file.
If errors or warnings are detected, the Exceptions dialog opens.
You must correct errors before download can proceed.
Warnings should be corrected, but the download will proceed.
➄ PanelBuilder software and terminal display status of download.
➅ Terminal resets, verifies and starts application.
Publication 2711-6.0
23–14
Validating and Transferring Applications
Remote I/O Pass-Through Setup
When you click the Setup button from the Download (or Upload)
Application dialog for a Remote I/O terminal, this dialog opens.
Note: If more than one COM port is configured with a DH+ driver,
the dialog will display available ports. Select the appropriate port.
To configure Remote I/O Pass-Through parameters:
1. Define Remote I/O Pass-Through parameters as described below.
2. Click OK to return to the Application Download dialog.
Use:
Path
Single DH+ Network
Multiple DH+ Networks
Single DF1 Network
Local Bridge/PLC/SLC
Node Address
Link ID
Remote Bridge/PLC/SLC
Node Address
Link ID
Operator Terminal
SLC Scanner Slot
Starting Module
Rack Address
Publication 2711-6.0
To:
Transfer an application directly between a computer on the DH+ network and a
PanelView terminal through a single controller.
Transfer an application between a computer on the local DH+ network and a
PanelView terminal through a PLC controller on a remote DH+ network.
Transfer an application directly between a computer and a PanelView terminal
through the DF1 port on a PLC controller.
Specify the address (0–77octal) of the PLC on the local DH+ network to which your
computer is connected (for Single DH+ Network). Specify address of Gateway
device on local network (for DH+ Multiple Networks).
Specify the unique ID number that identifies the local DH+ network to which your
computer is connected. This field is dimmed for a Single DH+ network.
Specify address (0–77octal) of the PLC on the remote DH+ network through which an
application is transferred. Dimmed if Single DH+ network selected.
Specify the unique ID number of the remote DH+ network through which an
application is transferred. Dimmed unless Multiple DH+ Networks is selected.
Specify the number of the slot where the SLC scanner resides. The default is the
slot closest to the processor.
Specify the starting module group of the PanelView terminal in the Remote I/O rack.
Specify the address of the PanelView terminal on the Remote I/O network.
Validating and Transferring Applications
23–15
DH-485 Pass-Through Setup
When you click the Setup button from the Download (or Upload)
Application dialog and the terminal is defined as a DH-485 terminal
with an RS-232 port, this dialog opens.
Note: If more than one COM port is configured with a DH+ driver,
the dialog will display available Ports. Select the appropriate port.
To configure DH-485 Pass-Through parameters:
1. Define the Pass-Through parameters as defined below.
2. Click OK to return to the Application Download dialog.
Use:
Local Network
Gateway Node Address
Link ID
Remote Network
Terminal Address
Link ID
To:
Specify the node address (0 to 76) of the SLC 5/04
controller or DH+/DH485 Gateway to which your computer
is connected.
Specify the unique ID number (1 – 65534) that identifies
the computer to controller (or DH+/DH485) link on the
DH+ network.
Specify the node address (0 to 31) of the PanelView
terminal on the DH-485 network to which you are
downloading an application.
Specify the unique ID number (1 – 65534) that identifies
the link between the controller and PanelView terminal on
the DH-485 network.
Publication 2711-6.0
23–16
Validating and Transferring Applications
Downloading
to a DOS Memory Card
This section shows how to download an application to a DOS
memory card in a .PVA format. After copying an application to a
memory card, you can download it to a PanelView terminal.
To download an application to a DOS memory card:
➀ Open the application you want to download.
➁ Choose Download from the Application menu.
➂ Select Download parameters.
Click OK to start
download.
Select DOS Memory Card
Enter name of .PVA file in which to
save the translated .PBA file or click
Browse to search for file.
➃ Click the Setup button to open this dialog.
➄ Enter or select a memory card command and then click OK. See next page for format.
➅ Application is validated and translated to a .PVA file, then downloaded to the Memory Card.
The memory card command executes a command (or batch file).
After the command is executed, you return to Windows.
Publication 2711-6.0
Validating and Transferring Applications
23–17
The format of the command entered in the Memory Card DOS
Command Setup dialog is specific to the card drive installed in your
computer.
• For ATA card drives, use the DOS COPY command, for example:
COPY C:\AB\PBWIN\CONTROL.PVA M:
where M: is the ATA card drive on your computer.
Memory cards compatible with the ATA card drives include
Catalog No. 2711-NM22, -NM24, -NM26.
• For DataBook TMB240 or TMB250 card drives, the command
string has three parameters as shown below.
Memory cards compatible with the DataBook card drives include
Catalog No. 2711-NM11, -NM12, -NM13, -NM14.
space space
CMD %s DriveLetter:
user defined parameter
required parameter
user defined parameter
TCXCOPY %s E:
The following table describes each command parameter.
Parameter
Description
CMD
DOS command that will download the application to the card.
Memory card DOS commands are drive specific. See the
instructions for your card drive.
%s
Wild card character which PanelBuilder replaces with the
application file name entered in the File Name box in the Application
Download dialog.
DriveLetter:
Memory card drive on your computer. The drive letter is always
followed by a colon (:).
After entering a command string for the first time, it automatically
appears in the command list box. You can then select the command
from the list box instead of entering it.
Publication 2711-6.0
23–18
Validating and Transferring Applications
Downloading to a DOS File
You can download applications to a file in the DOS environment
which can be downloaded to a terminal later using the Windows
version of the Application File Transfer Utility. The PanelBuilder
application file (.PBA) is translated and downloaded to DOS with a
.PVA file type.
Note: You can transfer the .PVA file between the computer and a
DH-485 terminal in the DOS environment using the PanelView File
Transfer Utility. See page 23–7.
To download an application to a DOS file:
➀ Open the application you want to download.
➁ Choose Download from the Application menu.
➂ Select Download parameters.
Select DOS File
Enter name of .PVA file in which to
save the translated .PBA file or click
Browse to search for file.
If you enter a .PVA file without a path,
the file is saved to the current default
directory. To save the file to a specific
folder, specify the location in the File
Name box.
➃ Application is validated and translated to a .PVA file, then downloaded to a DOS file.
If errors or warnings are detected, the Exceptions dialog opens.
You must correct errors before download can proceed.
Warnings should be corrected, but the download will proceed.
➄ Dialog opens with .PVA File Size and RAM requirements
Dialog compares the file size and RAM requirements of the
.PVA file with the PanelView’s file size and RAM capacity.
Publication 2711-6.0
Click OK to start
download.
Validating and Transferring Applications
Uploading Directly
from a Terminal
23–19
This section shows how to upload an application directly from a
PanelView terminal to your computer over a serial link.
Before uploading an application:
• check cable connections. See Publication 2711-6.1
• use the Internal DF1 driver to upload applications from terminals
with an RS-232/DF1 port.
• use the 1747-PIC (INTERCHANGE or RSLinx) driver to upload
applications from DH-485 terminals or RS-232 (DH-485
protocol) terminals.
To upload an application using the Internal DF1 driver:
➀ Choose Upload from the Application menu.
➁ Select the Upload parameters.
Select Operator Terminal
Select Internal DF1 Driver
Click OK to start
upload.
Setup button is
active if more than
one COM port is
available.
Enter name of .PVA file in which to
save the uploaded application or
click Browse to search for a file.
Select type of terminal from which
you are uploading application.
Under Presets, select:
S Original to upload presets (initial values)
defined for inputs.
S Current States to upload current input
values in terminal.
➂ PanelBuilder software and terminal display status of upload.
➃ When the upload is complete, the application opens in PanelBuilder.
Publication 2711-6.0
23–20
Validating and Transferring Applications
To upload an application using a DH485 Driver:
➀ Choose Upload from the Application menu.
➁ Select the Upload parameters.
Select Operator Terminal
Click OK to start
upload.
Select RSLinx or
INTERCHANGE Driver
Shows DH485
as active driver
Enter name of .PVA file in which to
save the uploaded application or
click Browse to search for a file.
Select the type of terminal from which
you are uploading application.
Under Presets, select:
S Original to upload presets (initial values)
defined for inputs.
S Current States to upload current input
values in terminal.
➂ PanelBuilder software and terminal display status of upload.
➃ When the upload is complete, the application opens in PanelBuilder.
Publication 2711-6.0
For DH-485 or RS-232 (DH485 protocol)
terminals, click Setup to verify node
address of terminal.
Validating and Transferring Applications
Uploading on a
Local DH+ Link
23–21
This section shows how to upload an application from a DH+
terminal on the DH+ link to your computer. The computer and
terminal are each a separate station on the DH+ link.
Before uploading application:
• check cable connections. See Publication 2711-6.1
• configure the DH+ driver using RSLinx or INTERCHANGE.
Note: The computer runs at 57.6K baud forcing the DH+ link and
terminal to use the same rate. Set the terminal’s DH+ network to this
baud rate before uploading an application.
➀ Choose Upload from the Application menu.
➁ Select the Upload parameters.
Select Local Network Operator Terminal
Select RSLinx or
INTERCHANGE Driver
DH+ is active driver
Enter name of .PVA file in which to
save the uploaded application or
click Browse to search for a file.
Click OK to start upload.
Click Setup to verify station
address of the terminal. The
address shown must match the
address in the Communication
Setup dialog.
Select DH+/RS232.
Under Presets, select:
S Original to upload presets (initial values)
defined for inputs.
S Current States to upload current input
values in terminal.
➂ PanelBuilder software and terminal display status of upload.
➃ When the upload is complete, the application opens in PanelBuilder.
Publication 2711-6.0
23–22
Validating and Transferring Applications
Uploading from a Terminal
Using Pass-Through
This section shows how to upload an application from a PanelView
terminal on a Remote I/O or DH-485 link to your computer on the
DH+ link.
Before uploading an application:
• check cable connections.
• enable Pass-Through in Block Transfer dialog (page 20–11).
• configure DH+ driver using RSLinx or INTERCHANGE.
To upload an application from a terminal using Pass-Through:
➀ Choose Upload from the Application menu.
➁ Select the Upload parameters.
Select Operator Terminal via Pass-Through
Click OK to start
upload.
Select RSLinx or
INTERCHANGE Driver
DH+ is active driver
Enter name of .PVA file in which to
save uploaded application or click
Browse to search for a file.
Select type of terminal from which you
are uploading application.
➂ PanelBuilder software and terminal display status of upload.
➃ When upload is complete, the application opens in PanelBuilder.
Publication 2711-6.0
Click Setup to configure Remote
I/O or DH-485 Pass-Through
parameters. See pages 23–14
and 23–15.
Under Presets, select values to upload:
S Original to upload presets (initial values)
defined for inputs.
S Current States to upload current input
values in terminal.
Validating and Transferring Applications
Using the Application
File Transfer Utility
23–23
Use the Application File Transfer Utility (WINPFT.EXE) to transfer
.PVA files between a terminal and a computer running Windows.
Important:
Applications that you upload or download with this
utility must be in a .PVA format.
To create a .PVA file for downloading, you must download the .PBA
application to a DOS file from the Application menu of
PanelBuilder. Applications uploaded from the terminal are already
in a .PVA format.
To start the Application File Transfer Utility:
• In Windows 95, select Application File Transfer Utility from the
PanelBuilder submenu under Programs on the Start menu.
• In Windows 3.x, double-click the Application File Transfer
Utility icon in the PanelBuilder program group (WINPFT.EXE).
In the Application File Transfer Utility, applications are transferred
from either the File menu or tool bar. The dialogs are very similar to
the PanelBuilder Download/Upload dialogs.
Choose:
Or Click:
To:
Download
Download a .PVA file to a PanelView terminal.
To create a .PVA file, you must download the application
to a DOS file from the Application menu in PanelBuilder.
Upload
Upload an application from a PanelView terminal to a
DOS (.PVA) file.
To load the application in PanelBuilder, open the .PVA
file from the PanelBuilder File menu. The file is translated
to a .PBA file for PanelBuilder.
Verify
Compare application in terminal with the download
application to verify that differences exist.
Exit
Exit the Application File Transfer Utility.
Publication 2711-6.0
23–24
Validating and Transferring Applications
Verifying an Application
Use the Verify command to compare an application with an
application loaded in a specific terminal. You might want to
download an application only if it is different from the application in
the terminal. The verification process checks whether the
applications match.
To verify an application:
➀ Click the Verify tool or choose Verify from the File menu.
➁ Select Verify parameters
Select source terminal for the verify.
Select appropriate driver
(Internal DF1 driver or
RSLinx or INTERCHANGE driver)
Enter name of .PVA file to verify or
click Browse to search for a .PVA file.
Select the type of terminal for which
you are verifying a loaded application.
➂ After clicking OK, the Application Verification dialog opens.
The dialog shows whether the applications match or not.
Publication 2711-6.0
Click OK to start the
verify.
Depending on the
Source selected, you
may have to click Setup
to edit/verify terminal
parameters.
Validating and Transferring Applications
23–25
Downloading to a PanelView Terminal
This section shows how to download a .PVA file to a PanelView
terminal using the Application File Transfer Utility.
!
ATTENTION: When downloading using
Pass-Through with the processor in run mode, verify
the rack address of the target terminal. Downloading
to an incorrect rack address may result in unexpected
operation or damage to equipment.
To download an application:
➀ Click the Download tool or choose Download from the File menu.
➁ Select Download parameters.
Click OK to start
download.
Select target device for download.
Depending on the
Destination selected,
you may have to click
Setup to edit/verify
terminal parameters.
Select appropriate driver
Enter name of .PVA file you want to
download or click Browse to search
for a file.
Check this box to download the
application only if it is different from
the application loaded in the terminal.
➂ After clicking OK, the following dialog opens.
Select the type of terminal you are
downloading application.
➃ Terminal resets, verifies and starts application.
Publication 2711-6.0
23–26
Validating and Transferring Applications
Downloading to a Memory Card
When downloading to a memory card, you can download a .PVA file
or an .OTF font file (created with FontTool) to either of the
following card drives:
• ATA card drive
• DataBook TMB240 or TMB250 card drive
The format of the command entered in the Memory Card DOS
Command Setup dialog is specific to the card drive installed in your
computer.
• For ATA card drives, use the DOS COPY command, for example:
COPY C:\AB\PBWIN\CONTROL.PVA M:
or
COPY C:\AB\PBWIN\FONT\CHINA_S.OTF M:
where M: is the ATA card drive on your computer.
Memory cards compatible with the ATA card drives include
Catalog No. 2711-NM22, -NM24, -NM26.
• For DataBook TMB240 or TMB250 card drives, the command
string has three parameters as shown on page 23–17.
Memory cards compatible with the DataBook card drives include
Catalog No. 2711-NM11, -NM12, -NM13, -NM14.
Publication 2711-6.0
Validating and Transferring Applications
23–27
Uploading from a PanelView Terminal
This section shows how to upload an application from a PanelView
terminal. The application is stored as a DOS file with a .PVA
extension.
To upload an application:
➀ Click the Upload tool or choose Upload from the File menu.
➁ Select Upload parameters.
Click OK to start upload.
Select terminal from which to
upload application.
Depending on the
Source selected, you
may have to click Setup
to edit/verify terminal
parameters.
Select appropriate driver
Enter name of .PVA file in which to
save the uploaded application or
click Browse to search for a file.
Select the type of terminal from
which you are uploading application.
➂ After clicking OK, the following dialog opens.
Under Presets, select values to upload:
S Original to upload presets (initial values)
defined for inputs.
S Current States to upload current input
values in terminal.
➃ The application is saved to .PVA file and you return to the utility workspace.
➄ Open .PVA application from PanelBuilder File menu.
The .PVA file is automatically translated to a
.PBA file for use in PanelBuilder.
Publication 2711-6.0
23–28
Validating and Transferring Applications
Decreasing the Size of
Application for Downloads
If the application is too large to download, the following dialog
opens. The dialog displays the size of the application and the
amount of available space in the PanelView terminal.
Cancels download
Retries download without the data specified in check boxes.
Creates .PVA file but terminates download because
file is too large for PanelView terminal.
You can reduce the size of the application by eliminating:
• PanelBuilder Application Data, including all screens and objects.
• Tag information for the application.
• Network Data, including run-time communication parameters for
the PanelView terminal and controller.
Special Considerations:
• If you eliminate PanelBuilder application data, you will not be
able to upload the application. The entire application must be
re-created.
• If you eliminate tag data, you will be able to upload the
application but will need to re-enter the tags in the Tag Editor.
• If you eliminate network data, you will be able to upload the
application but must re–enter runtime communication parameters
for devices in the Terminal Setup dialogs.
Exceeding RAM Memory
in Terminal
Publication 2711-6.0
The following dialog opens if the application you are downloading
exceeds the RAM memory in the PanelView terminal.
Creating Reports
Chapter Objectives
This chapter shows how to create application reports. It contains the
following sections:
Section
Types of Reports
Page
Types of Reports
24–1
Connecting a Printer
24–1
Creating and Printing a Report
24–2
Changing the Report Setup
24–3
Setting up a Printer
24–5
Sending the Report to a File
24–6
PanelBuilder lets you specify the types of information to include in a
report.
Report Options
Description
Description
Includes the first page of the application description as entered in
the Application Description dialog.
Object Attributes
Lists attributes of all objects in the application.
Objects are listed by their object ID.
Text
Lists all text strings in the application.
Terminal Setup
Lists setup parameters for the PanelView Terminal.
Tag Attributes
Lists all tag definitions in the application.
Alarm Setup
Lists all alarm information defined for the application.
In addition, you can include screen images and a summary of objects
for all screens or a range of screens in the application.
To print screen images, you need a graphics printer that’s supported
by Windows.
Connecting a Printer
Refer to the user manuals supplied with your printer and computer
for instructions on connecting a printer.
Publication 2711-6.0
24–2
Creating Reports
Creating and
Printing a Report
The Report command on the File menu lets you create a customized
report documenting all or specific aspects of an application. Reports
are useful for tracking application updates and changes.
To set up a report:
1. Choose Reports from the File menu.
2. Under Application, select topics to include in report by clicking
the appropriate check boxes. To disable a topic, clear the box.
3. Under Screens, select screens to include in the report. Click All
to include all screens or From to include a range of screens.
Enter the range of screen numbers in the From and To boxes.
4. The Alarm Banner check box specifies whether you want to
include the Alarm Banner with each screen. By default, the
Alarm Banner is included.
5. Under Include, specify whether you want to include Screen
Images and/or an Object Summary for each screen by clicking the
appropriate check box. To disable an option, clear the check box.
Do not select Screen Images when printing to a file.
Press:
To:
Send report to printer (or file). Click Cancel at any time to abort
printing of report.
Exit dialog without printing report.
Change page headers and title page of report. See page
24–3 for details.
Define printer settings for report. See page 24–5 for details.
Save current report settings as the default. Otherwise, the
dialog reverts back to the original settings when closed.
Publication 2711-6.0
Creating Reports
Changing the Report Setup
24–3
You can specify what components will appear in the page headers
and title page of a report.
To change the page headers and title page:
1. Click the Report Setup button from the Report Setup dialog.
The Report Setup dialog opens.
2. Select Header and Title Page options by clicking the appropriate
check boxes in each area. To disable an option, clear the box.
Select:
To print:
Application Name
Name of the application.
Time
Time of printout in a 24 hour format:
Hour / Minute / Second
Date
Date of printout in the format: Month / Day / Year
Page Number
Consecutive page numbers (includes title page).
User Defined Text
Up to 80 characters (including spaces) of
user-defined text.
The next page shows where each option appears in the page
header and title page of a report.
3. When done, click the OK button. Or click Cancel to exit
the dialog without saving changes.
Publication 2711-6.0
24–4
Creating Reports
Header
The header appears on every page of a report except the title page.
Page Number
Application Name
User Defined Text
Date and Time (of printout)
Title Page
The title page is the first page printed in a report.
Project: Application Name
Version and Save Information
Date and Time (of printout)
User Defined Text
Publication 2711-6.0
Creating Reports
Setting up a Printer
24–5
To print a report, a printer must be connected to your computer and
your computer must recognize the printer as a valid printer. See your
Microsoft Windows User’s Guide for details on installing print
drivers.
To set up the printer:
1. Click the Printer Setup button from the Report Setup dialog.
The standard Microsoft Print Setup dialog opens.
2. Set appropriate attributes for your printer.
3. Click the Options button to enter options specific to your printer.
The Options dialog is different for each printer type.
4. When done, click the OK button. Or click Cancel to exit the
dialog without saving changes.
If your printer is not listed:
• Check for hardware compatibility between your printer and one
of the printers listed.
• Check if your printer has an emulation mode that is compatible
with one of the printers listed.
• You may need to install a print driver for your printer. Refer to
the Microsoft Windows User’s Guide.
Publication 2711-6.0
24–6
Creating Reports
Sending the
Report to a File
To send a report to a file, the Generic / Text Only printer must be
installed and connected to the FILE: printer port on your computer.
This printer driver allows you to print text, but not graphics.
You can install this printer from the Printer icon of the Control Panel
window in the Program Manager. See your Microsoft Windows
User’s Guide for details.
To send a report to a file:
1. Click the Print Setup button from the Report Setup dialog.
The standard Microsoft Windows Print Setup dialog opens.
2. Under Specific Printers, select Generic / Text Only on FILE: as
shown above.
If Generic / Text Only on FILE: isn’t listed as an available option,
you must install this printer option.
If your application uses large text sizes, open the Options dialog and
enable Wide Carriage.
3. Click OK.
4. Click the Print button from the Report Setup dialog.
The Print to File dialog opens.
5. In the Output File Name box, enter the name of the file to receive
the report.
The default location is C:\AB\PBWIN\.
6. Click OK to output report to file.
If the file name already exists, you are given the option of
overwriting it or entering another file name.
Click Cancel at any time to abort operation.
Publication 2711-6.0
Command Summary
File Menu
Choose:
To:
New...
Create a new application file for a PanelView terminal.
Open...
Open an existing application file and display a list of all
screens in the application.
Close...
Close the application file.
Save
Save changes (since the last save) to the application file
and replaces the previous version stored on disk.
Save As...
Save a copy of the application file under a new name with
all changes you made to it. The original file remains intact.
Copy Font File...
Copies a font file stored in PBWIN\FONT to an ATA flash
card inserted in the ATA card drive on your computer.
Import/Export Graphics...
Import a bitmap created with another program. The bitmap
can be imported from a file or the clipboard. You can also
export a bitmap graphic to a file or the clipboard.
Reports...
Generate a customized report for an application using the
default or user defined format. Reports can be printed or
saved to a file.
Workstation Setup...
Access the INTERCHANGE Configuration Utility to
configure serial communications required for transferring
applications on your computer.
Exit
Quit PanelBuilder returning you to the Windows desktop.
1
2
3
4
Screen Menu
File Name
File Name
File Name
File Name
Open the most recently accessed file. The bottom of the
File menu displays the last 4 application files opened with
the most recently accessed file displayed first in the list.
Choose:
To:
New...
Create and open a new screen in the application file.
Open...
Open existing screens in the application file.
Close...
Close the active screen.
Attributes...
Rename, renumber or change the background color of the
active or selected screen.
Create Alarm Banner
Create a display in which alarm messages and alarm
buttons appear. The banner is global to all screens.
Publication 2711-6.0
A–2
Command Summary
Edit Screen Menu
Edit Objects Menu
Publication 2711-6.0
Choose:
To:
Cut Screen
Remove selected screens from the application and place
them on the clipboard. Anything you cut remains on the
clipboard until you change it or exit Windows.
Copy Screen
Copy selected screens to the clipboard leaving the
originals intact. Use this command to copy screens from
one application to another or within the same application.
Paste Screen
Place screens that are on the clipboard into the application.
Delete Screen
Remove selected screens from the application without
placing them on the clipboard.
Choose:
To:
Undo
Reverse the most recent edit operation: cut, copy, paste,
delete, select all, bring to front, send to back,
group/ungroup/regroup.
Cut
Remove selected objects from the screen and place them
on the clipboard. Anything cut remains on the clipboard
until you change it or exit Windows.
Copy
Copy selected objects to the clipboard leaving the originals
intact. Use to copy objects from one screen to another.
Anything copied remains on the clipboard until you change
it or exit Windows.
Paste
Place objects from the clipboard onto the screen. Objects
remain on the clipboard even after the paste operation.
Delete
Remove selected objects from screen without placing them
on the clipboard.
Select All
Select all objects on the screen.
Bring To Front
Move the selected object in front of other objects.
Send to Back
Move the selected object to the back of other objects.
Bring Dynamic Objects
to Front
Move all dynamic objects in front of other objects. Use this
command when done with a screen to verify what the
screen will look like on the terminal.
Group
Group two or more objects into a single unit.
Ungroup
Separate grouped objects.
Regroup
Reassemble a former group of objects.
Use Existing Text ...
Open a dialog that lets you access all text strings in the
application.
Object Attributes ...
Open a dialog for the selected object allowing you to edit
its attributes. You can also double-click an object to edit its
attributes.
Set Object Color Defaults
Set default colors for objects of the same type.
Command Summary
View Menu
Objects Menu
A–3
Choose:
To:
Tool Bar
Toggle the tool bar on or off.
Status Bar
Toggle the status bar on or off.
Toolbox
Toggle a toolbox of control, display and graphic objects on
or off.
ISA Symbols
Toggle a toolbox of ISA symbols on or off.
Color Palette
Toggle the color palette on or off. (Color Terminals only)
Alarm Banner Position
Reposition the Alarm Banner on application screens.
Keypad
Toggle the numeric keypad on or off for all screens.
Full Size
Return the screen to its full size. This command is used
with Zoom In and Zoom Out.
Zoom In
Magnify the screen so objects look larger. You can increase
the magnification several times. Each time you select Zoom
In, the magnification increases to the next higher setting.
Zoom Out
Reduce the magnification of the screen so objects look
smaller. You can reduce the magnification several times.
Each time you select Zoom Out, the screen reduces to the
next lower setting.
Choose:
To:
Push Button Open a submenu to create a momentary, maintained,
latched or multistate push button.
Screen Selectors Open a submenu to create a goto, goto config screen or
return screen button. You can also create a screen list from
which a screen is selected.
Numeric Entry Open a submenu that lets you create a cursor point or
keypad enable button. Both objects activate a scratchpad
and the terminal’s keypad for numeric data entry.
ASCII Entry Open a submenu that lets you create a cursor point or
keypad enable button. Both objects activate a scratchpad
for entering a character string.
Control List Selectors Open a submenu to create a standard or piloted control list.
Indicators Open a submenu to create a multistate or list indicator.
Numeric Data Display
Create a numeric data display.
Bar Graph
Create a horizontal or vertical bar graph without scaling.
Scale
Create a scale with tick marks to the right, left, top or bottom
of a bar graph.
Message Display
Create an ASCII message display for displaying status
information or instructions to the operator.
Graphics Open a submenu of drawing tools for creating lines, shapes,
freeform drawings and background text.
List Keys Alarm List
Open a submenu of list keys (Move Up, Move Down, Home,
End, Page Up, Page Down, Backspace, Enter).➀
Create an alarm list which displays triggered alarms.
Alarm Buttons Open a submenu of alarm buttons that you can place in the
Alarm Banner (Acknowledge, Clear, Print, Clear Alarm List,
Print Alarm List, Acknowledge All).
Global Object...
Open a dialog that lets you select a global object for
placement on a screen.
➀ Required on PanelView 900/1400 Touch Screens to move the cursor in a screen or control list.
Publication 2711-6.0
A–4
Command Summary
Align Menu
Format Menu
Choose:
To:
Grid
Toggle the screen grid on or off. A check mark (✓) next to
the command means the grid is active. To turn the grid off,
choose the command again.
Snap to Grid
Snap objects to grid points on the screen grid.
Touch screen terminals have a Snap to Grid feature which
automatically forces all controls to align with the touch grid.
Grid Attributes...
Set the spacing of grid lines on the X and Y-axis (in pixels) for
the screen grid. Grid attributes are not adjustable on the
touch grid.
Touch Grid
Toggle the touch grid on or off for touch screen terminals. A
check mark (✓) next to the command means the touch grid
is active. To turn the touch grid off, choose command again.
Push buttons are moved and sized in increments of cells on
the touch grid whether the grid is displayed or not.
Choose:
To:
Next State
Change the state of a multistate or list object to the next state
so that you can enter text or a graphic for that state.
Previous State
Change the state of a multistate or list object to the previous
state so that you can enter inner text or a graphic for that state.
Inner Text
Define inner text for each state of an object.
Inner Graphic
Select and insert a graphic for each state of a multistate object.
Text Size Open a submenu to set the size of the selected text.
Align Text Open a submenu to align text to the left, right or center.
Underline
Toggle underlining on or off for the selected text.
Word Wrap
Toggle word wrap on or off for the selected text.
Embedded Variable Open a submenu to insert a time, date, numeric or ASCII
variable in a text string. Also lets you edit a variable.
Foreground Color Open a submenu to select a foreground color for an object, text
or graphic.
Background Color Open a submenu to select a background color for an object,
text or graphic.
Toggle
Fore/Background
Reverse the foreground and background colors of an object,
text or graphic.
Blink
Toggle blinking on or off for the selected object or text.
Fill Pattern Shape
Line Type Publication 2711-6.0
Open a submenu to select a fill pattern for the selected objects.
Open a submenu to change the shape of selected objects.
Open a submenu to change the edge or border type of
selected object(s).
Command Summary
Application Menu
Window Menu
A–5
Choose:
To:
Text Editor...
Open the text editor which stores all text strings in an
application. From the Text Editor, you can create, edit, filter,
sort and print messages.
Tag Editor...
Open the tag editor to view, add or edit tag information for an
application. Tag information is specific to the communication
network on which the application will run.
Project Management...
Open the Project Management dialog to manipulate (display,
create, copy, rename, delete) projects and to manipulate
(create, copy, rename, delete) devices in projects.
Preferences...
Controls whether tags/devices in the application are validated
against the project database when an application is opened.
Description...
Enter an application description and change the application
name. Also shows when the application was last saved.
Validate Changes...
Validate only changes to the application since the last validate.
Changes are validated on a screen by screen basis.
Validate All...
Check the entire application for errors or warnings. This
command is useful for verifying the accuracy of an application
before downloading it to a PanelView terminal.
Download...
Download an application to an operator terminal, memory card
or file. You can also download to a terminal from a computer
on the DH+ network using Pass-Through.
Upload...
Upload an application to PanelBuilder from a PanelView
terminal using a direct connection or Pass–Through.
Terminal Setup...
Set runtime communication and operating parameters for the
PanelView terminal including powerup options, time/date
format, terminal status/control tags and advanced options such
as auto repeat settings for keys or touch cells.
Alarm Setup...
To define alarm messages, alarm triggers and global
parameters that apply to the alarm system.
Print Only
Object Setup...
Define a print only message object. Messages are printed
when triggered rather than displayed in a Message Display.
Choose:
To:
Exceptions...
Open the Exceptions dialog which displays errors created
during application validation. Use this window as a reference
while correcting errors.
Cascade
Arrange open screens in the workspace so that they overlap
each other, with the title bar of each screen remaining visible.
Tile Horizontally
Arrange open screens as horizontal tiles in the workspace.
Tile Vertically
Arrange open screens as vertical tiles in the workspace.
Arrange Icons
Arrange icons so that they are evenly spaced along the bottom
of the workspace and don’t overlap.
Close All
Close all active screens but does not close the application file.
1 Sample
2 1 – Main Menu
✓3 2 – Feed Pump
Activate an open screen. The bottom of the Window menu
displays a list of open screens. A check mark (✓) appears
next to the active screen.
Publication 2711-6.0
A–6
Command Summary
Help Menu
Publication 2711-6.0
Choose:
To:
Index...
Display a list of all available Help topics.
Command
Reference...
Display a description of each menu command and tool in
PanelBuilder.
Reference...
Display a list of help topics that are available for PanelBuilder.
About PanelBuilder...
Display copyright/release information about PanelBuilder.
Tool and Bitmap Summary
This appendix contains a brief description of all PanelBuilder tools
that are grouped on the tool bar, format bar and toolboxes. It also
provides a list of all .BMP files that PanelBuilder provides in the
C:\AB\PBWIN\PBLIB directory.
Tool Bar
File Tools
New File
Creates a new application file.
Open File
Opens a dialog that lets you open an existing
application file.
Save File
Saves changes to the application file.
Screen Tools
New Screen
Creates a new application screen.
Open Screen
Opens an existing application screen.
Cut
Cuts the selection and places it on the Clipboard.
Copy
Copies the selection to the Clipboard.
Paste
Pastes the contents of the Clipboard.
Undo
Reverses the last edit operation.
Edit Tools
Publication 2711-6.0
B–2
Tool and Bitmap Summary
Tool Bar
Format Bar
Publication 2711-6.0
Edit Tools
Object
Attributes
Opens a dialog that lets you edit the attributes of the
selected object.
Next State
Previous State
Changes the state of a multistate or list object to the
next state or the previous state. The State boxdisplays
the current state.
Inner Text
Adds or edits inner text for each state of an object.
Inner Graphic
Adds or changes an inner graphic to the selected state
of a multistate object.
Zoom In
Increases the screen view to the next higher
magnification.
Zoom Out
Reduces the screen view to the next lower
magnification.
Object Formatting Tools
Blink
Toggles blinking on or off for the selected object or
selected state of an object.
Toggle
Fore/Background
Toggles the foreground and background colors for the
selected object or selected state of an object.
Fill Pattern
Changes the fill pattern of an object or selected state
of an object.
Line Type
Changes the line type of the selected object.
Shape
Changes the shape of the selected object.
Group
Groups selected objects into a single unit.
Ungroup
Ungroups the selected group of objects.
Bring to Front
Moves the selected object in front of other objects.
Send to Back
Moves the selected object in back of other objects.
Tool and Bitmap Summary
B–3
Text Formatting Tools
Blink
Toggles blinking on or off for the selected text.
Underline
Toggles underlining on or off for the selected text.
Toggle
Fore/Background
Toggles the foreground and background colors of the
selected text.
Text Size
Increases or decreases the size of the selected text.
Left Align
Aligns the selected text to the left.
Center Align
Centers the selected text.
Right Align
Aligns the selected text to the right.
Embedded
Variable
Inserts a time, date, numeric or ASCII variable in a text
string. Also lets you edit a variable.
Existing Text
Opens the Existing Text dialog.
Edits inner text for an object.
Inner Graphic Tools
Selects an inner graphic from a list of imported bitmaps.
Import/Export
Graphics
Opens the Import/Export Graphics dialog.
Publication 2711-6.0
B–4
Tool and Bitmap Summary
Toolbox
Publication 2711-6.0
Graphic Tools
Selection Arrow
Cancels a tool selection.
Line
Draws a straight line.
Connected Lines
Draws connected lines to form shapes.
Rectangle
Draws a rectangle or square.
Ellipse
Draws an ellipse.
Freeform
Draws a continuous or freehand drawing.
Background Text
Draws a text box in which you can enter text.
Scale
Creates a horizontal or vertical scale with tick
marks on the top, bottom, right or left.
Import/Export
Graphics
Opens the Import Graphics dialog.
Graphic Image
Draws a border for inserting a graphic image.
Tool and Bitmap Summary
B–5
Control and Display Tools
Momentary
Push Button
Creates a momentary push button.
Maintained
Push Button
Creates a maintained push button.
Latched
Push Button
Creates a latched push button.
Multistate
Push Button
Creates a multistate push button.
Go To
Screen Button
Creates a screen selector button that when
pressed allows the operator to go to a specific
screen.
Return
Screen Button
Creates a screen selector button that when
pressed allows the operator to return to the
previous screen.
Screen
List Selector
Creates a vertical list of screen controls from
which the operator can select a screen.
Control
List Selector
Creates a vertical list of operator controls.
Numeric Entry
Cursor Point
Creates a cursor point object which activates a
scratchpad and the keypad for numeric data entry.
Numeric Entry
Keypad Enable
Creates a keypad enable button which enables
the keypad for numeric data entry.
Multistate
Indicator
Creates a multistate indicator.
List Indicator
Creates a list indicator.
Numeric
Data Display
Creates a numeric data display.
Bar Graph
Creates a horizontal or vertical bar graph that fills
from the top, bottom, right or left.
Message Display
Creates a message display for showing status
information or operator instructions.
Global Object
Opens a dialog to access control and display
objects that you’ve set up as global objects.
Publication 2711-6.0
B–6
Tool and Bitmap Summary
List Key Tools
The following List Keys are required on PanelView 900/1400 Touch
Screen terminals to move the cursor in a Control List or Screen List
Selector and to select a list item.
Publication 2711-6.0
Move Up
Moves the cursor up one item in a list.
Move Down
Moves the cursor down one item in a list.
Home
Moves the cursor to the first item in a list.
End
Moves the cursor to the last item in a list.
Page Up
Moves the cursor up one page in a scrolling list.
Page Down
Moves the cursor down one page in a scrolling
list.
Backspace
Moves the cursor to the currently highlighted
selection in a list.
Enter
Confirms a list selection and for a control list
sends the selection to the controller.
Tool and Bitmap Summary
B–7
ISA Symbols Toolbox
Selection Arrow
Cancels an ISA Symbol selection.
Horizontal Valve
with Actuator
Draws a horizontal valve with an actuator.
Horizontal Valve
Throttling Actuator
Draws a horizontal valve with a throttling actuator.
Horizontal Valve
Manual Actuator
Draws a horizontal valve with a manual actuator.
Vertical Valve
with Actuator
Draws a vertical valve with an actuator.
Vertical Valve
Throttling Actuator
Draws a vertical valve with a throttling actuator.
Vertical Valve
Manual Actuator
Draws a vertical valve with a manual actuator.
Butterfly Valve
Draws a butterfly valve.
Check Valve
Draws a check valve.
Relief Valve
Draws a relief valve.
Liquid
Draws a liquid filter.
Vacuum
Draws a vacuum filter.
Motor
Draws an electrical motor.
Transformer
Draws an electrical transformer.
Vessel
Draws a vessel.
Reactor
Draws a reactor.
Storage Bin
Draws a storage bin.
Distillation Tower
Draws a distillation tower.
Pressure
Storage Vessel
Draws a pressure storage vessel.
Weigh Hopper
Draws a weigh hopper.
Pump
Draws a pump.
Turbine
Draws a turbine.
Publication 2711-6.0
B–8
Tool and Bitmap Summary
Publication 2711-6.0
Blower
Draws a blower.
Compressor
Draws a compressor.
Agitator
Draws an agitator.
Conveyor
Draws a conveyor.
Screw Conveyor
Draws a screw conveyor.
Inline Mixer
Draws an inline mixer.
Rotary Feeder
Draws a rotary feeder.
Exchanger
Draws an exchanger.
Furnace
Draws a furnace.
Rotary Kiln
Draws a rotary kiln.
Cyclone Separator
Draws a cyclone separator.
Arrow-Left
Draws a left arrowhead.
Arrow-Up
Draws an up arrowhead.
Arrow-Right
Draws a right arrowhead.
Arrow-Down
Draws a down arrowhead.
Tool and Bitmap Summary
Bitmaps
B–9
This section provides a list of bitmaps that PanelBuilder provides in
the C:\AB\PBWIN\PBLIB directory. These bitmaps can be imported
into your application from the Import/Export Graphics dialog.
cnv2.bmp
pipe14.bmp
cnv3.bmp
pipe15.bmp
cnvy1.bmp
pipe16.bmp
m_3dpb.bmp
pipe21.bmp
m_s3dpb.bmp
pipe22.bmp
3dpb_b.bmp
pipe23.bmp
3dpb_g.bmp
pipe24.bmp
3dpb_gr.bmp
pipe25.bmp
3dpb_r.bmp
pipe26.bmp
3dpb_y.bmp
pipe27.bmp
mtr1.bmp
pipe28.bmp
mtr2.bmp
pipe29.bmp
mtr3.bmp
pipe3.bmp
mtr6.bmp
pipe34.bmp
pausepb.bmp
pipe35.bmp
Publication 2711-6.0
B–10
Tool and Bitmap Summary
Publication 2711-6.0
pipe1.bmp
pipe4c.bmp
pipe5.bmp
sw3.bmp
pipe6.bmp
tank1.bmp
pipe7.bmp
tanka.bmp
pipe8.bmp
tanke.bmp
pipe9.bmp
tankf.bmp
startpb.bmp
tankg.bmp
stoppb.bmp
tankh.bmp
resetpb.bmp
tankh2.bmp
s3dpb_b.bmp
tankj.bmp
s3dpb_g.bmp
tankk.bmp
s3dpb_gy.bmp
tankl.bmp
s3dpb_r.bmp
vlv1.bmp
s3dpb_y.bmp
vlv1b.bmp
sw1.bmp
vlv3.bmp
sw2.bmp
vlv4.bmp
PanelBuilder Worksheets
•
•
•
•
•
•
550/600 Touch Screen Worksheet
550/600 Keypad Screen Worksheet
900/1000/1400 Touch Screen Worksheet
900/1000 Keypad Screen Worksheet
1400 Keypad Screen Worksheet
Address Worksheet
Publication 2711-6.0
C–2
PanelBuilder Worksheets
Publication 2711-6.0
PanelBuilder Worksheets
C–3
PanelView 550/600 Operator Terminal
Touch Screen Worksheet
Project Name:
Application Name:
Screen Name / Number:
F1
F2
F3
F4
F5
F6
F7
F8
F9
F10
Project Name:
Application Name:
Screen Name / Number:
F1
F2
F3
F4
F5
F6
F7
F8
F9
F10
Publication 2711-6.0
C–4
PanelBuilder Worksheets
PanelView 550/600 Operator Terminal
Keypad Screen Worksheet
Project Name:
Application Name:
Screen Name / Number:
F1
F2
F3
F4
F5
F6
F7
F8
F9
F10
Project Name:
Application Name:
Screen Name / Number:
F1
F2
F3
F4
F5
F6
F7
F8
F9
F10
Publication 2711-6.0
PanelView 900/1000/1400 Terminal
Touch Screen Worksheet
Application Name: _____________________
Project Name:_________________________
Screen Name / Number: ______________________________
Note: 900 and 1400 terminals have same number of touch cells but cell size is different.
Project Name:_________________________
Application Name: _____________________
Screen Name / Number: ______________________________
PanelView 900/1000 Terminal
Keypad Worksheet
F1
F2
F3
F4
F5
F6
F7
F8
F9
F10
F11
F12
F13
F14
F15
F16
Project Name:_________________________
Application Name: _____________________
Screen Name / Number: ______________________________
F17
F18
F20
F21
F1
F2
F3
F4
F5
F6
F7
F8
F9
F10
F11
F12
F13
F14
F15
F16
PanelView 1400 Operator Terminal
Keypad Worksheet
F19
PanelView Operator Terminal
Address Worksheet
Word Address
Tag Name
Decimal
Octal
15
17
14
16
13
15
12
14
11
13
10
12
9
11
8
10
7
7
6
6
5
5
4
4
3
3
2
2
1
1
0
0
Word Address
Tag Name
Decimal
Octal
15
17
14
16
13
15
12
14
11
13
10
12
9
11
8
10
7
7
6
6
5
5
4
4
3
3
2
2
1
1
0
0
Word Address
Tag Name
Decimal
Octal
15
17
14
16
13
15
12
14
11
13
10
12
9
11
8
10
7
7
6
6
5
5
4
4
3
3
2
2
1
1
0
0
Word Address
Tag Name
Decimal
Octal
15
17
14
16
13
15
12
14
11
13
10
12
9
11
8
10
7
7
6
6
5
5
4
4
3
3
2
2
1
1
0
0
Software Error and Warning
Messages
This appendix lists messages that may appear during the
configuration of an application. Messages are listed alphabetically.
Message
Meaning
What to do
AB Utilities error creating project.
Project couldn’t be created. Cause could be
full disk or a write protected network partition.
Check available disk space. Or verify your
computers write privileges on network.
AB Utilities failed to initialize.
PanelBuilder could not initialize the AB
Utilities during startup because SHARE.EXE
is not running.
The PanelBuilder installation should add
SHARE.EXE to your AUTOEXEC.BAT file.
See README.TXT in C:\AB for details.
Application has exhausted terminal ID space.
Reduce number of objects in application and
retry.
The application contains more objects than
the application can support.
Reduce the number of objects on a screen
and try again.
Translation Failure!
Error occurred while translating a .PBA
application to a .PVA file for the terminal.
Check for validation error and warning
messages. Try to download again.
Attempt to recover data from (file name)
failed! Error Code: (code number)
Attempt to load data from terminal has failed.
Check network connections and try again.
Cannot create cancel dialog.
Couldn’t create print cancel dialog.
This warning doesn’t affect the print request,
but you may be unable to cancel the request.
Cannot create device context.
Printer driver could not be accessed because
of a corrupted print driver, no printer selected,
or an unstable Windows environment.
Check the Print Setup settings and reboot
computer. If the error reoccurs try another
print driver or reinstall the original driver.
Cannot create error logfile (PB550ERR.LOG).
Error log file couldn’t be created because of a
full disk or write protect condition.
Check available disk space or write
protection.
Cannot create new TAGMAN.
Internal error indicates a possible low memory
condition.
Exit the application and try again. If the error
reoccurs, contact A-B support.
Cannot delete device context.
Printer driver couldn’t be closed. Cause could
be an unstable Windows environment.
Close other applications and try again. If the
error reoccurs, exit Windows, reboot your
computer, and try again.
Cannot find desired terminal in Terminal
catalog.
The CATALOG.DAT file, which stores the
terminal type, is missing or corrupted.
Contact A-B technical support.
Cannot delete error logfile (PB550ERR.LOG).
New logfile will not be created.
On startup, PanelBuilder couldn’t delete the
log file. Cause could be a write protect error
or a SHARE violation.
Check access attributes of the file.
Cannot find or cannot load the Application
File Transfer Utility.
The WINPFT.EXE executable failed to load.
Cannot create the abort dialog box.
Abort dialog couldn’t be initialized. Windows
may be low on resources.
Close applications and try again. If error
reoccurs, exit Windows, reboot and retry.
Cannot initialize print device.
Printer couldn’t be initialized.
Check the Print Setup settings and try again.
Cannot load the Protocol Translate server
PanelBuilder can’t load required files. Editing
the PB550.INI file can cause this error.
Reboot computer and try again. If error
continues, re-install PanelBuilder.
Cannot load the Terminal Specification server
PanelBuilder can’t load required files. Editing
the PB550.INI file can cause this error.
Reboot computer and try again. If error
continues, re-install PanelBuilder.
Otherwise exit Windows and reboot computer.
This should clear SHARE violation. If the
error reoccurs, delete PB900ERR.LOG in c:
\ab\pbwin directory and try again.
Verify that WINPFT.EXE is in the same
directory as PBWIN.EXE. If the file is not
there, reload the file from the installation disk.
Publication 2711-6.0
D–2
Software Error and Warning Messages
Message
Meaning
What to do
Cannot load the Terminal Translate server
PanelBuilder can’t load required files. Editing
the PB900.INI file can cause this error.
Reboot computer and try again. If error
continues, re-install PanelBuilder.
Cannot locate data for tag: (tag name).
Internal error.
Check tag information. Contact A-B technical
support if error continues.
Cannot locate tag: (tag name)
Internal error.
Check tag information. Contact A-B technical
support if error continues.
Cannot open requested screen. Close open
screens to free additional resource memory.
A low memory condition exists.
Close open screens.
Cannot parse address for tag: (tag name).
Internal error.
Check tag information. Contact A-B technical
support if error continues.
Cannot print line.
Failed to send a text string. This may be a
printer error. The printout is terminated.
Check the Print Setup settings, Print Spooler
settings and the printer.
Cannot print text string.
Failed to send a text string. This may be a
printer error. The printout is terminated.
Check the Print Setup settings, Print Spooler
settings and the printer.
Cannot read the Terminal Catalog datafile.
The CATALOG.DAT file is missing or
corrupted. This file stores the terminal type
that is selected when creating a new
application or changing the terminal type for
an application.
Contact A-B technical support.
Cannot renumber text with same text ID.
Same number was used to renumber a
message. Message numbers must be
unique.
Select a different number or cancel operation.
Cannot shutdown print device.
Print session couldn’t be terminated.
Allow printout to complete.
Cannot translate unsaved applications.
Can’t translate a .PBA file to a .PVA file until
the application is saved.
Save the application with the default file name
or save with different file name.
Cannot write to error logfile
(PB550ERR.LOG).
Error log file couldn’t be created. Cause
could be a full disk or write protect condition.
Check available disk space or write
protection.
Cannot write to .INI, changes to editor
settings will not be saved.
.INI file is either write protected or missing.
Check file for possible access locks, such as
network access. PanelBuilder will continue.
Can’t delete project associated with current
application
You can’t delete the project associated with
the current application.
Reassign the current application to another
project, then delete the project.
Compressed file open failed:
(file name)
Couldn’t open compressed application file
because of a full disk or write protect.
Check disk space or write protection.
Compressed file write failed:
(file name)
Couldn’t write compressed application file.
Cause may be full disk or write protect error.
Check disk space or write protection.
Could not open (file name) for output!
Couldn’t open temporary translation file
because of a full disk or write protect.
Check disk space or write protection.
Could not retrieve PLC or Scanner data.
The PLC/Scanner is not configured.
From the Setup tab in the Terminal Setup
dialog, press the Comms. Setup button and
configure the PLC/Scanner type and name.
Could not retrieve terminal port data.
PanelBuilder couldn’t find the terminal port
information necessary for download.
From the Setup tab (Terminal Setup dialog),
press the Comms. Setup button to configure
terminal.
Could not retrieve terminal network data.
PanelBuilder couldn’t find the network
information necessary for download.
From the Setup tab (Terminal Setup dialog),
press the Comms. Setup button to configure
terminal.
Could not retrieve RIO network master data.
PanelBuilder couldn’t find the RIO controller
information necessary for download.
Check the RIO controller settings and retry.
Data format unknown for tag: (tag name).
Internal error.
Check tag information. Contact A-B support if
error continues.
Publication 2711-6.0
Software Error and Warning Messages
Message
Meaning
D–3
What to do
Delete Project From Database.
Are you sure?
The selected project tag database will be
permanently removed.
Select Yes to delete the project or No to
cancel operation.
Disk is full. Translated file cannot be saved.
Not enough disk space to save translated file
during a download.
Check available disk space.
Enter tag name before pressing Edit Tag
button.
Pressed Edit Tag button before entering a
tag name.
Before pressing Edit Tag button, there must
be a tag to edit (enter a tag name).
Error closing file. File may not be valid.
The file failed to close. Cause could be a full
disk or restricted access to network.
Check the amount of available disk space or
for valid access to network file.
Error executing application.
There is not enough memory to execute
<program name>. Please close an
application.
There is not enough memory to start another
session of PanelBuilder Configuration
Software.
Close an application and restart PanelBuilder.
Error importing graphic file.
Verify file is in correct format.
The graphic is too large or in the wrong
format.
.BMP graphic must not exceed pixel size of
display.
Error: Invalid data, missing state data!
Error while reading state data. This indicates
a corrupted edit session.
Close application without saving and retry. If
error reoccurs, contact Allen-Bradley support.
Error loading the font file.
Font file cannot be found or read.
Check location and name of font file. Font file
may need to be recreated.
Error reading application file.
File cannot be loaded.
A read error occurred. File may be corrupted
or a data timeout has occurred on network.
Check for valid access to the file. Try to load
application again.
Error writing application file.
Application not saved.
Disk is full, disk doesn’t exist or the file name
is invalid.
Check available disk space; verify validity of
file/path name; try to save application again.
Error writing application file to disk.
PanelBuilder was unable to write the .PVA
application file. Probable cause is full disk.
Check disk space and try again.
Failure reading file during decompress.
Failure writing file during decompress.
Failure opening file during decompress.
Failure closing file during decompress.
Errors occur during an upload. Cause could
be internal errors or bad floppy disk.
Exit the application and restart. Check for
bad floppy disk. If the error reoccurs, contact
A-B technical support.
File close failed:
(file name)
Upload operation couldn’t close file. Cause
could be a full disk or write protection.
Exit application and restart windows. If the
error reoccurs, contact A-B technical support.
File decompress fail:
(file name)
Compressed application file is corrupt.
Try again. If the error reoccurs, contact
A-B technical support.
File Error – Cannot find ISPCORE.DLL
PanelBuilder would not start because the
default path C:\AB\BIN is missing from
AUTOEXEC.BAT file.
Make sure your AUTOEXEC.BAT file contains
the default path C:\AB\BIN.
File rename error:
(file name)
A file exists with the same file name.
Check for duplicate file names and try again.
Filename Specified for Download Cannot
be same as Application Filename.
Downloaded application using the same file
name and type as the opened file. The file
name or type must be different to prevent the
download file from overwriting application file.
Specify a different file name or file type.
Normally the file type for a downloaded
application is .PVA.
Incompatible AB Utilities version.
PanelBuilder detected incorrect version of the
A-B utilities software on startup.
Reinstall the AB Utilities disk or contact
Allen-Bradley for support.
Insufficient available Windows resources to
run this application. Try closing some other
applications and try again.
There are too many applications running.
Close all running applications and try again.
Invalid application file.
Unable to restore all objects.
Internal error occurred while restoring file.
This may result from a file that was incorrectly
written.
Contact Allen-Bradley customer support.
Invalid filename specified for download.
Invalid destination file entered for the
download.
Enter a valid destination file name or use the
Browse button to search for a file.
Publication 2711-6.0
D–4
Software Error and Warning Messages
Message
Meaning
What to do
Invalid Left Margin. Please select another
number between 0 and 132.
The specified value is not a valid option.
Specify a value between 0 and 132.
Invalid message text number.
Please select another number.
Number entered is invalid.
Backspace over entry and enter a new
message number 1 to 256.
Invalid number of lines. Please select
another number between 1 and 255.
The specified value is not a valid option.
Specify a value between 1 and 255.
Invalid Page Length. Please select another
number between 0 and 255.
The specified value is not a valid option.
Specify a value between 0 and 255.
Invalid Page Width. Please select another
number between 20 and 132.
The specified value is not a valid option.
Specify a value between 20 and 132.
Invalid Perforation Skip. Please select
another number between 0 and 255.
The specified value is not a valid option.
Specify a value between 0 and 255.
Invalid queue size. Please select another
number between 1 and 100.
The specified value is not a valid option.
Specify a value between 1 and 100.
Invalid screen number.
Please select another number.
Screen number entered is invalid.
Backspace over entry and enter a new screen
number 1 to 29,999.
Low memory condition. Scrolling may not
work. Do you wish to continue?
Microsoft Windows is low on memory.
You can continue but the scroll function for
the list window will not be active.
Low resource memory.
Unable to create application screen list
window.
Low memory error.
Close other applications and retry. If error
reoccurs, exit Windows, reboot, try again.
Low resource memory.
Unable to create dialog manager window.
Low memory error.
Close other applications and try again. If the
error reoccurs, exit Windows, reboot your
computer, and try again.
Low resource memory.
Unable to create message edit window.
Low memory error.
Close other applications and try again. If the
error reoccurs, exit Windows, reboot your
computer and try again.
Low resource memory.
Unable to create new screen.
Low memory error.
Close other applications and try again. If the
error reoccurs, exit Windows, reboot your
computer and try again.
Low resource memory.
Unable to create PB frame window.
Low memory error.
Close other applications and try again. If the
error reoccurs, exit Windows, reboot your
computer and try again.
Low resource memory.
Unable to open screen.
Low memory error.
Close other applications and try again. If the
error reoccurs, exit Windows, reboot your
computer and try again.
Low resource memory.
Unable to open additional windows.
Low memory error.
Close other applications and try again. If the
error reoccurs, exit Windows, reboot your
computer and try again.
Maximum number of tick marks for scale is
(number). Tick marks will default to (number).
Entered more tick marks than appropriate for
the size of the scale.
Enter a value equal to or less than the
specified value or cancel the operation.
Memory allocation failed:
(file name)
Upload wasn’t able to allocate sufficient
memory to continue.
Close other applications and try again.
Memory overwritten!
Serious corruption of memory has occurred.
Exit application, exit Windows and reboot
your computer.
Text ID in use by other text.
An attempt to use a message number that is
already in use.
Select a different number.
Text ID must start at 1.
0 was entered as a message number.
Message numbers must start at 1.
Enter message number starting with 1.
Minimum number of tick marks for scale is 2.
Tick marks will default to 2.
Entered value of 2 for scale tick-marks.
Enter a new value.
Publication 2711-6.0
Software Error and Warning Messages
Message
Meaning
D–5
What to do
No application open to associate project with.
Tried to associate a project without opening
an application first.
Open an application and try again.
No data on clipboard.
Nothing on clipboard to paste.
Cut or copy object before pasting.
No default printer.
Use Control Panel to install and select a
default printer.
A default printer hasn’t been configured.
See your Windows User’s Manual for details
on how to install and select printers.
No file ID record found: (file name)
Internal error detected. Cause could be a
faulty disk drive or floppy disk.
Try again. If error reoccurs, contact
Allen-Bradley technical support.
No memory card command specified for
download.
Tried to download to a memory card without
specifying a memory card command.
Select a memory card command and try to
download again.
No source file specified for upload.
Upload requires a source file destination.
Enter source file name before trying again.
Not enough memory to create tool bar.
Not enough memory to install tool bar.
Not enough memory to load bitmap.
Not enough memory to load popup menu.
Low memory error.
Close other applications and other open
screens. If the error reoccurs, exit Windows
and reboot your computer.
Not enough resource memory to open dialog.
Low memory error.
Close other applications and retry. If error
reoccurs, exit Windows, reboot , and retry.
Note: Applications created by this
demonstration version of PanelBuilder 900
will not be compatible with licensed versions.
Application file created using a Demo release
of the configuration software will not be
supported by the released version.
Recreate file with a released version of the
PanelBuilder Configuration Software.
Objects in application have touch cells
assigned. Edit object attributes before
changing application type to Non-Touch.
When changing the terminal type from
touch/keypad to keypad only, you must
reassign touch cell objects to function keys.
For each object, change touch cell input to
function key input, or delete the object.
Out of memory.
Close other applications and try again.
Otherwise, select cancel to quit.
Attempt to allocate additional memory has
failed.
Close other Window applications and retry. If
unsuccessful, PanelBuilder exits.
PanelView application size of (number) bytes
exceeds maximum size of (number) bytes.
You can eliminate some of the upload data
and try again.
The application exceeds the allowable byte
size.
Try to reduce byte size of application.
PanelView application warnings found.
Continue with download?
Warnings found during validation.
The application will download and run.
However, it may not operate as intended.
Correct the warnings and try again.
PanelView internal tag.
No parameters to edit.
Edit Tag button was pressed for internal tag.
You can’t edit internal tags.
Print manager failed.
Error received from print manager (spooler).
Check print spooler for possible errors.
Printer Initialization string can be at most 20
characters.
The specified printer initialization string is too
long.
Shorten the string to 20 or less characters.
Printer setup failed.
Error occurred during printer setup.
Check validity of print driver. Reload driver if
necessary.
Project already associated with current
application.
Selected project is already associated with
the current application.
None.
Project created for tags in application
being opened.
Project Name:
A project doesn’t exist for the uploaded
application.
PanelBuilder creates a project for the
application and fills in all the application tags.
Project does not exist.
Selected project that doesn’t exist.
Select another project name.
Project does not exist. Can’t associate.
Associated application with a project name
that doesn’t exist.
Select an existing project name to link with
the application or create a new project.
Project exists.
Entered a project name that already exists.
Enter another project name or use existing
project.
Publication 2711-6.0
D–6
Software Error and Warning Messages
Message
Meaning
What to do
Range minimum must be less than range
maximum.
Minimum value entered is greater than the
maximum value.
Enter a minimum value that’s less than the
maximum value.
Required network node not found.
The PanelView terminal is attempting to read
or write to a nonexistent location.
Check the SLC setup and program.
Saved device data is missing or corrupted
and cannot be used to update the tag
database.
A .PVA file was uploaded without project
device data.
Recreate all application device data.
Saved tag data is missing or corrupted and
cannot be used to update the tag database.
A .PVA file was uploaded without project tags.
Recreate all application tags.
Screen number already exists.
Please select another number.
Same screen number can’t be used for more
than one screen.
Assign a unique number (1-29,999) to screen.
Seek error:
(file name)
Internal error detected. Cause could be a
faulty disk drive or floppy disk.
Try again.
Selected global object on screen. Global
object can only appear once on each screen.
Global device already appears on the screen.
A global device can only appear once per
screen. Use a local device if needed.
Selected name in use. Enter another name.
Selected graphic image name that’s in use.
Select a different graphic image.
Source file not found or cannot be opened.
Incorrect file name or path.
Verify file name and path are correct. Retry.
Tag in application being opened that does not
exist in the Project.
The application contains one or more tags
that don’t exist in the associated project.
You are asked if you want to add the tag(s).
Tag information saved with application is
incomplete. Please check tag information
when application is opened.
Tag information is incomplete. Tag was
created but doesn’t contain all the necessary
information.
Supply missing tag data in the tag editor.
Tag must be scanned with scan group.
The tags associated with a particular alarm
are not in the same scan group.
Change the tag addresses for the alarm and
make sure they are in the same scan group.
Target terminal cannot support an alarm
banner.
The specified terminal does not support
alarms.
Change the terminal type or remove alarms,
alarm triggers, alarm buttons, and alarm
banners from the application.
Target terminal cannot support alarm triggers.
The specified terminal does not support
alarms.
Change the terminal type or remove alarms,
alarm triggers, alarm buttons, and alarm
banners from the application.
Target terminal cannot support alarms.
The specified terminal does not support
alarms.
Change the terminal type or remove alarms,
alarm triggers, alarm buttons, and alarm
banners from the application.
Target terminal cannot support ASCII callouts.
The specified terminal type does not support
ASCII callouts.
Use the Application Text editor to remove all
ASCII callouts from the messages.
Target terminal cannot support number of
alarms contained in the application.
The specified terminal type cannot support
the number of alarms contained in the
application.
Refer to the user manual to determine the
maximum number of alarms allowed.
Remove any unnecessary alarms.
Target terminal cannot support print only
objects.
The specified terminal type does not support
printing.
Remove all Print Only Objects from the
application.
Temporary file open failed: \ (file name)
PanelBuilder was unable to open a temporary
file during an upload. Probable cause is full
disk or write protect condition.
Check available disk space or write
protection.
Temporary file read failed: \ (file name)
PanelBuilder was unable to read the
temporary file. The file may be locked by
another application or corrupt.
Check if file is locked by another application.
If not, contact Allen-Bradley technical support.
Terminal and computer nodes cannot have
same value.
The terminal and personal computer can’t
have the same address for a DH485 transfer.
Make sure the terminal node address and
computer node address are different.
The existing alarm banner will be overwritten.
Do you wish to continue?
Pasting an alarm banner will overwrite any
existing banner.
Specify whether you want to continue or
cancel the operation.
Publication 2711-6.0
Software Error and Warning Messages
Message
Meaning
D–7
What to do
The PanelView terminal can only use 255
screens, no more screens can be created.
The maximum number of screens is 255.
The specified path for the translated file is
invalid. The translated application file could
not be opened.
File could not be opened during a download.
Check path of specified file.
Too many files currently open. Translated
application file cannot be opened.
File could not be opened because too many
other files or programs are open.
Close other files or applications and try again.
Unable to create application file. Check if disk
write protected.
Disk may be write protected or network
partition has read only access.
If writing to floppy, check write protect. If
writing to a network file, verify write privileges.
Unable to load configuration utility.
Could not load the InterChange Config. utility.
Check that INTERCHANGE Software is
installed.
Unable to load file. Not a PanelBuilder file or
file is corrupted.
File did not pass the Cyclic Redundancy
Check (CRC). This may occur if the file is of
the wrong type or contains corrupted data.
Check that the file is a .PBA file (not .PVA).
If file is corrupted, it must be recreated.
Unable to load file. Application file created
with incompatible version of PanelBuilder.
Application file was created using a newer
release of the configuration software.
Recreate file with a released version of
PanelBuilder Configuration Software.
Unable to load font file (file name). Display
on the screen may not be correct. You may
need to re-install PanelBuilder.
The font file could not be found in its normal
location or is an invalid font file.
Check the name and location of the font file.
Unable to load help file.
Low memory error.
Close other Window applications and retry. If
unsuccessful, the program will exit. You can’t
recover from this error.
Unable to load PanelView terminal fonts.
Font file PB900.FON must be in same
directory as PBWIN.EXE.
Font file is not in its normal location.
Move the PB900.FON file into the same
directory as PBWIN.EXE (AB\PBWIN).
Unable to open exceptions window.
Microsoft Windows is out of resources or user
memory.
Close other applications and retry. If error
reoccurs, exit Windows, reboot , and retry.
UNABLE TO OPEN FILE.
This file was created by PanelBuilder 900
demonstration software.
Application file was created using a Demo
release of the PanelBuilder configuration
software.
Recreate file with a released version of
PanelBuilder Configuration Software.
Unable to open file for reading. File not
loaded.
Read error may occur if a file is corrupted or a
data timeout has occurred on network.
Check for valid access to file. Try to load
application again.
Unable to open screen list window.
Microsoft Windows is out of resources or user
memory.
Close other applications and retry. If error
reoccurs, exit Windows, reboot, and retry.
Unexpected EOF or Error: (file name)
File error. Operation will not continue.
Check for corrupted file.
Unknown fault. Unable to continue.
Unknown fault occurred.
Close application, exit Windows, and reboot.
Upload data may be corrupted. Save
application again and retry download.
Internal error detected.
Cancel download, resave application and
retry download. If error reoccurs, call
Allen-Bradley technical support.
Validating, translating and downloading
application.
Message appears during downloads.
Press the Cancel button to cancel the
download or continue with download.
Value out of range.
Entered value is not in acceptable range.
Enter a value within acceptable ranges.
Publication 2711-6.0
D–8
Software Error and Warning Messages
Message
Min/Max Range Values must be between 0
and 65535.
Meaning
What to do
Min/Max Range Values must be between 0
and 9999.
Min/Max Range Values must be between 0
and (value).
va e .
Va e entered that’s
that s not within
w th n the valid
va d range.
ran e.
Value
th n va
e.
Enter a new va
valuee w
within
validd ran
range.
Write access denied for the specified
translation file or current directory
File or directory could not be accessed.
Check write access.
You must assign an input F-Key.
Object must be assigned a function key.
Assign available function key to object.
You must assign an input F-Key or
turn the view on.
Object must be assigned a function key or the
object view must be turned on.
Assign available function key to object or turn
the object view on.
You must select a valid terminal and firmware
combination.
The terminal you selected is not compatible
with the firmware specified.
Make sure terminal and firmware are
compatible.
Min/Max Range Values must be between
-32768 and 32767.
Min/Max Range Values must be between
-99,999,997,952 and 999,999,995,904
Min/Max Range Values must be binary (a
combination of 0 and 1)
Publication 2711-6.0
Validation Messages
This appendix lists error messages that appear during a validation or
download operation. Messages are listed alphabetically.
Validation Message
Meaning
What to do
Ack Tag must have BCD, signed int, or
unsigned int data type.
An invalid data type was selected for the
alarm acknowledge tag.
Change tags or the data type. Valid data
types are BCD, signed integer, or unsigned
integer.
Ack Tag range must be greater than or equal
to trigger range.
The number of bits in the ack tag’s data
length must be greater than or equal to the
number of data bits for the trigger.
Increase the number of bits in the Alarm
Acknowledge tag.
Acknowledge all value must be greater than
highest bit position for this trigger.
For bit and least significant bit alarm triggers,
the acknowledge all bit position must be at
least one greater than the highest bit
specified for the alarm.
Increase the bit position specified for the
acknowledge all field.
Acknowledge all value used as alarm trigger
value/bit.
Acknowledge all value for the trigger is the
same as one of the values that triggers an
alarm.
Choose a unique value/bit for the
acknowledge all value.
Address overlaps Block Transfer/Pass Thru
Control Byte
A tag is assigned the same address as the
Block Transfer Control Byte (the lowest
accessible byte in the discrete I/O rack).
Enter a different address for the tag in the Tag
Editor or disable block transfers (if not using
BTs) in the Block Transfer dialog.
Alarm List queue size too large for remaining
NVRAM space.
The specified size of the alarm list queue is
too large for the available memory.
Specify a smaller alarm list queue size.
Alarm requiring acknowledgement must be
displayed.
An alarm acknowledge button is defined but
the alarm is not enabled for display.
Enable the alarm for display.
Alarm Trigger cannot be the same as the
acknowledge or handshake tags.
The alarm trigger is assigned the same tag
name as the Ack or Handshake tag.
Change the tag names so they are unique.
Alarms requiring acknowledgement cannot be
acknowledged individually from the alarm list
without the Enter list key.
An alarm that can be acknowledged in the
alarm list does not have an Enter list key on
the screen.
Add an Enter list key to the specified screen.
All states in this object refuse operator entry.
All states of the piloted control list have an
access of “Controller Only” or ”None”. This
is illegal.
Open the object’s dialog and change the
access for some of the states to “User and
Controller” or “User Only”.
An alarm ack button must exist.
There is an alarm that requires and
acknowledgement (ack) button.
Add an alarm acknowledge button to the
alarm banner.
An alarm clear button must exist
An alarm that does not require
acknowledgement exists. A clear button must
be defined to clear the alarm.
Add alarm clear button to the alarm banner.
An alarm banner must exist.
An alarm banner is not defined and an alarm
is enabled for display.
Turn off the display for the alarm or create an
alarm banner for the application.
Application translation failed – a Screen uses
too many Terminal Resources.
A screen contains too many controls and
indicators.
Redesign the screen with fewer control or
indicator objects.
Application type does not match terminal
type. Re-configure in Terminal Setup.
The application is configured for Remote I/O
or DH-485 communications but the selected
terminal type does match.
From the Setup tab in Terminal Setup, select
a terminal type that matches the application.
Or convert the application to match the
terminal type. Then update the tags.
At least one alarm must be configured to use
this object.
An alarm device exists which requires an
alarm to be configured.
Remove the device or add alarms to the
application.
Publication 2711-6.0
E–2
Validation Messages
Validation Message
Meaning
What to do
Bit positions for this trigger should be
contiguous.
For fastest operation, all alarms within a
trigger should use successive bits (i.e. 1,2,3,4
as opposed to 1,3,5,6)
Change the bits used for triggering so they
are contiguous for this trigger.
Bit position out of range for this trigger.
The bit position specified for the alarm trigger
exceeds the number of positions supported
by the trigger’s data type/length.
Move the alarm to another trigger or change
the trigger’s data type/length.
Block Transfer Channel Number: (Num) –
Length is Invalid.
The block transfer length is defined as 0 or
exceeds the maximum of 64.
In the Block transfer dialog, correct the invalid
length of a block transfer.
Cannot use Bit Array tags with LSB triggering
in FMW 1.00-1.xx.
A bit array has been specified as a Least
Significant Bit trigger.
Select a different data type.
Cannot use Internal Tags with LSB triggering.
An internal tag is specified for use with Least
Significant Bit triggering of an indicator.
Select a non-internal tag.
Cannot write to output of discrete rack
The write tag of a control object is assigned a
discrete rack output address. The PanelView
cannot write data to a controller output.
Change the address of the write tag
(controller input) or use a different write tag
for the object.
Can’t trigger off of an internal tag.
Internal tag specified as a trigger.
Select a non-internal tag.
Copying Font File...
Status message displayed while saving a font
file to disk or memory.
Wait for save operation to complete.
Custom text for numeric scratch pad (Enter
value) text is limited to (number) characters
Text is limited to 30/15 for characters when
single/double byte is selected.
Reduce text or change font size.
Custom text for numeric scratch pad (to) text
is limited to (number) characters
Text is limited to 4/2 for characters when
single/double byte is selected.
Reduce text or change font size.
Data bit (Num) number out of range
The bit number assigned to an object state is
out of range.
Open the object’s dialog and select a different
bit number for the object state.
Data value (value) is out of range
The value entered for an object state is not
within the valid range for the data type.
Open the object’s dialog and enter a valid
value for the state.
Decimal position must be less than field width
by at least 2 digits.
The decimal position for a numeric data
display or variable is > than the field width -2.
Open the object’s dialog and select a decimal
position that is less than the field width.
Decimal position (number) out of range
The decimal position for a numeric data
display or variable is invalid for the field width.
Open the object’s dialog and enter a decimal
position that’s valid for the field width.
Device (name) has node address outside
valid range 1 - 31
The device has an incorrect DH-485 node
address.
From the Setup tab in Terminal Setup, press
the Comms. Setup button to correct the
DH-485 node address.
Device too small for Text display
An object is too small to display the inner text.
Change the size of the object or use a smaller
text size.
Duplicate alarm values or bits exist within
trigger.
More than one alarm uses the same trigger
value/bit.
Change the alarm trigger bits/values so they
are not identical.
Duplicate data bit number (number) in state
(number)
The same bit number is assigned to two
states of an object.
Open the object’s dialog and select a different
bit number for one of the states.
Duplicate data value (value) in state (number)
The same value is assigned to two states of
an object.
Open object’s dialog and enter a different
value for one of the states.
Duplicate Tags
Write tag (name) is already in use
Two objects contain the same write tag.
Control objects cannot use the same write tag
address.
Select another write tag for one of the objects.
Dynamic object obscured by another object,
appearance on terminal may differ.
A dynamic object is obscured by another
object when redrawn on the terminal because
of data updated in controller. The object that
is obscuring the dynamic object is erased.
Move the object.
Field length (number) out of range
The field width for a numeric data display or
variable is invalid.
Open the object’s dialog and enter a valid
field width.
Publication 2711-6.0
Validation Messages
Validation Message
Meaning
E–3
What to do
Font file is not successfully loaded
Font file cannot be read.
Check the (file name).otf file to make sure it is
the latest file created from FontTool.
Font file must contain 16 high font to
customize numeric scratch pad text.
Font file does not contain 16 high font.
Create font file with 16 high font, refer to
terminal font setup dialog.
Foreground and background colors must be
different.
The foreground and background colors for
this object are the same.
Change colors so they are not identical.
Function key not assigned
The object is configured for function key input
but isn’t assigned to a specific function key.
Open the object’s dialog and select a function
key.
Function key (number) not valid
The specified object is assigned an invalid
function key.
Open the object’s dialog and assign a valid
function key.
Function key (number) used twice
The same function key is assigned to two
different objects on the same screen.
Open one of the object’s dialog and assign a
different function key.
Graphic foreground color is the same as its
background color.
Graphic foreground color is the same as text
background color.
Change colors so they are not identical..
Graphic (name) not found
An object or object state is assigned an inner
graphic that no longer exists.
Select another inner graphic for the object or
import a bit map graphic with the same name.
Handshake tag not defined
The handshake tag is undefined for a latched
push button object.
Open the object’s dialog and assign a
handshake tag name.
Height (value) is out of range
The height of the object is invalid.
Resize the object.
Hold time (value) is out of range
The hold time entered for a momentary push
button is invalid.
Open the object’s dialog and select a hold
time from the Hold Time list box.
Illegal font size for this type of device.
An internal font size with the same height as
the currently selected external font does not
exist for a device having a list cursor or an
acknowledge icon.
Make sure that an internal font size exists with
the same height as the currently selected
external font.
(Initial, Min, Max, Scale or Offset) value of
(value) not valid or not in range
The value entered for the initial value,
min/max value, or scale/offset value is invalid
or out of range for the tag data type.
Enter a value that is within the valid range for
the data type.
Initial Value entry of (value) for tag (name)
may result in out of range data value
Initial value specified for the tag is not within
the min/max data entry limits entered in the
Tag Editor.
Enter an initial value that is within the valid
min/max range for the tag.
Initial Value entry of (value) for tag (name) will
yield controller Initial Value of (value) due to
scaling and rounding
A warning that indicates the initial value sent
to the controller will be rounded because of
the precision of the scale factor.
Action is not required unless a rounded value
is unacceptable.
Initial Value of (value) for tag (name) yields an
Out of Range controller Initial Value of (value)
Initial value specified for the tag is not within
the valid range for the data type.
Enter an initial value that is valid.
Invalid length, Bit Arrays cannot cross word
boundaries.
The length of a bit array exceeds 16 bits.
Change the starting bit number for the bit
array or change the array size in Tag Editor.
Loading external font file...
Status message displayed when loading
external font.
Wait until operation is complete.
Logic controller is not configured for Block
Transfers. Terminal’s RIO Port setup requires
Block Transfer support.
The terminal is configured to use Block
Transfers but the controller is not.
From the Setup tab (Terminal Setup dialog),
press the Comms. Setup button. Verify that
the selected controller supports block
transfers. If the controller supports block
transfers, press the Block Transfer button and
verify that block transfers are defined.
Max entry limit of (value) for tag (name) may
result in out of range data value
The max data entry limit value entered in the
Tag Editor lets you enter a number resulting in
an out of range value on the logic controller.
Enter a valid maximum data entry limit in the
form view of the tag editor.
Min entry limit of (value) for tag (name) may
result in out of range data value
The min data entry limit value entered in the
tag editor lets you enter a number resulting in
an out of range value on the logic controller.
Enter a valid minimum data entry limit in the
form view of the tag editor.
Publication 2711-6.0
E–4
Validation Messages
Validation Message
Meaning
What to do
Min range (value) is greater than max range
(value)
The minimum value for a bar graph is set to a
value that’s greater than the maximum value.
Open the object’s dialog and re-enter valid
min/max range values.
Min value (value) is greater than the max
value (value)
The min setting is greater than the max
setting for data entry limits of a tag.
From the form view of the tag editor, make
sure the min data entry limit is less than the
max data entry limit for the tag.
Missing acknowledge tag.
Acknowledge handshake tag is defined
without an acknowledge tag.
Define an acknowledge tag for the trigger.
Missing or invalid screen assignment
A screen selector object has a missing or
invalid screen assignment.
Open the object’s dialog and reassign screen.
Missing notification or handshake tag
Notification and handshake tags are used
together. One of the tags is missing.
Enter the missing tag.
Missing remote acknowledge tag.
Remote acknowledge handshaking tag is
defined without a remote acknowledge tag.
Define a remote acknowledge handshake tag
in the Alarm Setup dialog.
Missing remote clear tag.
A remote clear handshake tag was defined,
but the remote clear tag was not defined.
Specify a remote clear tag in the Alarm Setup
dialog.
Msg (text) variable at Position (text number)
Indicates an error with an inner text string.
Open the Use Existing Text dialog and locate
the message. Correct the error.
Name is not valid
The specified screen name is invalid. A valid
screen name has 1 to 32 characters.
Rename the specified screen.
Name not found in project database
Tag not found in project database.
Enter tag name and attributes in project
database.
Network (name) has no RIO master device
found in project.
A remote I/O master device (PLC/SLC) is not
defined for the Remote I/O terminal.
From the Setup tab (Terminal Setup dialog),
press the Comms. Setup button to define PLC
or SLC controller.
Nonexistent trigger specified.
The trigger specified for this alarm does not
exist.
Use a valid trigger name in the alarm
definition.
No objects in application
The application doesn’t have any objects.
This is a warning.
Exit the application or create screens with
objects.
No objects on screen
The application contains an empty screen
(without objects). This is a warning.
Delete the screen or add objects (and tag
information) to screen before downloading.
No screens in application.
The application doesn’t have any screens.
This is a warning.
Exit the application or create screens with
objects.
No start-up screen assigned, default to
screen (name)
A startup screen wasn’t assigned for the
application so a default screen was selected.
Open the Terminal Setup dialog to select
another startup screen (if necessary).
Node address of (value) is not valid
The node address of the node associated
with the tag has not been entered or is invalid.
From the Setup tab (Terminal Setup), press
the Comms. Setup button to check the node
address.
Number of lines per alarm (number) is greater
than number of lines in object (number).
The number of lines specified for alarms in
the alarm list device exceeds the number of
lines available within the list device.
Make the alarm list device larger or reduce
the number of lines to display per alarm.
Number is not unique
Two screens have the same number. Screen
numbers must be unique.
Renumber one of the screens using the
Rename command on the Screen menu.
Object foreground color is the same same as
its background color.
Graphic foreground color is the same as text
background color, making the graphic a large
solid rectangle.
Change colors so that they are not identical.
Object (right, left, top, bottom edge) – location
(Num)
One or more edges of an object is off the
screen.
Move or size the object as appropriate.
Object has invalid function key or view
assignment
The object doesn’t have an assigned function
key for operator input.
Open the object’s dialog and assign an
available function key.
Object has invalid function key, touch cell, or
view assignment
The object isn’t assigned a function key or
touch cell for operator input.
Open the object’s dialog and select function
key or touch cell for operator input.
Publication 2711-6.0
Validation Messages
Validation Message
Meaning
E–5
What to do
Object not on touch cell boundary
A touch object doesn’t align with touch cells.
This can occur if the user assigns touch cell
input after the object has been sized.
Resize object or move object until it snaps to
grid.
Object requires function key or touch
assignment
The specified object isn’t assigned a function
key or touch cell for operator input.
Open the object’s dialog and assign a
function key and/or touch cell.
Object too small to display text.
The height of the object is too small to display
the first line of text.
Increase the height of the object.
Overlapping control objects
Two objects are overlapping on the screen.
Access the screen and reposition or resize
the objects so they don’t overlap.
PLC or Scanner not configured in Terminal
Setup – Comms. Setup
The PLC/Scanner with which the terminal will
communicate is not configured in Terminal
Setup (Communication Setup dialog).
From the Setup tab in Terminal Setup, press
the Comms. Setup button to configure the
PLC/Scanner type and name.
PLC or Scanner not found in Project
Database
The PLC/Scanner with which the terminal will
communicate is not defined in Terminal Setup
(Communication Setup dialog).
From the Setup tab in Terminal Setup, press
the Comms. Setup button to define the
PLC/Scanner type and name.
Print Only Objects do not support printing of
double-byte characters.
Double-byte font selected for print only object.
Select a single byte size font.
Project database has not been defined for the
application
The application is not linked to a tag
database.
Open the Project Management dialog
(Application menu) and either create a project
or link an existing project to the application.
Read tag not defined
A read tag has not been defined for the
object.
Open the object’s dialog and assign a read
tag.
Rack number of the Terminal is not supported
by the Logic Controller
The rack number assigned to the Remote I/O
PanelView terminal exceeds the rack number
supported by the controller or is set at 0 which
is not supported by the controller.
From the Setup tab in the Terminal Setup
dialog, press the Comms. Setup button and
reconfigure the rack number.
Required Tag fields missing or incomplete.
Tag has no type, node name, or address
specified.
Complete tag information in the Tag Editor.
Remote Ack tag range must be greater than
or equal to trigger range.
A bit array size for the Remote Acknowledge
tag was specified that is less than the
Trigger’s bit array.
Make sure the bit array size for the Remote
Ack tag is greater than or equal to the bit
array for the trigger.
Saved device data is missing or corrupted
and cannot be used to update the device
database.
The device data did not pass the CRC check
and will not be used to update the project
database.
Use Communication Setup to recreate
devices.
Saved tag data is missing or corrupted and
cannot be used to update the tag database.
The tag data does not pass the CRC check
and will not be used to update the tag
database.
Use the Tag Editor to recreate the tags.
(Scale factor) value of (value) has too many
significant digits.
A scale factor was entered with more than 4
significant digits.
Enter a valid scale factor.
Search and control tags are required for
Piloted Control Lists.
Either a search tag and/or a control tag was
not defined for a pilot control list. Both are
required.
Open the object’s dialog and enter the
missing search tag and/or control tag.
Slot Number of Address does not match other
tags
A tag has a different slot number than other
tags in the application. An application can
only access tags from one slot of an SLC.
Verify that all tags in the application use the
same SLC controller slot number.
Startup screen must be assigned to an
existing screen
Startup screen assigned to a nonexistent
screen in the application. The screen may
have been deleted.
Select the Power-up tab from Terminal Setup
dialog and reassign the startup screen.
State number (number) out of range
An object has an invalid state number.
Select the object, open the List Management
dialog and delete the invalid state(s).
Publication 2711-6.0
E–6
Validation Messages
Validation Message
Meaning
What to do
Tag does not have a valid address in the
terminals assigned Discrete Rack or Block
Transfers.
The tag address is not in the I/O rack or the
block transfer(s) configured for the terminal.
Enter the correct tag address in Tag Editor or
reconfigure parameters in the Terminal Setup
(Communication Setup) dialog.
Tag (name) Initial Value entry must be integer.
The initial value for the specified tag was
entered with a decimal point (1.5). The initial
value must be an integer.
Enter an integer for the initial value.
Tag (name) is not included in the Alarm
Trigger’s scan group.
Rem Ack tag or embedded tag in alarm
message is not in the alarm trigger’s scan
group.
Verify the alarm trigger has a lower address
than the remote tag or embedded tags.
Tag (name) must be of type Bit
A value type tag was selected where a bit tag
must be used.
Select an appropriate tag.
Tag (name) must be of type Value
A bit tag was selected where a value tag must
be used.
Select an appropriate tag.
Tag (name) – No Device in Project Database
to match Nodename (name)
The Project database does not have a device
matching the node name for the specified tag.
Use Communication Setup to add the device
with the specified node name to the project or
enter the correct node name for the tag in the
Tag Editor.
Tag not of type Value or Bit
An inappropriate tag was selected.
Select an appropriate tag.
Tag/Object data type mismatch.
Data type of an object entered in the tag
editor must be compatible with the data
format of the value entered in the object’s
dialog.
Correct the discrepancy by opening the
object’s dialog or accessing the object’s tag
information.
Tag references device (name). This is not the
Logic Controller selected in Terminal Setup –
Comms. Setup
The node name field in the Tag Editor
references a controller that is invalid or does
not match the controller name in Terminal
Setup (Communication Setup dialog).
Change the node name to match the
controller name in the Communication Setup
dialog or select the correct controller name in
the Communication Setup dialog.
Target terminal can only handle (number) list
devices on one screen.
Screen contains more list objects than the
terminal can handle.
Remove one or more of the list objects from
the screen.
Terminal (name) has no RIO Block Transfer
Channel Information in the Project Database
Block transfers have not been defined for the
Remote I/O terminal.
From the Setup tab in the Terminal Setup
dialog, press the Comms. Setup button. Then
press the Block Transfer button to define
block transfer assignments for the terminal.
Terminal (name) has no RIO Rack Module
Group Information in the Project Database.
The terminal is not assigned to a rack or
module groups in the rack.
From the Setup tab (Terminal Setup dialog),
press the Comms. Setup button to define the
rack and module group for the terminal.
Terminal (name) is not configured in Terminal
Setup – Comms. Setup
Communication parameters have not been
defined for the terminal name defined on the
Setup tab in the Terminal Setup dialog.
From the Setup tab (Terminal Setup dialog),
press the Comms. Setup button to define
communication parameters for the terminal.
Terminal (name) is not configured in Terminal
Setup – Comms. Setup – Type Unknown
The terminal is not configured properly.
Open the Project Management dialog and
delete the terminal device from the project.
Then open the Terminal Setup dialog and
reconfigure the terminal.
Terminal (name) is not configured in Terminal
Setup–Comms. Setup–No Runtime Comm.
Port
The terminal is not configured properly.
Open the Project Management dialog and
delete the terminal device from the project.
Then open the Terminal Setup dialog and
reconfigure the terminal.
Terminal (name) is not configured in Terminal
Setup – Comms. Setup – Runtime Comm.
Port Not in Project database.
The terminal is not configured properly.
Open the Project Management dialog and
delete the terminal device from the project.
Then open the Terminal Setup dialog and
reconfigure the terminal.
Publication 2711-6.0
Validation Messages
Validation Message
Meaning
E–7
What to do
Terminal (name) is not configured in Terminal
Setup – Comms. Setup – Runtime Comm.
Port is wrong type.
The terminal is not configured properly.
Open the Project Management dialog and
delete the terminal device from the project.
Then open the Terminal Setup dialog and
reconfigure the terminal.
Terminal (name) max node number (value)
not valid
The maximum node number is invalid. The
maximum node number must be in the range
of the terminal node number to 31.
From the Setup tab in the Terminal Setup
dialog, press the Comms. Setup button to
change the maximum node number.
Terminal name not assigned
The terminal isn’t assigned a terminal name.
From the Setup tab in the Terminal Setup
dialog, enter a name for the terminal.
Terminal (name) node number is not valid
The node number of the terminal must be in
the range of 1 to 31.
From the Setup tab in the Terminal Setup
dialog, press Comms. Setup button to change
the node number of the terminal.
Terminal selected in Terminal Setup does not
match Application type.
The wrong catalog number was selected for
the terminal name in Terminal Setup.
From the Terminal Setup dialog, select the
correct terminal type to match the application
(DH-485 or Remote I/O).
Terminal Status and Control cannot use the
same tag for the same purpose.
The same tag is being used for a control tag
and a status tag in the Terminal Setup dialog.
Control and status tags must be different.
From the Control or Status tab in Terminal
Setup correct the tag duplication.
Text foreground color is the same as its
background color.
Text foreground and background colors are
the same making the text invisible.
Change foreground and background colors so
they are not identical.
Text string contains character(s) from external
font file, selected font size is invalid.
Double byte external font is in use and text
contains double byte characters while an
internal font size is selected.
Specify an external font size.
The address string data type does not match
the tag data type
The tag address doesn’t match the data type
of the tag. For example, the tag address is
B3:0/2 but the tag data type is signed integer.
From the tag editor, correct the mismatch
between the tag address and the data type of
the tag.
The initial state in this device refuses operator
entry.
The initial (power-up) state for the piloted
control list does not allow operator access.
Open the object’s dialog and set the initial
state Access to “User and LC” or “User Only”.
The remote tags must be different from each
other.
Each remote tag must be unique for an alarm
setup.
Make the remote tags unique within the
application.
Time Format does not support double-byte
characters.
Double-byte font selected for Time Format.
Select a single byte size font.
Trigger and Remote Ack Tag have different
tag types.
The data type for these tags are not identical.
Change the tag data types so they are the
same.
Trigger cannot be same as the acknowledge
or handshake tags.
The trigger tag is the same as the
acknowledge or handshake tag for this
trigger.
Specify a unique tag for trigger, acknowledge
and handshake tags.
Trigger Name not Unique
Two triggers are using the same trigger tag
name.
Change trigger tag names so they are not the
same.
Trigger Tag duplication
Two triggers are using the same trigger tag
name.
Change trigger tag names so they are not the
same.
Trigger Tag same as LC Clear All Tag.
The Trigger Tag is the same as the Clear All
tag specified on the Alarm Setup screen.
Change tags so they are not identical.
Trigger’s Ack Tag same as LC Ack All Tag
The Trigger Alarm Ack Tag is the same as the
Ack All tag specified on the Alarm Setup
screen.
Change tags so they are not identical.
Trigger’s Remote Ack Tag same as LC Ack All
Tag.
The alarm trigger’s remote acknowledgment
tag is the same as the controller Ack All tag.
Change tags so they are not identical.
Unable to initialize Protocol Translation
Server. Invalid address for Block Transfer
Channel Num (number)
The address of the block transfer is invalid.
You may have entered a PLC address where
an SLC address was expected or an SLC
address where a PLC address was expected.
In the Block Transfer dialog, enter the correct
address for the specified block transfer
number.
Publication 2711-6.0
E–8
Validation Messages
Validation Message
Meaning
What to do
Unable to load (file) or one of its components
PanelBuilder cannot open specified file.
Verify that path contains AB\BIN\. Reboot
computer and try again.
Unknown graphic image
An object or object state is assigned an inner
graphic that no longer exists.
Select another inner graphic for the object or
import a bit map graphic with the same name.
Unused Block Transfer Channel will be
removed.
A block transfer defined in the Block Transfer
dialog is not used by the application.
Remove it from the application or reference it.
Unused Trigger
This alarm trigger is not being used by any
alarms and will not be downloaded to the
terminal.
Remove the trigger or use it in an alarm.
Used as indicator will display data written by a
control device using the same tag
Warning that PanelView is using data from
write tag of control object to display data for
indicator.
Nothing. Using the same write tag data for
the indicator eliminates ladder logic required
to move data from the write tag to read tag.
(Scale, Offset, Max, Min, or Initial) value of
(tag name) not valid or not in range
A tag attribute isn’t configured properly.
Open the Tag Editor from the Application
menu and change tag attributes as necessary.
Minimum array length of (tag) required for
object state data
The bit array length of the tag is smaller than
required.
Change values for the object’s states or
increase the bit array size in the Tag Editor.
Width (value) is out of range
The width of the object is invalid.
Resize the object.
Write tag not defined
A write tag has not been defined for object.
Open object’s dialog and assign a write tag.
Write and search tags must be different in
Piloted Control Lists.
A Piloted Control List will not function if the
search tag and write tag are the same.
Open the object’s dialog and change either
the write tag or search tag.
Publication 2711-6.0
Troubleshooting
This appendix contains tips to assist with troubleshooting if problems
occur when:
• Starting PanelBuilder
• Downloading to a DOS File
• Downloading using INTERCHANGE Drivers
Many computers contain power management options and utilities
that affect computer COM ports:
• POWER.EXE in AUTOEXEC.BAT or CONFIG.SYS
• option in CMOS setup
• Windows utility
• Power icon in Control Panel of Windows 95 (set to None)
For troubleshooting information on your PanelView terminal, see the
Operator Terminals manual.
Running Windows 95
Problem
Cause
Recommended Action
When rebooting your computer after installing
PanelBuilder/INTERCHANGE software, you
get a Windows protection error and your
computer locks up.
The C:\WINDOWS\SYSTEM
directory contains the files
VDF1.386 and V485.386.
Reboot the computer in Safe Mode and delete the
VDF1.386 and V485.386 files.
To enter Safe Mode, press the F5 key when the boot
message ”Starting Windows 95” appears.
Publication 2711-6.0
F–2
Troubleshooting
Starting PanelBuilder
Problem
Unable to load CMSERV.DLL or one of its
components.
Cause
Recommended Action
PanelBuilder cannot load
CMSERV.DLL or one of its
components because SHARE.EXE
is not running.
PanelBuilder finds the wrong
PXENGWIN.DLL file when
searching the DOS PATH variable
before finding the correct file in
C:\AB\BIN.
Related files left in the
C:\AB\PROJECTS directory.
Add SHARE.EXE to your AUTOEXEC.BAT file or
execute SHARE manually. See the README.TXT file in
C:\AB for more details.
The [Paradox Engine] section in
the file C:\WINDOWS\WIN.INI is
incorrect.
PanelBuilder could not initialize the
AB Utilities during startup because
SHARE.EXE is not running.
AB Utilities failed to initialize
Enter C:\AB\BIN as the first item in the PATH statement.
Do the following:
1. Exit the PanelBuilder software.
2. Delete these files from the C:\AB\PROJECTS
directory.
PARADOX.LCK
PDOXUSRS.LCK
These files are created when PanelBuilder is started and
should be deleted when the software is exited.
Check that C:\WINDOWS\WIN.INI contains these lines:
[Paradox Engine]
UserName=ISPCore
NetNamePath=C:\AB\PROJECTS
NetName=2
ShareLocal=YES
PX35Locking=NO
MaxTables=64
RecBufs=128
MaxLocks=32
MaxFiles=64
SwapSize=256
Add SHARE.EXE to your AUTOEXEC.BAT file or
execute SHARE manually. See the README.TXT file in
C:\AB for more details.
General Download Errors
Problem
Cause
Recommended Action
Application file length does not
match the header record.
When verifying the CRC of the .PVA file,
the file length did not match the length
stored in the file. This typically occurs
when you download a file that was
truncated by an aborted upload.
Specify a valid .PVA file.
Application file CRC is incorrect.
The CRC of the .PVA file does not match
the CRC stored in the file.
Specify a valid .PVA file.
In Windows NT/4.0, the following
error occurs during a download:
“Abnormal termination”.
The operating system needs to be
upgraded to Service Pack 2 (or later).
Install Service Pack 2 (or later) on your computer.
Publication 2711-6.0
Troubleshooting
F–3
Downloading to a DOS File
Problem
Cause
Recommended Action
When downloading an application to a DOS
file in PanelBuilder, you get this message:
“Unable to load WPFTDLL.DLL or one of its
components.“
INTERCHANGE is not installed on
computer. INTERCHANGE must
be installed, however, you are not
required to load INTERCHANGE
communication drivers.
Exit Windows and reinstall PanelBuilder to install
INTERCHANGE on your computer.
File(s) are missing or not found.
1. Verify that the path statement in AUTOEXEC.BAT
includes C:\RSI\IC\BIN or C:\ABIC\BIN.
2. Verify that the environment variable in
AUTOEXEC.BAT is set to
ABIC_CONFIG=C:\RSI\IC\BIN or C:\ABIC\BIN
3. Verify that WPFTDLL.DLL is in C:\AB\PBWIN.
4. Verify that DTLKTW.DLL is in C:\RSI\IC\BIN or
C:\ABIC\BIN.
Downloading with the PanelView File Transfer Utility
Problem
Cause
Recommended Action
Cannot download or upload an application
using the the PFT utility.
INTERCHANGE is running and
using the same COM port that was
specified in the PFT configuration
setup file (DEFAULT.STP).
1. Type ABICSTOP at the DOS prompt. For example:
C:\>ABICSTOP
2. Comment the following lines in the
C:\WINDOWS\SYSTEM.INI file:
[386Enh]
;Device=VDF1.386
;COM1IRQ=4
or
;COM2IRQ=3
;COM1VDF1
or
;COM2VDF1
or
[386Enh]
;Device=V485.386
;COM1IRQ=4
or
;COM2IRQ=3
;COM1VDF1
or
;COM2VDF1
Downloading Using the WINPFT Utility
Problem
Cause
Recommended Action
Unable to perform verify operation,
Incorrect Terminal Series/Revision
The File Transfer Utility (WINPFT)
cannot verify the application loaded in a
DH-485 or RS-232 terminal because the
firmware version is earlier than V1.06.
Upgrade the terminal’s firmware.
Unable to perform verify operation,
Download operation continuing...
PanelBuilder could not verify the
application loaded in a DH-485 or
RS-232 terminal before the download
(Download only if different from current
application box is checked). The
terminal’s firmware is earlier than V1.06.
The download is successful.
Upgrade the terminal’s firmware.
When downloading to an Operator
Terminal, this message appears:
“Error! Transfer Timeout!
Communication with terminal lost”
Interference from other programs in a
multitasking operating system.
Stop other programs running on the computer, especially if
running Windows 95.
Publication 2711-6.0
F–4
Troubleshooting
Downloading with INTERCHANGE
Problem
Cause
Recommended Action
When choosing the Download
command from the Application
menu, you get this message:
“Unable to load WPFTDLL.DLL or
one of its components.“
INTERCHANGE is not installed on
computer. INTERCHANGE must be
installed, however, you are not required
to load INTERCHANGE communication
drivers.
Exit Windows and reinstall PanelBuilder to install
INTERCHANGE on your computer.
File(s) are missing or not found.
1. Verify that the path statement in AUTOEXEC.BAT includes
C:\RSI\IC\BIN or C:\ABIC\BIN.
2. Verify that the environment variable in
AUTOEXEC.BAT is set to
ABIC_CONFIG=C:\RSI\IC\BIN or C:\ABIC\BIN
3. Verify that WPFTDLL.DLL is in C:\AB\PBWIN.
4. Verify that DTLKTW.DLL is in C:\RSI\IC\BIN or
C:\ABIC\BIN.
The C:\WINDOWS\SYSTEM.INI file
contains a driver conflict.
Check the C:\WINDOWS\SYSTEM.INI file. Here is a correct
example of the file.
When choosing the Download
command from the Application
menu, Operator Terminal does not
appear as a Destination option in
the Application Download dialog.
[Boot]
comm.drv=comm.drv
;not COM.DRV or DH485.DRV
or ICOMCOMM.DRV
mouse.drv=mouse.drv
[386Enh]
DEVICE=V485.386 or DEVICE=VDF1.386
COM1V485 or COM2V485 or COM1VDF1 or COM2VDF1
;DEVICE=C:\ICOM\WINLINX\VDDELINX.386
;commented out
DEVICE=*VCD
;should not be commented out
When downloading to an Operator
Terminal you get this error:
“Destination device node is not
a t ve
active”
Publication 2711-6.0
ABICRUN.BAT was not run before
starting WINDOWS.
Verify that the AUTOEXEC.BAT file contains:
CALL ABICRUN.BAT and not
REM CALL ABICRUN.BAT
Exit Windows and run ABICRUN.BAT.
In the INTERCHANGE Device Config.
utility, the station address of the PIC on
COM driver is set to the same address
as the PanelView terminal.
Using the INTERCHANGE Device Configuration Utility, set the
Station Address to 0 for the PIC on COM Port driver.
In the INTERCHANGE Device. Config.
utility, the incorrect Interrupt (IRQ) is set
for the COM Port.
Set the correct Interrupt for the COM port.
COM Port 1 requires an Interrupt (IRQ) of 4.
COM Port 2 requires an Interrupt (IRQ) of 3.
The Catalog No. 1747-PIC module is not
receiving power.
The 1747-PIC module requires 24V DC supplied by the SLC
processor or Catalog No. 1747-NP1 power supply. The
PanelView does not supply power to the PIC module.
Incorrect cabling.
Check the cable.
Troubleshooting
F–5
Problem
Cause
Recommended Action
When downloading to an Operator
Terminal you get this error:
In the INTERCHANGE Device. Config.
utility, the incorrect Interrupt (IRQ) is set
for the COM Port.
Set the correct Interrupt for the COM port.
COM Port 1 typically uses Interrupt (IRQ) of 4.
COM Port 2 typically uses Interrupt (IRQ) of 3.
In the INTERCHANGE Device. Config.
Utility, the baud rate or another driver
parameter is set incorrectly.
Set the correct baud rate or other driver parameter. To check
the PanelView terminal’s communication parameters, select
Communication Setup from the terminal’s Configuration Mode
menu.
Incorrect cabling.
Check the cable.
In the INTERCHANGE Device. Config.
Utility, parameters for the DF1 on COM
Port driver are incorrectly set.
Parameters for the DF1 on COM Port drivers must be set to:
Error Detect=CRC
Parity=None
Baud Rate=19200
INTERCHANGE Command Failure
PCCCEXT17––Timed out,
1771 backplane module not
responding
During a Remote I/O transfer,
PanelBuilder was unable to get a
response to a command. Probable
causes are: disconnected node device,
high network activity; low baud rate.
Verify that the PanelView terminal has a valid Remote I/O
network connection and that its application matches the
controller’s block transfer ladder logic. Retry the operation.
RNA: Error $C00A placing device
#n online
INTERCHANGE could not start the
driver associated with port #n of your
computer.
Use the INTERCHANGE Device Configuration Utility to check
the driver configuration. The driver may be set for a different
baud rate than the physical network.
The currently installed
INTERCHANGE driver cannot
download to the selected terminal.
The type of network transfer you are
attempting requires a different driver
than the one currently loaded on your
computer.
Configure the appropriate driver using the INTERCHANGE
Device Configuration Utility and then reboot computer.
When downloading an application
on a network using a KA5 bridge
(DH+<>DH485), the download
does not exit properly.
The download completes but does not
exit properly.
When the download is complete, select the CANCEL button on
the Download dialog.
Gateway device node is not active.
A Gateway device was not found at the
specified node address on the local
network.
Verify that a Gateway device is at the specified address or
change the node address in the File Transfer Setup dialog to
match the terminal’s network address.
Local Gateway device does not
support bridging operations or
remote network device is not an
operator terminal.
The local gateway device cannot pass
commands to another physical network
or the device on the remote network is
not an Operator Terminal.
In the File Transfer Setup dialog (page , verify that you have
entered the correct Gateway Node Address, Terminal Node
Address, and Link ID numbers.
Local network device is not an
operator terminal.
The specified device on the local
network is not an operator terminal.
Check the node address of the PanelView terminal in the File
Transfer Setup dialog.
Transfer Aborted
orted – unable
na e to send
“Transfer
commands to terminal”
When downloading to an Operator
Terminal you get this error:
“Command Failed – PCCCSTS02,
Remote station did not
acknowledge command.”
Downloading with RSLinx
Problem
Cause
Recommended Action
In Windows 95, this error occurs
during a download: “Unable to start
AB-KT–1 because duplicate nodes
were found on the network”.
The computer running the RSLinx driver
is assigned the same node address as
another computer running RSLinx on the
network.
Run RSLinx and change the node address for one of the
computers.
Publication 2711-6.0
F–6
Troubleshooting
INTERCHANGE Error/
Information Messages
This section lists and defines errors and messages that may occur
when the INTERCHANGE Software is started or stopped. These
errors are printed to the standard output when CFG_KT.EXE,
CFG_485.EXE, CFG_DF1.EXE, or RNA.EXE are executed.
Errors and Informational Messages
from CFG_KT.EXE, CFG-485.EXE and CFG_DF1.EXE
The following errors and messages are generated by CFG_KT.EXE,
CFG_485.EXE and CFG_DF1.EXE. “XXX” represents the strings
“KT”, “485”, and “DF1”. If an error/information message is only
applicable to one of CFG_KT.EXE, CFG_485.EXE or
CFG_DF1.EXE, the applicable program will appear as the first
string of the error/information message.
These messages occur normally at startup. They indicate the
location where the INTERCHANGE Software was installed.
CFG_XXX (0000) TSR configured, no errors detected
CFG_XXX (001A) Reading device configuration from C:\RSI\IC\BIN\CFG_KT.INI
CFG_XXX (001B) Reading diagnostic and protocol files from C:\RSI\IC\BIN
This message occurs normally at shutdown.
CFG_XXX (0001) TSR terminated, no longer resident in memory.
This message indicates an invalid version of DOS is loaded. Consult
the INTERCHANGE User Manual for valid and compatible versions
of DOS.
CFG_XXX (0002) TSR not ready, invalid version of DOS
Binary files downloaded to your communication card are
incompatible with the INTERCHANGE Software installed on your
system. Re-install the INTERCHANGE Software.
CFG_XXX (0003) TSR not configured, invalid version of KT protocol file
The indicated file could not be found. Check to ensure that the path
and/or file exist.
CFG_XXX (0004) TSR not configured, error opening file <filename>
The indicated file was found but could not be read. Check the
permissions on the file.
CFG_XXX (0005) TSR not configured, error reading file <filename>
Publication 2711-6.0
Troubleshooting
F–7
The indicated command or parameter in CFG_KT.INI is invalid.
Correct your CFG_KT.INI file and restart the INTERCHANGE
Software.
CFG_XXX (0007) TSR not configured, invalid line; <command>
CFG_XXX (0008) TSR not configured, invalid parameter; <parameter>
CFG_XXX (0009) TSR not configured, invalid ‘memory’ parameter <parameter>
CFG_XXX (000a) TSR not configured, invalid ‘interrupt’ parameter <parameter>
Not enough memory was available to configure the DTL_KT TSR.
Obtain more free memory on your computer and restart the
INTERCHANGE Software.
CFG_KT (000b) TSR not configured, unable to allocate memory
An error occurred when configuring the DTL_XXX TSR. The
DTL_XXX TSR may already be running. Shut down and restart the
INTERCHANGE Software to correct the problem.
CFG_XXX (000c) TSR not configured, ‘TSR’ parameter already in use
CFG_XXX (000d) TSR not configured, no KT(s) could be initialized
Commonly caused by one of the following:
1. no communication cards are specified in CFG_KT.INI.
2. the software or hardware setting of the memory address for your
communication card does not match that entered in the
CFG_KT.INI file.
3. the environment variable ABIC_CONFIG, points to a location
which has an invalid or nonexistent CFG_KT.INI file.
The executable CFG_XXX.EXE has previously been run to
configure the DTL_XXX TSR. It is not necessary to run
CFG_XXX.EXE again, however, it has caused no harm to do so.
CFG_XXX (000e) TSR already configured, no action taken
Your installation may have been unsuccessful. Re-install the
INTERCHANGE Software and restart the INTERCHANGE
Software. If this error still occurs, contact your Rockwell Software
Inc. Global Technical Support Representative.
CFG_XXX (000f) TSR version is incompatible with this executable
CFG_XXX (0010) TSR not found, must first be resident to be configured
Caused by one of the following:
Publication 2711-6.0
F–8
Troubleshooting
1. DTL_XXX TSR could not be de-installed. Issue the uninstall
command again (CFG_XXX -u).
2. An attempt was made to uninstall the DTL_XXX driver
(CFG_XXX -u) when it was not installed.
The DTL_XXX TSR could not be de-installed. Issue the uninstall
command again (CFG_XXX -u).
CFG_XXX (0011) TSR still running, unable to deinstall
The 1784-KT2 communication card must have its memory and
interrupt software configured before INTERCHANGE Software is
run. Make sure you have configured your 1784-KT2 for a memory
address and that this memory address matches that entered in the
CFG_KT.INI file.
CFG_XXX (0012) KT not found at specified ‘memory’ (KT2 only)
These errors occur during communication card diagnostics. The
execution of these diagnostics is controlled by the statement
SELFTEST=OFF in CFG_KT.INI. If this line is commented out, the
diagnostics are run by default. If this line is uncommented and says
SELFTEST=ON, the diagnostics are run. To stop the diagnostics
from running, ensure that this line is not commented out and says
SELFTEST=OFF. The most common cause for these errors is that
the software or hardware setting of the memory address for your
communication card does not match that entered into CFG_KT.INI
for the type of card you are using.
CFG_KT (0013) KT memory diagnostic RAM 0 error
CFG_KT (0014) KT memory diagnostic RAM 1 error
CFG_KT (0015) KT counter diagnostic error
CFG_KT (0016) KT timer diagnostic error
CFG_KT (0017) KT serial diagnostic error
CFG_KT (0018) KT protocol downloading error
CFG_KT (0019) KT dualport memory error
If these errors occur, contact your Rockwell Software Inc. Global
Technical Support Representative.
CFG_KT (001d) Undefined error
CFG_KT (001e) Undefined error
CFG_KT (001f) Undefined error
Publication 2711-6.0
Troubleshooting
F–9
Errors and Informational Messages Specific to CFG_485.EXE
This error indicates the Virtual Driver for DH485 isn’t running.
CFG_485 (0020) DH485 Fatal Error; V485 Driver not installed.
These errors indicate problems setting up the COM port.
CFG_485 (0021) DH485 Serial Communication Port not found.
CFG_485 (0022) DH485 Link Layer attach error.
CFG_485 (0023) DH485 Link Layer initialization error.
CFG_485 (0024) DH485 Link Layer configuration error.
This error indicates a conflict over which COM port is to be used.
CFG_485 (0025) DH485 CFG_KT.INI and SYSTEM.INI comm port inconsistency.
This error indicates that the driver did not exit cleanly.
CFG_485 (0026) DH485 Fatal Error during Link Layer Cleanup.
Errors and Informational Messages Specific to CFG_DF1.EXE
This error indicates the Virtual Driver for DF1 isn’t running.
CFG_DF1 (0020) DF1 Fatal Error; VDF1 Driver not installed.
These errors indicate problems setting up the COM port.
CFG_DF1 (0021) DF1 Serial Communication Port not found.
CFG_DF1 (0022) DF1 Link Layer attach error.
CFG_DF1 (0023) DF1 Link Layer initialization error.
CFG_DF1 (0024) DF1 Link Layer configuration error.
This error indicates a conflict over which COM port is to be used.
CFG_DF1 (0025) DF1 CFG_KT.INI and SYSTEM.INI comm port inconsistency.
This error indicates that the driver did not exit cleanly.
CFG_DF1 (0026) DF1 Fatal Error during Link Layer Cleanup.
Publication 2711-6.0
F–10
Troubleshooting
Errors and Informational Messages from RNA.EXE
This message occurs normally at shutdown.
RNA removed from memory.
This parameter for the -b argument (indicating number of solicited
message buffers to use) given on the command line for RNA.EXE
was out of allowed message range of 1 to 40. A default of 20
solicited buffers will be used.
RNA: -b must be 1-40, using default of 20
The format of the options given on the command line for RNA.EXE
were invalid. Correct the option(s) and start RNA.EXE again.
RNA: illegal option –– <option>
RNA: invalid option
RNA: invalid option (option); must begin with ‘–’
RNA: option requires an argument –– <option>
The number of packet buffers, <num> requested on the command
line cannot be created. If your buffers were loaded into upper DOS
memory (the default), your upper DOS memory may be full.
Specify -e0 on the RNA.EXE command line to force the buffers to
use low DOS memory.
RNA: ERROR – cannot create <num> packet buffers
The number of unsolicited buffers, <num>, requested on the
command line cannot be created. If your buffers were loaded into
upper DOS memory (by no additional command line options), it may
be full. Specify -e0 on the RNA.EXE command line to force the
buffers to use low DOS memory.
RNA: ERROR – cannot create <num> unsolicited data items.
The RNATSR was loaded from DOS. It cannot be uninstalled with
Windows running. Exit to DOS to uninstall the RNATSR.
RNA: RNATSR loaded before Windows, cannot uninstall from Windows
Other TSRs have been installed after the RNATSR. They must be
removed from memory before the RNATSR can be uninstalled.
RNA: Cannot uninstall RNATSR; not at end of INT 2F chain
The RNATSR must be installed before running RNA.EXE.
RNA: RNATSR is not installed.
Publication 2711-6.0
Troubleshooting
F–11
You must run and install the card driver (DTL_KT.EXE and
CFG_KT.EXE) before running the RNATSR and RNA.
RNA: ERROR –– no card drivers installed
RNA.EXE has already been run.
RNA: ERROR –– RNATSR <version> is already running
Your installation may have been unsuccessful. Re-install and restart
the INTERCHANGE Software. If this error still occurs, contact
your Rockwell Software Inc. Global Technical Support
Representative.
RNA: ERROR –– wrong version of KT driver
If either of these errors occur, call your Rockwell Software Inc.
Global Technical Support Representative.
RNA: Internal error. KTTSR_ATTACH returns <num1> instead of <num2>
RNA: Internal error – no driver has port <num>
These errors can occur if there was difficulty creating the packet
buffers or unsolicited table at startup. If that is the case, an error was
displayed at startup as well.
RNA: Error %X freeing the packet buffers
RNA: Error % freeing the unsolicited table
RNA: WARNING – no ports available on driver #x
Publication 2711-6.0
Internal Read Only Tags
This appendix lists internal tags of PanelBuilder. These tags can be
used for objects that read tag addresses such as an indicator.
General Tags
Tag Name
Data Type
Value Range
Description
0 to 114623 (PV550)
0 to 245695 (PV600)
0 to 245695 (PV900M)
Series D or earlier
0 to 1032128 (PV900M)
Bytes
Series E or later
0 to 1032128 (PV900C)
0 to 1032128
(PV1000G/PV1000C)
0 to 1032128 (PV1400)
0 to 1032128
Bytes
@Read_AppByteFree
Unsigned Integer
@Read_AppByteUsed
Unsigned Integer
@Read_Backlight
Unsigned Integer
0 or 1
@Read_ClockDate
Unsigned Integer
1 to 31
@Read_ClockHours
Unsigned Integer
0 to 23
@Read_ClockMinutes
Unsigned Integer
0 to 59
@Read_ClockMonth
Unsigned Integer
1 to 12
@Read_ClockSeconds
Unsigned Integer
0 to 59
@Read_ClockYear
Unsigned Integer
0 to 99
@Read_CommStatus
Unsigned Integer
1 or 2
@Read_CurrentLang
Unsigned Integer
0 to 4
@Read_FaultStatus
Unsigned Integer
0, 1 or 2
@Read_KeyRepeatDelay
Unsigned Integer
0 to 7
@Read_KeyRepeatRate
Unsigned Integer
0 to 5
0 = No repeat (default), 1 = Every second,
2 = Every 1/2 second, 3 = Every 1/3 second,
4 = Every 1/4 second, 5 = Every 1/5 second
@Read_MemCardStatus
Unsigned Integer
0 to 3
0 = Valid memory card format
1 = Incorrect memory card format
2 = No memory card installed
3 = No applications on memory card
0 = Off , 1 = On
0 to 89 (2000 to 2089)
90 to 99 (1990 to 1999)
1 = Comm is connected
2 = Comm is disconnected
0 = French, 1 = German, 2 = Italian
3 = Spanish, 4 = English (Default)
0 = Normal, 1 = Unable to run
2 = Functions but unable to run application
0 = 200ms, 1 = 400ms (Default), 2 = 600ms,
3 = 800ms, 4 = 1000ms, 5 = 1500ms,
6 = 2000ms, 7 = 2500ms
PV550 Tags
Tag Name
Data Type
Value Range
@Read_LCDContrast
Unsigned Integer
0 to 15
@Read_LCDRevVideo
Unsigned Integer
0 or 1
Description
0 = White displays on black background
1 = Black displays on white background
Publication 2711-6.0
G–2
Internal Read Only Tags
PV900M/1000G Tags
Data Type
Value Range
Description
@Read_DisplayOnTime
Tag Name
Unsigned Integer
0 to 65535
Minutes the terminal display has been running
@Read_LCDIntensity
Unsigned Integer
1 to 100
@Read_LCDRevVideo
Unsigned Integer
0 or 1
@Read_ScrnCond_Hour
Unsigned Integer
0 to 23
@Read_ScrnCond_Min
Unsigned Integer
0 to 59
@Read_ScrnCond_Mode
Unsigned Integer
0 to 1
@Read_ScrnSave_Intensity
Unsigned Integer
0 to 100
@Read_ScrnSave_Mode
Unsigned Integer
0 to 2
@Read_ScrnSave_Time
Unsigned Integer
1 to 1800
Screen save timeout in seconds.
@Read_TermOnTime
Unsigned Integer
0 to 65535
Minutes the terminal CPU has been running.
900M only: 1=35%, 9=40%, 24=50%,
39=60%, 54=70%, 70=80%, 85=90%,
100=100%
0 = White displays on black background
1 = Black displays on white background
Combined with @Read_ScrnCond_Min to determine the time of day to start conditioner.
Combined with @Read_ScrnCond_Hour to
determine the time of day to start conditioner.
0=Disabled, 1=Enabled
900M only: 0=0%, 1=35%, 9=40%, 24=50%,
39=60%, 54=70%, 70=80%, 85=90%,
100=100%
0=Off, 1=On, 2=Timed
PV600C/900C/1000C Tags
Data Type
Value Range
Description
@Read_DisplayOnTime
Tag Name
Unsigned Integer
0 to 65535
Minutes the terminal display has been running
@Read_LCDIntensity
Unsigned Integer
10 to 100
@Read_ScrnCond_Hour
Unsigned Integer
0 to 23
Percent of display intensity (900C range is
50–100%)
Not used
@Read_ScrnCond_Min
Unsigned Integer
0 to 59
Not used
@Read_ScrnCond_Mode
Unsigned Integer
0 to 1
Not used
@Read_ScrnSave_Intensity
Unsigned Integer
0 to 100
@Read_ScrnSave_Mode
Unsigned Integer
0 to 2
@Read_ScrnSave_Time
Unsigned Integer
1 to 1800
Screen save timeout in seconds.
@Read_TermOnTime
Unsigned Integer
0 to 65535
Minutes the terminal CPU has been running.
Percent of display intensity
0=Off, 1=On, 2=Timed
PV1400 Tags
Data Type
Value Range
Description
@Read_DisplayOnTime
Tag Name
Unsigned Integer
0 to 65535
Minutes the terminal display has been running
@Read_LCDIntensity
Unsigned Integer
25 to 100
Percent of display intensity
@Read_Degauss_Hour
Unsigned Integer
0 to 23
@Read_Degauss_Min
Unsigned Integer
0 to 59
@Read_Degauss_Mode
Unsigned Integer
0 to 1
@Read_ScrnSave_Intensity
Unsigned Integer
0 to 100
@Read_ScrnSave_Mode
Unsigned Integer
0 to 2
@Read_ScrnSave_Time
Unsigned Integer
1 to 1800
Screen save timeout in seconds.
@Read_TermOnTime
Unsigned Integer
0 to 65535
Minutes the terminal CPU has been running.
Publication 2711-6.0
Combined with @Read_Degauss_Min to determine time of day to start conditioner.
Combined with @Read_Degauss_Hour to determine the time of day to start conditioner.
0=Disabled, 1=Enabled
Percent of display intensity
0=Off, 1=On, 2=Timed
Internal Read Only Tags
G–3
DH-485 Tags
Data Type
Value Range
@Read_BaudRate
Tag Name
Unsigned Integer
1 to 4
@Read_MaxNodeAddress
Unsigned Integer
1 to 31
@Read_MemCardStatus
Unsigned Integer
0 to 3
@Read_NodeAddress
Unsigned Integer
0 to 31
@Read_SerCommStatus
Unsigned Integer
0 to 5
Description
1 = 1200, 2 = 2400, 3 = 9600, 4 = 19200
0 = Valid memory card format
1 = Incorrect memory card format
2 = No memory card installed
3 = No applications on memory card
0 = Communication link is ok
1 = PanelView terminal is off the link
2 = Scanned node not found
4 = I/O error (Invalid I/O form controller)
5 = Duplicate node address
Remote I/O Tags
Remote I/O Tag Name
Data Type
Value Range
Description
@SRIO_RackNumber
Unsigned Integer
0 to 62
@SRIO_RackSize
Unsigned Integer
0 to 3
0 = 1/4
1 = 1/2
2 = 3/4
3 = Full
@SRIO_DataRate
Unsigned Integer
0 to 2
0 = 57.6K
1 = 115.2K
2 = 230.4K
@SRIO_Module
Unsigned Integer
0 to 3
0 = Module Group 0,1
1 = Module Group 2,3
2 = Module Group 4,5
3 = Module Group 6,7
@SRIO_LastRack
Unsigned Integer
0 or 1
0 = False
1 = True
@SRIO_BlockTransferReadEnable
Unsigned Integer
0 or 1
0 = Disable
1 = Enable
@SRIO_BlockTransferWriteEnable
Unsigned Integer
0 or 1
0 = Disable
1 = Enable
@SRIO_BlockTransferTimeout
Unsigned Integer
0 to 65535
@SRIO_PassThruEnabled
Unsigned Integer
0 or 1
@Read_SerCommStatus
Unsigned Integer
1 to 128
0 = No Timeout
1 to 65535 (in milliseconds)
0 = Disable
1 = Enable
1 =Communications active
2 =Timeout in block transfer write from PLC
4 =Timeout in block transfer read
8 =Timeout in both block transfer write and block transfer read
16 =PLC offline
17 =Pass-Through occurring
32 =Communication with PLC failed
64 =Bad rack setup
128= PanelView RIO hardware failed startup tests failed
Publication 2711-6.0
G–4
Internal Read Only Tags
ControlNet Tags
You can display the Network Update Time (NUT), UMAX Node,
SMAX Node and other data on a screen by assigning one of the
following read only tags to a display objet. You must use an ASCII
display for tags with a string data type.
Tag Name
Data Type
Description
@Read_DCNUTime
Unsigned Integer
Network Update Time (NUT) in milliseconds.
@Read_DCUMAX
Unsigned Integer
Unscheduled Maximum (UMAX) node address
@Read_DCSMAX
Unsigned Integer
Scheduled Maximum (SMAX) node address
@Read_curDCAddress
Unsigned Integer
Current Node Address
@Read_DCASANumber
String
CIP/ASA serial number of the PanelView
@Read_DCCommStatus
Unsigned Integer
Communication status number
@Read_DCFirmwareRev
String
ControlNet firmware revision number
@Read_DCNewAddress
Unsigned Integer
Terminal address to use after a reset
@Read_DCProtocol
String
Firmware build date
@Read_DCRedundancy
Unsigned Integer
LED status number. Indicates status of A and B cables.
@Read_DCScanDelay
Unsigned Integer
Scan delay in milliseconds (time between reads)
DeviceNet Tags
Tag Name
@Read_DCB01
Data Type
Value Range
Unsigned Integer
Description
0 or 1
0 = Hold in Reset, 1 = Reset and Continue Comms.
@Read_DCCommStatus
Unsigned Integer
0 to 13
0 = No connection
1 = Connection timed out.
3 = Cannot obtain Explicit–Client tag
4 = Zero length I/O message received
5 = Message overrun
11 = No network power
12 = Dup MAC failure
13 = Bus–Off interrupt occurred
@Read_DCInputSize
Unsigned Integer
0 to 64
Number of words sent to scanner from PanelView with
each I/O scan.
@Read_DCOutputSize
Unsigned Integer
0 to 64
Number of words sent to PanelView from scanner with
each I/O scan.
@Read_DCScanDelay
Unsigned Integer
0 to 65535
Delay scan of the Explicit-Client tags
@Read_DCAddress
Unsigned Integer
0 to 63
Address of PanelView on DeviceNet link.
@Read_DCBaudRate
Unsigned Integer
0 to 2
0 =125 Kbps, 1 = 255 Kbps, 2 = 500 Kbps
DF1 Tags
Tag Name
Data Type
Value Range
Description
@Read_DFX_ErrorDetectOption
Unsigned Integer
0 or 1
0 = BCC, 1 = CRC
@Read_DFX_HandshakeOption
Unsigned Integer
0 or 1
0 = Off, 1 = On
@Read_DFX_Parity
Unsigned Integer
0 to 2
0 = None, 1 = Even, 2 = Odd
@Read_DFX_PortMode
Unsigned Integer
0–3
0 = N-8-1, 1 = E-8-1, 2 = O-8-1, 3 = N-8-2
@Read_DFX_StopBits
Unsigned Integer
0, 2
0 = 1 Stop Bit, 2 = 2 Stop Bits
@Read_BaudRate
Unsigned Integer
2 to 6
2 = 1200, 3 = 2400, 4 = 4800,
5 = 9600, 6 = 19200
@Read_SerCommStatus
Unsigned Integer
0 to 2
0 = Connected, 1 = Offline, 2 = Hardware Failure
@Read_DFX_NodeAddress
Unsigned Integer
0 to 253
0 to 253
Publication 2711-6.0
Using ASCII Characters
This appendix contains the ASCII Character Set and the Extended
ASCII Character set. You can access extended ASCII characters:
• directly within PanelBuilder
• using the Windows Character Map Utility
Fields not downloaded with an application such as tag name, screen
name, and screen descriptions use the Windows character set not the
extended character set in this appendix.
To access extended ASCII characters within PanelBuilder:
1. Select an object.
2. Enter inner text mode.
3. Hold down the ALT key and enter the 4-digit decimal equivalent
of the extended character using the numeric keypad.
You’ll find the decimal equivalents of the extended ASCII
characters on the next page. Because Windows requires you to
enter 4 digits, add a 0 to the beginning of each number.
4. When you release the ALT key, the extended character appears in
the text box.
For example, to enter the character equivalent to decimal 235,
hold down the ALT key and enter 0235 on the numeric keypad.
Extended character equivalent of decimal 0235
To access extended characters using the Character Map utility:
1. Select and copy characters to the clipboard from the Windows
Character Map dialog.
Select a PanelView Font
2. From your PanelBuilder application, select an object.
3. Enter inner text mode.
4. Use the Paste command or Paste tool to paste the characters from
the clipboard into the text box.
Publication 2711-6.0
H–2
Using ASCII Characters
ASCII Character Set
Publication 2711-6.0
Using ASCII Characters
H–3
Extended ASCII Character Set
Publication 2711-6.0
Glossary
active – The window (application file or screen) or object that is
currently selected. Only one window can be active at a time. If a
window is active, its title bar is highlighted to differentiate it from
other windows. If an object is active, it has handles. Windows or
objects that are not selected are inactive.
application – In the context of PanelBuilder, an application is a
logical arrangement of screens which replace the functions of a
control panel of buttons, switches and indicators. The application
runs in a PanelView terminal.
application file – File containing configuration information for the
PanelView terminal. Files exist as either a PanelBuilder application
(.PBA file type) or a PanelView application (.PVA file type). Files
transferred to a terminal are in a .PVA format. Files within
PanelBuilder are in a .PBA format.
application file window – The window containing a list of all
application screens in a PanelBuilder application file.
application screen window – The window that looks like a
PanelView terminal on which control panel objects are placed. An
application contains a logical arrangement of screens.
ATA card – Advanced Technology Attachment (ATA), Intelligent
Drive Electronics (IDE), PC Cards (formerly PCMCIA) combine the
drive controller and memory storage device. ATA cards can be
accessed with standard Copy or Delete commands on a personal
computer. The card looks like a hard drive to the user. You can use
the card on a variety of computers without any special setup.
attributes – In the context of PanelBuilder, information that
describes how an object will interact with the controller and how it
appears on the PanelView terminal.
auto repeat – A function where a button press/release is
automatically repeated when the button is held down for more than
1/ second.
2
background text – Screen text that is unattached or not linked to an
object.
baud – A rate at which a transmission occurs. One baud equals one
bit per second.
Publication 2711-6.0
Glossary–2
bit – The smallest unit of information in the binary numbering
system. A bit is represented by the digits 0 and 1.
bitmap – An image stored as a pattern of dots (or pixels).
byte – A sequence of 8 consecutive bits that are treated as a single
value.
cascade – A way of arranging opens windows (application file and
screens) in the workspace so that they overlap each other, with the
title bar of each visible.
choose – To use a mouse or keyboard to pick an item that begins an
action in PanelBuilder. You choose commands on the menus or tools
to perform tasks.
click – To press and release the mouse button quickly.
color palette – A fixed set of the 16 standard EGA colors which are
used to apply color to the foreground and background of objects, text
and graphics.
command – A menu item that you choose to carry out an action.
You choose a command from a menu or click a tool on one of the
tool bars.
command button – A button that carries out an action in a dialog
box. A command button has a label that describes the action to carry
out (Close, Cancel). Choosing a command button followed by
ellipsis (Options...) opens another dialog.
control panel – 1) A panel which may contain instruments or
user-operated switches. 2) In the PanelView terminal, objects that
allow an operator to access and control plant operations through
manipulation of the controller data table.
controller, programmable – Refer to programmable controller.
copy – To put a copy of the selected object or screen onto the
Clipboard so that you can transfer it to another location.
cut – To move the selected object or screen onto the Clipboard.
DF1 – A peer-to-peer protocol that combines features of ANSI
X3.28-1976 specification subcategories D1 (data transparency) and
F1 (two-way simultaneous transmission with embedded responses).
DH485 – Allen-Bradley network protocol for RS-485
communications.
Publication 2711-6.0
Glossary–3
DH+t link – Data Highway Plust link. An Allen-Bradley
token-passing baseband link for a local area network.
dialog – A window that opens temporarily to request information.
Dialogs have options you must choose before PanelBuilder can carry
out a command.
dimmed – Unavailable or disabled. A dimmed button or command
is displayed in light gray instead of black, and it cannot be chosen.
double-click – To rapidly press and release a mouse button twice
without moving the mouse. Double-clicking carries out an action
like opening a dialog box.
download – The process of transferring an application from the
computer running PanelBuilder to a PanelView terminal, PC
memory card or DOS file.
drag – To move an item on the screen by selecting the item and then
pressing and holding down the mouse button while moving the
mouse.
dynamic object – An object that interacts with a controller address.
format bar – A horizontal bar that appears below the tool bar. The
format bar contains tools for formatting objects and text. Commands
on the format menu carry out the same action as the tools on the
format bar.
function keys – A set of keys (labeled F1–F10, F1–F16 or F1-F21)
on the PanelView terminals that are used to initiate a function.
import – To bring a bitmap graphic into PanelBuilder from another
package.
inner text – Text that appears inside an object that’s linked to the
object. When an object is moved or deleted so is the inner text.
ISA– Refers to Instrumentation Society of America.
keypad – 18 keys on the PanelView terminal used to enter data.
memory card – A storage medium similar to a PC memory card
which can store a PanelBuilder application.
menu – A list of available commands in the PanelBuilder
application. Menu names appear in the menu bar at the top of the
window.
menu bar – The horizontal bar containing the names of
PanelBuilder menus. It appears below the title bar.
Publication 2711-6.0
Glossary–4
node –. A device on a DH485 network which has a unique address
(0 to 31)
node address – A unique value (0 to 31) assigned to each device on
a DH485 network. Addressing allows communications between
devices. All data transfers are assigned a destination address.
object – In the context of PanelBuilder, an individual component of
an application screen. Each object replaces the function of a button,
switch or indicator on a control panel. Objects include controls,
displays and graphics.
object attributes – See attributes.
PanelBuilder Software – A Microsoft Windows based program
used to develop an application to run in a PanelView terminal.
PanelView Terminal – An Allen-Bradley keypad, touch screen, or
touch screen and keypad terminal which runs a PanelBuilder
application. The terminal provides the operator interface to the logic
controller when the application is executing.
Pass-Through – Means of transferring data between a computer on
the DH+ network and a PanelView terminal on the Remote I/O
network. A PLC-5 controller acts as a bridge between the two
networks.
paste – To copy the contents of the Clipboard.
PC – Personal Computer memory card.
PLC – Acronym for Programmable Logic Controller, an
Allen-Bradley trademark.
point– To move the pointer on a screen until it rests on the item you
want to select.
pointer – The arrow-shaped cursor on the screen that follows the
movement of the mouse and indicates which area of the screen will
be affected when you press the mouse button. The pointer changes
shape during certain tasks. Also known as mouse pointer.
preset value – A value loaded into a controller data table when an
application is first started.
project – A database of tag definitions and device information
associated with an application.
Publication 2711-6.0
Glossary–5
programmable controller – A device used to replace relay logic
used for sequencing, timing, and counting. Instead of physical
wiring devices such as relays, push buttons and limit switches, a
programmable controller tests the state of inputs and sets outputs
according to stored programs.
remote I/O link – A serial link for carrying I/O data between a PLC
or SLC processor/scanner and remote I/O adapters. Also supports
transfer the block transfer of data that is moved using block transfer
ladder instructions.
save – The process of transferring data stored in memory to a disk
file.
scratchpad – Data entry window that opens when numeric entry
objects are activated.
screen – See application screen or touch screen.
select – To mark an item so that a subsequent action can be carried
out. You usually select an item by clicking it with a mouse or
pressing a key. After selecting an item, you choose the action that
you want to affect the item. See choose.
SLC – Allen-Bradley trademark for Small Logic Controllers.
static object – An object that doesn’t interact with a controller
address.
status bar – The horizontal bar at the bottom of the window that
tells you what PanelBuilder is doing at the moment.
tag – A group of parameters that define a controller address within a
processor and how it interacts with a PanelBuilder object.
tile – A way of arranging open windows (application file window or
application screens) so that no windows overlap but all are visible.
Each window takes up a portion of a screen.
tool bar – The horizontal bar that appears below the title bar. The
tool bar contains tools for frequently used commands. You click on
a tool to carry out an action. Some tools complete the action
immediately; others place you in a mode to complete the action.
touch cell – One of 128 or 384 rectangular areas on the display of a
PanelView terminal that can sense when touched. The PanelView
550/600 has 128 touch cells; the 900/1400 has 384 touch cells.
touch screen – A screen with touch cells that respond when touched.
Publication 2711-6.0
Glossary–6
upload – The process of transferring an application from a
PanelView terminal or memory card to the computer running
PanelBuilder.
validate – The process of checking an application for warnings and
errors. Applications that are validated successfully can be
downloaded.
verify – The process the PanelView uses to check an application for
errors.
workspace – The area of the window that displays the information
contained in the PanelBuilder application.
zoom – Enlarging or reducing the view of the screen so that objects
look larger or smaller than their actual size. Changing the view
affects the appearance of objects, not their actual size.
Publication 2711-6.0
A
Addressing, 3–12
Alarms
Clear Button , 1–7
Alarms
Acknowledge, 1–7, 15–3
Acknowledge All Alarms, 15–27
Acknowledge All Handshake Tags, 15–27
Acknowledge All Value, 15–23
Acknowledge Tag, 15–23
Adding Variable Data, 15–21
Alarm List, 1–7, 15–4, 15–9
Alarm List Examples, 15–5
Banner, 15–2, 15–6
Banner Position, 15–8
Buttons, 15–3
Clear Alarm, 1–7, 15–3
Clear Alarm List, 1–7, 15–3
Clear All Alarms Tag, 15–27
Clear All Handshake Tags, 15–27
Clearing Banner, 15–2
Creating, 15–16
Defining Triggers, 15–14
Examples, 15–28, 15–29, 15–30, 15–31, 15–32
Fields, 15–17
Global Acknowledge, 15–3
Global Parameters, 15–12
Handshake Tag, 15–23
Message Display, 15–7
Optional Tags, 15–22
Overview, 1–3, 15–1
Print, 1–7, 15–3
Print Alarm List, 1–7, 15–3
Remote Acknowledge Tag, 15–23
Remote Handshake Tag, 15–23
Remote Tags, 15–26
Trigger, 15–15
Using Existing Text, 15–20
Align Menu, Commands, A–4
Align Text Tools, B–3
Aligning Objects
Screen Grid
Resizing Grid, 7–6
Snapping Objects to Grid, 7–6
Touch Grid, 7–5
Application
Application Name, 6–3
Changing Application Name, 6–8
Changing Protocols, 7–22
Closing, 6–21
Converting, 20–15
Converting Between Color and Grayscale, 6–18, 20–15
Converting Between Color and Monochrome, 6–18
Copying Color to Grayscale, 7–22
Copying Color to Monochrome, 7–21
Copying Monochrome to Grayscale, 7–21
Copying Touch Screen to Keypad, 7–22
Creating New, 6–3
Description, 1–1, 6–9
File Icon, 5–3
File Window, 5–3
Moving to Another Computer, 21–7
Multilingual, 22–1
Opening Existing, 6–5
Planning, 3–1– 3–14, 4–1– 4–14
Project Name, 6–3
Reducing Size of, 23–28
Renaming, 6–8
Reports, 24–1
Saving, 6–20
Screen Icon, 5–3
Screen Window, 5–3
Terminal Type, 6–3
Text, 18–2
Typical Screens, 1–5
Validating, 23–2
Version Information, 6–8
Application File Transfer Utility
Downloading Application, 23–25
Uploading an Application, 23–27
Verifying an Application, 23–24
WINPFT, 23–23
Application Menu, Commands, A–5
ASCII Chart, Extended Characters, H–1
ASCII Entry
Creating Keypad Enable, 10–16
Cursor Point, 10–12
Dialog, 10–17
Display Tag, 10–18
Input, 10–17
Mask Characters, 10–18
Notification and Handshake Tags, 10–18
Scratchpad for 550 Touch Terminals, 10–14
Scratchpad for Keypad Terminals, 10–13
Scratchpad for Touch Terminals, 10–15
Scratchpad in other Languages, 10–16
Show Current String, 10–18
String Width, 10–18
Write Tag, 10–18
ASCII Variable, 7–17, 17–16, 18–5
Attributes
ASCII Entry, 10–17
Bar Graphs, 12–5
Control List, 9–6
Editing, 7–14
Latched Push Button, 8–4
List Indicator, 12–20
List Keys, 9–12, 11–9
Maintained Push Button, 8–4
Publication 2711–6.0
Index–2
Attributes
Message Display, 13–6
Momentary Push Button, 8–4
Multistate Indicator, 12–14
Multistate Push Button, 8–4
Numeric Data Display, 12–10
Numeric Entry, 10–7
Scale, 12–7
Screen List Selector, 11–6
Viewing, 7–14
Audience, Intended, P–1
Auto Repeat Settings, 20–21
B
Background Objects
Graphics, 16–16
ISA Symbols, 16–7
Text, 1–7, 16–8
Backlight, Terminal Setup, 20–22
Backspace List Key, 9–12, 11–9
Banner, Alarms, 15–2, 15–6
Bar Graphs
Attributes, 12–5, 12–7
this is how level2 wraps around to the following line, 7–5
Creating, 12–5
Data Ranges, 12–6
Description, 1–6
Dialog, 12–5, 12–7
Error State, 12–3
Examples, 12–4
Fill Direction, 12–6
Read Tag, 12–6
Scale, 12–7
Scaling, 12–2
Tick–Mark Labels, 12–8
Bit Array, 3–11
Bitmaps
Color, 16–10
Editing, 16–10, 17–23
Exporting, 16–10, 16–14
Importing, 16–10, 16–12
Maximum Size, 16–10
Length, 4–12
Multiple Block Transfers, 4–15
Piloted Control List Block Write Tag, 9–8
Read, 4–12, 4–13, 20–11
Setting Up, 4–12
Starting Address, 4–12
Write, 4–12, 4–14, 20–11
Bring Dynamic Objects to Front, 7–11
C
Character Array, 3–11
Color
Adding to Background Text, 16–9
Background, 5–8
Bitmaps, 16–10
Converting Color to Grayscale, 6–19, 20–15
Converting Color to Monochrome, 6–19
Converting Monochrome to Color, 20–15
Foreground, 5–8
Palette, 1–3
Setting Defaults, 7–13
Setting Foreground/Background, 17–8
Setting Graphic Foreground/Background, 17–21
Text, 17–29
Using Palette, 5–8
Command Conventions, 5–4
Check Mark, 5–4
Choosing, 5–4
Dimmed Command, 5–4
Ellipsis (...), 5–4
Triangle, 5–4
Using Key Combination, 5–4
Communications
Adding a Card, 2–17
Block Transfers, 4–11
DF1, 4–4
DH+, 4–3
DH–485, 4–2
Discrete I/O, 4–9
Remote I/O, 4–6
Terminal Ports, 4–1
Transferring Multiple Blocks, 4–15
Blinking
for Objects, 17–7
for Text, 17–28
Contact Types, 8–2
Block Transfers
Control List Block Write Tag, 9–3
Controllers Supporting, 4–7
Defining, 4–12, 20–11
Enabling or Disabling, 4–12
Example, 4–11
for Communicating Data, 20–11
for Pass–Through, 20–11
Helpful Hints, 4–13
Control List
Attributes, 9–6
Configuring States, 7–15
Creating, 9–5
Data Types, 9–7
Description, 1–6
Dialog, 9–6
Helpful Hints, 9–1
Illustrating, 9–4
Publication 2711–6.0
Contents, of Manual, P–2
Index–3
Inactive State, 9–3
Initial State, 9–6
List Keys, 9–12
Piloted Control List, 9–2
Piloted Control Tag, 9–8
Search Tag, 9–8
Setting Number of Entries, 9–10
Standard Control List, 9–2
Using Enter Key to Confirm Selection, 9–9
Using Multiple Lists, 9–5
Using Wrap Around, 9–9
Write Tag, 9–7
Control Tags
PLC/SLC Screen Changes, 20–24– 20–28
PLC/SLC Time or Date Changes, 20–24– 20–28
Control–Menu Box, 5–2
Controllers, Data File Access, 3–7
Conventions, P–3
Copying
Color to Monochrome, 7–21
Monochrome to Color, 7–21
Screens, 6–15, 6–16
Tags, 19–8
to a different protocol, 7–22
Touch Screen to Keypad, 7–22
Cursor Point
ASCII Data Entry, 1–6, 10–12
Numeric Data Entry, 1–6, 10–2
Cutting and Pasting, Screens, 6–17
D
Data Formats, PanelView Tag, 3–9
Data Scaling, Data Entry Variables, 10–4
Data Types, 3–8
Date
Inserting in Object, 17–13
Inserting in Text String, 17–13, 18–5
Decimal Point, Numeric Data Displays, 12–11
Deleting
Objects, 7–22
Objects from Function Keys, 7–22
Screens, 6–15
Description
Entering for Application, 6–9
Entering for Object, 7–18
Deselecting Objects, 7–8
Devices, Replacing, 21–8
DF1 Communications, 4–4, 20–7
Baud Rate, 4–4, 20–8
Controller Node Address, 4–4, 20–8
Controller Node Name, 4–4, 20–8
Controller Node Type, 4–4, 20–8
Error Detect, 4–4, 20–8
Handshaking, 4–4, 20–8
Parity/Stop Bits, 4–4, 20–8
Setting Runtime Parameters, 4–4, 20–8
Terminal Node Address, 4–4, 20–8
DF1 Driver, 2–7, 2–11, 2–12, 23–9
DH+ Communications, 20–5
Baud Rate, 4–3, 20–6
Controller Name, 4–3, 20–6
Controller Node Address, 4–3, 20–6
Setting Runtime Parameters, 4–3, 20–6
Terminal Node Address, 4–3, 20–6
DH–485 Communications, 20–3
Baud Rate, 4–2, 20–4
INTERCHANGE Driver, 2–13
Maximum Node Address, 4–2, 20–4
RSLinx Driver, 2–8
Setting Runtime Parameters, 4–2, 20–4
SLC Controller Name, 20–4
SLC Controller Node Address, 4–2, 20–4
Terminal Node Address, 4–2, 20–4
Using RS–232 Connection, 20–3
Using RS–485 Connection, 20–3
Dialog Boxes
Conventions, 5–9
Illustrated, 5–9
Moving, 5–9
Discrete I/O, 4–9
Example, 4–10
Display, Maintenance Schedule, 20–23
Display Intensity, 20–22
DOS File, Application Transfer, 23–7
Downloading Application
Directly to Terminal, 23–6, 23–10
on Local DH+ Link, 23–12
Reducing Size of File, 23–28
to DOS File, 23–6, 23–18
to Memory Card, 23–6, 23–16
using DH485 Driver, 23–11
using Internal DF1 Driver, 23–9
using Pass–Through, 23–13
Dragging Objects, 7–9
Draw Pointer, 7–3
Drivers
INTERCHANGE Software, 2–10
Internal DF1 Driver, 23–9
RSLinx Software, 2–7
Duplicating Tags, 19–9
Dynamic Objects, 1–6
Publication 2711–6.0
Index–4
E
F
Edit Objects Menu, Commands, A–2
File Menu, Commands, A–1
Edit Screen Menu, Commands, A–2
Fill Options, 17–3, 17–6
Editor
Spreadsheet, 1–2, 5–10
Tag, 1–3
Finding Tags, 19–10
Embedded Variables, 7–17
Inserting ASCII variable, 17–17
Inserting Numeric, 17–14
Inserting Time or Date, 17–13
End List Key, 9–12, 11–9
Enter List Key, 9–12, 11–9
Error, Messages, D–1
Error State
for Bar Graphs, 12–3
for List Indicators, 12–3
for Message Displays, 13–5
for Multistate Indicators, 12–3
for Numeric Data Displays, 12–3
Errors
Correcting Validation, 23–3
Specific to CFG_485.EXE, F–9
Specific to CFG_DF1.EXE, F–9
Specific to RNA.EXE, F–10
Tag, 19–20
Examples
Alarm List, 15–5
Alarms, 15–28, 15–29, 15–30, 15–31, 15–32
Application Screens, 1–5
Bar Graph Scaling, 12–2
Bar Graphs, 12–4
Bit/LSBit Triggered Alarms, 15–19
Block Transfer Read, 4–13
Block Transfer Write, 4–14
Control List, 9–4
Control Tags, 20–25
Data Entry Scaling, 10–4
Discrete I/O, 4–10
Global Objects, 14–2
List Indicator, 12–18
Message Displays, 13–2, 13–3
Multistate Indicator, 12–12
Numeric Entry Controls, 10–3
Numeric Data Display Scaling, 12–2
Numeric Entry Handshake Tags, 10–11
Scaling Precision and Rounding, 10–6
Using the Remote Ack Tag, 15–24
Value Triggered Alarms, 15–18
Exiting PanelBuilder, 6–21
Exporting Graphics, 16–11
to a Disk File, 16–15
to the Clipboard, 16–14
Extended ASCII Characters, H–1
Publication 2711–6.0
Font Files, 22–3
Code Page, 22–2
Copying to Memory Card, 22–14
Detecting Problems, 22–16
Double–Byte Character Set, 22–3
Enabling in PanelBuilder, 22–11
Glyph, 22–3
Input Method Editor, 22–2
Single–Byte Character Set, 22–2
Translating text in Excel, 22–19
Using to Create Application, 22–11, 22–13
FontTool, 2–6, 22–1
Creating Font Files, 22–6
Detecting Problems, 22–15
Font Files, 22–3
Input Method Editor, 22–4
Opening Font Files, 22–8
Printing Font Files, 22–10
Saving Font Files, 22–9
Using, 22–5
Viewing Sample Text, 22–8
Foreground/Background
for Color Graphics, 17–22
for Objects, 17–9
for Text, 17–30
Form View, Tag Editor, 19–3
Format Bar, 5–2, 5–6, 17–2
Inner Graphic Mode, 5–6, 17–2
Graphics List Box, B–3
Import/Export Graphics Tool, B–3
Inner Text Mode, 5–6, 17–2
Object Formatting
Blink Tool, B–2
Fill Pattern Tool, B–2
Line Tool, B–2
Shape Tool, B–2
Toggle Fore/Background Tool, B–2
Object Mode, 5–6, 17–2
Text Formatting
Blink Tool, B–3
Center Align Tool, B–3
Embedded Variable Tool, B–3
Existing Text Tool, B–3
Left Align Tool, B–3
Right Align Tool, B–3
Text Box, B–3
Text Size Tool, B–3
Toggle Fore/Background Tool, B–3
Underline Tool, B–3
Index–5
Format Menu, Commands, A–4
Formatting Objects, 7–13
Function Keys, Deleting Objects, 7–22
G
Global Objects
Accessing, 14–5
Copying, 14–3
Creating, 14–1
Defining, 14–4
Example , 14–2
Grouped Objects, 7–10
Moving and Resizing, 14–6
Global Technical Support (GTS), Information Required, 5–14
Goto Config Screen Button
Attributes, 11–4
Creating, 11–3
Description, 1–6, 11–2
Goto Screen Button
Attributes, 11–4
Creating, 11–3
Description, 1–6, 11–2
Dialog, 11–4
Graphic Tools, 16–2
Background Text Tool, B–4
Circle Tool, 16–5
Connected Lines Tool, B–4
Ellipse Tool, 16–5, B–4
Freeform Tool, 16–6, B–4
Graphic Image Tool, B–4
Import/Export Graphics Tool, B–4
Line Tool, B–4
Rectangle Tool, B–4
Scale Tool, B–4
Selection Arrow, B–4
Text Tool, 16–8
Graphics, 1–7
Background, 16–16
Helpful Hints, 16–1
Inner, 17–20
ISA Symbols, B–7
Objects, 16–2
Setting Foreground/background Colors, 17–21
Grids
Screen Grid, 7–6
Touch Grid, 7–5
Grouped Objects, 7–10
H
Handshake Timeout, 20–22
Help
Buttons, 5–14
Commands, A–6
Getting, 5–14
Menu, A–6
Home List Key, 11–9
I
Icons
Application File, 6–13
Application Screens, 6–13
Opening, 6–13
Importing Graphics, 16–11
Deleting, 16–15
Editing, 16–11, 17–23
From a Disk File, 16–12
From the Clipboard, 16–13
Viewing Imported Graphics, 16–14
Initial Values
for Control List Selectors, 9–6
for Numeric Entry Controls, 10–5
for Push Buttons, 8–5
Tag Editor Field, 19–6
Terminal Presets, 20–17
Inner Graphics, 17–10, 17–19
Adding, 17–20
Editing Bitmap or ISA Symbol, 17–23
Moving, 17–20
Removing, 17–23
Selecting a State, 17–20
Using Bit Map, 17–20
Using ISA Symbol, 17–20
Inner Text, 17–10, 17–19
Accessing Extended ASCII Characters, H–1
Editing, 17–11, 17–12
for Multistate or List Objects, 17–12
For Objects Without States, 17–11
Push Buttons, 8–3
Selecting a State, 17–11, 17–12
Using Existing Text, 18–2
Using Word Wrap, 17–11, 17–12
Installing PanelBuilder, 2–4
Intended Audience, P–1
INTERCHANGE Communication Software, 2–2
Accessing Drivers, 2–10
Advanced Parameters, 2–15
Configuring Drivers, 2–11
Conflicts with Drivers, 2–16
Disabling, 2–16
Editing Drivers, 2–14
Installing, 2–4
Other Software Using, 2–17
Removing Drivers, 2–14
Troubleshooting, F–6
Internal Read Only Tags, G–1
ISA Symbols Toolbox, 7–2, 16–7, B–7
Publication 2711–6.0
Index–6
K
Keypad Enable
ASCII Data Entry, 1–6, 10–12
Numeric Data Entry, 1–6, 10–2
Numeric Entry, 10–7
L
Language, Terminal Messages, 20–22
Latched Push Buttons
Attributes, 8–4
Creating, 8–4
Description, 1–6, 8–2
Least Significant Bit Trigger
List Indicator, 12–19
Message Displays, 13–4
Multistate Indicator, 12–13
List Indicator
Attributes, 12–20
Configuring States, 7–15
Creating, 12–20
Data Ranges, 12–23
Description, 12–18
Dialog, 12–20
Error State, 12–3
Examples, 12–18
Least Significant Bit Trigger, 12–19
Setting Number of States, 12–22
Triggering a State, 12–19
List Keys
Backspace Key, 1–7, 9–12, 11–9
Control List, 9–2, 9–12
Creating, 9–12, 11–9
Dialog, 9–12, 11–9
End Key, 1–7
Enter Key, 1–7, 9–12, 11–9
Home Key, 1–7, 9–12, 11–9
Move Down Key, 1–7, 9–12, 11–9
Move Up Key, 1–7, 9–12, 11–9
Page Down Key, 1–7, 9–12, 11–9
Page Up Key, 1–7, 9–12, 11–9
Screen List, 11–9
M
Maintained Push Buttons
Attributes, 8–4
Creating, 8–4
Description, 1–6, 8–2
Maintenance Schedule, Display, 20–23
Manual
Contents, P–2
Conventions, P–3
Related Publications, P–3
Publication 2711–6.0
Maximize Button, 5–2
Memory, Hints on Reducing, 3–14
Memory Cards, 23–7
ATA, 22–2
DataBook, 22–2
Downloading Application, 23–16
using a retainer, 22–14
Menu Bar, 5–2
Menus, Conventions, 5–4
Message Displays
Alarms, 15–7
Attributes, 13–6
Configuring States, 7–15
Creating, 13–6
Data Types, 13–7
Description, 1–6
Dialog, 13–6
Error State, 13–5
Examples, 13–2
Helpful Hints, 13–1
Inserting a Variable, 13–9
Least Significant Bit Trigger, 13–4
Read Tag, 13–7
Setting Number of Messages, 13–8
Triggering Messages, 13–4
Message Editor, 18–2
Messages
Error and Warning, D–1
Software, D–1
Validation, E–1
Minimize Button, 5–2
Momentary Push Buttons
Attributes, 8–4
Creating, 8–4
Description, 1–6, 8–2
Mouse Pointer, 5–2, 7–3
Move Down List Key, 9–12, 11–9
Move Up List Key, 9–12, 11–9
Moving Objects, 7–9
Multilingual Support, 22–1
Multistate Indicator
Attributes, 12–14
Configuring States, 7–15, 12–16
Creating, 12–14
Data Ranges, 12–17
Description, 1–6, 12–12
Dialog, 12–14
Error State, 12–3
Examples, 12–12
Least Significant Bit Trigger, 12–13
Read Tag, 12–15
Setting Number of States, 12–16
Index–7
Triggering a State, 12–13
Types, 12–12
Multistate Push Buttons
Attributes, 8–4
Configuring States, 7–15
Creating, 8–4
Description, 1–6, 8–2
Setting Number of States, 8–8, 8–9
N
Numeric Data Display
Attributes, 12–10
Creating, 12–9
Decimal Point, 12–11
Description, 1–6
Error State, 12–3
Read Tag, 12–11
Scaled, 12–2
Types of, 12–9
Without Scaling, 12–2
Numeric Entry
Cursor Point, 10–2, 10–7
Cursor Point Example, 10–3
Dialog, 10–7
Display, 10–9
Format, 10–10
Handshake and Notification Tags, 10–11
Input, 10–8
Keypad Enable, 10–2
Keypad Enable Example, 10–3
Scaling Data, 10–4
Scratchpad, 10–2
Write Tag, 10–8
Numeric Variable, 7–17, 17–14, 18–5
O
Object Formatting
Changing Fill Pattern, 17–6
Changing Line Type, 17–5
Changing Shape, 17–4
Using Foreground/Background, 17–9
Objects
Accessing, 7–2
Aligning, 7–5
Background, 7–16
Bring to Front, 7–11
Configuring States, 7–15
Copying, 7–20
Creating in Display Area, 7–3, 7–4
Creating on Function Keys, 7–3, 7–7
Cutting, 7–21
Default Size, 7–4
Deleting, 7–22
Description, 7–18
Deselecting, 7–8
Dragging, 7–9
Dynamic or Static, 1–6
Editing Attributes, 7–14
Fill, 7–16
Foreground, 7–16
Formatting, 7–13, 17–3
Global, 14–1, 14–5
Grouped, 7–10
Linking to Controller Data File, 3–6
Move to Back, 7–11
Moving, 7–9
Pasting, 7–21
Regrouping, 7–10
Resizing, 7–9
Selecting, 7–8
Selecting Multiple, 7–8
Setting Default Colors, 7–13
Sizing, 7–9
Stacking, 7–11
Text, 7–16
Turning View On or Off, 7–19
Types, 1–6
Ungrouping, 7–10
Viewing Attributes, 7–14
Zooming, 7–11
Objects Menu, Commands, A–3
P
Page Down List Key, 9–12, 11–9
Page Up List Key, 9–12, 11–9
Palette, Using Color, 5–8
PanelBuilder
Defaults, 5–13
Description, 1–1
Exiting, 6–21
Installing, 2–4
Preferences, 1–2
Starting, 6–2
System Requirements, 2–1
PanelBuilder Windows, 5–2
Application File Window, 5–3
Application Screen Window, 5–3
PanelView
Advanced Terminal Setup, 20–21
Converting Applications, 6–18
Features, 1–2
Screen Worksheets, C–1
Terminal Display Settings, 20–22
Terminal Setup, 20–2
Publication 2711–6.0
Index–8
Pass–Through
Communication Drivers, 23–14, 23–22
DH–485 Setup, 23–15
Enabling, 4–12, 20–11
Remote I/O setup, 23–14
Timeout, 4–12, 20–11
Uploading From Terminal, 23–22
Pasting
Objects, 7–20
Screens, 6–15, 6–16, 6–17
Piloted Control List, 9–2
Block Write Start Tag, 9–3
Inactive States, 9–3
Power–Up Options
Memory Card Load Conditions, 20–17
Preset Values, 20–17
Restart Screen, 20–17
Startup Screen, 20–17
Use Downloaded Settings, 20–17
Precision, of Scaled Values, 10–6
Preferences, 1–2
When Opening an Application, 6–7, 21–10
Preset Values
for Control Objects, 20–18
On Power–Up, 20–2
Write Initial Values, 20–17
Print Only Objects
Configuring Print Messages, 13–10
Copying a Print Object, 13–12
Deleting a Print Object, 13–12
Editing a Print Object, 13–12
Renaming a Print Object, 13–12
Printing
Configuring Printer Port, 20–13
Initialization String, 20–14
Print Only Message, 13–10
Reports, 24–5
Tags, 19–12
Text, 18–7
Validation Messages, 23–2, 23–4
Projects
Changing, 21–2
Copying a Device, 21–5
Copying a Project, 21–3
Copying to Another Computer, 21–6
Creating a Project, 21–3
Deleting a Device, 21–5
Deleting a Project, 21–3
Description, 1–1, 21–1
Loading Unknown Devices, 21–9, 21–10
Loading Unknown Tags, 21–9
Renaming a Device, 21–5
Renaming a Project, 21–3
Replacing Duplicate Devices, 21–8
Replacing Duplicate Tags, 21–8
Publication 2711–6.0
Restoring, 21–7, 21–11
Verifying an Application when Opened, 6–7, 21–10
Viewing Devices, 21–5
Publications, Related, P–3
Push Button Controls
Contact Types, 8–2
Contacts, 8–5
Data Types, 8–5
Default Inner Text, 8–3
Entering State Values, 8–10
Handshake Tag, 8–7
Hold Time, 8–5
Indicator Tag, 8–6
Initial State, 8–5
Inner Text and Graphics, 8–3
Latched, 8–2, 8–4
Maintained, 8–2, 8–4
Momentary, 8–2, 8–4
Multistate, 8–2, 8–4
Write Tag, 8–6
R
Regrouping Objects, 7–10
Related Publications, P–3
Remote I/O Communications, 4–6
Baud Rate, 4–8, 20–10
Block Transfers, 4–6, 4–8, 20–10
Communication Loss, 4–16
Controller Name, 4–8, 20–10
Controller Types, 4–7, 20–9
Discrete I/O, 4–6, 4–9
Last Chassis, 4–8, 20–10
Module Groups, 4–6, 4–8, 20–10
Pass–Through, 23–14
Rack Sizes, 4–6, 4–7
Terminal Rack Address, 4–8, 20–10
Remote Tags, Alarms, 15–26
Renaming Application, 6–8
Reports, 24–1
Adjusting Format, 24–3
Connecting to Printer, 24–1
Creating, 24–2
Options, 24–1
Overview, 1–3
Printer Setup, 24–5
Sending to a File, 24–6
Resizing Objects, 7–9
Resizing Screen Grid, 7–6
Restoring, Projects, 21–7, 21–11
Index–9
Return Screen Button
Attributes, 11–4
Creating, 11–3
Description, 11–2
Dialog, 11–4
Reversing Edit Operation, 7–22
Rounding, of Scaled Values, 10–6
RSLinx Communication Software, 2–2
Accessing, 2–7
Configuring Drivers, 2–7
Installing, 2–6
Mapping Drivers to Ports, 2–9
S
Screen List Selector
Attributes, 11–6
Configuring States, 7–15
Creating, 11–5
Description, 1–6, 11–2
Dialog, 11–6
Selecting Screen Names, 11–8
Setting Number of List Entries, 11–7
Using Multiple Lists, 11–2
Screen Menu, Illustrated, A–1
Screen Menu, Commands, A–1
Screen Number to PLC/SLC, 20–26
Screen Saver, 20–22
Display Intensity, 20–22
Screen Selectors
Goto Config Screen Button, 1–6, 11–2
Goto Screen Button, 1–6, 11–2
Helpful Hints, 11–1
List, 1–6
Return Screen, 1–6
Return Screen Button, 11–2
Screen List Selector, 11–2
Screens
Activating, 6–13
Arranging, 6–13
Closing, 6–14
Converting Copied, 6–18
Copying, 6–15, 6–16
Cutting and Pasting, 6–17
Deleting, 6–15
Opening Existing, 6–11
Opening Multiple, 6–12
Opening New, 6–10
Opening Single, 6–11
Reducing to Icons, 6–13
Renaming, 6–14
Search Tag, Piloted Control Lists, 9–8
Selecting Objects
Multiple Objects, 7–8
Single Objects, 7–8
Sizing Objects, 7–9
Spreadsheet Editor, 1–2
Add/Insert/Delete Row, 5–13
Changing Column Order, 5–12
Changing Column Width, 5–11
Changing Row Height, 5–11
Cut/Copy/Paste, 5–12
Using, 5–10
Stacking Objects
Bring to Front, 7–11
Move Dynamic Objects to Front, 7–11
Move to Back, 7–11
Standard Control List, 9–2
States
Control List, 9–10
List Indicator, 12–22
Multistate Indicator, 12–16
Operations Performed On, 7–17
Push Button, 8–8
Screen List Selector, 11–7
Static Objects, 1–6
Status Bar, 5–2
Status Tags
Screen Number Status, 20–26– 20–30
Time or Date Status, 20–26– 20–30
Support, Technical, P–4
Symbols, ISA, B–7
System Requirements, 2–1
T
Table View, Tag Editor, 19–1
Tag Editor, 1–3
Changing Between Views, 19–3
Description, 19–2
Form View, 19–3
Import/Export Utility, 19–15
Navigating, 19–3
Table View, 19–1
Tool Bar, 19–1, 19–3
Using Tools, 19–15
Validating Tags, 19–4
Tags
Address, 19–5
Array Size, 19–5
Control, 20–25
Copying, 19–8
Data Entry Limits, 19–5
Data Types, 19–5
Defining, 3–13
Duplicating, 19–9
Exporting, 19–18
Finding, 19–10
Publication 2711–6.0
Index–10
Tags
Having the Same Name, 19–17
Import/Export Errors, 19–20
Importing, 19–16
Initial Value, 19–5
Inserting and Deleting, 19–7
Internal Read Only, G–1
Node Name, 19–5
Printing, 19–12
Replacing, 21–8
Saving Form View, 19–7
Saving Table View, 19–7
Scaling, 19–5
Sorting, 19–11
Status, 20–26
Tag Description, 19–5
Tag Name, 19–5
Update Frequency, 19–5
Validating, 19–4
Viewing, 19–7
Technical Support, Information Required, 5–14
Terminal Preset Values, 20–2, 20–17, 20–18
Terminal Setup
Advanced Options, 20–21
Auto Repeat Settings, 20–21
Backlight, 20–22
Control Tags, 20–24– 20–28
Display Intensity, 20–22
Handshake Timeout, 20–22
Language Selection, 20–22
Overview, 20–2
Power–Up Options, 20–17
Preset Values, 20–2, 20–17, 20–18
Reverse Video, 20–22
Screen Saver, 20–22
Status Tags, 20–26– 20–30
Time/Date Formats, 20–19
Text
Adding New, 18–3
Aligning, 17–26
Background, 1–7, 7–16, 16–8, 16–9
Blink, 7–16
Color, 16–9
Copy/Paste, 18–4
Copying, 18–10
Deleting Unused, 18–8
Editing, 18–4
Filtering, 18–6
Foreground, 7–16
Foreground/Background Colors, 17–29
Formatting, 17–24
Inner, 17–12
Moving, 18–9
Printing, 18–7
Renumbering, 18–9
Sizing, 7–16, 17–25
Publication 2711–6.0
Sorting, 18–6
Underline, 7–16
Text Formatting, 17–24
Aligning Text, 17–26
Sizing Text, 17–25
Underlining Text, 17–27
Using the Blink Option, 17–28
Using the Color Foreground/Background Option, 17–30
Tick–Mark Labels, 12–8
Time
Inserting in Object, 17–13
Inserting in Text String, 17–13, 18–5
Time/Date Setup, 20–19
Title Bar, 5–2
Tool Bar, 5–2, 5–5
Copy Tool, B–1
Cut Tool, B–1
Edit Attributes Tool, B–2
Inner Graphic Tool, B–2
Inner Text Tool, B–2
New File Tool, B–1
New Screen Tool, B–1
Next State or Previous State Tool, B–2
Open File Tool, B–1
Open Screen Tool, B–1
Paste Tool, B–1
Save File Tool, B–1
Turning On or Off, 5–5
Undo Tool, B–1
Zoom In Tool, B–2
Zoom Out Tool, B–2
Toolbox
Background Text Tool, B–4
Backspace Key, B–6
Bar Graph Tool, B–5
Connect Lines Tool, B–4
Control List Tool, B–5
Controls, Displays and Graphics, 5–7, 7–2
Ellipse Tool, B–4
Enter Key, B–6
Freeform Tool, B–4
Global Object Tool, B–5
Go To Screen Button Tool, B–5
Graphic Image Tool, B–4
Graphics, 7–2
Home Key, B–6
Illustrated, B–4
Import/Export Graphics Tool, B–4
ISA Symbols, 5–7, 7–2, 16–7
ISA symbols, B–7
Latched Push Button Tool, B–5
Line Tool, B–4
List Indicator Tool, B–5
Maintained Push Button Tool, B–5
Message Display Tool, B–5
Index–11
Toolbox
Momentary Push Button Tool, B–5
Move Down Key, B–6
Move Up Key, B–6
Multistate Indicator Tool, B–5
Multistate Push Button Tool, B–5
Numeric Data Display Tool, B–5
Numeric Input Cursor Tool, B–5
Page Down Key, B–6
Page Up Key, B–6
Rectangle Tool, B–4
Return Screen Button Tool, B–5
Scale Tool, B–4
Screen List Selector Tool, B–5
Selection Arrow, B–4
Turning On or Off, 5–7
Touch Grid, 7–5
Transfer Error Messages, F–1
Transfer Utilities
Application File Transfer Utility, 23–8
Application Menu, 23–8
PanelView File Transfer Utility, 23–8
Troubleshooting
Download Errors, F–2
Downloading to a DOS File Errors, F–3
Downloading with INTERCHANGE, F–4
Downloading with PanelView File Transfer Utility, F–3
Downloading with WINPFT Utility, F–3
Error Messages, D–1
INTERCHANGE Communications Software, F–6
Messages Specific to CFG_485.EXE, F–9
Messages Specific to CFG_DF1.EXE, F–9
Messages Specific to RNA.EXE, F–10
Running Windows 95, F–1
Starting PanelBuilder, F–2
V
Validating Application
Correcting Errors, 23–3
Dialog, 23–2
Sending Messages to File, 23–5
Sending Messages to Printer, 23–2
Validation Messages, E–1
Printing, 23–2
Sending to a File, 23–5
Setting Up Printer, 23–4
Values, Initial, 10–5
Variables
Adding in Text Editor, 18–5
Adding to Alarms, 15–21
ASCII, 1–6, 17–16
Embedded, 7–17
in a Message, 13–9
Numeric, 1–6, 17–14
Scaling Data, 10–4
Time or Date, 17–13
View Menu, Commands, A–3
View Option, 7–19
Viewing Tags, 19–7
W
Warning Messages, D–1
Window Border, 5–2
Window Menu, Commands, A–5
Windows Environment, 5–1
WINPFT, Application File Transfer Utility, 23–23
Word Wrap, 7–16, 17–11, 17–12
Worksheets, 3–5, C–1
U
Underline, 7–16
Ungrouping Objects, 7–10
Uploading Application
Directly from Terminal, 23–19
on Local DH+ Link, 23–21
using DH485 Driver, 23–20
using Internal DF1 Driver, 23–9, 23–19
using Pass–Through, 23–22
Z
Zooming
Enlarging View, 7–11
Reducing View, 7–11
Publication 2711–6.0
PanelBuilder Tools
Tool Bar
Format Bar in Object View
Format Bar in Text View
Format Bar in Graphics View
Rockwell Automation helps its customers receive a superior return on their investment by bringing
together leading brands in industrial automation, creating a broad spectrum of easy-to-integrate
products including control logic, sensors, man-machine interface, motors, power devices and
software. These are supported by local technical resources available worlwide, a global network
of system solutions providers, and the advanced technology resources of Rockwell International.
Worldwide representation.
Argentina • Australia • Austria • Bahrain • Belgium• Bolivia • Brazil • Bulgaria • Canada • Chile • China, People’s Republic of • Colombia • Costa Rica • Croatia • Cyprus
Czech Republic • Denmark • Dominican Republic • Ecuador • Egypt • El Salvador • Finland • France • Germany • Ghana • Greece • Guatemala • Honduras • Hong Kong
Hungary • Iceland • India • Indonesia • Iran • Ireland-Eire • Israel • Italy • Jamaica • Japan • Jordan • Korea • Kuwait • Lebanon • Macau • Malaysia • Malta• Mexico
Morocco • The Netherlands • New Zealand • Nigeria • Norway • Oman • Pakistan • Panama • Peru • Philippines • Poland • Portugal • Puerto Rico • Qatar • Romania • Russia
Saudi Arabia • Singapore • Slovakia • Slovenia • South Africa, Republic of • Spain • Sweden • Switzerland • Taiwan • Thailand • Trinidad • Tunisia • Turkey
United Arab Emirates • United Kingdom • United States • Uruguay • Venezuela
Rockwell Automation Headquarters, 1201 South Second Street, Milwaukee, WI 53204 USA, Tel: (1) 414 382-2000 Fax: (1) 414 382-4444
Rockwell Automation European Headquarters, Avenue Hermann Debroux, 46, 1160 Brussels, Belgium, Tel: (32) 2 663 06 00, Fax: (32) 2 663 06 40
Rockwell Automation Asia Pacific Headquarters, 27/F Citicorp Centre, 18 Whitfield Road, Causeway Bay, Hong Kong, Tel (852) 2887 4788, Fax: (852) 2508 1846
Publication 2711–6.0 – December 1998
Supersedes Publication 2711-6.0 – April 1998
Supersedes Publication 2711–6.0.5 – July 1998
40061-359-01(E)
Copyright 1999 Allen-Bradley Company, Inc. Printed in USA
Publication 2711–6.0
Was this manual useful for you? yes no
Thank you for your participation!

* Your assessment is very important for improving the work of artificial intelligence, which forms the content of this project

Download PDF

advertisement