B.2 FoxDraw Software
1. When multiple rectangles are selected so that graphical attributes like Fill and Edge colors can be changed, the color changes only in the first rectangle that is selected. All other rectangles that were selected retain their original colors. (CAR 1009959)
2. “|Rxx” is created by DEdit for each successive dump and upload. (CAR 1010043) 3. FoxDraw 9.0.2 window that starts in a small window (about 1/4) cannot be enlarged
into a full screen easily. Previously used FoxDraw 99.x keeps the window parameters of the last opened window. (CAR 1009505)
4. Converting faceplates in .g , the field where there are "<BLKNAME>___" e <CMP-NAME>___" ends with an additional space character. Example: With space "<CMP-NAME>___ " and without space "<CMP"<CMP-NAME>___". With the space, FoxDraw does not substitute the text with the real compound name. (CAR 1010216)
B.3 FoxSelect Software
1. On a CP with 200 series FBMs attached and ECBs configured, select blocks in man-ual and send to file or print. When requesting Process Summary Report from Fox-View for blocks in Manual, all 200 Series ECBs are in the list but you cannot place an ECB in manual. (CAR 1007734)
2. When running the FoxSelect report ''Blocks with alarms inhibited'', the report excludes CIN blocks that only have the BADIO alarm enabled (BA0=1), but have the BADIO alarm inhibited. If the State alarm is enabled along with the BADIO alarm, then the CIN block is included in the report if INHIB=1. Since the BADIO alarm is a valid alarm for a CIN block, the CIN block should appear in the ''Blocks with alarms inhibited'' report, regardless of whether this is the only alarm enabled for this block. (CAR 1010166, CAR 1010159)
Appendix C. Problems Resolved in V10.2
This chapter describes problems resolved in the V10.2 release of FoxView and FoxDraw software.
C.1 FoxView Software
The following problems have been resolved in V10.2 of FoxView software:
1. The ''-range one'' option of the TREND display manager command does function properly. We can execute ''trend -g <trend name> -line 1 -range one'' to set the one shot autoscale for the pen one.(CAR 1007889)
2. FoxView used to crash when entering in an out of range value into an AIN faceplate for MEAS parameter. Now the problem has been fixed.(CAR 1007865)
3. When the trend commands with -perm is used in a dm command assigned to a but-ton, the units on assigned trend lines are dropped and the display changes are not saved permanently. This problem has been fixed.(CAR 1008418, CAR 1008472) 4. Now Text object can be configured with a text file, which has more than 245
charac-ters and work without any issues, when the Null terminated property is selected.
(CAR 1008244)
5. Now OOS (Object Out of Service) indication works for grouped objects.
(CAR 1008572)
6. In FoxView V10.1, when configuring text object to show a compound name or block name, Foxboro have used the following standards: < CMPNAME > ______ <
BLKNAME > ______. Unfortunately, when preceded by triangular brackets, the underscore is no longer recognized as a character. This problem has been fixed.
(CAR 1008593)(CAR 1008385)
7. We have a ''select trend'' capability that works with I/A v8.1 and FoxView v10.0.1 and v10.0.2 that does not work properly with I/A v8.2 and FoxView v10.1. Now the problem has been fixed. (CAR 1009072)
8. If a library object is configured with real time values that are coming from CP when ever CP goes offline and when it comes back online, library object was not updating by itself. The display has to be refreshed to see the correct status. This problem has been fixed. (CAR 1008175)
9. There is a function on the profile plot that allows the user to click on the profile plot to extract the profile values. This function does not work if the keyboard cap locks is ON. This problem has been fixed. (CAR 1008252)
10. Previously when historian was configured on DELL server and if the user configures the historian name for any trend on the detail display, it was not showing the histo-rian values properly. This problem has been fixed. (CAR 1008435)
11. When customer fixed trends are configured to autoscale using FoxDraw and are flushed to FoxView, some of the trends are appearing with the same high and low scale resulting in a flat lined trend. The user is not able to observe small fluctuations of real time values. This problem has been fixed and the user can observe the real time values with small variations. (CAR 1008570)
12. The Hi, Lo scale validation is present on OLTC. The user can configure any object with Hi, Lo scales and proper validation. (CAR 1008697)
13. When ever the user made modifications to the environment files and restarted Fox-View, FoxView used to appear in different size. This problem has been fixed. (CAR 1008497)
14. The DM command wrtfile executes properly and the data is written to file, if any object is configured with the command. (CAR 1008833)
15. The V8.2 OM does not allow the setting of OM_NUM_OBJECTS above 70,000.
Previous releases supported a setting of more than 140,000. When
OM_NUM_OBJECTS setting is changed to 90,000, FoxView will not appear after AW computer is rebooted and the following error message is displayed:
“FoxView Not available”. This problem has been fixed. (CAR 1008859)
16. There is a difference between the Profile Plot element in Display Manager and the Profile Plot element of FoxView. Originally in DM, the Profile Plot display does not show a line or a bar, when the data is a NAN (Not-a- Number). In FV, a NAN seems to be considered like a very high value because the line or the bar for those particular zones are shown at the high scale. This problem has been fixed. (CAR 1009281) 17. When the display was optimized before and then is called up deoptimized. This
prob-lem has been fixed. (CAR 1008989)
18. The string comes from C1:B1.P1 in CP1 and the trigger from C2:B2.P2 in CP2.
When the user changes the C1:B1.P1 in CP2 to C2:B2.P2 in CP1, it takes about 15 seconds before the string on FV-display on AW51F gets updated. This problem has been fixed. (CAR 1009159)
C.2 FoxDraw Software
1. After converting displays from FDF to G format, and editing the G files to fix direc-tory changes, and converting back to FDF files, the displays all behave like overlays.
Now the issue has been fixed. Base display files appear as base display and overlay files appear as overlays.(CAR 1008075)
2. FoxDraw Convention stores the delta value. Whatever you configure, the moment you close and re-open the dialog, delta does not show-up as 1, delta value keeps its value. (CAR 1008688)
C.3 FoxSelect Software
1. On any Windows XP AW70, certain file names used to save the ''blocks with alarms inhibited'' FoxSelect report when trying to print them causes the FoxSelect.exe pro-cess to utilize about 100% CPU usage and does not print the report. This problem has been fixed. Now the user can print reports which are having longer file names.
(CAR 1008523)
2. FoxSelect custom reports Blocks with alarms Inhibited. This report does not show
blocks of type AOUT and COUT even if their alarms are inhibited. This problem has been fixed. (CAR 1006060)
C.4 DConvert
1. When ever DM display converts to FoxView display, previously objects were losing its protection. This problem has been fixed and now the conversion happens properly.
(CAR 1008297)
2. When ever DM display converts to FoxView display, previously it was not converting text configuration as text, numeric configuration as numeric. This problem has been fixed and now the conversion happens properly. (CAR 1005495)
Appendix D. Problems Resolved in V10.1
This chapter describes problems resolved in the V10.1 release of FoxView and FoxDraw software.
D.1 FoxView Software
The following problems have been resolved in V10.1 of FoxView software:
1. FoxView leaves OM lists opened problem has been corrected now on server OM lists clears the entries of the client when the client session is closed. (CAR 1005970, CAR 1006046)
2. Sometimes displays created using a Windows NT workstation would not work on a Windows XP station. This problem has been corrected. (CAR 2000932)
3. The msglin display command can be configured to work for the close display com-mand script. Previously, the msglin command did not work for the close display command script. (CAR 1006146)
4. The functionality of the “@” Display Manager variable has been fixed. Now, the @ symbol resolves more than one string and works as per the display engineering document.
5. FoxView software now supports 32 instances for Windows Server 2003. The FoxView Usage Display has been enhanced to reflect the usage of 32 FoxView instances.
6. Now trends draw correctly for the historized points with static historical data.
(CAR 1006710, CAR 1007174)
7. FoxView software On-line Trend Configurator window appears on the second head of a dual-headed display if the major portion of the FoxView display appears on the second head. (CAR 1006711, CAR 1007134)
8. Sometimes when calling display files created with data/buttons/objects makes FoxView software hang. This problem has been corrected; the displays now appear normally without any missing objects. (CAR 1006922)
9. The FoxView trend command now removes the configured pen without changing the decimal places configured for remaining pens for the trend. (CAR 1006947)
10. If you run the change environment script using the command line, the Change Envi-ronment dialog box now appears correctly and prompts for a password.
(CAR 1006323)
11. Background text objects appear per the visibility passive dynamic connect variable state. (CAR 1007133)
12. Text objects appear per their visibility dynamic set using omset. (CAR 1005265) 13. Using the trend command, you can remove only the first pen without removing the
Y-scales and decimal places. (CAR 1006947, CAR 1007470)
14. If you configure a trend with pens without engineering units using FoxDraw software and flush the trend in FoxView software, the engineering units configured in the Inte-grated Control Configurator (ICC) is picked up and displayed in FoxView software.
(CAR 1007182)
15. Printscreen works beyond 40 continuous prints without printing any blank pages.
(CAR 1007534)
D.2 FoxSelect Software
The following problem has been resolved in V10.1 of FoxSelect software:
1. The \opt\fox\wp\foxselect -psr -cfg <reportname> -out <reportfile> com-mand in V10.0.1 of FoxView/FoxDraw software did not list C:B.P details. Now the report generates with the correct compound and block details. (CAR 1006867) 2. A new option, Save and Refresh from File, has been included in the Options
menu of FoxSelect software. Whenever the option is selected, FoxSelect software saves all compound and block data into a .dat file. Whenever the application is restarted, it fetches this information and populates the tree control of the Station view and the list control of the Block view. (CAR 1006245)
D.3 FoxDraw Software
The following problems have been resolved in V10.1 of FoxDraw software:
1. Previous versions of FoxView and FoxDraw software were not correctly converting the text contents of Display Manager displays to FoxView displays. This problem has been corrected; the tag name now appears with Compound:Block.Parameter after conversion.
2. The new dmcmd command dmcmd clearpick has been added to the display com-mand builder. This option clears the focus of the selected object. This option was not present in V9.0.1 FoxView and FoxDraw software. (CAR 1006025, CAR 1006728) 3. The filename length limitation is removed from FoxDraw software. Now FoxDraw
software accepts filenames of more than 20 characters. (CAR 1007302)
4. FoxView display files can now be saved starting with a number in IACC embedded FoxDraw. Previously, this option would crash IACC. This problem has been fixed.
(CAR 1007018)
5. Stand-alone FoxDraw software can now be re-installed on the C: drive without changing the environment variables if the software has been previously installed on a drive other than the C: drive and then uninstalled.
6. FoxDraw software now throws a warning message if you attempt to open a file using the Most recently Used list and the file is already open in another FoxDraw instance.
7. In FoxDraw software, the Retain case option has been added to the General tab of the User Options window to work with lower case AOS tag parameters.
(CAR 1005978)
8. FoxDraw software’s primitive objects can be properly configured in library objects for its graphic attributes.
9. FoxDraw software now allows the msglin command to be configured for customer
faceplates.
10. FoxDraw software now allows you to configure the duration up to 600 days for a trend. V9.0.1 allowed up to 7 days.
11. The Multi-create option is now not applicable for comment objects in FoxDraw soft-ware. Older versions of FoxDraw software would hang when using the multi-create option with comment objects in FoxDraw software.