Help
  • Explore Community
  • Get Started
  • Ask the Community
  • How-To & Best Practices
  • Contact Support
Notifications
Login / Register
Community
Community
Notifications
close
  • Forums
  • Knowledge Center
  • Events & Webinars
  • Ideas
  • Blogs
Help
Help
  • Explore Community
  • Get Started
  • Ask the Community
  • How-To & Best Practices
  • Contact Support
Login / Register
Sustainability
Sustainability

Ask Me About Webinar: Data Center Assets - Modeling, Cooling, and CFD Simulation
Join our 30-minute expert session on July 10, 2025 (9:00 AM & 5:00 PM CET), to explore Digital Twins, cooling simulations, and IT infrastructure modeling. Learn how to boost resiliency and plan power capacity effectively. Register now to secure your spot!

Building Automation Knowledge Base

Schneider Electric Building Automation Knowledge Base is a self-service resource to answer all your questions about EcoStruxure Building suite, Andover Continuum, Satchwell, TAC…

cancel
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Showing results for 
Show  only  | Search instead for 
Did you mean: 
  • Home
  • Schneider Electric Community
  • Knowledge Center
  • Building Automation Knowledge Base
Options
  • My Knowledge Base Contributions
  • Subscribe
  • Bookmark
  • Invite a Friend
Invite a Co-worker
Send a co-worker an invite to the portal.Just enter their email address and we'll connect them to register. After joining, they will belong to the same company.
You have entered an invalid email address. Please re-enter the email address.
This co-worker has already been invited to the Exchange portal. Please invite another co-worker.
Please enter email address
Send Invite Cancel
Invitation Sent
Your invitation was sent.Thanks for sharing Exchange with your co-worker.
Send New Invite Close
Labels
Top Labels
  • Alphabetical
  • Andover Continuum 2,208
  • TAC Vista 2,045
  • EcoStruxure Building Operation 1,860
  • TAC IA Series 1,828
  • TAC INET 1,458
  • Field Devices 721
  • Satchwell BAS & Sigma 474
  • EcoStruxure Security Expert 335
  • Satchwell MicroNet 252
  • EcoStruxure Building Expert 228
  • EcoStruxure Access Expert 150
  • CCTV 53
  • Project Configuration Tool 47
  • EcoStruxure Building Activate 17
  • ESMI Fire Detection 13
  • EcoStruxure Building Advisor 12
  • Automated Engineering Tool 5
  • EcoStruxure Building Data Platform 3
  • EcoStruxure Workplace Advisor 1
  • EcoStruxure for Retail - IMP 1
Top Contributors
  • Product_Support
    Product_Support
  • DavidFisher
    DavidFisher
  • Cody_Failinger
    Cody_Failinger
See More Contributors
Related Products
Thumbnail of EcoStruxure™ Building Operation
Schneider Electric
EcoStruxure™ Building Operation
4
Thumbnail of SmartX IP Controllers
Schneider Electric
SmartX IP Controllers
1
Thumbnail of EcoStruxure™ Building Advisor
Schneider Electric
EcoStruxure™ Building Advisor
1

Related Forums

  • Intelligent Devices Forum

Previous Next

Invite a Colleague

Found this content useful? Share it with a Colleague!

Invite a Colleague Invite

Building Automation Knowledge Base

Sort by:
Views
  • Date
  • Views
  • Likes
  • Helpfulness
Options
  • Subscribe
  • Bookmark
  • Invite a Friend
  • « Previous
    • 1
    • 2
    • 3
    • 4
    • …
    • 509
  • Next »

Do not install N4.11 or 4.12 to a JACE-8000 or Edge 10 running 4.10U7 or later

Issue Upgrading a JACE-8000 or Edge-10 from 4.10U7 to 4.11 or 4.12 will prevent Niagara Daemon from starting.  You will be unable to connect via Workbench or Browser. Product Line TAC IA Series Environment I/A Series N4 Jace 8000 Tridium Edge 10 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. Cause The software in builds 4.10u7 and later LTS builds (4.10u8, 4.10u9, 4.10u10) was released after 4.11 and 4.12 reached EOL.   4.10u7 contains a newer signing key that is not recognized by 4.11 and 4.12. Resolution When upgrading JACE-8000 and/or Edge 10 running 4.10 LTS builds 4.10u7 and later, please skip over 4.11 and 4.12 and instead upgrade to 4.13u3 or newer. Alternatively, you may apply the dist that reverts JACE-8000 to clean 4.9u1 state, or for Edge-10, the dist that reverts it to clean 4.7 state. You can then install 4.11u2 or 4.12u2, if that's the version you have to use.  If you've already attempted the commissioning operation and bricked a device, and have backups, you can connect to the debug port and use the factory reset process per the documentation.  For Edge 10, consult the section titled Factory Default Recovery  in the Niagara Edge 10 Install and Startup Guide.  For JACE-8000, consult the section titled Restoring factory defaults  in the JACE-8000 Backup and Restore Guide. If you are lacking any backups for the host, then before performing the factory reset, you should enable SSH/SFTP via the debug port, and then copy out the Station files using Filezilla or WinSCP or equivalent.  Reach out to your support channel if you have difficulty finding the location of station files. Typically, the files will be in a subfolder of /home/niagara/stations. The config.bog file will be keyring encrypted, and you'll have to reset it using the Bog File Protection Tool. See Editing the .bog file passphrase offline in the Niagara Platform Guide  for details on using the Bog File Protection Tool.  For details on using the debug port on JACE-8000, see Debug port  in the JACE-8000 Install and Startup Guide.  For details on using the debug port on Edge-10, see Connecting to the debug system shell  in the Niagara Edge 10 Install and Startup Guide.
View full article
Guinan RandyDavis Guinan
‎2024-10-15 09:09 AM

Last Updated: Crewman ContentModerator ‎2025-09-01 03:31 AM

Labels:
  • TAC IA Series
14405 Views

Offline activation of embedded licenses

Issue How to activate an embedded license for a SmartX Server using the Device Administrator when the computer with the Device Administrator is not connected to the internet. Product Line EcoStruxure Building Operation Environment Building Operation Automation Server Premium (AS-P) Cause Device Administrator is used to manage licenses on SmartX servers The following features of a SmartX server need licenses: SmartDrivers SNMP Notifications Personal Dashboards TimescaleDB MQTT Resolution Building Operation 2022 Note: The offline entry of the Activation-ID License items is not all visible - ONLY the first 5 are shown.  This makes entering this information impossible. This has been fixed in the Maintenance Release 4.0.2 of the Device Administrator.  After activating the embedded license offline and transferring this license to the servers, a license violation may be still shown.  The license status should update within 24 hours.  Perform a warm start and then a Refresh License Status on the selected servers to force this update.   If an error is seen in the progress status indicating ASEmbeddedAPI internal error during the offline activation, check the following Embedded license activation fails - Communities to correct the corrupted storage.   This video will show how to activate an embedded license for a SmartX Server using the Device Administrator when the computer with the Device Administrator and/or the server is not connected to the internet. IMPORTANT NOTES: You need to be connected to the SpaceLogic (SmartX) Server using IP (select +Add server on Device Administrator).  It cannot be connected via USB. Ensure always to run the Device Administrator with admin privileges. Select "Run as administrator." Should Device Administrator be running on a computer that has internet access, then there is no need to swap between online/offline computers.  The offline activation process can be run from the same Device Administrator with no need to change computers.  The offline workflow is always the same and detailed on the webhelp topic Offline Activation of Licenses Workflow  The video below shows version 3 licenses. In Version 4, there are a few more license features and quantities required to enter.  The following article may assist in entering this information. License Features list for version 3.0 and 4.0 Product names     At the end of the video session, you will be able to: Create a request file using the Device Administrator on an offline (to the Internet) computer. Activate request files from the Device Administrator on a PC connected to the internet. Send response files to the SmartX Server from the offline Device Administrator.
View full article
Janeway Jonas_Brissman Janeway
‎2022-02-09 04:10 PM

Last Updated: Crewman ContentModerator ‎2025-08-11 03:51 AM

Labels:
  • EcoStruxure Building Operation
14228 Views

Creating binding templates

Issue Creating binding templates. Product Line EcoStruxure Building Operation Environment Binding templates for Script and Function block programs. Binding template examples:  Type Binding Template Examples Path Matching Binding Templates and Syntax Path Matching Binding Template Examples  Cause 1 - Output points need to be bound to the Requested Value attribute, but the default name matching template only matches the value attribute. 2 - Binding  a Graphic which contains several controllers which all have the same names in the system tree structure, using a binding template. 3 - Binding Template Types examples Resolution 1 - Output points need to be bound to the Requested Value attribute, but the default name matching template only matches the value attribute. Under the system folder of the AS or ES there is a folder called "Binding Templates". In here you can create custom templates by right clicking and selecting "New", "Binding Template". To create a generic template that will bind both inputs, outputs, values and other object types follow these steps: Press Next and the following screen appears: Select All Types and press Next: Click twice on the Add Rule icon (Green +) then enter the three rules as follows: Press create and the new IO Binding template will be created.  If you have used a common naming convention in your points and within the programs, you will be able to use this template to bind all the points and values to your programs. Drag the AS across to the IO Binding template (as below) and it will match all of the point names and use Requested value attribute for the output points. This example shows 2 IO Binding templates, as one was created at the AS level and another at the ES level. Only 1 is actually required to provide this functionality. You can subsequently edit the binding template and it will show as follows:   2 - Binding  a Graphic which contains several controllers which all have the same names in the system tree structure, using a binding template. It is common for a system to consist of many controllers that have been created from the same import file. This will mean that there are many instances of the same names being used, but this is not an issue until a graphic containing several controllers are to be bound. Create a "Path Matching Binding Template" as shown above and configure as shown in the following screen shot. Notice that the Binding candidate has /Application/ between the "Unit" and "Point" to match the tree structure.        The screen shot below shows the site system tree structure, with part of the graphic binding page. Note that for the binding template to work, the bind names used in the graphic must be unique. eg. L6W1_CHB_006 (Unit) and ReturnAirTemp (Point).     For an Export of this template, click Binding Template Export 2013-08-15 083240.zip. 3 - Binding Template Types examples see the Online Help. An additional resource is the Exchange Community in particular the following Knowledge Reinforcement Session Also check out the SmartStruxure-Binding Templates-Lesson 1-7 Quick-Help video on the Exchange.
View full article
Picard Product_Support
‎2018-09-11 01:52 AM

Last Updated: Crewman ContentModerator ‎2025-08-11 03:52 AM

Labels:
  • EcoStruxure Building Operation
14182 Views

Default IP address for BCX, ACX57xx, CX9702 and Netcontroller II

Issue What is the default IP address for BCX, ACX57xx, CX9702 & Netcontroller II? Product Line Andover Continuum Environment Controller Netcontroller II (9680) BCX ACX57xx CX9702 Cause Default IP address for BCX, ACX57xx, CX9702 & Netcontroller II Resolution The default for all these controller types is: IP address: 169.254.1.1 Subnet: 255.255.0.0 Gateway: 169.254.0.0
View full article
Picard Product_Support
‎2018-09-06 02:12 PM

Labels:
  • Andover Continuum
13982 Views

How to set EcoStruxure BMS Server as Modbus TCP Server or Modbus RTU Server (Slave)

Issue A 3rd party system wants to poll data from EcoStruxure BMS server through Modbus, how to set it up? 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 If an EcoStruxure BMS server needs to share data with a 3rd party system through Modbus, the EcoStruxure BMS server can act in one of two roles: Modbus TCP server or Modbus RTU Server (Slave) EBO server acting as RTU slave EBO server acting as Modbus TCP server   Resolution  Create a Modbus interface under the EcoStruxure BMS server and define the Modbus device ID for the EcoStruxure BMS server. Create Modbus points under this Modbus interface and set the register numbers and register type for the points. Create a Modbus Slave network for serial connection, select the COM port and set relative communication parameter. Or create a Modbus TCP Server for TCP connection and can change the default Modbus TCP port if needed (Usually just leave it as default). Use standard Modbus test software like Modscan to scan the points through TCP or serial. Use Function Code 1 or 2 to read Digital Modbus points and Code 3 or 4 for Analog Modbus points. Be sure to match the data length setting in Modscan with the real points number in the EBO server. For instance, if there are only 3 values in EBO Modbus interface, the data length setting must be less than 3 in Modscan. Or it will show error in Modscan. The below video will demonstrate how to configure EcoStruxure BMS server to act as Modbus TCP server or Modbus RTU slave  
View full article
Picard Product_Support
‎2018-09-06 09:26 AM

Last Updated: Administrator CraigEl Administrator ‎2022-12-08 05:20 PM

Labels:
  • EcoStruxure Building Operation
13701 Views

Standard Library Components for StruxureWare Building Operation

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.  
View full article
Picard Product_Support
‎2018-09-10 06:51 AM

Last Updated: Administrator CraigEl Administrator ‎2022-08-07 10:50 PM

Labels:
  • EcoStruxure Building Operation
13324 Views

Replacing an Automation Server with an AS-P

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
View full article
Picard Product_Support
‎2018-09-10 01:04 PM

Last Updated: Crewman ContentModerator ‎2025-08-11 03:58 AM

Labels:
  • EcoStruxure Building Operation
13286 Views

Upgrading SBO 1.x or EBO 2.x licenses to EBO 2022 v4 or later

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  
View full article
Gary Schneider Alumni (Retired)
‎2022-02-17 09:16 AM

Last Updated: Kirk Mahmoud_Sayed Kirk ‎2025-05-12 05:49 AM

Labels:
  • EcoStruxure Building Operation
13162 Views

Backup of StruxureWare/EcoStruxure Building Operation AS and ES

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).
View full article
Picard Product_Support
‎2018-09-10 07:08 AM

Last Updated: Crewman ContentModerator ‎2025-08-11 03:53 AM

Labels:
  • EcoStruxure Building Operation
12925 Views

Migrating Infinet controllers from Continuum to EcoStruxure Building Operation

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) 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. 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.
View full article
Picard Product_Support
‎2021-02-19 02:37 AM

Last Updated: Crewman ContentModerator ‎2025-09-01 03:34 AM

Labels:
  • Andover Continuum
  • EcoStruxure Building Operation
12781 Views

Embedded license activation fails

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.
View full article
Janeway PeterEdvik Janeway
‎2020-03-19 02:35 AM

Last Updated: Crewman ContentModerator ‎2025-08-11 03:52 AM

Labels:
  • EcoStruxure Building Operation
12748 Views

External log storage setup and configuration

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  
View full article
Janeway Jonas_Brissman Janeway
‎2020-08-14 05:12 AM

Last Updated: Crewman ContentModerator ‎2025-08-11 03:49 AM

Labels:
  • EcoStruxure Building Operation
12595 Views

Unable to login to servers in Project Configuration Tool(PCT) 2.0

  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.    
View full article
Admiral StephenYang Admiral
‎2024-02-04 10:12 PM

Last Updated: Guinan RobertAndriolo Guinan ‎2024-07-18 03:55 PM

Labels:
  • EcoStruxure Building Operation
  • Project Configuration Tool
12578 Views

Tridium N4.11 Upgrade Considerations

Issue Tridium N4.11 Upgrade Considerations  Product Line TAC IA Series Environment I/A Series N4.11 Enterprise Server I/A Series N4.11 Jace 8000 Cause Detailed information about N4.11 upgrade prerequisites and best practices  Resolution The following details a set of upgrade considerations and known issues and their workarounds regarding Niagara 4.11. Please review prior to upgrading to Niagara 4.11. Niagara 4.11 and Default NRE Memory Changes: A change to the JACE-8000 file system has been introduced with the release of Niagara 4.11. The RAM disk was used to store alarm and history data. During station save, this data was copied from the RAM disk and zipped up into a single file that was stored on flash. In Niagara 4.11, the RAM disk has been removed entirely. This data is now written directly to the flash memory. This change has enabled ~384MB of RAM to be freed up to improve performance. Some of the space has been reallocated to code cache, metaspace, and heap space in the 4.11 NRE default settings. Any additional memory space is now available as general free memory. These changes should be transparent to most users and will provide moderate performance improvements on the JACE-8000. Prior to upgrading your JACE-8000, please review NRE default configuration changes and RAM disk removal In 4.11. Niagara 4.11 and Third-Party Modules Keeping your Niagara installations safe and secure is our highest priority. In Niagara 4.11, ALL third-party modules must be signed with either a trusted valid certificate or a self-signed certificate to successfully run on a station. This new policy greatly increases the security posture of Niagara installations by making administrators aware of any modules that may have been tampered with, compromised, or derived from untrustworthy sources. Niagara's new signature enforcement feature is being rolled out over multiple Niagara releases. The first iteration was built into release 4.8 to give developers adequate time to make the transition to always signing any third-party modules. Niagara 4.8 produced console and Security Dashboard warnings about unsigned modules but allowed them to run on a station. As of Niagara 4.11, unsigned modules will not execute. For more information, please review the Niagara documentation on Third-Party Module Signing Niagara 4.11 Updated Operating Systems, Browsers, and Databases For the latest information on supported operating systems, please refer to Supported OS and other software in the Niagara 4 Framework Installation Guide. Tridium remains focused on keeping pace with advancing IT infrastructure to enable more efficient, long-term support of each release version. This policy enhances the security posture of a Niagara installation by ensuring that only the most robust, secure operating systems and enterprise applications are compatible with the framework. The list below provides information on what we will be supporting with Niagara 4.11.   OS, Browser, Database Version Red Hat Enterprise Linux 8.1 (64 bit), 7.7 Ubuntu Linux 20.04 LTS – Desktop & Server Windows Server 2019 (64 bit), Server 2016 (64 bit), Windows 10 (64 bit) VMWare ESXi 6.7 Oracle Database 19.3, 18.3, ... 12.2/12.1 MySQL Database 8 MS SQL Database 2019, 2017, 2016 Browsers Chrome, FireFox, Microsoft Edge Mobile Browsers Safari (iOS 12, 13), Chrome (Android 8, 9, 10) As with all software products, we must also deprecate support for some operating systems and enterprise applications.  Nevertheless, you can be confident that the above list will handle your needs moving forward. Using Web Launcher with Niagara 4.11 Web Launcher 21.4.1 was recently revamped for Niagara 4.11 to include essential software dependencies updates along with critical defect fixes. This version of Web Launcher has Java version 8 update 311 and certificate management has been updated to work with Niagara 4.11 along with any legacy or prospective release. Prior to using Web Launcher with Niagara 4.11, customers should update Web Launcher accordingly (see steps below). How to update Web Launcher? Web Launcher has a feature to check for updates over the internet and prompts the user when a new version is available in the cloud. However, the existing version of Web Launcher has a bug that prevents a smooth update. Users will be required to perform a fresh install by downloading the latest version from the cloud via the station web Login page. Click on the Niagara Web Launcher Installer link on the station's Web Launcher Web Page, which can be reached via the link on the Login page itself. Once the download is successful, click on the msi file and follow the installation wizard. You do not have to uninstall the older version. The new installation will automatically update to the latest version. Niagara 4.11 Release Notes: The release notes for Niagara 4.11 are located here.
View full article
Guinan RandyDavis Guinan
‎2022-05-10 11:15 AM

Last Updated: Crewman ContentModerator ‎2025-08-11 03:54 AM

Labels:
  • TAC IA Series
12548 Views

Capture a Modbus trace log in EBO/SBO

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. 
View full article
Picard Product_Support
‎2018-09-06 09:00 AM

Last Updated: Crewman ContentModerator ‎2025-08-11 03:49 AM

Labels:
  • EcoStruxure Building Operation
12412 Views

How to capture localhost traffic with Wireshark to help troubleshoot EWS communication issues.

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).
View full article
Picard Product_Support
‎2018-09-10 09:07 AM

Last Updated: Guinan AdamSteele Guinan ‎2023-06-21 11:47 PM

Labels:
  • EcoStruxure Building Operation
  • EcoStruxure Security Expert
12383 Views

Conversion of Continuum devices from i2 to b3 and vice-versa in the field

Issue Continuum i2 and b3 field devices use the same hardware. With the exception of their -V models and the bCX (bCX9640/bCX4040) controller, they were not designed to have their firmware swapped from Infinet to BACnet (or BACnet to Infinet) in the field. Product Line Andover Continuum, EcoStruxure Building Operation Environment Continuum i2 Controllers (except -V) Continuum b3 Controller (except -V) 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. Cause With the exception of the -V controllers, the devices were not designed to have their protocol (Infinet/BACnet) swapped in the field, however, due to changes in market needs R&D is now providing a method to allow the protocol to be changed in the field. Resolution IMPORTANT: If a RoamIO2 is available, it can be used to do the conversion without the need to have Continuum Cyberstation and Continuum controllers. https://community.se.com/t5/Building-Automation-Knowledge/Conversion-of-Continuum-devices-from-i2-to-b3-and-vice-versa-in/ta-p/448337    To convert i2 field devices into b3 BACnet (or vice-versa) from CyberStation Contact PSS and request the conversion files for the specific model(s) you wish to convert. Follow the procedure detailed below or as per the attached document. To swap the firmware of any non -V i2 device from one protocol to the other (in this case, from Infinet to BACnet b3), you use the following procedure.  For more information, see section 1.3 “Converting Infinet i2 Field Devices to BACnet b3 Devices from CyberStation” below. NOTE: This procedure was developed by Schneider Electric’s R&D and tested in the Product Support Services (PSS) lab.   Before starting the procedure, you need the following items: An I2 device(s) to be converted. A Continuum CyberStation with i2 device(s) configured and online. A special, conversion b3 upgrade file for the appropriate device model as provided by PSS A b3 bootloader file for the appropriate device model, provided by PSS Physical access to the device.  You need this to push its Restart switch or to access the switch or breaker where you can shut off power to the device to force a restart. A bCX4040 controller configured in CyberStation xP Expansion I/O Note If the device to be converted from i2 to b3 has any expansion modules attached, make sure the modules do not exceed the power capacity of the expansion port (180 mA), it has been observed that the b3 devices adhere more strictly to the 180 mA limit than the i2 devices, resulting in loss of operation on IO channels located on the Expansion Port if the power limit is exceeded.  See attached xP Expansion IO Datasheet for information on power consumption of each xP IO module.   1.2 Preparing the Field Bus for the i2 to b3 Device Conversion To ensure a smooth conversion, it is necessary that you reduce the traffic on the field bus as much as possible in order to provide the necessary bandwidth to the upgrade operations required for the conversion. Before starting the process with the conversion file, be sure to follow these instructions.    To prepare the field bus for the i2 to b3 device conversion Disable all the programs in all the devices residing in the field bus. Close all Continuum Workstations except the one performing the upgrade. In the Workstation performing the upgrade, close all graphics, List views, and anything else that could be polling data from the field bus. Make sure MS/TP field bus is on same baud rate as Infinet field bus, mainly 19.2K 1.3 Converting i2 Field Devices into b3 BACnet from CyberStation You can convert Infinet i2 field devices into b3 BACnet field devices by swapping the firmware of any non -V model i2 device. IMPORTANT: When using this procedure, be aware of the following guidelines: It applies ONLY to the firmware or communication protocol (Infinet or BACnet) of the device. It does not convert the control application in the device. Following conversion, the device’s memory is cleared, so you need to configure a new control application. It may result in a loss of critical data if not performed properly. Before beginning, ensure that all important data is backed up in the event of data loss or the device losing its application and becoming non-operational.  For more information, see section 1.1 “Introduction” above. To convert i2 field devices into b3 BACnet from CyberStation Contact PSS and request the conversion files for the specific model(s) you wish to convert. You will be provided with an application file (namely, i2920toB3920B4.500077.upd) and a boot loader file (namely, B3920BootB4.500077.upd). From CyberStation, edit the i2 device and record its Serial Number and Infinet id. Consult the General tab to locate this information. From the Runtime tab, perform a Reset to clear the device’s database. Upgrade the i2 device using the application file provided by PSS. Once the upgrade is complete, the i2 device stays Offline since its communication protocol has now been swapped from Infinet to BACnet. Disconnect the device from the Infinet field bus of its host master controller (for example, a CX9680 or a bCX9640). Connect it to the bCX4040 MS/TP field bus. (MAKE SURE MS/TP FIELD BUS IS RUNNING AT SAME BAUD AS INFINET FIELD BUS DEVICE WAS ON, NAMELY 19.2K BAUD) In the bCX4040, configure a b3 device using the appropriate model as well the Serial Number and ID recorded previously. NOTE: You will need to provide BACnet Device ID. Typically, it will be the same as the Serial Number. You can also use a Learn to bring the device online under the bCX4040 and automatically assign the model, id etc.  Refer to this Knowledge Base article on using the serial number for the Device ID.  Remember here to set the Comm Port for comm2. Restart the device either by power cycling or using the restart button. The device will come online under the bCX4040 as a b3 device. Perform an Update b3 OS operation to send the appropriate b3 boot loader file provided by PSS. Go to the Runtime tab, and reset the device once the update is finished. Once the device reboots and comes back online, you can confirm it has the right boot loader by looking at the device from the BACnet side. The screenshots that follow display the before and after results of the i2 to b3 conversion process. Before: After: NOTE 1 If Continuum system is not available it is also possible to convert i2 to b3 using RoamIO and EBO server using the following steps Disconnect device from field bus and connect RoamIO directly to i2 device. Use InfinetServiceTool to send the application conversion file to the i2 device. After the uprev operation is done disconnect RoamIO and cycle power to the i2 device Connect converted device (now a b3) to MSTP of AS-P or other EBO server that supports BACnet MSTP Perform a b3 learn operation to bring the device online Right click the b3 device and proveed to 'Device->Update firmware...' Navigate to appropriate boot loader file for the b3 model After uprev of boot loader is complete, cycle power to the b3 device. NOTE 2 Similar steps can be used to convert b3 device to i2 device. Make sure to use the V2 version of the b3 to i2 conversion files as it was found the original set of b3 to i2 conversion files did not work in some cases. Please note that once a b3 device has been converted to i2 using this procedure the device will ONLY accept conversion uprev files, attempt to uprev using regular uprev file will result in the following error:   This Uprev file does not match this type of controller. This applies to b3 to i2 conversion only, it does not apply to i2 to b3 conversion.
View full article
Captain AbeMeran Captain
‎2022-12-06 09:57 AM

Last Updated: Crewman ContentModerator ‎2025-09-01 03:33 AM

Labels:
  • Andover Continuum
  • EcoStruxure Building Operation
12334 Views

Damaged or Disabled Licenses

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.
View full article
Picard Product_Support
‎2018-09-10 10:12 AM

Last Updated: Crewman ContentModerator ‎2025-08-11 03:49 AM

Labels:
  • EcoStruxure Building Operation
  • TAC Vista
12295 Views

License server and port used to reach Building Operation licensing server

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.
View full article
Picard Product_Support
‎2021-02-17 02:51 AM

Last Updated: Crewman ContentModerator ‎2025-08-11 03:51 AM

Labels:
  • EcoStruxure Building Operation
  • Satchwell BAS & Sigma
  • TAC Vista
12287 Views

Rectifier Type Power Supply - Full or Half Wave?

Issue What controller models have full-wave and which have half-wave rectifier type power supplies? Environment All Controllers Cause What controller models have full-wave and which have half-wave rectifier type power supplies? Resolution   Updates Product Rectifier Type       Full  Half Built-in     Wave Wave Isolation   CC-8102-024 X   X   CC-8104   X     CC-8111-024 X   X   CC-8118 X   X   CC-8155   X     CP-25xx   X     CP-8142-024 X   X   CP-8161-333   X     CP-8161-701   X     CP-8261-333   X     CP-8261-702   X     CP-8301 X   X   CP-8301-024 X   X   CP-8391-913 X   X   CP-8511-024   X     CP-8511-102   X     CP-8511-103   X     CP-8513   X     CP-8552   X     PP-2000 Series   X     PP-8121   X     PP-8311-120 X   X   PP-8311-024   X     PP-8516   X     PP-8616   X     PP-8621   X     T155 Series X       T158 Series X       T167 Series X       T168 Series X       TC97-MHP   X X   TC97-S   X X   TC97-SHP   X X   TC-98-M   X X   TC-98-MHP   X X   TC-98-S   X X   TSP7xxx         TSP-8111       08.03.06 VER-PHx-07-S   X   08.03.06 VER-PHx-08-S   X   08.03.06 VER-PHx-09-S   X               i2/b3865   X     i2/b3866   X     i2/b3865-S   X     i2/b3866-S   X     i2/b3865-WL   X     i2/b3866-WL   X               i2/b3885   X     i2/b3885-WL   X               i2/b3867   X     i2/b3867-S   X     i2/b3867-WL   X               i2/b3865-V   X     i2/b3866-V   X     i2/b3885-V   X     i2/b3865-V-WL   X     i2/b3866-V-WL   X     i2/b3885-V-WL   X               i2/b3887   X     i2/b3887-WL   X               i2/b3887-L-115 X   X   i2/b3887-L-115-C X   X   i2/b3887-L-230 X   X   i2/b3887-L-230-C X   X   i2/b3887-L-115-WL X   X   i2/b3887-L-115-C-WL X   X   i2/b3887-L-230-WL X   X   i2/b3887-L-230-C-WL X   X             i2/b3850 X   X   i2/b3851 X   X   i2/b3853 X   X   i2/b3850-S X   X   i2/b3851-S X   X   i2/b3853-S X   X   i2/b3850-WL X   X   i2/b3851-WL X   X   i2/b3853-WL X   X             i2/b3800   X     i2/b3800-S   X     i2/b3800-WL   X               i2/b3804   X     i2/b3804-S   X     i2/b3804-WL   X               i2/b3810   X     i2/b3810-WL   X               i2/b3814    X     i2/b3814-WL   X               i2/b3608   X     i2/b3624   X     i2/b3608-S   X     i2/b3624-S   X     i2/b3608-WL   X     i2/b3624-WL   X               i2/b3920 X   X   b4920 X   X   i2/b3920-D X   X   b4920-D X   X   i2/b3920-S X   X   b4920-S X   X   i2/b3920-WL X   X   b4920-WL X   X   i2/b3920-D-WL X   X   b4920-D-WL X   X             bCX1 Family   X               NetController I   DC Input               NetController II   X               CMX9924  X   X             ACX-2   X               CX9702 X   X             I2200AC X   X   I2210AC X   X   B-LINK-AC X   X   BLINK-F-AC X   X
View full article
Picard Product_Support
‎2018-09-06 01:45 PM

Labels:
  • Andover Continuum
12016 Views
  • « Previous
    • 1
    • 2
    • 3
    • 4
    • …
    • 509
  • Next »
To The Top!

Forums

  • APC UPS Data Center Backup Solutions
  • EcoStruxure IT
  • EcoStruxure Geo SCADA Expert
  • Metering & Power Quality
  • Schneider Electric Wiser

Knowledge Center

Events & webinars

Ideas

Blogs

Get Started

  • Ask the Community
  • Community Guidelines
  • Community User Guide
  • How-To & Best Practice
  • Experts Leaderboard
  • Contact Support
Brand-Logo
Subscribing is a smart move!
You can subscribe to this board after you log in or create your free account.
Forum-Icon

Create your free account or log in to subscribe to the board - and gain access to more than 10,000+ support articles along with insights from experts and peers.

Register today for FREE

Register Now

Already have an account? Login

Terms & Conditions Privacy Notice Change your Cookie Settings © 2025 Schneider Electric

Welcome!

Welcome to your new personalized space.

of

Explore