Welcome to the new Schneider Electric Community

It's your place to connect with experts and peers, get continuous support, and share knowledge.

Explore the new navigation for even easier access to your community.
Bookmark and use our new, easy-to-remember address (community.se.com).
Get ready for more content and an improved experience.

Contact SchneiderCommunity.Support@se.com if you have any questions.

Invite a Co-worker

Send a co-worker an invite to the Exchange portal.Just enter their email address and we’ll connect them to register. After joining, they will belong to the same company.

Send Invite Cancel

How can we help?

Building Automation Knowledge Base

Access this self-service resource 24/7 and post your questions or scroll through forums for answers on building automation.

Issue What mode must a LoyTec L-IP be configured to work with EcoStruxure Building Operation? Product Line EcoStruxure Building Operation Environment Loytec L-IP Enterprise Server Cause The operating mode limits the capabilities of the LoyTec L-IP when used with an Enterprise Server Resolution Smart Switch Mode Ensure that the LoyTec L-IP is in Smart Switch mode. This is achieved by using the DIP switch settings for switch 1 and 2 in the ON position. Reset Forwarding Tables Press the status button for at least 20 seconds. This will clear the forwarding group, the subnet/node forwarding, and the router domain table when used in smart switch mode. Important: If the L-IP is operated in smart switch mode and is moved from one location to another or if major changes to the configuration of the network are made, it is recommended to reset the L-IP forwarding tables Important: Wait at least 30 seconds after power-up of the L-IP before pressing the Status Button to ensure that the L-IP has booted properly! For additional detail please reference the LoyTec L-IP user manual.

Issue Troubleshooting Sigma IC LON Values going on and offline Product Line Satchwell Sigma Environment Sigma Release 4_05-SEB (Build 3_43_18) Sigma Release 4_05-SP2 (Build 3_42_48) Sigma Release 4_06 (Build 3_44_14) Sigma Release 4_06 SP1 (Build 3_44_16) Sigma Release 4_07 (Build 3_45_48) Sigma Release 4_07-SP1 (Build 3_45_51) Sigma Release 4_07-SP2 (Build 3_45_58) Sigma Release 4_08 (Build 3_46_57) IC LON Cause Lon Values going into and out of default Resolution Compare the IC-LON’s Receive heartbeat set in the “gateway.txt” file in the IC-LON controller, to the send heartbeat set in the controller. The recommendation is for the receive heartbeat be set to 2-5 times the send heartbeat of the field controller. Starting at 2 times, then increasing if the problem persists. If the controller doesn’t have a heartbeat and the LON value rarely changes, disable the receiver heartbeat in the IC-LON’s gateway.txt file by setting the heartbeat to 0. Example: 1 2 3 4 5 6 7 2, 2, 112, 1293, 0, 0, 0 The Sigma system is now out of its support period, consideration should be given to transitioning or upgrading to SpaceLogic - EcoStruxure Building Operation.

Issue Need to send Continuum alarm messages to email addresses Product Line Andover Continuum Environment Continuum Cyberstation Cause Alarm delivery required to remote users via email. Resolution Please note this resolution is applicable to all versions of Continuum Cyberstattion and requires Microsoft Exchange or Outlook to send emails. However, CyberStation version 2.xx does not necessarily require Microsoft Exchange or Outlook to send emails for alarm notifications. Instead, it is possible to configure an SMTP server on the network and use it to send alarm email notifications directly to the intended recipient. Please refer to SMTP Email Alarm Configuration in Continuum 2.00 to 2.03 Here are some requirements for forwarding Continuum workstation alarm events via email and paging: The Continuum workstations that have been designated primary and backup email and/or page handlers must have an email client such as Microsoft Exchange or Outlook. The email client application must communicate with an existing email server application, such as MS Exchange Server. The primary or backup email/paging workstation must be running Continuum at the time an alarm is generated. Each EventNotification object associated with the alarms that you wish to email or page must have its own email distribution list in the personal address book of the client email application using a specified naming convention as outlined in the table below. This email distribution list must be stored in the first address book shown in the list of available address books in the email client application. For example, if you create an EventNotification distribution list in the Personal Address Book in Microsoft Outlook, then the Personal Address Book must be the first one showing in the address list dropdown box when you open the Address Book. How to Create an EventNotification Distribution List Note: The following steps are based on Microsoft Outlook. Other mail applications may have different menu names and choices but the general procedure is the same. Step Action 1 Open the Address Book for the email account on the Continuum workstation that will be providing the email/paging services. Your toolbar may have a button for this. If not, use the Address Book option of the Tools menu. 2 Select New Entry from the Address Book File menu. 3 Select the entry type Personal Distribution List and put this entry in the Personal Address Book. 4 In the Name field enter a name for the distribution list using the following format: For E-mail: ACC.name For Paging: ACC.page.name where name is the name of the EventNotification. 5 Add members (the email addresses or pager and service numbers of those to whom the notification of the alarm will be sent) to your personal distribution lists. 6 Set address book options so that the address book where your personal distribution lists are stored is the first one to be searched when sending emails or pages.

Issue What is the password recovery procedure for the SpaceLogic Operator Display if the password is lost? Product Line EcoStruxure Building Operation Environment SpaceLogic Operator Display Cause If losing the password for the SpaceLogic Operator Display there is no password recovery procedure available to recover it. The only option to access the device again is to do a device recovery procedure on the device. When doing a device recovery on the device everything on it, all users, configuration data, and logs will be deleted and a new firmware loaded into the device Resolution Steps to perform a device recovery procedure: Download the device recovery file (tar.gz file) which is included in the “SpaceLogic Operator Display HMIST6400SL Firmware Package” which you can download from Schneider Electric Exchange Extract files and copy them to a USB stick (Format: FAT) a. Unpack the tar.gz b. Two unpacks are required, then "aurora" folder should be present c. Copy whole "aurora" folder to a USB stick d. The structure on disk should be: e. aurora (folder)-FIRMWARE (folder)- AURORA.CFG-nand.img Power off OPD (Operator Display) Connect a USB-OTG cable (On-The-Go cable, USB-micro-B to USB-A) to the USB-2 port on the rear of OPD . Note: The cable is like a key, to enable device recovery. Do NOT connect USB stick to cable. Connect the USB stick to the USB-1 port on the rear of the OPD Power on OPD Device will boot to a white screen and display: Recovery Mode Loading nand.img... Writing KERNEL... Writing ROOTFS... Udisk upgrade success! (Loud beep) "Upgrade successfully, Wait to Reboot!" Power off OPD. Remove USB stick and USB-OTG cable Power on device and it will boot to the loaded firmware Firmware version is shown on startup screen. For more details see video:

Issue What is the Intel Floating point number as used in the Modbus X Driver? Product Line Andover Continuum Environment Modbus RTU X Driver Cause It is not clear how the two special floating point function codes vary. Resolution There are two different floating point data formats (248 & 245) these are both standard 32 bit floating point numbers but the data bits stored in memory (or read over the protocol) differently. The 32 bits of Function 248 are stored as one string of bits, bit 0 through to bit 31. For the 245 format the upper and lower words are swapped around, so it stores the data as bits 15 to 0, then bits 31 to bit 16. This format is called Intel format as it is the way Intel microprocessors handle floating point data. Here is a link to information on floating point numbers FYI: https://en.wikipedia.org/wiki/Floating-point_arithmetic These two formats can also be called Big Endian (Function 248), or Little Endian (Function 245). Little Endian is also known as the Intel format. Information on Endianness can be found at: https://en.wikipedia.org/wiki/Endianness

Issue How does Modbus scattered read work? Product Line EcoStruxure Building Operation Environment EcoStruxure Building Operation Workstation (1.5 and above) EcoStruxure Building Operation Modbus Cause Requirement to optimise communication over Modbus to improve performance. Resolution The following is an extract from Web Help. The complete section can be viewed at Modbus Batch Read Function: 'Scattered read is an enhancement to the batch read function that enables multiple, non-contiguous slave device registers to be read in a single Modbus query. By using the scattered read function, you can enable the Enterprise Server or Automation Server to avoid reading a large block of contiguous registers when it is only necessary to read a few registers. Also, using scattered read avoids the multiple use of group function codes 03 (analog output holding registers) and 04 (analog input registers) in order to read non-contiguous registers. Group function codes 01 (discrete output logic coils) and 02 (discrete input contacts) are not supported for scattered read. Scattered read is available only for supported devices, for example, Schneider Electric branch circuit power meters with split core CTs. Furthermore, the scattered read function applies only when the Enterprise Server or Automation Server is operating as the master, not as as a slave. You can enable the scattered read function in the properties of all Modbus devices. However, if a device does not support scattered read, the device is polled by the master device in the same way as if you had not enabled scattered read.' The image below shows the properties dialogue window for a Modbus device and the corresponding setting. The left is version 3.1 and above, the right is version 3.0 and below where it is referred to as 'Non-contiguous read'. Refer to the Modbus TCP Device section on Web Help for more information.

Issue How are the 'Advanced Polling Configuration' settings under the BACnet interface to be used? Product Line EcoStruxure Building Operation Environment Enterprise Server (ES) Automation Server (AS) Cause These settings can be used to reduce traffic on the BACnet networks that can overload both the EBO server as well as the devices being polled. Resolution The settings are used to specify an amount of time (in milliseconds) that the server should wait after completing a polling cycle on the applicable BACnet network before starting the next cycle. A polling cycle is the set of point being polled on a particular network interface. For example, lets assume that the Minimum polling interval for MSTPA network has been set to 1000 ms, if you are polling 30 points on MSTP port A then the BACnet plug in will do synchronous ReadProperty requests to poll each of the 30 points one at a time. Once the 30 points are polled, (one polling cycle) the BACnet plug-in will delay 1000ms before polling the 30 points again. (next polling cycle) NOTE: The settings apply to polling ONLY and do not affect communications done via change of value (COV) To find a proper value to use, it is recommended that you start with 1000 ms and then adjust the value up or down based on polling performance. If the polled values update fast enough, increase the minimum polling interval to reduce CPU usage. If the polled values become too sluggish, reduce the minimum polling interval until performance returns to satisfactory levels. It may take some trial and error to find the optimum balance.

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

Issue Understanding Access Expert's schedules holidays and one-offs and their interaction with Triggers and Procedures Product Line EcoStruxure Access Expert Environment Access Server Hosted Software Access Server Premise Software Cause More details on schedules holidays and one-offs are needed to clear confusion about Triggers & Procedures configuration. Resolution Let's first break this down into some basic principles on Schedules and Holidays. Schedules can become active or inactive. A status change is commonly used as a Trigger to some procedure (ie change a reader mode to unlocked) Holidays act as schedule masks so that schedules cannot become active or inactive, thus never triggering. With that in mind; One-off dates are SCHEDULE behaviors, similar to how choosing "Monday" is a scheduled behavior. All schedules can be masked by holiday configurations. Special dates are HOLIDAY behaviors. They act as flags that effectively invert the bit that would normally mask, performing the inverse behavior. Now that we've established those event types and configurations, let's go over Triggers & Procedures. As mentioned in (1) that a status change is a trigger because it is a generated Mercury event. These triggers do whatever procedure you instruct them to do. As a result, whenever a trigger occurs that activates procedures A or B, or C, those procedures will execute. When configuring many reader modes you can quickly and easily produce conflicts where a schedule becomes active and thus a procedure occurs, which sets a behavior that another schedule does not like because that trigger already happened. There is no concept of "following a schedule" in Mercury. In order to correctly configure reader modes, you will want to limit the normal modes to as few as possible (preferably 1) and instead create intelligent sets of schedule INTERVALS within one schedule, more specifically, you wouldn't use multiple modes, you would use 1 mode with a schedule containing multiple intervals. If you would like a schedule to ignore a holiday, you would set "ALWAYS ACTIVE ON" and choose your holidays in the interval(s). The trick here is not to apply holidays to schedules that are not normally active. Mercury controllers support up to 8128 Triggers and 8128 Procedures. Holidays Mask schedules from becoming active. Always Active On will ensure that a schedule is NOT MASKED for that holiday group, by flipping a bit. For customers using many sites which their own holiday restrictions, we offer enterprise licensing. Each location should have its own shared instance where holidays are localized to that instance's controllers and hardware. Holidays should only be implemented when you want to mask schedules, if you then have schedules that shouldn't be masked, you would apply the "always active on" for those groups. If you have a schedule that won't become active on that holiday, then there's no need to override using always active on.

Issue Internal counter stops counting. Product Line EcoStruxure Building Operation Environment Script Function Block Counter 167777216 Cause When this script is used it stops counting at 16777216. Numeric Output CountOut Main: CountOut = 16777100 goto Counter Counter: CountOut = CountOut + 1 Resolution This issue was identified in the early days of Continuum and is regarded as a limitation, not a defect. Explanation - Internally the Script handles all numbers as IEEE754 single precision floats, which means that 16777216 is handled as 1.6777216E7. Adding 1 to 16777216 is unrecognizable in that representation. Using an IEEE754 converter at https://www.h-schmidt.net/FloatConverter/IEEE754.html, one can see that 16777216 and 16777217 have the same binary representation. The point at which the counter will stop, will depend upon the value being added each time, so adding 0.9 will count to a different number than adding 1. The counting range can be extended by two or more variables as shown below. Numeric Output CountOut Numeric CountOut1 Numeric CountOut2 Main: CountOut1 = 16777100 goto Counter1 Counter1: CountOut1 = CountOut1 + 1 CountOut = CountOut1 if CountOut1 = 16777216 then goto Counter2 Counter2: CountOut2 = CountOut2 + 1 CountOut = CountOut1 + CountOut2

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 User of EcoStruxure Building Operation WorkStation used the "Remember me on this computer" option and logged into an account that does not have account rights to logout. Product Line EcoStruxure Building Operation Environment WorkStation Cause A situation such as this could happen either due to inattention of the user or because of planned system design (Kiosk with Building Operation WorkStation logged into a read only account). However it might be necessary due to maintenance to adjust the login option. In the absence of a kiosk situation, it is recommended to always leave the ability for a user to logout by only hiding the toolbar instead of disabling it. Resolution The solution can differ depending on the installation or usage scenario. User has access to log off option Once logged into Building Operation WorkStation use the log off option to return to the login prompt Uncheck the "Remember me on this computer" option. Enterprise Server on another computer or accessing an Automation Server Disconnect the Ethernet cable for the computer or disable the network port Building Operation WorkStation attempts to login returning user to the login prompt. Enterprise Server on same computer The Enterprise Server can be stopped temporarily and the next attempt to start Building Operation WorkStation will result in a communication failure allowing you to modify the "Remember me on this computer" selection. This could result in loss of data while the Enterprise Server is stopped. Delete the Building Operation WorkStation configuration file (named either SBO.ClientUserProfile.bin or TAC.ClientUserProfile.bin for older versions) stored in the computer application data. Deletion of this file will result in loss of custom settings such as column widths and similar customizations.

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 After successfully setting up KIOSK mode to automatically login in to WebStation another user wants to login through WebStation on the same PC. Product Line EcoStruxure Building Operation Environment EcoStruxure Building Operation WebStation Cause The GUEST account login URL used with KIOSK mode retains the last user logged in and the WebStation menu bars have been removed so that user cannot "logout". Any subsequent attempts to access the WebStation using the same browser result in being automatically logged in under the GUEST account. Resolution The "KIOSK" link that you create will login automatically with the GUEST account as long as the GUEST account has already been created in the ES/AS. This then must set the "last credentials" in IE for that website and any subsequent connections to that server, even to the direct login URL, result in automatically being logged in with those last credentials. One of the two options below should work to disable GUEST login depending on where your ES is located. Enterprise Server on another computer or accessing an Automation Server Disconnect the Ethernet cable for the computer or disable the network port while Building Operation Workstation attempts to login returning user to the login prompt. Enterprise Server on same computer The Enterprise Server can be stopped temporarily and the next attempt to start Building Operation Workstation will result in a communication failure allowing you to modify the "Remember me on this computer" selection. To be prompted for a login: Disconnect the ES/AS with one of the options above. Then try to connect to the server page at "http:/localhost:444" (or your specific URL:Port). This results in a "this page can't be displayed" (or similar) message. Then start the service, or reconnect cable, and again attempt to connect to "http:/localhost:444". You should be presented with the login page. Do not try to open up the "KIOSK" URL or else this will again login with the GUEST account and you'll be back to square one. The next time you use the "KIOSK" URL it will automatically login with the GUEST account and this will again be used for subsequent logins until the above steps are repeated. Note1: This could result in loss of data while the Enterprise Server is stopped. Note2: Also see StruxureWare Building Operation Workstation Auto Login feature locked if encountering this issue with a Workstation.

Issue Unable to see EWS objects/points under an EcoStruxure Web Services interface Product Line EcoStruxure Building Operation Environment EcoStruxure Web Services (EWS) Enterprise Server Automation Server Cause An EWS License may be needed to allow your ES/AS to use EcoStruxure Web Services Resolution Purchase and install an EWS License if required. Note: The EWS option is NOT required when using EWS to integrate between two Schneider Electric systems or services. Refer to PA-00349 for details. This includes the new Smart Connector by Schneider Electric which does not require an EWS License but does require a Smart Connector License as usual

Issue How to transfer EBO 2022 or higher data to Azure IoT hub via MQTT protocol Product Line EcoStruxure Building Operation Environment Building Operation Enterprise Server Building Operation Automation Server Premium Building Operation Automation Server Bundled Cause Need to configure EBO MQTT interface and Azure IoT Hub, so EBO can send MQTT messages to Azure MQTT IOT Hub. Resolution The following video will illustrate how to: Create Azure IoT hub and IoT device using Azure Portal Create IoT interface and Azure MQTT client in EBO Configure the MQTT connection Create and configure a data group Test the connection Things you need: EBO 2022 or later with valid MQTT license or demo license (Enterprise Server, AS-P or AS-B) valid Azure Subscription with possibility to use free account during testing. For each Azure subscription one IoT hub in the free tier can be created, refer to IoT Hub | Microsoft Azure Visual studio code to be used to test the connection between EBO and Azure IoT hub, can be download from: Visual Studio Code

Issue Automation / Enterprise Server configuration very slow Attempting to make any configuration changes in the AS such as creating a new point/value or modifying existing objects is extremely slow. Note: This applies to the ES as well although less of a problem since the ES has better resources than the AS. CPU usage as seen in the Status Information of the server is very high. (above 80%) Question marks are shown on many objects in the application folder of third party BACnet devices that have been uploaded to the AS Enterprise Server takes a long time to startup (15 minutes) before allowing users to log on with Workstation. Deleting the BACnet Interface allows log on with 2 - 3 minutes on a restart. Product Line EcoStruxure Building Operation Environment Automation Server Enterprise Server BACnet Cause Uploaded BACnet devices contain unresolved references to notification class object(s) Resolution Ask for SE.SBO.ES-AS-1.5.0.1501-Hotfix. (SE.SBO.WS-1.4.1.16001-Hotfix for 1.4.1, there is no hot fix for versions before 1.4.1) After applying the hot fix the server should become responsive. The unresolved references can typically be cleaned up by creating a BACnet Notification object in the application folder of the third party BACnet device proxy that reside in SBO and manually setting the Instance ID to 0 (zero) NOTE: Cases have been seen where multiple notification class objects must be created using instance IDs 0,1,2,3,4 in order to clean up all the unresolved references. A few minutes after the notification class object with the proper instance ID is created the question marks should disappear from the icons and created notification class object will show up in the intrinsic alarm property as seen below. If creating the notification class objects with the above instance IDs does not resolve all the references a backup of the server can be provided to PSS, a PSS/R&D engineer can look directly at the database to determine the proper instance IDs the unresolved references are looking for.

Issue After setting up a UNC as a BBMD the other UNC's on that subnet are getting "network mismatch" errors in their standard output windows. Product Line TAC IA Series Environment R2 UNC's with BACnet jar's earlier than 535a. Cause This type of error is indicative of a routing loop on the BACnet internetwork. UNC's with a BACnet jar prior to 535a when set up as a BBMD will broadcast on their own subnet as well as to the other BBMD's and this can cause that also. Resolution Install BACnet jar 535a or later in the UNC that is the BBMD to see if this corrects this issue. If the issue persists investigate the BACnet internetwork for a router loop.

Issue How to configure a G3 station as a BACnet BBMD Product Line TAC IA Series Environment I/A Series G3 version 3.3.22 and later Cause Documentation Resolution In the G3 Station, expand the BacnetNetwork, expand Bacnet Comm, expand Network, and then double-click IP Port. The IP Port Property Sheet opens (see below) In the IP Device Type drop-down, select Bbmd. Click Save The station is now configured as a BACnet BBMD