Building Automation Knowledge Base

Issue When installing the site .plf license, Privilege Administrator states it is missing Developer Extension and terminates the installation. Environment Privilege Administrator / Licenser Developer Extension PLDevExt.pde Cause An error occurred during the installation of Privilege License Software where the Developer Extension was not executed. Resolution Manually execute the Developer Extension. Navigate using Windows Explorer to ..\System32\PLDevExt.pde Double click the PLDevExt.pde Restart Privilege Administrator Install site license by double clicking your .plf file Verify the licensed  TAC software starts successfully

Issue How can you find the Trend Log ID / GUID of trend logs in the Vista Server for use with custom reporting or querying of the SQL database? Environment Vista 5.x.x Cause The Vista database uses a Global Unique Identifier (GUID) for trend log storage in the SQL database. This Trend Log ID/GUID is stored in an property not immediately visible in the property window of the Vista Workstation environment. In Vista 5.1.7 a new database layout was introduced, database  layout version 2. The version of the layout  for the log database is possible to see from the Vista server setup. And it is possible to upgrade the database to version 2 with a tool called SQL Database Upgrade tool which is included in the Vista installation from Vista 5.1.7.    If using the new layout of the SQL database in Vista version 5.1.7 both the name of the trend log and the trendlog GUID is included in the TrendLog table. Resolution Single Trend Log Hold CTRL + SHIFT + right click and select properties of the trend log object. The Trend Log ID is one of the visible properties. Multiple Trend Logs Start a new search in Vista Workstation. Change the object types to Files\Trend Logs. Change the property to Trend Log ID. Leave the string as "*" for all trend logs. Click Search The results can be printed listing the database path, object name, and trend log id for use by the individual building the SQL reports. If using the new layout in Vista version 5.1.7 both the name of the trend log and the trendlog GUID is included in the TrendLog table.

Issue While opening a TGML graphic in webstation a security warning dialog box appears: 'Java has discovered application itemsthat could indicate a security concern'. Environment Webstation 5.1.X Java 6 update 19 and newer Cause Signed Java Web Start applications and applets that contain signed and unsigned items could potentially be unsafe unless the mixed code was intended by the application vendor. As of the Java SE 6 Update 19 release, when a program contains both signed and unsigned items, a warning dialog is raised. Resolution Mixed Code Protection Options for Users: User can manage how mixed code programs are handled through the Java Control Panel. To access the Java Control Panel goto, Start menu > Control Panel > Java Control Panel > Advanced > Security. The following screen shot shows the four levels of control available. See the Mixed code heading towards the bottom of the Java Control Panel. Below are the details of the available options. Enable - show warning if needed.This is the default setting. When a potential security risk is encountered, a warning dialog is raised. Clicking Yes blocks potentially unsafe items from running and may terminate the program. When the user clicks No, the application or applet continues execution with protections (packages or resources that are later encountered with the same names but have different trust levels, i.e., signed vs unsigned, will not be loaded). Enable - hide warning and run with protections.This option suppresses the warning dialog. The code executes as if the user had clicked No from the warning dialog. Enable - hide warning and don't run untrusted code.This option suppresses the warning dialog and behaves as if the user had clicked Yes from the warning dialog. Disable verification.This option is not recommended. This option completely disables the software from checking for mixing trusted and untrusted code, leaving the user to run potentially unsafe code without protections.

Issue Links in TGML graphics in Webstation do not work. A page can not be opened error message is shown.  No Java is installed, TGML viewer mode in Websettings is set to Autodetect and "Optimized TGML loading" is set to On. Environment Vista Webstation 5.1.6 TGML Graphics Cause For some reason the links do not work when no Java is installed, TGML viewer mode in Websettings is set to Autodetect and "Optimized TGML loading" is set to On. Resolution In Vista Websettings change "Optimized TGML loading" to Off.

Issue Is there any need to set up external alarms, trends or Time schedules for Programmable Xenta controllers if I use a LNS system? Environment TAC Vista LNS TAC Xenta 301, Xenta 302, TAC Xenta 401 TAC Xenta 281, Xenta 282, Xenta 283 Cause Differences in classic and LNS scenario Resolution No there are no need to set up any external alarms, the proprietary communication still works.

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 How to find the installation log file when SQL install fails during installation of Vista Server. Product Line TAC Vista Environment Vista 5.x.x SQL Server 2005 SQL Server 2008 Cause The SQL Server is installed with a silent install and error messages can only be found in the created installation log file. Resolution SQL Server 2005 Browse to C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\Log\Summary.txt SQL Server 2008 Browse to C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\Summary.txt Search the file using keywords "error" and "failed" to find the nature of any installation problems.

Issue XBuilder project will not download to the controller and there are no errors indicating other known issues with a download. It simply fails. Environment Xenta Server Xenta 511, 527, 701, 711, 721, 731, 913 Cause The Xenta controller may need to be recovered due to various software and hardware issues. XBuilder/Xenta firmware versions do not match Hardware or firmware failure requires hard reset Corrupted XBuilder project Fail-safe Resolution Check all software versions to ensure Vista, XBuilder, and Xenta Firmware all match. Correct any discrepancy by upgrading to the latest version. Try to download the XBuilder project, if that does not work...   Run in failsafe mode by jumpering pins 9 and 10 before power up. Try to download the XBuilder project, if that does not work...   From Hyperterminal DSH prompt do a FORMAT command. Correct the IP Address Download a new System Program to the controller. Try to download the XBuilder project, if that does not work...   Download a "blank" XBuilder project to ensure the project is not the root of the problem. Try to download the XBuilder project, if that does not work...   The controller may be bad. Replace the controller.

Issue Browsing the device in a Lonworks network tool, the SNVT shows the correct value, but in Vista, the value is incorrect and showing the default value. Environment NL220 and Lonmaker. Vista Cause The XIF file as been corrupted. This can occur sometimes if the System Plug-in has an error in the update process. Resolution The first thing to check is that the point in Vista is the correct point when related to the SNVT being referenced. If this is correct, then a good sign to look for is duplicate names in the Function block. If there are duplicate names this indicates a corrupt XIF. The only solution is to delete the device and re-add it. Once the device has been deleted, also remove the template so the new correct template is imported. If the template is not deleted, the network management software will use the same corrupt XIF file.

Issue Remote Alarm Manager 2.0, RAM 2.0 when first started after an install starts up in Demo mode. Environment Sigma, Micronet, Vista Cause RAM 2.0 has been installed and the RAM Console is started, RAM starts up in Demo mode and gives a 2hr trial period. Resolution This is correct. The demo mode will disappear when the Input interface e.g. Sigma R4 is created and at this point the customers dongle or the engineers PC ID code is read.

Issue SQL server install fails due to password complexity rules. Environment Microsoft SQL Server 2008 Vista 5.1.4 or higher Cause Microsoft SQL Server 2008 by default has higher password complexity rules then previous versions of SQL Server. Passwords cannot contain the user's account name or parts of the user's full name that exceed two consecutive characters. Passwords must be at least six characters in length. Passwords must contain characters from three of the following four categories: Latin uppercase characters (A through Z). Latin lowercase characters (a through z). Base 10 digits (0 through 9). Non-alphabetic characters. Resolution When installing Microsoft SQL Server 2008 select a SA password that complies with the complexity rules.

Issue An Alarm object in an XBuilder project has two outputs - digital and state.  The state output corresponds to the acknowledged state of the alarm.  To use this output programmatically, the enumeration values must be known. Environment Xenta 511,527,555,701,711,721,731 Cause Not knowing meaning of Alarm State output values in Xenta 700 Resolution The Xenta 700 alarm state enumeration is: 0 - Normal 1 - Passive_unacked 2 - Active_unacked 3 - Active_acked

Issue Parameters, configurations, calibrations and other settings are not stored within the M/STAT, I/STAT, or any of the STR series wall sensors with the exception of the STR-350. No data can be carried with the stat from one controller to another. Environment M/STAT I/STAT STR-150 STR-250 MR-VAV Xenta 102-AX Xenta 121 Xenta 104-A Various other STR series sensors and Xenta controllers Cause The aforementioned stats use only key code to communicate with their associated controllers and do not store any of their own parameters or settings. Resolution These stats may be moved from one controller to the another or a controller may be replaced while maintaining the original stat without carrying over any settings from the original controller.

Issue The Xenta 913 can only be used for both Modbus and BACnet at the same time if they are being used on separate ports or are both on the IP port. BACnet and Modbus can not both be used on the RS-485 A port at the same time. Environment Xenta 913 XBuilder BACnet Modbus   Cause Only the Ethernet 10 Base-T port on a Xenta 913 may have more than one interface at a time. Resolution The Xenta 913 may interface with BACnet and Modbus at the same time only if: The RS-485 A port is being used for Modbus and the Ethernet 10 Base-T port is being used for BACnet The RS-485 A port is being used for BACnet and the Ethernet 10 Base-T port is being used for  Modbus The Ethernet 10 Base-T port is being used for both BACnet and Modbus and the RS-485 A port is either unused or is being used for only BACnet or Modbus but not both The Xenta 913 may not interface with both BACnet and Modbus if they are both connected to the RS-485 A port.

Issue Getting "completion event failure" when doing a commission and download to a Xenta server running as a Lon device in Vista. Environment Vista 5.1.6 Xenta server 5.1.6 Cause If the Xenta 913 have the same IP address(which can happen if it is used as a Xenta server with lon units under it before the Vista will set subnet/node to either 1/126 or 1/127 ) as the lon network typically 1/126 or 1/127 you need to change it using for example Lonmaker. It is not possible with Vista or webpage in Xenta server. You can check the subnet/node in the webpage for the Xenta server under Utilities-Lonworks-domain table. Resolution Change the subnet/node either for the lon network in Vista or for the Xenta server

Issue How many characters can an object in Vista have? Environment Vista 5.1.6 and newer Cause When naming an object, all letters and digits are allowed. Additionally, the following characters may be used: (space) [ ] _ : / Up to 40 characters in length can be used. Resolution When naming an object, all letters and digits are allowed. Additionally, the following characters may be used: (space) [ ] _ : / Up to 40 characters in length can be used.  Examples of prohibited characters are: ! " # $ % & ' ( ) * + , - ; < = > ? @ \ ^ ` { } | ¦ .(period/fullstop)

Issue What log files exist in Vista Server and can be used to help diagnose problems experienced by Vista Server. Environment Vista 4.x.x/5.x.x b0warlog.txt b0dbglog.txt b0errlog.txt b0cfglog.txt Cause Vista Server creates log files in the $log sub directory of the Vista database folder. These logs are created as needed when a warning, error, or other message that needs to be communicated. The nature of messages in these log files are related to the Vista Server installation, configuration, and errors experienced when processing data from the network defined in Vista Server. Alarms and errors caused by the actual network are not displayed in these log files but are visible in the alarm pane or event log inside the Vista database. If experiencing a problem in Vista Server review of these log files and matching the time stamps can help identify the cause of the problem. Resolution There are multiple log files created when a warning or error occurs. Each message is time stamped with details of the process and message. b0warlog.txt - Warning Log File Warnings are recorded here. Some Vista Server alarms might point here for more details such as failure to transfer logs from a programmable controller.  Can also find configuration errors such as SMTP setup problems, failure to write property values,  or Vista report problems when trying to launch Microsoft Excel. b0dbglog.txt - Debug Log File Information related to debugging messages b0errlog.txt - Error Log File Error messages that are more severe then warnings relating to Vista Server. b0cfglog.txt - Configuration Log File Configuration messages such as importing a network from the Vista System Plug-in or communication port problems in LonWorks networks.

Issue Can not connect to a Remote SQL server 2008 R2 from Vista. Locally where the SQL server is installed it is working fine. Environment Vista 5.1.6 SQL server 2008 R2 Cause To connect remotely to a SQL server some additional settings must be set, see resolution below.  Resolution Open the SQL server management studio, open the properties for the SQL server, go to connections, make sure "Allow remote connections to this server" is marked. Open "Security" in the properties, make sure the correct server authentication mode is marked. In the firewall open port 1433 and 1434 which is the default ports used by the SQL server.

Issue No link LED on a Desktop's and Laptop's Network Interface Card (NIC). Environment Windows OS Cause Network interface card has power management feature enabled.  This will shutdown the network interface card if no activity is present, battery is low on power, or battery is intermittent. Resolution Disable power management features under Device Manager Network Adapters. 

Issue Xenta server stand alone and Vista at the same time. No alarms showing in TAC Vista when Xenta Server is connected. Environment TAC Vista TAC Xenta Server Cause If you add a stand alone Xenta Server on a Lon network it will send out heartbeats just like TAC Vista does. So the affect will be the same as having 2 TAC Vista servers on the same network.  But there is a way to turn this off. In Xbuilder you can turn this off by setting "Alarm Server" to disabled Resolution In Xbuilder click on the LON object Under General properties change "Alarm Server" to disabled. Download the project.