Wonderware Application Server provides you the ability to leverage the .NET development language for custom and advanced functionality made available through the ArchestrA Integrated Development Environment (IDE).
Custom Script Function Libraries are integrated with Wonderware Application Server by
- Importing multiple, independent DLLs, or;
- Importing multiple DLLs that have dependencies into the Galaxy.
Wonderware Application Server accommodates importing of multiple DLLs and DLLs with dependencies through the use of aaSLIB files. aaSLIB files make managing multiple DLLs and their dependencies easier by eliminating the need to track multiple DLLs.
Wonderware recently released three new Tech Notes on deploying custom script function libraries in Wonderware Application Server:
Wonderware customers from outside of the Wonderware PacWest distribution area can access the Tech Notes on the Wonderware Support Website.
Below is an example of a stored procedure that will retrieve wide-history data from Wonderware Historian 9.0 (formerly known as IndustrialSQL Server or InSQL):
CREATE PROCEDURE HistoryData
@Tags varchar(500) = ‘[SysDateDay], [SysDateMonth], [SysDateYear]’
–above: @Tags is an optional parameter, value after the equal sign is the default value if @Tags is omitted
SET NOCOUNT ON
DECLARE @SQLString varchar(1000)
SET @SQLString = ‘SET QUOTED_IDENTIFIER OFF ‘
SET @SQLString = @SQLString + ‘SELECT * FROM OPENQUERY(INSQL, ‘
SET @SQLString = @SQLString + + ‘”SELECT DateTime = convert(nvarchar, DateTime, 21), ‘ + @Tags + ‘ ‘
SET @SQLString = @SQLString + ‘FROM WideHistory WHERE wwRetrievalMode = ”Cyclic” AND wwResolution = 1000 AND wwVersion = ”Latest” ‘
SET @SQLString = @SQLString + ‘AND DateTime >= ‘ + CHAR(39) + CAST(@StartDateTime AS varchar(50)) + CHAR(39)
SET @SQLString = @SQLString + ‘ AND DateTime <= ‘ + CHAR(39) + CAST(@EndDateTime AS varchar(50)) + CHAR(39) + ‘”)’ EXEC (@SQLString)
The procedure accepts 3 parameters:
– Start date/time
– End date/time
– optional comma separated list of tag – this parameter allows the procedure to be run for different sets of tags
To install the procedure just run the script above against your Wonderware Historian’s Runtime database from within MS SQL Server Management Studio 2005 (or MS SQL Server 2000 Enterprise Manager).
Below is an example of how to run the command:
EXEC HistoryData ‘20081027 21:04:00′,’20081027 21:07:00’, ‘SysTimeSec, SysDateDay’
The example below retrieves data for tags SysTimeSec and SysTimeDay between Oct 27th, 2008 9:04pm and 9:07pm. But you can also skip the 3rd parameter and run it this way:
EXEC HistoryData ‘20081027 21:04:00′,’20081027 21:07:00’
In such case the procedure will return data for the list of tags specified as the default value of the @Tags variable (in the example below the default value of the @Tags variable is “SysDateDay, SysDateMonth and SysDateYear”.
Wonderware Tech Note 564 “Removing an Undeployed or Deleted Wonderware Application Server’s Galaxy Erroneously Listed in the Wonderware System Management Console, DAServer Manager and Log Viewer” is available.
In some instances when an Application Server’s Platform is undeployed or a Galaxy is deleted, the Galaxy information is not properly cleaned up on all of the Platforms in the Galaxy. When this occurrs a Galaxy may appear in the SMC in DAServer Manager and Log Viewer on a node that no longer has a platform deployed to it from this Galaxy. Unlike Node Groups, Galaxies in the SMC are read-only and cannot be deleted from the SMC.
This Tech Note explains how to remove a Galaxy listed in the SMC DAServer Manager and Log Viewer that should no longer appear.
Click here to review the tech note.
Wonderware IndustrialSQL (InSQL) Historian Server 9.0 Patch02 is available. This patch primarily includes support the following Wonderware Application Server 3.1 features:
- Configure most historization parameters for a tag from within the IDE (e.g. “swinging-door” filters, counter “rollover”, interpolation type, etc.)
- Time propagation from data in Application Server (already supported from IDAS in Historian 9.0)
- “Late” data from Application Server (“late” data from IDAS was already supported in Historian 9.0)
This release also includes several hotfixes for Historian 9.0 Patch01 released over the last ~20 months. The release is reflected on Wonderware PacWest’s Product Version page.
Wonderware Tech Note 563 “Configuring Wonderware FSGateway to Access Historian Data from Wonderware Application Server” is available.
Wonderware IndustrialSQL Server Historian (InSQL) provides an I/O Server called aahIOSvrSvc. This I/O Server is an interface for clients to access data from the Historian. It uses the SuiteLink protocol. The Historian I/O Server is re-configured with a single topic called tagname. The Historian I/O Server listens for clients that are attempting to establish a connection using the pre-configured topic.
Wonderware FSGateway is a communications protocol converter. It is used to link clients and data sources communicating with different communication protocols such as SuiteLink, DDE, FastDDE, and ArchestrA Message Exchange.
This Tech Note provides the step-by-step procedure to:
- Configure the FSGateway to communicate with the Historian I/O Server
- Configure the OPCClient proxy object from the Wonderware Application Server to access data from the Historian / FSGateway OPC Server via OPC protocol.
Click here to review the tech note.