<?xml version="1.0"?>
<configuration>
    <appSettings>
        <!-- Define the folder where the DTM can write data that is not project or instance related -->
        <!-- ============================================================== -->
        <!-- If a relative folder is used it is appended to the user specific or common application data folder of the operating system to specify an absolute folder -->
        <!-- Only one of the following two keys can be used. If both are specified the "UserAppDataRelativeBaseFolder" has priority and "CommonAppDataRelativeBaseFolder" is ignored -->
        <!--<add key="UserAppDataRelativeBaseFolder" value="IO-Link\Generic IO-Link Device DTM"/>-->
        <add key="CommonAppDataRelativeBaseFolder" value="IO-Link\Generic IO-Link Device DTM"/>
        <!-- If an absolute folder is used, this has priority any relative folder is ignored -->
        <!--<add key="AppDataAbsoluteBaseFolder" value="C:\Tmp\IO-Link\Generic IO-Link Device DTM"/>-->
        <!-- If none of the above folder keys is enabled the DTM uses the user specific application data folder and appends "IO-Link\Generic IO-Link Device DTM" to specify an absolute folder -->


        <!-- Define the folder where the DTMs can find the IO-Link DDs to be used -->
        <!-- (if whole key or value attribute is missing, then the subfolder "IO-Link\Generic IO-Link Device DTM\IO-Link DDs" of the common application data folder of the operating system will be used) -->
        <!-- ============================================================== -->
        <add key="DDAbsoluteFolder"/>

        <!-- Switch to control logging output of the DTM. -->
        <!-- Supported values are: Off, Error, Warning, Info, Trace, Debug. Default is "Off" if this key is missing -->
        <!-- ============================================================================ -->
        <add key="LoggingLevel" value="Warning"/>

        <!-- Sets the max logging output file size in bytes of the DTM. The size '0' is the equivalent to a unlimited size-->
        <!-- For a LoggingNumberOfMaxLogFiles greater than 1 the logger will switch to the next file if the LoggingMaxSizeBytes is reached -->
        <!-- 512kb is the default value -->
        <!-- add key="LoggingMaxSizeBytes" value="524288"/-->

        <!-- Sets the amount of files the logger can create for logging output of the DTM. -->
        <!-- 10 files is the default value -->
        <!-- add key="LoggingNumberOfMaxLogFiles" value="10"/>-->

        <!-- The key "LogFormat" sets the format of logging output of the DTM. -->
        <!-- Supported values are: 'LOG_FORMAT_CSV', LOG_FORMAT_XML -->
        <!--     Example: <add key="LogFormat" value="LOG_FORMAT_XML"/> -->

        <!-- The key "LogFormatDetails" sets additional information for the format of logging output. -->
        <!--  For the logFormat LOG_FORMAT_CSV: -->
        <!--    - A character or string can be defined which will be used as separating character (or separating string). If the key is missing a ';' is used as default. -->
        <!--  For the logFormat LOG_FORMAT_XML this two switches are available: -->
        <!--    - 'DEFAULT' -->
        <!--    - 'LOG4NET' -->

        <!-- CSV Example: -->
        <!--   <add key="LogFormat" value="LOG_FORMAT_CSV"/>    -->
        <!--   <add key="LogFormatDetails" value=";"/>          -->

        <add key="LogFormat" value="LOG_FORMAT_XML"/>
        <add key="LogFormatDetails" value="DEFAULT"/>

        <!-- Set the number of the algorithm to be used when building the device type ident information (used for device type assignment after scanning) -->
        <!--                                                                                                                                             -->
        <!-- Algorithms that create a separate <DeviceIdentification> XML element for every device variant (for every product id) -->
        <!-- ==================================================================================================================== -->
        <!-- 1: Uses slG. -->
        <!-- 2: Uses slP. -->
        <!-- 3: Uses slS. -->
        <!--                                                                                                                                           -->
        <!-- Algorithms that create only one <DeviceIdentification> XML element for all device variants. Uses a regular expression for the product ids.-->
        <!-- ========================================================================================================================================= -->
        <!-- 4: Uses slG and publishes all product id(s) combined into a regular expression.-->
        <!-- 5: Uses slP and publishes all product id(s) combined into a regular expression.-->
        <!-- 6: Uses slS and publishes all product id(s) combined into a regular expression.-->
        <!-- 7: Uses slG and publishes the product id with a regular expression that matches everything.-->
        <!-- 8: Uses slP and publishes the product id with a regular expression that matches everything.-->
        <!-- 9: Uses slS and publishes the product id with a regular expression that matches everything.-->
        <!-- 10: Uses slG and omits the product id(s).-->
        <!-- 11: Uses slP and omits the product id(s).-->
        <!-- 12: Uses slS and omits the product id(s).-->
        <!--                                                                                                  -->
        <!-- Definition of support levels (sl) used by the algorithms.                                        -->
        <!-- ========================================================= -->
        <!-- slG: All device type ident informations use "genericSupport" for the support level.  -->
        <!-- slP: All device type ident informations use "profileSupport" for the support level.  -->
        <!-- slS: All device type ident informations use "specificSupport" for the support level. -->
        <!-- Exception: The device type of the minimal IODD *ALWAYS* uses support level "genericSupport". -->
        <!--                                                                                                  -->
        <!-- Adding additional information that is normally treated as NOT APPLICABLE                     -->
        <!-- ================================================================ -->
        <!--  Appending a "+" to the algorithm number (e.g. 6+)  includes additional information into the <DeviceIdentification>.  -->
        <!-- This additional information is: FunctionId, IdHardwareRevision, IdSoftwareRevision.  -->
        <!-- These additional elements are added with a regular expression that matches everything. -->
        <!--                                                                                                                                      -->
        <!-- If this key is missing then the algorithm 1 is used. -->
        <!--                                                      -->
        <add key="DeviceTypeIdentBuilderAlgorithm" value="9+"/>

        <!-- Defines the kind of ComObject to be used for the communication adapter. -->
        <!-- If this value is set to "false" then an MTA ComObject is used. -->
        <!-- If this value is set to "true" then an STA ComObject is used and the adapter partially uses the main thread. -->
        <!-- If this key is missing then value "false" is is used. -->
        <add key="UseSTAForCommunicationAdapter" value="false"/>

        <!-- 2 keys for controlling automatic import of IODDs. Automatic import takes place in context of DTM catalog update by frame application. -->
        <!-- The DTM imports IODDs before publishing the supported device types (via IDtmInformation.GetInformation). -->
        <!-- The IODD Configurator is used to actually perform the import. -->
        <!-- If any of these keys is missing or if any value is an empty string then automatic import is disabled. -->
        <!-- The first key defines the command and options to be used by the IODD Configurator. This provides a maximum flexibility. -->
        <!-- Please refer to the IODD Configurator documentation for details about the command line arguments. -->
        <!-- The second key defines the path of the folder to be used for importing IODDs. -->
        <add key="AutoIoddImportCommand" value="-silent -hvo -addall"/>
        <add key="AutoIoddImportPath" value=""/>

        <!-- 2 keys for controlling automatic import of IODDs. Automatic import takes place in context of DTM catalog update by frame application. -->
        <!-- The DTM imports IODDs before publishing the supported device types (via IDtmInformation.GetInformation). -->
        <!-- The IODD Configurator is used to actually perform the import. -->
        <!-- If any of these keys is missing or if any value is an empty string then automatic import is disabled. -->
        <!-- The first key defines the command and options to be used by the IODD Configurator. This provides a maximum flexibility. -->
        <!-- Please refer to the IODD Configurator documentation for details about the command line arguments. -->
        <!-- The second key defines the filter arguments used for searching and downloading IODDs from IODDfinder. -->
        <add key="AutoIoddImportFromFinderCommand" value="-silent -hvo -addfin"/>
        <add key="AutoIoddImportFromFinderFilter" value=""/>

        <!-- Additional internal interpreter settings -->
        <!-- ============================================================================ -->

        <!-- Ignore stamp checking in the interpreter -->
        <!--<add key="Session.IgnoreDDStamp"/>-->

        <!-- Omit the device identification check when connecting to the physical device -->
        <!--<add key="CommunicationManager.OmitDeviceIdentityVerification" />-->

        <!-- Set the interval for variable read synchronization with the device. If this key is missing a default value is used -->
        <add key="CommunicationManager.VariablesSynchronizationInterval" value="2500"/>

        <!-- Set the interval for process data read synchronization with the device. If this key is missing a default value is used -->
        <add key="CommunicationManager.ProcessDataItemsSynchronizationInterval" value="1500"/>

        <!-- Defines the mode for applying direct write to device for variables shown in the user interface. -->
        <!-- If this value is set to "0" then variables that appear with a button are transfered with direct write (click on button writes the value to device). -->
        <!-- All other variables (appearing with text box or combo box) are transfered within context of a download or upload task only. -->
        <!-- If this value is set to "1" then the behavior of value "0" applies and additionally a special behavior for V_SystemCommand: -->
        <!-- For V_SystemCommand (which is write only) direct write is always used (ignoring if V_SystemCommand is represented with a button or not). -->
        <!-- If this value is set to "2" then the behavior of value "0" applies and additionally a special behavior for all variables declared as write only: -->
        <!-- For all write only variables direct write is always used (ignoring if such a variable is represented with a button or not). -->
        <!-- The default value is "0". -->
        <add key="CommunicationManager.DirectWriteUsageMode" value="1"/>

        <!-- Set the interval for the automatic reconnect in [sec]-->
        <!-- If this key is missing the default value 10sec is used -->
        <!-- The value should be between 5sec and 300sec (5min)-->
        <!-- If the value is set to "0", the reconnect feature will be disabled -->
        <add key="ConnectionController.ReconnectInterval" value="10" />

        <!-- Set the maximum time in [sec] a device needs to connect and verify its identity.-->
        <!-- The value should be between 7 and 300 seconds. The default value is 7 seconds.-->
        <!-- add key="TaskManagerBase.TimeToConnect" value="7" /-->

        <!-- Set the maximum time in [sec] the communication has to wait until a request is declared as timed out.-->
        <!-- If this key is missing the default value 10sec is used -->
        <!-- The value should be between 4sec and 300sec (5min)-->
        <!-- <add key="ResponseReceiverBackend.WaitForResponseTimeout" value="10" />-->

        <!-- Enables or disables the evaluation of the subindex access support to boost the communication speed.-->
        <!-- If the value is set to "true" the communication will transmit complex types in whole blocks.-->
        <!-- The value "false" will enable the evaluation of the "subindexAccessSupported" values from the IODD which will lead to single subindex access if supported. -->
        <!-- The default value is "true". -->
        <add key="Instantiators.DisableSubindexAccessSupport" value="true"/>

        <!-- Applies the mode for initial online tasks on demand. On demand means that the user is asked via message dialog. -->
        <!-- The user is asked in the following situations: -->
        <!-- 1) if the connection state is 'connected' and the user opens the user interface -->
        <!-- 2) if the user interface is open and the connection state changes to 'connected' -->
        <!-- If the value is set to "1" the user will be asked. Depending on the answer initial tasks will be executed or not. -->
        <!-- If the value is set to "0" the user will not be asked and no initial tasks will be executed. -->
        <!-- The default value is "0". -->
        <add key="UserInterfaceManager.InitialOnlineTasksMode" value="0"/>

        <!-- Applies the mode for supporting parallel online tasks. -->
        <!-- If the value is set to "0" then no parallel tasks are allowed. -->
        <!-- If the value is set to "1" then UpLoad, DeviceReplicationRead, DownLoad, DownLoadDifferences is allowed -->
        <!-- even if ReadSynchronizationForVariables or ReadSynchronizationForProcessDataItems are active. -->
        <!-- The default value is "0". -->
        <add key="TaskCoordinator.ParallelOnlineTasksMode" value="0"/>

        <!-- By default 50 event monitor history messages are visible. Minimum is 10 messages, maximum is 250 messages. -->
        <add key="EventMonitorController.HistoryQueueSize" value="50"/>

        <!-- Switch to control whether transmitters fire transmission in progress changed events. -->
        <!-- If these events are disabled then the user interface does not show the green communication arrows in the application and navigation area. -->
        <!--  false = events are disabled -->
        <!--  true = events are enabled -->
        <!--  If this key is missing the default value true is used -->
        <add key="TransmitterBase.TransmissionInProgressChangedEventsEnabled" value="true"/>

        <!-- Forces the user interface to use text editor controls for read only variables that would normally be represented by selection editor controls. -->
        <!-- If the value is set to "true" the usage of text editor controls is forced. -->
        <!-- If the value is set to "false" the editor control will be selected according to the value ranges of the variable . -->
        <!-- The default value is "false". -->
        <add key="TreeListRow.ForceTextEditorForReadonlyVariables" value="false"/>

        <!-- Applies the mode for representation of commands (variables shown with a button control in the user interface). -->
        <!-- If the value is set to "0" then the default representation for all variables is used for commands. -->
        <!-- If the value is set to "1" then a special representation for system commands (V_SystemCommand) only is used: -->
        <!--                            The node name in the user interface is the same as the command name shown on the button control. -->
        <!-- If this key is missing the default value "0" is used. -->
        <add key="TreeListRow.CommandsRepresentationMode" value="1"/>
    </appSettings>
</configuration>
