Building Automation Knowledge Base

Issue When a XIF file is imported in XBuilder, one or more SNVT's show a strange icon rather than the input or output symbol and even though the SNVT is supported. Environment XBuilder XIF SNVT Cause TAC XBuilder doesn't support multi line self documentation string for SNVT's Resolution [1] Edit the XIF file with a clear text editor such as notepad, notepad++ or jEdit [2] Locate the SNVT name(s) that has the issue (e.g. "VAR nviMode") [3] Delete all lines in the self documentation except from the first (Don't just place all the text on one line, as there is a max for characters on each line)       [4] Import the XIF file again

Issue On large screens, the alarm texts in the alarm list can be too small to easily read. Product Line TAC Vista Environment Webstation Cause Depending on the resolution, the size of texts will seem larger or smaller. Also, though the text is actually the same as the size used in Workstation, it seems that Workstation represents the text in a clearer way. Resolution All styling of Webstation is done with style sheets (CSS files) and can be changed at your own risk. PSS does not support changing these files. Browse to the styles folder (C:\inetpub\wwwroot\TACVistaWeb519\Style\Default) where "519" in this case is the version of Vista installed, and "Default" is the style selected in Webstation Settings. Make a copy of the file "AlarmListPage.css" and store it in a safe location. Edit the file "AlarmListPage.css" with e.g. notepad or another clear text editor (don't use MS Word or similar) Here are two different style options. You can make your own. To change the font size for everything in the alarm list, go to row 16 and change "x-small" to "small" To only change alarm text rows but leave the title size, go to line 54, and add an extra line here "font-size small;" To reduce the space between the actual texts in the alarm list and the cell borders, change line 51 to 0px and line 52 to 1px Save the file, and reload the page. You might need to manually chose to reload the web page, for the change to actually go through Examples Original All texts set to "small" Only alarm text rows set to small, and spacing lowered

Issue When using the Graphics Converter you get the error 'Failed to restore permissions to object' or 'Failed to restore permissions to parent object' one some or all graphics Environment Graphics Converter Cause At some point, an erroneous authority definition has been introduced to the database, making it impossible for the converter to restore the permissions. Resolution On all the folders containing graphics giving this error do the following: 1. Set the authority on the folder as below, overwriting the permissions on all sub objects 2. Restore special permissions on sub objects as required 3. Convert the graphics as normal

Issue When importing a XIF file generated by XBuilder a warning (that might look like it's an error) is shown regarding missing file name and generated date Environment SmartStruxure Xenta Server XBuilder Cause The XIF file generated by XBuilder doesn't completely follow the LONMARK Device Interface File Reference Guide Resolution The warning can be disregarded, but the XIF file can easily be altered to avoid getting the warning if desired Open the XIF in notepad or similar editor, and change the following. Note the colon before the filename. Original XIF header File generated by TAC XBuilder version 5.1.9, XIF Version 4 Copyright (c) 2000 by TAC AB All Rights Reserved. Run on 0000-00-00 00:00 Changed XIF header File: X913.xif generated by TAC XBuilder version 5.1.9, XIF Version 4 Copyright (c) 2000 by TAC AB All Rights Reserved. Run on Mon Nov 03 08:00:00 2014 File generated by TAC XBuilder version 5.1.9, XIF Version 4 Copyright (c) 2000 by TAC AB All Rights Reserved. Run on 0000-00-00 00:00File generated by TAC XBuilder version 5.1.9, XIF Version 4 Copyright (c) 2000 by TAC AB All Rights Reserved. Run on 0000-00-00 00:00

Issue In the past there was no way to calibrate the space temperature from a STR-150 when used with a Xenta 121 FC/HP.  Environment STR-150 Xenta 104A Xenta 120 Xenta Programmables Cause Any calibration applied to the temperature of a STR-150 had to be done downstream of the stat in the controller. In the past when the STR-150 room stat was wired up to a Xenta 121 there was no way to calibrate the space temperature as the Xenta 121 FC/HP had no kind of Temp Offset in the controller. Resolution Starting with version 1.4 (released September 2013) of the STR-150, there is a calibration feature built into the stat. This feature allows the calibration to be applied before the temperature is sent down to the controller (Example: Xenta 121 controller). Below you can find out how to check the version number of the stat and how to perform the calibration. There is not a way to upgrade older versions of the STR-150 to 1.4 or greater. Checking the STR-150 version number The version number of the stat can be found as parameter P0. View version: Push the fan and bypass button simultaneously for 2 seconds to display P0. The version number will be displayed here. Using the STR-150 Calibration Feature Enter Configuration: Push the fan and bypass button simultaneously for 2 seconds to enter P0.   In P0, hold down the bypass button and push the fan button three times to enter configuration mode. Note: the wrench symbol is lit when the STR-150 is in configuration mode.   In Configuration Mode: Press the fan button repeatedly until you reach parameter F0. Note: The two digits farthest to the left on the display show the parameter, while the two digits farthest to the right show the value.   Use the increase or decrease button to adjust the value. The offset scale ranges from 0-99 which corresponds to -5.0 to +4.9 degrees. If the STR-150 is setup for degrees C, then the offset is exact. If the STR-150 is setup for degrees F, then the offset is recalculated to a corresponding value.   Exit Configuration Mode: Push the fan and bypass button simultaneously for 2 seconds or allow the idle timeout to exit configuration mode on its own.

Issue References to objects and points are not easily understood Product Line TAC Vista Environment Xenta Server (511, 527, 701, 711, 721, 731, 913) Cause The references relates to the internal indexes in the project Resolution Here is an example of how to locate a Menta signal referenced in an error log. The procedure is the same for all other types, although the file names may vary. This is an example taken from an error log:   1337 03-09-2014 10:41:19 AM minor trend TLogNotifier 1 menta.5.62 Variable type disagreement (Error#:61971) 1336 03-09-2014 10:41:16 AM minor trend TLogNotifier 1 menta.5.60 Variable type disagreement (Error#:61971) 1335 03-09-2014 10:41:13 AM minor trend TLogNotifier 1 menta.5.61 Variable type disagreement (Error#:61971)   Here is how to locate the signals menta.5.62, menta.5.60 and menta.5.61 Navigate to the XBuilder location on your hard drive, and browse to the folder "TargetImage\configdb". If the XBuilder project is part of a TAC Vista database, either save the XBuilder project outside the database, or locate the zip file containing the project and un-zip it. Depending on the signal reference browse the folder appropriate folder - in this example "menta". Open the file "menta.xml" in notepad or similar - for a better overview you can paste the content of the file on this web page: XML Pretty Print Locate the program id and note the reference. In this case it's id 5: Open the file "mentablocks.xml" in notepad or similar - for a better overview you can paste the content of the file on this web page: XML Pretty Print Locate the signal id's under that program id, in this case it's: Open the file "BHP BILLITON/Mentas/Water Meters.aut" in notepad or similar Locate the ObjectId's, in this case it's: #1 "MUNIC_ABL" [124,32,0,1] '','','946C6EE5-4884-4c24-804F-F7E95BAF262D' = XPR {A-B-C-D-E} #2 "RAIN_ABL" [125,77,0,1] '','','1277F8E5-5451-4dad-BEBF-1461EC75AC30' = XPR {A-B} #3 "GREY_ABL" [124,122,0,1] '','','3FF1B614-2379-47a2-BFCA-782EEE4ADAC4' = XPR {A-B-C-D}

Issue Description of the Parameters used in the 102-AX Plug-In Product Line EcoStruxure Building Operation, TAC Vista Environment LonMaker NL220 HTML 102-AX Plug-In Cause This may aid in finding the SNVT associated with each Plug-In field. Resolution nviBoxFlow nvoActualValue nviAplicMode nviOccCmd nviEmergCmd nvoLocalLatch   INPUT OBJECTS nvoUnvInput1 nvoEmergCmd nvoAuxTemp1 nvoUnvInput2 nvoLocalOccLatch nvoUnvInput3 nvoCO2ensor nvoAuxTemp2 nvoUnvInput4 nvoSetPtOffset VAV STATUS nvoOccpncyStatus nvoUnitStatusMode nviTerminalLoad nvoSpaceTemp nvoEffectSetPt nvoBoxFlow nvoFlowControlPt nvoAirPressure nvoHighSpaceTemp nvoLowStaticPress nvoLowStaticPress nvoOAirFlowRatio NETWORK BOUND INPUTS nviApplicMode nviOccCmd nviEmergCmd nviAirFlowReset nviCO2 nviDuctInTemp nviOutsideTemp nviRelStPt nviUnvOutput1 nviUnvOutput2 nviUnvOutput3    UCPTcooling Band SCPTsetPnts.unoccupied_cool SCPTsetPnts.Standby_cool SCPTsetPnts.occupied_cool UCPTheatingBand SCPTsetPnts.unoccupied_heat SCPTsetPnts.Standby_heat SCPTsetPnts.occupied_heat UCPTovrdDuration SCPTmaxRange UCPTresponseRate nviSetPoint nciVAVSelctnCntl.oP.ESS (UCPTvavSelection UCPTnormalPeriod.minute UCPTnormalOpen Airflow Setpoint SCPTminFlow SCPTmaxFlow SCPTminFlowStby UCPTunocAirFlow SCPTminFlowHeat UCPTminFlowWU UCPTmaxFlowWU UCPTfanOnFlow UCPTfanOffFlow Airflow Reset nviAirFlowReset UCPTco2LoReset UCPTco2HiReset Outside Air Requirement UCPToccOAReqd UCPTunocOAReqd nvoOAirRatio Airflow Setting SCPTgain UCPToffsetPress UCPTpressCutOff UCPTairFlowCoeff UCPTloStatPrior  

Issue UPC Barcodes and EAN Barcodes Environment Site ordering parts from Schneider-Electric Cause What are UPC Barcodes and EAN Barcodes Resolution The EAN contains a 13 digit number and the UPC contains a 12 digit number. EAN = 0012345678905 UPC = (0)012345678905 or 012345678905 GS1, the original source for barcodes has created the confusion between UPC (Universal Product Codes) and EAN (European Article Numbers also called International Article Numbers) Below is an example of a Schneider Electric SHR110 room RH/Temp sensor:

Issue In some cases, if the block connected to reset (rs) of a Run Time (RT) block is a trigger (TRIG) block, the RT block will never reset. Environment Menta Xenta Cause If the order of the TRIG and RT block is not correct, the RT block will miss the pulse from the TRIG block. This only seems to happen when the block connected to the TRIG block is a PV block such as PVB. If the block connected to the TRIG block is e.g. a physical input such as DI the problem doesn't occur. Resolution There are two solutions to this problem Solution 1: Create the blocks in the correct order First create the "TRIG" block and then create the "RT" block. If you already have both, then delete the "RT" block, save and create a new "RT" block. Solution 2: Add a DELB block Add a "DELB" block before the "TRIG" block. This will make the "TRIG" block hold the signal long enough for the "RT" block to detect it.

Issue The first time a TGML graphic is opened after logging in through Workstation it takes a long time (approximately 30 seconds) before the graphic is shown Product Line TAC Vista Environment Windows Domain TAC Vista .NET Framework Cause This is usually only an issue when the PC has either no or a bad internet connection or is located behind a proxy server. The reason this is happening, is because an application using e.g. signed .NET Framework dll files will check for certificate revocation each time it's launched. That can only be done if the PC has internet connection. If the PC can't connect to Microsoft's server to get the newest list of revoked certificates, the application will appear to hang until a given timeout is reached. The default timeout is 35 (15+20) seconds. For a deep explanation of certificate revocation check and the base of this article, read this article. Resolution There are two solutions that can be implemented. The first is mandatory and the second is optional. The first solution solves the slow TGML opening issue, while the second seems to have a positive overall performance impact but doesn't solve the slow TGML opening issue. A third solution is to get internet connection for the PC, but that is usually not an option. Solution 1 : Lowering the timeout 1. Open the "Local Group Policy Editor" by typing "gpedit.msc" (no quotes) in "Start"->"Search programs and files..." 2. Navigate to "Local Computer Policy"->"Computer Configuration"->"Windows Settings"->Security Settings"->"Public Key Policies" 3. Open the object to the right called "Certificate Path Validation Settings" 4. In the tab "Network Retrieval" check "Define these policy settings" and write 1 in both retrieval timeout settings 5. Click "Apply" and "OK" and close "Local Group Policy Editor"   Solution 2 : Manually installing the newest certificate lists 1. Download the newest CRL updates from a PC with internet connection http://crl.microsoft.com/pki/crl/products/CodeSignPCA.crl http://crl.microsoft.com/pki/crl/products/CodeSignPCA2.crl 2. Copy the two files to the PC having the issue 3. Open a command prompt and navigate to the folder where the files are located 4. Install the CRL files using the following commands CertUtil -AddStore CA CodeSignPCA.crl CertUtil -AddStore CA CodeSignPCA2.crl

Issue When commissioning or decommissioning devices in LonMaker you get a message that your request has been placed in the transaction queue. Environment LonMaker LNS Cause You usually see this message if LonMaker is trying to update devices in the background and the devices are offline or can't be reached. Resolution To see if this message is due because LonMaker is trying to update devices in the background, please try to set the Update Interval property to 0. This can be done in LonMaker by going to the LonMaker menu->Network properties->Timing.  Setting the UpdateInterval to 0 will prevent LonMaker to update devices in the background. Please note that this setting is not usually recommended. If the message disappears once the UpdateInterval is set to 0, it means that devices need to be updated to match the database. If the delay is long, it can be because there are a lot of devices that needs updating and/or LonMaker can not communicate with them. Make sure all devices configured and commissioned are online and available.

Issue All setpoints are lost after a power outage and the function block programs revert back to initial value. Environment Menta Function Block Editor Menta Editor Xenta 280/300/400 Controllers Cause A Menta, Menta Editor, or Function Block Editor program with configurable setpoints will be lost if the default programming settings are used and there is a power loss. Resolution Backup feature in function blocks Menta and Menta Editor When the Backup check box is selected, the current value of the block output and internal states in the RAM are used when the device makes a warm start. Otherwise, the block output and internal states are reset to their initial values (same as for a cold start) at a warm start if the Backup box is not checked. If a power outage lasts longer than the power failure protection time for the device and the RAM contents are lost, the restart is a cold start. All blocks will be rest to their initial states regardless of the Backup option. The RAM working member that includes current values will last for 72 hours without power. Function Block Editor When the Backup check box is selected, the current value of the block output and internal states in the RAM are used when the device makes a warm start. If a power failure occurs, all important variables are automatically saved to the flash memory before complete shutdown. When power returns, this data retention function ensures that the Automation Server can continue to run with the correct set of values.

Issue 'Failed to connect to SQL Server (local\TACVISTA). "[18470] Login failed for user 'xxx\xxxxx'. Reason: The account is disabled." message appears when trying to install Vista using another account than the account that is logged on to the server. Product Line TAC Vista Environment TAC Vista 5.1.X SQL installation/connection Cause The TAC Vista installer SQL configuration settings page states 'Select authentication and specify SQL Login or Windows account and password to set how TAC Vista Server will access the SQL server.' This means how TAC Vista will access the SQL server when Vista is running, not during installation. Resolution Ensure that the user running the TAC Vista installer has the correct permissions to install an SQL server (if this is a new database) and configure it. The specified user will be used during runtime, but the launching user during installation. The installing user can then be removed from the SQL server security settings after installation is complete.

Issue Alarm view is not shown in Webstation instead this or similar is shown: The following errors have occurred. Please correct these errors and/or contact the system administrator. An unexpected exception has occurred: Index was outside the bounds of the array. System.IndexOutOfRangeException at TAC.WebStation.Modules.Alarms.AlarmViewTable.GetColumnData(Object[] rowData, Int32 columnIndex) at TAC.WebStation.Modules.ViewTableBase.AddColumnsToQueryString(QueryString queryString, Object[] rowData, Int32[] columns) at TAC.WebStation.Modules.Alarms.AlarmViewTable.CreatePropertiesCell(Object[] rowData) at TAC.WebStation.Modules.Alarms.AlarmViewTable.CreateAlarmRow(Object[] rowData, Int32 rowIndex, Boolean isDisabledView) at TAC.WebStation.Modules.Alarms.AlarmViewTable.CreateTable(Table table) at TAC.WebStation.Modules.ViewTableBase.FillTable(Table otherTable) at TAC.WebStation.Modules.Alarms.AlarmListPage.DataBind() at TAC.WebStation.Modules.Alarms.AlarmListPage.Page_Load(Object sender, EventArgs e) at System.Web.UI.Control.OnLoad(EventArgs e) at System.Web.UI.Control.LoadRecursive() at System.Web.UI.Page.ProcessRequestMain(Boolean includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint) Product Line TAC Vista Environment TAC Vista Webstation TAC Vista Server Cause If "site" is checked in the $alarmcolumns object this happens. This is a known defect. Resolution Find $Alarmcolums in the root folder In workstation Go to Properties and uncheck the site option

Warning Potential for Data Loss: The steps detailed in the resolution of this article may result in a loss of critical data if not performed properly. Before beginning these steps, make sure all important data is backed up in the event of data loss. If you are unsure or unfamiliar with any complex steps detailed in this article, please contact Product Support Services for assistance. Issue When clicking the menu point "Utilities"->"ProjectTree" the project tree doesn't open as expected in the window. Environment TAC Xenta Server Cause There is a problem with the file "applets.html" in the Xenta Server. Resolution You need FTP connection to the Xenta Server in order to carry out the following steps 1. Make sure that FTP access is enabled for the root user - this menu is available from Configuration->User administration->User administration                           2. Make sure that the number of concurrent FTP users is higher than 0 Correcting the html file 1. Connect to the Xenta Server with a FTP client 2. Browse to the location "/www/japplets" in the Xenta Server 3. Copy the file "applets.html" to your desktop 4. Make a backup of the file on your PC 5. Edit the file "applets.html" on your PC, e.g. with Notepad++ or another editor 6. Scroll down to line 376 - it should say "function writeXBMenuAppletTag" - if not you need to locate this line 7. Change the text "cyrrDoc" to "currDoc" 8. Save the file 9. In the FTP client, copy the edited "applets.html" file from your desktop to "/www/japplets" in the Xenta Server 10. Restart your browser Check if the project tree is opened now when the menu is clicked     The project tree will also open if you use "Tree2" as the menu type rather than "Menu" and Tree"

Issue When you use Webstation to access alarms in a Vista database you get a error in the alarm pane. Product Line TAC Vista Environment Vista 5.1.x Cause The $alarmColumns under the root directory has all of the selected columns selected for display. Resolution To get the Webstation alarm pane to display correctly uncheck one of the columns. This has been noted as a QT6670 and not to be fixed

Issue How to set up a Operator Panel to only see the TAC Xenta controller it is plugged into Product line EcoStruxure Building Operation Environment TAC Xenta Operator Panel firmware 3.7 TAC Xenta Programmable controller 3.85 or higher Cause When the Operator Panel is plugged into a TAC Xenta programmable controller the whole network of TAC Xenta controllers are listed. Resolution This option and the requirements are described in this TPA To enable the option in the TAC Xenta: How to enable this in the TAC Xenta: Edit the application and create a Public PVI-block with the name XENTASYSREG and set this block’s initial value to 8. If you have multiple TAC Xenta OP panels in the network, each one connected to a specific TAC Xenta Controller, it will be required to create this special PVI block in every one of these TAC Xenta Controller’s application code.   To enable the option in the OP Panel: 1. Open the TAC Xenta OP local service menu, by pressing and holding the “escape” and “enter” buttons for a few seconds. 2. Enter the bottom command: “11 OP connects to”. 3. Enter this sub-command, and then type in, using “+” or “-“, the specific TAC Xenta controller’s subnet and node address you want this OP to be “locked” to. The TAC Xenta controller subnet and node addresses can easily be found in TAC Vista Workstation; select “properties” for the TAC Xenta controller and the subnet/node address will be displayed. Observe that when you select, in the OP panel’s new menu, the node number and press enter the TAC Xenta OP will restart and seek for this now selected TAC Xenta controller. Note that it is still possible to access this specific TAC Xenta controller from another TAC Xenta OP in the network if that TAC Xenta OP is of a version prior to 3.70 or this new “lock-function” is not enabled in that TAC Xenta OP. However doing this, you will only here also “see the local TAC Xenta controller”. In this case you will be able to exit this TAC Xenta controller again by pressing “escape”. While in the locked TAC Xenta OP you will not be able to exit from the TAC Xenta controller it is locked to.

Issue All the alarms from an OPC Alarm & Events (AE) server are coming in as priority 5. Is it possible to change this? Product Line TAC Vista Environment Vista OPC Alarm Events (AE) client 3rd Party OPC AE server Cause The alarm categories/priorities for alarms that come from an OPC AE server are set on the OPC server. Some OPC AE server offer limited configuration possibilities and it may be desirable to change the category/priority in Vista. Resolution The priority can be changed by: Select the OPC AE server object in TAC Vista Workstation Open the Properties dialogue Locate the alarm settings section and the alarm category mapping will be displayed. By default "Use alarm priority map" is selected. In the example below, all the alarms from the OPC AE server with a category of between 500 and 599 will be mapped to category 5 in Vista. This mapping can be changed as desired.

Issue After a power cycle the Xenta Server need to be re commissioned to get it SNVTs functioning and the controller back online in NL220 or LonMaker Environment Lonmaker, NL220 Xbuilder 5.1.6. Cause As the Xenta Server is used in LonMaker and Vista the subnet is set in the Xenta project. When you then commission in NL220 or LonMaker the address is then set to the LonMaker or NL220 database specification. On a power failure the Xenta server reverts to its Xbuilders Subnet node address and goes offline in LonMaker or NL220 Resolution Save the X-Builder project out of the Vista database. this will allow the Subnet node to be set under the LON heading in the X-Builder project. Match the subnet and node address to the LonMaker or NL220 database subnet and node address of the Xenta Server. Save the X-Builder project back into Vista and then download to the Xenta Server. Now on a power cycle the subnet and node will Match the LonMaker or NL220 database and remain online.

Issue Xenta server trend logs not showing up in the Vista Server even though they were sent to be "Manual - On" in the XBuilder project. Environment XBuilder Workstation Xenta Server Vista Server Cause The Xenta Server trend can be set to "Manual On" or "Automatic" in the XBuilder project but still not transfer trend values over to the Vista Server. Resolution The Xenta Server trend log must be activated in the Vista Server as well as the Xenta Server. In Vista Workstation, locate the Xenta Server trend log, right click on it and go to Properties. Click on the "Vista Control" tab. Change the "Activate" field to Man-On or Auto. Click OK.