Errors and Warnings
When using one of the validators, one of the following detected errors or warnings may display:
Warning or Error Message | Description |
---|---|
Not all dependency information has been examined | Displays if an attempt is made to exit the program, or print a dependency report, before all the dependency information is viewed. The dependency information is considered viewed when all the top level program nodes in the view tree are expanded. These can be expanded individually, or all at once by clicking 'Expand All'. Dependency information is still considered viewed if the nodes are collapsed again. |
Abort, name too long! | Displays if a variable or program name read from the application symbols file, or the cross reference, is too long. The maximum identifier length supported by IEC1131 TOOLSET version 3.23 is 16. |
Aborted, unknown block type header | Displays by Validator #1 if an unknown header type is encounterd while reading through the cross reference file. Verify the correct file is selected, or try re-generating it. |
Aborting, input file is not a valid cross reference file | Displays by Validator #1 if a syntax or format error is encountered while reading through the cross reference file. Verify the correct file is selected, or try re-generating it. |
Aborting, input file is not a valid symbols file | Displays if a Validator encounters a syntax or format error while reading the application symbols file. Try re-compiling the application to re-generate the symbols file. |
Applications directory: <name> does not exist | Displays when a Validator cannot locate the specified Application Directory. |
Cannot find application symbols file Appli.tst for application <name> | Displays if a Validator cannot locate the application symbols file for an application. Verify the application compiled successfully. |
Cannot find TIC code file Appli.x6m for application <name> | Displays if a Validator cannot locate the download data base file for the application. Verify the application compiled successfully and the compiler options are set to generate code for a Motorola target (ISA68M). |
Cannot produce report, printer fault | Displays if a printer fault occurs while a Validator is attempting to output a report to the printer. |
Download database not in Motorola format | Displays if the applications download database file is not the correct format. Ensure the compiler options are set to generate code for a Motorola target (ISA68M) and re-compile the application. |
Error accessing application history file! | Displays when a file I/O error occurs while accessing the application history file. |
Error reading Uchar | Displays when an error occurs while reading from the download database file. Try re-compiling the application to re-generate the database file. |
Error accessing download database file | |
Error reading uint16 | |
Error reading uint32 | |
Error reading in ReadChars | |
Error reading in ReadCharsFrom | |
Error Loading CODEPROG | |
Error reading from formatted file! | Displays when a file I/O error occurs while reading from a formatted text file, like the cross reference file, or the application symbols, files which are text. |
Error accessing file <file> | |
Program count mis-match in application directory <name> database files in-compatible | Displays when the download database file and application symbols file contain different numbers of programs. Try re-compiling the application. |
Project name mis-match in application directory <name> database files in-compatible | Displays when the download database file and application symbols file are in-compatible because they contain different project names. Try re-compiling the application. |
Project symbols CRC mis-match in application directory <name> database files in-compatible | Displays when the download database file and application symbols file are in-compatible because the application symbols CRCs do not match. Try re-compiling the application. |
Unable to produce report file | Displays if a file I/O error occurs while a Validator is attempting to output a report to a text file. |
Provide Feedback