Module Parameters for UDS (Unified Diagnostic Service)

Enter any name for the hardware module.

Specifies how the system should react if the connection between INCA and the hardware module is interrupted at measuring start or during measurement.

• Abort after failure

  The measurement using this hardware module will be terminated in any case of measurement failure (at measuring start or during measurement). The system does not try to reinitialize the hardware module. After the connection has been interrupted, you have to reinitialize manually.

  This option is appropriate when, e.g., the measured values are not essential for the experiment, as the module will be ignored after any failure. This option is the default.

• Abort at start, try again later

  INCA stops measurement of this module in case of failure at measuring start, assuming the module is disconnected or has any systematic problem.

  It continues to try measurement in case of failure during the measurement assuming the failure is temporal and can be resolved via retries.

• Retry always

  INCA continues to try measurement of this module in any case of measurement failure (at measuring start or during measurement).

  This option is useful if you want to conduct quick start or cold start measurements.

This specifies whether timestamps are to be rounded or not.

If rounding is enabled, the precision is determined according the following rule:

Divide the acquisition rate by 10 and round to the next smaller power of 10.

Example:

If the connection between INCA and the hardware module is interrupted and then restored, you can specify whether the required reinitialization is to be done manually or automatically.

• Prompt for reinitialize

  After the connection is restored, a dialog will prompt you whether you want to reinitialize the hardware or not.

  This option is the default.

• Reinitialize automatically

  After the connection is restored, the hardware is reinitialized automatically.

• Reinitialize automatically and download the working page

  After the connection is restored, the hardware is reinitialized automatically. INCA checks whether the checksums in INCA and in the ECU are still equal. If the checksums differ, INCA automatically downloads the dataset to the ECU.

  This option is particularly useful for MCD3 operation, where different checksums resulting from a connection loss would interrupt the operation.

Shows the name of the project used and the current working dataset.

To select a different project or working dataset: in the Value column, double-click the field next to Project/working data.

Shows the name of the reference dataset used.

Shows the difference in bytes between the working dataset and the reference dataset.

You cannot edit this field.

Automatically defines whether the current working dataset is to be the new reference dataset when you close the calibration session or experiment.

• Automatic Flash Back

  The contents of the working page of the ECU are automatically copied to the reference page, and the working page in the database becomes the new reference page.

  During copying, a dialog opens in which you define a name for the new read-only dataset.

• No Automatic Flash Back

  The current working dataset is not saved as the new reference dataset.

Shows the baud rate defined in the current project.

You cannot edit this field.

Defines how the memory page contents for the ECU and the experiment are checked during initialization.

• Always check

  The checksums from the memory page contents for the ECU and the experiment are calculated during initialization.

• Check if needed

  The memory page contents are downloaded directly from the ECU and the experiment during initialization.

• Never check

  The memory page content's checksums for the ECU and the experiment are not calculated during the initialization.

Shows the name of the DLL used to give you access to the ECU.

To select a different DLL: in the Value column, double-click the field next to Seed&Key DLL.

Defines the expected slew rate.

The slew rate is the leading edge of the CAN signal.

Defines the interface used for flash programming using the integrated tool ProF.

The choice depends on the hardware used.

Defines whether a confirmation is necessary before the program switches to the checksum calculation page.

• Yes

  Additional confirmation is necessary before the program switches to the checksum calculation page.

• No

  No additional confirmation is necessary before the program switches to the checksum calculation page.

Determines which device is used for flashing via the ODX interface. You can select from the list any device that is capable of flashing, added to the hardware configuration and that has an ODX project assigned to it.

Determines whether the device is to be used only for measuring and calibration or also for flashing.