NET/ActiveX controls that act as an OPC server for AD instruments. OPC Server for .NET/ActiveX allows you to connect to multiple devices with only one interface. The OPC Server implementation is written in C# and requires an.NET Framework version 2.0, and runs as a separate thread within the control.
{#ijerph-11-03571-f001}
The OPC Server for .NET/ActiveX consists of three components: (1)The OPC server itself, which accepts data from OPC clients, the messages it receives and the response it sends back;(2)The OPC client, which connects to the OPC server and sends data to it, and then receives the response from it;(3)The OPC interfaces that act as the interface between the OPC client and the OPC server, acting as a translator.
OPC Server includes the following features: (1)The ability to interface with multiple instruments at once. Usually, one device is selected, but it is possible to have several in the OPC Server window.(2)The possibility to attach a custom OPC client to communicate with a device.(3)Data can be inserted or removed from the range of the OPC server, and the range of the interface changed accordingly. Once the range of the OPC server has been changed, it can be saved. If the OPC client device does not work within the new range, a warning is given.
In order to connect to a .NET/ActiveX control as an OPC client, users need to install the OPC Server component. This component is available for .NET/ActiveX controls and is included in the OPC Server for .NET/ActiveX component. After the .NET/ActiveX component has been installed, users can choose to add an OPC client. This will connect to the .NET/ActiveX control and create a .NET/ActiveX interface that communicates with the device.
[Figure 2](#ijerph-11-03571-f002){ref-type="fig"} shows the OPC interface for a linear actuator, which is a .NET/ActiveX component and is configured in the ADT. After connecting to the OPC server, the OPC interface component's
Related links:
Comments