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
  • Building Automation Knowledge Base
  • Label: EcoStruxure Building Operation
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,854
  • TAC IA Series 1,826
  • TAC INET 1,459
  • Field Devices 721
  • Satchwell BAS & Sigma 474
  • EcoStruxure Security Expert 334
  • Satchwell MicroNet 252
  • EcoStruxure Building Expert 228
  • EcoStruxure Access Expert 150
  • CCTV 53
  • Project Configuration Tool 47
  • EcoStruxure Building Activate 17
  • EcoStruxure Building Advisor 12
  • ESMI Fire Detection 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

Label: "ecostruxure building operation"

View in: "Building Automation Knowledge Base" | Community

1851 Posts | First Used: 2018-09-06

Building Automation Knowledge Base

Sort by:
Date
  • Date
  • Views
  • Likes
  • Helpfulness
Options
  • Subscribe
  • Bookmark
  • Invite a Friend
  • « Previous
    • 1
    • 2
    • 3
    • …
    • 93
  • Next »
Label: "EcoStruxure Building Operation" Show all articles

How BACnet controllers are established as being Online / Offline

Issue How are BACnet controllers established as being Online / Offline? Product Line EcoStruxure Building Operation Environment BACnet Cause BACnet controllers may appear offline in the system, even though they can still be communicated with. This raises questions about how their online/offline status is determined. Resolution The online/offline status of BACnet devices is managed by the BACnet device manager plugin, which processes BACnet I-Am messages to maintain a device table.   The following rules and mechanisms are used to determine the status of BACnet controllers: Device Discovery and Initial Probing When a new device is discovered, an entry is added to the device table. The system probes the new entry up to four times at 5-second intervals. If the device does not respond within this time, it is declared offline. Offline Detection via MSTP Driver Building Operation uses the MSTP dev driver to monitor token passing. If three consecutive tokens are missed, the device is marked as offline. Probing Offline Devices Once a device is offline, the system sends a Who-Is message every 60 seconds. Offline devices are probed indefinitely at 60-second intervals until they respond. Online devices are never probed. Status Transition A device is considered online once it responds to a request. If it fails to respond, its status is updated to offline, and probing resumes.
View full article
Picard Product_Support
‎2018-09-06 09:47 AM

Last Updated: Administrator CraigEl Administrator ‎2025-08-13 05:47 PM

Labels:
  • EcoStruxure Building Operation
2567 Views

Getting data from Rayleigh Instruments RI-78-80-C kWh Meter

Issue How to get data from Rayleigh Instruments RI-78-80-C kWh power meters Product Line EcoStruxure Building Operation Environment EcoStruxure Building Operation Automation Server (ASP/ASB) Modbus RTU Interface Cause The RI-78-80-C meter provides a single 48-bit Modbus RTU word representing energy in kWh. This word spans three 16-bit registers (registers 0, 1, and 2). The meter: Only responds to a valid 48-bit read Does not return exceptions for invalid or partial register reads Resolution To successfully read the 48-bit value: Step-by-Step Instructions Create a Modbus Group Set an appropriate polling interval. Add Registers Add three 16-bit unsigned registers to the group: ModReg0 (Register 0) ModReg1 (Register 1) ModReg2 (Register 2) Create an Analog Value Example name: kWReading Script Program Use the following calculation: kWReading = ((256 * 256 * ModReg0) + (256 * ModReg1) + ModReg2) / 100 ​ This formula accounts for the fact that each register only uses half of its 16-bit range (values from 0 to 255). The register values represent 1/100 of a kWh, so a scaling factor of /100 is applied. Bind Points Bind the Modbus registers and analog value to the script program. Example Calculation If: ModReg0 = 3 ModReg1 = 167 ModReg2 = 59 Then: kWReading = ((3 × 256 × 256) + (167 × 256) + 59) / 100 = 239419 / 100 = 2394.19 kWh ​   Additional Notes The device may appear online in EcoStruxure even if it’s not responding correctly. This is because the online poll interval mechanism expects a response from a 16-bit register. Since the RI-78-80-C doesn’t respond to invalid reads, it may falsely appear online. To avoid this, set the online poll interval mechanism to “Inhibit”. Compatibility Warning: This device may not function correctly in v2.0 and v3.0 due to changes in offline detection. This issue is resolved in v3.1. Resources Example Modbus Objects and Script RI-78-80-C Exports.zip Numeric Output kWReading   Line Calc1 kWReading = ((256*256*ModReg0) + (256*ModReg1) + ModReg2)/100
View full article
Picard Product_Support
‎2018-09-11 07:08 AM

Last Updated: Administrator CraigEl Administrator ‎2025-08-13 05:24 PM

Labels:
  • EcoStruxure Building Operation
3158 Views

Trigger multiple alarms on a single variable

Issue How to trigger different alarms with different alarm texts depending on the value of a single variable Product Line EcoStruxure Building Operation Environment Building Operation Workstation Alarms Cause There is a requirement to trigger different alarms based on the value of a single variable.  As an example, a variable coming from an APC Symmetra UPS will report various alarm states as a number from 1 to 7 in the same variable, and it is required to differentiate the alarm text on each value. Value Status Alarm text 1 unknown Module is in Unknown state from UPS 2 not installed Module not installed in UPS 3 Off OK Module not installed in UPS 4 On OK Module not okay in UPS 5 Off Fail Module off fail in UPS 6 On Fail Module on fail in UPS 7 Lost Communication Module lost comm. in UPS Resolution Here are two examples on how to do it Example 1: 7 different alarms with different alarm texts monitoring the same point Example 2: 1 alarm monitoring a point, and a script dynamically changing the alarm text     From version 1.9 upwards Alarm Decoration is available and could also be used in various ways to achieve the same result.  Similar to example 1 a decoration could be created for each state.  For example for state 3, create a decoration that filters on the active alarm (1) and when the value at change is three (2) override the alarm text message (3) with the relevant text (4). The decorations have the added benefit they can be applied to multiple point alarms.  
View full article
Picard Product_Support
‎2018-09-06 09:12 AM

Last Updated: Crewman ContentModerator ‎2025-08-11 04:14 AM

Labels:
  • EcoStruxure Building Operation
1309 Views

Modbus groups with duplicate registers

Issue An increased amount of polling caused by Modbus groups with duplicate registers. Product Line EcoStruxure Building Operation Environment Modbus Building Operation Automation Server Premium (AS-P) Building Operation Automation Server Bundled (AS-B) Building Operation Automation Server (AS) Cause Modbus Register Groups cause multiple resisters to be requested in a single query. This can be a very efficient way of collecting data from a device. See this Article for details. However, if a register is repeated (duplicated) within a group it can cause an increased amount of polling.    The screenshots shows a Modbus Register Group with a Requested group poll interval set to 10,000ms, but the misconfiguration is forcing polls at 500ms. Resolution The resolution is simply to avoid such a configuration. NOTE - If a Modbus Register Group with duplicates registers becomes unstable with some registers showing offline, then disabling the Scattered Read function will usually help.
View full article
Dave_Shore Schneider Alumni (Retired)
‎2022-04-27 07:09 AM

Last Updated: Crewman ContentModerator ‎2025-08-11 04:14 AM

Labels:
  • EcoStruxure Building Operation
1537 Views

Remove Server information shown in WorkStation drop down list

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 Remove Server information shown in WorkStation drop down list Product Line EcoStruxure Building Operation Environment Building Operation WorkStation Cause Building Operation WorkStation 'caches' user customization's including the server names / IP addresses that it has previously successfully logged on to. Resolution Two tools are available on the Community that can assist in this process. Refer to the details and instructions for both on the Community. SBO Reset WorkStation Login SBO WorkStation Favorites To manually delete the file containing the servers list (among other information), navigate to and delete the file. The location and file name depends on the installed version of WorkStation. Version 1.3 C:\Users\%username%\AppData\Roaming\Schneider Electric\Workstation\TAC.ClientUserProfile.bin Version 1.4 and 1.5 C:\Users\%username%\AppData\Roaming\Schneider Electric StruxureWare\Building Operation\WorkStation\TAC.ClientUserProfile.bin   Versions between 1.6 and 1.9 C:\Users\%username%\AppData\Roaming\Schneider Electric StruxureWare\Building Operation\WorkStation\SBO.ClientUserProfile.bin Version 2.0 and above When hovering over a server in the drop down list, a trash can appears at the right side that allows the server to be deleted from the list: WorkStation 2.0 and aboveWorkStation 2.0 and above Alternatively the path to the file is: C:\Users\%username%\AppData\Roaming\Schneider Electric EcoStruxureWare\Building Operation\WorkStation\SBO.ClientUserProfile.bin Next time you run WorkStation again, a new user profile file will be created. Note: All IP addresses will be cleared and you will lose settings such as column widths and similar user customization's.
View full article
Picard Product_Support
‎2018-09-11 08:44 AM

Last Updated: Crewman ContentModerator ‎2025-08-11 04:12 AM

Labels:
  • EcoStruxure Building Operation
1601 Views

HTTP 500.21 - Internal Server error when starting SmartStruxure WebReport

Issue After installing SmartStruxure WebReport and starting it in a web browser, it will show an error: HTTP 500.21 - Internal Server error / Handler "PageHandlerFactory-Integrated" has a bad module "ManagedPipelineHandler" in its module list. Product Line EcoStruxure Building Operation Environment SmartStruxure WebReport Cause According to the explanation from Microsoft, the most likely causes are: managed handler is used; however, ASP.NET is not installed or is not installed completely; there is a typographical error in the configuration for the handler module list. Resolution Silent repair of the 4.0 .NET Framework for 32 bit servers with .Net Framework version 4.0.30319 run the command (in command prompt): %windir%\Microsoft.NET\Framework\v4.0.30319\SetupCache\Client\setup.exe /repair /x86 /x64 /ia64 /parameterfolder Client /q /norestart for 64 bit servers with .Net Framework version 4.0.30319 run the command: %windir%\Microsoft.NET\Framework64\v4.0.30319\SetupCache\Client\setup.exe /repair /x86 /x64 /ia64 /parameterfolder Client /q /norestart Install the ASP.NET version and configure IIS to use it open command prompt (Start -> cmd) and for 32 bit servers run the command: %windir%\Microsoft.NET\Framework\v4.0.30319\aspnet_regiis.exe /i open command prompt (Start -> cmd) and for 64 bit servers run the command: %windir%\Microsoft.NET\Framework64\v4.0.30319\aspnet_regiis.exe /i Try to view WebReports and it should work now. To also assist in WebReports installations there is a useful tool SBO Reports Preparation available on the Buildings Business Communities website. This tool assists in the pre-installation of WebReports. **Please note Schneider Electric Product Support Services does not provide support for the tool and you should contact the author through the Community for issues/enhancements.  
View full article
Picard Product_Support
‎2018-09-11 06:38 AM

Last Updated: Crewman ContentModerator ‎2025-08-11 04:12 AM

Labels:
  • EcoStruxure Building Operation
1380 Views

License activation stops at 80% or License Administrator crash

Issue Two related issues are covered in this article While attempting to activate a customer or demo license, the activation process stops at around 80%. When clicking the "Diagnostics" tab in the License Administrator it crashes with a "System.DllNotFoundException" error. System.DllNotFoundException: Unable to load DLL (Tac.Nsp.Archive.Licensing.Client.dll) Product Line EcoStruxure Building Operation Environment First detected in Windows 10 First detected with Microsoft Visual C++ Redistributable 2012 (VC++ 2012) License Administrator Cause There can be two reasons why this happens If the activation process stops at around 80%, but the License Administrator does not crash when the "Diagnostics" tab is selected, the license system needs to be completely reset. If the activation process stops at around 80%, and the License Administrator crashes when the "Diagnostics" tab is selected, Microsoft Visual C++ components need to be repaired. Refer to solutions below depending on the issue detected. Resolution Solution 1: Resetting the license system The process to reset the license server system is covered in Resetting the License Server. In some cases, a deeper reset can be required. For that, a tool called "SBO License Server Reset" can be downloaded from the Community. Solution 2: Repairing Microsoft Visual C++ components Method 1 In Control Panel, click Uninstall a program in the Programs group. In the programs list, locate Microsoft Visual C++ 2012 Redistributable (X64) - 11.0.61030 or Microsoft Visual C++ 2012 Redistributable (X86) - 11.0.61030, depending on your system architecture. Right-click the entry name, and then click Change. In the Modify Setup dialog box, click Repair. After the repair process is completed, restart the computer if you are prompted to do this. Method 2 Run the Modify Setup repair functionality for Microsoft Visual C++ Redistributable by starting the installer. VC++ installers In the Modify Setup dialog box, click Repair. After the repair process is completed, restart the computer if you are prompted to do this.
View full article
Picard Product_Support
‎2018-09-06 07:54 AM

Last Updated: Crewman ContentModerator ‎2025-08-11 04:12 AM

Labels:
  • EcoStruxure Building Operation
4003 Views

How to search for personal and public dashboards

Issue How to find out if a user has created a personal and/or a public dashboard Product Line EcoStruxure Building Operation Environment EcoStruxure Building Operation Workstation Cause Customers may want to know if there is a personal or public dashboard (or both) under a user Resolution We can search in Workstation to know if a user has created a personal or public dashboard (or both). Enter “Dashboard” on the “Include type” and search over the whole server.   Public dashboards can be created by any user anywhere under the server except under the system tree. In the following example, any results that appear under the “/Server 1/System/Domains” is a personal dashboard since it is tied to the users, and the rest are public dashboards.     Please note that creating a personal dashboard requires a Personal Dashboard License.    How Dashboards Work  Public vs Personal Dashboards  
View full article
Lt. Commander Reza Lt. Commander
‎2022-03-16 03:33 PM

Last Updated: Crewman ContentModerator ‎2025-08-11 04:12 AM

Labels:
  • EcoStruxure Building Operation
1130 Views

Can the XIF be generated for an AS?

Issue Can the XIF be generated for an AS? Product Line EcoStruxure Building Operation Environment Automation Server Cause Want to add AS into another system and need XIF Resolution In version 1.4.0 and below the Automation Server can not be integrated into other systems using LonWorks. From version 1.4.1 and up, you can configure an "Externally Managed LonWorks Network" to the Automation Server, and as a result use the Automation Server in e.g. LonMaker or NL220. The Automation Server supports "Upload from device", but if you need the xif file, you can refer to the following guides available on the Community. Generate XIF file from SmartStruxure AS - LonMaker Generate XIF file from SmartStruxure AS - NL220.
View full article
Picard Product_Support
‎2018-09-11 12:12 AM

Last Updated: Crewman ContentModerator ‎2025-08-11 04:11 AM

Labels:
  • EcoStruxure Building Operation
2642 Views

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

Warning Potential for Data Loss: The steps detailed in the resolution of this article may result in a loss of critical data if not performed properly. Before beginning these steps, make sure all important data is backed up in the event of data loss. If you are unsure or unfamiliar with any complex steps detailed in this article, please contact Product Support for assistance. Issue 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) 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-08-11 04:11 AM

Labels:
  • Andover Continuum
  • EcoStruxure Building Operation
10997 Views

WorkPlace Tech and WorkPlace Tech Editor Ribbon Function

Issue The WorkPlace Tech and WorkPlace Editor add-in for the VisioRibbon is available in the toolbar of Visio but all or some of the functions are unavailable. Product Line TAC IA Series, EcoStruxure Building Operation Environment I/A Series WorkPlace Tech 5.9.x, 5.10.4 Building Operation Workstation (WorkPlace Tech Editor) Microsoft Visio 2010, 2013, 2016, 2019 (WorkPlace Tech 5.10.4 only) Cause There may be one or several of these situations causing this behavior depending on a combination of products installed. The Visio installed is an unlicensed product or in its evaluation period and not registered  The Visio installed is not properly updated There is an error in the WPDispatcher.msi Resolution Review the proper area for the Visio you are using to assure the product is registered; Visio 2010 Visio 2013/2016/2019 If the Visio is part of a subscription-based product, it will be noted as such rather than saying the product is activated. Thoroughly read this Knowledge Base Article for the information required to assure your Visio is properly updated. Workplace Tech 5.9.3 / Workplace Tech Editor (EBO) Microsoft Security Updates required for Visio and Office  To correct any possible WorkPlace Tech or Editor (SBO/EBO) dispatcher problems, Follow the path C:\Program Files (x86)\WorkPlace Tech to the WPDispatcher.msi and "right click / Uninstall" Do this for each version of SBO or EBO installed that has Workstation with WorkPlace Tech Editor.  Here is the path C:\Program Files (x86)\Schneider Electric EcoStruxure\Building Operation X.Y\WorkStation or C:\Program Files (x86)\Schneider Electric StruxureWare\Building Operation X.Y\WorkStation (X.Y will be the version installed i.e 3.1).  Perform the same Uninstall of the WPDispatcher.msi.  The picture below is what will appear if the dispatcher has been removed or was not previously installed.  This message is expected. Open the WorkPlace Tech or the WorkPlaceTech Editor.  The WPDispatcher.msi will run the correct version.
View full article
Guinan RandyDavis Guinan
‎2020-04-23 12:14 PM

Last Updated: Crewman ContentModerator ‎2025-08-11 04:10 AM

Labels:
  • EcoStruxure Building Operation
  • TAC IA Series
2529 Views

EBO Data Collection Summary

Issue There is currently no summary KB article for all the data collection available in EBO systems. Product Line EcoStruxure Building Operation Environment Building Operation Enterprise Server Building Operation Enterprise Central Building Operation Workstation Building Operation Webstation Building Operation Automation Server Premium Building Operation Automation Server Bundled Cause Identified the need to review data from EBO to analyze performance or issues. Resolution Purposes for Data Collection Provide visual information about the issue Screenshots (from Windows Snip & Sketch or other tools) Video Capture or Mobile Device Video Device LEDs, provide any information about them and when they change. Provide information about your configuration/installation Network devices, including routers, switches, and any configuration you can provide BMS Routers Site Topology, including all devices included in the communications path Provide server (EC/ES/AS) XBK backup Configuration only is smaller and useful when investigating configuration, bindings, and/or programming All Data is larger and recommended when need to see trends or events to help investigate the issue's timeline. Provide any information to replicate the issue. Provide as specific as possible steps used to create that outcome Provide VERSIONS of ALL software, hardware, and protocols involved If submit any captures or logs, perform the following: Provide any steps performed in EBO during the capture or log with the date & time, so these events can be matched.   Servers (EC/ES/AS) Collect logs from an Automation Server Collect logs from the Enterprise Server and Enterprise Central Backing Up EcoStruxure BMS Servers Manually  (Configuration Only or All Data) Server Fieldbus Protocols Infinet: Gathering Trace Log information for the Infinet bus in EBO Lon: (Video included) Analyze Lon communication using trace log in EBO Modbus: Capture a Modbus trace log in EBO/SBO   Software EBO Webstation Collect EBO Webstation browser logs EBO Workstation Collect EBO Workstation logs EBO Project Configuration Tool (PCT) Collect log files from Project Configuration Tool (PCT) Windows Review the Windows Event Logs. What specifically happens when an error occurs? Follow this KB article to view and save the Windows Events: Viewing, Saving, Sharing Windows Event Logs for Troubleshooting Purposes Wireshark For extended period capturing, use this article to set up a Ring Buffer in Wireshark. Wireshark capture ring buffer for continuous capturing Hardware b3/Infinet Controller Collect log from a b3 or Infinet controller BACnet/IP Controller Workstation method - BACnet/IP Controller Diagnostics Building Commission method - Viewing and Exporting Diagnostic Files (WebHelp) or Viewing Diagnostic Files (YouTube)   Protocols & Electrical Interfaces Ethernet Capture any ethernet traffic, including IP: Using WireShark to analyse communications on an Ethernet network Capture Loopback (127.0.0.1) traffic between applications and/or servers running on the same host OS: How to capture localhost traffic with Wireshark to help troubleshoot EWS communication issues Lon Using Loytec LPA with SpaceLogic Server AS-P RS-485 Fieldbuses include BACnet MS/TP, I/Net, Infinet, Modbus RTU BACnet MSTP Capture Application - Communities (se.com) aka mstpcap.exe BACnet - PicoScope Basics Picoscope Configuration for Modbus RTU capturing and decoding Modbus RTU capturing in Wireshark
View full article
Picard David_Purser Picard
‎2022-08-29 12:04 PM

Last Updated: Crewman ContentModerator ‎2025-08-11 04:10 AM

Labels:
  • EcoStruxure Building Operation
4468 Views

Collect logs from the Enterprise Server and Enterprise Central

Issue When troubleshooting server issues, it can be helpful to look at the logs that are recorded within the Enterprise Server or Enterprise Central Product Line EcoStruxure Building Operation Environment Building Operation Enterprise Server Building Operation Enterprise Central Cause Within the Enterprise Server and Enterprise Central logs are many records that are logged as a part of normal operations and unexpected events. Resolution Collect ES and EC Logs via EBO Workstation: Refer to the Workstation section of KB article: Collect logs from an Automation Server Collect ES and EC Logs via Windows Explorer, especially if ES or EC will not run as a service or keep crashing: The ES or EC database path is listed in Software Administrator.   For Windows 7, Server 2008, or higher, the default paths for the logs folder are: Enterprise Server: C:\ProgramData\Schneider Electric [EcoStruxure|StruxureWare]\Building Operation [n.n]\Enterprise Server\db\logs Enterprise Central: C:\ProgramData\Schneider Electric EcoStruxure\Building Operation [n.n]\Enterprise Central\db\logs In EBO V3.2 or higher, shortcut buttons can be found in Software Administrator to go to the folder for logs and database directly.    By default, the "Program Data" folder is hidden, so Windows needs to be configured to view hidden files and folders. For Windows 10 or 11, open Windows Explorer and select View > Show > Hidden items. For other Windows versions, please refer to this Microsoft help article: Show hidden files (microsoft.com). Using Windows Explorer, Navigate to the ES or EC logs folder to find System and Trace logs. Copy the Logs folder contents and send them to Product Support as a compressed file if required. To open a log file, Right-click on one of the logs and select Open with... Expand the window and select WordPad. For Windows XP:   Other ways to review site-specific issues: Is the issue site-specific regarding workstation being used or applications/programs running on these machines? Always try to keep the programs on a workstation to a minimum. Review the Windows Event Logs. What specifically happens when an error occurs? Follow this KB article to view and save the Windows Events: Viewing, Saving, Sharing Windows Event Logs for Troubleshooting Purposes - Communities Make sure that PCs and Windows OS used for WorkStation, ES or EC meet the requirements mentioned in Information Technology System Planning Guide (se.com) Make sure that the firewall and antivirus are correctly configured, and required ports are open for EBO, as explained in Information Technology System Planning Guide (se.com) Make sure that the current installed EBO version is supported, as per the Software Support Policy for EcoStruxure Building Operation - PA-00300. Check if Microsoft currently supports the installed Windows OS: Lifecycle FAQ - Windows | Microsoft Docs
View full article
Picard Product_Support
‎2018-09-06 03:56 PM

Last Updated: Crewman ContentModerator ‎2025-08-11 04:10 AM

Labels:
  • EcoStruxure Building Operation
5003 Views

Type of Acknowledgement set to 'Extended' on Sigma Interface object alarm and hardware alarm

Issue After a Sigma transition into EBO, alarm clears are requiring acknowledgements. In the Sigma Interface, the object alarm and hardware alarm 'Type of Acknowledgement are set to 'Extended' and cannot be changed to 'Single' Product Line EcoStruxure Building Operation, Satchwell Sigma Environment Building Operation Enterprise Server Satchwell Sigma Cause Alarm Clear Controls are incorrectly set in Sigma Alarm Manager. Resolution During the Data Import into EBO, the settings of the Sigma Alarm Manager is checked and the alarm clear acknowledgement type is set to a specific type. If acknowledgement on alarm clears is no longer required in EBO then it will need to be changed on the Sigma server,   To change to 'Single' so that alarms only are able to be acknowledged, in Sigma: Open the Alarm Manager and go to the menu options: Configure > Alarm Controls.   Uncheck the 'Alarm Clears Acknowledgeable' box.   Redo the Data Import, the 'Type of Acknowledgement' is now seen to be set to 'Single'. However, If it is now showing 'No', then the KB article Type of Acknowledgement set to 'No' on Sigma Interface object alarm will explain how to change this.
View full article
Sisko DavidChild Sisko
‎2022-02-28 07:48 PM

Last Updated: Crewman ContentModerator ‎2025-08-11 04:10 AM

Labels:
  • EcoStruxure Building Operation
  • Satchwell BAS & Sigma
1014 Views

Troubleshooting Smart Connector SoapEwsRestProvider connection with EBO

Issue SoapEwsRestProvider serves data sourced from any EWS Server using the standard EWS SOAP protocol. The architecture for the SmartConnector REST Extensions integrates Swagger to provide a rich self-documenting API. Below errors indicate configuration issues. The User Name or Password were incorrect.The User Name or Password were incorrect. "Message": "Authorization has been denied for this request. ""Message": "Authorization has been denied for this request. " "Message": "The HTTP request was forbidden with client authentication scheme 'Digest' ""Message": "The HTTP request was forbidden with client authentication scheme 'Digest' " Product Line EcoStruxure Building Operation. Environment Building Operation Automation Server Building Operation Automation Server Premium Building Operation Automation Server Bundled Building Operation Enterprise Server Building Operation Enterprise Central Cause Smart Connecter or EBO Incorrect configuration. Resolution Make sure that SboEwsRestProvider is started and has a correct port that is not used by any other Smart Connector data provider or other application.   Make sure that EWS server address has the following format: HTTP: http://ipAddress:port/EcoStruxure/DataExchange HTTPS: https://ipAddress:port/EcoStruxure/DataExchange For ES/EC, check software administrator to make sure there is no port conflict: Software Administrator shows red outline (box) on the Communication Ports (HTTP / HTTPS) - Communities (se.com) In EBO, make sure EWS server is enabled: Enabling the EcoStruxure Web Service Server Check if username and password used for the SOAP provide has correct permissions and can be used to login to EBO server. If the user is not located in the default domain, make sure to add the domain name in the Username string, ex. "Domain/User". If HTTP protocol is used (not recommended), check the following: In EWS server configuration, make sure that "Enforce Secure Communication" to Disabled. In Security Manager, make sure that "Enable Incoming http communication" is enabled.
View full article
Kirk Mahmoud_Sayed Kirk
‎2022-03-03 03:26 PM

Last Updated: Crewman ContentModerator ‎2025-08-11 04:10 AM

Labels:
  • EcoStruxure Building Operation
2450 Views

OPC or DDE with EcoStruxure Building Operation

Issue Support for OPC or DDE integration with EcoStruxure Building Operation Product Line EcoStruxure Building Operation Environment Building Operation Enterprise Server Building Operation Automation Server Premium Cause The OPC Server is a software program that converts hardware communication protocol into the OPC protocol. The OPC client software is any program that needs to connect to the hardware. The OPC client uses the OPC server to get data from or send commands to the hardware. Resolution Neither the OPC server nor the DDE configuration is supported at this time. There is not currently a roadmap for direct OPC client or server capability within the EcoStruxure Building Operation. To avoid problems with OPC Integration (and lose a project), there are two options for OPC integeration: It is possibe to use a converter to convert OPC to/from one of EBO supported protocols.  For example, use a 3rd party software to translate all the OPC points into BACnet Objects, “OPC Server -> BACnet Server”, or translate all EBO BACnet points to OPC. Perhaps one of the software programs below will be of benefit. Take into consideration what specifically will the ES be doing. If it is exchanging point values then it should work fine. Kepware Matrikon SCADA engine Note: These are 3rd party products that are not supported by Shneider Electric.    Use a SmartConnector Extension to be a middleware between EBO and OPC cilent or server. Check available extenstions at Exchange shop and SmartConnector Server and refer to EBO SmartDriver and Smart Connector KB article for more information.
View full article
Picard Product_Support
‎2018-09-10 05:35 AM

Last Updated: Crewman ContentModerator ‎2025-08-11 04:10 AM

Labels:
  • EcoStruxure Building Operation
4931 Views

Obtaining a Database Schema for EBO WebReports / Report Server

Issue Where can you obtain the Database Schema for the EBO WebReports / Report Server Database Product Line EcoStruxure Building Operation Environment Building Operation Report Server Cause From EBO version 3.2.x WebReports/RS is no longer being developed as we move to External Log Storage with Postgres and Timescale DB.    To allow our customers to continue to work with existing WebReports/RS databases if they so wish, it may be helpful to provide the DB Schema. Resolution An inbuilt Report already exists within WebReports call 'Database Schema' which allows you to select which Tables you would like to see in the WebReports / RS Database Running this will produce a .pdf Report detailing the RS Database Schema tables, to aid with 3rd Party integrations and other DB manipulation. A full database schema report is attached for reference (Version 3.2.3) 
View full article
Admiral David_Kendrick Admiral
‎2022-03-14 08:36 AM

Last Updated: Crewman ContentModerator ‎2025-08-11 04:09 AM

Labels:
  • EcoStruxure Building Operation
4075 Views

Understanding the FILE part of a XIF file

Issue When having issues with a specific NCI (SCPT or UCPT) in a XIF file it can be hard to understand the FILE definition in the XIF file in order to troubleshoot a given issue For information regarding NCI's that are not part of a FILE definition, refer to Understanding the NVVAL part of a XIF file Product Line EcoStruxure Building Operation, Satchwell MicroNet, Satchwell Sigma, TAC IA Series, TAC Vista Environment LonWorks XIF Cause The FILE definition can be somewhat cryptic - here is an example   FILE template 0 2 "1.1;" "2,23.24.25.26.27.28.29.30.31.32.33.34.35.36.37.41.42.43.45.46,0\x80,49,2;" "1,1,0\x80,60,12;" "1,1,0\x80,52,2;" "2,0.2.3.5.6.7.8.9.10.16.17.18.19.20.21,0\x80,48,2;" "1,0,0\x80,17,31;" "1,1,0\x80,34,2;" "1,1,0\x80,23,2;" "1,1,0\xA4,169,1;" "1,1,4\x80,3,8;" "1,1,4\x80,5,17;" "1,1,3\x80,1,2;" "1,1,4\x80,4,9;" "1,1,4\xA4,13,1;" "1,1,4\xA4,14,1;" "1,1,4\xA4,15,1;" "1,1,4\xA4,16,1;" "1,1,4\xA4,17,1;" "1,1,4\x80,18,1;" "1,1,0\x80,42,2;" "1,1,0\x80,36,2;" "1,1,0\x80,193,2;" "1,1,4\x80,8,2;" "1,0,3\x80,2,2;" "1,0,0\x84,165,1;" "1,0,0\xA4,166,1;" "1,1,6\xA4,2,8;" FILE value 1 1 116 0x0B, 0xB8, 0x09, 0x1D, 0x09, 0xFB, 0x0B, 0x80, 0x08, 0x77, 0x07, 0x98, 0x06, 0x13, 0x00, 0x02, 0x23, 0x28, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x78, 0x7F, 0xFF, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x80, 0x80, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x01, 0x00, 0x00, 0x00, 0x00, 0x00, 0xFF, 0xFF, 0x7F, 0xFF, 0x7F, 0xFF, 0x13, 0x88, 0x00, 0x00, 0x02, 0x0B, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00 Resolution The FILE section describes the configuration variables (or SCPT's and UCPT's) for a device. Here is an explanation of the various parts of the FILE section.
View full article
Picard Product_Support
‎2018-09-11 03:06 PM

Last Updated: Crewman ContentModerator ‎2025-08-11 04:09 AM

Labels:
  • EcoStruxure Building Operation
  • Satchwell BAS & Sigma
  • Satchwell MicroNet
  • TAC IA Series
  • TAC Vista
2910 Views

Can TAC BACnet (Viconics) thermostats have identical names and deviceids within sub networks using their default names?

Issue Can TAC BACnet (Viconics) thermostats have identical names or device ids within sub networks using their default names? Product Line Andover Continuum, EcoStruxure Building Operation Environment Viconic BACnet Thermostats BACnet BCX B4 MSTP Cause Viconic stats need a unique address and unique name across the entire BACnet network. Resolution BACnet Viconics thermostats must have a unique name and device id across the entire BACnet network. The BACnet data link layer has two key parameters: the device object name and the device object ID. The device object name must be unique from any other BACnet device object name on the BACnet network (i.e. not just the MS/TP sub-network). Typically this question comes up because a thermostat will not come online. Run an acctrace during the Find and you will probably see a duplicate MAC address. Once you have given unique names and comm addresses to each of the thermostats on the entire BACnet network, these devices should communicate and come online properly. Each of the Viconic stats are given a unique name that includes the address (once it has been made unique) To change the communication address: Hold down the menu button until the option for menu comes up Answer the questions for the various options and eventually you will be brought to change comm address. Change Comm address, select Yes and then use the up or down arrows to give this MSTP Viconic stat a unique address. There is a Configuration Tool to access and edit the name and device id unique naming scheme. Click here for ViconicsConfigurationTool.zip. Installing and using the Viconics Configuration Tool on a Windows Laptop  You will need a serial adapter connection to tie into the MSTP bus that the thermostat(s) are connected to Select the Viconics folder > ViconicsConfigurationTool.zip You can install this ZIP file in any directory you wish, but the bacdocm.ini file must be installed on your C:\Windows directory. Use the bacdocm.ini file to configure your network settings at the Configurator Tool level. You can set the MAC address of your tool, the baud rate of your connection (max 38400 - limited by the RS-232 to RS485 port and Windows) etc. The "Our Device Instance" value represents the MAC address of the tool which must be unique on the MSTP network. Also the "MaxMaster" value must be set to a higher value than the highest MAC value on the MSTP network. You can edit this INI file to modify your settings OR you can modify the settings by going though the BACdoor Configuration Tool. Once you launch the Configuration Tool, you'll notice a white applet appearing at the right bottom of your screen. That is the BACdoor MSTP sniffer that actually looks for devices and objects. If you click on that icon, and select the "Configure" tab, a configuration window will be displayed. Select the baud rate at which you want to communicate with your device. This BACdoor configuration does the same thing as changing the BACDOCM.ini file (if properly located in C\Windows). Launch the Configurator Tool application. It automatically looks for devices on that network (at the baud rate set in the bacdocm.ini file or in the BACdoor Configuration window). If no device is detected an error message will pop-up after 1-2 minutes. All discovered devices will show up in the "Device List" you have to "Connect to device" in order to list all the objects of that device. After you changed the Baud Rate, you have to click on the "Apply changes" button. Don't forget that the max speed of this tool is 38400. For the first connection, you need to power cycle the thermostat (if it was running at 76800 previously) so that it auto-detects the 38.4 network. Once you set it to 76.8, you can not connect to that thermostat with the tool because of that 38.4 limitation. Also this tool does not support Read Multiple Property so it reads every property of every object one at a time. In its default mode of operation, the device will automatically match its baud rate to the baud rate of the network. Automatic baud rate detection will occur when the MS/TP communication port is initialized (on power up). If the network speed is changed, the device will keep listening at the previously detected speed for 10 minutes before resuming auto-bauding. Re-powering the devices will force right away auto-bauding. SE7xxx series requires the tool. The SE8xxx series does not as access is available through the menu on the device.
View full article
Picard Product_Support
‎2018-09-07 12:48 AM

Last Updated: Crewman ContentModerator ‎2025-08-11 04:09 AM

Labels:
  • Andover Continuum
  • EcoStruxure Building Operation
1647 Views

Calibrating Airflow on a Xenta 102-AX (or MR-VAV-AX) using the M/STAT

Issue Step-by-step instructions for calibrating airflow on a Xenta 102-AX (or I/NET MR-VAV-AX) using the M/STAT. Test and air balance procedure for balancing airflow Product Line EcoStruxure Building Operation, TAC INET, TAC Vista Environment Xenta 102-AX MR-VAV-AX M/STAT Cause The preferred method for calibrating airflow in Xenta 102-AX or MR-VAV-AX is through the plug-in.  However, this is not always an option, especially when the responsibility for calibrating is given to a third party test and balance company.  Pocket references exist for navigating through the M/STAT menu, but there aren't clear step-by-step instructions to tell exactly how to perform the calibration. Resolution Click here to download this document in Microsoft Word format Connect M/STAT Plug the M/STAT into the jack on the thermostat. The initial display shows the set temperature.   Enter Password Press the Service button. This prompts you to enter the service mode password. Default password is 183. Use the +/- keys to set each digit and the enter key to submit. If the password is incorrect, the display will blink. Airflow Parameters If the password is correct, the first menu option – Unit Parameters (UP) – is displayed. Hit the select button down twice until Airflow Parameters (AP) is displayed. Press enter. Cooling Low Flow Setpoint The first option is Cooling Low Flow Setpoint (CLF). Press enter to view the setpoint (divided by 1000). Record this value. Press the service key to escape out of the menu. Cooling High Flow Setpoint Navigate to Cooling High Flow Setpoint (CHF). Press enter to view the value (divided by 1000). Record this value. Press the service key to escape out of the menu. Reset Factory Calibration Navigate to Factory Calibration Settings (FCS) and press enter. Use the change keys to display “YES” and press the enter key. This will set the box back to default settings. This is a good idea to do prior to every calibration. Press the service key to escape out of the menu. Calibrate Low Airflow Navigate to Calibrate Low Airflow (CPL). Press enter and the current airflow is displayed. Wait for the airflow to reach the CLF and level out. Once the value is steady at setpoint, press the enter key only once. The display does not change. Enter Actual Low Airflow Measure the actual airflow. Use the change keys to set the display value to the measured value. Press the enter key. Choose One or Two-Point Now Calibrate High Airflow (CPH) is displayed. If one-point (offset only) calibration is desired, press the service key to escape out of this mode and calibration is complete. If two-point (gain and offset) calibration is desired, press enter to continue to the next step. Calibrate High Airflow The current airflow is displayed again. Wait for it to rise to meet the CHF and level out. Once the value is steady at setpoint, press the enter key only once. The display does not change. Enter Actual High Airflow Measure the actual airflow. Use the change keys to set the display value to the measured value. Press the enter key. CPH is displayed again, this time as a general menu item. Escape Service Mode Press the service key to escape out of the menu. If you are finished configuring the box, escape all the way back out of the service menu before disconnecting the M/STAT. Disconnecting in configuration mode can leave the stat displaying “00” or other incorrect numbers.
View full article
Picard Product_Support
‎2018-09-07 07:09 AM

Last Updated: Crewman ContentModerator ‎2025-08-11 04:08 AM

Labels:
  • EcoStruxure Building Operation
  • TAC INET
  • TAC Vista
3152 Views
  • « Previous
    • 1
    • 2
    • 3
    • …
    • 93
  • 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