Building Automation Knowledge Base

Issue While Continuum controllers and EcoStruxure controllers do not utilize Power over Ethernet (POE), can plugging in a Continuum or EcoStruxure controller into a POE switch damage either the POE port or the controller? Product Line Andover Continuum, EcoStruxure Building Operation Environment PoE Ethernet Cause Controllers must be installed on a subnet served by a POE switch. Resolution According to the IEEE standard, a POE switch shall determine if the connected device is POE capable before turning on the power. The detection if a connected unit is POE capable is done by measuring the resistance between the pair #2 - #3 and pairs #1 - #4. On a POE capable unit the resistance is 25kohm, with some tolerance. If it is lower or higher it is not considered to be POE capable. As there are no Continuum or EcoStruxure ethernet controllers that apply a 25K ohm load, a properly functioning switch port will not enable PoE power and the device will not be damaged. Find information on the PoE standard in the Fundamentals of Power Over Internet (PoE) PDF

Issue When the Vista export file is converted using the Vista conversion to an EBO Server the Xenta devices are created with an empty application. Product Line TAC Vista, EcoStruxure Building Operation Environment Vista Conversion tool Cause The user name that was used to log into Vista Database to run the Database export does not have full access to the Xenta devices Function Block Program. Resolution Log in with the System user that has full access to the Vista Database and export the database for the conversion tool to use.

Issue The Alarm Priority does not display the correct value (110) in the Alarm View or Event View when the Alarm is in the "Alarm" state and displays 100 Value instead. It displays correctly in the Alarm view when the alarm state is "Acknowledged" or "Reset", and it displays correctly in the Event view when the alarm state is "Reset Product Line EcoStruxure Building Operation Environment Building Operation Workstation Building Operation Automation Server Building Operation Enterprise Server Cause Incorrect configuration Resolution There is an"Alarm decorator override" that seems to override the priority for the alarm If in alarm state and priority is 110, then the priority is overridden to 100 as configured in the alarm decorator object Removing the override in the decoration will resolve this issue

Issue IP Controller is getting incorrect overrides at Priority 16. The room control unit is writing to Priority 16 which is then writing to multiple setpoints with a zero (0) value in the function block program, causing programming to fail. Product Line EcoStruxure Building Operation Environment Building Operation Workstation Building Operation Automation Server Cause Even though priority 16 and the Value can sometimes be synonymous, they are still separate Objects The room control unit is writing to Priority 16 AND the Value has been set to Zero.   The value is set to 0  Writing directly to priority 16 from the room control unit Resolution The best practice would be to:  Bind to the Value Object from the room control unit and also set the retain level under Value rather than biding to and setting Retain level on Priority 16

Issue Embedded WebStation client licenses were needed when logging directly into a SmartX server as of 3.0.1 but are no longer needed Product Line EcoStruxure Building Operation Environment Building Operation Webstation Building Operation SmartX Server Cause The license requirement is being removed due to market feedback. The quantity of direct web connections to the SmartX server is restricted by the Architectural Guidelines only. Resolution Important for version 4.0 (EBO 2022) and above:  Note that in Building Operation 2022 (v4.0.x) and above, WebStation licenses have now been enforced at the server level and are required.   If there is no embedded server license for example "XWSWXBU0000SD ASP Bundle - Standard" in the SpaceLogic server it will not be possible to login to the server using Webstation. The Webstation license is included in the embedded server license.   For version 3.0.x The change is available via a HotFix to version v3.0.3 and will be incorporated into Maintenance Release v3.0.4. In both the HotFix and the Maintenance Release, license status presentations in the Device Administrator and Control Panel will indicate the availability of 99 client licenses. However, the supported quantity of direct web connections to a single SmartX server is established by the Architectural Guidelines; currently, the maximum is five concurrent connections. In v3.1, the Device Administrator and Control Panel will not list client license availability at the SmartX server level since it is not constrained by licenses.  

Issue Understanding how to check the firmware version of the USB-485-INET adapter and upgrade it to the latest version. Product Line TAC INET, EcoStruxure Building Operation Environment Building Operation I/NET USB-485 I/F Building Operation Automation Server Building Operation Automation Server Premium Cause If the firmware version of an I/Net USB interface is at an older firmware version then it may need to be updated. Please check the Exchange website for the latest firmware version Note: If the USB adapter is not at least at firmware version 1.02 then the system may experience communication issues in which I/Net values are not updating in SmartStruxure or Automation Servers may be dropping offline.  In some cases, the Enterprise Server can lock up due to the older firmware in the I/Net USB adapter. Resolution To download the latest "USB-485-Inet Firmware Update Utility" click here. To Verify the Current Adapter Firmware Version in EBO 2.0 and Higher Right click the Inet Interface is the System Tree of WorkStation and choose Properties. Down towards the bottom of the Basic tab you will find the Firmware Version.   To Verify the Current Adapter Firmware Version in SBO 1.9 and Lower Connect the USB Interface to a laptop with the USB cable that is attached to the AS-P. Do not hold the pushbutton in on the USB Interface. Run the firmware executable. Press Enter. It will display: "Found USB Device on COMX"  and will display the hardware version, software version, and the firmware date. It will then say, "Press Enter to begin the upgrade.  Note: Pressing Enter here will only repeat the hardware and firmware versions. The process to Upgrade the Adapter Firmware Note: If the I/Net USB adapter is already plugged into the laptop from checking the firmware version as described above, then to start the upgrade process USB cable will need to be unplugged from the laptop. Then follow the steps below. While holding down the pushbutton of the I/Net USB adapter, unplug the adapter's USB cable from the AS/AS-P and plug it into your laptop. After it is plugged into the laptop, release the pushbutton.  You will see that the LEDs on the interface are not flashing. On the laptop, run the firmware executable. After the command window opens, press Enter to start the update process. It should display "Unprogrammed device located" followed by "Device programmed successfully". Next, it will say "Found USB Device on COMX" and show the hardware version, firmware version, and the firmware date. Press Esc to close the command window.  The firmware upgrade is now complete. Note: Some laptops will not recognize the USB Interface and will not assign it a Com port.  If this is the case you will still be able to upgrade the firmware.  But instead of giving the Com port the and the firmware version after the upgrade is complete, it will show "Unable to find USB Device".   Also, you would not be able to check the firmware version prior to upgrading as mentioned above.  To correct this you must install the 7801 Tap.inf driver.  Click here to download the 7801 Tap.inf drivers. To install the 7801 Tap.inf drivers: Connect the USB Interface to a laptop with the USB cable that is attached to the AS-P. Go into Device Manager and find the Inet USB Interface.  It will have an error because of no driver. Right-click on it and choose to Update Driver Software... Select Browse my computer for driver software and browse to the 7801 Tap.inf file. Then follow the instructions above.

Issue After editing an MNL-800 application with the WorkPlace Tech Tool Editor, an error is displayed indicating that the application file could not be saved. Product Line EcoStruxure Building Operation Environment Building Operation Workstation >1.4 Building Operation WorkPlace Tech Editor Cause The name of a LON Network Variable (nvi or nvo SNVT) or a LON controller configuration constant (nci SNVT) contains a space. Echelon standards do not allow spaces in network variables or configuration constant names. Resolution Edit the application file removing any spaces or other non-supported characters from network variable and configuration constant names. More information is contained in the SBO WebHelp topic "WorkPlace Tech Editor"

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 The added to parent column shows incorrect information. Product Line EcoStruxure Building Operation Environment Building Operation Project Configuration Tool (PCT) Cause PCT doesn't detect detachment in WorkStation. Resolution Do not detach the child server from its parent in PCT. Webhelp information: Adding a Virtual EcoStruxure BMS Child Server to a Parent Server.

Issue Detailing configuration and starting DWiz on a computer running EcoStruxure for Buildings Operation. Product Line EcoStruxure Buildings Operation Environment Building Operation Workstation Xenta 281 Xenta 301 Xenta 401 Cause DWiz (Download Wizard) was a part of the TAC Vista installation, but not so commonly used in EcoStruxure Buildings Operation, and therefore no longer included in the Start menu. It is however still installed and could be started from Windows File Explorer. Resolution   Verify the Com port used. If your computer does have a serial port, this is normally Com1 or Com2. If you are using a USB to RS232 adapter (like Aten), you could get a much higher number. The program requires a port number between 1 and 9. You may need to change the port number. This could be done via Windows Device Manager. In Windows File Manager, go to the directory where EcoStruxure Buildings Operation Workstation is installed. Here you will find DWiz.exe as well as MentaSetup.exe. Start MentaSetup.exe, adjust Com Port, select Apply and Close. MentaSetup        5.  Now it should be possible to start DWiz.exe located in the same directory.

Issue How to troubleshoot a communication issue with the Sigma interface Is there a log available within the ES that shows the Sigma communication between Sigma controllers and the ES Product Line EcoStruxure Building Operation, Sigma Environment Building Operation Workstation Building Operation Enterprise Server Cause When troubleshooting Sigma issues in an ES it can be helpful to see the communication between the Sigma controller and the Sigma interface in the ES to help identify this issue. The trace log within the ES is available and is configured as described below in the resolution. Resolution The level of logging for Sigma in the Trace Log needs to be increased: Open Workstation and navigate to [ES name]/System/Modules/Trace/Loggers/nsp/nsp.pin. Right-click "nsp.pin.sigma" and choose Properties. Under Level, change from "Information" to "Trace", then click ok. Let it run a few minutes. If there are some user input needed to recreate the Sigma issue, then perform these steps now. e.g. If ifs a graphics issue then run the respective graphic. Retrieve the log by right-clicking [ES name]/System/Modules/Trace/TraceSettings and choose Trace settings->Get trace log.  Save the log file. A useful tool available on the Community, the Sigma decoder can be used to assist in viewing/debugging the Sigma trace log file information saved in the previous step. Once debugging is complete remember to change log level back to "Information" (reverse of step 3).   Note: If the ES is restarted for any reason whether by manually stopping in the Software Administrator or other, the nsp.pin.sigma will default back to 'Information'.

Issue Many users are unsure of the implication of the field "Interval time zone" in the Trend Log configuration window. Product Line EcoStruxure Building Operation Environment Building Operation Enterprise Server Building Operation Automation Server Building Operation Automation Server Premium Cause The setting "Interval time zone" under the Trend log configuration has caused some users to believe that this setting stores trend data in either "UTC" or "Server local time" Resolution The trend log data is always stored in UTC time, regardless of the option selected under this setting. This setting is intended for preventing problems with Daylight Savings Time (DST) when the logging interval is more frequent than 1 hour. See Interval Trend Log Properties – Basic Tab in EcoStruxure WebHelp. NOTE: When the interval is longer than 1 hour and you want to continue to log that interval after a DST change, use Server Local Time. For example, the log interval is every 24th hour at midnight and you want to continue to log at midnight even after a DST change, so you use Server Local Time. During the DST change in the Spring, the log sample will register after 23 hours. After the DST change in the Autumn, the log sample will register after 25 hours. Interval Time zone 

Issue AS-B/P is unable to upgrade to the EcoStruxure Building Operation V3.2.x from out-of-the-box or DFU mode. When checking the upgrade progress file, you receive the following error: Product Line EcoStruxure Building Operation Environment Building Operation Automation Server Premium Building Operation Automation Server Bundled Cause In V3.2.1, the change was made to use IP-over-USB as a way to communicate faster through the USB. Due to this, IPv4 and IPv6 need to be enabled on the connected device running Device Administrator. Resolution Check to make sure IPv6 is enabled on your machine. Open a Command Prompt window and run the "route print -6" command If it only shows two IPv6 addresses then IPv6 is disabled and you will need to enable it To enable IPv6 Open Registry Editor on your Windows Machine Navigate to: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Tcpip6\Parameters\ Double-click on DisabledComponents to edit Change value from "FF" (IPv6 disabled) to "00" (IPv6 enabled) Note: The Disabled Components registry value does not affect the state of the check box. Therefore, even if the Disabled Components registry key is set to disable IPv6, the check box in the Networking tab for each interface can still be checked. This is the expected behavior. Note: You must restart your computer for these changes to take effect.  

Issue The WorkPlace Tech and WorkPlace Editor add-in for the VisioRibbon is available in the toolbar of Visio but all or some of the functions are unavailable. Product Line TAC IA Series, EcoStruxure Building Operation Environment I/A Series WorkPlace Tech 5.9.x, 5.10.4 Building Operation Workstation (WorkPlace Tech Editor) Microsoft Visio 2010, 2013, 2016, 2019 (WorkPlace Tech 5.10.4 only) Cause There may be one or several of these situations causing this behavior depending on a combination of products installed. The Visio installed is an unlicensed product or in its evaluation period and not registered  The Visio installed is not properly updated There is an error in the WPDispatcher.msi Resolution Review the proper area for the Visio you are using to assure the product is registered; Visio 2010 Visio 2013/2016/2019 If the Visio is part of a subscription-based product, it will be noted as such rather than saying the product is activated. Thoroughly read this Knowledge Base Article for the information required to assure your Visio is properly updated. Workplace Tech 5.9.3 / Workplace Tech Editor (EBO) Microsoft Security Updates required for Visio and Office  To correct any possible WorkPlace Tech or Editor (SBO/EBO) dispatcher problems, Follow the path C:\Program Files (x86)\WorkPlace Tech to the WPDispatcher.msi and "right click / Uninstall" Do this for each version of SBO or EBO installed that has Workstation with WorkPlace Tech Editor.  Here is the path C:\Program Files (x86)\Schneider Electric EcoStruxure\Building Operation X.Y\WorkStation or C:\Program Files (x86)\Schneider Electric StruxureWare\Building Operation X.Y\WorkStation (X.Y will be the version installed i.e 3.1).  Perform the same Uninstall of the WPDispatcher.msi.  The picture below is what will appear if the dispatcher has been removed or was not previously installed.  This message is expected. Open the WorkPlace Tech or the WorkPlaceTech Editor.  The WPDispatcher.msi will run the correct version.

Issue Sigma server fails when a Data Import is initiated during a Sigma transition Product Line EcoStruxure Building Operation, Satchwell Sigma Environment Sigma Building Operation Enterprise Server Cause Sigma server fails when an EBO data import is initiated. Resolution It is important that the Sigma Database is checked with the Doctor utility (found in SigmaX) before a Sigma transition into EBO is undertaken. Longtext - Longtext file contains 'mandarin' type characters - probably from previous BAS/Sigma upgrades. If the file contains these, then Longtext has probably not been used in the past or not used currently. Delete the file (located c:\sigma\data), it will self re-create. Shorttext - Shorttext contains an incorrectly formatted entry. Find entry and correct. To find, delete 1 -250, if it continues to fails, the entry in question will be in the range 251 to 500 and keep halving until the entry is found. Index A errors - index contains a looping segment, where the page references itself. Correct index as necessary using SigmaX - Doctor. Index A errors - page is referenced more than once, i.e. the index page can be opened via two (or more) routes. Correct Index as necessary using SigmaX - Doctor. Note: the Index should be checked with SigmaX before a transition. Object corruption - open object in Sigma, if it fails to open, then correct by whatever means that is required, Sigma server will fail at a point during the Data Import. Log Sets - Fail to import log sets. To find, in Sigma, locate the logset.rec in the c:\sigma\data\server...folder file, take a copy. In Sigma, delete 50% of the log sets and try the import again. If it fails, delete another 50% and repeat. Or if it succeeds, then the issue may lie in the 50% of log sets originally deleted, re-instate these using the copied logset.rec file and try again by deleting the other 50% and so forth.

Issue Customers may need a copy of their License Entitlement certificate Product Line EcoStruxure Building Operation Environment Building Operation Licensing Cause Missing Entitlement certificate  Resolution Customers have access to the following link, where they can use the Entitlement ID or Activation ID to login to the Licensing page: License Page information After logging in, select the “List Entitlements” under “Activation & Entitlements” on the top. Tick the checkbox in front of one Activation ID (ACT), select View/View certificate Now, a new page pops up which contains the Entitlement Certificate information. This can be saved or printed.

Issue Users asked if it is possible to do a warm and cold starts of the Automation Server using the reset button on the physical hardware Product Line EcoStruxure Building Operation Environment EcoStruxure Building Operation Cause Users may need to do a Warm/Cold start of the Automation Server Resolution From V1.5 and higher, the Warm start of the Automation Server can only be done through the command from the Workstation Software.  From V1.7 and higher, the Cold start of the Automation Server can only be done through the command from the Workstation Software.    Please refer to the following Webhelp for more information: Reset functionalities of the Automation Server    

Issue On an existing trend log, the calculation type can be set to the “Meter Consumption”, but this does not generate any log records. Product Line EcoStruxure Building Operation Environment EcoStruxure Building Operation Cause The “Set initial meter” under the “Meter Info” tab has been set to false when the trend log was initially created. Resolution The following image demonstrates the issue. The “Is meter log” is false because in the trend log creation process the “Set initial meter” has been set to false. This causes the “Meter Consumption” calculation type does not generate any log records. To resolve this: Create another Trend log with the “Set initial meter” set to true Or Right-click on an existing trend log (with “Is meter log” = false), press manage meter, configure the required settings, and then press save. This will change the “Is meter log” to true  Now, if the calculation type is set to “Meter Consumption” on the trend log, the log records are getting populated.

Issue Unable to use SE8650 to control heat pump with a two Stages Furnace (auxiliary heat) Product Line EcoStruxure Building Operation, EcoStruxure Building Expert Environment Building Operation Workstation Building Operation Automation Server SSL SE8000 Cause Only one output is available in the SE8650 for Auxiliary heating Resolution A simple solution would be to Wire both Furnace W1 and W2 to the SE8650 W1 terminal, and both will be on at the same time Both furnace stages will be activated as a single stage from the same output Or a more advanced option would be to use a LUA Script to control the second stage of Auxiliary heating. See the below example using the SE8650 UO11 terminal  

Issue Strange characters are displayed in the display of a VT7000 and SE7000 Series thermostat. Product Line EcoStruxure Building Operation, EcoStruxure Building Expert Environment Building Operation Workstation Building Operation Automation Server SSL SE7000 Cause The thermostat has experienced a brownout condition. Any time the power drops below 16-17Vac for a 1/10 of a second or so it will cause this condition. Resolution The thermostat still updates to the BMS correctly; it’s only its display that’s affected.  Cycling power to the unit will clear the issue. However, if the brown out condition is not addressed, it can happen again. If a repeated brownout issue at the site cannot be corrected, consider powering the controller with an UPS.   

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 SigmaX checks prior to transition into EBO Product Line Satchwell Sigma Environment SigmaX Cause Programmable Object checks required prior to transitioning Sigma to EBO. Resolution Programmable Object checks steps to be taken to check a Sigma database is free of more than one type of RETURN statement is used prior to a transition to EcoStruxure Building Operation (EBO). This video will demonstrate how to use SigmaX to find and create a report of any Programmable Objects that are using more than one type of RETURN statement. This video with SigmaX is the third of three videos, the first SigmaX Quick Help Video will check for Database Errors and the second video will check for Duplicated Names.     When launching the SigmaX application, see the Knowledge Base articles for Side by Side errors and errors regarding missing SigmaX files should they occur.