Module Parameters for XCPSimTime

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 selected transport layer instance, for example, for ECU on private CAN or on vehicle CAN.

The drop-down list of the Transport Layer Instance parameter provides all Ethernet transport layer with their type as prefix UDP or TCP.

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.

Defines the IP address of the ECU used for communication.

Displays the IP destination port of the Ethernet communication.

Displays the IP source port of the Ethernet communication.

Switches the Ethernet Protocol Type (TCP-IP or UDP-IP) which is used to send Ethernet messages to the ECU.

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.

Determines what information is used if there are inconsistencies between the ECU description file (ASAM-2MC) and the information coming directly from the ECU.

• ASAP2

  The information from the ECU description file (ASAM-2MC) is used.

• ECU

  The information from the ECU is used.

• User

  In conflicting cases, you can select the valid information in a dialog box.

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.

Shows the privileges provided by the selected Seed&Key DLL.

You cannot edit this field.

Shows the name of the checksum DLL used.

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

Defines whether the ECU supports a fast start and whether a fast start is to be made.

In the Value column, double-click the field next to Fast start and enable Fast start enabled.

Wait 10 seconds between switching the ECU off and on again.

Use this field to define the ECU connect mode.

• NORMAL

  The ECU executes its normal code and is enabled.

• USER DEFINED

  The ECU only starts the XCP communication but not its program. This mode can only be used to configure a quick start measurement configuration or to modify the ECU program.

  Note
  The USER DEFINED mode may be customized. Please contact your ECU manufacturer for further information.

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 Ethernet protocol used for sending Ethernet messages to the control device (TCP-IP or UDP-IP).

The counter incrementation can be set in a number of ways. The correct method is dependent upon how the ECU manufacturer has set up the slave device. The following possibilities exist :

• one counter domain for all CTOs+DTOs (RES+ERR+EV+SERV+DAQ)
• one counter domain for RES+ERR+EV+SERV and one counter domain for DAQ
• a separate counter domain for each of RES+ERR, EV+SERV, DAQ

Please select the correct behavior for the slave device. If in doubt, ask your ECU vendor.

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.

• No periodic connection check

  When the connection check is disabled, the GET_STATUS command is not sent to the ECU periodically. Thus, measurement and calibration is possible.

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.

Specifies the byte order that will be used for the checksum calculation. This is necessary to make sure that INCA calculates the same checksum as the ECU itself. The following byte order formats are available:

• Motorola
• Intel
• Use MOD_COMMON

Determines whether OFFLINE_DATA memory segments are included in the checksum calculation.

Setting this option to 'No' restores the behavior prior to INCA 6.2.1.

This is the period of time that INCA will wait after a sleep command before executing a disconnect. This allows INCA to disconnect when the user is not able to press the cancel command. This supports situations when INCA is controlled by another client such as ASAP3 or when the setup is used for the data logger. You can enter values between 0 and 120 s. A value of 0 seconds will mean that there is no timeout applied.

Displays information about connected devices found during the hardware search.

Shows information about the fill level.

Shows information about the manufacturer.

Shows information about the state of measurement.

Shows information about this module type.

Shows information about this module type.

Shows information about the driver.

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.