Issue The TAC Xenta Operator Panel does not hold steady when navigating down into programmable controller point lists. At random times the OP will back out and return to the main screen with the list of programmable controllers. Product Line TAC Vista Environment Operator Panel (OP) Vista Cause The XENTASYSREG bit 0 does not work in version 3.87 of the Xenta programmable controllers.  Resolution The latest firmware hotfixes need to be downloaded and installed for the corresponding TAC Xenta programmable controllers. For all Xenta Versions, download Hotfix version 3.88

Issue In Vista 5.1.1 an "Unable to request license" alarm appears every minute, although the license is installed and the system is operating correctly. Environment Vista 5.1.1 Cause Software limitation. Resolution Install TAC Vista Server and Workstation 5.1.1 Hotfix 17. This replaces hotfix 11 where this issue was originally addressed. See TPA-MALI-08-0022.01 for details.

Issue When logging into the web server of a Xenta controller using Mozilla Firefox 4 an error message is shown stating that the website is using an invalid security certificate.  When logging into Xenta server using Firefox 4 a certificate error is displayed as displayed below: The complete error screen reads as follows: This Connection is Untrusted You have asked Firefox to connect securely to 192.168.1.152, but we can't confirm that your connection is secure. Normally, when you try to connect securely, sites will present trusted identification to prove that you are going to the right place. However, this site's identity can't be verified. What Should I Do? If you usually connect to this site without problems, this error could mean that someone is trying to impersonate the site, and you shouldn't continue. Get me out of here! Technical Details (IP Address of Xenta) uses an invalid security certificate. The certificate is not trusted because it is self-signed. The certificate is only valid for (IP Address of Xenta) (Error code: sec_error_ca_cert_invalid) I Understand the Risks If you understand what's going on, you can tell Firefox to start trusting this site's identification. Even if you trust the site, this error could mean that someone is tampering with your connection. Don't add an exception unless you know there's a good reason why this site doesn't use trusted identification. Add Exception... How to install a self signed certificate. Product Line Satchwell MicroNet, TAC INET, TAC Vista Environment Mozilla Firefox 4 Xenta 511, Xenta 527, Xenta 555, Xenta 701, Xenta 711, Xenta 721, Xenta 731, Xenta 913 SSL Cause The default certificate in the Xenta web server is a self-signed certificate. Since the certificate is not issued by a recognized Certificate Authority the web browser (in this case Firefox 4) cannot validate the authenticity of the certificate and suggests that the user not continue to the website each time the user tries to access it. Resolution There are two possible resolutions: Install the self-signed certificate using the following steps: Expand the "I Understand the Risks" bullet then click the "Add Exception" button. Firefox will automatically retrieve the certificate from the Xenta server. Make sure to check "Permanently store this exception" and then click "Confirm Security Exception" The certificate is now installed and the warning screen will no longer show up when logging into the server. It may be necessary to restart Firefox for the changes to take effect. Note: The certificate will need to be installed in each client computer that accesses the Xenta server but once this complete it does not need to be done again. The exception to this is if the web address of the Xenta server is changed or if Firefox is uninstalled then reinstalled. Update: Starting in September 2014, all major browsers will be disabling 1024-bit roots within their trusted roots stores. Any SSL certificates chained to a 1024-bit root will no longer work on any browsers that takes this action or one that relies on another's root store (the self-signed certificate is 1024-bit). This means that you will still get the security warning even if you have installed the self-signed certificate. Purchase a certificate issued by a Certificate Authority (CA): These certificates are pre-installed into the web browser and will automatically prevent certificate errors from occurring on all client computers that access the web server. Note that these can be quite expensive and unless the Xenta web server is being hosted on the internet they are not necessary. Please see TAC Xenta Server - TAC Networks - Technical Manual for more information. See "There is a problem with this website's security certificate." when logging in to Xenta web server using Internet Explorer 8 for information on installing certificates into Internet Explorer.

Issue In TAC Vista 5.1.9 when trying to lock a license file to an end user dongle, the taclic vendor daemon starts briefly, but then stops again and you see the error "Invalid license key (inconsistent authentication code)" in the taclic.log file. Usually you only see that message if the license file has been tampered with. 8:48:28 (taclic) Invalid license key (inconsistent authentication code) 8:48:28 (taclic) ==>INCREMENT Menta.View taclic 5.1 permanent 1 ISSUER=TAC \ ISSUED=30-may-2014 BORROW NOTICE=3424672 \ SN=FID__47eba299_146164ca427__7ec5 SIGN="13DC 795D AF25 E8ED \ D6EG 7BAA 8495 2ED7 B4B0 F6E4 EDD8 C3C1 6EAE 2BF0 598D 0759 \ AE4A 3C9E 391C A6ED B313 9971 369A 349C 8671 E194 2E42 E2DC \ 8A9A 7905" Product Line TAC Vista Environment TAC Vista 5.1.9 License Server Cause An issue has been detected in TAC Vista 5.1.9 when locking a license file to an end user dongle. You see the error "Invalid license key (inconsistent authentication code)" in the taclic.log file. The error is located in the taclic.exe file. Resolution Contact PSS for a permanent hotfix for this issue, or download it from Exchange Download Center.  Work around 1: Lock the license to the MAC address of the PC Follow Rehosting a Vista 5 License on the FlexNet License Server to rehost a license file to a MAC address.  Work around 2: Use a previous version of the taclic.exe file Access a PC having a previous version of the license server installed Locate the file "taclic.exe" and copy it - it's normally located in the TAC Vista installation folder under "License Server" Stop the license server on the PC having TAC Vista 5.1.9 installed Rename the original taclic.exe file to taclic_11.12.exe Paste the "taclic.exe" file you copied into the folder Start the license again  In general when working with the license system on TAC Vista versions from 5.1.8 and above, this utility can come in handy: TACLicenseServer Settings.

Issue Error message when opening Vista 5.1.5 Webstation: "HTTP Error 404.2 - Not found. The page you are requesting cannot be served because of the ISAPI and CGI Restriction List settings on the web server." Product Line TAC Vista Environment Windows 2008 server (32-bit & 64-bit). Webstation 5.1.5, 5.1.6, 5.1.7 Cause ISAPI (Internet Services Application Programming Interface) and CGI (Common Gateway Interface) services are not activated by default in Windows 2008 Server. Resolution After following the installation instructions in the Vista 5.1.5 TPA-VSTA-11-0002.01 (or Send to controller fails with "Not enough memory" error in Distribution View) do the following: Click on Start and then Run. Type inetmgr Once Internet Information Services Manager has opened, change to "Detail View" in the View menu. Double-click on ISAPI and CGI Restrictions Feature.   Under the "ISAPI and CGI Restrictions" right-click on ASP.NET v4.0.30319 and select "Allow". Webstation should now work.

Issue Error: "Could not create remote directory" or "Failed to establish connection with the target device" when trying to upgrade/downgrade a Xenta 5/7/9xx controller     Product Line TAC INET, TAC Vista, Satchwell MicroNet Environment Xenta Servers Xenta 511, 527, 527-NPR, 555, 701, 711, 721, 731, 913 XBuilder Warning Potential for Data Loss: The steps detailed in the resolution of this article may result in a loss of critical data if not performed properly. Before beginning these steps, make sure all important data is backed up in the event of data loss. If you are unsure or unfamiliar with any complex steps detailed in this article, please contact Product Support for assistance. Cause This error can be caused by any of the following reasons: Trying to downgrade a Hardware version 2.x Xenta Server device to System Program version 2.10 or older Internet Options are configured to use a proxy server IP communication is not properly established due to incorrect IP settings, a bad cable or a faulty device The controller is 5.1.8 or lower and Microsoft KB 2661254 or KB 2661254-V2 is installed on the PC. In this upgrade Microsoft has changed the criteria for the certificate Key. Service packs are available on the extranet to correct this issue. Download blocked because of other Windows updates SSL 2 and 3 is not activated Resolution First, establish that the System Program that you are attempting to load is compatible with hardware version of the device. The older HW 1 versions can be upgraded to System Program 5.1.2 or older. Only system program versions 2.2.0 and newer can be loaded into devices that are hardware version 2.X. Hardware Version System Program 1.0 5.1.2 or older 2.X 2.2.0 or newer 3.X 5.1.6 SP1 or newer Note: Hardware version 1 devices are not labeled as HW 1 since only one version of hardware existed at the time. Hardware devices can be identified by the lack of any hardware version printed on the Neuron ID sticker. Note: If running the firmware update software, ensure you are running as an administrator. Next, check to verify that IP communications are configured properly and are functional: Check the IP address defined in XBuilder Verify a good connection to the IP port of the controller (10Base-T port on the far right) with a crossover cable. If that is all good, then a reformat of the controller may be necessary. Connect via Hyperterminal to the unit and at the dsh> prompt type format and press enter command . This will recreate the directory structure of the controller and allow you to attempt the upgrade/downgrade again. Finally, verify that the Internet Options are not configured to use a proxy server or, if they are, temporarily change them as follows: To temporarily change this setting follow these steps: In Internet Explorer select the Tools Menu and select Internet Options. Or select Internet Options from your Control Panel. Go to the Connections tab. Click the LAN settings button. Uncheck the Use a proxy server for your LAN box. Click Ok in the LAN settings window and the Internet Options window. Complete the System Program download. Return to the Internet Options window and re-check the Use a proxy server for your LAN box in the LAN Settings found in the Connections tab. Another Matrix explaining the compatibility of each with Vista versions can be found in Xenta-Server-firmware-versus-Vista-Server-versions If you have the Xenta FW 5.1.8 or lower and KB 2661254 or KB 2661254-V2 were installed during a Windows Update you will need install the service packs. These new service pack builds have been released and are available on the extranet. See TPA-VSTA-12-0028.00 - TAC Xenta Servers, Not Possible to Download Firmware for more info. Another issue has been reported to support relating to the bit length of the Xenta server boot certificate. The Xenta server installer uses a 512 bit key length of the boot certificate, and Windows in some instances can be configured for a 1024 bit length certificate. If the issue still exists after removing the above mentioned Windows Updates, or if you are getting this error and the Windows Updates are not on your machine. Download the attached tool, Allow Weak Certificates.zip, and execute the file, chose "Allow Weak Certificates", and "Update".   Here is what the tool set: Windows Registry Editor Version 5.00 [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Cryptography\OID\EncodingType 0\CertDllCreateCertificateChainEngine\Config] "EnableWeakSignatureFlags"=dword:00000002 "minRSAPubKeyBitLength"=dword:00000200 If taking the preceding steps fails to resolve the issue then see the following articles for additional steps that can be taken: Xenta Server "Run" light is solid red, with no communication via Ethernet,  Fail to upgrade the TAC Xenta Server system software (firmware)  An unexpected error occurred while downloading using a Xenta Server

Issue Vista 5.1 license is not working.  Trying to launch Vista components results in error:  lc_checkout failed: Cannot checkout an uncounted license within a Windows Terminal Services guest session. Environment Vista 5 Terminal Services Virtual Machine VM Cause There is a special feature needed in the license which allows the use of Terminal Services. Resolution You must download the 14 day Demo TS Evaluation License on The Exchange Download Center. *note that Terminal Services are only supported in Vista 5

Issue In a web graphic hosted on a Xenta Server, clicking to change a value displays the dialog momentarily, then it immediately disappears. Product Line TAC Vista Environment Xenta server Cause The Java version is too new or too old. Resolution Make sure The java versions installed have been tested against the installed Xenta version. A Compatibility Matrix can be found on The Exchange Download Center. Or see Software and Firmware compatibility matrix for older versions of the traditional product lines. If the wrong versions are installed, download the correct version and install it.

Issue What effect do Central Time Charts have on a Xenta time schedule object? Can the Central Time Chart be selectively overridden at individual units? Making changes to a Xenta time schedule results in the following Information message: A central week chart and a central alternative chart are defined. any changes made in the chart will be overridden by the central charts. Xenta time schedule events are shown with an asterisk (*) next to the start time. Environment Vista Workstation Time Chart - TAC Xenta Time Chart - Global Time Chart - Local Cause If a central time chart has been defined for a Xenta time schedule object, the central time chart will override the operation completely (both for scheduled on and scheduled off times). Resolution Double click a Time Chart - TAC Xenta object in Vista Workstation. The edit dialog is shown. Click on the third tab, Central Time Charts Select either a Time Chart - Global or a Time Chart - Local object to override the Xenta time schedule object. This can be done selectively for just Weekly recurring events, just Holiday alternative events, or both. Once selected, all events defined in the Xenta time chart will be shown with asterisks (*) indicating that they are being overwritten by a Central Time Chart. Exceptions cannot be made to the Central Time Chart for individual units. Refer to the TAC Vista Technical Manual Chapter 19.1 Time Charts for additional information.

Issue Object type "Time Chart - Global" does not update local time schedule in a Xenta programmable controller. Environment Vista 5.1.6 and below Xenta programmable controllers Xenta 281, 282, 301, 302, 401 Cause After changing a "Time Chart - Global," changes are sent out to all time schedules located in the associated Xenta units. If the Xenta is busy when this update occurs, it can take too long for the update to arrive and a time-out happens. This causes the Xentas to not get updated. Resolution Various time chart/time schedule updates have been corrected in Vista 5.1.7 and more are to come in 5.1.8. Please read the latest updates in the TPA

Issue What is the wiring for the RS-232 A, RS-232 B, RS-485 A, RS-485 C, and 10Base-T ports on a Xenta Server? Product Line Satchwell MicroNet, TAC INET, TAC Vista Environment Xenta Servers Xenta 511, 527, 555, 701, 711, 721, 731, 913 BACnet/IP BACnet MS/TP M-Bus C-Bus Lon Modbus Cause The wiring and pin outs for the Xenta Server hardware is detailed in chapter 2.1.2 of the TAC Xenta 500/700/911/913 Product Manual . Resolution The ports and wiring is unique for each port. RS-232 A port For serial communication it is typical to only connect the RX, TX, and Ground pins. Pin 3 4 5 Serial Cable RX TX Ground  RS 232 B port   10 Base-T port (Web connection) Note: The Xenta 913 also supports BACnet/IP and Modbus TCP/IP on this port. RS 485 A port (Modbus) Note: The Xenta 913 also supports BACnet MS/TP on this port. If two wire communication is being used then only use pins 5 and 6. Pin 5 6   + - If four wire communication is being used then all four pins will be used. Pin 5 6 7 8   TX + TX - RX + RX - RS485 C port (I/NET) This port is used for I/NET communication. Pin 19 20   + -

Issue Xenta Server reports it is in FAILSAFE mode without shorting out terminals 9 and 10. After connecting via HyperTerminal, restarting and trying to reset the IP address, the screen continues to scroll back to dsh/> Xenta Server has gone offline and can not connect directly to it using Ethernet. The Run light is flashing Green on first start up but then reverts to red and the LON light also flashes red. During boot up it pauses and reports an error (via HyperTerminal) in loading the RAM disk.  IP Address is set to 172.22.1.5 and can not change it.  Not able to load any firmware into the device – error received. "Error: Could not create remote directory." Product Line Satchwell MicroNet, TAC INET, TAC Vista Environment Xenta Server 527, 511, 555 Xenta Server 701, 721, 731 Cause Unknown corruption of the Xenta Server hard drive / flash drive, possibly due to electrical noise. Resolution To attempt to recover this device, try to format the device’s flash drive. To achieve this you can follow these steps using HyperTerminal or an equivalent application: (For further assistance with connecting to Xenta Servers and HyperTerminal refer to Connecting a serial cable to a Xenta 5/7/9xx controller).   Login and type the command FORMAT.  (May require device to be placed physically into the fail-safe mode by shorting terminals 9 and 10). The format command can take up to 3 minutes to complete but you should see the confirmation through HyperTerminal while this is occurring. If you have placed the device into Fail-safe mode, remove the link on terminal 9 & 10. Restart the device, by either cycling the power or typing the command RESTART through HyperTerminal. Set the IP address and IP settings (command SETIP). Install the latest firmware. You can download the latest firmware from The Exchange Extranet; ensure that you use the correct version since there various versions for the Xenta Servers. Run the firmware download to the device. During the download you may receive an error regarding "Failure to get the hardware version from the target device…", select OK Continue the installation The download will then occur, it will take some time and may appear that the software is not responding but this is normal. Be patient and if you don’t receive any errors then all should be ok. The device should now restart, after a 1-2 minute window the “RUN” LED should be a solid green. If after following these procedures, the device is still not responding as expected please send into Repairs via your normal repair process.

Issue Will the data in the Xenta Server still be intact after a power failure? How long is the "power outage protection time" for the various Xenta servers? Environment TAC Xenta 511 TAC Xenta 527 TAC Xenta 555 TAC Xenta 701 TAC Xenta 711 TAC Xenta 721 TAC Xenta 731 TAC Xenta 911 TAC Xenta 913 Cause Needs to know how the Xenta Server handles a power failure Resolution Power Outage Protection – Settings like configurations and web pages are stored in the non-volatile (flash) memory and will not be lost in the event of a power outage. A built-in capacitor maintains operation of the RAM memory for at least 72 hours in the event of a power outage. More information may be found in the TAC Xenta 500/700/911/913 Product Manual, chapter 2.1

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