Actions

Difference between revisions of "VS-OPC Classic for AlphaCom - Release Notes"

From Zenitel Wiki

(Created page with "Category: Release notes Category: OPC '''Release State:''' Released<br/> '''Release Version:''' 6.0.3.1<br/> '''Installation Package:''' VS-OPC Classic for AlphaCom_S...")
 
m
 
(25 intermediate revisions by 5 users not shown)
Line 1: Line 1:
 +
{{A}}
 
[[Category: Release notes]]
 
[[Category: Release notes]]
 
[[Category: OPC]]
 
[[Category: OPC]]
  
−
'''Release State:''' Released<br/>
+
'''Release State:''' Released<br />
−
'''Release Version:''' 6.0.3.1<br/>
+
'''Release Version:''' 6.0.3.13<br />
−
'''Installation Package:''' VS-OPC Classic for AlphaCom_Setup_V6.0.3.1.msi
+
'''Installation Package:''' VS-OPC Classic for AlphaCom_Setup_V6.0.3.13.msi
  
−
= VS-OPC Classic for AlphaCom 6.x.x.x =
+
=VS-OPC Classic for AlphaCom 6.x.x.x=
  
−
== Important Note about Upgrading from version 5.x.x.x. ==
+
==Important Note about Upgrading from version 5.x.x.x.==
 
The AlphaCom OPC server has now been renamed to '''VS-OPC Classic for AlphaCom'''. By default it is now installed in '''C:\Program Files (x86)\Vingtor Stentofon\VS-OPC Classic for AlphaCom''' and the Start menu location is '''Start --> Vingtor Stentofon'''. This is where the shortcut to '''OPC Configurator for AlphaCom''' can be found. It is therefore important to uninstall an AlphaCom OPC server with a version number earlier than 6.x.x.x, before installing this new software.<br>
 
The AlphaCom OPC server has now been renamed to '''VS-OPC Classic for AlphaCom'''. By default it is now installed in '''C:\Program Files (x86)\Vingtor Stentofon\VS-OPC Classic for AlphaCom''' and the Start menu location is '''Start --> Vingtor Stentofon'''. This is where the shortcut to '''OPC Configurator for AlphaCom''' can be found. It is therefore important to uninstall an AlphaCom OPC server with a version number earlier than 6.x.x.x, before installing this new software.<br>
 
It is also required to register the server. In the installation directory right-click '''RegServer.exe''' and select '''Run as administrator'''.
 
It is also required to register the server. In the installation directory right-click '''RegServer.exe''' and select '''Run as administrator'''.
  
−
==VS-OPC Classic for AlphaCom 6.0.3.1==
+
==VS-OPC Classic for AlphaCom 6.0.3.13==
−
===Upgrades===
+
The code was intentionally designed not to send any I/O updates if the station is in a faulty state.
−
The OPC server is now based on .NET 4.6.2
+
This condition has been removed.
−
===Errors corrected===
+
<br>
−
====MTN-1180: OPC: hanging OPC server process====
+
==VS-OPC Classic for AlphaCom 6.0.3.12==
−
In some installations the OPC server would hang or crash. This was solved by upgrading to .NET 4.6.2 and upgrading to the latest Advosol components.
+
The AlphaNet OPC Server does not support configuring an event as a ”Condition”-event. Only “Simple” and “No-Event” are supported. The possibility of configuring “Condition” event has been removed for the AlphaOPCConfigurator application.
−
====MTN-1183: OPC client cannot connect to OPC server after server restart====
 
−
When the server computer running the OPC server is restarted (power failure for instance), the OPC client cannot automatically reconnect to the OPC server.This was solved by upgrading to .NET 4.6.2 and upgrading to the latest Advosol components.
 
−
====MTN-1321: Relay on Turbine not operating from OPC on 12.3.3.2====
 
−
The mapping of outputs has been changed on AMC-IP software 12.3.3.2. The OPC server is now independent of this mapping and will work with all AMC-IP software versions.
 
−
====MTN-1322: Turbine extended not supported in OPC server====
 
−
Turbine Extended has more outputs available than Turbine. These outputs are now also accessible from the OPC server
 
−
====MTN-1356: The station.releatedto item does not show any info after call transfer====
 
−
After a call transfer, the station.relatedto now shows the correct information
 
  
−
For the release notes of AlphaCom OPC Server 5.x.x.x please go to
+
==VS-OPC Classic for AlphaCom 6.0.3.11==
 +
This release solves the issue, that the OPC-Server was not able to reconnect to the ICX-AlphaCom / ICX-core after a link disconnection. The OPC-Server will now constantly try reconnecting after a link disconnection.
  
−
= AlphaCom OPC Server 5.x.x.x  =
+
==VS-OPC Classic for AlphaCom 6.0.3.10==
 +
In this release the following has been changed:<br>
  
−
== Important Note about Upgrading from version 5.0.x.x. ==
+
* LineState typecasted to Byte. Parameter1 typecasted to Int32.
 +
* Attempt to use group message 0 is ignored and not transfered to ICX-AlphaCom.
  
−
Due to bug "{{Bugzilla|406}} OPC Server Windows 7 Compatible", and good programming practices, the location of the OPCServer configuration file needed to be moved from '''Program Data Folder''' to '''Application Data Folder'''.
+
==VS-OPC Classic for AlphaCom 6.0.3.9==
−
It is not implemented any automatic transfer of the configuration file, so after an upgrade either the old config files needs to copied manually to its new location, or the configuration needs to be re-done with the new AlphaComOPCConfigurator tool (v 2.1.3.0).<br/>
+
'''MTN-2849: ICX-AlphaCom VS-SDK unstable 'related station' handling.'''
−
'''Note!''' After a manual copy the configuration should be verified in the new AlphaComOPCConfigurator tool.
 
  
−
== AlphaCom OPC Server 5.4.3.2 (2014-04-29) ==
+
The ’related station’-field for an established connection is cleared in case another station calls one of the participants – gets busy and hangs up. This issue is now fixed.
 +
==VS-OPC Classic for AlphaCom 6.0.3.8==
 +
'''The VS-OPC Classic has been improved by'''
  
−
=== Errors Corrected ===
+
1)    ss.Linestate and cp.Parameter1 is typecasted to UInt32 as the protocol expects.
  
−
==== MTN-495: OPC node status not updated when multiple nodes are involved in AlphaNet====
+
==VS-OPC Classic for AlphaCom 6.0.3.7==
 +
'''The VS-OPC Classic has been improved by'''
  
−
Incorrect Node status and node behavior for Alphanets with eight or more nodes.
+
1)    Making VS-OPC Server able to connect to the the AlphaCom via a remote connection provided by the AlphaNetServiceProvider.
  
−
== AlphaCom OPC Server 5.4.3.1 (2014-03-28) ==
+
2)    Updating the AlphaOPCConfigurator configuration utility for configuration of the remote connection.
  
−
=== Errors Corrected ===
+
==VS-OPC Classic for AlphaCom 6.0.3.6==
 +
'''When the connection from the OPC-server to the AlphaCom fails  and comes back again (either AlphaCom switch off/on, or Ethernet cable unplugged/plugged in again), the OPC-server seems unable to re-establish the link to AlphaCom.'''
  
−
==== MTN-486: Can not delete Call requests after some runtime ====
+
This problem has now been fixed.
  
−
Issue with Signed Mailtag references causes failing of deleting mailtags with value greater then 32768.
+
==VS-OPC Classic for AlphaCom 6.0.3.5==
−
This issue with signed integers in OPC server could also potentially give problem with other OPC features where large numbers are involved.
+
'''Shutdown of OPC-Server in case of no connection to AlphaCom  during startup has been changed.'''
  
−
== AlphaCom OPC Server 5.4.3.0 (2014-03-07) ==
+
The server will now constantly try reconnecting to Alphacom until connection is established or manually closed down.
  
−
=== Functional Enhancements ===
+
==VS-OPC Classic for AlphaCom 6.0.3.4==
  
−
====Added SmartInspect log events====
+
'''Update COS from the OPC-client'''
  
−
Use OPCConfigurator Tool to configure log file name, or use SmartInspect Log Viewer to connect directly to OPC server in run time and view logs.<br>
+
A new station item 'station_cos' has been added. This can be used to set a new COS value for the station.
−
Download [http://www.gurock.com/smartinspect/extras/ Redistributable Console]
 
  
−
=== Errors Corrected ===
+
==VS-OPC Classic for AlphaCom 6.0.3.3==
  
−
====MTN-479: OPC AE: Custom format fails on CallRequest Synchronization events====
+
'''MTN-1832: cr_iterate_command & cr_iterate_station does not match station display'''
  
−
The Custom format for "Call Request" from OPCConfigurator Tool works only for new events. Synchronization of event during OPC connect time, or
+
The order of the call requests in the queue as held by the OPC-server did not always match the order as shown in the station display. This has now been rectified.
−
when writing '0' to the DA .synchronized item will send CallRequest events with default format.
 
  
−
====MTN-439: Sending of OPC Event Stops====
+
==VS-OPC Classic for AlphaCom 6.0.3.2==
  
−
Sending of all OPC Events may stop if OPC Client request Call Request Items in same time as Call Request being updated from AlphaCom
+
'''MTN-759: OPC Config File Location - Config not active running OPC server as a service'''
  
−
== AlphaCom OPC Server 5.3.3.0 (2013-01-24) ==
+
Both the OPCServer Configurator tool, and the OPC Server use the environment variable APPDATA (on windows 7 at least) to get the base location of the config file. 
 +
Really, it uses the .NET Environment API to get the location, so the real env variable might be different on different OSes. 
 +
Still, the idea is that it should use the same location for both applications. We have a reported issue, that when OPC Server is run as a service and configurator tool as normal application, these locations differs. A windows service AppData folder is typically placed under the c:\windows{somewhere} folder.. 
 +
In this case it seems like the AppData env variables returns an empty string..!? Is the server run in some “sandbox environment” with a stripped env?
  
−
=== Functional Enhancements ===
+
.NET code to get folder:
  
−
====MTN-49: OPC Server support for IP-ARIO and Turbine====
+
_defaultConfigFile = Environment.GetFolderPath(Environment.SpecialFolder.ApplicationData) + "
 +
" + 
 +
"STENTOFON\\SDK
 +
" + configFile;
  
−
Number of inputs and outputs updated for stations type IP-ARIO and Turbine Compact Stations.
+
Configuration file is now stored in _defaultConfigFile = Environment.GetFolderPath(Environment.SpecialFolder.CommonApplicationData) +
−
For IP-ARIO also tags are added for statusflags, ackfault and clearfault.
 
  
−
====MTN-142: OPC: Uses old version of DANSrvAE.exe====
+
"\\Vingtor Stentofon\\OPC\\" + configFile;
  
−
Advosol OPC server toolkit updated to latest version 7.0.0.0. Some bug fixes and memory issues fixes.
+
which is c:\ProgramData\Vingtor Stentofon\OPC\configFile;
−
New OPC DA tag now also show the version of the Advosol toolkit used: '''AlphaComOPCServer.AdvosolVersion'''.<br>
 
−
Latest OPC Core Components from OPC Foundation can be used for this release. A download link for OPC Core Components is added to is the "AlphaCom OPC Configurator Tool" in the "About" tab.
 
  
−
=== Errors Corrected ===
+
==VS-OPC Classic for AlphaCom 6.0.3.1==
−
 
+
===Upgrades===
−
====MTN-53: OPC Configurator: Using node "0" gives problems====
+
The OPC server is now based on .NET 4.6.2
−
 
+
===Errors corrected===
−
Node 0 was originally used for simple configuration when only connecting to 1 (local) node.
+
====MTN-1180: OPC: hanging OPC server process====
−
The Node 0 features is not compatible with other updates in the OPC project.
+
In some installations the OPC server would hang or crash. This was solved by upgrading to .NET 4.6.2 and upgrading to the latest Advosol components.
−
Possibility to program node 0 in OPC Configurator is removed.
+
====MTN-1183: OPC client cannot connect to OPC server after server restart====
−
 
+
When the server computer running the OPC server is restarted (power failure for instance), the OPC client cannot automatically reconnect to the OPC server.This was solved by upgrading to .NET 4.6.2 and upgrading to the latest Advosol components.
−
== AlphaCom OPC Server 5.2.3.0 (2011-02-18) ==
+
====MTN-1321: Relay on Turbine not operating from OPC on 12.3.3.2====
−
 
+
The mapping of outputs has been changed on AMC-IP software 12.3.3.2. The OPC server is now independent of this mapping and will work with all AMC-IP software versions.
−
=== Functional Enhancements ===
+
====MTN-1322: Turbine extended not supported in OPC server====
−
 
+
Turbine Extended has more outputs available than Turbine. These outputs are now also accessible from the OPC server
−
== AlphaCom OPC Server 5.2.3.1 (2011-05-09) ==
+
====MTN-1356: The station.releatedto item does not show any info after call transfer====
−
 
+
After a call transfer, the station.relatedto now shows the correct information
−
=== Errors Corrected ===
 
−
 
 
−
===={{Bugzilla|541}}: Station item "Operational" is not reporting "0" when station is disconnected====
 
−
 
 
−
== AlphaCom OPC Server 5.2.3.0 (2011-02-18) ==
 
−
 
 
−
=== Functional Enhancements ===
 
−
 
 
−
==== Added new station OPC item '''.customparameter1''' ====  
 
−
The parameter will enable sending of a custom parameter (16 bit int) from the evnethandler programmed in AlphaPro.
 
−
E.g. @01C7 M7F01 L(1)101 U0 W1200 W0 W0 W0 W0
 
−
 
 
−
== AlphaCom OPC Server 5.1.3.2 (2011-01-04) ==
 
−
 
 
−
=== Functional Enhancements ===
 
−
 
 
−
==== New Informational log Event:  Connecting to AlphaCom {ip}/{port} ====
 
−
 
 
−
== AlphaCom OPC Server 5.1.3.1 (2010-10-10) ==
 
−
 
 
−
=== Errors Corrected ===
 
−
 
 
−
====AE: Custom text format do not work for OPC AE Events (Only default custom texts is used) ====
 
−
 
 
−
== AlphaCom OPC Server 5.1.3.0 (2010-09-17) ==
 
−
 
 
−
 
 
−
Old Configuration file:
 
−
 
 
−
C:\Program Files\STENTOFON\AlphaCom OPC Server\Stentofon.AlphaCom.AlphaNet.Config.OPC.xml
 
−
 
 
−
The location of the new configuration file depends on OS version and other enviromnet setups (using variable '''Environment.SpecialFolder.ApplicationData''').<br/>
 
−
Typical locations:
 
−
 
 
−
WinXP: C:\Documents and Settings\{username}\Application Data\Stentofon\SDK\Stentofon.AlphaCom.AlphaNet.Config.OPC.xml
 
−
Win7 : C:\Users\{username}\AppData\Roaming\Stentofon\SDK\Stentofon.AlphaCom.AlphaNet.Config.OPC.xml
 
−
 
 
−
=== Functional Changes/Enhancements ===
 
−
===={{Bugzilla|227}} OPC DA: No information available telling which station is A- and B-subscriber in a conversation ====
 
−
New tag .callapri, see [[OPC_Server#Station_Item_Table|Station Item Table]]
 
−
====OPC DA: No information available seperating if station is in calling mode (private ringing) or in a conversation (connected) ====
 
−
New tag .callmode, see [[OPC_Server#Station_Item_Table|Station Item Table]]
 
−
 
 
−
===={{Bugzilla|420}} From OPC it should be possible to send alarm messages to groups ====
 
−
Added new nodeX.groups.gx node tree, see [[OPC_Server#Node_Item_Table|Node Item Table]]
 
−
 
 
−
=== Errors Corrected ===
 
−
===={{Bugzilla|362}} OPC DA: Tone Test errors are not reported by the Linestate item====
 
−
New item .tonetest added for indication tonetest errors (The linestate can be OK even if tonetest error)
 
−
See [[OPC_Server#Station_Item_Table|Station Item Table]]
 
−
===={{Bugzilla|330}} AE: Some events are not reported on the selected format ====
 
−
====DA: Only output.1 for IP stations is working output.2 and .3 do not work  ====
 
−
===={{Bugzilla|406}} OPC Server Windows 7 Compatible (64 bit) ====
 
−
* For 64 bit OSs it is required to install the "Advosol OPC Core Components" included in the new Setup package
 
−
* The Config file is moved to the "Application Data Folder".
 
−
* Securtiy exeption when creating new Event Log Source "AlphaComOPCServer" resolved with new function in the
 
−
  AlphaComOPCConfigurator to create the source (requires "run as Admininstrator")
 
−
====DA: Only up 255 stations was reported in the OPC DA item tree. ====
 
−
Now the maximum of stations is 1000 (practical available is 552) 
 
−
<br/>
 
−
 
 
−
= AlphaCom OPC Server 5.0.0.0 (2009-07-01) =
 
−
 
 
−
== Functional Changes/Enhancements ==
 
−
 
 
−
'''Major changes'''<br/>
 
−
*Re-written to use the new '''[[Stentofon.AlphaCom.AlphaNet.dll]]''' library.<br/>
 
−
*Config file name and format is changed with the new library. New config file name: '''Stentofon.AlphaCom.AlphaNet.OPC.xml'''<br/>The [[OPCServerConfigurator]] application will test for old config file, and prompt for automatic conversion to the new format.
 
−
*Implemented '''Redundant OPC''' Server mode allowing two OPC Devices connect to the same AlphaCom nodes. Requires AlphaCom Sys version '''10.55'''
 
−
*The station item '''.relatedto''' is now updated on AlphaCom CallStatus event. The .relatedto property will then be set on calls in private mode, before the call is accepted.
 
−
<br />
 
−
'''Easy Projects Activities'''
 
−
 
 
−
{| {{prettytable}}  class="sortable"  border="1"
 
−
|- style="background: #ffdead;"
 
−
! Activity
 
−
! Short Description
 
−
|-
 
−
| 209
 
−
| Make (IP) station IO items based on ST_STATE messages, make RCO/RCI item obsolete
 
−
|-
 
−
| 210
 
−
|Make global node RCI based on RCI_CHANGED messages incl OPC/RCI config
 
−
|-
 
−
| 211
 
−
| Implemented OPC Items for M-Key, C-Key and DAK-key
 
−
|-
 
−
| 217
 
−
| Updated to use library Stentofon.AlphaCom.AlphaNet.dll
 
−
|-
 
−
| 166
 
−
| Redundant OPC Server
 
−
|}
 
−
<br/>
 
−
'''Limitations'''<br/>
 
−
Global RCI/RCO states is updated on state changes, but '''is not''' synchronized at OPC Server startup.
 
−
 
 
−
== Errors Corrected ==
 
−
 
 
−
'''Easy Projects Activities'''
 
−
 
 
−
{| {{prettytable}}  class="sortable"  border="1"
 
−
|- style="background: #ffdead;"
 
−
! Activity
 
−
! Short Description
 
−
|-
 
−
| 205
 
−
| cr_iterate_command items offset
 
−
|-
 
−
| 206
 
−
| OPC AE: "Station UP" is reported on all ST_STATE changes
 
−
|}
 
−
 
 
−
= AlphaCom OPC Server 4.1.0.0 (2009-04-01) =
 
−
 
 
−
== Functional Changes/Enhancements ==
 
  
−
Added the OPC AE event StationSignal (.signal).<br/>
+
'''MTN-1173: In the OPC configurator About tab there is a link to download OPC core components. This link is no longer valid'''.
−
This event is generated from the station sending a Call Request ("I need attention")
 
  
−
= AlphaCom OPC Server 4.0.0.0 (2008-10-29) =
+
The link now connets to a page from where download of OPC core components is possible.
  
−
First official Release
+
=AlphaCom OPC Server 5.x.x.x=
 +
For the release notes of AlphaCom OPC Server 5.x.x.x please go to [[OPC Server - Release Notes]]

Latest revision as of 14:04, 22 March 2024

AlphaCom icon 300px.png

Release State: Released
Release Version: 6.0.3.13
Installation Package: VS-OPC Classic for AlphaCom_Setup_V6.0.3.13.msi

VS-OPC Classic for AlphaCom 6.x.x.x

Important Note about Upgrading from version 5.x.x.x.

The AlphaCom OPC server has now been renamed to VS-OPC Classic for AlphaCom. By default it is now installed in C:\Program Files (x86)\Vingtor Stentofon\VS-OPC Classic for AlphaCom and the Start menu location is Start --> Vingtor Stentofon. This is where the shortcut to OPC Configurator for AlphaCom can be found. It is therefore important to uninstall an AlphaCom OPC server with a version number earlier than 6.x.x.x, before installing this new software.
It is also required to register the server. In the installation directory right-click RegServer.exe and select Run as administrator.

VS-OPC Classic for AlphaCom 6.0.3.13

The code was intentionally designed not to send any I/O updates if the station is in a faulty state. This condition has been removed.

VS-OPC Classic for AlphaCom 6.0.3.12

The AlphaNet OPC Server does not support configuring an event as a ”Condition”-event. Only “Simple” and “No-Event” are supported. The possibility of configuring “Condition” event has been removed for the AlphaOPCConfigurator application.

VS-OPC Classic for AlphaCom 6.0.3.11

This release solves the issue, that the OPC-Server was not able to reconnect to the ICX-AlphaCom / ICX-core after a link disconnection. The OPC-Server will now constantly try reconnecting after a link disconnection.

VS-OPC Classic for AlphaCom 6.0.3.10

In this release the following has been changed:

  • LineState typecasted to Byte. Parameter1 typecasted to Int32.
  • Attempt to use group message 0 is ignored and not transfered to ICX-AlphaCom.

VS-OPC Classic for AlphaCom 6.0.3.9

MTN-2849: ICX-AlphaCom VS-SDK unstable 'related station' handling.

The ’related station’-field for an established connection is cleared in case another station calls one of the participants – gets busy and hangs up. This issue is now fixed.

VS-OPC Classic for AlphaCom 6.0.3.8

The VS-OPC Classic has been improved by

1)    ss.Linestate and cp.Parameter1 is typecasted to UInt32 as the protocol expects.

VS-OPC Classic for AlphaCom 6.0.3.7

The VS-OPC Classic has been improved by

1)    Making VS-OPC Server able to connect to the the AlphaCom via a remote connection provided by the AlphaNetServiceProvider.

2)    Updating the AlphaOPCConfigurator configuration utility for configuration of the remote connection.

VS-OPC Classic for AlphaCom 6.0.3.6

When the connection from the OPC-server to the AlphaCom fails  and comes back again (either AlphaCom switch off/on, or Ethernet cable unplugged/plugged in again), the OPC-server seems unable to re-establish the link to AlphaCom.

This problem has now been fixed.

VS-OPC Classic for AlphaCom 6.0.3.5

Shutdown of OPC-Server in case of no connection to AlphaCom  during startup has been changed.

The server will now constantly try reconnecting to Alphacom until connection is established or manually closed down.

VS-OPC Classic for AlphaCom 6.0.3.4

Update COS from the OPC-client

A new station item 'station_cos' has been added. This can be used to set a new COS value for the station.

VS-OPC Classic for AlphaCom 6.0.3.3

MTN-1832: cr_iterate_command & cr_iterate_station does not match station display

The order of the call requests in the queue as held by the OPC-server did not always match the order as shown in the station display. This has now been rectified.

VS-OPC Classic for AlphaCom 6.0.3.2

MTN-759: OPC Config File Location - Config not active running OPC server as a service

Both the OPCServer Configurator tool, and the OPC Server use the environment variable APPDATA (on windows 7 at least) to get the base location of the config file.  Really, it uses the .NET Environment API to get the location, so the real env variable might be different on different OSes.  Still, the idea is that it should use the same location for both applications. We have a reported issue, that when OPC Server is run as a service and configurator tool as normal application, these locations differs. A windows service AppData folder is typically placed under the c:\windows{somewhere} folder..  In this case it seems like the AppData env variables returns an empty string..!? Is the server run in some “sandbox environment” with a stripped env?

.NET code to get folder:

_defaultConfigFile = Environment.GetFolderPath(Environment.SpecialFolder.ApplicationData) + " " +  "STENTOFON\\SDK " + configFile;

Configuration file is now stored in _defaultConfigFile = Environment.GetFolderPath(Environment.SpecialFolder.CommonApplicationData) +

"\\Vingtor Stentofon\\OPC\\" + configFile;

which is c:\ProgramData\Vingtor Stentofon\OPC\configFile;

VS-OPC Classic for AlphaCom 6.0.3.1

Upgrades

The OPC server is now based on .NET 4.6.2

Errors corrected

MTN-1180: OPC: hanging OPC server process

In some installations the OPC server would hang or crash. This was solved by upgrading to .NET 4.6.2 and upgrading to the latest Advosol components.

MTN-1183: OPC client cannot connect to OPC server after server restart

When the server computer running the OPC server is restarted (power failure for instance), the OPC client cannot automatically reconnect to the OPC server.This was solved by upgrading to .NET 4.6.2 and upgrading to the latest Advosol components.

MTN-1321: Relay on Turbine not operating from OPC on 12.3.3.2

The mapping of outputs has been changed on AMC-IP software 12.3.3.2. The OPC server is now independent of this mapping and will work with all AMC-IP software versions.

MTN-1322: Turbine extended not supported in OPC server

Turbine Extended has more outputs available than Turbine. These outputs are now also accessible from the OPC server

MTN-1356: The station.releatedto item does not show any info after call transfer

After a call transfer, the station.relatedto now shows the correct information

MTN-1173: In the OPC configurator About tab there is a link to download OPC core components. This link is no longer valid.

The link now connets to a page from where download of OPC core components is possible.

AlphaCom OPC Server 5.x.x.x

For the release notes of AlphaCom OPC Server 5.x.x.x please go to OPC Server - Release Notes

Retrieved from "https://wiki.zenitel.com/w/index.php?title=VS-OPC_Classic_for_AlphaCom_-_Release_Notes&oldid=236016"