Building Automation Knowledge Base

Issue How to add a calibration factor or offset value to an input using automatic scaling. Product Line Andover Continuum Environment Continuum Universal Input Cause If using the Conversion field to offset the ElecValue on an input that is using an automatic scale, the resulting value will not be calculated properly. Resolution For this to function with an input using an automatic scale we need to setup an InfinityFunction to do the scaling for us and then add/subtract our offset from this result.   1. Create a new InfinityFunction in the controller called “IPConvert” 2. Paste the below code (between the lines) into the function and save it. ======== 'This InfinityFunction must be called from the conversion line of the input 'This InfinityFunction will allow an offset to be applied to a universal input 'Example Conversion line in the Input - IPConvert(EngScaleTop, ElecScaleTop, EngScaleBot, ElecScaleBot, -1) Arg 1 EngTop 'Engineering Units -  Top of Scale Arg 2 VltTop 'Voltage -  Top of Scale Arg 3 EngBot 'Engineering Units -  Bottom of Scale Arg 4 VltBot 'Voltage - Bottom of Scale Arg 5 Offset 'Amount to Offset returned value Numeric Slope, C Slope = ((EngTop - EngBot) / (VltTop - VltBot)) C = EngBot + (Slope * (minimum(VltTop, maximum(ElecValue, VltBot)) - VltBot)) Return C + Offset ========== 3. Go to your inputs on that controller that need to use this function. 4. confirm that the auto conversion fields have been set to the scale range you require. 5. type the below into the conversion field, replacing the “-0” at the end with whatever offset is required. IPConvert(EngScaleTop, ElecScaleTop, EngScaleBot, ElecScaleBot, -0)

Issue Backup and Restore Process for WebReports Product Line EcoStruxure Building Operation Environment WebReports Reports Server SQL Server 2008 R2 Cause Need detailed backup process Resolution Refer to Online Help Topic for details Backing Up the WebReports Database  On the Windows toolbar, select Start, and then click SQL Server Management Studio. Click Connect.   Note: When using a remote computer to connect to the Report Server SQL database, the Windows Accounts must exist on both machines and have administrative rights for the SQL database otherwise a successful backup will not occur.  In this instance, it is recommended to use the SysAdmin 'sa' login / password details when connecting in remotely.   Expand the Databases folder. Right-click StruxureWareReportsDB, point to Tasks, then click Back Up. Under Destination, click Add. Click OK. In the Destination on disk box, select the backup destination. Click OK. Click OK.   Restoring the WebReports Database Ensure the Enterprise Server is up and running with the correct database.  Stop the SQL Server Reporting Services and WebReports Agent (if installed).  Note: If moving the WebReports Database it is recommended to restore the database then Install WebReports.  Then when Installing WebReports select Upgrade existing (as shown) and NOT New database  Restore the WebReports database to recover reports data from backup.  This will include any Dashboard reports saved. On the Windows toolbar, select Start, and then click SQL Server Management Studio. Click Connect. Expand the Databases folder. Right-click StruxureWareReportsDB and select Tasks, then select Restore, then select Database. In the Restore Database dialog box, select the database set(s) that you want to restore. Click OK. Click OK. If not already installed now complete the installation of WebReports 

Issue Created new Alarm Enrollment, attach to point and put point in alarm but no alarm is received and the points alarm value does not show the point is going in alarm. No problem when using an existing Alarm Enrollment created in the past when the total number of Alarm Enrollment objects was much less. Environment CyberStation CX9900 CX9640 CX9702 CX9680 ACX5720 ACX5740 Cause Controller's handle id limit on Alarm Enrollment objects has been exceeded. Resolution Click here to download this article as a PDF: Continuum Alarm Enrollment Handle ID Limits Continuum Alarm Enrollment Handle Ids Limit. (Note the information presented here applies only to non BACnet alarms) In Continuum there is a limit on the number of Alarm Enrollment objects that can be sent to the controller, the limit is 4000. Unlike the BACnet alarms, the Continuum alarm enrollments are meant to be re-usable, the system was designed for the Alarm Enrollment to be reused hence the limit, when the system is used as designed is very unlikely if not impossible to exceed the 4000 Alarm Enrollment objects limit. There have been cases where this limit has been exceeded due to site requirements that do not conform to the Continuum design, further more as of version 1.94 Continuum does not provided any feedback when the limit is exceeded, the alarm simply won’t work since the controller does not accept the alarm enrollment objects sent by the CyberStation. Guidelines to avoid exceeding the alarm enrollment handle id limit. Re-use, re-use, re-use. The Continuum system was designed for the Alarm Enrollments to be reused. If for some reason the number of alarm enrollment object is approaching the limit, do not delete Alarm Enrollment objects, if you have an alarm enrollment that is no longer needed rename it and re-purpose it instead of deleting it and creating a new one, the reason for this is that the handle ids once assigned are never re-assigned, so if you delete an alarm enrollment its handle id is lost forever. How to clean up if the limit is ever exceeded. If there are any Alarm Enrollment objects with handle ids out of range in the database they should be deleted to avoid confusion but before they are deleted all links to the enrollments have to be identified and the links removed. To find any links to alarm enrollment objects with id out of range run the following query against the ContinuumDB Select * from EventEnroll where AlarmRefLo > 562041735 If you get any results look at the uiName column, the uiName will consist of the point’s number and the AlarmEnrollment’s name separated by a period. Example: Num1.TempTooHigh Now From the Continuum explorer, find the point named ‘Num1’ that has a link to ‘TempTooHigh’ and remove the link. After all the links have been removed run the following query to find all the Alarm Enrollment objects with handle ids out of range. Select * from AlarmEnroll where ObjectIdLo > 562041735 Note the name in the uiName column, from the Continuum explorer delete the AlarmEnrollment objects.

Issue Where can I find documentation which explains what a Trend Log Comparison Report does? Environment StruxureWare Building Operation 1.3 Cause The Trend Log Comparison report provides a way for you to compare the output of the trend logs associated with a data point, such as the kilowatts for a power meter. The report provides similar reporting as the Trend Chart, however, you can export the report, schedule the report, and run the report using a Web browser and without access to WorkStation.   Resolution It is possible to read about Trend Log Comparison report in the manual Web report reference guide which you find on the Extranet under Products > StruxureWare Building Operation > Product information > StruxureWare > Building Operation 1.3 > Report server.  

Issue How to configure individual alarm viewers for users. Environment StruxureWare Building Operation Workstation 1.3.0 Cause If all users workspaces are connected to the same alarm view then if one user changes the filter the alarmview will change for all users. This is because they are all links to the same object. To have individual filters you have to create multiple alarm views and attach them to the workspaces. Resolution Create a new alarm view by In workstation Right click and select new-view Select Alarm View Type in a name, click create Attach the alarm view to a workspace. Open the control panel in Workstation, click on account management Select the workspace you want to add the alarm view to in the drop down list under Workspaces Click on content. Click on the alarms pane (or add one) and click edit. In the field "initial path" browse to the alarm view you created before. Click close

Issue After a template has been loaded in the ES, you will not see this template listed in the list of templates on any of the AS devices that reside under that ES.  Environment Binding Templates Device Templates xif files DRF Kits Enterprise Server Automation Server Cause SmartStruxure designates separate levels between the AS and ES to prevent unnecessary distribution templates that will use up the memory in the AS.  For example, it is possible to have Binding Templates that have a great use in the ES but little to no use in the AS.  For this reason, you will need to take an extra step to load the necessary templates into the AS if needed. NOTE:  There is not currently a function to delete unwanted templates out of a device in SmartStruxure.  Make sure the correct template is selected before you complete the import process. Resolution You will be required to import that all of the necessary templates into the ES and all of the AS devices that may require a use for that particular template. This can be done by simply logging directly into the AS to load the template locally.

Issue What are the limitations of Building Operation Web Services? Product Line EcoStruxure Building Operation Environment StruxureWare Building Operation Version 1.3 Cause Due to the XML response rate (XML file information send to Building Operation), it has some limitations. Resolution General Guide in the Technical Reference Guide: The limit for the whole XML response is 100 kb, which includes manually created values. The limit for a string value is 10 kb, which includes manually created values. The maximum number of values created in the Web Server interface is 200. The recommended limit for XML elements in the Web Service interface is 100 The recommended number of Web Service interfaces in an Automation Server XML elements at a polling rate of 60 seconds. is 2. Additional Information: Maximum number of Web Services in an Automation Server Also refer to Architectural Guidelines for your respective version in use.

Issue Can not print a TGML graphic from the TGML editor, get error message, "Could not print string was not recognized as valid date time." Product Line TAC Vista Environment TAC graphic editor version 5.1.5 Cause A defect is written for this problem. Resolution This problem is fixed in TGML editor 5.1.6

Issue Various items are not being displayed in the system tree or the binding tree of EcoStruxure Building Operation Workstation. When navigating through the tree, items such as folders or parameters may be missing. Product Line EcoStruxure Building Operation Environment Workstation System tree Cause If items are missing in the system tree or the binding browse tree then the filter settings are not set up correctly. Resolution If the expand icon next to a folder is missing or items are missing from the system tree, follow the steps below.     If the expand icon next to a folder is missing or items are missing from the system tree, make sure that the funnel icon is not clicked or activated (Show/Hide non-presentation objects)     If points are missing in the bindings browse window, make sure the funnel in the top left corner of that window is not clicked or activated (Hide parameters)

Issue Is JSON supported in a web service environment? Product Line EcoStruxure Building Operation Environment Web Services JSON StruxureWare Building Operation Cause Many third party application only communicate JSON. Resolution JSON is not a supported format in StruxureWare Building Operation as an HTTP response in Generic Consume. Only Simple XML Web Service and SOAP Web Service are supported. It must be an XML document. There is a tool developed on the Community to automatically convert the JSON response from a Web Service to XML, and though it is not officially supported by PSS, it has proven to be a valid work around. Refer to SBO - Web Service through a Proxy, JSON and Image conversion.

Issue Will there be any problems wiring two HID iClass RP40 readers to one reader channel?  Environment ACX57xx, AC-1 Cause Need two readers on a vehicle entrance at different heights Resolution Tested (2) HID RK40 (iClass with keypad). The RP40 uses less power but should be very similar. Not recommended to power the two readers from the same reader input unless you are sure the reader input can handle the combined peak mA rating of the two readers. ACX5720 - worked fine. The RK40s were powered with different reader channels and then just doubled up the 1-DATA, 0-CLK and LED1 terminals on the ACX with the DATA1, DATA0 and Green LED leads from the readers. AC1 - worked fine. The AC-1 terminals are small so a single piece of wire was used off the DATA/1, CLK/0, and LED terminals of the AC-1 and landed on a terminal block with DATA1, DATA0 and Green LED leads from the readers. The RK40s were powered with an external power supply.  

Issue Prior to XBuilder 5.1.1, it was not possible to change the type of an Xenta Server in an XBuilder project once it had been created.  Sometimes there is a need to move the project to a different type of Xenta Server without losing all the links and bindings within the project. Environment Xenta Server XBuilder 5.1.0 or earlier Xenta 511, 527, 555, 701, 711, 721, 731, 913 Cause In XBuilder 5.1.0 or earlier, it is not possible to edit the Xenta Server type in the network pane of the XBuilder project Resolution Upgrading to Vista/XBuilder 5.1.1 or later will allow you to easily change the device type directly from XBuilder.  Note that this must be done from an XBuilder project that is saved to the computer. If the project is in a Vista database start by opening the XBuilder project, clicking on File > Save as and then save it to the computer. Then, close XBuilder, reopen XBuilder and open up the saved copy of the XBuilder project from the PC. In the XBuilder Project menu select 'Change Target type...'.  Choose your preferred target device from the drop-down list.   If it is not possible to upgrade, the following instructions allow an XBuilder project to be transferred to a different type of Xenta Server without losing graphic bindings or bindings between objects on the System pane and the Network pane.  The one proviso is that the target Xenta Server's hardware must be able to support any network defined in the source project and have the same or better Menta and User graphic capabilities.   There are many different combinations of Server types and BMS platforms that these instructions could apply to in general.   The example given here transfers an Xenta 555 project to an Xenta 731.  The Xenta 555 has a Lonworks network and a Modbus network and is part of a Vista database.   Creating the Xenta 731 in the Vista database: Open the Vista database containing the Xenta 555 project. Right-click on the 555 and select Edit from the dropdown menu. The XBuilder project opens.  Keep this open for the following steps. In the Vista database create a new Xenta 731.  The name is not important but it should be similar but not identical to the 555 it will replace. Transferring the Lonworks network to the Xenta 731: In Vista, drag and drop the LON network from the 555 to the 731. Right-click on the 731 and select Edit from the dropdown menu. The 731 project opens in a new instance of XBuilder.  Rename the default folder in the system pane to the same name as the top level folder in the 555 project. In the 731 project right-click on the LON object in the Network pane.  Select 'Refresh network from TAC Vista'. Transferring the Modbus network to the Xenta 731: In the 555 project, right-click a Modbus device and select 'Edit Device template' When the device editor opens, select File | Save as.. Save the file in the default location with the default name. Repeat steps 2 to 3 for all Modbus devices in the network. In the 731 project recreate the Modbus network using the templates just saved.     Transferring the System objects to the Xenta 731: In the 555 project, right-click an object below the top level folder and select 'Copy'. Move focus to the 731 project, right-click on the top level folder and select 'Paste'. Repeat steps 1 and 2 for each object and folder below the top level in the 555 project.  Selecting a folder also selects all the objects and folders beneath it.  Although it is possible to copy the top level folder in the 555 project, it is not possible to paste it into the 731 project. Graphics bindings are retained and the reference paths are automatically updated with the new network tree i.e. 'TAC_Xenta_555' is replaced with 'TAC_Xenta_731'. Some object bindings will be broken e.g. Time objects.  These must be rebound manually. When all objects have been copied across and rebound if necessary, close the 555 project. Deleting the Xenta 555 and downloading the project to the Xenta 731: In the Vista database, delete the Xenta 555. Generate the 731 project.  There will be a warning message offering to copy the original TGML files to the new default location.  Select 'Yes'. The 731 project should now generate without errors. Download the project to the Xenta 731.   If the 555 only contains a Modbus network, a similar methodology will also work with standalone 555 and 731 projects.  

Issue In WorkPlace Commissioning Tool, the following error message appears when browsing a BACnet/IP network: "A critical error occurred in the communication server rtmonitor.exe. Please shutdown this application and the communication server then try again." Product Line TAC IA Series Environment Windows 7 computer WorkPlace Tech Tool software version 5.7 or later Cause The WinPcap driver, used in WorkPlace Tech BACnet communications was configured to start on demand and the WPT module that is attempting to start WinPcap does not have the necessary Windows security rights.  Resolution NOTE 1:  Before using this procedure, please verify that the issue noted in WorkPlace Commissioning Tool UDP Port: "A critical error occurred in the communication server rtmonitor.exe" has been corrected, if present, and did not solve the problem. NOTE 2: If the computer is running Windows 7-64 bit, replace the following references to "Program Files" with "Program Files (x86)". To correct this issue, perform the following steps. Open Windows Explorer, i.e., "My Computer" or "Computer" from the Windows Start menu or computer desktop. Open the folder "C:\Program Files\WorkPlace Tech" For each of the following program files listed here, in turn: RTMonitor.exe, WPCT.exe, WPFB.exe and WPTech.exe Right click on the program name, Select Properties from the pop-up menu, Select the "Compatibility" tab. In the Compatibility display, click the button [Change settings for all users]. Locate "Privilege Level" section of the displayed window and check the box "Run this program as an administrator". (See snapshot below) Click the [OK] button to save the settings for all users. The window will close. You will see that the Privilege Level option is no longer selectable. Click the [OK] button to save the compatibility settings.   After setting the privilege option for each of the four programs in the Workplace Tech folder, repeat the same setting change for the Microsoft Visio program itself, VISIO.EXE. Depending on the version you are using, it will be located in the C:\Program Files\Microsoft Office\OfficeXX folder where xx is 14, i.e., Office14, for Visio 2010, 12, i.e., Office12, for Visio 2007 or 11, i.e., Office11, for Visio 2003. After setting these options, the computer should be shut down and restarted before using the WorkPlace Tech Tool software.  

Issue It has come to our attention that people are using Backup and Restore to duplicate Automation Server databases, this is not supported and should not be used as it results in various issues.  Some of the known issues at this time are listed below: When attempting to update Server IP addresses using the advanced feature "Repair server communication"; one or more Automation Servers are listed as Offline even though they are shown as Online within the System Tree. (Click on image for larger view)   When performing a backup / restore from the Enterprise Server the Automation Server(s) are not listed as part of the Child view.    Right-clicking on the Automation Server does not give all the options available and most are grayed out. Product Line EcoStruxure Building Operation Environment Building Operation Automation Server 1.2, 1.3, 1.4 and 1.5 Cause This situation arises because each Automation Server receives a unique identifier, global unique identifier (GUID), when using the backup and restore function this GUID is retained.  Therefore when restored to other Automation Servers these will retain the same identifier.  The only course of action available within this environment is to detach the Automation Server from the Enterprise Server and create a new database from scratch. The correct duplication process across Automation Servers is to use the export and import feature or copy and paste (drag and drop) across Automation Servers.   Resolution StruxureWare Building Operation 1.6 and above update:   You can now use the Restore function to re-use the configuration data from a backup set in a new standalone Automation Server. Rather than manually configuring your preferred Automation Server configuration, you can save time and configure the standalone Automation Server from a backup set. Online help topic: Duplicating an Automation Server Using Restore Backup and Restore feature should NOT be used to duplicate multiple Automation Server's databases it should only be backed up and restored to the same server.  Instead the Export / Import and copy and past features are designed for this function.   A warning note in the Technical Reference and IT Reference guides (versions 1.2, 1.3, & 1.4) has been added warning the users not to use the backup and restore function for duplication.  See the online StruxureWare WebHelp for this current Important Note (login required): Backup and Restore Overview However if you have this situation then it may be possible to recover some or most of the database, please contact Product Support and reference this article number so that this issue can be confirmed.  

Issue What is the latest specification For a Continuum PC Product Line Andover Continuum Environment Cyberstation SQL Server Cause Computer specification required. Resolution The PC specifications for a version does not change from the time of release, so there is no "Latest Specification" as such. For all versions the hardware requirements are defined in the installation guide (Installation.PDF) on the software CD, or in the downloaded zip file from The Exchange Download Center for the version to be used. This document will contain the minimum and recommended specification required for that Cyberstation version on a typical site, if any other software is to be installed on the computer or the computer is to be heavily loaded; the requirements should be increased accordingly. The same RAM and Processor requirements will also apply to the SQL Server on a typical LAN system. You also need to check the Software and Firmware compatibility matrix for older versions of the traditional product lines for details on the compatible operating system requirements for the version to be used. For a V2.01 system the recommended hardware for servers and workstations are: Intel 8 Cores, 2 GHz or better 8Gb RAM 30Gb Available HDD space (NTFS Partition) CD ROM Drive Video resolution: 1024 x 768 pixels Parallel or USB port For larger systems and where there will be a lot of Extended logging or Alarming, the Hard drive, RAM size and processor speed should be increased.  

Issue Menta module names disappear when exporting a Xenta from Vista version 5.1.8 and importing it to Vista version 5.1.7  Environment TAC Vista 5.1.7 and 5.1.8 Cause Changes is made in the export/import function in TAC Vista 5.1.8 which will cause problems to import a export file from TAC Vista 5.1.8  in to TAC Vista 5.1.7. Resolution To be sure that the export/import function should work only export and import between Vista systems of the same version. 

Issue Diagnosis of a full Vista database shows that trend log storage size the culprit. Environment Vista trend logs SQL database Cause Excessive trend logging can quickly fill a database. Resolution This search will show both Xenta trend logs declared in Workstation/Menta and Vista Server logs. Search for ‘Type of devices or objects: Logical objects – Files – Trend Logs – Trend Log Vista’ Set Property Value – Status – Equal to ‘On’ Deselect the ‘interrupt if more than 1000 results’ if large Db with need for many logs. Once search populates right click on any result, Additional Property Value – Log space. This will add a column showing this setting in seconds.  Sort column to identify any trends that are set to store more than the desired amount of values and could be causing issues.  Note: 604800 sec = 1 week

Issue Extended Trend Logs Product Line EcoStruxure Building Operation Environment Building Operation Enterprise Server Building Operation Automation Server Premium (AS-P) Building Operation Automation Server Bundled (AS-B) Cause When configuring extended logging in the BACnet application folder, these objects are not available when performing a device discovery from the AS or ES. Prepare one AS with a BACnet point Create a trend log on the BACnet point Create an Extended log for that BACnet trend log From a second AS, the BACnet objects are available after a Device Discovery except for the Extended log object. StruxureWare Building Operation online help for “Configuring Extended Logging for a BACnet Trend Log” states:    ***Key Concept: Extended trend logs are not BACnet objects. These are StruxureWare Building Operation exclusive. The term "BACnet Extended Trend Log" does not exist and is a misnomer. Resolution The main reason is that extended logs are not defined in the BACnet standard; they are proprietary to EcoStruxure.  Everything that is proprietary to EcoStruxure Building Operation is not exposed to BACnet including graphics, script & function block programs and central IO points are not directly exposed, but have to be bound to BACnet I/O objects. The extended log serves the purpose of expanding a log on a larger capacity server.  A trend log on an AS would be more appropriate to extend on an ES. If you have a trend log in an external BACnet device (like a b3 or a 3rd party device/system) then you would want an extended log in the AS, to collect from that device (and then maybe a larger extended trend on a parent ES). If there is a local BACnet trend log in an AS (in the BACnet interface application folder) that is required to be larger, consider increasing the buffer size property of the one log that is needed (the default size of 10 may be too small, and increasing to 1000 up to 5000 (extended log size) may be an option). That would be most interoperable with other (3rd party) BACnet clients that need access to the trend log data.

Issue Clarification on how to wire Form A and Form K Triac outputs on i285-V / b3865-V controllers. Environment i2865-V b3865-V i2866-V b3866-V i2865-V-S b3865-V-S i2866-V-S b3866-V-S Cause Had issues in the past with blown Triac outputs due to wiring, need to confirm how they are properly wired for Form A and Form K Triac outputs. Resolution As per 30-3001-810 i2 b3 865-866 Controller Installation Instructions (see page 5), you can configure your Triac so they switch the 24VAC (hot) or the GND (ground), but all Triac outputs must be configured the same. The difference between the Form A and the Form K is that the Form A is two digital outputs using a single triac each while the Form K is a single tristate output using both physical triacs for the one (logical) output. The Form A Triac outputs can be configured as either a hot or ground switch but the Form K must be configured as a ground switch (TRIAC REF tied to GND, Load to 24VAC).

Issue At times the firmware and software on the Roam IO2 requires updating and instructions are needed Product Line Andover Continuum, EcoStruxure Building Operation Environment Roam IO2 Windows XP Windows 7 Windows Server 2003 Windows Server 2008 Windows Mobile Cause Instructions for upgrading the software and firmware are provided in the User's guide, but this article places them in an easy to find location Resolution The full instructions for installing and using the RoamIO2 software and hardware are in the User Guides: BACnet Service Tool User Guide + Software Infinet Service Tool User Guide + Software NOTE: The RoamIO2Appl2.000002.upd firmware firmware can only be updated from the BACnet service tool, the Infinet service tool does not have the update OS option.     Please see instructions for installing firmware and hardware for the RoamIO2 for an overview.