DISTAB Editor
The DISTAB Editor is only available for (X)ETK types supporting DISTAB.
In the DISTAB Editor you can configure any settings that are related to the DISTAB
Display Table; DISTAB is a method for the acquisition of measurement variables from the ECU. It uses two different tables for each raster: an address table and an output table. The DISTAB address table specifies the ECU addresses of the variables that are to be measured; moreover the address table header contains a flag indicating whether the raster is enabled or disabled, as well as information on the byte size of the variables to be measured. The measurement variables are written to the DISTAB output table. functionality. Which settings are available depends on the DISTAB version being used. The settings apply to a the complete project, i.e. if the project contains more than one device configurations, the settings apply to all devices in the project.
For ETKs, the DISTAB settings will be used for the creation of A2L definitions only; they will not be downloaded to or uploaded from a connected ETK device!
If you download a configuration to an ETK device and upload it again to the PC, the DISTAB settings in the DISTAB Editor will be empty!
Editing the entries in the DISTAB editor may lead to invalid settings or conflicts between certain settings. In this case the corresponding fields are underlaid in red. To correct the settings, modify the entries until they are not marked as invalid any more, otherwise it will not be possible to generate an export file with the A2L entries of the current configuration.
In case the raster size of the current setting is smaller than defined in the DISTAB editor: Adapt the raster size settings in the raster editor according to the requirements. Summarized, the values "Maximum variable per second" and "Maximum bytes per second" must need less or the same than the size specified in the "Event Config Area" and "Event Output Area" box in the DISTAB editor. If there are restrictions in the "Performance Limitations" box, the values must also fit into them.
The DISTAB Editor contains the following sections:
Select the DISTAB version
that will be used in the current project.
For DISTAB versions 13 to 16, no further settings are available.
If you select Disabled, no DISTAB configuration will be created.
Detailed settings for DISTAB version 17
Define the ECU event list address and the table alignment in the Event Config and the Event Output area.
These settings will be used by the MC Measurement and Calibration tool to create the tables accordingly.
Define the start address and the size in bytes of the Event Config Area.
Define the start address and the size in bytes of the Event Output Area.
This section defines the performance limitations of the individual cores of the ECU and/or of the overall ECU. This information is required for cases such as offline experiment configuration.
Use the context menu in this section to add and remove core or overall ECU settings as required. Each core of the ECU is listed as a separate row in the table.
If both individual core and overall ECU performance limitations are defined, all limitations must be observed, i.e. the limitation which is reached first will be applied.
The definition of core and/or overall ECU performance limitations is optional. Performance limitations related to an individual raster are defined in the raster editor.
Enter a number identifying the ECU core.
Enter the maximum number of variables per second that shall be handled by the core.
This indicates the core's maximum performance (in variables) of the total of all rasters.
If you enter the value "0" the core will not be used at all for measurements.
Enter the maximum number of bytes per second that shall be handled by the core.
This indicates the core's maximum performance (in bytes) of the total of all rasters.
If you enter the value "0" the core will not be used at all for measurements.
The following table provides a simple example showing the assignment of some rasters to cores and their performances, as well as the performance for the cores and the complete ECU:
| Raster 1: core=1 | variables/s = 100 | bytes/s = 400 |
| Raster 2: core=1 | variables/s = 200 | bytes/s = 800 |
| Raster 3: core=2 | variables/s = 300 | bytes/s = 1200 |
| Core performance for core 1 | variables/s = 250 | bytes/s = 1000 |
| Core performance for core 2 | not defined | not defined |
| Overall performance | variables/s = 400 | bytes/s = 1600 |
These data can be read as follows:
- The total of rasters 1 and 2 may not exceed 250 variables or 1000 bytes respectively.
- The total of all rasters may not exceed 400 variables or 1600 bytes respectively.
When using dynamic triggering, it must be defined in the A2L file which hardware triggers will be available for MC tasks.
Use the context menu in this section to add and remove hardware triggers as required. Each hardware trigger is listed as a separate row in the table.
Enter the number of the hardware trigger.
Select the type of the trigger used for a raster.
|
Direct |
The hardware trigger is directly associated with the raster, i.e. there is only one raster used for the corresponding hardware trigger. |
|
Indirect |
It is possible to associate multiple rasters with one hardware trigger. |
This field is optional. You can assign an ECU ID to the trigger, which must be unique across all triggers, independent of their type (except for timer triggers, which are not handled by the ECU).
Whether the ECU will write ECU IDs or trigger IDs depends on the ECU code. If the ECU requires ECU IDs, you must define them; in this case, you must assign them to all hardware triggers. It is not possible to assign ECU IDs to only some of the available hardware triggers.
In this section you can distribute the acquisition channels to MC Measurement and Calibration tasks.
The channels are identified by their priority. The higher the number, the higher the priority.
Use the context menu in this section to add and remove channel ranges as required. Each range is listed as a separate row in the table. The ranges may not overlap.
Using a channel for both MC Measurement and Calibration and RP Rapid Prototyping tasks may lead to problems. Make sure that you only use those channels for RP tasks that do not belong to a range defined in this table.
As long as the error symbol 
is shown, the configuration cannot be downloaded
to the (X)ETK device. However, you can generate the corresponding A2L entries if there are no other errors. Saving the configuration is also possible.
Details on the concrete error are given in the Application Log Window.
Defines the first channel of the range.
Defines the last channel of the range.
See also