B0193wu A

® B0193WU
REV A
I/A Series®
Display Engineering Utilities
November 30, 1998
B0193WU – Rev A
Foxboro, Fox, and I/A Series are registered trademarks of The Foxboro Company.
Windows NT is a trademark of Microsoft Corporation.
Solaris is a trademark of Sun Microsystems, Inc.
Copyright 1998 by The Foxboro Company

All rights reserved
ii
Contents
Preface............................................................................................................................. vii
Purpose ........................................................................................................................ vii
Audience ...................................................................................................................... vii
Revision Information .................................................................................................... vii
Document Conventions .............................................................................................. viii
Reference Documents .................................................................................................... ix
1. Overview of Utilities ................................................................................................... 1

Conversion and Migration of User Interface Applications ................................................... 1
Engineering Utilities ........................................................................................................... 1
2. Converting WP20/WP30 Files to 50 Series Format .................................................... 3

Converting WP20/WP30 Format Display Files to 50 Series Format ................................... 3
Command Syntax ........................................................................................................... 4
Examples ........................................................................................................................ 5
Error Handling ............................................................................................................... 5
Output ........................................................................................................................... 5
Converting WP20/WP30 Format Libraries to 50 Series Format ......................................... 5
Command Syntax ........................................................................................................... 6
Example ......................................................................................................................... 7
Error Handling ............................................................................................................... 7
Output ........................................................................................................................... 7
Converting WP20/30 Format Fonts and Markers to 50 Series Format ................................ 8
Converting Fonts and Markers to Other Sizes ................................................................ 8
Converting WP20/WP30 Color Palette Files to 50 Series Format ..................................... 10
Converting Environment Files .......................................................................................... 11
Command Syntax ......................................................................................................... 11
Error Handling ............................................................................................................. 11
Output ......................................................................................................................... 11
3. Converting 50 Series Files to WP20/WP30 Format .................................................. 15

Converting 50 Series Display Files to WP20/WP30 Format ............................................. 15
Command Syntax ......................................................................................................... 15
Examples ...................................................................................................................... 16
Error Handling ............................................................................................................. 16
Compatibility Issues ..................................................................................................... 16
Output ......................................................................................................................... 17
Bit Acronym Replacement ............................................................................................ 18
iii
B0193WU – Rev A Contents
Converting 50 Series Libraries, Fonts, Markers, Color Palettes, and Environments to

WP20/WP30 Format ........................................................................................................ 18
4. Converting from Display Manager to FoxView ......................................................... 19

What Needs to be Converted from Display Manager to FoxView Format ......................... 19
Display Names .................................................................................................................. 19
Converting and Modifying Display Manager Files ............................................................ 19
FoxView/FoxDraw File Extensions ............................................................................... 20
The /opt and /usr Directories ....................................................................................... 20
User Edits to Standard Files .......................................................................................... 21
Converting Displays ..................................................................................................... 21
Converting Custom Markers ........................................................................................ 23
Converting a Customized Color Palette ........................................................................ 24
Copying colordef.dat .................................................................................................... 25
Editing colordef.dat ...................................................................................................... 25
Configuring Blinking Colors ........................................................................................ 27
Copying fv_blink.dat ............................................................................................... 27
Editing fv_blink.dat ................................................................................................. 27
Upgrading Customized Environment Files - Overview ................................................. 29
Sample FoxView Environment File (Initial.env) ...................................................... 30
Sample Menu Bar File (Initial.mbr) ......................................................................... 31
Sample Menu Definition File (file.mnu) .................................................................. 32
Example: Upgrading Display Manager Environment Files to FoxView .................... 32
Display Bar Configuration Menu ............................................................................. 34
Protecting Display Bar Menu Picks, System and Process Buttons, and Select/Assign .... 34
System and Process Buttons ..................................................................................... 35
Select and Assign Mode ........................................................................................... 36
5. Moving FoxView Display Files Between Windows NT and Solaris ........................... 37

Moving Displays and Library Objects ............................................................................... 37
Converting Display and Library Objects ....................................................................... 37
Changing Foxboro Display File Format ................................................................... 37
Converting Displays ................................................................................................. 38
Converting Library Objects ..................................................................................... 39
Converting Displays with Bitmaps ........................................................................... 40
Moving .g Files ............................................................................................................. 40
Converting ASCII Files to FoxView Format ................................................................. 40
Moving Environment Files ................................................................................................ 40
Known Issues in Moving Files Between Platforms ............................................................. 40
6. Engineering Utilities ................................................................................................. 43

Obtaining Information About Windows and Moving Windows (show_win) .................... 43
Examples ...................................................................................................................... 43
iv
Contents B0193WU – Rev A
Adjusting Touchscreens (ts_util) ....................................................................................... 43

Eliminating Touchscreen Interference .......................................................................... 43
Adjusting Touchscreen Sensitivity ................................................................................ 44
Copying and Converting Display Files Between 50 Series workstations (getremfiles) ........ 44
Command Syntax ......................................................................................................... 45
Example ....................................................................................................................... 46
Editing Display Manager Environments (dmsepass) .......................................................... 49
Command Syntax ......................................................................................................... 49
Example ....................................................................................................................... 49
Updating Display Files (cvupdate_wp50) .......................................................................... 50
Command Syntax ......................................................................................................... 50
Updating Display Builder Graphics History Offsets (hist_offset) ...................................... 50
Command Syntax ......................................................................................................... 51
Examples ...................................................................................................................... 51
Appendix A. Converting Display Manager Files to FoxView Format

from a Command Window ........................................................................................... 53
Copying Display Manager Displays .................................................................................. 53
Converting the Displays .................................................................................................... 53
Examples ...................................................................................................................... 54
Upgrading Displays for the 6.0 Release ......................................................................... 54
Converting Customized Markers ....................................................................................... 55
Creating Bitmap Display Bar Files .................................................................................... 55
Index .............................................................................................................................. 57
v
B0193WU – Rev A Contents
vi
Preface
Purpose
This document describes two types of utilities:
♦ Conversion utilities
♦ Engineering utilities
Audience
This document is intended for users who must:
♦ Migrate I/A Series Display Builder/Display Manager human interface applications
between WP20/WP30 and 50 Series platforms
♦ Migrate I/A Series Display Builder/Display Manager applications on 50 Series
platforms to FoxView/FoxDraw
♦ Move FoxView/FoxDraw applications between Solaris and Windows NT
platforms
♦ Maintain I/A Series workstations
This document assumes that you are familiar with the I/A Series system and the UNIX
operating system.
Revision Information
This is the first issue of this document. Portions of this document were extracted from
I/A Series Release 6.0 documents.
vii
B0193WU – Rev A Preface
Document Conventions
The paper form of this document uses these typographical conventions (fonts).
Example Purpose
Enter date (mm/dd/yy): In an example, shows the workstation’s output or
display
AMNAME 54AW51 54AW51 .- foxDefault In an example, shows actual content of a file.
almack or dmcmd In a paragraph, identifies the name of a command
or utility.
COMPOUND:BLOCK.PARAMETER.bitex- In a syntax statement, shows parts of a command.
tension
cd \usr\display In an example, shows a user entry.
Process or File or Save In a paragraph, identifies a button, field, or menu
item on the workstation’s user interface.
bold text In a paragraph, emphasizes a word.
Workstation Alarm Management In a paragraph, identifies the name of a
document.
The on-line form of this document uses these typographical conventions (fonts).
Example Purpose
Enter date (mm/dd/yy): In an example, shows the workstation’s output or
display.
AMNAME 54AW51 54AW51 .- foxDefault In an example, shows actual content of a file.
almack or dmcmd In a paragraph, identifies the name of a command
or utility.
compound:block.parameter.bitextension In a syntax statement, shows parts of a command.
cd \usr\display In an example, shows a user entry.
Process or File or Save In a paragraph, identifies a button, field, or menu
item on the workstation’s user interface.
bold text In a paragraph, emphasizes a word.
Workstation Alarm Management In a paragraph, identifies the name of a document.
viii
Preface B0193WU – Rev A
This document uses the following terms.
Term Meaning
display manager The user interface to the process (Display Manager or FoxView)
Display Manager The traditional (Pre-V5.0) display manager
FoxView The new (V5.0 or later) display manager
Remote terminal A terminal running X-Windows
Reference Documents
Refer to these documents for additional information:
♦ Workstation Configuration (B0193AG)
♦ Process Alarm Configuration (B0193AU)
♦ Process Alarm Configuration (FoxPanels Configuration for Windows NT and Solaris)
(B0400AU)
♦ Workstation Alarm Management (B0193RV)
♦ FoxView (B0193WH)
♦ FoxDraw (B0193WG)
♦ Display Configurator for 50 Series Workstations (B0193NL)
♦ Display Builder for 50 Series Workstations (B0193MP)
♦ Display Manager/FoxView Calls (B0193DF)
♦ FoxDraw/FoxView Release Notes (B0193WL)
♦ Display Reporter and Connection Editor (B0193JN)
♦ Grouped Object Editor for Displays (B0193DV)
Also refer to the on-line Help for these applications:
♦ Alarm/Display Manager Configurator
♦ Alarm Manager
♦ FoxView (available only on Windows NT)
♦ FoxDraw
ix
B0193WU – Rev A Preface
x
1. Overview of Utilities
This chapter describes the focus of the book’s two chapters.
This document is divided into two sections. Both are organized by task.
♦ Conversion and migration of user interface applications
♦ Engineering utilities
Conversion and Migration of User Interface

Applications
These are the tasks:
♦ Moving I/A Series human interface applications using the Display Builder and
Display Manager between WP20/WP30 platforms and 50 Series platforms.
♦ Converting I/A Series human interface applications utilizing Display Builder
and Display Manager to FoxDraw and FoxView.
♦ Moving I/A Series human interface applications utilizing FoxDraw and
FoxView between 50 Series and 70 Series platforms.
Engineering Utilities
You use engineering utilities for:
♦ Adjusting and maintaining touchscreens.
♦ Moving files between workstations.
♦ Maintaining reporting and editing functions for display files.
1
B0193WU – Rev A 1. Overview of Utilities
2
2. Converting WP20/WP30 Files
to 50 Series Format
This chapter describes how you convert WP20/WP30 files to 50 Series format.
The following 50 Series utility programs are available to convert WP20/WP30 display files,
display libraries, fonts, and markers into 50 Series format.
Utility Purpose
convdisp2_50 Converts WP20/WP30 display files on the 50 Series workstation disk to
50 Series format.
convdisp2_20 Converts 50 Series display files on the 50 Series workstation disk to
WP20/WP30 format.
convlib2_50 Converts WP20/WP30 display libraries on the 50 Series workstation disk
to 50 Series display templates (not libraries).
cvtfonts Converts WP20/WP30 display fonts on the 50 Series workstation disk to
50 Series font files.
cvtmarkers Converts WP20/WP30 display markers on the 50 Series workstation disk
to 50 Series marker files.
cvtpal Converts WP20/WP30 color palette on the 50 Series workstation disk to
50 Series color palette.
cvtenv Converts WP20/WP30 environment definition files on the 50 Series
workstations to 50 Series script files.
Since the conversion programs run on 50 Series workstations, you must copy the
WP20/WP30 format files to the 50 Series workstation before converting the files to 50 Series
format.
Other display-related files for use with 50 Series workstations are listed below.
♦ Environment files: refer to “Converting Environment Files” on page 11.
♦ Alarm Panel configuration: refer to Process Alarm Configuration (WP20/30, PW
and WP/AW50) and Workstation Alarm Management (WP/AW51).
♦ Alarm Table configuration: refer to Process Alarm Configuration (WP20/30, PW
and WP/AW50) and Workstation Alarm Management (WP/AW51).
Converting WP20/WP30 Format Display Files to

50 Series Format
Use the 50 Series convdisp2_50 utility to convert WP20/WP30 packed display files into
50 Series packed display files.
3
B0193WU – Rev A 2. Converting WP20/WP30 Files to 50 Series Format
Before displaying WP20/WP30 display files, convert and pack them on a 50 Series worksta-
tion. This makes the binary data contained in these files compatible with the data representa-
tion method of 50 Series workstations. convdisp2_50 automatically repacks the display files,
which are approximately double the size of the WP20/WP30 files.
WP20/WP30 display files can display on 50 Series workstations. The 50 Series Display Man-
ager converts these files “on-the-fly”, but this is not efficient because they are converted and
saved to a temporary file. Therefore, they must be converted each time they are invoked.
The file propagation program getremfiles calls convdisp2_50 to convert WP20/WP30 dis-
play files to 50 Series format. Because getremfiles simplifies the file copying and conversion
process, use getremfiles to convert WP20/WP30 display files to 50 Series display files.
If you use convdisp2_50, you must first copy the display files to the 50 Series workstation. By
default, convdisp2_50 replaces the WP20/WP30 display file with the 50 Series file. Using the
-o option keeps the WP20/WP30 display files on the disk, with the “ia16” extension added to
the file names.
Do not run file conversions recursively from the root directory. The utility for converting dis-
play files from WP20/WP30 format to 50 Series format must be run only on directories con-
taining display files and any subdirectories as needed, and not on higher-level directories,
which may contain other types of files. In particular, do not attempt to recursively convert all
files in “/” or “/usr”.
For example, if displays files are located in /usr/menus1 and /usr/menus2 on a WP50, use the
commands:
convdisp2_50 /usr/menus1
convdisp2_50 /usr/menus2
! CAUTION
Do not use the command: convdisp2_50 -r /usr
Command Syntax
The command line syntax for convdisp2_50 is:
convdisp2_50 [-r] [-n number_stations] [-o] [-s] filename...
where:
-r Recursively converts directories and subdirectories. You can pass a combination
of file names and directory names on the command line. If you pass any directo-
ries, use the -r option.
-n Sets the size of the network address table in the header of the display file to
between 0 and 31. The default table size is that of the WP20/WP30 display file.
-o Keeps the original WP20/WP30 file on the disk by renaming it to
<filename>.ia16.
-s Operates silently.
filename Is a list of packed display files and/or directories to be converted and packed.
4
2. Converting WP20/WP30 Files to 50 Series Format B0193WU – Rev A
Examples
1. The following command saves a WP20/WP30 packed display file called file2 as
file2.ia16, and converts file2 to a 50 Series packed display file of the same name
with a network address table size of 31:
convdisp2_50 -n 31 -o file2
2. The following command converts a directory of WP20/WP30 packed display files
called dir1 and its subdirectories into 50 Series packed display files:
convdisp2_50 -r dir1
NOTE
If convdisp2_50 finds any files in the directory that are not packed display files,
it displays an error message and continues on to the next file until all files in the
directory have been processed.
Error Handling
When convdisp2_50 finds a display file with an error, it displays an error message, does not
alter the file, adds the .ia16 extension to the file name, and continues on to the next file. It
does not alter files that are not packed display files. Only a major system error, such as a mem-
ory allocation error, stops the conversion process.
If the command line syntax is in error, convdisp2_50 exits and displays a usage message.
Output
The converted files are binary data files, compatible only with the 50 Series Display Manager.
The new file format header files are in:
usr/include/fox/df64*.h
convdisp2_50 prints a log of the conversion process to the screen. If you want to generate a
log file, redirect this output to a file as shown in the following example:
convdisp2_50 -r /usr/menus >/usr/fox/wp/data/conv2_50.log 2>&1
Converting WP20/WP30 Format Libraries to 50 Series

Format
Use the 50 Series convlib2_50 utility to convert WP20/WP30 display libraries into 50 Series
packed display files.
The 50 Series workstations do not use display libraries. You cannot convert 50 Series display
files to WP20/WP30 display libraries.
First, you must copy the WP20/WP30 libraries to be converted onto the 50 Series worksta-
tion disk into the proper directory, for example, /usr/displib.
Converting WP20/WP30 Format Libraries to 50 Series Format 5

The converted files are placed in a directory named as the base name of the converted library.
Each file is given the name of the original library entry. For example, if the library user.lib
contains two entries named Entry1 and Entry2, the converted files are:
user/Entry1
user/Entry2
Since these library entries are now individual files, certain ACSII characters are not allowed.
These characters are:
# $ ^ & * ( ) | \ / ; ' “ ` < > ? SPACE TAB NEWLINE
If the entry name contains any of the above-listed invalid character(s), the invalid character(s)
are replaced with underscores. Then, a unique extension is added to the filename.
For example, if the entry name has a space in it, as in the entry “Group trend”, the space is
replaced by an underscore, resulting in “Group_trend”. After “Group trend” is changed to
Group_trend, a unique extension is added to prevent the same named file being created as a
result of other underscore replacements. The extension is really a counter (starting at 0) and
reset to 0 when processing a new library. For each library, the first modified filename has “00”
appended to the file name. The second modified file name has “01” appended, and so on.
Thus, the original entry “Group trend” is changed to file name Group_trend00. If the file
name is modified, a warning message displays to report the old and new file names.
The convlib2_50 command line accepts multiple library files, multiple directories, or a com-
bination of both, converting each in the order that they are passed on the command line.
Options are passed from convlib2_50 to the convdisp2_50 utility. This allows network
address size flags to be passed to convdisp2_50. Because convlib2_50 is designed to handle
multiple library files or directories in a single invocation, it does not exit on individual file
errors.
If the utility finds a library file it cannot fully convert for any reason (such as: it is not a dis-
play library file, the file does not exist, or the source library file is corrupt) an error is returned
when the program exits.
If all libraries are converted without error, a 0 is returned; otherwise a 1 is returned.
The background color for each of the entry displays is not stored in the library file. All
extracted displays have a background color of light grey. Light grey is the default color for base
displays.
Command Syntax
The command line syntax for convlib2_50 is:
convlib2_50 [-f] [-n number_stations] [-o] [-r] [-s] filename...
where:
-f Forces the new directory to overwrite any previous conversion of a file of this
name. The default is not to convert this library if the directory exists.
-n Sets the size of the network address table in each extracted file to be
between 0 and 31.
6
-o Leaves the original source library and WP20/WP30 format files on the
disk after they are converted. With this option, the final directory contains
two copies of each extracted file, one in WP20/WP30 format and one in
50 Series format, and the source library is moved to <libname>.ia16. The
default is to remove all WP20/WP30 files that convert without error.
-r Recursively converts directories and subdirectories of library files, if found.
You can pass a combination of filenames and directory names on the com-
mand line, but if any directories are passed, the -r option must be present or
directories are not converted and an error message is displayed. The default is
not to convert directories.
filename Is a list of library files and/or directories to be converted and packed.
Example
1. The following command converts a display file library called Faceplates.lib to mul-
tiple 50 Series packed files in the directory called Faceplates:
convlib2_50 Faceplates.lib
A directory called Faceplates is created in the current directory. If the conversion
was successful, Faceplates.lib is deleted and the new directory Faceplates is filled
with the extracted files in 50 Series display file format.
2. The following command converts a directory of display file libraries into multiple
directories of 50 Series packed display files:
convlib2_50 -r /usr/displib
Each library in the directory /usr/displib has its own directory and its extracted
files are placed in that directory. If convlib2_50 finds any files in the /usr/displib
directory that are not display library files, it displays an error message and contin-
ues on to the next file until all files in displib have been processed.
Error Handling
If convlib2_50 finds any files that are not display library files, it displays an error message and
continues on to the next file. Only a major system error, such as a memory allocation error,
stops the conversion process.
If the command line syntax is in error, convlib2_50 exits and displays a usage message.
Output
The converted libraries are compatible only with the 50 Series Display Manager.
convlib2_50 prints a log of the conversion process to the screen. If you want to generate a log
file, redirect this output to a file as shown in the following example:
convlib2_50 -r /usr/displib >/usr/fox/wp/data/conv2_50.log 2>&1
Converting WP20/WP30 Format Libraries to 50 Series Format 7

Converting WP20/30 Format Fonts and Markers to

50 Series Format
You can convert WP20/30 format fonts and markers to 50 Series format.
Converting Fonts and Markers to Other Sizes

To convert a font or marker to other sizes, run the font_expand and font_shrink utilities in
/usr/fox/wp/bin/tools and directly specify the required input and output file names. These are
the most common options:
Marker to full size:
font_expand -L -o “output” “source”
Marker to half-width, half-height:
font_shrink -o “output” “source”
Font to single width, double height:

font_expand -h -o “output” “source”
Font to double width, single height:
font_expand -w -o “output” “source”
Font to double width, double height:

font_expand -200 -o “output” “source”
Use the cvtfonts and cvtmarkers utilities to convert WP20/30 font and marker files to
50 Series format.
A procedure is provided to convert WP20/30 font and marker files to 50 Series format. This
procedure involves typing one of the following from a VT100 window:
cvtfonts fontfile.gc3
or
cvtmarkers markerfile.gc3
where fontfile can be sys_fnt or sys_fnt1 and markerfile can be usr_mkr or usr_mkr1.
This procedure involves first converting the file from Intel to Sun format for the Foxboro
default window size, then deriving the other sizes (such as double-wide/single-high, single-
wide/double-high, and so on) from that default size file.
The initial conversion and the subsequent derived sizes are not perfect because the scale factor
is not a whole number. This introduces anomalies in the converted fonts or markers. These
anomalies become even more exaggerated when expanding the files such as when doubling
the height or width. The only way to fix this is to use the Font Editor and to manually
smooth out or fine tune the converted files (for example, usr_mkr.bdf and usr_mkr1.bdf).
The cvtfonts and cvtmarkers utilities allow you to stop the conversion process after the initial
conversion. The following prompt occurs.
At this time, you may elect to interrupt the conversion procedure to fine-tune
this file using the Font Editor before the other sizes are derived from it.
If you do so, you may resume the conversion later using the “-r” option.
8
Do you want to continue the conversion now (y/n)?

This allows the basic default size to be fine tuned before deriving other files from it and pre-
vents the derived files from exaggerating any anomalies.
To resume the conversion after modifying the default size, use the “-r” option as follows:
cvtfonts -r fontfile.gc3
or
cvtmarkers -r markerfile.gc3
Note that the extension is the same (for example, .gc3) as that specified when the conversion
was initially specified (not .bdf). Although smoothing the default size file produces an
improvement in the derived sizes, it is not as good as manually fine tuning each of the derived
files. For example, any curved segments that are in the default size becomes more jagged in the
derived sizes.
The recommended procedure is to stop the conversion after the initial conversion, fine tune
the default file using the Font Editor, resume the conversion using the -r option, and then
fine tune the derived files using the Font Editor.
To do this, you need to know the names of the files to edit. The files are in the
/usr/fox/wp/fonts directory, which is the default directory displayed when the Font Editor is
invoked.
For example, if you are converting usr_mkr.gc3, edit these files edit using the Font Editor:
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.
If you are converting usr_mkr1.gc3, these are the files you should edit using the Font Editor:
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.
If you are converting sys_fnt.gc3, edit these files using the Font Editor:
ia0swsh.bdf The default window size version.
ia0swdh.bdf The single-width/double-height size.
ia0dwsh.bdf The double-width/single-height size.
ia0dwdh.bdf The double-width/double-height size.
ia0hwhh.bdf The half-width/half-height size (small) version.
Lia0swsh.bdf The full-screen window size (large) version.
Lia0swdh.bdf The full-screen single-width/double-height size.
Lia0dwsh.bdf The full-screen double-width/single-height size.
Lia0dwdh.bdf The full-screen double-width/double-height size.
If you are converting sys_fnt1.gc3, substitute ia1 for ia0 in the above filenames.
Converting WP20/30 Format Fonts and Markers to 50 Series Format 9

Run install_fonts from a VT100 window when you have finished modifying all the files using
the Font Editor. Also, after running install_fonts, exit applications that have open windows
and restart them to use the modified fonts or markers.
If a WP20/30 marker file was converted on a release prior to V3.2, the full-screen (large) size
and half-width/half-height size files were not automatically generated. To generate these sizes
without going back to the original WP20/30 file and reconverting it, perform the following
from a VT100 window:
cd /usr/tmp
cvtmarkers -r usr_mkr.gc3
or
cvtmarkers -r usr_mkr1.gc3
Each time a conversion procedure is run, you are queried whether to back up the existing files.
This backup is made by copying the default size files and all of its derivatives to the
/usr/fox/wp/fonts/backup directory.
To restore files from the backup, perform the following (assuming you want to restore all the
files related to usr_mkr):
cd /usr/fox/wp/tmp/backup
ls (to verify that the files to be restored are there)
cp *usr_mkr.* ..
xset fp rehash
Then, any applications that have open windows must be restarted to use the restored fonts.
Rebooting the station also accomplishes this.
To restore files related to usr_mkr1, substitute the following in place of the cp line above:
cp *mkr1.* ..
To restore files related to sys_fnt, substitute the following in place of the cp line above:
cp *ia0* ..
To restore files related to sys_fnt1, substitute the following in place of the cp line above:
cp *ia1* ..
Only the most recently backed up copies of files are available to be restored. No historical
record is kept of versions of files from multiple backups.
Converting WP20/WP30 Color Palette Files to

50 Series Format
You can convert color palettes from WP20/WP30 format to 50 Series format with the cvtpal
utility.
To convert a WP20/WP30 Color Palette File to 50 Series Format:
1. From a local VT100 window on a 50 Series workstations, mount the source AP20
by entering:
10
rmount <source_AP> /rem/<source_AP>

2. Copy the WP20/WP30 color palette file to the /usr/fox/wp/data directory on a
50 Series workstation. For example, enter:
cd /usr/fox/wp/data
cp /rem/<source_AP>/usr/fox/hi/sys_pal.gc3 .
Run the cvtpal utility. For example, enter:
cd /usr/fox/wp/data (if you are not already in that directory)
cvtpal sys_pal.gc3 > new_pal
3. If you want the WP50 or AW50 to use the new file at the next reboot, back up the
default file /usr/fox/wp/data/sys_pal.wp50, if it exists. Then, rename the new file
to the default file name. For example, enter:
mv sys_pal.wp50 sys_pal.wp50.bak
cp new_pal sys_pal.wp50
The new colors do not take effect until the station is rebooted.
Converting Environment Files

You can convert environment files from WP20/30 format to 50 Series format with the cvtenv
utility.
WP20/30 environment definition files must be converted to ASCII Display Manager script
files for use on the 50 Series. The ASCII format of these files allows editing of the files with a
standard text editor, such as vi.
Command Syntax
The command line syntax for cvtenv is:
cvtenv [-f pwfilename] [-o] filename(s)
where:
filename(s) Is a list of environment files to be converted.
-f Sets the password file name to other than the default. The default is
/usr/fox/wp/data/dmpasswd_cfg.
-o Keeps the old (unconverted) file on the disk, renamed as filename.ia16.
Error Handling
Errors encountered while converting a list of environment files do not stop the conversion
process. Errors leave the original file untouched.
Output
The converted file is an ASCII Display Manager command file with the general format:
dmcmd nologscr
dmcmd passwd
Converting Environment Files 11

dmcmd chng_env
dmcmd button butno label path
dmcmd DMbuiltin
where:
butno Top button (1 - 10).
label Button label (if label is null, button is removed).
path Path name (or command text) to be executed when button is
picked. (If path is null, button definition is left untouched.)
DMbuiltin Display Manager command.
For example, conversion of the Init_Env produces the following file:

dmcmd nologscr
dmcmd passwd
dmcmd chng_env
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 “”

Note the use of double quotes around commands. This allows single quotes inside the com-
mand itself; for example:
“” dmcmd msgln “Environment: Init_Env” “”
Follow and precede the double quote with spaces.
As part of the conversion process, a password configuration file is generated, or information is
appended to the existing file. This file has the following format:
user_id:encrypted_password:description
The password information is stored in this file. An entry is made for each converted environ-
ment file, even if there is no password configured, as this file also stores the environment
description.
A log of the conversion process is printed to the screen. Redirect this output to a file if a log
file is desired.
If Environment Files (typically, those files in /usr/fox/sys/Change_Env) do not work properly
on the 50 Series station after having been converted from WP20/30 format, it may be because
12
the original files contained trailing blanks. If this occurs, edit the converted file with any text
editor to remove any trailing blanks. The buttons should then operate normally.
Refer to Display Manager/FoxView Calls for a description of the commands used in this con-
version process.
Since the converted files are standard Display Manager scripts, you can insert access level set-
tings directly in environment script files, without taking up a “button” slot, and without writ-
ing separate “pre-environment file” scripts. In addition, you can include any other Display
Manager command (such as message line text, standard display for the environment, and so
on) in the converted environment file.
You can add the passwd built-in to any script file to provide password protection in general
scripts.
Converting Environment Files 13

14
3. Converting 50 Series Files to
WP20/WP30 Format
This chapter describes how to convert 50 Series files to WP20/WP30 format.
Converting 50 Series Display Files to WP20/WP30

Format
Use the 50 Series convdisp2_20 utility to convert 50 Series packed display files into
WP20/WP30 packed display files.
Before displaying the 50 Series display files, you must convert and pack them on the WP20 or
WP30. Object Manager (OM) optimization information is lost on the conversion.
The file propagation program getremfiles calls convdisp2_20 to convert 50 Series display
files to WP30 format. Because getremfiles simplifies the file copying and conversion process,
use getremfiles to convert 50 Series display files to WP30 display files.
Use the convdisp2_20 utility to convert 50 Series display files to WP20 files, because the
header in WP20 display files has a maximum network address table size of 12, as compared to
30 on the WP30. You cannot use getremfiles to set the network address table size of display
files for use on the WP20.
If you use convdisp2_20 , copy the display files to a temporary directory to avoid inadvert-
ently losing the 50 Series files. By default, convdisp2_20 replaces the 50 Series display file
with the WP20/WP30 file. Using the -o option keeps the 50 Series display file.
NOTE
Do not copy display files to the /usr/tmp directory, because getremfiles uses this
directory for temporary storage. For temporary storage, copy display files to
another temporary directory.
Command Syntax
The command line syntax for convdisp2_20 is:
convdisp2_20 [-n number_stations] [-o] [-r] [-s] filename...
where:
-n Sets the size of the network address table in the header of the display file to be
between 0 and 30. WP20s require a value of 12 or less. See the NOTE below.
-o Keeps the original 50 Series file on the disk by renaming it to <filename>.ia64.
-r Recursively converts directories and subdirectories. You can pass a combination of
file names and directory names on the command line. If you pass any directories,
use the -r option.
15
B0193WU – Rev A 3. Converting 50 Series Files to WP20/WP30 Format
filename Is a list of packed display files and/or directories to be converted and packed.
NOTE
The 50 Series format permits a maximum of 31 stations in the network address.
table. The WP30 format permits a maximum of 30 stations in this table. If the
input 50 Series file is configured for 31 stations and you do not use the -n
option, the table size is set to 30 stations in the output WP20/WP30 file and
does not connect on a WP20.
The WP10 and WP20 only support displays that connect to 12 stations. You must convert
50 Series displays that will be displayed on these WPs with the -n 12 option or modify them
with the WP20 or WP30 Display Builder after converting them.
Examples
1. The following command saves a 50 Series packed display file called file1 as
file1.ia64, and converts file1 to a WP20/WP30 packed display file of the same
name with a network address table size of 12:
convdisp2_20 -n 12 -o file1
2. The following command converts a directory of 50 Series packed display files
called dir1 and its subdirectories into WP20/WP30 packed display files:
convdisp2_20 -r dir1
If convdisp2_20 finds any files in the directory that are not packed display files, it displays an
error message and continues on to the next file until all files in the directory have been pro-
cessed.
Error Handling
When convdisp2_20 finds a display file with an error, it displays an error message, does not
alter the file, adds the .ia64 extension to the file name, and continues on to the next file. It
does not alter files that are not packed display files. Only a major system error, such as a mem-
ory allocation error, stops the conversion process.
If the command line syntax is in error, convdisp2_20 exits and displays a usage message.
Compatibility Issues
convdisp2_20 removes the following configurations, which are supported only in 50 Series
display files:
♦ Embedded scripts
♦ Action name records and references
♦ All commands containing backquote syntax
♦ All commands containing the else syntax
16
3. Converting 50 Series Files to WP20/WP30 Format B0193WU – Rev A
♦ All commands longer than 100 characters (length of WP30 Display Manager local
buffer) or commands longer than 78 characters containing a ’$’ (78 characters is
the length of the WP30 Display Configurator data input line)
♦ Some trend fields:
♦ Autoscale and related fields
♦ Merged vs. banded mode
♦ MDE configuration
♦ Various overlay positioning and sizing information
If an unsupported command is removed from a display file, convert2_20 notifies you with a
warning message. You are also notified if the file contains embedded scripts or action names.
An example of the warning message that the convdisp2_20 utility shows when an incompati-
ble (or missing) overlay file is used in a 50 Series display:
CRVT WARNING : FileName : Loosing Configuration Information :
Variable overlay.
In this case, the display file will be converted to 20 Series format, however, size and/or posi-
tion information may have been lost.
The following commands, which are not supported on the WP20/30 platform, are not
removed from the display file. These commands are ignored by WP20/30 Display Manager:
♦ pick
♦ lt
♦ le
♦ gt
♦ ge
♦ select_pt
♦ get_select_pt
♦ trend
NOTE
If the 20 Series display is modified and then converted back to the 50 Series, the
lost configuration information is not restored to the 50 Series display.
Output
The converted files are binary data files, compatible only with the WP20/WP30 Display
Manager.
convdisp2_20 prints a log of the conversion process to the screen. If you want to generate a
log file, redirect this output to a file as shown in the following example:
convdisp2_20 -r /usr/menus >/usr/fox/wp/data/conv2_20.log 2>&1
Converting 50 Series Display Files to WP20/WP30 Format 17

B0193WU – Rev A 3. Converting 50 Series Files to WP20/WP30 Format
Bit Acronym Replacement

When a connection contains only a single Boolean number or a list of them, or a bitmask, the
bit extension is not substituted. The following connection types are checked:
♦ Trend connection
♦ Execute Program, Relative Pick, Momentary Contacts
These Execute Program and Relative Pick acronyms are supported:
Acronym Arguments Substituted
toggle last argument
setb <pntname> argument (arg. #1)
= 2nd argument
setglbl 2nd argument
== arguments 1 and 2
!= arguments 1 and 2
subst argument 2
Converting 50 Series Libraries, Fonts, Markers, Color

Palettes, and Environments to WP20/WP30 Format
These files are not backwards convertible to the WP20/WP30 format.
18
4. Converting from Display
Manager to FoxView
This chapter describes how to convert Display Manager items for use by FoxView.
Installing this software does not affect any existing functionality. On Solaris systems, the Dis-
play Manager, Display Builder, and Display Configurator can still be used. FoxView and
FoxDraw are installed as additional applications, not as replacements for existing products.
What Needs to be Converted from Display Manager to

FoxView Format
♦ Display files, including display library objects (for example, custom faceplates)
♦ Custom markers
♦ Custom color palette
♦ Customized environment files. A set of new environment files has been provided.
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 dis-
play 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 fol-
lowing 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 are:
♦ Converting Display Manager display files
♦ Converting custom markers
♦ Merging custom color palette edits
♦ Upgrading customized environment files
19
B0193WU – Rev A 4. Converting from Display Manager to FoxView
FoxView/FoxDraw File Extensions

File extensions are helpful in identifying file types.
Extension File Type
.fdf FoxView display file
.pdf Name given to a converted Display Manager display
.g ASCII version of .fdf
.m1 FoxDraw library object
.m2 Optimized .m1 file
.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
modified 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 display files and Display Manager scripts) do not need to be changed.
NOTE
When you convert displays with the Convert option in FoxDraw (refer to “Con-
verting Displays” on page 21) be sure to specify the new directory (for example,
/opt/menus) in the Convert to a Different Directory field.
20
4. Converting from Display Manager to FoxView B0193WU – Rev A
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.
I/A Series Release Customer Edits
/usr/fox/wp/data /opt/customer/data
/opt/fox/displib /opt/customer/displib
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 Displays
NOTE
This conversion can only be done if the display manager files have a .pdf exten-
sion; otherwise, convert fails without an error message.
1. To convert Display Manager displays automatically in FoxDraw, choose Convert

from the File menu.
Figure 4-1. Select Display Conversion Dialog Box (PDF to FDF Selected)
2. In the Select Display Conversion dialog box, select PDF to FDF.

3. In the View group box, check Conversion Data and Error Messages to make
the conversion data file (log_conversion.dat) and the error log file
Converting and Modifying Display Manager Files 21

(logERR_conversion.dat) viewable in vi (Solaris) or Notepad (Windows NT). The

files are located in the target directory.
In the Target Directory group box, select create, then type /opt/menus, then
select OK. By default, converted files are written to the source directory.
4. Select Next for the PDF to FDF conversion options dialog box.
Figure 4-2. PDF (Packed Display File) Conversion Options Dialog Box
5. Select the Convert Faceplates Only option to convert 50 Series faceplate files
(.pdf format) to Foxboro library objects (.m1 format).
If you select the Retain .g Files option, the .g (ASCII) files that are created as an
intermediate step in the conversion process are saved to the target directory. You
will the .g format files for moving displays between Windows NT and Solaris
(refer to “Moving Displays and Library Objects” on page 37).
If you select the Recursively search directories option, the conversion utility
searches for PDF files in the directory you specify plus all subdirectories.
6. Select Next for the Files to Convert dialog box.
22
Figure 4-3. Files to Convert Dialog Box
7. Select the desired Display Manager files and click the Convert button.
Converting Custom Markers

New versions of the standard Foxboro markers are shipped with your system. If you created
customized markers using the Font Editor on UNIX and want to preserve them, convert
them to FoxDraw library objects (.m1 files).
1. To convert markers automatically in FoxDraw, choose Convert from the File
menu.
NOTE
To run the marker conversion utility from a command line, refer to “Converting
Display Manager Files to FoxView Format from a Command Window” on
page 53.
2. In the Select Conversion dialog box, select BDF (Bitmapped Distribution For-
mat, the 50 Series marker) to .m1 (FoxDraw library object).

Figure 4-4. Select Display Conversion Dialog Box (BDF to M1 Selected)
By default, converted markers are written to /opt/customer/displib/Markers. You

can use the Target Directory options to select or create a different directory, but
FoxView and FoxDraw expect the markers to be in the /opt/customer directory.
3. Select Next.
4. Choose Markers to convert.
5. Select Convert.
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 Palette Editor, you can determine any customized RGB values in the 50 Series color
palette, sys_pal.wp50, and then enter the values to 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 following 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
24
Color Index Red Green Blue

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
IMPORTANT: Do not edit the colordef.dat file in /usr/fox/wp/data. Copy the
file to /opt/customer/data and make the edits in the /opt/customer/data direc-
tory. This allows you to install future updates of FoxView/FoxDraw without
affecting your custom palette.
To copy the file:

♦ At a cmdtool or VT100 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 is as follows:
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
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
26

31 63 white
Configuring Blinking Colors

When an object is configured to blink, it blinks from its base color index, defined in color-
def.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 or Notepad on Windows NT).
Copying fv_blink.dat
NOTE
IMPORTANT: 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 with-
out affecting your custom blink-to colors.
To copy the file:

♦ From a cmdtool or VT100 window, type:
cd /opt/customer/data
cp /usr/fox/wp/data/fv_blink.dat
Editing fv_blink.dat
fv_blink.dat is illustrated below. 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.
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).
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
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
28

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

The location of environment files is controlled by the WP’s 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 dif-
fer 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
customization 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 but-
ton commands that are no longer needed.
3. Create a new environment (.env) file to call 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.
NOTE
The .acl file does not exist by default.
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
section is a sample upgrade procedure.
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.)
30
$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.
Since this is a standard FoxView script, you can 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
Purpose of each line:

dmcmd script
Identifies this file as a script file.
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 command 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 pulldown definition
file. In this case, the contents of the file pulldown 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 10 labels, with up to 6 characters in each label.

Sample Menu Definition File (file.mnu)

The first line of the menu definition file must contain the words “pulldown 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
FoxView commands, displays, directories, or other pull-down menu files.
Here is the menu definition file, file.mnu.
pulldown foxview menu
“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
“Select Point” “select_pt on”
“Update Lights” “annun 0 0 0" -p 100
“Process Summary Reporter” “/usr/fox/sys/Proc_Summary” -p 100
“&1 MRU” “MRU1”
Example: Upgrading Display Manager Environment Files to FoxView

The following procedure illustrates moving a Display Manager environment file to FoxView.
Here is the Display Manager file (/usr/fox/sys/My_Env).
dmcmd nologscr
dmcmd passwd
dmcmd chng_env
dmcmd button 0 Sys /usr/fox/sys
dmcmd button 1 Alarm “dmcmd rcntalms”
dmcmd button 2 Help /usr/Help
dmcmd button 3 keep
dmcmd button 4 Disp /usr/menus
dmcmd button 5 Disp_1 /usr/menus/d1
dmcmd button 6 Disp_2 /usr/menus/d2
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) exten-
sion:
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 label “keep” with
no button definition following) is not supported.
32
♦ Standard menu definition files (*.mnu) have been supplied for the File and
Help pull-down menus. You can 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 following entries can be moved or deleted, as indicated:
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 pass-
word 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 Ini-

tial.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.
To have a “thumbnail” image of the Overview display appear on the display bar,
convert the display to a bitmap (Overview.i) using the FDF to BMP selection in
FoxDraw's File, Convert feature. (To run the fdf_i conversion utility from a com-
mand line, refer to Appendix A “Converting Display Manager Files to FoxView
Format from a Command Window”.)
The display Overview should have been moved to the /opt directory. FoxView can
find the display if this button is configured as /usr/menus/Overview, but it finds it
faster if the button is configured as /opt/menus/Overview.
6. 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 runtime:
♦ Right-click on the button.
A pop-up menu opens.
When you save the configuration, be sure to save to the /opt/customer/env directory, not to
/opt/fox/env (the default).
Protecting Display Bar Menu Picks, System and Process

Buttons, and Select/Assign
The pop-up menu items can be protected with the following WP globals:
Global Variable Protects
DBM_PROT All items in the pop-up menu
DBA_PROT Assign/Clear
DBS_PROT Save/Save As
DBSN_PROT New
DBL_PROT Load
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.
34
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 a 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 environments,
and want to assign a protection value of 10 for this function. Add the following 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 environment
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

These variables protect System and Process buttons:
SYS_PROT System button
PRC_PROT Process button
Follow the procedure for protecting the Display Bar pop-up menu.

Select and Assign Mode

This variable protects the Select and Assign mode for configuring trends in FoxView:
SAA_PROT Select and Assign
Disabling this feature prevents objects from being selected with a right mouse button selec-
tion.
Follow the procedure for protecting the Display Bar pop-up menu.
36
5. Moving FoxView Display Files
Between Windows NT and Solaris
This chapter describes how you move files between Windows NT and Solaris
workstations.
Moving Displays and Library Objects

There are three main steps in moving displays between platforms:
♦ Converting binary “.fdf” displays and library objects (.m1) to ASCII “.g” format
on the source workstation.
♦ Moving the “.g” files from the source to the destination workstation.
♦ Converting ASCII “.g” displays to binary “.fdf” files on the destination
workstation.
Converting Display and Library Objects

You can convert display and library objects.
Changing Foxboro Display File Format

If the FoxView software running on the source and destination workstations do not have the
same revision levels, the display file format must be changed.
NOTE
IMPORTANT: The format of the Foxboro Display File (.fdf) format has been
changed to enhance display call-up time with the 50 Series Version 6.0E release.
These changes are not incorporated into FoxView for the Windows NT plat-
form at Version 6.0. Before moving the files to a Windows NT system, convert
the display files back to the older file format.
If the Solaris displays have already been upgraded to the new file format, you
may find it more convenient to copy all displays and libraries to a temporary
directory, convert them back to the older Solaris Foxboro Display File format,
and then convert them to Windows NT format.
The display file format must be changed from the command line.
NOTE
This function cannot be performed through the conversion dialog box.
You must perform the following procedure from a VT100 window.
37
B0193WU – Rev A 5. Moving FoxView Display Files Between Windows NT and
To convert Foxboro display file format:

1. Type:
cd /opt/menus
This changes directory to the display file directory or display library directory.
The example command above assumes that the display files are in the /opt/menus
directory. Use the path to the appropriate display or library directory on your
system.
2. Type:
/usr/fox/wp/bin/tools/fdf_version -v 6 *
This changes the file formats to the older format.
Errors are written to a log file in the working directory. The log file’s name is
FDFxxxxxx.dat, where xxxxxx is a unique value each time the fdf_version utility is
run.
Converting Displays
To convert displays:
1. On the source workstation, access FoxDraw and choose File, Convert.
2. In the Select Conversion dialog box, select FDF to G.
Figure 5-1. Select Conversion Dialog Box (FDF to G Selected)
3. If desired, select the Recursively search directories check box and type a target
directory. By default, FoxDraw converts to the source directory.
4. Click the Next button.
38
5. Moving FoxView Display Files Between Windows NT and Solaris B0193WU – Rev A
5. At the Files to Convert dialog box, select the desired file(s) and then click the
Convert button.
Figure 5-2. Files to Convert Dialog Box
A pop-up dialog box indicates progress.

6. Click OK when the conversion is completed.
Figure 5-3. Progress Dialog Box
7. To verify the conversion, in the Files to Convert dialog box, at the List Files of
Type field, select All Files.
Converting Library Objects

To convert library objects:
If you have created any library objects, these must also be converted.
♦ In the Select Conversion dialog box, select M1 to G and follow the same proce-
dure as above.
Moving Displays and Library Objects 39

Converting Displays with Bitmaps

To convert displays with bitmaps:
1. Copy the bitmap files to /opt/customer/displib/Bitmaps.
2. To convert from Windows (.bmp) format to Solaris (.i) format, in a command
window enter the following:
/opt/windu/bin/convert -map /opt/fox/wp/FoxDraw/bitmap.bmp <file-
name>.bmp xwd:<filename>.i
where <filename> is the name of the bitmap to be converted.
NOTE
REMINDER: Solaris is case-sensitive. The .i filename must be in the same case as
the reference to the file in the .g display.
Moving .g Files
To move the .g files:
1. Copy the converted displays and library objects (the .g files only, not the .fdf or
.m1 files) to floppy, but do not copy them directly. “Tar” them into a single file
and copy the tar file to floppy. If you do not do this, the file names are forced to
DOS 8.3 format. Refer to “Known Issue #1” below.
2. Use the “tar extract” command to extract the displays and library objects into the
/opt directory on the target system. Library objects must go into /opt/cus-
tomer/displib/Symbols.
Converting ASCII Files to FoxView Format

To convert the files to FoxView (.fdf) format:
1. To convert the displays, in FoxDraw, select File, Convert, G to FDF.
2. To convert the library objects, select the G to M1 conversion.
Moving Environment Files

To move the environment files:
1. Copy any customized environments from the Windows NT workstation. Use
“tar”, not “copy” to avoid 8.3 filename problems.
2. Since Windows NT and Solaris environment files may be slightly different, merge
the edits instead of replacing files.
3. Place the files in the /opt/fox/env directory.
Known Issues in Moving Files Between Platforms

1. Solaris allows mounting a DOS (Windows NT) floppy disk through the /pcfs file
system. This allows files to be copied to and from diskette on both platforms.
40
5. Moving FoxView Display Files Between Windows NT and Solaris B0193WU – Rev A
However, Windows NT allows “long” filenames which are not supported by

Solaris. Solaris forces all filenames to their DOS 8.3 equivalents.
If filenames safely fit the 8.3 naming convention, they can be transferred to dis-
kette with “copy” (Windows NT) or “cp” (Solaris). If they do not fit the 8.3 con-
vention, they must be tarred into another file and the resulting tar file copied onto
diskette. It is also possible to tar directly to floppy – the “tar” utility is shipped on
both Windows NT and Solaris platforms and the format is compatible.
2. Filenames in Windows NT are not case sensitive. That means that Windows NT
regards the filenames “TOWER1.fdf”, “Tower1.fdf”, and “tower1.fdf” as all refer-
ring to the same file. On the other hand, Solaris filenames are case-sensitive.
Solaris regards the above names as referring to three different files. Be sure that the
names of your displays, library objects, and overlays account for this difference.
For instance, if you have a display which invokes an overlay named “Tower1.fdf”,
the overlay could have the name “TOWER1.fdf” on the Windows NT worksta-
tion and the overlay would be displayed correctly. However, on the Solaris work-
station, the overlay would not be found and would not display.
3. Although font mapping between platforms is relatively good, displays created on
one platform and moved to the other have detectable differences in font size and
location. In addition, since fonts are not infinitely scalable, relative size and posi-
tion vary depending on the size of the FoxView/FoxDraw window. It is recom-
mended that you create displays at the size that they will be most frequently
viewed.
If font size and position are extremely important, it may be advisable to use
Hershey fonts. Hershey fonts are created from line segments which can be posi-
tioned and scaled to the nearest pixel. They can also be rotated to arbitrary angles.
4. If you rotated or scaled a display object in FoxDraw and did not specify a reference
point, an invalid reference point is added, making the object appear in the wrong
location after it is moved from Solaris to Windows NT. If the object also has a
move horizontal or move vertical dynamic update, the reference point for the
move will be incorrect. To fix this problem, select the object in FoxDraw and spec-
ify a reference point at the center.
Known Issues in Moving Files Between Platforms 41

42
6. Engineering Utilities
This chapter describes the available engineering utilities which are run from a
VT100 window.
Obtaining Information About Windows and Moving

Windows (show_win)
You can obtain information about windows with the show_win command. Using this com-
mand without any arguments displays the state of various windows, open or iconified, that are
active for a workstation.
Examples
To bring the specified window to the front of the stack of open windows:
♦ Type:
/usr/fox/wp/bin/tools/show_win <window title>
To bring the window V2WP51:ADM001 to the front of the stack:
♦ Type:
show_win V2WP51:ADM001
You can configure annunciator keys to execute show_win. Refer to Process Alarm Configura-
tion for details.
Adjusting Touchscreens (ts_util)

Use the touchscreen utility (ts_util) to program the touchscreen controllers of adjacent CRTs
to run at different frequencies can help to avoid interference.
Eliminating Touchscreen Interference

Touchscreens located close to other touchscreens can interfere with each other, particularly
when they are tilted towards each other. This interference can cause the cursor to jitter, or
make the touchscreen extremely sensitive. For example, the cursor might move without user
contact to the touchscreen glass.
Interference usually occurs between CRTs that are located side-by-side or above-and-below
each other. Diagonally adjacent CRTs do not experience interference.
To program touchscreen controller frequency:
1. Open a local VT100 window on the screen corresponding to the touchscreen con-
troller that is to be programmed.
2. Type:
43
B0193WU – Rev A 6. Engineering Utilities
ts_util -f <number>
where <number> is 0 or 1. The following diagram shows how to program mul-
tiple CRTs that are both horizontally and vertically adjacent.
ts_util -f 0 ts_util -f 1 ts_util -f 0
ts_util -f 1 ts_util -f 0 ts_util -f 1
3. Exit the VT100 window.

Perform this procedure at any time, because the system does not need to be rebooted. The fre-
quency setting is stored in non-volatile memory.
Adjusting Touchscreen Sensitivity

You can adjust the touchscreen’s sensitivity level by using ts_util. This utility allows touch-
screen usage while wearing gloves. Although it does not work with all gloves, it works with
most latex, rubber, thin cotton, and some leather gloves.
To adjust sensitivity:
1. Open a local VT100 window on the screen corresponding to the touchscreen con-
troller that is to be programmed.
2. Type:
ts_util -s <number>
where <number> is 0, 1, 2, or 3. Use the default level (0) for normal usage.
Each subsequent level increases the sensitivity, and 3 is the most sensitive level.
3. Exit the VT100 window.
NOTE
Use the lowest level that provides satisfactory results. Setting the sensitivity to
the highest level may cause inaccuracies when used with a non-gloved hand that
touches the screen lightly. The touch location can also be effected by the posi-
tion of the palm of the hand at the highest level.
Perform this procedure at any time, because the system does not need to be rebooted. The fre-
quency setting is stored in non-volatile memory.
Copying and Converting Display Files Between

50 Series workstations (getremfiles)
Use the 50 Series file propagation utility (getremfiles) to copy all types of files from APs or
50 Series workstations to other APs or 50 Series workstations anywhere in the network. You
can use getremfiles to convert display files only to the appropriate format.
44
6. Engineering Utilities B0193WU – Rev A
getremfiles allows you to copy multiple files to multiple destinations. You can optionally con-
vert display files to WP30 or 50 Series format before propagating the display files. getremfiles
cannot convert display libraries.
You can invoke getremfiles to operate in one of two modes:
♦ Interactive mode – you specify command options in response to prompts.
♦ Automatic mode – the program reads the options from an ASCII data file.
Command Syntax
This is the command syntax for getremfiles:
getremfiles [-c filename]
where:
-c Reads commands from the specified ASCII command
list file instead of prompting.
filename Is the name of the command file.
If you do not enter the -c option, getremfiles prompts for the necessary information and
builds an ASCII command file of your responses. It then passes this command file to a shell
script that does the actual file propagation, which may involve remounting file systems and
calling a conversion program.
You can edit the ASCII command file with a text editor such as vi to make subsequent runs.
getremfiles allows you to specify:
♦ The command file’s name for saving your responses to the prompts.
♦ The earliest creation/modification date for files to be propagated.
♦ The destination path for files.
♦ Automatic conversion and repacking of display files in 50 Series or WP30 format.
♦ Source and destination WP(s), AW(s), and AP(s) by letterbug.
♦ Source files and directories to be propagated. The standard UNIX wildcard char-
acters (* and ?) are not supported. If directories are specified, all files and
subdirectories within the specified directory are propagated and possibly
converted.
♦ Viewing of the command file.
♦ Execution of the command file.
If you specify display file conversion, the located packed display files are converted and copied
to all destination letterbugs. You are not allowed to convert some files to 50 Series format and
others to WP30 format.
If any file conversion is specified, each file, display, or otherwise, is copied from the source let-
terbug to the /usr/temp directory on the local workstation disk. Files are identified, converted
(if necessary), and copied to the destination letterbug(s), one file at a time. The temporary
copy is then deleted from /usr/tmp directory.
Copying and Converting Display Files Between 50 Series workstations (getremfiles) 45

NOTE
Do not use getremfiles to copy files to the /usr/tmp directory. For temporary
storage, copy the files to another temporary directory.
If no file conversion is specified, each file is copied from the source “letterbug” directly to the
destination letterbug(s).
If you do not specify a file name for saving the dialog to a command file, a temporary com-
mand file is created to hold your responses. After the file propagation shell script completes,
this file is deleted. Otherwise, this file is available for use by typing:
getremfiles -c command_file
WP20/WP30 display files that are converted to 50 Series format are configured for 31 sta-
tions in their network address table.
50 Series display files that are converted to WP30 format retain their original number of sta-
tions, except where the file is configured for 31 stations. Since the WP30 format can handle
up to 30 stations only, any 50 Series display file with 31 stations is automatically reconfigured
for 30 stations and a warning message is printed.
NOTE
To convert 50 Series display files to WP20 files, you must use the convdisp2_20
utility program, because WP20 display files have a maximum network address
table size of 12, as compared to 30 on the WP30. You cannot use getremfiles to
set the network address table size of display files for use on the WP20.
Example
This example shows how to convert WP20/WP30 display files to 50 Series display files via
getremfiles prompts.
Each prompt is listed as a separate step; repeat prompts for the same series of entries are not
listed to save space. The example uses bold typeface to indicate user entry and un-bold type-
face to indicate system response.
Start the conversion from the command tool window on a 50 Series workstation, by typing:
getremfiles
--- File Propagation Utility Version 1.1 ---
Enter name of command file name to save

your responses in or <CR> to skip this option
/usr/tmp/log_fl.out
Enter earliest creation/modification date of files to be copied.

Default is 01/01/70.
Enter date (mm/dd/yy) (<CR> only for default):
05/20/94
46
Enter destination path if different than source path.

Default path is the same as the source path.
(<CR> only for default):
<CR>
Do you want display files to be converted and re-packed

automatically. Default is YES. (Y/N):
y
Do you want display files to be converted and re-packed

in the WP50 Series format or the WP30 Series format?
Default is WP50 Series. (WP50/WP30):
WP30
Enter Destination Letterbug. One entry per line

Press <CR> only to end:
WP5001
WP5002
<CR>
Enter Source Letterbug. One entry per line

WP5101
Specify Source File(s). One entry per line

Press <CR> only to end):
/usr/menus/d1/file1
/usr/menus/d2
/usr/fox/sys/Change_Env
<CR>

WP5102
<CR>
Specify Source File(s). One entry per line

Press <CR> only to end):
/usr/fox/wp/data/init.user
/usr/fox/customer/hi/dmcfg
<CR>

<CR>
Copying and Converting Display Files Between 50 Series workstations (getremfiles) 47

View command list? default is YES (Y/N):

y
#File Transfer Commands Version2

#Created Fri May 20 12:54:38 1994
log_path=/usr/tmp/log_fl.out
cdate=05/20/94
dest_path=
convert_disps=YES
format=WP30
destination=
WP5001
WP5002
source=
WP5101
/usr/menus/d1/file1
/usr/menus/d2
/usr/sys/fox/Change_Env
WP5102
/usr/fox/wp/data/init.user
/usr/fox/customer/hi/dmcfg
Proceed with copy? (Y/N):

y
copying...
using convert2_20
>From WP5101:
To WP5001: /usr/menus/d1/file1
To WP5002: /usr/menus/d2/file1
CONVERTING and PACKING DISPLAY FILES:

Convert Flags:
CONVERTED : /usr/tmp/display1
PACKED : /usr/tmp/display1
To WP5001: /usr/menus/d2/display1
48
CONVERTING and PACKING DISPLAY FILES:

Convert Flags:
CONVERTED : /usr/tmp/display2
PACKED : /usr/tmp/display2
To WP5001: /usr/fox/sys/Change_Env/Proc_Eng_Env
To WP5002: /usr/fox/sys/Change_Env/Proc_Eng_Env
To WP5001: /usr/fox/sys/Change_Env/Proc_Op_Env
To WP5002: /usr/fox/sys/Change_Env/Proc_Op_Env
>From WP5102:
No newer file(s): /usr/fox/wp/data/init.user

To WP5001: /usr/fox/customer/hi/dmcfg
To WP5002: /usr/fox/customer/hi/dmcfg
... done copying.
Editing Display Manager Environments (dmsepass)

Use the 50 Series set environment utility (dmsepass) to edit Display Manager environment
script file passwords and descriptions. dmsepass is located in the directory
/usr/fox/wp/bin/tools on the 50 Series stations.
Command Syntax
The command line syntax for dmsepass passwd_id is:
dmsepass passwd_id [-p password] [-d description] [-f filename]
where:
passwd_id The environment to be affected by password.
password The password. (No password removes the password.)
description An optional identifier description.
filename An optional password configuration filename.
Example
This example shows how to edit the password of the Initial Environment to be “jackson” and
changes the description.
♦ From a VT100 mode on the 50 Series station, type:
dmsepass Init_Env -p jackson -d “New password for Init_Env”
Editing Display Manager Environments (dmsepass) 49

The password and description for the Initial Environment is saved in the file:
/usr/fox/wp/data/dmpasswd_cfg
This is an ASCII file that contains the encrypted password and a description for each environ-
ment. A backup file, passwd_cfg.bak, which is also created, contains the contents of
passwd_cfg previous to the most recent change.
To remove this environment from the password file:
♦ Type
dmsepass Init_Env
The Init_Env now has no password.
Do not use the -f option.
NOTE
Passwords are not limited to use in an environment script file. Any Display
Manager script may include passwords.
Updating Display Files (cvupdate_wp50)

Use the 50 Series cvupdate_wp50 utility to update 50 Series display files with conventions
from the convention file and repack the display file. cvupdate_wp50 generates a log of update
actions. Conventions are stored in the binary file /usr/fox/wp/data/conventions.
Command Syntax
The command line syntax for cvupdate_wp50 is:
cvupdate_wp50 [-a -c] convention_filename display_filename...
where:
c Sends the update action log to the file /usr/tmp/cvupdate.out
instead of displaying it on the screen.
a Appends the update action log to the file
/usr/tmp/cvupdate.out instead of displaying it on the screen.
convention_filename Is the name of the display convention file.
display_filename Is a list of display files to be updated.
Updating Display Builder Graphics History Offsets

(hist_offset)
Use the 50 Series hist_offset utility to update the recent history offsets for any historical or
recent history trends in 50 Series packed display files on the workstation disk. This program
prints the name of each file processed, along with any applicable error messages.
50
To speed Display Manager call-up of trend displays, update trend display files with the
hist_offset program after:
♦ Reconfiguring a 50 Series Historian
♦ Converting an AP20 Historian database to 50 Series format
♦ Converting an AP20 trend display to 50 Series format
hist_offset accesses Historians on remote 50 Series APs. You need only run hist_offset just
once per display file.
Remote APs hosting referenced Historians must be running when hist_offset is run. If the
specified Historian for a given point in a display file is not found (for example, because the AP
is not running, or the requested point is not there), the offset for the point is set to -1, and a
warning message is printed at the terminal.
The 50 Series Display Manager detects when a configured trend point in a display file has the
incorrect offset into the Historian database. When this occurs, the Display Manager acquires
the correct offset and makes a second request for the data so that the proper historical infor-
mation can be displayed. This slows down the display call-up.
The Display Manager does not write the correct offset into the display file, so it makes this
second request each time the display is called up, until you correct the offset in the file. You
can correct the display using either hist_offset or the on-line trend configurator to make a
permanent change.
Because the Display Manager does not write the recent history offset into the display file, you
can use generic historian trend connections (that is, trends with dollar substitution
connections).
Command Syntax
The command syntax for hist_offset is:
hist_offset filename...
where:
filename Is a list of display files, directories, or both to be corrected. If you specify
a directory, the program recursively traverses that directory to process all
packed display files in the directory and its subdirectories.
Examples
The following command updates the recent history offsets in a WP50 packed display file
called file1:
hist_offset file1
The following command updates the recent history offsets in WP50 packed display files in
directory dir1 and its subdirectories.
hist_offset dir1
If hist_offset finds any files in the directory that are not packed display files or that do not
have trends in them, it displays an error message and continues on to the next file until all files
in the directory have been processed.
Updating Display Builder Graphics History Offsets (hist_offset) 51

52
Appendix A. Converting Display
Manager Files to FoxView Format
from a Command Window
This appendix shows you how to convert Display Manager files from a command
window.
Copying Display Manager Displays

Copy all displays to be converted to a new location on the disk. FoxView displays should be
located in a parallel directory, that is, they should be copied from /usr to /opt.
For example, to copy all displays from /usr/displays to /opt/displays
♦ At a VT100 window type:
cd /opt
cp -r /usr/displays
This copies all the files and subdirectories in /usr/displays to /opt/displays. Repeat this proce-
dure for all subdirectories containing display files.
Converting the Displays

To convert the displays:
♦ At a command window, type:
/usr/fox/wp/bin/tools/pdf_fdf [arguments] <files>
where [arguments] are:
Argument Meaning
-r Recursive conversion (include subdirectories in the conversion).
-f Converts faceplates.
[files] are: the name(s) of the displays to be converted. Wildcards (that is, the
asterisk character, *) are allowed.
The conversion utility produces the following files:
File Description
.fdf All converted displays have the .fdf extension.
.pdf All Display Manager displays are renamed with the .pdf extension.
.dat Two log files (a conversion report log and a conversion error log).
Files that could not be converted are reported in the error log.
53
B0193WU – Rev A Appendix A. Converting Display Manager Files to FoxView
NOTE
1. Files that are not 50 Series Display Manager display files are not affected by
the conversion utility.
2. 20 Series Display Manager display files are not converted to FoxView format.
You must first convert them to 50 Series files as a separate step.
Examples
♦ To convert the display /opt/displays/overview
Type:
/usr/fox/wp/bin/tools/pdf_fdf /opt/displays/overview
♦ To convert all the displays in the directory /opt/displays
Type:
/usr/fox/wp/bin/tools/pdf_fdf /opt/displays/*
♦ To convert all the displays in the directory /opt/displays and in all its
subdirectories
Type:
/usr/fox/wp/bin/tools/pdf_fdf -r /opt/displays/*
Using a text editor, check the log files for any errors during the conversion process.
Upgrading Displays for the 6.0 Release

You must upgrade displays and library objects (including faceplates) that have been created on
all previous FoxView releases for use on Release 6.0.
To upgrade the display and library objects:
At a command window, type:
/usr/fox/wp/bin/tools/fdf_version [arguments] <files>
where arguments are:
Argument Description
-r Recursive conversion. The conversion includes the files in
the subdirectories.
-v The final version level of the files. Files should be upgraded
to Version 7. The previous version level is 6. The default is 7.
-h Displays help messages.
<files> refers to the name(s) of the displays to be converted. Wildcards ( * ) are

permitted.
The utility produces the following files:
Extension Description
.fdf Upgraded display files
54
Appendix A. Converting Display Manager Files to FoxView Format from a Command Window B0193WU – Rev A
Extension Description
.m1 Upgraded library object files.
.dat Log file.
NOTE
Files that are already at the specified version and files that are not FoxView dis-
play files are left untouched.
♦ To upgrade all the displays in the /opt/menus directory

Type:
/opt/fox/wp/bin/tools/fdf_version -r /opt/menus/*
♦ To change these same displays back to display version 6
Type:
/opt/fox/wp/bin/tools/fdf_version -r -v 6 /opt/menus/*
♦ To upgrade all the library objects
Type:
cd /opt/customer/displib
/opt/fox/wp/bin/tools/fdf_version -r *
Converting Customized Markers

Skip this section if you have not customized the standard I/A Series (usr or usr1) markers.
50 Series markers are not supported by FoxView. Converted standard markers have been
included in this release. However, if you customized 50 Series markers, you must convert
them to FoxView library objects.
I/A Series markers (.bdf format files) are located in /usr/fox/wp/fonts.
To convert customized markers:
♦ From a VT100 window, type:
cd /usr/fox/wp/fonts
/usr/fox/wp/bin/tools/bdf_m1 -f <markerfile.bdf>
where <markerfile.bdf> is either usr_mkr.bdf or usr1_mkr.bdf.
The converted files are placed in /opt/customer/displib/Markers.
Creating Bitmap Display Bar Files

The following example procedure shows how to create a display bar bitmap file of the
/opt/custom/Initial_Disp file.
To create a display bar bitmap file:
♦ From a VT100 window, type:
Converting Customized Markers 55

B0193WU – Rev A Appendix A. Converting Display Manager Files to FoxView
cd /opt/custom
/usr/fox/wp/bin/tools/fdf_i -f Initial_Disp
The file “Initial_Disp.i” is created, which can be displayed on a Display Bar.
56
Index
.bmp
converting to .i format 40
.g Files
moving between Windows NT and Solaris 40
/opt Directory 20
/usr Directory 20
50 Series Format to WP20/WP30 Format

converting display files 15
A
ASCII Files
moving to FoxView format 40
B
bdf_m1 Utility 55
Bit Acronym Replacement 18
Bitmap Display Bar Files
creating 55
Bitmaps
converting display with bitmaps 40
Blinking colors
configuring 27
Button
Process 35
System 35
C
Color Palette
converting 10, 24
colordef.dat File 25
Colors
blinking 27
convdisp2_20 3
convdisp2_20 Utility 15
convdisp2_50 3
convdisp2_50 Utility 4
Conversions
57
B0193WU – Rev A Index
required from Display Manager to FoxView 19

convfonts 3
convlib2_50 3
convlib2_50 Utility 6
Custom Markers
converting 23
Customized Markers
converting 55
cvtenv 3
cvtenv Utility 11
cvtfonts Utility 8
cvtmarkers 3
cvtmarkers Utility 8
cvtpal 3
cvtpal Utility 11
cvupdate Utility 50
D
Directories
/opt and /usr 20
Display
converting 38
converting Display Manager displays from a command window 53
Display Bar
configuring 34
Display Conventions
updating 50
Display Files
converting 37
Display Manager
converting files 19
copying displays 53
upgrading environment files 32
upgrading o FoxView 19
Display Names
rules 19
Displays
converting 21
upgrading for Release 6.0 54
dmsepass Utility 49
E
Environment File
conversion 11
Environment Files 40
58
Index B0193WU – Rev A
customizing 29
upgrading 32
Environment Passwords
setting 49
F
fdf_i Utility 55
fdf_version Utility 54
File
colordef.dat 25
extensions 20
file.mnu 32
fv_blink.dat 27
Inital.mbr 31
Initial.env 30
menu bar 31
File Propagation 44
file.mnu File 32
Files
.bmp 40
creating display bar bitmaps 55
user edits to standard file 21
font_expand Utility 8
font_shrink Utility 8
Fonts
converting to other sizes 8
FoxDraw
file extensions 20
FoxView
file extensions 20
upgrading from Display Manager 19
fv_blink.dat File 27
G
getremfiles Utility 44
Globals
protecting 35
H
hist_offset Utility 50
Historian
updating offsets 50
59
I
Initial.env File 30
Initial.mbr FIle 31
K
Known Issues
moving files between platforms 41
L
Library Objects
converting 38
M
Markers
converting 23, 55
converting to other sizes 8
Menu Bar File 31
Menu Definition File 32
Mode
Select and Assign 36
moving from Windows NT to Solaris 40
P
Palette
converting 24
Passwords
environment 49
pdf_fdf Utility 53
Platforms
known issues when moving files 41
Problems
moving files between platforms 41
Process Button 35
S
Select and Assign Mode 36
show_win Utility 43
Software
upgrading from Display Manager to FoxView 19
Standard Files
user edits to 21
System Button 35
60
Index B0193WU – Rev A
T
Touchscreen
adjusting sensitivity 44
eliminating interference 43
ts_util Utility 43
U
Utilities
engineering 43
Utility
bdf_m1 55
convdisp2_20 15
convdisp2_50 4
convlib2_50 6
cvtenv 11
cvtfonts 8
cvtmarkers 8
cvtpal 11
cvupdate 50
dmsepass 49
fdf_i 55
fdf_version 54
font_expand 8
font_shrink 8
getremfiles 44
hist_offset 50
pdf_fdf 53
show_win 43
ts_util 43
W
Window Information 43
WP20/30 Format to 50 Series Format
converting environment files 11
converting fonts 8
converting markers 8
WP20/30 to 50 Series Format
converting color palettes 10
WP20/WP30 Format to 50 Series Format
converting display files 3, 5
61
The Foxboro Company

33 Commercial Street
Foxboro, Massachusetts 02035-2099
United States of America
http://www.foxboro.com
Inside U.S. 1-508-543-8750 or 1-888-FOXBORO (1-888-369-2676)
Outside U.S. - Contact your local Foxboro Representative.
Printed in U.S.A. 1198

An Invensys company

B0193wu A

Încărcat de

Informații document

Titlu original

Drepturi de autor

Formate disponibile

Partajați acest document

Partajați sau inserați document

Opțiuni de partajare

Vi se pare util acest document?

Este necorespunzător acest conținut?

Drepturi de autor:

Formate disponibile

B0193wu A

Încărcat de

Drepturi de autor:

Formate disponibile

® B0193WU

Copyright 1998 by The Foxboro Company

1. Overview of Utilities ................................................................................................... 1

2. Converting WP20/WP30 Files to 50 Series Format .................................................... 3

3. Converting 50 Series Files to WP20/WP30 Format .................................................. 15

Converting 50 Series Libraries, Fonts, Markers, Color Palettes, and Environments to

4. Converting from Display Manager to FoxView ......................................................... 19

5. Moving FoxView Display Files Between Windows NT and Solaris ........................... 37

6. Engineering Utilities ................................................................................................. 43

Adjusting Touchscreens (ts_util) ....................................................................................... 43

Appendix A. Converting Display Manager Files to FoxView Format

This document uses the following terms.

Conversion and Migration of User Interface

Converting WP20/WP30 Format Display Files to

Converting WP20/WP30 Format Libraries to 50 Series

Converting WP20/WP30 Format Libraries to 50 Series Format 5

Converting WP20/WP30 Format Libraries to 50 Series Format 7

Converting WP20/30 Format Fonts and Markers to

Converting Fonts and Markers to Other Sizes

Font to single width, double height:

Font to double width, double height:

Do you want to continue the conversion now (y/n)?

Converting WP20/30 Format Fonts and Markers to 50 Series Format 9

Converting WP20/WP30 Color Palette Files to

rmount <source_AP> /rem/<source_AP>

Converting Environment Files

Converting Environment Files 11

For example, conversion of the Init_Env produces the following file:

dmcmd button 1 Alarm “” dmcmd rcntalms “”

dmcmd button 9 Select “” dmcmd stddisp “”

Converting Environment Files 13

Converting 50 Series Display Files to WP20/WP30

Converting 50 Series Display Files to WP20/WP30 Format 17

Bit Acronym Replacement

Converting 50 Series Libraries, Fonts, Markers, Color

What Needs to be Converted from Display Manager to

Converting and Modifying Display Manager Files

FoxView/FoxDraw File Extensions

The /opt and /usr Directories

User Edits to Standard Files

1. To convert Display Manager displays automatically in FoxDraw, choose Convert

2. In the Select Display Conversion dialog box, select PDF to FDF.

Converting and Modifying Display Manager Files 21

(logERR_conversion.dat) viewable in vi (Solaris) or Notepad (Windows NT). The

Figure 4-3. Files to Convert Dialog Box

Converting Custom Markers

Converting and Modifying Display Manager Files 23

Figure 4-4. Select Display Conversion Dialog Box (BDF to M1 Selected)

By default, converted markers are written to /opt/customer/displib/Markers. You

Converting a Customized Color Palette

Color Index Red Green Blue

To copy the file:

Converting and Modifying Display Manager Files 25

sys_pal.wp50 Index colordef.dat Index X11 Color Name

sys_pal.wp50 Index colordef.dat Index X11 Color Name

Configuring Blinking Colors

To copy the file:

File Line colordef.dat Base Color X11 fv_blink.dat Blink-to Color

Converting and Modifying Display Manager Files 27

File Line colordef.dat Base Color X11 fv_blink.dat Blink-to Color

File Line colordef.dat Base Color X11 fv_blink.dat Blink-to Color

Upgrading Customized Environment Files - Overview

Converting and Modifying Display Manager Files 29