Building Automation Knowledge Base

Issue If you are integrating LON to I/NET with a Xenta 527 or Xenta 913, you may run into a unit conversion problem in the integration process. Product Line TAC INET, TAC Vista Environment I2V I/NET LON Integration Xenta 527, Xenta 913 System Program Version 5.0.0 or higher XBuilder 5.0.0 or higher Cause When integrating LON to I/NET, all data will make its way to I/NET in SI units. Resolution View the units of the points on the LON side of the connection object in XBuilder. On temperature, for example, XBuilder uses the unit "F" to show Fahrenheit on a temperature signal. However this temperature value will show up in I/NET in Centigrade.  Engineering units on the AO point in the I/NET controller will have to be "F" to mirror the unit on the LON signal in XBuilder. These two units have to match exactly, and they are case sensitive. When the engineering units match on both points, I/NET will convert to the correct value. If the value on the I/NET side is left blank, it will just pass on the Celsius value. There are limitations to this conversion since I/NET has a four-character limit and some units in XBuilder will exceed this. Pressure, for example, will have to be sent in Pascals or PSI. 

Issue After upgrading Vista, upon opening reports you receive the error "Report is of a previous format. Please try updating the database again." Environment Upgraded Vista Workstation Reports Cause Version property may need to be set for each report that needs to be upgraded. Resolution Upgrade the current database. You may have to change the Version property for each report that needs to be upgraded. Right-click on the report, select Properties while pressing down CTRL + SHIFT. This opens the 'advanced' properties dialog. If Version is 1 change it to 0. Run regedit to open the Registry Editor. Open 'HKEY_LOCAL_MACHINE\SOFTWARE\TAC AB\TAC Vista\4.2' (Select folder that matches your version of Vista) and locate the key 'UpgradeReports'. Set this value to 1. (0 means do not upgrade.) Start Vista Server and the reports in the database should be upgraded properly. The file UpgradeReportsLog.txt in the database folder $log contains detailed information about the upgrade process.  

Issue Xenta 121 temperature calibration precision problem Environment Xenta 121 ZBuilder Cause Calibration of a temperature input on a Xenta 121 controller is limited to whole increments in degrees Celsius. Resolution To allow greater precision in calibrating thermistor inputs on the 121 in either Fahrenheit or Celsius do the following. Note: Any LonMaker drawings or LNS databases that are open ought to be closed (and backed up) before doing this. In the file C:\LonWorks\types\User\TAC\Xenta100.fmt, find the following three consecutive lines: UCPTIOOffsetB1: text("%d"); UCPTIOOffsetB2: text("%d"); UCPTIOOffsetU1: text("%d"); Replace with the following six lines: UCPTIOOffsetB1#SI: text("%f"); UCPTIOOffsetB1#US: text("%f", *1.8+0(0:855)); UCPTIOOffsetB2#SI: text("%f"); UCPTIOOffsetB2#US: text("%f", *1.8+0(0:855)); UCPTIOOffsetU1#SI: text("%f"); UCPTIOOffsetU1#US: text("%f", *1.8+0(0:855)); This will allow precise calibration in the user's default temperature format. 

Issue Cache Time for Record Changes - Xenta 527 for Vista - I/Net systems. Environment I/NET Seven integrated under Vista Xenta Server 527 / 731 Cause When using the Xenta 527 Web Server to view records in Vista from I/Net Seven, changes that are made do not show up immediately. Cached data does not reflect any recent changes made in the original SQL Host database. Once data has been stored in the local cache, the Cache timeout must expire before the data can be updated by retrieving it from the SQL Host. The default time is set to 720 minutes, which allows the device to store data read from the SQL host for twelve hours.   Resolution The default time is set to 720 minutes, which allows the device to store data read from the SQL host for twelve hours. If the user wants to see the changes made and not wait for that period, they can connect to the device and change the Cache Time. If the system is large, this may affect performance and cause slow down because of the volume of data that is coming through. Choose a time that is best suited for the application. However, by restarting the device it also gets an update from the SQL Host.

Issue Xenta 102-AX effective setpoint output is perpetually offset by a fixed unadjustable amount Environment Xenta 102-AX Cause There is a variable in the memory of the Xenta 102-AX that can offset the space temperature setpoint.  It is set when adjusting the space temperature setpoint with an M/STAT and pressing Enter -- which is not a step required to make the adjustment.  From then on, this other variable will feed the M/STAT/STR-250 adjustment. Resolution The only way to clear the invisible offset is the same way it was set: Configure the setpoint display to show normalized.  This will stop the setpoint from shifting between heating and cooling setpoints while it is being adjusted. Connect the M/STAT and adjust the setpoint to the intended, non-adjusted value and hit Enter again. Once the problem is corrected, remember not to hit the Enter key when adjusting the setpoint from the M/STAT.  This shouldn't be an issue for customers since the STR-250 doesn't have an Enter key.

Issue   Xenta 700 Menta viewer in Internet Explorer displays some blocks at half-size Environment Xenta Server Xenta 701, 711, 721, 731 Menta Internet Explorer Cause Illegal characters in the description field of the point has caused problems with the web interface live Menta viewer. Resolution Verify that there are no strange characters in the description field of the point. In the most recent case, the = sign caused the block to shrink.

Issue TAC Xenta 280/300/401, the Menta application could stop due to one of the Week charts or Holiday charts in a TSCH block Max set to 0 (zero). Environment Xenta programmable controllers up to version 3.74 Xenta 280, 281, 282, 283, 300, 301, 302, 401, 401:B Menta TSCH block Cause Setting the maximum number of either Week Charts or Holiday Charts to 0 will cause this error. Resolution Make sure that you set Max to at least 1 for both the holiday and the week charts, even if you only are going to use one of the charts.

Issue Unable to create new OGC graphic pages in Xbuilder 5.0.2 or later.  The edit option has been grayed out and I cannot open the OGC graphic editor. Environment XBuilder TGML Graphics Editor Vista Cause In Xbuilder 5.0.2 the system was changed to support UTF-8 character encoding. Since OGC Graphics pages cannot support this change all new graphic pages added to XBuilder will be forced to be TGML pages which support the UTF-8 character encoding.  Resolution OGC graphics created in earlier versions of XBuilder will still display properly when those projects are upgraded to newer versions of XBuilder but they can no longer be edited. If changes need to be made to these files you can follow one of the two options listed below:  #1. In order to make changes to these graphics the files must first be upgraded to TGML graphics. This is done by opening the OGC graphics with the TGML editor and the graphics will be automatically updated. #2. It is possible for 2 versions of XBuilder to reside on one PC. You can download the 5.0.2 version of XBuilder and use this version of the tool to make the necessary changes. Once the changes are made you will save the project and open the edited project in the newer version of XBuilder.  

Issue In Xenta Server's web interface, web pages are displayed incompletely. Environment Xenta Server Xenta 511, 527, 701, 711, 721, 731, 913 HP and Siemens PCs Cause Hyperthreading has been found to be a problem on some PCs. Resolution Disable Hyperthreading in the PC's BIOS. This issue has been found on some HP and Siemens PCs.

Issue TAC Xenta 120, up to version 1.08, CO 2 input as 2-10 Volt Environment Xenta 121-FC ver 1.08 and earlier Xenta 121-HP ver 1.08 and earlier Cause The input is designed for 0-10 volt signal and will be offset by 20% if a 2-10 volt sensor is applied. Resolution When 0-10V for input is used the 120 will multiply the voltage by the scale factor: V * S = CO 2 reading. When 2-10V for input is used the 120 will multiply the voltage by an adjusted scale factor: V * ((S*10) / 😎 = CO 2 reading. When using a 200ppm Scale factor this results in a reading of 600 ppm when reading 3V on a 0-10V input and 250 ppm when reading 3V on a 2-10V input. This behavior is not correct, and needs to be corrected in a future release.  

Issue How to change the default XBuilder project location. Environment XBuilder Cause The default XBuilder project location is in the hidden Application Data folder. Some would prefer to have this default to their usual projects folder on the hard drive. Resolution Go to Start > Run > and type 'regedit' Go to HKEY_CURRENT_USER > Software > TAC > TAC XBuilder X.X.X >Options X.X.X is the version of XBuilder e.g. 5.0.3 Change the "ProjectLocation" key

Issue Unable to delete disabled alarms that no longer exists in the TAC Vista Db. Environment Vista Workstation Alarm Queue Cause If you delete alarm objects that have previously been disabled in the database these alarms will still be in the Disabled alarm list.  Resolution In the database folder in $thisdb there are 2 files called $this.blk and $this_bp.blk that contain the disabled alarm list. Close TAC Vista server and open these files with notepad. Find the alarm that no longer exists and delete the whole line. Save the files and restart the TAC Server.

Issue What is the difference between the XIF and NXE files in any LON controller? Environment LNS LON Controllers NL220 LonMaker Cause There are different files related to a LON device. The XIF and NXE files have completely different purposes. Resolution The XIF is a text-based file that defines the device’s network image to a network management tool (e.g. Niagara, LonMaker, etc.). The XIF along with files termed device resource files (DRFs) are used by the management tools to work with the LON device. Device resource files provide definitions especially when the manufacturer has not used standard SNVT types. When requesting a shadow object from Tridium, the XIF file must be provided as a minimum. If the manufacturer has defined their own variable types, the associated set of device resource files must also be provided. The only other alternative would be to use a dynamic device and hope that the device’s manufacturer implemented the files within the device correctly. When a dynamic device is commissioned, Niagara will upload the XIF from the device and attempt to create an object from the file’s definitions. The NXE is an abbreviation for (Neuron Executable file). Some devices allow the user to download an NXE or new application image file that changes the operation and / or network interface of the target device. New or different application firmware can be downloaded to the Neuron. This is the way some manufacturers upgrade their devices and / or the network interface portion of the device. If the LON device can support an NXE, this would have to be provided by the device’s manufacturer.

Issue Writing directly to a SR (set-reset) simple block in a Xenta 700 Menta application where that SR output is sent to a Delay block, the Delay block may not delay. The output on the Delay block will be set immediately, without any delays. Environment Xenta Servers version 5.1.1 and lower Xenta 701, 711, 721, 731 Menta Cause This was a bug in version 5.1.1 and lower. Resolution Upgrading the Xenta Server to version 5.1.2 or later will resolve the issue. If upgrading is not an option, this can be worked around by not writing to the SR block itself, but to a block in the logic before the SR block.

Issue Writing directly to DELB (delay binary) simple block in a Xenta 700 Menta application where that DELB output is sent to a TRIG block, the TRIG block may not work. Environment Xenta Servers version 5.1.1 and lower Xenta 701, 711, 721, 731 Menta Cause This was a bug in version 5.1.1 and lower. Resolution Upgrading the Xenta Server to version 5.1.2 or later will resolve the issue. If upgrading is not an option, this can be worked around with one of these options: Write to a block prior to the DELB block, not the DELB block itself Put a second DELB block at the end before the TRIG block

Issue Can't  Override/force an I/O point on an I/O-Module connected to a Xenta 7xx Environment Vista Xenta 7xx Cause Xenta 7xx way of override value has been changed from the way Xenta 4xx did Resolution There are no way of forcing the RI/BI or RO/BO signals like you can do with the AI/AO DI/DO in Xenta 300/400/280. In the 700 you can only force the real physical point. You find the points under the Xenta Server object $IO.

Issue No values in a TAC Xenta Server Trend log in TAC Vista Environment Xenta Servers Xenta 511, 527, 701, 711, 721, 731, 913 Trend Logs Vista Workstation Cause The Xenta Server trend logs have not been enabled in the Vista Workstation. Resolution To be able to view and store TAC Xenta Server trend logs in TAC Vista: Find the trend log in TAC Vista Workstation Right click and select Properties. There are two different control tabs here, Vista control and Xenta control. Xenta control turns on and off the actual log in the Xenta server (same as in XBuilder). Vista control decides if the Log gets stored in TAC Vista's SQL database and if the log can be viewed from Workstation. In the Vista control tab change Activate to manual-on. Now you can see the logs from TAC Vista.

Issue Does TAC Vistas new OPC server (version 1.1.0) that was released with TAC Vista 5.1 only work with Vista 5.1? Environment Vista 5.0 OPC server  1.1.0 Cause Because the new version of OPC comes with Vista 5.1, it may be assumed that it is not fully backwards compatible. Resolution OPC server version 1.1.0 is compatible with all Vista 5 versions.

Issue When trying to access TAC Webstation a message saying 'Service unavailable' occurs. Environment Webstation Cause The problem is that the application pool in the IIS where TAC Vista Webstation is located is closed down when trying to access it. Resolution The workaround for this is: Go to Properties for the application pool which contains TAC Vista Webstation Choose Identity and change the predefined 'Network service' to 'local system'

Issue Getting error message "page cannot be found" when trying to open TAC Vista Webstation. Environment Windows 2003 Server and IIS 6.0 Cause Enable ASP.NET in Web Service Extensions. Resolution Open the IIS 6.0 (Internet information services). Click on "Web Service Extensions" and make sure ASP.NET is "Allowed". http://www.youtube.com/watch?v=r62cbZx4vhQ NOTE: XP Uses IIS 5.1 and Web Services Extensions do not exists in this version of IIS.