Wonderware Intouch Historical Trend

[Heinz Francis]

HelloAll, I am using InTouch 10.1.301 and Archestra 3.1.301. I am attempting to use an archestra trend client with intouch historical data. I am not using the wonderware historian, rather the intouch LGH files archived on a network client machine. I also would like to use indirect tags to configure the archestra graphic and have built the custom properties to do this. My goal is to create a trend window using indirect tags, script naming the indirect tags for the pens when the window is called. As of right now, I have a very successful real time trend that refuses to load any historical data. The regular Intouch trend client loads the historical data without issue. TROUBLESHOOTING THUS FAR:I have set up the Historical Sources tab of the trend client to the LGH file share and set the UNC path. I have set up each of the Pens in the trend, and pointed their historical source at the name of the historical source in the historical sources tab. I have verified the historical source of InTouch is the same as the UNC path set up in the trend. I tried calling WW tech support and their recommendation was to use Memory tags vs indirect tags. This was the dumbest thing a tech support has ever recommended, but I went with it anyway. All this made me have to do is script the direct tag values to the mem tag values along with all of the dot fields AND have to create a "while running" script to update the mem tag value every second, because mem tag values are only updated when something triggers the value update. And it did nothing to pull in the historical data. I tried using direct tags and cut out the indirect and mem tags. This did nothing to pull in the historical dataI moved the historical source in both the trend setup and intouch setup to directory local to the Galaxy Repository. I found this article and I made another archstra symbol with the trend client, and configured it as recommended, no custom properties, pointed the pen directly at the direct intouch tag, and configured the historical source, also pointing the pen history at the source and directly to the intouch tag. ANNNDDDD its a stripped down real time trend with no history. I am getting very frustrated as all documentation and sources indicate this should be possible, WW tech support says it is possible, but I cannot get anything over tier 1 support on this version. Does anyone have any ideas?

I just came across this same issue while upgrading from v10.1 to v11.1 and migrating to ArchestrA graphics. I found the article linked below that had the answer I was looking for. It turns out that under the Pen configuration tab, under the Historical heading at the bottom of the window, you don't use the "InTouch:" prefix before the tag name.

Popularly referred to as lgh files by those familiar with the Wonderware InTouch Human Machine Interface (HMI) software, these daily historical log files contain data for InTouch HMI tags which were only accessible using the Wonderware HistData Utility or Wonderware InTouch trending tools.

LGH File Inspector can open and read lgh files effortlessly through an easy and intuitive user interface that gives plant operators, engineers, and managers the ability to query one or more InTouch tags for a given time frame and then export the results into a Microsoft Excel workbook or now a CSV File. There is no dependency on the HistData utility or the Wonderware InTouch HMI software.

LGH File Inspector has no dependency on Wonderware InTouch HMI software or the HistData Utility; it reads lgh files directly. Just browse to the folder containing the lgh files that you want to query and LGH File Inspector is ready to go. This makes LGH File Inspector a great tool for analysts and engineering firms. All a client has to do is provide you with the lgh files that you need to analyze, and LGH File Inspector can query all of the relevant data.Easily Build and Run Queries.

1 - Select the starting date and time, the duration, and the interval for returning data.2 - Drag and drop the tags you want to query into the Query Tags List.3 - Click the Run Query button.Automate Query Execution.

Every query can be saved and executed automatically without having to reopen LGH File Inspector. Advanced query options provide the ability to schedule a query to execute at regular intervals and update an Excel workbook automatically.Also Functions as a Reporting Tool.

Use Microsoft Excel to build reports that reference data populated by the LGH File Inspector. Workbooks can automatically receive data from one or more LGH File Inspector queries when the user opens the query, or from automatically generated queries run by any scheduling program, such as Windows Task Scheduler.

Microsoft Windows XP SP2 introduces several security technologiesincluding disabled NetDDE, enhanced Windows firewall, and a reduced RPC attacksurface. These enhancements affect the uses of NetDDE, WWLogger, and SuiteLinkprotocols in InTouch.

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

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

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

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

L00020697 Enhancementrequest: New feature to be able to bypass the creation of placeholders (basedon the existence of tags in the tagname dictionary) when windows and scriptsare imported from one application to another.

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

L00028900 TerminalServices client connects to a server and runs WindowViewer in a different screenresolution than that of the server application, and the font size is notadjusted to the client environment when set to Japanese as its default languageor when using a Japanese OS.

Problem:

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

Problem:

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

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. Thecheck box is cleared after breaking the wizard cell, double-clicking onVisibility, and then clicking on the Cancel button.

Problem:

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

Problem:

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

Problem:

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

Problem:

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

Problem:

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

Problem:

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

3a8082e126