Building Automation Knowledge Base

Issue When the Xenta 104-A goes from occupied to unoccupied mode, it switches from HVAC_COOL to HVAC_HEAT. This shows up on the graphic by the nvoEffectiveStpt showing the UNOCCUPIED_HEAT setpoint when the UNOCCUPIED_COOL was expected. Environment Xenta 104-A Cause Switching from occupancy mode, or override mode, causes the 104-A to go into HVAC_HEAT mode unexpectedly. Resolution The above graphic shows the room temperature over time as a red/blue line. When the line is shown in red, the 104-A would be in HVAC_HEAT mode. When the line is shown in blue, the 104-A would be in HVAC_COOL mode. Make note that on the first program cycle, if the box is occupied, but the temperature is below the OCCUPIED_COOL setpoint, it will default to HVAC_HEAT mode. During the occupied time, the box performs as expected. If the temperature rises above the OCCUPIED_COOL setpoint, the box goes into HVAC_COOL mode. If the temperature falls below the OCCUPIED_HEAT setpoint, the box goes into HVAC_HEAT mode. Make note of the circled portion of the chart. When the RTU transitions from occupied to unoccupied mode, if the temperature is below the UNOCCUPIED_COOL setpoint, it will default to HVAC_HEAT mode, even if it was in HVAC_COOL prior to the transition. The unit will not be calling for heat, but will display the heating setpoint on the effective setpoint output.

Issue Modbus slave device only supports function code 10 hex/16 dec for writing of holding registers. Environment Xenta 913 Xenta 701/711/721/731 Xenta 511/527 Cause In system program 5.1.4 a trigger was added to the Xenta Server software that enables the device to use only the Multi-Register function code. This command is executed from the console port or from the VXI web shell command webpage. VX M 1 = Enable Multi-Register write VX M 0 = Disable Multi-Register write VX M = Display current status of the trigger Note: This setting is persistent on the unit until the firmware has been reloaded. If the unit is upgraded the setting will need to be reapplied. Resolution Log In to the webpage of the Xenta Server Access the Utilities\Target System\VXI Web Shell Commands webpage. Issue a "VX M" command to display the current status. Issue a "VX M 1" to enable the multi register write command option. Some of the Xenta Servers with recent Modbus support do not have the VXI web shell commands web page and the console will need to be used instead. The VXI web shell commands web page should be available in firmware 5.1.6.

Issue Equipment required to implement a NIC852 Orion Stack on a Vista LNS system Environment LNS network Loytec NIC852 Orion Stack Cause It may be necessary to utilize the communication protocols in a Loytec Orion Stack to make Vista's communication with the LNS database more efficient. Resolution Loytec NIC852 has two solutions: LOY-NIC-852 Floating license via USB hardlock key   LOY-NIC-852-SW Software activation with costs for one PC Here is a link to the LOYTEC website. You will need to create a free user account to download the latest NIC manual. This is available from the "Support/Manuals/NIC User manual" location. In chapter 2 the supported operating systems are listed for the NIC options.

Issue Get the following error message when viewing a TGML graphic in Webstation:  Java-plugin 1.6.0_20 Använder JRE-version 1.6.0_20-b02 Java HotSpot(TM) Client VM Användarens hemkatalog = C:\Documents and Settings\Administrator ---------------------------------------------------- c:   töm systemfönster f:   slutför objekt i slutföringskö g:   skräpinsamling h:   visa det här hjälpmeddelandet l:   dumpa classloader-lista m:   skriv ut minnesförbrukning o:   utlösarloggning q:   dölj konsol r:   ladda policykonfiguration på nytt s:   dumpa system- och distributionsegenskaper t:   dumpa trådlista v:   dumpa trådstack x:   töm classloader-cache 0-5: ange spårningsnivån till ----------------------------------------------------  PostSender: Failed to create json object: request sent is includeHidden:true, tgmlId:, requestId:3211, path:objectId=715325441&, command:GetObject, includeViewType:true, includeAggregated:0, java.lang.NullPointerException             at java.lang.String.indexOf(Unknown Source)             at java.lang.String.indexOf(Unknown Source)             at SE.Graphics.communication.TgmlGetter.checkFileIfExistsAndNotModified(TgmlGetter.java:279)             at SE.Graphics.communication.TgmlGetter.readTgmlObject(TgmlGetter.java:374)             at SE.Graphics.viewer.TgmlJComponent.fetchTgmlStr(TgmlJComponent.java:127)             at SE.Graphics.viewer.TgmlJComponent.loadTgmlDocument(TgmlJComponent.java:108)             at SE.Graphics.viewer.TgmlApplet.init(TgmlApplet.java:104)             at sun.plugin2.applet.Plugin2Manager$AppletExecutionRunnable.run(Unknown Source)             at java.lang.Thread.run(Unknown Source) Undantag: java.lang.NullPointerException or Unable to view TGML graphics in webstation. Get a blank screen with an error message from java console. Detected from bootclasspath: C:\PROGRA~1\Java\jre7\lib\deploy.jar Couldn't get Int parameter debuggingPort null returning 80 Couldn't get Int parameter minPollInterval null returning 500 @TgmlApplet#init object path is: objectId=1709965313&, server path: https://system.evalvomo.fi/webstation/active.tgml? key 0: ASP.NET_SessionId value 0: v30z342d1nj34zwcjm1a3agu Added cookie to result: ASP.NET_SessionId=v30z342d1nj34zwcjm1a3agu Proxy list:[DIRECT] proxy hosttype: DIRECT No Proxy for this hosttype - clearing proxy settings. executePost failed: HTTP/1.1 404 Not Found proxy hosttype: DIRECT No Proxy for this hosttype - clearing proxy settings. executePost failed: HTTP/1.1 404 Not Found PostSender: Failed to create json object: request sent is includeHidden:true, tgmlId:, requestId:1734, path:objectId=1709965313&, command:GetObject, includeViewType Environment TAC Vista 5.1.X Windows 2003 server Cause The .tgml extension has for some reason not been registered in Internet Information Services. Resolution Confirm that the error is as described above Register the TGML extension Go to the Start Menu and select Run. Type INETMGR and click on OK - this will open the Internet Information Services (IIS) console. Locate the virtual directory Webstation (\Web Sites\Default web site\Webstation) and right click on it. Select Properties   Click on the Configuration button. Look for the .tgml extension in the dialogue Application Configuration that opens up, under the tab Mappings.   If the problem is as reported, .tgml should not appear in the list. Click on Add and add the .tgml extension. Click on OK on all the open dialogues and then restart IIS. Click on Edit  and verify the checkbox "Verify that file exists" is not checked. Restart webstation and confirm the TGML are now working.

Issue Attempting to connect to a remote LNS Server in NL-220 results in a connection error (LNS, #108). Environment NL-220 4.5.x Cause Symantec Endpoint Protection includes a firewall named Network Threat Protection. This firewall will block the outbound and inbound connections to the a remote LNS Server. Resolution Disable Network Threat Protection on the computer the LNS server resides on and the remote NL-220 computer. Open Symantec Endpoint Protection Click Options Select Disable Network Threat Protection

Issue After several days or weeks, all Xenta Servers go offline in Vista. They can't be reached via the web interface, however they can still be pinged. Environment TAC Vista Xenta 511, 527, 701, 711, 721, 731, 913 Cause We have identified a memory allocation issue where the memory was not released properly for a Microsoft component (secur32.dll). This can be seen in the memory when the heap for this Microsoft module was re-allocated and tried to double its size after a certain time interval. The re-allocation required that a continuous block in memory was available for a successful re-allocation to be done. As a result of a failed re-allocation, all Xenta Servers went offline in TAC Vista Workstation. Resolution If the Vista PC is running Windows 2003 Server there is solution, but older Operating Systems (like Windows 2000/XP) will likely never get this fixed. Newer Operating Systems like Server 2008/Windows 7 don't suffer from this bug.   The solution provided by Microsoft is not included in any Windows update or Service Pack release for Windows 2003 currently available. Microsoft has confirmed that this will be included in the next Service Pack release for Windows 2003; Service Pack 3. (release date is not known at this time).  Step-by-step instructions:  1. Download http://www.microsoft.com/downloads/details.aspx?FamilyID=3ce0efe2-82ec-4134-9891-37efeab24e3a 2. Start a DOS prompt and go to the download folder, then type “WindowsServer2003-KB968389-x86-ENU.exe /b:SP2QFE” (without quotes) and hit Enter 3. Reboot PC 4. Check that you have the correct version of secur32.dll in Windows\system32. If the update has completed successfully, it should be 5.2.3790.4530 QFE .

Issue In the TAC Vista System Plug-In, a programmable controller is configured through the Xenta Device Plug-In. Browsing to a Menta file on the hard drive should associate that application with the controller to be uploaded to the database later. Instead, an error message is displayed:   TAC Xenta Device Plug-In Could not generate MTA application Environment TAC Vista System Plug-In TAC Xenta Device Plug-In Xenta programmable controller Xenta 280, 281, 282, 283, 300, 301, 302, 401, 401:B Menta Cause An error in the Menta file is keeping it from generating the necessary background files for the download to occur. Resolution Open the Menta file Go to Options > Simulate If no error occurs, choose Commands > Generate Either at simulation or at generation, an error should be highlighted in the Menta file that is responsible for the failure to generate. Fix this error and save the Menta file back to the hard drive. Attempt to browse in the Menta file again.

Issue In TAC Menta, under Options > Memory Usage > Advanced, there is a BPR size calculator.  What is a Network Neighbourhood (BPR file) and what does this calculation mean? Product Line TAC Vista Environment TAC Menta Xenta 281 Xenta 301 Xenta 401 Cause The total amount of memory consumed in a programmable controller includes Application and Application Files Parameters Work Area Number of Objects FBD (COD file) OP Menu Tree (BIN file) National Character Set (CHR file) Network Neighbourhood (BPR or Blueprint file) Trend Log Definitions (XLG file) Resolution The BPR is the blueprint file. It contains:  The TAC Xenta network name All TAC Xenta group names The TAC Xenta's own group's members' names The TAC Xenta's own I/O modules' info The BPR is unique for every single TAC Xenta device. This information is created by Vista and included with the TAC Menta images just before download of the Xenta. So this file is not saved anywhere as a separate file. The information is downloaded and does consume memory inside the TAC Xenta controller, however, so the BPR calculator is included to approximate how much room might be required to store the network descriptions for this specific TAC Xenta device. Where memory is close to filling the controller, it can provide more accurate estimates of which applications will fit into the controller.

Issue GSM modem does not send text message when an alarm is generated. Environment Sigma BAS 2800+ Micronet Vista Cause Remote Alarm Manager configuration is incorrect. Resolution Check the recipient configuration to ensure that the selected interface is correct.

Issue Alarms (change of state objects) in Vista have many attributes. Two of these are displayed as State (STATE) and X Alarm Status (XSTATE). If alarm blocks displayed on graphics pages are not following the logic in the Menta file, it may be beneficial to use XSTATE bindings instead of STATE. Environment Vista Workstation Menta Alarms Cause In large systems sometimes, there can be a discrepancy between the Vista alarm status and the Xenta alarm status that can manifest themselves especially on a graphic page bound to an alarm block in a Menta file. Resolution Check the Vista alarm status. Right click on the alarm and select properties. Navigate to the General tab. Check the Status Check the Xenta alarm status. From properties, navigate to the Status tab. Check the Xenta alarm status If the two are not matching, the Xenta alarm status is typically more reliable and always follows the logic in the Menta file. Switch the graphics binding to look to the XSTATE instead of STATE.

Issue Xenta programmable controllers will sometimes show an asterisk (*) next to their name in a Vista network. Hovering over the controller name will display a message that says, "Needs to be commissioned."  What does this mean?  Why are they there? How can they be prevented? How can they be removed? Environment Vista LonMaker/NL220 Vista System Plug-In Cause The asterisk indicates that this controller may need to be downloaded in order for a change in the network to take place. Sometimes it is precautionary and does not mean that a controller will cease to function if a download is not performed, so discretion should be used when to heed the warning and when not to. Resolution Read the following scenarios and how each will mark controllers for download.  Screen captures indicate the network impact of the different actions as seen from Vista System Plug-in and Workstation. Adding a Xenta unit to an existing Xenta Group By dragging and dropping the new unit into the desired group flags that group for download.  This is the preferred method for adding a Xenta unit to an existing group. In this example, AHU7 is added to XG_WING_B Xenta Group.   Using the Update TAC Network button updates the entire TAC Network. The System Plug-in will attempt to preserve the current group structure.  Thus any new controllers are sectioned off into new Xenta groups, most often denoted with an _#. The creation of a new Xenta Group will flag the entire network as requiring a download, so this is not the preferred method. In this example, AHU7 is added to the network automatically and a new Xenta Group is created for it.   Removing a Xenta unit from an existing Xenta Group flags the group for download. In this example, AHU6 is removed from XG_WING_B Xenta Group.   Moving a Xenta unit from one existing Xenta Group to another flags the destination group only for a download. In this example, AHU6 is moved from XG_WING_B to XG_WING_A Xenta Group.   Reassign the group master of an existing Xenta Group flags the group for download. In this example, the XG_WING_B Xenta Group master is changed from AHU4 to AHU5.   Adding a new Xenta Group flags the entire network for download. In this example, XG_WING_C containing AHU7 is added to the network.   Renaming an existing Xenta Group flags the group for download. In this example, XG_WING_B Xenta Group is renamed to XG_WING_C.   Editing and updating a Menta file associated with a controller flags that one controller for download. In this example, AHU1 Menta file is edited in the database. Once a controller has been marked needing to be commissioned, the only way to remove the asterisk is to perform a download on that controller.

Issue When importing I/NET sav files into an XBuilder project, it will try to reconcile unknown Engineering Units in I/NET with recognized units in XBuilder.  If these units are set incorrectly by accident, there is a process for correcting them. Associate Unit Please associate the unrecognized unit with a unit known to XBuilder. If you do not want an association for this unit, select "NoCategory", which will result in that all signals having this unit will be displayed as having no unit. Product Line TAC INET, TAC Vista Environment Xenta 527, 731, 913 I2V I/NET sav files Cause Engineering unit Associate unit dialog accidentally set wrong units, or need to set a defined unit to "No Category" to avoid conversion issues in an integration. Resolution Locate the XBuilder project directory In the root project directory is a filed called UserDefUnits.txt If there are not many units defined, this file can be deleted.  It will then be recreated in its entirety the next time a batch of sav files are added to the XBuilder project. If there are many definitions that need to be preserved, this file can be edited. Erroneous entries can be deleted, or edited if the correct XBuilder unit definitions are known.  Example file below: ; *** UserDefUnits.txt *** ; User defined conversion of units to TAC XBuilder/Domino units ; degF=F Browse the sav files into the project again.  This will prompt the user to define the unknown units again, and the correct selection can be made and stored in the UserDefUnits.txt file.

Issue How to configure Xenta 913 to talk to C-Bus devices Environment Xenta 913 C-Bus Cause C-Bus is a public protocol which is commonly used in lighting control. Xenta 913 can be configured to talk to C-Bus devices with proper settings. Resolution A. Device Preparation C-bus 5500PC (PC Interface) RS-232 port        Xenta 913 RS-232A port NOTE: Communication is between Xenta913’s RS-232A port (NOT RS-485A port) and 5500PC’s RS-232 port (NOT C-Bus port).   Communication Cable Xenta913   C-Bus 5500PC, PC Interface RS-232A    <---------------------> RS-232 3(TX) <---------------------> 5(RX) 4(RX) <---------------------> 6(TX) 5(COM) <---------------------> 4(COM) Above number are RJ45 jack (as shown below) pin numbers.   B. Configuration Configure C-Bus device with CBusToolkit. Make sure to write down the Application number and the device’s Group number which Xenta 913 needs to communicate with.   Configure Xenta 913 in Xbuilder. Set Application number to 38 (38 is the HEX value of 56).   In DeviceEditor   The Group number (Hex value) needs to be inputted. Such as ‘01’ in the figure below. Same Group number can be inputted in different lines; however the ‘IO’ type should not be the same, such as ‘R’ and ‘W’ in below figure. ON Only and OFF Only types are NOT applicable to read-only values.   C. Verification In Xbuilder, drag all C-Bus points onto Value page. Download Xbuilder project into Xenta 913. Login Xenta 913 webpage and check if all point are correct and can be modified.   D. Additional Information Since CBusToolkit communicates with 5500PC by 5500PC’s RS-232 port, and Xenta 913 also communicates with 5500PC by 5500PC’s RS-232 port. Therefore, Only ONE device can be connected to 5500PC’s RS-232 port for CBusToolkit and Xenta 913.

Issue Xenta application has crashed or become corrupted and may exhibit one or more of the following symptoms: Controller not online in Vista Workstation I/O modules will not associate with Master Xenta controller will not accept download through System Plug-in Reset the Xenta controller by wiring a reset dongle. Clear the application/memory by shorting certain pins on the RS-232 port. Product Line TAC Vista Environment Xenta version 3.61 or higher, Xenta 280 (281, 282, 283), Xenta 300 (301, 302), Xenta 401 Menta System Plug-in Vista Workstation RJ45 Reset Tool Reset Dongle Cause Xenta may have crashed during download especially if interrupted during download. There are various other possible causes. Resolution Verify whether cycling power corrects problem. If that fails then perform the following steps:   If a Xenta 280/300/401 application has crashed and refuses to accept a new download, both from Vista and Menta, there is a way to clear the application (Xenta version 3.61 or higher). Manufacture a RJ45 jack with the following pins short-circuited: Note: This can be done by cutting off the end of an old Cat5 network cable, leaving approximately 4-6" of cable, and connecting the wires that correspond to the pins shown above.   Turn off power to the controller or remove it from the base plate. Put the manufactured RJ45 jack in the RS-232 port. Turn on power to the controller or re-insert it into the base plate. A forced Clear Application will be made. Remove the jack. Cycle power to the device to perform a fresh boot-up.

Issue When browsing to the LNS database on the new NL220 project screen, an error message says, "Setting NeuronID of router <%s> ..._O" Product Line Other, TAC Vista Environment Lonmaker Newron NL220 Cause The name of the database folder is over 12 characters. For example, C:\LM\Db\367_Collins_St Resolution To correct this error, rename the folder containing the lonworks database to 12 characters or less. The above example folder name in the Cause heading could be renamed to  C:\LM\Db\367CollinsSt

Issue LNS Database errors Corrupted LNS Database Product Line TAC Vista Environment LNS Turbo (3.2 or later) Database LonMaker, NL220 Cause There are various causes for a corrupted LNS database.  Backups, disk defragmenters, older versions of LNS, PC crashes, can cause errors in the LNS database. Resolution Before giving up on a troublesome database and rebuilding everything from scratch, try to repair any background errors by running it through the LNS Database Validator.  It can identify, and sometimes fix errors in the database, restoring functionality. The Validator tool works in "layers". Depending on the corruption, errors may need repaired by a specific hierarchy. This means validation may need to be performed multiple times to correct remaining errors. Backup the LNS database.  Do not proceed until a valid backup is created. Go to Start > Programs > Echelon LNS Utilities > LNS Database Validator This program only works on LNS 3.2 and later, and will not be available to LNS 3.1 PCs Under Network to Validate: browse to the desired LNS database Do not check "Repair Database" the first time.  Just hit Validate. Make note of any errors that are found.  Now check "Repair Database" and Validate again. Make note of any errors that have been corrected. Try to open and use the LNS database again. You may need to repeat steps 5 and 6 until all errors are corrected, or until the Validator refuses to correct the remaining errors.

Issue The Remote Alarm Manager shuts down during use, or cannot be restarted. Environment Sigma BAS 2800+ Vista Micronet Remote Alarm Manager RAM Cause The Log.mdb file becomes too large, and uses excessive memory, this can cause the RAM Engine to shut down. Resolution The Log.mdb can record all system alarms, user actions and the actions that RAM is taking. This file will increase in size and has no restrictions on how big it can get. How fast it increases in size will depend on the logging requirements set in the configuration. This file needs to be managed, and this is achieved as follows: 1 - If the system is running without any problems, then this file should be deleted or renamed on a regular basis. To do this stop the RAM services and locate the Log.mdb record (For Sigma it is most likely located in Sigma\Data\Remote Alarm Manager), and delete / rename it. Restarting the RAM services will recreate a new file. 2 - Ensure that all logging is set to its most infrequent setting. The above screen shot shows the "Debugging" screen for the "GSM Modem" interface. In this instance, logging has been set to "Nothing", but there are four other options. 1 - Errors - Only errors are logged. 2 - Normal - Only low level information is recorded,. 3 - Detailed - More in depth information is stored. 4 - Verbose - All information is logged. If RAM is operating correctly, then choosing either Nothing or Errors, would be appropriate.

Issue Unable to restore a taclogdata database in SQL Management Studio. The following error message occurs: "An exception occurred while executing a Transact-SQL statement or batch. (Microsoft.SqlServer.ConnectionInfo). Cannot open backup device 'C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\Backup\XXXX.bak'. Operating system error 5(Access is denied.). RESTORE HEADERONLY is terminating abnormally. (Microsoft SQL Server, Error: 3201)" Environment SQL Management Studio - all versions (express 2005, 2008 etc). Vista 5.X Cause The SQL server does not have the authority to access the back up file (.bak). Resolution 1. Identify which account is running the TAC Vista SQL Server a. Open Services - Start\Settings\Control Panel\Administrative Tools\Services. b. Locate the SQL Server (TACVISTA) service. c. In the "Log on as" column, make a note of the user account being used. In the example below the "Network Services" account. 2. Locate the back-up file 3. Change the security settings for the back-up file a. Right-click on the file and select Properties. b. If not already added, add the user account you noted step 1.c and grant the account full control permission for the file. It should now be possible to restore the backup.

Issue When the Update TAC network is selected  from the System Plug-in LNS objects are not updated in the TAC Network View Only Xenta devices are updated. Environment TAC Vista 5.xx System Plug-In Cause The "Include LonWorks devices" is not checked in the TAC System Plug-in. Resolution To correct the LNS objects failing to be updated in the TAC Network, carry out the following steps: In the TAC System Plug-in select the TAC Network from the tool Bar. Select the setting option Ensure the "Include Lonworks devices" option is checked as shown below.

Issue The System Plug-In had a failure and when reopened the TAC Network was missing. Environment Microsoft Window XP SP3 TAC Vista 5.1.4 Cause The failure on the System Plug-In has caused the TAC network to be removed. Resolution To reinstate the removed TAC Network in the System Plug-In follow these steps. Ensure that the Vista Database has not been updated with the blank System Plug-in TAC Network view. If this has been done restore a recent backup of the Vista DB. See TAC Vista Technical Manual for restore process. From the heading bar on the System Plug-in select TAC Network   Then select Import TAC Network Enter the database user name and password where prompted. Select Yes to the "Overwrite current edited TAC Network" prompt. Select your current Lonworks network. The current Vista database will then be imported into the system Plug-In.