Module Parameters for CCP

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.

Defines whether the address is calculated by the ECU or by INCA.

• by ECU

  The address is calculated by the ECU. This is the default.

• by Tool

  The address is calculated by INCA.

The page switching feature in INCA allows you to select access to the reference or the working page. This means that the data of the two pages, depending on the implementation of the ECU architecture, may be located at different addresses. However, the ECU description file (A2L) contains only one address. It is usually the ROM address of the production version.

Now there are two ways to implement the address access to the data on the second page:

Either the ECU modifies the address depending on the active page, or the calibration system (tool) does this.

Typical implementations perform the address calculation on the ECU side, which is reflected also in the INCA default setting. However, there are also implementations that require an address calculation on the tool side. If this is the case for the ECU at hand, the setting must be modified accordingly.

Within the ECU description file (A2L), there is no way to define the behavior.

Defines whether access to the ECU is necessary for measuring tasks.

In the Value column, double-click the field next to the Measurement privilege line and enable Privilege is required.

To obtain access to the ECU for measuring tasks, you also have to select the corresponding DLL in the DLL for measurement privilege field.

Defines whether access to the ECU is required for calibration tasks.

In the Value column, double-click the field next to Calibration privilege, and enable Privilege is required.

To obtain access to the ECU for calibration tasks, select a DLL in the DLL for calibration privilege field.

Defines whether assess to the ECU is required for programming tasks.

In the Value column, double-click the field next to Programming privilege, and enable Privilege is required.

To obtain access to the ECU for programming tasks, select a DLL under DLL for flashing privilege.

Shows the name of the DLL used to authorize you to access measurement tasks.

To select a different DLL, double-click the Value column next to the DLL for measurement privilege line.

Shows the name of the DLL used to authorize you to access calibration tasks.

To select a different DLL, double-click the Value column next to the DLL for calibration privilege line.

Shows the name of the DLL used to authorize you to access programming tasks.

To select a different DLL, double-click the Value column next to the DLL for flashing privilege line.

Defines the expected slew rate.

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

Select here the interface for flash programming using the integrated tool ProF.

The selection is independent of the employed hardware.

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.

Defines the preparation mode of the ECU for the quick start measurement (e.g., for cold starts).

• Quick start off

  No cold start or quick start measurement possible. No additional parameters are available.

• Save configuration (extended CCP)

  This is a special method that is an extension to the CCP standard. Detailed information is available on request from the INCA hotline.

• Save configuration (Suspended Mode)

  A quick start functionality described in the CCP specification as an optional method. INCA supports this method. To check whether the saved configuration in the ECU matches the configuration of the experiment environment, the method has been enhanced by an extension. When configuring the measurement, an identifier is also written to the ECU. It is stored in the EIS. The EIS is an extension of the CCP standard. It is an information block that is exchanged using the "Exchange_ID" command when connecting the ECU. Detailed information on the structure and the method is available from the INCA hotline.

• Resume (ActServ Write/Read)

  Resume mode with configuration consistency check method action service write/read.

  With this variant in the quick start configuration, INCA uses a CCP Action Service to write a configuration ID to the ECU.

  At the start of the quick start measurement, a CCP Action Service reads the ID in the ECU.

  A comparison of the ECU ID with the ID stored in the experiment ensures that data capture is consistent.

  This method must be supported by the ECU.

• Resume (ActServ Write/Check)

  Resume mode with configuration consistency check method action service write/check.

  With this variant in the quick start configuration, INCA uses a CCP Action Service to write a configuration ID to the ECU.

  At the start of the quick start measurement, a CCP Action Service sends the ID to the ECU again. The ECU checks whether the ID matches the saved ID and sends the result to INCA.

  The comparison of the ECU ID with the ID stored in the experiment ensures that data capture is consistent.

  This method must be supported by the ECU.

Defines that a special mode is used for quick start measurements.

This special mode causes an accelerated receive readiness allowing to receive measured data without delay.

Select this mode only if you want to conduct a quick start measurement.

For normal calibrations, this mode should be disabled.

For the Save configuration (extended CCP) procedure, defines that the programming mode is used for transmitting offline applied data to the ECU before the quick start.

Defines whether all memory areas or only modified memory areas are to be uploaded or downloaded during uploads and downloads.

• Yes

  If an upload or download is to be executed, a checksum calculation is made separately for the individual memory areas. Only the memory areas with different checksums are uploaded or downloaded.

• No

  When an upload or download is invoked, all memory areas are uploaded or downloaded.

Enables/disables calibration access to the ECU.

Enable this function to be able to modify calibration values in the ECU. For pure measurement tasks, you do not need calibration access.

Address offset to be added to the addresses of all calibration variables.

This allows for accessing different variants within a data version.

Enter a value for the Command Processor Busy (CPB) timeout.

If the ECU issues a CPB error (error code 0x10), INCA then uses the (CPB) timeout (overrule timeout) specified here instead of the command-specific timeout.

Enter a value for the maximum number of repeats for the user-specific timeout.

This setting prevents a timeout being triggered every time the ECU sends several CPB replies in response to a CCP command from INCA.

Shows information about this module type.

Shows information about this module type.

Displays information about connected devices found during the hardware search.

Shows information about the driver.

Shows information about the fill level.

Shows information about the manufacturer.

Shows information about the state of measurement.

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.