Building Automation Knowledge Base

Issue Unable to find the latest firmware for ADv3 in EcoXpert Extranet Product Line EcoStruxure Building Operation Environment Advanced Display v3 (ADv3) Cause The firmware is not publicly posted since the process to load the firmware should not be attempted without guidance from Product Support. Resolution All customers must to open a support case to receive fixes or enhancements.

Issue A new Automation Server won't load in Device Administrator versions earlier than EBO 2022. A "Failed to process USB connection event for DevicePath:\\?" error is shown when adding the device.   Product Line EcoStruxure Building Operation Environment Building Operation Automation Server AS-P with Secure Boot Building Operation Automation Server AS-B Scalable Cause Secure Boot/Scalable Automation Server hardware is not supported in EBO versions prior to EBO 2022. Resolution It is not possible to install EBO versions prior to EBO 2022 in Secure Boot/Scalable Automation Server hardware. Verify the Automation Server part number to ensure it is a non-scalable/non-secure boot version. Refer to the Part Number and Hardware and Software Matrix for a list of parts numbers and their associated EBO version compatibility.

Issue Initialization errors when starting I/NET Seven 2.42 or higher Error: "You must install an instance of SQL 2008R2 (64bit) before completing the INET install" Product Line TAC INET Environment I/NET Seven 2.42 Windows Server 2008 64-bit Windows 7 64-bit SQL 2008 64-bit Windows 8 Cause I/NET 64-bit requires specific installation process in order to function on a 64-bit PC Resolution Installing SQL Download SQL2008 R2 Express 64 bit (SQLEXPR_x64_ENU.exe) from this location: http://www.microsoft.com/en-us/download/details.aspx?id=30438 Run SQLEXPR_x64_ENU.exe In the left hand section, select Installation In the Right and section, select New SQL Server stand-alone installation of add features to an existing installation. At the "Setup Support Rules" screen select OK At the "Product Key" screen, select Next At the "License Terms" screen, check accept and select "Next" At the "Setup Support Files" screen, select Install At the "Setup Support Rules" screen, select Next At the "Feature Selection" screen select: Database Engine Services, SQL Server Replication, Management Tools - Basic (If Present) and SQL Client Connectivity SDK. Leave the Shared feature directory as default. At the "Instance Configuration" screen, select the Default instance option, accept the default Instance ID, accept the Instance root directory default settings and select next. At the "Disk Space Requirements" screen, select Next At the "Server Configuration" screen, under SQL Server Database Engine set the Account name to NT AUTHORITY/SYSTEM, leave the password field blanks, and set the startup type to automatic. Under SQL Server Browser Service, set the Startup Type to Automatic At the Database Engine Configuration screen, set the Authentication Mode to "Mixed Mode", Define a strong password (example: @sql2008), in the Specify SQL Server administrators section click "Add Current User". Select Next. At the "Error and Usage Reporting" screen, select Next At the "Installation Rules" screen, select Next At the "Ready to Install" screen, select Install At the Installation Progress screen, when the setup process is complete, select Next At the "Complete" screen, select Close. SQL Configuration: In the Windows Start Menu, launch the SQL Server Configuration Manager In the Left hand section of the window, highlight SQL Server Services Verify that SQL Server Browser and SQL Server are Running In the left hand section of the window, expand SQL Server Network Configuration and highlight Protocols for MSSQLSERVER Enable Named pipes and TCP/IP Close the SQL Server Configuration Manager Restart the PC Installing SQL Server 2005 Backward Compatibility On the I/NET 2.42 or higher installation CD, look in Support\SQLBCM_64Bit and launch the SQLServer2005_BC_x64.msi file Follow all the prompts on each screen and accept all defaults. Install I/NET Seven 2.42 or higher Install I/NET Seven 2.42 or higher using the installation CD Follow prompts and use defaults When prompted for the SQL password, select "Windows Authentication" Restart the PC Open I/NET Configuration through the start menu. Modify the default Config profile or create a new profile. Close I/NET Configuration Start I/NET NOTE: If error occurs during SQL installation stating invoke or begin invoke failed, follow instructions at this link: http://support.microsoft.com/kb/975055 UPDATE: SQL2008 SP1 prevents the invoke failed error. It can be installed with the same instructions as above. Download it at this link: http://www.microsoft.com/en-us/download/details.aspx?id=25052

Issue Can the EasyLogic range of controllers & RP-IO Modules work under Building Operation 3.2 as BACnet MS/TP third-party devices  Product Line EcoStruxure Building Operation Environment EasyLogic Controllers, EasyLogic RP-V, EasyLogic RP-C, EasyLogic MP-C EasyLogic RP-IO SpaceLogic Advanced, Pro, and Pro Plus Controllers that support native BACnet MS/TP (via a SpaceLogic RS-485 Adapters.   Standalone BACnet field controller Cause The documentation states that EasyLogic Controllers can be used as a Native BACnet MS/TP device. These devices must be configured using their respective supported Building Operation versions, such as Building Operation 2022 and above. However, there are no guidelines on whether they can be used as a third-party BACnet device, particularly in earlier versions such as Building Operation 3.2.    Resolution EasyLogic controllers can be used as BACnet MS/TP third-party devices in Building Operation 3.2 since the EasyLogic range of RP and MP controllers, and RP-IO I/O modules, natively communicate using the BACnet MS/TP protocol.  This same concept applies when using the devices as true 3rd-party devices (e.g., with Continuum and I/A systems) when older controllers fail, and these EasyLogic controllers are used as temporary replacements before a complete transition.   What MUST be understood before taking this approach is that there is no automatic conversion when migrating the site (and devices) to later Building Operation versions that support these devices natively. After the upgrade, the controller must be deleted from the database and hosted as a native EBO controller.   During this process, some programming may be lost. This risk may be mitigated by creating Custom Types for the application once engineered in Building Operation 2022 (or higher) to future-proof the site for upgrades.  Using the latest firmware for the EasyLogic range of devices is also recommended.     Furthermore, the SpaceLogic Controller Range that supports native BACnet MS/TP (via an RS-485 Adapters) can be configured in the same fashion as described for the EasyLogic range.   Refer to Hardware Overview for further details on each product line. 

Issue How to install a language pack on Enterprise Server (ES) Webstation. Environment StruxureWare Building Operations Enterprise Server Webstation 1.1.0.362 Cause This functionality needs to be activated via StruxureWare Building Operation Workstation. In the Automation server (AS) webstation an "Add Language" menu item is used but this needs to be activated in ES webstation. AS Add or Remove language settings. ES (default) Add or Remove language settings. Settings for the default administrator group that don't allow a language pack to be added in ES webstation Resolution Create a new StruxureWare Building Operation User group 1. In ES workstation go to the Control Panel and select User Accounts -> Account Management. 2. Select the appropriate domain and then select User Account Groups -> Add. 3. The settings can then either be set via the Create Object wizard or can be done later. Choose the preferred method and add the users/Groups that are to be granted authority to add language packs. Set the policies for the new user group 1. Go to .../Domains/Local/Groups/Your new group in the menu tree and select the tab Policies. 2. Select the check box AS web configuration - May access web user interface. 3. Save the changes. Add the language pack in webstation 1. Go to ES webstation and log in. 2. Click on the settings menu and then select Add or Remove Language. 3. Click on add and browse in the language pack zip-file. Click on OK. Check that the installation was successful 1. Click on Settings -> Change language. 2. The newly installed Language pack should appear in the drop-down menu. 3. Select the language and click on OK. The language should change straight away.     

Issue DHCP server is required to assign addressing to IP devices Product Line TAC IA Series, EcoStruxure Building Operation Environment I/A Series Jace 8000 I/A Series ScheniderMPx Modules Building Operation Multi-purpose VAV  Building Operation Multi-purpose Controller Building Operation Room Controller (RPC) 24 V Building Operation IP-IO Cause When working with the SchneiderMPx modules for engineering Spacelogic devices, the Jace can be used as a DHCP server for the field devices. Resolution This video discusses how to; - Configure the second IP network port for DHCP server use - Add an additional IP Port to the Jace station  

Issue After setting up a REST gateway in SmartConnector, how can it be tested to see that it is working using the built in test client called Swagger? Product Line EcoStruxure Building Operation Environment Building Operation Enterprise Server Building Operation Enterprise Central SmartConnector   Cause Swagger is a built in test REST client which can be used to read and set values in EBO. So it can be used instead of a "real" REST client to test the REST gateway in the SmartConnector and test that the connection between SmartConnector and EBO is working. Resolution The objective in this video is to set up a REST gateway in SC and show how we can test that the gateway is working using the built in test REST client called Swagger. Please see video.

  Issue Cannot communicate to an ADV3 connected to the USB port of an AS-P or AS-B. The error message “Website not available” is displayed. Product Line EcoStruxure Building Operation Environment EcoStruxure Building Operation Advanced Display v3 (AD v3) Cause The AS-P or AS-B’s USB port uses a IP network connection to the ADV3 that defaults to 192.168.42.116. If the AS-P’s primary port is in the same range, for example the main LAN network range is 192.168.42.* there is a conflict with the USB IP network. Resolution Change the sites main LAN, which the AS-P or AS-B primary port connects too, to another network range.

Issue What is the difference between a Numeric Input, Numeric Output and Numeric Public within a script program. Is using a Numeric Public a less efficient choice (as opposed to using a Numeric Input or Numeric Output) that will generate negative overhead in the AS? Product Line EcoStruxure Building Operation Environment Building Operation Automation Server (AS, AS-P or AS-B) Building Operation Workstation b3 and Infinet controllers Cause Want to determine best practices when choosing numeric types during script programming. Resolution Numeric Input is a read only numeric (from the point of view of the script program) that accepts a binding. Numeric Output is a write only numeric (from the point of view of the script program) that accepts a binding. Numeric Public is both read and write (from the point of view of the script program). Numeric Public also accepts a binding. (A Numeric Public can be bound to both a Graphic and a Value Object to allow overriding of values from a Graphic. See SBO Script Public.zip for an example) When choosing the numeric type in a script program there is no overhead cost difference between using one of these numeric types vs the others. Also check out the Script Programming - Writing the Script Program Quick-Help video on the Exchange. NOTE b3 and Infinet Controller scripts do not support "Numeric Public", but "Numeric Output", in these controller scripts, can be used in a similar way to "Numeric Public" The Bound value is read by the script as well as being written to.

Issue Valve Flange Tables Product Line Field Devices Environment Valves Flanged Gaskets Bolt holes PN rating PCD Cause What flanged tables are used with what valves? Resolution The PN of the valve and the valve size will indicate the diameter, PCD (Pitch Circle Diameter), number of bolt hole/size and bolt size and therefore size of flange and gasket. Download the flange tables for BS EN 1092 (metric), ANSI  (ASA) and BS10 or here for an alternative flange table document.

Warning Electrostatic Discharge Required: Always discharge static electricity from your person by touching metal prior to handling any hardware. Failure to do so may result in damage to devices. 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 Currently, a procedure exists to do conversion of i2 to b3 and vice versa using Continuum Cyberstation and NetControllers.   However, it is much simpler to do the conversion using the RoamIO and the Infinet/BACnet Service Tools. Product Line Andover Continuum, EcoStruxure Building Operation Environment Continuum i2 Controllers (except -V) Continuum b3 Controller (except -V) Cause This article describes an alternate and simplified conversion method to the original procedure published to convert i2 to b3. Before using this procedure, read the Conversion of Continuum devices from i2 to b3 and vice-versa in the field Knowledge Base article in its entirety for important information about converting i2/b3 controllers in the field.  Resolution Before starting the procedure, you need the following items: The device to be converted. The serial number of the device to be converted. A RoamIO2 configured to communicate with your PC via Bluetooth and the Infinet and BACnet Service Tools A special, firmware application upgrade file for the appropriate device model as provided by Product Support A bootloader file for the appropriate device model, provided by Product Support To convert i2 field devices into b3 BACnet using RoamIO2 Contact Product Support and request the conversion files for the specific model(s) you wish to convert. You will be provided with an application file (e.g. i2920toB3920B4.500077.upd) and a boot loader file (e.g. B3920BootB4.500077.upd) for each model you are converting. Connect the RoamIO2 directly to the i2 device (make sure device is disconnected from field bus) Launch the InfinetServiceToolPC.exe (attached) and click on the connect icon Once the device shows up on the tree, right click on it then select 'Uprev firmware...' Send the conversion application file provided by Product Support Once the uprev operation is complete, click the connect icon to disconnect the Infinet Service Tool from the i2 device then close the InfinetServiceTool app. Cycle power to the RoamIO2 then start the BACnet Service Tool In the BACnet Service Tool, de-select View by networks, then click the connect icon, the conversion from i2 to a b3 causes the device to default to baud 38400 and an invalid BACnet master MAC id, so upon connection the following error will be shown... Click 'Yes' to continue From the 'Tools' menu select 'Set b3 baud rate' and set it to Baud38400  From the 'Tools' menu select 'Set offline b3 MAC id' and enter the serial number of the device and a valid MAC id then click on 'Apply' If the baud and MAC id have been set successfully, the device will automatically pop up in the tree but it will only be partially online, to bring the device fully online, click the red disconnect icon on the BACnet Service Tool to disconnect from the device, wait about 30 seconds then  click the now green connect icon to reconnect the BACnet Service Tool to the device Right click on the device then select 'Update OS', send it the appropriate boot loader file provided by Product Support Once the uprev of the boot loader has completed, select the device and click on 'Cold start device' After the device re-start, click on the device in the tree and select 'Switch view', confirm the firmware and boot loader versions are correct. (you may need to do a refresh from the 'Tools' menu)

Issue Site experiencing comm issues on the Infinet or MSTP bus. Controller error logs show many 1465 (Cyclical Redundancy Check) errors. Product Line Andover Continuum Environment Infinet MSTP b3 i2 Controller error log Cause CRC errors are check sum errors. Before a packet is sent, the sending controller calculates a checksum based on the packets contents. This checksum is then appended to the packet. When the packet is delivered, the receiving controller calculates it's own checksum based on the packets contents. If the check sums do not equal, this indicates that somewhere in the delivery process the packet has been altered, usually due to bad cable or connections, controller grounding, or a bad controller transceiver. For additional information on troubleshooting the infinet or mstp bus, see Infinet and MSTP bus troubleshooting. Resolution CRC errors usually indicate poor signal integrity on the physical bus. Infiltration of "noise" on the comm cable due to the presence of high voltage conductors, radio transmissions, etc. In some cases a failed transceiver may be involved but this is generally not the case. Poor controller grounding can also contribute to this issue. Generally CRC errors call for using a scope to assess the signal integrity on a bus.

Issue Tips for Configuring HID OSDP Reader LED Colors Product Line EcoStruxure Security Expert Environment EcoStruxure Security Expert OSDP Reader Cause Additional tips for configuring OSDP Reader LED Colors Resolution The Configuring LED Colors section of AN-254 Configuring OSDP Readers in Security Expert  details the basic steps for LED configuration. This article details some additional areas of the HID reader setup and Security Expert configuration that may be useful when configuring the LED colors.   Note: The steps in this article are specific to an HID Signo RP10 Reader BLE and may not apply to other HID reader models or other brands of OSDP readers.   Upgrade the Reader firmware to the latest version. Earlier versions of the reader firmware would not correctly allow LED control. The Bluetooth option allows the configuration of the reader using the HID Reader Manager App. For detailed information see HID Reader Manager App Information Note: To use the HID Reader Manager App to configure a reader, the Security Technician or Security Installer needs to create and register an account with HID. The Reader Manager Administrator for your organization or company needs to enroll this new account using the Reader Manager Service and issue an invitation code and key authorization for this and other readers. The Security Technician can then verify the key authorization has been received in the HID Reader Manager app. Detailed instructions for all of this are included in the HID Reader Manager App Information URL listed above.   HID Reader Manager App Firmware snapshots       In the HID Reader Manager App, change the Reader Options for LED color to "Host Controlled" in 2 places. The reader must be controlled by the Security Expert controller. Credential Reader AV LED Idle Color Ensure that the firmware for the following hardware is upgraded to these versions or greater in order for LED Color Output to work. Security Expert 4.3.308.46 SP-C 2.08.1234 MRDM2 1.2.590 In Security Expert the Outputs to control the LEDs need to be manually created. Programming> Outputs> Add A pop-up asking to Invert Output will display, select 'No' when prompted Output 3 (GreenLED Port 1) Output 4 (Red LED Port 1) Output 6 (Green LED Port 2) Output 7 (Red LED Port 2)   Name the Outputs whatever is appropriate Example:  GreenLEDPortON RedLEDPortOff LED Colors The default LEDs are Blue when Idle and Green when active. As an example, the LED colors will be changed to Red when Idle and Green when Active. Color Options:   Set the colors for both Red(idle) and Green(active) in the Security Expert Output Command Window for the newly created outputs RedLEDPortOff   GreenLEDPortOn Update the modules and wait for about 15 seconds before activating the output to test. Just saving the updated command setting doesn't work, the module must be updated.   Activate the GreenLEDPort1 - the color should change to what the output was set to in the command. In this case, green. Deactivate goes back to Off (idle) Red. GreenLEDPort1 = On State RedLEDPort1 = Off State   Note: The Off state if left at the default of Blue can't be used with the On state of custom(non-default). Both Outputs must be specified in the command window for the colors to work together.   Example: If the OFF state is left at the default of blue and the color of the ON state is set in the command window and Activated, the LED color will change to what it is set to(green), but when deactivating the Off(idle) output it will not turn blue.

Issue How do points map from a i2 controller and the xP expansion modules to Infinity SX8000? Environment Using Continuum i2 controllers and xP modules on SX8000 Infinity systems. Cause The I/O channels on expansion modules are different from Infinity to Continuum. Resolution You can add an i2 controller to your Infinet networks on Infinity and it will co-exist with the other Infinity controllers. The controller will be seen as a equivalent infinity controller i.e. a i2850 will be seen as a TCX850. Also you will not be able to use any of the additional features that a i2 controller has like the flash memory or the smart sensor connection. For Expansion modules you could however use the xP modules (not including the xP display) the attached spreadsheet that shows how the i2 controllers I/O channels will be seen by the Infinity Controller. Download the spreadsheet here.  

Issue Enterprise Network Server station failed. Attempts to start the station resulted in the following error messages. ERROR [15:32:36 04-Jul-12 SGT][sys] Cannot load station java.io.EOFException    at javax.baja.xml.XParser.read(XParser.java:753)    at javax.baja.xml.XParser.parseText(XParser.java:621)    at javax.baja.xml.XParser.next(XParser.java:268)    at javax.baja.io.BogDecoder.decodeDocument(BogDecoder.java:164)    at javax.baja.io.BogDecoder.decodeDocument(BogDecoder.java:152)    at com.tridium.sys.station.Station.loadStation(Station.java:128)    at com.tridium.sys.station.Station.bootStation(Station.java:78)    at com.tridium.sys.station.Station.main(Station.java:978)    at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)    at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)    at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)    at java.lang.reflect.Method.invoke(Unknown Source)    at com.tridium.sys.Nre.runClass(Nre.java:224)    at com.tridium.sys.Nre.main(Nre.java:149) App Failed   Environment I/A Series G3 Cause The station's config.bog appears to be corrupted. The reason for this is unknown at this time. Resolution Restore the station database with the latest copy of a known good backup.

Issue The System License Information screen has a lot of useful data on the status of licenses in the EBO system. Is there a way to export or screenshot the entire System License Information page? Product Line EcoStruxure Building Operation Environment Building Operation Enterprise Central Building Operation Enterprise Server Building Operation Automation Server Cause Unable to save or export the System License Information screen Resolution There is no option to print or export the Control Panel System license Information screen. It is possible to get a reasonably close facsimile by viewing the LicenseStatus item in System>LicenseManager and adding columns for Required Licenses, Checked Out Licenses, Installed Licenses, Available Licenses, and License Violation.   This can then be Exported in XLSX format for future reference or if required by Product Support  

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 Seeing multiple losses of functionality starting to occur, such as controllers going offline, browsing with the client being slow, reports failing to run and events not being logged. Product Line EcoStruxure Security Expert Environment Security Expert SQL Server Cause In SQL Server the SecurityExpertEvents database has a very large LOG file ( hundreds of gigabytes) resulting in degraded performance in SQL and Security Expert.   The Recovery model of the SecurityExpertEvents database is set to FULL and the database has not been maintained. When using the Full recovery model, regular backups of the transaction log should be performed to prevent the transaction log file size from growing out of proportion to the database size. Recovery model full New user databases are created with the same recovery model as the model database. The default recovery model for the model database depends on the edition of SQL Server you have installed. Editions targeted at test and development environments (SQL Server Express) set the recovery model of the model database to SIMPLE. Other editions set the recovery model of the model database to FULL. Resolution Reduce the size of the log file and prevent it from getting too large again by changing the recovery model of the database from FULL to SIMPLE. The databases are then shrunk to free up drive space.   Refer to the following steps: Take a backup of both the SecurityExpert and SecurityExpertEvents databases and store them in a safe location Change the Recovery Model of the SecurityExpertEvents database from Full to Simple in SQL Server Management Studio. To do this, right-click on the SecurityExpertEvents database and go to its properties. Select 'Options'. Change the Recovery Model setting to Simple. Recovery model simple Right-click on the SecurityExpertEvents database and select Tasks > Shrink > Files Shrink files In the Shrink File - SecurityExpertEvents window, change the File type to Log. Shrink log file Click OK Repeat steps 2-5 for the SecurityExpert database   It is recommended that regular scheduled backups be configured when using the SIMPLE recovery model. In SIMPLE recovery mode, changes since the most recent backup are unprotected.

Issue There is mention of the Modbus integration service in Security Expert manuals and release notes but no application note explaining what features are supported or how to configure the integration. Product Line EcoStruxure Security Expert Environment Security Expert controller Modbus integration Cause The Modbus integration in Security Expert is currently not supported by the Offer. The current Modbus integration has known issues and is being rewritten. There is no further information on when this will be completed or what devices this will be supported in. Resolution If the Modbus integration is required, the local solution category management team should be contacted to have this requirement properly prioritized and to get updates on any new Modbus integration work.

  Issue Site upgraded SmartX IP Controller from 2.00.03.1203 to  v3.02.03.02109. When the upgrade was completed, they attached the SmartX room sensor to the controller.  The sensor appeared to update but the screen display was distorted.             Product Line EcoStruxure Building Operation Environment • Building Operation Multi-purpose VAV • Building Operation SmartX Living Space Sensor • Building Operation Workstation   Cause With a blank database, an MP-V with firmware V2.00.03.1203, when the sensor is connected the screen is distorted, but  after upgrading the MP- V to firmware V3.02.03.02103 , the screen display shows up with no issues Something is breaking for the site when attempting to go from 2.0.3.1203 to 3.2.3.02103 Resolution Upgrade the firmware to a higher version (ex 4.x). After the MP-V is upgraded, the sensor will upgrade automatically which takes about 10 to 15 minutes and the status will be operational. The screen will then display properly.

Issue How to configure search object to display SpaceLogic controllers IP settings "Changes pending" in the search's list view Product Line EcoStruxure Building Operation Environment Space Logic IP controllers  Cause Confusion when attempting to find the appropriate type to include in the search  Resolution The IP settings "Changes pending" property is not a property of the device but rather a property of the IP Network Port as seen in the screen shot below