(error 700) file 'file name': could not open tabbed DDE file for reading, 'error message'.

The interface tool could not read the DDE file named 'file name' and the operating system's reason for not being able to do so is given by 'error message'. Correct the reason for failure and try again.

(error 800) file 'file name': could not open units file for reading, 'error message'.

The interface tool could not read the units file named 'file name' and the operating system's reason for not being able to do so is given by 'error message'. Correct the reason for failure and try again.

(error 900) line 'number' of 'file name': from within the 'compound' statement, there is a missing 'assignment' statement.

The interface tool has read an interface specification file called 'file name' and at line 'number' has found a compound statement with a missing assignment statement called 'assignment'. In this case, the interface tool is expecting the assignment statement to be present (i.e., the assignment statement is not optional).

(error 901) file 'file name': within the interface file, there is a missing 'compound' statement.

The interface tool has read an interface specification file called 'file name' and at line 'number' has found that the file is missing a compound statement called 'compound'. In this case, the interface tool is expecting the compound statement to be present (i.e., the statement is not optional).

(error 1001): line 'number' of 'file name': 'dde name' is an invalid name for a data dictionary entry (must be greater than 3 characters long).

All data dictionary entry names must be greater than 3 characters long. Change the name so it is at least 4 characters in length.

(error 1002): line 'number' of 'file name': 'dde name' is an invalid name for a data dictionary entry (must be less than 256 characters long).

(error 1003): line 'number' of 'file name': 'dde name' is an invalid name for a prefix-style data dictionary entry (must not start with a digit or a '_' character).

To provide compatibility with Simulink, prefix-style DDE names must not start with an underscore. To provide compatibility with Simulink and C compilers, prefix-style DDE names must not start with a digit.

(error 1004): line 'number' of 'file name': 'dde name' is an invalid name for a prefix-style data dictionary entry (must only use characters 'a' through 'z', 'A' through 'Z', '0' through '9' or '_').

Simulink and many C compilers disallow certain characters to appear in signal and variable names. Change the name to avoid the use of these characters.

(error 1005): line 'number' of 'file name': 'dde name' is an invalid name for a calibration map (must end in '_x' or '_y' or '_z').

The tool has recognised that the DDE forms part of a calibration map but does not conform to the rules for naming these entities. See Section 8.2.5, “Naming rules” for more details.

(error 1006): line 'number' of 'file name': 'dde name' is an invalid name for an item which is not a calibration map (must not end in '_x' or '_y' or '_z').

The tool has recognised that the DDE does not form part of a calibration map and does not conform to the rules for naming these entities. See Section 8.2.5, “Naming rules” for more details.

(error 1007): line 'number' of 'file name': 'dde name' is a calibration but has no value.

The entry is a calibration of some sort but does not contain a default calibration value, which it must do.

(error 1008): line 'number' of 'file name': 'dde name' has an invalid value 'text of value'.

The tool could not convert the text of the value into a numeric value. All numeric values must be scalar and represent a real value. The following are examples of valid values: 3.14, 10, 10., .001, 1e8, 3.14e-10, 0e0.

(error 1009): line 'number' of 'file name': 'dde name' must be a vector or a matrix surrounded by '[' and ']').

The tool has recognised that the entry forms part of a calibration map but that the value or values supplied are not valid expressions, either of a vector or of a matrix. Values for an axis (_x or _y) should be given as a vector. Values for the data points (_z) should be given as a vector for 1-d maps or as a matrix for 2-d maps.

(error 1010): line 'number' of 'file name': the row sizes for 'dde name' differ."

The tool requires map axes and map data to match in size. For instance, a 1-d map with 5 elements in the x-axis, requires 5 elements in the z-data. Change the axis and data elements to match in size.

(error 1011): line 'number' of 'file name': the row size for 'dde name' must be at least 2 entries.

The tool requires that map axes and map data have at least 2 elements. For instance, if a 1-d map had 1 element for the x-axis and therefore 1 element for the z-data, the map lookup would be equivalent to a constant block.

(error 1012): line 'number' of 'file name': the row data for 'dde name' must be 1xN matrix.

The tool requires that any map axis be a vector (a 1xN matrix), the OpenECU 1-d and 2-d map lookup blocks do not work with other sized matrices.

(error 1013): line 'number' of 'file name': the units for 'dde name' is too long (must be less than 'number' characters long).

The units field must be less than 32 characters long by default so that it can be exported into other file formats (e.g., ASAP2 file) without issues. Either change the units so it contains less than 32 characters, or change the limit using the Simulink Model Configuration Option 'Maximum data dictionary entry name length'.

(error 1014): line 'number' of 'file name': the units for 'dde name' cannot contain single quote characters.

The units field must not contain single quote characters so that it can be exported into other file formats (e.g., ASAP2 file) without issues.

(error 1015): line 'number' of 'file name': the units for 'dde name' cannot contain double quote characters.

The units field must not contain double quote characters so that it can be exported into other file formats (e.g., ASAP2 file) without issues.

(error 1016): line 'number' of 'file name': the description for 'dde name' is too long (must be less than 256 characters long).

The description field must contain less than 256 characters so that it can be exported into other file formats (e.g., ASAP2 file) without issues.

(error 1017): line 'number' of 'file name': the description for 'dde name' cannot contain single quote characters.

The description field must not contain single quote characters so that it can be exported into other file formats (e.g., ASAP2 file) without issues.

(error 1018): line 'number' of 'file name': the description for 'dde name' cannot contain double quote characters.

The description field must not contain double quote characters so that it can be exported into other file formats (e.g., ASAP2 file) without issues.

(error 1019): line 'number' of 'file name': 'dde name' has an unspecified type (must be one of: int8_T, S8, uint8_T, U8, int16_T, S16, uint16_T, U16, int32_T, S32, uint32_T, U32, real_T, F32, BOOL).

The type of the DDE must be one of the types that MATLAB/Simulink/RTW supports so that simulation and code generation can occur without error. See Section 4.2.2.2, “Data dictionary files” for more.

(error 1020): line 'number' of 'file name': 'dde name' has an invalid type 'type text' (must be one of: int8_T, S8, uint8_T, U8, int16_T, S16, uint16_T, U16, int32_T, S32, uint32_T, U32, real_T, F32, BOOL).

The type of the DDE has been specified but it is not one of the types supported by MATLAB/Simulink/RTW. See Section 4.2.2.2, “Data dictionary files” for more.

(error 1021): line 'number' of 'file name': 'dde name' represents map calibration data and must have a real_T or F32 type.

OpenECU 1-d and 2-d map lookup blocks only work with floating point types (integer types are unsupported in these blocks). Change the type of the map axis or map data to be real_T or F32.

(error 1022): line 'number' of 'file name': 'dde name' has an invalid number 'x' for the accuracy column.

The tool was expecting to find a number in the accuracy field but found something else instead.

(error 1023): line 'number' of 'file name': 'dde name' has a maximum value but no minimum.

The tool expects to see both a minimum and a maximum for the DDE if one or the other is present. The DDE must either have no minimum and maximum specified or both.

(error 1024): line 'number' of 'file name': 'dde name' has a minimum value but no maximum.

The tool expects to see both a minimum and a maximum for the DDE if one or the other is present. The DDE must either have no minimum and maximum specified or both.

(error 1025): line 'number' of 'file name': 'dde name' has an invalid number 'x' for the minimum value.

The tool was expecting to find a number in the minimum field but found something else instead.

(error 1026): line 'number' of 'file name': 'dde name' has boolean type so its minimum must be zero.

The type of the DDE is a boolean, so the minimum value must be zero but the tool found a different value for the minimum field.

(error 1027): line 'number' of 'file name': 'dde name' has an invalid number 'x' for the maximum value.

The tool was expecting to find a number in the maximum field but found something else instead.

(error 1028): line 'number' of 'file name': 'dde name' has boolean type so its maximum must be one.

The type of the DDE is a boolean, so the maximum value must be one but the tool found a different value for the maximum field.

(error 1029): line 'number' of 'file name': 'dde name' has an invalid number 'x' for the scale value.

The tool was expecting to find a number in the scale field but found something else instead.

(error 1030): line 'number' of 'file name': 'dde name' has an invalid number 'x' for the offset value.

The tool was expecting to find a number in the scale field but found something else instead.

(error 1032): line 'number' of 'file name': 'dde name' has a different matrix size from the X-axis matrix size.

The tool has detected that the z-data matrix size in for the x-axis differs in size from the x-axis. The size of the axes and data must match.

(error 1033): line 'number' of 'file name': 'dde name' has a different matrix size from the Y-axis matrix size.

The tool has detected that the z-data matrix size in for the y-axis differs in size from the y-axis. The size of the axes and data must match.

(error 1034): line 'number' of 'file name': 'dde name' has multiple rows but no Y-axis data dictionary entry.

The tool has detected that the z-data for a map contains data for both the x and y axes but no y-axis DDE has been declared.

(error 1035): line 'number' of 'file name': 'dde name' does not have a corresponding X-axis data dictionary entry.

The tool has detected that there is z-data for a map lookup but no corresponding x-axis DDE has been declared.

(error 1036): line 'number' of 'file name': 'dde name' must be a scalar.

The tool has read more than one value for the scalar calibration. Only one value can be specified.

(error 1037): line 'number' of 'file name': an unnamed column was found — skipping entire data dictionary.

The tool has found a column without a name. This can occur if two tab characters are placed next to each other

Name Value Units Description Type Accuracy Min Max Offset Scale Cref

(error 1038): line 'number' of 'file name': column 'name' is only allowed in 'style'-style data dictionaries — skipping entire 'style'-style data dictionary.

The tool has found a column in the title line of the data dictionary that it does not recognise. The only valid column names in a prefix-style data dictionary file are:

Name Value Units Description Type Enums Accuracy Min Max Offset Scale Cref

The only valid column names in a C-style data dictionary file are:

Name Units Description Accuracy Min Max Offset Scale Class Xaxis Yaxis Lookup

(error 1039): line 'number' of 'file name': 'dde name' is an invalid Cref for a data dictionary entry (must not start with a digit).

The tool has found an invalid name for the Cref column. This is an internal error. Please contact OpenECU support.

(error 1040): line 'number' of 'file name': 'dde name' is an invalid Cref for a data dictionary entry (must only use characters 'a' through 'z', 'A' through 'Z', '0' through '9' or '_').

The tool has found an invalid name for the Cref column. This is an internal error. Please contact OpenECU support.

(error 1041): line 'number' of 'file name': 'dde name' is a reserved name for a data dictionary entry (must not use the 'mpl' prefix).

The tool has found a DDE with a name which starts with mpl. This prefix is reserved for OpenECU use. Rename the DDE variable using a different prefix.

(error 1042): line 'number' of 'file name': the 'field_name' field must be present in [style]-style data dictionaries — skipping entire data dictionary.

The tool has found the title line but could not locate all the necessary fields/columns. At a minimum, the following fields/columns must be present in prefix-style data dictionaries:

Name Value Units Description Type Min Max

And for C-style data dictionaries, the following fields/columns must be present:

Name Units Description Class Min Max

In both cases, the Name field must be first.

(error 1043): line 'number' of 'file name': 'dde name' is an invalid [object] name for a data dictionary entry (must be greater than 3 characters long).

All data dictionary entry enumeration names must be greater than 3 characters long. Change the name so it is at least 4 characters in length.

(error 1044): line 'number' of 'file name': 'dde name' is an invalid [object] name for a data dictionary entry (must be less than 'number' characters long).

Some versions of Simulink and some C compilers disallow names that contain more than 31 characters. Some ASAP2 calibration tools disallow names that contain more than 32 characters. Either change the name so it contains less than the character limit, or change the limit using the Simulink Model Configuration Option 'Maximum data dictionary entry name length'.

(error 1045): line 'number' of 'file name': 'dde name' is an invalid [object] name for a data dictionary entry (must not start with a digit or a '_' character).

Simulink and C compilers disallow names that start with a digit or '_' character. Change the DDE name to start with a letter.

(error 1046): line 'number' of 'file name': 'dde name' is an invalid [object] name for a data dictionary entry (must only use characters 'a' through 'z', 'A' through 'Z', '0' through '9' or '_').

Simulink and C compilers disallow certain characters to appear in names. Change the name to avoid the use of these characters.

(error 1047): line 'number' of 'file name': 'dde name' is an invalid [object] name for a data dictionary entry (must not end in '_x' or '_y' or '_z').

The tool has recognised that the referenced enumeration looks like a map DDE. Rename the enumeration reference so it does not end like a map.

(error 1048): line 'number' of 'file name': 'dde name' is a reserved name for a data dictionary enumeration entry (must not use the 'mpl' prefix).

The tool has found a DDE with an enumerated name which starts with mpl. This prefix is reserved for OpenECU use. Rename the DDE variable using a different prefix.

(error 1049): line 'number' of 'file name': 'dde name' uses an enumeration 'enum name' that is not declared in any data dictionary.

The tool has found an enumeration reference for the DDE named 'dde name' that does not exist in any data dictionary. Change the enumeration reference to a data dictionary entry that does exist.

(error 1050): line 'number' of 'file name': 'dde name' uses an enumeration 'enum_name' which has a non-scalar value.

The tool has found a reference to an enumeration which has a non-scalar value. All enumerations must be single valued entries.

(error 1051): line 'number' of 'file name': 'dde name' uses enumerations 'enum_name' and 'enum_name' which have the same value.

The tool has found a data dictionary entry which refers to two enumerations but both enumerations have the same value. Enumerations for one data dictionary entry must have unique values.

(error 1052): line 'number' of 'file name': 'dde name' has a value less than its type allows.

The tool has found a value for a data dictionary entry which has a value outside the range of its type.

(error 1053): line 'number' of 'file name': 'dde name' has a value greater than its type allows.

The tool has found a value for a data dictionary entry which has a value outside the range of its type.

(error 1054): line 'number' of 'file name': 'dde name' must not have a scale value of zero.

The tool has found a DDE with a scaling factor of zero. This is disallowed, as the reciprocal of the factor is used by OpenECU tools and calibration tools.

(error 1055): line 'number' of 'file name': 'dde name' has no corresponding DDE called 'z-data dde name'.

The tool has found a x-axis DDE without a corresponding z-axis DDE, both are needed to create a 1-d map.

(error 1056): line 'number' of 'file name': 'dde name' has no corresponding DDE called 'z-data dde name'.

The tool has found a y-axis DDE without a corresponding z-axis DDE, both are needed to create a 2-d map.

(error 1057): line 'number' of 'file name': 'dde name' is a displayable with a value.

The tool has found a displayable DDE with a value, only calibration DDEs can have values.

(error 1058): line 'number' of 'file name': 'dde name' has a minimum smaller than its type allows.

The tool has found a DDE which has a minimum value less than the type of the DDE can store. The minimum or type must be adjusted.

(error 1059): line 'number' of 'file name': 'dde name' has a maximum larger than its type allows.

The tool has found a DDE which has a maximum value greater than the type of the DDE can store. The maximum or type must be adjusted.

(error 1060): line 'number' of 'file name': 'dde name' has duplicated enumeration 'enum name'."

The tool has found a DDE which has a repeated enumeration in the DDE's enumeration list. Duplicated enumerations are disallowed.

(error 1061): line 'number' of 'file name': 'class' is an invalid Class for a data dictionary entry (must be one of: 'c', 'cmap', 'caxis', 'cstring', 'carray', 'd', 'darray').

The string 'class' given in the Class column is not one of the allowed types for this DDE.

(error 1062): line 'number' of 'file name': enum 'c identifier' has an invalid byte size = 'bytes'.

The interface tool has found an enumeration with name 'c identifier' which has a byte size it does not recognise. If this error occurs please contact OpenECU technical support.

(error 1063): line 'number' of 'file name': variable 'c identifier' is a pointer; this is not supported for ASAP2 generation.

The interface tool can generate ASAP2 files but ASAP2 files cannot represent pointers. DDE references to C variables which have pointer type are therefore rejected.

(error 1064): line 'number' of 'file name': variable 'c identifier' is a bitfield; this is not supported for ASAP2 generation.

The interface tool cannot yet generate ASAP2 files that access bitfields. Adjust the data structure to avoid using bitfields or copy the bitfields of interest to other variables which are accessible.

(error 1065): line 'number' of 'file name': variable 'c identifier' has a type not currently supported for ASAP2 generation of 'value'.

The interface tool has found type information for a C variable that it does not know how to handle. If this message occurs, please contact OpenECU technical support.

(error 1066): line 'number' of 'file name': variable 'c identifier' has class cstring but is not a byte array.

A C-style DDE has been classed as a string but the type of the equivilent C variable is not signed or unsigned char (wide characters are not supported). Either change the C variable to have an appropriate type of change the class of DDE.

(error 1067): line 'number' of 'file name': variable 'dde name' is not class cmap yet has Xaxis, Yaxis and/or Lookup entries.

A C-style DDE has information in the Xaxis, Yaxis or Lookup columns but the DDE is not a calibration map. Only calibration maps should have information in the Xaxis, Yaxis or Lookup columns.

(error 1068): line 'number' of 'file name': variable 'dde name' used in map must have real_T (float) type.

OpenECU 1-d and 2-d map lookup blocks only work with floating point types (integer types are unsupported in these blocks). Change the type of the map axis or map data to be real_T or F32.

(error 1069): line 'number' of 'file name': variable 'dde name' has Lookup entry 'name' which caused an unexpected error.

An internal error has occurred in the interface tool. If this error occurs, please contact OpenECU technical support.

(error 1070): line 'number' of 'file name': variable 'dde name' has x and y Lookup entries 'string' but no Yaxis entry.

The calibration map with 'dde name' is 2d and has an x-axis Lookup DDE but no y-axis Lookup DDE. Calibration maps must have a lookup DDE for each map axis.

(error 1071): line 'number' of 'file name': variable 'dde name' has Lookup entry 'name' which is not found in ELF data.

The lookup DDE 'name' for calibration map DDE 'dde name' doesn't exist in the Diab ddump file. Check that the spelling is correct, that the equivalent C variable is declared and not optimised away by the compiler.

(error 1072): line 'number' of 'file name': variable 'dde name' has Lookup entry 'name' which has no corresponding DDE, removing lookup variables from map.

The lookup DDE 'name' for calibration map DDE 'dde name' doesn't exist as a DDE in any of the other DDE files. The lookup DDE must be declared in one of the DDE files.

(error 1073): line 'number' of 'file name': variable 'dde name' has Lookup entry 'name' which does not have Class 'd'.

The lookup DDE 'name' for calibration map DDE 'dde name' is declared as something other than a displayable (Class column set to 'd'). Only displayable variables can be used as lookups to calibration maps.

(error 1074): line 'number' of 'file name': variable 'dde name' has Lookup entry 'name' which does not have type real_T (float).

The lookup DDE 'name' for a calibration map DDE 'dde name' must have single precision floating point type to correctly match the C-API to the map lookup functions.

(error 1075): line 'number' of 'file name': variable 'dde name' has Xaxis and Yaxis but only one Lookup entry; should have nothing or two.

The calibration map with 'dde name' is 2d and has one lookup DDE. Calibration maps must have a lookup DDE for each map axis. Check that the Lookup column does not specify only a y-axis lookup DDE.

(error 1076): line 'number' of 'file name': 'dde name' is not found in the ELF information file output, contains an out of range array index, or is declared but not referenced in the source code.

A DDE is declared in the data dictionary but the corresponding varaible could not be found in the Diab ddump or GNU objdump output file. Check the name for spelling mistakes or add the corresponding variable to the application C code.

(error 1077): line 'number' of 'file name': map variable 'dde name' has no Xaxis or Yaxis specified.

A calibration map specified by a C-style DDE has neither the Xaxis and Yaxis DDEs specified. A 1d calibration map must have the Xaxis specified, a 2d calibration map must have both the Xaxis and Yaxis specified.

(error 1078): line 'number' of 'file name': 'dde name' is not found in the ddump ELF file output, contains an out of range array index, or is declared but not referenced in the source code.

The name for a C-style data dictionary entity wasn't present in the final linked application image and therefore cannot be processed. Check the name for spelling mistakes or add the corresponding variable to the application C code.

(error 1079): line 'number' of 'file name': 'dde name' is an invalid name for a C-style data dictionary entry (must resolve to a C identifier).

The name for a C-style data dictionary entity doesn't conform to the allowed scheme. The name of the DDE must be changed.

(error 1080): line 'number' of 'file name': variable 'dde name' has Lookup entry 'string' but should have one identifier or two separated by a comma.

The Lookup column for DDE 'dde name' has an unexcepted value of 'string'. Instead the Lookup column should have one DDE name or two DDE names separated by a comma.

(error 1081): line 'number' of 'file name': unexpected information at end of line — skipping entire data dictionary.

The tool has found a DDE line containing more information that there are columns. Remove the additional information and tab characters, or declare an additional column in the title line of the DDE file.

(error 1082): line 'number' of 'file name': 'dde name' is an invalid name for a C-style data dictionary entry (must not start with a digit character).

To provide compatibility with C compilers, C-style DDE names must not start with a digit.

(error 1083): line 'number' of 'file name': 'dde name' is an invalid name for a C-style data dictionary entry (must only use characters 'a' through 'z', 'A' through 'Z', '0' through '9' or '_', '.', '[', ']').

The interface tool accepts a subset of the C lanaguage syntax for variable names, array and structure member access.

(error 1085): line 'number' of 'file name': column 'name' is unrecognised — skipping entire data dictionary.

The tool has found a column with a name it does not recognise, i.e., not one of the allowed column names. The only valid column names in a prefix-style data dictionary file are:

Name Value Units Description Type Enums Accuracy Min Max Offset Scale Cref

The only valid column names in a C-style data dictionary file are:

Name Units Description Accuracy Min Max Offset Scale Class Xaxis Yaxis Lookup

(error 1086): line 'number' of 'file name': DDE 'dde name' has Lookup entry 'string' but should have none, one or two identifiers separated by a comma.

The Lookup column for DDE 'dde name' has an unexcepted value of 'string'. Instead the Lookup column should have one DDE name or two DDE names separated by a comma.

(error 1087): line 'number' of 'file name': 'dde name' is a constant but has no value.

The entry is a constant but does not contain a default value, which it must do.

(error 1100) file 'file name': could not open 'ELF-type' output file for reading, 'error message'.

The interface tool could not read the Diab ddump or GNU objdump file named 'file name' and the operating system's reason for not being able to do so is given by 'error message'. Correct the reason for failure and try again.

(error 1101): file 'file name': variable with no name attribute in ELF information file at line 'number'.

The interface tool has found an unnamed attribute in the Diab ddump or GNU objdump file, something the tool was not expecting. If this error occurs please contact OpenECU technical support.

(error 1102): file 'file name': 'object' with no type attribute in ELF information file at line 'number'.

The interface tool has found a variable or typedef declaration without additional type information in the Diab ddump or GCC objdump file, something the tool was not expecting. If this error occurs please contact OpenECU technical support.

(error 1103): file 'file name': referenced ID not found in ELF information file at line 'number'.

The interface tool has found a reference in the ELF information file with no corresponding entry, as if the Diab ddump or GNU objdump file was incomplete. If this error occurs please contact OpenECU technical support.

(error 1104): file 'file name': nested array in ELF information file at line 'number'.

The interface tool has found a nested array reference in the Diab ddump or GNU objdump file, something the tool was not expecting. If this error occurs please contact OpenECU technical support.

(error 1105): file 'file name': structure element with unreadable offset in ELF information file at line 'number'.

The interface tool has found a structure member in the Diab ddump or GNU objdump file but could not read the offset information, something the tool was not expecting. If this error occurs please contact OpenECU technical support.

(error 1106): file 'file name': structure element with no offset in ELF information file at line 'number'.

The interface tool has found a structure member that the Diab ddump or GNU objdump file has no offset information for, something the tool was not expecting. If this error occurs please contact OpenECU technical support.

(error 1107): file 'file name': variable with no byte size in ELF information file at line 'number'.

The interface tool has found a variable without size information in the Diab ddump or GNU objdump file, something the tool was not expecting. If this error occurs please contact OpenECU technical support.

(error 1108): file 'file name': DIE with two identically named attributes found.

The interface tool has found two identically named attributes in the contents of the Diab ddump file 'file name'. This is an unexpected condition, please contact OpenECU technical support if this message occurs.

(error 1109): file 'file name': two DIEs with same tag 'name' found in ELF information file.

The interface tool has found two identically named DIEs in the contents of the Diab ddump or GNU objdump file 'file name'. This is an unexpected condition, please contact OpenECU technical support if this message occurs.

(error 1110): auto-generated data dictionary output from the C-API has been fed back in as input; this is disallowed to avoid the possibility of attempting to write a file which is simultaneously being used as input.

The interface tool rejects attempts to read the autogenerated data dictionary file the interface tool itself generates. Instead, the autogenerated data dictionary entities of interest should be copied to a separate data dictionary file and included.

(error 1112): file 'file name': no match for 'dde name' in ELF information file.

The interface tool found an array which was too small or could not find an array element while decoding the 'dde name' DDE. Check that the 'dde name' exists as a C variable and that the variable has not been optimised away by the compiler.

(error 1113): file 'file name': no match for 'dde name' in ELF information file — array bound exceeded.

The interface tool has found a matching C variable for the DDE 'dde name' but one of the array range specifiers in the DDE is outside the bounds of the equivalent array range of the C variable.

(error 1114): file 'file name': unexpected section type 'name' in ELF information file.

The interface tool found an ELF section in the Diab ddump or GNU objdump file it wasn't expecting. If this error occurs, please contact OpenECU technical support.

(error 1115): file 'file name': no debug variables or section information found in ELF information file — is this a Diab 5.5.1.0 (or later) ddump -Dht file?

The interface tool could read the Diab ddump or GNU objdump file but did not find any C variable or ELF section information. Check that the correct file was specified in the command line options.

(error 1116): file 'file name': no match for 'dde name' in ELF information file.

The interface tool could not find information about DDE 'dde name' in the Diab ddump or GNU objdump output file. This may occur if there is no equivilent C variable with the same name as the DDE.

(error 1117): line 'number' of file 'file name': 'dde name' has an invalid number 'number' for the sample rate value.

The interface tool expects the sample rate value to be a natural integer.

(error 1118): line 'number' of file 'file name': the group for 'dde name' cannot contain single quote characters.

The interface tool expects each group name to avoid the use of the single quote character ', to avoid issues with ASAP2 validation by calibration tools.

(error 1119): line 'number' of file 'file name': the group for 'dde name' cannot contain double quote characters.

The interface tool expects each group name to avoid the use of the double quote character ", to avoid issues with ASAP2 validation by calibration tools.

(error 1120): line 'number' of file 'file name': the group for 'dde name' is invalid (group must start with a '/' character).

The interface tool expects each group name to be empty or start with a / character denoting the top of the hierachy. In this case, the group is not empty, change the group string to start with a / character.

(error 1200): line 'number' of file 'file name': there must be no more than 8 DAQ rasters defined for CCP messaging.

The platform software does not support more than 8 DAQ rasters. Reduce the total number of rasters to 8 or less.

(error 1201): line 'number' of file 'file name': the total size of the CCP DAQ rasters must be no more than 254.

The CCP protocol does not support more than 254 ODTs for all of the defined rasters. Reduce the size of each raster to total less than the allowed limit.

(error 1202): line 'number' of file 'file name': the CCP DAQ raster name '%s' must not be repeated.

When generating an ASAP2 file, the interface tool requires that the name of each CCP DAQ raster is unique. This avoids situations where a calibration tool displays the same raster name for different rasters, making the selection of raster ambiguous.

(error 1203): line 'number' of file 'file name': the CCP DAQ raster named 'raster-name' must have a rate not smaller than 5 milliseconds.

The platform software supports CCP DAQ rasters with a base period of 5 milliseconds. Increase the raster rate to be at least 5 milliseconds.

(error 1204): line 'number' of file 'file name': the CCP DAQ raster named 'raster-name' must have a rate not exceeding 10 seconds.

The platform software supports CCP DAQ rasters with a maximum period of 10 seconds. Reduce the raster rate to at least 10 seconds.

(error 1205): line 'number' of file 'file name': the CCP DAQ raster named 'raster-name' must have a rate that is a multiple of 5 milliseconds.

The platform software supports CCP DAQ rasters with a period resolution of 5 milliseconds. Adjust the raster rate to be a multiple of 5 milliseconds.

(error 1206): line 'number' of file 'file name': the CCP DAQ raster named '%s' must have have at least one ODT.

The platform software does supports CCP DAQ rasters with one or more ODTs. Increase the raster size to at least 1.

(warning 1207): line 'number' of file 'file name': the CCP DAQ raster rate '%s' is repeated and may confuse some calibration tools.

Not all calibration tools support multiple CCP DAQ rasters with the same periodic rate (for example, INCA v.5.1.2). Workaround the calibration tool issue by changing the periodic rates of rasters to differ.

(warning 2001): line 'number' of 'file name': 'dde name' has type 'type' which supports at most 'x' digits of display after the decimal point.

The tool has detected that the type of the element can support a certain number of digits after the decimal point, but the DDE accuracy field asks for more digits to be displayed. The tool reduces the number of digits to be displayed after the decimal point to the maximum supported by the type.

(warning 2002): line 'number' of 'file name': 'dde name' has a value less than the minimum specified.

The minimum specified for the DDE is greater than the minimum value given. The minimum field is adjusted to the minimum of the values.

(warning 2003): line 'number' of 'file name': 'dde name' has a minimum greater than the maximum.

The tool was expecting to see a minimum value less than the maximum value but this was not the case.

(warning 2004): line 'number' of 'file name': 'dde name' has a value greater than the maximum specified.

The maximum specified for the DDE is greater than the maximum value given. The maximum field is adjusted to the maximum of the values.

(warning 2005): file 'file name': repeated unit 'units'.

The tool has read the unit 'units' more than once. The redundant copy (or copies) can be removed from the units file.

(warning 2006): file 'file name': empty units file.

A units file is present but it contains no unit definitions (the file contains whitespace or comments only).

(warning 2007): line 'number' of 'file name': the unit 'unit name' for DDE 'dde name' is not in the units file.

The tool has read a DDE with a unit definition that does not match any from the units file. Edit the unit definition for that DDE to match any unit definition in the units file, or extend the units file accordingly.

(warning 2008): file 'file name': found an empty tabbed DDE file.

A tabbed DDE file is present but it contains no DDE definitions (the file contains whitespace or comments only).

(warning 2009): file 'file name': found repeated DDE 'dde name', discarding DDE.

A repeated DDE named 'dde name' was found in file file name. The original DDE is retained and the duplicate is ignored.

(warning 2010): line 'number' of 'file name': variable 'c identifier' occurs at more than one address.

The interface tool has found more than address in memory for the same C variable and does not know which address to use. If this warning occurs please contact OpenECU technical support.

(warning 2011): line 'number' of 'file name': ignoring variable 'dde name' for which no type information was obtained from the ELF information file; this may occur if it is declared but not actually used in source code, or if you specify a containing structure instead of a specific element within it.

The interface tool found a DDE which had no corresponding type information. The DDE information was either derived from a Diab MAP file (which does not contain type information), or the DDE was declared but not used in the source code, or the DDE name refers to a structure rather than a structure member. If a Diab MAP file was used, consider using the Diab ELF file instead, otherwise check the DDE name use in the application source.

Warning (2501): 'dde_name' is an unrecognised map type. Skipping this DDE.

The tool has found a data dictionary entry which appears as if it were a map but does not follow the naming convention specified in Section 8.2.5, “Naming rules”.

Warning (2502): 'dde_name' must be a 1xN vector. Skipping this DDE.

The tool has found a data dictionary entry which is an array or a axis DDE but the data for the DDE isn't a vector (as required).

Warning (2503): 'dde_name' must be a MxN matrix. Skipping this DDE.

The tool has found a data dictionary entry which is the z-data for a map but the data for the DDE isn't a 2-D matrix (as required).

Warning (2504): 'dde_name' the x-axis DDE 'dde_name' for map 'map_dde_name' must be a 1xN vector. Skipping this DDE.

The tool has found a data dictionary entry which has a x-axis DDE which isn't a vector (as required).

Warning (2505): 'dde_name' the size of the x-axis DDE 'dde_name' for map 'map_dde_name' must be a 1xN vector (where N > 1). Skipping this DDE.

The tool has found a data dictionary entry for an x-axis with only one element. X-axis DDEs should have at least two elements.

Warning (2506): 'dde_name' the size of the x-axis DDE 'dde_name' differs from the number of columns in the map DDE 'map_dde_name'. Skipping this DDE.

The tool has found a data dictionary entry for an x-axis which does not match the size of the corresponding z-data map DDE.

Warning (2507): 'dde_name' the y-axis DDE 'dde_name' for map 'map_dde_name' must be a 1xN vector. Skipping this DDE.

The tool has found a data dictionary entry which has a y-axis DDE which isn't a vector (as required).

Warning (2508): 'dde_name' the size of the y-axis DDE 'dde_name' for map 'map_dde_name' must be a 1xN vector (where N > 1). Skipping this DDE.

The tool has found a data dictionary entry for a y-axis with only one element. Y-axis DDEs should have at least two elements.

Warning (2509): 'dde_name' the size of the y-axis DDE 'dde_name' differs from the number of columns in the map DDE 'map_dde_name'. Skipping this DDE.

The tool has found a data dictionary entry for a y-axis which does not match the size of the corresponding z-data map DDE.