Building Automation Knowledge Base

Issue MQTT client from an AS-P cannot establish communication with the Mosquitto broker installed on the machine that hosts the Enterprise Server (ES). At the same time, the MQTT client from the ES was online with the Mosquitto broker. Product Line EcoStruxure Building Operation Environment Building Operation Enterprise Server Building Operation Automation Server IoT messaging MQTT (Messaging Queuing Telemetry Transport) Cause In version 1.6.x and earlier from the Mosquitto broker, the option - allow_anonymous [ true | false ] from the configuration setup (e.g. mosquitto.conf — the configuration file for mosquitto) of the broker was defaulted to  true  unless there were other security options set.   In recent versions of the broker, the option allow_anonymous defaults to  false - Unless no listeners are defined in the configuration file, in which case it set to  true  - but connections are only allowed from the local machine if external connections are required; specific port listeners need to be set. Resolution To configure the MQTT Mosquitto broker for insecure communication with an EBO server, follow these steps.  Download the Mosquitto broker latest version from the Eclipse website and install it on the host machine. Locate the mosquitto.conf file in the  Mosquitto installation folder (Default: C:\Program Files\mosquitto). Edit the mosquitto.conf file with a text editor application (e.g. Notepad, Notepad++). Setting up the  allow_anonymous configuration as true and the listeners to the desired communication ports (e.g. 1883: This is the default MQTT port. 1883 is defined at IANA as MQTT over TCP. 8883: This is the default MQTT port for MQTT over TLS.)   Check the Video attached, which includes the basic configuration of the mosquitto.conf file.   

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 Page 1031 of the hardware reference guide only states wire cross-sectional area: 0.34 to 2.5 mm 2 (22 to 14 AWG) and not the number of wires allowed to terminate. Product Line EcoStruxure Building Operation Environment Building Operation Room Controller (RPC) 24V Building Operation Room Controller (RPC) 230V Cause Documentation clarification. Resolution It is OK to terminate up to 2 wires into each terminal as long as the total area of the wires does not exceed 2.5mm 2 .  

Issue Model and Device Name from SLP sensor via Modbus RTU Product Line EcoStruxure Building Operation Environment Automation Server AS, ASP, ASB SpaceLogic Sensor SLP Cause The Model, Device Name and Serial number are 64bit values and need to be collected with a single query to get the correct data. Script and Function Block programs can not manipulate 64 bit values - Model Register 9, 64bit, read only, Read Function Code 4 - Serial number Register 42, 64bit, read only, Read Function Code 4 - Device Name Register 7, 64bit, read/write, Read Function Code 3 (currently the documentation shows these as 32bit) Resolution A simple way to collect the Model and Serial Number is shown below This involves creating a Modbus Poll Group for the 4x 16bit parts of the 64bit Modbus Register. This will effectively query the 4 registers in a single packet, ensuring the correct data is collected. The same method can be used to collect the Device Name, but this value cannot be written using the same Group, as block/group write is not supported in EBO Create a Modbus Poll group containing the four 16bit registers, then create a String variable Then create a script to convert to ASCII characters

Issue Upgrading SQL Express to a paid Edition of SQL for EcoStruxure Reports Server Product Line EcoStruxure Building Operation Environment WebReports Reports Server SQL Express Cause SQL Express 2008 R2 (for example) is limited to 10 Gb of Storage and 1 Gb of Ram usage. Many sites need a larger, more robust database than this allows. Resolution NOTICE: Before beginning, it is important to understand the difference between the Instance name and the version of SQL running.  The default instance name used in the the SQL Express version of SQL is SQLEXPRESS. This can be changed to anything during installation, but cannot be changed later.  This means that when upgrading to SQL Enterprise edition, the SQL instance name will still need to be SQLEXPRESS. The instruction below assumes the instance name is SQLEXPRESS and will be typed in that manner.   Perform a full backup of the Enterprise Server and Reports Server before beginning any upgrade process. Save these files to an external drive. Purchase a supported edition of SQL for the revision of EcoStruxure Building Operation WebReports being used. Please check the data sheet for the release to obtain this information. Open the Command Prompt and Browse to the location of the installation files for SQL. This should be the folder containing the setup.exe file for the new version of SQL Enter the Command "setup /ACTION=editionupgrade /INSTANCENAME=SQLEXPRESS /PID=XXXXX-XXXXX-XXXXX-XXXXX" NOTE:If  not using the default instance name, enter the correct instance name in place of SQLEXPRESS. PID is the product ID that came with the installation media. In some cases, this will be left out of the command string and entered later. (setup /ACTION=editionupgrade /INSTANCENAME=SQLEXPRESS) The SQL Installer will open. After the Setup Support Rules operation runs, click OK Click Next Verify the Product Key and click Next. Accept the License Agreement and click Next Ensure that the correct instance of SQL is selected and click Next. After the Edition Upgrade Rules runs, click Next Review the Upgrade Summary and click Upgrade When Complete click Close Open the SQL Server Configuration Manager using the start menu and verify that the SQL Server (SQLEXPRESS) service is running and that the SQL Server Reporting Services service is running. If either are stopped, right click and select the start option. Verify the upgrade is successful by opening a Web Browser and entering the URL "http://localhost/Reports_SQLEXPRESS" It should now be possible to see the option to directly edit reports in Report Builder. Log into the WebReports Interface. Notice that the initial report showing Database usage no longer runs.

Issue Using CARD + BIOMETRIC credentials at an integrated Suprema reader for user access. Product Line EcoStruxure Security Expert Environment Security Expert Suprema Biometric Reader Cause Security Expert does not support CARD + BIOMETRIC credentials being read at the integrated Suprema reader. Only BIOMETRIC credentials are supported to be read at the Suprema reader. Resolution For situations where CARD and BIOMETRIC credentials are required to authenticate users a supported solution is to install a Security Expert reader in conjunction with a Suprema reader at the door. The Security Expert reader will read the Security Expert Mifare/DESFire tags, compare this to the credentials configured in Security Expert user and then wait for the proper biometric to be provided before allowing access through the door.

Issue The Continuum BACNet MSTP devices (b3 controllers) are created and do not appear in the BACNet View of the Continuum Explorer when the "Find New BACNet Devices" is performed.  In rare cases, they are all showing online in Infinity View and stay stable but some of them are not showing in BACNet View at all.  Product Line Andover Continuum Environment Continuum Explorer BACNet MSTP devices (b3 controllers) Cause Most of this issue happens when these BACNet objects are left over in the Continuum database due to an incomplete/unsuccessful delete operation on the BACnet devices that previously existed in the database.  Resolution When this happens, deleting all the objects from BACNet view from Continuum Explorer and redo the "Find New BACNet Devices" will fix it most of the time.  If the issue persists, it is necessary to run the "ACCTrace.exe" utility located in the Continuum directory of the workstation to start a capture.  Wireshark will also need to be run at the same time whilst completing a  "Find New BACNet Devices" again.  Wait for about 5 minutes then stop the ACCTrace and Wireshark captures and save the log files.  Send the log files to Product Support with a Continuum Analyzer log file and the names of the issued MSTP devices which are not showing in the BACNet View. SQL Enterprise Manager will need to be available to fix the issue in the database.

Issue Understanding and configuring controllers for Access Control using SystemStatus and AccessServer system variables. Product Line Andover Continuum Environment Access Control CX9702 ACX57xx Netcontroller Netcontroller II Cause Operators can be unsure what the various values for SystemStatus and AccessServer are and what they need to be set to for successful access control. Resolution 1. SystemStatus The first thing to realize is that there are four different modes that an Access controller can be set to, the SystemStatus indicates the mode controller is currently in. This is an Access-only system variable and will default to NoDatabase if left unconfigured. These four values are as follows: Normal — The controller is working normally. NoComm — Local controller has lost communications to the Workstations configured as Primary and Secondary Access Servers. NoDatabase — The Access server and the local controller have been reset or have otherwise lost connection to the database to check access card numbers and personal identification numbers (PINs). Can also indicate that the local controller has lost comms to the Access Server and has no local personnel database to authenticate to. ColdStart — Indicates the Access Controller SystemStatus initial value, before any door has been configured. The sequence for how SystemStatus gets set is as follows: On a ColdStart if the AccessServer = 1-190 it is set to NoDatabase when the first door is configured. When CyberStation finishes the personnel distribution, it explicitly sets the value to Normal.  On a ColdStart if the AccessServer  > 190 it is set to Normal when the first door is configured and the controller is communicating with the Primary and/or Secondary Access Server workstations. Note: Upon initial configuration, or a restart, the CyberStation can fail to set the SystemStatus to Normal; leaving the controller in NoDatabase mode. If this occurs, the value can be manually set to Normal to "kick start" the controller. 2. AccessServer The second thing to look at is that the value of the AccessServer SystemVariable has been set. This should be set to the ACC Net Id of the Workstation configured as the Primary Access Server (> 190) for local then remote validation or set to the controllers ACC Net Id for local validation only. 3. Door Object Additionally Door objects need to be configured to handle the above conditions, there are a number of ways they can require authentication when a card is presented, these are listed in the Entry Reader and Exit Reader tabs of the Door object in the form of check boxes. The main ones being validate site, validate card, valid pin, and Door Forced Lock Schedule. Tick whatever options are required.

Issue What is the correct procedure for replacing a Continuum bCX 4040 controller Product Line Andover Continuum Environment CyberStation bCX 4040 Cause Considering both Continuum and BACnet 'sides' replacing a bCX4040 can seem a complicated process. Resolution Commission new/replacement bCX through its default webpage just as the as old bCX except for the BACnet Configurable Properties section. Set the BACnet Device ID = The same ID in the old bCX (serial number of controller by default) Set the BACnet Port Number UDP = same as old bCX (BAC0 by default) Set the BACnet Network ID UDP = same as old bCX (1 by default) Set the BACnet Network ID Comm2 = same as old bCX (2765 by default) Set the BACnet MAC ID Comm2 = Same as old bCX (0 by default) Set the BACnet MS/TP Enhanced Mode = Same as old bCX (TRUE by default) Set BACnet BBMD Enabled/Disabled = Same as old bCX (False by default) Bring the bCX online in Continuum Explorer, Select menu item Options | Send to Controller options Select "Reload attached objects, but not attached controllers" - select ok Verify the bCX Comm2 settings and baud rate speeds. In Continuum Explorer, right click on the bCX and perform a "send to controller" Verify points and communications.

Issue Getting error "Communications failure due to routing device not available" when reloading BACnet Controller Product Line Andover Continuum Environment CyberStation 1.74 above b3 controllers BACnet bCX1 Cause Anti-virus applications can prevent the BACnet objects from saving into the Continuum Database (BACnet objects may also not appear on the BACnet side).   When you reload the BACnet controller which contains these objects, they are 'inaccessible' and the error is generated in the distribution property window Resolution Close Continuum CyberStation Disable all the Anti-Virus applications then restart Continuum CyberStation From the BACnet Device side, Right click the Controller you want to reload then select SendToDatabase, all the BACnet objects will appear under the controller. Reload the controller again.

Issue Device Administrator is not able to load new database version into AS-P. Error message “New database failed” Product Line EcoStruxure Building Operation Environment Building Operation Workstation Building Operation Automation Server Cause The new McAfee firewall policy where Local the firewall is blocking ICMP6 to the PC. The device needs to be able to "call back" to the PC. If that doesn't happen, the upgrade will not continue and stop at exactly 70%. This is seen in 3.x, EBO 2.0 does not exhibit this issue The device may be defective due to software or hardware error. Resolution   The McAfee firewall issue can be resolved by:  Temporarily disabling the local firewall Trying another PC since McAfee policy or some restriction might have caused installing 3.2 to fail. Another possible solution for this issue which we have seen working is to first install version 3.1 using DFU mode and create a new database and then upgrade to version 3.2 using IP connection.   How to cross-testing and identify if the device is defective? Use the same PC and Device Administrator to install a new DB on a different AS-Ps.  If the same PC can install a new DB on a different AS-P then the issue is not on the PC. Use another PC with the same version of Device Administrator to install a new DB on the suspecting device. If it fails to install a new DB then RMA is needed. Remember to DFU the device before installing a new DB.

  Issue Instructions needed to configure the Card Format for 75-bit Wiegand PIV  Product Line EcoStruxure Access Expert Environment Access Expert Hosted V3 Cause Steps needed to configure 75-bit Wiegand PIV Class card format Resolution A site may have converted from Continuum or is a greenfield site needing to configure 75-bit PIV Smart cards. Below are the card format instructions: Access Expert Card Format snapshot Additional configuration tips: Keep Live monitoring open while configuring this format. Present a User's (Cardholder's) card and you'll see an "access denied entry". While setting this format, a "-1 as a facility code" will show when expanding access denied events while presenting a card in Live Monitoring. This is expected. In Live monitoring the encoded card number is shown. Type the card number into Notepad Copy the card number into the User's Card Assignments> Encoded Card Number field and Save.  Repeat for each cardholder and Test

Issue ACX5720 or ACX5740 backup to flash renders error message: "Unable to backup objects to flash for controllername_\XKD06.51_MCD.  Backup to flash failed.,WS3,conrollername_\XKD06.51_MCD" Product Line Andover Continuum Environment Flash Backup AXC5720 ACX5740 Cause Failure to backup to Flash Resolution Before claiming a faulty controller, it could be a corrupted point or program. Disable all the programs, and try backing up the controller. Disconnect everything except communication and power, and try to backup to flash again. If you have tried to re-flash and it still is giving this error, the controller might be the issue.   Email support with the results if this controller still will not backup to flash: product.support@buildings.schneider-electric.com For configuration and operation program write operations to flash, a counter is incremented for each save and you need to create the numeric INFFlashDisabled to monitor the number of write operations. When the 2000 limit is reached, INFFlashDisabled is set to a non-zero value and logs an error. Using CyberStation, reset this value to 0 and reboot the controller to enable write operations.

Issue What is the recommended process for Database and Workstation Initialization Product Line Andover Continuum Environment Database Initialization Workstation Initialization Cause Sometimes it is necessary to do Workstation and/or Database Initialization eg. following a Continuum service pack install Resolution Database initialization LAN systems (SQL is on a separate SQL server PC) Close all connections to the database (all cyberstations, webclient servers etc.) Open "Database Initialization" from Start/All Programs/Continuum Select "Server" Select "Update Existing Database", ensure Database Information is correct, fill in User Login Password Usually Enhanced Alarm Logging and Enhanced Alarm Delivery are ticked. Then select Continue Database initialization Stand Alone (Single User) systems (SQL is on a CyberStation PC) Close all connections to the database (all cyberstations, webclient servers etc.) Open "Database Initialization" from Start/All Programs/Continuum Select "Stand Alone" Select "Update Existing Database", ensure Database Information is correct, fill in User Login Password Usually Enhanced Alarm Logging and Enhanced Alarm Delivery are ticked. Then select Continue WorkStation Initialization Close the CyberStation on the PC being initialized (other CyberStation can be running) Open "Database Initialization" from Start/All Programs/Continuum Select "Workstation" Check both tabs and fill in the User Password Then select Continue See the Continuum Installation manual for further information   NOTE 1 With the some domains the following has been found - XP - "Right click" on the "Database Initialization shortcut" and “Run As” use local admin - Windows 7 - "Shift" & "Right click" on the "Database Initialization shortcut" and “Run as a different user”, use local admin To log on use the workstation name followed by user eg. WSUK1AB123ABC\dave   NOTE 2 Long CyberStation names can result in the error "Workstation name with invalid characters. Please enter it again" In this case use a shorter name, below 16 characters is best. This can occur even with an existing longer CyberStation name.

Issue How to configure the Security Expert system to use multiple Custom Credentials on the same door Product Line EcoStruxure Security Expert Environment Custom Credentials Cause The older inbuilt Card Formats used Primary and Secondary Reader Formats to allow two Card Formats to be used on the same Door.  But how is this functionality achieved with Custom Credentials? Resolution It is possible to add two or more Custom Credentials to a single Door.  However, when you do this it is instructing the system to request the First Credential AND the Second Credential before granting access to that Door (perhaps even in sequence) If in fact the system is required to request EITHER the First Credential OR the Second Credential before granting access, then the Fallback Credential feature is used. This allows for as many Custom Credentials on a single door as needed.   Please see demo video below:

Issue How can a USB Camera be integrated into Security Expert Product Line EcoStruxure Security Expert Environment EcoStruxure Security Expert 4.3x or greater USB Camera (Example: Logitech C922 ProStream) Cause Twain Driver cameras are not supported in Windows10 or Security Expert for badging photos Resolution The following video will illustrate how to integrate a USB camera to take badging photos

Issue Error messages in Workstation saying "No valid license to add AS found", when trying to add one more AS-P to the ES. Product Line EcoStruxure Building Operation Environment Building Operation Enterprise Server Building Operation Workstation Building Operation Automation Server Premium (AS-P) Demo License file Cause The error message is caused by an expired demo license. When using the Demo License file, the ES checks the Licence at startup, and when doing some operations, like adding AS-Ps. If the Demo license expires, the ES may still work, but you cannot add any more AS-Ps. License Administrator is unable to locate the License Server by using @localhost or IP address(@xxx.xxx.xxx.xxx). Resolution Download a new demo license file from EcoXpert Extranet – The Exchange, and upload it to License Administrator. After the new Demo license file has been added to the License server, you may also need to restart the ES to make sure the new license file will be in use. For more information about the Demo license, please refer to the article EcoStruxure Building Operation Evaluation License for 2.0 and up. When using EBO 2022 v4.0.x and later, the error message (No Valid License to add AS found) can also be displayed if the attached AS-x embedded demo license has expired. Add a current embedded demo license to the device administrator and then re-activate the license to all AS-x servers that require it. Please refer to the article How to activate a demo license on an Automation Server at EBO 2022  Go to Control Panel> System and copy the Device Name Update @localhost in License Administrator > License Server Address to the @"Device Name" Reboot the System(PC) Example The Device Name is "computer1".     Update the License server address to "@computer1" since the Device Name is "computer1"  

  Issue In a system that is working normally for about 3 years EBO 3.1.1.312, appeared an alarm message saying there is a “Duplicate of Local Network” in “BACnet Gateway to network 1”.     Product Line EcoStruxure Building Operation Environment • Building Operation Workstation • Building Operation Automation Server Cause Sometimes there is a device (you can check under device discovery) possibly a router or a gateway where the primary network has NOT been configured as 1, and the secondary network was set as 1 which should be assigned a unique network ID. Also sometimes gateways only require configuring one network which also in this case should be assigned the unique ID, not 1. Resolution The main site network was set as Network 2 Another network, that was routed from the site network was set as Network 1 The main site network was changed to 1 and the other network needs to have a unique network number, so was changed to 2. They also have Cisco and Philips controllers which have their standalone networks and had already been configured with used network numbers so were changed to 3 and 4 accordingly. *Please Note: All controllers must be warm started after the Network number changes so the BACnet network can be remapped in the controller

Issue When DHCP network configuration is Enabled, the gateway changes when connected to an ADv3 through a Y-Cable. If other applications or devices need to route to the AS-P through the Gateway, the change of gateway will break the connection.       Product Line EcoStruxure Building Operation Environment Advanced Display v3 Cause AS-P overwrites its Default Gateway when connected to an ADv3   Resolution Update the Address Method to Static then enter the IP and Subnet address manually.  

Issue Reader beeper needs to be disabled so the reader makes no noise during operation including when a card is being badged at the reader. Product Line EcoStruxure Security Expert Environment Security Expert Smart card readers Cause When attempting to disable reader beeper by toggling the Disable buzzer processing option under Reader expanders Reader options tab the reader will beep when a card is read. Disable buzzer processing: When this option is enabled the reader expander will not control the reader beeper. The reader will beep once when a card is read, but will not beep additional times to indicate access granted or denied. The BZ output can be used for another function. Disable buzzer processing Resolution Unfortunately the reader beeper cannot be completely disabled, it will continue to produce a single beep when a card is read. This single beep on card reads is hardcoded into the reader firmware.  

Warning Potential for Data Loss: The steps detailed in the resolution of this article may result in a loss of critical data if not performed properly. Before beginning these steps, make sure all important data is backed up in the event of data loss. If you are unsure or unfamiliar with any complex steps detailed in this article, please contact Product Support Services for assistance. Issue For various reasons, it may be necessary at times to change a b3's Device ID (Object ID) to avoid a duplicate. Product Line EcoStruxure Building Operation Environment Building Operation Enterprise Server (ES) Building Operation Automation Server (AS) BACnet Cause There is little or no formal documentation on steps to change the Device ID of an existing B3 controller. Resolution As seen in the screenshot below, once a b3 is added to the network, its Device ID, EBO Object ID, can not be changed.  The reason for this is that the Device ID references the device and objects contained within it.  Once the ID is changed, such references will become orphans. To successfully give the b3 a different Instance/Device ID the b3 must be deleted from the MSTP Network in the Building Operation database and recreated   Write down the b3's Serial Number, MAC Address, Model, and BACnet Name before deleting it. Right-click and Export all BACnet Objects within the b3's Application Folder to file (.xml) Delete the b3 from under the MSTP network. Re-create the b3 manually using its S/N, MAC, Model, Name, etc but enter the new Device ID Commission/Download the b3 to get the new ID to take effect Import the File (.xml) exported in step 2 back into the newly created b3's Application Folder Commission/Download the controller again Important: References to the old Device ID will no longer work and must be re-created.