Creating a Template for a Mapping File: Configuration in ASAP2.ini
INCA supports entries in the ASAP2.ini file that define how a template for experiment conversion will be created from an A2L file. These entries must be placed in an [ExperimentConvert] section in the ASAP2.ini file.
Entries in the ASAP2.ini
Raster Extension
The RasterExtension allows to specify an extension that INCA adds to the name of a raster. Examples:
RasterExtension=
no extension added
RasterExtension=.rasterRenamed
INCA adds the extension .rasterRenamed
If RasterExtension= is missing in the ASAP2.ini file INCA does not add an extension.
Name Extension
The NameExtension allows to specify an extension that INCA adds to the name of the measuement or calibration object. Examples:
NameExtension=
no extension added
NameExtension=.nameRenamed
INCA adds the extension .nameRenamed
If NameExtension= is missing in the ASAP2.ini file INCA does not add an extension.
Source and Destination Device
SourceDevice and DestinationDevice allow to specify a new device for each measurement or calibration object. SourceDevice= specifies the original device, DestinationDevice= specifies the new device. Examples:
DestinationDevice=ES910/Simulations-Controller:1
SourceDevice=ETK test device:1
Device Mapping
The DeviceMapping specifies a general mapping that is valid for all measurements and calibrations. It can be used instead of Source and Destination Device.
If Source and Destination Device is given additionally, then the specification of the source and destination devices is applied.
Example of [ExperimentConvert] section in ASAP.ini
[ExperimentConvert]
RasterExtension=.rasterRenamed
NameExtension=.nameRenamed
DestinationDevice=ES910/Simulations-Controller:1
SourceDevice=ETK test device:1
DeviceMappingSource0=ETK test device:1
DeviceMappingDestination0=ES910/Simulations-Controller:1
DeviceMappingSource1=CCP device:1
DeviceMappingDestination1=ES910/Simulations-Controller:2
See also