Building Automation Knowledge Base

Issue Do the light emitters in the I2-210 Fiber repeater use an LED or LASER light source Product Line Andover Continuum  Environment I2-210 Fiber repeater Cause Fiber optic modules light source type Resolution The transmitter in the B-LINK-F is LED; it is specified as an AEL Class 1 LED light source and is considered "eye safe"

Issue When a SED-TRH-G-5045 sensor is positioned outside the range of the main EBO Zigbee wireless mesh, what is the recommended method or product to extend the wireless coverage? Product Line EcoStruxure Building Operation Environment Building Operation Automation Server Premium Cause The SED-TRH-G-5045 is a Zigbee pro sleepy end device. Resolution Any Zigbee router within the system can function as a repeater to extend the radio communication. The router should be positioned within the radio range of the sensor and within the range of the RPx or another router. If a Zigbee device is powered by mains, it typically operates as a router. While there are currently no SE products designed solely with "repeater capability," several SE products possess router capabilities in addition to other capabilities, SE8000 SpaceLogic room controller Wiser plug CCTFR6500 Wiser Power Micromodule CCTFR6730 Wiser Room Thermostat with display CCTFR6400 or CCTFR6401. We have not officially tested any 3rd party Zigbee routers, however the IKEA TRÅDFRI repeater is known to work effectively.

Issue The first batch of White TRCs (produced in 24H1) could appear too bright in some low-light level situations. All future batches (post 24H1) do not have the issue. See the precise list of affected serial numbers in the appendix section below. Product Line EcoStruxure Building Operation Environment SpaceLogic Touchscreen Room Controller Cause The housing color is set in the device’s manufacturing configuration to tell it what color the screen bezel is (black or white). White TRCs produced with an incorrect housing color will read a higher value for light level. This has a direct impact on the backlight dimming levels, and the only effect will be the screen staying brighter in dark rooms. Resolution Customers experiencing brightness issues may simply adjust the backlight brightness parameters to a lower value, which are configurable in the TRC configuration screens and via BACnet/Modbus. This would reduce the overall brightness of the devices immediately, without fixing the housing color. We recommend going with a permanent fix, by setting the housing color via the USB port. The steps to fix this permanently would be: Connect USB-C cable to TRC Log in as an administrator into the TRC’s configuration screens (to enable USB connection) Open a terminal app like hyperterm or putty, with settings: Speed (baud): 115200bps Data bits: 8 Stop bits: 1 Parity: None Paste in the command: #001000061009FE00009C! Device responds: #000E00071009FE0051! To confirm or test, paste in the command: #000C00001009FEE8! Device responds: White housing: #001200011009FE000000F9! Black housing: #001200011009FE000001FA! Examples Below is an example of 4 white TRCs: The two (2) outermost devices are too bright (leftmost and rightmost white TRCs). The two (2) devices in the middle have been corrected to show adequate brightness. Appendix Since the Touch Room Controller’s serial number includes the date code, knowing whether a unit is impacted is very straightforward. Follow these instructions to determine if the unit of interest is impacted: Retrieve the serial number from the unit you suspect has the incorrect housing color. Example: FL24075TRC00002 Examine the serial number date code, wrapped between the “FL” and “TRC” substrings. Example: 24075 Decrypt the date code, using this logic: 24: year 2024 07: week 07 of 2024 5: day 5 of week 7 of 2024 If the date code is between the values 24074 and 24285, the product is impacted. Products outside of this date code range are not impacted, and no fix to housing color will be needed.

Issue Required a VPAT (Voluntary Product Accessibility Template) or statement of accessibility for EcoStruxure Building Operation. Product Line EcoStruxure Building Operation Environment EcoStruxure Building Operation Cause The Voluntary Product Accessibility Template (VPAT) is a document that evaluates how accessible a particular product is according to the Section 508 Standards. It is a self-disclosing document produced by the vendor which details each aspect of the Section 508 requirements and how the product supports each criterion. VPATs are used by buyers to determine how accessible a product is and where any potential deficiencies are. They are required by some buyers before a purchase is made. More Information can be found from the below public links: Section 508 of the Rehabilitation Act of 1973 Voluntary Product Accessibility Template (VPAT) Overview of Technologies and Formats WHAT IS A VPAT AND HOW IS IT USED? Resolution Schneider Electric does not have a VPAT document for EcoStruxure Building Operation.

Issue Required a VPAT (Voluntary Product Accessibility Template) or statement of accessibility for the Andover Continuum System. Product Line Andover Continuum Environment Andover Continuum Cause The Voluntary Product Accessibility Template (VPAT) is a document that evaluates how accessible a particular product is according to the Section 508 Standards. It is a self-disclosing document produced by the vendor which details each aspect of the Section 508 requirements and how the product supports each criterion. VPATs are used by buyers to determine how accessible a product is and where any potential deficiencies are. They are required by some buyers before a purchase is made. More Information can be found from the below public links: Section 508 of the Rehabilitation Act of 1973 Voluntary Product Accessibility Template (VPAT) Overview of Technologies and Formats WHAT IS A VPAT AND HOW IS IT USED? Resolution Schneider Electric does not have a VPAT document for Continuum.

Issue Define what Network 8000 devices that can be integrated with EcoStruxure Building Operation. Product Line EcoStruxure Building Operation, TAC I/A Series Environment EcoStruxure Building Operation Automation Server version 1.2 until and including 3.2 Network 8000 Cause Need to know the supported devices for a Network 8000 to EcoStruxure Building Operation upgrade.  Resolution EcoStruxure Building Operation supports the following Network 8000 LCM devices: LCM EcoStruxure Building Operation supports the following Network 8000 ASD devices: Microzone II MicroFlo II LIM PEM  The following Micronet 2000 products are supported: MN-FLO MN-FLO3T MN-HPFC MN-ASDI  The following Network 8000 products are not supported in EcoStruxure Building Operation: CCL GCM LNC SIM GCM PLC Note: EcoStruxure Building Operation version 4.0 (EBO 2022) and higher are not supported

Issue How to remove an unknown Embedded Demo License Product Line EcoStruxure Building Operation Environment Building Operation Automation Server Premium (AS-P) Device Administrator v4.0.5 (EBO 2022) and below Cause The Embedded Demo Licenses are handled from the Device Administrator software. However, if the installed Embedded Demo License in the SpaceLogic servers does not comply with the file in the Device Administrator, the installed Demo License could not be removed. Resolution Instructions shown in the video below are for EBO 2022 (v4.0.5) and below. In the later releases EBO 2023 (v5.x) and above, a feature now allows the Demo licenses to be returned from selected servers.  See WebHelp topic Returning All Demo Licenses from the Selected SpaceLogic Automation Servers  For any License activations/returns to occur, there must be a trusted state (Certificate State) between the server and Device Administrator. Ensure that this is in place before attempting either resolution. For more info, see Certificates Managed using Device Administrator   If this function does not work, you can attempt the manual file name manipulation described below.    To check the name of the installed Embedded Demo License, log in to the SpaceLogic servers from Workstation. Navigate to System, LicenseManager, LicensingMetadata, ClientMetadata, Product 0. In ProductID, you will see the filename of the actual file.   Rename a Demo license file and import it into Device Manager to uncheck the selected Demo License file.   At the end of this session, you will be able to: Remove Unknown Demo License in SpaceLogic servers        

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 "Trace", then click ok. Let it run a few minutes. If there are some user input needed to recreate the Modbus issue, then perform these steps now. Retrieve the log by right-clicking [AS/ES name]/System/Modules/Trace/TraceSettings and choose Trace settings->Get trace log.  Save the log file. A useful tool available on the Community, the Modbus decoder can be used to assist in viewing/debugging the Modbus trace log file information saved in the previous step. Once debugging is complete remember to change log level back to "Information" (reverse of step 3). Note: If the ES or AS is reset, i.e. cold started or warm started, the log level will return to 'Information', so if further increased logging is required, the procedure will need to be repeated. Note2: From v6 (2024), adding the trace below can be helpful for Modbus RTU /[ASName]/System/Modules/Trace/Loggers/nsp/nsp.pin/nsp.pin.sport/nsp.pin.sport.DeviceRS485   Here is a video showing the above process. 

Issue Multiple MP-Vs have SpaceLogic Sensors (formerly SmartX Sensors) connected, all with identical configurations.  Some are missing the Properties, Scene Configurations, Button and Scene Configuration tabs. Product Line EcoStruxure Building Operation Environment Building Operation Workstation Building Operation Automation Server Building Operation Room Controller (RPC)  Building Operation RP-V VAV Building Operation Multi-purpose Controller Building Operation Multi-purpose VAV Cause Delete the sensor and add it back, which takes a long time to execute for all sensors Resolution In WorkStation, in the System Tree pane, expand the BACnet Interface and the IP network. Click the BACnet/IP controller device. In the Actions menu, point to Device, Advanced, and then click Restore optional properties. In the Actions menu, point to Device and click Download all objects 

Issue A large room has multiple SpaceLogic Sensors SXWS (formerly SmartX sensor) and the temperature setpoint is changed in one of them. Is it possible for the temperature setpoint to be changed in the other sensors?  Product Line EcoStruxure Building Operation Environment Building Operation SpaceLogic Sensor Building Operation Room Controller (RPC) Building Operation RP-V VAV Cause In EBO (EcoStruxure Building Operation) version 3.1 a functionality called HMI references is introduced which can be used in this case. This new functionality makes it possible to have bi-directional bindings for the following value types in the RP series controller Blind position: analog value Occupancy override: digital value Fan speed: multistate value HVAC mode: multistate value Light level: analog value Selected scene: analog value Blind slat angle: analog value Temperature setpoint: analog value Resolution This is done by creating a value of the value types supporting the HMI reference functionality in the Application folder of the RP IP controller which the SpaceLogic Sensors are connected to. Then bind that value to the Display properties of each SpaceLogic Sensor       For example an Analog value is created in the Application folder of the RP-C and then bound to the Display Temperature Setpoint property of each connected SpaceLogic sensor. If then changing the Temperature setpoint from the RP-C that will be distributed to all SpaceLogic Sensors. But also if changing the Temperature setpoint in any of the SpaceLogic Sensors that value will be distributed to the other SpaceLogic Sensors and the RP-C.   To see an example on how this can be done please see video:  

Issue A Vista workstation remote need to go thru a firewall when connecting to the Vista server will this work? Product Line TAC Vista Environment Vista Workstation Cause Workstation is using DCOM to communicate with the Vista server, DCOM is using port 135 initially but then a random port is used. Workstation will contact the server on port 135 but then the server will respond on a random port. This makes it very hard to use workstation through firewalls (it is difficult to open a port when that port number is not known). .   Resolution It is possible to via registry settings limit DCOM to use a range of 100 ports. But usually it is hard to get the IT department to open 100 ports. The way that people usually go through firewalls is using a extra Vista server which is communicating via TCP on port 45612 through the firewall and then connect the workstation to this Vista server, if the server is empty it doesn't cost a extra license.

Issue Upgrade path from version 1.0 to a current version Product Line EcoStruxure Building Operation Environment SmartStruxure Building Operation versions 1.0, 1.1, 1.2, 1.3, 1.4, 1.5, 1.6, 1.7, 1.8, 1.9 EcoStruxure Building Operation versions 2.0, 3.0, 3.1, 3.2, 3.3 (limited), 4.0, 5.0, 6.0 Cause Upgrade path from version 1.0 to current - version Important - The upgrade process is sequential, for example, 1.1 to 1.2 to 1.3 to 1.4 From v1.9, non-sequential upgrades are possible  The primary released versions were, Release Note Dates (approximate) 1.0.0.161   1.1.0.362 Dec 2011 1.2.0.767 July 2012 1.3.0.938 Nov 2012 1.3.0.10100 SP1   1.3.0.20011 SP2   1.4.0.4020 Sept 2013 1.4.1.68-73 Oct 2013 1.5.0.532 July 2014 1.6.0.250 (RC) Dec 2014 1.6.1.5000 Feb 2015 1.6.2.27 Maintenance Release Jun 2016 see TPA-SBO-16-0003 1.7.0.255 (RC) July 2015 1.7.1.89 Oct 2015 1.7.2.29 Maintenance Release Jun 2016 see TPA-SBO-16-0003 1.8.0.244 (RC) Mar 2016 1.8.1.79-87 Jun 2016  1.9.1.95 Apr 2017   1.9.2.45 Maintenance Release Oct 2017  - See release note 1.9.3.24 Maintenance Release April 2018  - See release note 1.9.4.29 Maintenance Release April 2019  - See release note 2.0.1.130 & 135 June 2018 (130(License, WS, Reports Server) 135 - Server (AS, ES, EC)) - See release note 2.0.2.67 Maintenance Release Sep 2018  - See release note 2.0.3.45 Maintenance Release Dec 2018  - See release note 2.0.4.83 Maintenance Release June 2019  - See release note 3.0.1.104 May 2019  - See release note 3.0.2.33 Maintenance Release July 2019  - See release note 3.0.3.11 Maintenance Release Aug 2019  - See release note 3.0.4.43 Maintenance Release Dec 2019  - See release note 3.1.1.312 Dec 2019  - See release note 3.1.2.29 Maintenance Release Mar 2020  - See release note 3.2.1.630 Aug 2020  - See release note 3.2.2.61 Maintenance Release Nov 2020  - See release note 3.2.3.59 Maintenance Release Mar 2021  - See release note 3.3.1.59L Limited distribution release Feb 2021 - intended for specific feature compatibility with some hardware or applications - See release note EBO 2022 (4.0.1.86) Dec 2021 - This version follows v3.x, and reflects a new naming convention focused on release year for clarity - See release note EBO 2022 (4.0.2.559 & 562) Maintenance Release Apr 2022 - WorkStation Hotfix and License Admin 4.0.2.562, others 4.0.2.559, see revised release note EBO 2022 (4.0.3.176) Maintenance Release Jul 2022 - See release note EBO 2023 (5.0.1.86) Dec 2022 - See release note EBO 2024 (6.0.1.93) Mar 2024 - See release note Resolution It is most important to read the Release Notes and System Upgrade Reference Guide for each version you are upgrading to, as there are some special notes that only apply to some installation types. Click Here for Release Notes Click Here for Upgrade documentation The Minimum upgrade path would be as below (See Release Notes for any special instruction) 1.0.0.161 1.1.0.362 See StruxureWare Building Operation v1.0 to v1.1 upgrade issues Appendix A 1.1.0.1225 See Appendix A 1.2.0.767 See Appendix A This version can be avoided by using 1.2.0.1412 if possible 1.2.0.2207 (Hotfix) Available from PSS See also Appendix A 1.3.0.938 See also Appendix A 1.3.0.10100 (SP1) (needed if runtime compatibility is required during upgrade) 1.4.0.4020 or 1.4.1.68 (Only needed if runtime compatibility is required during upgrade) See Upgrading Automation Servers from 1.3 to 1.4 1.5.0.532 1.6.1.5000 See Upgrade to 1.5.0 or 1.6.0 fails 1.7.1.89 1.8.1.87 See Product Announcement 00471 Pre-Upgrade LON Add-On 1.7.1 to 1.8.x 1.9.1.95 Possible to upgrade directly from v1.5, but carefully study the release notes and upgrade instructions Option to 1.9.2.45 Upgrade options more limited with this version, only from v1.7.2, see the release note Option to 1.9.3.24 Upgrade options more limited with this version, only from v1.7.2, see the release note Option to 1.9.4.29 Upgrade options more limited with this version, only from v1.7.2, see the release note 2.0.1.130/135 Possible to upgrade directly from v1.5, but carefully study the release notes and upgrade instructions. NOTE the new License structure for v2.0. 3.0.1.104 Possible to upgrade directly from v1.8, see the table in "System Upgrade Reference Guide" (3.0.1 System Upgrade Overview), but carefully study the release notes and upgrade instructions. NOTE the new Licenses for v3.0. 3.1.1.312 Possible to upgrade directly from v1.8 See Release notes and upgrade documents for full details 3.2.1.630 AS Classic not supported, Win 7 and Win server 2008 not supported 3.3.1.59L Limited distribution release - intended for specific feature compatibility with some hardware or applications, see release note for details. If you do not require the specific features outlined in this Release Notes, it is recommend installing EcoStruxure Building Operation 3.2.x instead EBO 2022 (4.0.1.86 and later) The following protocols, objects, and devices are not supported in EcoStruxure Building Operation 4.0 or higher: I/NET, Sigma, MicroNet, NETWORK 8000 ASD and LCM. A multi-version system supports I/NET, MicroNet, NETWORK 8000 ASD and LCM on automation servers and Sigma on an enterprise server, running an earlier version than 4.0. Report Server/WebReports is not supported in EcoStruxure Building Operation 4.0 or higher. See release notes for details. EBO 2023 (5.0.1.128 and later) New SpaceLogic and Easylogic Controller support, External Storage support for MS SQL, Some support for IPv6, BACnet protocol rev.16, Virtualized Automation Server - Edge Server added,   See release notes for details. EBO 2024 (6.0.1.93 and later) Added New Software Assurnace, Sustainability Pack, EBO Enterprise Server and Enterprise Central for Linux, OPC UA Client Support, Modbus2 Support, Visual Programming for Function Block, XLSX Report, and Touch Room Controller Support. See release notes for details. Appendix A - Upgrading from Specific 1.x Builds Upgrade from V1.0.0.XXXX to V1.3 (via V1.1 and V1.2) Upgrade from 1.0.0.XXXX to 1.1.0.1225 Upgrade from 1.1.0.1225 to 1.2.0.1412 (Do not use 1.2.0.767) Upgrade from 1.2.0.1412 to 1.3 Upgrade from V1.1.0.XXXX to V1.3 (via V1.2) Upgrade from 1.1.0.XXXX to 1.2.0.1412 (Do not use 1.2.0.767) Upgrade from 1.2.0.1412 to 1.3 Upgrade from V1.2.0.767 to V1.3 Apply hotfix 1.2.0.2207 Upgrade from 1.2.0.2207 to 1.3 NOTE: These hotfix builds are not available for download from the Extranet site, you will need to contact Product Support and request them

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 An explanation of Hosted backup options is needed to understand which objects are backed up and which are not. Product Line EcoStruxure Access Expert Environment Access Expert Hosted V3 Cause It's important to understand the backup options available for an instance. Resolution By default, each instance includes a one-year transactional history retention, giving one year of Event History backup. Additional event history retention time can be purchased if required, and such purchases will be visible under "Manage License." Example: Note: There are currently no configuration specific backups that are retained or that can be restored to reinstate deleted hardware or objects into an instance.    Recommendations: Exercise caution when deleting objects, especially controllers, from Access Expert. A prompt requests confirmation before deletion. Generate snapshots of controller configurations and other detailed objects. These snapshots serve as references in case of accidental object deletion, assisting the reconstruction of controllers or other objects with their original configurations. Summary reports can also be useful when trying to rebuild objects. For example: Inputs, Outputs, Readers, etc.

Issue After a PC crash the customer needs to merge a old Vista log database with a new one, is this possible? Product Line TAC Vista Environment Vista Server Cause There is no function in TAC Vista for merging Log databases. The logdata is saved in a SQL database and to merge two SQL databases a SQL management tool is needed along with special SQL scripts. Resolution it is very hard and needs to be done by R&D. When it has been done in the past, the customer has paid for this service.

Issue Do all StruxureWare I/O modules use the same base? Product Line EcoStruxure Building Operation Environment Building Operation I/O Module Cause Want to select the correct I/O module base Resolution Yes all Building Operation I/O modules use the same SXWTBIOW110001 terminal base.

Issue When a trend log is opened up from Vista Workstation, there are no values or information in them. The trend logs are empty. Product Line TAC Vista  Environment Vista Server Cause The computer or user permissions do not allow Vista to create new directories. Resolution Check the $queues folder in the Vista database. If the $queues does not have the insertevents and insertlogvalues folders underneath it then create these folders manually. Now check the trend logs in Vista Workstation again, all of the trend logs should show up.

Issue If a constant is set to public (meaning it can be edited by the user from the front end) then it can only be used once in a Menta application. Options > Constants Table will show you which constants are set to public. Any attempt to use them more than once will result in the following error: Tam32 Public constant used more than once: Product Line EcoStruxure Building Operation Environment Building Operation Workstation Cause Typically a public constant is being used because the simplicity of a simple block is desired. A delay block may be used on three different fan commands and the user desires all of them to have the same delay attribute. Resolution To use one value for multiple simple blocks, the functionality of those simple blocks will have to be recreated using other Menta blocks until a single PVR can be sent to multiple HFBs. For example, instead of a delay block, some configuration of trigger and pulse blocks could delay the output and a PVR could be used to set the length of the delay. Note: Non-public constants can be used multiple times in simple block parameters and expressions. For example, "pi" could be defined as 3.1415926535 and used in multiple equations. It's just public constants that cannot.

Issue When trying to run an EBO virtual server in PCT2 the following error message is received: Server failed with reason 'unschedulable, 0/1 nodes are available: 1 Too many pods. preemption: 0/1 nodes are available: 1 No preemption victims found for incoming pod..'. Go to diagnostics page for more information. Server failed with reason 'unschedulable, 0/1 nodes are available: 1 Too many pods. preemption: 0/1 nodes are available: 1 No preemption victims found for incoming pod..'. Go to diagnostics page for more information.   Product Line EcoStruxure Building Operation Environment Building Operation Project Configuration Tool (PCT) Cause The maximum number of running servers in PCT 2 has been exceeded. Resolution PCT 2 supports a maximum of 250 running servers. If this limit is reached with 250 servers already operational, no additional servers can be started.

Issue What can be used to get the Device Log (aka Error Log) from a b3 or Infinet connected to an Automation Server (AS)? Product Line EcoStruxure Building Operation Environment Building Operation Server Bacnet Infinet Cause Need to get the Device Log (aka Error Log) from a b3 and/or Infinet connected to an AS. Resolution A tool called Building Operation Device Log Viewer (SE.SBO.Device.Log.Viewer.exe), starting with v1.9 now contains a dropdown used to choose BACnet (b3) or Infinet.  Prior to v1.9, it was limited to only obtaining b3 error logs.   64-bit Windows OS Default Location: "C:\Program Files (x86)\Schneider Electric [EcoStruxure|Struxureware]\Building Operation [n.n]\WorkStation\Script\SE.SBO.Device.Log.Viewer.exe"   32-bit Windows OS Default Location: "C:\Program Files\Schneider Electric [EcoStruxure|StruxureWare]\Building Operation [n.n]\WorkStation\Script\SE.SBO.Device.Log.Viewer.exe"   Note: Based on the EBO system version you are connecting, use either [EcoStruxure|StruxureWare] and version [n.n] that matches. Note: Before v1.6 it was called Building Operation b3 Device Log Viewer and had a similarly named EXE file.   The Log Viewer tries to connect to the AS-P via UDP port 33487 when BACnet is selected and UDP port 33488 when Infinet is selected.

Issue Identify which Access Expert LDAP Active Directory Keep version is installed Product Line EcoStruxure Access Expert Environment Access Expert Hosted V3 Access Expert LDAP Active Directory Keep Integration Active Directory Cause Windows Control Panel Programs and Features doesn't indicate which version of the LDAP Active Directory Keep Integration is installed Resolution Login to Access Expert and the Instance that has LDAP Active Directory Installed Navigate to the General Configuration Tab> LDAP Agents LDAP Right Click on the LDAP agent and select View Event History Note: You may need to change the Priority from 50 to 0 and the Date Range to see an event Expand (Click the plus sign) of one of the LDAP Events (i.e LDAP Agent - Started) The version of the LDAP Active Directory Keep installation will show