Thursday, July 26, 2012

Configuring the ArchestrA TrendClient Control as an InTouch Real-Time or History Trend


The TrendClient control shown in your ArchestrA Graphic Editor can be used to display data from either Wonderware Historian or from classic stand-alone InTouch. This tip shows you how to set up the control as either a real-time or historical trend for InTouch data.

CONFIGURATION

1.      The most important thing to remember when using the TrendClient control is that it cannot co-exist with Wonderware Historian Client. So if you've got Historian Client installed, you'll need to uninstall it to use this control.

2.    The TrendClient control is a native .NET control, so first you'll need to create a new ArchestrA Symbol, and embed the TrendClient control into it.
 






3.      Double-click the embedded TrendClient and select Historical Sources under Configuration.
  • Click + to add a source.
  • Select InTouch Log History/LGH
  • Enter the computer (Name) and file location of your LGH files (UNC Path)

REAL TIME TREND



4.     Configure Pens for a Real Time Trend

  • Select Pens under Configuration
  • Click + to add a new pen
  • Give it whatever name you wish, such as the tagname
  • For Expression/Reference, enter the InTouch tag in the form INTOUCH:Tagname.
  • Pen Details can be hard-coded, or use InTouch tag dotfields as done here.


5. Embedding the Trend symbol into InTouch at this stage results in a Real-Time Trend.

INTOUCH HISTORY TREND

6. Configure Pens for Historical Trend


  • Follow the same steps as above to configure pen names and tags
  • Under Historical...
    • Enter the computer (Source)
    • Enter the InTouch tag (same as Reference above without the INTOUCH: prefix)
    • This is a common mistake. Just enter the tagname here, without prefix.






7. Embed the Trend Symbol in your InTouch window and you'll have a Historical Trend. No configuration is necessary in InTouch.


8. To specify start and end dates/times for historical trend display, you can specify a time range under the Options configuration, or use the SetStartAndEndTimes() method in a script. For example:



TrendClient1.SetStartAndEndTimes("7/23/2012 3:00 PM", "7/23/2012 3:30 PM", 0);

Monday, April 16, 2012

Using ScaleForResolution=0

Avoid screen resolution problems when moving InTouch applications between computers

If you're using classic InTouch, you've no doubt encountered the problem when editing an application on your development system that was created in a different video resolution. Common these days might be a target application for a screen size of 1280x1024 and a development system running on your wide-screen laptop at 1920x1080.  Nice laptop, by the way.

You always had to be careful when jumping between resolutions, but when you also change aspect ratios to a wide-screen, it's even more difficult.
There are two simple solutions.  One is to switch to using Managed InTouch applications and edit using the ArchestrA IDE. When opening InTouch WindowMaker, and prompted to change resolutions, you can just click 'No', and it lets you edit in the application's native resolution.

The other solution, for classic InTouch users, is to add the line:
ScaleForResolution=0



to the INTOUCH.INI file in your application's folder:
 




When you open the application, you will still be prompted to convert the resolution. Go ahead and click 'Yes'.  It will go through the conversion process,but it will not rescale your graphics. So a 100x100 pixel rectangle in the original application will still be a100x100 pixel rectangle after conversion.
Once you're done editing, you're going to copy your modified application to the original target computer, which had the 1280x1024 resolution in our example.  The modified application will show up in your Application Manager as having your edited 1920x1080 resolution, but don't worry.

Open your InTouch Application Manager and select Tools /Node Properties, then click on the Resolution tab. Select 'Allow WindowViewer to Dynamically Change Resolution', and then select 'Convert to screen video resolution':


When you open the application on your target computer in WindowViewer, it will convert the resolution back to 1280x1024.  But again, no rescaling will take place, so your application looks great.
One more note, you must always be aware of fonts.  If the original application used a font that was installed on one of the computers, but does not exist on the other computer, Windows will 'guess' as a font. And it usually guesses poorly. It's best to confirm that the same fonts already exist.

How do I create a new application on my wide-screen laptop that will be target for a different resolution target computer?
Sorry, no way around it. You must create your original application in that target application resolution. Then you can change your monitor back to your preferred resolution.

------

Update:  Starting with InTouch version 10.5 (part of System Platform 2012), you can set a checkbox in WindowMaker to perform this same thing. In WindowMaker, select Special / Configure / WindowMaker.  Check the box 'Lock Window Size'.


Tuesday, April 3, 2012

Getting Started with Remote Apps

Remote Apps is a new feature of Windows Server 2008 and onwards.  It uses the same technology as Remote Desktop, but displays only specified applications instead of an entire desktop. From the workstation perspective the app appears to be running locally; in reality it is running on the server. 

InTouch is a good candidate to run as a remote app because you often want more secure access by your HMI applications.
Accessing InTouch using Remote Apps is easy.  You can open a web browser and navigate, or you can embed a link on your desktop. Double-click on the link and it opens your InTouch application, just as if it were a local application.

The rest of this article focuses on how to setup Remote Apps.  If you have experience setting up a terminal server this will be trivial.  If you don’t, it still shouldn’t be too bad.

Client Setup
RDP version 6.1 or above is required on the client computer.  The required version of RDP ships with Windows XP SP3, Windows Vista SP1, Windows 7, Windows Server 2008, and Windows Server 2008 R2.  If need on another OS the required RDP version can likely be installed, even a Mac or a Tablet.

There are three options for setting up the clients.  All clients can be setup the same way or mixed and matched.
Option 1 - RDP File
The server can be used to create a *.rdp file with all the correct info.  The rdp file is put in a convenient location like the desktop where the user double clicks it to launch the app (such as InTouch).
Option 2- MSI File
The server can generate an msi file.  On the client machine the msi file is executed in order to install a shortcut in the start menu.
Option 3- Website
The server can host a website with links to launch apps like InTouch.  The big benefit of this is that zero client configurations are required.  An example link might be: https://RemoteAppsDemo/RDWeb/.  A user would then have to sign in to launch an app like InTouch.

Server Setup
Remote Apps is included with both Windows Server 2008 and Windows Server 2008 R2.
Given the choice to enable remote apps when adding the remote desktop services role(old name: terminal services role).
Installing Remote Apps
On Windows Server 2008 R2 (similar process for 2008) goto Server Manager add the roles “Remote Desktop Session Host” and “Remote Desktop Web Access”. 
Configuring Remote Apps
Goto Server Manager->Roles->Remote Desktop Services->RemoteApp Manager.  Here is where all the configuration will be done for Remote Apps. 
First thing to do is check for any warnings that looks significant.  One that will need to be addressed is “The TS Web Access Computers group is empty”.  The link “Learn more” can be clicked on for details on what this is and how to resolve it (resolution is easy).
The second step is to pick applications to enable as remote apps.  This is done by clicking “Add RemoteApp Programs” in the Actions pane on the far right.  The process of picking apps is simple.  A likely setup would be just WindowViewer, which would launch a specific InTouch project.  Another option might be to give them access to the InTouch Application Manager so they can pick which InTouch project to launch.

Thursday, March 22, 2012

Wonderware Customer FIRST Shipment

Here is a list of contents for the current Customer First support shipment.

Disc 1
  • Wonderware System Platform 2012
Disc 2
  • ArchestrA Workflow 2012
  • Wonderware Corporate Energy Management 1.2
  • Wonderware InBatch 9.5
  • Wonderware Intelligence 1.5
  • Wonderware MES 4.0 SP1
  • Wonderware QI Analyst 8.0 SP2
  • Utilities:  7-Zip and Microsoft FCIV
Disc 3
  • Patches and Service Packs
Disc 4
  • Device Connectivity Products (DA Servers)

Thursday, February 23, 2012

Automatic Email Notification of InTouch Patches & Updates

This article details how to setup automatic email notifications when there is a new InTouch patch, service pack, or version. This can be helpful to stay up to date or help with regulatory compliance. Setting up these notifications is a two-step process.

1. Set up Wonderware email notifications of new software downloads. You cannot select just InTouch notifications however--you get all products.


2. To counter that, use Outlook to filter out unrelated notifications, leaving only InTouch notifications.


Step 1:

- Go to wdn.wonderware.com then navigate to Downloads -> Software Downloads

- In the right side of the page click 'Alert me when Updated'. This opens the New Alert page.

- In the section 'Send Alerts For These Changes', select the radio button 'Someone changes an item that appears in the follow view.'

- In the pulldown under this entry, change 'Demo Applications' to 'Software'.

There are a few other preferences you can set. When done configuring click 'OK' and you will begin getting notifications.


Step 2:

Outlook's Rules feature can be configured to filter all the software updates to only InTouch.

- Launch Outlook then navigate to your Inbox.

- Navigate to Home -> Rules -> Manage Rules & Alerts

- Click on 'New Rule'

- A rule can be set up many different ways, but one example is to move all emails with the subject containing 'Downloads -', and does not contain 'InTouch' to the trash. Below is a screenshot of that example.

Tuesday, January 31, 2012

How do you connect GE's new Ethernet based CPU?

The new CPE305 has a new way to connect to via Ethernet straight out of the box. Instead of using a utility and pushing an address into it, you can simply use the factory address of 192.168.0.100. Once online with the CPU you can change the target address as needed.

There are two alternative methods to get online with a new CPE305 as well:

Use a configured Ethernet module (IC695ETM001) in that same rack and download an address into the CPE305 via the ETM.

Use a serial cable (IC693CBL316) to download into the CPE305.

The CPE310 has the same Ethernet setup as the CPE305. The main connectivity difference is the number of serial ports. Similar to the classic CPU310, it has one 9 pin port as well as one 15 pin port.

Keep in mind the CPE310 can be loaded with a CPU310 configuration which makes migration much easier. This allows you to use your Machine Edition with versions back to 5.5 SP1.

Monday, November 28, 2011

System Platform 2012

Customer First members may now download the new 2012 versions of System Platform and InTouch from the Wonderware Developer Network. Temporary licenses are available, with upgrade licenses available by Dec 5.

All System Platform applications now share a common installation from a single DVD with a new simplified "role"-based paradigm.

Some key features and enhancements:


  • "ShowGraphic" script function to show/hide symbol using scripting, and pass custom properties to other symbols.


  • "GetWindowName" script function to return currently displayed window.


  • Improved screen resolution management reduces need to convert resolutions.


  • Terminal Server multiple monitor support.


  • Terminal Server load balancing across CPUs/cores.

  • Faster window draw times in WindowViewer.


  • Faster I/O binding in graphics for ArchestrA graphics.


  • InTouch Tag Viewer (ObjectViewer for InTouch) replaces wwclient.


  • InTouch Window preview thumbnails.


  • Smart memory caching of windows based on most frequently shown.


  • SmartCard support for login/logoff.


  • Support for Embedded Standard Windows 7 for WindowViewer.


  • High-Availability and Disaster Recovery via Hyper-V.


  • Remote Desktop App support (allow access to only specific programs, such as WindowViewer).

Customer First members may download from here.