The OPC Client.NET product enabled unlimited local and remote OPC Clients to communicate with a licensed OPC Systems Service. This design allows unlimited OPC Client connections while maintaining only one OPC connection to the local OPC Servers. Also third party .NET data can be added to the real-time database using OPC Windows HMI.NET, OPC WPF HMI.NET, or OPC Mobile.NET, and read only data from databases of SQL Server, Oracle, or Access can be integrated with OPC Recipe.NET. Data from Microsoft Excel can be enabled for read and write functions using OPC Excel.NET. OPC Client.NET eliminates the need for remote DCOM configuration as all communications is performed using .NET, not DCOM.
OPC Client communications is simply provided by installing the OPC Systems.NET OPC Server on every system that has an OPC Client. So the OPC Client connection is local to the OPC Systems.NET OPC Server, the OPC Server uses .NET communications to obtain an asynchronous connection with all licensed OPC Systems.NET Services. Any OPC Systems.NET Tag can be accessed by the OPC Systems.NET OPC Server. Each licensed OPC Systems.NET Service provides unlimited numbers of OPC Client connections through an unlimited number of OPC Systems.NET OPC Servers.
To browse directly to OPC Server on the OPC Systems Service system use the DirectOPC interface when browsing for items.
View the following video presentation on using OPC Client.NET.
View the Quick Start-Third Party OPC Clients section for a quick tutorial on using the OPCSystems.NET OPC Server with third party OPC Clients.