To configure VTS to work as an OPC Server you will need:
A VTS license key that includes the OPC Server option. Contact your account representative.
A configured OPC Server Setup tag. See the following discussion.
Security. Please refer to the topic: Securing an OPC Server.
Example: Configuring a VTS application to include an OPC Server.
Assuming that your VTS license key includes the OPC Server option, follow these two steps:
1. From the tag browser, add an OPC Server Setup tag
2. Give it a namespace the name of the application is recommended
Within VTS, no further action is required, but you may wish to secure your application. This is done outside VTS using Windows user and group configuration tools as described in Securing an OPC Server.
Values are updated on change. The client attached to the VTS OPC server need not (and should not) use polling. The fastest update rate supported by the server is 20ms.
Adding an OPC Server tag to a networked application enables the OPC server on every workstation running the application. Clients will need to specify which workstation they are connecting to. Automatic fail-over is not built-in, however you can use the DriverMUX tag to define redundant configuration links.
If your goal is to share live data between separate VTS applications, using an OPC Server and Client combination will provide the most efficient means of transferring that data.