Building Automation Knowledge Base

Issue In XBuilder there is a setting called "Max number of HTTP sessions" that can also be found using the web interface by navigating to Configuration > Servers > HTTP Server. What does this setting do? Does it limit the number of users who can log in simultaneously? Environment Xenta Server Xenta 511, 527, 555, 701, 711, 721, 731, 913 XBuilder Cause This setting is somewhat vague and is sometimes believed to be a limit on the number of simultaneously logged-in users. Resolution The Max. number of HTTP sessions is set to a default value of 15 and can be set to anywhere from 10-20. This setting does not limit the number of simultaneously logged in users, however. The TAC Xenta Server - TAC Networks Technical Manual explains this setting as follows: HTTP The Xenta Server is an HTTP (Hypertext Transfer Protocol) server. Several users can view the web pages at the same time, but they are limited by the number of HTTP sessions allowed. Max. simultaneous HTTP sessions, choose a number from the list. The default setting is 15. Several users can view files at the same time. What is an HTTP Session? Internet Explorer is an HTTP client, sending requests to the Xenta Server. The HTTP server in the Xenta Server receives the request and, following any necessary processing, the requested file is returned. An HTTP session is the connection that exists during data communication between the web browser and the Xenta Server. The session ends when all the data has been received. Rules of Thumb Each web page (values page, alarm page, and the graphics page), sets up a full HTTP session. When loading a web page, a number of sessions may be used simultaneously, depending on the number of sessions available.

Issue Can Inovonics wireless equipment be used with Xenta Servers? Environment Xenta Servers Xenta 511, 527, 555, 701, 711, 721, 731, 913 Cause The Inovonics Frequency Agile product line which is compatible with the Xenta Server driver is being obsoleted by the manufacturer Inovonics at the end of 2011. Resolution If you have existing devices installed in the field then they should continue to work and function. New installations should explore other options for wireless sensors due to unavailability from the manufacturer. The ability to add a RS232 wireless Inovonics interface was removed from XBuilder beginning in version 5.1.8.

Issue Offline Xenta 401 Not Generating Alarms Environment Xenta 401 Xenta Group Cause Xenta Group Master is offline Resolution Determine if the Group Master is offline In the Vista System Plug-in TAC Network Pane, the Xenta Group Master will be the only controller in the Xenta Group that is underlined Determine if this controller is offline in LonMaker or NL220 If the group Master or any of the Xenta devices in that Xenta Group show an " * ", you will need to download application and parameters Change the Group Master to a more reliable controller Determine which controller in the Xenta group has the least amount of potential traffic In the Vista System Plug-in TAC Network Pane, Right-Click on this device and select "Set as Master". Download Application and Parameters to any device that shows and " * " after this change.

Issue Xenta Servers are producing lots of Messages that contain the text "$COS#...#MA1 All Messages start with $COS# followed by an object ID and they end with #MA1 The messages are coming, although there are no trend log values missing. Environment Tac Vista 5.1.6 or older Cause This is a bug which is fixed in Vista 5.1.7. This message - $cos - is created every time Vista tries to retrieve an alarm from a Xenta controller and fails. Vista then tries again a couple of times. If successful, this message is removed. The problem is that the acknowledgement that should remove this log entry never arrives. Resolution Upgrade to Vista 5.1.7

Issue What is extended lon talk? Is there no support for connection objects in TAC XBuilder 5.1.5 and 5.1.6? Environment TAC Vista 5.1.5, TAC Vista 5.1.6 XBuilder Xenta Server Cause In the release TPA-VSTA-11-0013.00 for Vista 5.1.6 it says: Extended LonTalk It is not possible to write to Extended LonTalk devices within XBuilder. Connections have to be engineered using NL220, Lonmaker or TAC Vista Workstation through object transfers. This can be misunderstood as connection objects are no longer supported. "Extended LON" means a newer type of neuron chip that has more address and domain tables (e.g. Loytec's LISA chip). The support for this was added in TAC Vista 5.1.5 but it is not added to the Xenta Servers. So support has not been removed for anything, just added support in TAC Vista. Resolution "Extended LON" refers to a newer type of neuron chip that has more address and domain tables (e.g. Loytec's LISA chip) There are no change in the use of connection objects in TAC Xbuilder 5.1.5 and 5.1.6

Issue Procedure to Change Imperial to SI units in VAV Controller in Classic Network System. Environment Xenta 102-AX VAV Controller TAC Vista (Classic) Cause In classic Network System, when trying to change the Xenta 102-AX VAV units from Imperial to SI, it is not changing. Resolution It is possible to change the Xenta 102-AX VAV units from Imperial to SI, in LNS System using the plug-in, But in Classic Network system, it requires some system settings to take the effect. Follow the below steps to change the Xenta 102-AX VAV units from Imperial to SI: Make sure that these setting are checked in the Administrator account. I some cases there may be two or more administrator accounts that require these setting checked Go to Control Panel -> Open "Regional and Language Options" -> in Standards and formats, change from English (United States) to English (United Kingdom). Note: - If the units are required in Fahrenheit set the English language to United States. - If the units are required in Degree Celsius set the English language to United Kingdom.   Change the Location to your local region.   Go to Advanced TAB -> change from English (United States) to English (United Kingdom). Note: - If the units are required in Fahrenheit set the English language to United States. - If the units are required in Degree Celsius set the English language to United Kingdom.   Click on "Apply all Settings to the current user account and to the default user profile".   Click on "Apply" and then click on "OK".   Re-Start the Computer.   After the computer has restarted, open the TAC Vista Server and Work Station. Then Right Click on "VAV Controller", go to its properties, and reload the XIF file, then press "OK".   Commission and Download.   It should now be possible to change the units of the device.

Issue Upgrade Xenta I/O modules Environment Xenta 421A, Xenta 422A, Xenta 420A Xenta 411, Xenta 412 Xenta 491/492 Xenta 451A, 452A, 450A Xenta 471 Cause It is not very common to upgrade I/O modules. If it must be done, they are upgraded the same as any other LonWorks device without a host processor. Resolution Right click on the target file to store the file locally on the hard drive. To be able to download the NXE-file, you need both the NXE and the according XIF-file for the specific device. In LonMaker, select Replace or Commission, depending if the device are already in the database or not. If the XIF-file already exist in the database, select the correct Device Template. In the next dialog, select Load application image. Browse to find the directory for the NXE-file. Change File of type to NXE. Browse to find the directory for the XIF-file. Select Next to decide about source for CP values. Select Next, if you do a Replace, you could select the Neuron ID manually, and the old Neuron ID will already be in the dialog. Select Finish to download the new NXE-file into the device.

Issue Is it possible to access the Pelco Video Server through TAC Vista Webstation Environment TAC Vista Webstation Pelco Video Server (Digital Sentry) Cause The Pelco Video Server can not be accessed through TAC Vista Webstation. Resolution No, It is not possible to access the Pelco Video Server through TAC Vista Webstation. It is only possible to access Pelco video viewers through TAC Vista Workstation. In TAC Vista Workstation activates a special program which allows viewing of this video. Note: TAC Vista supports only for Pelco - Integral Digital Sentry Video System.

Issue Is it possible to determine if a TGML graphic is being run in Workstation or Webstation? Environment TGML Graphics Editor 1.1.X Vista 5.1.X Workstation TacWebApps 5.1.X (Webstation) Cause There are differences in the rendering of graphics between Workstation and Webstation. Sometimes this leads to the necessity of creating two sets of components depending on where the graphics will be presented. By being able to programmatically determine the environment, one set of components can be used regardless of the presentation, reducing engineering time. Resolution The results of the JavaScript function Packages.java.lang.System.getProperty can determine whether the viewer is currently in Vista Workstation or not.    Note: This is not a supported function in TGML. Because it is unsupported, it is subject to change without notification, and should be used accordingly at your own risk.   Create a document-level script tag that runs OnDocumentLoad. Determine the current Vista version (and keep potential future upgrades in mind as well). The implementation of the property changed in an upgrade from Vista 5.1.4 to Vista 5.1.5. If the system is Vista version 5.1.4 and prior, use the following function: if (Packages.java.lang.System.getProperty("browser") == "ActiveX Scripting Host") If the statement is true, then the graphic is being run in Workstation. If the system is Vista version 5.1.5 and later, use the following function if (Packages.java.lang.System.getProperty("java.runtime.name") == "IKVM.NET") If the statement is true, then the graphic is being run in Workstation. The following script can be run for any version of Vista 5. /*   returns what browser Tgml is viewed in (Workstation==false,Webstation/Webserver==true)  */ var getBrowserType = function() {    var browser = false; // initiates browser indication variable as Webstation/Webserver  if (Packages.java.lang.System.getProperty("browser") != null) { // checks Vista version   // evaluated for Vista is 5.1.4 or earlier   if (Packages.java.lang.System.getProperty("browser") == "ActiveX Scripting Host") {       browser = false;   // indicates variable as Workstation   } else {      browser = true;    // indicates variable as Webstation/Webserver     }  } else {   // evaluated for Vista 5.1.5 or later   if (Packages.java.lang.System.getProperty("java.runtime.name") == "IKVM.NET") {    browser = false;   // indicates variable as Workstation   } else {    browser = true;    // indicates variable as Webstation/Webserver   }  }   return browser;     // returns browser indication } 

Issue Zbuilder will not launch from LonMaker on Windows Vista. If running LonMaker in elevated mode or with User Access Control disabled then trying to launch Zbuilder will result in an error: Unhandled exception thrown. Message: Object reference not set to an instance of an object. StackTrace: at TAC.Xenta100ConfigTool.Framework.LNS.LnsNetworkManager.OpenNetworkAndSystem(String network) at TAC.Xenta100ConfigTool.Framework.LNS.LnsNetwork.InitLNSPlugIn(String objectPath, String mode, String networkInterfaceName) at TAC.Xenta100ConfigTool.Program.RunAsLnsPlugIn(Assembly frameworkAssembly, String[] args) at TAC.Xenta100ConfigTool.Program.Main(String[] args) Environment LonMaker 3.2 Vista 5.1.0, 5.1.1, 5.1.2 Windows Vista Cause When the Vista Toolpack 5.1.0 was developed, LonMaker did not support Windows Vista limiting the ability to test for compatibility and all problems. As a result this problem is only experienced when launching Zbuilder from LonMaker. Resolution Upgrade the TAC Toolpack to version 5.1.3 or higher. If Vista Server is being used as well then ensure that the Toolpack and Vista Server versions are still the same revision.

Issue Dehumidification using Xenta 121-FC Environment Xenta 121-FC Xenta 121-HP Cause Some aspects of how the dehumidification mode in the Xenta-121 operate are undocumented. Resolution The dehumidification feature of the Xenta 121 can operate either by turning on external dehumidification equipment using one of the digital outputs or, if no external equipment is provided, it will use the cooling for dehumidification. In the latter scenario, the heat continues to be operational when the cooling is forced for dehumidification. Additionally, if there is an outside air damper, it will be controlled to its minimum position before forcing the cooling on. When is external dehumidification enabled? For On/off cooling, cooling is enabled for dehumidification when the nvoDehumidActive value is greater than 10% and is disabled when the nvoDehumidActive value drops below 5%. For all other types of cooling, nvoCoolPrimary is set to match the nvoDehumidActive whenever it is a greater than cooling PID output + 5% or whenever the cooling PID output is less than 5%. The dehumidification feature can be configured using the ZBuilder configuration tool. However, the individual features can also be accessed via the points listed below using either Vista Workstation or another Lon management tool such as LonMaker: Applic UCPTappOptions Bit Usage If FALSE If TRUE Additional notes 5 Dehumidification control enable Not active Active   6 Dehumidification type Internal External Only applicable if bit 5 = true. External control can be hardwired or via SNVT. Internal will force cooling as a dehumidification method. 7 External dehumidification active on Open contact Closed contact Only applicable if bits 5 and 6 are both true. UCPTappOptions2 Bit Usage If FALSE If TRUE Additional notes 7 External dehumidification type Digital Analog If true then the RH reading is mirrored to the analog output (0-100% = 0-10V). Only applicable if UCPTappOptions bits 5 and 6 are both true.

Issue Xenta Group and Xenta Programmable Device specifications for an LNS system Network communication errors Environment Vista NL220 LonMaker Vista System Plug-in Cause Improper configuration of Xenta Programmable controllers will result in poor network performance Resolution Design Each LNS database within the following limits A maximum of 400 Xenta Programmable devices A maximum of 30 Xenta Groups A maximum of 30 devices with-in each Xenta Group Xenta groups should not have members separated by a router

Issue Can Andover Continuum and Vista be installed on the same computer? Product Line Andover Continuum, TAC Vista Environment Windows computer with desire to install both iBMS (intelligent Building Management System)  Cause Single computer with desire to install both Andover Continuum and TAC Vista  Resolution Vista and Continuum cannot run on the same computer. Even if it is the latest Windows version. There are a couple of problems right up front, the License dongle, required by Continuum, can only be a single license dongle. In other words, only one dongle per computer. If Continuum sees a second dongle for license in the computer, there are problems. Second issue is the SQL, the two programs, Vista and Continuum have different install methods and therefore are not compatible. Continuum uses a V1/x strict compatibility install, where Vista uses the default Latin install. Note: Unofficially, sites have been reported as using VMWare to install both in the virtual environment. This of course is not supported, but has been done and is a possible solution. By the time the software is purchased and all possible problems have been addressed, it may be equal to using a second computer or laptop for the other system. Officially though, both systems on the same computer is not supported. 

Issue The wrong version of the .xif file is being used. Environment NL220 LonMaker Vista LonWorks Device XIF Cause The numbers/types of SNVTs in the file have changed. SNVTs have been added to an Xenta 500/700/913. Resolution Ensure that Vista Server is running. In Vista System Plug-In, in the LNS Network pane, right-click the LonWorks device object. Click Replace Click Next Keep default neuron ID. Click Next Select Upload From Device Click Next Click Ok Select the LonWorks device object and check that the SNVTs are available in the object view window

Issue When writing the invalid value (163.835) to the Airflow Reset (%) in the Xenta 102-AX plug-in, the value is only changed to 163.830 and the airflow setpoint is set to the Maximum airflow setpoint. Environment Xenta 102-AX plug-in Cause The Xenta 102-AX plug-in does not support 3 decimal places of precision and will only write a 163.830 value to the device. The plug-in will state this is an invalid value because it is over 100, but it will treat the airflow reset like it is configured as 100%. Resolution Power cycle the Xenta 102-AX controller to revert the nviAirFlowReset SNVT to the invalid value (163.835) Use the LNS Browser to manually write the value 163.835 to the nviAirFlowReset SNVT on the VAV Controller function block.

Issue After importing a pointlist to XBuilder and downloading the XBuilder project, all values both in TAC Vista and on a values page in the Xenta Server are shown as Invalid Address. VisiSat is still working and you can connect to the controllers using the Xenta Server as a IP tunnel. Environment MicroNet Xenta Server Cause This is due to a problem with a double point address in the pointlist, meaning that two points have different names, but the same table reference. Resolution Make a new pointlist in VisiSat. Mark all the points in the pointlist and copy all the points to the new pointlist. You will now get an error message showing you which point is represented more than once in the pointlist. Correct the points until errors stop, copying the entire pointlist. Export the pointlist for XBuilder, and import it again. Download to the Xenta Server.

Issue The dongle doesn't work when launching an application through Windows Remote Desktop. Environment NL220 Dongle Windows Remote Desktop Protocol (RDP) Cause The Windows Remote Desktop feature is not supported for NL220 dongles. Resolution Use an alternative remote solution, like Ultra VNC.  

Issue Trend logs not working after upgrading from Vista 4.2.5 to Vista 5.1.6. Environment Vista 4.2.5 Vista 5.1.6 Non-english regional settings. Cause When upgrading from a Vista version older than 4.5.0, it is recommended (in the latest TPA) to upgrade first to Vista 4.5.0 and then to Vista 5.1.6. However with non-english /US regional settings this can cause problems, such as the trend logs not being upgraded and, due to this, not working. Resolution Follow these 2 simple steps: Change the regional setting to "Location" US and set the language to English (United States). Upgrade directly to Vista 5.1.6 (not via 4.5.0.)

Issue When upgrading a Vista from Vista 5.1.3 to Vista 5.1.4, make changes in the Lon network and download it the Xenta master goes offline. This only when running the 911 in low bandwidth. Environment Vista 5.1.4 Cause In the Xenta 911 software version 5.1.4 changes are implemented to support extended characters. This means that when using Xenta 911 in low bandwidth, we need to download the node information to the Xenta 911 using a .cfg file instead of a .xml file. If you have a Xenta 911 with version 5.1.4 it waits for a .cfg file and if you do not have TAC Vista version 5.1.4, it cannot deliver a .cfg file. This means that customers that have upgraded to Vista 5.1.4 need to upgrade all of their Xenta 911s to 5.1.4 if any changes are done in the network. Resolution Upgrade the Xenta 911 to version 5.1.4. Update: This is solved in 5.1.5 and later versions.

Issue What is the proper configuration for a Change of State object to detect a digital or binary point. Environment Vista 5.x.x Cause Vista requires that the point being monitored is set with a watch setting of watch or alarm. Also as long as the low limit and high limit values match the alarm will trigger when the point is active or on. Resolution Create the Change of State object in Vista and set the Low Limit to 0 and High Limit to 0.