How can I sync my computer clock to Historian’s computer clock using an ArchestrA Object?

Question: How can I sync my computer clock to Historian’s computer clock using an ArchestrA Object?

Answer: The below script can be inserted into an ArchestrA Object to do the task.

dim netTime = new System.Diagnostics.Process;

netTime.StartInfo.FileName = "net.exe";

'this sets the the local computer's time to be the same as a computer called Hist

' The word Hist can be changed to any computer name, another example would be CompanyAHist.

netTime.StartInfo.Arguments = "time \\Hist /SET /YES";

netTime.Start();

For more information or for customer technical support, visit us at Logic Support. 

Connect to InTouch Applications Anytime

Wonderware  InTouch Access Anywhere is a Web HMI and Mobile SCADA solution that lets you securely achieve great visibility of your plant floor operations - all your graphics, performance, alarms and trends - from any location, with html5 compliant browser.

Mobility Solutions for the Oil & Gas Industry

Wonderware    Giving your mobile and dispersed workforce the support and tools they need to succeed on the job can be a challenge. Unsecured devices, limited manageability, and performance issues can adversely impact productivity, data security, and costs. Today, Schneider Electric, Intel, and Microsoft have partnered to help the oil and gas industry meet those challenging issues, empowering mobile workforces with increased performance capabilities, manageability, and security - anytime, anywhere.

Security and Connectivity in Industrial Automation

If only we could throw a big security blanket over all operations and rest easy knowing that we can prevent attacks, mistakes, and malfunctions.

If only it could be that simple... but as we become more connected to devices, networks, and software our risk increases. In this month's e-newsletter, we focus on how we can gain protection through upgrading, remote access, managed switches and more.

 We would like to hear from you and how your organization minimizes security risk.

Email us.

Best regards,

Jane Mohr   

When it comes to security, choose automation software you can trust Wonderware  What do you look for when you choose an automation software provider? If you are like most people, you have a long list of expectations. Perhaps at the top of that list, you expect automation software to keep your processes and data secure. Ultimately, Wonderware is the only automation software that has the longevity and stability to do just that. With a solid track record, over 25 years in the industry, Wonderware is dedicated to protecting your systems. Take a look at Wonderware System Platform.  It is a highly secure development & deployment environment that can be configured to control system access and user rights, along with tracking system changes by user. It is also supports Microsoft Integrated Security, SmartCard & other security protocols and methods. Since applications are managed from a central location, you do not have to worry about security issues associated with multiple applications running at multiple sites; this significantly reduces the burden on your IT organization. Wonderware is the automation software partner you can trust. See why.

Secure remote access to HMIs, PLCs, and other industrial equipment Secomea  Industrial communications must be deployable, secure, and reliable. With Secomea remote access solutions, you can easily monitor, manage, and service equipment. The solution consists of a control unit at the factory (SiteManager) and a Web or Windows based client (LinkManager) for an engineer or end-user. These two components are tied together via a M2M communication server (GateManager) that is available as both a cloud based service and a stand-alone server. Whether it is programming, controls, logging, infrastructure or all of the above, this remote access solution is secure and hassle-free.

Gigabit cyber security solutions Moxa There are three key vulnerabilities of automation networks:  1)Time-critical applications and data-hungry applications (such as video) have extremely low tolerance for latency.  2)The unsecure Modbus TCP protocol is widely used in industrial automation.  3)Non-industrial-grade cyber security devices can't withstand harsh industrial operating conditions, and will malfunction in those settings. Moxa offers a router/switch solution to minimize these security risks. The EDR-810 is a highly integrated industrial multiport secure router with Firewall/NAT/VPN and managed Layer 2 switch functions. It is designed for Ethernet security applications in sensitive remote control or monitoring networks.

Introducing some new features of Wonderware System Platform 2014

John Doll, from Logic Technical Services, explains some of the transformative graphics that will maximize user experience. Watch this video to see the significantly new content.

Make sure to attend our St. Louis Tech Expo on October 10th to discover more about Wonderware's 2014 release. Learn more and register

Don't Use Platform Killer

Platform killer is an unsupported tool.  Most people believe the tool is supported because it was so widely used, even recommended (out of necessity) by support people.  The necessity has been eliminated in System Platform 2012. Now, platforms remove much cleaner.  There is a supported reliable method for removing a platform.  It is done though the system management console. Here are the steps.

1.) Open SMC – Navigate to Start | All Programs | Wonderware | System Management Console

      2.) Navigate to Galaxy name – In the left pane, find platform manager and expand it.  Click on the name of your galaxy.

3.) Remove Platform – Right click on the name of your plant then select remove platform from the context menu.  This removes the platform from the local computer and only the local computer, no other platforms will be removed.  Your screen will look like the screenshot below at this step.

Please remember to use this supported method.  Platform Killer shouldn’t be used for System Platform 2012 and above.  Platform Killer can create problems requiring a system to be reformatted on 2012 and above.  Even for versions before 2012 it is better to try the supported method first then try Platform Killer. 

Exporting a Wonderware Log File

This document details the steps of exporting a Wonderware log file.

Step 1: Open System Management Console – In Windows search bar type “System Management Console” then launch it.

Step 2: Select the logger – Click on “Log Viewer” in the left pane.

Step 3: Select the relevant computer’s logger – Drill down into logger viewer then drill down into default group then click the relevant machine.  Most likely you are working on the local computer so “local” would be the relevant computer.  Below is a screenshot of what your screen should look like at this point.

Step 4: Filter Data by Time Range – Refer to the above screenshot.  Select the filter icon by the black arrow.  Now select the Time Range time.  Adjust the time range to one day before the issue that occurred to one day after the issue occurred.

Step 5: Select Export – Right click in the left pane on the computer you are working on.  Navigate in the context menu to messages then export.  Click export.  Refer to below screenshot for example.

Step 6: Save the file – Put your company’s name at the start of the filename but leave the rest the same.  Leave the save type the same.  Pick a location to save the file, anywhere you choose, then click save. 

Step 7: Send Log file to Logic tech team -  If the log file is smaller than 10 MB it can be sent through email to the logic person working with you on the issue.  Files greater than 10 MB will not go through Logic’s email servers and will need to be uploaded (you can try zipping a file to get it under 10 MB limit).  To upload a file go here: http://www.logic-control.com/uploadform.php.  The upload is extremely easy to use, no username/password required.  Once the upload is complete, give us a call to review your file. 

Moving DA Server Configuration

It is desirable to move a DA Server configuration from one computer to another via a file. This avoids the process of moving the configuration over by simply looking at the original DA Server. The risk of a manual move is that a configuration will be missed. You would then by faced with all of the challenges of integrating a DA Server with a device, leading to hours of work being lost. To avoid the risk of losing hours of work follow the simple steps below.

1. On source machine goto SMC->DAServer Manager->Default Group->local->Archestra.[DA Server Manager Name].[x]->Right Click On Configuration->Click Archive Configuration Set

2. Give a meaningful name to the configuration set. An example would be "DASABCIP_10_9_2013". DASABCIP indicates which DAServer it is and 10_9_2013 indicates the date.
3. Copy the configuration set from the source machine to media like a flash drive. The configuration set can be found in this location:
   C:\ProgramData\Wonderware\DAServer\[DA Server Name]\[Configuration Set Name].aaCFG
4. The file just copied to media needs to be copied to the destination machine. Copy it to the same location it was copied from in Step 3.
5. Deactivate the DAServer on the destination machine you want to restore the configuration set to.
6. Right click on configuration like in Step 1. Then select "Use Another Configuration Set" and select the name you gave the configuration set in Step 2.
7. Activate the DAServer

Trend Live Mode Refresh Interval

To reduce load on your Historian server, change your live trend’s refresh interval.  By default the live trend will refresh itself every 1 second.  Generally every 5 seconds will be satisfactory.  Just right click on your trend area and select properties.

The refresh interval setting is the first one on the “General” tab.

Time Sync

           Computer clocks don’t keep perfect time and tend to drift.  Since Wonderware Software products are real-time systems it is important to keep the time correct to avoid problems like data loss, incorrect data, and a variety of other problems.  Such problems can be prevented by implementing a time sync strategy.

           There is a wide range of time sync strategies ranging from enabling the domain controller’s time sync feature to relying on a feature of Historian that is on by default.  The one strategy that stands out from the crowd is using a command line program called net time.  It is the simplest to implement and works better than the rest.

             Implementing net time is as simple as creating a Windows Scheduled Task to run the command “NET TIME \\Historian /SET /YES” every hour on all control system PCs except the PC selected to be the time master.  The time master PC should sync to an atomic clock either through the Internet or an NTP time server available on the LAN.  If there is a Historian in the system it is the preferred time master.  For screenshots on implementing net time refer to Wonderware Tech Note 882.

             If you are using System Platform it would be good to consider implementing net time inside of an object.  The advantage is maintenance.  A small problem of having a Windows Scheduled Task is when replacing the PC years later the Windows Scheduled Task might be forgotten and not migrated to the new PC.  The Windows Scheduled Task isn’t remembered again until there is a problem with time synchronization and it has to be troubleshot/re-implemented.  This problem can be avoided by implement net time inside a platform object, this way it is automatically deployed to the computer.  Even the potential problem of the time master’s computer name changing could be dealt with by doing some engineering. For example, you could place an attribute on the platform called “TimeMasterName” and use that when calling net time.

             It is important to turn off other time sync tools when implementing net time.  When multiple time sync tools are on they tend to conflict.  Below is the list of commonly used time sync tools on systems.  Exactly how to disable them varies between versions, but a quick Google search can look up disabling methods.

• ·         Windows Automatic Time Sync to Internet

• ·         VMWare’s Time Sync

• ·         Hyper-V’s Time Sync

• ·         Historian’s SuiteLink Time Sync (found in the system parameters)

• ·         The Domain Controller’s Automatic Time Sync (off by default)

Helpful Links

Wonderware Tech Note 882 on using net time.  Note that it isn't necessary to make a batch file like the tech note does, a windows scheduled task can run net time commands without a batch file: https://wdnresource.wonderware.com/support/kbcd/html/1/t002685.htm

Microsoft article for Synchronizing to an atomic clock: http://www.microsoft.com/resources/documentation/windows/xp/all/proddocs/en-us/windows_date_it_overview.mspx?mfr=true

Prepare Windows 7 for Wonderware Products

Installing Wonderware products to a computer has gotten far easier with the new one-disk install. There are a few things, however, the OS needs set as a best practice before installation.

Step 1 
Disable Data Execution Prevention: bcdedit.exe /set {current} nx AlwaysOff

Step 2 
Disable User Account Control: Control Panel, User Accounts, User Account Control, and lower the slider to the bottom. This will require a computer restart.

Step 3 
Firewalls can keep a computer safe from intrusions. They also hinder Wonderware communications if left with default settings. Either shut your firewall completely off or add a series of exceptions:

InTouch

• slssvc.exe
• wm.exe

InSQL or Historian

• InSQLData.exe
• InSQLConfig.exe
• InSQLSCM.exe
• InSQLRet.exe
• SQLServr.exe

General Ports

• 445 tcp
• 1434 udp
• 1433 tcp
• 135 tcp
• 102 DAS SI Direct
• 502 DAS MBTCP
• 2221 DAS ABTCP
• 2222 DAS ABTCP
• 2223 DAS ABTCP
• 5413 S/L DA Servers
• 44818 DASABCIP

For more details, visit the Security Settings for Wonderware Products pdf.
Now you're ready to begin Wonderware installation.

Top Ten Things To Do If You Get Wonderware System Platform Communication Errors

1.Reset the ArchestrA Network Services Account. This is the #1 reason.

2.Software version or patch level different between machines. All must be identical, down to the patch level.

3.Multi network cards? Check the bind order. Move the NIC used for platform communication to the top of the list.
4.Ports might closed. Run the OSConfiguration utility to open them in the Windows firewall.

5.Make sure Simple File Sharing is turned OFF.
6.DNS resolution issues. Try using IP address or host file instead.

7.Anti-Virus software. Check the Application Server Readme file for a list of folders to exclude.

8.DCOM issues. Kind of involved. See Wonderware Tech Note 461 or call us.

9.None of that helped, what next? On the GR node, turn the Galaxy Repository (aaGR) service OFF, then back ON.

10.Still nothing? Bummer. It's time to call us at 913-254-5000 or email support@logic-control.com.

In Search Of... Missing Time & Date Tags in Wonderware ArchestrA Symbols

Some of the InTouch system tags that do not exist in ArchestrA symbols relate to time and dates. Here's a quick tip on where to find them.

Step 1: Launch your Quick Script Editor.
Step 2: Click F(x) to list functions.

Step 3: Expand the 'Types' category and you'll be able to explore Microsoft's .NET System Namespace.
You'll find a number of familiar properties.

Here is a list of InTouch system tags and their equivalent .NET property:

$Month	System.DateTime.Now.Month
$Day	System.DateTime.Now.Day
$Year	System.DateTime.Now.Year
$Hour	System.DateTime.Now.Hour
$Minute	System.DateTime.Now.Minute
$Second	System.DateTime.Now.Second
$TimeString	System.DateTime.Now.ToString("hh:mm:ss")
$DateString	System.DateTime.Now.ToString("mm/dd/yyyy")

In addition to replacements for the classic InTouch time/date tags, you'll also find new properties and methods such as:

DayOfWeek

returns the day of the week (integer)

Add

adds incremental time to an existing time value (also AddDays, AddHours, etc)

DaysInMonth(month)

returns how many days are in the specified month

Compare

compares two datetimes and returns =, <, >

ToString

converts datetime value into a string equivalent (see table above)

To see more information about the .NET System Namespace, check out:

http://msdn.microsoft.com/en-us/library/yxcx7skw.aspx

Corporate Energy Management from Wonderware

by Drew Siebert, PE

Wonderware recently released a new application for System Platform which helps sustainability professionals and plant managers better understand their energy usage and take steps to control it.  Not only will this product allow you to monitor and alert based on your instantaneous peak demand and monthly usage, you can also configure it to capture the energy usage per product manufactured.

Imagine the benefits to those setting prices for product of better understanding the per-piece expense of energy required to manufacture that widget.  Or, in today's more sustainability conscious environment, marketing can advertise to users how small the usage is.

Recently some retailers are even requiring partners to capture and report sustainability information.  In 2009, Walmart started polling suppliers for this information and providing it to conscious consumers to help them make better decisions.  Implementing Wonderware's CEM can be a valuable step toward offering valuable information back to Walmart and consumers.

(c) Walmart

The question often asked, is "How is Wonderware Corporate Energy Management different than what we can create on our own through custom code with Wonderware or another SCADA vendor?".  The short answer, is that Wonderware's CEM industry application contains significant quantities of pre-written scripts and reports with drill-down capabilities that would take enormous numbers of man hours to replicate to recreate all of the functionality available from the pre-designed Wonderware Corporate Energy Management Industry Application.

Contact Wonderware Great Plains for a personalized demonstration and assessment of how Wonderware's Corporate Energy Management Industry Application can benefit you.

UGD95N23KGH2