Actions

OPC Classic for AlphaCom - Installation

From Zenitel Wiki

AlphaCom icon 300px.png
Example configuration: AlphaCom with VS-OPC Classic for AlphaCom Server

This article describes how to install and configure the VS-OPC Classic for AlphaCom Server, and how to test that the server is operational.

Uninstalling the previous version of the OPC server (OPC Server 5.4.3.2 and earlier)

VS-OPC Classic for AlphaCom will by default be installed in a new directory C:\Program Files (x86)\Vingtor Stentofon\VS-OPC Classic for AlphaCom. It will not automatically uninstall or overwrite version 5.4.3.2 or earlier of the OPC Server. It is therefore strongly recommended to uninstall this server before installing VS-OPC Classic for AlphaCom.

Installing VS-OPC Classic for AlphaCom

VS-OPC Classic for AlphaCom is installed on an external Windows computer.

  1. Download the AC_OPC-Server-Classic_Setup software from the download page
  2. Unzip the downloaded file
  3. Install the OPC Server software by double-clicking the unzipped file AC_OPC-Server-Classic_Setup_Vx.x.x.x.msi
  4. The OPC server requires that "Microsoft .NET Framework" is installed. The installation program will check if Microsoft .NET Framework is already installed. If not, you are notified and a link to Microsofts download site is displayed. Follow this link and install .NET Framework (freeware). Then run the installation file AC_OPC-Server-Classic_Setup_Vx.x.x.x.msi again
  5. The OPC server requires that "OPC Core Components" are installed. There are 2 versions available, for 64-bit (x64) and 32-bit computers (x86). The "OPC Core Components" are placed in the installation directory of VS-OPC Classic for AlphaCom, by default this is C:\Program Files (x86)\Vingtor Stentofon\VS-OPC Classic for AlphaCom\Advosol OPC Core Components

Server Deregistration / Registration

Before the OPC-server can be activated via the DCOM it must be registered. The registration is done in the following way:

  • Browse to the folder where your existing OPC server is installed and run UnRegServer.exe as administrator
  • Uninstall existing OPC server from Program and Features in Windows
  • Install new version. It will be installed in Program Files (x86)\Vingtor Stentofon\VS-OPC Classic for AlphaCom
  • Run RegServer.exe
  • Restart PC

It is recommended that the deregistration is done before uninstallation of the existing OPC-server because it will clean up the registry database. 

Configuration

Configure VS-OPC Classic for AlphaCom

  • Start the OPC Server Configuration Tool by selecting Start -> All programs -> Vingtor Stentofon -> AlphaCom OPC Configurator - Please note: The OPC Server Configuration Tool must be run in administrator mode.
  • In the 'main config' tab, enter:
    • AlphaCom IP (must): Enter the IP address of the AlphaCom exchange
    • AlphaCom Port (must): Select one of the 2 available ports 61112 or 61113. Make certain that the port is not in use by another entity, for instance another OPC server or an on the AlphaCom SDK based software package. If a redundant OPC server mode is used, both ports must be assigned, one to each OPC server.
      • Port 61112 -> OPC Device 1 (AlphaCom Device number 199)
      • Port 61113 -> OPC Device 2 (AlphaCom Device number 196)
    • AlphaNet Node List (must): Add the AlphaCom node number with which the OPC Server is communicating (must). In case of AlphaNet, enter the node number of all AlphaCom nodes in the network.
    • Master stations (applicable for OPC DA only): If the OPC client should control an intercom station (e.g. call setup and disconnection controlled from the OPC client), the "Operator station" must be defined in the 'Master Station List'. Use the format node{nn}.station{xxxx} where nn is the AlphaNet node number and xxxx is a station directory number, i.e. node1.station1101
    • Node config (optional): If the OPC client should control RCO's or read RCI's in the AlphaCom, the relevant RCO's/RCI's must be defined:
      • Select a node from the 'AlphaNet Node List'
      • Tick Enable RCO's and select the range of RCO's that should be controlled via the OPC server.
      • Tick Enable RCI's and select the range of RCI's that should be monitored via the OPC server.
      • Tick Enable Local Groups and select the range of RCI's that should be monitored via the OPC server.
The OPC server will now build "OPC items" for the RCO's/RCI's selected.
OPC Server configuration. Here AlphaCom node 1 and 4, and two operator stations are defined as well as RCO/RCI and groups.


Configure the AlphaCom

AlphaCom software requirement: AMC 10.40 or higher. For Redundant OPC Mode: AMC 10.55 or higher.

  • Filter settings: Enable TCP port 61112 in the filter settings in AlphaWeb. If OPC Device 2 is used the port 61113 needs also to be enabled.
    The OPC Server communicates with the AlphaCom over the TCP/IP protocol using this port.
Additional notes:
  • Only physical positions were there is an ASLT board or ATLB board present will consume licenses.
  • Stations which are deleted from the Directory & Features list in AlphaPro will not consume any license.
  • IP stations take API license regardless if the station is registered or not.
  • Individual stations can be disabled from OPC registration, and thus consume no license. This setting is done in AlphaPro. Select Users & Stations > User Preferences > "Disable reporting to OPC server".
  • RCI: In AlphaPro the RCI table has to be programmed for each RCI entry to be monitored by the OPC Server. A $RCIC command has to be sent to the OPC Server(s).
    Examples:
    • Send RCI1 ON to OPC Device 1 on node 3: "@03C7 $RCIC W1 U1"
    • Send RCI2 OFF to OPC Device 1 (199) on node 3 and Device 2 (196) on node 11: "@03C7 $RCIC W2 U0;@0BC4 $RCIC W2 U0"
  • RCO: The RCO state will be automatically sent to the connected OPC Server(s).
AlphaPro RCI Configuration


Testing VS-OPC Classic for AlphaCom

In order to test VS-OPC Classic for AlphaCom you need an OPC test client. The OPC test client might run on the same computer as the OPC Server. VS-OPC Classic for AlphaCom supports two types of OPC standards, OPC AE and OPC DA.

OPC AE (Alarms & Events)

OPC AE is used to receive (read) status information and event reports from AlphaCom. A free test client for OPC AE (Alarms & Events) is installed in the VS-OPC Classic for AlphaCom installation directory.

  • Run the OPC AE test client (AETestClientNet4.exe) by double clicking it.
  • Select Browse Servers. Now Stentofon.AlphaCom.1 should appear in the server list
  • Select Connect. The OPC client will now attempt to connect to the OPC AE Server. A successful connection is indicated by 'Server state' = Running.
OPC AE Client successfully connected to VS-OPC Classic for AlphaCom


  • Open the Event Viewer by clicking Create EventView. Activity (call setup, call requests etc.) in the AlphaCom will show up in the event viewer
  • See OPC Alarms & Events for futher details
The event viewer in the OPC AE Client


OPC DA (Data Access)

OPC DA can send (write) commands to the AlphaCom (call setup etc.), and receive status information from AlphaCom. A free test client for OPC DA is installed in the VS-OPC Classic for AlphaCom installation directory.

  • Run the OPC DA test client (DA3TestClientNet4.exe) by double clicking it.
  • Select Network. Now a list of computers on your network is listed. Select the computer running the OPC Server.
  • Select Browse Servers. Now Stentofon.AlphaCom.1 should appear in the list.
  • Select Connect. The OPC client will now attempt to connect to the OPC DA Server. The text 'Running' in the bottom left corner of the window indicates successful connection to the OPC server
  • Select Browse Items. A list of OPC items appear in the Items table at the right hand side
  • Items with two green arrows are Read/Write (RW), items with one green arrow are Read Only (RO)
  • See OPC Data Access for further details
OPC DA Client - list of OPC items


Example 1: Read the busy/free status of station 1101

  • Select the Read tab in the OPC DA Client
  • Click on station 1101 in the OPC item list
  • Right-click the item 'Busy', and select 'Add selected item to read list'
  • Press the blue button Read
  • The value 0 is returned if station 1101 is free, and value 1 if it is busy
Example 1: Read the busy/free status of station 1101


Example 2: Read connection status of station 1101

  • Click on station 1101 in the OPC item list
  • Right-click the item 'RelatedTo', and select 'Add selected item to read list'
  • Press Read to get the directory number of the station in conversation with 1101 (if any)
Example 2: Read connection status of station 1101


Note! If you enable the Data Chg option next to the Read button, the data is automatically updated without having to press the READ button every time.

Example 3: Initiate a call from station 1101 to station 1111

  • Select the Write tab in the OPC DA Client
  • Click on station 1111 in the OPC item list
  • Right-click the item 'Connect', and select 'Add selected item to write list'
  • Click on the item node1.station1111.connect in the write list
  • A new window appear, enter the value 1 (This value must match the ID of the 'Master station' defined in the OPC server)
  • Press the blue botton Write
  • A call is made from 1101 to station 1111 (Station 1101 was predifined as 'Master station' with ID 1 in the OPC server configuration)
  • To cancel the call, change the value to '0', then press Write
Example 3: Initiate a call from station 1101 to station 1111


Additional information

  • It is possible to have multiple OPC clients open at the same time. For instance one can have both an OPC DA client and an OPC AE client open at the same time, and view in the OPC AE client the feedback of the actions made from the OPC DA client
  • VS-OPC Classic for AlphaCom is running only when an OPC client is connected to it
  • When running it is shown in the Windows Task Manager (Ctrl+Alt+Del -> Task Manager -> Processes): DANSrvAENet4.exe
  • VS-OPC Classic for AlphaCom startup, shutdown, and errors are reported to the Windows Event Log System (Control Panel -> Administrative Tools -> Event Viewer -> Application)

Remote clients

OPC DA/AE communication relies on DCOM.
Matrikon gives this warning: DCOM was developed to function in a specific environment where the following conditions applied:

  • All machines and users belonged to the same domain.
  • There were no firewalls enabled on any machines or network devices.
  • All communication media were highly reliable.
  • There were no bandwidth restrictions.

All of these were typical of a LAN setup in an average office environment; however this bears little resemblance to the process control networks of today. Multiple domains, security-oriented IT policies, geographically-dispersed data sources, and a multitude of other factors all make OPC communication based on DCOM extremely complicated to configure while maintaining security.

There are several guides available on the Internet, but even following these exactly will not guarantee that a remote client will be able to connect to the OPC server. In case of such problems it should be considered to use MatrikonOPC Tunneler. This utility will open a TCP tunnel between client and server which normally will make configuration of the communication setup much simpler. Note that MatrikonOPC Tunneler is not a free tool.

Related articles

MediaWiki spam blocked by CleanTalk.