Overview – 3rd Party OPC Client
The OPC Client Connector product enabled unlimited local and remote OPC Clients to communicate with a licensed OAS Engine. This design allows unlimited OPC Client connections while maintaining only one OPC connection to the local OPC Servers. This is true for both OPC UA and OPC DA Clients.
All data sources of OAS support read and write access from Classic OPC DA Clients and OPC UA Clients.
This includes but is not limited to the following:
- Allen Bradley PLCs
- Modbus Masters and Slaves
- MTConnect – (Read Only)
- OPC DA Servers
- OPC UA Servers
- Siemens S7 Controllers
- OAS Calculations
- MQTT
- Sparkplug B
- Databases
- Excel
- AWS IoT Gateway
- Kafka
- .NET Applications
- REST API
Networking to remote OAS Engines is also supported.
Any Open Automation Software Tag can be accessed by the Open Automation Software OPC Server. Each licensed Open Automation Software Service provides up to 10,000 OPC DA Client connections through up to 10,000 OPCSystems.NET OPC Servers. The maximum number of OPC UA Client connections to each OAS OPC UA Server is 1,000. Each OAS Engine can also connect to up to 10,000 from each OPC UA Client with built in networking.
Each Tag supports over 800 variables for access from OPC Clients, .Value is the most commonly used.
OPC DA
Classic OPC DA Client communications is provided by installing the OPCSystems.NET OPC Server on every system that has an OPC Client. The OPC Client connection is local to the OPCSystems.NET OPC Server, the OPC Server uses TCP communications to obtain an asynchronous connection with all licensed Open Automation Software Services.
For information on how to interface OPC DA Clients with OAS data, visit Getting Started – OPC DA Client.
OPC UA
Connections for OPC UA Clients is built into the OAS Engine to the endpoint opc.tcp://<Network Node>:58728. An example opc.tcp://localhost:58728. The port number is adjustable.
For information on how to interface OPC UA Clients with OAS data, visit Getting Started – OPC UA Client.