I/A Series® System

FoxView™ and FoxDraw™

Software V10.4.4 Release
Notes

*B0700SN* *G*

B0700SN

Rev G
March 31, 2016
Schneider Electric, Invensys, Foxboro, FoxAPI, FoxDraw, FoxRemote, FoxSelect, FoxView, and I/A Series are
trademarks of Schneider Electric SE, its subsidiaries, and affiliates.

All other brand names may be trademarks of their respective owners.

Copyright 2013-2016 Invensys Systems, Inc.

All rights reserved.

Invensys is now part of Schneider Electric.

SOFTWARE LICENSE AND COPYRIGHT INFORMATION

Before using the Invensys Systems, Inc. supplied software supported by this documentation, you
should read and understand the following information concerning copyrighted software.
1. The license provisions in the software license for your system govern your obligations
and usage rights to the software described in this documentation. If any portion of
those license provisions is violated, Invensys Systems, Inc. will no longer provide you
with support services and assumes no further responsibilities for your system or its
operation.
2. All software issued by Invensys Systems, Inc. and copies of the software that you are
specifically permitted to make, are protected in accordance with Federal copyright
laws. It is illegal to make copies of any software media provided to you by
Invensys Systems, Inc. for any purpose other than those purposes mentioned in the
software license.
Contents
Preface................................................................................................................................... vii

1. Introduction to FoxView/FoxDraw Software..................................................................... 1

1.1 About this Release ............................................................................................................... 1
1.1.1 I/A Series Symbols for Windows ................................................................................. 1
1.2 Supported Platforms ........................................................................................................... 1

2. Installation Notes .............................................................................................................. 3

2.1 Display File Compatibility .................................................................................................. 3
2.1.1 Display Conversions .................................................................................................... 3
2.1.2 Moving Displays to V9.x Versions of FoxView/FoxDraw Software ............................. 6
2.1.2.1 Conversion Using DConvert Utility .................................................................... 6
2.1.2.2 Conversion Using FoxDraw Software .................................................................. 6
2.1.2.3 Conversion Using the Command Line ................................................................ 6
2.2 Multiple Ramp Operations ................................................................................................. 7
2.3 Files to Back Up Before Installation .................................................................................... 7
2.4 Installing the Software ......................................................................................................... 8
2.4.1 Windows 7, Windows Server 2008 R2 Standard,
Windows XP and Windows Server 2003 Platforms with
I/A Series Software ............................................................................................................... 8
2.4.2 Non-I/A Series Windows Platforms ............................................................................. 9
2.4.3 Uninstalling on Windows 7, Windows Server 2008 R2
Standard, Windows XP and Windows Server 2003 Platforms ............................................ 10
2.4.4 De-Optimizing Displays Configured to Display Data from
50 or More Control Stations .............................................................................................. 10
2.5 FoxDraw Software and AIM*API Software ....................................................................... 11

3. New Features................................................................................................................... 13
3.1 New Features for FoxView/FoxDraw Software v10.4.4 ..................................................... 13
3.1.1 Thicker Overlay Borders ........................................................................................... 13
3.2 New Features for FoxView/FoxDraw Software v10.4.3 ..................................................... 13
3.2.1 Retaining Configured Engineering Units of the Display Manager Trends in FoxView
Software ............................................................................................................................. 13
3.3 New Features for FoxView/FoxDraw Software v10.4.2 ..................................................... 14
3.3.1 Text Rendering Compatible with 10.2.x Displays .................................................... 14
3.3.2 Maintaining Font Aspect Ratio on Window Resize ................................................... 14
3.4 New Features for FoxView/FoxDraw Software v10.4.1 ..................................................... 15
3.4.1 Defining a Cursor ..................................................................................................... 15
3.4.2 Scroll Region Fonts ................................................................................................... 15

iii
B0700SN – Rev G Contents

4. Known Problems............................................................................................................. 17
4.1 FoxView Software ............................................................................................................. 17
4.2 FoxDraw Software ............................................................................................................. 18

5. User Notes....................................................................................................................... 19
5.1 FoxView Software ............................................................................................................. 19
5.2 FoxDraw Software ............................................................................................................. 24
5.3 FoxSelect ........................................................................................................................... 30
5.4 DEdit ................................................................................................................................ 30
5.5 DConvert .......................................................................................................................... 31
5.6 Reserved Keywords (Not for Use in Foxboro Display Files) .............................................. 31
5.7 10x to 9x Conversion ........................................................................................................ 31

6. FoxView Capabilities ....................................................................................................... 33

6.1 Display Manager to FoxView Migration Strategy .............................................................. 33
6.1.1 DM Font Conversion ................................................................................................ 33
6.2 FoxView Performance ....................................................................................................... 36
6.3 Cross-Platform Capability ................................................................................................. 37
6.4 Remote Display Capability ................................................................................................ 37

Appendix A. Problems Resolved in v10.4.4 ......................................................................... 39

A.1 FoxView Software ............................................................................................................. 39
A.2 FoxDraw Software ............................................................................................................ 39

Appendix B. Problems Resolved in v10.4.3 ......................................................................... 41

B.1 FoxView Software ............................................................................................................. 41
B.2 FoxDraw Software ............................................................................................................ 41

Appendix C. Problems Resolved in v10.4.2 ......................................................................... 43

C.1 FoxView Software ............................................................................................................ 43
C.2 FoxDraw Software ............................................................................................................ 44

Appendix D. Problems Resolved in v10.4.1......................................................................... 45

D.1 FoxView Software ............................................................................................................ 45
D.2 FoxDraw Software ........................................................................................................... 46
D.3 FoxSelect Software ........................................................................................................... 46
D.4 Display files ..................................................................................................................... 46

Appendix E. Problems Resolved in v10.4 ............................................................................ 47

E.1 FoxView Software ............................................................................................................. 47

iv
Contents B0700SN – Rev G

E.2 FoxDraw Software ............................................................................................................ 47

E.3 FoxSelect Software ............................................................................................................ 48

Index .................................................................................................................................... 49

v
B0700SN – Rev G Contents

vi
Preface

Software Version
Unless otherwise indicated in this document, the referenced version of FoxView™ software
(FoxView) and FoxDraw™ software (FoxDraw) is 10.4.4. This release of FoxView/FoxDraw soft-
ware can only be installed on I/A Series®or Control Core Services systems running:
♦ I/A Series software v8.8 and later or Control Core Services v9.0 or later for
Windows 7® or Windows Server®2008 R2 Standard platforms.
♦ I/A Series software v8.2 and later for Windows XP®, and Windows Server®2003
platforms.

NOTE
FoxView and FoxDraw software v10.3 and later do not run on Solaris platforms.
Refer to FoxView™ and FoxDraw™ Software V10.2.4 Release Notes (B0700RJ),
FoxView™ Software (B0700BD) and FoxDraw™Software (B0700BE) for further
information on Solaris support. These documents are available from the Global
Customer Support at https://support.ips.invensys.com.

Purpose
This document is designed to assist users in the installation of FoxView/FoxDraw software, and it
also indicates the problems fixed for v10.4.4 and User Notes if any.

Audience
As a current user of FoxView and FoxDraw software, you are encouraged to read the Revision
Information section for an explanation of what has been updated in this document. Additionally,
you should review the Appendix A “Problems Resolved in v10.4.4” for the problems that were
fixed in this current release.

Revision Information
For this revision of the document (B0700SN, Rev. G), the following changes were made:
Global
♦ Updated all references from 10.4.3 to 10.4.4.
Chapter 3 “New Features”
♦ Added section “New Features for FoxView/FoxDraw Software v10.4.4” on page 13.

vii
B0700SN – Rev G Preface

Chapter 5 “User Notes”

♦ Updated “FoxView Software” on page 19.
Appendix A “Problems Resolved in v10.4.4”
♦ Added this appendix for 10.4.4.

Reference Documents
For FoxView and FoxDraw software v10.4 running on Windows 7, Windows Server 2008 R2
Standard, Windows XP, or Windows Server 2003 platforms, refer to the following documents:
♦ FoxView™ Software V10.4 (B0700FC, Rev. B or later)
♦ FoxDraw™ Software V10.4 (B0700FD, Rev. B or later)
For FoxView and FoxDraw software v10.3 running on Windows 7 or Windows Server 2008 R2
Standard platforms, refer to the following documents:
♦ FoxView™ Software V10.3 (B0700FC, Rev. A)
♦ FoxDraw™ Software V10.3 (B0700FD, Rev. A)
♦ FoxView and FoxDraw V10.3 Release Notes (B0700SA)
For FoxView and FoxDraw software v10.2.4 running on Windows XP or Windows Server 2003
platforms, refer to the following documents:
♦ FoxView™ Software (B0700BD)
♦ FoxDraw™Software (B0700BE)
♦ FoxView™ and FoxDraw™ Software V10.2.4 Release Notes (B0700RJ)
For information about installing and configuring a Remote X Server for FoxView software, refer
to:
♦ Appendix A in FoxView™ and FoxDraw™ Software V10.2.4 Release Notes (B0700RJ)
For FoxView and FoxDraw software v9.0.4 or earlier running on Windows XP, Windows Server
2003, or earlier Windows platforms, refer to the following documents:
♦ FoxView™ Software (B0193WH)
♦ FoxDraw™Software (B0193WG)
♦ FoxView and FoxDraw V9.0.4 Software Release Notes (B0193WL)
In addition, refer to the following documents for more information about FoxView and FoxDraw
software:
♦ Display Commands (B0193DF)
♦ FoxRemote™ and TCP/IP Network Integration, Installation, and Configuration Guide
(B0193VR)
♦ The MESH Control Network System Planning and Sizing (B0700AX)
♦ I/A Series® Model 51FoxRemote III Installation and Configuration Guide (B0193WZ)
Most of these documents are available on the I/A Series Electronic Documentation media
(K0173WT). The latest revisions of each document are also available through our Global Cus-
tomer Support at https://support.ips.invensys.com.

viii
1. Introduction to
FoxView/FoxDraw Software
This chapter discusses characteristics of this release and the supported platforms.

1.1 About this Release

Unless otherwise indicated in this document, the referenced version of FoxView™ software
(FoxView) and FoxDraw™ software (FoxDraw) is 10.4.4. This release of FoxView/FoxDraw soft-
ware can only be installed on I/A Series or Control Core Services systems running:
♦ I/A Series software v8.8 and later or Control Core Services v9.0 or later for Windows
7® or Windows Server®2008 R2 Standard platforms.
♦ I/A Series software v8.2 and later for Windows XP®, and Windows Server®2003
platforms.

NOTE
FoxView/FoxDraw software v10.3 and later software is not available for use on the
Solaris 10 platform. Solaris10 platform is supported only on FoxView/FoxDraw
software v10.2.x. For more information on support for Solaris 10 platform, refer to
the documentation provided with such versions of the product.

1.1.1 I/A Series Symbols for Windows

The I/A Series Symbols for Windows (part number K0175TW) CD is no longer packaged as a
separate CD. The I/A Series Symbols can be found on the installation CD within their own
directory.

1.2 Supported Platforms

FoxDraw software is available as a separate installation for workstations with non-I/A Series sys-
tems running on the Windows 7, Windows Server 2008 R2 Standard, Windows XP, and Win-
dows Server 2003 operating systems.
FoxView/FoxDraw software are supplied for:
♦ I/A Series Workstations running on Windows 7
♦ I/A Series Workstation Server running on Windows Server 2008 R2 Standard
♦ I/A Series Workstations running on Windows XP
♦ I/A Series Workstation Server running on Windows Server 2003

1
B0700SN – Rev G 1. Introduction to FoxView/FoxDraw Software

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

2.1 Display File Compatibility

The Displays and library objects built with the latest version of FoxDraw software are generally
not compatible with the older versions of FoxView and FoxDraw software. When upgrading from
a previous version of FoxView software and/or FoxDraw software, all workstations 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 configuration
information, newer displays and library objects may not work correctly on older versions of
FoxView and FoxDraw software.

NOTE
Displays created using FoxDraw software v10.3 or later cannot be used in earlier
versions of FoxView or FoxDraw software without using conversion tools.

2.1.1 Display Conversions

Table 2-1 through Table 2-6 explain the possible conversions from the Display Manager displays
to FoxView displays and display conversions between different versions of FoxView software.

NOTE
For further details of display conversions, refer to succeeding sections.

Table 2-1. Conversion Steps Required To Use Display on Destination Station - Display Manager

Version on Source Converted to any Windows or Solaris FoxView Version on Any Version
Station of Windows or Solaris Listed in The Tables In This Subsection
Display Manager 1. Copy the Display Manager file (.pdf ) to the destination station.
2. On the destination station, run the utility pdf_fdf on the display.

3
B0700SN – Rev G 2. Installation Notes

Table 2-2. Conversion Steps Required To Use Display on Destination Station - 10.3-10.4.4 Windows

Conversion Steps
FoxView Version on
Source Station DESTINATION FoxView Version : 10.3-10.4.4 Windows
9.0.3 -10.4.4 Windows Display can be directly opened on destination station.
10.2 - 10.2.4 Solaris 10 1. On the source station, run fdf_g on the display.
2. Copy the .g file to the destination station.
9.0.3 - 9.0.4 Solaris 2.5.1/ 3. On the destination station, run g_fdf on the .g file.
Solaris 8

Table 2-3. Conversion Steps Required To Use Display on Destination Station - 10.2-10.2.4 Windows

Conversion Steps
FoxView Version on
Source Station DESTINATION FoxView Version : 10.2-10.2.4 Windows
10.3-10.4.4 Windows 1. On the source station, run fdf_g on the display.
2. Copy the .g file to the destination station.
10.2-10.2.4 Solaris10 3. On the destination station, run g_fdf on the .g file.
9.0.3-9.0.4 Solaris 2.5.1/
Solaris 8
9.0.3-10.2.4 Windows Display can be directly opened on destination station.

Table 2-4. Conversion Steps Required To Use Display on Destination Station - 10.2-10.2.4 Solaris

Conversion Steps
FoxView Version on
Source Station DESTINATION FoxView Version : 10.2-10.2.4 Solaris
9.0.3-10.4.4 Windows 1. On the source station, run fdf_g on the display.
2. Copy the .g file to the destination station.
3. On the destination station, run g_fdf on the .g file.
10.2 - 10.2.4 Solaris 10 Display can be directly opened on destination station.
9.0.3-9.0.4 Solaris 2.5.1 /
Solaris 8

Table 2-5. Conversion Steps Required To Use Display on Destination Station - 9.0.3/9.0.4
Windows

Conversion Steps
FoxView Version on
Source Station DESTINATION FoxView Version : 9.0.3/9.0.4 Windows
10.4.4 Windows 1. On the source station, run the Dconvert 10x to 9x utility.
2. Copy the .g file to the destination station.
3. On the destination station, run g_fdf on the .g file.

4
2. Installation Notes B0700SN – Rev G

Table 2-5. Conversion Steps Required To Use Display on Destination Station - 9.0.3/9.0.4
Windows (Continued)

Conversion Steps
FoxView Version on
Source Station DESTINATION FoxView Version : 9.0.3/9.0.4 Windows
10.2-10.4.4 Windows 1. On the source station, run the Dconvert 10x to 9x utility.
2. On the source station, run fdf_g on the 9x .fdf file.
10.2 - 10.2.4 Solaris 10 3. Copy the .g file to the destination station.
4. On the destination station, run g_fdf on the .g file.
9.0.3-9.0.4 Windows Display can be directly opened on destination station.
9.0.3-9.0.4 Solaris 2.5.1/ 1. On the source station, run fdf_g on the display file (.fdf )
Solaris 8 2. Copy the .g file to the destination station
3. On the destination station, run g_fdf on the .g file.

Table 2-6. Conversion Steps Required To Use Display on Destination Station - 9.0.3-9.0.4
Solaris 2.51/ Solaris 8

Conversion Steps
FoxView Version on
Source Station DESTINATION FoxView Version : 9.0.3-9.0.4 Solaris 2.51/Solaris 8
10.4.4 Windows 1. On the source station, run the Dconvert 10x to 9x utility.
2. Copy the .g file to the destination station.
3. On the destination station, run g_fdf on the .g file.
10.2 - 10.4.2 Windows 1. On the source station, run the Dconvert 10x to 9x utility.
10.2 - 10.2.4 Solaris 10 2. On the source station, run fdf_g on the 9x .fdf file.
3. Copy the .g file to the destination station.
4. On the destination station, run g_fdf on the .g file.
9.0.3-9.0.4 Windows 1. On the source station, run fdf_g on the display.
2. Copy the .g file to the destination station.
3. On the destination station, run g_fdf on the .g file.
9.0.3 -9.0.4 Solaris Display can be directly opened on destination station.
2.5.1/ Solaris 8

5
B0700SN – Rev G 2. Installation Notes

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 software v10.x:
1. Historical Data in X/Y Plots: Only FoxDraw software v10.x provides the ability
to configure historical data in X/Y plots.
2. Additional X/Y Plot Color Configuration Option: With FoxDraw software 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 software v10.x only, X/Y plots
supports the configuration of zone lines for each pen in a plot.
4. Trend Features: With FoxDraw software 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 is updated to include the 10x to 9x G conversion option. The purpose
of this option is to convert a FoxView/FoxDraw software v10.x display file (.fdf ) or library object
(.m1) to a FoxView/FoxDraw software v9.x g file.
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.
Transfer the .g files to the target station, and run g_fdf or g_m1 to get compatible .fdf/.m1 files
for the 9.x station.

2.1.2.2 Conversion Using FoxDraw Software

To convert displays from FoxDraw software:
1. Click Save As 9.x (.g file) from the File menu.
2. Select the path in which you want 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
ascii format (.g files) in the 9x folder.
2. Type:
/usr/fox/wpb/bin/tools/fdf_version -b *.m1

6
2. Installation Notes B0700SN – Rev G

This converts all the library objects in the current directory and saves the converted
library objects in ascii format (.g files) in the 9x folder.
On the target station, the .g files should be converted to .fdf/.m1 format using the conversion
utility "g to fdf" or "g to m1".
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 Multiple Ramp Operations

Because FoxView software updates the display after set operations are complete, it may appear to
the user that multiple ramp operations are not working on a busy network.
Beginning with FoxView software v10.4.3, mouse clicks will be ignored until the current ramp
operation completes. The user will be notified of this with the following message:
Ignoring current event: Ramp already in progress.
Multiple mouse clicks are ignored only when the user repeatedly tries to click the ramp button.
This will not affect the existing continuous ramp functionality.

2.3 Files to Back Up Before Installation

Display files (.fdf ) are not overwritten during installation of FoxView/FoxDraw software. Display
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 software release. If these subdirectories are restored
with files from a previous release, the modifications included with this new release are lost. In gen-
eral, 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 overwritten 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 environment’s .env file must be found in the
/opt/fox/env directory.
It is recommended to take a back up of the ScratchPad and Trend Configuration files in the
/opt/Customer directory for Operator and Process_Eng, before installing a new version of Fox-
View/FoxDraw software:
D:/opt/customer/ScratchPads/Operator/Trends/trend_sublist.txt

7
B0700SN – Rev G 2. Installation Notes

D:/opt/customer/ScratchPads/Operator/ScratchPads/trend_list
The file /usr/fox/wp/data/fv_cmds is used to set:
♦ Different permissions to local and remote sessions of FoxView software
♦ Define the FoxView startup environment
♦ Define the initial display etc.
If any changes have been made to this file, it is recommended to take a backup of the file
/usr/fox/wp/data/fv_cmds.

2.4 Installing the Software

The FoxView/FoxDraw DVD-ROM contains the installations for the Windows 7,
Windows Server 2008 R2 Standard, Windows XP, or Windows Server 2003 versions of FoxView
and FoxDraw software along with the FoxView/FoxDraw documentation and I/A Series Symbols.
The software is compatible with I/A Series software v8.2 to 8.8, Control Core Services v9.0, and
later.

NOTE
Contact the Global Customer Support Center at 1-508-549-2424 (worldwide) or
1-866-746-6477 (U.S. Canada toll-free) or visit the Global Customer Support
Web Site at https://support.ips.invensys.com for the recommended Quick Fixes to
install for this software release.

2.4.1 Windows 7, Windows Server 2008 R2 Standard,

Windows XP and Windows Server 2003 Platforms with
I/A Series Software
To install the FoxView/FoxDraw software from the DVD-ROM on Windows 7, Windows Server
2008 R2 Standard, Windows XP, or Windows Server 2003 platforms, use the following
procedures:
1. Back up any customized files. Please refer to “Files to Back Up Before Installation” on
page 7 for suggested files.
2. If a previous version of FoxView/FoxDraw software is installed, uninstall it using the
procedures on page 10. Wait several minutes between the uninstall and install on
Windows Server 2008 R2. This allows the operating system time to complete its
pending delete operations on uninstalled files.
3. The FoxView/FoxDraw software installation process requires that the I/A Series soft-
ware be turned off.
♦ For Windows 7 or Windows Server 2008 R2 Standard platforms, from the
Control Panel, select the I/A Series Startup Options.
♦ For Windows XP and Windows Server 2003 platforms, from the Control Panel,
select the Foxboro I/A Control Panel applet and select Startup Options
for Reboot.
♦ When the dialog appears, check either Autologon or Manual Logon in the
“I/A Series Off ” group.

8
2. Installation Notes B0700SN – Rev G

4. Reboot the workstation.

5. Insert the FoxView/FoxDraw DVD-ROM into the DVD-ROM drive.
6. The Installation program should start automatically. If it does not, locate the
\Win\setup.exe on the DVD and double-click on the file to initiate the installation.
7. When the FoxView/FoxDraw Setup dialog box appears, select the button beside the
component FoxView/FoxDraw v10.4.4, and click Next to continue with the
installation.
8. After installation is complete, turn on the I/A Series software and reboot the worksta-
tion:
♦ For Windows 7 or Windows Server 2008 R2 Standard platforms, use the menu
option Start -> Shutdown -> Restart.
♦ For Windows XP and Windows Server 2003 platforms, use the FoxShutdown
command.

NOTE
Installation of FoxView/FoxDraw software installs the FoxView User Guide, Fox-
Draw User Guide, and FoxView/FoxDraw Release Notes.
These documents can be accessed through Start > Program > FoxView-FoxDraw
Documentation.

NOTE
FoxView/FoxDraw software v10.4.4 integrates with IACC v2.6.4. Refer to “Fox-
Draw Software” on page 24 for information on successful integration between previ-
ous versions of FoxView/FoxDraw software and IACC.

2.4.2 Non-I/A Series Windows Platforms

FoxDraw software can be installed on a non-I/A Series station with the Windows 7, Windows
Server 2008 R2 Standard, Windows XP, or Windows Server 2003 operating systems. To install
the Windows version of FoxDraw software from the DVD-ROM, use the following procedures:
1. If a previous version of FoxDraw software is installed, prepare to uninstall FoxDraw
software as follows:
♦ For Windows 7 or Windows Server 2008 R2 Standard platforms, select Control
Panel -> Programs and Features.
♦ For Windows XP or Windows Server 2003 platforms, select Control Panel ->
Add or Remove Programs.
2. Select FoxView/FoxDraw, click Change/Remove, then click Yes to remove the appli-
cation and all of its components.
3. Insert the FoxDraw v10.4.4 DVD-ROM into the DVD-ROM drive.
4. From Explorer, double-click on \setup.exe.
5. After the installation is completed, reboot the station.

9
B0700SN – Rev G 2. Installation Notes

2.4.3 Uninstalling on Windows 7, Windows Server 2008 R2

Standard, Windows XP and Windows Server 2003 Platforms
FoxView/FoxDraw 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.
♦ For Windows 7 and Windows Server 2008 R2 Standard platforms, select
Control Panel -> I/A Series Startup Options icon.
♦ For Windows XP and Windows Server 2003 platforms, select Control Panel ->
Foxboro I/A icon.
2. When the dialog box appears, check either Autologon or Manual Logon in the
“I/A Series Off ” group.
3. Reboot the workstation.
4. Select the following:
♦ For Windows 7 or Windows Server 2008 R2 Standard platforms, select Control
Panel -> Programs and Features. Select FoxView/FoxDraw, click Unin-
stall, then click Yes to remove the application and all of its components.
♦ For Windows XP or Windows Server 2003 platforms, select Control Panel ->
Add or Remove Programs. Select FoxView/FoxDraw, click Change/Remove,
then click Yes to remove the application and all of its components.
5. On Windows Server 2008 R2, please wait several minutes before initiating an installa-
tion. This allows time for the operating system to complete its pending delete opera-
tions on uninstalled files.

2.4.4 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 software v10.x Perform the
following 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 direc-
tory>\<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 direc-
tory>\<filename>.g

10
2. Installation Notes B0700SN – Rev 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 control stations.
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 software
v10.1 and if de-optimization is already done, the above de-optimization for the dis-
plays is not required.

2.5 FoxDraw Software and AIM*API Software

FoxDraw software uses the AIM*API (Application Program Interface) server interface to con-
nect to the I/A Series system via TCP/IP client/server communication protocol and then access
I/A Series data. Acting as a client, FoxDraw software retrieves Compound Summary Access
(CSA) data to support the Compound/Block browser, parameter and range data from the
Control Processor for faceplates, trend pens, marker locations, and attributes such as Fill Level.
FoxDraw software automatically looks for any configured servers.
FoxView/FoxDraw software integrates with different versions of AIM:
♦ For Windows XP and Windows Server 2003 platforms - AIM 3.3
♦ For Windows 7 and Windows Server 2008 R2 Standard - AIM 3.4
For further information on configuring servers with the AIM*API software, refer to the
AIM*AT Installation Guide (B0193YM, Rev. G or later).

11
B0700SN – Rev G 2. Installation Notes

12
3. New Features
This chapter describes the new features included in the software since the last major release of
FoxView/FoxDraw/FoxSelect software.

3.1 New Features for FoxView/FoxDraw Software

v10.4.4
3.1.1 Thicker Overlay Borders
FoxView 10.4.4 and later allows the configuration of thicker overlay borders using the new vari-
able FV_THICK_OVL_BORDERS. To enable this border style, complete the following proce-
dure.
1. open the init.user file in D:/usr/fox/wp/data location.
2. Add the following line FV_THICK_OVL_BORDERS=Y.
3. Save the file and restart the machine.
Thicker overlay borders are applied only to overlays in stationary mode. When the FoxView win-
dow gets resized, the thicker overlay borders get reset.

3.2 New Features for FoxView/FoxDraw Software

v10.4.3
FoxView/FoxDraw software v10.4.3 is updated to retain the configured engineering units of
Display Manager trends in FoxView software.

3.2.1 Retaining Configured Engineering Units of the Display

Manager Trends in FoxView Software
A new command line option -d is implemented in the conversion g_fdf utility tool. The -d
option allows the engineering units of the pen to be retained as they were originally configured in
the Display Manager, instead of defaulting to percentage units.
To retain the Display Manager Engineering Units:
1. Open command prompt
2. Go to \usr\fox\wp\bin\tools
3. Run the g_fdf utility using the command line option -d
e.g. g_fdf.exe -d d:\opt\menus\d1\disp1.g
You can also use the -d option along with wild cards and other command line
options.
e.g. g_fdf.exe -d d:\opt\menus\d1\*.g
g_fdf.exe -d -r d:\opt\menus\d1

13
B0700SN – Rev G 3. New Features

NOTE
The -d option is recommended only for displays with Display Manager trends.
If you convert .g files using the dconvert utility, the Display Manager
engineering units are not retained.

3.3 New Features for FoxView/FoxDraw Software

v10.4.2
FoxView and FoxDraw v10.4.2 have been updated to support user-defined control of the display
rendering and aspect ratio of text objects. Both features require modifying variables in the
init.user file. If you do not have the init.user file on your system, copy the
/usr/fox/wp/data/init.user.rel file to /usr/fox/wp/data/init.user. The
init.user.rel file is a template file for init.user.

3.3.1 Text Rendering Compatible with 10.2.x Displays

FoxView and FoxDraw v10.4.2 have been updated for use with the variable
FV_CLASSICFONTS to allow the user to select the font rendering style, addressing the issue
that some fonts may render slightly smaller or larger on FoxView/FoxDraw v10.3 and later when
compared to FoxView/FoxDraw v10.2.x. By default, fonts will be rendered as v10.3 and greater.
For font display rendering compatible with 10.2.x, define and set the FV_CLASSICFONTS vari-
able to 1 in the init.user file as described below. This variable instructs FoxView/FoxDraw to ren-
der fonts as pre-10.3 versions do. If not defined or set to 0, fonts will be rendered as v10.3 and
later.
Define as described below:
1. On I/A stations, set the variable by adding the FV_CLASSICFONTS=1 in
/usr/fox/wp/data/init.user.
2. Restart the machine to effect the change in FV_CLASSICFONTS value.
3. On standalone FoxDraw software installations, set the value in Control Panel System
environment variables; i.e. FV_CLASSICFONTS = 1.

3.3.2 Maintaining Font Aspect Ratio on Window Resize

In some cases, fonts may be resized when the window is not resized. This behavior has been seen
when the taskbar is hidden on a widescreen monitor. The variable FV_FONTASPECTRATIO
can be defined and set to N to avoid this unusual behavior. By default and undefined, font aspect
ratio is Y.
Use as described below:
1. Define FV_FONTASPECTRATIO in the /usr/fox/wp/data/init.user file.
2. Set the Value to ‘N’
i.e. FV_FONTASPECTRATIO=N.
3. Restart the machine.

14
3. New Features B0700SN – Rev G

3.4 New Features for FoxView/FoxDraw Software

v10.4.1
FoxView and FoxDraw v10.4.1 have been updated to support a user-defined cursor and scroll
region font. Both features require modifying the init.user file. If you do not have the init.user file
on your system, copy the /usr/fox/wp/data/init.user.rel file to
/usr/fox/wp/data/init.user. The init.user.rel file is a template file for init.user.

3.4.1 Defining a Cursor

FoxView allows the user to define a cursor to override the windows defined mouse pointer. In the
init.user file assign FV_CURSOR to a defined cursor file; e.g.
FV_CURSOR=C:/WINDOWS/Cursors/pen_i.cur
If the file does not exist, is not valid or definition/assignment is incorrect, the default cursor file
will be used.

3.4.2 Scroll Region Fonts

The user can specify the font for Scroll regions in the init.user file.
The format is specified below in the example configuration syntax.
FV_FONTNAME=Courier New
FV_FONTSTYLE=Italic
FV_FONTSIZE=16
♦ FV_FONTNAME - select from the list of fonts specified in the fontdef.dat file which
is located at opt/fox/wp/data or opt/customer/data
♦ FV_FONTSTYLE - select from Regular, Bold, Italic, or Italic Bold
♦ FV_FONTSIZE - specify the point of the font. Minimum 2, maximum 16.
If the font name and style are not specified in the init.user file or the specified font in the init.user
is not supported by FoxView, the default font, style and size will be used.
The default values considered are:
♦ FontName - Font specified in the registry location for Notepad or Windows, by
default, will use the best possible match.
♦ FontStyle - Regular
♦ FontSize - 16
See User Note 34 item 4 on page 24 regarding the default font size change from 16 to 10. This
change is available in version 10.4.2.

15
B0700SN – Rev G 3. New Features

16
4. Known Problems
This chapter lists the known problems that affect the FoxView/FoxDraw software.

4.1 FoxView Software

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) with-
out entering any data, the field does not return to its original text contents until an
update is received for the field.
4. If text objects are resizing to display over neighboring objects, convert the text objects
to text rectangles with a fit-width constraint. This will contain the text so it does not
overlay nearby objects.
To convert text objects to text rectangles:
a. Convert all text objects to text rectangles.
b. Save the .fdf file, then convert the .fdf file to a .g file.
c. Open the .g file, find the text and change the tconstraint value from 0 to 2 for the
object (this changes the constraint from 'none' to 'fit width', which will constrain
it to the size of the rectangle extents).
d. Save the .g file,
e. Convert the .g file to .fdf.
f. Load the .fdf file into FoxView software.

17
B0700SN – Rev G 4. Known Problems

4.2 FoxDraw Software

1. User settings are not saved when you exit FoxDraw software.
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 software to actually get the original contents of the display file from the disk
drive. Instead, FoxDraw software uses the currently open display. This means that you
cannot abandon changes made to the current display by reopening the display. To do
this, open another display (or create a new display) first and select No when asked
whether you would like to save the changes to the current display.
4. Widescreen conversions are not applicable to library objects and palettes (with .m1
extension). However, when they are saved in FoxDraw software, the “Opening display
after conversion” dialog box appears if “Yes” is selected for the Save display in the User
Options - Widescreen preferences; but the widescreen conversion will not occur.

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

5.1 FoxView Software

1. When pressing the buttons in FoxView software, the Hist names in the “BATCH
Advanced Trend Configuration” change, but the Trend updates from the other, after
two refreshes with CTRL+1. To resolve this, use the command as follows:
dmcmd trend -line 1 -g Trend_1 -name C:B:P -hist histname
Ex: dmcmd trend -line 1 -g Trend_1 -name
SIMCMP1:COSINE.MEAS -hist ding10
Without giving the C:B:P name, the trend command is not complete, as per
I/A Series Display Commands I/A Series® Display Commands (B0193DF) document.
The command does not take effect (and the trend is not redrawn) until the trend
command is complete.
2. A new parameter DM_CRAMP has been added to enable/disable continuous ramp-
ing when the left mouse button was held down. This parameter can be defined as “N”
in the /usr/fox/wp/data/wp51_glbls.all to disable continuous ramping. If it is not
defined or set to any other value, continuous ramping will be enabled.
3. Blinking colors are not supported in trends. This applies to displays that have been
converted from Display Manager format to FoxView format.
4. 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.

19
B0700SN – Rev G 5. User Notes

5. When configuring pickable areas within faceplates, the use of $ is allowed. However,
for data entry and ramp fields, FoxView software 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.
6. 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 con-
verted 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.
7. FoxView software provides block out-of-service (OOS) indication only for text update
dynamics to strings of the background text type. In FoxDraw software, select Back-
ground Text for all strings that have text update connections applied.
8. If a display has a group that contains no objects when the display is called into
FoxView software, the entire display flashes for up to three updates. To fix this prob-
lem, call the display into FoxDraw software, make a change, and save the display.

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

9. When you move the mouse out of the FoxView window with a Select/Assign or
display bar configuration pop-up menu that is displayed, the input focus may not fol-
low 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 software.
10. Environment names must have fewer than 14 characters; otherwise, they are not pro-
cessed.
11. FoxView software must have a working initial display (/opt/custom/Initial_Disp.fdf )
and a working initial environment (/opt/fox/env/Initial.env, Initial.dbr, Initial.mbr)
in order for FoxView software to start.
12. Some of the resources within the Windows workstation are limited. Examples of these
limited resources are menu entries, windows, dialogs, pens, and other Windows
graphics. This means there is a maximum number of combined menu entries, win-
dows, etc., for the entire workstation. While this limit is large, it is possible to config-
ure the workstation in such a way that this limit is reached. For example, if multiple
instances of FoxView software are running on a single workstation and each FoxView
software is in an environment that contains a large number of menu entries, this limit

20
5. User Notes B0700SN – Rev G

can be reached. When the limit is reached, one or more FoxView software instances
are missing from of the expected menu items. To avoid this problem, large environ-
ments 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.

13. When editing PLB, do not call the new ladder display into FoxView software until the
Control Configurator has completed the installation of the ladder.
14. 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.
15. It is not recommended that objects with thick edge widths be configured for visibility.
FoxView software 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.)
16. 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.
17. 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 soft-
ware. It is not possible to create a display named tank_on_legs and successfully link
the tank_on_legs library object into that display.
18. 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 software 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 software do not support |RO1 in commands within aliased objects.
Instead, the |DEFAULT syntax should be used. (CAR 1004615).

21
B0700SN – Rev G 5. User Notes

19. 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.
20. 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 software resolves @
character.
21. You may observe white patches on moveable overlays while opening or closing or
moving out screen area and other applications like the On-Line Trend Configurator
(OLTC). This can be overcome by moving the mouse pointer over the affected overlay
region.
22. When FoxView software is running through Exceed™ on a Windows NT worksta-
tion, changing an overlay from moveable to stationary causes the overlay position to
change. This is the default behavior of overlays when FoxView software 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
> Exceed> 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. Whenever time is set back using SMDH or System Manager, displays containing
trend / plot objects need to be re-called to reflect updates.
24. FoxView/FoxDraw/FoxSelect software does not support changing time backwards by
more than two (>2) years at a time using SMDH.
25. 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.
26. FoxView software 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.
27. 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.
28. Whenever the user clicks on Close button of the Help option for
Group_list/Trend_list under scratchpads, half of the screen appears white. This prob-
lem occurs with Resolution 1280x1024. To fix the problem move/resize the window.
29. When the user opens an overlay as “Open Overlay” action configured for any object,
the right and top margin does not appear for the overlay.

22
5. User Notes B0700SN – Rev G

30. On Windows 7, resize the FoxView window to see the right scale of any configured
Trend.
31. The g_fdf utility encounters an error when the first character in the file name of a
library object is numeric. The scripts are provided to resolve this issue. Refer to
FoxDraw Software (B0700FD) document, under section Display Convert Utility -
Library Objects having first character as Numeric for the script for more information.
32. When a trend configured with historical data is opened in Pause mode and switched
to update mode there can be a disconnect between the historical data and the real-
time data. This is displayed as a line connecting the last point of historical data and
the first point of real-time data. The behavior is because until the update button is
clicked the data collection for real time data has not happened. This happens only for
the first time after opening the display in pause mode. Then on, switching between
pause and update mode any number of times will not result in such a behavior. To
view the correct trend for that particular duration reload the display.
33. When optimized FoxView displays are copied from one I/A Series system to another,
it is recommended that they are de-optimized.
Failure to de-optimize highly complex displays may result in the displays failing to
connect to control database values.
To de-optimize the display, convert the display from fdf-to-g (with the fdf_g utility)
and g-to-fdf, (with the g_fdf utility) as described in “Conversion Utilities” in
FoxDraw Software (B0700FD).
34. Text Sizing, Resizing and Fonts
1. In some cases, fonts may be resized when the window is not resized. This behavior
has been seen when the taskbar is hidden on a widescreen monitor. The variable
FV_FONTASPECTRATIO can be defined and set to N to avoid this unusual behav-
ior. By default and undefined, font aspect ratio is Y.
Use as described below:
a. Define FV_FONTASPECTRATIO in the /usr/fox/wp/data/init.user
file.
b. Set the Value to ‘N’
i.e. FV_FONTASPECTRATIO=N.
c. Restart the machine.
2. If window resizing causes text objects to display over neighboring objects, convert
the text objects to text rectangles with a fit-width constraint. This will contain the text
so it does not overlay nearby objects.
To convert text objects to text rectangles:
a. Convert all text objects to text rectangles.
b. Save the .fdf file, then convert the .fdf file to a .g file.
c. Open the .g file, find the text and change the tconstraint value from 0 to 2 for
the object (this changes the constraint from 'none' to 'fit width', which will con-
strain it to the size of the rectangle extents).

23
B0700SN – Rev G 5. User Notes

d. Save the .g file.

e. Convert the .g file to .fdf.
f. Load the .fdf file into FoxView software.

3. Fonts may render differently on FoxView/FoxDraw software v10.3 and later when
compared to FoxView/FoxDraw software v10.2.x. A new variable
FV_CLASSICFONTS is introduced to allow the user to select the font rendering.
The value of this variable can be either 1 or 0. Value 1 will turn ON the use of classic
fonts i.e. 10.2.x style. By default, classic fonts are not used; in other words, set
FV_CLASSICFONTS=0 or leave it undefined.
To turn ON the use of classic fonts, proceed as follows:
a. On I/A stations, define FV_CLASSICFONTS=1 in
/usr/fox/wp/data/init.user.
b. Restart the machine to effect the change in FV_CLASSICFONTS.
c. On standalone FoxDraw software installations, set the value in the
Control Panel System environment variables
Ex: FV_CLASSICFONTS = 1.

4. The FoxView scroll region font size rendering has been enhanced to more closely
resemble the font size rendering in Notepad. If no scroll region font is specified in the
init.user file, the following default values are used:
♦ FontName - Font specified in the registry location for Notepad or Windows, by
default, will use the best possible match
♦ FontStyle - Regular
♦ FontSize - 10

NOTE
When Arial 8 font is used, there may be truncation of some text if the input file has
spaces followed by tab characters. In such cases, it is advisable either to modify the
input file or to opt for a different font.

35. Continuous ramp operations will be terminated when the touchscreen gets powered
off or, the mouse gets disconnected on the actual AW and not on the stations that
connect to the AW using remote desktop application (mstsc).
36. When closing remote sessions, it is recommended that the user log off rather than dis-
connect or use any other means so that resources are freed up for further use. On I/A
series server 2003 stations, a special user account ("ia") is available for remote
FoxView access with limited privileges. When working with the "ia" user account, the
session is automatically logged off when you exit the FoxView session. This is the rec-
ommended method to close the remote sessions with the "ia" user account.

5.2 FoxDraw Software

24
5. User Notes B0700SN – Rev G

1. FoxDraw software integrates with IACC. To integrate FoxDraw software v10.4.1 suc-
cessfully with IACC 2.6, IACC QF1212056 needs to be installed on IACC 2.6. If
QF1212056 is not installed over IACC 2.6, then when installing FoxView/FoxDraw
software v10.4.1 setup with IACC installed, the error message, “The
FoxView/FoxDraw setup failed to launch the IACC integration script” appears.
Ignore this error message and install the QF1212056 for successful 10.4.1 integration
with IACC 2.6.
2. In a Non-I/A Series Windows Platform (I/A Series software not installed) if you are
unable to install FoxDraw software with the error “Cannot Install FoxDraw over I/A”
delete the following registry fields from the System.
HKEY_LOCAL_MACHINE\SOFTWARE\Foxboro\I/A Series\CurrentVer-
sion (or)
HKEY_LOCAL_MACHINE\SOFTWARE\Foxboro\IA Series\CurrentVersion
Install FoxDraw after these keys are deleted from the regis-
try.
3. For creating a new display using gedit, “NEW” command must be used in the script.
Please refer to FoxDraw™ Software (B0700FD) for more information.
4. FoxView software reads the user-defined convention file only upon startup. If you
add, change, or delete a convention in FoxDraw software, the effect of that change
does not take place until FoxView software is restarted.
5. 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:
Windows \opt\cus-
tomer\data\usr_conventions.dat

6. The base display area is logically a 75.0 high by 100.0 wide area for legacy display (4:3
aspect ratio) and 75.0 high by 133.33 wide area for widescreen displays (16:9 aspect
ratio) that occupies the client area of FoxView and FoxDraw software. The size of this
area is fixed and cannot be changed in FoxView or FoxDraw software. However,
within FoxDraw software, it is possible to drag objects outside of this area, either par-
tially or entirely. This can occur when using zoom out feature of FoxDraw software,
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 software.
An off-screen graphic can be so far off screen that it is not visible in FoxDraw soft-
ware. 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 software. Also, a defective
display eventually causes the workstation to fail.
To determine whether a display has this problem:
Within FoxDraw software, you can determine whether a display has this problem by
choosing Select All from the Edit menu and observing where the bounding selec-
tion rectangle is drawn.
a. Load the display.

25
B0700SN – Rev G 5. User Notes

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 software.
c. Click the Zoom out button twice. The area around the display appears.
d. Lasso the 75x100 base 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 software 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 software is to ignore invalid objects. If you believe
that you have a display that might have invalid objects and you would like FoxDraw
software 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 software.
If any potentially invalid objects are detected, FoxDraw software displays a message
box informing you of this. You have the option of ignoring the objects and leaving the
display as it is or allowing FoxDraw software to move the objects into the valid range.
Be sure to save the display if you have FoxDraw software move any objects.
7. 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.
8. 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.
9. 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 Table 5-1 below for a partial list of

26
5. User Notes B0700SN – Rev G

reserved words. Refer to “Reserved Keywords (Not For Use in Foxboro Display Files)”
on page 31 for the location of the full list of reserved words.

Table 5-1. Partial Reserved Word List

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

10. FoxView and FoxDraw software do not support file or directory names containing
spaces.
11. 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.
12. Copying an object configured with a fill level dynamic and then changing the object
orientation by rotating it causes problems in FoxView software with the redrawing of
the fill level. As a work around to this, rotate the object before applying the fill

27
B0700SN – Rev G 5. User Notes

dynamic or deselect the OptimizedUpdate checkbox in the Continuous dynamic

configuration dialog box.
13. 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 software.
14. Transparent rectangles configured with a fill level dynamic are not transparent for the
unfilled area of the object. If this behavior is not acceptable, use polygons instead of
rectangles.
15. When configuring custom menu entries in FoxDraw software, quotes are supported
within the command if the quote character (“) is preceded by a backslash (\).
16. Displays and library objects built with the latest version of FoxDraw software, are gen-
erally not backward compatible with previous versions of FoxView and
FoxDraw software. New features found in the latest FoxDraw software are not sup-
ported in previous versions of FoxView and FoxDraw software. However, if it becomes
necessary to move files from FoxDraw software v9.0.1 to a previous version of Fox-
View and FoxDraw software, 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 software, or use the utility fdf_g for display files and
the m1g utility for library objects.
b. If Windows FoxDraw software v9.0.1 or later used, the .g file must be converted
to be compatible with older versions of FoxView and FoxDraw software using the
g_back_g utility.
\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 software, or the g_fdf and
gm1 utilities from a command tool.
17. FoxDraw software must be restarted to affect the mode for case-sensitive tag names.
Stand-alone FoxDraw software restarts automatically. When FoxDraw software is
restarted, the FoxView button in FoxDraw software is disabled.
18. 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.
19. 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
objects, shift mouse click the objects on the screen in the order, and then select Layout
> Space Evenly to space the objects evenly.
20. 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.

28
5. User Notes B0700SN – Rev G

21. 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 software 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.
22. Only msglin command can be configured for close script for base displays.
23. Comment objects can not be created with multi-create option.
24. In FoxDraw software, the “zoom out” option does not work as intended when used
with widescreen display files on a standard definition (legacy) monitor.
Due to the difference in the aspect ratio of the standard definition monitors (with 4:3
aspect ratio) and the display file (with 16:9 aspect ratio), the “zoom out” option for a
widescreen format display file on a standard definition will not zoom out the display
to the center of the screen.
25. In FoxDraw software, when opening a legacy (.fdf at 4:3 aspect ratio) display for a
widescreen (16:9 aspect ratio) monitor, a dialog may appear which states: “Do you
wish to convert the display to Widescreen format?” Moving this dialog box around the
screen leaves trails and obscures the background. This also occurs for the dialog box
which states, “The display is configured in Widescreen format. It will open as Read-
only.” which opens when opening a widescreen display on a standard definition (4:3
aspect ratio) monitor. These trails may not disappear when the dialog boxes are closed.
It is recommended that you do not move these dialog boxes when they appear.
26. A widescreen display file opened on a legacy (4:3 aspect ratio) monitor will open as
read-only to prevent edits. It is assumed, as a widescreen file, that the user intends to
make edits within a monitor with a 16:9 aspect ratio. It is marked read-only to prevent
edits within a 4:3 aspect ratio monitor.
27. If a Display Manager display (.pdf ) file contains characters such as (Ctrl+x “”,
Ctrl+Esc "" and Ctrl+y "") which are treated as unprintable characters, the
pdf_fdf utility does not convert these characters to correct symbols.
If a Display Manager display (.pdf ) file contains (Ctrl+z "") which is treated as
EOF in windows, the conversion process will be terminated and the resulting display
file (.fdf ) may not be proper.
28. FoxDraw software supports context-sensitive help, however, the documentation
guides on the CD are the most current. If some of the context-sensitive links cannot
find their target, open the online documentation and search for the topic in question.
29. While creating faceplates, you must ensure the following conventions are maintained:
a. Custom faceplates should be stored in /opt/customer/displib/Faceplates.
b. Custom faceplates should be named as <BLOCKTYPE>_<text>.m1.
The <BLOCKTYPE> must be the name of a standard I/A Series block and must be
uppercase. The <text> can be a combination of uppercase and lowercase letters
and the numbers 0-9. For example, RIN_AUTO.m1.
c. When linking a faceplate to a display (from the Object menu, select Link Face-
plate/Trend), the custom faceplates are listed along with the default option.
(Refer to the subsection “To save the file” under “Creating a User-Built Faceplate”
in FoxDraw Software (B0700FD).)
To use custom faceplates in scratchpad group displays, perform the following:

29
B0700SN – Rev G 5. User Notes

a. Create and save overlay faceplates in the desired location. For example,
/opt/customer/overlayFaceplates
b. Define the variable FV_FPOVL in /usr/fox/wp/data/init.user.
The value set by this variable overrides the default path -
/opt/fox/displib/OverlayFaceplates.

NOTE
The custom faceplates should have the same name as the block, e.g. RIN.fdf. The
size of the custom faceplates should be same as the standard Foxboro faceplates.

Refer to the “ov_conn” section and the “Reserved Workstation Variables” chapter
in Display Commands (B0193DF). The defaults for FoxView software are
FV_FPOVL or /opt/fox/displib/OverlayFaceplates.
30. Due to enhanced security features, the Foxboro default environment of FoxView/Fox-
Draw software v10.3 and later are different from the environment of versions prior to
v10.3. You can revert the security enhancements by deleting/relocating the .acl files
available at opt/fox/env.
You can add commands to the .acl files to protect /unprotect the required access locks.
If an access is protected, an unprotect command is required to unlock it. For exam-
ple, if a protect all command is specified in the initial environment (.env) all
other environments (.env) that require full access must have the dmcmd unprotect
all command in the .acl file.

5.3 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 con-
nected 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.
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. 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)

30
5. User Notes B0700SN – Rev G

5.4 DEdit
1. If you have the “Validate Points in Reports” option enabled for a large display with
many unavailable or nonexistent 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 dis-
abled.
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. While converting the original display .fdf to Ascii.g format on Windows 7, the user
need not specify the flag. The fdf_g utility is built with the special flag. If sl-gms util-
ity is used directly then the user has to specify the -tdigits 10 flag.
For example, m1g -tdigits 10 D1180_182_01.m1.

5.6 Reserved Keywords (Not for Use in Foxboro

Display Files)
Refer to the appendix “Reserved Keywords (Not For Use in Foxboro Display Files)” in FoxDraw
Software (B0700FD) for a list of reserved keywords for which objects in converted user-modified
Foxboro display files should not be named.
When converting user-modified Foxboro display files (that is, Foxboro display files which you
have modified), be aware that the conversion tool has a list of reserved keywords that should not
be used when building displays. After conversion, some objects may derive a name which exists in
this list of reserved keywords. Ensure that the objects in converted Foxboro display files do not
match any of the keywords listed in this appendix.

5.7 10x to 9x Conversion

The 9x .fdf/.m1 files created on the source stations (with FoxView and FoxDraw software 10.3
and later) cannot be used directly on the target stations (with FoxView and FoxDraw software 9x).
This is due to the incompatibility with the third party (SL-GMS) version. In such cases, you need
to perform the following additional steps:
1. Convert .fdf files to .g files on the source station
2. Convert .g files to .fdf files on the target station
From FoxView and FoxDraw software 10.4.3 onwards, the 10x to 9x conversion generates a .g file
directly instead of a .fdf/.m1 file. This ensures that the user need not manually convert the .fdf file
to a .g file. The generated .g file must then be converted to a .fdf/.m1 file on the target station.

31
B0700SN – Rev G 5. User Notes

The .g file can also be generated from any of the following options:
♦ Save As 9.x (.g file) option from FoxDraw software
♦ -b command line option of fdf_version.exe

32
6. FoxView Capabilities
This chapter provides migration information as well as performance capabilities as well as
cross-platform and remote display 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 software. Conver-
sion 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).
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 software v10.4.3
includes the functionality to handle DM font conversion correctly for Windows platforms.
To convert DM displays using FoxView/FoxDraw software v10.4.3 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 -foxboro-ia2swdh-bold-r-normal--0-0-75-75--0-

33
B0700SN – Rev G 6. FoxView Capabilities

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. For better visibility on windows platforms these entries should be modified as follows
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 con-
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).

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 software.

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

34
6. FoxView Capabilities B0700SN – Rev G

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).

To load I/A Series fonts on Windows XP/Server 2003 for FoxView/FoxDraw software:
1. After installing FoxView/FoxDraw v10.4.3 or later, the font \ia will be available in
the folder “D:\opt\fox\displib\font\ia”.
2. Browse and open C:\WINDOWS\Fonts.
3. From the File menu, select “Install New Font”.
4. From the Drives drop-down menu select the drive you want.
5. In the Folders, double click the folder that contains the font you want to add.
D:\opt\fox\displib\font\ia
6. In List of Fonts, click Select All to add all of the listed fonts and then click
OK. This installs the I/A Series fonts.
7. Run \usr\fox\wp\bin\tools\mod_fontdef.bat batch file to update the font
def.dat file with I/A Series fonts.
8. Make sure that following I/A Series font entries are there in the
D:\usr\fox\wp\data\fontdef.dat file. The entries are added by
mod_fontdef.bat
default raster 92 ia0swdh
default raster 93 ia0dwsh
default raster 94 ia0swsh
default raster 95 ia2swsh
default raster 96 ia2dwsh
default raster 97 ia2swdh
9. Restart FoxView.
To load I/A Series fonts on Windows 7/Server 2008 R2 for FoxView/FoxDraw software:
1. After installing FoxView/FoxDraw v10.4.3 or later, the font \ia will be available in
the folder “D:\opt\fox\displib\font\ia”.
2. Copy all the fonts in D:\opt\fox\displib\font\ia to C:\WINDOWS\Fonts.
This will automatically install the fonts.
3. Run \usr\fox\wp\bin\tools\mod_fontdef.bat batch file to update the
font_def.dat file with I/A Series fonts.
4. The following I/A Series font entries will be added to the
D:\usr\fox\wp\data\fontdef.dat file.
default raster 92 ia0swdh
default raster 93 ia0dwsh
default raster 94 ia0swsh

35
B0700SN – Rev G 6. FoxView Capabilities

default raster 95 ia2swsh

default raster 96 ia2dwsh
default raster 97 ia2swdh
5. Restart FoxView software.

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 software. These files, even if they do not have a large number of connections,
can experience 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
high numbers of connections to frequently changing data is magnified if the workstation hosts a
large number of FoxViews.
Certain dynamic update objects simply use more workstation resources than others. The objects
using the most resources are those with move attributes (Scale, Rotate, Move Horizontal, Move
Vertical, Move Path), time trends, XY Plots, and Profile Plots. Users should not be discouraged
from using these objects and dynamics, but should use them wisely.
Each workstation has a limited amount of processing power. If a workstation is running other
application, such as a batch engine or another application, then fewer resources are available for
FoxViews. Remote FoxView software, those running on an X-Terminal, a personal computer with
X-Terminal, or a personal computer hosted by a Server 2003, use as many resources as a
FoxView software displayed on the workstation’s monitor. When the CPU idle time drops below
30%, FoxView software begins dynamically adjusting resource levels to try to optimize perfor-
mance. (See “Dynamic Resource Allocation” in Display Engineering for FoxView™ Software and
Display Manager Software (B0193MQ).

36
6. FoxView Capabilities B0700SN – Rev G

6.3 Cross-Platform Capability

FoxDraw software is available as a separate installation for non-I/A Series workstations using Win-
dows. Displays built with FoxDraw software on a stand-alone platform may be used with Fox-
View software on either Windows or Solaris I/A Series platform.
Each platform has a binary display format which can be converted into an ASCII format. The
ASCII version of displays may be moved between platforms and converted back into binary.
Inter-platform compatibility is excellent. The only known differences in display appearance are
due to fonts. True-type fonts on Windows platforms are mapped to scalable X-Window System
fonts on Solaris platforms. While the mapping is excellent, it is not perfect. If you require exact
font mapping and scaling, use Hershey fonts, which map to the nearest pixel.

6.4 Remote Display Capability

Windows Server 2003 and Windows Server 2008 R2 Standard operating systems provide remote
display capability for FoxView software.

37
B0700SN – Rev G 6. FoxView Capabilities

38
Appendix A. Problems Resolved in
v10.4.4
This appendix lists the problems resolved for FoxView/FoxDraw software version 10.4.4

A.1 FoxView Software

1. For FF blocks, FoxView detail displays show incorrect values (negative) if the value of
Channel, EUI1 and EUO1 parameters is greater than 32767. (CAR 1268906)
2. When 4:3 displays are opened in Wide Screen Resolution (WSM), executing momen-
tary contact as "Hold-Down" does not work. (CAR 1275036)
3. The FoxView startup option is not enabled in the Configurator interface due to
incompatibility between FVFD (10.4.2 and 10.4.3) and FCS 6.0 installation. (CAR
1276972)
4. The Display Manager (DM) blink functionality does not work after converting DM
overlays to FoxView overlays. (CAR 1268161)
5. In WSM resolution, when two overlays are opened side by side, the previous overlay is
closed even if the overlays do not overlap each other. (CAR 1278782)
6. Overlays in FoxView don't show a black colored border by default. (CAR 1193764)
7. If touch screen is powered off while the user performs a continuous ramp operation,
FoxView does not terminate the ramp operation. (CAR 1277009)
8. The Logarithmic trend configuration of the Online Trend Configuration, advanced
option, Low Decade behavior has changed from 9.0.4. (CAR 1288645)
9. Scratch pad trend overlays when restored, do not resize the trends. A refresh/resize of
the overlay is required. (CAR 1278433)
10. Sometimes a remote FoxView connection cannot be established with the server. A
reboot is required to restore functionality. (CAR 1252536 ,CAR 1262252,
CAR 1276394)
11. FoxView Trends show incorrect data at the beginning of the trend lines during Pause
mode. The data displayed is different from the real data. (CAR 1224856)

A.2 FoxDraw Software

1. In FoxDraw v10.3 and above, setting the default display Attributes has no effect. The
chosen defaults are not applied after having them configured. (CAR 1277256)

39
B0700SN – Rev G Appendix A. Problems Resolved in v10.4.4

40
Appendix B. Problems Resolved in
v10.4.3
This appendix lists the problems resolved for FoxView/FoxDraw software version 10.4.3.

B.1 FoxView Software

1. The historical trend data of FoxView software appears shifted by one hour when
viewed from Daylight Savings Time (DST) and when the system is in standard time.
Data does not appear shifted when viewed from standard time. When the system is in
DST, data does not appear shifted when viewed from DST. (CAR:
1140773/1227049)
2. FoxView software may crash when a user erroneously creates a substitution list that
calls itself instead of a display or another sub file. (CAR: 1220459)
3. When the pointer is moved beyond the visible Y-axis of the FoxView software trends
area, the right-most data is displayed instead of the left-most data. (CAR: 1224860)
4. The message bar on the FoxView software window is moved to the second row even
when there is space available and the window is not resized. (CAR: 1238489)
5. When displays configured with I/A fonts are loaded, FoxView software leaks GDI
objects and may become unresponsive or crash over a period of time. This problem
may happen on FoxView/FoxDraw software versions 10.4.1 to pre-10.4.3. (CAR:
1241490)
6. FoxView software trends take a longer time to load when the pens are configured with
empty user variables. (CAR: 1243916)
7. FoxView software becomes unresponsive when the History Start/Stop dialog box is
opened from a maximized trend overlay. (CAR: 1244327)
8. FoxView software sets the value of the env variable incorrectly when a customer
environment (from opt/customer/env) is loaded. (CAR: 1255765)
9. The relative pick feature does not work consistently in FoxView software.
(CAR: 1270806)

B.2 FoxDraw Software

1. When a converted Display Manager trend is opened in FoxDraw software, the
engineering units of the pen are converted to percentages instead of being retained as
they were. See “Retaining Configured Engineering Units of the Display Manager
Trends in FoxView Software” on page 13. (CAR: 1246311)

41
B0700SN – Rev G Appendix B. Problems Resolved in v10.4.3

2. When a customer creates or modifies a new display in FoxDraw software 10.4.1 and
selects the Save as 9.x option, the display generated does not work in
FoxDraw software 9.0.4. See “10x to 9x Conversion” on page 31. (CAR: 1261992)
3. When the Wingdings font style is selected in the Attributes window of the
FoxDraw software, it is not displayed properly. It is not displayed properly in FoxView
software as well. (CAR: 1269588)

42
Appendix C. Problems Resolved in
v10.4.2
This appendix lists the problems resolved for FoxView/FoxDraw software version 10.4.2.

C.1 FoxView Software

1. If the value of OM_NUM_OBJECT is greater than 40000, the On-Line Trend Con-
figurator cannot be opened more than once. (CAR: 1014171)
2. Operators using remote services to log in using the remote ia user account often fail to
connect to a session. Ghost lists occasionally were left during very busy FoxView
remote sessions. All lists have been closed on session disconnect/end. (CAR:
1161108)
3. If the size of the title bar is set to 21 in widescreen resolution and the taskbar is hid-
den, some fonts are resized even if the window is not resized. For more information
see the user note, Text Sizing, Resizing and Fonts on page 23. (CAR: 1174591)
4. XY Plot does not update automatically and needs to be refreshed to view the new
coordinates. (CAR: 1188869)
5. Displays created with FoxDraw software versions prior to v10.3 and opened in
FoxView/FoxDraw software versions 10.3 and greater may possibly be missing line
segments. Contact Global Customer Support for QF 1214147. (CAR: 1214147)
6. FoxView/FoxDraw software could not be configured to display Russian text. Contact
Global Customer Support if assistance is needed to configure dual language support.
(CAR: 1215776)
7. FoxView software may crash when incorrect dmcmd command lines are assigned to
display bar buttons in .dbr files. (CAR: 1216566)
8. FoxDraw software prompts the user to convert a graphic to widescreen format even
though the graphic is already a widescreen graphic. (CAR: 1217811)
9. If a printer is named LP00, it is not displayed in the OAJ field of the FoxView status
bar. Fix FoxView software to show printers named LP00. (CAR: 1220855)
10. Numerical entry into .SPT and .OUT on user-built substitution faceplates takes user
entry correctly, but when the user attempts to read back the entries the rightmost
number or character is dropped. (CAR: 1221213)
11. Foxboro default environment of FoxView/FoxDraw software 10.3 and later behave
differently when compared to versions prior to 10.3 due to enhanced security features.
For more information, refer to the user note on page 30. (CAR: 1221385)
12. Converting FoxView displays from FoxView v10.2.1 to FoxView v9.03/v9.04 results
in File Read error. (CAR: 1225450)

43
B0700SN – Rev G Appendix C. Problems Resolved in v10.4.2

13. FoxView software may crash if a half screen trend is configured with user variable
picks with four $ variables for four different pens. (CAR: 1232229, 1235141)
14. If you edit and save a library object with profile in FoxDraw software, the library ele-
ment gets corrupted and reference to this element causes FoxView software to crash.
(CAR: 1237035)
15. Conversion of a display file to a widescreen monitor (WSM) display fails if object
names include an object type with a numeric character. For example, if a line object is
named myline1, WSM conversion fails because fdf_wsmfdf.exe is not able to interpret
the object data correctly. (CAR: 1237858)

C.2 FoxDraw Software

1. If a ramp value button is configured with more than one action item with the same
command, FoxDraw software may crash on save. Revise FoxDraw software to only use
and save the first configured action. (CAR: 1217599)

44
Appendix D. Problems Resolved in
v10.4.1
This appendix lists the problems resolved for FoxView/FoxDraw software version 10.4.1.

D.1 FoxView Software

1. When using the dmcmd setb command to set a bit in a PAKOUT the command will
clear a bit but will not set a bit. (CAR:1008639)
2. DM graphics conversion (pdf to fdf ) to FoxView software doesn’t convert poly lines
correctly. Fix conversion utility for poly lines. (CAR:1018947)
3. FoxView software only supports the standard pre-configured pathname
(/opt/fox/env). Allow support for custom environment pathnames. (CAR: 1066384)
4. Converting DM graphics (pdf to fdf ) to FoxView software may misalign and distort
some text. (CAR:1068013)
5. Selecting the A/M button on the PIDA faceplate shows that the $PID_FP function is
not working correctly. If the block is in manual, the SPT should highlight.
(CAR:1081395)
6. Incorrect use of DM commands could result in a FoxView software crash. Enhance
DM command error handling to generate an error message. (CAR:1110676)
7. Sometimes displays take a very long time to connect to shared variables. Cause deter-
mined to be that the profplot.dll needs to build against 32-bit time. (CAR:1119672)
8. Using relative pick and entering text in a customized ramp button does not work cor-
rectly. (CAR:1124227)
9. The XY Plot blinks/refreshes per the scan rate. It should not, it should only update
data and the rest of the graph should not flash. (CAR:1145893)
10. Operator Action Journal (OAJ) messages are truncated to 32 characters when printed
to a dot matrix serial printer. The entire messages should be printed. (CAR:1161296)
11. Converting an .m1 file to a .g file using the command line tool returns the error ‘Not
a .g file”. Resolution is to correct the sgm1 and sm1g .ksh scripts. (CAR:1167319)
12. The ‘More’ button on the FoxView Usage display does not become visible when there
are more than 16 DMs configured. (CAR:1168523)
13. When a library symbol is used to open a display using aliases, the display file may be
deleted when FoxView software tries to optimize the display. (CAR:1169324,
1189115)
14. When the Online Trend Configurator is open and an overlay is then made moveable,
the trend also becomes moveable. The trend should remain unmovable.
(CAR:1175662)
15. When multiple overlays are opened that are both ‘moveable’ and ‘sticky’ and the focus
is changed from FoxView software to another application and then back to FoxView

45
B0700SN – Rev G Appendix D. Problems Resolved in v10.4.1

software, the overlay that was on top and had focus no longer does. The last overlay
opened should retain focus. (CAR:1177194)
16. When converting displays using the pdf to fdf utility, text objects on trends are not
aligned properly nor are the correct descriptions displayed. (CAR:1183033)
17. The FoxView Usage display does not show active thin clients. (CAR:1184269)
18. FoxView software only uses the Windows-defined mouse cursor. Users may now
define another cursor in the init.user file using FV_CURSOR for assignment. If the
specified cursor file exists, FoxView software will use that cursor, otherwise it will use
the default cursor. See “Defining a Cursor” on page 15. (CAR:1187230)
19. When a moveable overlay is moved, it may be unintentionally resized as well as reposi-
tioned. This may happen more often on 16:9 screens with overlays whose width is
greater than its height. (CAR:1187277, 1208684)
20. When the value of II01 is a negative number FoxView displays an unsigned integer,
e.g. -1 is shown as 65535. The parameter should be a signed integer from -32768 to
32767. (CAR:1188577)
21. The MAIMeas object may cause a crash if the measurement indication is connected to
a value that changes. Need changes made to move path percent and index in the gms
functions. (CAR:1192718)
22. When an operator uses alt + tab to cycle through windows, show desktop can also be
selected and this will minimize FoxView software. If the FoxView window is mini-
mized on a station without privileges, it cannot be restored. Allow restore of FoxView
software. (CAR:1193547)
23. It is possible for FoxView software to crash if dmexit is configured in an open script.
This is corrected in this release. (CAR:1194212)
24. There is currently no method to configure a font for FoxView scrolling text windows.
The Notepad configured font is used. This presents a configuration problem on secu-
rity enhanced installations. See “Scroll Region Fonts” on page 15. (CAR:1194523)

D.2 FoxDraw Software

1. When using global change in FoxDraw software, the tagname is only updated in the
Update tab, not in the Action tab. (CAR:1081640)
2. The FoxDraw drawing area (background object) is no longer fixed. The drawing area
should be non selectable and unmovable. (CAR:1175889)

D.3 FoxSelect Software

1. FoxSelect crashed when querying an FCP270 with a recent download. Problem deter-
mined to be a buffer overrun when reading packet information. (CAR:1144114)

D.4 Display files

1. Please reference QF1156739 for additional display file fixes that may be installed
along with FoxView/FoxDraw software 10.4.1.

46
Appendix E. Problems Resolved in
v10.4
This appendix lists the problems resolved for FoxView/FoxDraw software version 10.4.

E.1 FoxView Software

1. Opening an overlay with a start position of outside of the drawing area may cause
FoxView software to crash. (CAR:1015939 and CAR:1128117)
2. Engineering Units are not shown on Trends for RIN block. (CAR:1098391)
3. Setting a password on the Initial environment may cause FoxView software to close
unexpectedly. (CAR:1123591 and CAR:1131580)
4. If FoxView software cannot find a custom initial display it may crash. Modify Fox-
View software so that if a custom Initial display cannot be found, the installed default
initial display will be used. (CAR:1125041/ CAR:1141183)
5. FoxView display files that do not contain any OM update points are being optimized
(i.e. a write action is done to these files) every time they are being closed. This is a
unnecessary action because there is nothing to optimize. (CAR:1142098/
CAR:1142099)

E.2 FoxDraw Software

1. When changing a user-created convention in FoxDraw software, the changes are not
updated in library symbols after restart of FoxView software. (CAR:1094875)
2. When changing a visibility Graphics attribute, click Apply and then close Configure
Object dialog with the cross (upper right); but the display cannot be saved. Also no
other selection can be made in FoxDraw software. To fix this, open the Configure
Objects display again and close this via Cancel or OK button. Then the display can be
saved again and also another selection can be made. (CAR:1116694)
3. When Control Values is used in FoxDraw software to retrieve high and low scale val-
ues for the RIN block, they are not retrieved correctly. (CAR:1125379)
4. FoxDraw software cannot retrieve CP data for the Meas param of the RIN block.
(CAR:1127533)
5. In FoxDraw software, when trying to add/assign action to a item, under the Display
Command Builder the wrtfile command does not exist. When this command is typed
manually, the error 'File wrtfile /usr/test.txt lncr80w80o0i0l test data does not exist' is
displayed. (CAR:1134201)

47
B0700SN – Rev G Appendix E. Problems Resolved in v10.4

E.3 FoxSelect Software

1. When generating Inhibit reports, the alignment of the report is not correct.
(CAR:1112741)

48
Index
B
Backing up files 7
Blinking colors 19

C
Compatibility
displays 3, 28
library objects 28
Converting
displays 26, 28
library objects 28

D
DConvert 31
DEdit
known problems 18
user notes 30
Disk space required 33
Display and library objects
naming 21
Display Manager software
migrating to FoxView software 33
Displays
compatibility 28
converting 26, 28
file compatibility 3
moving to older workstations 3

E
Edge widths and visibility 21
Enhancements
FoxView/FoxDraw V10.1 15

F
fdf_to_g and g_to_fdf conversion utilities 26
Filenames 27
Fill levels 27
Flashing displays 20
Fonts
exact mapping 37
FoxDraw
introduction 1

49
B0700SN – Rev G Index

known problems 18
user notes 24
FoxSelect
connecting to a station 30
Refresh All 30
user notes 30
FoxView
capabilities 33
introduction 1
known problems 17
new features 15
performance 36
user notes 19

G
Global Customer Support viii

H
Hard coded ranges 21

I
I/A Series software versions vii
Installation
files to back up 7
FoxView/FoxDraw 8
Windows NT/XP platforms without I/A Series software (FoxDraw) 9
Introduction 1

K
Known problems 17

L
Large displays 30
Library objects
compatibility 28
moving to older workstations 3
Linked library objects in displays 31

M
Menu entries
custom 28
Migration
Display Manager software to FoxView software 33
Mouse/keyboard focus 20

50
Index B0700SN – Rev G

N
Naming display and library objects 21
New features
FoxView software 15
trends 15
usage display 15
X/Y plots 15

O
On-line trend configurator, advanced screen 21

P
Pickable areas within faceplates 20
Platforms
FoxDraw 1
FoxView 1
operating FoxDraw and FoxView 37
PLB 21
Problems
known in this software release 17

R
Ramp operations 26
Relative picks 19
Requirements
disk space 33
Reserved words 26

S
Software
installing 8
uninstalling 10
Software installation, see Installation
Supported platforms 1
Supported software vii

T
Transparently filled objects 21, 27, 28
Trend features 15

U
Uninstalling 10
Usage display 15
User notes 19
FoxDraw 24
FoxDraw DEdit 30

51
B0700SN – Rev G Index

FoxSelect 30
FoxView 19

V
Validate points in reports option 30

W
Windows resources 20

X
X/Y plots 15

52
Index B0700SN – Rev G

53
Invensys Systems, Inc.
38 Neponset Avenue
Foxborough, MA 02035-2037
United States of America
www.schneider-electric.com

Global Customer Support

Inside U.S.: 1-866-746-6477
Outside U.S.: 1-508-549-2424
Website: https://support.ips.invensys.com