Issue
Description of the file types and file extensions in Menta.
Environment
- Menta
- Vista
- Lonmaker
.AUT, .TLG, .MCB, .COD, .XLG, .ESP, .OPE, .OPC, .ESP, .BIN, .CHR,
.COD, .XIF, .MTA, OPDOC.GOP, .SPT, .BIN, OPDOC.SPT, OPDOC.TMP, .BPR.
Cause
Description of the filetypes in Menta.
Resolution
The following data files are involved when creating a Menta application for a Xenta 280/300/401 device.
- .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.
This information was taken from the TAC Menta Technical Manual.
