Version history
Current Version: V03.01.01
Release date: 20th February 2006
Additional info:  

Verion history for the CT OPC Server is shown in the table below.

Version Dated Details
V03.01.01 20/02/06

NOTE: Uninstall any previous version of the server before installing this version.

This update is required to correct an error in a 3rd party component included with OPC server, this problem caused certain OPC clients not to update item values. Some spreadsheet parameters incorrectly given read only attributes, are now corrected to read/write.
V03.01.00 24/08/05

This version adds support for CT-TCP/IP (Ethernet) and has many performance improvements and fixes a bug with multiple value writing.

  • Added new thread for handling cache updates so that these can update in parallel to requests, (improves performance in systems where there are many requests from the client).
  • Added i/o queue not empty check so that processing of next request can start immediately after last request completes.
  • Used toolkits reporting rather than polling for client updating, giving a large reduction in CPU load.
  • Added StatusBar showing simple performance information.
  • Fixed bug in multiple value writes.
  • Separated IO handling from windows handling.
  • Installer now includes CTCommsServer V01.01.00 with Ethernet support.
V03.00.01 15/03/05 First full release of the OPC V3 Server
Bug fixed: Synchronious read/wrie group methods return "S_OK" even when not connected to a drive.
Bug fixed: Installer version history page had incorrect caption of "Text"
Changed: Default name space xml file changed back to use "Default.xml"
Changed: Add namespace and VB exampple client links.
Changed: Object list access will provide higher read speeds.
Changed: A menu for setting up and simple diagnostics.
Changed: Better display of version numbers via an about box.
Changed: Ability to set name space file from a dialog box, as well as the command line.
Changed: Ability to save diagnostics strings to a file.
Changed: OPC Version 3 data access is supported (Along with version 2.0 and version 1.0a)
Changed: The server now disables its user interface when started via a clients COM interface.
Changed: The server now uses the CTCommsServer component and so can be used along side SyPTPro CTSoft (V1.5 on).
Changed: All asynchronous reads are cached and rely on data changes pushed in from the CTCommsServer to keep the cache up to date.
Changed: All synchronous reads and all writes use events rather than polling to sequence the transaction.
V03.00.00 07/02/05

Development version 3 of the server, never released.
Bug fixed: Boolean reads are reversed.
Bug fixed: Certain parameters in the Excel namespace tool added addation full stops to the namesapce which confused the server.
Changed: An option in the Excel namespace tool has been added to truncate the namespace produced to a more manageable size using abbreviations.
Changed: There was an incorrect reference in the V2.x.x. help document. This has be rectified along with a new help file.
V02.01.05 07/09/04 Development version never released.
Bug fixed: Bad picture links in th eHTNL help file
Bug fixed: Server canget into a state where it permanently reports FifoBuffersFull (-17)
V02.01.04 16/07/04 Bug fixed: 16 bit fixed point values (eg #3.10 in Unidrive SP) are read incorrectly by the server. Writes work correctly.
Bug fixed: Values such as 0.5 are represented internally as 0.49999... this problem causes the conversion to fail.
V02.01.03 16/06/04 Support added for Unidrive SP and SM option modules.
Several small bug fixes
V02.01.02 29/08/02 First full release of the OPC V2 Server.
There is no change between this version and the beta V2.1.2 version apart from the installer now adds a start menu item for the OPC Server help.
V02.01.02 24/07/02

Beta release
Bug fixed: Boolean writes did not work is written value was true.
Bug fixed: Automation wrapper did not allow group update rate to be set.
Extensive VB Example added to installer with install option
V02.01.01 27/06/02 Beta release
Bug fixed: Occasional erroneous value of zero returned on synchronous reads
V02.01.00 26/06/02

Beta release
Bug fixed: Server thread stops when there is no connection.
Bug fixed: Opcproxy.dll, opc_aeps.dll, Opccomn_ps.dll and Opcenum.exe. were not installed registered correctly.
Bug fixed: Server shut down does not work.
Bug fixed: Server info strings held Softing name and wrong version number
Changed: OPCAutoSofting.dll has been replaced by a new “CTized” automation wrapper CTOPCDAAuto.dll.Internal
OPC compliance test: The server has passed the OPCCompliance test test using the official test software, We expect to have compliance registered in a few weeks after the product is out of Beta.
Testing under Windows XP: We have now tested under windows XP and found no problems.
Tested as remote server: We have tested the server with a remote client on a local network & found no problems. While operation over the Internet is possible it is extremely difficult to set up due to the limitations of DCOM and is not recommended or supported.
Switches added: A specific switch (N) for namespace dignostics printing has been added, a further switch (X) allows temporary overriding of certain registry settings (see help document).
Failure to log on to CTNetAPI: If the server cannot connect to and start the CTNetAPI it will terminate. In this circumstance the server displays the API dialog before shutting down so the user has a chance to fix the API problem.

V02.00.00 17/05/02

First version. Supports OPC DA 2.03 and uses a fixed namespace which is created using a Microsoft Excel spreadsheet.
V01.00.00 19/06/01

The V1 server supported only OPC DA 1.0a.
Last updated: 21 February, 2006
(c) Control Techniques Ltd

Current Version: V03.00.01
Release date: 15th March 2005
Additional info:  

Verion history for the CT OPC Server is shown in the table below.

Version Dated Details
V01.00.00 19/06/01 The V1 server supported only OPC DA 1.0a.
V02.00.00 17/05/02 First version. Supports OPC DA 2.03 and uses a fixed namespace which is created using a Microsoft Excel spreadsheet.
V02.01.00 26/06/02

Beta release
Bug fixed: Server thread stops when there is no connection.
Bug fixed: Opcproxy.dll, opc_aeps.dll, Opccomn_ps.dll and Opcenum.exe. were not installed registered correctly.
Bug fixed: Server shut down does not work.
Bug fixed: Server info strings held Softing name and wrong version number
Changed: OPCAutoSofting.dll has been replaced by a new CTized  automation wrapper CTOPCDAAuto.dll.Internal
OPC compliance test: The server has passed the OPCCompliance test test using the official test software, We expect to have compliance registered in a few weeks after the product is out of Beta.
Testing under Windows XP: We have now tested under windows XP and found no problems.
Tested as remote server: We have tested the server with a remote client on a local network & found no problems. While operation over the Internet is possible it is extremely difficult to set up due to the limitations of DCOM and is not recommended or supported.
Switches added: A specific switch (N) for namespace dignostics printing has been added, a further switch (X) allows temporary overriding of certain registry settings (see help document).
Failure to log on to CTNetAPI: If the server cannot connect to and start the CTNetAPI it will terminate. In this circumstance the server displays the API dialog before shutting down so the user has a chance to fix the API problem.

V02.01.01 27/06/02 Beta release
Bug fixed: Occasional erroneous value of zero returned on synchronous reads
V02.01.02 24/07/02 Beta release
Bug fixed: Boolean writes did not work is written value was true.
Bug fixed: Automation wrapper did not allow group update rate to be set.
Extensive VB Example added to installer with install option
V02.01.02 29/08/02 First full release of the OPC V2 Server.
There is no change between this version and the beta V2.1.2 version apart from the installer now adds a start menu item for the OPC Server help.
V02.01.03 16/06/04 Support added for Unidrive SP and SM option modules.
Several small bug fixes
V02.01.04 16/07/04 Bug fixed: 16 bit fixed point values (eg #3.10 in Unidrive SP) are read incorrectly by the server. Writes work correctly.
Bug fixed: Values such as 0.5 are represented internally as 0.49999... this problem causes the conversion to fail.
V02.01.05 07/09/04

Development version never released.
Bug fixed: Bad picture links in th eHTNL help file
Bug fixed: Server canget into a state where it permanently reports FifoBuffersFull (-17)
V03.00.00 07/02/05 Development version 3 of the server, never released.
Bug fixed: Boolean reads are reversed.
Bug fixed: Certain parameters in the Excel namespace tool added addation full stops to the namesapce which confused the server.
Changed: An option in the Excel namespace tool has been added to truncate the namespace produced to a more manageable size using abbreviations.
Changed: There was an incorrect reference in the V2.x.x. help document. This has be rectified along with a new help file.
V03.00.01 15/03/05

First full release of the OPC V3 Server
Bug fixed: Synchronious read/wrie group methods return "S_OK" even when not connected to a drive.
Bug fixed: Installer version history page had incorrect caption of "Text"
Changed: Default name space xml file changed back to use "Default.xml"
Changed: Add namespace and VB exampple client links.
Changed: Object list access will provide higher read speeds.
Changed: A menu for setting up and simple diagnostics.
Chnaged: Better display of version numbers via an about box.
Chnaged: Ability to set name space file from a dialog box, as well as the command line.
Changed: Ability to save diagnostics strings to a file.
Changed: OPC Version 3 data access is supported (Along with version 2.0 and version 1.0a)
Changed: The server now disables its user interface when started via a clients COM interface.
Changed: The server now uses the CTCommsServer component and so can be used along side SyPTPro CTSoft (V1.5 on).
Changed: All asynchronous reads are cached and rely on data changes pushed in from the CTCommsServer to keep the cache up to date.
Changed: All synchronous reads and all writes use events rather than polling to sequence the transaction.
Last updated: 16 March, 2005
(c) Control Techniques Ltd