Building Automation Knowledge Base

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.

Issue Can not view OGC graphics in Vista 4.5.0, only a white screen is shown when the graphic is opened. It is possible to edit the graphic and create new graphics but not view any OGC graphics. Environment Vista 4.5.0 Windows 2003 server Cause The folder C:\Documents and Settings\user\Local Settings\Temp\TemporaryGraphicsFiles is missing, this is where the cached OGC files should be saved. Resolution Create a new Windows user Log into Windows with that user Start Vista with that user The cache folder is created and it is now possible to see graphics again

Issue A loggbackup file is not copied from $bkp in the Vista database to the place specified in the backup object. Environment Vista 5.1.5 Windows XP SQL 2005 express Cause When the SQL server is finished with the backup it tells Vista, and Vista then copies the bkp file from $bkp in the Vista database to the place specified in the backup object in Vista. In this case the SQL server succeeds with the backup but fails to put it in the history log called dbo.backupfile in the MSDB database. So Vista never gets the message that SQL is finished and doesn't move it to the right location. Resolution The dbo.backupfile table in the msdb database was corrupt and needed repair. Contact PSS or have a SQL expert check the msdb database.

Issue What is the switching level resistance for a digital input to be seen as 1 in a Xenta 411/412 I/O modules Environment Xenta 411/12 Cause Integrating third party devices with Xenta 411/412 I/O modules. Resolution The switching level resistance for a digital input to be seen as 1 in a Xenta 411/12 is around 2000ohm

Issue Decommissioned devices in a LonMaker database which was converted from a NL220 database; however, did not get LNS credits back. Environment LonMaker NL220 Cause Converting NL220 database into LonMaker database is not simple. The major issue is to recreate the Visio drawing. In addition, Since the database was created in NL220, LonMaker will not be able to give those credits back even user decommission those devices. Resolution Decommission devices in a LonMaker database which was converted by NL220 WILL NOT let users get the LNS credits back. For additional information, please contact ECHELON and NEWRON SYSTEM. ECHELON product support: lonsupport@echelon.com NEWRON SYSTEM product support: hot.line@newron-system.com

Issue Alarm message received "Trend Log Object [Object Name]. Could not transfer log values automatically. Try Manually" Environment Vista Server Xenta Controllers Cause Log space set to 0 seconds or minutes for trend log. Communication breakdown between Vista and Xenta Controllers. Resolution Set Log Space to minimum 10 sec or 1 min per trend log Communication between Xenta and Vista should be normal.

Issue How to interpret a M-Bus point details in a VX communication log such as External Temp [C] {1:0:0}. Environment Xenta Server 913 Cause The  External Temp [C] {1:0:0} message is providing important information about the point. External Temp = Field Type [C] = Unit {1 = Storage # :0: = Sub-Unit 0} = Tariff # Resolution Use the details of the communication log message to correct configuration problems in the device editor. MVAL External Temp [C] {1:0:0} value not required This message provides device details that a point exists, but the Device Editor is not looking for it. !MVAL External Temp [C] {2:0:0} =not received A point is expected but was not found.

Issue SQL Host not passing data to Xenta 527 Web Server Product Line TAC INET, TAC Vista Environment I/NET 527 Web Server Cause When defining the Host for the primary SQL server, you have options of 1-250. When using a Web Server to send this information to a Vista System you must define the primary SQL server with a Host number less than 63. Resolution In I/NET configuration, define the primary SQL server's Host number between 1 and 63 Restart the I/O server Connect to each Xenta 527 Web Server on site and modify change the SQL Host # to the host number assigned in step 1 Restart each 527

Issue Vista reports running on EXCEL 2010 do not save the date format correctly. Environment Microsoft EXCEL 2010 Vista 5.1.5 and below Cause Excel 2010 is not supported on Vista 5.1.5 and below Resolution To get the date and time format to work correctly with Vista uninstall Excel 2010 and install Excel 2007. The other option is to upgrade to Vista 5.1.7 which supports Excel 2010 A possible  workaround  is to insert your trends into the Work Area of the report. That is the area to the right of the main page. Then you can copy this information to the main page and format the cells on the main page.    

Issue Xenta 102-B nviManOverride allows for flow or percentage overrides. But since this controller is intended to be used along with a Belimo flow controller/actuator, how do these modes of operation differ? Environment Xenta 102-B Cause Flow control is not actually an option for this controller. Flow values will be interpreted as desired percentages of airflow. Resolution nviManOverride.state = HVO_PERCENT, nviManOverride.percent = 35% The controller fixes the Airflow output (Y1) at 35% (3.5V) nviManOverride.state= HVO_FLOW_VALUE All of the flow values are actually being treated as percentages ... there is no way to set it to a desired flow. (nviManOverride.flow X nciNomFlow / 100) is limited to 0-100% and sent to the Airflow output (Y1). Emergency Override can override these setting, as can setting the controller to slave mode (the overrides would have to be performed on the master controller in that setting). The way to release these states is to set the nviManOverride.state to any value other than HVO_PERCENT or HVO_FLOW_VALUE. Those are the only two values accounted for in the logic.

Issue Compressor will not activate blocking the cooling or heating of the Xenta 121-HP. Environment Xenta 121-HP Cause A compressor temperature lockout exists in the Xenta 121-HP application. The lockout has a minimum and maximum temperature the source signal must be between for the compressor to activate. The source signal changes depending on whether the application uses a air source or a water source. Air Source - nviOutdoorTemp Water Source - nviSourceTemp Resolution Ensure that the source temperature signal is between the compressor lockout minimum and maximum.

Issue Using an End-User Dongle to license XBuilder or Menta when Vista Server is not installed Environment Vista 5.1.7 and older XBuilder Windows XP Menta Cause License may not be able to install due to previous license file conflicts. Resolution Install or re-install the TAC License Program found on Exchange Select Start>All Programs>Schneider Electric>TAC Tools>LMTools (or Start>All Programs>TAC>TAC Tools>LMTools Click on the Start/Stop/Reread Tab Click on "Start Server" Click on "ReRead License File" Close LMTools and Start XBuilder If the option is available, it is preferred to host the license to a MAC address instead of a dongle ID.

Issue TGML graphics Editor will not open even though the Engineering Dongle is connected. Environment TGML Graphics editor Vista IV Cause The Vista IV engineering Dongle is not licensed to allow TGML Graphics Editor to open. It will only allow OGC Graphics Editor to open. This Feature was not included until Vista 5. Resolution Use a Vista 5 Engineering Dongle or download the Demo License to edit TGML files.

Issue After launching the Vista Server program, it seems to cycle through its startup process, but stops on: "initializing server functions field bus initializations..."  Vista Server will never finish opening regardless of how long it is left to run and must be forced closed with the Task Manager. When attempting to open a LonMaker drawing, the last process displayed before hang up is: "Opening network connections". Environment LonMaker Vista Cause Corrupted LonMaker database. Possibly due to unexpected termination of the LonMaker program such as a loss of power or Ending the process from Task Manager. Resolution Attempt to open the associated LNS database through LonMaker. It will most likely fail to open. Restore last known good backup. Optionally,  send the damaged database to Echelon Support for further investigation at lonsupport@echelon.com. Field bus is referred to as LNS Server Ports in the Vista world.  If the LNS database will not open, then the Vista server cannot access it.

Issue How to change the online keyboard layout of a Magelis Opti PC. Change input language for the keyboard on Magelis Opti PC. Environment Magelis Opti PC (Touch screen PC OP panel) Cause The Magelis Opti PC runs on windows XP embedded version so you change the keyboard input the same way as any PC. Resolution Open Control Panel and click on Regional and Language settings Click on language tab- Details Add the language you need.

Issue Not possible to have a zero in the beginning of an address to a M-bus device in XBuilder.  For example, add an M-bus device in XBuilder. Write a secondary address (used default) with a zero in the beginning. Click OK and the zero in the beginning disappears. Environment Vista 5.1.5 XBuilder Cause This is just a display attribute in XBuilder to trim leading zeros in the address field. Resolution Even if the zero in the beginning disappears in the address box, it will still be used when the Xenta server communicates with the M-bus device. Write the address with a zero as it should be and that address will be used.

Issue Cannot view SCPTs, UCPTs, or UNVTs in XBuilder. Warning in XBuilder: "2147483647    Warning -1     ____ will be skipped. Unrecognized SNVT type from Vista Database:0" Environment XBuilder LON Devices Xenta 102-AX Xenta 121-HP, 121-FC STR-350 Cause XBuilder can only view, read, and write to SNVTs in a LON device. Resolution There is no way to view SCPTs in XBuilder. If XBuilder is required for transferring data, a work around will have to be found. Instead of writing to SCPTsetPoints, use nviSetpoint, for example. The resulting warning in XBuilder is alerting that it cannot process the information contained in a SCPT, UCPT or UNVT, only SNVT. Therefore the "SNVT type" is unrecognized.

Issue The default font size in the TGML Graphics Editor is 15. Can this value be changed? Environment TAC Vista - TGML Graphics Editor Cause Default Font Size in TGML Editor is 15 and it is hard coded in the software.  Resolution It is not possible to modify the default font size. When we change the font size, the TGML editor automatically remembers the last value used.

Issue Can the Loytec L-VIS be used in a Vista Classic scenario? Environment Loytec L-VIS Cause The need to have a touch screen interface to a Vista Classic network. Resolution The L-VIS cannot be used in a Vista Classic system because it uses SNVTs to interface the Lon. LNS must be used. A solution to a Vista Classic scenario would be to touch screen PC or tablet to interface the graphics in an Xenta Webserver (5xx,7xx).

Issue Triggered an alarm for a Xenta 121 if the space temperature is too high or low from the setpoint. Environment Xenta 121-FC Xenta 121-HP Zbuilder Cause The Xenta 121 controller has a low spacetemp and a high space temp alarm. These alarms are triggered for the following reasons: Low Space temp alarm - In heating mode when space temperature is lower then Setpoint - nciSpaceTempDev High Space temp alarm - In Cooling mode when space temperature is higher then Setpoint + nciSpaceTempDev These alarms can be monitored here: Low Space temp alarm - nvoSystemStatus bit 13 High Space temp alarm - nvoSystemStatus bit 14 Resolution Specify the nciSpaceTempDev by using the ZBuilder plug-in and accessing the Configuration page. On the Lon\Node screen the Space temperature deviation is editable. The default value is 3.6 deg F or 2.0 deg C. Use a value that will not trip the alarms erroneously, but still warn if there is a problem.