There are 31 different Parser Errors that can result from a Menta direct download to a programmable controller.
- Xenta programmables
- Xenta 280, 281, 282, 283, 300, 301, 302, 401, 401:B
Causes vary by error code. See details below and any links to additional information.
|1||PARSER_CREATE_OBJ_ERROR||Seen immediately on an attempt to download directly. Subsequent attempts result in "Download Failed." Resetting the device caused the error to come back. See in the error in COD window that its showing 0,0 coordinate pairs and underlying information. The error's not in the Menta code itself. No spaces allowed in the Program Specification -- a change from earlier versions. May render your device unusable after attempting to download -- correct files won't download either.|
|9||PARSER_SIGNAL_ERROR||Error 9 has to do with the signal list (ESP-file) there all the public signals are transferred from Menta into the GraphOP tool by a sort of a long list. Normally, if you just make the application in Menta, this should not be any problem, however search and replace on signal names could give you headache.|
|10||PARSER_ALARMTEXT_ERROR||Seems to download and fails on resetting device. Had a case where this occurred when the application was too large due to generation of an OP tree where there wasn't one before. Check memory.|
|13||PARSER_IO_ERROR||The terminal may not exist in this unit type. Could also include situations where the same terminal reference is used in multiple references (this could be on the Xenta or the IO module). Typically caused by copy/paste.
Reference to unsupported I/O Error in COD file - Error:13 for more information.
|15||PARSER_CODE_ERROR||Constants table has scientific notation, PVR blocks have scientific notation, Expression block attempting to use scientific notation, application size too large
PARSER_CODE_ERROR Error in COD file - Error:15 for more information.