Issue i2 controllers randomly go offline then back online 10 minutes later. During this period of showing as offline, all points under the i2 controller can be viewed. Environment Continuum i2xxx Controllers Netcontroller II (CX9680) Cause After an i2 controller goes offline on a noisy Infinet, the Netcontroller II can miss receiving the reconfig of the i2 controller coming back online. It fails to see the i2 controller come back online but still continues passing requests down to it and receiving responses. After 10 minutes of not receiving the token, the i2 controller announces that it is on the bus. At this point the Netcontroller II gets the controller online message and the network reconfigures again bringing in this controller to the token pass. Resolution This has been fixed in a new build of the Netcontroller II v2.100031 which can be found at the link below. Netcontroller II v2.100031

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

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 Upgraded CX9200 chips and not able to load Bacnet PTP xdriver Environment Continuum Cyberstation CX 9200 Bacnet Xdriver Cause Upgraded chips on CX9200 and cannot load the Bacnet PTP xdriver. Resolution Use the latest Bacnet PTP xdriver version BacnetPTP1.00001.xdr

Issue XIF files for the standard MNL controllers are available on The Exchange Download Center.  Please do not use with SmartStruxure.  See XIF files for Version 1 and Version 2 of MNL controllers. Product Line TAC IA Series Environment I/A Series standard (fixed profile) controllers: MNLRF2 - Fan Coil profile MNLRH2 - Heat Pump profile MNLRR2 - Rooftop profile MNLRS1 - Satellite 1 / Rooftop profile MNLRS2 - Satellite 2 / Rooftop profile MNLRV2 - VAV profile MNLRF103 - Fan Coil profile MNLRH103 - Heat Pump profile MNLRR103 - Rooftop profile MNOTPVA3 - VAV profile MNLRF3 - Fan Coil profile MNLRH3 - Heat Pump profile MNLRR3 - Rooftop profile MNLRS3 - Satellite 3 / Rooftop profile (revised previous Satellite 1) MNLRS4 - Satellite 4 / Rooftop profile (revised previous Satellite 2) MNLRV3 - VAV profile Cause XIF files are available if needed. Resolution Download the file TAC_LLC.zip from The Exchange Download Center. Also see the accompanying Readme file.

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 Enabling XDriver on the first generation of controllers, 9200, 9400, 9940, 9900 including the enabling of TCP/IP Product Line Andover Continuum Environment Older Continuum sites Cause Connectivity to third Party devices using the old NCI or First Generation Controllers requires an updated file. Resolution For 1st generation controllers, a .upd file is needed to turn on the bit for the Comm port. There is 1 bit per port to enable X Driver then a second bit to enable IP X Driver support required for the Modbus TCP/IP driver. The same principle applies to the generation1, 9200, 9400 controllers.   These controllers have flash memory just for things like the Serial number, model num, & X Driver settings, even though the controllers have EEPROM's for the firmware   As far as loading these drivers using hyperterminal, apart from firmware, one can load the X Driver file/ code through hyperterminal if required, but easier to do through Cyber'.   These files which enable the Xdriver for the Comm port, and TCP/IP are available by filling out the Driver Request Form, then they will be emailed directly to the customer from the factory in U.S.   X Driver list (Search for 'Third Party Driver List') and Order Forms (Search for 'xdriver order form') are located on the Exchange Download site  Difference between first and second generation controllers, visit What is the difference between 1st and 2nd Generation X Drivers. For information on Physical Ports, visit What controller ports and physical standards are supported by the Modbus X Drivers?  For Second Generation Controllers, visit How to order a controller with or upgrade a controller to have XDriver support.

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.