The two configuration fields on the driver’s properties window are:
- Machine Name: name of the machine running the OPC A&E server. To access a host in the local computer, leave this field blank or fill it with “localhost”.
- OPC A&E Server: name of the OPC A&E server. To access it, type this server’s Program ID (the name under which the COM component has been registered) or click Expand to select a server from a list of servers registered in the computer configured as Machine Name.
This driver features two tags, which can be created with the Tag Browser:
- Status (N1:1, N2:0, N3:0, N4:0): returns a String with the OPC A&E server’s current status.
- EventBlock (B1:2, B2:0, B3:0, B4:0, Size: 18): returns an 18-element data block for each alarm or event reported by the server. Each read in this tag can return anything from 0 (zero) to “n” events. The application can access events individually via OnRead event.
The Communication Interfaces are set up at the driver’s configuration dialog. At Elipse E3, click Configure Driver from the driver’s toolbar. At Elipse SCADA, follow these steps:
1. Open the Organizer.
2. Select the driver from the Organizer’s tree.
3. Click Extras on Driver tab.
NOTE: To connect this driver to a remote server, you will need to set up the DCOM permissions (dcomcnfg) both in the computer running the driver and in the computer running the OPC server. Generally speaking, they should be configured as follows: the driver’s computer must grant both local and remote access from IOServer.exe process to users LOGIN ANONYMOUS, SYSTEM, and EVERYONE, and the OPC server’s computer must grant remote access to these same users.
