Building Automation Knowledge Base

Issue Subnet/Node address shown in Local Node Properties dialog is not what is used on the LonWorks Network. Product Line EcoStruxure Building Operation. Environment Building Operation Workstation. Building Operation Automation Server Premium. LonWorks . Cause When using External Managed Network, an external binding tool is used to address LonWorks devices, and the external tool sets the address in the Neuron chip, that is used for communication. This information is not tranfered to the database. Resolution When using External Managed Network, the correct address information could be read in the Domain table of the device.

Issue Replacements for Schneider-Electric SmartX MS41 Damper Actuator Product Line Field Devices Environment SmartX MS41 Cause Replacement of SmartX MS41 Damper Actuators within the Schneider-Electric range Resolution Outgoing Actuator Model          Replacement Model (Part Number)       MS41-6083-G00                        MD10A-24 (875 1019 000)       MS41-6153-G00                        MD20A-24 (875 1029 000)       MS41-6153-G10                        MD20A-24 (875 1029 000)       MS41-6153-G12                        MD20A-24 (875 1029 000) + Aux Switch (914 1061 000)

Issue Permissions are set with multiple tags as the following:      When the user logs into Access Expert and looks at the hardware tree, they are able then to see all the hardware on the instance rather than just those with the matching tags. Product Line EcoStruxure Access Expert Environment Access Expert Hosted Software Access Expert Premise Software Cause The tags are meant to be on separate permissions and shouldn't be used on the same individual permission Resolution Tags and permissions should be set up as illustrated:

Issue After upgrading a site that contains MicroNet or IAC controllers from SBO to EBO the time Schedules no longer display time periods entered. Product Line EcoStruxure Building Operation Environment Building Operation Workstation (from v2.0.1) Building Operation WebStation (from v2.0.1) Building Operation Enterprise server (from version 2.0.1) Building Operation Automation Server (AS Classic from v2.0.1 to v3.1 and AS-P from v2.0.1) Cause From EBO 2.0.1 release includes support for MicroNet time and holiday schedules in WebStation, to achieve this the existing SBO schedules have been replaced by a TGML graphic for both WebStation and WorkStation. Resolution To enable the new schedules, run the Data Importer on each MicroNet interface, this will add new TGML schedule objects for all existing MicroNet and IAC Time and Holiday schedules. Before upgrading. After upgrading. Carry out a Data import. After the Data import, then the associated TGML graphics can be seen. Further information is available in the EBO 2.0.1 release note. The graphic creation is confirmed in the trace information presented when Data importing: The trace will be sent to: C:\ProgramData\Schneider Electric EcoStruxure\Building Operation n.n\DataImport\Trace.DataImport.MicroNet Interface.txt and the following is seen: Source: C:\Satchwell\Projects Full URL: C:\Satchwell\Projects Processing XML... Committing to server... Creating object editor graphics (3) ... Object editor graphics created

Issue Unable to access the SE7xxx Room Controller configuration parameters menu - displays an error code. Product Line EcoStruxure Building Expert, Field Devices  Environment SE7xxx Room controller SE7000 Series Ex. Viconics branding VT7000 Series Cause The display shows an error code when used, this is indicating a password is required, an example of the error code may be 977 or 996. Resolution Contact your region's Customer Care Center for a temporary password. The error code which is unique to that controller will be required by the Customer Care Center to calculate the temporary password. Note for PSS; Check Internal article. 

Issue Replacements for Satchwell AY series actuators Product Line Field Devices Environment AY Actuator Cause Obsolescence of AY series actuators from Satchwell Options range Resolution The following pop top actuators can be used to replace the AY actuator series:   AY1201                                              AG13U230 AY1251                                              AG23U230 AY1301                                              AG13A230 AY1351                                              AG23A230   For further Knowledge Base information - Types of TAC Erie Pop Top valves and actuators available from Schneider Electric in the UK.

Issue Getting error message when selecting Character set file for the TAC  Xenta Operator Panel (OP).     Product Line EcoStruxure Building Operation, TAC Vista, Xenta OP Environment TAC Xenta OP EcoStruxure Building Operation Microsoft Windows 10 Cause Microsoft Windows 10 does no longer allows the software to change files in all directories. Resolution Manually open up the directory C:\Program Files (x86)\Schneider Electric EcoStruxure\Building Operation 3.2\WorkStation\CharSet.lib Select the Charset you want to use, depending on the language, and copy the file. Remove the extension, so that the file is named Charset, without any extension. Manually open up the directory C:\ProgramData\Schneider Electric EcoStruxure\Building Operation\WorkStation\Function Block Editor Paste the copied file here.

Issue Upon presenting valid credentials at the door and physically entering thru it, the event reported for the transaction is "Valid Access No Entry" instead of the normal Valid Access event. The door is properly configured with a door switch but the controller does not see the door switch open. Product Line Andover Continuum Environment Continuum CX Gen 1 Continuum Net Controller II Cause For unknown reasons the door's entry and exit IOU are set to the same value, typically the GUI will not allow such invalid configuration. Resolution Edit the door and set the Exit IOU to zero (for a single-sided door) or to the appropriate IOU number associated with the AC1/AC1Plus on the exit side of the door. 

Issue When a disabled card is presented to a reader the Door name of that reader is not included in the User Record Disabled events.  Product Line EcoStruxure Security Expert Environment Security Expert Disabled User Card Cause Once the user has been disabled the User object no longer resides in the controller. Resolution The information in the User Record Disabled event can be used to determine which reader the user has badged at. The Controller column has the controller that registered this event and the Description will tell you the Reader Expander and Port on that Expander. Record Disabled Event In the above example event, we can determine Bill has badged at Reader Port 1 of Reader Expander address 1 on controller QCA02 - ADM.

Issue Importing Infinet devices into AS-P fails with the following error "Invalid Data Error: Invalid_Data (0x10000) in module Coml(11). "Invalid cast from null": CreateObjectRequest".  Product Line EcoStruxure Building Operation Environment Building Operation Automation Server Premium Cause Infinet devices have a space character within their names Resolution Remove the space character and use an underscore in its place.

Issue Auxiliary I/O or inputs and outputs, allow a system to be expanded to include additional devices outside of standard door hardware such as sirens, panics buttons, or warning lights. Product Line Access Expert Environment Access Expert v3 Cause Lack of documentation on Auxiliary I/O Resolution Input Devices Inputs are also added to  Downstream (interfaces). Inputs are typically added automatically when used to support door contacts and REX but can be implemented to connect motion detectors, glass break detectors, and even panic buttons. Inputs in this section would be separate from those associated with the reader-controlled doors. Inputs can have cameras associated with them to associate alarm points.   Though you can assign multiple cameras to a single point the Assign Camera section will only present one camera at a time. The Assign View allows multiple cameras to be brought together in a single view. To add an Input: Open a downstream interface configuration Select the “Add Input” Enter a Display Name. Define the Address for the input. Set the Behaviour. Click “Save” or “Save & Close”. **Note: Take special care when setting the address as the value does not match the number labeled on the physical hardware. The first address is always 0 (not 1). Input Attributes: Display Name: This is the name of the input that is used throughout the system. Address: The address that the hardware is connected to on the downstream. Behavior: The Normally Open or Normally Closed setting of the input. This is also where any custom EOL Tables are applied. Debounce: The amount of time required before registering the signal. Bouncing is the tendency of any two metal contacts in an electronic device to generate multiple signals as the contacts close or open. “Debouncing” is any kind of hardware or software that ensures that only a single signal will be acted upon for a single opening or closing of a contact. Latching Mode: This sets the type of latching used by the input. Normal Mode (No Entry or Exit Delay): This will cause the input to report an alarm immediately upon activation and deactivation. Non-latched Entry: If set, the alarm will not be reported from an input activation until the entry delay expires. If the input is still activated when the entry delay expires the alarm will be reported. If the input is not active when the Entry Delay expires, no alarm will be reported. Latched Entry: If set, the alarm will not be reported from an input activation until the entry delay expires. If the input is still activated when the entry delay expires AND the input has not been masked, the alarm will be reported. Entry Delay: The time before the input alarm will report. Exit Delay: This function is useful to secure a door when an individual is leaving.  When the ‘exit delay’ mode is set, the following shall occur.  The alarm will not be reported from an input activation until the exit delay expires.  If the input is still active upon exit delay expiry, the alarm will be reported.  If the input is not active upon exit delay expiry, the alarm will not be reported. Hold Time: This can be thought of as a Motion Detector Delay. This is the number of seconds that the change of state must be held before the input will be changed to a deactivated state. Attached: Sets the Attached status of the input. Input Addressing The address programmed in Keep will not match the address shown on the physical board. The programming address is 1 less than the space used on the physical board. Input Address on Board Programmed Address in Keep by Feenics 1 0 2 1 3 2 4 3 Outputs Outputs are also added downstream. Outputs are not only used to support strikes but can be implemented to connect sirens, strobes, and other signaling type devices. Outputs in this section would be separate from those associated with the reader-controlled doors. Outputs can also have cameras associated with them to associate alarm points.   To Add an Output: Open a downstream interface configuration Select the “Add Output” Enter a Display Name. Define the Address for the input. Set the Behaviour. Click “Save” or “Save & Close”. Output Attributes: Display Name: This is the name of the output that is used throughout the system. Address: The address that the hardware is connected to on the downstream. Activation Time: This is the amount of time the output will be active when pulsed. Mode: This sets the output to be in a normal operating mode (normally un-energized) or inverted operating mode. Schedule: This sets the time during which an output will activate. Assign Camera/View: The associated cameras or views for the output. These will display in the Live Monitor/Event History for events associated with the output. Output Addressing The address programmed in Keep will not match the address shown on the physical board. The programming address is 1 less than the space used on the physical board. Output Address on Board Programmed Address in Keep by Feenics 1 0 2 1 3 2 4 3 Scheduling Outputs Outputs can be scheduled by clicking the schedule drop-down menu and selecting the desired schedule. The output will then Activate when the schedule activates, and deactivate when the schedule deactivates.

Issue How does the controller-resident schedule work in a Revision 11.x MicroSmart controller? Environment MicroSmart controllers revision 11.x and 10.x Cause Main DMS panel and/or NC panel were removed. Resolution With the loss of schedule control from the DMS or NC, each controller has two built-in schedules numbered 1 and 2. The Start/Stop point requiring a schedule can be assigned either one of these schedules followed by a letter A or letter B. Letter A stands for 'always' and letter B for 'backup'. With no DMS or NC present, enter the schedule as 1/A or 2/A.  Assign 'off' and 'on' times as required. Remove any reference to a DMS or NC schedule number (i.e. set it to a value of 00). 

Issue Unable to drag and drop the Application folder into the include types box while performing a search of application files.   Product Line EcoStruxure Building Operation Environment Building Operation Workstation v3.0.x  Building Operation Workstation v3.1.x  Cause Searchable interface not implemented on the Application folder (nor on other devices like b3). This is a known issue in v3.0.x and v3.1.x Resolution Rather than using the left mouse button to drag the application folder, right-click the application folder to drag and drop into the include types box. This is to be fixed in 3.2.1.x.

Issue After an upgrade to EBO version 3 the  "Alarm State Sort Order" in EBO Webstation is not following the  "Alarm State Sort Order" set in Workstation for certain Alarm Views. Workstation:   Webstation: Product Line EcoStruxure Building Operation Environment Building Operation Webstation version 3.0 and later Cause This issue is only seen on Alarm views upgraded from a version earlier than 1.9 to EBO 3.0 or later The problem is that in EBO version 1.9 Webstation did not follow the sort order for Workstation, back then the sort order in the alarm view in Workstation and Webstation was separated. And the default sort order in Webstation was "Triggered time" when upgrading to version 3 the upgrade does not change the sort order for Webstation. So after the upgrade the sort order in the alarm view is "Triggered time" and it will not follow the sort order from Workstation.    Resolution In EBO Webstation version 3 click on the "Filter" button in the Alarm view. Click on "Sort" and remove "Triggered time", click OK In Workstation open the Alarm view and right-click, Open Alarm view settings and click on "Reset standard layout to standard default"  

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 In some cases the event and trend database can grow really big although not all the space in the files is used Product Line EcoStruxure Building Operation Environment SQLite Building Operation Enterprise Server Cause Frequent inserts, updates, and deletes can cause the database file to become fragmented - where data for a single table or index is scattered around the database file. Running VACUUM ensures that each table and index is largely stored contiguously within the database file. In some cases, VACUUM may also reduce the number of partially filled pages in the database, reducing the size of the database file further. Read further information here: https://www.sqlite.org/lang_vacuum.html Resolution Stop the Enterprise Server Open SQLiteStudio (link to download) Select "Databases" --> "Add database" Select the event.db or trend.db file from the "historical" folder of the SmartStruxure database folder Execute the following command: vacuum;

Issue When a very long path is included in a request to the SmartConnector RESTful EWS gateway, such as when attempting to acknowledge an alarm with a long path, the gateway returns the error "HTTP Error 400: The request URL is invalid."   <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01//EN""http://www.w3.org/TR/html4/strict.dtd"> <HTML><HEAD><TITLE>Bad Request</TITLE> <META HTTP-EQUIV="Content-Type" Content="text/html; charset=us-ascii"></HEAD> <BODY><h2>Bad Request - Invalid URL</h2> <hr><p>HTTP Error 400. The request URL is invalid.</p> </BODY></HTML> Product Line EcoStruxure Building Operation Environment SmartConnector Cause In Windows, the default maximum number of characters in a URL path segment (the area between the slashes in the URL) is 260 characters. When the object path, after double URL encoding, exceeds 260 characters, it triggers error 400. Resolution To resolve this issue, follow these steps: Add a registry key "UrlSegmentMaxLength" to the following path in the SmartConnector PC registry: Path: HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\HTTP\Parameters Name: UrlSegmentMaxLength Type: DWORD Value: 0 - 32,766 (e.g., set the value to 1000) After adding the registry key, restart the HTTP services or restart the PC. Detailed instructions for this process can be found in the "Http.sys registry settings for Windows" guide on the Microsoft Learn website. Http.sys registry settings for Windows - Internet Information Services | Microsoft Learn

Issue How to calculate memory needed for PCT. Product Line EcoStruxure Building Operation Environment Project Configuration Tool. Cause Unclear memory usage in PCT. Resolution The specifications show that the PCT default memory is 8 GB in Hyper-V. Each running PCT server takes 2 GB and 170 MB per running server. A 4-core CPU can run up to approximately 100 servers and an 8-core CPU can run up to approximately 200 servers. Memory Usage calculation example: For 23 servers, i.e. 23*0.170 GB + 2 GB = 6 GB For 36 servers, i.e. 36*0.170 GB+ 2 GB = 8 GB (default) For 47 servers, i.e. 47*0.170 GB+ 2 GB = 10 GB To start 100 servers, 100*0.170 GB+ 2 GB = 19GB   Helpful Link: PCT 2.0 memory configuration in Hyper-V

Issue EBO acts as a BACnet server and a BACnet client send SubscribeCOVProperty to get value updates of specific property of a BACnet object, ex. present value, but EBO respond with "NOT_COV_PROPERTY".   Product Line EcoStruxure Building Operation Environment Building Operation Enterprise Server Building Operation Automation Server Building Operation Automation Server Premium Building Operation Automation Server Bundled Building Operation Edge Server - Standard Cause Specified property does not support COV notifications. Resolution EBO only supports SubscribeCOVProperty (DS-COVP-B) for the following properties and object types: Status_Flags: AI, AO, AV, BI, BO, BV, MI, MO, MV, Loop, Trend Log Event_State, Reliability, Out_Of_Service: AI, AO, AV, BI, BO, BV, MI, MO, MV, Loop When a client attempts to use SubscribeCOVProperty for another property not listed above, the appropriate response is 'Not COV Property', as specified in BACnet standard. When getting this response from EBO, the client is expected to automatically use another method to acquire the property value (either via COV subscription or polling). If the client is attempting to read Present_Value, then using SubscribeCOV would be the preferred mechanism.

Issue The following record is seen in trace logs of EBO servers that have a BACnet Interface:   nsp.pin.BACnet.VariableProperty PollingVariableProperty: variable is a zomby!! Product Line EcoStruxure Building Operation Environment Building Operation Enterprise Server Building Operation Automation Server Building Operation Edge Server Cause A zomby variable is the BACnet plugin coming across an object that will be deleted but has not yet. Resolution No further action is required.

  Issue When attempting to add a downstream device to an SSC the error "exception of type \'Feenics.Keep.DomainModel.KeepException\' was thrown" Product Line EcoStruxure Access Expert Environment  Access Expert V3 Cause The SSC has a limitation of 32 downstream devices no matter what port(s) are being used either RS485 or virtual.  Resolution The SSC specification data sheet indicates the SSC can manage up to 64 downstream devices. However, R&D has corrected our understanding of this limitation which is only 32 downstream devices. Attempting to add a 33rd downstream device will result in the   \'Feenics.Keep.DomainModel.KeepException\' error. An additional SSC or Mercury upstream controller will be necessary to commission greater than 32  downstream devices.   From R&D: "The SSC can support a Total of 32 downstream devices no matter what port they are connected to either RS485 or Virtual. The SSC can also support 64 doors total." SSC data specification sheet  *Note: The specification sheet will be corrected in the future by the Product Owner.