B0700RJ

(1)

REV D

I/A Series

®

System

FoxView™ and FoxDraw™ Software

V10.2.1 Release Notes

(2)

Invensys plc, its subsidiaries, and affiliates.

SOFTWARE LICENSE AND COPYRIGHT INFORMATION

Before using the Invensys Systems, Inc. supplied software supported by this documentation, you should read and understand the following information concerning copyrighted software.

1. The license provisions in the software license for your system govern your obligations and usage rights to the software described in this documentation. If any portion of those license provisions is violated, Invensys Systems, Inc. will no longer provide you with support services and assumes no further responsibilities for your system or its operation.

2. All software issued by Invensys Systems, Inc. and copies of the software that you are specifically permitted to make, are protected in accordance with Federal copyright laws. It is illegal to make copies of any software media provided to you by

Invensys Systems, Inc. for any purpose other than those purposes mentioned in the software license.

(3)

Preface

Software Version

FoxView™ software (“FoxView”) and FoxDraw™ software (“FoxDraw”) can be installed on I/A Series® systems running Version 8.x software. This document refers to the latest version of the software as FoxView/FoxDraw V10.2.1

Purpose

This document is designed to assist users in the installation of FoxView/FoxDraw software.

Audience

Current users of FoxView and FoxDraw should review Chapter 3 “New Features”. All users should carefully review Chapter 5 “User Notes” and Chapter 4 “Known Problems”.

Revision Information

For FoxView/FoxDraw software Version 10.2.1, the following changes have been made to this document:

Chapter 2 “Installation Notes”

♦ Added a note regarding the documents that come along with the installation of the Windows version of the software and the path to access these documents, in section “Windows XP and Windows Server 2003 Platforms with I/A Series Software” on page 8.

♦ Added a step, about running a script to install user documents and Release Notes, in the procedure to install Solaris version of the software in “Solaris Platforms” on page 9.

♦ Added a note regarding the documents that come along with the installation of the Solaris version of the software and the path to access these documents, in section “Solaris Platforms” on page 9

Appendix B “Problems Resolved in V10.2.1”

♦ Added New Sections

References

Refer to the following documents for more information about FoxView and FoxDraw:

♦ FoxView™Software (B0700BD)

♦ FoxDraw™ Software (B0700BE)

(8)

♦ FoxRemote™ and TCP/IP Network Integration, Installation, and Configuration Guide

(B0193VR).

♦ The MESH Control Network System Planning and Sizing (B0700AX)

♦ I/A Series® SystemV8.3 Software for the Solaris Operating System Release Notes and

Installation Procedures (B0700RR)

(9)

1. Introduction to

FoxView/FoxDraw Software

This chapter discusses characteristics of this release and the supported platforms.

1.1 About This Release

This release of FoxView™ software is available for use on the Solaris platform and FoxView™

/FoxDraw™ software for the Windows XP® platform and the Windows® Server 2003 platform is

labeled V10.2.1.

FoxView™ /FoxDraw™ V10.2.1 for the Windows XP® platform and the Windows Server 2003 platform supports I/A Series V8.x. FoxView V10.2.1 for the Solaris platform supports I/A Series V8.3 and above.

NOTE

There is no V10.2.1 FoxDraw available for Solaris.

1.2 Supported Platforms

FoxView and FoxDraw software are supplied for:

♦ _{I/A Series Workstations running the Windows XP operating system}

♦ _{I/A Series Workstation Server running the Windows Server 2003 operating system.}

FoxView software is supplied for:

♦ _{I/A Series Workstations running the Solaris10 operating system}

FoxDraw V 10.2.1 is available as a separate installation for workstations with non I/A Series sys-tems running on Windows XP operating system, and Windows Server 2003 operating system.

1.3 New Features

No new features have been added for FoxView/FoxDraw V10.2.1 release. Listed below are some of the features provided with the FoxView/FoxDraw V10.2 release. Refer to Chapter 3 “New Fea-tures” for more details of the new features in this release.

♦ _{Solaris10 operating system support: FoxView runs on Solaris10 on I/A Series}

V8.3 and above releases.

♦ Solaris: DEdit, DConvert tools are accessible from the Config -> Display_Tools

pull-down menu options of FoxView. Previously these tools are accessible from Solaris FoxDraw.

♦ FoxView: FoxView V10.2 is compatible with IACC V2.3/2.3.1. It is possible to

(10)

incorporated in this release of FoxView.Please refer to APPENDIX A for detail list of CARs.

♦ Trend Features: When trend is paused, the Scooter line appears in the graph area of

trend at the point where mouse button is released. The purpose of this is to print out various process values at different instants of time.

(11)

2. Installation Notes

This chapter provides information for system requirements, file backup, and FoxView/FoxDraw installation.

2.1 Display File Compatibility

Displays and library objects built with the latest version of FoxDraw software are generally not backward compatible with older versions of FoxView software and FoxDraw software. When upgrading from a previous version of FoxView software and/or FoxDraw software, all worksta-tions should be upgraded. If it becomes necessary to move displays or library objects to older workstations, the files must be converted to .g (ASCII) format on the new workstation and then converted to binary format on the older workstation. However, due to changes in display file con-figuration information, newer displays and library objects may not work correctly on older ver-sions of FoxView software and FoxDraw software.

2.1.1 Display Conversions

The following table explains the possible conversions from display manager displays to FoxView displays and display conversions between different versions of FoxView.

NOTE

(12)

FoxView Version on Source box 10.1/10.2 /10.2.1

Win

10.2 / 10.2.1

SOL10 9.0.3 Win 9.0.3 SOL2/8 DispMgr Conversion Steps required to use display on Destination box - 10.1/10.2/10.2.1 Win

Display can be directly opened on destination box On the source box, do an fdf_g on the display Display can be directly opened on destination box On the source box, do an fdf_g on the display Copy the DM display (.pdf ) to destination box Copy the .g file

to destination box.

Copy the .g file to destination box. On destination box, run pdf_fdf utility on the display On destination box, do g_fdf utility on .g file On destination box, do g_fdf utility on .g file

Conversion Steps required to use display on Destination box - 10.2 / 10.2.1 SOL10

On the source box, do an fdf_g on the display Display can be directly opened on destination box On the source box, do an fdf_g on the display Display can be directly opened on destination box Copy the DM display (.pdf ) to destination box Copy the .g file to

destination box.

Copy the .g file to destination box. On destination box, run pdf_fdf utility on the display On destination box, do g_fdf util-ity on .g file On destination box, do g_fdf utility on .g file

Conversion Steps required to use display on Destination box - 9.0.3 Win

Run 10x to 9x in DConvert to con-vert the existing 10x display to

9x fdf

Run 10x to 9x in DConvert to convert the exist-ing 10x display to 9x fdf Display can be directly opened on destination box On the source box, do an fdf_g on the display Copy the DM display (.pdf ) to destination box

Copy the .fdf file to destination box

On the source box, convert the 9x .fdf to .g file using fdf_g

Copy the .g file to destination box.

On destination box, run pdf_fdf utility on the dis-play

Copy the .g file to destination box.

On destination box, do g_fdf utility on .g file

(13)

10.1/10.2 /10.2.1

Win

10.2 /10.2.1

SOL10 9.0.3 Win 9.0.3 SOL2/8 DispMgr

On destination box, do g_fdf utility on .g file

Conversion Steps required to use display on Destination box - 9.0.3 SOL2/8

Run 10x to 9x in DConvert to con-vert the existing 10x display to

9x fdf

Run 10x to 9x in DConvert to convert the exist-ing 10x display to 9x fdf On the source box, do an fdf_g on the display Display can be directly opened on destination box Copy the DM display (.pdf ) to destination box

On the source box, convert the 9x .fdf

to .g file using fdf_g

On the source box, convert the 9x .fdf to .g file using fdf_g

Copy the .g file to destination box. On destination box, run pdf_fdf utility on the display Copy the .g file to

destination box.

Copy the .g file to destination box. On destination box, do g_fdf utility on .g file On destination box, do g_fdf util-ity on .g file On destination box, do g_fdf utility on .g file

(14)

2.1.2 Moving Displays to V9.x Versions of FoxView/FoxDraw

Software

Displays and library objects built with the latest version of FoxDraw software are backward com-patible with V9.x versions of FoxView software and FoxDraw software.

NOTE

The V9.x displays generated by the conversion utilities does not contain the follow-ing new features that are available only with FoxDraw V10.x:

1. Historical Data in X/Y Plots: Only FoxDraw V10.x provides the ability to

hhconfigure historical data in X/Y plots.

2. Additional X/Y Plot Color Configuration Option: With FoxDraw V10.x only, X/Y

plots allows the value of another variable to drive the color of the most recent point.

3. X/Y Plot Zone Line Configuration: With FoxDraw V10.x only, X/Y plots supports the configuration of zone lines for each pen in a plot.

4. Trend Features: With FoxDraw V10.x only, up to four static reference lines can be configured per trend. In addition, the text formatting of the trend data value field can be configured on a per-trend basis.

2.1.2.1 Conversion Using DConvert Utility

The DConvert utility has been updated to include the 10x to 9x conversion option. The pur-pose of this option is to convert a FoxView/FoxDraw V10.x display file (.fdf ) or library object (.m1) to a FoxView/FoxDraw V9.x display file or library object.

This conversion saves the converted file in the 9x folder by default. However, you can provide a different destination path. The filename can begin with any character except a hyphen or space, and can be followed by any characters except spaces.

The display file conversion from V10x to V9x, requires an additional step while moving displays from Solaris 10 stations to Solaris 8 or Solaris 2.5.1 Workstations. Once the 9x fdfs are created, using the conversion utility on Solaris 10, run fdf_g on these files. Transfer the .g files to the Solaris 8 or Solaris 2.5.1 Workstations, and run g_fdf to get compatible fdf files for Solaris 8 or Solaris 2.5.1.

2.1.2.2 Conversion Using FoxDraw Software

To convert displays from FoxDraw software:

1. Click Save As 9.x from the File menu.

2. Select the path in which to save the converted file, and then click Save.

2.1.2.3 Conversion Using the Command Line

To convert displays from the command line:

1. Type:

/usr/fox/wp/bin/tools/fdf_version -b *.fdf

This converts all the displays in the current directory and saves the converted files in the 9x folder.

(15)

2. Type:

/usr/fox/wpb/bin/tools/fdf_version -b *.m1

This converts all the library objects in the current directory and saves the converted library objects in 9x folder.

Errors and removed objects or keywords 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.

2.2 Files to Back Up Before Installation

V10.2.1 of FoxView and FoxDraw can only be installed on I/A Series V8.x Windows systems and I/A Series V8.3 and above for Solaris 10 system. This version cannot be installed on an I/A Series Workstation whose version is prior to V8.0. The following information is provided as back-ground information only, as this software cannot be installed as an upgrade on I/A Series V6.x/V7.x workstations.

Display files (.fdf ) are not over-written during installation of FoxView/FoxDraw software. Dis-play location is a user-definable function, and is specific to each system.

FoxView/FoxDraw library objects are loaded in the /opt/fox/displib directory and its subdirecto-ries during the installation. If any changes have been made in the /opt/fox/displib directory and its subdirectories, these files need to be backed up. However, files in these subdirectories are often modified as part of the FoxView/FoxDraw release. If these subdirectories are restored with files from a previous release, the modifications included with this new release are lost. In general, it is unwise to make modifications to files in the /opt/fox/displib subdirectories. All modified files should be saved in the /opt/customer/displib subdirectories.

Library objects that are located in the /opt/customer/displib directory and its subdirectories are not over-written during an installation.

FoxView environment files located in /opt/fox/env are upgraded during the software installation. If changes have been made to the default set of environment files located in the /opt/fox/env directory, they need to be backed up. After installation, it is recommended that the changes made to the standard environment files be incorporated into the customized versions. These customized files should be saved to /opt/customer/env.

Note that FoxView software automatically loads environment files from the /opt/customer/env directory instead of the /opt/fox/env directory. However, the dialog box that allows environment selection only displays the names of files in the /opt/fox/env directory. In order to have an envi-ronment presented in the dialog box list, the envienvi-ronment’s .env file must be found in the /opt/fox/env directory.

2.3 System Requirements for Solaris Platforms

Running FoxView on an I/A Series V8.3 and above Solaris workstation requires the following hardware. FoxView does not impose any additional memory requirements that are already speci-fied by the I/A Series V8.x Solaris workstation.

(16)

2.3.1 Required Disk Space

This table shows the disk space required for each partition.

NOTE

For hardware and software requirements, refer Chapter 4 “Hardware

Require-ments” in “I/A Series® SystemV8.3 Software for the Solaris Operating System Release

Notes and Installation Procedures (B0700RR)”.

2.4 Installing the Software

The FoxView/FoxDraw V10.2.1 CD-ROM contains the installations for the Windows XP and Windows Server 2003 versions of FoxView and FoxDraw software. It also includes FoxView V10.2.1 for Solaris 10. The software is compatible with I/A Series system releases V8.x and higher for Windows systems and I/A Series system releases V8.3 and higher.

NOTE

Contact IPS Global Client Support Center at 508-549-2424 (worldwide) or 1-866-746-6477 (US, Canada toll-free) or visit the Global CSC website at http://sup-port.ips.invensys.com for the recommended Quick Fixes to install for this software release.

2.4.1 Windows XP and Windows Server 2003 Platforms with

I/A Series Software

To install the Windows XP/Server 2003 version of the software from the CD-ROM, use the fol-lowing procedures.

1. If a previous version of FoxView/FoxDraw software is installed, uninstall it using the

procedures on page 12. Model Type System Type Model P79 AW51M0 Model P80 AW51M2 Model P81 AW51M1 Model P82 AW51M2

Table 2-1. Required Disk Space

Partition

Space Required

/opt 75MB

(17)

2. The FoxView/FoxDraw software installation process requires that I/A Series software

be turned off. From the Control Panel, select the Foxboro I/A icon. When the Star-tup Options for Reboot dialog box appears, check either Autologon or Manual Logon

in the “I/A Series Off ” group.

3. Reboot the workstation.

4. Insert the FoxView/FoxDraw V10.2.1 CD-ROM into the CD-ROM drive. 5. The Installation program should start automatically. If it does not, from Windows

Explorer double-click on \Win\setup.exe.

6. When presented with the FoxView/FoxDraw 10.2.1 Setup Dialog, select the check

box beside the component, FoxView/FoxDraw 10.2.1 and click Next to continue installation.

NOTE

When installing FoxView on I/A Series process operator or process engineering sys-tems configured for more than three instances of FoxView, the number of Object Manager OS parameters may need to be increased. Refer to Chapter 5 “User Notes” for more information.

7. After installation is completed, turn on I/A Series software and reboot the workstation

using the Shutdown/Reboot pick from the FoxView SftMnt menu pick.

NOTE

FoxView/FoxDraw 10.2.1 Installation installs the FoxView User Guide, FoxDraw User Guide, and FoxView/FoxDraw 10.2.1 Release Notes.

These documents can be accessed through Start > Program > Menu Option.

2.4.2 Solaris Platforms

Perform the installation from a command window or a command tool window.

CAUTION !

Do not install the software while in single user mode, as the /opt partition is not mounted.

To install the Solaris version of the software from the CD-ROM, use the following procedures.

1. Exit any open FoxSelect application.

2. Insert the FoxView/FoxDraw V10.2.1 CD-ROM into the CD-ROM drive. 3. From a command window or CmdTool, mount the CD-ROM drive by typing:

mount -o ro -F hsfs /dev/sr0 /cdrom

4. Change directory by typing:

cd /cdrom/UNIX

5. Type:

inst_sw.sh

(18)

inst_sw.sh

6. To install FoxView/FoxDraw User Guide and Release Notes, please run

InstallDoc-Menu.sh script. Type:

InstallDocMenu.sh

NOTE

FoxView/FoxDraw 10.2.1 Installation installs the FoxView User Guide, FoxDraw User Guide and FoxView/FoxDraw 10.2.1 Release Notes. These docu-ments can be accessed through Launch > Applications > Menu Option.

7. Change directory back to / (root) with:

cd /

8. Unmount the CD-ROM drive by entering:

umount /cdrom

NOTE

If you operate your I/A Series system on Daylight Saving or Summer Time, go to the section “Daylight Saving Time - Solaris” on page 10 and continue with step 8.

9. After installation is completed, reboot the station using the Shutdown/Reboot pick from the FoxView SftMnt menu pick

or

Reboot the Solaris workstation from the command window Type:

reboot

2.4.2.1 Daylight Saving Time - Solaris

FoxView10.2.1 includes the functionality to handle the setting back of time correctly for Solaris systems, and resolves operational problems related to system time changes. Systems running on the Windows® based platforms does not experience this issue.

FoxView needs a process named “dst” to be running when the clock is being set back. FoxView 10.2.1 installation automatically loads this file in /opt/fox/wp/FoxView directory

After completing FoxView installation, it is recommended that the “dst” process is started using the following procedures.

NOTE

Running “dst” process does not set the clock back, it only prevents FoxView lockup.

♦ Method A. needs a FoxView re-start or

♦ Method B. does not need a FoxView re-start. However, this needs to be performed every time the workstation is rebooted.

(19)

NOTE

It is recommended to use Method A.

Method A.

1. Add the line “dmcmd dst start” command in FoxView start-up environment file. Example: /opt/fox/env/Initial.env file

---dmcmd nolog_script dmcmd passwd dmcmd chng_env dmcmd dst start $ENV_DIR/Initial.acl $ENV_DIR/Initial.dbr $ENV_DIR/Initial.mbr $ENV_DIR/Initial.dms shortcut_menu_style configurable

shortcut_menu -type object -file $ENV_DIR/obj.mnu shortcut_menu -type display -file $ENV_DIR/disp.mnu

---2. Restart the FoxView after editing.

3. Repeat steps 1 and 2 for each workstation.

Method B.

1. Open a Terminal window

2. Run the command: pref -<DMNAME> dmcmd “dst start” 3. Repeat Step 2 for each active FoxView on the workstation 4. Repeat Steps 1 to 3 for each workstation.

How to stop the “dst” process:

When the clock is not being set back, the “dst” process for FoxView can be stopped. 1. Open a Terminal window

2. Run the command: pref -<DMNAME> dmcmd “dst stop”. This affects all active FoxViews on the workstation.

(20)

2.4.3 Non I/A Series Windows Platforms

FoxDraw V10.2.1 can be installed on a non I/A Series station with Windows NT, Windows XP, or Windows Server 2003. To install the Windows version of FoxDraw from the CD-ROM, use the following procedures.

1. If a previous version of FoxDraw software has been installed, use the Add or Remove

Programs icon in the Control Panel to uninstall FoxDraw software.

2. Insert the FoxDraw Version 10.2.1 CD-ROM into the CD-ROM drive. 3. From Explorer double-click on \setup.exe.

4. After the installation is completed, reboot the station.

2.4.4 Uninstalling on Windows XP and Windows Server 2003

Platforms

FoxView/FoxDraw 10.2.1 software can be uninstalled through the Control Panel. The uninstall process requires that I/A Series software be turned off. Uninstall the software as follows:

1. If you are running I/A Series software, disable it. Select the Foxboro I/A icon from the Control Panel. When the Startup Options for Reboot dialog box appears, check either Autologon or Manual Logon in the “I/A Series Off ” group.

2. Reboot the workstation.

3. From the Control Panel, select the Add or Remove Programs icon.

4. Select FoxView/FoxDraw, click Change/Remove, then click Yes to remove the applica-tion and all of its components.

2.4.5 De-Optimizing Displays Configured to Display Data from

50 or More Control Stations

Any FoxDraw displays that have been configured to display data from more than 50 control sta-tions must be de-optimized before they work correctly with FoxView 10.2.1. Perform the follow-ing steps for each display file (.fdf ):

1. Change directory to /usr/fox/wp/bin/tools:

D:\>cd /usr/fox/wp/bin/tools

2. Convert .fdf files to .g files by typing the following:

D:\usr\fox\wp\bin\tools>fdf_g<display file directory>\<filename>.fdf

Where <display file directory_{> is the directory in which the display file resides}

and <filename_{> is the name of the file configured to display data from more than 50}

control stations.

For example, type the following to convert the “mydisplay.fdf ” file in the D:\opt\menus\d1 directory from the .fdf to the .g format:

fdf_g D:\opt\menus\d1\mydisplay.fdf 3. Convert .g files to .fdf files by typing the following:

D:\usr\fox\wp\bin\tools> g_fdf <display file directory>\<filename>.g

Where <display file directory_{> is the directory in which the display file resides}

and <filename_{> is the name of the file configured to display data from more than 50}

(21)

For example, type the following to convert the “mydisplay.g” file in the D:\opt\menus\d1 directory from the .g to the .fdf format:

g_fdf D:\opt\menus\d1\mydisplay.g NOTE

It is mandatory to perform this step for display files that are configured to display data from 50 or more control stations. If the displays are from FoxView V10.1 and if de-optimization is already done, the above de-optimization for the displays is not required.

2.5 FoxDraw V10.2.1 Software and FoxAPI or

**AIM*API Software**

2.5.1 I/A Series Workstations

FoxDraw software uses FoxAPI (Foxboro Application Program Interface) and/or the AIM*API server interfaces to connect to the I/A Series system via TCP/IP client/server communication pro-tocol and access I/A Series data. Acting as a client, FoxDraw software retrieves Compound Sum-mary Access (CSA) data to support the Compound/Block browser, and parameter and range data from the Control Processor for faceplates, trend pens, marker locations, and attributes such as Fill Level. If you want to use these features of FoxDraw software, you must install FoxAPI software or AIM*API software on the workstation or server and edit the client initialization file, an_init.cfg. The API Server Connection utility, api_connect, is used to create and edit the an_init.cfg file. FoxDraw is able to browse the servers only after the an_init.cfg file has been created by the API Server Connection utility. Refer to one of the following subsections, depending on the API ver-sion that is installed on the I/A Series workstation.

After accessing the connection utility, edit the an_init.cfg file according to the instructions in the appropriate document: FoxAPI Installation Guide (B0193UC) or AIM*AT™ Installation Guide

(B0193YM).

2.5.1.1 FoxAPI V4.3.2

To set up the an_init.cfg file on a workstation running FoxAPI V4.3, invoke the api_connect utility by selecting the Options > Configure Servers menu item in FoxDraw.

**2.5.1.2 AIM*API V3.3**

The platform api_connect utility, included in the API Server Connection Utility kit, must be installed and run prior to using FoxDraw software. The API Server Connection Utility kit con-tains the following items:

♦ The API Server Connection diskette for Windows (K0173XL) contains the utility to be loaded on Windows NT and Windows XP I/A Series workstations.

♦ The API Server Connection Utility (B0400EE) document contains the installation and usage instructions for the utility.

(22)

It is recommended that you install the API Server Connection diskette prior to using FoxDraw. You are not able to access this utility by clicking the Configure Servers menu item.

NOTE

You are not able to access the connection utility by selecting the Options > Config-ure Servers menu item in FoxDraw.

NOTE

AIM*API users must use this new API Server Connection utility. Do not access the connection utility via the earlier API Admin > Edit Server Connection method. When AIM*AT software is installed, the an_init.cfg path changes in the registry according to the value set by AIM*AT installation. In this scenario, there are two an_init.cfg files: one in the location used earlier by FoxDraw and the other in AIM*AT installation directory. FoxAPI calls connect to the an_init.cfg file in the AIM*AT installation directory since the registry points to this path. You can either reconfigure the servers using the API Server Connection utility, or manually copy the server entries from the FoxDraw an_init.cfg file to the AIM*AT an_init.cfg file.

2.5.2 Off-Platform Workstations with Stand-alone FoxDraw

Software

The API Server Connection utility, api_connect, is used to create and edit the an_init.cfg file. The api_connect utility resides on the API Server Connection diskette for Windows (K0173XL), and this diskette is included with the API Server Connection Utility kit. You must install and run the api_connect utility prior to using FoxDraw software.

The installation and usage instructions for the utility are included in the API Server Connection

(23)

3. New Features

This chapter describes the new features since the last release of FoxDraw software, FoxView software and FoxSelect software.

NOTE

Refer Appendix B “Problems Resolved in V10.2.1” for a significant list of issues that have been resolved in the 10.2.1 release.

3.1 FoxView/FoxDraw Software

(24)

(25)

4. Known Problems

This chapter lists known problems that affect the V10.2.1 FoxView/FoxDraw software.

4.1 FoxView

1. If a trend graph’s first pen is configured as Boolean and its Y-axis scale is configured to be visible, the state names are displayed in the Y-axis scale area instead of the numeric scales. This situation can be avoided by configuring a numeric pen as the first pen for the trend graph, or by selecting any numeric pen as the pen whose scales are displayed within the graph.

2. The ov and ov_conn commands do not support the overlay positioning arguments

-rel_pick and -pick if the commands are executed from an overlay.

3. If you select a data entry field and then unselect it (by selecting another object) without entering any data, the field does not return to its original text contents until an update is received for the field.

4. (Solaris Only) Displays containing Profile Plots with bars should be configured for

Full Refresh in the Display Properties dialog box within FoxDraw. If not config-ured in this way, an update to the position of the bars may not completely erase the previous bars.

5. (Solaris Only) The Clear (CE) key on a modular keyboard does not work within the Online Trend Configurator.

To correct a typing error, cancel out of the Online Trend Configurator dialog box, and re-enter the data.

6. (Solaris Only) Selecting File > Print from the Help window causes Help to crash. 7. (Solaris Only) Selecting print screen from the display bar does not directly print the

page by configuring the Printer in FoxView. The user has to save the screen shot to a file. In the Save Screenshot dialog box, retain the other default settings and click on Save button. The next dialog window appears. Select File-> Print from the menu option to print the screen.

8. (Solaris Only) User can not undo Control_Cfg, Station_Cfg while using the “all” pick. If more than 226 stations (38x7) exist while using the “all” selection, the Sta-tionCfg pick disappears from the menu list. The CP list in StaSta-tionCfg can not be “undone” without this selection.

4.2 FoxDraw

1. User settings are not saved when you exit FoxDraw.

2. The Font Selection dialog box erroneously displays fonts that have not been installed. 3. Reopening the current display after making changes to the display does not cause

FoxDraw to actually get the original contents of the display file from the disk drive. Instead, FoxDraw uses the currently open display. This means that you cannot aban-don changes made to the current display by reopening the display. To do this, open

(26)

another display (or create a new display) first and respond No when asked whether you would like to save the changes to the current display.

4. When connecting to the FoxAPI servers on large systems, requesting compound data can cause the client side of FoxAPI software to crash, thereby causing FoxDraw to crash. To resolve this problem, make sure the latest version of FoxAPI server is installed on the workstation. This is currently FoxAPI version 4.2.5 or AIM* version 5.3. Contact our Global Customer Support Center or visit the web site for informa-tion on receiving the latest server software.

5. Occasionally, when running FoxDraw in an X-Window System™, the Configure Objects dialog box is drawn such that the buttons at the bottom of the dialog box are drawn off the screen. To work around this, try to move the window by grabbing any one of its borders and moving it up enough to make the buttons visible.

4.3 DEdit

1. (Solaris Only) When FoxDraw DEdit is first called up, the tabs for the second and third page of the tabbed dialog box may not be drawn correctly. They may appear as faint horizontal lines just above the position where the tabs should be. By selecting either of these faint lines, the tabs are redrawn correctly. Their appearances are appro-priate from then on.

(27)

5. User Notes

The User Notes provide operational guidelines, recommendations, cautions, workarounds, and/or notes relating to FoxView/FoxSelect/FoxDraw that you may find useful.

5.1 FoxView

1. Blinking colors are not supported in trends. This applies to displays that have been converted from Display Manager format to FoxView format.

2. Relative picks that are to be used for data entry or ramp operations must contain a range specification. These fields should be configured as:

= PICK1 C:B.P|R=low,high

where low is the low range, and high is the high range

-or-= PICK1 C:B.P|RIx = PICK1 C:B.P|ROx

where RIx is an input range (for example, RI1), and ROx is an output range (for example, RO1).

You may use either the R = low,high format or the Rxx format to specify the range. If a range is not specified for the relative pick, no range checking is performed when the relative pick is used in the data entry or ramp.

3. When configuring pickable areas within faceplates, the use of $ is allowed. However, for data entry and ramp fields, FoxView evaluates these connection names when the display containing the faceplate is called in, not when the pickable field is actually selected. This allows fields to contain references to WP variables that may change before the field is selected. However, there are occasions when the $ evaluation needs to be performed when the field is selected. The most common example of this is the use of relative picks and the $PICK1 variable. When referencing $PICK1 in data entry and ramp fields in a faceplate, the reference should be to $$PICK1 (note the double $). This has the effect of delaying the evaluation of the $ until the object is selected.

4. When converting a Display Manager display file using the pdf_fdf conversion utility, ensure that the display is converted on a workstation that has the same color palette that was used by the Display Manager. This is important when the display to be converted contains references to blinking colors. The utility must read the color palette definition file, /usr/fox/wp/data/sys_pal.wp50, to determine whether any of the colors referenced in the display file are blinking colors. Conversion of blinking colors requires that an additional dynamic configuration be added to each object that requires blinking.

5. FoxView provides block out-of-service (OOS) indication only for text update dynamics to strings of the background text type. In FoxDraw, select Background Text for all strings that have text update connections applied.

(28)

6. If a display has a group that contains no objects when the display is called into FoxView, the entire display flashes for up to three updates. To fix this problem, call the display into FoxDraw, make a change, and save the display.

NOTE

FoxDraw does not save the display unless a change is made.

7. When you move the mouse out of the FoxView window with a Select/Assign or display bar configuration pop-up menu displayed, the input focus may not follow the mouse. If this happens, keyboard input is not accepted in other windows. To fix the problem, return the mouse to the FoxView window and click in the window.

This problem occurs only if the mouse is moved out of the FoxView window directly onto another window that is stacked on top of FoxView.

8. Environment names must have fewer than 14 characters; otherwise, they are not pro-cessed.

9. FoxView must have a working initial display (/opt/custom/Initial_Disp.fdf ) and a working initial environment (/opt/fox/Initial.env, Initial.dbr, Initial.mbr) in order for FoxView to start.

10. (Windows Only) If you configure more than three instances of FoxView for a Windows workstation, the number of Object Manager OS parameters may need to be increased to support the additional instances of FoxView. To increase the parameter, edit the file \etc\fox\opsys_usr.cfg and change the line that specifies the number of OM objects from 450 to 1250:

OM_NUM_OBJECTS 1250

To make this configuration available to the workstation, run the verifier application, then reboot the station. Type:

\usr\local\verifier -V c

then reboot the workstation.

11. (Windows Only) Some of the resources within the Windows workstation are limited. Examples of these limited resources are menu entries, windows, and so forth. This means there is a maximum number of combined menu entries, windows, and so forth for the entire workstation. While this limit is large, it is possible to configure the workstation in such a way that this limit is reached. For example, if multiple FoxView instances are running on a single workstation and each FoxView is in an environment that contains a large number of menu entries, this limit can be reached. When the limit is reached one or more FoxView instances are missing some of the expected menu items. To avoid this problem, large environments should be broken up into smaller ones, and accessed as needed.

NOTE

This issue is not a resource leak. All resources associated with menu entries are released when the menu entry is deleted. This issue is strictly one of maximum resource limits.

(29)

12. When editing PLB, do not call the new ladder display into FoxView until the Control Configurator has completed the installation of the ladder.

13. The Advanced screen of the On-Line Trend Configurator takes a long time to close when one of the pens is connected to a parameter that does not exist.

14. It is not recommended that objects with thick edge widths be configured for visibility. FoxView may not completely erase the object when it transitions to invisible. Similarly, it is not recommended that objects with thick edge widths be configured for edge color or edge blink dynamics. To accomplish the same effect, use a combination of layered solid filled rectangles (with no edge or with standard edge width of 1.) 15. If a display has polygons with transparent fill, these objects are drawn as solid until the

display has been updated (redrawn) once. If there are no continuously updating fields on the display, add a continuously updating field to the display for the polygons to be drawn as transparent.

16. Display and library objects cannot have the same name. For instance, there is a standard library object named tank_on_legs shipped with FoxView/FoxDraw. It is not possible to create a display named tank_on_legs and successfully link the tank_on_legs library object into that display.

17. When configuring ranges in alias objects, “hard coded” ranges are not allowed. For example,

= PICK1 {CB}.OUT|DEFAULT

is not a hard-coded range, but

= PICK1 {CB}.OUT|RO1

is a hard-coded range. There is no way to specify a hard-coded RO1, RI1, and so forth in an aliased object. For example, if configuring a fill bar in an aliased object to {CB}.OUT, when configuring the range, there are three choices:

♦ static range, that is, |R=0,100

♦ runtime range, that is, |DEFAULT

♦ range alias, that is, |MYRANGE or |RO1.

Note that FoxDraw does not make any distinction between MYRANGE and RO1 in the range alias configuration. If the field is configured as |RO1, then the range alias must be resolved when configuring the object on the base display.

When configuring commands within aliased objects, the same rules apply. FoxView and FoxDraw do not support |RO1 in commands within aliased objects. Instead, the

|DEFAULT syntax should be used. (CAR 1004615).

18. The new parameters AMRTIN and NASTDB appear on several faceplate overlays for many blocks with alarming. If you make changes to an overlay containing these parameters, the overlay is not updated until it is refreshed.

19. The @ symbol is not resolved for subst command if it is passed as a character in dou-ble quotes. For all the rest of the dmcmd commands FoxView resolves @ character. 20. You may observe white patches on moveable overlays while opening or closing or

moving out screen area, other applications like the On-Line Trend Configurator (OLTC). This can be overcome by moving the mouse pointer over the affected over-lay region.

(30)

21. When displaying the default display trend overlays, the trend overlay may be closed if a previously opened overlay is closed. For example, if a PID default display is called in, selecting CONFIG and TREND overlays, and then closing the CONFIG overlay, causes the TREND overlay to also be closed.

22. When FoxView is running through Exceed™ on a Windows NT workstation, chang-ing an overlay from moveable to stationary causes the overlay position to change. This is the default behavior of overlays when FoxView is run through Exceed on

Windows NT. To change this default behavior, perform the following steps:

a. Open XConfig by selecting Start > Programs > Hummingbird Connectivity >

XConfig.

b. Enter the password and click OK to open Xconfig dialog. (By default, the password is foxboro.)

c. Double-click on Window Mode icon to open the Window Mode dialog box.

d. Uncheck the Cascade Windows setting.

e. Click OK to save the setting.

23. (Solaris Only) The Sun® Solaris X Server used by all versions of FoxView has a design defect that leads to all XResourceIDs being used up. This is similar to a memory leak, but does not result in memory, swap space, or CPU problems. Basically, once all XResourceIDs have been used, FoxView is unable to change environments. The work-around is to restart FoxView.

The primary consumer of XResourceIDs is changing environments. Each entry in the menu structure consumes one XResourceID. There are four million XResourceIDs, and thus, this condition can occur after several weeks of operation. If the workstation or FoxView is restarted, the condition clears. Many sites have never experienced this condition, because they often restart FoxView, reboot the workstation, do not change environments often, or have very small environments.

24. (Solaris Only) On the Solaris platform, fonts are scaled incrementally, not continuously. This means that for small changes in window size, the font used for the text objects within the window may not change. If the change in window size is not large enough to cause a change in the font size, text positioning relative to other objects within the window changes, possibly causing text objects to overlap other objects in the display. This text misalignment may also happen between the FoxView and FoxDraw windows. If the display was built in FoxDraw in a window of one size, and displayed in FoxView in a window of another size, text object alignment may not be identical between the two windows. To minimize text-sizing issues, leave enough room between the end of text objects and the start of other graphic objects to allow for incremental scaling.

25. (Solaris Only) If a directory contains a large number of menu items, FoxView may not be able to display all the menu items within the area available in the window. The preferred solution for this issue would be for a large directory to be broken up into multiple smaller directories. If this is not possible, FoxView provides a way to limit the number of menu entries displayed at once, while still allowing access to the entire list of files in the directory. To enable this feature, the following lines must be added to the file /usr/fox/wp/data/init.user:

(31)

MENUNEXT=More...

The MENUMAX flag indicates that all menus are displayed in a single column, with a More... button at the end of the menu column if needed. When the More... button is selected, the next column of menu items are displayed to the right of the previous col-umn. If the next column of menu entries is too close to the right hand edge of the window, the column is moved toward the left of the window. The MENUNEXT variable contains the text to be displayed on the menu button at the bottom of the menu list. 26. Colors of certain areas of the applications like FoxView or FoxDraw or FoxSelect can change as different programs are executed. The Motif color system, in combination with the Wind/U porting tool causes this.

NOTE

Users should close applications like AIM*, FoxDraw before opening FoxSelect or vice-versa.

27. Whenever time is set back using SMDH, displays containing trend / plot objects need to be re- called to reflect updates.

28. FoxView/FoxDraw/FoxSelect does not support changing time backwards by more than two (>2) years at a time using SMDH.

29. Divide the files into subdirectories, For Example if there are files Config_1 to Config_500 files in /usr/fox/config/Control_Cfg/CIO_STN_Cfg directory, create subdirectories like Config_1_100 and copy all the files from Config_1 to Config_100 into that directory. Follow the same method for all the remaining files, so that the user does not miss any menu items.

30. FoxView supports only 16 trends per display. If we configure more than 16 trends on a display, then up to 16 trends are displayed clearly but for the remaining trends, the trending area appears as blank.

31. When a Pen color is changed in OLTC, sometimes color of the data field does not change accordingly. When this happens, if the cursor is brought on to the data field and right clicked, then the color of the data field is updated to the same changed color in OLTC.

32. (Solaris 10 Operating System Only) FoxView detail display supports only 24 charac-ters in the description field. If we configure more than 18 characcharac-ters in the description field, then up to 18 characters are displayed clearly but for the remaining characters, the description is not shown properly.

5.2 FoxSelect

1. By default, FoxSelect does not Refresh any stations when it is first called in. You must perform a Refresh All, or refresh each station individually. If FoxSelect is started with the -REFRESH command line option, FoxSelect refreshes all previously connected stations when it starts up. To start FoxSelect with this option, edit the file

/usr/fox/wp/data/init.user and add the following line:

FS_OPT=-REFRESH

Note, there are no spaces in this line. After editing the init.user file, the workstation must be rebooted.

(32)

2. Before connecting to a station in FoxSelect, wait for the Integrated Control Configurator (ICC) to complete a Load ALL or checkpoint, and wait while bus switching is in progress.

3. Whenever a station is refreshed (Options > Refresh) or excluded from refresh (Options > Exclude from Refresh) from the station view, all the active reports clear all their contents. The user has to refresh the report again to list out the compounds or blocks.

4. For Solaris10, FoxSelect does not display last item of the CP list. The last item in the CP list is sometimes not visible. Therefore the user, needs to resize FoxSelect Window to see the entire CP list properly.

5. Solaris (ULTRA 25) AW or WP and Wind/U do not provide support to wheel mouse with any application. Hence, the Wheel mouse functionality on ULTRA 25 (Solaris AW or WP) differs from windows and should be avoided on SOTM.

6. To enable the SSPROMPT functionality, the FS_OPT option must be enabled with the following addition: -ACK. With FS_OPT= -ACK, the pop-up window confirms that you want to turn a compound ON/OFF. (CAR 1008692)

5.3 FoxDraw

1. FoxView reads the user-defined convention file only upon startup. If you add, change, or delete a convention in FoxDraw, the effect of that change does not take place until FoxView is restarted.

2. When a user-defined convention is added, changed, or deleted, remember to copy the updated convention file to all other workstations where displays using conventions are used. User conventions are stored in the following file:

3. The display area is logically a 75.0 (high) by 100.0 (wide) area that occupies the client area of FoxView and FoxDraw. The size of this area is fixed and cannot be changed in FoxView or FoxDraw. However, within FoxDraw, it is possible to drag objects out-side of this area, either partially or entirely. This can occur when using FoxDraw’s zoom out feature, which causes the FoxDraw screen to show an area considerably larger than the 75x100 display area.

A graphic that extends outside the display area causes the workstation to use considerably more memory when the display is called up in FoxView.

An off-screen graphic can be so far off screen that it is not visible in FoxDraw. The only visible indication that a display is defective is that it flashes (because it is being redrawn several times) when called up in FoxView. Also, a defective display eventually causes the workstation to fail.

To determine whether a display has this problem:

Solaris /opt/customer/data/usr_conventions.dat

(33)

Within FoxDraw, you can determine whether a display has this problem by choosing

Select All from the Edit menu and observing where the bounding selection rectangle is drawn.

a. Load the display.

b. Click the Zoom out button twice.

c. Choose Select All from the Edit menu.

♦ If an off-screen object exists, the bounding selection rectangle extends off screen.

♦ If all objects are within the visible display area, the entire bounding selection rectangle is visible.

To repair a display:

a. Rename the defective display with a name that indicates that it is defective

(for example, rename FIC1001.fdf as FIC1001_bad.fdf ).

b. Call up the defective display in FoxDraw.

c. Click the Zoom out button twice. The area around the display appears.

d. Lasso the 75x100 display area. This selects everything on the visible display. NOTE

Do not use Select All, which selects everything.

e. Choose Edit/Invert selection.

f. Choose Edit/Delete to delete the items outside the normal drawing area.

g. Save the display as usual. Examples of defective displays:

One defective display had two lines that extended from -32768 to 32768. Another sample had an entire intact display section copied to a location at 16000. When the off-screen graphics were removed, both displays behaved normally.

FoxDraw can automatically detect and move objects that appear to have invalid coordinates. However, occasionally, valid objects are mis-identified as invalid. The default behavior of FoxDraw is to ignore invalid objects. If you believe that you have a display that might have invalid objects and you would like FoxDraw to check for them, perform the following steps:

a. Using any text editor, create a file called “check_points” in the FoxDraw home

directory (/opt/fox/wp/FoxDraw).

b. Open the display in FoxDraw.

If any potentially invalid objects are detected, FoxDraw displays a message box informing you of this. You have the option of ignoring the objects and leaving the dis-play as it is or allowing FoxDraw to move the objects into the valid range. Be sure to save the display if you have FoxDraw move any objects.

4. The ramp operation can only be specified by percentage. You cannot configure a RAMP button to increment by an absolute value. For example, use 50 to ramp a value by 5000 when its range is 10000 to 0.

(34)

5. The fdf_to_g and g_to_fdf conversion utilities cannot convert displays containing groups if any group name contains a hyphen ( - ) character or slash ( / ) character. 6. There are a number of reserved words that cannot be used for any of the following:

display file names (including base displays, library objects, and so forth), object names, group names and bitmap names. See the next table for a partial list of reserved words.

7. FoxView and FoxDraw do not support file or directory names containing spaces. 8. The overlapping portion of transparent and opaque objects may be drawn

inconsis-tently depending on the orientation and positioning of the objects. Shifting the objects can cause the overlapping portion of the objects to be drawn correctly. The inconsistent rendering of the overlapping portions of the objects has to do with the interference patterns of the fill colors of non-solid objects.

Partial Reserved Word List

Act Align Bitmap Cd Canter Chdir Circle Clear Color Cons Current Delay Dump Face Filled Font Free Get Grid Line Nil Offset Pan Path Pause Pie Points Port Preview Quit Radius Rampvalue Redraw Save Scale Sector Segments Set Size Spline Status Stress Text Time Update View Zoom Zoomin Zoomout

(35)

9. Copying an object configured with a fill level dynamic and then changing the object orientation by rotating it causes problems in FoxView with the redrawing of the fill level. To work around this, rotate the object before applying the fill dynamic or deselect the OptimizedUpdate checkbox in the Continuous dynamic configuration dialog box.

10. When converting displays and library objects from .g (ASCII) format to .m1 or .fdf format, make sure to convert the .g file back to its original file type. For example, .g files that were created as displays need to be converted to .fdf format and .g files that were created as library objects need to be converted to .m1 format. Displays and library objects each contain different configuration information, which is generated only when the file is created in FoxDraw.

11. Transparent rectangles configured with a fill level dynamic are not transparent for the non-filled area of the object. If this behavior is not acceptable, use polygons instead of rectangles.

12. If the connection to the FoxAPI or AIM*Server is broken when FoxDraw is running, calling up the browser dialog causes FoxDraw to hang-up until the connection is re-established. The same behavior is seen if the CSA server becomes unavailable.

13. When configuring custom menu entries in FoxDraw, quotes are supported within the command if the quote character (“) is preceded by a backslash (\).

14. Displays and library objects built with the latest version of FoxDraw are generally not backward compatible with previous versions of FoxView and FoxDraw. New features found in the latest FoxDraw is not supported in previous versions of FoxView and FoxDraw. However, if it becomes necessary to move files from FoxDraw V9.0.1 to a previous version of FoxView and FoxDraw, the following steps should be taken:

a. Convert the files to .g (ASCII) format on the latest platform. Use the Display

Converter tool in FoxDraw, or use the utility fdf_g for display files and the m1g utility for library objects.

b. If using Windows FoxDraw 9.0.1 or later, the .g file must be converted to be

compatible with older versions of FoxView and FoxDraw using the g_back_g util-ity.

\usr\fox\wp\bin\tools\g_back_g <.g files to convert>

c. Bring the .g files to the older workstation, and convert back to their original type

using either the Display Converter tool in FoxDraw, or the g_fdf and gm1 utili-ties from a command tool.

15. FoxDraw software must be restarted to affect the mode for case-sensitive tag names. Stand-alone FoxDraw software restarts automatically. When FoxDraw is restarted, the FoxView button in FoxDraw software is disabled.

16. While configuring a faceplate in FoxDraw software, the compound and block names are not reflected when the faceplate is drawn in FoxDraw software. However, these names are reflected if you save and reopen the display, or select the Configure Object menu for the faceplate.

17. Sometimes, while spacing objects evenly (Layout > Space Evenly) by lassoing objects, it would appear as though FoxDraw software is sorting the objects. In such a scenario, undo the Space Evenly operation. Instead of lassoing and selecting the

(36)

objects, shift mouse-click the objects on the screen in the order, and then select

Lay-out > Space Evenly to space the objects evenly.

18. When a Display Manager configured display is converted to a FoxView graphic, the “-c” option does not use the control ranges that were configured in the Display Configurator.

19. When reinstalling stand-alone FoxDraw software on a different drive, set the system variables FOXDRIVE and FOXROOT to the new installation drive. For example, if FoxDraw was installed on the D: drive and then reinstalled on the “C:” drive, the installation procedure does not set the FOXDRIVE and FOXROOT to “C:”. Set these system variables manually using the System applet in the Control Panel. 20. Only msglin command can be configured for close script for base displays.

21. While configuring a faceplate in FoxDraw software, the compound and block names are not reflected when the faceplate is drawn in FoxDraw software. However, these names are reflected if you save and reopen the display, or select the Configure Object menu for the faceplate.

22. Comment objects can not be created with multi-create option.

5.4 DEdit

1. If you have the “Validate Points in Reports” option enabled for a large display with many unavailable or non-existent tag names, it might take several minutes for DEdit to complete checking all of them for the Connection, Complexity, or Exception reports. If you do not need tag names validated for your reports, make sure this option is disabled.

2. DEdit cannot be used to modify linked library objects in displays. This is because the linked library object is a separate file. To modify library objects to be linked into displays, edit those library objects directly with DEdit.

3. When DEdit modifies displays, a number of command tools windows are displayed. These windows can be ignored.

5.5 DConvert

1. The display file conversion from V10x to V9x, needs an additional step while moving displays between Solaris 10 stations to Solaris 8 or Solaris 2.5.1 stations. FV10.2 uses SL-GMS 6.1 and FV9.0.2 uses SL-GMS 6.0, which makes a direct conversion incom-patible. Once the 9x fdfs are created using the conversion utility on Solaris 10, run fdf_g on these files. Transfer the .g files to the Solaris 8 or Solaris 2.5.1 boxes, and run g_fdf to get compatible fdf files for Solaris 8 or Solaris 2.5.1.

2. To perform conversions through gnome-terminal, we must be a super user. To switch to super user mode, use su - root command, so that user profiles and environment variables are loaded.

3. (Solaris) Displays built on windows workstations and converted for use on Solaris workstations may contain partition references such as “C:” or “D:” in path designa-tions. Picks made within the Solaris display that contain the invalid partition refer-ence result in overlays not coming up, scripts or executables not executing, etc.

(37)

To avoid this issue, the user must remove partition references such as “D:” or “C:” from the .g file prior to executing the conversion from g to fdf format. To edit the “.g” file use any of the editors such as vi, textedit, gedit, etc.

(38)

(39)

6. FoxView Capabilities

6.1 Display Manager to FoxView Migration Strategy

Conversion tools are provided to allow you to convert displays from original Display Manager format to FoxView format. Converted displays may be edited with FoxDraw. Conversion is one-way, from old format to new format. No tools are available for converting FoxView displays into Display Manager displays.

All display engineering applicable to original Display Manager displays is usable with FoxView displays. This includes Display Manager command scripts and internal display manager functions such as “pre-pick” and the various display manager variables (for example, $P1).

NOTE

The Display Manager and FoxDraw are not available on Solaris10 Platform.

Given the same display content, FoxView displays require approximately the same amount of disk space as Display Manager displays. However, it is also very easy to make very large (and proportionally slower) FoxDraw displays. Both WP and AW stations should, at a minimum, have 1.05 GB disk drives. 2.1 GB drives are preferred.

6.1.1 DM Font Conversion

Previously, when DM displays were converted to FoxView displays using conversion tools, the text in displays was sometimes of incorrect size and misaligned. FoxView 10.2.1 includes the functionality to handle DM font conversion correctly for Solaris, Windows platforms.

To convert DM Displays using FVFD 10.2.1 display conversion utilities:

1. Identify the fontdef.dat being used on the workstation.

♦ The Invensys supplied default file is located in /usr/fox/wp/data.

♦ If there is a user customized file, it is located in /opt/customer/data. This file takes precedence over the Invensys-supplied file.

2. Take a backup of the file as fontdef.bak

3. Note the numerical value at the third string position in the last line. In the below example, the value is 91.

default raster 90 -b&h-lucidatypewriter-medium-r-normal-sans-0-0-0-0-m-0-iso8859-1 default raster 91 -b&h-lucidatypewriter-bold-r-normal-sans-0-0-0-0-m-0-iso8859-1

4. Add the following lines at the end of file:

default raster xx -foxboro-ia0swdh-bold-r-normal--0-0-75-75--0--default raster xx -foxboro-ia0dwsh-bold-r-normal--0-0-75-75--0--default raster xx -foxboro-ia0swsh-bold-r-normal--0-0-75-75--0--default raster xx -foxboro-ia2swsh-bold-r-normal--0-0-75-75--0--default raster xx -foxboro-ia2dwsh-bold-r-normal--0-0-75-75--0--default raster xx

(40)

-foxboro-ia2swdh-bold-r-normal--0-0-75-75--0-NOTE

The conversion depends on the existence of following font files in /usr/fox/wp/fonts directory. ia0swdh ia0swsh ia0dwsh ia2swdh ia2swsh ia2dwsh The above fonts correspond to the font choices provided by the Display Manager. 5.

a. Update the numerical value of third string “xx” for the newly added six lines. The

number should be incremented by one for each line. The entries should look like the example below: (For Solaris).

default raster 90 -b&h-lucidatypewriter-medium-r-normal-sans-0-0-0-0-m-0-iso8859-1 default raster 91 -b&h-lucidatypewriter-bold-r-normal-sans-0-0-0-0-m-0-iso8859-1 default raster 92

-foxboro-ia0swdh-bold-r-normal--0-0-75-75--0--default raster 93 -foxboro-ia0dwsh-bold-r-normal--0-0-75-75--0--default raster 94 -foxboro-ia0swsh-bold-r-normal--0-0-75-75--0--default raster 95 -foxboro-ia2swsh-bold-r-normal--0-0-75-75--0--default raster 96 -foxboro-ia2dwsh-bold-r-normal--0-0-75-75--0--default raster 97

-foxboro-ia2swdh-bold-r-normal--0-0-75-75--0--b. For better visibility on windows platforms these entries should be modified as

fol-lows in the fontdef.dat file:

default raster 90 -b&h-lucidatypewriter-medium-r-normal-sans-0-0-0-0-m-0-iso8859-1 default raster 91 -b&h-lucidatypewriter-bold-r-normal-sans-0-0-0-0-m-0-iso8859-1 default raster 92

-foxboro-ia0swdh-medium-r-normal--0-0-75-75--0--default raster 93 -foxboro-ia0dwsh-medium-r-normal--0-0-75-75--0--default raster 94 -foxboro-ia0swsh-medium-r-normal--0-0-75-75--0--default raster 95 -foxboro-ia2swsh-medium-r-normal--0-0-75-75--0--default raster 96 -foxboro-ia2dwsh-bold-r-normal--0-0-75-75--0--default raster 97

-foxboro-ia2swdh-medium-r-normal--0-0-75-75--0--6. Copy the modified fontdef.dat file to all the corresponding workstations, where the DM converted displays are likely to be viewed. (If the fontdef.dat file is modified as mentioned in step 5 (a) copy that fontdef.dat file to Solaris work station, or else if the fontdef.dat file is modified as mentioned in step 5 (b) copy the modified fontdef.dat file to windows workstation.)

7. Convert the displays using the Display Converter or pdf_fdf utility from command line.

8. Copy the FoxView displays to all the corresponding workstations. (If they are verted on solaris platform copy them on to the solaris platforms or else if they con-verted on windows platform copy them on to the windows platforms).

(41)

NOTE

The fonts in converted FoxView displays are designed to look like fonts in DM displays, only when FoxView window size is same as DM default window size. However, when FoxView window is resized, the fonts may appear as slightly wider or taller. This is due to the window aspect ratio (width x height) differences between the Display Manager and FoxView.

NOTE

To view DM displays on Windows workstations, the displays need to be converted on windows station using pdf_fdf utility.

NOTE

To view the displays on windows platforms which are converted using pdf_fdf util-ity on solaris platform they need to be converted to fdf_g on solaris platform and need to copy the resultant .g file to windows platform. After copying the .g file to windows platform need to convert the .g file to fdf file using g_fdf utility on win-dows platform. (Vice versa).

6.2 FoxView Performance

FoxView performance is measured in two ways:

♦ Display call-up times

♦ Display update times.

Running multiple FoxViews on a workstation where loading and display configuration are not well planned results in reduced performance by lengthening display call-up time and slowing display update rates.

Display performance is affected by a variety of factors, including:

♦ Display graphical complexity

♦ The number of updating objects on the display

♦ The frequency with which the data changes

♦ The dynamic update graphics type

♦ Workstation processing power.

Displays with many highly complex, shaded, or 3-D objects and embedded bitmaps often results in extremely large display files. These complex, highly detailed displays are actually quite easy to create in FoxDraw. These files, even if they do not have a large number of connections, can expe-rience lengthy call-up times.

The load on a workstation processor increases in relation to the number of display update points and the frequency with which the data changes. When comparing displays, a display where a majority of the data changes once per second places greater load on the workstation than a display where the data points change on an average of once every 5 seconds. The impact of displays with

B0700RJ

REV D

I/A Series

®

System

FoxView™ and FoxDraw™ Software

V10.2.1 Release Notes

Contents

Preface

Software Version

Purpose

Audience

Revision Information

References

1. Introduction to

FoxView/FoxDraw Software

1.1 About This Release

1.2 Supported Platforms

1.3 New Features

2. Installation Notes

2.1 Display File Compatibility

2.1.1 Display Conversions

2.1.2 Moving Displays to V9.x Versions of FoxView/FoxDraw

Software

2.1.2.1 Conversion Using DConvert Utility

2.1.2.2 Conversion Using FoxDraw Software

2.1.2.3 Conversion Using the Command Line

2.2 Files to Back Up Before Installation

2.3 System Requirements for Solaris Platforms

2.3.1 Required Disk Space

2.4 Installing the Software

2.4.1 Windows XP and Windows Server 2003 Platforms with

I/A Series Software

2.4.2 Solaris Platforms

2.4.2.1 Daylight Saving Time - Solaris

2.4.3 Non I/A Series Windows Platforms

2.4.4 Uninstalling on Windows XP and Windows Server 2003

Platforms

2.4.5 De-Optimizing Displays Configured to Display Data from

50 or More Control Stations

2.5 FoxDraw V10.2.1 Software and FoxAPI or

AIM*API Software

2.5.1 I/A Series Workstations

2.5.1.1 FoxAPI V4.3.2

2.5.1.2 AIM*API V3.3

2.5.2 Off-Platform Workstations with Stand-alone FoxDraw

Software

3. New Features

3.1 FoxView/FoxDraw Software

4. Known Problems

4.1 FoxView

4.2 FoxDraw

4.3 DEdit

5. User Notes

5.1 FoxView

5.2 FoxSelect

5.3 FoxDraw

5.4 DEdit

5.5 DConvert

6. FoxView Capabilities

6.1 Display Manager to FoxView Migration Strategy

6.1.1 DM Font Conversion

6.2 FoxView Performance

**AIM*API Software**

**2.5.1.2 AIM*API V3.3**