Configuration Files

DataPorter stores the configuration in the following three files:

• CAS.DataPorter.exe.config – a configuration file for main application settings (for details see section: “DataPorter™ configuration file (CAS.DataPorter.exe.config)”).

• XML database file – a configuration file that stores information about servers, tags and operations (for details see topic: “OPC Viewer getting started” or topic: „Using DataPorter/Using OPC Viewer” ).

• XML description file – a configuration file that stores additional information describing tags configured in the XML database file (for details see topic: “ItemDescriber”).

DataPorter™ stores the configuration as an XML file. The default DataPorter configuration file is DemoConfiguration.oses. Default location of this file is:

• Windows 2000/XP/2003: c:\Documents and Settings\All Users\Application Data\CAS\CAS.DataPorter\DemoConfiguration.oses

• Windows Vista, 2008, 7: C:\ProgramData\CAS\CAS.DataPorter\DemoConfiguration.oses

You can edit any configuration file using the OPC Viewer tool.

CAS.DataPorter.exe.config is the main configuration file of DataPorter. Change this file to set advanced features for the application. Find this file in your DataPorter™ directory. Default location is:

"c:\Program Files\CAS\DataPorter\CAS.DataPorter.exe.config"

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

<?xml version="1.0" encoding="utf-8" ?>
<configuration>
  <appSettings>
    <add key="HTTPSoapPort" value="8001"/>
    <add key="TCPBinaryPort" value="8002"/>
    <add key="configfile" value="DemoConfiguration.oses"/>
    <add key="PLCNaN" value="65535"/>
    <add key="MinAvgMax_FrameResponse_management" value="20"/>
    <add key="MinAvgMax_CharacterGap_management" value="500"/>
    <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"/>
    <add key="WaitForFirstGroupUpdateSendInMiliSec" value="1000"/>
    <add key="UseLocalTime" value="False"></add>
  </appSettings>
</configuration>

Each parameter is configured in the following way:

<add key="attribute name" value="value" />

• attribute name – this is an internal name that DatPorter™ software associated with a particular functionality. (Names are not freely configured. Only DataPorter internal names can be used. The example above uses the whole set of available names).

• value – the value of a particular attribute. This value must be in compliance with a particular type of this attribute; below there are listed types that are available and can by changed by any user.

The following parameters must be set:

• configfile – specifies the file, where the communication configuration is stored (the default value is “DemoConfiguration.oses”)

• MinAvgMax_Tag_management – the value indicates the number of tag read operations to be used to update current statistics (for more details see topic: “Using DataPorter™/Item Tab” )

• MinAvgMax_Group_management – the value indicates the number of transition executions in the current group, which are used to update current statistics (for more details see chapter: “Using DataPorter™/Group Tab” for more details)

• MinAvgMax_Group_Read_management – the value indicates the number of group read operations to be used to update current statistics (for more details see chapter: “Using DataPorter™/Group Tab”)

• MinAvgMax_Transition_management – the value indicates the number of operations on transitions to be used to update current statistics (see chapter: “Using DataPorter™/Transaction Tab”)

• PLCNaN – the value that is written to the OPC tag if BAD QUALITY tag should be written. E.g. if we want to copy tag1 to tag2 and tag1 has BAD QUALITY, then the value defined by the PLCNaN will be assigned (written) to tag2

• WaitForReconnectServerInSec – this is a period of time in seconds that a client waits after an error before it tries to reconnect to a server

• HTTPSoapPor, TCPBinaryPort – ports numbers that are used for communication with OPCWSDataAccess webservice (do not change it unless you want to run two DataPorters simultaneously on one PC)

Other parameters such as:

• “MinAvgMax_FrameResponse_management”

• “MinAvgMax_CharacterGap_management”

• “UseLocalTime”

are for internal use only of the runtime library and should not be changed.

You can also edit this file to add problem tracing to DataPorter™ and run software in the “debug” mode (for details refer to topic: “Diagnostic and troubleshooting/Tracing”).