Building Automation Knowledge Base

Issue A repository of objects available somewhere for sharing TGML graphics such as Smart Widgets (Power Objects), Camera, Door, Lighting, Reader, override, etc. Product Line EcoStruxure Building Operation Environment StruxureWare Building Operation site with Smart Widgets. Cause Graphical interface of power object, such as a Power Meter, Power Objects, Camera, Door, Lighting, Reader, override, etc. for viewing in TGML graphics mode. Resolution These objects should appear on the StruxureWare Building Operation Community Site. However, there is an ongoing centralized effort in producing more objects in a uniform way and the developers have not yet seen the devices they developed objects for. One of these developers has made objects for these devices: PM710, PM9, PM800, ION6200, Compact NSX. There are standardized updates in progress for these and also for the PM210. The community is the best place to get these. PSS does not have a repository of these type of objects.  

Issue It is not clear how to replace an existing AS with a new AS-P Product Line EcoStruxure Building Operation Environment Automation Server (AS) Automation Server Premium (AS-P) First detected in version 1.7 Cause Detailed instructions on how to replace an existing AS with a new AS-P are needed Resolution WebHelp references Automation Server Replacement Using Restore Automation Server Replacement Using Restore Workflow Overview Main differences between an AS and an AS-P: In the AS-P, the RS-485 ports have been re-located to the top. The AS-P has 2 Ethernet ports; port 2 can be used as a switch only as of SBO version 1.81. AS-P device USB port format changed to mini USB. Operator Panel port has been removed. Hardware factory reset has been removed. AS-P uses pluggable connectors for field buses. (not shown in picture above) Consider the power consumption. AS-P requires 10 watts, while the Automation Server only required 7 watts. Preparations In preparation for replacing an Automation Server with an AS-P the following considerations must be made: Power consumption Since the AS-P consumes three more watts than the classic Automation Server, the power budget needs to be reviewed to check whether an additional power supply and/or rearrangement of the current configuration is needed, if the configuration includes IO modules. Terminal base The terminal base for the classic Automation Server can be used with the new AS-P after removal of the upper terminal block. Note though that all field buses wiring has to be moved to the pluggable connectors used with the AS-P. RS-485 field bus re-wiring Since the RS-485 ports and connectors have been relocated, the termination at the server of any field bus located on those ports will need re-wiring. Also, the physical specification of the RS-485 port is changed in the AS-P, so review whether the termination resistors needs to be replaced. Refer to Configuration Selection for Generic RS-485 Network Devices AS-P firmware Unlike the classic Automation Server, the AS-P ships from the factory with no firmware installed. Make sure to procure the appropriate Device Administrator firmware to install in the unit. First version that supports the AS-P is 1.7. Note once again that the USB port format in the AS-P is mini USB, so procure the appropriate USB cable. Backup file Make a backup of the classic AS to be replaced, the AS-P will restore from a classic AS backup but this is a one way process, the classic AS will not restore from an AS-P backup file. If the classic AS is running an older version of firmware, it will have to be upgraded first to at least 1.7.2. Power budget review Since the AS-P consumes 10 watts of power versus 7 watts for the classic Automation Server, it is necessary to review the power budget to ensure there is enough power for the AS-P, if the Automation Server being replaced is hosting IO modules. One power supply (PS-24V) can supply 30W. The following table shows power consumption for the different device types Device Power AS-P 10 AS 7 DO-FA-12-H 1.8 DO-FA-12 1.8 DO-FC-8-H 2.2 DO-FC-8 2.2 DI-16 1.6 RTD-DI-16 1.6 AC-4 11.1 UI-16 1.8 AC-2 5.5 AO-8-H 4.9 AO-8 4.9 AO-V-8-H 0.7 AO-V-8 0.7 UI-8-AO-4 3.2 UI-8-AO-4-H 3.2 UI-8-DO-FC-4 1.9 UI-8-DO-FC-4-H 1.9 UI-8/AO-V-4 1.0 UI-8/AO-V-4-H 1.0 In case one or more additional power supplies are needed, refer to the example given in last part of this article.   Note: The following "replacement procedure" applies to SBO 1.7.x, 1.8x, 1.9x, EBO 2.0x and 3.0.x and 3.1.x. The AS-P must be running the same version as the original AS backup. The AS was no longer supported from EBO 3.2.x. If the site needs to take the AS-P to EBO 3.2 or later, the following should be followed at the AS supported version, then once the AS backup has been restored to the AS-P, the AS-P can be upgraded further, following the supported upgrade path, which can be found in the release notes for the specific EBO version.   Replacement procedure The following procedure assumes the classic Automation Server is being replaced with a brand new AS-P from the factory If the Automation Server is hosting IO modules then perform the steps in the 'Power Budget' section below before going to the next step. Perform pre-maintenance procedure per site requirements, i.e. put equipment in hand control mode etc. Pull out the classic Automation Server from the terminal base. The hardware is designed for hot swapping so there is no need to power down the system. Remove the terminal block from the terminal base as indicated above. Insert the AS-P in the terminal base. Connect Device Administrator to AS-P via USB and install a new database on it. You may want to check the 'Set time on device' check box to initialize the time in the AS-P since its current time is most likely at default if this is a brand new unit or a unit that has been powered down for a while. Using Device Administrator set the communication parameters of the AS-P (IP address etc) to match the settings of the classic Automation Server being replaced. Connect Ethernet cable from network switch to Ethernet 1 port on the AS-P. If a hotfix was installed on the Automation Server that is replaced, apply any hotfix needed to match the version of the firmware in the AS-P to the version of the backup from the Automation Server. Since the AS-P should now be able to communicate over IP the application of any HF can be done either over USB or IP. Using WorkStation, log in directly into the AS-P and restore the backup from the classic AS. Insert pluggable connectors for field buses. If there is an Enterprise Server, log into Enterprise Server from WorkStation and verify the newly swapped AS-P is online. Verify IO modules (if any) are online. Verify field devices (if any) are online. Return the system to software control per site requirements. Verify the system is operating correctly then perform a backup of the AS-P. Power supply addition example Consider the following system If we do the math, the power consumption of this system is 29.8 watts. To avoid exceeding the capacity of the existing PS we need to add an additional PS to the configuration before we replace the Automation Server with an AS-P. In order to maximize the use of the capacity of the first PS we will add a new PS at slot #7 and move the UI8AO4 IO module from slot #7 to slot #8.   Steps Disconnect the UI8AO4 IO module making sure it powers down. It is necessary that any IO modules being relocated on the IO bus are powered down so that they 'forget' their current module IDs. *** Logon to the Automation Server, make sure UI8A04 shows offline then edit the module and change its Module ID from 7 to 8. Insert power supply at slot #7 Attach the UI8A04 after the new PS (slot #8), when it powers up it will obtain its new Module ID (8) from the Automation Server. Last, if the module’s name contains the ID (Slot07:UI8AO4) it may be a good idea to rename it using the new ID to avoid confusion. (Slot08:UI8AO4) *** It is absolutely necessary that all the modules that will change IDs be powered down, if there are multiple power supplies in the chain make sure to power down all power supplies that are supplying power to any modules that will change slot #. When removing or inserting IO modules or handling S-Cables, care should be taken not to bend or otherwise damage the pins that connect the module to its IO terminal base, any damage to the pins may cause the module address to shift.   Tip There is a tool on the community (SBO xbk Analyzer) that can be used to automatically calculate the power budget from a backup of the AS/AS-P. Here is the power budget report generated from the tool after addition of second power supply at slot #7 before replacing the classic AS with an AS-P. The total power consumption is 29.8 watts but we have increased the power capacity of the system to 60 watts with the addition of the second power supply.   The instructions above are available as a PDF: Replacing a classic AS with AS-P

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 Finding the correct procedure for migrating Infinet controllers from a Continuum controller fieldbus to an AS-P. Product Line Andover Continuum,EcoStruxure Building Operation Environment Continuum Cyberstation Building Operation Automation Server Premium (1.9 onwards) Building Operation Automation Server Bundled (1.9 onwards) Cause The wrong procedure has been followed which is not the approved and tested procedure to be used when migrating Infinet controllers from Continuum to EBO.  Resolution Procedure for Converting / Transitioning the Infinet Bus Prior to migrating the Infinet The RS-485 network cable should be routed in a continuous daisy chain bus configuration. There should not be any stub connections, stars or ring configurations. The bussed cable should pass through each node to be connected with no splits or branches in the cable network. Repeaters can be used to achieve the star, distributed star (backbone with clusters), off of the backbone. For additional information, review the article: EBO Webhelp Cabling Using the conversion tool and other engineering efforts, create the AS-P database for all Infinet devices, Infinet, Interface items, etc. in either a live AS-P or in the PCT. At the site From Continuum CyberStation,  the following must be completed to each Infinet controller that you are moving to an AS-P. Upgrade all Infinet devices that are going to be converted to the latest firmware version.  Firmware upgrading capability will not be available in EBO until a future release. Clear the memory of all Infinet devices involved before relocated to the AS-P com port by editing the controller object and selecting Runtime > Reset. If the conversion was done on the PCT, deploy the AS-P. Verify that the AS-P firmware is 1.9.0.73 or higher. Disconnect Infinet bus from the Continuum controller com port(s). Move the Infinet bus (busses) to the corresponding RS485 port(s) on the AS-P. Confirm that the Infinet devices are all showing online under the AS-P Download the Infinet devices. * Backup all Infinet devices to flash memory.   *  If the Infinet devices share data with other Infinet devices then it may be necessary to repeat this step in order to establish the complete Import/Export table. PLEASE NOTE The above steps are important! If not followed, offline and bus problems can occur. There may be a desire to skip the rest of the controllers, but the steps must be followed The likelihood is high that there will be substantial difficulties in getting the i2 controllers online and in a stable state to accept the download files. All of the Infinet controllers must be reset in Continuum before moving the bus to the AS-P.  The controllers should then be backup up to flash memory to ensure that they do not revert to their Continuum configuration following a cold start. If problems occur that make it necessary to abort the migration process and return the controllers to the Continuum system, all of the Infinet controller must have their memory cleared before re-attaching the bus on the comm port of the original Continuum controller.  For those controllers which have not established communications under the AS-P, this will mean performing a hard reset at the Infinet controller hardware. At no time should the Infinet bus be connected to the both the AS-P and the Continuum controller at the same time as this  confuses the Infinet controllers causes communications issues that will take some time to resolve. Please also see the "Infinet under the hood" community post Continuum Conversion Tool NOTES V3.0.x and v3.1.x Conversion Tools should not be used. The Workaround is to use the 2.0 Conversion Tool then upgrade. (The Conversion tool was fixed by v3.1.2.6000 (CP5)) V3.2.x onwards the Conversion Tool operates correctly v4.0.3 has an issue converting Infinet controllers, 4.01 or 4.02 should be used instead Now fixed in v4.0.3.5005 CP3(Known Issues) v3.x outperform 4.x, 5.x and 6x.(known Issues). The Workaround is to convert the dmp file in CCT 3.x then upgrade the DB to the expected version in PCT or AS-P.

Issue Licenses required to upgrade SBO/EBO to EBO 2022 v4.0.x Product Line EcoStruxure Building Operation Environment Building Operation Automation Server Premium - Secure boot Building Operation Automation Server Premium Building Operation Automation Server Bundled Building Operation Enterprise Server Cause Clarifying licensing upgrade requirements for EBO 2022 v4.0.x Resolution Example: Upgrading a site SBO 1.x or EBO 2.x to EBO 2022 v4.0.x or later directly. Site has an Enterprise Server (ES) the ES has 7x Automation servers AS-Ps and 2x AS-Bs attached. One AS-P has a Modbus interface, and 1 AS-B has a Modbus interface. Adding 1 additional AS-P classic (non-secure boot), 1x AS-P-S secure boot and 1 AS-B scalable. The SBO 1.x or EBO 2.x licenses need to be upgraded to EBO 3.x first. Upgrade ES licensing from SBO 1.x license to EBO 3.x.  These licenses need to be activated using License Administrator.   1 x SXWSWESUP13010 ES Upgrade from 1.X to 3.0 with 10 or less AS  Note: Upgrading ES from 1.x gives the ability to host the maximum quantity of field devices / controllers at the Enterprise Server (600). Also, when a system is upgraded from 1.x, it will be provided with an unlimited (bounded by the maximums stated in the Architectural Guidelines) client license for connections to the Enterprise Server that has been upgraded.   The following additional licenses are required for each AS-x when upgrading a site from SBO 1.x to EBO 3.x or upgrading a site from EBO 2.x that was originally installed at SBO 1.x and upgraded to EBO 2.x. These are not required if the site was originally installed at EBO 2.0 and upgrading to EBO 3.x. These licenses need to be activated using License Administrator.   7 x SXWSWASUP00001 license will be required one for each AS-P. 2 x SXWSWASUP00001 licenses will be required one for each AS-B.   Note: If the site has more than 24 AS-xs then part number SXWSWASUP00099 provides 999 licenses. EBO 3.2.x architectural guidelines allows a maximum of 250 AS-xs per ES.   Upgrade ES license from EBO 3 to EBO 4 This license needs to be activated using License Administrator.   1 x SXWSWESUP30010 ES Upgrade from 3.X to EBO 2022 or later (i.e. to the current EBO version) with 10 or less AS Upgrade AS-P/B licensing from EBO 3 to EBO 4 or later These licenses need to be activated using Device Administrator.   For each AS-P (non secure boot AS-P and AS-P-NL), one of the following bundles would be required for each AS-P.   SXWSWASPUP30SA Upgrades AS-P-XX from EBO 3.x to EBO 2022 or later AS-P Bundle – Standalone SXWSWASPUP30SD Upgrades AS-P-XX from EBO 3.x to EBO 2022 or later AS-P Bundle – Standard SXWSWASPUP30EN Upgrades AS-P-XX from EBO 3.x to EBO 2022 or later AS-P Bundle - Enhanced SXWSWASPUP30FU Upgrades AS-P-XX from EBO 3.x to EBO 2022 or later AS-P Bundle – Full SXWSWASPUP30BP Full Bulk pack for upgrading AS-P-XX from EBO 3.x to EBO 2022 or later, contains 125 pieces of SXWSWASPUP30FU. For the AS-P with the Modbus interface, an SXWSWX000MBRTU license is not needed as Modbus is grand-fathered for AS-P classics.   Note: Once an AS-P license is upgraded, there is no differentiation between AS-P Secure Boot and AS-P Non-Secure Boot (Classic):   If the “SXWSWASPUP30SD Upgrades an AS-P from EBO 3.x to EBO 2022 or later AS-P Bundle – Standard” license was purchased for an AS-P classic, and later it requires an enhanced or full license.   SXWSWXUP00SDEN ASP Bundle upgrade - Standard to Enhanced SXWSWXUP00SDFU ASP Bundle upgrade - Standard to Full Would need to be purchased.   If the “SXWSWASPUP30EN Upgrades an AS-P from EBO 3.x to EBO 2022 or later AS-P Bundle – Enhanced” license was purchased for an AS-P classic, and later it requires an  full license. SXWSWXUP00ENFU ASP Bundle upgrade - Enhanced to Full Would need to be purchased.   For the AS-Bs (AS-B-24, AS-B-24H, AS-B-36, and AS-B-36H), one of the following bundles would be required for each AS-B. These licenses need to be activated using Device Administrator.   SXWSWASBUP30SD Upgrades AS-B from EBO 3.x to EBO 2022 or later AS-B Bundle – Standard SXWSWASBUP30FU Upgrades AS-B from EBO 3.x to EBO 2022 or later AS-B Bundle - Full A SXWSWX000MBRTU Modbus license is not needed with AS-Bs Note: Once an AS-B license is upgraded, there is no differentiation between AS-B Scalable and AS-B (L) Non-Scalable (Classic): If the “SXWSWASBUP30SD Upgrades AS-B from EBO 3.x to EBO 2022 AS-B Bundle – Standard” license was purchased for an AS-B (L) classic, and later it requires a full license.   SXWSWXBBUPSDFU ASB Bundle upgrade - Standard to Full, would need to be purchased.   To upgrade the AS-B-L (classic) type, the SXWSWASBUP30SD ASB Upgrade – Standard license is all that is required.   For the additional AS-P classic one of the following licenses would be required. SXWSWASPUP30SA Upgrades AS-P-XX from EBO 3.x to EBO 2022 or later AS-P Bundle – Standalone SXWSWASPUP30SD Upgrades AS-P-XX from EBO 3.x to EBO 2022 or later AS-P Bundle – Standard SXWSWASPUP30EN Upgrades AS-P-XX from EBO 3.x to EBO 2022 or later AS-P Bundle - Enhanced SXWSWASPUP30FU Upgrades AS-P-XX from EBO 3.x to EBO 2022 or later AS-P Bundle – Full For the AS-P with the Modbus interface, an SXWSWX000MBRTU license is not needed as Modbus is grand-fathered for AS-P classics.   For the additional AS-P secure boot one of the following licenses would be required. SXWSWXBU0000SA ASP Bundle - Standalone  SXWSWXBU0000SD ASP Bundle – Standard  SXWSWXBU0000EN ASP Bundle – Enhanced  SXWSWXBU0000FU ASP Bundle - Full  For the AS-P secure boot if a Modbus interface is to be used the SXWSWX000MBRTU Modbus license would be required. For the additional AS-B Scalable one of the following licenses would be required. SXWSWXBBU010SD ASB Bundle – Standard SXWSWXBBU050FU ASB Bundle – Full A SXWSWX000MBRTU Modbus license is not needed with AS-B scalable. If an additional AS-B classic was added one of the following licenses would be required. SXWSWASBUP30SD Upgrades AS-B from EBO 3.x to EBO 2022 or later AS-B Bundle – Standard SXWSWASBUP30FU Upgrades AS-B from EBO 3.x to EBO 2022 or later AS-B Bundle - Full A SXWSWX000MBRTU Modbus license is not needed with AS-Bs     Addition: If the site had an Enterprise Central (EC) at EBO 2.0 and was upgrading to EBO 2022 v4.0.x or later, one of the following licenses would be required to upgrade to EBO 3.x first:   SXWSWECUP23005 EC Upgrade with 5 or less ES SXWSWECUP23010 EC Upgrade with 10 or less ES Then one of the following licenses would be require to upgrade from EBO 3.x to EBO 2022 v4.0.x or later:   SXWSWECUP30005 EC Upgrade from 3.x - with 5 or less ES SXWSWECUP30010 EC Upgrade from 3.x - with 10 or less ES   For more information on the bundles, search for 'software bundles" in the  “Part Numbers and Hardware/Software User Matrix – EBO 2024”   For information on software and features that require licenses  

Issue When the EWS is installed on the same machine using the service then all packets will be going to the localhost and will not hit the NIC so will not be captured in a Wireshark packet capture. Product Line EcoStruxure Building Operation, EcoStruxure Security Expert Environment Security Expert Building Operation Enterprise Server Building Operation Automation Servers (AS-P, AS-B) Cause Packets sent between services on the same machine (like SOAP and EWS) do not hit the NIC and therefore cannot be captured with the default configuration of Wireshark using the WinPcap packet sniffing library.  Resolution Replace WinPcap with Npcap to emulate a loopback NIC for packet capture. Go to https://nmap.org/npcap/ for details on the library. Download the library installer from https://nmap.org/npcap/#download Uninstall WinPcap. Install Npcap. Npcap will then create an adapter named Npcap Loopback Adapter. In Wireshark choose this adapter to capture, loopback traffic will be the seen the same way as other non-loopback adapters. This can be tested by typing in commands like "ping 127.0.0.1" (IPv4)  or "ping ::1" (IPv6).

Issue When trying to activate an embedded license on a SmartX Server using Device Administrator, the activation fails with the following error message: Failure (error) received when reclaiming an embedded license on an Automation Server   "Embedded operation: Activate failed: ASEmbeddedAPI internal error: Capability request could not be created." Product Line EcoStruxure Building Operation Environment Building Operation Automation Server Premium (AS-P) Building Operation Automation Server Bundled (AS-B) Building Operation Automation Server (AS) All of the above v. 3.0 or higher Cause The cause of this problem is that the trusted storage, i.e., the embedded license database on the SmartX server, is corrupt. The embedded licensing framework undertakes internal checking and if it determines there is a consistency problem, it will consider the trusted storage to be corrupt. This means that no operations to the trusted storage, such as activating licenses, will succeed. At the time of writing, it is unclear why the consistency problems happen. In the server log, you may also observe the following error message: 10:08:06: Executing licensing command 10:08:06: Executing embedded operation: Activate ActivationID: ACT-XXXXXXXXXX-XXXXXX-XXXXXXXX 10:08:11: Embedded operation: Activate failed: ASEmbeddedAPI internal error: Capability request could not be created 10:08:11: Licensing command completed 10:08:11: Activating licenses failed (Real Activation ID replaced with ACT-XXXXXXXXXX-XXXXXX-XXXXXXXX)   Although this process is specific to the "Capability request could not be created" error, similar errors can be corrected by following the steps shown in the resolution. Please attempt all steps before contacting support.   Resolution   Building Operation 2022 v4.0.4  and above Upgrading to the above versions will now resolve the trusted storage corruption and inhibit license activation. Building Operation 3.2.X and up to EBO 2022 v4.0.3   Note: Although this process is specific to the "Capability request could not be created" error, similar errors can be corrected by following the below steps. Please attempt all steps before contacting support.    Clear trusted storage within the server Using Device Administrator select the affected server and Open a PuTTY Console An alternative way of connecting to the server is to use WinSCP. Use File protocol SCP and the admin user. When connected, follow the instructions as per the Word Document also attached below Warm or Cold Start the AS-P If failures still occur, attempt the Offline Activation of Licenses Workflow; The key step is that the license is activated offline and then transferred to the server in two different steps, allowing the license activation process to complete successfully.   Warm or Cold Start the AS-P If there are still failures with either of these options, send a support request through your local support center including the errors seen with each activation attempt.     Building Operation version lower than 3.2.X   If the embedded license is a Client license, there is no need to activate the license. Install the EBO Hotfix 3.0.3.2001 (CP1) or later. This will remove the enforcement of SmartX server Clients in the licensing system. See also article Embedded WebStaion client license when logging directly into a SmartX server no longer needed. Other licenses like SmartDrivers, SNMP, and Personal Dashboards may still need to be activated. Contact your local support center to fix this problem.

Issue Steps to backup within StruxureWare/EcoStruxure Building Operation Product Line EcoStruxure Building Operation Environment StruxureWare/EcoStruxure Building Operation site with AS and/or ES Backup, Automation Server, Enterprise Server, Workstation, .xbk, xbk, backup set, db backup, db_backup Cause Must an AS or ES be stopped in order to do a full backup? Is a raw copy of the database folder from within Windows Explorer sufficient for backing up an ES?  For instructions on how to restore a backup in StruxureWare/EcoStruxure Building Operation, see How to restore a StruxureWare Building Operation server backup set. Resolution Concerning the backup and comparing SQL to the proprietary database that StruxureWare/EcoStruxure creates begs the question, are these backup complete? StruxureWare freezes the database while a backup is in progress in different ways. For configuration changes, StruxureWare Building Operation queues up the changes until the backup completes. For historical data, StruxureWare Building Operation buffers the data based on the limits of the buffer size. A stop of the ES is not necessary, nor is a stop of an AS. Because of this freeze and buffering, the data is put into that backup folder referenced in the pdf you sent. Three rules to remember: Restores of backups must be same software revision Do not rename the backup set A StruxureWare/EcoStruxure Building Operation backup should not be renamed after it has been created. When creating a backup, give the appropriate prefix to the standard name format.     The backup file will be shown as below. Should the backup name need to changed, then either create a new backup, or, zip up the backup using the new name.   Backups default to every Sunday morning 1:00am Here is the procedure for backing up an AS or ES: In Workstation, in the System Tree pane, select an Automation Server (AS) or Enterprise Server (ES) On the Actions menu, click Backup. This opens the Backup Options window In the Include column, select the servers that you want to include in the backup In the Backup content column, select the type of data you want to backup for each server: Select All Data to back up both the historical and configuration databases. This combined option protects the configuration, historical data, and custom object type data for a specified date and time Select Configuration only to back up the configuration database and custom object type data. This data option protects the configuration data for a specified date and time In the Backup set description column, type a brief description up to 255 characters to help identify the content of the backup Click Backup Verify that each backup succeeded and click Close Backup Files of ES: The backup data files are stored in the C:\ProgramData\Schneider Electric StruxureWare\Building Operation 1.X\Enterprise Server\db_backup\LocalBackup or  C:\ProgramData\Schneider Electric EcoStruxure\Building Operation 2.X\Enterprise Server\db_backup\LocalBackup   Backup Files of AS: Login to AS from WorkStation and navigate to System > Backup and Restore > Backup sets> Local. Then Right-click on the backup file and Save To... (then select a folder on your HDD) Note: Let this not be confused with the 'Starting a Project Tutorial [101248].pdf' in section 5.1 page 44, where it describes the user simply doing a raw copy of the database folder from within Windows Explorer. This can be mistaken with the orderly backup that uses the inbuilt StruxureWare backup facility. This copy procedure described has no chance to freeze the database. The user can just do it at any random time and StruxureWare has no idea that the copy has been made. A sample database should be created using the Backup/Restore functions of the system, not by just doing a raw folder copy as the server may be in the middle of transactions to various files in that folder. A copy of this folder could be used, but only while the SE.EnterpriseServer.exe process has been stopped. However, it is recommend using the system’s backup facility to accomplish this (Not all items are backed up such as Alarm data. The Backup/Restore help section of StruxureWare Building Operation Guide discusses what is and isn’t backed up).

Issue How do I setup and configure the database when using External log storage in EBO? Product Line EcoStruxure Building Operation Environment PostgreSQL TimescaleDB pgAdmin Building Operation Workstation Cause When using External log storage in EcoStruxure Building Operation(EBO) PostgreSQL server and TimescaleDB are installed on a computer where the trend log data and events should be stored. The database used for External Log storage needs to be setup and configured correctly. Resolution The EBO External Log Storage Installer tool available on the Community assists with installing and configuring the PostgreSQL server. But if you like to see how it is done manually please watch this video. The following steps are shown in the video: Create the database in the PostgreSQL server Create a user which will be used by EBO when it connects to the database Configure the database for use with EBO Configure EBO to be able to connect to the database  

Issue Firewall issues when trying to reach out to the activation server for a license Product Line EcoStruxure Building Operation, Satchwell Sigma, TAC Vista Environment Building Operation Licensing Firewall Cause If the corporate network has a very restricted firewall policy or rules, the port needed to reach and activate a license may be blocked. Note: The same license server is used for EcoStruxure Building Operation, Satchwell Sigma and TAC Vista software licenses. Resolution Open Port 443 (HTTPS) for the server hosting the license server, and ensure that the routing paths to the Flexnet Licensing server URL's are all fully open. The Licensing Server URL should be opened from the site, and it is:  https://schneider-electric.flexnetoperations.com ocsp.r2m02.amazontrust.com Ocsp.r2m02.amazontrust.com Ocsp.rootca1.amazontrust.com If the site of the old server has issues with non-secure communications or communications forwarding between the previous and the new server, a tool is available to configure EBO to only use the new server. See the Exchange Community article for the download: SBO License Setup Note: From EBO V2.0 only the new license server is used, port 80 is no longer required and HTTP is redirected to HTTPS.

Issue Licenses are becoming damaged repeatedly over time and/or licenses are going in to a disabled state. Product Line EcoStruxure Building Operation, TAC Vista Environment SmartStruxure License Administrator Virtual Machine Cause Damaged Licenses: If the license server / license administrator is installed on a virtual machine, the common reason for damaged licenses is that the MAC address of the virtual machine is not set to be static. Every time the MAC address changes, the license will become damaged. Disabled Licenses: This is usually caused when the license fails to complete a process such as a return or repair. This could be due to an intermittent internet connection or the process timed out while trying to communicate with the license server. Resolution Repair License with License Administrator The first step to take with a damaged or disabled license is to use the repair function in license administrator. Follow the steps from WebHelp topic Repairing an EcoStruxure Building Operation Software License. If the repair function does not work, then the license server will need to be reset.  Reset License Server (Unable to Repair License) Below are the steps to remove the damage or disabled licenses before reactivating the permanent licenses again: Put a SBO demo license on the site to get it back up and running right away. Locate the Entitlement ID and/or activation ID of the impacted licenses. Open a case with your local BMS support group and provide them this information. This information will be used to release the licenses to prepare them to be rehosted. There are then two potential methods to  reset the license server: Download and run the SBO License Server Reset tool from the Community Manually reset the License Server Stop the License Server. In the License Server application folder, remove all files:                 - File path for Windows 7, Windows 8.1, and WIndow 10: \ProgramData\FLEXnet                 - File path for Windows Server 2008 and Windows Server 2012: \ProgramData\FLEXnet   Start the License Server Reactivate the returned network licenses.   Note: When you reactivate all returned network license, new License Server .data files are created together with the activation of the first license. For more detail, reference WebHelp: Resetting the License Server.

Issue How can I troubleshoot a communication issue with the Modbus protocol Is there a log available within the AS or ES that shows the Modbus communication between Modbus devices Product Line EcoStruxure Building Operation Environment Building Operation Workstation Building Operation Automation Server Building Operation Enterprise Server Cause When troubleshooting Modbus issues in an AS or ES it can be helpful to see the communication between devices to help identify this issue. The trace log within both server types is available and is configured as described below in the resolution. Resolution Open Workstation and navigate to [AS/ES name]/System/Modules/Trace/Loggers/nsp/nsp.pin. Right-click "nsp.pin.modbus" and choose Properties. Under Level, change from "Information" to "Debug", then click ok. In EBO 7.0 and higher, "Debug" will report 1 line per transaction, where "Trace" will report 8 lines for the same transaction. In EBO 7.0 and higher, instead of logging all Modbus with "nsp.pin.modbus," you can log separately Modbus TCP and Modbus Serial using either "nsp.pin.modbus.CommunicationLayer.ModbusCommsLogger.Serial" or "nsp.pin.modbus.CommunicationLayer.ModbusCommsLogger.TCP" Let it run a few minutes. If there are some user input needed to recreate the Modbus issue, then perform these steps now. Retrieve the log by right-clicking [AS/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 Modbus decoder can be used to assist in viewing/debugging the Modbus 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 or AS is reset, i.e. cold started or warm started, the log level will return to 'Information', so if further increased logging is required, the procedure will need to be repeated. Note2: From v6 (2024), adding the trace below can be helpful for Modbus RTU /[ASName]/System/Modules/Trace/Loggers/nsp/nsp.pin/nsp.pin.sport/nsp.pin.sport.DeviceRS485   Here is a video showing the above process. 

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 On a new JACE-8000, or on one in which the clean-dist or factory restore procedure has been applied, the JACE can be pinged but, you cannot connect to the platform, and the system time's year shows as 2020 or greater.   The following symptomatic messages can be observed in the serial shell via the debug port:  ERROR [01:26:53 01-Jan-2037] [tid = 1] niagarad: policy file verification failed. Policy files may have been tampered with. Cause is: [/opt/niagara/security/policy/java.security failed signing verification]  ERROR [01:26:53 01-Jan-2037] [tid = 1] niagarad: throwable occurred while initializing daemon (java.lang.SecurityException), can not continue  sysmon: niagarad is no longer running  The following symptomatic messages appear in the system logs:  Jan 01 01:26:53 2 11111 0 niagarad: policy file verification failed. Policy files may have been tampered with. Cause is: [/opt/niagara/security/policy/java.security failed signing verification]  Jan 01 01:26:53 2 11111 0 niagarad: throwable occurred while initializing daemon (java.lang.SecurityException), can not continue  Jan 01 01:26:53 2 11111 4 sysmon: niagarad no longer running Product Line TAC IA Series. Environment I/A Series Jace-8000 Cause This issue is encountered when the RTC clock's date is Wednesday, December 30, 2020, or later.  Resolution Use the debug port to connect to the system shell with PuTTY. See the System Shell section of the JACE-8000 Install and Startup Guide Set the system clock to a date before the year 2020, and then commission the JACE with 4.2 or newer.  The issue is corrected within the fix for the following issue, addressed in Niagara 4.2.36.10:   NCCB-19628: Code signing timestamps checked improperly, verification will fail Jan 1, 2021    We will continue to see the issue on new JACE-8000 as they ship with a 4.1 daemon. This may also occur on a JACE-8000 on which the clean-dist or factory restore procedure has been applied.

Issue BBMD and BBDT Enterprise Server or Automation Server Product Line EcoStruxure Building Operation Environment Building Operation Enterprise Server and Automation Server BBMD (BACnet Broadcast Management Device) IP subnet, IP router  Cause Clarification for both BACnet Broadcast Management Device (BBMD) and BACnet Broadcast Device Table (BBDT) when used within Building Operation servers. Resolution A BBMD is needed when communicating to BACnet devices on another IP segment/subnet (across IP routers). One BBMD is required per subnet; this is because IP routers block broadcast packets and BACnet uses broadcast packets to initiate and maintain communications.  Continuum CyberStation (below) or bCX4 can act as a BBMD.     A BBMD can be created in a Building Operation Enterprise Server or Automation Server.    The BBMD on the other subnet should be as below   Now all the BACnet devices should be visible on both subnets Notes No more than a single BBMD should be created on each subnet for each IP port used. Additional information about BBMDs is available on WebHelp The Teach and Learn commands are useful for larger networks with multiple BBMDs  

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

Issue SQL error: [Microsoft][ODBC SQL Server Driver][SQL Server]The transaction log for database 'tempdb' is full. To find out why space int he log cannot be reused, see the log_reuse_wait_desc column in sys.databases Product Line Andover Continuum Environment SQL Server Cause Low disk space or unreasonably low maximum size for tempdb database growth. Resolution SQL Server allocates a database called tempdb, primarily for worktable / #temp table usage. Sometimes, you will encounter a transaction log full error   Causes    Usually, tempdb fills up when you are low on disk space, or when you have set an unreasonably low maximum size for database growth.    Many people think that tempdb is only used for #temp tables. When in fact, you can easily fill up tempdb without ever creating a single temp table. Some other scenarios that can cause tempdb to fill up:  any sorting that requires more memory than has been allocated to SQL Server will be forced to do its work in tempdb;    if the sorting requires more space than you have allocated to tempdb, one of the above errors will occur;    DBCC CheckDB('any database') will perform its work in tempdb -- on larger databases, this can consume quite a bit of space;    DBCC DBREINDEX or similar DBCC commands with 'Sort in tempdb' option set will also potentially fill up tempdb;    large resultsets involving unions, order by / group by, cartesian joins, outer joins, cursors, temp tables, table variables, and hashing can often require help from tempdb;    any transactions left uncommitted and not rolled back can leave objects orphaned in tempdb;    use of an ODBC DSN with the option 'create temporary stored procedures' set can leave objects there for the life of the connection.   Short-term fix    Restarting SQL Server will re-create tempdb from scratch, and it will return to its usually allocated size. In and of itself, this solution is only effective in the very short term; assumedly, the application and/or T-SQL code which caused tempdb to grow once, will likely cause it to grow again.      Long-term prevention    Here are some suggestions for maintaining a healthy tempdb:  Make sure that tempdb is set to autogrow -- do *NOT* set a maximum size for tempdb. If the current drive is too full to allow autogrow events, then buy a bigger drive, or add files to tempdb on another device (using ALTER DATABASE) and allow those files to autogrow. You will need at least one data file and at least one log file in order to avoid this problem from halting your system in the future. 

  Issue Fail to login to the selected server when the User name and Password are correct. Product Line EcoStruxure Building Operation Environment Project Configuration Tool 2.0 Cause In the example, the Server is in EBO 3.2.1.630 and the Workstation is 3.2.3.59. The Workstation is at a higher version than the Server but it's not the latest version. PCT loads the incorrect IP(192.168.10.2) in the WS due to the version.     Resolution PCT requires to use of the latest version of WorkStation for all releases (3.2, 4.0, 5.0, 6.0).  For example: EBO 3.2.1.630, 3.2.2.61, 3.2.3.59 and 3.2.4.1009 use WorkStation 3.2.4.4007(CP2) or above. EBO 4.0.1.86, 4.0.2.559, 4.0.3.176, 4.0.4.45 and 4.0.5.7 use WorkStation 4.0.5.3004(CP2) or above.    

Issue There can be confusion on the differences between EcoStruxure Energy Expert (formerly Power Manager) and EcoStruxure Power Monitoring Expert (PME)  Product Line EcoStruxure Building Operation, Other Environment EcoStruxure Building Operation  EcoStruxure Energy Expert (formerly Power Manager) EcoStruxure Power Monitoring Expert Cause Power Monitoring Expert (PME) is a long-established product in the Schneider Power (EMS) offer and so its place in the market is well known and its support path is very clear. Energy Expert is a much newer offering that intentionally sits nearer to EcoStruxure Building Operation (EBO) in the BMS community, while still remaining an EMS product and so its place in the market and support path is more easily confused. Resolution Definitions   EcoStruxure Power Monitoring Expert (PME) Schneider Electric's supervisory software dedicated to power monitoring that enables you to maximize operational efficiency, optimize your power distribution system, and improve bottom-line performance   EcoStruxure Building Operation (EBO)  Schneider Electric's premier building management system (BMS) providing integrated monitoring, control, and management of energy, lighting, HVAC, and fire safety.   EcoStruxure Energy Expert (EE)                                                    Designed to offer Power Monitoring Expert (PME) features to new and existing EcoStruxure Building Operation (EBO) projects, giving extra capabilities to manage power utilization in a BMS environment.   It utilizes EcoStruxure Web Services (EWS) to be able it to share data between the two EcoStruxure software platforms. (EBO and EE) and applications such as the ETL Tool and the Integration Utility in the integration process.   EcoStruxure Web Services (EWS) The Schneider Electric standard for sharing data among various Schneider software platforms to facilitate the creation of EcoStruxure Solutions. Based on conventional Web Services technology (SOAP, WSDL)   ETL Tool The function of the ETL is to extract select historical data (Trend logs) from EBO, and load that data into the Energy Expert SQL database for use in Dashboard and Reports etc.   Integration Utility The function of the Integration Utility is to export Energy Expert Dashboards, Reports and Alarms for import into EBO to enhance its Power Offer to the customer   Product Support Path: PME, Energy Expert, ETL and the Integration Utility are are all fundamentally Power Products and so should always be raised through your local Product Support Team (via your Customer Care Center (CCC)) under an EMS commercial reference. However in cases where an Energy Expert project needs specific assistance with the EBO side of the integration then a BMS commercial reference should be used instead.

Issue When attempting to trust a self signed certificate, the option to permanently trust the certificate is not enabled. When viewing the certificate, you see the message "Bad server certificate" in the field "Issued by" Refer to WebHelp Article 10326 for further information about certificate types Product Line EcoStruxure Building Operation Environment Certificates Cause There can be various reasons why a certificate can not be trusted, and many or these are described in SSL Certificates - Security Certificate Risk warning logging in to WorkStation or WebStation using HTTPS. In this specific case where you see the message "Bad server certificate", the cause is that the certificate is not deemed trustworthy. First of all, you need to check what the reason behind the certificate being flagged as bad is. This is easiest done by examining the "CRL Distribution Points" property of the certificate, to determine which service is checking or affecting the certificate. In this example, we can see that it is ZScaler (a proxy server provider) is listed, so the reason why the certificate is deemed as bad, is most likely because the certificate is self signed, and that is not accepted by the company policy. If disabling the usage of a proxy server on the PC you are working on allows you to trust the certificate, you can confirm that it is an issue with the proxy server not allowing the self signed certificate. For more information about how e.g. ZScaler handles certificates, refer to the How does ZScaler protect SSL traffic article. Resolution Either reconfigure the proxy to allow the self signed certificate, or (the better option) get a proper CA signed certificate. For more information about preparing and importing a CA signed certificate, refer to Preparing and importing a signed CA certificate.

Issue This condition will arise after successfully installing and running Project Configuration Tool for some time. PCT 1.x can no longer initialize the virtual host adapter as a result of the adapter being deleted or removed. The errors may be a result of but not limited to: Introducing a new VPN software package to your PC/Laptop. Manually removing or modifying the Virtual Box Host Only - Network Adapter. Malware or Antivirus platforms that have removed or disabled the adapter. Example: PCT Version - 1.1.2.57 Local mode was set up on a physical laptop and used to offline engineer a project. The job was completed and PCT was not used again for roughly a month. A new project was sold and required PCT for offline engineering. The laptop was booted up and PCT failed to open. The user was presented with the following errors: "Get System State Command: 'Could not connect' " "Get predefined properties command: 'Could not connect' " "GetDashboardErrors Command: 'Could not connect' " "Get System Memory info Command: 'Could not connect' " Product Line EcoStruxure Building Operation Environment Windows Client versions (64 Bit Only) Windows Server versions (64 Bit Only) PCT SERVER versions (64 Bit OS Only) Project Configuration Tool 1.x Cause PCT 1.x can no longer initialize the virtual host adapter as a result of the Vbox adapter being deleted or removed. Resolution Reinstall PCT 1.x on top of your current installation. Your projects will not be modified in the process. Locate the installer. Run the installer, it will ask you to remove the previous version. Press ok. Progress will show as uninstalling. PCT will prompt for installation. Click Next. Select default installation paths. Click Next. Select desired PCT mode. Click next. Ready to Install selected mode. Click Next. PCT software installed. Click Finish. Now PCT will set up the Virtual Host Adapter. Press Ok. Status bar. Compted setup dialog. Click Ok. Run PCT. If successful you will see the template sets getting installed via the top right of the window. Open a project and test an AS/AS-P. If the above steps do not work, here are a few more to try:   Restart the machine after the PCT software finishes re-installing Right-click and select “Run as Administrator” Uninstall PCT software and Oracle VirtualBox and re-install once more   If PCT 1.x still will not work, please open a support case with your local Product Support Group.