Building Automation Knowledge Base

Issue Adjusting the setpoint from the SXWSC3XSELXX device. Product Line EcoStruxure Building Operation Environment Building Operation SmartX Living Space Sensor. Cause SXWSC3XSELXX has plus and minus buttons that could be used for changing setpoint. Resolution Navigate in the System Tree to the Display entry for the SmartX Sensor. Go to the Button and Scene Configuration tab under Properties. Scroll down to Front Menu Button Configuration, change Button 1 function to Change temperature setpoint. Select the tab Advanced, and scroll down to the Feature Control Settings. Set Allow setpoint changes to On. Set max and min limits for the setpoint under Setpoint high limit an Setpoint low limit.   When the plus or minus button is pressed, the Setpoint will change in steps. The size of the steps depends on the difference between the Setpoint high limit and low limit, divided by 10 (when using SI units). In the example above, the difference  between the Setpoint high limit and low limit is 28-18 = 10, so the Setpoint will be changed in step of 1 degree C.  

Issue Is there any limitation for the number of local program variables that can be declared in a script program located in ExoStruxure BMS servers or BACnet/IP controllers?   Product Line EcoStruxure Building Operation Environment Building Operation Enterprise Server Building Operation Automation Server Building Operation Automation Server Premium Building Operation Automation Server Bundled Building Operation Multi-purpose Controller Building Operation Multi-purpose VAV Building Operation Room Controller (RPC) 24 V Cause A script program has a lot of variables declared. Resolution There are no hard limits imposed by the script compiler. for the number of local program variables. The limits are performance and device resources. The bigger a program is, the more memory and processor bandwidth it will consume and the longer it will take to execute. 

Issue The sequence numbers for Alarm Events are changing daily for all active alarms in the system. This can be a problem for applications using sequence number as alarm identifier. Product Line EcoStruxure Building Operation Environment Building Operation Enterprise Server. Building Operation Automation Server Premium Cause Every night there is a cleanup in the alarm table and alarms can then get new sequence numbers. Every night historic updates with old time stamps are removed in the alarm table.   When this cleanup takes place, there is a reorganization of sequence numbers of current alarms. They all get a new sequence number.   The new sequence numbers are always higher than the latest sequence number before the cleanup. Resolution Do not use alarm sequence number for alarm identifier, use triggered time stamp instead.

Issue There is no information on how to create and prepare signed certificates for import in Building Operation. PEM file format has to be used. If another format is used or the certificate files are not correct, you get a message like this when importing SAXParseException: Reference to invalid character number in line X column Y Product Line EcoStruxure Building Operation Environment Certificates Cause There is no information on how to create signed certificates in Building Operation. Resolution Make sure that when preparing the pfx file that the full chain of trust is included in the pfx file. You have various options when preparing a pfx certificate export file, and the private keys and chain of trust are options that must be selected. Otherwise, you won't extract the intermediate certificate or the private key if not included. Complete a Certificate Request and then request a certificate in PEM format in a .pfx file "container".  Extract the CA certificate, Intermediate certificate, and private key using the following OpenSSL commands. After executing each command, enter the password if prompted. Make sure you reference the right pfx file. Below filename.pfx is used as an example Make sure you enter the commands manually and do not copy/paste from this article Download OpenSSL tool here or use OpenSSL installed with EBO  openssl pkcs12 -in filename.pfx -out host.pem -nodes -clcerts -nokeys openssl pkcs12 -in filename.pfx -out inter.pem -nodes -cacerts -nokeys openssl pkcs12 -in filename.pfx -out privkey.prv -nodes -nocerts The three files produced must then be parsed of any characters that aren't in the part of the certificate/key and in PEM format (or PRV if private key) - basically all the characters before "-----Begin Certificate-----" or after "-----End Certificate-----". Ensure each file ends with a blank line and that a blank line separates each section. This can be done in any text editor; however, this example uses Notepad++ with the "Show All Characters" button selected.  Import the files into SBO using the certificate manager in the Control panel. File type conversion If the host and intermediate certificate are in crt, cer or der format, you can convert them to pem format using the following method/command: openssl x509 -outform der -in certificate.cer -out certificate.der openssl x509 -inform der -in certificate.der -out certificate.pem Replace "certificate.cer" with the name of your file Determining certificate file type To determine which filetype a given certificate file has (PEM, DER, or pkcs12/pfx), you can use the following commands (replace "cert.crt" with the name of your file). A valid output will confirm the file type. PEM openssl x509 -in cert.crt -text DER openssl x509 -in cert.crt -inform DER -text pkcs12/pfx openssl pkcs12 -in cert.crt -info

Issue When using Project Configuration Tool (PCT) in Server mode and connecting from a remote PCT client, it is not possible to transfer backups or exports. The transfer gets stuck, and a complete reboot is required to start using the project again. Product Line EcoStruxure Building Operation Environment Building Operation Project Configuration Tool (PCT) Cause In the "Settings for Project Configuration Tool" the Notification and Listening port defaults to 0. Port 0 means that PCT will ask the OS for an available port. But if network policies prevent PCT from communicating using that port, PCT cannot detect that.  Resolution In "Settings for Project Configuration Tool" Change the port number for the Notification port and Listening port to a port that is available to use.

Issue In TAC Vista, we had a function for the OGC graphics called standard graphic. Do we have something similar in Building Operation? Product Line EcoStuxure Building Operation Environment Building Operation 2.0 and above Graphics  Cause All graphics connected to the standard graphic in TAC Vista changed if the standard graphic was changed. This is a very useful function when having many similar graphics.    In Building Operation, a new object was implemented in version 1.8 labeled shared Graphics, Custom Types superseded this in version 2.0, and this function is similar to shared Graphics but not identical. Resolution There is no direct function like this in Building Operation.  Custom Types is the only similar feature available in the currently supported versions of Building Operation. Additional information can be viewed in the online help topic Custom Types Overview.  

Issue How to configure two room sensors in ZBuilder. Product Line EcoStruxure Building Operation Environment ZBuilder Cause It is possible to configure TAC Xenta 121 or TAC Xenta 122 to use two room sensors via the ZBuilder tool. Resolution In Zbuilder, under the tab Configuration, under Room unit, select the type of sensor you are going to use. Select the tab I/O Setup,  Right click on the sensor and select Duplicate. Move the sensors to the input you are going to use.   At the end of this session you will be able to: Configure TAC Xenta 121/122 to use two room sensors. Understand that the nvoSpaceTemp value is calculated as average value of the two sensors. Understand that it is not possible to see the actual value of a single sensor when using two sensors.    

Issue Extended Logs have stopped updating on the Enterprise Server. Product Line EcoStruxure Building Operation Environment Extended Trend Logs Cause Extended Trend logs have been set up on the site for some time and have operated correctly. Now some of them have stopped updating.  Resolution This issue can be caused by a Server backup being restored. Trend logs and Extended Trend logs are allocated sequence numbers, and if the sequence numbers do not follow the correct sequence, the Extended Trend log may not update. To confirm that this is the issue; Trend Log. Navigate to the Trend log and open it in a "Trend Log List" view. Add an additional column to show the Sequence number. Note the highest sequence number used. Extended Trend Log. Navigate to the Extended Trend log that is referencing the above Trend Log. Open it in a Extended Trend Log properties. Press and hold down the "ALT" key and click where the dot is indicated on the screen shot below, (just below the Basic tab).       This will show some more properties for the Extended Trend Log, the one you are interested in is “Last transferred sequence number”.   If the last transferred sequence number on the Extended Trend Log is higher than the Trend log’s highest sequence number, then that is why the Extended Trend Log has stopped. How can this issue be resolved? Increase the sample interval of the Trend log until it has caught up. The Extended Trend Log will only fetch new records that has a sequence number higher than the last transferred sequence number. So until the sequence has caught up, you will not see any new records in the Extended Trend Log, and only records created after you have caught up in sequence numbers will be fetched. Re-create the Extended Trend Log. The new Extended Trend Log will fetch every record the log has and continue from there, but you will lose the records the old Extended Trend Log had that the log does not have anymore. Backup / restore on the AS. The Trend log will be cleared but the Extended Trend Log will start fetching new records.    

Issue Is it possible to let the ES directly write the write to file notification into the Windows event database? Is there a rotation for the Write To File Notification file so that a new file is written when the file is bigger than xMB?   Product Line EcoStruxure Building Operation  Environment EcoStruxure Building Operation - ES Cause Write to file notification can only be written to a file in the "db / notifications" folder on the server where the notification object is located. Unfortunately there is no rotation either. Resolution At this time it is not possible for an Enterprise Server to write directly to the Write to File notification in the Windows event database. There is also no rotation for the Write to File notification file so that a new file is written when the file is bigger than xMB.

Issue 3rd party BACnet device can send a reinitialize device request to an EBO server. Product Line EcoStruxure Building Operation Environment Building Operation Automation Server Building Operation Automation Server Premium Building Operation Automation Server Bundled Building Operation Enterprise Server Cause EBO servers support the "ReinitializeDevice-B" Bacnet device management service. This allows BACnet clients, such as BACnet browsers or operator WorkStations, to initiate ReinitializeDevice requests, i.e. Warm Start or Cold Start. Resolution EBO currently does not support passwords for the ReInitializeDevice service. It is possible to create a whitelist for the EBO server and exclude a 3rd party BACnet device from that list, but this will block all communication with the 3rd party BACnet device.

Issue When changing values like Check-in interval (s) under Poll Control for Zigbee device SED-MTH-G-5045, the value seams not to have been change when opening the dialog again. Product Line EcoStruxure Building Operation. Environment Building Operation Automation Server Premium (AS-P) Building Operation Room Controller (RP-C) non-Greenpower sensors SED-MTH-G-5045 Cause Setting is sent to the sensor only once every tenth minute. Resolution Open the dialog box again after 10 minutes to verify your changes.

Issue Using Download Wizard 32 with Application set to Clear Memory, one will get an error that "The application file could not be found! Product Line EcoStruxure Building Operation Environment Building Operation Workstation Xenta Programmable Controller Cause EBO Workstation does not include the Lonm<Model Number>.MTA file. Resolution There are two solutions: Create a minimal MTA file for the device type. Open Menta Editor Change the device specification for the appropriate Xenta Type. Add one PVR block Save the file. In DWiz, change Application selection to Download New and Browse in the new file. Perform the steps again with the expected files in the same folder as DWiz. Download the attached Lonm.zip (derived from Menta 5.1.9) Extract the files in the zip to the same Workstation folder where Dwiz.exe is found. Sample Location: "C:\Program Files (x86)\Schneider Electric EcoStruxure\Building Operation 3.2\WorkStation\DWiz.exe" Perform the download again with the same Clear Memory selection under the Application section.

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 Correcting failed links between programming objects after upgrading files from .vsd to .vsdx Product Line TAC IA Series, EcoStruxure Building Operation Environment I/A Series WorkPlace Tech Building Operation Workstation (WorkPlace Tech Editor) Cause After existing .vsd files from pre-WorkPlace Tech 5.10 versions can have corrupted links that stay red when programming objects are added or modified. Resolution This video demonstrates how to correct binding failures that can occur when existing Visio drawings are converted from .vsd to .vsdx format when upgrading to Workplace Tech 5.10 and EBO 4.0 and newer WorkPlace Tech Editor. Note: The objects in the original drawing will no longer show a Master Shape reference (below) The frame around the object appears a little different as well.  The Mega Master will not be changed so this has no effect on the performance of these objects.

Issue Receive error "Property value out of range" when creating a BACnet interface on the Enterprise Server   Following problems after upgrading SmartStruxure servers to 1.5: Attaching an Automation Server to or detaching it from an Enterprise Server will fail with “Property value out of range” error. Changes to the ~/System/Interface Manager/BACnet fail to be propagated lead-shadow functions through to the child servers. Automation Server controllers dropping offline following an upgrade to 1.5 (BACnet command priority related  also may see numerous "Changeset Rollback errors") Product Line StruxureWare Building Operation 1.1, 1.2, 1.4, 1.5 and above Environment Enterprise Server (ES) BACnet IP Interface Windows XP, Windows 7 and Windows Server 2008 R2 Cause Their may be various items that generate this error, checking the Enterprise Server (ES) system log in the Software Administrator may assist in pin pointing the error.  If you see an error that ends with ~/BACnet Interface/IP Network, then this error is generated when their is no valid IP Network.  For SmartStruxure 1.5 or above or planning to upgrade from 1.4 to 1.5 (and above)  This issue only occurs if a BACnet interface is used and the site has changed the BACnet "Default Priority Level" from the default value of 16, to 8 or a smaller numeric value in the Automation Server while running in V1.4. The "Property value out of range" message relates to the new Force priority level in 1.5 and the Default priority level in 1.4.1 being mismatched. Resolution The ES must be connected to an IP network. To resolve this error follow these steps: Close all Workstations (if running) Connect the Enterprise Server to a valid IP network (with a valid IP address). Stop and Restart the Enterprise Server service through the Software Administrator application. This should now allow the BACnet Interface to be created successfully For SmartStruxure 1.5 or above or planning to upgrade from 1.4 to 1.5 (and above) Please refer to TPA-SBO-14-0005.00 Before upgrading to 1.5 make sure the "Default Priority Level" within the Automation Server is set to 9 or higher.  If the system has been upgraded with the incorrect values, then: If the site uses single servers, or the ES/AS communication still operates correctly, then this can be corrected by changing the setting in both the AS and the ES to a value of 9 or higher.   If after upgrading a multi server configuration and the AS does not stay online, then a Hotfix can be used fix the problem using the following steps: Apply the hot fix #1.5.0.4301; available from Product Support Services Fix the multi-server (by detaching/re-attaching the servers) Correct the two properties (AS and ES). WARNING: It is essential for any BACnet system at 1.5 or later that the "Default Priority Level" must have a larger numeric value than the "Force Priority Level, otherwise some BACnet functions may not behave as expected. Note: This also applies even if the hot fix has been installed. The effects of not setting the Default above the Force Priority level are: If Force Priority Level is equal to the Default Priority Level: Changing the Value of a BACnet value or a BACnet output object will cause the Value to appear Forced. This applies to the BACnet objects in both SmartStruxure servers and those in 3rd party BACnet devices.   If Force Priority Level has a larger numeric value than the Default Priority Level: Changing the Value of objects mentioned above will cause the Priority Override icon overlay to be turned on next to the Value property in the WorkStation’s property grid.   

Issue Steps on how to setup BACnet Time Synchronization to 3rd Party BACnet controllers. Product Line EcoStruxure Building Opertaion Environment SmartX Enterprise Server (ES) SmartX Automation Server (AS) BACnet Cause It is not always clear what is required to setup BACnet Time Synchronization and how to confirm that EcoStruxure Building Operation is actually performing it properly. Resolution To use the Time Synchronisation you will need to bring the 3rd Party BACnet device (Eg. Continuum bCX) under the EBO BACnet Interface -> IP Network: Go to the BACnet Interface Time Synchronization Recipients Tab. Add a new Local time synchronization recipient with the '+' button. Select recipient type as 'reference' In the Recipient device object reference field browse for your BACnet Device. Press OK and then save the changes. Right-click on the BACnet Interface and select send time sync now. This will send out an unconfirmed-req TimeSynchronization to that specific Device only.   Test Scenario with a bCX setup as a third-party BACnet controller You will see a unconfirmed-req TimeSynchronization packet being sent from the ES in WireShark but with no response from the bCX.  You may not see responses back from other 3rd party devices. The time in the bCX should be seen to change from within Continuum, (assuming it was incorrect in the first place) 

Issue Removing software from a PC may leave behind unused / old registry entries and folders from the removed software, this in some cases may prevent software re-installation Product Line Andover Continuum,EcoStruxure Building Operation,Satchwell BAS & Sigma,Satchwell MicroNet,TAC INET,TAC Vista Environment All supported Operating Systems Cause This is due to the windows uninstall program not fully removing all elements for the software. Some of this is due to windows thinking the the software may have been removed unintentionally and therefor all the previous settings will still be saved in case of  re-installation. For example, when SQL is uninstalled the program folders that contain the database will remain intact. This may be an issue if, for example, the software is removed due to a problem with the original installation. This is when a complete removal off all components and registry entries may be needed. Resolution The best solution for removing all the unused registry entries is to use a program designed to remove obsolete registry entries and temporary files. Some examples of these are: CCleaner, which will allow you to clean up your PC by removing past installation components. Revo Uninstaller  which is useful for removing redundant folders / files / Registry entries.   It may be useful to use both of these programs to ensure a complete cleanup. Revo Uninstaller can be used to remove unused software and then CCleaner to get rid of all the Temp files etc.  Finally remove the relevant folders from within the windows explorer, Example: C:\Program Files (x86)\Continuum Once done you should then be able to install a fresh clean copy of the application software. This solution is current in all versions of Windows including windows 10  

Issue Are there drawing templates available for AS’s, modules, RPC etc for use in BMS wiring diagrams. Product Line EcoStruxure Building Operation Environment Building Operation equipment Cause Need for CAD drawings of PS, AS, or I/O Modules Resolution Drawings in AutoCAD format (DWG, DXF) are available on the EcoXpert Extranet. DXF files are able to be imported into Visio.

Issue Current information will be stored and updated in release notes and online documentation. Compatibility Matrix of Operating Systems, Video, Product Announcements, SQL Compatibility Product Line Andover Continuum, EcoStruxure Building Expert, EcoStruxure Building Operation, Satchwell Sigma, TAC IA Series, TAC INET, TAC Vista Environment Windows Operating Systems and iBMS (intelligent Building Management System) Software Cause Compatibility, Firmware, Product Announcements Resolution Please see release documentation for current and recent products. For the Firmware compatibility matrix for: I/NET, it is available HERE or the EcoBuilding Download Center Continuum, click HERE Xenta Software Downloads HERE Vista, click HERE StruxureWare Building Operation, click HERE Product Announcements can be a great tool for discovering which products have been tested and are compatible with the different versions. These documents are available on the Extranet, but have been compiled here for ease of access: I/NET 2.40   Product Announcement 2.41   Product Announcement 2.41a Product Announcement 2.42   Product Announcement and Compatibility Matrix (page 5) 2.43   Product Announcement PA-00239 2.44a Software Available from Exchange Download Center 2.45   Software Available from Exchange Download Center 2.46 Software Available from Exchange Download Center 2.47 Software Available from Exchange Download Center 2.47a Software Available from Exchange Download Center 2.47b Software Available from Exchange Download Center 2.48 Software Available from Exchange Download Center Operating Systems and SQL Supported Video Compatibility Support Policy PA-00279 Software Support for TAC I/NET Continuum v1.92 Product Announcement v1.93 Product Announcement v1.94 Product Announcement PA-00210 1.94 SP1 Product Announcement PA-00273 1.9 - 2.1 Software, Firmware, & Video Compatibility Matrix Concerning IE10 and IE11 browser support  2.0 Feature Blast 2.0 + 2.01/ 2.02 Update Compatibility Matrix 2.0  Product Announcement PA-00353 2.0 CyberStation Installation Guide 2.0 WebClient Installation Guide 2.0 Software License and Ordering Activation Process 2.0 Software and Controller Upgrade Process Andover Continuum PA-00333 Support Policy PA-00272 for Andover Continuum Vista v5.1.5 Product Announcement v5.1.6 Technical Product Advisory v5.1.7 release note document, TAC Vista Compatibility Matrix, SNVT Matrix documents, and TPA-VSTA-11-0020.00 v5.1.7 Product Announcement x5.1.8 Release Note TAC Vista 5.1.8 and TAC Xenta 500/700/900 5.1.8 v5.1.9 Vista Compatibility Matrix SecurityIAS Product Announcement PA-00291 Product Announcement TAC Vista transition to SmartStruxure solution overview  Support Policy PA-00274 for TAC Vista Satchwell Sigma v4.05 SEB Release Notes v4.06 Release Notes v4.06 Release Note Supplement v4.07 Release Notes Satchwell Sigma Standard Edition Installation and User’s Guide Support Policy PA-00297 for Satchwell Sigma v4.08 Release Notes PA-00397 Sigma Version 4.08 Sigma server on a virtual machine Satchwell Micronet data sheet - MicroNet View 2.1 OS Compatibility - Micronet View PA-00228 Product Announcement Support Policy PA-00298 for Satchwell MicroNet PA-00228 Satchwell MicroNet End of Commercialization Announcement I/A Series PA-00163 I/A Series R2 & G3 Product Announcement PA-00114 Legacy Products Windows 7 Compatibility I/A Series R2 with Windows Compatibility Chart PA-00243 Software Product Update - Q2 2013 PA-00251 Hardware Product Update - Q2 2013 PA-00278 Software Product Update - Q3 2013 I/A Series (Niagara) R2 Windows Compatibility Matrix with additional detail I/A Series (Niagara) AX/G3/N4 Windows Compatibility Matrix with additional detail Support Policy PA-00280 R1 for TAC I/A Series StruxureWare Building Operation Please visit Maximum number using StruxureWare Building Operation (Scalability and Capacity) SmartStruxure Lite Please visit SmartStruxure Lite solutions

Issue Content Types are not working correctly. A Content Type that was just created appears under the ES but not under the AS in which it was created in. Product Line EcoStruxure Building Operation Environment Building Operation Enterprise Server Building Operation Workstation Building Operation Automation Server Premium Building Operation Software 1.9 or greater Cause Problems with or changes to the network configuration are affecting both the function and the lead shadow relationship of Content Types. Resolution   The following video will help us, Understand the Lead/Shadow aspects of Content Types Diagnosis and correct possible issues regarding the Lead/Shadow Online help topic for further information is also available here: Content Types (se.com)  

Issue How to perform the activation of an embedded demo license Product Line EcoStruxure Building Operation Environment Building Operation Automation Server Premium (AS-P) Cause The embedded demo License is a temporary license used for demonstration purposes, training, site engineering, when waiting on a permanent license order, or license support. This license file has a .Bin extension and can be downloaded from the EcoStruxure Exchange (ecoxpert.se.com) and is valid for a limited time (3 months). Resolution This video will demonstrate where to download, and how to activate an embedded demo license on an Automation Server using the Device Administrator.