http://buildingskb.schneider-electric.com/results.php

1. задание COM порта  для обмена задается или в каждой  программе индивидуально на действующий сеанс связи или в программе MentaSetup.exe
2.  

Индикация TAC Xenta 280, 281, 282, 283, 300, 301, 302, 401, 401:B

The red service diode is primarily an error indication. It also lights up if the Service pin is activated.

1. A solid red light usually indicates that the hardware has failed.  Please see a few simple steps to deactivate the solid red light below.
   • Use a reset dongle to wipe the controller then reinstall the firmware and menta program.
   • If the controller is the group master you might try to assign a different controller to group master.  This method has not been proven but has worked before during internal testing.
     NOTE: The hardware may need to be replaced if the solid red light continues after these steps.
2. If the red indicator light is blinking once per second this will indicate a non-configured node.
   • If the controller has been commissioned you might try to decommission the controller and try again.
3. If the red indicator light is off this would indicate that it has been commissioned and added properly to the network.  You should not see the red indicator light if the controller is working properly.
4. The green status diode blinks once per second to indicate that the program is running properly. (В нормальном режиме при штатном выполнении программы, светодиод мигает с чвстотой 1Гц. Если поисходит программное зависание контроллера- светодиод светится зеленым цветом.
5. Но! часто из-за условий эксплуатации оборудования в режиме повышенной температуры окружающей среды помимо рассыхания пластмассовых деталей, «высыхания» электролитических конденсаторов, возникают проблемы с пайкой — нарушается контакт, а также «теряют» сопротивление резисторы. Так, в частности несколько раз встречалась проблема, связанная с отсутствием индикации при полной работоспособности контроллера — терял сопротивление резистор в цепи «светодиод-коллектор управляющего транзистора». )
6. По аналогичной причине (повышенная температура окружающей среды) возникают сходные проблемы с операторской панелью что може привести в частности к такому дефекту как «квадратики» вместо символов

Типы файлов:

• .AUT Text file with application program source code and data including graphical block diagram.
• .TLG The trendlog definition.
• .MCB Macro block file (Group of blocks).
• .COD “Machine code” file in ASCII format for downloading to the TAC Xenta controller.
• .XLG The compiled trendlog definition.
• .ESP Specification file with public signals, their attributes etc. generated by TAC Menta. This file contains input data to the OP configuration tool.
• .OPE A file with an empty tree, i.e. an OP tree without a specification file. This is the kind of file that is created when the OP configuration tool is run from the program manager.
• .OPC A mix of an .OPE and an .ESP file. This file is created by the OP configuration tool when it has been invoked from TAC Menta.
• .BIN Binary file with OP menu tree data for downloading to the TAC Xenta controller together with the .COD file.
• .CHR National character set file for downloading to the TAC Xenta controller together with the
  .COD file.
• .XIF External interface file containing a standardized description of all network variables/ objects of the application program. The .XIF enables binding and communication with LonWorks nodes from other manufacturers.
• .MTA Menta project file, which can include all files (all types mentioned above except for .MCB and .OPE) related to a certain application. Once a file (for example .AUT or .OPC) has been inserted (saved) in the project file, it can be extracted (opened) anytime as an .MTA file. The .MTA file can be stored directly in the TAC Vista database.
  Note:
  The .MTA file can be stored in the TAC Vista database even though it can not be compiled. An .MTA file which is not compilable will not, of course, be possible to download into a TAC Xenta device. It must be correct and compilable before download is possible. In addition to the files listed above, the following data files are involved in the creation of the .BIN file. These files are placed in a specific directory for temporary files.
• OPDOC.GOP An ASCII file created by the OP configuration tool when the Generate command is executed. This file is converted to an .SPT file, which in turn is converted to a .BIN file
• OPDOC.SPT Intermediate ASCII file generated from the.GOP file.
• OPDOC.TMP Intermediate ASCII file generated from the.GOP file.
• BPR The Network Neighborhood file, describing the TAC Xenta device’s surrounding network nodes and groups.

http://buildingskb.schneider-electric.com/view.php?AID=3935
http://buildingskb.schneider-electric.com/view.php?AID=4036

Parser error

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

 

Возможные неисправности:
— при включении блока (например 421), светится зеленый светодиод, по сети не виден. Необходимо проверить конденсаторы в цепях питания (ESR).

Для отображения русского языка на панели Xenta OP необходимо в редакторе TAC Menta -> OP configuration -> Formats -> Settings убрать:
— use system menu
— OP: custom