Issue Xenta Server is marked with an asterisk and says "Needs to be Commissioned" Environment Vista Workstation Xenta Server Xenta 511, 527, 555, 701, 711, 721, 731, 913 Cause The files in the Xenta Server do not match the Xbuilder project stored in the Vista Database. Resolution Right-click on the Xenta Server in Vista Workstation and select Edit.  This will open XBuilder. In Xbuilder, click "Send to Target" to download the files to the Xenta Server.

Issue Nodes not showing up under subsystem view in System plug-in with NL220. However, in NL220 under subsystem tree, everything shows up fine. Environment NL220, system plug-in Cause This can occur if the default root subsystem "Locations" was deleted. The "Locations" root subsystem must be linked to the geography of the site. Therefore, deleting it may cause the lost of the link. You can change the "Locations" root subsystem’s name to something else. However, we do not suggest deleting and adding a root subsystem back. Resolution Before doing anything, please make a back up of your LNS database. Create a new root subsystem. (Right click on the Project object and select the option “New root subsystem”). When asked for the name, type "Locations". Copy all nodes under all subsystems and paste them into the "Locations" root subsystem you just created. Delete all the subsystems outside of the “Locations” root subsystem. Go to "Edit" tab, choose "define location subsystems" Select "Locations" root subsystem. Click on "location subsystem" button on the right. Click on "Yes" Refresh the tree. Go to the System Plug-in, you should be able to view all nodes under subsystem view. Now, you can go back to NL220 and change the root subsystem name to anything you want.

Issue Graphics or Webpages not working in a Xenta 701 or 721.  They can be built and configured in XBuilder, but then when logging into the web interface, they do not appear in the menu. Environment Xenta 701, Xenta 721 Cause The Xenta 701 and Xenta 721 only have "Service Web" capabilities. Service Web means it is not possible to have any end-user web content, such as graphics, trend viewers, alarm viewers or value pages. To get access to end-user information, connect the Service Web controllers to TAC Vista and retrieve the full range of information. The Xenta 711 and Xenta 731 have the necessary support for "Custom Web." Custom Web means that the web interface is totally configurable in TAC XBuilder, the Xenta server configuration tool; navigation and all features for creating a full end-user web are available.   Modbus MicroNet I/NET WEB I/O Modules Support Xenta 280/300/401 Xenta 701       Service 10   Xenta 711       Custom 10 X Xenta 721       Service 20 X Xenta 731 X X X Custom 20 X Resolution If custom web is needed at the Xenta Server then a Xenta 711 or 731 needs to be installed instead of the 701 or 711. Another option would be to put Vista on top of the Xenta Server and build graphics at the HMI level.

Issue During the boot sequence of a Xenta Server the message "Unmap block xxx at remount" occurs. Environment Xenta 511 Xenta 527 Xenta 555 Xenta 701 Xenta 711 Xenta 721 Xenta 731 Xenta 913 Cause Sections of the flash drive are being declared bad and are being removed from the accessible drive map. This can be a natural pruning process of bad sections due to drive damage or that section exceeding the maximum number of writes. The amount of lost space is: # of pages * 2 bytes All hardware 2 Xenta Servers have 16mb flash drives, so it takes a large number of pages to be lost before significant space is lost and will impact performance of the unit. Resolution If the number of pages is low and is not increasing then the unit should function normally without any additional action. If the number of pages is exceeding 50000 or increasing rapidly, then have the Xenta Server repaired or replaced depending on its age.

Issue Various error when trying to login, cant open graphics Environment Vista webstation Cause Java errors i.e. When opening graphic error "Error: Click for detail" or Dynamic mode not functioning. Resolution Dynamic picture not working are most likely caused by wrong Java version. Vista 5.1.4 uses Java 1.6-17 but installing this version afterwards might causes other problem like "Error: Click for detail (various java code errors). This can be resolved by reinstalling the webserver again or check for the following. IIS use the wrong version of .NET. - Go to administrator tool and choose Internet information services. - Choose Web sites then Default Web Site - Right click on Webstation and choose properties - Go to the ASP.NET tab and make sure the version specified are 2.0.... Address used  HTTP://IP/defaultpage.aspx when it should be using HTTP://IP/webstation/defaultpage.aspx - Go to same path as above but instead of right clicking the Webstation right click on the tree above "Default Web Site" and choose properties. - Go to the tab Home directory and check local path it should be directed to wwwroot (see attached) Then write in the address HTTP://IP/webstation/ (might work if you try directly) There have always been problem in which order you install programs, it has been noticed that sometimes java needs to be installed before webstation since webstation tries to reach components in java that do not exist else. So a try would also be to reinstall webstation now when the new Java version are already installed.

Issue How and when does a Xenta 102-AX resynchronize its damper floating output control? Environment Xenta 102-AX v2.17 and up Cause Documented reasons for a damper and floating output resynchronization on a Xenta 102-AX controller Resolution There are 5 events that cause a Xenta 102-AX to resynchronize its floating control logic for the damper and other outputs. These reasons are: At controller reset. (This could be a power cycle or reset command via TAC Vista/LNS) If the damper motor position command has been inside its "active zone" (5% - 95%) for an accumulated time of 24 hours, AND the motor position then goes to 0% or 100% (Note that the outputs and damper are timed and reset independent of each other) Indication of error in flow detection. This is if nvoFlowControlPt = 0 but nvoMotorPositn > 0 for 1 minute or more If nviEmergCmd is set to any of the following modes: EMERG_PRESSURIZE EMERG_DEPRESSURIZE EMERG_PURGE EMERG_SHUTDOWN and then goes back to EMERG_NORMAL A controller reset via Lonmaker or NL220 will also cause a resynchronization of the damper and the other floating outputs. This is necessary if the stroke time (throttling range) or stroke direction is changed in the middle of a damper operation

Issue When directly connected to a Xenta programmable controller through a serial cable, and observing live Menta, it is possible to override inputs and outputs.  This override is the same override attribute that can be set from the OP and from the Workstation. Environment Menta Xenta programmable Xenta 280, 281, 282, 283, 300, 301, 302, 401, 401:B Cause Overriding points while simultaneously witnessing live updates of all program values is an effective troubleshooting technique. Resolution Directly connect live to a Xenta Programmable Download the correct Menta file to the hard drive of a laptop. Right click on the controller in Workstation and select Edit. File > Save As ... to the hard drive. The Menta file must exactly match what currently is downloaded into the controller or else it won't connect. Connect to the RS-232 port on the face of the Xenta programmable. Open the Menta file. Options > Simulate Click the Online button in the top left corner. Select "Connect" from the menu. View I/O and override Options > I/O Configuration This brings up a list of all inputs and outputs in the controller.  The last column says "Not overridden" for any point not currently overridden.  If it is, it will show the override value.  Choose a point and click the Override button at the bottom. Check the box to override and enter the desired value.  Click OK. The point is now in override. NOTE: This override attribute is the same override that is available through the OP and through Vista Workstation.  Points can be put into override and taken out of override from any of these 3 locations and it will dynamically update any other concurrent users.

Issue In TAC Menta, under Device Specification, it is not possible to  define the actual System Version or Hardware version of your TAC Xenta device. Environment TAC Menta Version 5.1.5 TAC Xenta 280/300/401 Version 3.80, 3.84 Cause When a new System Program for TAC Xenta devices is released, TAC Menta is not always updated with the latest TAC Xenta version number. Resolution Until the correct TAC Xenta System Version number are available in the TAC Menta, you could use the closest lower version number.

Issue Changes made in TAC vista workstation are not saved in TAC Menta. Change of alarm texts made in TAC Vista workstation are not saved in TAC Menta Change of value of a PVR block made in TAC Vista workstation is not saved in TAC Vista. Environment TAC Vista 5.1 Cause In TAC Vista workstation it is possible to type in texts in the description field that are longer then TAC Menta allows. If you do this no changes made to that signal (block) done from TAC Vista workstation will be saved in the TAC Menta file Resolution Edit the Description for the block so that it is 41 characters of less.

Issue When transferring a value from an analog value to a multistate using object transfer, negative values are inverted. Environment Vista Object Transfers Cause A problem in the Vista software. Resolution This value with need to be converted in Menta first, then connected to the object transfer. The steps to convert the value in Menta are: Select the TAC Xenta device in Vista. Right-click the device and select "Edit". Add an AI block and connect it to a ConversionAA operator. Connect the ConversionAA operator to a DELI block. Edit the DELI block - give the variable a name (Identifier) and make sure the "Public" checkbox is ticked. Save and close the Menta application. Commission and download the updated Mental application. Connect the new variable created in step 5 to the "Object Transfer" object. 

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 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 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 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 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.