InTouch 7.11 P07

Материал из archestra.info
Перейти к: навигация, поиск



InTouch 7.11® Patch 07 ReadMe

This ReadMe file describes the defects fixed in this patch and known issues.


 

Before installing this patch, it is strongly recommended that you exit all FactorySuite® programs, including executable (.exe) files and services.

This InTouch 7.11 Patch 07 Build has primarily been tested on:

1.      Windows XP Professional with SP2 and MDAC 2.81

2.      Windows 2000 Professional with SP4 and MDAC 2.7 SP1

3.      Windows NT 4.0 SP6a and MDAC 2.60

4.      Internet Explorer 6.0 SP1

*  NetDDE is not supported on Windows XP SP2, Windows 2003 and later operating systems.

Microsoft Windows XP SP2 introduces several security technologies including disabled NetDDE, enhanced Windows firewall, and a reduced RPC attack surface. These enhancements affect the uses of NetDDE, WWLogger, and SuiteLink protocols in InTouch.

If InTouch needs to be operated on Windows XP SP2, you should contact your local Wonderware Distributor or download the OS Configuration Utility from the Wonderware Technical Support web site (Wonderware Technical Support). This utility opens specific ports that enable NetDDE and adds Wonderware SuiteLink and Wonderware Logger to the firewall exception list.

InTouch will not work properly on a Windows XP SP2 computer if you do not run the OS Configuration Utility after installation of InTouch.


Resolved Issues

The following defects were fixed for this patch release. Click on the defect number for a more detailed description of the problem.

L00006191 Duplicate shortcut keys in SQL Access Manager/Table Template Configuration dialog box in the German version of InTouch 7.11.

L00009846 3Dtext and text object in Japanese version of InTouch 7.11 P03 (double-byte code) is displayed rotated or using incorrect font.

L00011536 In the French version of InTouch 7.11, an item cannot be added to the Symbol Factory object library.

L00012425 AlarmDBView Control takes a long time to get populated with data if database contains a large number of records.

L00014196 The "Invalid floating pt value" error message box is not modal (is hidden).

L00014738 SuperTags are not shown in alphabetical order, but are in the order in which they were created.

L00014778 Logger shows Mutex errors after a few days of running InControl.

L00015140 Wizard is not retaining animation links.

L00015163 "Not enough space for string - new name too long?" error message is displayed when you attempt to convert an InTouch application to another screen resolution.

L00016049 There is a difference in the text display block between single and double byte characters. Double byte character fields are much wider that the text included.

L00016475 Inconsistent message dialog boxes are displayed when using illegal characters along with hex numbers and/or tagnames in a script.

L00016753 Unexpected results occur when setting width of pen in 16-pen trend during design time.

L00016921 Fast switching from WindowMaker to WindowViewer causes the following error messages in WWLogger:
AlarmBuf /!CBThrd_Dispatch_Timer1Sec PostThreadMessage failed - Error: (1444) - Invalid thread identifier.
AlarmBuf /!PostThreadMessage(0) (thread-id=0x724) failed (AlmMgr=0x710,0x648,0x724).

L00016991 Fonts display is 'blotchy' in WindowMaker when using 'Smooth edges of screen fonts' setting. Fonts in WindowViewer are displayed OK.

L00017565 Alarm Purge/Archive shuts down when user clicks OK.

L00017621 Tag assignment in 16-pen window results in "Tagname.x is in an out-of-date format or corrupted" and the application cannot be opened again.

L00017790 The Edit Custom Color dialog box, when opened from the 16-pen trend control dialog box, causes WindowMaker to crash.

L00017809 X or Y location of window changes when reducing the width or height of the window manually and without saving and closing.

L00017828 Cannot change a double byte font in AlarmDBView control.

L00017865 Unselecting all radio button settings in Discrete Value Pushbutton can crash WindowViewer.

L00017867 In the French version of InTouch, the Set/Reset Display button has incorrect translation for Open.

L00017877 When a new application and a new window are created, printing the window disables WindowMaker after the printout.

L00017904 It is possible to clear all radio buttons (unchecked) in the animation links, such as Object Height/Width and the Percent Fills, which causes WindowMaker to crash.

L00017934 In the 16 Pen Trend environment, switching between WindowMaker and WindowViewer and then clicking on the scooter (or F2) will increase its size.

L00017936 When creating a new WWALMDB, Alarm DB Logger does not set any permissions for WWUser / WWPower / WWAdmin users for the *Ex views; hence those accounts cannot be used for alarm retrieval using Alarm DB View.

L00017944 In the 16 Pen Trend environment, Pen Trend goes blank in the run-time if trend is stopped (Stop button) while the Configuration dialog box is opened.

L00017975 In the French version of InTouch, the All and Historical options on the Query tab in Alarm DB Logger Manager are not translated.

L00017979 In the Japanese version of InTouch, creating an application path with certain Japanese characters and deleting the application from the list causes the InTouch Application Manager to not find the application.

L00017982 In the Japanese version of InTouch, the All and Historical options on the Query tab in Alarm DB Logger Manager are not translated.

L00017994 Alarm DB Logger Manager hangs if the Alarm database was not created and you click Start.

L00017999 Not able to log alarms as user wwPower in the Alarm DB Logger.

L00018231 In Japanese version of InTouch, there are corrupted fonts in WindowMaker dialog boxes using Japanese local settings.

L00018283 Alarm DB Logger will not function if there are more than 16 lines of queries in its Alarm Query configuration.

L00018284 The sharing of the Wonderware license folder when InTouch is started is a security concern. Provide the ability to halt the sharing of this folder.

L00018294 After installation of InTouch 7.11 Patch 06, Alarm DB Logger no longer logged alarms to the database.

L00018335 In the French, German, and Japanese versions of InTouch, the word “None” in the following error message is translated: "Change Password for Operator None".

L00018519 Enhancement to the 16-pen trend functionality to eliminate occasional double thick line.

L00018566 WindowViewer crashes on initialization of a HistData wizard.

L00018756 The Cross Reference utility’s Save As function does not write the tag link locations to the CSV file as documented in the InTouch Users Guide.

L00018790 In the Japanese version of InTouch, the color fill animation link is the opposite of what is true.

L00018838 Use of the DialogValueEntry or DialogStringEntry causes a crash when users’ IDEA script function is only used in Application On Shutdown script.

L00018906 In Historical trending mode, 16-pen trend, the start time of the trend is the current time. This problem results in an empty future trend.

L00019008 In the Japanese version of InTouch, the error "can not open tagname.x" is displayed after importing windows containing the password wizard.

L00019096 Changing the font properties does not always provide the same results.

L00019104 The Log file *.ALG does not include the Alarm Comment when the ACK or .ACK was used, or when the almAck comment was blank (empty string).

L00019196 Unreadable characters displayed in the keypad (a dash "-" looks the same as period ".").

L00019283 No longer able to use the AlarmDBView ActiveX in Visual Basic after installation of InTouch Patch 06.

L00019352 Using local variables in GetNodeName() will get error message dialog "Must have writeable message variable for this argument to GetNodeName".

L00019410 The Hardware/Software flow control settings are not preserved in the Alarm Printer.

L00019431 WWRequest does not function after a failed connection.

L00019440 Failed to create view in wwAlmDB by using AlterWWALMDB.exe.

L00019460 Crash related to special characters in the MSSQL DB; no crash if unused tags are deleted from the InTouch application.

L00019569 After disabling and enabling InSQL, the analog tag does not update. InSQL shows Null until the tag changes value.

L00019699 During UNACK_RTN events, when ACKed on a client of a Hot Backup pair, the ACK is not sent to the backup computer.

L00020058 DAO querying a Hot Backup pair does not detect that WindowViewer is shutdown on the primary provider when the Alarm DB Logger is also running on the primary provider.

L00020170 AlterWWALMDB.EXE in InTouch Patch 06 fails when used with Microsoft SQL Server 7.0 SP3. Error message is the following: “Failed to Create v_AlarmEventHistoryEx1 view”. This function works OK on SQL Server 2000 and MSDE.

L00020214 Tagname Dictionary allows "Ctrl+Enter" to be typed in the Alarm Comment field of Discrete tags, which results in an embedded CRLF that causes problems for DBDump/DBLoad.

L00020312 Alarm DB Restore stops restoring when it encounters comments in the comment file that contain a comma.

L00020460 WWDlg_ScriptEdit returns a modified script when the user clicks Cancel. There is no way to know whether the user clicks OK or Cancel to close the Script Editor.

L00020552 Unable to write to the ROCpct dot field from an IDEA application.

L00020559 Windows Textbox only displays 130 characters of a 131-character-long tag.

L00020610 A gap is displayed on the right side of a historical trend during the fall back time change in October for Greenwich time zone when it is set to auto adjust for time change.

L00020697 Enhancement request: New feature to be able to bypass the creation of placeholders (based on the existence of tags in the tagname dictionary) when windows and scripts are imported from one application to another.

L00020741 The following error message is displayed on alarm consumer’s node after a provider stop/start: "/UNKNOWN /!SmartHeap Error Code 14, MEM_BAD_POINTER 00140188, in pool 0 /UNKNOWN /!memory corruption(4013002B) val=0x40 -> AlarmConsumer must restart".

L00020742 Screen display flickers when halo is bigger than screen resolution and the mouse is moved over push buttons.

L00020788 If the password of the SPCPro database user is more than 4 characters long, an SPCPro application or HeapShareFree error message is displayed when WindowMaker is started.

L00020819 When browsing tags during historical trend pen assignment, the entire remote tagname dictionary is displayed instead of only the history tags.

L00021400 If an application is developed with a later version of InTouch, the Application Manager states the version as 'Old'.

L00021729 The alarm system registers Rate of Change alarm based on a previous setpoint at startup when Retentive Parameters is selected for a tag.

L00022064 Cross Reference utility crashes WindowMaker if specific Recipe.csv file is in the application directory.

L00022250 Not enough disk space error is displayed when trying to install InTouch Patch 5a.

L00022365 In the French version of InTouch, the Set/Reset Display button has incorrect translation for "Open".

L00022618 Incorrect info on the SPCPro About box.

L00022760 Alarm entries are corrupted when acknowledged if the AlarmUserDefStr is set in the application on a start script.

L00022771 An Alarm Tree ActiveX object displays the following error message when calling scripts. "Error processing AlarmTree1.UpdateView on method call (execute). Exception 0x800A005B: Object variable or With block variable not set".

L00022981 Tags Alarm 'Disabled' properties (for example, AlarmLoEnabled and .AlarmHiEnabled) are not being retained if 'Update Use Counts' is used with WindowMaker.

L00023092 60k license is not allowing over 61,405 RTR (and local tags, total).

L00024256 In the Tagname Dictionary (SuperTags), the member list does not work after clicking Select then Cancel.

L00024292 A /View Unknown Opcode in GetSValue popup message is displayed from QuickFunction.

L00024336 Text Object's Font size does not save correctly when modifications are done with the mouse.

L00024601 The AlterWWALMDB.exe utility does not use the "top max records" setting in the dialog for the first run, but rather uses the default 1000 records.

L00025147 The InTouch Keyboard is shown even when the check box is cleared.

L00025585 Unable to connect InSQL 8.0 or InSQL 7.1 to InTouch 7.11 when InTouch is running on a Windows XP SP2 computer.

L00025933 If there are a large number of alarms in the database, InTouch will only display the oldest alarms in the AlmDbViewCtrl and display $NewAlarm for the rest.

L00026422 The AlterWWALMDB.exe utility crashes after it fails to "Test Connection".

L00026453 Uninstall does not remove the /Programs/Wonderware FactorySuite/InTouch/Alarm DB Alter shortcut.

L00026454 Unable to use the AlmDbViewCtrl for event history.

L00026587 In the Japanese version of InTouch, the AlmDbViewCtrl property dialog box’s "Refresh", "sort", and "sort" check boxes should be “Refresh", "Sort", and "Reset”.

L00026588 In the Japanese version of InTouch, Display Modes of the AlmDbViewCtrl property dialog box are user editable.

L00026879 The status bar on AlmDbViewCtrl displays incorrect information: "Displaying 1 thru 2000 of 1000 records".

L00027371 In a workgroup environment, WindowViewer crashes after switching users on a Windows XP computer.

L00027697 In the Simplified Chinese version of InTouch, there are untranslated strings in Alarm DB View and Alarm DB logger.

L00027800 Read-only I/O tags are writeable using Indirect Tags.

L00028153 When you open an application created in an English version of InTouch in a Japanese WindowMaker, some characters' font size changes.

L00028170 In AlmDbViewCtrl of the Simplified Chinese version of InTouch, the default font does not show.

L00028309 Attempting to display historical data in a trend when the selected range spans a Daylight Savings Time transition loses data.

L00028900 Terminal Services client connects to a server and runs WindowViewer in a different screen resolution than that of the server application, and the font size is not adjusted to the client environment when set to Japanese as its default language or when using a Japanese OS.

L00028982 When InSQL data is set for Greenwich Mean Time and the trend is set to plot for one hour, two hours of data is shown during the Daylight Savings Time change.

L00029247 SPC Limits Wizard does not create tags and errors are logged to the Wonderware Logger after clicking on suggest and OK button.

Back to Top


Detailed Descriptions for Resolved Issues

L00006191 Duplicate shortcut keys in SQL Access Manager/Table Template Configuration dialog box in the German version of InTouch 7.11.

Problem:
In the German version of InTouch, the "Element
löschen" and "Länge" controls had the same keyboard shortcut (L). Keyboard shortcut “S” is now assigned to löschen.

Back to Resolved Issues

L00009846 3Dtext and text object in Japanese version of InTouch 7.11 P03 (double-byte code) is displayed rotated or using incorrect font.

Problem:
Times New Roman font is rotated 90 degrees, and Terminal font is incorrect.

Back to Resolved Issues

L00011536 In the French version of InTouch 7.11, an item cannot be added to the Symbol Factory object library.

Problem:
In previous versions of the Symbol Factory when used with a localized version of InTouch (e.g. French, German InTouch...), users could not add their own InTouch objects to the library. The user would receive the error message "You must first select an InTouch object" when trying to add an object, even though the object was, in fact, selected. This has been fixed.

Also, if a new library was created and then an item added, it succeeds but the object is blank in the library.

All INI file operations were modified to use the Registry instead. This allows the Symbol Factory to operate properly under Windows XP if a restricted-access user is logged on. Three new Registry entries and a help file for Symbol Factory were introduced in this patch. Symbol Factory help file was changed from WinHelp() to HtmlHelp(), so now the Symbol Factory uses SymFac.chm instead of SymFac.hlp. SymFac.chm is in the same folder as SymFac.dll.

Back to Resolved Issues

L00012425 AlarmDBView Control takes a long time to get populated with data if database contains a large number of records.

Problem:
If the WWALMDB has 200,000+ records in it, and you open the AlarmDBView Control to query the alarms from the last 5 minutes, it takes 110 to 180 seconds (2-3 minutes) to populate even if no records are returned. Running the same query from Query Analyzer also has the same delay. Delay is greatest when SQL Server is on another node.

Back to Resolved Issues

L00014196 The "Invalid floating pt value" error message box is not modal (is hidden).

Problem:
When entering an invalid floating point value (for example, entering a comma instead of decimal point in an input animation link), the error message window that is displayed may be hidden. If there is a popup type window covering the message, it remains hidden, waiting for the user to click OK. If the ALT TAB key combination is disabled, there is no way to access the error message.

Back to Resolved Issues

L00014738 SuperTags are not shown in alphabetical order, but are in the order in which they were created.

Problem:
When selecting tags for pens of Trend object, the SuperTags are not shown in alphabetical order, but are in the order in which they were created.

Back to Resolved Issues

L00014778 Logger shows Mutex errors after a few days of running InControl.

Problem:
Run InTouch application, InControl application, and IO Server in the same node. After 2 to 3 days, the following errors appear in the logger:

2003/05/01 09:47:44.450/-0240:0264/UNKNOWN /Unable to access stats memory (two timeouts on mutex)

2003/05/01 09:47:44.450/-0458:0454/UNKNOWN /Unable to access stats memory (two timeouts on mutex)

2003/05/01 09:47:45.452/-03BC:03EC/UNKNOWN /Unable to access stats memory (two timeouts on mutex)

The process value in the logger indicates that RTEngine, mbenet, and view all get the mutex errors. After the initial group of errors, RTengine reports Mutex errors continuously every couple of minutes. Restarting RTEngine causes the errors to stop.

Back to Resolved Issues

L00015140 Wizard is not retaining animation links

Problem:
A new object is placed by using the Place Wizard command. The Wizard Generator (for creating wizards) has a Visibility check box that links to a tag. The check box is cleared after breaking the wizard cell, double-clicking on Visibility, and then clicking on the Cancel button.

Back to Resolved Issues

L00015163 "Not enough space for string - new name too long?" error message is displayed when you attempt to convert an InTouch application to another screen resolution. 

Problem:
"Not enough space for string - new name too long?" error message is displayed when you attempt to convert an InTouch application that has a script longer than 32,000 characters to another screen resolution. The new maximum limit is 32,700 characters. For any script that has more than 32,700 characters, including spaces and line breaks (each line break = 2 characters), the script will be truncated after importing or conversion.

Back to Resolved Issues

L00016049 There is a difference in the text display block between single and double byte characters. Double byte character fields are much wider that the text included.

Problem:
A font display problem exists in Japanese version of InTouch. There is a difference in the text display block between single and double byte characters. Double byte character fields are much wider that the text included. Some Japanese fonts could not display all characters on window.

Back to Resolved Issues

L00016475 Inconsistent message dialog boxes are displayed when using illegal characters along with hex numbers and/or tagnames in a script.

Problem:
Inconsistent message dialog boxes are displayed when using illegal characters along with hex numbers and/or tagnames in a script.

Back to Resolved Issues

L00016753 Unexpected results occur when setting width of pen in 16-pen trend during design time.

Problem:
There were two different methods for setting the width of a pen on the 16-pen trend during design time. One method was in the upper gray area of the configuration window in the frame titled Current Pen. The second method was using a column along the right side of the grid with the pens, tags and other settings. When using the first method, you must select the Pen number in the Current Pen area, then its width, and then click Done to set the width of all the pens. Then, you must select the next pen in the configuration window. This methodology has changed to the following: at run-time, all pens will display at the width of their design time specifications and the widths can be changed using the dialog box and through any supported scripts functions.

Back to Resolved Issues

L00016921 Fast switching from WindowMaker to WindowViewer causes the following error messages in WWLogger:
AlarmBuf /!CBThrd_Dispatch_Timer1Sec PostThreadMessage failed - Error: (1444) - Invalid thread identifier.
AlarmBuf /!PostThreadMessage(0) (thread-id=0x724) failed (AlmMgr=0x710,0x648,0x724).

Problem:
When WindowViewer is starting up and the timer message is in place but the callback thread is still not fully initialized, this problem occurs. The timer message implemented by AlarmManager tries to post the message to the callback thread, which is not yet initialized.

Back to Resolved Issues

L00016991 Fonts display is 'blotchy' in WindowMaker when using 'Smooth edges of screen fonts' setting. Fonts in WindowViewer are displayed OK.

Problem:
Fonts display is “blotchy” in WindowMaker when using 'Smooth edges of screen fonts' setting. Right-click on the desktop, select property, select Effects tab, and then select the 'Smooth edges of screen fonts" check box. Text in WindowMaker has holes or white space around the font edges. This “blotchy” appearance is not displayed in WindowViewer.

Back to Resolved Issues

L00017565 Alarm Purge/Archive shuts down when user clicks OK.

Problem:
Alarm Purge/Archive shuts down when user clicks OK. The label OK is misleading and has been changed to Close.

Back to Resolved Issues

L00017621 Tag assignment in 16-pen window results in "Tagname.x is in an out-of-date format or corrupted" and the application cannot be opened again.

Problem:
Assign tag to a couple of 16-pen charts by selecting it from the tag dictionary dialog box. Close the window, log off the application, and shut down using the Action script in a pushbutton. When you restart WindowViewer the following error message is displayed: "Tagname.x is in an out-of-date format or corrupted". Also the application cannot be opened again.

Back to Resolved Issues

L00017790 The Edit Custom Color dialog box, when opened from the 16-pen trend control dialog box, causes WindowMaker to crash.

Problem:
The Edit Custom Color dialog box, when opened from the 16-pen trend control dialog box, causes WindowMaker to crash.

Back to Resolved Issues

L00017809 X or Y location of window changes when reducing the width or height of the window manually and without saving and closing.

Problem:
X or Y location of window changes when reducing the width or height of the window manually and without saving and closing. The entire window moves left instead of being resized. The top-left of the window is no longer at (4,4), but rather is relocated to the left out of the visible pane (the white area).

Back to Resolved Issues

L00017828  Cannot change a double byte font in AlarmDBView control.

Problem:
Cannot change a double byte font in AlarmDBView control. It resets to default font.

Back to Resolved Issues

L00017865 Unselecting all radio button settings in Discrete Value Pushbutton can crash WindowViewer.

Problem:
If none of the radio buttons (Direct, Reverse, Toggle, Reset, and Set) are selected for Discrete Value Pushbutton when assigning a discrete tag to a rectangle, clicking on the object in run-time can crash WindowViewer.

Back to Resolved Issues

L00017867 In the French version of InTouch, the Set/Reset Display button has incorrect translation for Open.

Problem:
In the French version of InTouch, the Set/Reset Display button has incorrect translation for Open.

Back to Resolved Issues

L00017877 When a new application and a new window are created, printing the window disables WindowMaker after the printout.

Problem:
When a new application and a new window are created, printing the window disables WindowMaker after the printout. Note: If you close the window first, then open it again before printing, WindowMaker is not disabled.

Back to Resolved Issues

L00017904 It is possible to clear all radio buttons (unchecked) in the animation links, such as Object Height/Width and the Percent Fills, which causes WindowMaker to crash.

Problem:
It is possible to clear all radio buttons (unchecked) in the animation links, such as Object Height/Width and the Percent Fills. WindowMaker crashes when you double-click on one of the Alarm Type radio buttons for Line Color/Analog Alarm or Fill Color/Analog Alarm animation link.

Back to Resolved Issues

L00017934 In the 16 Pen Trend environment, switching between WindowMaker and WindowViewer and then clicking on the scooter (or F2) will increase its size.

Problem:
In the 16 Pen Trend environment, switching between WindowMaker and WindowViewer and then clicking on the scooter (or F2) will increase its size.

Back to Resolved Issues

L00017936 When creating a new WWALMDB, Alarm DB Logger does not set any permissions for WWUser / WWPower / WWAdmin users for the *Ex views; hence those accounts cannot be used for alarm retrieval using Alarm DB View.

Problem:
When creating a new WWALMDB, Alarm DB Logger does not set any permissions for WWUser / WWPower / WWAdmin users for the *Ex views; hence those accounts cannot be used for alarm retrieval using Alarm DB View.

Back to Resolved Issues

L00017944 In the 16 Pen Trend environment, Pen Trend goes blank in the run-time if trend is stopped (Stop button) while the Configuration dialog box is opened.

Problem:
The contents of the Pen Trend will disappear even after the Configuration dialog box is closed. Only clicking the Play button will make data appear again.

Back to Resolved Issues

L00017975 In the French version of InTouch, the All and Historical options on the Query tab in Alarm DB Logger Manager are not translated.

Problem:
In the French version of InTouch, the All and Historical options on the Query tab in Alarm DB Logger Manager are not translated.

Back to Resolved Issues

L00017979 In the Japanese version of InTouch, creating an application path with certain Japanese characters and deleting the application from the list causes the InTouch Application Manager to not find the application.

Problem:
In the Japanese version of InTouch, creating an application path with certain Japanese characters and deleting the application from the list causes the InTouch Application Manager to not find the application.

Back to Resolved Issues

L00017982 In the Japanese version of InTouch, the All and Historical options on the Query tab in Alarm DB Logger Manager are not translated.

Problem:
In the Japanese version of InTouch, the All and Historical options on the Query tab in Alarm DB Logger Manager are not translated.

Back to Resolved Issues

L00017994 Alarm DB Logger Manager hangs if the Alarm database was not created and you click Start.

Problem:
Alarm DB Logger Manager hangs if the Alarm database was not created and you click Start. Both the Start and Settings buttons are disabled.

Back to Resolved Issues

L00017999 Not able to log alarms as user wwPower in the Alarm DB Logger.

Problem:
Not able to log alarms as user wwPower in the Alarm DB Logger. InTouch modified to give permissions to user wwPower. Existing customers must click either Update Permissions or Alter Database button to resolve this issue.

Back to Resolved Issues

L00018231 In Japanese version of InTouch, there are corrupted fonts in WindowMaker dialog boxes using Japanese local settings.

Problem:
In Japanese version of InTouch, there are corrupted fonts in WindowMaker dialog boxes using Japanese local settings.

Back to Resolved Issues

L00018283 Alarm DB Logger will not function if there are more than 16 lines of queries in its Alarm Query configuration.

Problem:
Alarm DB Logger will not function if there are more than 16 lines of queries in its Alarm Query configuration. The new limit for the query text field is 1024 characters. If there is more than one line in the query window, two hidden characters must be added to the total characters for each line. For example, if each line in the query is 32 characters long, the total number of lines in the query can be calculated by this equation: 1024 / (32 + 2) = 30 lines.

Back to Resolved Issues

L00018284 The sharing of the Wonderware license folder when InTouch is started is a security concern. Provide the ability to halt the sharing of this folder.

Problem:
User needs to follow these steps:

1.      Create a new "License.ini" file in the \\Program Files\FactorySuite\Common folder.

2.      Type both of the following lines into the "License.ini" file:

[License]
CreateLicenseShare=0

3.      Remove share from the "\\Program Files\FactorySuite\Common\License" folder by selecting "Do not share this folder" in the sharing properties tab.

4.      Click Apply and OK buttons.

Back to Resolved Issues

L00018294 After installation of InTouch 7.11 Patch 06, Alarm DB Logger no longer logged alarms to the database.

Problem:
After installation of InTouch 7.11 Patch 06, Alarm DB Logger no longer logged alarms to the database. Some computers are OK while others demonstrate the problem. The alarms are buffered into the queue. If the user tries to stop the logging, the message "Flushing alarms in buffer.." is displayed and the logger hangs at 100% CPU usage.

Back to Resolved Issues

L00018335 In the French, German, and Japanese versions of InTouch, the word “None” in the following error message is translated: "Change Password for Operator None".

Problem:
In the French, German, and Japanese versions of InTouch, the word “None” in the following error message is translated: "Change Password for Operator None".

Back to Resolved Issues

L00018519 Enhancement to the 16-pen trend functionality to eliminate occasional double thick line.

Problem:
Drawing mode from the maximum value of one-data-collection time frame to the minimum value of the next is requested, instead of from average to average.

Resolution: The modification contains two drawing modes.

  • Averaging mode: It is the current drawing mode. Because of the time range and the buffer size of the 16-Pen trend, each pixel on the chart is representing several seconds’ worth of data, which means several values. These values might not be identical, and the data point on the chart might appear as a vertical line between the maximum and the minimum values observed for all the changes within that time frame. Once that vertical (Min to Max) line is drawn, it moves the pen back to the Average value, and then waits for the next collection of data. Once the new set of data is calculated, it does the same thing again. It starts by drawing a line from where the pen was left (the average value of the last collection) to the average value of the new collection.
  • Min - Max mode: A new option is introduced in this patch to support those who do not want the chart to draw from the average to the average value of the new data collection. In this new algorithm, the line draws as cleanly as possible – it directly connects the endpoints of each data collection to prevent lines from overlapping.


To enable the Min-Max drawing algorithm, you must type the following entry in the InTouch.ini file:

[InTouch] 16PenTrendDrawMode=1

If this algorithm is enabled (16PenTrendDrawMode=1), the Log Viewer will display "16-Pen Trend Drawing Mode= Min - Max". Otherwise it will display "16-Pen Trend Drawing Mode = Averaging."

If the Min-Max INI entry is missing or the following entry is found in the InTouch.ini file, the software will use the existing drawing algorithm:

[InTouch] 16PenTrendDrawMode=0

Back to Resolved Issues

L00018566 WindowViewer crashes on initialization of a HistData wizard.

Problem:
WindowViewer crashes on initialization of a HistData wizard.

Back to Resolved Issues

L00018756 The Cross Reference utility’s Save As function does not write the tag link locations to the CSV file as documented in the InTouch Users Guide.

Problem:
The Cross Reference utility’s Save As function does not write the tag link locations to the CSV file as documented in the InTouch Users Guide.

Back to Resolved Issues

L00018790 In the Japanese version of InTouch, the color fill animation link is the opposite of what is true.

Problem:
In the Japanese version of InTouch, the color fill animation link is the opposite of what is true.

Back to Resolved Issues

L00018838 Use of the DialogValueEntry or DialogStringEntry causes a crash when users’ IDEA script function is only used in Application On Shutdown script.

Problem:
The sequence of the function call causes memory corruption in MFC42.DLL. This resulted in the crash after the WindowViewer exited.

Back to Resolved Issues

L00018906 In Historical trending mode, 16-pen trend, the start time of the trend is the current time. This problem results in an empty future trend.

Problem:
In Historical trending mode, 16-pen trend, the start time of the trend is the current time. This problem results in an empty future trend.

Back to Resolved Issues

L00019008 In the Japanese version of InTouch, the error "can not open tagname.x" is displayed after importing windows containing the password wizard.

Problem:
When importing a window that contains a password wizard, which is not configured, WindowMaker crashes with the error "can not open tagname.x".

Back to Resolved Issues

L00019096 Changing the font properties does not always provide the same results.

Problem:
Changing the font properties does not always provide the same results, depending on the order and tools used to change the font. Text objects that have an appearance show the same font attributes when checking the font properties.

Back to Resolved Issues

L00019104 The Log file *.ALG does not include the Alarm Comment when the ACK or .ACK was used, or when the almAck comment was blank (empty string).

Problem:
The Log file *.ALG does not include the Alarm Comment when the ACK or .ACK was used, or when the almAck comment was blank (empty string).

Back to Resolved Issues

L00019196 Unreadable characters displayed in the keypad (a dash "-" looks the same as period ".").

Problem:
When the keypad is called using DialogValueEntry, a dash "-" appears as a period ".".

Back to Resolved Issues

L00019283 No longer able to use the AlarmDBView ActiveX in Visual Basic after installation of InTouch Patch 06.

Problem:
Prior to installation of InTouch Patch 06, users were able to create a VB application on a computer with InTouch installed, drop the AlarmDBView ActiveX onto a form, and right-click to get to the properties.

Back to Resolved Issues

L00019352 Using local variables in GetNodeName() will display the following error message: "Must have writeable message variable for this argument to GetNodeName".

Problem:
Using local variables in GetNodeName() will display the following error message: "Must have writeable message variable for this argument to GetNodeName". For instance:

DIM LocalMsg AS MESSAGE;
GetNodeName(LocalMsg, 15);
LogMessage("LocalMsg: " + LocalMsg);

On the attempt to validate or save the script, the error message is displayed.

Back to Resolved Issues

L00019410 The Hardware/Software flow control settings are not preserved in the Alarm Printer.

Problem:
Under Port Configuration on the Printer Tab, change the selection for Flow Control from None to Hardware, click Apply and then OK. Reopen Port Configuration and note that Flow Control has been set back to the default value (None).

Back to Resolved Issues

L00019431 WWRequest does not function after a failed connection.

Problem:
WWRequest does not function after a failed connection.

Back to Resolved Issues

L00019440 Failed to create view in wwAlmDB by using AlterWWALMDB.exe.

Problem:
Failed to create view in wwAlmDB by using AlterWWALMDB.exe.

Back to Resolved Issues

L00019460 Crash related to special characters in the MSSQL DB; no crash if unused tags are deleted from the InTouch application.

Problem:
Crash related to special characters in the MSSQL DB; no crash if unused tags are deleted from the InTouch application. WWLogger message is the following: "/PTACC /Attempt to set string value having more than 131 characters. String truncated."

Back to Resolved Issues

L00019569 After disabling and enabling InSQL, the analog tag does not update. InSQL shows Null until the tag changes value.

Problem:
After disabling and enabling InSQL, the analog tag does not update. InSQL shows Null until the tag changes value.

Back to Resolved Issues

L00019699 During UNACK_RTN events, when ACKed on a client of a Hot Backup pair, the ACK is not sent to the backup computer.

Problem:
During UNACK_RTN events, when ACKed on a client of a Hot Backup pair, the ACK is not sent to the backup computer.

Back to Resolved Issues

L00020058 DAO querying a Hot Backup pair does not detect that WindowViewer is shutdown on the primary provider when the Alarm DB Logger is also running on the primary provider.

Problem:
DAO querying a Hot Backup pair does not detect that WindowViewer is shutdown on the primary provider when the Alarm DB Logger is also running on the primary provider.

Back to Resolved Issues

L00020170 AlterWWALMDB.EXE in InTouch Patch 06 fails when used with Microsoft SQL Server 7.0 SP3. Error message is the following: “Failed to Create v_AlarmEventHistoryEx1 view”. This function works OK on SQL Server 2000 and MSDE.

Problem:
AlterWWALMDB.EXE in InTouch Patch 06 used syntax that is not supported in SQL Server 7.0.

Back to Resolved Issues

L00020214 Tagname Dictionary allows "Ctrl+Enter" to be typed in the Alarm Comment field of Discrete tags, which results in an embedded CRLF that causes problems for DBDump/DBLoad.

Problem:
Tagname Dictionary allows "Ctrl+Enter" to be typed in the Alarm Comment field of Discrete tags, which results in an embedded CRLF that causes problems for DBDump/DBLoad. Disable the Ctrl+Enter key sequence in the Alarm Comment field so a new line cannot be inserted.

Back to Resolved Issues

L00020312 Alarm DB Restore stops restoring when it encounters comments in the comment file that contain a comma.

Problem:
Alarm DB Restore stops restoring when it encounters comments in the comment file that contain a comma.

Back to Resolved Issues

L00020460 WWDlg_ScriptEdit returns a modified script when the user clicks Cancel. There is no way to know whether the user clicks OK or Cancel to close the Script Editor.

Problem:
WWDlg_ScriptEdit returns a modified script when the user clicks Cancel. There is no way to know whether the user clicks OK or Cancel to close the Script Editor.

Back to Resolved Issues

L00020552 Unable to write to the ROCpct dot field from an IDEA application.

Problem:
Unable to write to the ROCpct dot field from an IDEA application.

Back to Resolved Issues

L00020559 Windows Textbox only displays 130 characters of a 131-character-long tag.

Problem:
Windows Textbox only displays 130 characters of a 131-character-long tag.

Back to Resolved Issues

L00020610 A gap is displayed on the right side of a historical trend during the fall back time change in October for Greenwich time zone when it is set to auto adjust for time change.

Problem:
Issues in historical logging and retrieving: InTouch has been modified so that no data is lost during transitions between standard time and daylight savings time.

Back to Resolved Issues

L00020697 Enhancement request: New feature to be able to bypass the creation of placeholders (based on the existence of tags in the tagname dictionary) when windows and scripts are imported from one application to another.

Problem:
When windows and scripts are imported from one InTouch application to another, placeholders are used preceding each tag. This causes a problem when there are many tags used in windows/scripts due to the limitation in the number of placeholders (approx 4095). The user cannot import big applications, but rather must import chunks of windows at a time to ensure that the number of placeholders is not exceeded.

A new feature was introduced to the InTouch 7.11 Patch 07 that allows users to import windows directly from one InTouch application into another through the File - Import menu in WindowMaker. There are several options and limitations in the new feature:

  • WindowViewer must to be shut down before performing the importing process.
  • The user has the option to preserve the placeholders with a check box in the Application Data Import Options dialog.
  • The preserved placeholder only works when tag types are matched correctly (so that a string tag is not replaced with an integer tag, for example) between current application and the application it is imported from.
  • The application being imported should be imported from a proper InTouch directory. Otherwise, the preserved placeholder will not work with an exported window.
  • The preserved placeholder only preserves placeholders for existing tags in the current application. If tags are not in the current tagname database, placeholders will be placed in front of each tag.
  • The user must manually change and validate the following tagnames:
    • Trend object Name and Pen Scale Tagname in the "Historical Trend with Scooters wizard".
    • Pens assignments in the Real-Time Trend (from the Draw Object Toolbar).
    • Pens assignments for Historical Trend (from the Draw Object Toolbar) must be manually reassigned.
  • For any large scripts, the script will be truncated after importing (up to 32,700 characters long, including spaces and line breaks, each line break = 2 characters). The new script may or may not include placeholders(?type:) depending on the existing tags in the current tagname database.

Back to Resolved Issues

L00020741 The following error message is displayed on alarm consumer’s node after a provider stop/start: "/UNKNOWN /!SmartHeap Error Code 14, MEM_BAD_POINTER 00140188, in pool 0 /UNKNOWN /!memory corruption(4013002B) val=0x40 -> AlarmConsumer must restart".

Problem:
For any application which has more than 100 alarm groups on the alarm provider node, if user stops the provider, adds three or more alarm groups in the application, and then starts the provider, the logger shows the error message above.

Back to Resolved Issues

L00020742 Screen display flickers when halo is bigger than screen resolution and the mouse is moved over push buttons.

Problem:
Screen display flickers when halo is bigger than screen resolution and the mouse is moved over push buttons.

Back to Resolved Issues

L00020788 If the password of the SPCPro database user is more than 4 characters long, an SPCPro application or HeapShareFree error message is displayed when WindowMaker is started.

Problem:
If the user’s password for Microsoft SQL Server is modified after the SPCPro database has been created, SPCPro displays an application error or HeapShareFree displays an error message when WindowMaker is started.

Back to Resolved Issues

L00020819 When browsing tags during historical trend pen assignment, the entire remote tagname dictionary is displayed instead of only the history tags.

Problem:
Using Distributed History Provider as an InTouch History Provider for historical trending, the entire remote tagname dictionary is displayed instead of just the History Tags. This occurs during historical trend pen assignment by using the "ProviderName." to browse the tags.

Back to Resolved Issues

L00021400 If an application is developed with a later version of InTouch, the Application Manager states the version as 'Old'.

Problem:
If an application is developed with a later version of InTouch, the Application Manager states the version as 'Old'. This has been changed to "Unknown".

Back to Resolved Issues

L00021729 The alarm system registers Rate of Change alarm based on a previous setpoint at startup when Retentive Parameters is selected for a tag.

Problem:
The alarm system registers Rate of Change alarm based on a previous setpoint at startup when Retentive Parameters is selected for a tag. Calculation for limit value uses ROC value from tag database instead of ROC value from retention. InTouch change made for both integer tag alarm and real tag alarm.

Back to Resolved Issues

L00022064 Cross Reference utility crashes WindowMaker if specific Recipe.csv file is in the application directory.

Problem:
Cross Reference utility crashes WindowMaker if specific Recipe.csv file is in the application directory and the length of the line in the Recipe.csv exceeds the buffer limit (512 characters). These issues have been fixed: the buffer size has been increased to 2048 and the cross-reference utility reads all *.csv files in the application folder.

Back to Resolved Issues

L00022250 Not enough disk space error is displayed when trying to install InTouch Patch 5a.

Problem:
If the free space of the target drive is about 8.01 GB, the following error message pops up while installing a patch: "There is not enough space on drive c:\ to extract this package, please free up 9.08 MB and click Retry". The problem does not occur with 7.00 GB free or anything higher than 9 GB free.

Back to Resolved Issues

L00022365 In the French version of InTouch, the Set/Reset Display button has incorrect translation for "Open".

Problem:
In the French version of InTouch, the Set/Reset Display button has incorrect translation for "Open".

Back to Resolved Issues

L00022618 Incorrect info on the SPCPro About box.

Problem:
"Serial No.: xxxx" has been removed.

Back to Resolved Issues

L00022760 Alarm entries are corrupted when acknowledged if the AlarmUserDefStr is set in the application on a start script.

Problem:
Alarm entries are corrupted when acknowledged if the"$System.AlarmUserDefStr="Test String" is set in the application on a start script. After the alarm is acknowledged, the Name field displays "est String", Class display "String", and type displays "est".

Back to Resolved Issues

L00022771 An Alarm Tree ActiveX object displays the following error message when calling scripts. "Error processing AlarmTree1.UpdateView on method call (execute). Exception 0x800A005B: Object variable or With block variable not set".

Problem:
When using InTouch 7.11 Patch 06 and AlarmSuite 7.1, the problem occurs. With an Alarm Tree ActiveX object on the screen and a button with scripting to set the path and then update the view, the object is set to 'Always Expand' and the error message is displayed. If this option is unchecked, then the error does not occur.

Back to Resolved Issues

L00022981 Tags Alarm 'Disabled' properties (for example, AlarmLoEnabled and .AlarmHiEnabled) are not being retained if 'Update Use Counts' is used with WindowMaker.

Problem:
Tags Alarm 'Disabled' properties (for example, AlarmLoEnabled and .AlarmHiEnabled) are not being retained if 'Update Use Counts' is used with WindowMaker.

Back to Resolved Issues

L00023092 60k license is not allowing over 61,405 RTR (and local tags, total).

Problem:
60k license is not allowing over 61405 RTR (and local tags, total). Maximum number of remote tags allowed for 60k license was 60K (the number of local tags). Now the maximum number of tags allowed in a 60k license is 61,439 total local and system tags and 65,535 total local, system and remote reference tags.

Back to Resolved Issues

L00024256 In the Tagname Dictionary (SuperTags), the member list does not work after clicking Select then Cancel.

Problem:
In the Tagname Dictionary (SuperTags), the member list does not work after clicking Select then Cancel.

Back to Resolved Issues

L00024292 A /View Unknown Opcode in GetSValue popup message is displayed from QuickFunction.

Problem:
If a QuickFunction returns an integer and the return value is used in an ActiveX event script such as Microsoft form ComboBox startup or change event, then WindowViewer crashes with the error, "/View Unknown Opcode in GetSValue ():21".

For existing applications that exhibit the problem above, do the following: after installing the Patch, resave the Script / QuickFunction in WindowMaker (this is a requirement). The fix is in the parsing of the script. After parsing, the script is saved to an ".nmd" file. WindowViewer loads the file and executes the script.

Please follow this procedure to regenerate the .nmd file (resaving the script).

1.      Open the quick function.

2.      Insert a blank line in the script body. This enables the "Save" button.

3.      Click Save, and then OK.

Back to Resolved Issues

L00024336 Text Object's Font size does not save correctly when modifications are done with the mouse.

Problem:
Text Object's Font size does not save correctly when modifications are done with the mouse.

Back to Resolved Issues

L00024601 The AlterWWALMDB.exe utility does not use the "top max records" setting in the dialog for the first run, but rather uses the default 1000 records.

Problem:
The AlterWWALMDB.exe utility does not use the "top max records" setting in the dialog for the first run, but rather uses the default 1000 records.

Back to Resolved Issues

L00025147 The InTouch Keyboard is shown even when the check box is cleared.

Problem:
In the Password Input Wizard dialog, the "Show Keyboard" check box appears to be inoperative. The InTouch Keyboard is shown even when this check box is cleared.

Back to Resolved Issues

L00025585 Unable to connect InSQL 8.0 or InSQL 7.1 to InTouch 7.11 when InTouch is running on a Windows XP SP2 computer.

Problem:
Microsoft Windows XP SP2 introduces several security technologies including disabled NetDDE, enhanced Windows Firewall, and a reduced RPC attack surface. These enhancements affect the use of NetDDE, WWLogger and Suitelink protocols in InTouch.

If any Wonderware products must be operated on a Windows XP SP2 computer, you should contact your local Wonderware Distributor or download the OS Configuration Utility from the Wonderware Technical Support website (Wonderware Technical Support). The OS Configuration Utility will open up specific ports, enable NetDDE and add Wonderware Suitelink and Wonderware Logger to the Firewall exception list.

Wonderware products will not work properly on a Windows XP SP2 computer without running the OS Configuration Utility. If users want to install a new copy of InTouch 7.11 on a Windows XP SP2 computer, and would like to use NetDDE, the StartUp Type of ClipBook, Network DDE, and Network DDE DSDM, services MUST be changed from disabled to Manual before installing the product.

Back to Resolved Issues

L00025933 If there are a large number of alarms in the database, InTouch will only display the oldest alarms in the AlmDbViewCtrl and display $NewAlarm for the rest.

Problem:
If there are a large number of alarms in the database, InTouch will only display the oldest alarms in the AlmDbViewCtrl. All other alarms after the first 1,000 alarms will simply show the event $NewAlarm even if the display is configured to show a small portion of time in which the new alarms occurred. This behavior is only present if the database is configured as Consolidated.

Back to Resolved Issues

L00026422 The AlterWWALMDB.exe utility crashes after it fails to "Test Connection".

Problem:
The AlterWWALMDB.exe utility crashes after it fails to "Test Connection".

Back to Resolved Issues

L00026453 Uninstall does not remove the /Programs/Wonderware FactorySuite/InTouch/Alarm DB Alter shortcut.

Problem:
Uninstall does not remove the /Programs/Wonderware FactorySuite/InTouch/Alarm DB Alter shortcut.

Back to Resolved Issues

L00026454 Unable to use the AlmDbViewCtrl for event history.

Problem:
Unable to use the AlmDbViewCtrl for event history.

Back to Resolved Issues

L00026587 In the Japanese version of InTouch, the AlmDbViewCtrl property dialog box’s "Refresh", "sort", and "sort" check boxes should be “Refresh", "Sort", and "Reset”.

Problem:
In the Japanese version of InTouch, the AlmDbViewCtrl property dialog box’s "Refresh", "sort", and "sort" check boxes should be “Refresh", "Sort", and "Reset”.

Back to Resolved Issues

L00026588 In the Japanese version of InTouch, Display Modes of the AlmDbViewCtrl property dialog box are user editable.

Problem:
The General tab in the AlmDbViewCtrl property dialog box is user editable.

Back to Resolved Issues

L00026879 The status bar on AlmDbViewCtrl displays incorrect information: "Displaying 1 thru 2000 of 1000 records".

Problem:
The status bar on AlmDbViewCtrl displays incorrect information: "Displaying 1 thru 2000 of 1000 records".

Back to Resolved Issues

L00027371 In a workgroup environment, WindowViewer crashes after switching users on a Windows XP computer.

Problem:
If an application is running and the operator switches to another user who has Administrative privileges and back again to the original user, the following error is displayed:

Assertion Error - Make note of error U:\IntouchDev\src\sc-core-Irvine\view\viewlib\vudraw.c Line 94 Continue?

Only one instance of WindowMaker or WindowViewer is allowed on a non-TSE node. An error message is displayed if the user tries to run a second instance.

Back to Resolved Issues

L00027697 In the Simplified Chinese version of InTouch, there are untranslated strings in Alarm DB View and Alarm DB logger.

Problem:
In the Simplified Chinese version of InTouch, there are untranslated strings in Alarm DB View and Alarm DB logger.

Back to Resolved Issues

L00027800 Read-only I/O tags are writeable using Indirect Tags.

Problem:
With a read-only I/O real number assigned to an Indirect Tag, write-back is possible.

Back to Resolved Issues

L00028153 When you open an application created in an English version of InTouch in a Japanese WindowMaker, some characters' font size changes.

Problem:
Font size changes when you open the application created in InTouch English version in other languages that use double byte characters.

Back to Resolved Issues

L00028170 In AlmDbViewCtrl of the Simplified Chinese version of InTouch,  the default font does not show.

Problem:
The characters inside the AlmDbViewCtrl are not Chinese when using the default font.

Back to Resolved Issues

L00028309 Attempting to display historical data in a trend when the selected range spans a Daylight Savings Time transition loses data.

Problem:
Attempting to display historical data in a trend when the selected range spans a Daylight Savings Time transition loses data. InTouch has been modified so no data is lost during the transition between standard time and Daylight Savings Time.

Back to Resolved Issues

L00028900 Terminal Services client connects to a server and runs WindowViewer in a different screen resolution than that of the server application, and the font size is not adjusted to the client environment when set to Japanese as its default language or when using a Japanese OS.

Problem:
Terminal Services client connects to a server and runs WindowViewer in a different screen resolution than that of the server application, and the font size is not adjusted to the client environment when set to Japanese as its default language or when using a Japanese OS.

Back to Resolved Issues

L00028982 When InSQL data is set for Greenwich Mean Time and the trend is set to plot for one hour, two hours of data is shown during the Daylight Savings Time change.

Problem:
In InSQL, the history data is stored in UTC time. But when querying the data, the START TIME and END TIME are converted to Local Time and submitted as part of the SQL query. Because of this, the data is not shown correctly in the trend during the Daylight Savings Time change.

Back to Resolved Issues

L00029247 SPC Limits Wizard does not create tags and errors are logged to the Wonderware Logger after clicking on suggest and OK button.

Problem:
SPC Limits Wizard does not create tags and errors are logged to the Wonderware Logger after clicking on suggest and OK button.

Back to Resolved Issues

Back to Top


Known Issues

L00011814 Distributed alarm object (DAO) is not always printed; application that overlaps DAO is sometimes displayed in the DAO portion of the InTouch window instead.

Problem:
Switching to different application while doing a print window is not recommended.

L00013442 Problem with FileReadFields in an asynchronous function if FileReadFields is also called from another script at the same time.

Problem:
Using FileReadFields() in an asynchronous quick function is not recommended.

L00014331 StringfromReal() is rounding the result.

Problem:
Issues arise in assigning a value of a real tag in a script and displaying that value with in an analog value display (#.##########) or a string value display.

1.      Action script:

·          When assigning a value to a real tag in a Touch Pushbuttons Action script (Realtag = 1111.444444444;), InTouch assigns a number that is precise to six digits. In that case, after the button is pressed, the value for RealTag is 1111.4400000.

·          Another example: If the script "RealTag=1.123456789;" is used in an action script, you should expect the displayed value to be 1.1234600.

 

2.      StringFromReal( Number, Precision, Type );

·          If a float number is assigned to a Number variable in a script [for example "Result = StringFromReal( 1234.123456789, 10, "f" );"], first the action script will convert 1234.123456789 to 1234.12 as explained above, then the StringFromReal will convert 1234.12 to a string. So the value of the Result is 1234.1200000000.

·          If a real tagname is assigned to a Number variable in a script ["Result = StringFromReal( RealTag, 10, "f" );"], and you create a user input, a value display animation link for the RealTag, enter 1234.123456789 to the RealTag., first the value will display as 1234.1234568 (rounding up at the 7th value after decimal).
When the script is activated, the StringFromReal will convert the value of the RealTag, which is 1234.123456789, to a string. Therefore, the value of the Result is 1234.1234567890.

L00018176 AlarmLogger skips the alarm records if the master record is not present in the database.

Problem:
AlarmLogger skips the sub-state change alarm records if the master record (equivalent ALM record) is not present in the database.

This problem can happen in two cases:

  • Purge Operation: For instance, purging is scheduled for every day at 5:00 a.m., and a tag goes into alarm state at 4:58 a.m. At 5:00 a.m., this alarm record will be purged from the database. If the same alarm record changes its state to ACK or ACK_RTN, then these alarm records will not be logged into database and the message "The current record is skipped. The equivalent ALM record has not been logged in the database" will be logged in WWLogger.
  • High burst Scenario: If the connection to the database is not present, then AlarmLogger starts buffering the alarm records. When the number of alarm records reaches the maximum buffer limit, AlarmLogger starts deleting the alarm records from the buffer/smart cache.
    For instance, high burst occurs at 5:00 a.m., and the master alarm record is deleted from the buffer/smart cache. Database connection is established at 5:05 a.m. If the tag corresponding to the deleted alarm records changes its state, then these alarm records will not be logged into the database and the message "The current record is skipped. The equivalent ALM record has not been logged in the database" will be logged in WWLogger.

When the AlarmLogger encounters a new alarm record (UNACK_ALM), it creates a new record for AlarmMaster and one new entry for the AlarmDetail/AlarmConsolidated tables. The alarm master record entry contains a “GUID” and “AlarmId” for that instance of the alarm; this entry in the AlarmMaster table acts as a parent record for all of the alarm records logged for each sub-state change or the alarm transition logged in the Alarm Detail or Alarm Consolidated table for that particular instance of alarm. AlarmId in the AlarmMaster table is the reference key for the AlarmDetail or Alarm Consolidated table.


If the master alarm record is not present in the WWALMDB database and a sub-state change alarm is encountered by the AlarmLogger, then it fails to log it to the AlarmDetail or AlarmConsolidated table because there is no corresponding parent alarm in the alarm master table for that particular instance of alarm record. This behavior is as designed.

L00018476 Several wizard sizing problems exist in InTouch.

Problem:
The sizing problems occur when a wizard object is placed on a window or resized, and then the window is closed and then reopened. For instance, when using a wizard for creating buttons and meters, the objects change size when opening the window for the first time after placing the object on the window or resizing it. This problem affects all wizards including third-party ones (Symbol Factory).

L00027877 Cannot use an ampersand (&) as an operator between two hexadecimal numbers.

Problem:
InTouch now allows using an ampersand as an operator between two hexadecimal numbers without spaces in a script (for example: Tag1 = 0x0a&0x01). Notes: Since ampersand is a valid character for a tagname, it's very important to use spaces before and after “&” if you want to use it as an operator. An ampersand between two tag names will be interpreted as a new tag name. For example:

tag1 = (tag2&tag3); InTouch interprets tag2&tag3 as a new tagname.

or

tag1 = (tag2& tag3); InTouch interprets tag2& as a new tagname.

Back to Top


© 2004 Invensys Systems, Inc. All Rights Reserved.