b0193mq M

B0193MQ
REV M
I/A Series
Display Engineering for
FoxView Software and Display Manager Software
September 28, 2007
Invensys, Foxboro, FoxDraw, FoxSelect, FoxView, and I/A Series are trademarks of Invensys plc, its
subsidiaries, and affiliates.
All other brand names may be trademarks of their respective owners.
Copyright 1993-2007 Invensys Systems, Inc.

All rights reserved
SOFTWARE LICENSE AND COPYRIGHT INFORMATION

Before using the Invensys Systems, Inc. supplied software supported by this documentation, you
should read and understand the following information concerning copyrighted software.
1. The license provisions in the software license for your system govern your obligations
and usage rights to the software described in this documentation. If any portion of
those license provisions is violated, Invensys Systems, Inc. will no longer provide you
with support services and assumes no further responsibilities for your system or its
operation.
2. All software issued by Invensys Systems, Inc. and copies of the software that you are
specifically permitted to make, are protected in accordance with Federal copyright
laws. It is illegal to make copies of any software media provided to you by
Invensys Systems, Inc. for any purpose other than those purposes mentioned in the
software license.
Contents
Figures.................................................................................................................................... ix
Tables..................................................................................................................................... xi
Preface................................................................................................................................. xiii
Audience ................................................................................................................................ xiii
Revision Information ............................................................................................................. xiii
Reference Documents ............................................................................................................ xiii
Conventions ........................................................................................................................... xiv
1. Overview ........................................................................................................................... 1
Multiple Instances of FoxView, Display Manager and Alarm Manager ..................................... 1
Designing Displays Using ExpertSelect Functionality ............................................................... 1
Setting Display Resolution and Colors 70 Series .................................................................... 2
2. Dual-Headed Workstations ............................................................................................... 5

50 Series Dual-Headed WorkStations ....................................................................................... 5
70 Series Dual-Headed WorkStations ....................................................................................... 5
3. Multiple FoxViews, Display Managers, and Alarm Managers............................................ 7

Alarm Manager Considerations ................................................................................................. 8
Starting Up Additional FoxViews, DMs or AMs ..................................................................... 10
Solaris Workstations ........................................................................................................... 10
Windows Off Mode ...................................................................................................... 11
Windows Workstations ...................................................................................................... 11
Stopping Additional FoxViews, DMs and AMs ....................................................................... 11
50 Series Workstations ....................................................................................................... 11
Windows Workstations ...................................................................................................... 11
Dedicated FoxViews, DMs and AMs and Licensing ................................................................ 11
Remote FoxViews, DMs and AMs .......................................................................................... 12
Dynamic Resource Allocation ................................................................................................. 12
Instructions for Editing the Initial RALs ............................................................................ 13
Accessing WP51/AW51 CPU Idle Time and RAL for DMs .............................................. 14
Security ................................................................................................................................... 14
Limiting Access to FoxView, DM, or AM from Remote Terminals .................................... 14
Limiting Access within a DM or AM ................................................................................. 17
iii
B0193MQ Rev M Contents
4. ExpertSelect..................................................................................................................... 23
Display Manager ExpertSelect Functionality ........................................................................... 23
Evaluation of Object Manager Data Values in Display Commands .................................... 24
Support for Named Actions ............................................................................................... 25
Display Commands Embedded in Display Files ................................................................. 25
Examples ................................................................................................................................. 26
Detail Displays and Faceplates ................................................................................................ 28
5. Pull-Down Menu Access Control .................................................................................... 29

.pulldown File ......................................................................................................................... 29
Examples ................................................................................................................................. 30
Disabling Pull-Down Menu Picks ...................................................................................... 30
Enabling Pull-Down Menu Picks ....................................................................................... 30
Changing the Color of Pull-Down Menu Picks (DM Only) .............................................. 30
Inserting Space Between Pull-Down Menu Picks (DM Only) ............................................ 31
Indenting Pull-Down Menu Picks (DM Only) .................................................................. 31
6. Configuring and Assigning Passwords for FoxView Environments.................................. 33

Environment Definition Files ................................................................................................. 33
Access Level File ................................................................................................................. 34
Examples ....................................................................................................................... 35
Menu Bar Definition File ................................................................................................... 35
Example ........................................................................................................................ 36
Menu Button Definition Files ....................................................................................... 36
Examples ....................................................................................................................... 37
Display Bar Definition Files ............................................................................................... 37
Example ........................................................................................................................ 38
Bitmap Utility ......................................................................................................................... 39
Setting Environment Passwords Utility ................................................................................... 39
Example ............................................................................................................................. 39
FoxView Shortcut Menu Definition ........................................................................................ 40
Command Menu Entry ........................................................................................................... 41
Menu Separator ...................................................................................................................... 41
Cascading Menu Entry ............................................................................................................ 42
Menu Variables ....................................................................................................................... 42
SELDISP ............................................................................................................................ 42
SELTAG ............................................................................................................................ 42
SELCOMP ........................................................................................................................ 42
SELBLOCK ....................................................................................................................... 43
Examples of Shortcut Menu Definition Files ........................................................................... 43
Example 1 .......................................................................................................................... 43
Example 2 .......................................................................................................................... 43
Environment Shortcut Menus ................................................................................................. 44
iv
Contents B0193MQ Rev M
Environment Shortcut Menu Styles ................................................................................... 44

Environment Shortcut Menu Types ................................................................................... 44
7. File Access ....................................................................................................................... 47

ia16 Subdirectory on 50 Series AP or AW ............................................................................... 47
Display Manager Search Paths ................................................................................................ 47
FoxView Search Paths ............................................................................................................. 48
Display Conversion On-the-Fly .............................................................................................. 48
Programmable Logic Block (PLB) Ladder Display Access ....................................................... 49
Configuring Ladder Display Location ................................................................................ 49
50 Series Workstation Access .............................................................................................. 51
50 Series WP Configuration Option ............................................................................. 51
Installing Ladder Displays on Local Disk or Logical Host .............................................. 52
Sequence Code Access ............................................................................................................. 52
50 Series Workstation Access .............................................................................................. 52
FoxView Sequence Block Detail Display Access ................................................................. 53
8. Databases ........................................................................................................................ 55
Display Manager 50 Series Fonts and Markers ........................................................................ 55
Creating Custom Markers for the 50 Series ........................................................................ 57
Expanding Marker Files on WP51 and AW51 .............................................................. 58
Parameter Database df_pdef or dsppdef.dat ......................................................................... 59
Parameter Definition Syntax .............................................................................................. 59
Optional Arguments for Real Parameters ....................................................................... 60
Optional Arguments for Range Parameters .................................................................... 60
Optional String Parameter Arguments ........................................................................... 60
Optional Boolean Parameter Arguments ........................................................................ 60
Optional Packed Boolean/Long Arguments ................................................................... 61
Block Database gdblk50.db or dspblock.dat .................................................................... 62
Database File Layout Requirements ............................................................................... 62
9. Upgrading from Display Manager to FoxView ................................................................ 67

FoxView .................................................................................................................................. 67
Whats New ....................................................................................................................... 67
Whats the Same ................................................................................................................. 67
What Needs to be Converted from Display Manager to FoxView Format .......................... 67
FoxSelect ................................................................................................................................. 68
FoxDraw ................................................................................................................................. 68
FoxDraw Browser Capability .............................................................................................. 68
Display Names ................................................................................................................... 68
Converting and Modifying Display Manager Files .................................................................. 68
FoxView/FoxDraw File Extensions ..................................................................................... 68
The /opt and /usr Directories ............................................................................................. 69
User Edits to Standard Files ............................................................................................... 69
v
Converting a Display File ........................................................................................................ 70

Converting a Customized Color Palette .................................................................................. 71
Copying colordef.dat .......................................................................................................... 71
Editing colordef.dat ............................................................................................................ 72
Configuring Blinking Colors .............................................................................................. 73
Copying fv_blink.dat ..................................................................................................... 73
Editing fv_blink.dat ....................................................................................................... 74
Upgrading Customized Environment Files .............................................................................. 76
Sample FoxView Environment File (Initial.env) ............................................................ 77
Sample Menu Bar File (Initial.mbr) ............................................................................... 77
Sample Menu Definition File (file.mnu) ....................................................................... 78
New Commands to Support Menu Definition Files ...................................................... 79
Sample Display Bar Definition File ............................................................................... 79
Example: Upgrading Display Manager Environment Files to FoxView .......................... 80
Display Bar Configuration Menu .................................................................................. 82
Protecting Display Bar Menu Picks, System and Process Buttons, and Select/Assign .......... 82
System and Process Buttons ........................................................................................... 83
Select and Assign Mode ................................................................................................. 84
On-Line Trend Configuration Picks .............................................................................. 84
FoxSelect On/Off Access ............................................................................................ 84
Getting Started with FoxView ................................................................................................. 85
Using FoxView ................................................................................................................... 85
Using FoxSelect .................................................................................................................. 86
Using FoxView ........................................................................................................................ 86
Display Access .................................................................................................................... 86
Changing Environments ..................................................................................................... 86
FoxSelect ............................................................................................................................ 86
Alarm Bar ........................................................................................................................... 87
Message Bar ........................................................................................................................ 87
Status Bar ........................................................................................................................... 87
New Display Window Variables ......................................................................................... 88
10. ScratchPad Group and Trend Displays.......................................................................... 89

Overview ................................................................................................................................. 89
ScratchPad Trends ............................................................................................................. 89
ScratchPad Group Displays ................................................................................................ 89
Installation .............................................................................................................................. 89
ScratchPad Trends ............................................................................................................. 89
ScratchPad Group Displays ................................................................................................ 90
Installed Components ........................................................................................................ 90
ScratchPad Trends ......................................................................................................... 90
ScratchPad Groups ........................................................................................................ 95
Procedures ............................................................................................................................... 98
ScratchPad Trends ......................................................................................................... 98
ScratchPad Trend Shortcut Menu ............................................................................... 104
ScratchPad Group Displays ......................................................................................... 106
vi
Contents B0193MQ Rev M
Appendix A. Multiple Display Window and AM Configuration ....................................... 117

Minimum Configuration Requirements ................................................................................ 118
Customizing DMs and AMs Using a Text Editor ................................................................. 120
SCREEN Definition ........................................................................................................ 121
TYPE Definition .............................................................................................................. 121
Display Window Property ........................................................................................... 122
DM Class or AM Class ................................................................................................ 123
FoxView/DM or AM Environment ............................................................................. 123
Examples of DM and AM Type Configurations .......................................................... 123
Assigning Custom Monitors and Types to a FoxView/DM or AM ................................... 124
DM to AM Associations ................................................................................................... 125
Index .................................................................................................................................. 127
vii
viii
Figures
1-1. Setting Display Resolution and Colors .......................................................................... 3
3-1. DM_Usage Display WP51/AW51 ............................................................................. 8
4-1. Generic Overlay Using ExpertSelect Functionality ...................................................... 26
4-2. Group Display Using ExpertSelect Functionality ........................................................ 27
6-1. Examples of Shortcut Menus ....................................................................................... 40
9-1. Convert Display Files Dialog Box ............................................................................... 70
9-2. Assign Pop-up Menu ................................................................................................... 82
0-1. Select Screen Display ................................................................................................... 87
10-1. DMScript Listing ........................................................................................................ 91
10-2. trend_sublist.txt Listing .............................................................................................. 92
10-3. Quarter Screen Trend ................................................................................................. 93
10-4. Trend Object with Assignable Pens ............................................................................. 94
10-5. Quarter Screen Size Trend .......................................................................................... 96
10-6. Trend List Overlay ...................................................................................................... 98
10-7. Trend_Setup Overlay ................................................................................................ 100
10-8. Different Sizes of Trends ........................................................................................... 100
10-9. Default Substitution Text String ............................................................................... 101
10-10. Changed Text String ................................................................................................. 101
10-11. Update_list.dmscript File .......................................................................................... 101
10-12. Online Trend Configurator ....................................................................................... 103
10-13. ScratchPad Trends Shortcut Menu ........................................................................... 104
10-14. Trend Location Overlay ............................................................................................ 104
10-15. Trend Button Name Overlay .................................................................................... 105
10-16. Trend Mode Overlay ................................................................................................ 106
10-17. Group_list Overlay ................................................................................................... 107
10-18. Label Overlay ............................................................................................................ 108
10-19. Default Substitution Text String ............................................................................... 108
10-20. Changed Text String ................................................................................................. 109
10-21. Group_#.dmscript .................................................................................................... 109
10-22. Group Base ............................................................................................................... 110
10-23. Group_config Overlay .............................................................................................. 111
10-24. Online Trend Configurator ....................................................................................... 115
A-1. Initial dmcfg File after Bootup WP51 .................................................................... 118
A-2. Example of WP Configured for Four DMs and Two AMs ........................................ 119
ix
B0193MQ Rev M Figures
x
Tables
8-1. Parameters for FoxView/FoxDraw File dspblock.dat ................................................... 64
8-2. Parameters for Display Manager File gdblk50.db ........................................................ 65
9-1. File Types and Their Extensions ................................................................................. 69
9-2. Standard File Location ................................................................................................ 69
9-3. Color Indices Entries ................................................................................................... 71
9-4. Mapping Information ................................................................................................. 72
9-5. fv_blink.dat File .......................................................................................................... 74
9-6. Menu Definition Files ................................................................................................. 79
9-7. Entries ......................................................................................................................... 81
9-8. Global Variables .......................................................................................................... 82
9-9. Global Variables that Protect System and Process Buttons .......................................... 83
9-10. Global Variables that Protect the On-Line Trend Configurator .................................. 84
10-1. ScratchPad Trend Environment Files .......................................................................... 91
10-2. ScratchPad Group Environment Files ......................................................................... 96
xi
B0193MQ Rev M Tables
xii
Preface
This document provides information needed to develop, convert and install display applications
on 50 Series and 70 Series Workstation Processors (WPs) and Application Workstations (AWs).
The 50 Series workstations use the Solaris operating system. The 70 Series workstations use the
Windows NT or Windows XP operating system. This document describes FoxView soft-
ware (FoxView), Display Manager software, display engineering tools, and display databases
that are available.
In this document, WP/AW means that the information applies to the both the 50 Series and
70 Series workstations. WP51/AW51 means that the information is specific to the 50 Series
workstations. WP70/AW70 means that the information is specific to the 70 Series workstations.
This document includes information for both the FoxView and Display Manager applications.
Where information applies to both applications, the term display window is used. When infor-
mation applies to only one of these applications, the specific application is referenced
Audience
This document is intended for process and software engineers who are responsible for developing
display applications and deploying them to I/A Series workstations. You only need to be familiar
with the operating system of your workstations.
Revision Information
For this revision of the document (B0193MQ-M), the following change has been made to reflect
FoxView/FoxDraw Software Version 9.0.3 and Version10.2:
Updated lines in the Initial environment file \opt\fox\env\Initial.dbr on
page 34.
Reference Documents
Refer to the following documents for additional information:
FoxView Software (B0193WH)
FoxDraw Software (B0193WG)
Display Commands (B0193DF)
Display Engineering Utilities (B0193WU)
Process Operations and Displays (B0193MM)
System Operations Guide (Windows NT Operating System) (B0400CR)
Display Builder for 50 Series Workstations (B0193MP)
Display Configurator (B0193AR)
Display Reporter and Connection Editor (B0193JN)
Group Object Editor for Displays (B0193DV)
xiii
B0193MQ Rev M Preface
Workstation Alarm Management (B0193RV)

Process Alarm Configuration (B0193AU)
Model 51 X Terminal System Administration Guide (Solaris 2.x) (B0193UB)
Server 70 and Model P95 System Administration Guide (Windows NT Server 4.0,
Terminal Server Edition) (B0400AS)
Hardware and Software Specific Instructions Workstation P93*A (GX240) (B0400RU)
Hardware and Software Specific Instructions for Model P95*B (PE2500, Windows NT
Server 4.0 Terminal Server Edition) (B0400RX)
Hardware and Software Specific Instructions Workstation P92*A (PW340) (B0400HD)
Hardware Kit Installation Procedures for Model P79 Workstation (Solaris 8 Operat-
ing System) (B0400SR)
Hardware Kit Installation Procedures for Model P80 Workstation (Solaris 8 Operat-
ing System) (B0400SS).
Hardware and Software Specific Instructions Workstation P92*C (PW360) (B0700BL)
Conventions
The following conventions are used in the command descriptions in this document:
The term FoxView/DM means FoxView or Display Manager.
Arguments within square brackets [ ] are optional.
Arguments that appear in italics are replaced by actual string or numerical values.
A vertical line ( | ) indicates OR. For example, a | b means a or b.
Braces { } delimit a set of choices from which the user must choose one.
In all cases, the command syntax is one continuous string (no embedded carriage
returns).
Multiple commands are separated by semicolons.
xiv
1. Overview
This chapter describes the use of multiple instances of FoxView, Display Manager and Alarm
Manager. Brief descriptions of the ExpertSelect feature and display conversion are also
provided.
Multiple Instances of FoxView, Display Manager and

Alarm Manager
You can invoke and run multiple instances of FoxView, Display Manager (DM) and Alarm Man-
ager (AM) on a single WP or AW workstation, providing multiple display and alarm windows on:
The same physical screen
Different screens of dual-headed WPs or AWs
Remote screens serviced by remote X Servers, X Terminals or remote hosts, over the
second Ethernet network
Remote screens serviced by Server 70 remote client software.
Each instance of FoxView, DM, or AM, and consequently each display and alarm window, is
totally independent. Each display and alarm window functions as though it were running on a
separate processor. At run time, no data or operator actions are shared among the display win-
dows. Each display window has its own environment, access protection level locks, HIxcfile (pref )
interface, on-line trend configuration interface, Object Manager HI globals, and so on. Each
alarm window is accessed from a display window environment via the Process button in FoxView
or the Alarm field in the DM menu bar. From the initial alarm window, additional alarm win-
dows can be opened.
Designing Displays Using ExpertSelect Functionality

The ExpertSelect feature and enhanced command functionality are included in FoxView/DM
display files. The ExpertSelect feature allows a display object to be selected through a display com-
mand, without having an operator actually select the object on the screen. Selecting a display
object causes the action that was configured for that object to be executed.
The enhanced command functionality includes the following features:
Evaluation of Object Manager data values within display commands
Display commands used to support ExpertSelect [see Display Commands (B0193DF)
for the commands]
Commands embedded in display files.
1
B0193MQ Rev M 1. Overview
Setting Display Resolution and Colors 70 Series

For proper operation of I/A Series software with the Windows NT operating system, configure
the graphics board for 1024x768 pixel resolution with 256 colors.
Configure the graphics board using the Control Panel facility, shown in Figure 1-1:
1. Double-click My Computer.
2. Double-click the Control Panel icon.
3. From the Control Panel window, double-click Display. Click the Settings tab in the
resulting Display Properties dialog box. Here, you can specify such display characteris-
tics as available colors, font size, resolution, and refresh frequency.
4. Select 256 Colors as the number of colors in the Color Palette section and
1024 by 768 pixels as the resolution in the Desktop Area section.
5. Click Test, and click OK in the Testing Mode dialog box. Wait approximately five
seconds for the test bitmap to display.
6. Click Yes if you see the test bitmap properly, click Apply, then OK.
2
1. Overview B0193MQ Rev M
Figure 1-1. Setting Display Resolution and Colors
3
B0193MQ Rev M 1. Overview
4
2. Dual-Headed Workstations
This chapter describes the use of dual-headed workstations.
50 Series Dual-Headed WorkStations

A WP51/AW51 workstation can optionally have a second monitor. An additional color graphics
card is required to connect the second monitor to the workstation. At system boot time, the pres-
ence of the second color graphics card inside a WP51/AW51 is detected automatically.
On a dual-headed WP51/AW51 station, a single cursor can be moved seamlessly across the two
monitors. By default, the second monitor is configured to be positioned above the primary moni-
tor. As a result, when the cursor is moved past the top edge of the primary monitor, it enters the
bottom edge of the second monitor.
To change the configuration for the position of the second monitor, type the following commands
in the local VT100 window:
echo X > /usr/fox/sp/crt_location
where:
X is the position of the second monitor and can have the following values:
L - Left of the primary monitor
R - Right of the primary monitor
T - On top of the primary monitor (default)
B - Below the primary monitor.
Examples:
echo L > /usr/fox/sp/crt_location
The cursor enters the second monitor when moved past the left edge of the primary
monitor.
echo R > /usr/fox/sp/crt_location
The cursor enters the second monitor when moved past the right edge of the primary
monitor.
For the new configuration of a second monitor to take effect, a WP51/AW51 must be rebooted.
70 Series Dual-Headed WorkStations

A WP70/AW70 station can optionally have a second monitor. An additional color graphics card is
required to connect the second monitor to the workstation. For more information, refer to the
following documents:
Hardware and Software Specific Instructions Workstation P93*A (GX240) (B0400RU)
Hardware and Software Specific Instructions for Model P95*B (PE2500, Windows NT
Server 4.0 Terminal Server Edition) (B0400RX).
5
B0193MQ Rev M 2. Dual-Headed Workstations
6
3. Multiple FoxViews, Display
Managers, and Alarm Managers
This chapter provides detailed descriptions of how you configure and use multiple instances of
FoxView, DM and AM.
A WP/AW station is capable of supporting multiple instances of FoxView, DM and AM. Each
instance is totally independent of all others. Unlike FoxView and DM, which provide one display
window, each AM provides a set of six alarm display windows and an operations display window.
A FoxView/DM display window and set of AM alarm display windows can be individually con-
figured to be displayed on:
The same monitor
Either monitor of a dual-headed workstation
A remote terminal running X-Window System
Remote terminal server client.
A WP/AW station comes standard with a license for a single FoxView/DM which starts up auto-
matically at boot time and a corresponding license for a single AM. Additional FoxView/DM
licenses must be purchased. Each FoxView/DM license comes with an AM license.
NOTE
Though licensing allows one AM to be run per FoxView/DM on a workstation,
memory constraints and the computing power of the individual workstation may
limit the usefulness of configuring a one to one relationship of FoxViews/DMs to
AMs. With the functional capability of a single AM providing access to multiple
alarm windows, a more beneficial configuration may be to have multiple
FoxViews/DMs configured to access the same AM. See Alarm Manager Consider-
ations on page 8.
To verify the number of licenses available for additional FoxViews on a WP51/AW51:

In File menu, click FoxView Usage.
The number of FoxView licenses available for the WP51/AW51 is displayed at the bottom of the
FoxView Usage Summary display. The number of licenses available includes the license for the
default FoxView. The number of AM licenses equals the number of FoxView licenses.
To verify the number of licenses available for additional DMs on a WP51/AW51:
In Sys menu, click DM_Usage.
The number of DM licenses available for the WP51/AW51 is displayed at the bottom of the
DM_Usage display (Figure 3-1). The number of licenses available includes the license for the
default DM. The number of AM licenses equals the number of DM licenses.
You must be configure a WP/AW that is licensed for additional FoxViews/DMs and AMs before
you can use the additional FoxViews/DMs and AMs.
7
B0193MQ Rev M 3. Multiple FoxViews, Display Managers, and Alarm
Figure 3-1. DM_Usage Display WP51/AW51
Alarm Manager Considerations

The AM works in cooperation with the workstation FoxViews/DMs allowing easy access to block
detail displays and user graphics via menu or button picks from the alarm displays. You may
respond to process alarm conditions via custom graphics optimized for your needs. Multiple
instances of AMs can run on the workstation both locally and remotely. Although each purchased
FoxView/DM license also provides an AM available for use, configuring multiple
FoxViews/DMs to a single instance of an AM (via DM/AM associations) provides a more benefi-
cial configuration to best utilize the memory and computing power of the workstation.
Four of the six alarm displays (Most Recent Alarms and the three Alarm Summary Displays) form
Object Manager connections with the control stations, similar to the way in which FoxView/DM
graphics connect to the control stations. Optionally, the Current Alarm Display can be configured
to form OM connections for the MEAS parameter. These alarm display connections allow for the
quickest possible presentation of a change to the alarm status information to be shown on the dis-
play. In addition, the alarm status parameter of the block (ALMSTA) is now used on these dis-
plays to reflect the alarm acknowledge status and the in-alarm versus returned-to-normal state.
The fact that these displays form connections to the control stations needs to be considered when
configuring the number of AMs to run on the workstation.
8
3. Multiple FoxViews, Display Managers, and Alarm Managers B0193MQ Rev M
Each connectable AM display is limited to one OM list, which holds a maximum of 255 points.
Each alarm can require two points in the list, one for the block alarm status parameter (ALMSTA)
and one for the analog parameter that is in alarm (for example, MEAS). If multiple alarms exist
within the block, the AM optimizes the number of points in the list by sharing the ALMSTA
point between the two alarm entries. Unlike the DM, the AM connections are dynamic in nature.
They are dependent upon which control stations have generated alarms to the workstation at a
particular time and which are currently in view on a display. An hour later, the same AM display
may be connected to an entirely different set of control stations. The AM adds OM connection
points to the open list only for alarms that are being shown in the display. For example, a New
Alarm Summary display may contain 436 alarm entries, but only 30 of them are available in the
display window. Therefore, the AM would add points to the list associated with only those 30
alarm entries.
When an alarm has a connection that is no longer displayed, the AM deletes the connection for
that alarm, but not immediately. Because alarms can oscillate, certain rules are in place to prevent
any unnecessary addition and deletion of connection points because this places a burden on the
system.
The following are some caveats associated with AMs OM list manipulation logic:
1. An alarm must be present in the display window for a minimum of two seconds
before the AM starts to add connection points for it. This prevents extraneous con-
nections being made when an operator is scrolling through one of the displays.
2. An alarm must be off the display window for a minimum of thirty minutes before the
AM removes the connection point.
3. Any time the OM list becomes full, the entire list is closed and reopened afresh.
Closing the entire list and reopening it is less taxing on the system than performing a
multitude of dynamic deletions from the list.
4. When an alarm appears in the display window, there can be a delay of up to eight
seconds before the first update occurs. This is equivalent to the sum of:
OmConnectDelay + OmActivateDelay + OmRefRate
where:
OmConnectDelay Specifies how long an alarm must be in the display window
before the AM starts to add points for it to the OM list
(2-second default).
OmActivateDelay Specifies how often the AM is allowed to perform an activate
on the list; essentially an add must be followed by an activate
to make it occur. This allows the AM to optimize the number
of activates needed for multiple additions. (1-second default).
OmRefRate Specifies how often the OM should provide updates regardless
of how often the data is actually changing in the control
station (5-second default).
Though each AM display is limited to one OM list, this maps to a variable number of workstation
IPC connections, each one for a different CP from which alarms have been received and are dis-
played. This information needs to be considered when determining the number of AMs to display
alarms on a given workstation.
9
From the control station perspective, the number of workstations and associated AM connected
displays from which alarm conditions are to be viewed needs to be considered when establishing
alarm destinations.
The application of match/filter criteria to a display may be used as a means of limiting the num-
ber of control station connections established by the AM for any of its connected alarm displays.
Starting Up Additional FoxViews, DMs or AMs

Additional FoxViews, DMs, or AMs can only be started up after they have been configured.
Solaris Workstations
Additional FoxViews or DMs can be started up from the FoxView Usage or DM_Usage display
by selecting a name in the DMNAME column and then selecting the START button. A FoxView
or DM can be started up from a monitor only if the named FoxView or DM name has been con-
figured to be displayed on that monitor. Additional AMs are started from the additional FoxView
or DM window.
A DMNAME that can be started from the Usage display highlights as an active selectable area
when the cursor is moved over the field. A DMNAME that cannot be started from a Usage
display shows the reason in the Reason Not Selectable column.
If a DMNAME is running, the Active Screen column identifies the monitor where the
FoxView/DM is currently running.
Additional FoxViews, DMs, and AMs can also be started from the workspace menu of a
WP51/AW51 by pressing the right button on the mouse or trackball and selecting the Program
menu. The Program menu includes the following commands: I/A Display Manger, I/A FoxView,
and I/A Alarm Manager. If a FoxView/DM or AM license is available, and the
FoxView/DM or AM is configured to be displayed on that monitor, the FoxView/DM or AM
starts up on that monitor. Otherwise, the following error message is displayed:
Display Manager Not Available
FoxView Not Available
Alarm Manager Not Available
There may be more than one FoxView/DM and AM configured to be displayed on a given win-
dow. When you start these applications from the Workspace menu, the instance of the application
that is started is determined in the following order:
FoxView, DM, or AM specifically configured for that window
FoxView, DM, or AM configured for multiple monitors including that monitor
FoxView, DM, or AM with the default monitor configuration, that is, a floating (non-
dedicated) instance.
10
Windows Off Mode

When you run a WP51/AW51 in Windows Off mode, only one FoxView/DM or AM is
allowed on the local monitor of a single-headed WP51/AW51. The default FoxView/DM starts
up on the local monitor at boot time. When an AM is started from the I/A Series environment,
the AM runs in the foreground.
On dual-headed WP51/AW51 workstations, the additional FoxView/DM must be configured to
start up on the second monitor at boot time. This is the only way to bring up a FoxView/DM
window on the second head of a dual-headed workstation in Windows Off mode.
The Usage does not allow additional FoxViews/DMs to be started from local monitors of a
WP51/AW51 station running in Windows Off mode.
Additional FoxViews/DMs or AMs, if configured, can be called up on remote terminals running
the X-Window System. For additional information, refer to the section Remote FoxViews, DMs
and AMs on page 12.
Windows Workstations
An additional FoxView can be started by clicking Additional FoxView in the File menu. An addi-
tional FoxView window appears.
If the additional FoxView has not been configured in the dmcfg file, an error message stating that
FoxView is not available appears.
Stopping Additional FoxViews, DMs and AMs

50 Series Workstations
The additional FoxViews/DMs can be stopped from the Usage display by selecting the
DMNAME and then selecting the STOP button.
Only manually started DMs can be stopped from the Usage display.
Additional manually started AMs can be stopped from the Alarm Manager File pull-down menu
using Exit or Dismiss from the last opened AM Display or Quit from the window Control menu.
Windows Workstations
The additional FoxView can be stopped by clicking Exit in the File menu to close and exit the
additional FoxView.
Only manually started FoxViews can be stopped from the File menu.
Dedicated FoxViews, DMs and AMs and Licensing

A dedicated FoxView/DM or AM has a reserved license that cannot be used by non-dedicated
FoxViews/DMs or AMs. For example, if a WP/AW is licensed for four FoxViews/DMs and you
have configured six of them in the dmcfg file, four of which are dedicated, you will not have any
licenses left for the two non-dedicated ones even if the dedicated ones are not active.
11
Remote FoxViews, DMs and AMs

You can call up a FoxView/DM or AM on a remote terminal running the X-Window System. For
detailed information on how to start up and use remote FoxViews/DMs, refer to:
50 Series X Client/Server Support (B0193NV)
Server 70 and Model P95 System Administration Guide (Windows NT Server 4.0,
Terminal Server Edition) (B0400AS).
By default, all configurators under the Config menu selection are disabled for remote
FoxViews/DMs. You can enable these menu selections. Chapter 5 Pull-Down Menu Access Con-
trol explains how to enable menu selections.
The configurators that use peripherals (diskette drives, tapes, and so on) for some of their func-
tions, cannot use peripherals connected to the remote terminals. Only peripherals connected to
the stations on the I/A Series network are accessible from these configurators.
Some of the configurators create temporary files in the directory /var/tmp on a WP51/AW51
disk, and therefore, need write permission to this directory when running remotely. To provide
write permission, enter the following command at the WP51/AW51 console:
chmod 777 /var/tmp
The Process Summary Reporter (PSR) requires permission to create files in the directory
/usr/fox/psr/files. To provide write permission, enter the following command at the WP51/AW51
console:
chmod 777 /usr/fox/psr/files
Dynamic Resource Allocation

With multiple instances of FoxView/DM running on a WP/AW station, a dynamic resource allo-
cation scheme is used in order to optimize the performance of the workstations. Each DM is
assigned a Resource Allocation Level (RAL) that determines the rate at which it updates the dis-
plays.
The Resource Allocation Levels (RALs) range from 0 to 20 and are a function of DM Class. A
FoxView/DM with lower RAL updates displays faster than the one with the higher RAL. Gener-
ally, a FoxView/DM with RAL = X would update displays twice as fast as a DM with RAL = 2X.
The RAL of 0 is reserved for the default DM.
Following are the default Resource Allocation Levels (RALs):
DM Class Resource Allocation Level (RAL)

Default DM 0
B 1
O 1
E 2
V 10
12
A FoxView/DM will dynamically adjusts its RAL upwards or downwards between 1X to 5X of the
initial RAL with an absolute maximum RAL of 20. This dynamic adjustment is based on system
CPU load and is not performed unless the CPU load goes above 70%. As long as the CPU load
remains above this threshold, the RAL is increased until the maximum of 5X or 20 RAL is
reached. If the CPU load goes below the threshold, the RAL is decreased until its initial value is
reached.
Examples:
A FoxView/DM with initial RAL=1 adjusts its RAL in following increments:
1 1x1
2 1x2
3 1x3
4 1x4
5 1x5
A FoxView/DM with RAL=4 adjusts its RAL as follows:
4 4x1
8 4x2
12 4x3
16 4x4
20 4x5
Instructions for Editing the Initial RALs

If necessary, although not recommended, you can modify the default RAL using the procedure
described below. Only RAL of 1 to 10 can be specified. RALs of 11 to 20 are strictly used by
FoxView/DM to dynamically adjust its RAL based upon the CPU idle time (100% - CPU
load %).
Each DM class has an associated initial RAL. These values are defined as read-only variables:
DM_DLEVEL=0 # default level for default DM

DM_BLEVEL=1 # default level for DM class B(oot)
DM_OLEVEL=1 # default level for DM class O(perator)
DM_ELEVEL=2 # default level for DM class E(ngineer)
DM_VLEVEL=10 # default level for DM class V(iew)
To change these values, edit the file /usr/fox/wp/data/init.user. For example, if the initial level for
DM class E is to be changed from 2 to 4, enter the following line in the init.user file:
DM_ELEVEL=4
Edits take effect after the next reboot.
13
Accessing WP51/AW51 CPU Idle Time and RAL for DMs

You can access the CPU idle time for a workstation and RAL for DMs by reading the following
shared variables:
WPIDLE<stationlbug> An Object Manager shared variable of type float containing

the current CPU idle time for the station.
DMLEVEL<dmname> A long integer Object Manager shared variable containing the
current RAL for each DM. This variable may be trended or
used on a user-built display.
To conserve CPU cycles, by default the above variables are not set by FoxViews/DMs and are
initialized to -1. To turn on the setting of these variables by FoxViews/DMs, run the following
command for each FoxView/DM:
pref -dmname dmcmd enable monitor
To turn off the setting of the above shared variables, run the following command:
pref -dmname dmcmd disable monitor
Security
Configuring multiple FoxViews, DMs and AMs also requires security considerations. For infor-
mation on general security issues, refer to:
50 Series X Client/Server Support (B0193NV)
Server 70 and Model P95 System Administration Guide (Windows NT Server 4.0, Ter-
minal Server Edition) (B0400AS).
There are several ways in which to limit access to the FoxView/DM and to individual functions
within it.
Limiting Access to FoxView, DM, or AM from Remote Terminals

The window of a dedicated FoxView, DM or AM can only be displayed on the terminal(s) to
which it is dedicated. Assigning one of these to specific terminals limits its access to only these
terminals. Only non-dedicated ones are accessible from any terminal.
The following is an example of a dmcfg file with DMs limited to local terminals and AMs avail-
able to local terminals and a specific remote terminal.
#
#TYPE <type> <window <class> <environment>
attributes>
#
TYPE Operator - B Proc_Op_Env
TYPE AuxillaryOper QLRSM O Proc_Op_Env
TYPE RemoteOperator - O Proc_Op_Env
TYPE Engineer - E Proc_Eng_Env
14
TYPE View_Only - V -
#
#AMTYPE <type> <class> <environment>
#
AMTYPE Operator B Proc_Op_Env
AMTYPE AuxillaryOper O Proc_Op_Env
AMTYPE RemoteOperator O Proc_Op_Env
AMTYPE Engineer E Proc_Eng_Env
AMTYPE View_Only V -
#NAME <lbug> <dmname> <dedicated <type>

monitor(s)>
#
NAME WP5100 WP5100 .0 Operator # 1st local head
NAME DM0001 .1 Operator # 2nd local head
NAME DM0002 .- AuxillaryOper # either local head
#AMNAM <lbug> <amname> <dedicated <type>

E monitor(s)>
#
AMNAME WP5100 WP5100 .0 Operator # 1st local head
AMNAME AM0001 .1 Operator # 2nd local head
AMNAME AM0002 .- AuxillaryOper # either local head
AMNAME AM0003 term1 View Only # term1 only
The following example includes an additional DM dedicated to a specific remote terminal.
#
#TYPE <type> <window attributes> <class> <environment>
#
#
15

monitor(s)>
#
NAME DM0003 term1 Engineer # term1 only
In this example, DM003 can be invoked from the remote terminal TERM1 only. All other
remote access is disabled. Also note that DM0003 cannot be invoked on either local head.
In this final example, the Display Manager DM004 is available for general remote access, and
DM0003 is now available on either local head.
#
# SCREEN <screen_variable> <monitor1> <monitor2>....
#
SCREEN ENG term1 .- # terminal term1 and either local head
#
#
#

monitor(s)>
#
NAME DM0003 $ENG Engineer # term1 or local
NAME DM0004 - View_Only # anyone
16
Limiting Access within a DM or AM

All remotely displayed FoxViews, DMs and AMs provide the following initial protections, regard-
less of configured type:
Setting of control processor parameters is disabled
Access to all configurators and most applications is disabled
Accessing the Alarm Display does not silence the annunciator horn
Clearing alarm from the Alarm Display is disabled
Redirection of displays from the Alarm Display is disabled
Acknowledging alarms from the Alarm Display is disabled
Muting/unmuting horns from the Alarm Display is disabled.
Each of these initial protections may be modified from within the FoxView, DM, or AM. The
recommended way to accomplish this is within password-protected environments that use the
access lock mechanism within the FoxView/DM. Access locks are a standard protection feature,
which can be used in display files and menu pull-down files to disable access to individual fields
within displays and pull-down menus. Access lock protection is configured for display files
through the Display Configurator or FoxDraw software application (FoxDraw), and for pull-
down menus through the ASCII file .pulldown within the referenced subdirectory.
NOTE
Access locks for AM command buttons and menu bars fields and pull-down menus
for the Alarm Manager are configured via the Alarm/Display Manager Configura-
tor. Refer to Workstation Alarm Management (B0193RV).
Environment files are FoxView/DM script files that use display commands. For more informa-
tion, refer to Display Commands (B0193DF) or Display Engineering Utilities (B0193WU).
The following example illustrates the use of access locks, and uses the dmcfg file from the previous
example.
#
#
SCREEN ENG term1 .- # terminal term1 and either local head
#
#
17
#
monitor(s)
#
NAME DM0003 $ENG Engineer # term1 or local
NAME M0004 - View_Only # anyone
In this example, each referenced environment has been password-protected, and the initial envi-
ronment, Init_Env, has been modified to protect (or lock) all access levels. (The initial environ-
ment, Init_Env, is loaded by each Display Manager before the environment that is optionally
configured in the dmcfg file.)
In addition, this example uses the following access lock assignments:
120 - 129 Engineering functions
130 - 139 Operator functions
100 Standard remote Display Manager protection lock
These environments contain the following commands:

Init_Env:
dmcmd nologscr # delay oaj logging until after password

dmcmd passwd # verify password, exit if invalid
dmcmd chng_env # successful password, log oaj
protect all # Initially, protect all access locks

unprotect value 0 # Enable lock 0
disable omsets # Disable changing Control Process variables
# and clearing alarms from CAD
dmcmd button 0 Sys /usr/fox/sys

dmcmd button 1 Alarm dmcmd rcntalms
dmcmd button 2 Help /usr/Help
dmcmd button 3
dmcmd button 4
dmcmd button 5
dmcmd button 6
dmcmd button 7
dmcmd button 8
dmcmd button 9 Select dmcmd stddisp
18
Proc_Oper_Env:

unprotect value 0,130-139 # Enable lock 0, and Oper locks
enable omsets # Enable changing Control Process variables

dmcmd button 1 keep
dmcmd button 2 keep
dmcmd button 3
dmcmd button 4 Disp /usr/menus
dmcmd button 5 Disp_1 /usr/menus/d1
dmcmd button 8 keep
dmcmd button 9 keep
Proc_Eng_Env:

unprotect value 0,100,120-129,130-139
# Enable lock 0, remote lock 100, Eng and
Op locks
enable omsets # Enable changing Control Process variables

dmcmd button 1 keep
dmcmd button 2 keep
dmcmd button 3 Config /usr/fox/config
dmcmd button 7 SftMnt /usr/fox/soft
dmcmd button 8 keep
dmcmd button 9 keep
19
These environments may be accessed from any Display Manager. For example, although the
Proc_Eng_Env is the default environment only for DM0004, this environment may be accessed
through any Display Manager. Since the environment is password-protected, only users knowing
the engineers password have access to the enabled functions within this environment. In a similar
manner, the Proc_Op_Env environment enables all operator functions that may have been dis-
abled, and is accessible only to users knowing the operators password. These environments are
accessible within Alarm Manager for those users with knowledge of the passwords.
NOTE
Although the above examples are for Display Manager, you can use the same com-
mands in FoxView environments.
If the access lock feature is to be used to disable display pick fields, these fields must be configured
through FoxDraw for FoxView or the Display Configurator for the Display Manager. For more
information, refer to FoxDraw (B0193WG) or Display Configurator (B0193AR).
Using access locks for pull-down menu protection requires editing or creating ASCII files within
the directories to be accessed by the top menu button. Refer to Chapter 5 Pull-Down Menu
Access Control in this document.
From the previous example, notice that the files found under the /usr/fox/config and /usr/fox/soft
directories (buttons 3 and 7) are only accessible from the Proc_Eng_Env environment. These
directories are not included in any other environment, and in fact, buttons 3 and 7 are either
redefined or removed in the Init_Env and Proc_Op_Env environments.
Both the Proc_Eng_Env and Proc_Op_Env environments have access to the files under
/usr/menus. However, it is possible to selectively protect individual entries within this directory
structure based on access locks.
In the following example, only the engineer has access to the subdirectory Engineer. Both the
operator and engineer have access to the subdirectory Boiler and the file Maintenance. All users
have access to all other files.
Directory Structure:
/usr/menus d1 subdirectory
d2 subdirectory
d3 subdirectory
d4 subdirectory
Engineer subdirectory
Boiler subdirectory
Overview display file
Maintenance display file
The file /usr/menus/.pulldown looks like this:
Overview
Boiler -p 130
Engineer -p 120
Maintenance -p 130
20
Note that the subdirectories d1 through d4 have not been included in the .pulldown file. These
entries are located in the pull-down menu after the entries specifically defined in the
.pulldown file.
Any environment that unprotects access locks and is accessible to all users should be password-
protected. The utility /usr/fox/wp/bin/tools/dmsepass is used to add/modify environment
passwords.
21
22
4. ExpertSelect
This section describes the Display Manager ExpertSelect feature and enhanced command
functionality which are included in I/A Series software release 4.0 and later. These features
allow a display object to be selected through a display command, without an operator actually
picking the object on the screen. Picking a display object causes the action that was configured
for that object to be executed.
Appropriate detail displays and faceplates that have ExpertSelect functionality configured by
default are provided. This functionality can be easily removed by editing the file
/usr/fox/wp/data/init.user. WP51/AW51 displays that contain these faceplates can be converted
to WP30 format without any warning messages or loss of configuration information. Although
ExpertSelect is not available on the WP30, the configuration information within the faceplates is
ignored by the WP30 Display Manager.
Display Manager ExpertSelect Functionality

The ExpertSelect feature provides an interface for a display object to be selected, through a display
command, without having an operator actually pick the object on the screen. As a result of pick-
ing the display object, the action that was configured for that object is executed. This is typically
setting a relative pick and highlighting the display object. This feature may be used as part of the
display call-up process. You can configure a display to automatically select a specified graphic
object. You can use this feature in any display command, not only when initiating a display.
In addition to selecting display objects from display commands, you can make conditional picks,
based on current values of control processor parameters. The FoxView/DM can retrieve control
processor variables, and interpret and process their values within display command lines.
To simplify configuration, display commands to be executed as part of the display call up process
can be embedded within the display files. This eliminates the need to generate separate display
scripts for each display file, and allows the ExpertSelect function to be permanently associated
with the display file.
To illustrate the capabilities of these features, two examples of an ExpertSelect implementation are
shown in Figure 4-1 and Figure 4-2. Figure 4-1 shows a generic overlay, configured with an
embedded script. When the overlay is called up, the processing of the embedded script pre-picks
either the output or setpoint relative pick, based on the current value of the .MA parameter.
Figure 4-2 shows a base display file, with two faceplates. There is no embedded script in this dis-
play, but each faceplate descriptor field is configured so that when the descriptor field is selected,
either the setpoint or output relative pick is also selected. The operator does not need to make the
decision about which relative pick to select; selecting the descriptor field always selects the correct
relative pick.
The ExpertSelect features are incorporated into the Display Manager Command language sup-
port. Each of the features is discussed separately in the following sections.
23
B0193MQ Rev M 4. ExpertSelect
Evaluation of Object Manager Data Values in Display

Commands
The display command backquote syntax permits evaluation of Object Manager data values. The
syntax c:b.p within a FoxView/DM command line is interpreted as a request to retrieve the value
of c:b.p from the Object Manager, and insert its value into the command line. The following are
some examples of the use of this syntax:
== CMP:BLK.MA 1 e /usr/menus/display1 # if .MA is set call display1
!= CMP:BLK.MA 1 e /usr/menus/display2 # if .MA is not set call display2
Bit extensions are allowed in the backquote () expression. The value of a parameter with bit
extension is always either 0 or 1. By using bit extensions, the previous example could have been
configured as:
== CMP:BLK.ALMSTA.AMA 1 /usr/menus/display1 # if .MA is set call display1
!= CMP:BLK.ALMSTA.AMA 1 /usr/menus/display2 # if .MA is not set call display2
In addition, an optional second argument is allowed within the backquote expression. The second
argument in the .PARAM name is to be used with the CMP:BLK specified in the first argument.
This supports the $PICK1 functionality. The previous example could also have been configured
as:
= PICK1 CMP:BLK.OUT # .OUT parameter is picked
== $PICK1 .BLKSTA.AMA 1 /usr/menus/display1 # if .MA is set call display1
!= $PICK1 .BLKSTA.AMA 1 /usr/menus/display2 # if .MA is not set call display2
The evaluation of the backquote expression gets converted into an ASCII integer. For example, if
CMP:BLK.MEAS is currently 85.538, then the expression:
= P8 CMP:BLK.MEAS
expands to:
= P8 86
which sets the WP variable P8 to 86.
When evaluating display command lines, the FoxView/DM first expands any $ expressions,
then the expressions. For example, if:
P8 = CMP1:BLK.P1
and
P7 = CMP2:BLK.P2
then
setb $P8 $P7
expands to
setb CMP1:BLK.P1 CMP2:BLK.P2
which sets CMP1:BLK.P1 to the current value of CMP2:BLK.P2.
Nesting of backquote expressions is not supported. For example, the following is not allowed:
setb CMP1:BLK.P1 C:B.P #this is invalid!
All command lines may contain backquote references. The backquote syntax supports shared vari-
ables in addition to control processor variables.
24
4. ExpertSelect B0193MQ Rev M
If the backquote expression can not be evaluated, the command is aborted and a message is dis-
played on the top message line. Examples of this condition are:
invalid C:B.P syntax
point is not found on the network
Support for Named Actions

Active connections may be given action names that are used in the display command pick to
reference a specific active connection within a display file. Action names are configured within
FoxDraw or the Display Configurator.
Action names must be unique within a display file. The best way to ensure uniqueness is to
include action names within display groups that are added to display files using the Import and
Configure feature in the Display Builder. Refer to Display Builder (B0193AQ) for details.
Display Commands Embedded in Display Files

Display files may include embedded post call-up DM commands, that are executed as the last
step in calling up a display. These embedded commands are part of the display file itself, and are
not contained in a separate display script file. The embedded commands are executed as though
they were contained in a display script.
For FoxView, these commands are configured with FoxDraw. Refer to FoxDraw (B0193WG).
For Display Manager, these commands are configured with the Display Builder Display Embed-
ded Script dialog box, accessed from the ATTRIBUTES menu. Each command line in the dialog
box can be up to 80 characters long, with a limit of 10 command lines per display. Embedded
script commands may also be imported into the display file from an existing DM script file. The
name of the imported script is saved in the display file, in addition to the actual script commands.
Imported commands may be edited after being imported. Refer to Display Builder for 50 Series
Workstations (B0193MP) for information on embedded scripts.
25
Examples
TO OPERATE:
Call Overlay from base display.
The SPT or OUT will be automatically selected.
Perform required operation using buttons at bottom of base display.
Embedded Post Call-up Script:
Operation: If BLOCK1 is in manual, pick output

else if BLOCK1 is in local, pick setpoint
Actual Script: = P1 COMPOUND:BLOCK1

== `$P1.MA` 0 pick $P1.OUT else == `$P1.LR` 0 pick $P1.SET
Pick Operation: If BLOCK1 is in manual, pick output

else pick header
Active Connection: Set relative pick

Configured Path: = PICK1 COMPOUND:BLOCK1
== `$PICK1.MA` 0 pick $PICK1.OUT
else == `$PICK1.LR` 0 pick $PICK1.SET
GENERIC OVERLAY
Pick Operation: Set relative pick to SPT

DESCRIPTION
COMPOUND Action Name: COMPOUND:BLOCK1.SET
BLOCK1 ALM
Configured Path: = PICK1 COMPOUND:BLOCK1.SPT
MEAS
50.00
SPT
Pick Operation: Set relative pick to OUT
50.00
OUT
80.00 Action Name: COMPOUND:BLOCK1.OUT
Configured Path: = PICK1 COMPOUND:BLOCK1.OUT
L A
R M
Figure 4-1. Generic Overlay Using ExpertSelect Functionality
Figure 4-1 is a generic overlay. When called from a base display, the WP variable P1 is set to the
desired compound and block name. The overlay contains an embedded script, which selects
either the output or the setpoint, based on the value of the .MA parameter. This is done as part of
the display call-up sequence. This means that the selecting of the output or setpoint is performed
before any operator actions are processed.
26
4. ExpertSelect B0193MQ Rev M
NOTE
In the command == `$PICK1 .MA` 0, $PICK1 and .MA are separate words.
TO OPERATE:
Select the Faceplate Header.
The SPT or OUT will be automatically selected.
Perform required operation using buttons at bottom of base display.

Configured Path: = P1 COMPOUND:BLOCK1
== `$P1.MA` 0 pick $P1.OUT
DESCRIPTION
else == `$P1.LR` 0 pick $P1.SET
COMPOUND
BLOCK1 ALM
MEAS
50.00
Action Name: COMPOUND:BLOCK1.SET
SPT Configured Path: = PICK1 COMPOUND:BLOCK1.SPT
50.00
OUT Pick Operation: Set relative pick to OUT
80.00 Active Connection: Set relative pick

Action Name: COMPOUND:BLOCK1.OUT

Configured Path: = PICK1 COMPOUND:BLOCK2
DESCRIPTION == ` $PICK1.MA` 0 pick $PICK1.OUT
else == ` $PICK1.LR` 0 pick $PICK1.SET
COMPOUND
BLOCK2 ALM
MEAS
Action Name: COMPOUND:BLOCK2.SET
SPT
Configured Path: = PICK1 COMPOUND:BLOCK2.SPT
50.00
OUT Pick Operation: Set relative pick to OUT
Action Name: COMPOUND:BLOCK2.OUT
L A
R M
Figure 4-2. Group Display Using ExpertSelect Functionality
27
Figure 4-2 shows part of a group display. There is no embedded script configured for this display,
but each faceplate header (the box containing the descriptor and control block name) is config-
ured to select the appropriate relative pick field. The operator always selects the header, and either
the output or setpoint is selected.
Detail Displays and Faceplates

Detail displays and faceplates contain ExpertSelect functionality by default. To view the entire list
of WP variables used in ExpertSelect functionality in detail displays and faceplates, refer to file
/usr/fox/wp/data/wp51_glbls.all.
Variables ending in _DD are used in detail displays; those ending in _FP are used in faceplates on
user-built displays.
The logic for the PID variables:
if MA == 0, select the OUT relative pick
else if LR == 0, select the SPT relative pick.
The logic for the AOUT variables:
if MA == 0, select the OUT relative pick.
The logic for the MLS variables:
select the OUT relative pick.
For the exact configuration of these variables, see the file /usr/fox/wp/data/wp50_glbls.
NOTE
The A/M and R/L buttons on detail displays and in the BUTONS_40 button set
are also configured for ExpertSelect. These buttons execute the ExpertSelect logic
when selected.
To remove ExpertSelect functionality from these displays/faceplates, the associated variables can
be redefined in the /usr/fox/wp/data/init.user file to <null>. For example:
PID_DD=
removes the definition of PID_DD, thereby removing ExpertSelect from the PID family of detail
displays.
28
5. Pull-Down Menu Access Control
This chapter describes how you configure pull-down menus. This capability is achieved through
the use of the .pulldown file.
You may need to selectively disable/enable entries in FoxView or DM pull-down menus. To
accomplish this, the FoxView/DM reads an optional pull-down file found within the directory
being accessed by the pull-down menu. The .pulldown file provides the following functionality:
Allows entries within a pull-down menu to be inactive (non-pickable) based on
assigned access levels. Pull-down entries cannot be deleted, only made inactive.
Allows specification of potential menu entries
Allows ordering of entries within the pull-down menu
Provides blank entries and leading blanks in menu entries (DM only)
Allows specification of menu entry colors (DM only).
The .pulldown file can have entries that are not actually found in the directory. Entries in the
pull-down menu that are not actually found in the directory are not included in the pull-down
menu.
The .pulldown file is optional. If the file is not found, Display Manager creates the pull-down
menus. All entries in the directory (up to 255) are displayed and enabled in the pull-down menu.
Invensys Foxboro provides default .pulldown files for each directory that is referenced in the stan-
dard environment files. These files contain access level protection for all single-instance applica-
tions, the Usage display, and all configurators. The access level used is 100.
Menu entries can be made active (pickable) or inactive (unpickable) through access levels. The
Display Manager commands protect and unprotect are used to control the access levels.
.pulldown File
The .pulldown file is an ASCII file found within a directory accessed by FoxView/DM top menu
entries. It contains a list of lines in the following format:
filename [options]
where:
filename Name of directory entry. Leading white space characters are supported,
such as filename or . If there is no filename, a blank non-pickable entry
is added to the pull-down menu.
options Properties of the directory entry. This field is optional.
-p level Makes entry inactive if access protection level has been protected.
29
B0193MQ Rev M 5. Pull-Down Menu Access Control
-c color Foreground color of menu entry. Default color is:

(DM only) HI_YELLOW.
1 = HI_RED
2 = HI_GREEN
3 = HI_YELLOW
4 = BLUE
7 = WHITE
Examples
In the following examples, the vi editor is used for editing. Editing is done on a 50 Series WP/AW
workstation using the VT100 emulation mode.
Disabling Pull-Down Menu Picks

To disable all Display Manager DM0001 pull-down menu picks assigned an access level of 100,
run the following command:
pref -DM0001 dmcmd protect value 100
All disabled pull-down menu picks are cyan colored.
Enabling Pull-Down Menu Picks

To enable all Display Manager ADM002 pull-down menu picks assigned an access level of 100,
run the following command:
pref -ADM002 dmcmd unprotect value 100
You can disable or enable more than one access level at the same time. For example, to enable
pull-down menu picks within a range of 100-110 for Display Manager ADM002, use the follow-
ing command:
pref -ADM002 dmcmd unprotect value 100-110
Changing the Color of Pull-Down Menu Picks (DM Only)

To change the color of the Change_Env pick to green and Reboot_Station pick to red:
1. Enter vi /usr/fox/sys/.pulldown.
2. Edit the lines for the Change_Env and the Reboot_Station entries as follows:
Change_Env -c 2 /* color index 2 = green */

Reboot_Station -c 1 -p 100 /* color index 1 = red; Reboot_Station is
assigned an access level = 100 */
3. Save the .pulldown file.
30
5. Pull-Down Menu Access Control B0193MQ Rev M
Inserting Space Between Pull-Down Menu Picks (DM Only)

To insert space between the AlarmHistory and the Change_Env pull-down picks under the Sys
menu pick:
1. Enter vi /usr/fox/sys/.pulldown.
2. Insert (pair of double quotes) between the AlarmHistory entry and the
Change_Env entry as follows:
AlarmHistory

Change_Env
Indenting Pull-Down Menu Picks (DM Only)

To indent the Display_Build and the Display_Cfg picks under the Config menu pick:
1. Enter vi /usr/fox/config/.pulldown.
2. Edit the lines for the Display_Build and the Display_Cfg as follows:
Display_Build
Display_Cfg
31
B0193MQ Rev M 5. Pull-Down Menu Access Control
32
6. Configuring and Assigning
Passwords for FoxView
Environments
This chapter covers modifying environment definition files and assigning environment
passwords.
FoxView comes with a set of environments that are suitable for your use, but it is recommended
that you create your own environments tailored to your control system and its users. The default
FoxView environment files found in \opt\fox\env can be modified to include custom menu bars,
pull-down menus, display bars, and security or used to create new environments. The following
definition files are found in the \opt\fox\env directory:
Environment definition files (.env)
Access level files (.acl) for each environment
Menu bar files (.mbr) for each environment
Display bar files (.dbr) for each environment
Menu files (.mnu) for the each of the pulldown menus (File, View, Help).
Additionally, passwords may be assigned to each environment.
Environment Definition Files

Each environment has its own environment definition file that defines the environment:
Initial environment (\opt\fox\env\initial.env)
Operators environment (\opt\fox\env\Operator.env)
Process Engineers environment (\opt\fox\env\Process_Eng.env)
Software Engineers environment (\opt\fox\env\Software_Eng.env).
For example, the default Initial environment file contains:
dmcmd nolog_script #Stops logging to OAJ prior to password checking
dmcmd passwd
dmcmd chang_env
\opt\fox\env\Initial.acl #Access Level Definition File
\opt\fox\env\Initial.mbr #Menu Bar Definition File
\opt\fox\env\Initial.dbr #Display Bar Definition File
#Name of Display Associated with Environment Callup
The lines in the Initial environment file perform the following tasks:
dmcmd nolog_script
Is a script file that stops logging to the Operator Action Journal.
33
B0193MQ Rev M 6. Configuring and Assigning Passwords for FoxView
dmcmd passwd Checks for configured password for this environment. This is found in the
/usr/fox/wp/data/dmpasswd_cfg file.
dmcmd chang_env
Clears the existing menu bar.
\opt\fox\env\Initial.acl
Calls in the script file containing the access protection levels.
\opt\fox\env\Initial.mbr
Calls in the script file containing the menu bar entry definitions.
\opt\fox\env\Initial.dbr
Calls in the script file containing the display bar definitions.
dmcmd <display filename path> #Name of the Display associated with
Environment Callup
All other environment files are similar, but each calls in a unique set of files (.acl, .mbr, .dbr files)
containing access levels, menu bar definitions, and display bar definitions that are specific to that
environment.
Access Level File

The purpose of the access file is to indicate which level, levels, or range of levels are protected and
unprotected for the associated environment. To protect access to pull-down menu entries or dis-
play buttons within an environment, access levels must be assigned in the .pulldown file or in the
display file. Additionally, Display Commands, disable and enable, can be used to disable DM sets
of variables that include actions such as ramping, alarm acknowledgment, data entry of values, as
well as the set DM commands. Refer to Display Manager Commands (B0193DF) for additional
information on the following commands: disable, enable, protect, unprotect, setacl (50 Series ref-
erences) and the FoxDraw Help file for protection ID information.
The access level definition files are:
Initial.acl
Operator.acl
Process_Eng.acl
Software_Eng.acl.
For display areas, such as buttons, to be protected or unprotected:
Assign protection IDs using the FoxDraw application
Enter the desired protect/unprotect commands in the access level files.
In the access level file for the environment, enter the protect and unprotect commands related to
the protection ID or access level assignments. The following syntax for protect and unprotect is
used:
dmcmd protect [all/value[range]]
dmcmd unprotect [all/value[range]]
where:
all Protects/unprotects all areas
34
6. Configuring and Assigning Passwords for FoxView Environments B0193MQ Rev M
value[range] Specifies the levels to be affected in the following format:

a = single value
a,c = indicate multiple values
a-d = range from a to d
a,c-e = combination of a single value and a range
a,c,e-g = combination of multiple values and a range.
When you use the .acl file to restrict access in an environment, place the .acl file before the menu
bar definitions (.mbr) file so that the access levels become effective on the new menu bar.
Examples
If you want to make the Auto/Manual button on a display inaccessible in the Initial Environment,
assign an access level code to it and then set up the Initial.acl file.
To assign a protection ID to the Auto/Manual button, access FoxDraw and proceed as follows:
1. Select the desired display, and click the Auto/Manual button.
2. From the Object menu, select Configure Objects.
3. In the Configure Objects dialog box, click the Operator tab.
4. Click Add and select an Operation Action.
5. In the Protection ID field, assign a non-zero value, 1 in this example, to the area. The
range of values is 0-255. Zero is the default setting, which makes the area accessible in
all environments.
To set up the Initial.acl file, access the \opt\fox\env\Initial.acl file.
Enter the following information related to disabling access to the Auto/Manual
button:
dmcmd script #Identifies this as a script file.
dmcmd unprotect all #Clears existing protections from the initial environment.
dmcmd protect value 1 #Makes all objects with a protection ID of 1 inaccessible.
The default Initial.acl file uses the DM call disable to prevent users from clearing alarms from the
Current Alarms display and the alarm database from the Initial environment. The file contains
the following:
dmcmd script
#script containing protection levels for Initial environment
dmcmd disable clralm #disable clearing alarms from CAD
The default Process_Eng.acl file uses the DM call enable to allow users to clear alarms from the
process engineers environment.
dmcmd script
# script containing protection levels for Process_Eng environment
dmcmd enable clralm # enable clearing alarms from CAD
Menu Bar Definition File

Each environment has its own menu bar definition file that defines the menu button commands,
which can point to another file or to a directory:
35
Initial.mbr
Operator.mbr
Process_Eng.mbr
Software_Eng.mbr.
The syntax is:
dmcmd button -1 &Label file
where:
-1 Indicates button position and is used as a place holder to make the com-
mand backward compatible.
&Label Identifies the label to be associated with the button.
file Identifies the file containing the contents of the pull-down menu.
NOTE
There is no restriction on the number of menu labels or the length of the label text.
Example
The default Initial menu bar definition file contains:
dmcmd script
dmcmd button -1 &File \opt\fox\env\file.mnu
dmcmd button -1 &Help \opt\fox\env\help.mnu
The lines in the Initial environment file perform the following tasks:
dmcmd script
Identifies this file as a script file.
dmcmd button -1 &File \opt\fox\env\file.mnu
Is the standard command line to place a menu button (File) on the menu
bar. Definition files or subdirectories are supported.
dmcmd button -1 &Help \opt\fox\env\help.mnu
Is the standard command line to place a menu button (Help) on the menu
bar.
Menu Button Definition Files

The menu definition file for each menu button contains commands, directory references, and/or
references to other menu definition files:
\opt\fox\env\file.mnu
\opt\fox\env\view.mnu
\opt\fox\env\help.mnu.
All menu definition files must start with the keywords pulldown foxview menu.
36
Examples
The file.mnu contains the following commands:
pulldown foxview menu
Change &Environment...Ctrl+E chng_env_dlg #Calls Change Environ. Dialog Box
"&Select Screen..." "stddisp" #Accesses Select Screen
"Separator" "separator" #Adds dotted separator line
&Print...Ctrl+P psc_dlg #Accesses Print Dialog Box
Additional &FoxView run $WPBIN/dm.exe #Opens a second FoxView window
&1 MRU MRU1 #Accesses current display
&2 MRU MRU2 #Accesses previous display
&3 MRU MRU3 #Accesses second previous display
&4 MRU MRU4 #Accesses third previous display
"&Exit" dmexit #Exits additional FoxView window
The help.mnu file contains:

"Contents" "help contents" #Provides Table of Contents for Help file
About FoxView about FoxView #Provides FoxView Vers information
Display Bar Definition Files

Each environment has its own display bar shown vertically at the left side of the screen. There are
two templates available:
Button version which displays 18 buttons that can be configured to call up a display
or execute a FoxView command.
Icon version which displays up to 8 bitmaps of displays which can also be configured
to call up a display or execute a FoxView command.
NOTE
Display files referenced within a display bar definition file must have corresponding
bitmap files. The files accessed via the display buttons or the mini-display icons
depending on the button template selected.
The display bar definition files are:

\opt\fox\env\Initial.dbr
\opt\fox\env\Process_Eng.dbr
\opt\fox\env\Operator.dbr.
37
The following syntax is used for button command:

dbar_btn button_number button_command [-1 label][-b bitmap_name]
where:
-1 label Indicates the following text is the button label. When no label is specified,
the base name of the display is used for the label.
-b bitmap_name Indicates the following is the name of the bitmap file. If no bitmap is spec-
ified, the .bmp file is assumed to be in the same directory as the .fdf file.
Example
The Process_Eng.dbr contains:
dmcmd script
dmcmd dbar_tmplt $TMPLTS/button_display_bar
dmcmd dbar_button 1 dmcmd chng_env_dlg -1 Change Env
dmcmd dbar_button 2 dmcmd psc -1 Print Screen
dmcmd dbar_button 3 dmcmd stddisp -1 Select
dmcmd dbar_button 4 \opt\menus\demo\Centrifuge
dmcmd dbar_button 5 \opt\menus\demo\Extraction
.
.
.
dmcmd dbar_button 18 \opt\custom\Initial_Disp
The lines in the file perform the following tasks:

dmcmd script
dmcmd dbar_tmplt $TMPLTS/button_display_bar
Identifies the name of the template to be used for the display bar.
dmcmd dbar_button 1 dmcmd chng_env_dlg -1 Change Env
Identifies the command to access the Change Environment dialog box.
dmcmd dbar_button 2 dmcmd psc -1 Print Screen
Identifies the command to print a screen.
dmcmd dbar_button 3 dmcmd stddisp -1 Select
Identifies the command to call up the Select Screen.
dmcmd dbar_button 4 \opt\menus\demo\Centrifuge
Identifies the button to call up a display called Centrifuge.
38
Bitmap Utility
The utility for creating display bar thumbnail bitmaps associated with display files referenced
within a display bar is fdf2bmp.
To create a bitmap for the file \opt\customer\Initial_Disp:
1. Change to the display directory:
cd \opt\customer
2. Run the bitmap utility:
\usr\fox\wp\bin\tools\fdf_bmp -f Initial_Disp
3. The Initial_Disp.bmp file is created.
NOTE
Use the -b option to reference any Windows bitmap in the display bar. See previous
section, Display Bar Definition Files on page 37.
Setting Environment Passwords Utility

The utility for editing Display Manager Environment script file passwords and descriptions is
dmsepass. It can be found in the directory /usr/fox/wp/bin/tools on the 70 Series stations.
The following syntax is used:
dmsepass passwd_id [-p password] [-d description]
passwd_id Is the environment to be affected by password.

password Is the password. No password removes the password.
description Is an optional identifier description.
Example
To edit the password of the Initial Environment to be jackson and change the description, type
the following from a command tool on the workstation:
dmsepass Initial -p jackson -d New password for Initial_Env
The password and description for the Initial Environment is saved in the following file:
/usr/fox/wp/data/dmpasswd_cfg
This is an ASCII file which contains the encrypted password and a description for each environ-
ment. A backup file, passwd_cfg.bak is also created. This file contains the contents of passwd_cfg
previous to the most recent change.
To remove this environment from the password file, type:
dmsepass Initial
The Initial environment now has no password.
NOTE
Passwords are not limited to use in an Environment script file. Any Display Man-
ager script may include the use of passwords.
39
FoxView Shortcut Menu Definition

FoxView invokes a user-defined, context-sensitive, shortcut menu of display commands when you
click the right mouse button on an updating field (see Figure 6-1). You specify the contents of this
menu through menu definition files, similar to the definition files used to specify the contents of
the window menus such as the File, View, Help, and other menus. The use of menu definition
files allows common menu commands to be easily assigned to large groups of updating fields. In
addition to menu definition files, you can configure individual custom menu entries for specific
updating fields.
Configured I/O Point Cascade Menu Cascade Menu
Figure 6-1. Examples of Shortcut Menus
Each shortcut menu command definition starts with an operation code. This operation code
indicates the type of action to be taken when you select the menu command. The operation codes
are described in the following sections. For examples of how these commands can be used in a
shortcut menu, see Examples of Shortcut Menu Definition Files on page 43.
Each operation code is followed by arguments that contain information about the menu
command. Arguments are expressed in the -argument value form. The menu command
format can also include references to the parameter, block type, parameter type, and specific
FoxView targets.
The menu file format supports comments within the file. All text following a # character on
each line is ignored.
Operation codes are:
COMMAND Is a command in display command format.
SEPARATOR Indicates a separator field.
CASCADE Indicates a reference to another menu file.
40
Command Menu Entry

Syntax
COMMAND -label text [-cmd foxview cmd [-p access level]
[-fvname fvname] [-enable condition]]
where:
text Is the text that appears in the menu. This text can be any length, but a
long string makes for a wide menu.
foxview cmd Is the command to be executed when the entry is selected. This command
is in display command format.
access level Is the access protection number(s) associated with the menu entry. If more
than one access level is specified, the access level numbers must be sepa-
rated by only a comma (no spaces).
fvname Is the name of the FoxView to receive the command.
condition Is the condition in which this Menu Item is enabled. Valid conditions are:
base The menu item is enabled when the menu is

opened from a base display.
overlay The menu item is enabled when the menu is
opened from an overlay.
stat The menu item is enabled when the menu is
opened from a stationary overlay.
move The menu item is enabled when the menu is
opened from a moveable overlay.
Description
The Command menu entry displays a text field in the menu to execute a FoxView command
when you select the text field.
label is a required argument. If cmd is missing, the menu entry is selectable, but there is no action
associated with the selection. The arguments p and fvname have meaning only if the
argument cmd is present.
Both label and cmd can contain keywords that are specific to the selected object. The syntax for
referencing these items is described below.
Menu Separator
Syntax
SEPARATOR
Description
The SEPARATOR menu entry displays a separator bar in the shortcut menu.
41
Cascading Menu Entry

Syntax
CASCADE -label text -file filename
where:
text Is the text that appears in the menu. This text can be any length, but a
long string makes for a wide menu.
filename Is the full pathname of the file containing the cascaded menu entries.
Both label and file are required arguments. If one of these arguments is missing, the menu
entry does not display.
Description
The Cascading menu entry allows you to construct a menu that cascades into another menu.
Menu Variables
The following subsections describe the keywords that are recognized by the shortcut menu
subsystem. These variables are not Object Manager or environment variables, but are strictly
keywords that are replaced with string values based on the selected display object. Replacing menu
variables with data values is performed prior to sending the selected menu command to FoxView.
Menu variables can be placed in label and cmd menu arguments. To reference any menu variable
in a menu definition, place a $ in front of the variable.
SELDISP
The menu variable SELDISP can be placed in a menu entry. Before the menu is displayed, this
variable is replaced with the full pathname of the selected display/overlay.
For example, the following menu entry directs the current overlay to another FoxView:
COMMAND -label Send to: FV0001 -cmd ov $SELDISP 1 -fvname FV0001
SELTAG
The menu variable SELTAG can be placed in any menu entry. When a menu entry is selected,
this variable is replaced with the full pathname of the selected parameter. This replacement is
performed prior to sending the command to FoxView.
For example, the following menu definition displays a menu entry labeled Detail. This menu
entry calls in the detail display for the selected parameter. If access levels 100 or 101 are protected,
this menu entry is disabled.
COMMAND -label Detail -cmd stddisp $SELTAG -p 100,101
SELCOMP
The menu variable SELCOMP can be placed in any menu entry. When a menu entry is selected,
this variable is replaced with the actual name of the compound portion of the selected full path-
name. This replacement is performed prior to sending the command to FoxView.
42
SELBLOCK
The menu variable SELBLOCK can be placed in any menu entry. When a menu entry is selected,
this variable is replaced with the actual name of just the block portion of the selected full
pathname. This replacement is performed prior to sending the command to FoxView.
Examples of Shortcut Menu Definition Files

Menu definition files define the layout and commands that appear in the shortcut menu. Shortcut
menus can have DM commands, compound:block.parameter names, and separators to organize
the menu, and they can also include additional cascaded menu lists.
Example 1
The following is a sample default menu definition file. This is only an example, and may not
reflect the exact commands needed to accomplish the desired action.
# Example Shortcut Menu Entry File

COMMAND -label $SELTAG -cmd get_select_pt $SELTAG
COMMAND -label Block Detail -cmd stddisp $SELTAG -p 1,2,100
SEPARATOR
COMMAND -label Previous Display -cmd $ST1
COMMAND -label Overview -cmd /opt/menus/overview.fdf
The sample menu appears as follows.

Compound:Block.Parameter
Block Detail
Previous Display
Overview
Compound:Block.Parameter represents the name of an actual block parameter in the control and
I/O database.
Example 2
The following example menu definition file defines the menus shown in Figure 6-1 on page 40.
COMMAND -label $SELTAG -cmd set_select_pt $SELTAG

COMMAND -label Block Detail Display -cmd stddisp $SELTAG
SEPARATOR
COMMAND -label FoxDraw -cmd run \opt\fox\wp\FoxDraw\foxdraw $SELDISP -fvname DMNAME
SEPARATOR
CASCADE -label DISPLAYS -file /opt/menus/tmplt_Plant/displaylist.mnu
CASCADE -label OVERLAYS -file /opt/menus/tmplt_Plant/overlaylist.mnu
SEPARATOR
COMMAND -label Moveable -cmd ov_switch -move
43
COMMAND -label Stationary -cmd ov_switch -stat

SEPARATOR
COMMAND -label Prev Disp -cmd $ST1
Environment Shortcut Menus

Shortcut menus are customizable menus that open when you right-click in the FoxView display.
Displays and environments can be set up to use the standard FoxView right-click menu that
shows a list of configured I/O points, or they can be set up to use a customized right-click menu.
Environment Shortcut Menu Styles

To define the right-click menu style for an environment, engineers must edit the environment's
.env file. This file is located in either the \opt\fox\env or \opt\customer\env directory.
The DM command shortcut_menu_style must be added to the file:
shortcut_menu_style style
where:
style Is either default or configurable.
shortcut_menu_style default sets the right-click action to open the standard right-click menu
where only a list of configured I/O points are shown.
shortcut_menu_style configurable sets the right-click action to open the new configurable
shortcut menus.
Environment Shortcut Menu Types

You can specify the following two types of shortcut menu files within an environment:
Display Menus Shortcut menus that open when operators right-click in an area of the
FoxView display that is not configured.
Object Menus Shortcut menus that open when operators right-click in an area of the
FoxView display that is configured.
To specify which menu definition file to use for a display or an object within an environment,
engineers must edit the environment's .env file. This file is located in either the \opt\fox\env or
\opt\customer\env directory. Menu files that are defined through the .env file are now the default
menu files. The shortcut menus for displays can be customized through the display property dia-
log box in FoxDraw. The shortcut menus for objects can be customized through the configuration
dialog box in FoxDraw. For more information on the property and configuration dialog boxes,
refer to FoxDraw (B0193WG).
The DM command shortcut_menu must be added to the file:
shortcut_menu -type type -file Menu_filename
where:
type Is either object or display.
Menu_filename Is the name of the menu file to use as the shortcut menu.
For example, the environment file can include the following commands:
44
shortcut_menu_style configurable
shortcut_menu -type object -file $ENV_DIR/obj_eng.mnu
shortcut_menu -type display -file $ENV_DIR/disp_eng.mnu
First, the menu style is set to configurable. The next statement specifies which menu definition
file to use when an operator right-clicks on configured I/O points. In this case it uses the
obj_eng.mnu file located in the environment directory. The third statement specifies which menu
definition file to use when an operator right-clicks in an area that is not configured. It is set to the
disp_eng.mnu file located in the environment directory.
45
46
7. File Access
This chapter describes the search paths that the Display Manager uses to access files.
ia16 Subdirectory on 50 Series AP or AW

All files which are accessed by I/A Series WP20 or WP30 stations are found relative to the direc-
tory /usr/fox/ia16 on a 50 Series AP or AW. For example, if a WP20 or WP30 is to read the dis-
play file:
On an AP20: /usr/menus/blending/tank
The file must be located in:
On an AP50: /usr/fox/ia16/usr/menus/blending/tank
This is transparent to the user of the WP20 or WP30. When building and configuring the dis-
play, there is no mention of the /usr/fox/ia16 sub-path. You need only be aware of this when writ-
ing applications on the AP50 which refer to these files, or when using terminals viewing the
AP50s file system. The exact name of the prefix path may change in future releases. For forward
compatibility, applications which use this path should use the path contained in file
/etc/fox/ia16_world.
Display Manager Search Paths

The 50 Series Display Manager uses the following logic to open and read files:
1. An attempt is made to open the desired file on the local disk.
2. If this attempt fails, an attempt is made to open the file on the Logical Host AP which
is currently mounted.
3. If this attempt fails, a final attempt is made to open a file of the same name and path,
but relative to the /usr/fox/ia16 directory on the same AP as the previous step.
This sequence is followed for all files which the Display Manager reads explicitly, including dis-
play files, scripts, programs, and directories.
The only exceptions are files specifically configured to be called up from remote locations. When
searching for these files, the Display Manager skips Step 1.
Searching can have an adverse impact on display call-up speed, but it does allow for placing files
in a central location on an AP for access by multiple 50 Series workstations.
When call-up speed is critical, you should ensure that copies of desired files are on the 50 Series
WP/AW local disk, and that the displays are converted.
Note that this logic is only for files which the Display Manager reads. It is not used for programs
which the Display Manager may attempt to start and execute, and it does not utilize or change the
PATH environment variable.
47
B0193MQ Rev M 7. File Access
FoxView Search Paths

FoxView uses the following logic to open display files and scripts:
1. If the full pathname of the file starts with /usr, look in /opt before looking for the file
in /usr.
2. If the full pathname does not contain the .fdf extension, this extension is added to the
file name.
For library objects and environment file, FoxView uses the following logic to open the file:
If the full pathname starts with /opt/fox/displib or /opt/fox/env, first look for the file
in /opt/customer/displib or /opt/customer/env.
For detail displays and faceplates, FoxView looks for the enhanced detail displays and faceplates.
If the full pathname starts with /opt/fox/dd or /opt/fox/displib/Faceplates or
/opt/fox/displib/OverlayFaceplates, first look for the file in /opt/fox/dd_1 or
/opt/fox/displib/Faceplates_1 or /opt/fox/displib/OverlayFaceplates_1 as appropriate.
On 50 Series workstations, FoxView also locates files on the remotely mounted logical host. See
Display Manager Search Paths on page 47.
Display Conversion On-the-Fly

When reading an older format display, FoxView or Display Manager automatically converts the
display file to the newer format and calls the display in the display window. The steps for accom-
plishing this are as follows:
Invoke the conversion program to generate a temporary file on the local disk
Call the converted display into the display window
Print a warning message on the message line that the file was converted
Delete the temporary file.
The original file is left untouched because it may still need to be read by the older display applica-
tion, particularly if the file is located on a remote station or a workstation where both FoxView
and DM are running.
This is most likely to occur in the case of programmable logic controller (PLC) displays.
When display call-up speed is important, you should copy the older displays and then convert
them.
On a heavily loaded system, a large display file on-the-fly conversion can cause the Display Man-
ager to time out and an error message to be displayed on the message line. When this happens, the
display file should be converted manually using the appropriate display conversion utility.
On-the-fly conversion of display files is not recommended for day-to-day plant operations. On-
the-fly conversion reduces display call-up speed.
Converting displays using display conversion utilities is a CPU intensive process. Converting a
large directory of displays can take up all of the CPU time for the duration of the conversion pro-
cess and affect the performance of other applications.
48
7. File Access B0193MQ Rev M
NOTE
Converting a single file or two is not a problem.
If you must convert directories/subdirectories of displays, you should pick a time when the system
is in a quiescent state.
Programmable Logic Block (PLB) Ladder Display

Access
The Integrated Control Configurator installs PLB ladder displays in the format required by the
system:
FoxView format on both 50 Series and 70 Series workstations
Display Manager format on 50 Series workstation
20/30 Series format if required by the system.
A Control Configurator running on an AP20 cannot install ladder display files in 50 Series for-
mat. It always installs them in 20/30 Series format.
If the I/A Series system is being upgraded to Release 4.1 or a subsequent release, and PLB ladder
displays have been copied locally for file access speed, these displays may be removed from the
workstations local disk and/or logical host disk to free up hard disk space, but only if these disks
are not the location for the Control Configurator installed files.
NOTE
The 70 Series FoxView cannot access PLB displays on remote hard drives. As
described in FoxView Search Paths on page 48, 70 Series FoxView does not
include a logical host in its file access search path.
Configuring Ladder Display Location

By default, the Control Configurator installs the ladder displays in the following directories:
/usr/plcfv for FoxView files
/usr/plc50 for 50 Series Display Manager files
/usr/plc for WP20/30 Display Manager files.
These locations are configurable through ASCII file /usr/plc/plb_dir on the CPs host. Modifying
this file allows you to have the ladder display location in different directories or disk partitions.
The Control Configurator reads the plb_dir file to identify where to install the ladder displays.
The Display Manager also reads this file to identify the base directory of the ladder displays for
that particular host.
The plb_dir file contains the following keywords:
PLB50 = 50_Series_base_directory
PLB = 20_Series_base_directory
49
where:
50_Series_base_directory
is the full pathname to the Display Manager 50 Series display file base
directory (maximum of 200 characters)
20_Series_base_directory
is the full pathname to the Display Manager 20 Series display file base
directory (maximum of 50 characters).
To relocate a ladder display directory (for example, into the /opt partition), you must:
1. Create or modify the /usr/plc/plb_dir file with the appropriate ladder display
directories.
2. Move the existing ladder displays to the new base directory
When relocating 20 Series display files on a 50 Series station to a base directory other than
/usr/fox/ia16, you must link or loop-back-mount the new_directory to
/usr/fox/ia16/new_directory, otherwise WP20s, WP30s, and PWs cannot access the ladder
displays.
For example, to move all the 20 Series and 50 Series ladder displays on an AP51 into the /opt/lad-
der directory, you must:
1. From the VT100 prompt, create the plb_dir file using the vi editor by typing:
vi /usr/plc/plb_dir
2. Set the keywords in the plb_dir file using the vi editor by typing:
PLB50=/opt/ladder/disp50
PLB=/opt/ladder/disp20
3. From the VT100 prompt, loop-back-mount the /opt/ladder/disp20 directory:
a. For Model 50 stations, type:
mount -t lo /opt/ladder/disp20 /usr/fox/ia16/opt/ladder/disp20
b. For Model 51 stations, type:
mount -F lofs /opt/ladder/disp20 /usr/fox/ia16/opt/ladder/disp20
In addition to the above steps, you must add the new mount point to the Invensys Foxboro
mount table files, such that the /usr/fox/ia16/opt/ladder/disp20 is mounted when you reboot the
AP:
From the VT100 prompt, use the vi editor to edit the mount table files:
a. For Model 50 stations, add the following line to the /etc/fstab file:
/opt/ladder/disp20 /usr/fox/ia16/opt/ladder/disp20 lo rw o o
b. For Model 51 stations, add the following line to the /etc/vfstab file:
/opt/ladder/disp20 - /usr/fox/ia16/opt/ladder/disp20 lofs - yes -
Once these changes are made, all 20/30 and 50 Series workstations are able to access the ladder
displays from the new directory, and the Control Configurator installs the PLB ladder displays
into these directories.
50
50 Series Workstation Access

FoxView and Display Manager can directly access the ladder displays on any CPs host on the net-
work. This requires the Compound Summary Access (CSA) software.
When you select the compound and PLB from FoxSelect or the Select Screen, FoxView or DM
searches for the ladder display in the following order:
From the CPs host, in FoxView, DM, and 20/30 Series Format
From the local disk (50 Series only)
From the workstations logical host in FoxView, DM, and 20/30 Series format.
If the search is unsuccessful and the display was invoked through FoxSelect, the Select Screen, or a
Detail Display button on a display, the detail display appears with the following message:
Ladder display not accessible, loading Detail Display
Directories used for searching are defined on the destination station disk, not the local worksta-
tion disk.
NOTE
When the plb_dir file does not exist, the Display Manager defaults to the /usr/plc or
/usr/plc50 directory.
50 Series WP Configuration Option

Using the WP global variable CTLFRST, you can configure the FoxView/DM search sequence
for ladder displays or sequence code. The /usr/fox/wp/data/init.user file contains the CTLFRST
variable.
When CTLFRST = CPHOST, the FoxView/DM searches for the requested ladder display or
sequence code file in the following order:
CP host
Local disk
Logical host.
When CTLFRST = LOCAL, the FoxView/DM searches for the requested ladder display or
sequence code file in the following order:
Local disk
Logical host
CP host.
When the CPs host is not accessible, the local configuration prevents FoxView/DM time-outs if
the ladder display or sequence code files are available on the local disk or the WPs logical host.
The local configuration, however, does not assure that you are reading the latest ladder display or
sequence code.
If the local configuration is used, you must distribute the ladder display or sequence code files to
the local disk or the WPs logical host every time the Control Configurator changes them. You can
distribute the ladder display or sequence code files to remote 50 Series workstations using the
get_remfiles utility [refer to Display Engineering Utilities (B0193WU)].
51
Installing Ladder Displays on Local Disk or Logical Host

When installing the ladder displays on the WP local disk (WP50 only) or WP logical host, you
should install the ladder displays in the following directories:
/usr/plcfu (for FoxView displays)
/usr/plc50 (for DM 50 Series ladder displays)
/usr/plc directory (for 20 Series ladder displays)
When the ladder displays are installed in different directories, you must create the
/usr/plc/plb_dir file and set the required PLB keywords to the ladder display base directories.
You can distribute the ladder display files to remote 50 Series stations using the 50 Series
get_remfiles utility [refer to Display Engineering Utilities (B0193WU)]. This utility can convert
20 Series displays to 50 Series format.
You should convert 20 Series ladder displays to 50 Series DM format on the WP50 local disk or
50 Series logical host. The 50 Series Display Manager can recognize both formats, however, each
time it reads a 20 Series display file, it must convert the file into 50 Series format. This can take
up to 15 seconds for a large display file and a heavily loaded workstation.
If the ladder displays are installed in the default directories, you can convert 20 Series displays to
50 Series format by typing the following commands from the VT100 mode:
cp -r /usr/plc /usr/plc50
/usr/fox/wp/bin/tools/convdisp2_50 /usr/plc50
Sequence Code Access

The Control Configurator installs the sequence code files that are used by the Block Detail Dis-
play All Code page in the following directories:
/opt/fox/ciocfg/<compound>(70 Series servers and 50 Series AP and AW)
/usr/fox/ciocfg/<compound>(AP10 and AP20).
50 Series Workstation Access

FoxView and DM can directly access the sequence code on any CP host on the network. The
pathname of the sequence code file is contained in the WP variable SEQ variable.
When you select the ALL CODE button from a sequence block detail display, FoxView/DM
searches for the sequence code in the following order:
From the CP host in both the 50 Series directory ($SEQ) and 20/30 Series directory
(/usr/fox/ia16/$SEQ)
From the local disk (50 Series WP only) in the $SEQ directory
From the WPs logical host in both the 50 Series directory ($SEQ) and 20/30 Series
directory (/usr/fox/ia16/$SEQ).
If unsuccessful, the Display Manager displays the following message on the message line:
Can not access sequence code
The above search order can be changed similar to the PLB ladder displays (see 50 Series WP
Configuration Option on page 51).
52
FoxView Sequence Block Detail Display Access

When you are calling in Sequence Code detail displays, FoxView sends the display request to the
Sequence Function Chart (SFC) Display Manager if the sequence block was configured through
the SFC Configurator. A menu entry within the SFCDM is provided to allow viewing of the
FoxView detail display if desired. When you are calling in a detail display through FoxSelect, the
Show Parameter Detail Display menu pick is provided for this purpose.
53
54
8. Databases
This chapter describes fonts and markers as they apply to different models of workstations.
Display Manager 50 Series Fonts and Markers

For 50 Series workstation applications that use the Invensys Foxboro HI Library API, there are
four sets of fonts and four sets of markers. These fonts and markers are used by Display Manager.
On WP20/WP30, fonts and markers can be loaded dynamically by applications. On 50 Series
workstations, all the fonts and markers are pre-loaded and cannot be dynamically changed by
applications. These pre-loaded fonts and markers have been converted from the WP20/WP30
versions to X font file formats. Refer to Display Engineering Utilities (B0193WU) for information
on converting WP20/30 fonts into the 50 Series workstation format. Note that markers now have
the same X format as the font files and are treated as fonts, unlike on WP20/30 where they had
different formats.
The HI Library interface allows applications to request variations of the loaded fonts, such as sin-
gle width, double width, single height, double height, and any such combination.
On WP20/WP30, these variations are derived on-the-fly as an application requests them. On
50 Series workstations, all variations of the fonts exist as files and are pre-loaded before an applica-
tion runs. They are not derived at the time an application runs.
On WP20/30, the assignments of the four font files and four marker files are:
Index Fonts Marker

0 sys_fnt sys_mkr
1 sys_fnt1 usr_mkr
2 48l_fnt plc_mkr
3 unused usr_mkr1
On 50 Series workstations, font and marker files and their size variations are named as follows:
Index Fonts Markers

0 ia0swsh sys_mkr
ia0swdh
ia0dwsh
ia0dwdh
1 ia1swsh usr_mkr
ia1swdh
ia1dwsh
ia1dwdh
2 ia2swsh plc_mkr
55
B0193MQ Rev M 8. Databases
Index Fonts Markers

ia2swdh (half-height)
ia2dwsh (half-height)
ia2dwdh (half-height)
3 ia3swsh (half-height) usr_mkr1
ia3swdh (half-height)
ia3dwsh (half-height)
ia3dwdh (half-height)
To support the resizing of windows without having rescalable fonts, the following half-width,
half-height variations are used when windows are made small (for example, quarter-screen):
Index Fonts Markers

0 ia0hwhh hhsys_mkr
ia0hwsh
ia0swhh
1 ia1hwhh hhusr_mkr
ia1hwsh
ia1swhh
2 ia2hwhh hhplc_mkr
ia2hwsh
ia2swhh
3 ia3hwhh hhusr_mkr1
ia3hwsh
ia3swhh
The following large version of the fonts and markers are provided for use in windows that are
sized to occupy the full screen:
Index Fonts Markers

0 Lia0swsh Lsys_mkr
Lia0swdh
Lia0dwsh
Lia0dwdh
1 Lia1swsh Lusr_mkr
Lia1swdh
Lia1dwsh
Lia1dwdh
2 Lia2swsh (half-height) Lplc_mkr
Lia2swdh (half-height)
56
8. Databases B0193MQ Rev M
Index Fonts Markers

Lia2dwsh (half-height)
Lia2dwdh (half-height)
3 Lia3swsh (half-height) Lusrmkr1
Lia3swdh (half-height)
Lia3dwsh (half-height)
Lia3dwdh (half-height)
The X versions of the fonts and markers can be modified using the Font Editor, which is accessi-
ble from the Config menu in the I/A Series Display Manager window. The files that can be edited
are /usr/fox/wp/fonts that have a .bdf extension. After modifying these files, you must compile
and install them. This is done as follows:
1. On a 50 Series workstation, invoke a local VT100 window by selecting VT100.local
from the SftMnt menu in the I/A Series Display Manager window.
2. Click in the VT100 window.
3. Type: install_fonts.
Applications must be exited and restarted in order to use the modified fonts.
NOTE
Only the files listed above are pre-loaded. Fonts or markers with any other names
are not usable by applications using the Invensys Foxboro HI Library API.
Creating Custom Markers for the 50 Series

If you create custom marker files (such as usr_mkr.bdf and usr_mkr1.bdf ) using the Font Editor,
you should be aware that there are multiple sizes of each marker file to accommodate different
window sizes. Currently, Invensys Foxboro provides three sets of marker sizes: the Invensys Fox-
boro default window size, the full-screen window size and the small size.
Typically, the default window size version of the marker file is created using the Font Editor and
the other sizes are derived using utilities. After the utilities are run, the Font Editor is used to
manually smooth out any anomalies produced by the conversion process (such as jagged curves).
The names of the files associated with user-modifiable markers are:
usr_mkr.bdf The default window size version
hhusr_mkr.bdf The half-width/half-height size (small) version
Lusr_mkr.bdf The full screen window size (large) version
usr_mkr1.bdf The default window size version
hhusr_mkr1.bdf The half-width/half-height size (small) version
Lusrmkr1.bdf The full-screen window size (large) version.
57
Normally, you would create or modify the usr_mkr.bdf and usr_mkr1.bdf files using the Font
Editor. An easy way to create the derived files is to type the following in a VT100 window (noting
that the file extension is .gc3 not .bdf in the cvtmarkers command):
cd /usr/tmp
cvtmarkers -r usr_mkr.gc3
or
cvtmarkers -r usr_mkr1.gc3
Note that after doing this, it is often desirable to call up each of the derived files using the Font
Editor to alleviate any anomalies. After modifying all the files, type the following from a VT100
window:
install_fonts
Applications that have windows opened must be exited and restarted in order to be able to use the
modified markers.
Expanding Marker Files on WP51 and AW51

On a WP51 or an AW51, it is possible to expand existing marker files to include up to 255 sym-
bols. The procedure for doing so is as follows:
1. From a Display Manager window, select Font_Edit from the Config pull-down
menu.
2. When the Font Editor comes up, select Load Font and type the name of the file that
is to be expanded, for example, usr_mkr1.bdf. Click on OK when done.
3. After the marker table is displayed, click on the keyboard input field that allows a
character number to be entered. Enter the number of the highest character you wish
the file to contain. The maximum is 255.
The marker display highlights a blank box on the left half of the window and a blank
grid appears on the right half.
4. Edit the grid to contain the contents of the highest marker. When finished, select
Save Changes from the Edit pull-down menu.
5. Now save the file using the Save Font option under the File pull-down menu. Click
on OK if the marker filename is correct.
6. To edit the other markers in the expanded file, reload the marker file using the Load
Font option under the File pull-down menu. Now, the marker display at the left dis-
plays all the blank spaces between the last marker in the original marker file and the
newly added highest marker.
7. After all the markers have been edited and the file saved (in /usr/fox/wp/fonts), type
install_fonts from a local VT100 window.
8. Restart any running application which uses this marker file (such as the Display Man-
ager) so that it uses the expanded version.
After Step 4, it is possible to add the other markers as well. However, by saving the file and reload-
ing it, the marker table displayed at the left of the window is easier to work with.
58
Parameter Database df_pdef or dsppdef.dat

This section describes the df_pdef and gdblk50.db database file layouts and the associated data
structures used by FoxDraw, Display Builder, g_edit, d_edit to build/update faceplates, groups,
trends, and to verify connections (d_edit) on a 50 Series workstations. It also describes the
dsppdef.dat and dspblock.dat database files used by FoxDraw to perform the same functions on
70 Series workstations.
Path (DM) /usr/fox/wp/data/df_pdef

Path (FoxView) /usr/fox/wp/data/dsppdef.dat
File Type ASCII
! WARNING
You should not modify the df_pdef or dsppdef.dat file. If you change this file, the
edits could be lost at the next release.
The display file parameter definition (df_pdef ) file contains all the default parameter definitions.
However, not all the control database parameters are defined in this file.
For each individual parameter, the df_pdef file defines the data type as well as optional arguments
such as range name, Boolean acronyms, and engineering units.
The first line of this file must be defined as #df_pdef , otherwise the file cannot be loaded.
Comments begin the # character and can start at the beginning or in the middle of a line. The
prompt character is to be used as part of a string definition.
Parameter definitions are the same for the pdef and block database files, except that the block
database files do not support packed Boolean or packed long data types. These may only be
defined in the pdef files (df_pdef or dsppdef.dat).
Parameter Definition Syntax

The command syntax is:
parname data_type [arg1.....argn] [\] [;color=value]
where:
parname Control DB parameter name
data_type Parameter data type:
S = String
B = Boolean
I = Integer
L = Long
R = Real
PB = Packed Boolean
PL = Packed Long
arg1.....argn Optional arguments (see following subsections).
59
;color=value Specifies the trend line color for the parameter; value is a color macro or
integer.
\ Optional argument indicating that arguments continue on the next line
(currently supported only for packed boolean and packed long data types)
Examples: COUT Bstate0Bstate0state1; COLOR=WHITE

SPT R RI1 EI2; COLOR=HI_MAGENTA
Optional Arguments for Real Parameters

arg1 Defines the scaling range parameter (for example, RI1)
arg2 Defines the engineering unit String parameter name (for example, EI1)
Examples:
MEAS R RI1 EI1
OUT R RO1 EO1
PNT_1 R RO1_1
HDALIM R
Optional Arguments for Range Parameters

arg1 arg2 arg3 Define the default scaling factors (high scale, low scale, and delta). If no
defaults are supplied, the default values defined in DEF_SCALING are
used.
Example: The ACCUM block scales are defined as follows:

R01 RNG 1000000.0 0.0 0.0005
Optional String Parameter Arguments

arg1 Default string name
Examples:
EI1 S %
NM0_1 S state0
DESCRP S # a NULL string
stg1 T FALSE
Optional Boolean Parameter Arguments

arg1 exp0 exp1
where:
exp = state name, or
exp = :.state_parameter, or
exp = state_name:.state_parameter
60
Examples:
CIN B state0 state1
CIN_1 B :.PNM_00 :.PNM_01
IN_1 B state0:.NM0_1 state1:.NM1_1
The names state0 and state1 are the default names (names assigned, for
example, to trends with a compound:block name that does not yet exist);
:. is a delimiter used to find the optional parameter name; NM0_1,
NM1_1, PNM_00, and PNM_01 are the Compound:Block string
parameters that contain the associated state name.
Optional Packed Boolean/Long Arguments

arg1.....argn Bitacronym or a list of bitacronyms and the bitmask. Each argument is
defined as:
acronym:hex_bitmask
Acronyms are up to four characters long.
It is recommended that you use no more than 32 arguments because the
convention editor and display configurator bitmap dialog bob are not able
to display more than 32 bit fields.
Multiple acronyms for the same hex_mask may be used. A maximum of
four acronyms may be configured. A list of acronyms should be defined as:
acronym_1, acronym_2.....acronym_n:hex_mask
For example, BLKSTA bit 16 is defined as ACT,TRIP:10000.
A hex_mask may define multiple consecutive bits. The bits must be con-
secutive bits only (such as in ALMSTA bit acronyms CRIT and
PRTYPE).
When a packed boolean or packed long has no acronyms defined, the
Connect_path bit extension may contain only a hex_mask or Boolean
numbers as defined in the 50 Series df_pdef parameters 10---- (for
packed longs) or 9----- (for packed booleans). The 70 Series hex_mask
or Boolean numbers are defined in :DEFLT PL (for packed longs) or
:DEFLT PB (for packed Booleans).
For a packed boolean/long that contains a list of acronyms, connections
that use bit extensions may refer both the default Boolean number and the
bit acronym.
The packed boolean and the packed long contain the default Boolean
numbers and are not control DB parameters. The OM data type value is
used to determine the names. For 50 Series, the packed Boolean data type
is 9 and the packed long data type is 10.
For more examples, refer to the 50 Series df_pdef file or the 70 Series
dsppdef.dat file.
61
Block Database gdblk50.db or dspblock.dat
Path (50 Series) /usr/fox/wp/data/gdblk50.db

Path (70 Series) /usr/fox/wp/data/dspblock.dat
Type ASCII
The gdblk50.db file for Display Manager and dspblock.dat file for FoxView contain all the
defined block types supported by the I/A Series system, and they are used to retrieve pertinent
data associated with the block type and the faceplates.
The database file is an ASCII file containing predefined keywords. Keywords contain block name,
block type, and a list of parameters that pertain to the block.
Using this database file, you can change the percent_of_scale_delta from 0.5 to any other value
or change the way particular parameters are scaled.
The gdblk50.db file for 50 Series is not backward compatible with the AP20 delivered
/usr/fox/hi/gdblk.db file.
Database File Layout Requirements

1. Keywords must end with a = character. No space is allowed between the keyword
and the =. Keywords must not be changed.
2. A comment line starts with the # character and ends at the end of the line. You can
start a comment in the middle of a line.
3. NAME is the block name keyword. All block data must start with the keyword
NAME. The block name must be on the same line as the keyword. The NAME key-
word must be followed by the TYPE keyword. All other data can be in any order.
Syntax:
NAME= block_name
4. TYPE is the control processor block type (optional). The block type must be on the
same line as the keyword.
Syntax:
TYPE= block_type
5. FPDESCn is used by block types that have multiple faceplates associated with them.
For example, the MCIN block has 32 input parameters but the faceplate for this block
can support only 16 connections because of faceplate size limitations. Therefore, there
are two faceplates associated with MCIN; these are MCIN for contacts 1 through 16,
and MCIN_2 for contacts 17 through 32. FPDESCn is the way routines that inter-
face with gdblk50.db for 50 Series or dspblock.dat for 70 Series can determine
whether a block type has multiple faceplates associated with it. In the above example,
FPDESC1 and FPDESC2 should be defined under MCIN. The text should reason-
ably describe the faceplate. Any description with more than one word must be
enclosed within double quotes.
Syntax:
FPDESCn= descriptor text
62
Examples for NAME= MCIN:

FPDESC1= MCIN_1 contacts 1 - 16
FPDESC2= MCIN_2 contacts 17 - 32
6. SCALE is an optional keyword used to list all the range parameters for a given block
type. The range parameters contain optional arguments that define the default scaling
factors: high scale, low scale, and delta. If no defaults are supplied, the default values
defined in DEF_SCALING are used.
Syntax:
range [hi_scale [lo_scale [delta]]]
Examples for defining the ACCUM block scales:
SCALE=RI1
RO1 100000.0 0.0 0.01
The first range used (RI1), contains the default scaling factors; see the
DEF_SCALING keyword. However, the RO1 range contains the default high
scale of 100000.0, the default low scale of 0.0, and the default
percent_of_range_delta of 0.01. High scale and low scale default values are
assigned if the block does not exist. If the block exists, the CP block scales are
used. However, the delta assigned to a connection is always calculated from the
percent_of_range_delta defined in this file.
7. PARAMS is an optional keyword that defines the list of block parameter names,
which are:
Not defined in the df_pdef file for DM or dspdef.dat file for FoxView, or
Defined in df_pdef or dspdef.dat file, but should contain a different definition
for this block type.
The PARAMS list may not have strings, packed boolean, or packed long parameter
definitions. String parameters must be defined in the STRINGS list; packed bool-
ean/long can be defined only in the df_pdef or dspdef.dat file. The parameter defini-
tion is the same as the df_pdef or dspdef.dat parameter definition.
8. STRINGS is a list that contains all faceplate substitution strings and control DB
string parameters. This list must contain all the block type string parameters.
A name with two arguments is a string parameter definition and a name with only one
argument is the text substitution name.
Syntax for substitutions:
substitution_name text_value
Syntax for string parameters:
param_name S text_value
To define a substitution name in the display template, the name must be surrounded
by angular brackets. For example, stg1 is a substitution name, while
substitution_name equals stg1.
63
9. TRENDING variables are defined in a similar but not identical way in

FoxView/FoxDraw and Display Manager. For FoxView/FoxDraw, the trending related
keywords are added to the list of parameters for a block type, whereas the Display
Manager format file uses the parameter keyword TRENDING to group the trend
related keywords.
The FoxView/Foxdraw file dspblock.dat uses the following parameters:
Table 8-1. Parameters for FoxView/FoxDraw File dspblock.dat
Variable Definition
TL[n] Trend pen parameter name, where n is the pen number 1 - 4
TL_COLOR[n] Trend pen color name, where n is the pen number 1 - 4
GRID_COLOR Color name to be used for grid
GRAPH_COLOR Color name to be used for graph area
SCAN_RATE Real-time collection intervals in seconds
DURATION Total duration of the graph area, in [value units] format, that
is, 15 minutes
ACCESS_LEVEL Access level (0-255) for permanent changes
CONFIG_ACL Access level (0-255) for access to the on-line trend
configurator
NAME0 Text displayed for Boolean pen when in the 0 state
NAME1 Text displayed for Boolean pen when in the 1 state
SIZE0 Height of the Boolean 0-state data in the graph in percent of
graph
SIZE1 Height of the Boolean 1-state data in the graph in percent of
graph
TL_LOCATION[n] Location of Boolean data in percent of graph, where n is pen
number 1-4
An example of configured trend data from the dspblock.dat file follows:

################ PID ######################################
NAME= PID # Block Name
TYPE= 7 # Block Type
TL[1]= MEAS
TL[2]= SPT
TL[3]= OUT
64
The Display Manager gdblk50.db file uses the following parameters:
Table 8-2. Parameters for Display Manager File gdblk50.db
Variable Definition
TL1 Line 1 parameter name
TL1_HIST Line 1 historian name
TL1_COLOR Line 1 color number from 0-31
GRID_COLOR Color number to be used for grid, 0-31
GRAPH_COLOR Color number to be used for graph area, 0-31
OFF_NORM_COLOR Color number for off normal area, 0-31
NORM_LIMITS Off normal range for trend, in percent of graph
RECT_HIST Recent history flag, ON or OFF
SCAN_RATE Real-time collection intervals in seconds
ACCESS_LEVEL Access level (0-255) for permanent changes
CONFIG_ACL Access level (0-255) for access to the online trend
configurator
An example of configured trend data from the gdblk50.db file follows:

################ PID ######################################
NAME= PID # Block Name
TYPE= 7 # Block Type
TRENDING= TL1 MEAS # Line number, parameter
TL2 SPT
TL3 OUT
TL4 RSP
65
10. DEF_SCALING defines the default high scale, low scale, and delta values in case no
values are defined in the SCALE keyword. The I/A Series default definition is:
high scale = 100.0
high scale = 0.0
delta = 0.5 percent_of_scale
11. DEF_TRENDING contains a list of trend variables and values used to configure
trend objects for all blocks. Trend variables that are defined within the block type
section take precedent over the default values configured under DEF_TRENDING.
Refer to TRENDING on page 64 for a list of default trend variables.
66
9. Upgrading from Display
Manager to FoxView
This chapter provides information on upgrading from Display Manager to FoxView.
FoxView is the next generation of the Display Manager, and FoxDraw is an enhancement of the
Display Builder and Display Configurator.
Installing this software does not affect any existing functionality. On Solaris systems, the Display
Manager, Display Builder, and Display Configurator may still be used. FoxView and FoxDraw are
installed as additional applications, not as replacements for existing products.
FoxView
The following material discusses elements and considerations for FoxView.
Whats New
Enhancements and new capabilities for FoxView include:
New menu system, with support for menus that are independent of directory struc-
ture on disk
New Select Screen, now called FoxSelect
Message line with drop-down list, showing the last 25 messages
Display bar for quick access to configured displays
Most Recently Used display list, allowing quick access to the most recently called
displays
File extensions associated with file types.
Mnemonics and accelerator keys
Whats the Same

FoxView features that retain original features include:
Display hierarchy single base display with fixed position overlays
Display look-and-feel
Display access from menu picks and display picks
Multiple FoxView configuration
dmcmd scripting language.
What Needs to be Converted from Display Manager to FoxView

Format
Items requiring conversion from Display Manager to FoxView include:
Display files, including display library objects (for example, custom faceplates)
67
B0193MQ Rev M 9. Upgrading from Display Manager to FoxView
Custom markers
Custom color palette
Customized environment files. A set of new environment files has been provided.
FoxSelect
FoxSelect takes the place of the Select Screen in Display Manager. Refer to FoxView Software
(B0193WH).
FoxDraw
FoxDraw takes the place of the Display Builder and Display Configurator.
FoxDraw Browser Capability

FoxDraw uses FoxAPI Invensys Foxboro Application Interface and the AIM*Server interfaces
to connect to the I/A Series System via TCP/IP client/server communication protocol. Acting as a
client, FoxDraw can retrieve CSA data to support the compound/block browser, and parameter
and range data from the control processor for faceplates, trend pens, marker locations, and
attributes such as Fill Level.
To use the FoxDraw browser, you must connect to the FoxAPI server. You must install four ais
files and edit the an_init.cfg file. Refer to the FoxDraw Software (B0193WG) book for more
information.
Display Names
Displays and library objects cannot have the same name. For instance, there is a standard library
object named tank_on_legs shipped with FoxDraw. You cannot create your own display named
tank_on_legs and then successfully link the tank_on_legs library object into that display.
FoxView and FoxDraw do not currently support display names that do not contain at least one
alphabetic character or contain more than one period (.) character. For instance, the following
names are not supported and do not work correctly:
12345.fdf
tower1.new.fdf
Converting and Modifying Display Manager Files

The basic steps in the upgrade process for Display Manager files are:
Converting Display Manager display files
Converting custom markers
Merging custom color palette edits
Upgrading customized environment files.
FoxView/FoxDraw File Extensions

File extensions are helpful in identifying file types. The File types and their extensions are listed in
Table 9-1.
68
9. Upgrading from Display Manager to FoxView B0193MQ Rev M
Table 9-1. File Types and Their Extensions
Extension File Type

.fdf FoxView display file
.pdf Name given to a converted Display Manager display
.g ASCII version of .fdf or .m1 files
.m1 FoxDraw library object
.bmp Windows NT bitmap file
.i Solaris bitmap file
.env Environment definition file
.mbr Environment menu bar definition
.mnu Environment menu pull-down definition
.dbr Environment display bar definition
The /opt and /usr Directories

Display Manager files and FoxView files can reside on the same file system. Converted and modi-
fied files should be placed in a parallel directory structure, with /opt replacing /usr as the root
directory.
For example, if Display Manager displays are located in:
/usr/menus
locate FoxView displays in:
/opt/menus
FoxView automatically looks in the /opt directory before accessing the /usr files. This means that
even though converted displays are in another directory, references to those displays (within dis-
play files and Display Manager scripts) do not need to be changed.
NOTE
When you convert displays with the Convert capability in FoxDraw (refer to Con-
verting a Display File on page 70) be sure to specify the new directory (for exam-
ple, /opt/menus) in the Convert to a Different Directory field.
User Edits to Standard Files

A separate directory structure has been set up to contain standard I/A Series display-related files
that have been user edited. This allows user edits to be unaffected by installation of new I/A Series
software. Table 9-2 gives the directories where these files reside.
Table 9-2. Standard File Location
I/A Series Release Customer Edits

/usr/fox/wp/data /opt/customer/data
/opt/fox/displib /opt/customer/displib
/opt/fox/env /opt/customer/env
69
The environment files (located in /opt/fox/env) are not yet supported by this mechanism. This
means that user edits to standard environment files (Initial, Process_Eng, Software_Eng, and
Operator) are lost when a new software release is installed.
Converting a Display File

The FoxDraw conversion utility allows you to convert many different styles of display file from
one version to another. For more information, refer to FoxDraw (B0193WG).
To convert a display file:
1. From the FoxDraw Tools menu, choose Display Converter.
The Convert utilitys Convert Display Files dialog box appears as shown in Figure 9-1.
Figure 9-1. Convert Display Files Dialog Box
2. Click an option button (such as FDF to G).

3. Click Browse.
The File Open dialog box appears.
4. Select one or more files to be converted.
NOTE
All input files must be on the same drive on which the I/A Series software is
installed.
5. Click Convert.
The output files are created in the same directory as the input files and have the same
base name (to the left of the dot) as their associated input file. The output files exten-
sion (to the right of the dot) is different from the input file.
Exceptions:
The Upgrade Display conversion overwrites the input file with the output file.
70
For BDF to M1 conversions, each input file yields multiple output files. Output
file base names are composed of the input files base name followed by an under-
score and a number.
Converting a Customized Color Palette

Skip this section if you have not customized the standard I/A Series color palette.
FoxView and FoxDraw use a new color palette definition file, /usr/fox/wp/data/colordef.dat. This
is an ASCII file that you can modify with a text editor, if desired. Using the I/A Series Color Pal-
ette Editor, you can determine any customized RGB values in the 50 Series color palette,
sys_pal.wp50, and then enter the values into the colordef.dat file.
The colordef.dat file has the format:
<color index> RGB values
For example, color indices 16 through 31 have the entries, as listed in Table 9-3.
Table 9-3. Color Indices Entries
Color Index Red Green Blue

16 0 0 0
17 .760 0 0
18 0 .619 0
19 .619 .333 0
20 0 0 .60
21 .709 0 .674
22 0 .627 .619
23 .714 .714 .714
24 .447 .447 .447
25 1.0 0 0
26 0 1.0 0
27 1.0 .988 0
28 0 0 1.0
29 1.0 0 .952
30 0 1.0 .988
31 1.0 1.0 1.0
Copying colordef.dat
NOTE
Do not edit the colordef.dat file in /usr/fox/wp/data. Instead, copy this file to the
/opt/customer/data directory and edit the copied version. This allows you to install
future updates of FoxView/FoxDraw without affecting your custom palette.
71
To copy the file:

At a cmdtool or command window, type:
cd /opt/customer/data
cp /usr/fox/wp/data/colordef.dat
Editing colordef.dat
The color indices in the 50 Series color palette, sys_pal.wp50, do not directly match the color
indices in colordef.dat. Note that the first 16 entries in sys_pal.wp50 (entries 0-15) are not used
in the FoxView/FoxDraw palette. The mapping information is listed in Table 9-4.
Table 9-4. Mapping Information
sys_pal.wp50 Index colordef.dat Index X11 Color Name

0
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
0 16 black
1 17 red3
2 18 green4
3 19 sienna
4 20 blue4
5 21 magenta3
6 22 cyan4
7 23 gray
8 24 dim gray
9 25 red1
10 26 green
11 27 yellow
72
Table 9-4. Mapping Information (Continued)
sys_pal.wp50 Index colordef.dat Index X11 Color Name

12 28 blue
13 29 magenta
14 30 cyan
15 31 white
16 48 burlywood2 (tan)
17 49 red3
18 50 green3
19 51 sienna
20 52 SkyBlue4
21 53 magenta3
22 54 cyan4
23 55 gray71
24 56 dim gray
25 57 DarkOrange1
26 58 SpringGreen3
27 59 Yellow
28 60 SkyBlue1
29 61 LightPink1
30 62 aquamarine3
31 63 white
Configuring Blinking Colors

When an object is configured to blink, it blinks from its base color index, defined in colordef.dat,
to the corresponding FoxView blink-to color index, defined in /usr/fox/wp/data/fv_blink.dat.
Each line in fv_blink.dat defines the blink-to color associated with the base color.
To change the blink-to color for a particular base color:
Modify the corresponding line in fv_blink.dat using a text editor (textedit on Solaris
systems or Notepad on Windows NT systems).
Copying fv_blink.dat
NOTE
Do not edit the fv_blink.dat file in /usr/fox/wp/data. Copy the file to
/opt/customer/data and make the edits in the /opt/customer/data directory. This
allows you to install future updates of FoxView/FoxDraw without affecting your
custom blink-to colors.
73
To copy fv_blink data:

From a cmdtool or command window, type:
cd /opt/customer/data
cp /usr/fox/wp/data/fv_blink.dat
Editing fv_blink.dat
The file fv_blink.dat is illustrated in Table 9-5. By default, all blink-to colors are set to gray71
(colordef.dat index 23).
To change the blink-to color for red1 from gray71 to black:
1. Locate the base color red1, which is index 25 in colordef.dat.
2. Then locate the base color black, which is index 16 in colordef.dat.
The colordef.dat index 25 appears on line 26 in the fv_blink.dat file.
3. In line 26, change the fv_blink index from 23 (gray71) to 16 (black).
Table 9-5. fv_blink.dat File
File Line colordef.dat Base Color X11 fv_blink.dat Blink-to Color

Number Index Name Index X11 Name
1 0 23 gray71
2 1 23 gray71
3 2 23 gray71
4 3 23 gray71
5 4 23 gray71
6 5 23 gray71
7 6 23 gray71
8 7 23 gray71
9 8 23 gray71
10 9 23 gray71
11 10 23 gray71
12 11 23 gray71
13 12 23 gray71
14 13 23 gray71
15 14 23 gray71
16 15 23 gray71
17 16 black 23 gray71
18 17 red3 23 gray71
19 18 green4 23 gray71
20 19 sienna 23 gray71
21 20 blue4 23 gray71
22 21 magenta3 23 gray71
23 22 cyan4 23 gray71
74
Table 9-5. fv_blink.dat File (Continued)

24 23 gray71 23 gray71
25 24 dim gray 23 gray71
26 25 red1 23 gray71
27 26 green 23 gray71
28 27 yellow 23 gray71
29 28 blue 23 gray71
30 29 magenta 23 gray71
31 30 cyan 23 gray71
32 31 white 23 gray71
33 32 gray93 23 gray71
34 33 gray88 23 gray71
35 34 gray80 23 gray71
36 35 gray68 23 gray71
37 36 gray58 23 gray71
38 37 gray48 23 gray71
39 38 gray38 23 gray71
40 39 gray28 23 gray71
41 40 (pink) 23 gray71
42 41 (pink gray) 23 gray71
43 42 (gray pink) 23 gray71
44 43 (dark gray pink) 23 gray71
45 44 (cream) 23 gray71
46 45 (cream gray) 23 gray71
47 46 (taupe) 23 gray71
48 47 (dark taupe) 23 gray71
49 48 burlywood2 (tan) 23 gray71
50 49 red3 23 gray71
51 50 green3 23 gray71
52 51 sienna 23 gray71
53 52 SkyBlue 23 gray71
54 53 magenta3 23 gray71
55 54 cyan4 23 gray71
56 55 gray71 23 gray71
57 56 dim gray 23 gray71
58 57 DarkOrange1 23 gray71
59 58 SpringGreen3 23 gray71
60 59 yellow 23 gray71
75
Table 9-5. fv_blink.dat File (Continued)

61 60 BlueSky1 23 gray71
62 61 LightPink1 23 gray71
63 62 aquamarine3 23 gray71
64 63 white 23 gray71
65 64 gray91 23 gray71
... 23 gray71
92 91 gray38 23 gray71
Upgrading Customized Environment Files

The location of environment files is controlled by the WPs ENV_DIR variable, which, by
default, is set to /opt/fox/env.
FoxView environment files are standard script files, similar to Display Manager files. They differ
as follows:
FoxView environment script files have been reorganized to promote re-use of menu
bar entries. The .env file is the top environment script, which calls in the other scripts.
Top menu bar items must point either to a directory, as in Display Manager files, or to
a new menu definition file (.mnu file). The menu definition files allow easier custom-
ization of menus, which do not depend on a directory structure.
Menu items cannot directly call in display files or execute application programs. The
new display bar provides direct access to displays.
Top menu bar items do not blink. The blinking Sys and Alarm buttons have been
moved to an alarm bar.
To upgrade a Display Manager environment file:
1. Copy the file from /usr/fox/sys/Change_Env to /opt/fox/env, and add the .mbr (menu
bar) extension.
2. Edit the .mbr file, moving certain commands to a new .env file, and deleting button
commands that are no longer needed.
3. Create a new environment (.env) file which calls the .acl, .dbr, and .mbr files.
4. Create a new display bar (.dbr) definition file, using Initial.dbr as a template.
5. Create a new access level (.acl) file and add the desired access level protection com-
mands to it.
To help you understand the process, the following files are provided as examples of a FoxView
environment file, menu bar file, menu definition file, and display bar file. At the end of this sec-
tion is a sample upgrade procedure.
76
Sample FoxView Environment File (Initial.env)

Here is the FoxView Initial Environment file (/opt/fox/env/Initial.env).
dmcmd script
dmcmd passwd
dmcmd chng_env
$ENV_DIR/Initial.acl # script file containing access levels
$ENV_DIR/Initial.dbr # script file containing display bar
# definition
$ENV_DIR/Initial.mbr # script file containing menu bar
# definition
# add optional display to call in here
Purpose of each line:

dmcmd script
Identifies this file as a FoxView script file.
dmcmd passwd
Determines whether a password is configured for this environment.
dmcmd chng_env
Clears the menu bar and logs the script in the Operator Action Journal, if logging has
been turned on. (Note: this command does not clear the menu bar as it did in the Display
Manager.)
$ENV_DIR/Initial.acl
Calls in the script containing the access protection level commands. It is intended that
access level commands be placed in a separate script, which makes it easier to re-use the
settings in other environments.
If access levels are specified as part of the environment, these commands should be located
before the menu bar definitions (Initial.mbr), so that the access levels take effect on the
new menu bar.
$ENV_DIR/Initial.dbr
Calls in the script containing the display bar definition.
$ENV_DIR/Initial.mbr
Calls in the script containing the menu bar definition.
As this is a standard FoxView script, you may add additional dmcmd commands to it.
Sample Menu Bar File (Initial.mbr)

Here is the Initial.mbr file.
dmcmd script
dmcmd button -1 &File $ENV_DIR/file.mnu
dmcmd button -1 &Help $ENV_DIR/help.mnu

dmcmd script
77
This is the standard dmcmd command for placing a menu label on the menu bar. The
button position (-1) is ignored and is included only as a place holder to make the com-
mand backward compatible with the previous implementation of the command. Each
button command appends the specified button to the menu bar.
NOTE
The ampersand character (&) before the File and Help text identifies the key to be
associated with the menu label.
The argument following the label name is the file definition of the menu label. This was
previously a directory name, but now can be a menu pull-down definition file. In this
case, the contents of the File pull-down menu is specified in the file /opt/fox/env/file.mnu
(see below).
The button command supports only menu definition files or subdirectories. Direct access
buttons, such as the Display Manager Alarm and Select buttons, are not supported.
There is no restriction on the number of menu labels or the length of the label text. The
previous restriction was ten labels, with up to six characters in each label.
Sample Menu Definition File (file.mnu)

The first line of the menu definition file must contain the words pull-down foxview menu
to identify it as a menu file containing pull-down menu definitions.
The format of the rest of the file is:
label action
The label is the text that appears in the pull-down menu. The action can include standard Fox-
View commands, displays, directories, or other pull-down menu files.
Here is the menu definition file, file.mnu.
Change &Environment... Ctrl+E chng_env_dlg
Fox&Select Ctrl+S stddisp
Separator SEPARATOR
&Print psc -p 100
Separator SEPARATOR
FoxView Usage $ENV_DIR/Usage -p 100
Separator SEPARATOR
Select Point select_pt on
Update Lights annun 0 0 0 -p 100
Process Summary Reporter /usr/fox/sys/Proc_Summary -p 100
Separator SEPARATOR
&1 MRU MRU1
&2 MRU MRU2
&3 MRU MRU3
&4 MRU MRU4
78
New Commands to Support Menu Definition Files

The commands listed in Table 9-6 support menu definition files.
Table 9-6. Menu Definition Files
Command Action
chng_env_dlg Brings up the Change Env dialog box.
SEPARATOR Adds a separator to the menu.
psc_dlg Brings up the Print dialog box (not yet supported).
MRU1 Call in the current base display.
MRU2 Calls in the previous base display.
MRU3 Calls in the second previous base display.
MRU4 Calls in the third previous base display.
NOTE
MRU commands are valid only in pull-down menu files. They cannot be used in
display manager script files.
Sample Display Bar Definition File

The FoxView display bar definition file looks like this:
dmcmd script
dmcmd dbar_tmplt $FV_DBAR/button_display_bar
dmcmd dbar_btn 1 dmcmd stddisp -l Select Screen
dmcmd dbar_btn 2 $INITDSP...

dmcmd script
dmcmd dbar_tmplt $FV_DBAR/button_display_bar
Specifies the name of the template file to be used for the display bar.
There are two choices for display bar templates: button_display_bar and
icon_display_bar. They are located in the $FV_DBAR directory, or
/opt/fox/displib/DisplayBar by default.
The button version displays 18 buttons that you can configure to call up any display or to
execute an application or script.
The icon version displays up to eight thumbnails or bitmaps of display files. These can
be bitmaps of the display itself, or any other bitmap file. The action is taken by selecting
the thumbnail. Bitmaps are in xwd format.
In addition, any bitmap file may be referenced by the display bar, using the -b option.
When FoxView calls in an environment, it automatically creates bitmaps for displays ref-
erenced on the display bar.
79
dmcmd dbar_btn 1 dmcmd stddisp -l FoxSelect -b $FV_DBAR/selscrn.i

dbar_btn is the keyword to define a button on the current display. The format of this
command is:
dbar_btn button_number button_command [-l label] [-b bitmap_name]
This line specifies FoxSelect to execute when the button is selected. The -l label argument
is required to specify the button label.
dmcmd dbar_btn 2 $INTIDSP
This line specifies only a display name, no label. If no label is specified, the base name of
the display is used for the label.
Example: Upgrading Display Manager Environment Files to FoxView

The following procedure illustrates moving a Display Manager environment file to FoxView.
Display Manager file /usr/fox/sys/My_Env

dmcmd nologscr
dmcmd passwd
dmcmd chng_env
dmcmd button 1 Alarm dmcmd rcntalms
dmcmd button 2 Help /usr/Help
dmcmd button 3 keep
dmcmd button 7 OverVw /usr/menus/Overview
dmcmd button 8 keep
dmcmd button 9 Select dmcmd stddisp
To upgrade My_Env:
1. Copy the file to the directory /opt/fox/env, and add the .mbr (menu bar) extension:
cp /usr/fox/sys/Change_Env/My_Env /opt/fox/env/My_Env.mbr
2. Move the first three commands to a new My_Env.env file (see below) and move or
delete the button entries that are no longer needed.
The button command with no definition (for example, the keep label with no
button definition following) is not supported.
Standard menu definition files (*.mnu) have been supplied for the File and Help
pull-down menus. You may modify these files, as needed.
The button numbers are not supported in this release. All button commands
append the button definition to the end of the menu bar.
In this example, the entries in Table 9-7 can be moved or deleted, as indicated.
80
Table 9-7. Entries
Entry Action
nologscr Move to the new .env file.
passwd Move to the new .env file.
chng_env Move to the new .env file.
Sys Replace with the standard File pull-down menu (file.mnu).
Alarm Delete (already contained on the alarm bar).
keep Delete (not supported).
Help Replace with the standard Help pull-down menu (help.mnu).
OverVw Move this button to the display bar.
Select Delete (already contained in the standard File pull-down menu).
The modified My_Env.mbr file now looks like this:

dmcmd mruflush
dmcmd button -1 &Disp /usr/menus
dmcmd button -1 Disp_&1 /usr/menus/d1
dmcmd button -1 Disp_&2 /usr/menus/d2
dmcmd button -1 &Help $ENV_DIR/help.mnu
3. Create a new environment file /opt/fox/env/My_Env.env. This top level script is the
one that should contain the dmcmd passwd command, which forces the password to
be verified.
Here are the contents of /opt/fox/env/My_Env.env:
dmcmd nologscr
dmcmd passwd
dmcmd chng_env
$ENV_DIR/My_Env.acl
$ENV_DIR/My_Env.dbr
$ENV_DIR/My_Env.mbr
4. Create a new display bar definition file, /opt/fox/env/My_Env.dbr, using Initial.dbr as
a template:
cp /opt/fox/env/Initial.dbr /opt/fox/env/My_Env.dbr
5. Edit My_Env.dbr to add the reference to the overview display that was removed from
the original script:
dmcmd dbar_button 8 /opt/menus/Overview
When selected, button 8 now calls in the overview display.
Notice the configuration of the other button commands. FoxSelect and the Change
Environment dialog box can be accessed using this display bar definition.
81
To have a thumbnail image of the overview display appear on the display bar, convert
the display to a bitmap (Overview.i) by selecting File, then selecting Convert and FDF
to BMP from FoxDraw. (To run the fdf_i conversion utility from a command line,
refer to FoxDraw (B0193WG) book.)
6. The display overview should have been moved to the /opt directory. FoxView can find
the display when this button is configured as /usr/menus/Overview, but it finds it
faster when the button is configured as /opt/menus/Overview.
7. Create a new access level file named /opt/fox/env/My_Env.acl, and add any access
level protection commands to it.
Display Bar Configuration Menu

To assign the current display or a command to a display bar button at run time:
Right-click on the button.
A pop-up menu opens as shown in Figure 9-2.
Figure 9-2. Assign Pop-up Menu
When you save the configuration, be sure to save to the /opt/customer/env directory, but not to
/opt/fox/env (the default directory).
Protecting Display Bar Menu Picks, System and Process Buttons,

and Select/Assign
The pop-up menu items can be protected with the WP globals listed in Table 9-8.
Table 9-8. Global Variables
Global Variable Protects

DBM_PROT All items in the pop-up menu
DBA_PROT Assign/Clear
DBS_PROT Save/Save As
DBN_PROT New
DBL_PROT Load
DBC_PROT Assigned/Command
The globals must be given protection values in the range of 1-255, and the assigned values must
then be protected in an environment script, as follows.
82
To define the global variables:

The variables are defined in the /usr/fox/wp/data/init.user file. If this file does not
exist, create it.
To create an init.user file:
At the command prompt, type:
cd /usr/fox/wp/data
cp init.user.rel init.user
To give the globals protection values:
Decide what value(s) are to be given to different functions. Not all variables need to be
defined. For example, to protect all the items in the display bar menu, you need to
assign a value only to the DBM_PROT variable.
Suppose that you want to protect (disable) all display bar menu items in all environ-
ments, and want to assign a protection value of 10 for this function. Add the follow-
ing line to the end of the file init.user:
DBM_PROT=10
NOTE
Edits to init.user do not take effect until the station is rebooted.
To edit the environment script:

To protect display bar access in an environment (My_env), add this line to the
My_env.acl environment file:
dmcmd protect value $DBM_PROT
The line could also have been edited to have the numeric value hard-coded into it.
dmcmd protect value 10
To remove the protection (enable access), add this line to the .acl file of another envi-
ronment file (such as, Process_Eng.env):
dmcmd unprotect value $DBM_PROT
You can use this same mechanism to protect any of the other items in the display bar menu.
System and Process Buttons

The variables that protect System and Process buttons are as listed in Table 9-9.
Table 9-9. Global Variables that Protect System and Process Buttons

SYS_PROT System button
PRC_PROT Process button
Follow the procedure for protecting the display bar pop-up menu.
83
Select and Assign Mode

The SAA_PROT variable protects the Select and Assign mode for configuring trends in FoxView:
Disabling this feature prevents objects from being selected with a right mouse button selection.
On-Line Trend Configuration Picks

Use the variables in Table 9-10, to protect features within the On-line Trend Configurator.
Table 9-10. Global Variables that Protect the On-Line Trend Configurator

TND_PROT Invoking the On-line Trend Configurator.
TLC_PROT Changing trend line connections with the keyboard.
TLD_PROT Changing trend descriptors with the keyboard.
PSV_PROT Permanent saving.
ADV_PROT Access to the Advanced Trend Configuration Browser dialog box.
CBP_PROT Access to the browser feature of the Advanced Trend Configuration
Browser dialog box.
FoxSelect On/Off Access

The variable SEL_PROT disables/enables the capacity in FoxSelect of turning compounds on and
off. If this feature is disabled and FoxSelect started, compounds cannot be turned on and off.
To disable the ability to turn compounds on and off in an environment (My_env):
Add these lines to the My_env.acl file:
dmcmd = SEL_PROT 20
dmcmd protect value $SEL_PROT
NOTE
You need to exit and restart FoxSelect for the disable/enable to take effect.
To enable the ability to turn compounds on and off:

Add this line to the .acl file of another environment (for example, Process_Eng.acl):
dmcmd unprotect value $SEL_PROT
NOTE
You need to exit and restart FoxSelect for the disable/enable to take effect.
84
Getting Started with FoxView

FoxView requires a license, just as Display Manager does.
On Solaris Systems:
To set FoxView as the default display manager, type:
/usr/fox/wp/bin/tools/use_foxview.sh
To switch back to Display Manager, run this script and then reboot:
/usr/fox/wp/bin/tools/use_displaymanager.sh
Using FoxView
When FoxView is started, the initial display appears in the main window.
The display bar is at the left of the main window. Display bar buttons allow quick access to con-
figured displays or commands.
The alarm bar contains the System and Process alarm buttons. These buttons take the place of the
Sys and Alarm buttons in Display Managers top menu bar.
The message bar is to the right of the alarm bar. This area takes the place of Display Managers
message line, where informational messages are displayed to the operator.
The time/date bar is to the right of the message bar.
To call up the Alarm Manager:

Click the Process button in the alarm bar.
To start up System Management:

Click the System button on the alarm bar.
To call up FoxSelect (updated Select display):

At the display bar or the File menu, click FoxSelect.
FoxSelect, which starts as a separate application, gives a hierarchical view of the con-
trol stations and their database. See below for more details.
To call up demo displays:

Click a display button in the display bar located at the left of the main window.
To call in the previous display:

From the File menu, select the second display in the display list, or press Ctrl + 2.
To change environments:
1. At the display bar or the File menu, select Change Environment.
2. In the Change Environment dialog box, select an environment from the list.
Type a password, if required, and click OK.
85
The menu bar changes to reflect the new environment. The display bar may also
change, depending on the environment.
Using FoxSelect
The I/A Series database is organized hierarchically by station, compound, and block. When the
FoxSelect window first opens, only the stations appear. Refer to FoxView Software (B0193WH)
for more information.
Using FoxView
Display Access
Displays are accessed in the same way as in the previous Display Manager, with the exception of
top menu bar direct access. In addition, displays can be accessed from the display bar, or from the
Most Recently Used (MRU) list of display files. This list is found under the File menu.
The MRU entries also support access through accelerator keys. Ctrl 1 calls in the current display,
Ctrl 2 calls in the previous display, Ctrl 3 the next previous, and so forth.
Changing Environments
A Change Environment dialog box can be accessed from the File pull-down menu. This dialog
box is also tied to an accelerator key, Ctrl E. By default, the list box displays the environment files
from the directory $FOX_ENV, or \usr\fox\env. This directory contains the enhanced environ-
ment files. A drop-down list box contains all files in this directory that:
have a .env extension
have the command chng_env.
After selecting an environment, enter any required password. FoxView automatically checks for
configured passwords, based on the name of the environment. Passwords are set using the
\usr\fox\wp\bin\tools\dmsepass utility.
Note the following compatibility issues with previous environment definitions:
The chng_env command must be found in the environment file, if the menu bar
should be cleared.
The button location specifier is not supported. All menu buttons are appended to the
current menu bar. Use the chng_env to clear the current menu bar. Menu buttons
cannot be swapped. The whole menu bar should be fully defined in the environment
file.
Direct access menu buttons are not supported. If encountered in an environment file,
they are ignored.
Menu buttons cannot blink.
FoxSelect
The Select Screen is now a dialog box with a tree or hierarchical representation of the control
database. Double-clicking on an expandable entry expands the entry. Expandable entries are iden-
tified with a + before the entry.
Non-expandable entries have a - before the entry.
86
Double-clicking on a block calls in the detail display for the block.
Figure 0-1. Select Screen Display
Alarm Bar
The alarm bar contains the Process button to access the Current Alarms Display and the System
button to access System Management Display Handler (SMDH). These buttons also indicate the
alarm status of process and system alarms.
Message Bar
The message line displays the current message. A drop-down list is provided to display the last
25 messages. This number is not currently configurable.
Status Bar
The status bar at the bottom of the window frame displays the following information, starting
from the right:
Full pathname of the current base display
Full pathname of the current environment
Name of the printer where operator actions are currently logged
Name of the historian where operator actions are currently logged
87
Number of active moveable overlays associated with the FoxView instance.
New Display Window Variables

The following variables can be set to override DM defaults:
ENV_DIR
Is the directory containing environment files. Default is: \usr\fox\env
DM_IGNORE_EXT
Ignores extensions when displaying directory contents in pulldown
menus. Default is .pdf , .g, .ml.
88
10. ScratchPad Group and Trend
Displays
This chapter provides information on installation procedures, installed component parts, and
files for Scratchpad Group and Trend Displays.
Overview
FoxView installation includes a set of scratchpad trends (named TrendsList) and group displays
(named GroupList). Each of these scratchpad applications allows you to set up a unique set of 20
trend overlays and/or 20 group overlays for each FoxView environment.
ScratchPad Trends
You can create as many as 20 reusable trends from FoxView without having to build and config-
ure them through FoxDraw. These trends can be created with simple mouse clicks, and with min-
imal effort. You can build a trend, choosing from the four available sizes, 1/8, 1/4, 1/2, or Full
Screen. These trends can also be positioned anywhere in the FoxView window.
ScratchPad Group Displays

You can create as many as 20 reusable group displays. These displays can be created from
FoxView, with simple mouse clicks, and with minimal effort. The group displays can have a com-
bination of as many as 8 Compound Block Faceplates and/or 1/8 screen size trends. Each of the
trends or faceplates can be easily replaced or removed from the group display.
Installation
ScratchPad Groups and Trends are separate applications and do not have to be added to every
environment. When FoxView is installed, the Group displays are added to the Process_Eng envi-
ronment, and Trends are added to both the Process_Eng and Operator environments. ScratchPad
Groups and Trends can also be added to other environments. Each of them have their own instal-
lation scripts and can be installed separately.
ScratchPad Trends
To install scratchpad trends in Windows and Solaris based workstations:
1. From a DOS or CMDTOOL window, change to the ScratchPads Common directory
on the drive where the I/A Series software resides (typically D:).
For Windows based workstations, type:
D:
cd \opt\fox\displib\ScratchPads\Common
89
B0193MQ Rev M 10. ScratchPad Group and Trend Displays
For Solaris based workstations, type:

cd /opt/fox/displib/ScratchPads/Common
2. Run the shell script Install_Trends.
sh Install_Trends Enviroment Menubar Name
Install_Trends Enviroment Menubar Name
where Environment Menubar Name is the name of the environment .MBR file that
trends are being installed to. In most cases, this is the same as the environment.
For example, to install into the Initial environment, type:
sh Install_Trends Initial

To install scratchpad group displays in Windows and Solaris based workstations:
1. From a DOS or CMDTOOL window, change to the ScratchPads Common directory
on the drive where the I/A Series software resides (typically D:).
D:
cd \opt\fox\displib\ScratchPads\Common
cd /opt/fox/displib/ScratchPads/Common
2. Run the shell script Install_Groups.
sh Install_Groups Enviroment Menubar Name
Install_Groups Enviroment Menubar Name
where Environment Menubar Name is the name of the environment .MBR file that
groups are being installed to. In most cases, this is the same as the environment.
For example, to install into the Initial environment, type:
sh Install_Groups Process_Eng
Installed Components
The installed components are listed in the following sections.
ScratchPad Trends
The ScratchPad Trends use several new trends, scripts, and FoxDraw displays. It also requires that
several new OM variables get added to the wp51_globals.all file, which is located on the drive
where the I/A Series software resides (typically D:) in the \usr\fox\wp\data directory. The OM
objects are added to the wp51_globals.all file during installation of FoxView.
FoxView installation also creates a new directory ScratchPads under \opt\fox\displib. This
directory holds the files required for the operation of the ScratchPad Trend displays (except for the
90
10. ScratchPad Group and Trend Displays B0193MQ Rev M
trend library objects). The trend objects are installed into the \opt\fox\displib\Trends
directory.
The ScratchPads directory contains the following four subdirectories:
Common
Groups
ScratchPads
Trends.
ScratchPads and Trends are default directories, where files and directory structure are copied
from when installing ScratchPad Trends to an environment. Each environment that uses the
trends will have a unique set of files located in the \opt\customer\ScratchPads
\EnvironmentName directory. These files will access and use scripts and commonly used displays
from the Common directory.
Environment Files
Table 10-1 lists and describes the environment files.
Table 10-1. ScratchPad Trend Environment Files
Environment File Description

ScratchPads\ScratchPads\ The directory and files copied during Group or Trend
installation and used for the menu picks.
trend_list The menu pick for opening the list of trends. See
Figure 10-1 for the dmscript that executes the trend
substitution list.
ScratchPads\Trends\ The directory and files copied during ScratchPad Trend
installation.
trend_sublist.txt The substitution list used for button labels and com-
mands for the trend_list overlay. Refer to Figure 10-2.
dmcmd
$SPAD_DIR/../Trends/trend_sublist.txt
Figure 10-1. DMScript Listing
91
dmcmd
close -name $FOX_DISPLIB/ScratchPads/Common/trend_list.fdf
subst button1
subst command1
subst button2
subst command2
subst button3
subst command3
subst button4
subst command4
subst button5
subst command5
subst button6
subst command6
subst button7
subst command7
subst button8
subst command8
subst button9
subst command9
subst button10
subst command10
subst button11
subst command11
subst button12
subst command12
subst button13
subst command13
subst button14
subst command14
subst button15
subst command15
subst button16
subst command16
subst button17
subst command17
subst button18
subst command18
subst button19
subst command19
subst button20
subst command20
ov $FOX_DISPLIB/ScratchPads/Common/trend_list.fdf -l UR
Figure 10-2. trend_sublist.txt Listing
Each button on the trend_list overlay has a button label buttonX, where X is the number ranging
from 1 to 20. Each button also has a DM command configured as commandX, where X is the num-
ber ranging from 1 to 20. When this substitution list is run, it opens the trend_list overlay and
substitutes all the configured commands and button labels. They are replaced by the above text.
92
NOTE
To add an existing trend overlay to the trend list, change a button label name or set
a trend to open in a location different from the one configured. This is the file that
gets edited.
Refer to the section ScratchPad Trends on page 98 for the syntax.
Common Files
The common files are listed below:
Trends \opt\fox\displib\Trends
Overlay_trend.m1 Quarter screen size trend object with assignable pens.
Refer to Figure 10-3.
Close Button
Alarm Priority - Marker Style - Compound - Current Value

- Block - Hi Scale Value
Assign Button - Parameter - Lo Scale Value
Figure 10-3. Quarter Screen Trend
Overlay_trend2.m1 One-eighth screen size trend object with assignable pens. Refer
to Figure 10-4.
93
Trend Area - Right click on this area to open the

Online Trend Configurator.
Pause, Pause Controls and Timestamp

Close Button
Assign - Marker Style - Value - Eng. Units - Alarm Priority
Figure 10-4. Trend Object with Assignable Pens
Overlay_trend3.m1 Full width/half height screen size trend object with assignable
pens.
Overlay_trend4.m1 Full screen size trend object with assignable pens.
The information on the last two trends is set up like the quarter screen trend.
Trend Overlay \opt\fox\displib\ScratchPads\Common
master_trnd_eighth.fdf
master_trnd_half.fdf
master_trnd_quartr.fdf
master_trnd_full.fdf
When a new trend is assigned to an environment trend_list, one of files is copied into the
\opt\customer\ScratchPads\EnvironmentName\Trends directory. The copied file is
renamed as trend_button#.fdf, where button# is the number of the button that was
assigned to open the trend, and EnvironmentName is the name of the FoxView
environment.
For example:
If an operator assigns a quarter screen size trend to the tenth button in the Process_Eng
environment trend_list, the master_trnd_quartr.fdf file would be copied to:
\opt\customer\ScratchPads\Process_Eng\Trends\trend_10.fdf
Scripts \opt\fox\displib\ScratchPads\Common
convert90.script This script converts existing FoxView 8.0 ScratchPad files to the
new 9.0.1 format. It is executed when FoxView 9.0.1 is installed or it can be run man-
ually from a command prompt:
sh \opt\fox\displib\ScratchPads\Common\convert90.script
94
copy_trend.script This script copies the appropriate Master Trend Overlay file,
when an operator assigns a new trend to a list. The trend that is copied is based on the
choices made by the operator. It also updates the Trends substitution list file with a
new button label and command for the new trend that was added.
Create_NTglobals, Create_UNIXglobals Depending on the platform, one of these
scripts must be run during initial installation of FoxView. This file adds the new OM
variables to the wp51_globals.all file.
Install_Trends This script is used to install ScratchPads Trends into an environ-
ment. This is explained in the section Installation on page 89.
Update_list.dmscript This dmscript resets the variables entered, when creating a
new trend overlay. It then closes the trend setup overlays and opens the trend_list
overlay again with the new changes added.
Text files \opt\fox\displib\ScratchPads\Common
Help_Trends.txt This is the help file that is available to an operator through the
help pick on the trend_list overlay. This explains the general operation of the
ScratchPad Trends.
Displays \opt\fox\displib\ScratchPads\Common
Help_Trends.fdf This is the help overlay that is accessed from the Help button on
the trend_list overlay.
trend_list.fdf This overlay displays a list all the buttons and available trends.
trend_setup_1_2.fdf This overlay is used when assigning a new trend to the list.
trend_setup_full.fdf This overlay is used when assigning a new trend to the list.
trend_setup1.fdf This overlay is used when assigning a new trend to the list.
ScratchPad Groups
The ScratchPad Group displays use several scripts and FoxDraw displays. It also requires that sev-
eral new OM variables get added to the wp51_globals.all file, which is located on the drive
where the I/A Series software resides (typically D:) in the \usr\fox\wp\data directory. The OM
objects are added to the wp51_globals.all file during installation of FoxView.
The FoxView installation creates a new directory in \opt\fox\displib\ called ScratchPads.
This directory holds the files required for the operation of ScratchPad Group displays, except for
one trend library object. The trend object is installed into the \opt\fox\displib\Trends direc-
tory. There are four subdirectories under the ScratchPads directory: Common, Groups,
ScratchPads, and Trends. The default files and directory structure are copies to the Groups and
ScratchPads directories when installing ScratchPad Group displays into an environment. Each
environment that uses ScratchPad Group displays will have its own unique set of files located in
the \opt\customer\ScratchPads\EnvironmentName directory. These files will access and use
scripts from the Common directory. The Trends directory is used for ScratchPad Trends.
95
Environment Files
Table 10-2 lists and describes the ScratchPad Group environment files.
Table 10-2. ScratchPad Group Environment Files
Environment File Description

ScratchPads\Groups\ The directory where files are copied during ScratchPad
Group installation.
group_sublist.txt The substitution list used for button labels and com-
mands for the group_list overlay. This file is identical to
trend_sublist.txt except that it opens the group_list.fdf
display.
ScratchPads\ScratchPads\ The directory where files are copied during Group or
Trend installation. Also used for the menu picks.
group_list The menu pick for opening the list of Group displays.
This is a dmscript that executes the group substitution
list. This file is identical to trend_list except that it runs
the group_sublist.txt substitution list.
Common Files
Trends \opt\fox\displib\Trends
Overlay_trend5.m1 Quarter screen size trend object with assignable pens. Refer to
Figure 10-5.
Trend Area - Right click on this area to open the

Online Trend Configurator.
Pause, Pause Controls and Timestamp

Close Button
Assign - Marker - Current Value - Alarm State
Figure 10-5. Quarter Screen Size Trend
This object is slightly smaller than Overlay_trend2.m1. This provides enough space in
the display, for a set of control buttons at the bottom of the Group display.
96
Trend Overlays \opt\fox\displib\ScratchPads\Common

trend_master.fdf When a new trend is assigned to a group display, this file is copied
into the directory \opt\customer\ScratchPads\EnvironmentName\Groups
\grouptrendbutton#, where button# is the number of the button that was assigned to
open the group display, and EnvironmentName is the name of the FoxView environment.
The copied file is renamed to trend_tile#.fdf, where tile# is the position number on
the screen where the trend will be placed. The tile numbers are 1 to 4 for the top row of
one-eighth screen size faceplates and 5 to 8 for the bottom row of faceplates.
For example:
If an operator in the Process_Eng environment adds a trend faceplate to the upper right
corner of the display (position 4), and the group display that he adds it to is assigned to
button number 10.
The trend_master.fdf file would be copied to:
\opt\customer\ScratchPads\Process_Eng\Groups\grouptrend_10\trend_4.fdf
Scripts \opt\fox\displib\ScratchPads\Common\
group_#.dmscript When creating a new group display, FoxView creates a dmscript
with a list of Compound:Blocks or Trends to be opened on top of the
group_base.fdf display. This script gets built and saved in the
\opt\customer\ScratchPads\EnvironmentName\Groups and is called
group_button#.dmscript. The EnvironmentName is the FoxView Environment, and
button# is the number of the button assigned to open this group display.
add_grp2list.script This script creates the group_#.dmscript with no compound
names in the group_base.fdf display. This script also updates both the assign and
group substitution list with a button label and command that runs the group_#
dmscript.
Create_NTglobals, Create_UNIXglobals Depending on the platform, one of these
scripts is run during the initial installation of FoxView. These files add the new OM
variables, used by ScratchPads, to the wp51_globals.all file.
Install_Groups This script is used to install ScratchPads Groups into an environ-
ment. This is explained in the Installation on page 89.
Config_save.script This script updates both the assign and group substitution list
with any changes to the button label. It also updates the dmscript with any changes
made to the list of Compound Block overlays.
Display.dmscript This dmscript runs after the base display is opened. It opens a
faceplate for each Compound listed in the group_#.dmscript.
Text files \opt\fox\displib\ScratchPads\Common\
Help_Groups.txt This is the help file that is available to an operator through the
help pick on the group_list overlay. This explains the general operation of the Scratch-
Pad Groups.
Displays \opt\fox\displib\ScratchPads\Common
group_base.fdf This display file is used to display all group displays.
group_config.fdf This overlay used to assign compounds and trends to the tile
positions in the group display.
97
group_list.fdf This overlay displays a list all the buttons and available group
displays.
Help_Groups.fdf This is the help overlay that is accessed from the Help button on
the group_list overlay.
label.fdf This overlay is used to assign a group display to a button.
Procedures
ScratchPad Trends
Accessing Trend_list
To access ScratchPad Trends and open the list of available trends (as shown in Figure 10-6):
From FoxView, click ScratchPads > trend_list.
20 trend buttons available for

assignment Buttons to assign new
trends to the adjacent
trend buttons
A Help button with general operating instructions
A. Close button to close the trend_list overlay
Figure 10-6. Trend List Overlay
98
To add a button to the display bar:

Add a display manager command to the appropriate.env file.
For example, to add a trend_list to display bar button 18, type:
dmcmd dbar_button 18 dmcmd subslist
$SPAD_DIR/../Trends/trend_sublist.txt -l button_label
where button_label is the name that appears on the button.
To add a button to a FoxView display:
From FoxDraw, add the following configuration to a button or object in a display:
Operator Action DM Command:
dmcmd subslist $SPAD_DIR/../Trends/trend_sublist.txt
Creating a New Trend on trend_list

To create a new trend on trend_list:
1. Add a new trend by selecting the A assign button next to the trend button to be
assigned, as shown in Figure 10-6. This button opens the trend_setup1.fdf overlay
in the top center of the display, as shown in Figure 10-7.
2. In the trend setup overlay, give the trend button a label by selecting and typing in the
Button Label area. This label can be up to 10 characters long. The operator can use
any alphanumeric characters. Spaces are converted to underscores.
NOTE
A carriage return must be used for the new label to be assigned. Any lowercase letters
used get converted to uppercase.
3. After giving the button a label, select the type of overlay to use (Default, Stationary or
Moveable) as shown in Figure 10-7. Default opens the overlay in the mode to which
FoxView is set. Stationary or Moveable opens the overlay as described by the term.
4. After selecting the overlay type, select the size of the trend to be used, as shown in
Figure 10-7. This opens one of the trend setup_size.fdf overlays, as shown in
Figure 10-8.
99
trend_setup.fdf
Trend_list
Button Label
Selected
Overlay Type
Overlay Types
Trend size to
create
Figure 10-7. Trend_Setup Overlay
There are four different screen-positioning overlays, one for each size trend. On this
overlay an operator can type coordinates into the ROW and COLUMN text boxes, or
move the horizontal and vertical slider, to position the overlay in the display. Select
Save after the trend position is set.
Four sizes of trends that can be created are shown in Figure 10-8.
Half Screen Quarter Screen Eighth Screen Full Screen
Figure 10-8. Different Sizes of Trends
5. Click the Save button to run the copy_trend script.

This script uses the button number selected in the assign_trend overlay, the label
entered from the trend_setup1 overlay, and the ROW and COLUMN coordinates
entered from the positioning overlay.
With this information the copy_trend.script does the following:
a. Replaces any spaces with underscores
b. Converts all characters to uppercase
100
c. Using the environment name, the button number and the selected trend type, it
copies one of the master trends into the ScratchPad Environment directory and
calls it trend_X.fdf, where X is the button number.
d. Using the new file name, the button label, the button number, and the ROW,
COLUMN coordinates, it edits the trend_sublist.txt substitution list. It searches
for the button number and replaces the button label and the button overlay
command.
Default substitution text string, as shown in Figure 10-9 changes to text string
shown in Figure 10-10.
subst button
subst command
Figure 10-9. Default Substitution Text String
subst button NEW_LABEL

subst command ov /opt/customer/ScratchPads/Process_Eng/Trends/trend_#.fdf
sticky -mode -l location
Figure 10-10. Changed Text String
e. After editing the trend_sublist.txt file, the script runs the

Update_list.dmscript file, shown in Figure 10-11. This script resets variables,
closes open setup overlays, and re-opens the trends_list overlay by running the
edited trend_sublist.txt file.
dmcmd script
= TRND_NAM Label
dmcmd close -l 5%,95%
dmcmd subslist $SPAD_DIR/../Trends/trend_sublist.txt
exit 1
Figure 10-11. Update_list.dmscript File
Adding Pens to a Trend

There are several ways to configure the pens of the trend overlay through FoxView.
To add pens using Select point:
1. Open a display that has the I/O point to be trended.
2. Right-click the mouse over an object that the I/O Point is connected to. This opens a
list of configurations that are connected to the object.
101
3. Click the configuration that is configured to the Compound:Block.Parameter, to be

trended. This copies the Compound:Block.Parameter to the system clipboard.
4. Open the trend_list overlay from the ScratchPads pull down menu and select the
appropriate trend button.
5. In the pen information area of the trend, the white box with the letter A is an assign
button. Press this button to assign the Compound:Block.Parameter in the clipboard
to the pen.
To add pens using a touch screen:
2. From FoxView, click File > Select Point.
3. Click the mouse over an object that the I/O Point is connected to. This opens a list of
configurations that are connected to the object.
4. Click the configuration that is to be trended. This copies the
Compound:Block.Parameter to the system clipboard.
5. Click ScratchPad > trend_list to open the trend_list overlay, and select the appro-
priate trend button.
6. Press the white box with the letter A (Assign button) in the pen information area of
the trend to assign the Compound:Block.Parameter in the clipboard to the pen.
To add pens using the Online Trend Configurator:
1. Click ScratchPad > trend_list to open the trend_list overlay, and select the appro-
priate trend button.
2. Right-click the mouse over the Trend Grid Area. This opens the Online Trend
Configurator.
For information on using the Online Trend Configurator, refer to FoxView Software
(B0193WH).
Saving Pens of a Trend

All new pen assignments will be lost when the trend is closed unless they are saved.
To save the pen assignments, use the Online Trend Configurator:
1. Right-click the mouse over the trend grid area. This opens the Online Trend Configu-
rator.
2. Click the Permanent button in the Save / Exit Choices section of the display.
3. Click OK.
102
Select this button to save pen configurations

Figure 10-12. Online Trend Configurator
Editing trend settings

It may be necessary to change the trend setting, such as Pen Ranges and markers, or Trend dura-
tion and scan rate.
To change these settings using the Online Trend Configurator:
1. Right-click the mouse over the Trend Grid Area. This opens the Online Trend
Configurator.
For information on using the Online Trend Configurator, refer to chapter FoxView
Software (B0193WH).
2. Click the Permanent button in the Save/Exit Choices area of the display to make the
changes permanent.
3. Click OK.
103
ScratchPad Trend Shortcut Menu

A shortcut menu (Figure 10-13) is accessible from the trend_list overlay by right-clicking a con-
figured trend_list button.
From this shortcut menu you can change:
The location where the trend opens
The label of the button that appears in the trend list
The mode in which the overlay opens: Moveable or Stationary.
Shortcut
Menu
Figure 10-13. ScratchPad Trends Shortcut Menu
Change Trend Location

Change Location, in the ScratchPad Trend shortcut menu, opens the Trend Location overlay
(Figure 10-14). The operator can change the location in which the trend opens without rebuild-
ing and configuring a new trend.
Figure 10-14. Trend Location Overlay
To change the location of the trend:

1. Right-click a configured trend_list button.
2. From the shortcut menu, click Change Location.
104
3. Click one of the nine predefined overlay location setup buttons. The buttons corre-
spond to the relative screen location (for example, UL=Upper Left, UP=Upper
Center, and UR=Upper Right).
-Or-
Enter a value for ROW (% down from the top of the screen) and press Enter; then enter
a value for COLUMN (% across from the left) and press Enter. Click ASSIGN.
The location selections are display in the New Loc field.
4. Click one of the following:
SAVE to save the changes to the trend_list button.
CANCEL to exit without saving the changes.
Change Trend Label

Change Label, in the ScratchPad Trend shortcut menu, opens the Trend Button Name overlay
(Figure 10-15). The operator can change the label that appears in the trend list overlay.
Figure 10-15. Trend Button Name Overlay
To change the label that appears on a trend list overlay:

2. From the shortcut menu, click Change Label.
3. In the New Name field, enter the name that is to appear on the trend_list button, and
press Enter.
Change Trend Mode

Change Mode, in the ScratchPad Trend shortcut menu, opens the Trend Mode overlay
(Figure 10-16). The operator can change the mode in which the overlay opens (Default, Move-
able, or Stationary) without building or configuring a new display.
105
Figure 10-16. Trend Mode Overlay
To change the mode in which the overlay opens:

2. From the shortcut menu, click Change Mode.
3. Click:
DEFAULT to open the overlay in the mode specified by FoxView.
STATIONARY to open the overlay in stationary mode.
MOVEABLE to open the display in moveable mode.

ScratchPad Group displays work by running a DM command script on top of a common base
display used by all the group_list displays. When a new group display is created, it builds a DM
script that assigns all the variables defined by the operator and opens the group_base.fdf display
from the \opt\fox\displib\ScratchPads\Common directory. After the base display is opened, the
\opt\fox\displib\ScratchPads\Common\Display.dmscript script is run. There are eight 1/8
screen size locations on the base display numbered 1to 4 on the top row and 5 to 8 on the bottom
row. The script checks the variable assigned to each location to see if the location is empty, or if
the location is assigned to a trend or compound:block. The script then opens the appropriate
overlay in the specific location.
Accessing Group_list
The group_list can be accessed using several ways.
To access ScratchPad Groups and open the list of available trends (as shown in Figure 10-17):
From FoxView, click ScratchPads > group_list.
106
20 trend buttons available for

assignment Buttons to assign new
trends to the adjacent
trend buttons
A Help button with general operating instructions
A. Close button to close the trend_list overlay
Figure 10-17. Group_list Overlay
To add a button to the display bar:

Add a display manager command to the appropriate.env file.
For example, to add a trend_list to display bar button 18, type:
dmcmd dbar_button 18 dmcmd subslist
$SPAD_DIR/../Groups/group_sublist.txt -l button_label
where button_label is the name that appears on the button.
To add a button to a FoxView display:
From FoxDraw, add the following configuration to a button or object in a display:
Operator Action DM Command:
dmcmd subslist $SPAD_DIR/../Groups/group_sublist.txt
Creating a Group Display on the group_list

To create a group display on the group_list:
1. Add a new group display by selecting the A (Assign) button next to the group button
to be assigned, as shown in Figure 10-17. This button opens the label.fdf overlay in
the top center of the display, as shown in Figure 10-18.
107
2. In the group setup overlay, give the group button a label by selecting and typing in the
Label area. This label can be up to 10 characters long. The operator can use any alpha-
numeric characters. Spaces are converted to underscores.
NOTE
A carriage return must be used for the new label to be assigned.Any lowercase letters
used get converted to uppercase.
3. After entering the Group Display label, click the Create button. This creates the new
Group display.
Button label
Creates
Group Display
Figure 10-18. Label Overlay
4. After selecting the Create button, the Add_grp2list script is run.

This script uses the environment name, the button number selected and the label to
create a dmscript. The purpose of the dmscript is to assign the group displays position
variables. These position variables are defined later by the operator. Initially the posi-
tion variables are EMPTY.
With the information provided, the Add_grp2list script does the following:
Replaces spaces with underscores
Converts all characters to uppercase
Using the environment name, the button #, and the Label, the script creates the
default dmscript called group_button#.dmscript and places it the \opt\customer
\ScratchPad\Environment\Group directory
where button# is the number of the selected button and Environment is the name
of the Environment.
Using the new file name, the button label, and the button number, the script edits
the group_sublist.txt and assign_sublist.txt substitution lists. It searches
for the button number and replaces the button label and the button overlay
command.
Default substitution text string, as shown in Figure 10-19 changes to text strings
shown in Figure 10-20.
subst button#
subst command#
Figure 10-19. Default Substitution Text String
108
subst button# NEW_LABEL

subst command# close -name old_overlay;ov new_overlay
Figure 10-20. Changed Text String
After editing the substitution lists, the script opens the common base display by
running the new script group_#.dmscript.
dmcmd script # = the button number on

= P1 EMPTY the group_list overlay
= P2 EMPTY
= P3 EMPTY
= P4 EMPTY Position Variables for positions 1-8
= P5 EMPTY This opens the display file but
= P6 EMPTY places the dmscript file onto
= P7 EMPTY FoxViews recent file list
= P8 EMPTY instead. If the base display is
= GRP_NAME NEW_LABEL Variables for group display name opened without running this
= FOX6 # Variables for button number script first, the display will be
nostack 1 wrong.
$FOX_DISPLIB/ScratchPads/Common/group_base.fdf
stack $SPAD_DIR/../Groups/group_#.dmscript
Figure 10-21. Group_#.dmscript
After the display is called into FoxView, the Display.dmscript script checks the
position variables and opens the appropriate overlay.
== _$P1 _TREND dmcmd ov $SPAD_DIR/../Groups/grouptrends$FOX6/trend1.fdf -sticky -tile 1

else != _$P1 _EMPTY dmcmd ov_conn -cb $P1 -sticky -tile 1
== _$P8 _TREND dmcmd ov $SPAD_DIR/../Groups/grouptrends$FOX6/trend8.fdf -sticky -tile 8

else != _$P8 _EMPTY dmcmd ov_conn -cb $P8 -sticky -tile 8
For Variables P1 through P8, the script will (# = the P# variable number 1to 8):
Check if the location is a TREND. == _$P# _TREND. If it is a TREND, the
script opens the trend assigned to that location, (FOX6 is the variable for the
Button assigned to this group display).
ov $SPAD_DIR/../Groups/grouptrends$FOX6/trend#.fdf -sticky -tile #
If it is not a TREND, the script will then check to see if the location is not
EMPTY,
else != _$P# _EMPTY.
If it is EMPTY, the script goes on to the next P# variable
If it is not EMPTY the script opens the default faceplate for the Com-
pound:Block,
109
dmcmd ov_conn -cb $P# -sticky -tile #.
Adding Faceplates and Trends to the Group Display

The Group Editor button is at the bottom of the group display, as shown in Figure 10-22. Click
this button to open the Group_config.fdf overlay. See Figure 10-23. This overlay lets the opera-
tor define what overlays to be opened in each location of the group display. A location can be
EMPTY, connected to a COMPOUND:BLOCK faceplate, or connected to a TREND.
1 2 3 4
Faceplate
Positions
5 6 7 8
Group
Configuration
Figure 10-22. Group Base
110
Tile
Positions
Group Display Save

Name Changes
Cancel Changes
Figure 10-23. Group_config Overlay
There are several ways to assign a Compound Block faceplate to a tile position.
To assign a Compound:Block faceplate to a tile position using Select point:
2. Right-click the mouse over an object that the I/O Point is connected to. This opens a
list of configurations that are connected to the object.
3. Click the configuration that is configured to the Compound:Block.Parameter to be
4. Open the group display from the group list, or choose from FoxView recent file list, if
it exists.
5. Open the Group Editor overlay, and select the A (Assign) button next to the tile posi-
tion where the faceplate is to appear.
6. To save the changes click Update. The new group display opens.
To assign a Compound:Block faceplate to a tile position by manually typing the
Compound:Block:
1. Select the text field for one of the position variables P1 to P8.
2. Type the Compound:Block name, and press Enter.
Upper and lowercase may be used. The Update button converts everything to upper-
case.
111
3. To save changes, click Update.

The new group display opens.
To assign a Compound:Block faceplate to a tile position using a touch screen:
3. Click the mouse over an object that the I/O Point is connected to. This opens a list of
configurations that are connected to the object.
4. Click the configuration that is configured to the Compound:Block.Parameter to be
5. Open the group display from the group list, or choose from FoxView recent file list, if
it exists.
6. Open the Group Editor overlay and select the A (Assign) button next to the tile posi-
tion where the faceplate is to be assigned.
7. To save changes click Update. The new group display opens.
To add a TREND to a tile position:
2. Type the word TREND and press Return.
Upper and lowercase may be used. The Update button converts everything to upper-
case.
To remove a position configuration:
1. Click the Delete button next to the position to be removed.
-Or-
2. Type the word EMPTY, and press Enter.
Upper and lowercase may be used. The Update button will convert everything to
uppercase.
3. To save changes click Update.
The new group display opens.
The operator can also rename the group label name that appears on the Group_list by selecting
the GROUP NAME text area, located at the bottom of the overlay, and typing the new name.
This label can be up to 10 characters long. The operator can use any alphanumeric characters.
Spaces are converted to underscores. Press Enter to assign the new label.
NOTE
Any lowercase letters are converted to uppercase.
112
Saving changes to the Group Configuration

Once all edits are made, the operator can cancel the edits by clicking the Cancel button, in the
lower right corner of the overlay, or save the edits by clicking the Update button. Update runs the
script called config_save.script, located in the \opt\fox\displib\ScratchPads\Common direc-
tory. This script operates the same way as the add_grp2list.script worked:
1. Replaces any spaces with underscores
2. Converts all characters to uppercase
3. Using the environment name, the button #, and the Label, the script re-creates the
default dmscript called group_button#.dmscript and places it the \opt\customer
\ScratchPad\Environment\Group directory
where button# is the number of the selected button and Environment is the name of
the Environment.
4. Using the file name, the button label, and the button number the script then edits the
group_sublist.txt and assign_sublist.txt substitution lists. It searches for the
button number and replaces the button label and the button overlay command.
5. After editing the substitution lists, the script then opens the common base display by
running the new script group_#.dmscript.
While the config_save.script script is running, it checks to see if any TRENDs are listed. If it
finds a trend listed, the script will check to see if the trend already exists. If the trend exists, the
script moves on to the next variable. If the trend does not exist, it will make a new one.
Trends are saved in a specific way. This is to allow each of the 20 Group displays, from every envi-
ronment that group_list is installed into, to have a unique trend in each of the eight tile locations.
In the ScratchPad directory, \opt\customer\ScratchPads\Environment\Groups, a new subdirec-
tory is created. This subdirectory uses the button number assigned to the current group display.
For example, if the current group display is opened by selecting the fifth button on the group_list,
the script creates a subdirectory called grouptrends5. Within this directory, the script copies the
trend_master.fdf overlay from the \opt\fox\displib\ScratchPads\Common directory, and call
it trendtile_position.fdf where tile_position is the tile location where the trend appears.
So, with the previous example, if a trend was added to position 2, the script would create the
directory and file called \opt\customer\ScratchPads\Environment
\Groups\grouptrends5\trend2.fdf.
Adding Pens to a Trend Overlay

There are several ways to configure the pens of the trend overlay through FoxView.
To configure the pens of the trend overlay using Select point:
1. Open a display that has the I/O point to be trended, or use one of the faceplates from
the Group display if the I/O point is present.
2. Right-click the mouse over an object that the I/O Point is connected to.
This opens a list of configurations that are connected to the object.
trended.
This copies the Compound:Block.Parameter to the system clipboard.
4. Open the group display if it is not already open.
113
5. Click the A (Assign) button in the pen information area of the trend to assign the
Compound:Block.Parameter in the clipboard to the pen.
To configure the pens of the trend overlay using a touch screen:
1. Open a display that has the I/O point to be trended, or use one of the faceplates from
the Group display if the I/O point is there.
3. Click the mouse over an object that the I/O Point is connected to.
This opens a list of configurations that are connected to the object.
trended.
This copies the Compound:Block.Parameter to the system clipboard.
5. Open the group display if it isnt already open.
6. Click the A (Assign) button in the pen information area of the trend to assign the
Compound:Block.Parameter in the clipboard to the pen.
To configure the pens of the trend overlay using the Online Trend Configurator.
1. Open the group display if it is not already open.
2. Right-click the mouse over the Trend Grid Area to open the Online Trend Configura-
tor, as shown in Figure 10-24.
Refer to the FoxView Software (B0193WH) on how to use the Online Trend Configura-
tor.
Saving the Pens of a Trend

When configuring the pens of a trend for the first time, the configurations do not remain perma-
nent. The configuration is lost as soon as the trend overlay is closed. To prevent this from happen-
ing, the operator can save the pen configurations through the Online Trend Configurator, if
permanent saving of a trend is allowed.
To permanently save a trend:
1. Right-click the mouse over the Trend Grid Area.
This opens the Online Trend Configurator, as shown in Figure 10-24.
2. Click the Permanent Button in the Save /Exit Choices area of the display.
3. Click OK.
114
Select this button to save

pen configurations
Figure 10-24. Online Trend Configurator
Editing Trend Settings

It may be necessary to change the trend setting, such as pen ranges and markers, or trend duration
and scan rate. Using the Online Trend Configurator, you can easily change these settings.
To edit trend settings using the Online Trend Configurator:
1. Right-click the mouse over the trend grid area. This opens the Online Trend Configu-
rator, as shown in Figure 10-24.
Refer to the FoxView Software (B0193WH) for information on using Online Trend
Configurator.
2. Click the Permanent Button in the Save /Exit Choices section of the display to make
changes permanent.
3. Click OK.
115
116
Appendix A. Multiple Display
Window and AM Configuration
This appendix describes how to configure additional FoxViews/DMs and AMs on a 50 Series
or 70 Series AW/WP by editing the dmcfg file.
To configure additional FoxViews/DMs and AMs on a 50 Series or 70 Series AW/WP, you should
use the Alarm/Display Manager Configurator which is accessible from the Config pull-down
menu in the Process Engineers Environment [refer to Workstation Alarm Management
(B0193RV)]. However, you can edit the dmcfg file to configure additional DMs and AMs.
To start with DMs and AMs, edit the file /usr/fox/customer/hi/dmcfg using a text editor. At boot
time, an initial dmcfg file is automatically created if one does not already exist (see Figure A-1).
Figure A-1 shows a dmcfg file for a system configured with WP workstations WP5101, WP5111,
and WP5121. The dmcfg file for a system configured with AWs is similar to the one in
Figure A-1.
NOTE
1. There is no need for users to configure a default DM and a default AM. A default
DM automatically starts up when a WP/AW is rebooted and has access to the
default AM. The default DM and AM have the letterbug name. If the Alarm/Dis-
play Manager Configurator is used to configure additional DMs and AMs, you
must to recreate the default DM and default AM so that the information resides in
the configuration file.
2. Refer to Workstation Alarm Management (B0193RV) for information regarding

Alarm Managers and the Alarm/Display Manager Configurator.
117
B0193MQ Rev M Appendix A. Multiple Display Window and AM
.
.
.
# Configuration of Multiple Display and Alarm Managers
#
#
#
#
#
# AMTYPE <type> <class> <environment>
#
#
# NAME <lbug> <dmname> <dedicated monitor(s)> <type>
#
NAME WP5101 WP5101 .0 -
NAME WP5111 WP5111 .0 -
NAME WP5121 WP5121 .0 -
Figure A-1. Initial dmcfg File after Bootup WP51
Minimum Configuration Requirements

There are various configuration options available to customize a DM or AM (see Customizing
DMs and AMs Using a Text Editor on page 120). However, to start using the additional DMs
and AMs quickly, at a minimum you must enter the names for additional DMs and AMs in the
dmcfg file.
A DM or AM name must be six uppercase alphanumeric characters and must be unique through-
out the I/A Series system. The names of the Default DM and Default AM are automatically set to
be the same as the letterbug of the station and cannot be changed by the users. Figure A-2 shows
an example of a WP named DMWP51 configured for three additional DMs ADM001,
ADM002, and ADM003.
118
Appendix A. Multiple Display Window and AM Configuration B0193MQ Rev M
The title bar of a DM window displays the name of that DM as:

station letterbug:DM Name
For example, the title bar for ADM001 running on workstation DMWP51 displays:
DMWP51:ADM001
The title bar of an AM window displays the name of that AM as:
station letterbug:AM Name
.
.
.
# Configuration of Multiple Display and Alarm Managers
#
#
# SCREEN <screen_variable> <monitor1> <monitor2> ....
#
#
# TYPE <type> <window attributes> <class> <environment>
#
#
# AMTYPE <type> <class> <environment>
#
#
# NAME <lbug> <dmname> <dedicated monitor(s)> <type>
#
NAME DMWP51 DMWP51 .0 -
NAME " ADM001 - -
NAME " ADM002 - -
NAME " ADM003 - -
#
AMNAME DMWP51 DMWP51 .- Operator
AMNAME " AM0001 .0 -
#
DMTOAM ADM001 AM0001
Figure A-2. Example of WP Configured for Four DMs and Two AMs
119
For flexibility, you can configure more DMs and AMs than the number of DM or AM licenses on
a WP/AW. However, at any given time the number of DMs or AMs running on a WP/AW is lim-
ited to the number of licenses available on that station.
To prevent usurping of system resources, the number of DMs that can be configured on a
WP/AW station has an upper limit of sixteen. Depending on your operating philosophy, you can
have multiple DMs accessing the same AM rather than having each DM associated with its own
AM.
Whenever the /usr/fox/customer/hi/dmcfg file on a WP/AW is modified, the station must be
rebooted for the changes to take effect. Configuration errors are logged on the system printer at
boot time.
For ease of maintenance, it is recommended that you configure all the additional DMs and AMs
for all the WP/AW stations on their system using one /usr/fox/customer/hi/dmcfg file. This
master dmcfg file can then be copied to all the other WP/AW stations. This should help minimize
any confusion and/or errors resulting from editing the dmcfg file on various WP/AW stations.
Duplicate DM names or AM names are a prime example of such errors.
NOTE
For quick startup, the dmcfg file can be manually edited as described. However, the
Alarm/Display Manager Configurator also allows you to configure multiple DMs
and AMs for multiple stations. The configurator must be used to configure AM
Properties.
Besides this document, a file /usr/fox/customer/hi/dmcfg.man is also provided to help you with
the configuration of multiple DMs and AMs. The file dmcfg.man is a text file and can be read by
using the more command, the vi editor, or any other text editor.
Customizing DMs and AMs Using a Text Editor

Manually customizing a FoxView/DM or AM on a WP/AW consists of assigning properties to a
display window and assigning monitors on which a display or AM window can be displayed. Also
assign DM/AM associations to indicate which AM is accessed from the FoxView/DM upon selec-
tion of the Alarm or Process field in the display window.
The following steps are required to manually customize a DM or AM:
1. Define the SCREEN section and/or the TYPE section in the multi-DM/AM
configuration file /usr/fox/customer/hi/dmcfg.
2. Assign the SCREEN and TYPE to DMs in the NAME section of the file /usr/fox/cus-
tomer/hi/dmcfg.
Assign the SCREEN and AMTYPE to AMs in the AMNAME section of the file
/usr/fox/customer/hi/dmcfg.
3. Assign the DM to AM associations in the last section of the file.
NOTE
The Alarm/Display Manager Configurator is recommended for configuring cus-
tomized multiple DMs and AMs. See Workstation Alarm Management (B0193RV).
120
SCREEN Definition
This section consists of defining a screen variable containing a list of monitors as follows:
SCREEN screen_variable monitor1 monitor2 monitor3......
A monitor can have following values:
.0 Primary monitor of a WP51/AW51 station

.1 Second monitor of a dual-headed WP51/AW51 station
XTERM1 A remote terminal running X-Window System
REMOTE A remote terminal server client station.
Examples:
SCREEN ALL_MONITORS .0 .1 XTERM1 REMOTE

SCREEN LOCAL_MON .0 .1
A screen variable defined in the SCREEN section can be used to assign a FoxView/DM or AM to
multiple monitors (see NAME or AMNAME section). Specifying the screen variable is the only
way to assign a FoxView/DM or AM to more than one monitor if at least one of the monitors is a
remote terminal. When assigning a FoxView/DM or AM to come up on either of the local moni-
tors, you can either use a screen variable or enter .- (a period followed by a dash) when specifying
a monitor name in the NAME or AMNAME section of the dmcfg file.
NOTE
The .0 and .1 convention of specifying the first or second read from a multi-headed
workstation is not supported on 70 Series workstations.
TYPE Definition
Defining a DMTYPE or AM TYPE consists of assigning the following properties:
DM Window Property (AM Window Property can only be assigned via the
Alarm/Display Manager Configurator)
DM Class or AM Class
FoxView/DM Environment or AM Environment.
Syntax for defining TYPE or AMTYPE:
TYPE Typename Window_Property Class Environment
OR
AMTYPE AMType Class First_Environment
where,
Typename or AMtype is a user-given name up to 14 characters long, and
Window_Property, Class, and Environment are described in the following sections.
121
Display Window Property

Defining a Display Window Property consists of specifying the following options:
The size and the positioning of a display window
Ability to resize a display window
Clamping the minimum size of a resizable display window to quarter screen.
Size and Position of Window Configuration Code

Default Size/Upper Left Corner D[S][M] or -
Full Screen Size F[S][M]
Quarter Screen/Upper Left QUL[S][M]
Quarter Screen/Upper Right QUR[S][M]
Quarter Screen/Lower Left QLL[S][M]
Quarter Screen/Lower Right QLR[S][M]
Intermediate Size/Upper Left IUL[S][M]
Intermediate Size/Upper Right IUR[S][M]
Intermediate Size/Lower Left ILL[S][M]
Intermediate Size/Lower Right ILR[S][M]
The default configuration code is - and translates into DSM.

The configuration codes S and M are optional.
The code S is required to resize a DM window.
The code M is required if you wish to limit the shrinking of a DM window to the quarter screen
size the smallest legible font size. The code M must be used in conjunction with the code S.
Examples of DM Window Properties are:
DSM Default DM window, resizable, with minimum size limit
QUL Quarter screen/Upper Left DM window, not resizable
FSM Full Screen DM window, resizable, with minimum size limit
QURSM Quarter Screen/Upper Right DM window, resizable with minimum size limit.
NOTE
The Alarm/Display Manager Configurator must be used to configure AM
Properties.
122
DM Class or AM Class
A FoxView/DM or AM can have one of the following four classes:
Description of Class Configuration Code

Operator, started automatically at boot time B
Operator, manually started O
Engineer, manually started E
View-only DM, manually started V
The Default FoxView/DM and Default AM have a class, which cannot be changed by users.
Other DMs and AMs, by default, are assigned the class O.
A DM or AM with class O is meant for use by an operator and must be manually started by the
operator. You can terminate a DM or AM with class O after you have no further use for that DM
or AM. Otherwise, there is no difference between DM classes B and O.
A DM or AM with class E is meant for use by an engineer and must be manually started by the
engineer. An engineer can terminate a DM or AM with class E after he has no further use for that
DM. The only difference between DM classes O and E is that a class E DM updates displays
more slowly than a class O DM. There is no difference in updating performance between AM
classes O and E.
A DM or AM with class V is meant for occasional use for viewing process information only or for
remote users where process security is an issue. A class V DM or AM must be started manually.
Process variables cannot be set from a view-only DM; they can only be read. A class V DM
updates displays more slowly than a class E DM.
FoxView/DM or AM Environment
Users can specify the environment for a FoxView/DM or AM. The environment can be a stan-
dard Invensys Foxboro environment or a user-defined environment.
The default configuration code is - and it translates into Initial or Init_Env.
The default pathname for environments is /opt/fox/env for the FoxView environment and
/usr/fox/sys/Change_Env for the DM environment. You must enter the full pathname if the envi-
ronment file is not in one of these directories.
Examples of DM and AM Type Configurations

The following examples illustrate how DM Window Property, Class, and Environment are com-
bined to define a DM TYPE:
TYPE Operator DSM B Proc_Op_Env
TYPE ViewOnly QULS V -
TYPE Engineer FSM E Proc_Eng_Env
123
The following examples illustrate how AM Class and Environment are combined to define an
AM TYPE:
AMTYPE ViewOnly V -
Assigning Custom Monitors and Types to a FoxView/DM or AM

When a FoxView/DM or AM is assigned to a monitor(s) and that the monitor name is not -, it
is called a dedicated FoxView/DM or AM. Otherwise, a FoxView/DM or AM is called non-dedi-
cated. A dedicated DM or AM can be started up and displayed only on its assigned monitor(s). A
non-dedicated DM or AM can be started up and displayed on any monitor.
Syntax
keyword station_name dm_name monitor_name dm_type
Examples
NAME DMWP51 ADM001 .1 Operator

NAME ADM002 $LOCAL_MON Engineer
NAME ADM003 $ALL_MONITORS ViewOnly
In the above examples, DMWP51 is dedicated to the second head of DMWP51. AADM001 is
dedicated to an X Terminal. ADM002 and ADM003 are both dedicated to monitors on
DMWP51 defined in the screen variables LOCAL_MON and ALL_MONITORS respectively. A
quote in the field means copy the contents of the field defined in the previous line.
NOTE
In the above example for ADM002, you could have specified .- (a period followed
by a dash) instead of $LOCAL_MON to assign ADM002 to either local monitor.
Specifying xterm1 assigns ADM002 to X Terminal 1.
Syntax
keyword station_name am_name monitor_name am_type
Examples
AMNAME DMWP51 DMWP51 .1 Operator
AMNAME AM0001 $LOCAL_MON Engineer
AMNAME AM0002 $ALL_MONITORS ViewOnly
In the above examples, DMWP51 is dedicated to the second head of DMWP51. AM0001 and
AM0002 are both dedicated to monitors on DMWP51 defined in the screen variables
LOCAL_MON and ALL_MONITORS respectively. A quote in the field means copy the con-
tents of the field defined in the previous line.
124
NOTE
In the above example for AM0001, you could have specified .- (a period followed by
a dash) instead of $LOCAL_MON to assign AM0001 to either local monitor. Spec-
ifying xterm1 assigns AM0001 to X Terminal 1.
DM to AM Associations
In order to access a particular AM from the display window, you may create a FoxView/DM to
AM association. By default, letterbug AMs and DMs are associated with each other; an AM with
the same name as a DM is also automatically associated with its same-named DM. Depending on
the memory constraints and computing power of the individual workstations, multiple DMs may
need to be associated with the same AM. See Alarm Manager Considerations on page 8.
Defining a DMTOAM consists of entering the DM name and the AM name.
Syntax for defining DMTOAM:
DMTOAM dm_name am_name
The following are the DM to AM associations found in the configured dmcfg file shown in
Figure A-2 on page 119.
keyword dm_name am_name

In the above example, Display Managers ADM001 and ADM001 access Alarm Manager
AM0001 and Display Manager ADM003 accesses Alarm Manager AM0003.
125
126
Index
/opt directory 69
/usr directory 69
50 Series fonts and markers 55
A
Access level definition files 34
Additional AMs
starting up 10
stopping 11
Additional DMs
starting up 10
stopping 11
Alarm bar 87
Alarm Manager
calling up 85
Alarm Manager, considerations 8
Alarm/Display Manager Configurator 117, 120
AM
assigning custom monitors 124
assigning types 124
class 123
environment 123
licenses 7, 120
name 119
remote 12
B
Backward compatibility 47
Bitmap utility, thumbnail bitmaps 39
Blinking colors, configuring 73
Block database file format 62
Block parameter database functions 59
Button
process 83
system 83
C
Cascading menu entry 42
Changing environments 86
127
B0193MQ Rev M Index
Class 123
Color
blinking 73
palette, converting 71
colordef.dat file 71
Command, menu entry 41
Compounds
on/off access
disabling 84
enabling 84
Configuration
minimum requirements 118
multiple AMs 10
multiple DMs 10
Conversion, required from Display Manager to FoxView 67
Converting, display files 70
Customizing
AMs 11
DMs 11
D
Database file layout requirements 62
Dedicated AMs, licensing 11
Dedicated DMs, licensing 11
DEF_SCALING, keyword 66
DEF_TRENDING, keyword 66
Default AM 117, 118, 123
Default DM 117, 118, 123
Directories, /opt and /usr 69
Display access 86
Display bar
configuring 82
definition file 79
Display bar definition files 37
Display files, converting 70
Display Manager
converting files 68
switching back to 85
upgrading environment files 80
upgrading to FoxView 67
Display menus 44
Display names, rules 68
Display window
licenses 7, 8
variables 88
DM
assigning custom monitors 124
assigning types 124
class 123
environment 123
128
Index B0193MQ Rev M
licenses 120
name 119
remote 12
search paths 47
window property 122
DM to AM associations 8
dmcfg file 117, 118, 120
dmcfg.man file 120
Dual-headed WP51/AW51 stations 11
Dynamic resource allocation 12
E
Editing default Resource Allocation Levels 13
Environment
changing 85
definition files 33
passwords, setting 39
shortcut menu styles 44
shortcut menu types 44
Environment files, upgrading 80
ExpertSelect 23
functionality 23
F
File
colordef.dat 71
extensions 68
fv_blink.dat 73
Inital.mbr 77
Initial.env 77
menu bar 77
user edits to standard file 69
Font files 55
FoxAPI 68
FoxDraw
browser capability 68
file extensions 68
using the FoxAPI 68
versus Display Builder and Display Configurator 68
FoxSelect 86
calling up 85
using 86
versus Select Screen 68
FoxView
file extensions 68
getting started with 85
upgrading from Display Manager 67
using 85
129
B0193MQ Rev M Index
versus Display Manager 67

FPDESCn, keyword 62
fv_blink.dat file 73
G
Globals, protecting 83
I
Initial.env file 77
Initial.mbr file 77
L
Ladder display
access 49
configuring location 49
installing on local disk 52
installing on logical host 52
relocate 50
workstation access 51
Layout requirements for database file 62
Licensing 11
Limiting access
to Alarm Manager from remote terminals 14
to Display Manager from remote terminals 14
within a Display Manager 17
within an Alarm Manager 17
M
Marker files 55
Menu bar definition files 35
Menu bar file 77
Menu button definition files 36
Menu definition file
sample 78
Menu definition files 43
Menu entry
cascading 42
command 41
SEPARATOR 41
Menu variable
SELBLOCK 43
SELCOMP 42
SELDISP 42
SELTAG 42
Message bar 87
Mode, select and assign 84
Multi-headed WP51/AW51 stations 5
130
Index B0193MQ Rev M
Multiple
alarm managers 7
display managers 7
N
NAME, keyword 62
O
Object Manager
connections 8
list 9
Object menus 44
Operation code 40
P
Palette, converting 71
Parameter database functions 59
PARAMS, keyword 63
Previous display, calling up 85
Process button 83
protect 29, 30
Pulldown file 29
Pull-down menu access control 29
R
RAL for DMs, accessing 12
Remote AMs 12
Remote DMs 12
Resource Allocation Levels (RAL) 12
S
SCALE, keyword 63
ScratchPad group displays
installation procedures 90
installed components 95
common files 96
environment files 96
overview 89
procedures 106
accessing group_list 106
adding faceplates and trends to group display 110
adding pens to trend overlay 113
creating a group display on group_list 107
editing trend settings 115
saving changes to group configuration 113
saving the pens of a trend 114
131
B0193MQ Rev M Index
ScratchPad trends
installation procedures 89
installed components 90
common files 93
environment files 91
overview 89
procedures
accessing trend_list 98
adding pens to a trend 101
creating a new trend on trend_list 99
editing trend settings 103
saving pens of a trend 102
SCREEN definition 121
Security 14
SELBLOCK menu variable 43
SELCOMP menu variable 42
SELDISP menu variable 42
Select and assign mode 84
SELTAG menu variable 42
SEPARATOR menu entry 41
Sequence code, access 52
Shortcut menu 40
examples 40
styles 44
types 44
Software, upgrading from Display Manager to FoxView 67
Standard files, user edits to 69
Status bar 87
STRINGS, keyword 63
System
button 83
T
Trending, database parameters 64
TRENDING, keyword 64
TYPE definition 121
DM window property 122
TYPE, keyword 62
U
Unprotect 29, 30
W
Windows Off Mode 11
WP configuration option 51
132
Index B0193MQ Rev M
133
B0193MQ Rev M Index
33 Commercial Street
Foxboro, Massachusetts 02035-2099
United States of America
www.foxboro.com
Inside U.S.: 1-866-746-6477
Outside U.S.: 1-508-549-2424 or contact your local Foxboro representative.
Facsimile: 1-508-549-4999
Printed in U.S.A. 0907

b0193mq M

Caricato da

Informazioni sul documento

Titolo originale

Copyright

Formati disponibili

Condividi questo documento

Condividi o incorpora il documento

Opzioni di condivisione

Hai trovato utile questo documento?

Questo contenuto è inappropriato?

Copyright:

Formati disponibili

b0193mq M

Caricato da

Copyright:

Formati disponibili

B0193MQ

Copyright 1993-2007 Invensys Systems, Inc.

SOFTWARE LICENSE AND COPYRIGHT INFORMATION

2. Dual-Headed Workstations ............................................................................................... 5

3. Multiple FoxViews, Display Managers, and Alarm Managers............................................ 7

5. Pull-Down Menu Access Control .................................................................................... 29

6. Configuring and Assigning Passwords for FoxView Environments.................................. 33

Environment Shortcut Menu Styles ................................................................................... 44

7. File Access ....................................................................................................................... 47

9. Upgrading from Display Manager to FoxView ................................................................ 67

Converting a Display File ........................................................................................................ 70

10. ScratchPad Group and Trend Displays.......................................................................... 89

Appendix A. Multiple Display Window and AM Configuration ....................................... 117

Index .................................................................................................................................. 127

Workstation Alarm Management (B0193RV)

Multiple Instances of FoxView, Display Manager and

Designing Displays Using ExpertSelect Functionality

Setting Display Resolution and Colors 70 Series

Figure 1-1. Setting Display Resolution and Colors

50 Series Dual-Headed WorkStations

70 Series Dual-Headed WorkStations

To verify the number of licenses available for additional FoxViews on a WP51/AW51:

Figure 3-1. DM_Usage Display WP51/AW51

Alarm Manager Considerations

Starting Up Additional FoxViews, DMs or AMs

Windows Off Mode

Stopping Additional FoxViews, DMs and AMs

Dedicated FoxViews, DMs and AMs and Licensing

Remote FoxViews, DMs and AMs

Dynamic Resource Allocation

DM Class Resource Allocation Level (RAL)

A FoxView/DM with RAL=4 adjusts its RAL as follows:

Instructions for Editing the Initial RALs

DM_DLEVEL=0 # default level for default DM

Accessing WP51/AW51 CPU Idle Time and RAL for DMs

WPIDLE<stationlbug> An Object Manager shared variable of type float containing

Limiting Access to FoxView, DM, or AM from Remote Terminals

#NAME <lbug> <dmname> <dedicated <type>

#AMNAM <lbug> <amname> <dedicated <type>

The following example includes an additional DM dedicated to a specific remote terminal.

#NAME <lbug> <dmname> <dedicated <type>

#NAME <lbug> <dmname> <dedicated <type>

Limiting Access within a DM or AM

These environments contain the following commands:

dmcmd nologscr # delay oaj logging until after password

protect all # Initially, protect all access locks

dmcmd button 0 Sys /usr/fox/sys

protect all # Initially, protect all access locks

dmcmd button 0 Sys /usr/fox/sys

protect all # Initially, protect all access locks

dmcmd button 0 Sys /usr/fox/sys

Display Manager ExpertSelect Functionality

Evaluation of Object Manager Data Values in Display

Support for Named Actions

Display Commands Embedded in Display Files

Embedded Post Call-up Script:

Operation: If BLOCK1 is in manual, pick output

Actual Script: = P1 COMPOUND:BLOCK1

Pick Operation: If BLOCK1 is in manual, pick output

Active Connection: Set relative pick

Pick Operation: Set relative pick to SPT

Figure 4-1. Generic Overlay Using ExpertSelect Functionality

Pick Operation: If BLOCK1 is in manual, pick output