CommServer configuration file (CASOpcDaWrapper.exe.config)

CASOpcDaWrapper.exe.config is the main configuration file of CommServer; please find this file in your CommServer directory. Default location is:

c:\Program Files\CAS\CommServer\CASOpcDaWrapper.exe.config

You can edit this file using any text editor. An example of the configuration file is shown below:

XML

Copy

<?xml version="1.0" encoding="utf-8" ?>
<configuration>
  <appSettings>
    <add key="configfile" value="comunicationNetXmlDoc.XML" />
    <add key="MinAvgMax_FrameResponse_management" value="20" />
    <add key="MinAvgMax_CharacterGap_management" value="500" />
    <!-- internal RTLib config part -->
    <add key="PLCNaN" value="65535" />
    <add key="MinAvgMax_Tag_management" value="50" />
    <add key="MinAvgMax_Group_management" value="50" />
    <add key="MinAvgMax_Group_Read_management" value="50" />
    <add key="MinAvgMax_Transition_management" value="50" /> 
    <add key="WaitForReconnectServerInSec" value="30" />
    <!-- end of internal RTLib config part -->
  </appSettings>
</configuration>

The following parameters must be set:

configfile – specifies the file, where the communication configuration is saved (default value is “DefaultConfig.xml”; see next chapter for more details)
MinAvgMax_FrameResponse_management – the value indicates the number of frames when frame response statistics are updated
MinAvgMax_CharacterGap_management – the value indicates the number of characters (bytes) in a communication channel when Character Gap statistics are updated.

Other parameters such as: “PLCNaN”, “MinAvgMax_Tag_management”, “MinAvgMax_Group_management”, “MinAvgMax_Group_Read_management”, “MinAvgMax_Transition_management”, “WaitForReconnectServerInSec” are internal settings of RTLib and should not be changed.

You can also edit this file to add problem tracing to CommServer and run the software in “debug” mode.

Note
On Windows Server 2003 or 2008 the problem with running CommServer may appear (e.g. the OPC Server address space is empty) This issue is caused by missing configuration file. CommServer OPC server executable (CASOpcDaWrapper.exe) is trying to open: “C:\Program Files\CAS\CommServer\CASOpcDaWrapper.config” but this file does not exist. The file that exists in the directory is: “C:\Program Files\CAS\CommServer\CASOpcDaWrapper.exe.config ”. Somehow the system is trying to find .config file (not .exe.config); this situation is different in comparison to the other Windows OS. The solution is to create of a copy of the “CASOpcDaWrapper.exe.config” file and rename the copy “CASOpcDaWrapper.config”. Before reconnection to OPC server make sure that CASOpcDaWrapper.exe is not appear on the task list (in Windows Task Manager). If it is exist please kill the process before reconnection.

Note

On Windows Server 2003 or 2008 the problem with running CommServer may appear (e.g. the OPC Server address space is empty)

This issue is caused by missing configuration file. CommServer OPC server executable (CASOpcDaWrapper.exe) is trying to open: “C:\Program Files\CAS\CommServer\CASOpcDaWrapper.config” but this file does not exist. The file that exists in the directory is: “C:\Program Files\CAS\CommServer\CASOpcDaWrapper.exe.config ”.

Somehow the system is trying to find .config file (not .exe.config); this situation is different in comparison to the other Windows OS.

The solution is to create of a copy of the “CASOpcDaWrapper.exe.config” file and rename the copy “CASOpcDaWrapper.config”.

Before reconnection to OPC server make sure that CASOpcDaWrapper.exe is not appear on the task list (in Windows Task Manager). If it is exist please kill the process before reconnection.