Menta Parser Errors

Issue

There are 31 different Parser Errors that can result from a Menta direct download to a programmable controller.

Product Line

TAC Vista

Environment

  • Xenta programmables
  • Xenta 280, 281, 282, 283, 300, 301, 302, 401, 401:B
  • Menta

Cause

Causes vary by error code.  See details below and any links to additional information.

Resolution

No. Name Comment
0 PARSER_OK  
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.
2 PARSER_ALLOCATE_FLASH_ERROR  
3 PARSER_IOMOD_SAVE_ERROR  
4 PARSER_VERSION_ERROR  
5 PARSER_APPNAME_ERROR  
6 PARSER_ABBREV_ERROR  
7 PARSER_TYPE_ERROR  
8 PARSER_SOURCEFILE_ERROR  
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.
11 PARSER_TIMESCHEDULE_ERROR  
12 PARSER_IOMOD_ERROR  
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.
Click here for more information.
14 PARSER_CYCLETIME_ERROR  
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
Click here for more information.
16 PARSER_DST_ERROR  
17 PARSER_CHECKSUM_ERROR  
18 PARSER_EOF_ERROR  
19 PARSER_SNVT_ERROR  
20 PARSER_SNVT_CRC_ERROR  
21 PARSER_AUTHOR_ERROR  
22 PARSER_BLUEPRINT_ERROR  
23 PARSER_NO_BPR_FILE  
24 PARSER_TLOG_RAM_ERROR  
25 PARSER_TLOG_FLASH_ERROR  
26 PARSER_TLOG_TO_MANY  
27 PARSER_TLOG_ERROR_IN_DEF  
28 PARSER_TOLG_PARSE_ERROR  
29 PARSER_IMAGE_TOO_BIG  
30 PARSER_RESET_BEFORE_PARSED  
31 PARSER_SELF_DESTRUCTION_PERFORMED