Building Automation Knowledge Base

Issue When trying to launch the Energy Expert Integration Utility (formerly the Power Manger Integration Utility) the following error is given. Product Line EcoStruxure Building Operation Environment Energy Expert Power Manager for SmartStruxure Integration Utility Cause This error message can be the result of different causes. Check the IntegrationUtility.log file found in the same location as the Integration Utility for more information.  Example of Integration Utility Log error: ERROR: Microsoft.Practices.Unity.ResolutionFailedException: Resolution of the dependency failed, type = "IntegrationUtility.Shell", name = "(none)". Exception occurred while: Calling constructor IntegrationUtility.Pme.Services.PmeUserDataStore(). Exception is: ConfigurationProviderException - Could not locate a connection string provider. Resolution NOTE: If you have already downloaded the software, you must first delete the folder you unzipped before doing the process below.  Unblock the Zip file The first thing that MUST be done after downloading the Power Manager software from the Exchange is to unblock the zip file. Right click on the zip file and select Properties. Under the General tab, towards the bottom click Unblock. Click Apply and close the properties window.  You can now unzip the software and use it as normal.  Compatible .Net Framework Versions Different versions of the Power Manager / Energy Expert Integration Utility require certain versions of Microsoft .Net Framework. Note: Having multiple versions of .Net Framework installed may cause issues.    Pease refer to the Energy Expert Compatibility Matrix for further detail.

Issue When attempting to access the dashboard URL via the web browser or in SBO Workstation, the following message is displayed. Product Line EcoStruxure Building Operation, EcoStruxure Energy Expert Environment Power Manager 1.2 and newer Power Manager Expert 8.1 and newer Building Operation Workstation Cause A Power Manager 1.2 or newer system running a permanent license allows the user to a log into the Management Console, manual authentication URL, and through the EWS interface in SmartStruxure Workstation. After upgrading to the latest version of Power Manager this access no longer works. The Ports match in License Manager and FlexNet and this site has previously worked. The cause to this issue is that the URL being used has changed starting in PME 8.1. Resolution This issue is due to a change made in the dashboards URL starting in Power Manager 1.2 / Power Manager Expert 8.1. The URL needs to be changed by replacing "Web" with "Dashboards" in the URL found in the EWS link settings or when logging in directly with a web browser.    Example: http://XXXX/SystemDataService/Auth/LogOnWithMultiuseAuthToken?RedirectUrl=http%3a%2f%2fFS2%2fWeb%2f%3fDisplayEmbedded%3dTrue&multiuseAuthToken=11324... http://XXXX/SystemDataService/Auth/LogOnWithMultiuseAuthToken?RedirectUrl=http%3a%2f%2fFS2%2fDashboards%2f%3fDisplayEmbedded%3dTrue&multiuseAuthToken=11324...   Also in the newer versions of Power Manager, there is a limit regarding what can be accessed in PME when using a Power Manager license. In Power Manager 1.2 and on you can access: /Reporter /Dashboards /Trends /HierarchyManager /RateEditor and use the integration toolkit to get into SBO if necessary. Power Manager is now known as EcoStruxure Energy Expert.

Issue The error below occurs as soon as the Management Console is launched.  Environment Power Manager Power Monitoring Expert (PME) Management Console Cause In order for the Management Console to work properly it needs to see the correct dll files in three separate locations. If the install process of PME was not completed successfully or did not have full administrative rights while installing then some of these files may be missing.  Resolution The issue was that the Licensing.LicenseManager.resources.dll and Licensing.LicenseManager.dll was not present in all of the three following folders:     C:\Program Files (x86)\Schneider Electric\Power Monitoring Expert\Web\bin   C:\Program Files (x86)\Schneider Electric\Power Monitoring Expert\system\bin   C:\Program Files (x86)\Schneider Electric\Power Monitoring Expert\system\ReportDataService\bin Verify that the Licensing.LicenseManager.resources.dll and Licensing.LicenseManager.dll files are present in all three of the locations below. If they are missing in any location, copy and paste the files accordingly.      C:\Program Files (x86)\Schneider Electric\Power Monitoring Expert\Web\bin   C:\Program Files (x86)\Schneider Electric\Power Monitoring Expert\system\bin   C:\Program Files (x86)\Schneider Electric\Power Monitoring Expert\system\ReportDataService\bin     Note: Replace "Program Files (x86)" with "Program Files" if you are working on a 32 bit computer.   

Issue Data not showing in a single row on the Trend Log Comparison Report Creating Custom Reports Environment Report Builder 3.0 Struxureware Building Operation WebReports Cause Trend sample data is stored in the Reports Server at a resolution of less than 1 second. In some cases the user wants to compare data in showing less resolution than what is in stored in the database.  Resolution Open Microsoft Report Builder and Edit the existing Trend Log Comparison Report.  You can get detailed instructions on how to perform this task on the online help guide. Scroll to the bottom and select the DateTimeStamp Field in the Second Tablix object. Click on the drop down menu in the Row Groups pane and select Group Properties On the General Tab, click on the Fx button Change the Expression to say: =FORMAT(Fields!DateTimeStamp.Value, "dd MM yyyy hh:mm") Repeat this for the Sorting Tab. Enter the same Expresssion. =FORMAT(Fields!DateTimeStamp.Value, "dd MM yyyy hh:mm") Click OK to save changes. Right click on the DateTimeStamp TextBox and select Text Box Properties. In the Number tab, change the default format to the desired display format Perform a Save AS to ensure you do not overwrite the factory supplied report.  Follow the instructions on web help to allow the modified report to be used in WebReports.

Issue 3rd party Modbus RTU devices go offline or have unstable value transfer after upgrading to version 1.7.1 or above Product Line EcoStruxure Building Operation Environment Detected in version 1.7.1 or above. Automation Server Modbus RTU (RS485) interface Cause The performance of the Modbus RTU interface was improved in version 1.6 and further in version 1.7. This improved performance can make the Modbus Master in SmartStruxure too fast for some third party Modbus RTU devices, and they may be unable to handle the faster polling rates the newer software can provide. Resolution In the Modbus Master Network there are various settings that can be changed to allow it to compensate for slower devices. The settings in this screen shot shows example settings that may be suitable for slower devices or problem networks.   Increasing the Transmit Guard bits from the default of 2 allows more time after one packet before the next packet will start transmitting on the bus. This is useful both for slow responding devices, devices that take longer to turn off their Transmit driver as well as networks that have a high capacitance due to poor cable selection. The Receive timeout (ms) is the length of time the master will wait to receive a response. Decreasing this from the default of 2000 mS (2 Seconds) can often improve network communications, by not waiting too long for a device that may not be responding or offline will improve the overall network operation. By default there is 0 delay between polling the points, by introducing a delay in the Point Poll Delay (ms)  it allows slower devices to handle the data polls from the interface. This is a key setting for slower devices that cannot keep up with the faster polling from the latest Automation Servers and most 3rd party devices will require a value greater than 0. The Silence Characters do not usually need changing in an upgrade, but they can be used to help with poor installations where there is high capacitance in the cabling or poor grounding, this can often be used with lower baud rates on problem sites. The default Poll Duty Cycle is usually appropriate for most installations and is not affected by the upgrades, but can be adjusted if required to match 3rd party devices. In V3.x the same settings apply and the screenshot now looks like this:

Issue User unable to find means to add I/O points for an AS-B in workstation Environment Automation Server Basic Cause User not selecing the AS-B-XX onboard IO object Resolution In the system tree browse to the IO Bus/AS-B-XX onboard IO Right click on the object and select New/Input or Output Point Select the type of IO and continue creating the IO point.

Issue While attempting to import files to through WorkStation or libraries from the Script Editor, the program crashes with the error message below. It can even happen when doing mass create or mass change, or when adding columns to a list view. "StruxureWare Building Operation has stopped working" Environment Building Operation WorkStation Building Operation Script Editor Cause It has been identified that a program called "F-Secure Key" interferes with other installed programs, and can ultimately leed to other programs crashing. "F-Secure Key" hooks into the Microsoft dll "UIAutomationCore.dll" which is used to idenitfy and manipulate elements in the user interface. If "F-Secure Key" is installed, it can easily be identified, as you will see a blue circle with a key when logging in through WorkStation Resolution Uninstall all "F-Secure Key" related program from "Programs and Features" in the Control Panel on the PC

Issue When attempting to get the trace or system logs through WorkStation, you get the following error "Application not found" Product Line EcoStruxure Building Operation Environment Building Operation WorkStation Detected in version 1.6.1 Windows 7 or below Cause The program or editor associated with the file type *.log can not be found on the PC. Resolution Associate a valid program with the filetype *.log 1. Create a new text file e.g. on the desktop 2. Change the file extension on the file from .txt to .log - refer to the following instructions if the file extension is not visible 3. Double click the file, and select a new default editor 4. Get the trace log from WorkStation

Issue If creating a new "Utility" in Workstation it is possible to create a object called " Object Creator". This object is not documented. Environment WorkStation version 1.7.1 and earlier Cause There is no documentation for this object, as it is an internal test object that should not be used in the field. visible and if you use it wrong it will crash. In 1.8 it is removedIt’sIt’sIt’s actually a internal test object used to quickly  create a folder structure. It shouldn’t be used as it isn’t supposed to be  visible and if you use it wrong it will crash. In 1.8 it is removed actually a internal test object used to quickly  create a folder structure. It shouldn’t be used as it isn’t supposed to be  visible and if you use it wrong it will crash. In 1.8 it is removedactually a internal test object used to quickly  create a folder structure. It shouldn’t be used as it isn’t supposed to be  visible and if you use it wrong it will crash. In 1.8 it is removedIt’s actually a internal test object used to quickly  create a folder structure. It shouldn’t be used as it isn’t supposed to be  visible and if you use it wrong it will crash. In 1.8 it is removed Resolution The object is removed in version 1.8

Issue When logging on to the Report Manager or Report Builder to manage, create or install custom report packs, the following error is shown: User does not have required permissions. Verify that sufficient permissions have been granted and Windows User Account Control (UAC) restrictions have been addressed Environment WebReports Cause This is a known issue with Microsoft Reporting Services when User Account Control (UAC) is enabled on the server. By default the local administrators are only given the role of "Content Manager", which does not allow for all operations. The easy solution is to disable UAC, but below is the solution for how to solve it without disabling UAC. For further reference, refer to the following discussion. Resolution 1. Launch Internet Explorer as administrator (right click the shortcut and click "Run as administrator"). 2. Open the Report Manager on the local server using "localhost" in the URL. E.g. if the URL is normally http://server_name/Reports_SQLEXPRESS you need to enter http://localhost/Reports_SQLEXPRESS 3. Click "Folder Settings" 4. Click "Edit" next to the "BUILTIN\Administrators" 5. Check all the options and click "Apply"

Issue PowerFail System Variable for b3 controllers does not show correct value in Script Editor Binding Variables Window Environment Schneider Electric b3 controllers Cause The script program editor for b3 controllers does not recognize the PowerFail system variable as a system-defined value. The value of the variable can still be used in a b3 Script program by creating a Numeric Input in the program header, and then binding the SystemVariable to the program.     Once the value is bound however, the value of the PowerFail System variable is not displayed correctly in the program editor Binding Variables display window. The value of the PowerFail system variable should be shown as a binary value – either 0/1, ON/OFF or True/False.  Instead, the Normal (OFF) value displays as the integer value “1536”. Resolution Although its value is not displayed correctly Binding Variables display window, when the object is bound to the program the value of the object is correctly interpreted when the program is compiled and executed. For coding purposes, the numeric should be treated as a binary value with the expected values of ON and OFF.  Do not use the integer value shown in the Binding Variables window. Example would be : If PowerFail = On then Goto DelayStart Note : The PowerFail system variable in a b3 controller is only active for ONE scan FOLLOWING the restoration of power following a power loss to that controller.

Issue When viewing a graphic using WebStation, the zoom controls are not visible in the toolbar. Only "Reset zoom" is shown. Environment WebStation Graphics Zoom Cause The method of zooming a graphic in and out has changed at StruxureWare Building Operation 1.7.1. Prior to this a toolbar was available, but this has now been removed. Resolution To zoom the graphic in and out, the mouse wheel (scroll) is used. The graphic can be positioned by dragging the graphic. On a touchscreen, zooming is achieved using the pinched fingers method. To reset the Graphic to a 1:1 ratio click "Reset zoom".

Issue When an Automation Server backup is restored, the programs or IO's linked to a time schedule does not show their correct states Environment Automation Server Backplane Function Block Time Schedule Cause More than one AS has been fitted onto the same backplane and this e.g. causes the Function Block program to malfunction. The result of this is that the FB program does not reflect the correct state of the time schedule binding, when a backup is restored.               Resolution The installation of multiple AS's onto the same backplane is not allowed.  Do not install more than one AS on a backplane. If you do, they will both try to drive the IO bus and will collide in doing so. This causes the Task Scheduler to lock up in the AS. Results will be unpredictable! To overcome this issue, make sure only one AS is fitted on the same backplane, and "warm-start" the AS.

Issue When opening a graphic or function block live view, you get the following error: Could not create TGML Invalid data Can not open file Environment Detected in versions: 1.6.1, 1.7.1 Runtime Compatibility Graphics Function Block Cause This happens during upgrade, and only in a multi server environment. The ES will be at one version, and the AS one version below. As SmartStruxure has runtime compatibility, this works. There is however currently an issue with how the files from the AS are cached. As a result, when trying to open a graphic located in an AS just after upgrading the AS, you get this error. Resolution Restart WorkStation after upgrading an AS

Issue BACnet Broadcast Device Table (BDT) on a BACnet Broadcast Management Device (BBMD) becomes corrupted after a server version upgrade, only if the BACnet BDT was taught from another BBMD The following upgrades have this issue v1.5 to v1.6, v1.6 to v1.7, v1.7 to v1.8 Product Line EcoStruxure Building Operation Environment BACnet Broadcast Device Table BBDT BDT Management BBMD Cause When a BDT is manually built (or BBMD first created), BDTE00001 is always set to the Server IP address. In the example this is 192.168.1.15 When the BDT is taught from another BBMD, the BDT is changed and BDTE00001 is modified. When a Server (Enterprise or Automation) is upgraded (V1.5-1.6, 1.6-1.7, 1.7-1.8), then BDT entry BDTE00001 is changed to it's own IP address. Thus the Servers BBMD BDT can be corrupted with the Server IP address appearing twice in the BDT Resolution The taught BDT can either be set manually, before the upgrade, so it does not get corrupted by the upgrade process or be corrected following the upgrade. Option 1: Change the BDT before the upgrade The BDT Entry BDTE00001 should be set to the IP address the Server that contains it. The BDT Entry (BDTE00002 in the simple example above) that held the IP address of the Server should be set to the value that was in BDTE00001. Option 2: Correct the BDT after the upgrade For the first Server being upgraded Upgrade the Server Log into the Server and view the BDT from WorkStation Multi-select and delete all entries, Then manually reenter in all the BDT entries. For all remaining servers being upgraded Upgrade the Server Log into the Server and view the BDT from WorkStation Multi-select and delete all entries From the First Server BBMD do a teach Verify the BDT table is in the Server Below would be the first upgraded Server as option 2 or a corrected as option 1   NOTES Versions 1.8 and beyond include a fix so that the "BDT Teach" Mechanism does not allow the BDTE00001 to be changed. A hotfix will be available in V1.7 Upgrading to a fixed version will not correct the issue, one of the two resolutions above will still need to be completed.

Issue The StruxureWare Building Operation BACnet digital value is seen as being in alarm Product Line EcoStruxure Building Operation Environment BACnet Digital Value Alarm Cause Having created a BACnet Digital Value under the BACnet Interface / Application. When the digital value is "Enabled" (Active Text), the IN ALARM status flag is set. This causes the third party device to show it as being in alarm. Resolution From v3.0, EcoStruxure Building Operation is BACnet standard at protocol revision 14 so this is not an issue. The text below was written for earlier versions and is valid for v2.0 and earlier. It is not possible to disable the evaluation of intrinsic alarming on BACnet points (which updates the status flags and event state properties). Not updating status flags and event state (according to the alarm-value) was identified by the BACnet Test Lab as a compliance issue with the BACnet standard at protocol revision 6 – the revision SBO implements. The essence of the issue is that we are not allowed to have the intrinsic alarming properties, but not use them – updating the object state according to its configuration. The feature to disable intrinsic alarming (an alarm disable property) was introduced at a more advanced protocol revision (13), which is not currently not available for SmartStruxure. A possible workaround for the issue, if the value periodically changes between active and inactive: set the time-delay (which is measured in seconds) to a large value. If the delay is longer than the amount of time the value spends in what would be the alarm state, then evaluation is avoided. A value of 32,000,000 for example delays evaluation for a little more than a year. NOTE - make sure to set the time delay while status flag in-alarm is false, and event-state is normal, otherwise it would take a year to get out of the alarm state.

Issue After upgrading to version 1.7.1 or later, a performance issue is seen when reading BACnet values from BACnet/IP devices. The CPU usage on an Automation Server is continuously high. Product Line EcoStruxure Building Operation Environment Detected in version 1.7.1 Automation Server Enterprise Server BACnet/IP Cause A new "BACnet ReadPropertyMultiple Service" has been included from version 1.7.1. Data retrieval from devices that support ReadPropertyMultiple service and do not support the COV (Change of Value) service has been optimized. The resulting improved polling behaviour will particularly benefit graphics performance for ReadPropertyMultiple. If a site is upgraded to version 1.7.1 where this improved communication service gets used automatically, it is possible that the server CPU usage increases. This issue will only be seen if the third party device does not support COV subscriptions, does support ReadPropertyMultiple and a large number of values are being requested from the same device e.g. using bindings. This is a result of much more data being requested by the Server in the same time period.  From Release Notes version 1.7.1 3.4.4 Improved polling performance Data retrieval from devices that support ReadPropertyMultiple service and do not support the COV (Change of Value) service has been optimized. The resulting improved polling behavior will particularly benefit graphics performance for ReadPropertyMultiple.” Resolution Select the BACnet interface where the performance issue is seen Select the advanced properties for the interface Change the “Minimum polling interval for local IP networks (ms) to “3000” In case the BACnet interface is configured in an Automation Server, test other values in step 3 until the CPU usage is stabilized You can check the AS CPU usage, by dragging the CPU usage property to the watch window in WorkStation NOTE It is also worth setting the MSTP polling to 3000mS, to ensure third party BACnet Devices that do not support COV subscriptions, are not overloaded. Without this value set, it has occasionally been seen that Bacnet devices go offline or value readings stop updating the values.

Issue When connecting the RoamIO-2 service tool directly to a standalone BACnet b3 controller which is not connected to the MSTP network yet, the RoamIO-2 does not show the b3 controller on the screen. Environment RoamIO-2 Continuum SmartStruxure BACnet b3 controller Cause By default, the View option of the ROAMIO2 Bacnet Service Tool is set to view "By Network".  Resolution Connect the RoamIO2 service tool directly to the b3's service port. Launch the BACnet Service Tool and in the 'View' menu de-select 'By Networks' and 'BACnet Only' menu entries. Click the green icon to connect. Now, it will show the b3 controller in the service tool.

Issue When logging in via WorkStation all is fine, but logging in via WebStation shows a blank initial screen (see below). Environment WebStation Cause The system has been configured with a user defined default workspace. The default workspace contains an 'ampersand (&)' in the name. Resolution Apply hot fix 1.6.1.28100 or remove the ampersand character from the workspace's name. NOTE: This issue exists in all versions of StruxureWare Building Operation prior to 1.8, as of the writing of this article only 1.6.1 had a hot fix available to solve the problem. The issue has been resolved in StruxureWare Building Operation version 1.8

Issue Unable to use a Feature of Power Monitoring Expert due to license limitation.    Environment Power Manager Power Monitoring Expert Cause Open the PME Management console Select Help>About You should see the active License Modules as shown below. You may or may not also see additional features that are part of the 90 day trial.   Resolution Contact your sales representative to purchase the additional licenses