User Options for Data Exchange: Bounds Check Dialog Box

To open this dialog box, click the User Options button and select the Data Exchange tab. On the Data Exchange tab, double-click in the Value field of the Bounds Check option.

INCA can check whether the actual values in the datasets comply with the definitions in the ECU project description file (*.a2l).

As this requires a direct comparison with the entries in the A2L file, checks are only possible for datasets as well as for data exchange files that are linked to an A2L file.

In this tab you can define what shall be checked.

Note
These settings for bounds checks apply both to automatic checks (executed automatically if the INCA user option Online Bounds Check is set to Yes) and to manual bounds checks (executed via the dataset context menu).

Maximum size check
Checks whether the sizes of the values in the dataset exceed the maximum sizes defined in the A2L file (A2L keywords MAX_AXIS_PTS, MATRIX_DIM, NUMBER).
Monotony check
Checks whether simple monotony or the monotony given in the A2L file is violated.
This check works independently of the INCA user option Strict Monotony.
Strict monotony check
CDM delivers an error if monotony is worse than strict monotony or the monotony given in the A2L file.
This check works independently of the INCA user option Strict Monotony.
Hard bounds check
Checks whether the values in the dataset are within the hard bounds.
INCA derives hard bounds violations from the data type check, extended limits check and conversion table check.
Weak bounds check
Checks whether the values in the dataset are within the weak bounds.
INCA derives weak bounds violations from the data type check, lower/upper bounds check and conversion table check.
Data type bounds check
Checks whether the implementation values comply with the data type defined in the A2L file.
This check only applies to data exchange file.
Lower/Upper bounds check
Checks whether the physical values comply with the normal limits defined in the A2L file.
Extended limits check
Checks whether the physical values comply with the extended limits defined in the A2L file (A2L keyword EXTENDED_LIMITS).
Tab limits check
Checks whether the implementation values are covered by the computation table.
Pole limits check
Checks whether the computation method has a pole in the needed range.