*.exe.config

See Also: Sample ODIS.exe.config File

The exe.config file is an XML file created along with the ODIS application. The features referenced in the file are usually set once on installation and left in place. However, as the features may require modification, a user can edit some of the features as needed.

Sections

The file has several subsections, only the appSettings section can be altered by the user.

The exe.config file is used to store configuration information about ODIS and other programs. The file will be named the same as the application, e.g. if the application is "ODIS_NDT.exe", the configuration file will be called "ODIS_NDT.exe.config". The file is an XML file and can be edited in a text editor.

appSettings

AppSettings, i.e. Application Settings, is the section in the file that is used to configure ODIS Server information and to identify the Token File to be used to activate the program. The settings are configured as key/value pairs.

the available keys are as follows:

ServerIP

This defines the IP address used when ODIS is configured as a server.

ServerPort

This defines the port used by ODIS when configured as a server.

ServerID

A User-defined string identifying this instance of ODIS. Can be used to distinguish between ODIS servers if more than one system is present.

BroadcastIP

The IP Address used by the ODIS server to broadcast messages.

RestoreParameters

factory use only

TokenFile

The name of the token file used to activate ODIS. The name must match the Token file name exactly.

Settings that were previously in other files

Recently, ODIS has been updated so most configuration settings are located in the exe.config file. This shows the features that have been imported from those files into the appSettings section:

From ODIS_Config.xml

Dir_Working

Sets the Working directory for ODIS. This is the location where Scan data is stored.
Note: This directory can be overridden by the "Set Working Directory" menu option. See Main Menu.

 <add key="Dir_Working" value="C:\OKOS\ODIS_DATA\Scans"></add>

Dir_Parameters

Sets the Parameters directory for ODIS. This is the location where parameter files are stored.

 <add key="Dir_Parameters" value="C:\OKOS\ODIS_DATA\Scans"></add>

Dir_Temp

Sets the Temporary directory for ODIS. This is the location where temporary files are created. Any files left behind in this directory can be deleted once ODIS exits.

 <add key="Dir_Temp" value="C:\OKOS\ODIS_DATA\Temp"></add>

Dir_Palette

Sets the directory where Palette files are stored.

 <add key="Dir_Palette" value="C:\OKOS\ODIS_DATA\Palettes"></add>

Dir_ScanMath

Sets the directory where ScanMath code is stored. All code in this directory must be compilable by the C# runtime, otherwise errors may occur when using the Scan Math features of ODIS.

 <add key="Dir_ScanMath" value="C:\OKOS\ODIS_DATA\ScanMath"></add>

Dir_Transducers

Sets the directory where Transducer information is stored. This information is edited in the Transducers menu item.

Dir_Reports

Sets the directory where report stylesheets are stored. This includes both Cascading Style Sheets (CSS) and XML transforms (XSLT).

 <add key="Dir_Reports" value="C:\OKOS\ODIS_DATA\Reports"></add>

PRType

This tells ODIS which type of Pulser/Reciever to look for. Most digital P/Rs also require an ODIS_Config section describing the ports used for communication (see Pulser Configuration Settings). Current recognized types are:

Tag	Description
DPR500	JSR DPR500
DPR300	JSR DPR300, all configurations
PR5800	Panametrics 5800
PR5900	Panametrics 5900
DPR002	JSR DPR002, uses special serial control
DPR35	JSR DPR35, uses special serial control
DPR35G	JSR DPR35G
PureView	PureView USB P/R
Shell	Creates a dummy Pulser/Receiver shell for simulation modes
Multi	Used in systems with multiple Pulser/Receivers
None	No Pulser/Receiver window will be displayed

Use “None” or “Shell” if using a Pulser/Receiver that is not controlled digitially.

 <add key="PRType" value="Shell"></add>

PRIOHW

Sets the type of I/O used to communicate with the P/R. Applies to DPR002 and DPR35 only. Ignored for other pulser types. Current values are:

ETH32

Winford ETH32

IO24

Elexol I/O Controller

Other types will be added as supported.

 <add key="PRIOHW" value="ETH32"></add>

PRIPAddress

IP Address with which to communicate with the P/R, or the hardware used to talk to the P/R. The IP address should be in standard format “XXX.XXX.XXX.XXX”, where “XXX” is from 0 to 255.

 <add key="PRIPAddress" value="192.168.1.1"></add>

NumPulsers

If using multiple P/Rs, this lists the number of pulsers expected. If not present, the number of pulsers is assumed to be one.

 <add key="NumPulsers" value="3"></add>

PRPort

Sets the communication (COM) port used to control the digital P/R, for pulser types that use a Serial port. Ignored if using a “Shell” pulser. Current values are:

COMx

Sets the COM port to use, where "x" is the assigned serial port (e.g. "COM3")

Simulate

tells the system to create the control for the pulser but will only simulate hardware communications. If simulation is active the NumPulsers key will be used to determine how many pulsers to simulate, and the PRType key will determine the type of pulser.

 <add key="PRPort" value="COM1" />