AlphaNetServiceProvider

This article is under construction. The software described here is not available yet.

Introduction

The AlphaNetServiceProvider is a software component, which makes it possible for more clients to connect to one of the two AlphaCom API ports simultaneously. The ports are named “OPC Server 1” and “OPC Server 2” in the AlphaCom. The ports are assigned the port numbers 61112 and 61113 respectively.

The AlphaNetServerProvider is shipped in two versions

1. AlphaNetServerProviderApp. The AlphaNetServiceProviderApp is a Windows GUI application. The application is used for configuration and test of the AlphaNetService provider
2. AlphaNetServerProviderService. The AlphaNetServerProviderService is a Windows service, which runs in the background without any user interface.

AlphaNetServiceProviderApp

The AlphaNetServiceProviderApp is distributed within the Windows installer package named VS-SDK for AlphaCom_Setup_Vx.x.x.x.msi.

The installation can be checked via Start->Control Panel->Programs and Features:

The program package is installed in directory C:\Program Files (x86)\Vingtor Stentofon\VS-SDK for AlphaCom

The AlphaNetServiceProvider Application is mainly a configuration and test tools added to the SDK for easy employment of the AlphaNetServiceProviderService. The application is started by double click on the AlphaNetServiceProviderAppl.exe

or via Start->All Programs->Vingtor Stentofon->Shortcut to AlphaNetServiceProvider.exe

After invocation push the “Config”-button to check or change configuration data:

Enter the AlphaCom IP-address. Select the port number on the AlphaCom to be used. Legal values are 61112 or 61113.

Choose a Server port number, which the clients must use in order to connect to the Service Provider. The clients must also choose the IP-address on which the service runs. Enter “IPCONFIG” at a command prompt on the server to determine this address.

The “RunTime Config” is the maximum time elapsed for the receipt of a “Pong”-response to a “Ping” before the Service Provider detects client connection down.

If the configuration is changed, push the “Save To File”-button to save the configuration data.

Press “Connect” to start connecting to the AlphaCom. After about 30 seconds the Service Provider has discovered all nodes and stations in the AlphaNet.

Start one of the two test clients (Examples.Stations or Examples.Stations_Basic) from the SDK installation directory or shortcut in the Start Menu.

Push the "Config"-button to check and change configuration data. The IP-Address and port number is the IP connection port to the AlphaNetService Provider. Remember to set check mark in "Remote Connection".

Press the "Connect"-button and after about 30 seconds the discovered nodes and stations are displayed:

The established connection to the AlphaNetServiceProviderAppl is shown in the “Remote Clients” window:

AlphaNetServiceProviderService

The AlphaNetServiceProviderService is distributed as a Windows installer package named AlphaNetServiceProviderService_Setup_Vx.x.x.x.msi.

The installation can be verified via Start->Control Panel->Programs and Features:

The service can be viewed in the list of installed service, which can be shown by pushing

Start->Control Panel->Administrative Tools->Services:

The properties of service can be viewed by right clicking the AlphaNetServiceProviderService and select “Properties”

Right after the installation the service will be in the stopped state, but can be started manually by pushing the “Start the service” option.

Via the “Properties”-window it is possible to select start up type Automatic, which means the service is started automatically at system start up.

The service can be tested using one of the two clients - Example.Stations or Example.Stations_Basic  - as previously described.

Please Note!

1. The AlphaNetServiceProviderAppl and AlphaNetServiceProviderService cannot run simultaneously.
2. The AlphaNetServiceProviderAppl and AlphaNetServiceProviderService use the same configuration. The configuration is handled in the AlphaNet DLL, which stores configuration files in “C:\Users\”actual user”\AppData\Roaming\STENTOFON\SDK”. This directory cannot be accessed by the service – it will raise an exception – and therefore the config window in the application will also store a copy in “C:\ProgramData\STENTOFON\SDK Service Provider” to be used by the service. Please check if this configuration file is available – otherwise make a copy manually.