Building Automation Knowledge Base

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 You want to search for a specific LonWorks device in the database Product Line EcoStruxure Building Operation Environment Lon Cause You might have a duplicate Neuron ID Resolution Make a new search right clicking the LonWorks network and then selecting "New" > "Search" Write an asterisk (*) in the search field Click "Advanced Settings" In "Include types:" select the type you want. Either select the specific device template, or just select all device templates. In "Conditions:" enter the neuron ID or other criteria you want to search for. Now click the search button, and you should find the device you are looking for. Here is an import file with a search sample.

Issue How do I format a Comma Separated Variable file (CSV) to create personnel objects via import that will include area assignments and photos. Product Line Andover Continuum Environment CyberStation Cause Need way to mass create personnel objects. Resolution Typically personnel information is provided from Human Resources in a MS Excel file, the data can be saved as a CSV file and easily formatted for import into the Continuum system which will automatically create one personnel object per row using the information (LastName, FirstName etc) included in the file. Assigning areas during import is accomplished by specifying a personnel template (previously created using Continuum). Different areas can be assigned to different personnel objects as a template can be specified per row. When the personnel object is created via the CSV import, it will be assigned all the areas found in the specified template. Importing a photo for the personnel object is accomplished by specifying an image file in the PhotoFile column. Click Here for a sample CSV file.

Issue Continuum single user system database backup with SQL 2005 Express. Environment Continuum Cyberstation single user (SU) Cause Method to backup system database. Resolution Continuum single user system database backup with SQL 2005 Express. Using SQL Express Management tool Right Click on the Continuumdb> Tasks>Backup Add a Destination where you want the .bak file to be located Click Ok Using sqlcmd With the limited release version of Continuum 1.82 and future 1.9x releases SQL 2005 Express will be the database platform that is used for Single User configurations. Some of you may remember backing up databases in earlier versions of SQL from the windows command line and recall having to create a backup device in order to perform the backup operation. This is the case for backing up a database in the SQL 2005 Express version as well.  Open up the Windows command line and type in CD\ and press enter. This puts us at the root of the drive. Log on to the SQL 2005 server, by typing sqlcmd -Syourmachinename\sqlexpress and press enter. You should see 1> at this point. If you do not see the 1> prompt at this point, a few things could be going on. Make sure you type in your computer name without spaces following the -S switch. Another problem could be that your user logon doesn't have admin privileges. You need to have admin privileges to backup the database.  Once at the 1> create a backup device. Type EXEC sp_addumpdevice 'disk', 'MyDBbackup','c:\myTest.bak' and press enter, which should bring you to the 2> prompt At the 2> type in GO And press enter. This will create a device that we can now use to backup the database. The device should only need to be created once. Now that we have a device named MyDBbackup (you can name yours differently) and are at the 1> again, type in BACKUP database continuumdb TO MyDBbackup with init press enter and you should be at the 2> now type in GO You should have a backup of your database at the root of c:\ named mytest.bak It would be a wise idea to write down the name of the device you have created, since you can use the same device again.  Using the windows task scheduler, you can setup a task to backup your database automatically at the times you've specified in the task scheduler is an easy thing to do.

Issue Maximum number of expansion modules and doors per controller Product Line EcoStruxure Security Expert Environment SP-C Security Expert Security Expert Controller SP-RDM2 Security Expert Security Expert Door Expansion Module Cause Documentation states that one SP-C supports up to 128 doors but this is dependent on the communications.  Resolution The current recommendation from Product Management is a maximum of 24 to 34 doors per SP-C. This equates to about 10 to 17 reader expansion modules.  

Issue Error states: "Ensure that Vista Server is started" when trying to log into TAC Vista Workstation. The server is started. Product Line TAC Vista Environment TAC Vista Workstation 4.2.5, 4.3.0-4.5.0, 5.0.0 and higher Microsoft Windows XP Service Pack 2 Cause Microsoft Windows XP Service Pack 2 has security changes/upgrades from previous service packs.  This affects the DCOM permissions that Vista Server relies on. a variety of other reason could result in an error in DCOM parameters in later operating systems. Resolution Vista 4.2.5 Apply settings described in this TPI to get TAC Vista to work properly. Vista 4.3.0-4.5.0 Apply settings described in this TPI to get TAC Vista to work properly. Vista 5.0.0 and higher Apply settings described in TAC Software Installation Manual available on The Exchange Download Center. This can be done using the DCOM Utility in Helpful Vista Utilities - Configure DCOM instantly, Register ASP.NET. Error Message: Ensure that Vista Server is started lists manual steps to access DCOM.

Issue What is the bCX and NCII required bandwidth? 10Mb, 100Mb Network Connections, GSM Modems. Environment Continuum Ethernet level controllers: ACX57xx, Netcontroller II and bCX1 Cause IT Departments often ask for the required IP Network bandwidth for the CX and bCX controllers; as it is not listed on the datasheets. Is there a bandwidth calculator available? Resolution The Network usage of a bCX/ CX/ ACX controller will vary constantly depending on what is happening on the system at the time. It will be affected by user commends, Graphics, Plain English programming, Access events, reloading or re-flashing controllers and time triggered events. The 2nd generation controllers network connection supports a 10Mb half duplex or 100Mb full duplex auto sensing permanent connection. Note: Older 1st generation controllers (CX9200, CX9400, CX9900 series) only support 10Mb half duplex. So a corresponding up to 10Mb or 100Mb connection would be ideal. GSM Modem or other packet based communication networks are unlikely to be able to provide the continuous data throughput required by Continuum. In terms of bandwidth an absolute minimum of 1Mb in both directions is recommended but this will depend on the specific site requirements you have, for example if there is a requirement to update graphic or alarm values within a specific time then a 10Mb connection would be more appropriate. The following Bandwidth Calculator can be used to determine the % network usage on a 10Mb network connection. This was created specifically for typical Access Control projects, so for HVAC applications the following should also be considered: data logging, PE programs passing data, IP based X Drivers. Fill in the appropriate values in Column D for the system: Bandwidth Calculator.

Issue Are Xenta Servers supported in StruxureWare Building Operations? Product Line EcoStruxure Building Operation Environment EcoStruxure Building Operation Xenta 701, 711, 721, 731, 511, 527, 555 Cause Want to use Xenta Server as a controller in StruxureWare Building Operations. Resolution No there are no special support for Xenta servers. But you can add them as normal LonWorks devices. You can only read/write SNVTs from the Xenta server. Normal Lon rules applies here, you can have a maximum of 64 nodes to a segment (we recommend to keep it under that). TAC Xenta Server I/O modules will not be seen in StruxureWare Building Operation, but they will count towards the 64 nodes on the segment. See Maximum number using StruxureWare Building Operation (Scalability and Capacity) for more information on Lonworks units in StruxureWare Building Operation.  

Issue Right after successfully creating a simple XML Web Service all the values show 0 and the Web Service is offline Product Line EcoStruxure Building Operation Environment Simple XML Web Service Workstation Enterprise Server Automation Server Cause Possible cause 1: SmartStruxure Workstation can handle URL's both with and without the final forward slash even if the URL is just an IP address and a port number. The ES or AS can't handle that, and so after creating the variables through Workstation, the Web Service goes offline after it is added to the server. Possible cause 2: The XML file or response is not UTF8 encoded but "UCS-2 LE BOM" encoded or something else. Resolution Solution 1: Add a final forward slash to the Web Service URL - e.g. http://localhost:8000 should be http://localhost:8000/ Solution 2: Make sure the XML file is correctly encoded in UTF8 - you can check and change the encoding with e.g. Notepad++

Issue Continuum has a limit on the number of entries that can be added to the BBMD table in the bCX and CyberStation. Do the AS and ES servers have the same limitation? Product Line EcoStruxure Building Operation Environment Building Operation Automation Server (AS-P, AS-B) Building Operation Enterprise Server Continuum Cause Limitations must be known for engineering design. Resolution The number of BDT Entries you can add to the BBMD table in EcoStruxure Building Operation is limited only by the available resources, so for all practical purpose there is no limit. Device BDT (Broadcast Distribution Table) FDT (Foreign Device Table) ES only limited by memory 64 (up to v1.4) 600 (from v1.5) AS only limited by memory 64 (up to v1.4) 254 (from v1.5) ASB only limited by memory 50 bCX1 32 32 Cyberstation 1024 1024 Always refer to the Architectural Guidelines for the latest information

EBO doesn't support save from controller for B3s

Issue After upgrading to Continuum 1.94, Cyberstation throws the following error: Failed to call pILiveData -> GetLiveData().  ACDataServices has an error. Product Line Andover Continuum Environment Continuum 1.94 Schedule Error Cause This behaviour is due to a bug that was described in TPA-BOST-12-0002 00 Schedule Exception Errors. Resolution Install the CyberStation v1.94 SP1 - Software which can be found on the Exchange Extranet.

Issue Upon rebooting an MP-V, that has not yet gone through a Flow Balance, the Box Flow data goes to zero. Product Line EcoStruxure Building Operation Environment Building Operation Multi-purpose VAV Cause When a box is not yet balanced, the Balanced K-Factor is zero. Part of the calculation of Box Flow is based on the Balanced K-Factor. Resolution There are two workarounds for this issue: Workaround 1: Balance the box Workaround 2: Enter in a number for the Box measured maximum flow and the Hood measured maximum flow. Either option will update the Balanced K-Factor to being a non-zero value.   This has since been fixed and first consolidated in IPC Hotfix 3.01.02.02000 (CP1), and fixed in release firmware release v3.02.01. See details in Box Flow goes to zero on restart, warm start, or cold start in the Known Issues and Solutions community page.

Issue When logging in to Web Reports, the "Reports Tree" to the left is not shown, and an error message is shown stating that login has failed for the user "NT AUTHORITY\IUSR". Product Line EcoStruxure Building Operation Environment Building Operation WebReports Cause This is a result of not following the Web Reports installation guide.  The SQL Server must be installed with an instance name, and the SQL Server must be started by the user "SYSTEM". Resolution There are two solutions to this issue: Reinstall the SQL Server and Web Reports following the installation guide Use the SBO Reports Agent Config tool on the Community to give access to the 'NT AUTHORITY\IUSR' Alternatively for a more in-depth answer consult How to Fix Login Failed For User NT AUTHORITY IUSRS to add the user "NT AUTHORITY\IUSR" to the SQL Server

Issue After configuring a Niagara R2 station with BACnet MSTP communications, the UNC displays an error in the standard output window: "Cannot load BACnet MSTP Driver". Error details below: *************************************************************** ERROR: Cannot load BACnet MSTP Driver tridium.nre.DriverException: Not found [mstp]    at tridium.nre.Platform.installDriver (bytecode 98)    at tridium.nre.Platform.getDriver (bytecode 42)    at tridium.nre.Nre.driver (bytecode 4)    at tridiumx.bacnet.services.link.mstp.MstpLinkService.init (bytecode 3)    at tridiumx.bacnet.services.network.NetworkPort.linkInit (bytecode 14)    at tridiumx.bacnet.services.network.NetworkPort.linkStart (bytecode 😎    at tridiumx.bacnet.services.network.MultipleNetworkService.start (bytecode 29)    at tridiumx.bacnet.services.network.RouterNetworkService.start (bytecode 1)    at tridiumx.bacnet.services.BACnetService.startService (bytecode 44)    at tridium.foundation.Sys.startServices (bytecode 49)    at tridium.foundation.Station.startStation (bytecode 63)    at tridium.foundation.Sys.boot (bytecode 27)    at tridium.foundation.Sys.bootLocalSns (bytecode 17)    at tridium.tools.StationMain.bootSns (bytecode 0)    at tridium.tools.StationMain.doIt (bytecode 352)    at tridium.tools.StationMain.main (bytecode 10)    at java.lang.reflect.Method.invoke (Native Method)    at tridium.nre.Nre.mainImpl (bytecode 271)    at tridium.nre.Nre.main (bytecode 1) *************************************************************** Product Line TAC IA Series Environment Niagara R2 Cause BACnet MSTP driver does not load on a UNC reboot. Resolution Add the line illustrated below to the drivers.properties file and reboot the UNC: driver.mstp=tridium.nre.vxworks.mstp.VxWorksMstpDriver

Issue References Guide and changes from release 1.3 to release 1.4.x and forward Product Line EcoStruxure Building Operation Environment StruxureWare Building Operation site with regards of release 1.3 to release 1.4.x Cause In release 1.3 and earlier the reference system was relaxed allowing for bindings to be created in ways that made the applications error prone. In release 1.4 this is now being more strictly controlled, which will allow the system to: Help the user to not unintentionally create faulty combinations of references, resulting in bad/unpredictable application behavior and last man win situations Better understand and control how references will behave in copy/paste/move/delete situations. Improve performance in the system, e.g. the limitation of variable connectors is removed. For the complete Reference Guide, please download the pdf from the Download Center For instructions on how to upgrade an Automation Server and how to get the conversion log, See Upgrading Automation Servers from 1.3 to 1.4. For explanations of the entries found in the conversion log, See AS Conversion Log Analysis. Resolution What has changed There are 2 areas which have changed:   1. Rules Programmatic control: A reference means that data is sent from A to B. In Release 1.3 it was possible to send data from A to B and from C to B. This gave a "last man win" situation. In Release 1.4 it is only possible to send data from exactly one source to a recipient. This means A to B and C to B is no longer allowed. User control: This is where properties are displayed in graphics, watch windows and other client components. In release 1.3 it was possible to change a property that was programmatically controlled. This gave a "last man win" situation. In release 1.4 it is not possible to change a property as a user if this property is programmatically controlled by something else. The property will automatically be read only for the user.   Public signals: In release 1.3 and earlier, it was possible to programmatically control a public value in programs. Public signals are intended to be used for user control, while inputs are intended for programmatic control. In release 1.4 this is now changed to the following: Public signals in programs (FB/Script/Menta) can be referenced by user control - NOT by programmatic control Public signals intended for programmatic control must be changed to inputs and rebound. This will give the following benefits: Public signals cannot be forced, while inputs can. If a user needs to take control of a programmatically controlled input, via e.g. graphics or watch window", he will force the signal and there will be no risk of a program overwriting the user value. As stated above - if an input is programmatically controlled, this will for the user be read only. However, force is still possible. There is no more risk for "last man wins" situation between user control and programmatic control. The system will remove any ambiguity with these new sets of rules. Update: Release 1.4.1 and later version add the feature of binding to PVB/PVI/PVR back. But for Script, it still keeps the same. LonWorks Local Node nvis: In release 1.3 it was possible to programmatically write to local node NVIs. These NVIs exist to receive data from the LonWorks network. This gave a "last man win" situation. In release 1.4 it is no longer possible to programmatically control local node NVIs.   2. Definitions In release 1.3 a reference could be a) relative b) system absolute c) server absolute In release 1.4 a reference will be a) "normal" b) Locked A reference created by the user will always be normal (which means relative). In the bindings view the user can then choose to "lock" a reference (which means server absolute). The references will behave identically until a copy/paste (or import/export)  operation is done.         Upgrade Upgrading from release 1.3 to release 1.4 will apply the new sets of rules. It is there for very important to read the log to understand if any existing references in release 1.3 will be impacted during the upgrade For AS: In the Device Administrator the logs are available before the upgraded DB is deployed to the AS. It is up to the user to either examine the upgrade log, make changes in running release 1.3 and rerun the upgrade, or to make the changes after upgrade. It is recommended to do changes prior to upgrade to ensure a fully functional system directly after upgrade. Some warnings are benign and can be disregarded, please refer to release notes for more information. IF an upgrade detects that references will be impacted, the user will be informed about this with a orange progress bar indication and a written information that the upgrade succeeded with warnings. After upgrade, all invalid or unresolved references will be visible from WorkStation for further examination if needed.

Issue Procedure to upgrade SQL database from TAC Vista 5.x.x to 5.1.7 Environment TAC Vista 5.x.x TAC Vista 5.1.7 MSSQL Express 2005 SP4 MSSQL Express 2008 R2 -SP1 Cause Revised TAC Vista SQL database layout: TAC Vista 5.1.7 introduces a revised and improved SQL database layout in order to improve the overall performance in the TAC Vista system with large databases. The revised database layout is utilized by default for new installations and current installations can be upgrade either automatically or manually depending on the installation type. SQL 2008 R2 Express SP1: Microsoft SQL Server 2008 R2 Express SP1 is now included in the TAC Vista Server 5.1.7 installer. The TAC Vista Server installer can upgrade an existing SQL Server 2005 Express installation to SQL Server 2008 R2 Express SP1; only supported in a typical TAC Vista installation.     Resolution Follow the Instructions before Implementing this procedure: Take the Vista Backup and SQL DB backup before implementing this process. Shutdown the TAC Vista Server. If the Vista Server running as a Server, Stop the service and shutdown the TAC Vista Server. Open the “SQL Database Upgrade 5.1.7” (From Program Files [or] from Start Menu)   Check the Server and Database options.   Choose the correct type of Authentication. If the vista using SQL Server, choose the SQL Server Authentication, enter the correct Login details.   Click on “Test Connection” and “Test User access”. You should find Test Connection access and Test User access successful. If Vista and SQL DB backup has taken, check on the “Check Box”.   Click on “Upgrade”, then the following screen appear. Then Click on “YES” to upgrade.   After the upgrade is complete check the Vista Server has a connection to the upgraded SQL database. This is done from the Vista server setup. Use the test connection If the connection is successful you will see a message like this.   Now, the SQL database has been upgraded. Download this procedure in PDF Here .

Issue Archiving and database size with FIFO not working Product Line TAC INET Environment I/NET site Cause dbo.Events keeps growing and presumably is not in FIFO mode (First In First Out) Resolution Note: Autogrowth is not used with TAC I/NET Seven or TAC Andover Continuum The size of the InetDB can be set through Microsoft SQL Server Management Tool:   By selecting the InetDB database properties you can set the Autogrowth setting via the Files page.  Under the Autogrowth column select the browse button as shown:   The Change Autogrowth setting by either disabling the Autogrowth check box or you can set Autogrowth to a Maximum File Size as shown:     The Autogrowth value now shows this setting is restricted to setting define in step 2.   Disabling Autogrowth allows the events to be removed from the table when the total size of the SQL database reaches the limitation set in the properties of the db. The table dbo.Events has all the current events and it should be the biggest. The dbo.currenteventdetail table keeps up with the current max events and the current minimum events. Lets say it is around a million (1,000,000) events and so the first event in this table would be 01 and the last would be the 1000000. If items are removed from the other table, the dbo.Events, then this other table, the dbo.currenteventdetails is off. This means we run the risk of losing those events that are not correctly numbered. Manually removing items from one table can have an impact on other tables and how this data is kept and archived. About archiving and shrinking the db, this is a function of SQL. SQL goes into a FIFO mode, which means First In, First Out. This keeps the db from getting to large. The archived records are designated as archived in the db and even though they are still (secretly) in the db, they will be out as soon as the db is over the capacity amount and the amount designated in the db.currenteventdetail table is the guide for what is current. The thing that keeps the db from getting to large is the archive is setup correctly and old data is archived. It is still available via Reports, but considered not technically in the db. That is what shrinks the db and keeps it from getting over size.    Note: Autogrowth is not used with TAC I/NET Seven or TAC Andover Continuum

Issue Configuring Daylight Savings Time. What is the proper way to do this? Product Line TAC INET Environment I/NET Cause There are two different ways to setup the Daylight Saving Time in I/NET. Daylight Saving Time DST is not observed in Queensland, the Northern Territory or Western Australia, South Africa, and other parts of the world. The document below shows how to set 0 in the DST settings. If using a revision of I/NET prior to 2.21 be reminded that the DCU time sync problem in the ReadmeSeven.txt is not just pertaining to the error generated by not having DST settings for the controller. 2.21 is referring to the version where this was fixed. Also note that when upgrading a site, go all the way to 2.31 at least because it solved problems which were in the previous revisions. Resolution Option #1: Using Windows time and NO controller time synch Set Windows Time for daylight savings changes. Remember to change the time zone for you location. In my example I am in the Central time zone. Set the Inet Host settings to do Time Sync. Function for all the controllers you wish to time sync with the PC. Enable the Daylight Savings settings using the "Setup" button. This is the correct settings for the controller configuration. Note if you set the daylight settings in this format you will get a 2 hour shift up or back. The daylight setting must be set to zero (0)   Option #2 Using Windows time and controller time synch Set Windows Time for daylight savings changes Set the Inet Host settings to NO Time Sync. Function This the correct setting for this controller configuration using the controller to shift the daylight saving time   The Daylight Savings times were set by the Congress of the USA in 2004 The beginning was to be the second week of March on a Sunday. This comes out in I/NET as being Month = 3 Week = 2 Day = 1 (Sunday is always day 1 Thus Saturday is day 7) The ending was to be the first week of November on a Sunday This comes out in I/NET as being Month = 11 Week = 1 Day = 1 (Sunday is always day 1 Thus Saturday is day 7)

Issue After using the STR-350/351 as an I/O module to a Xenta programmable controller and then using STR-350/351 LonMaker Plug-In the changes made in the Plug-in default back to previous settings Environment Vista LonMaker, NL-220 STR-350 Plugin Cause If the STR was added to the Menta application then the controller will continually update the STR with the settings programmed. Any changes made with the STR LonMaker Plug-In will then be overwritten. Resolution In order to use the STR 350/351 LonMaker Plug-In, the STR must not be set up in classic mode by adding it in the Menta application of the controller communicating with it. If the STR-350 has already been added to a Menta application it must be configured using the Menta application. Otherwise, the STR-350 should be removed from the Menta application before attempting to configure the STR-350 as a Lon node using the Plug-in.