OPC Alarm&Event .NET Client Development Component_Develop Controls_Develop Controls Versioning

OPCAE.NET

OPC Alarm&Event .NET Client Development Component

Program OPC A&E .NET clients in C# of VB without the hassle of COM interoperability. The OPCAE.NET assembly provides classes and methods that take advantage of the .NET features and make OPC AE Server access real simple and quick because:

	the OPC functions are provided as methods with an easy to use .NET interface
	the wizards create an application project or add a class with a small OPC AE client that connects to an OPC AE server and displays events.
	the EventView control minimizes coding requirements
	a test simulation server and several sample clients are supplied in C# and VB source code.
	the Visual Studio integrated help contains detailed information including the OPC specifications. Context sensitive help displays the needed information without elaborate searches.
	it can be used for stand-alone OPC AE clients or combined with OPCDA.NET for OPC DA / AE clients or with OPCHDA.NET for OPC Historian / Alarms clients.

EventView Control

The EventView control handles a wide range of OPC Alarms&Events viewing requirements. OPC AE handling can be added in a snap to any Windows form application. Just pull the control from the Visual Studio toolbox to the form and customize the control by setting properties and subscribe to the OPC AE server with a single method call.

The EventView control can show events without allowing user actions.
The displayed event information is selected in the control customization in the Visual Studio Designer. It is also possible to modify control properties from the user application and change the appearance and behavior of the control dynamically.

Optionally visible buttons enable the user to:
- acknowledge events
- delete old events
- display event details
- change the event filter
- modify the display colums

Accessing OPC .NET (Xi) Servers
OPCAE.NET with the OPCAE.NET-Xi option enables clients to access OPC .NET (Xi) servers and Classic OPC AE servers through the same API.
The server ID (ProgID or URL) determines the type of serve accessed.

No external converters are required and DCOM is completely eliminated.

Xi uses secure WCF communication and is specified for efficient wrapping to and from Classic OPC.

Accessing UA Servers
OPCAE.NET with the OPCAE.NET-UA option enables clients to access OPC UA servers and Classic OPC AE servers through the same API.
The server ID (ProgID or URL) determines the type of serve accessed.

No external converters are required and DCOM is completely eliminated.

Features Include
	VB and C# Wizards for quick project creation
	EventView control that eliminates coding needs in many cases
	Works in 32-bit mode and 64-bit mode
	Full source code available
	VB .NET sample clients with VS2012/2010/2008/2005 projects
	C# .NET sample clients with VS2012/2010/2008/2005 projects
	Visual Studio 2012, 2010, 2008, 2005 and 2003 integrated help
	Site license with one time license fee, no royalties.
	Update/Support subscription included for 90 days.

System Requirements
	Windows 8, Windows 7, Vista, XP, Windows 2000, Windows Server 2003/2008 32bit or 64bit
	.NET Famework 1.1, 2.0, 3.0, 3.5, 4.0 or 4.5
	Microsoft Visual Studio .NET 2012/2010/2008/2005, Visual Basic or C#

Accessing UA Servers thru a Converter Server

The COMtoUA converter server enables OPCAE.NET based client applications to access UA servers.

No changes are requird in existing applications.

DCOM communication is used between the client application and the converter and UA communication between teh converter and the UA server.