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 Replacements for Schneider Electric SmartX MF41 Damper Actuator Product Line Field Devices Environment SmartX MF41 Cause Replacement of SmartX MF41 Damper Actuators within the Schneider-Electric range Resolution Outgoing Actuator Model         Replacement Model (Part Number)        MF41-6083-G00                         MD10B-24 (875 1015 000)      MF41-6083-G02                         MD10B-24 (875 1015 000) + Aux Switch (914 1061 000)      MF41-6153-G00                         MD20B-24 (875 1025 000)      MF41-6153-G02                         MD20B-24 (875 1025 000) + Aux Switch (914 1061 000)

Issue When setting up the TH90x series thermostats there are communication limitations.  Unable to pull multiple registers.  Some registers are only in Celsius, regardless of the display setting. Product Line EcoStruxure Building Operation, Field Devices Environment SpaceLogic TH903 Series Thermostat SpaceLogic TH907 Series Thermostat Cause The TH903/TH907 does not support multiple/block register reads in Modbus.    The following parameters will show their value in Celsius only via Modbus communication regardless of whether the display is showing values in Celsius or Fahrenheit:   All SpaceLogic Series TH9xx thermostats Register 30 - Function Code 3/6 - Room Temperature (from the remote Modbus Controller) Register 1 - Function Code 4 - Actual Room Temperature 7 Day Programming Versions of TH900: Register 26 - Function Code 3/6 - 7 Day program schedule, heat set-point Register 27 - Function Code 3/6 - 7 Day program schedule, cool set-point Register 30 is used by the customer to override the current temperature. This register expects a value to be written to it every 15 seconds. If no values are written to it every 15 seconds, then it will populate with our internal temperature sensor value. Resolution Registers must be read one at a time rather than in groups. When using Modbus write the set-point values in Celsius. 

Issue How to upgrade an Automation Server if Port 80 is closed and the Automation Server is placed behind a NAT router. Getting error message when upgrading: Product Line EcoStruxure Building Operation Environment Building Operation Automation Server Building Operation Automation Server Premium Cause The problem is that the certificate are generated with the IP address off the Automation Server, and not the NAT Router IP. Resolution The Device Administrator has the option to add SAN's (Subject Alternative Name) and not just the address of the server. So add both the LAN and the WAN addresses in the SAN field when you generate the certificate and transfer to the server.

Issue When doing an "import Trend Logs" in TAC Vista Conversion Tool only HTTPs works and not HTTP. When using HTTP the error message below is shown: "Log on to Building Operation server failed because Failed to access the server, a network error occurred" Product Line EcoStruxure Building Operation Environment TAC Vista Conversion Tool version 3.1.1 Cause This is an issue fixed in TAC Vista Conversion Tool version 3.2. The issue is that the "Import Trend Logs" tab looks at the HTTP/HTTPS settings of the "Convert Database" tab instead of its own. Resolution Use TAC Vista Conversion Tool version 3.2 when available. Workaround: Set the HTTP/HTTPS settings on the first tab(Convert Database) even if "Import of trend logs" is done.

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 How to combine multiple Continuum DBs into one DB Product Line Andover Continuum Environment Continuum Cyberstation Cause Multiple Continuum site databases need to be combined into a single site database Resolution Guideline for combining Multiple sites to one Database Executing this procedure requires a technician who thoroughly understands Continuum and how it works with SQL Server. This procedure does not encompass BACnet controllers. There is a multitude of decisions related to efficiencies and site preferences that are not documented here. The following procedure is intended for use as a guideline for combining multiple databases. This work must be done offline on a development database and validated on a test bench before Note:Before proceeding with this procedure you must do the following. Backup the Continuum database in SQL. Backup all the files and folder structure under New Graphic Files. Note that these files may be on the SQL Server or elsewhere on a mapped drive. Back all Cyberstation Profiles. Steps 1 – 11 must be done before any of the site exports are done. Preparation All sites must have the same revision software and CX firmware. NO EXCEPTIONS! Make sure that all the Alarm Enrollments and Event Notifications have unique names between all sites as these will wind up together in a single database. Make sure that all the Graphics in the Root directory have unique names between all sites. Make sure each Schedules in the Root directory has a unique name across all sites. Make sure each Custom ListViews in the Root directory has a unique name across all sites. Make sure each Groups in the Root directory has a unique name across all sites. Make sure each Reports in the Root directory has a unique name across all sites. Once steps 1-5 are completed, export each class in the root individually. Import files from step 6 into the new site The Local Site name on all the sites that will be combined must be named LocalSite. All workstations must have unique names and ACC IDs between the sites. All CX, ACX and BCX controllers must have unique names and ACC IDs between the sites. Note: The safest way to do steps 9 & 10 is to create a new controller in offline mode with the changed ID, then drag and drop copy from the original controller to the new controller. Panels, reports, and programs then must be edited to bind to the new controller. Another way to merge the panel, reports, and programs that are in the root is to copy all the panels, programs, and reports to their corresponding controller then export the controller. Doing this will keep all the bindings linked. Then once the controller is imported into the merged database they can be copied back up to the root. All Commports on all controllers and workstations must be named Comm1, Comm2, etc… Each site must have the default “ACC” user and password. All graphic files (.pin) under the New Graphic Files folder must have unique names between the sites. Merging the databases Install a standard multi-user Continuum system being sure to size the database big enough to accept all the other databases combined into one database.  After a clean installation is done, shut down the new workstation and the SQL server. Copy the empty database files to an area where they won’t get corrupted. Do a complete site export from each of the sites that will be combined. Back up all the Graphic files (.Pin) files from the site so that they can be transferred to the new server. Copy all the backed up Graphic files (.Pin) from each site onto a New Graphics Files folder in the location of choice. Note these files can reside on the SQL server or elsewhere on a mapped drive. Import each of the site text exports from the old systems into the new system. After each import check to make sure that each import went cleanly. Check all the Graphics, Programs, Alarm Enrollments, and Event Notifications to make sure that all the links were made during the import process.

Issue When using the SBO xbk Analyzer, a warning with the following details is observed:  *** possible configuration issue *** (QC#49504)  Issue: 'Communication failed' alarms between servers, even if no bindings are made Action: Make sure servers can communicate with each other so they can synchronize. Product Line EcoStruxure Building Operation Environment Building Operation Server backups version 3.x and above.  Cause The defect mentioned in the tool (QC#49504 / DBSQA-57599) was initially created because alarms were generated between two (or more) Automation Servers that had no bindings (or references) between them. This behavior is considered normal. This occurs because the servers attempt to synchronize references but fail due to communication issues, resulting in the alarms. These Automation Servers were previously part of the same system but were separated before reference synchronization was completed. A possible scenario for this issue is: Two servers can see each other. Bindings are established between the two servers. The connection between the two servers is then disrupted (i.e., offline). Subsequently, one or more of the bindings are deleted, leading to offline alarms between these servers, even if no binding exists now, due to pending synchronization. Resolution  The XBK analyzer tool detects this situation via a "SyncPending" flag, indicating that it needs to be investigated if a "Communication Alarm" exists between these servers. This warning can be ignored if no communication alarms are associated with the servers listed by the analyzer tool.   In most cases, if the server names listed by the tool are part of the system, the issue can be resolved by checking and verifying for unresolved bindings via Binding Diagnostics. while connected to a working EBO System.   If the tool lists any other server names that are not part of the system, these server names can be cleared by upgrading to EBO 2024 (v6.0.x) and above.  As stated, it is only a warning for earlier versions and can be ignored, as there can be instances where this is not cleared until upgraded to this release.        

Issue Analog Producer value located in an RP-C controller cannot command light object(BACnet type: crs-lighting-output) or blind object(BACnet type: crs-blind-output) located in another RP-C's CRS expansion module. Analog Producer Value, Status flags: Fault and Reliability: communication-failure.     Product Line EcoStruxure Building Operation Environment Building Operation Room Controller (RPC) 24 V Building Operation Room Controller (RPC) 230 V Cause Light and Blind objects support only two priorities (1 - Force, 2 - Normal). An error will be returned by the RP if the Priority in the Write request from the Producer Value is outside this range, ex. Priority 16. Resolution In the Analog Producer Value, set the default priority for writing to 2 (normal) or 1 (Force), as shown in below screenshot:  

Issue Do the Xenta IO modules, when used under a programable Xenta device, need to have a Field Device license added? Product Line EcoStruxure Building Operation Environment Building Operation Licensing Cause No clear information is provided on if the Xenta IO model needs a Field Device license. Resolution No Field License is needed for IO modules if they are set up under a Xenta programable device like a Xenta 400 or 300 series device. Only the devices that communicate to a Building Operation server require a license (Enterprise or Automation Servers). The Xenta IO modules only communicate with the Xenta programable device using LACNET communication and not the Building Operation servers.

Issue Unable to Access Access Expert after converting from V2 to V3 Product Line EcoStruxure Access Expert Environment Access Expert Hosted software V3 Cause Used the same Password as V2 Resolution When a site is converted from V2 to V3, Feenics sends out an email with a new username and password that can only be used within AX Version 3.   *Note* These new credentials cannot be used in V2. Once the conversion to V3 occurs, the V2 instance will be retired and you will only be able to use the V3 AX client to access your instance.

Issue After a PIN Duress Event at a door, the Duress Trouble Input stays "ON" and is unable to reset or restore the trouble input until a Valid Access Event occurs at the door. Product Line EcoStruxure Security Expert Environment Security Expert Controller Cause Attempting to restore Duress Trouble Input remotely after an accidental PIN Duress Entry by Card Users Resolution This is the intended design and function of the PIN Duress Trouble Input. It is considered an extremely-high priority issue and must be restored by a specific physical action. Remotely restoring (via Keypad in another location) would defeat the purpose of the PIN Duress Trouble Input. This is intentional to prevent a real duress event from going unnoticed.

Issue Is there any limitation for the number of local program variables that can be declared in a script program located in ExoStruxure BMS servers or BACnet/IP controllers?   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 Multi-purpose Controller Building Operation Multi-purpose VAV Building Operation Room Controller (RPC) 24 V Cause A script program has a lot of variables declared. Resolution There are no hard limits imposed by the script compiler. for the number of local program variables. The limits are performance and device resources. The bigger a program is, the more memory and processor bandwidth it will consume and the longer it will take to execute. 

Issue What is Life Reporting? Product Line EcoStruxure Security Expert Environment Security Expert Schindler Elevator HLI Integration Cause What function does the Life Reporting feature in a Schindler Elevator HLI Integration perform Resolution Life Reporting is a feature in the Security Expert Schindler Elevator HLI Integration. The life reporting interface is how Access Events from the Schindler system are reported back to Security Expert via TCP port. When enabled, you can receive "floor unlocked" events. Multiple loggers can be configured for the life reporting interface using the same IP address. Up to 32 loggers can be configured for the life reporting interface. You can also use Schneider Electric card readers for elevator access control alongside the Schindler system. For more details including prerequisites and configuration, please read AN - 196 - Security Expert Schindler HLI Integration    NOTE: Security Expert Software v 4.1.180 or higher is required. SX Controller Firmware v 2.08.919 or higher is required. One Security Expert Schindler Elevator High Level Interface License (SX-ELV-HLI-SC) per controller is required.

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 Instructions needed for batch importing Users into Access Expert Product Line EcoStruxure Access Expert Environment Access Expert Hosted V3 Cause Steps are needed to import Users from another system Resolution Batch Import   When converting a site, all user records and information needs to be imported into the new system. For Access Expert here are the steps in order to accomplish this:   Log on to the instance Once it opens up select the Access Control Tab and choose the Batch icon When this editor opens up select the Download Default Example file This will give a sample of the format that is expected when the Upload CSV is needed From the original application, if there is a dump file (Continuum) or an existing csv, copy and paste into an excel file or use the template and rename it accordingly. Choose the relevant columns to match from the list. Once satisfied with all the entries and fields, save the file then return to AccessXpert and select the Upload CSV as mentioned in Step 3. Select the file to open and once completed, all the users will then be displayed.

Issue Doors are going offline and online. Verification of the number of Reader Licenses purchased for an Instance Product Line EcoStruxure Access Expert Environment Access Expert Hosted Software V3 Cause When adding readers to an existing site the number of subdevices and readers may exceed the number of licensed readers in the instance, so doors bounce offline/online if power is removed from existing readers. A method for verifying the number of reader licenses is needed. Resolution Steps for verifying the number of Reader Licenses for an Instance Open Access Expert and log on to the Instance Right Click on the Instance and select the Manage License option A list of licenses for each object is displayed for the current Instance Based on this information the partner/user can determine how many licenses are required Create a Purchase Order and use the needed part number for the object Example: AXH-RMC-32V3 to add additional reader licenses

Issue Frequency of Zigbee device SED-CO2-G-5045 sending its values. Product Line Field Devices. Environment Zigbee SED-CO2-G-5045 CO2 sensor with room temperature and humidity Cause Unsure how frequently the sensor updates it's values to the network. Resolution The sensor has a Transmission Period (writable) that sets how often the device will send a measurement. Default value = 150 seconds Minimum period = 30 seconds maximum period = 600 seconds   Note that there is also a “Night Mode” to help extend battery life. During “Night Mode”, the transmission period is multiplied by 4.   Night mode is entered when the CO2 level falls below the “Comfort Limit Value”, which is 600 ppm by default.  

Issue Frequency of  Zigbee device SED-MTH-G-5045 sending its values Product Line Field Devices. Environment Zigbee SED-MTH-G-5045 Motion/Humidity/Temperature Sensor Cause Unsure how frequently the sensor updates it's values to the network. Resolution Motion Transmitted immediately on sensing of motion. Temperature  Transmitted, by default at least once every 10 minutes. If it has changed by 0.5 C or more, than it will be sent immediately with a limit on sending no more often than every 2.5 minutes. Minimum interval = 2.5 minutes Maximum interval = 10 minutes Reportable Change = 0.5 degrees C Relative Humidity Transmitted, by default at least once every 10 minutes If it has changed by 0.5%RH or more, it will be sent immediately with a limit on sending no more often than every 2.5 minutes. Minimum interval = 2.5 minutes Maximum interval = 10 minutes Reportable Change = 0.5% RH   These reporting rates are configurable for the sensor.  

Issue Troubleshooting Sigma IC LON Values going on and offline Product Line Satchwell Sigma Environment Sigma Release 4_05-SEB (Build 3_43_18) Sigma Release 4_05-SP2 (Build 3_42_48) Sigma Release 4_06 (Build 3_44_14) Sigma Release 4_06 SP1 (Build 3_44_16) Sigma Release 4_07 (Build 3_45_48) Sigma Release 4_07-SP1 (Build 3_45_51) Sigma Release 4_07-SP2 (Build 3_45_58) Sigma Release 4_08 (Build 3_46_57) IC LON Cause Lon Values going into and out of default Resolution Compare the IC-LON’s Receive heartbeat set in the “gateway.txt” file in the IC-LON controller, to the send heartbeat set in the controller. The recommendation is for the receive heartbeat be set to 2-5 times the send heartbeat of the field controller. Starting at 2 times, then increasing if the problem persists. If the controller doesn’t have a heartbeat and the LON value rarely changes, disable the receiver heartbeat in the IC-LON’s gateway.txt file by setting the heartbeat to 0. Example: 1     2     3        4      5   6  7 2,   2,  112,  1293,  0,  0, 0   The Sigma system is now out of its support period, consideration should be given to transitioning or upgrading to SpaceLogic - EcoStruxure Building Operation.

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. Issue The SLO Label shows an incorrect value range for kL. Product Line Field Devices Environment SpaceLogic SLO series Lux sensor Cause The label on the SLO shows the incorrect value range for kL. Resolution SLO: The product specification sheet states the Ranges for the jumper as: - 0 to 500 lx and 0 to 20 kLx The range to 500 lx can be seen on the circuit board. The product’s label shows 0 – 4kL The manufacturer has confirmed the label is incorrect the value should be 500 lx, New labels will be used in production from August 2022.   SLR: The tense delivery situation during the pandemic, especially for electronic components, has forced the manufacturer to make technical changes to the SLR in order to stay able to continue to deliver reliably. The range has extended from 0.4 to 0.5 kLux. These changes are incorporated in the corresponding instructions, provided with the devices. New labels will show the extended range.

Issue The Alarm Priority does not display the correct value (110) in the Alarm View or Event View when the Alarm is in the "Alarm" state and displays 100 Value instead. It displays correctly in the Alarm view when the alarm state is "Acknowledged" or "Reset", and it displays correctly in the Event view when the alarm state is "Reset Product Line EcoStruxure Building Operation Environment Building Operation Workstation Building Operation Automation Server Building Operation Enterprise Server Cause Incorrect configuration Resolution There is an"Alarm decorator override" that seems to override the priority for the alarm If in alarm state and priority is 110, then the priority is overridden to 100 as configured in the alarm decorator object Removing the override in the decoration will resolve this issue