Building Automation Knowledge Base

Issue Can not import double-byte (2-byte) character from third party BACnet device receive error "Property invalid datatype" Character support in Building Operation Product Line EcoStruxure Building Operation Environment StruxureWare Building Operation 1.2 and above Cause Building Operation supports various language characters as part of Unicode. These characters are usually received in UCS-4, UCS-2 or UTF-8 and sent in either UCS-2 or UCS-4. Double-byte format such as JIS X 0208 character set is not supported. Here is a reference posted on Microsoft Developers Website: Double Byte Character Sets. The note (second paragraph) of this reference indicates that new applications should use Unicode and that DBCS is a legacy protocol. Resolution There are no plans to support double-byte characters. It is recommended that a Unicode standard (UCS-4, UCS-2 or UTF-8) be used.

Issue DPU Offline shows up when the Door Configuration is selected from the Summary Controller. Product Line TAC INET Environment All versions of I/NET Cause The Resident I/O Points for those doors are either non existent in the save file, offline or have lost communications to the controller. Resolution Verify that the DPUs are Online and communicating to the Controller by clicking connect Controller/MCU Configuration and verify that the addresses are blue and communicating Select Resident I/O Points and verify that the 08 and 09 points does exist for the respective points If not add and then update the database Select Summary/Door Configuration/ and verify that the doors are now in blue rather than red indicating that they are online. Temporary Individuals have the DPU RES check box, which means the information is stored in the DPU (such as a SCU) until the battery runs out.

Issue Error when creating Event Notification Template Error "An error was detected during the creation of a remote refresh cached object Unable to find an object in the database" Seen when creating the EventNotification Template Product Line Continuum Environment Templates Event Notification Cause Error "An error was detected during the creation of a remote refresh cached object Unable to find an object in the database" Seen when creating the EventNotification Template and modifying Ack Required or Priority before pressing "OK" Resolution The error is not always seen but a simple work around is to press "OK" before editing the template. Then re-open and modify the template as required - This issue has been reported to engineering and is being evaluated for correction in a future revision NOTE - This was a minor issue and was fixed by version 1.94

Issue It seems like SNMP is supported but there is no information on how this feature is enabled or used. Product Line Security Expert Environment Security Expert SNMP (Simple Network Management Protocol) Cause The SNMP Feature is seen on the Security Expert license page, showing "Feature : Number of SNMP". Feature : Number of SNMP Resolution SNMP is not supported in Security Expert. The SNMP license item that is showing in the Security Expert Client license page has never been enabled and will be removed in a future release.

Issue The Continuum icon in the system tray does not respond to a right click when attempting to logon to Cyberstation  via a remote desktop connection. Restarting the Cyberstation application will temporarily correct this issue. This problem is usually found when multiple remote machines are accessing the same Cyberstation workstation via Remote Desktop. Product Line Andover Continuum Environment Microsoft Windows 10 Cause Windows Remote Desktop behavior can be affected when several RDU hosts whose screen resolutions are not the same and connecting to a remote workstation.  Resolution Ensure the various machines accessing Continuum Cyberstation over Windows Remote Desktop use the same windows resolution aspect ratio.

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 for assistance. Issue After switching the recovery model from Full to simple, the shrink task fails to shrink the transaction log file. Product Line Continuum Environment Continuum Microsoft SQL Server Cause A transaction log cannot be shrunken while there is a process actively accessing the log file. Resolution Use the log_reuse_wait_desc function in a SQL query to help you identify the process that is preventing the shrinking of the transaction log. Open SQL Server Management Studio.  Click on the New Query button. In the query window type the following SQL statement: SELECT log_reuse_wait_desc FROM sys.databases WHERE name = 'ContinuumDB' Note: The name in single quotes should be the name of the Continuum Database. In some cases, it may have been changed to something other than "ContinuumDb." This query will return one or more of the following keywords.  Each of the following keywords indicates a transaction log process that is taking place. Here is a list of keywords that could be returned. NOTHING CHECKPOINT LOG_BACKUP ACTIVE_BACKUP_OR_RESTORE ACTIVE_TRANSACTION DATABASE_MIRRORING REPLICATION DATABASE_SNAPSHOT_CREATION LOG_SCAN OTHER_TRANSIENT For example, if this query were to return REPLICATION, this would indicate that the replication process has control of the transaction log.  In that case you might investigate the replication configuration or perhaps even turn replication off temporarily to successfully shrink the log. You can find a detailed description for what each keyword indicates by searching the following website Eight Reasons Transaction Log Files Keep Growing

Issue Can expansion boards P8UI4AOC and P8UI4AOV be used with a 7718? Product Line TAC INET Environment I/NET Seven P8UI4AOC Expansion Modules P8UI4AOV Expansion Modules 7718 Process Control Unit (PCU) Cause In addition to the eight inputs and eight outputs on the base card, the 7716 supports the control of additional relay outputs and the monitoring of additional AI, DI, and PI inputs connected via the expansion port. These inputs and outputs occupy point addresses 0100 through 0107. Due to address limitations of the 7718, these expansion boards are not compatible with the 7718. Resolution Expansion boards P8UI4AOC and P8UI4AOV cannot be used with a 7718. Refer to 7718 Process Control Unit - TAC INET - Installation Guide TCON106 regarding supported Expansion Modules.

Issue A Niagara R2 Enterprise Server station is extremely slow in starting, and there are hundreds of alarms. Is there a way to delete all the alarms? Product Line TAC IA Series Environment Niagara R2 Enterprise Server Cause Storing unwanted various alarms can cause the station to boot slow. Resolution The alarms can be deleted in two ways. The first method is to delete the app folder under the station directory. The entire historical content of the station will be deleted. This includes archived trends, alarms, and events. Follow the steps below to delete the app folder. Deleting the app folder to clear the contents of the database only applies to a Cloudscape installation. Open windows explorer and navigate to Niagara\station\[station name]\app Delete or move the app folder Restart the station The second method, is to use the appdb/queryForm servlet to selectively remove data from each table including alarms. This is done by using a web browser. Depending on the size of the database this method may take a substantial amount of time. Follow the steps below to delete data from the database by using SQL queries. Open a web browser and navigate to http://[ipaddress]/appdb/queryForm In the form, enter the following query - delete from event.eventhistory This will delete all history data in this table. For further information refer to the SQL_Tutorial\QueryExamples_10_6_04.pdf

Issue Need an example of how to input or output a particular Structured SNVT type in Menta. Product Line TAC Vista Environment Menta macro block library SNVTs Cause Structured SNVTs use several Member variables to create the SNVT. Resolution Complete macro blocks (FDB or .AUT files) for many of the structured SNVTs exist in the TAC Macro block library. Access the Library: Select menu item File > Open Browse to /TAC Menta/Library/Macro Block Library/Miscellaneous/SNVT., filetype= .FBD (.AUT). Alternatively, right click in your Menta app and select "Load Macro Block" and follow the path above. This Macro block Library has complete examples of how each Structured SNVT is to be configured, showing the units and types of I/O needed for each SNVT.

Issue The CyberStation installation guide states that the Continuum DB Server can be run on a Windows 7 PC while the Continuum Compatibility Matrix does not. Which document is correct? Product Line Andover Continuum Environment CyberStation WebClient ContinuumDB Server Cause There are a variety of documents that describe system requirements for various Continuum products, it is unfeasible to update system requirement information in each document every time a change occurs. For this reason the Continuum Compatibility Matrix should be used as the ultimate word on Continuum products and controllers and the software and firmware that support them. Resolution The Continuum Compatibility Matrix is the ultimate authority when it comes to hardware/software/firmware compatibility.

Issue In Niagara G3, how do I display an object's BACnet instance number within the object in the Wire Sheet? Product Line TAC IA Series Environment Niagara G3 all versions Cause The BACnet object ID is not displayed by default. Resolution Steps for displaying the BACnet object’s ID in the object Right-click in the BACnet object you want to display its objectID and select Slot Sheet Right-click on the view pane and select "Add Slot". Enter "objectID" for Name For Type, select "bacnet" and "BacnetObjectIdentifier" from the drop-down menu and then select "OK" to save Expand the BACnet object in the tree and right-click its "Proxy Ent" and select "Link Mark" from the drop-down menu Right-click on the BACnet object in the tree and select "Link from "Proxy Ent"" Under Proxy Ext (Source) select "Object ID", and under the BACnet object (Target) select "ObjectID" and then click on the OK button The BACnet ObjectID will now be displayed in the object.

Issue Can a UNC be setup as a BACnet server to expose its native Niagara objects as BACnet objects? Product Line TAC IA Series Environment Niagara R2 UNC-520 Cause By default, the UNC can only act as a BACnet client, not as a BACnet Server. A UNC-520 can be configured as a BACnet Server. Resolution Steps for configuring exposing native Niagara objects and BACnet objects: Open the properties of the native Niagara object you want to expose as a BACnet object. Click on its Config tab The foreignAddress must be changed from its default of “-1” to an integer from 0 - 4194302. (BACnet instance number rules applies) Apply the change The object is now exposed as a BACnet object. The following standard Niagara objects can be exposed and BACnet objects: AnalogInput (AI) AnalogOutput (AO) BinaryInput (BI) BinaryOutput (BO) MultistateInput (MSI) MultistateOutput (MSO) Calendar Schedule Reference Chapter 4 of the "BACnet Integration Reference" guide for more detailed information.

Issue Is the Personnel Import Utility (PIU) included with Continuum or is it add-on software? Product Line Andover Continuum Environment CyberStation Cause The PIU is sometimes confused with the Personnel Data Importer, which is add-on software. Resolution The Personnel Import Utility is part of the Continuum system but must be enabled in the CyberStation key before it can be used. The key must have the -D (Data Exchange) option in order for the PIU to work.

Issue Accumulate KW consumption for seven days, then clear the data. Product Line TAC INET Environment I/NET Site Cause How to accumulate KW consumption for seven days, then clear the data. Resolution Add a Consumption extension (CN) to the PI point. Collect the data in a docutrend cell. Consumption data is always reset to zero at midnight, even if the PI point is in test mode. Set the transient duration for seven days. Refer to TCON 237 and TCON 239.

Issue Capability to import a BACnet device objects via an EDE file? Product Line EcoStruxure Building Operation Environment StruxureWare Building Operation site with BACnet Cause Questioning if StruxureWare Building Operation has the capacity to import a BACnet device objects via an EDE file? Resolution We do not support importing from EDE files. We would like to have a good solution for pre-engineering 3rd-party BACnet devices. This is a problem that R&D has looked at on several occasions. The Engineering Data Exchange (EDE) concept is one way to address this issue. Although the BACnet community is in favor of solving this problem, they are not aligned on using EDE files as the solution. The EDE file concept was introduced through the BACnet Interest Group Europe (BIG-EU) by Siemens as an attempt to mimic LonWorks functionality. For worldwide adoption it must become an official extension to the BACnet standard as an approved addendum via the ASHRAE BACnet committee SSPC 135. The BACnet committee has reviewed the EDE file concept and feels that the solution does not fit in with the BACnet roadmap and is not technically ideal. The EDE file is a CSV format and the BACnet committee favors a more modern standard that has extensive self-describing features such as with XML or JSON. For example, BACnet Electronic PICS (EPICS) and BACnet Web Services is XML based and their is an active XML Working Group within the BACnet committee. We understand the BIG-EU is looking to ASHRAE for guidance on this issue and would like to be aligned with the standard going forward. There is a deeper issue beyond adoption by ASHRAE and the technology choice. The reliability of the EDE file cannot be guaranteed. The BACnet Device and Network IDs and objects contained within must be set exactly in the EDE file or configured offline to match the actual device in the field. If these BACnet addresses and objects don't match you will most likely end up with major problems when the database is brought online. Packet captures will reveal duplicate messages and excessive network traffic and references will fail to work. EDE Files for application specific (ASC) devices are likely to have a longer shelf life then EDE files for free-programmable building controllers. However, if an ASC has it's firmware updated, even an ASC EDE file will become outdated and useless. It is rumored that EDE files have been used successfully in the field but want to point out that this is not a fail-safe method nor is it tested and supported. As we continue to participate in the ASHRAE BACnet working groups, we will activity engage ourselves in the pre-engineering solution discussions. Our hope is that a universally accepted solution that can address most of the concerns can become an approved addendum to the ASHRAE BACnet standard.  It turns out that the ASHRAE BACnet committee is further along than reported above. ASHRAE 135-2008 Addendum which added the XML file formats to the standard addresses this application: http://www.bacnet.org/Addenda/Add-135-2008t.pdf Looking at the rational section of this addendum you will see a list of the intended applications: This syntax is intended to be the core data representation for the following use cases: An electronic version of a PICS document, consumable by workstations and other tools, to describe the capabilities of a device. An XML version of an EPICS, defining not only the capabilities of the device, but also including the complete test database and other test-oriented data. An "as built" description of a deployed device, distributed either as a separate file or as a File Object resident in the device itself. Descriptions of proprietary objects and properties and datatypes (in any of the above three uses). These descriptions may be minimalistic, providing basic data sharing capabilities, or extremely rich, providing complete descriptions of the meaning and usage of the data to enable a comprehensive user interface, including the capability of providing such descriptions in multiple human languages. An export format for tools and workstations to export or publish their knowledge of the arrangement and configuration of a device or a complete system of devices and networks. Web services that exchange complex or constructed data With an official ASHRAE BACnet solution it is just a matter of determining which method to go with. Despite the format, it is possible to have a utility application that can automatically generate an export file. It would even be possible to convert an EDE file to XML. Albeit, I believe the EDE file would be less descriptive then an XML file generated from the actual device. It may be better to natively import via XML. We would then either get a BACnet XML file from the vendor or have a small external utility gather from the live device or convert an EDE file.

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 TAC Vista SQL transaction log file is very large and won't shrink. Product Line TAC Vista Environment Vista 5.1.X SQL server 2005, 2008 Cause An SQL transaction log consists of a number of virtual files whose size is defined in the database's properties. Once the virtual file is full, the next virtual file in sequence is used. These files are an essential part of the 'rollback' functionality, allowing SQL to roll back a transaction if for some reason (i.e. disk space runs out)  it can't be completed. With the simple model, the virtual file will be marked as reusable once the transaction(s) contained within the file is complete. So a database may look like this, with the '2' in the status column indicating that the virtual file is still in use: With the recovery model set to a simple, a shrink operation will remove all the virtual files that aren't in use. With the full or bulk-logged recovery model shrink operations behave differently. A full description of this can be found here, but the most important point is that a backup of the transaction log must be made before any virtual files can be marked as reusable.  A shrink operation may not remove all virtual files straight away either so multiple shrinks may be necessary to remove all unused/expired  Resolution Run the following queries: DBCC loginfo This will show the file structure of the SQL log file. BACKUP LOG taclogdata TO DISK = 'c:\taclogdata.bak' Run DBCC loginfo again. Check to see if there is any change. Run a 'Shrink' command (via SQL Management Studio) and then run DBCCloginfo again. Check the size of the database: sp_helpdb taclogdata Keep repeating the process until the database logfile is as small as it can be.

Issue Can the actuator collar and set-screws for the VAV controllers (MNL, MNB, MicroNet 2000 product lines) be purchased separately? Product Line TAC IA Series Environment VAV controllers (MNL, MNB, MicroNet 2000 product lines) Cause Replace parts in the VAV (Variable Air Volume) controllers. Resolution Actuator collars and set screws for VAVs can only be purchased in a retrofit/enhancement capacity as detailed in Product Announcement 06-030. The part number for ordering is DCQC-234-10.

Issue When balancing a MNB VAV box with WorkPlace Tech Flow Balance tool it fails when starting the "Maximum flow" function with an error that states "Unable to read previous balance values." Product Line TAC IA Series Environment MNB VAV WorkPlace Tech Cause This error indicates there is invalid data in the memory location where the balance data is stored. Resolution To clear the error: Open the WorkPlace Commissioning tool Select the VAV box in question and launch the flow balance software from the WorkPlace Commissioning tool. Balance page opens. Click on "Balance Data" in the left column. On the "Flow Balance Details" window, click on the "clear" button Click OK. Start the Flow Balance process again.

Issue Collecting String data from third party BACnet systems where they do not support BACnet String Objects Product Line EcoStruxure Building Operation Environment Third Party BACnet systems Continuum Text/Strings Datetime Cause BACnet String and Date (characterstring-value and datetime-value) objects are not included in some BACnet systems eg. Continuum. Continuum supports these objects types in a proprietary manor but not as BACnet objects, therefore these values cannot be simply collected by EBO Resolution A simple method of collecting text strings from Continuum is to convert each character to its ASCII equivalent number, then pass these values via BACnet Analog Values, then convert back to a string in EBO The simplistic PE program below shows conversion of the first 8 characters of "String8Character" Object to 8 Analog Values "StringChr01-08", these are collected by EBO The Script Program below converts the Analog Values back to a Text String  

Issue How to correctly configure the Live Alarm Printer filtering in Sigma Product Line Satchwell Sigma Environment Sigma release 4.05 SP1, SP2 and SEB Cause General configuration advice Resolution The Sigma Live Alarm Printer filters provide the option of which alarms to print, and which to print immediately. It is only possible to select one filter, per function per printer. In the Sigma Alarm Manager select the "Configure" option, and then select "Printer Filters" Create a maximum of two printer filters, one to "Filter Alarms to Printer" and the second to "Filter Alarms to print now". In reality only one filter might be necessary, but this will depend on site printing requirements. In the Sigma Alarm Manager select the "Configure" option, and then select "Live Printers" Select a "Live Alarm Printer" from printer list. Select a filter in the "Filter Alarms to Printer" option. Select a filter in the "Filter Alarms to print now" option. This is the configuration completed for this printer. If another printer is also required to print "Live Alarms" then repeat the above process again, making sure that the printer is highlighted first.