Building Automation Knowledge Base

Issue What is the limit to the number of objects that can be created in a Workstation? Product Line Andover Continuum Environment CyberStation Cause Want to create a large number of AnalogValue's and BinaryValues in the Workstation for programming and display purposes. Resolution There are no limits to the number of variable objects that can be created in the Workstation. There may well be some practical limits based on the SQL limitations but for all intents and  purposes this limit will most likely not be reached on a full SQL install. There maybe issues with DB size on an SQL Express system but even then, the AV / BV objects don't actually take up that much physical space. As an example, tested this on a v1.94 system and have been able to create over 2500 AV's in my Workstation folder without any issues. NOTE - Running a large number of Programs on a CyberStation can cause issue. System control, etc. should be from a Controller rather than CyberStation.  

Issue AVU2201 Replacement Product Line Field Device Environment AVU2201 Cause AVU2201 obsolescence, replacement required. Resolution The replacement actuator is the MZ300S-24F actuator.

Issue When importing Security Expert controllers into Security Expert Server using the Data Sync Service, the Register As Reader Expander address field is different from the value in the CSV file. The address field is incremented by 1. Product Line EcoStruxure Security Expert Environment Security Expert Server Security Expert Data Sync Service Cause Register As Reader Expander values in the Security Expert SQL database are stored as integers where indexing starts at 0, whereas in the Security Expert Client the same values are displayed as integers starting at 1. The Data Sync Service updates the database values directly, which is why the values differ between the CSV file and the user interface. Resolution In the CSV import file, decrement values in the Register As Reader Expander column by 1. For example: If the address in the user interface is '1', the value in the CSV file should be changed to '0'. See screenshot from Data Sync Service (left) and Security Expert Client (right) below.  

Issue A Log Processing Trend Log created in an EBO server and connected to an Extended Trend Log will not transfer any records even if the Force Transfer command is executed. Product Line EcoStruxure Building Operation Environment Building Operation Enterprise Server Building Operation Automation Server Premium Building Operation Automation Server Bundled Cause Log processing trend log records are not saved to database, so they will not be transferred to Extended Trend logs. Resolution In the Basic Properties of the Log Processing Trend Log, set "Persist data" to True to store trend data in the database. This will enable the records to be transferred to the connected Extended trend Log.

Issue Importing Security Expert controllers' serial numbers will break the import process and result in only creating default templates for the controllers. Product Line EcoStruxure Security Expert Environment Security Expert Server Security Expert Data Sync Service Cause Security Expert controllers' serial numbers are displayed in hexadecimal. However, in the SQL database they are  stored as decimal values. So the Data Sync Service is expecting a decimal integer and is instead receiving a string.  Resolution Convert the serial numbers in the .CSV import file from hexadecimal to decimal. This can be done in excel using the  "HEX2DEC" function. E.g. if the controller serial number is "ABCDEF12", it must be converted to decimal value "2882400018" before importing to Security Expert. 

  Issue Have an Alarm Category assigned to an Alarm but does not appear in the Alarm View Product Line EcoStruxure Building Operation Environment Building Operation Enterprise Central Building Operation Enterprise Server Building Operation SmartX Servers Cause In this case, the system has an Alarm Decoration which is filtered on the server name and overriding ALL alarms associated with this server and hence is overriding the Alarm Category defined within the Alarm Handling.   Resolution Option 1: Add the Alarm Category to the Alarm Decoration as shown in the screenshot below: Re-activate the alarm and the Alarm Category should now show in the Alarm View Option 2: If the Alarm Decoration is not required, then delete the Alarm Decoration completely.    

Issue The License Server is not working and may show Vendor Daemon Down errors. The LMadmin log shows the error. LicenseEngine (taclic) exited with status 28 Product Line TAC Vista EcoStruxure Building Operation Environment Vista Building Operation Enterprise Server License server Cause Data Execution Prevention (DEP) is activated. Antivirus or other software can scan/use the port used by the vendor daemon. If the time drifts over two minutes and a time synch occurred, the vendor daemon can stop. https://support.citrix.com/article/CTX137111 Resolution First, check that DEP is not activated. Make sure that there is no antivirus program that has portscan activated Make sure there is no other software that uses the same port as the vendor daemon Make sure that the time does not drift too much, if the time drifts two or more minutes and then a resynch occurs the vendor daemon can stop This is more likely on VMware where time synch can occur from either the domain or VMware tool. Check Windows event log (Security) for time synch messages. NOTE: It can also appear just by stopping the server manually.

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 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 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 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 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 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.