Building Automation Knowledge Base

Issue Is the Continuum Cyberstation a B-OWS (BACnet Operator Workstation)? Product Line Andover Continuum Environment Continuum Cyberstation BACnet Cause Can't find reference to Continuum Cyberstation being defined as a B-OWS. Resolution The Continuum Cyberstation is a B-OWS and complies with ANSI/ASHRAE standard 135-2004.  However, the Continuum Cyberstation has not been BTL tested, please see the Schneider Electric BTL Listing of Tested Products.    The following selection is taken from the Andover Continuum Family of User Interfaces document describing Continuum's Cyberstation capabilities. Native BACnet B-OWS CyberStation communicates with the BACnet devices using BACnet/IP in strict accordance with ANSI/ASHRAE standard 135-2004 and is designed to function as a BACnet Operator Workstation (B-OWS) and BACnet Broadcast Management Device (BBMD). The CyberStation can communicate to all Andover Continuum BACnet Devices as well as any third party BACnet Device on the BACnet network.

Issue Unable to establish communication between the enterprise and automation servers through the TCP Port 4444. Values are not being passed between the enterprise to the automation servers or between automation server to automation server. Product Line EcoStruxure Building Operation Environment Building Operation Enterprise Server Building Operation Automation Server Premium Building Operation Workstation Cause Windows Firewall is not allowing inbound or outbound information from passing through the TCP port 4444. Resolution First download and run TCP View. With TCP View running, sort the list by the Local Port and find all devices that are talking on port 4444. If the automation servers are in a state of LISTENING then rules must be created to allow communication. Copy the file path of SE.EnterpriseServer.exe in order to create the rules. This can be found by right clicking on one of the SE.EnterpriseServer.exe process > Process Properties... (C:\Program Files\Schneider Electric\StruxureWare 1.2\Enterprise Server\bin\SE.EnterpriseServer.exe) If the automation servers are in the state of ESTABLISHED, then take a look at Binding between ES and AS or two AS shows Unresolved and "Communication Failed" Alarm occurs when Adding an AS. Source: /Server 1/Servers/ASL/System/Server Communications/Models/2deef04c-05d1-41ae-9c3f-f84a9f7e0b41 for more troubleshooting help.   Change Windows Firewall Settings to Allow Programs Go to Start > Control Panel. Click on Windows Firewall. Click on "Allow a program or feature through Windows Firewall" on the left hand side of the window. Find "StruxureWare Building Operation" in the list of programs and make sure Home/Work and Public networks are selected.  Note: If you do not have permission rights to make changes in this area of Windows, move on to the next section where you can set up inbound and outbound firewall rules.   Creating Inbound and Outbound Windows Firewall Rules Go to Start > Control Panel.  Click on Windows Firewall. Click "Advanced settings" on the left side of the window. Select Inbound Rules on the left side of the window and then click New Rule... on the right side of the window. On the first screen of the New Rule Wizard, choose Program. Click Next. In "This program path:" either browse to SE.EnterpriseServer.exe or paste the file path that was copied earlier from the TCP View into the box. Click Next. Select the option to "Allow the connection". Click Next. Leave Domain, Private, and Public checked unless otherwise desired. Click Next. Name the rule StruxureWare. Click Finish. Select Outbound Rules on the left side of the window and then click New Rule... on the right side of the window. Follow steps 5 through 9 to create the Outbound Rule. Note that the SBO Firewall Config tool on the community can be used to automatically create the required firewall rules.

Issue A BACnet devices can contain 1000's of objects, performing an upload on these devices can take upwards of 30 minutes to complete when only a few objects are required for integration. Product Line EcoStruxure Building Operation Environment Building Operation Enterprise Server Building Operation Automation Server Premium Cause Uploading all objects in a controller can take a lot of time and is often not required. Resolution From version 2.0 Open the device discovery view / BACnet - then Discover All. Once the Device is hosted, click on the device (in the Device Discovery window) and open the right-hand Object pane. Drag/drop the required Object into the hosted BACnet device Application folder. Alternatively, the Hardware folder can be used, this was the best method for some earlier versions Perform the BACnet discovery, then view the Hardware folder at /ServerName/System/Hardware/BACnet devices. Navigate to the required Device/Object, then Drag and drop the Device and Object as above.

Issue When logging in to an AS or ES, WorkStation freezes or it takes a very long time (>30 minutes) before the login process finishes. Building Operation WorkStation hangs on "Reading data..." when trying to login to an AS or ES Product Line EcoStruxure Building Operation Environment Building Operation Enterprise Server Building Operation Automation Server Premium Building Operation Automation Server Bundled Building Operation WorkStation Cause The problem is related to a delay when validating the license details. It only seems to happen when running a mixed EBO/SBO 1.9.3 system and after having EBO license administrator 2.0.1 previously installed. Resolution Run the SBO License Server Reset tool and perform Reset - Simple Log in to WorkStation, and if the hang or freezing is still present, then follow the next set of instructions. Run Diagnostics in the License Administrator and take note of all the ACT (Activation) and Entitlement IDs Return all the licenses Close all WorkStations and stop all SBO/EBO processes (whichever may be running) Uninstall all License Administrator and License Server Run the SBO License Server Reset tool and perform a Reset - Complete (you will get an output of the commands and result) Install the latest released version of License Administrator and License Server (the latest released version of License Administrator has fixes for virtual servers and some cyber security vulnerabilities, note that License Administrator is backward compatible with earlier SBO versions) Activate the licenses based on the info from step 3 Note: If running the demo license, steps 3 and 4 may be skipped. If problems continue to occur, then send the above details collated (in step 3) and email this/contact support.

Issue Finding the rules governing the BACnet device Instance ID in EBO and learning to change it if required. Product Line EcoStruxure Building Operation Environment Building Operation Enterprise Server Building Operation Automation Server Premium Building Operation Automation Server Bundled  Cause The BACnet device Instance ID must be unique within a BACnet system. There may be a need to find out or change the device Instance ID to ensure there are not duplicates.  Resolution When a BACnet Interface is added to an SmartX server, AS or ES, the Server will become a BACnet device and it will have an Instance ID (automatically generated or manually assigned).  To check an ES or AS BACnet device instance ID go to the properties of the BACnet Interface and then the Advanced tab. The device instance ID is defined as the Object ID. To check other BACnet device, SmartX controller or 3rd party BACnet device, go to the properties of the BACnet Device and then the Advanced tab. The device instance ID once again is defined as the Object ID.  No 2 BACnet devices in any system may have the same Instance ID/Object ID. The valid range of Instance Numbers for a BACnet device is 0 to 4194302.   Change BACnet Device ID: You can change BACnet device IDs for SmartX Server or Controller when there is a conflict with another BACnet device, move controller or in those situations where you need to change the originally selected value for some local or site-specific reason. In EBO V3.2.3 or higher (except V3.3), it is possible to change BACnet Device ID of an SmartX server (ES, AS-P or AS-B), as explained in: Changing the BACnet Device ID in a SmartX Server To change SmartX IP Controller BACnet device ID, follow: Changing a BACnet/IP Device ID

Issue When trying to log in to WebStation Version 1.7.1 using Internet Explorer 11 you get the following error message: Wrong domain, user name or password Product Line EcoStruxure Building Operation Environment Building Operation Automation Server Premium Building Operation Webstation Cause The cookie sent from the SmartStruxure server has an old expiry date. This can be confirmed by tracing communication using Fiddler or similar. Resolution Set the correct date and time in the Automation Server or Windows PC where the Enterprise Server is installed. Refer to Web Help #4388 for instruction on how to set the time in an Automation Server

Issue Is it possible to use TAC Vista WebStation over ISDN Routers in a WAN Intranet? Product Line TAC Vista Environment TAC Vista Webstation ISDN Routers WAN Intranet Cause This is possible to configure. Resolution To run TAC Vista Webstation, log into a NT domain. An ISDN router can be a link on an Intranet.

Issue When TAC Vista is setup as an OPC Server, Can you access the Historical Data (HDA) from TAC Vista SQL DB Product Line TAC Vista Environment TAC Vista OPC Server OPC Client Cause When TAC Vista is acting as an OPC Server and providing integration with a third party software / device, online and alarm values are all that is supported. Historical data is not supported via the OPC interface. Resolution It is not possible to access the historical data from the Vista SQL database, when using Vista's OPC Server . It may be possible to get historical data with the help of some third party OPC-HDA-Server for SQL software.  This option has not been tested, and issues related to this interface are also not supported. Click on below link to see an example of OPC-HDA Server for SQL. http://www.opcti.com/OPC-HDA-Server-for-SQL.aspx

Issue TAC Vista appears to keep trying to retrieve logs from controllers despite them being offline. This causes a lot of event messages to be created and fills up the log database quicker. Product Line TAC Vista Environment TAC Vista 5.X Older RPU (remote processing unit) under a PLB ( 5751), containing logs to be retrieved by Vista. Cause TAC Vista appears to keep trying to retrieve logs from controllers despite them being offline. This causes a lot of event messages to be created and fills up the log database quicker. Resolution Vista continues cyclically trying to retrieve the log/s even when the RPU under the PLB is offline.

Issue BACnet/MSTP communication to Viconics VT thermostats is intermittent. Product Line Field Devices Environment SE7000 Room Controller Cause Possible cause is physical layer and device addresses. Resolution Verify the physical layer (i.e. wire, end of line resistors and bias resisters) is installed as recommended.  A common wiring error is landing the trunk cable shield to the "REF" terminal at the thermostat. The shield should be carried through but not landed at the thermostat and the trunk shield should be grounded in one place. Duplicate device addresses can cause this type of issue as well. Verify each controller has a unique "Com addr" which is part of its instance number. This can be viewed and modified from the display panel of the thermostat. To enter the configuration parameter menu: VT7200 series press and hold the button(OVERRIDE) for 8 seconds VT7300 series press and hold the middle button(°C/F or OVERRIDE)for 8 seconds. VT7600 series press and hold the button(MENU)for 8 seconds

Issue How to use multiple monitors when working in Building Operation WorkStation. Product Line EcoStruxure Building Operation Environment Multiple Monitors Building Operation WorkStation Cause Need to understand how to utilize multiple monitors with Building Operation WorkStation available as an option from version 1.4.1 and above. Resolution Building Operation Workstation provides the ability to place any pane in WorkStation on a separate monitor including the alarm, watch, and event windows. This can be a very productive feature for a building front-end computer or even in the engineering stages of the system. Versions 1.4.1 and above The multi-monitor display support in WorkStation includes the ability to save and reset workspace layouts. Individual users at a given WorkStation can modify the workspace layout and save it such that whenever that user logs in using that PC the workspace will revert to their modified layout. Included in the modified layout is the ability to move panes to a second monitor and have those panes positioned in the same way whenever that user logs in with that PC. The user can revert to the default layout at any time. How to move WorkStation panes to a second monitor Click, hold and drag the title bar (1) of any pane in WorkStation that is to be moved to another monitor. The pane will appear as a purple shadow (2).  Drag the pane to another monitor, release and re-size as necessary (3).    How to save the workspace layout for the current user At the top of the WorkStation window, click on the View menu (1) and select "Save workspace layout" (2).  When the same user logs out and then logs back in again, the layout will remain the same. To return the layout to the default, go to the View menu and select "Reset workspace layout". Note: When working with a two-monitor layout using a laptop on a docking station, if the laptop is undocked it will no longer be possible to see the panes that were moved to the second monitor.  To correct this go to the View menu and select "Reset workspace layout".     Versions 1.4.0 and prior It is possible to use WorkStation and WebStation on multiple monitors in prior releases: Launch multiple instances of the clients and run them on different monitors. In WorkStation, “Tear off” view windows and position on different monitors. Manual positioning of windows is needed.  To get more automatic behavior at start-up or logon, it is better to run with multiple computers with separate displays or see if a 3rd party window positioning utility can help.

Issue Running Bomgar Remote Support Client from Linux for support from Product Support Services Product Line EcoStruxure Building Operation Environment Building Operation Edge Server - Standard Cause Bomgar session downloads Bomgar-scc-[long string of characters].desktop file and need to run to connect with a Product Support Services agent. Resolution The file needs to be granted permission to execute and then run. Open browser on Linux OS for website: https://seconnect.se.com  Enter the 7-digit Session Key and press SUBMIT button. After saving the client to the Downloads folder, right-click on the bomgar-scc-[long string of characters].desktop file, then click Properties.  Click on the Permissions tab, then check the checkbox next to Execute to Allow executing file as program.  Open Terminal, then type "sh " (without quotes and not forgetting a space), then drag the file to the Terminal window, then press Enter. The full command will look similar to this image.  Once the executable runs, this image will appear on the screen as the full session begins.  Click Allow to let the agent view and control your computer. 

Issue In MNB-1000 (Plant Controller) firmware Revision 1.50E, the Spanning Tree Protocol is Disabled, by default. All previous versions were shipped with the Spanning Tree Protocol enabled. Product Line TAC IA Series Environment I/A Series MNB-1000 (Plant Controller), firmware Revision 1.50E, and later. Cause In some cases where multiple BACnet routers (eg, MNB-1000, UNC, ENC, etc) were installed on the same BACnet-IP internetwork, having the Spanning Tree Protocol enabled in the MNB-1000 would allow a "router loop". Resolution Be aware that in MNB-1000s with firmware Revision 1.50E and later, the Spanning Tree protocol is disabled, by default. Click here to see the Release Notes for firmware Revision 1.50E . It is always recommended the highest firmware version available for the MNB-1000 be used.  Many issues have been addressed for better functionality.

Issue Field office needs to access the Web Service page so that they can perform an Ethernet network packet capture for communications troubleshooting purposes. Product Line TAC IA Series Environment I/A Series MNB 1000 with firmware 1.510 and later only. Cause The field office needs to access the Web Service page so that they can perform an Ethernet network packet capture for communications troubleshooting purposes. Resolution The Web Service page has been removed from the MNB-1000 Plant Controller firmware effective with release version 1.510.   All functions that were previously included on the MNB-1000 Web Service page are now included in the WorkPlace Commissioning Tool -- Device Properties window for MNB-1000 controllers.  The changes to the Device Properties screens were documented in the WorkPlace Tech Tool 5.7.7 release notes, available here.

Issue In MNB-1000 with firmware Revision 1.50E, the Router Table can be viewed and /or reset without resetting the Plant Controller. This allows users to clear table entries that could cause router problems, without needing to reset the MNB-1000. Product Line TAC IA Series Environment I/A Series MNB-1000 (Plant Controller) with firmware Revision 1.50E, or later. WorkPlace Tech Tool, Commissioning Tool (WPT CT) version 5.7.7 and later Cause Product enhancement. Resolution To view or reset the Router Table, choose from the following procedures, depending on the version of firmware: For MNB-1000 with Revision 1.50E, use a web browser to access the Plant Controller to view or clear its Routing Table. Click here to see the Release Notes for Revision 1.50E, for more details. For MNB-1000 with Revision 1.510, use the WorkPlace Tech Tool Commissioning Tool, version 5.7.7.  Go to the Device Properties, Diagnostics Tab, and Router Table Information button. Click here to see the Release Notes for WPT 5.7.7, for further details.

Issue Unable to ping the MNB-1000 (Plant Controller) using firmware Revision 1.50E until 1.532  Product Line TAC IA Series Environment I/A Series MNB-1000 (Plant Controller), firmware Revision 1.50E, until 1.532. Cause Common IP (Internet Protocol) ports echo (7), daytime (13) and time (37) are open. Having any of these IP ports open may be a cause of concern for customers that are sensitive to network security issues; these customers include defense installations, financial institutions, and government buildings. Resolution The services using the echo, daytime, and time protocols have been disabled which prevents IP ports 7, 13, and 37 from being open. These services and protocols have no purpose during the normal operation of the MNB-1000. Disabling the echo protocol and closing of port (7) has the side effect that the MNB-1000 cannot be “pinged”. Using the command line program Ping will not detect an MNB-1000 that has firmware v1.50E installed. Use WPCT instead of Ping to verify communications with the MNB-1000. Click here to see the Release Notes for firmware Revision 1.50E. Update; In firmware 1.532, the ping function was re-initiated as the default.  Please see the TPA-IA-19-0004.00 Firmware 1.532 Release Notes.  It is always recommended the highest firmware version available for the MNB-1000 be used.  Many issues have been addressed for better functionality.

Issue Unable to gain access to Building Expert Product Line EcoStruxure Building Expert Environment SmartStruxure Lite Multi Purpose Manager MPM-GW MPM-UN MPM-VA Cause The admin password has been changed and the user has lost the password Resolution For MPM with firmware 2.14 and earlier: Send the MPM 'default.db' file to Product Support.  From a web browser, you can save the default.db file to the local drive by typing the address http://[ip_address]/root/default.db (replace [ip_address] with the actual IP address of the MPM, or 10.50.80.2 if bootloader is used) For MPM with firmware 2.15 and later: Send the MPM Node ID or MAC Address to Product Support. Refer to the document StruxureWare Building Expert Password Recovery When Accessing MPM - Reference Guide for the procedure to obtain the MPM Node ID or MAC Address.

Issue How to create a Continuum Cyber workstation Product Line Andover Continuum Environment Continuum Cyberstation / Workstation Andover Continuum Software and Firmware Compatibility Matrix Cause Creation of Continuum Cyber Workstation. Resolution Download the version of CyberStation Software from Exchange and follow the 'Setting Up Workstation Parameters' section of the Cyberstation Installation Guide included in the zip file.  

Issue A Continuum Workstation has become corrupted and cannot be re-added Product Line Andover Continuum Environment Continuum Cyberstation / Workstation Continuum Database Initialization SQL Database Cause Workstation will not initialize correctly and Continuum does not start correctly even though database can be seen correctly from the PC Resolution Occasionally a workstation can get corrupted, within Continuum, such that the computer cannot connect as that particular workstation.  A new workstation needs to be created within Continuum using Database Initialization.  Consider the following:  During the initialization process new Workstation Name, Folder Name, Device Node ID, and Network ID are required.  When initializing an IP conflict may occur, requiring a manual change to the computer IP address first. Once created log in using the new Workstation,  copy over any required objects from the old Workstation and then delete the old Workstation. Please refer to How to create a Continuum Cyber Workstation for supporting information  

Issue Servers not visible after upgrade due to permission change Product Line EcoStruxure Building Operation Environment Enterprise Server ES Enterprise Central EC Cause The Domain Local Group " Reports Administrators" is removed when an ES is upgraded to v4.0 or greater. This Group is automatically deleted during the upgrade because Report Server is not supported in v4.0 or greater. It is possible for local users to be selected as User Group members of " Reports Administrators", so the permissions for these users may change after the upgrade. This is not good practice, only the Reports Server login user should be part of the " Reports Administrators" Group " After the upgrade the Group "Reports Administrators" is removed and the Servers are not accessible Resolution Any users that were part of Group "Reports Administrators" should be reassessed and their permissions corrected