Building Automation Knowledge Base

Issue When trying to browse for Areas to assign to the Area Inside Door and Area Outside Door fields in Door records, not all Areas are shown or available to be selected. Product Line EcoStruxure Security Expert Environment Security Expert Cause The Programming Mode selector is set to "Local" which is the default value. This will only show objects that are already attached to the controller this record resides in.   Programming Mode Resolution Change the Programming Mode to "Global" which will now show all Area records, including those unassigned or assigned to other controllers.   Programming Mode Global

Issue During the initial configuration of the Suprema Biometric integration with Security Expert, the existing user information stored in Suprema Biostar is not imported into Security Expert. Only new Users enrolled through Security Expert are available. Product Line EcoStruxure Security Expert Environment Security Expert Suprema Biometric Integration Cause The user database in the Suprema Biometric devices is not automatically brought over into Security Expert during configuration of the integration. This database of users needs to be created and biometrics enrolled through Security Expert. Resolution A workaround to getting this user information into Security Expert would be to export the user data from Suprema to a CSV file and then import that into Security Expert.   After these Users have been created in Security Expert the fingerprint enrollment will need to be redone to capture this within Security Expert. To Export from Suprema: Click on the USER menu. Select a user or multiple users to export. If you want to export all users in the server, click on the dropdown button and click Select All. Click on … below the user search bar. Click CSV Export. The csv file is stored in your Windows Downloads folder. To Import User Records into Security Expert from a CSV File: Navigate to Sites | Import Users to launch the Import Users wizard. Browse to and select the CSV File you wish to import the users from, then click Next. Select the line to start importing data from and the text delimiter to use, then click Next. If your CSV file contains a header row, ensure you start the import at line 2 so the header row is not imported. Select each column in the panel on the left and map it to the associated fields you wish the data to be imported into on the right. The data in the top pane is updated as you make your selections. Click Next to continue. Assign the facility number, first card number, and access level if you have not already done so. You can also choose to generate PIN numbers automatically. Click Next to continue. Click Finish to start the import process. The user records are imported and the wizard closes.

Issue Need to activate an Output when access is denied to a User at a Door. Product Line Security Expert Environment Security Expert Cause In the Door object, there is a facility for triggering Outputs on Pre Alarm, Door Left Open, and Door Forced Open but nothing for when a User is denied access. Resolution There were new Door commands added to SP-C firmware 2.08.1018 and newer to add this functionality. AccessDeniedTime = # has been added to the Door commands which will specify the duration in seconds that an output or output group will be activated for when access to the door has been denied. This must also be paired with one of the following 2 commands in order for the functionality to occur. AccessDeniedOutput = # has been added to the Door commands which will specify the output that will be activated when access to the door has been denied. The # will be the database ID of the output/output group. AccessDeniedOutputGroup = # has been added to the Door commands which will specify the output group that will be activated when access to the door has been denied. The # will be the database ID of the output group. As an example, if you wanted the Output with an Id = 3 to turn on for 5 seconds when access is denied at the Door, the following lines would need to be added to the Door object in the Commands section. AccessDeniedTime = 5 AccessDeniedOutput = 3 Door Command - Access Denied Output  

Issue When attempting to add a new Automation Server under an Enterprise Server that already has one or more AS servers attached it results in an "Object already exists" error ERROR Object already exists Domain: Data access Info:~/System/Server Communication/Models/xxxxxxxx/Members/xxxxxxxxx in module Run Db manager xxxxxxxx = Global Unique Identifier (GUID) The GUID underlined in red in the screenshot above is the duplicated Id. Additional error message possible depending on EBO release version. ERROR: Server already part of a multi server system Domain: Invalid data  Info: Attempt_To_Add_An_Object_To_The _System_That_Already_Exists ERROR: Cannot add a server that is a clone of a server that already exists in your system Domain: Startup  Technical Info: An added server with name 'XXXXX' has the same unique id as an existing server with the name 'YYYYY' which is not allowed. Product Line EcoStruxure Building Operation Environment Building Operation Enterprise Server Building Operation Automation Server  Building Operation Automation Server Bundled Cause The AS that is being added has been restored from a backup created from one of the servers that are already configured under the ES resulting in a duplicate GUID. Resolution Backup the Server Restore the Server and make sure to select "Restore configuration with new IDs" check box. This will ensure that a new GUID is assigned to the AS. Add the Server from ES Please note that the restore function to re-use configuration data from a backup set is supported for all Building Operation supported protocols, except for BACnet and b3 BACnet.  To read more see Web Help To read more see Web help: http://help.sbo.schneider-electric.com/topics/show.castle?id=10228&locale=en-US&productversion=1.7 To read more see Web help: http://help.sbo.schneider-electric.com/topics/show.castle?id=10228&locale=en-US&productversion=1.7

Issue SE8000 Best Practices Product Line Field Devices, EcoStruxure Building Expert Environment SE8000 Cause Best Practices for commissioning SE8000 room controllers Resolution The following information has been contributed by a field engineer and their experience to assist others in commissioning the SE8000 device. It brings together or provides leads to various articles that can be found on the Download Center. SE8K Programming Tutorial v1.1

Issue Temperature Sensor Resistance Charts Product Line Andover Continuum, EcoStruxure Building Operation, Field Devices, Satchwell MicroNet, Satchwell Sigma, TAC IA Series, TAC INET, TAC Vista Environment Temperature Sensors Cause Temperature (°C) to Resistance Charts (ohms). Upgrading the site BMS, but retaining the existing sensors and the sensor resistance values are not known. Resolution The resistance of a sensor at a specific temperature can be downloaded here. The devices covered are Schneider-Electric's range including Andover, TAC and Satchwell and other manufacturers temperature sensors. All are detailed below. For the standard thermistor, tables click here, where the INET, I/A, and BALCO resistance tables are detailed. This is the chart for the Precon Thermistors - ACCTemp 10K Type III thermistor also known as the 10K4A1 Thermistor. For EcoStruxure I/O Module universal inputs, the type of thermistor bead is classed as a: "10k Type I (Continuum)".   Satchwell T range is now known as STR600, STP660, STD600, STO600 10K3A1 with shunt Drayton DC1000, DC1100 30K6A1 is now known as STR600D, STP600D, STO600D Andover 10K4A1 TAC Inc. Vista 1.8KA1 I/A series 10K3A1 with 11K shunt INET 10K2A1 (10k Dale) BALCO 1000 ohm RTD For further explanation of Building Operation Thermistor type selections refer to the article Thermistor type selection in EBO   TC900 RS-03 sensor chart can be found here.   Older Satchwell ranges: Satchwell DW1204, DW1305, DWS1202 Satchwell DO Satchwell DD/DR Other manufacturers include: Allerton 3K3A1 Ambiflex 2012, Honeywell Aquatrol, Jel/Thorn, Trend, York 10K3A1 Schlumberger (air) 5K3A1 Schlumberger (immersion) 100K6A1 Automatrix, York, Sibe 10K4A1 Honeywell 20K6A Landis & Gyr PT100A, PT1000A For I/A Series Controllers (MNL/MNB) Compatible sensors that have a built-in 11k shunt resistor include the TS-5711-850, TS-57011-850, TS-57031-850, and TSMN-90110-850 Series. Any sensor that matches resistance to temperature curve for a 10K Thermistor Type G (U.S. Sensor), Type 9 (Dale/Vishay) or Type III (ACI Series AH) can be used with the I/A Series MNL and I/A Series MNB series controllers, provided that a 11k ± 0.1% 1/8 watt resistor is wired in parallel with the sensor. The input has a range of -10 to 135 °F (-23.3 to 57.2 °C) with an accuracy of ±1% of span. Temperature / Resistance Reference Values Temperature Deg F (Deg C) Resistance Resistance Incl. 11k Shunt 32 (0) 25490 8,012 68 (20) 12,260 5,798 75 (25) 10,000 5,238 104 (40) 5,592 3,707 140 (60) 2,760 2,206 The full temperature/resistance table for the US Sensor 10K Thermistor R-T Curve Type G sensor can be found here. Please note that the controller may not be able to use the full temperature range shown in the table.  

Issue Confusion over the thermistor type selection for an EBO Temperature Input object Product Line EcoStruxure Building Operation Environment Building Operation I/O Module Building Operation Automation Server Bundled Building Operation Multi-purpose Controller (MPC) Building Operation Room Controller (RPC) Building Operation IP-IO Cause The Thermistor type selection lists sensor "Types" I through V     This is confusing since, for example, the Continuum sensor is listed as 10k Type I but in manufacturers literature and temperature vs resistance tables is often referred to as 10k Type 3 Resolution The reference to Thermistor 10k Type in the selection list is an internal reference and not intended to refer to the types listed in manufacturers literature and temperature vs resistance tables. For reference the selections refer to the following sensor types:   Thermistor 10k Type I (Continuum) – Thermistor 10K4A1 also referred to as 10k Type 3 Thermistor 10k Type II (I/NET) – Thermistor 10K Dale/Vishay Thermistor 10k Type III (Satchwell) – Thermistor 10K3A1 Type T Thermistor 10k Linearized (Satchwell D/T) – Thermistor 10K3A1 Type T with shunt Thermistor 10k Type IV (FD) – Thermistor 10K type ‘G’ (U.S. Sensor) Thermistor 10k Type V (FD w/ 11k shunt ) – Thermistor 10K type ‘G’ (U.S. Sensor) with external 11k ohm shunt resistor installed Thermistor 1.8k (Xenta) – Thermistor type 1.8KA1 Thermistor 1k (Balco) – (not a thermistor) RTD, 1000 ohm Balco Thermistor 20k (Honeywell) – Thermistor 20K6A1 type H Thermistor 2.2k (Johnson Controls) – 2.2K3A1   Refer to the Temperature Sensor Resistance Charts Knowledge Base article for temperature vs resistance charts for these sensor types and others.

Issue What is the purpose of the battery/coin clip on some of the I/NET Hardware Product Line TAC INET Environment TAC INET Hardware  7718, 7716, 7798C  Cause The initial development path plan was to include an additional feature to allow communication with Dallas Semiconductor ID tag/coin, similar to that used with the I/NET Access Control I/DISC.  This development was never implemented Resolution This battery/coin tag serves no active purpose or functionality

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 Certificate for FDA regulations in the manufacturing of pharmaceuticals, 21 CFR Part 11 "Electronic Records / Electronic Signatures." Can Building Operation incorporate a comment section to capture a reason for change made by an operator/user? Product Line EcoStruxure Building Operation Environment EcoStruxure Building Operation Cause Building Operation site in need of the compliance certificate for 21 CFR Part 11 "Electronic Records / Electronic Signatures." Usually, these are pharmaceutical manufacturing sites, and the full FDA document PRT11Elect.pdf is attached to this article. Resolution EcoStruxure Building Operation 3.2 and higher Compliance Pack enables 21 CFR Part 11 compliance for regulated industries. The Compliance Pack is an add-on module to EcoStruxure Building to help regulated industries meet the compliance requirements for Electronic Signatures & Electronic Records that are in place in the region.   This feature in our EcoStruxure Building Operation software provides facility-wide accountability and traceability of the environmental conditions that can impact the quality and safety of products developed in controlled environments in line with the 21CFR Part 11 regulation.   Compliance Pack is a licensed feature and compatible with EcoStruxure Building Operation V3.2.1 and later. Part Number Description SXWSWCMPLPK001 Compliance Pack – includes ES level TimescaleDB, Digital PDF Signing, Change Control, for Enterprise Server and all child level SmartX servers For technical documentation and sales enablement tools for the Compliance Pack, please visit The Exchange Building & Power Extranet and use the search keyword: 21cfr ebo   EcoStruxure Building Operation 3.1 and below EcoStruxure Building Operation V3.1 and below has not addressed the pharmaceutical market and there is no electronic signature feature set that meets the FDA regulations 21 CFR part 11.   For sales issues surrounding FDA regulations, please contact through your sales channel to the local Category Manager. Americas: Americas.EcoStruxureBuilding@schneider-electric.com EMEA: EMEA.EcoStruxureBuilding@schneider-electric.com Asia Pacific: AsiaPac.EcoStruxureBuilding@schneider-electric.com

Issue Nuisance forced door alarms are showing when exiting through doors with panic bars. Product Line EcoStruxure Security Expert Environment Security Expert Client Cause Need to stop a forced door event from registering an alarm notification when a doors panic bar is used. Resolution Enable the feature "Forced Door Sends Door Open" on the Door Inputs tab.

Issue Browsing between different records in the Security Expert Client is slow. It takes a longer than normal amount of time to see records update. Product Line EcoStruxure Security Expert Environment Security Expert Client Cause There are a large number of unacknowledged alarms being stored in the SecurityExpertEvents database. When the Security Expert Client starts up it will process all of these unacknowledged alarms which can impact browsing the database. Resolution To resolve the immediate problem: 1. Reduce the size of the SecurityExpertEvents database by reducing the overall number of events that will be stored. Setting up automatic event purging and backup helps keep this in check. Under Global | Global Settings | General change the Purge Events older than from the default setting of "Never" to another value from the drop down menu. To backup these events before being purged, ensure the Generate Differential Events Backup option is checked. This is the default setting. 2. If there are more alarms to be acknowledged than can be done manually then contact Product Support mentioning this Knowledge Base Article. Remote access to the site and SQL Server will be required.   To minimize this from happening again: 1. Reduce the amount of events that are setup as alarms. Remove any alarms that are setup for All Events and review any configured alarms to ensure those events are required to be generating alarms. Double check all Inputs and Trouble Inputs to see if they have the Log to Event Buffer option enabled. Not all inputs will require this for normal operation and in some cases having this enabled can result in a large number of unwanted events being logged. This, in addition to an alarm setup to monitor the All Events event filter, is a recipe for disaster resulting in a large number of alarms being generated in a short amount of time. 2. Ensure that a large number of unacknowledged alarms are not allowed to build up over time. Alarms are not able to automatically acknowledged and will stay in the active alarms list until an operator acknowledges them. Operators need to acknowledge alarms on a regular basis. Note that it is possible to batch acknowledge blocks of alarms at one time in the Security Expert Client by doing a multiple selection then right-click acknowledge alarm.

Issue There isn't enough documentation on how to disable the different connection protocols. I.e. TLS or SSH. Product Line EcoStruxure Building Operation Environment Building Operation Enterprise Central Building Operation Enterprise Server Building Operation Workstation Building Operation Automation Server Cause The WebHelp documentation is incomplete Resolution The only valid protocols are as shown when you hover the mouse over disabled protocols. See below. SSLv1,v2,v3 are all implicitly disabled  

Issue Number of individuals that a controller can have based on the firmware revision. Adding individuals to a system that has more than 24,000 users and is not working. Product Line TAC INET Environment I/NET Seven DPU 7910 DPU 7920 with or without 48K MIP Card SCU1284 Cause Although TAC I/NET supports up to 32,000 individuals per tenant, the model type and revision date of a tenant’s door controllers will ultimately determine how many individuals will be supported Resolution I/NET Supports up to 32,000 individuals per tenant based on the model type and revision date of the tenant's door controllers determines how many individuals it will support. The following table shows the capacity of the various door controllers. Firmware Revision Door Controller Maximum Number of Individuals Maximum number per Tenant 2.1X and earlier DPU 7910, DPU 7920 Up to 24,000 per door 24,000 2.2X to 3.23 DPU 7910, DPU 7920 w/o 48K MIP Up to 48,000 per controller. 24,000 DPU 7920 with 48K MIP, SCU 1284 Up to 48,000 per door 1 3.24 and later DPU 7920 with 48K MIP, SCU 1284 Up to 64,000 per door 1 32,000 1 Typically, the total number of individuals for a selected door cannot exceed 32,000. However, if one of the two doors controlled by a DPU is not being used (that is, no individuals are assigned to the door), you can assign up to 64,000 individuals to the door that is being used. This also requires the use of more than one tenant since no single tenant can have more than 32,000 individuals.

Issue A Dashboard is created with a couple of widgets in it, the widgets are placed where they should be and the Dashboard looks good. But if the Dashboard is opened in a monitor with a smaller screen, the available work area for the dashboard is smaller and the widgets move around. Product Line EcoStruxure Building Operation Environment Building Operation Webstation Cause There is no option to lock the widget positions on both horizontal and vertical axis as the screen area available to the dashboard changes when creating the Dashboard. Resolution Set the Maximum column count in the Dashboard Layout setting to the total number of columns of the desired widget layout. For example if widget one has Column span 2 and widget two has Column span 3 then the Maximum column count should be set to 5 for the Dashboard. Then set the Minimum column size to 0. Now the text still scales but the widgets lock in position.

Issue Need a link to provide an easy way of uploading one or more files to Global Expert Technical Support - Digital Buildings - Asia Pacific Region on Box. Product Line Andover Continuum, EcoStruxure Building Expert, EcoStruxure Building Operation, Field Devices, Satchwell BAS & Sigma, Satchwell MicroNet, TAC IA Series, TAC INET, TAC Vista Environment Schneider Electric "Asia Pacific" Box server folder Cause Many email services have a limit on the size of attachments. In many cases, large files must be sent to Support so that the support engineer can investigate a reported issue. Resolution Using the following Box link will allow the upload of case files associated with your support ticket. Please note that you must have an open support ticket with Support before uploading a file. Files uploaded without a reference to a support ticket without previous approval will be deleted.  

Issue SE7300 and SE8000 room controller fan speeds do not turn off when fan mode is set to auto. When cooling and / or heating is no longer needed, the fan speed remains at low speed. Product Line EcoStruxure Building Expert, Field Devices Environment SE7000 series room controller SE8000 series room controller Cause It is required that the fan be turned off when no demand for cooling or heating is needed. Resolution SE7300 controllers Enter the configuration mode of the room controller. Refer to page 19 of the SE7300 Series Installation Guide for the procedure to enter the configuration mode. In configuration mode, there is a parameter 'AutoFan'. The default mode for this parameter is 'AS'. In order for the fan to stop when there is no demand, the mode should be set to 'AS AD'. AS (Default) = Auto Speed during occupied periods. Fan is always on during occupied periods. Low, medium and high speeds operate on temperature offset from set point. AS AD = Auto Speed / Auto Demand during occupied periods. - Medium and high speeds operate on temperature offset from set point. Low speed operates on demand and will shut down when no demand is present. SE8000 controllers On the room controller, select the fan mode parameter from the home screen. The fan mode must be set to Smart in order for the fan output to function as expected. In Smart mode the fan will turn off when there is no demand for cooling or heating. For SmartStruxure applications of the SE8000 controller This issue can also be seen when binding to the "Value field of the Occupancy Command of the SE8000 controller. Make sure to bind to a priority, not to Value otherwise the fan command will not turn off.

Issue Some AIC objects are pre-configured for the most common thermistors used in the industry. However in Building Expert, i cannot see the description of the AIC object until it has been added. Product Line EcoStruxure Building Expert Environment Multi Purpose Manager AIC Cause Feature not available on the MPM Resolution The description of each of the AIC object is available below. AIC1 to AIC10 = Empty (Manually configurable objects) AIC11 = 10kOhm Type II Thermistor Celsius AIC12 = 10kOhm Type II Thermistor Fahrenheit AIC13 = 10kOhm Type III Thermistor Celsius AIC14 = 10kOhm Type III Thermistor Fahrenheit AIC15 = 1 KOhms Pt1000 Platinum RTD Sensor Celsius AIC16 = 1 KOhms Pt1000 Platinum RTD Sensor Fahrenheit AIC17 = 100 Ohms Pt100 Platinum RTD Sensor Celsius AIC18 = 100 Ohms Pt100 Platinum RTD Sensor Fahrenheit AIC19 = 1 KOhms Ni1000 Nickel RTD Sensor Celsius AIC20 = 1 KOhms Ni1000 Nickel RTD Sensor Fahrenheit

Issue Lookup table for the AIC Analogue Input Configuration for different sensors. What types of sensors can be used with the MPM controller? Product Line EcoStruxure Building Expert Environment Multi Purpose Manager AIC Cause A lookup table is required for a sensor that is not listed in the AICs. What sensors can be used? Resolution For the Satchwell range (new generation or T range) STP660, STC600, STR600 series. Note the engineering output is Celsius.   For the TAC range STP100 series, STC100, STR100 series, STD100 series. Note the engineering units is Celsius.   For the Andover range STP500 series, STC500, STR500 series, STD500 series. Note the engineering units is Celsius.   AIC 1 to AIC 10 are empty Analogue Input Configurations, the remainder are pre-configured as below. For 10K Type II in Celsius use AIC 11 For 10K Type II in Fahrenheit use AIC 12 For 10K Type III in Celsius use AIC 13 For 10K Type III in Fahrenheit use AIC 14 For 1K PT1000 RTD Platinum in Celsius use AIC 15 For 1K PT1000 RTD Platinum in Fahrenheit use AIC 16 For 1K PT100 RTD Platinum in Celsius use AIC 17 For 1K PT100 RTD Platinum in Fahrenheit use AIC 18 For 1K NI1000 RTD Nickel in Celsius use AIC 19 For 1K NI1000 RTD Nickel in Fahrenheit use AIC 20

Warning Hazard of Electric Shock: Remove all power from all devices before removing any covers or doors of the system. Disconnect power at the device and at the power source. Electrostatic Discharge Required: Always discharge static electricity from your person by touching metal prior to handling any hardware. Failure to do so may result in damage to devices. Issue A Security Expert reader that supports Wiegand and RS-485 is wired for Wiegand. It is not working. It only works on RS-485. Product Line Security Expert Environment Security Expert Smart Card Readers which support both 125Khz and 13.56Mhz (SX-DRD-xx, SX-DRK-xx, SX-RK-xx) Cause Tried to use a Smart Card Reader wired for Wiegand after it had been connected by RS-485 to the controller. Resolution Once a Security Expert Smart Card Reader is used in an RS-485 configuration it will not work in Wiegand configuration until it has been re-programmed with a configuration card designed for that purpose. The configuration card  (SX-ISO-CONFIG) must be purchased through Schneider Electric. See the Security Expert Credentials Order Form for details.   This is because RS-485 is a two-way communication, intelligent wiring protocol. Once the reader is set in this two-way communication mode there is currently no way, without the configuration card, to go back to a less intelligent one-way mode like Wiegand.   Note: Readers manufactured in 2017 or before may have a firmware version that uses a configuration mode that will not respond to a configuration card. If you contact Schneider Electric for a configuration card, supply the serial number (SN) from the back of the reader on your request.