Building Automation Knowledge Base

Issue After installing Vista 5.1.5 on a new XP or 2003 server PC, nothing happens when launching Vista server setup or Vista Server. Environment New installation of Vista 5.1.5. New installs only, Vista 5.1.4 upgrades do not apply. Windows XP and Windows 2003 server. Cause Windows Imaging Component (WIC) needs to be installed before .NET 4 is installed. Vista 5.1.5 as a fresh install (not upgraded from 5.1.4) requires Windows Imaging Component (WIC) to be installed before .NET 4(included in Vista installation). This component is also included in Microsoft .Net Framework 3.5. Resolution To resolve this issue, install either Windows Imaging Component or Microsoft.net framework 3.5 (see links below). Install Windows Imaging Component or... 32-bit: http://go.microsoft.com/fwlink/?LinkId=162643&clcid=0x409 64-bit: http://www.microsoft.com/downloads/en/details.aspx?familyid=f64654ac-6e26-41d9-a90a-0e7783b864ee&displaylang=en Install Microsoft .net framework 3.5 Visit http://www.microsoft.com/downloads/en/details.aspx?FamilyId=333325fd-ae52-4e35-b531-508d977d32a6&displaylang=en Download and install Microsoft .Net Framework 3.5 Reboot the computer Install Vista 5.1.5 If this issue still can't be solved, update to Vista 5.1.6.

Issue Using the Xenta 421A, 422A, 451A or 452A I/O modules as a stand alone Lonworks node and all values are reading the default 0. Product Line EcoStruxure Building Operation, Field Devices, TAC Vista Environment Xenta I/O Modules Xenta 400, 421A, 422A, 451A, 452A as stand alone LON nodes Cause The Xenta 421A and Xenta 451A as stand alone Lonworks node require the UCPTConfiguration to be set to the necessary integer value for the required input. Resolution Please see the supporting documentation for the TAC Xenta 421A/422A and TAC Xenta 451A/452A that gives each nci value for the needed input type. To configure each input to the correct type please follow these steps: Navigate to the node in your Lonworks network management software (Lonmaker, NL220, Tridium, Etc.) Browse / Edit the controller to view all of the inputs, outputs, and configuration properties. Find the Universal Input module for the input you need to configure, and locate the UCPTConfigInput variable within that module Set this UCPTConfigInput variable to one of the following: 1 = 1.8 kohm thermistor 2 = DI with green indication 3 = 0-10 vdc 4 = 0-20 mA 5 = 10 kohm thermistor 6 = DI with red indication 7 = DI with green inverted indication 8 = DI with red inverted indication NOTE: This is normally done in Menta when you are using these controllers as I/O modules to a Xenta 401, Xenta 301, Xenta 302 base unit.  The scan time of all inputs is (200ms * number of inputs used).  So if there are 3 inputs, the complete module will have been scanned every 600ms.

Issue 5.1.5 is now packaged into two different spanned archives because of how large the installer files have become. At this point there is a 300 MB file limit on exchange online and the 5.1.5 installer package is now 336 MB, hence the reason the installation package had to be split into two archives. Because the installation package is a spanned archive it will need to be opened with WinZip or a compatible archive program. In these instructions we will be downloading and installing WinRar to open the installation archives. Note 1: WinRar is technically not free software, but it does allow its demo license to extend on past the demo period. It is at the customer’s discretion on what legal and compatible archiving software they chose to use. Note 2: The built in zip archive program in Windows 7 will open this spanned archives without fail. Product Line TAC Vista Environment Vista 5.1.5 software download on any operating system older than Windows 7 Cause File limit set on exchange online and the built in .Zip extractors in older operating systems do not have the capabilities to open these spanned archives. Resolution Create a folder on your local C: drive and name it 5.1.5 To download and install WinRar please visit http://www.rarlabs.com/download.htm and find the appropriate version. If you would like to use Winzip instead, please visit http://www.winzip.com/win/en/downwz.htm to download and install the appropriate version Navigate to exchange online at Download Center login, and click the links Product > TAC Vista > Vista Software > TAC Vista 5.1.5 > Downloads Click the file named TAC Vista Server 5.1.5 with Workstation (File 1 of 2) and save. Save the file to the 5.1.5 folder created in step 1. Click the file named TAC Vista Server 5.1.5 with Workstation (File 2 of 2) and save. Save the file to the 5.1.5 folder created in step 1. Allow the downloads to finish and navigate to the location of the 5.1.5 folder. Right click on the file named TACVistaServer515.zip and select Open With > WinRar archiver WinRar should open the archive file and you can now double click and run the TACVistaServer515.exe file within it. This exe file will access the other file (TACVistaServer515.z01) within the 5.1.5 folder automatically during the install process.

Issue Removing or deleting a SNVT programmed within a Xenta Device that is no longer required in the application. By removing SNVT you increase the chance of having difficulty of getting the LonMaker Template to synchronize correctly with the modified Menta file. Understand the ramifications of deleting a SNVT and only do it when the benefits outweigh the complications. Environment TAC Vista TAC Menta NL220 or Lonmaker Cause Removing a SNVT will upset the SNVT binding order, by causing the index numbers in the XIF file to be corrupted. In this case it is not advised to delete SNVTS Changing a SNVT name or type will also cause indexing problems. The Vista object name can be changed to reflect that the SNVT is spare and not used If you have no SNVTs bound in LonMaker, the cost of deleting a SNVT is potentially having difficulty getting your LonMaker device template to synch up with the Menta file. If you have a few bindings, the downside of deleting a SNVT also includes redoing all of the bindings -- with one or two that's not a big deal. If you have 200 bindings, it can be a huge deal. Leaving a SNVT in the Menta file that isn't being used anymore just consumes one network variable input ... which can usually be dealt with easier than deleting it. So it's just weighing the pros and cons, but don't just go through without knowing what will happen. Resolution If the SNVT is no longer required in the Menta Application then carry out these steps. Disconnect the SNVT from the logic in the Menta application Allocate an area in you Menta application for unused SNVTs Move your unused SNVT into this area Label this area with the Text "UNUSED SNVTS DO NOT DELETE" Remove the public check box from the point if you do not want it visible in Vista Download the Menta application to the Xenta controller. Note: If the Xenta Application is standalone (Classic) and not in a LNS database SNVTs can be deleted without a problem

Issue Xenta 555 –Configuration of the Ethernet Communications settings, using HyperTerminal. Environment Connection to the site Ethernet network Cause A requirement to change the Ethernet connection settings Resolution This operation will allow the user to modify the settings, as detailed below.   Connect the laptop to the Xenta RS-232 port B, using the RJ45-to-RJ10 Cable and DB9/Female-to-RJ45/Female Adaptor.   Run HyperTerminal on the laptop and configure as follows;   Run Hyper Terminal and configure as: - Baud             9600 Data bits       8 Parity            None Stop Bits       1 Flow Control   None   Press ‘Enter’ to display activate the command prompt.   Xenta555 Website name…    Session-id: xxxxxxxxxxxxxxxxx Enter the Username: root Enter the Password: root At the prompt - Dsh/> - Enter setip   DHCP Yes/No  As appropriate (A fixed IP address is easier) IP Address     As appropriate Subnet Mask  As appropriate Default Gateway       As appropriate (This would be the address of the main network router, it will be the same as the PC uses) Dns     xxx.xxx.xxx.xxx (Again, if it is used then it will be the same as the PC uses) Website Name   As required (This can be entered now, or downloaded via Xbuilder) Domain Name  (Used for information only) Host Name     (Used for information only)   Change Root password yes/no        no Do you want to restart the IP Interface. yes/no        yes After configuring the 555 controller details, Enter: Dsh/>restart   The above information is also available in the TAC Xenta 500/700/911/913 Product manual, section 2.2.2.

Issue Alarms not showing up in the alarm list. Environment TAC Vista Workstation TAC Vista Server Cause The alarm could be disabled. The alarm might have priority 0 (info). There might be a filter in place in the alarm list. Resolution The alarm could be disabled, in workstation go to View > Disabled alarms to see the list and enable again. The alarm might have priority 0 (info). No Alarms with priority 0 is shown in the alarm list. There might be a filter in place in the alarm list, in the alarm view you are using right click and select filter to check this. A good practice is to set the "Date and Time" tab settings to reflect "Tripped " and "Last change" to show all alarms. This is done by checking the four checkboxes for "First alarm" and "Last alarm" allowing all alarms to be viewed.  

Issue Xenta Server (527/701/721/913) graphics, time schedules not working on the webpage. Xenta Server (511/555/527/913) can not create Menta object. Xenta Server (701 and 913) does not work with Xenta programmable controllers (Xenta 280/300/401). Which Xenta Server takes I/O modules and how many? Which Xenta Server works with I/NET, MicroNet, or ModBus. Product Line Satchwell MicroNet, TAC INET, TAC Vista Environment Xenta Server version after 5.1.5 (5.1.5 included) TAC XBuilder version after 5.1.5 (5.1.5 included) Vista, I/NET, LON, MicroNet, ModBus Cause Different Xenta Servers have different features. Using a different Xenta Server may result in missing features. Resolution Xenta Server 5.1.5 Major Features. Product LON I/NET MicroNet BACNet ModBus Web * I/O Modules Xenta Supp. ** Menta Supp. Xenta 511 X       X C   X   Xenta 527 X X     X C   X   Xenta 527-NPR   X       S       Xenta 555 X   X   X C   X   Xenta701 X       X ST 10   X Xenta 711 X       X C 10 X X Xenta 721 X       X ST 20 X X Xenta 731 X X X   X C 20 X X Xenta 913 *** X X   X X S       * S – Service. Means that the web interface is automatically generated in XBuilder and only contains values in value pages and is aimed for commissioning and service. NOTE: For Xenta 701 and Xenta 721, it is not possible to have any end-user web content, such as graphics, trend viewers, alarm viewers or value pages.  Xbuilder allows the user adding a Value Page in the Xbuilder project. It will not be displayed on the webpage though. T – Time Object Pages. Means that Time Object Pages can be added to the XBuilder project. These will only appear for Xenta Servers 701/721 in TAC Vista Workstation and can be used to control Xenta Server time charts from Vista Workstation C – Custom. Means that the web interface is totally configurable in XBuilder; navigation and all features for creating a full end-user web are available. ** Xenta Supp. – Xenta 280/300/401 support. Means that Xenta 280/300/401 can be installed on the LonWorks network beneath a Xenta Server and are fully supported by both the Xenta Server and TAC Vista on top of Xenta Server. *** The Xenta 913 also supports BacNet, M-Bus, and C-Bus. For Xenta Server 5.1.4 major features, please read Xenta Server 5.1.4 Major Features (Xenta 5XX/7XX/913 Capabilities with Graphics, Web Applications, and Migration to other systems).

Issue Can Newron NL220 or Echelon LonMaker systems run on a 64-bit operating system? Product Line TAC Vista Environment Windows 7 64-bit Windows Server 2008 64-bit LNS Newron NL220 4.5.12 Echelon  Lonmaker Turbo SR4 Cause Support is  provided for Newron NL220 4.5.13 on 64-bit operating systems. Lonmaker SR4 does provide some support for 64-bit systems. Resolution The current supported operating systems for this environment are as follows: Newron NL220 4.5.12 Windows NT Windows 2000 Windows 2003 Windows XP (32-bit) Windows Vista (32-bit) Windows 7 (32-bit)   Newron NL220 4.5.13 Windows XP (32-bit) Windows Vista (32-bit) Windows 7 32-bit and 64-bit Server 2003 32-bit and 64-bit Server 2008 32-bit and 64-Bit http://www.newron-system.com/index.php?Page=soft&Traite=download&Prod=nl220te (Account needed to view this document) Lonmaker Turbo SR4 32-bit version of Windows 7, Server 2008, Windows Server 2003 R2 with MSXML 6.0 Windows Vista with Service Pack (SP) 1, or Windows XP with SP3.  http://www.echelon.com/support/documentation/datashts/370xx-324_LonMakerTurbo_SR4.pdf 64-bit versions For 64-bit operating systems, please refer to Echelon's Software Compatibility List for restrictions and approved configurations: http://www.echelon.com/support/downloads/detail.aspx?partNum=153-0339-01A   Lonmaker 3.1.3            32-bit version of Windows 98. Windows 2000. Windows XP. http://www.echelon.com/Support/documentation/datashts/370x0.pdf

Issue Xenta Server on a remote site locks up intermittently.  A power reset of the Xenta 527 is required to bring the device back online. Environment TAC Xenta Server 511, 527, 701,711, 721, 731, 911, 913 revision 5.1.4 and earlier. Cause This Issue has been noticed in earlier firmware revision Resolution Upgrade your Xenta Server to 5.1.4 sp1 or later. Please refer to TPA-VSTA-10-0007.00 for upgrade procedure.

Issue The Xenta 102-AX can be set to NIGHT_PURGE mode using the plug-in or VAV_Controller.nviApplicMode.  The documentation does not state what this mode does. Environment Xenta 102-AX Cause The Xenta 102-AX Product Manual enumerates all of the possible modes for the controller, but does not go into detail about night purge or any of the other modes. Resolution NIGHT_PURGE mode will: Set the unit mode (nvoUnitStatus.MODE) to HVAC_NIGHT_PURGE Set the airflow setpoint (nvoFlowControlPt) to Cooling Maximum (SCPTmaxFlow) The Xenta 102-AX will enter NIGHT_PURGE mode automatically when the unit is UNOCCUPIED and the terminal load is 100%. NIGHT_PURGE mode will end and return to the active nviApplicMode when the terminal load reaches 0% or below. Note:  Heating outputs are not disabled in this mode. If the Xenta 102-AX is in night purge mode when it goes occupied it will be stuck in that mode. The box will not come out of night purge until the terminal load reaches 0% just as when it is unoccupied

Issue Echelon LON USB not recognized by TAC Vista 5 in a Classic network. Echelon U10/U20 USB interface is not supported in Vista installations. It oftentimes will not come online under a Vista Server. Product Line TAC Vista Environment Echelon LTA U10/U20 USB to LON converters Vista Server Classic Network Cause Because of numerous problems integrating an Echelon U10/U20 USB interface, Echelon's USB to LON converters are not supported by TAC Vista. Resolution Download the TAC Vista Server Data Sheet and reference page 11 for supported LTAs. The supported LonTalk Adapters are: PCLTA TAC Xenta 511 PCLTA-10 TAC Xenta 527 PCLTA-20 TAC Xenta 555 PCC-10 TAC Xenta 701 i.LON 1000 TAC Xenta 711 NIC709-PCI TAC Xenta 721 NIC709-USB TAC Xenta 731 NIC709-USB100 TAC Xenta 911 NIC709-IP TAC Xenta 913 NIC852       FT 10 TP 1250 RS 485 IP 852 Ethernet NIC709-PCI X X N/A N/A NIC709-USB X X N/A N/A NIC709-USB100 X X N/A N/A NIC709-IP X X N/A N/A NIC852 N/A N/A N/A X

Issue Xenta 5/7/9xx System Report shows "Menta: Overrun error (Error#:62468)" Environment Xenta 701, 711, 721, 731 version 5.1.4 and below Cause A Menta application took to long to run a loop. Probably due to temporary high load of the system. Resolution Upgrade the Xenta 700 to version 5.1.4 SP1 or greater, preferably the most recent release of Xenta Server software.

Issue Step-by-step instructions for calibrating Space Temperature sensor on a Xenta 102-AX (or I/NET MR-VAV-AX) using the M/STAT. Environment Xenta 102-AX MR-VAV-AX M/STAT Cause The preferred method for calibrating temperature in Xenta 102-AX or MR-VAV-AX is through the plug-in.  However, this is not always an option, especially when the responsibility for calibrating is given to a third party test and balance company.  Pocket references exist for navigating through the M/STAT menu, but there aren't clear step-by-step instructions to tell exactly how to perform the calibration. Resolution  Step 1: Connect M/STAT Plug the M/STAT into the jack on the thermostat.  The initial display shows the set temperature.  Step 2: Enter Password Press the Service button.  This prompts you to enter the service mode password.  Default password is 183.  Use the +/- keys to set each digit and the enter key to submit.  If the password is incorrect, the display will blink.  Step 3: Operational Parameters If the password is correct, the first menu option – Unit Parameters (UP) – is displayed.  Hit the select button down until Operational Parameters (oP) is displayed.  Press enter.  Step 4: Calibrate Space Sensor Hit the select button until Calibrate Space Sensor (CSS) is displayed.  Press enter to view the current value.    Step 5: Enter Actual Value Use the +/- keys to change the value beginning with the tenths of degrees.  Press select to change to the degree and ten degree digits.  When the display matches the Actual Value, press enter.  Step 6: Escape Service Mode Press the service key to escape out of the menu.  If you are finished configuring the box, escape all the way back out of the service menu before disconnecting the M/STAT.  Disconnecting in configuration mode can leave the stat displaying “00” or other incorrect numbers.

Issue Xenta Server (527/701/721/913) graphics, time schedules not working on the webpage. Xenta Server (701) does not work with Xenta programmable controllers (Xenta 280/300/401). Which Xenta Server takes I/O modules and how many? Which Xenta Server works with I/NET, MicroNet, or ModBus. Product Line Satchwell MicroNet, TAC INET, TAC Vista Environment Vista, I/NET, LON, MicroNet, ModBus Xenta Servers (Xenta 5XX/7XX/913) Cause Different Xenta Servers have different features. Using a different Xenta Server may result in missing features. Resolution Xenta Server 5.1.4 Major Features. Product LON I/NET MicroNet BACNet ModBus Web * I/O Modules Xenta Supp. ** Xenta 511 X         C   X Xenta 527 X X     X C   X Xenta 527-NPR   X       S     Xenta 555 X   X     C   X Xenta701 X         ST 10   Xenta 711 X         C 10 X Xenta 721 X         ST 20 X Xenta 731 X X X   X C 20 X Xenta 913 *** X X   X X S     * S – Service. Means that the web interface is automatically generated in XBuilder and only contains values in value pages and is aimed for commissioning and service.  NOTE: For Xenta 701 and Xenta 721, it is not possible to have any end-user web content, such as graphics, trend viewers, alarm viewers or value pages.  Xbuilder allows the user adding a Value Page in the Xbuilder project. It will not be displayed on the webpage though. T – Time Object Pages. Means that Time Object Pages can be added to the XBuilder project. These will only appear for Xenta Servers 701/721 in TAC Vista Workstation and can be used to control Xenta Server time charts from Vista Workstation C – Custom. Means that the web interface is totally configurable in XBuilder; navigation and all features for creating a full end-user web are available. ** Xenta Supp. – Xenta 280/300/401 support. Means that Xenta 280/300/401 can be installed on the LonWorks network beneath a Xenta Server and are fully supported by both the Xenta Server and TAC Vista on top of Xenta Server. *** The Xenta 913 also supports BacNet, M-Bus, and C-Bus. For Xenta Server 5.1.5 major features please read Xenta Server after version 5.1.5 (5.1.5 included) Major Features (Xenta 5XX/7XX/913 Capabilities with Graphics, Web Applications, and Migration to other systems).

Issue Date and time gets incorrect periodically in TAC Xenta Programmable controllers Time stamp in alarm list is incorrect Time stamp in alarm list is wrong  Vista Server local time and the local time in all Xenta controllers in the network go out of synch.   All local time settings are correct in TAC Xenta Environment TAC Xenta 30x/401/28x Cause The time in a TAC Xenta can be changed by TAC Vista TAC OP, note that a change of the time in one controller is broadcasted to the whole network. TAC Xenta group master will broadcast the time to it's group every 24 hours A Xenta Server (Xenta7xx, Xenta5xx, Xenta 913) Menta, this only affects the controller Menta is connected to. Most likely, the problem is a Xenta Server in the network that has the wrong time. It can be enough that a Xenta server is connected to the network, it does not have to be configured in this network.. Resolution Log in to Xenta server from the web interface. Go to Configuration-time If the date and time is incorrect set the correct date and time. Click on time synchronization, the lonworks time synchronization should only be set to enable  if this is a Xenta Server in TAC Vista or if this is a site that does not have TAC Vista on it and it is the only source to sync the time to.

Issue Alarm time logged into Vista from a Xenta controller 1 Hour earlier than actual alarm time even though the Xenta and Vista Server have the same time. This can also cause issues with Xenta trend logs where they will have estimated values for the past hour worth of logs. Environment Workstation Xenta Controllers Cause The offline (Engineering) Daylight / Standard time (DST) settings do not match the online (Operating) Daylight / Standard time settings. Resolution The Daylight saving and Standard time settings need to be corrected in the Xenta controller as follow: Place Vista into Engineering mode using the drop down list on the tool bar. Select the controller that is having the alarm time error. Right mouse click and select Properties. Select the Time Settings tab. Correct the Daylight saving and Standard Time settings. Return the Vista into Operating Mode using the drop down list on the tool bar. Retest alarm for correct time stamp or recheck your Xenta trend logs.

Issue Right-click on a device in LonMaker and choose "Browse...."  This should launch the LonMaker Browser.  Instead of launching, an error pops up that says "Unable to find a matching plug-in for device, use network properties to register the correct plug-in." Environment LonMaker Cause Echelon LonMaker Browser is a plug-in that must be registered like any other.  If it has not been registered properly, it will need to be registered, or re-registered. Resolution In LonMaker, choose the LonMaker toolbar menu Go to Network Properties > Plug-In Registration Tab Find "Echelon LonMaker Browser (Version X.X)" either in Already Registered or Not Registered window. Double click the plug-in, which adds it to the To Be Registered window. Click Apply or OK to register to plug-in. Launch the LonMaker browser again.

Issue Time schedules appear to be working backwards. Time schedule that controls occupancy of a LonWorks unit is not controlling properly. The unit is unoccupied instead of occupied. Time schedule outputs need to be reversed to control I/NET points where 0 and 1 may not be off/on. Environment Xenta Server Xenta 511, 527, 555, 701, 711, 721, 731, 913 XBuilder Cause SNVT_Occupancy has the following values: 0 - Occupied 1 - UnOccupied 2 - ByPass 3 - StandBy If the time object does not use the correct default and active values then the wrong value will be sent from the time schedule. I/NET controls with the "first of the pair, second of the pair" which may require a 0 to be ON and a 1 to be OFF. Resolution Modify the Time Object for a SNVT_occupancy: In the Show Other Properties editor change the default value to 1 (Unoccupied). In each time event change the Active Value on the Other tab to 0 (Occupied). If edited offline, generate the project and send to the target.

Issue Apply an offset to Universal Inputs (U1, U3) on the Xenta 102-AX Environment Xenta 102-AX Cause Universal inputs U1, U3 on the Xenta 102-AX can be configured to read in several different data types.  Applying a software offset may be required to calibrate the reading for certain settings. Resolution For the following signals, use the listed SCPTs to offset the inputs: Universal Input 1 set to Duct Temperature use UnivIn1_Sense.SCPToffsetTemp Universal Input 3 set to CO2 Sensor use UnivIn3_Sense.SCPToffsetCO2 Universal Input 3 set to OA Temp. Sensor use UnivIn3_Sense.SCPToffsetTemp Hint:  For SCPToffsetTemp used with °F, first double-click the value to open the Edit Properties window and change the units to "°F, diff."  This will zero out the 32° offset and allow you to use the value as a temperature differential.

Issue How to prevent times schedules from being overwritten when downloading an updated version of the XBuilder project to a Xenta Server. When uploading new configuration to Xenta 7xx device, all the scheduling is deleted. TSCH changes made from web interface are deleted when downloading the XBuilder project again Environment TAC XBuilder TAC Xenta server Cause There is no automatic check to see if time schedules have been modified since the last download. Information must be manually uploaded to the project. Resolution Before sending the updated Xbuilder project to target: Go to Project - Get from target Select Get online changes, click ok. Now the updated schedules are saved in XBuilder.