Overview – 3rd Party OPC Client
The OPC Client Connector product enabled unlimited local and remote OPC Clients to communicate with a licensed OAS 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 the .NET Data Connector and read only data from databases of SQL Server, Oracle, mySQL, or Access can be integrated with OAS Recipe.
Data from Microsoft Excel can be enabled for read and write functions using OAS Excel Connector. OPC Client Connector 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 Open Automation Software Services.
Any Open Automation Software Tag can be accessed by the Open Automation Software OPC Server. Each licensed Open Automation Software 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 OAS Service system use the DirectOPC interface when browsing for items.
You can also combine OPCClient.NET with any of the direct drivers in the OAS realtime service including ABLogix, ABClassic, Siemens, Modbus, OPTO, MQTT, and many more to provide direct access to controllers from your OPC Client.