Building Automation Knowledge Base

Issue StatusBackup "State" system variable is not able to be manually changed and attempting to set this variable to Enabled produces a script error instead of resetting the flash circuit breaker. Product Line EcoStruxure Building Operation Environment Building Operation v1.8 and below. b3/i2 Controllers Cause Feature to reset flash circuit breaker was not implemented in the earlier versions of Building Operation Resolution A new feature to reset the flash circuit breaker was implemented in Building Operation v1.9 to address this issue. The b3 BACnet Device Memory on-line help topic shows how this is manually reset from the WorkStation in the Device menu.

Issue Point under the Application folder of MP-x device shows error "Contains unresolved BACnet reference" Product Line EcoStruxure Building Operation Environment Building Operation Multi-purpose Controller Building Operation Multi-purpose VAV Building Operation IP-IO Cause Incomplete entry in point's BACnet priority array. The screenshot below shows the XML file obtained from exporting the point, as it can be seen, 'Priority16' is missing the 'Type' section. Resolution Perform the following steps to correct the problem: Export the point out to a file. Delete the point. Import the file created at step 1, once the point has been re-created via import the unresolved error is gone. NOTE: There is no need to make any modifications to the XML file, it can be imported as is, the system will automatically correct the incomplete entry for priority16.

Issue The path to the templates and libraries is not documented Product Line EcoStruxure Building Operation, TAC Vista Environment Graphics editor Cause In order to use your own color and gradient templates and to copy component and snippet libraries you need to know the path to these files and folders. Components and snippets can preferably be managed directly through the graphics editor. Resolution In TAC Vista The libraries and templates are one and the same for all users: Colors and gradients: C:\ProgramData\TAC Graphics Editor\Brushes Components: C:\ProgramData\TAC Graphics Editor\Components Snippets: C:\ProgramData\TAC Graphics Editor\Snippets In SmartStruxure Each user has their own set of libraries and templates: Colors and gradients: C:\Users\%username%\Documents\StruxureWare\Graphics Editor\Brushes Components: C:\Users\%username%\Documents\StruxureWare\Graphics Editor\Components Snippets: C:\Users\%username%\Documents\StruxureWare\Graphics Editor\Snippets

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 Services for assistance. Issue The database files used by the WebReports SQL database need to be moved to another location. Product Line EcoStruxure Building Operation Environment WebReports SQL Server Cause There are numerous reason for wanting to do this, but the most common reason is that there is not enough space on the disk where the WebReports databases are located. By moving to another disk this will allow space for future expansion. Note that this article only describes how to move the database files to another harddrive. The SQL server and database files must still be on the same PC where WebReports is installed. Resolution To move the database files, follow this process: Start by backing up everything. Stop the reporting agent service (name: ReportingAgentService). Open SQL Server Management Studio and locate the database. Right-click on the database and select Tasks-->Detach. Locate the SQL database files (*.mdf and *.ldf) in Windows explorer. Cut or copy these files and move them to the desired location. Go back to SQL Management Studio and select the Databases folder. Right-click and select Tasks-->Attach database. When the dialogue opens up, locate the 'ADD' button and click on it. Browse to the database files' new location and click on OK. Restart the reporting agent service.

Issue When attempting to add an Automation Server to an Enterprise Server, an error message "Log on temporarily disabled' is displayed. The operation fails and the Automation Server is not added to the ES. Error message displayed on version 1.8 Product Line EcoStruxure Building Operation Environment Building Operation Enterprise Server Building Operation Workstation Building Operation Automation Server (AS, AS-P or AS-B) All of the above version 1.9 or earlier Cause This only occurs after an initial failed attempt to add a server to the Enterprise Server. On each subsequent attempt to add the server, it always tries to authorize to the server with the admin account's default credentials, which in most cases are no longer valid. This locks the admin account. So when the admin account has been locked initially, it will not be unlocked, as every time an attempt is made to add the server, the default admin credentials are being used, and therefore it fails. Normally a locked account is a temporary condition, but in this case it is never recovered. This problem occurs on version 1.9 or earlier. It was fixed in version 2.0. Resolution The current workaround to allow the SmartStruxure Server Device to be added to the Enterprise Server is to perform a Warm Start or by cycling the power on the device. Upgrade to version 2.0 or later to resolve the issue permanently.

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 When trying to add a SmartX server to an ES, or when trying to rename an ES, you see the following error message: "All subserver must be online at least once before adding" Product Line EcoStruxure Building Operation Environment Building Operation Enterprise Server (version 2.0 or later) Cause This issue is caused by a mismatch between the content in the folders called MountPoints and Versions in the ES database folder. Resolution Before doing this make sure you have a good backup of the ES database. Identify and delete the files in the ES database folder called Versions which don't have representation in the ES database folder called MountPoints. The files have the same GUID-name in both folders, but not the same content, so you cannot copy paste between the folders. It requires a manual comparison. Procedure to identify files to remove (for version 2.0): 1. Check files in C:\ProgramData\Schneider Electric EcoStruxure\Building Operation 2.0\Enterprise Server\db\System\MountPoints 2. Check files in C:\ProgramData\Schneider Electric EcoStruxure\Building Operation 2.0\Enterprise Server\db\System\Versions 3. In Versions only remove the files which don't have a representation in MountPoints. Comparing the files in MountPoints (1) to the ones in Versions (2 & 3). Here they are identical and all is OK.

Issue There is a performance issue affecting the Infinet bus under an AS-P. Product Line EcoStruxure Building Operation Environment Building Operation Workstation Building Operation Automation Server Premium Cause Product Support has requested a Trace log with increased reporting for use in troubleshooting the Infinet bus.  Resolution 1. Under the System Tree in Workstation, expand the Modules folder.        2. In the Module folder, under the Trace folder expand the Loggers folder.   3. Under Loggers, navigate to the following modules. nsp.pin.BACnet.Continuum nsp.BACnet.Continuum (EBO versions 2.0 and below only). 4.  Right click on each module to expose the module Properties and increase the reporting level to Trace.     5. Just below the Loggers folder, right click on the Trace Settings folder.   6. In the context menu under Trace Settings, select Get trace log.     The Trace log will appear as a text file in a text editor.  Save the log to an appropriate folder.   Be sure to return the reporting level on all modules to Information once you are finished gathering the logs.   Leaving the reporting level at Trace will fill up the Trace logs with Infinet log entries leaving very little room for anything else. 

Issue Example graphics components required Product Line EcoStruxure Building Operation Environment TGML - Building Operation Graphics Editor Cause No standard graphics or components are supplied within the product. Resolution A Standard graphic component library can be downloaded from the Buildings Download Center. This consists of a number of Component Libraries that can be installed on a Workstation by double clicking on each one. In your TGML Editor, Right click in the Components window and select "Categories" you can then select the categories you require to see in your components section. There are also a lot of standard Snippets that have been developed by users around the world, these are available to download from the EcoStruxure Building Operation Forum - Graphics Exchange.

Issue User Permissions Path needed to be modified to reflect the renaming of Server, Folder and Object Names. Product Line EcoStruxure Building Operation Environment Building Operation Enterprise Server  Building Operation Automation Server Premium Cause Following the renaming of a server (or Folder or Object), a User has different access to the system via WorkStation or WebStation. This may be no access to a server and new access to a server. The changes seen by the user will depend on the Permissions set for the Group or User. The Permissions are not updated in line with renaming of Servers/Folders/Objects. Resolution Following any changes to Servers/Folders/Objects, all the User and Group Permissions should be checked and corrected as required. See WebHelp for extra details

Issue License Administrator does not operate as expected Product Line EcoStruxure Building Operation Environment Building Operation Licenses Administrator Cause This program is not designed to operate as a 64-bit program.  In Windows, you have 2 folders for program installation. One is called Program Files and one is called Program Files(x86). The folder Program Files(x86) is used for 32-bit program. Resolution Make sure the license server is installed under Program Files (x86)

Issue TGML graphics to display "OFF" and "ON" instead of "0" and "1" Product Line EcoStruxure Building Operation, TAC Vista Environment TGML Graphics Editor Cause Data in the Vista database is stored as 0,1 but may be displayed using paired texts. Those paired texts can be set to show up on the graphic, or a unique conversion can take place in TGML. Resolution If you use default snippets that come provided with the editor, you have the option of displaying a value with either NumericPresentation or TextPresentation. The only real difference between the two is that TextPresentation defines the binding's behavior format as "Presentation" rather than "None." This will only display built in presentation formats -- an alarm state will show up as "Alarm" or "Normal" -- or if you've defined paired text within a binary point in the Vista database, that will show up instead of (0,1). This does not, however, explicitly give you the option from within the Graphics Editor to convert decimal values into text. The example TGML code below describes how to take a value that is showing up as "0" and "1" and make it read instead as "OFF" and "ON." <Text>Value   <Bind Attribute="Content" Name="Value">     <ConvertValue SignalEqualTo="0" AttributeValue="OFF"/>     <ConvertValue SignalEqualTo="1" AttributeValue="ON"/>   </Bind> </Text> Cut and paste this TGML code into the editor's Source view to view it in the editor. Just be sure to paste it between the opening tag and closing tag. If all you see in the Source view is one self-closing tag, that is because the page is empty. Either add separate opening and closing tags, or go back to Design view and add one object to the page to automatically split them.You can see here that a Text object has a binding associated with it. That binding's target attribute is "Content" because this will alter the content of the Text. (We could also change the text's stroke color, background color, font size, position on the page, etc., by changing our binding's target attribute.) ConvertValues underneath the binding tell the binding how to alter the Text's content. A SignalEqualTo 0 will write "OFF" to the content and a SignalEqualTo 1 will write "ON" to the content. The number of ConvertValues is not limited to only two. There could be a third one to say that a value of 2 should read "STANDBY."

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 When you attempt to save a Menta application in Workstation you will get an "Invalid Data" Error. Product Line EcoStruxure Building Operation Environment Building Operation Workstation Building Operation Menta Editor Cause Some public variable in the Menta application has had Initial bindings added that conflict with the EBO bindings. Resolution Remove the Initial bindings from the variables in the Menta application and use EBO bindings. To find these Initial bindings follow these steps, Edit the Menta device with the issue From the File Menu "export" the Menta application to a known location on the PC and save it as a MTA file. Browse to this MTA file you exported and open this file with the Menta Editor From the File menu select "Save as" option. Give the file a name and in the Save as Type select FDB (*.AUT) Using Note Pad++ edit the AUT file you just created. Search the AUT file for the label "InitialBindings" [see Figure1 below] Make a note of the objects with Initial bindings so the initial bindings can be deleted from the Menta file. In Workstation edit the Menta device and remove the initial bindings from the objects found in step 7 and change the name of the object noting the original name down. Save the Menta application to the server. In Workstation edit the same Menta device and rename the object back to the noted name in step 8. Save the Menta application.

Issue BACnet String Value Object or BACnet DateTime Value Object in EcoStruxure Building Operation cannot be created. Only the EcoStruxure Object is created. Product Line EcoStruxure Building Operation Environment Building Operation Automation Server Premium Building Operation Enterprise Server Building Operation Multi-purpose Controller (MP-X) Building Operation Room Controller (RP-C) Building Operation IP-IO Cause Only EcoStruxure String Value Object or DateTime Value Objects can be created under the Servers, even if created under the BACnet/Application Folder. There are no current plans to change this. MP-X, RP-C are native BACnet devices so BACnet String Value Object and BACnet DateTime Value Object can be created. Resolution BACnet String Value Object or BACnet DateTime Value Object can be read and hosted by all versions of EcoStruxure Building Operation, but not created in the Server

Issue When a user logs on to Workstation and accesses the hyperlink, the website is displayed without prompt for login credentials Product Line EcoStruxure Building Operation Environment Building Operation Workstation Microsoft Internet Explorer Cause EcoStruxure Building Operation software uses Microsoft Internet Explorer to present web pages. How the page logs on is an IE function and not a function of EBO Workstation Resolution  Log off from the web site before logging off from Workstation  Configure Internet Explorer to delete browsing history on exit Go to Internet Explorer settings and then the Internet Options On the General tab, under the Browsing history, enable the checkbox for 'Delete browsing history on exit' (computer restart may be required)

Issue A temperature input on one device is referenced in an external binding, e.g. a consumer value, in another (BACnet) device. The value on the consumer side is incorrect and seems to have been converted from Fahrenheit to Celsius although the units all show Fahrenheit. Product Line EcoStruxure Building Operation Environment Building Operation Workstation Building Operation Automation Server (Premium) Building Operation Enterprise Server / Enterprise Central BACnet Device(s) supporting external binding (e.g. MP-X or IP-IO) Cause The probable cause is that the value of the temperature input is not configured to a specific unit. This means that the unit is decided by the electrical type of the thermistor. In most cases this is Temperature °C, which means that the values are stored in °C, and this is the value being transferred in the consumer binding. If the measurement system in Workstation is set to United States Customary Units (US), the input value will be displayed in Fahrenheit (°F) and one might think that the unit of the temperature input value is also configured to Fahrenheit, when in reality it is in Celsius. In this situation the value on the consumer side is in Celsius as it has no information about units. Furthermore, if the consumer value unit is configured to Fahrenheit, then we have the situation shown in the screenshot above. Resolution Start by changing measurement system in Workstation to As configured in object. (Refer to the Webhelp for more information about how to do this.) By doing this the values will be displayed unconverted. It is now clear that the temperature input in reality is in Celsius. The next step is to configure the input unit to Fahrenheit. Open up Properties for the Temperature input and click the gear wheel next to Value to configure. Check the box to the left of Unit and click the button with the three dots to the right. Select °F and click Select Click OK to confirm the changes in both open windows. Both the temperature input and the consumer value will now be displaying the correct value in Fahrenheit.

Issue Most systems have an Overview Graphic of the whole building.  The user then navigates from this graphic to specific floors and rooms of interest. If the Workspace is configured incorrectly, navigating to a newly selected graphic does not work as expected. The overview graphic does not disappear and the new graphic is forced to open very small at the edge of the screen. Product Line Building Operation Enterprise Server Environment Workspaces Cause The standard Administration and Engineering Workspaces used in EBO contain a Work Area Window (WAW) which is necessary 'space' to show a selected graphic/trend/schedule If an Overview Graphic Pane is created in a Customer Workspace and this graphic takes up most of the screen, there is no space left to show the new object which the customer wishes to see Note: The Overview Graphic 'Building' is now shown in a Graphic Viewer only   When the system tries to open a new graphic, there is not space to open it in, The graphic is forced to open at the very edge of the screen and is therefore very small. Resolution General information about creating and using Graphic Panes, Work Area Windows and Panel Components can be found in the EBO webhelp, But for specific information on how to prevent a graphic opening at the edge of the screen see below.  Rather than adding a Graphic Pane to the Workspace to show the Overview Graphic add a Work Area Window (WAW) instead. Next, define the required Overview graphic as the initial path for the WAW on startup so the Overview graphic opens at user log on. Note: The Overview graphic 'Building' is now shown in the WAW rather than the Graphic Viewer. Graphics will always close themselves on navigation to the next object by default when used with a WAW (this can be changed). As soon as the user needs to navigate away from the overview page to a new graphic/schedule/trend, the system can use the WAW which will then use most of the screen as the 'space' to show it. In this case, as soon as the link to the next graphic 'Floor' is pressed, the first graphic 'Building' closes according to its default and the new object is shown in its place.

Issue Cannot use the Hall Effect Sensor object under the Onboard IO of an MP-X   Product Line EcoStruxure Building Operation Environment Building Operation Workstation Building Operation Multi-purpose VAV Cause The object is an internal sensor for measuring the position of the actuator. Resolution The hall Effect Sensor Object is not an user configurable object.

Issue Clicking a graphic page link fails to open any graphic page, but when opening the path using the System Tree of the server that contains the graphic page, successfully allows the link to open the graphic page. When opening the same page using WebStation, the graphic pages all open successfully. Product Line EcoStruxure Building Operation Environment Building Operation WorkStation 1.9.x or below. Cause Typically having 'dead links' or unresolved binds in any graphic page is the reason for the issue. WorkStation pre-loads all objects of the references to the graphics. This call (CSP GetObjects) fails since (at least) one path of the objects points to a server that does not exist. Unfortunately the protocol can't return the objects that do exist and WorkStation then marks all these objects as non-existent and fails to open the respective binding. This operation cannot be corrected in this version of WorkStation and requires an upgrade to 2.x or above to correct this. Resolution Two options are available Correct/remove all link bindings that are shown with unresolved references to invalid server paths. Example showing an Unresolved Binding Upgrading to Building Operation 2.0 or higher will also resolve this issue.

Issue In Function Block Editor, it is possible to define units for function blocks, and these units can only be set to basic units. There is no way to add a metric prefix to the unit. For example W or Wh can be used, but it is not possible to define kW, MW or kWh, MWh. Unit configuration in Function Block Editor v. 1.8 Product Line EcoStruxure Building Operation Environment Building Operation Workstation version 1.8 or earlier Cause Metric prefixes are not implemented for function blocks in Building Operation version 1.8 or earlier. Resolution Upgrade EcoStruxure Building Operation to version 1.9 or later. When editing a function block In Function Block Editor click Select unit and choose unit and Prefix. Function block with prefix in v. 3.0

Issue Monitoring duct temperature on a Xenta 102-AX without putting it into Morning Warmup (Central Plant Heat) mode Environment Xenta 102-AX Cause The Xenta 102-AX Plug-in allows you to configure the hardware inputs for several different purposes.  If you configure Universal Input 1 as a duct temperature, that is assuming duct inlet temperature.  Any time the duct inlet temperature is higher than the room temperature (suggesting that central plant heat is being provided by the air handler) the action of the damper will reverse and the box will show HVAC_MRNG_WARMUP as its application mode.  If it is really the duct reheat outlet temperature that is being measured, this could be an undesirable result. Resolution There are two options to read in a duct temperature without it affecting the internal logic of the Xenta 102-AX.  The recommended method is: Connect the temperature sensor to Universal Input 1. Configure the Xenta 102-AX Plug-in, Hardware Configuration, Input 1 Section to "None." This will continue to report the temperature on UnivIn1_Sense.nvoAuxTemp1 but will not affect the internal logic of the controller. The other option is: Connect the temperature sensor to Universal Input 3. Configure the Xenta 102-AX Plug-in, Hardware Configuration, Input 3 Selection to "OA Temp. Sensor." This will report the temperature on UnivIn3_Sense.nvoAuxTemp2 but will not affect the internal logic of the controller.