Issue Does the Xenta Server firmware version have to match the TAC Vista Server version? Product Line TAC Vista Environment Xenta Servers Xenta 511, 527, 701, 711, 721, 731, 913 Vista Server Cause This situation usually occurs when upgrading a site. After the Vista software has been brought up to the latest version, does each Xenta Server also have to have its firmware upgraded to match? Resolution Whenever possible it is best to have the Xenta Server firmware version match the Vista Server version. However, if this is not possible, then ensure that the Vista Server is always of a later version than the Xenta Server. For example: a Vista 5.1.5 Server is okay with a Xenta 5.1.4 server, but a Vista 5.1.5 Server may not operate correctly with a Xenta 5.1.6 Server. The table below describes the compatibility between the TAC Vista Server, TAC XBuilder and TAC Xenta Server applications/firmware; third party dependency, e.g. java, not considered. More information about the table above including footnotes can be found in the document TAC Vista v5.1.8, TAC Xenta 500 700 900 v5.1.8 - Release Notes section 12.3. Consult the release notices for release software to identify defect corrections, new features, and potential changes in compatibility. If the versions are compatible then the decision to upgrade is up to the user, scheduling, and access to the units in the event of a failed upgrade units are remote. To upgrade a Xenta Server in Vista right click on the Xenta Server and select properties. Change the XBuilder Version property to the version of System Program and XBuilder being used. Note: In a specific situation there has been issues with the Xenta Server password in the properties window in Workstation. In this situation the Workstation was at version 5.1.8, the Xenta server was upgraded to 5.1.9, and then the XBuilder project was downloaded to the Xenta Server again. The Xenta Server was offline in Workstation. When the properties window was opened, the Xenta server password was much longer then it should have been. By reentering the password and clicking Okay, the Xenta Server came back online.

Issue Xenta Server Log Error contains the error line: Generic OS: Too Many Semaphores. 5326 02-Dec-2011 12:47:33 AM fatal  undef  httpdd           1      Generic OS: Too many semaphores.   (Error#:8202) Environment Xenta Server System Error Log Xenta 701, 711, 721, 731 Cause An Application in Xenta 700 consumes too many internal semaphores which cause a fatal error resulting in repeated coldstarts. Resolution Corrected in release 5.1.0 and documented on page 6 of TPA-MALR-08-0009.00. Upgrade to Vista version >5.1.0.

Issue The local time inside a Xenta programmable unit is dependent upon server time, time zone, and daylight savings time settings.  Incorrect DST settings result in incorrect times in the controller which causes problems from incorrect start times on HVAC equipment, to incorrect alarm time stamps in alarm queues. Product Line TAC Vista Environment Xenta Programmables version prior to 3.74 Xenta 280, 281, 282, 283, 300, 301, 302, 401, 401:B Cause In 2007, most of the United States and Canada changed when DST is observed to the second Sunday in March to the first Sunday in November.  Because it had never changed prior to that, programmable controllers retained the old settings (first Sunday in April to last Sunday in October). Resolution The issue was resolved with the release of firmware MOT version 3.74.  Upgrading your controllers to 3.74 is a viable solution, however not always cost effective.  There are two ways to work around the issue. Note: For information on how to download firmware to Xenta programmable devices using the Download Wizard please see Download an .MOT file into a Xenta Programmable controller. Configure TAC Xenta Central DST Settings Refer to the TAC Vista Technical Manual Chapter 19.6 In the folders pane, right-click the folder where you want to place the time event object. Point to New, point to Object, and then click Time Event – Object. Type the name. Open the time event object. On the General tab, type a description. On the Time Event Settings tab, set a suitable repeat interval, for example, first Monday in each week. Click OK. In the folders pane, right-click the folder where you want to place the Central Daylight Settings – Xenta object. Point to New, point to Object, and then click Central Daylight Settings – Xenta. Type the name. Open the Central Daylight Settings – Xenta object. Two options are available. You can use Windows start and end times for the daylight saving time or specify your own start and end times. If you want to specify your own start and end times: Clear the Use Windows settings check box. In the Daylight saving starts box, set the start time for the daylight saving time. In the Daylight saving ends box, set the end time for the daylight saving time. In the Update schedule box, browse to the time event object that triggers the push to the TAC Xenta devices. Click Select. Click OK. Note: You must select Manual DST Mode and Central DST for each controller in the system for a global change to take effect. Manually set DST Settings for each controller The DST Xenta object is not available in all versions of Vista.  If that is not an option, DST settings on each controller can be manually set for the start day and stop day.  Unfortunately, time settings do not allow for designations of "first Sunday" or "last Sunday," only calendar dates.  So each controller will have to be edited each year to maintain correct time settings. In order to facilitate this, this utility:  ODXentaTimezoneChanger was created.  It must be used each year to update the settings, but it will allow you to change all time settings on all controllers in a Vista database simultaneously, greatly reducing the time it takes to correct a system. NOTE: If the Lonworks network has not been properly commissioned & downloaded the tree will not properly communicate with the Vista Server. Check your network tree for asterisks to see if any downloads are required.

Issue Xenta 700 System Report shows "Menta: IO error (Error#:62464) Environment Xenta 700, 701, 711, 721, 731 Cause Some of the causes could be following: Might be configured to use wrong I/O Modules Wrong Neuron ID configured Menta program issues Resolution To resolve this error, check the following: Upgrade Xenta Firmware with Latest Version from the Exchange Extranet. Ensure correct I/O modules are configured. Ensure all the controllers and I/O modules are online.

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 If there are already TAC Xenta 104-A devices commissioned in an LNS database, then it may not be possible to add TAC Xenta 104-A controllers of different system versions into the same database. Nor is it possible to do a replace. Certain firmware versions of the 104-A controller are not compatible with one another. Trying to add a different system version to an existing database will produce an interface does not match error. For more information on this error, see The new program interface does not match the previously defined program interface. (Subsystem: NS, #59). Product Line TAC Vista Environment NL220 LonMaker Vista Cause The incompatibility between different system versions of the TAC Xenta 104-A controller is due to a change that was made in the size of the SNVT declaration area residing in the device memory. The change in device memory occurred between version 1.10 and 1.20. For the same Program ID, LNS requires this size to be the same as previously commissioned devices. Resolution The first action that should be taken is to update the LNS network to the most recent version. It has been confirmed that newer LNS versions have addressed this issue so that no further action is required. With newer LNS software, different version types of the TAC Xenta 104-A may be added to the same database.  If upgrading the LNS software is not an option, the firmware in the controllers can be upgraded as a work around to correct the issue. In order for a TAC Xenta 104-A controller with version 1.10 to reside in the same database as version 1.20, the 1.20 controller must be upgraded to version 1.20A. In similar fashion, version 1.21 must be upgraded to version 1.21A to coincide with version 1.10. To add a 104-A controller with version 1.21 to a database with version 1.20 already on it, no further action need be taken. Version 1.20 and 1.21 are compatible. It is important to reference the compatibility matrix found below. Changing the firmware to an "A" version will then make the controller incompatible with versions 1.20 and 1.21. Also note that it is not possible to upgrade from system version 1.10 to 1.20/1.21 due to the memory configuration. The modified "A" versions will not be loaded into the controllers from the factory. These NXE/APB files will only be available on the Buildings Business Extranet. To download the NXE/APB file for v1.20A or v1.21A, go to The Exchange Download Center. Perform a search for TAC Xenta 104-A Firmware. The 1.20A version will be labeled "TAC Xenta 104-A Version 1.20 (78 Kb)" and the 1.21A version will be labeled "TAC Xenta 104-A Version 1.21A (45 Kb)".

Issue Xenta 102-AX version 2.14 and prior will not honor nviSpaceTemp unless it is bound with a true SNVT binding. This can be an issue in a Vista classic scenario using a Xenta Server to do the connection in XBuilder. Product Line TAC Vista Environment Xenta 102-AX version 2.14 or prior Vista Classic Network Cause The Xenta 102-AX version 2.14 and prior requires a true SNVT binding on nviSpaceTemp from an LNS Management software (LonMaker, NL220). The controller does a check to see if there is a true bound value on the nviSpaceTemp and if it does not exist, it reverts to the hard-wired room temperature sensor. When using the Xenta 700, Xenta 500, or Xenta 900 the controller simply connects the desired temp value to nviSpacetemp via a connection object. This is not a true LNS binding and the controller WILL NOT honor the connected value. Resolution Upgrade the firmware of the Xenta 102-AX to version 2.16 or later. Firmware 2.16 allows the use connection objects in XBuilder to send a value to the nviSpaceTemp SNVT of a 102-AX. Download the latest Xenta 102-AX firmware Instructions on upgrading the firmware are located here: Upgrading a Xenta 102-AX to version 2.16 or later.

Issue Need to download the XIF and NXE files for a SVEA Lon I/O Module DR-N-3D1M (0-10V) module, but having difficulty locating these files on the Extranet. Product Line Andover Continuum, EcoStruxure Building Expert, EcoStruxure Building Operation, Satchwell Sigma, TAC Vista Environment SVEA XIF NXE Cause The difficulty in locating these files, is due to them being identified by their article number, in this case DR-N 3DIM. This number was used when these were classified as the SVEA devices. The Schneider version is now known as MTN881001, and not DR-N 3DIM. Resolution The Schneider Electric (MTN881001) files are located on The Exchange Download Center Download the XIF / NXE files for the SE MN881001 Download the XIF / NXE files for the SVEA DR-N 3DIM Note: It appears that although these devices are both classified as Lon I/O Module 1-10V, the XIF / NXE files are different.

Issue When sending Xbuilder Project to Xenta Server, an error will prompt that the Xbuilder project of hardware version 3 will be sent to a hardware version 2 controller, which is not allowed. Environment Xenta 500/700/913 Hardware version 3 Cause The hardware version setting in the Xbuilder doesn't match the real hardware version of Xenta Server. Resolution There is a hardware version option in the property window of Xenta Server. Check the hardware version of Xenta Server on the label of the controller, and choose the right hardware version in the Xbuilder to match the controller.   For more information about the hardware 3 Xenta Server, refer to TPA-VSTA-12-0029.00.

Issue Where to find documentation about TAC Vista OPC Server and OPC Client, including which versions of the OPC standard are supported in the different versions of TAC Vista OPC Client/Server. Environment TAC Vista OPC Server TAC Vista OPC client TAC Vista OPC tool Cause It is not always easy to know where to look for Vista documentation. Resolution All documentation about TAC OPC can be found in The Exchange Download Center. Search Vista OPC on The Exchange Download Center Narrow results by Asset types (Specification Sheet, Manual, Release Notes, etc...)

Issue Where is the information on LVIS Display/Screen Environment Lon Bacnet Loytec LVIS L-VIS L-VIS Touch Panel for BACnet networks   Cause Information on Loytec L-VIS Resolution The L-VIS from Loytec uses bacnet MSTP or LON. See Product Announcement - LonWorks and BACnet Touch Panels release for more information. All support for this product is via Loytec

Issue When were the different TAC Vista Server versions released? When was Vista Server version 4.X.X or 5.X.X released? Need a list of release dates for TAC Vista Server Need to know approximately how old a Vista site installation is Environment TAC Vista Server Cause It would be interesting to know the release date of the different Vista Server versions Resolution All the Vista release note documents are available on the The Exchange Download Center. TAC Vista 3.11 - 1998-10-21 TAC Vista 3.21 Service Pack 1 - 2000-02-04 TAC Vista 2000 Server and Workstation 3.31 Service Pack 1 - 2001-07-04 TAC Vista 2000 Server and Workstation 3.32 - 2001-09-10 TAC Vista 2000 Server and Workstation 3.33 - 2001-12-20 TAC Vista 2000 Server and Workstation 3.33 SP2 - 2002-11-15 TAC Vista IV Server/Workstation/Menta 4.01 - 2003-02-21 TAC Vista IV Server/Workstation/Menta 4.10 - 2003-10-24 TAC Vista IV Server/Workstation/Menta 4.2 - 2004-03-10 TAC Vista IV Server/Workstation/Menta 4.2.1 - 2004-04-19 TAC Vista IV Server/Workstation/Menta 4.2.2 - 2004-06-24 TAC Vista IV Server/Workstation/Menta 4.2.3 - 2004-11-30 TAC Vista IV Server/Workstation/Menta 4.2.5 - 2005-03-21 TAC Vista Server and Workstation 4.3.0 - 2005-04-29 TAC Vista Server and Workstation 4.3.0 SP1 - 2005-05-25 TAC Vista Server and Workstation 4.3.1 - 2005-07-15 TAC Vista Server and Workstation 4.3.1 SP1 - 2005-10-31 TAC Vista Server and Workstation 4.4.0 - 2005-12-16 TAC Vista Server and Workstation 4.4.1 - 2006-03-13 TAC Vista Server and Workstation 4.4.2 - 2006-05-29 TAC Vista 4.5.0 - 2006-07-05 TAC Vista 5.0.0 - 2006-11-15 TAC Vista 5.0.1 - 2007-04-26 TAC Vista 5.0.2 - 2007-09-28 (first version to support Xenta 700) TAC Vista 5.0.3 - 2008-01-21 TAC Vista 5.1.0 - 2008-06-03 TAC Vista 5.1.1 - 2008-10-27 TAC Vista 5.1.2 - 2009-04-15 TAC Vista 5.1.3 - 2009-09-24 TAC Vista 5.1.4 - 2010-03-31 TAC Vista 5.1.5 - 2011-01-25 TAC Vista 5.1.6 - 2011-07-04 TAC Vista 5.1.7 - 2012-01-03 Note: All dates are in the form [year]-[month]-[date]  

Issue What wall module (room sensor) to use for the TAC Vista series controllers Environment TAC Xenta 101, Xenta 102, Xenta 103, Xenta 104 TAC Xenta 301, Xenta 302, TAC Xenta281,  Xenta 282, Xenta 283 TAC Xenta 401 Cause Need to know what sensors to use Resolution Use the Sensor selection tool

Issue Have two LNS databases and need to share values between them. Environment Lonmaker Newron NL220 Vista Cause As the two LNS networks are not connected you cannot bind values between them. You can use a Object transfer in Vista or a Loytec L-Proxy controller Resolution The main difference between the two methods is the object transfer is PC based and the Loytec option is field based.  Object Transfer option: Add an object transfer as described in the Chapter 14 of the TAC Vista Technical Manual. L-Proxy Loytec controller option: This product will reside on both LNS channels and can be setup to transfer values across networks. Here is a link to the product . From here scroll down to find the L-Proxy Datasheet

Issue Some security software will report that there are vulnerabilities for SSL of Xenta Server. Some vulnerabilities look like: SSL Server allow anonymous authentication vulnerability SSL Server allow Cleartext communication vulnerability  Weak encryption model Environment Vista I/NET Cause This is how Xenta Server designed to work. Resolution There is a security enhancement for Xenta Server in Xenta 5.1.9. Update the firmware to Xenta 5.1.9 will fix these vulnerabilities. You can download Xenta 5.1.9 from Buildings Download Center.

Issue Unable to relay Email not working Product Line TAC Vista Environment Vista SMTP Cause If an error "Unable to relay" is returned, this is most likely because authentication is not sent to the SMTP server. Resolution Go to Vista Server settings At the email tab set proper authentication (TAC Vista Technical Manual Chapter 3.3 explain this more in detail) You may need to consult with the IT department on site For more information on troubleshooting sending emails from a Vista server, see Troubleshooting Sending Emails from a Vista Server.

Issue Vista compatibility for video integration in Workstation. Product Line Pelco, TAC Vista Environment Vista Workstation Integral Digital Sentry 4.1/4.2, 7 Cause To pull video into a Vista Workstation front end, the digital recorder software version must be of the correct type and version. Resolution Download TAC Vista Compatibility Matrix for a complete list of Vista compatibility.  < <   5.1.8 5.1.7 5.1.6 5.1.5 5.1.4 5.1.3 5.1.2 5.1.1 5.1.0 5.0.3 5.0.2 5.0.1 5.0.0 Integral Digital Sentry 4.1/4.2 X X X X X X X X X         Integral Digital Sentry 7 X X X X X                   Only Pelco Integral Digital Sentry DVRs are compatible. Individual DVRs are not listed for Vista compatibility because Vista is actually communicating with the Digital Sentry software, which is running as a Video Server.  Ensure the software version is Digital Sentry 4.1, 4.2, or 7, depending on the Vista version.

Issue Remote Alarm Manager running with TAC Vista loses the connection to the license file. Environment RAM pre 2.1 Remote Alarm Manager License file Cause Remote Alarm Manager fails to recover after its license management briefly loses a valid license from the TAC license server Resolution This issue is now corrected by installing the RAM Software Release 2.1 Then follow the upgrade options in the RAM Release 2.1 Release Notes documentation.

Issue Vista 5.0.3 Graphics Editor crashes when you right-click on a graphics page in Workstation and click edit. Here is the error message: Could not load file or assembly 'TAC.Interop.TacosOI, Version=5.0.0.0, Culture=neutral, PublicKeyToken=null' or one of its dependencies. The located assembly's manifest definition does not match the assembly reference. (Exception from HRESULT: 0x80131040) FileLoadException at TAC.Graphics.Windows.Vista.VistaSystemProxy.Create(String server, String user) at TAC.Graphics.Editor.EditorApplication.CreateApplicationForm(ReadOnlyCollection`1 commandLine) in C:\TAC\VistaSw\V5030\Graphics\Editor\EditorApplication.cs:line 90 at TAC.Graphics.Editor.SingleInstanceApplication.<>c__DisplayClass3.b__1(Object splashFormSender, EventArgs splashFormEventArgs) in C:\TAC\VistaSw\V5030\Graphics\Editor\SingleInstanceApplication.cs:line 79 at System.Windows.Forms.Form.OnShown(EventArgs e) at System.Windows.Forms.Form.CallShownEvent() at System.Windows.Forms.Control.InvokeMarshaledCallbackDo ThreadMethodEntry tme) at System.Windows.Forms.Control.InvokeMarshaledCallbackHelper(Object obj) at System.Threading.ExecutionContext.runTryCode(Object userData) at System.Runtime.CompilerServices.RuntimeHelpers.ExecuteCodeWithGuaranteedCleanup(TryCode code, CleanupCode backoutCode, Object userData) at System.Threading.ExecutionContext.RunInternal(ExecutionContext executionContext, ContextCallback callback, Object state) at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state) at System.Windows.Forms.Control.InvokeMarshaledCallback(ThreadMethodEntry tme) at System.Windows.Forms.Control.InvokeMarshaledCallbacks() Environment Vista Workstation 5.0.3 TAC TGML Graphics Editor 1.0.3 Cause An error occurred at installation and the Graphics Editor must be removed completely and reinstalled. Resolution Shutdown the Vista Server and Workstation. Uninstall the TAC Graphics Editor 1.0.3 from the Control Panel of the PC. Delete the entire C:\Program Files\TAC\GraphicsEditor directory that is left behind from the un-install. Download the TACGraphicsEditor103.exe from The Exchange. Re-install the TACGraphicsEditor103.exe

Issue How to configure an exception mode of a TAC Xenta 121 device to use terminal load as the activation input. Environment TAC Xenta 121-HP TAC Xenta 121-FC ZBuilder Cause To use Terminal Load in an Exception mode both the version of ZBuilder as well as the version of the system program of the TAC Xenta 121 device must be taken into consideration.  Resolution TerminalLoad used as input to Exception mode in Xenta 121 ZBuilder version Firmware <1.14 Firmware 1.14 Firmware > 1.23 < 5.1.3 No Yes 1 No 5.1.3 No Yes 1 Yes 2 5.1.4 No Yes 1 Yes 2 5.1.5 or later No Yes 1 Yes 1 Only exception modes 7 and 8 can be used for this; this is done by selecting Space Temp as the activation input for the exception mode and also setting nciAppOption2.bit12 manually in the device (in Vista Workstation this point is Applic.UCPTappOptions2.bit12). These steps are described in TPA-MALR-09-0003.00. 2 Only exception modes 7 and 8 can be used for this; the activation input can be correctly set as Terminal Load in the exception mode in ZBuilder.