Building Automation Knowledge Base

Issue How do you determine which version of Access Expert being used Product Line EcoStruxure Access Expert Environment Access Expert Hosted V3 Cause Unsure which version of Access Expert is installed Resolution When opening Access Expert new users may not know what version they are currently running. The following differences can help to identify the version being used.   Version 2: Uses a url e.g. http://seba.accessxpert.com The Hardware tree is on the left pane when selected Only five tabs on the header Icons are larger on screen No Folder View  Version 3: Uses an app that needs to be installed The hardware tree is on the right Seven tabs on the header depending on the license Icons are much smaller Folder view when enabled  These are just a few of the differences that are visible to help determine which version is being used.

Issue Details on Access Expert Keep Alert Feature Message usage Product Line EcoStruxure Access Expert Environment Access Expert Hosted software V3 Cause Details on Access Expert Keep Alert Feature Message usage Resolution The Keep Alert feature in Access Expert comes with a default 500 SMS messages a month. This can be used to send a broadcast to the users on the system. For example, if the administrator wants to send a text out to 50 people based on an event, then that would leave a total of 450 remaining.   Another use case would be if there was an active shooter at a school campus where there are 500 students, then this would be done one time and the max texts would be sent.   Additional amounts can be purchased in 500 amounts based on what the need is for the customer. so that their monthly usage stays within the amount purchased.

  Issue Information needed to work with Access Expert Custom Forms Product Line EcoStruxure Access Expert Environment Access Expert V3 Hosted Cause Access Expert Custom Form configuration Resolution Custom Forms Overview Forms can be designed and applied to maintain additional people & reader information outside of traditional documentation or notes. Unlimited customer forms/fields can be added to the system and associated with a person or reader. The layout of the forms can be built to accommodate customer needs and can even be segmented. A good practice is to group additional information into common groupings such as Car Information, Health Information or Department Information. This type of approach will make the data entry easier. Information captured in a Custom Form can also be searched on and reported on. Once a custom form is created it will be available for use from either the person menu or the reader menu. Custom fields can then be utilized for applications such as customizing people reports, capturing additional information about employees, doing system searches as well as badge designing.   New Custom Form To start creating a custom form: Select the ‘General Configuration’ Select "Custom Forms”. Click “Add Custom Form”. Choose which editor the form will apply Enter the name of the Custom Form in the Application Name. (OPTIONAL) Choose the casing for the form. This is only important when leveraging the API or LDAP integration. Click “Save” or “Save & Close”. Below is an example of a Custom Form that has been created. The header, fields, titles, and placement of information on the form is customizable by clicking, dragging and dropping. The initial series of editors that support the creation of the form are across the top of the screen. Add Text Box – Adds a free form text box. Add Combo Box – Adds a free form text box that allows for multiple pre-selected entries from a picklist. Add Date Time – Adds a time and date entry box. Add CheckBox – Adds a checkmark box. Add Group Box – Adds a split box where the top section can be used as a title then other fields can be added. Add Header – Adds a header field that can be used for a single line title. Group Box When one of the box types is added to the form, the Properties section can be used to apply additional information and modify the data as it resides in the box. Every Content field that is added to a Custom Form must have a name. In this example, we will add a Group Box to capture information about an employee. Clicking the ‘Add Group Box’ provided the initial field. The title was applied by clicking the blank box and adding the name in the Properties editor under Content. This information can also be positioned to the left, center, stretched or to the right. The overall box can be enlarged by clicking the perimeter and then dragging to the desired size. Text Box Additional fields of information can be added to the Group Box by clicking on the desired data field type and it is applied to the Group Box. To ensure the new field is added inside the perimeter of the Group Box make sure to click inside the Group Box prior to selecting the data field. The new field can be dragged into the Group Box if it is added outside the group box. Once the field is added to the Group Box the Properties editor will allow the same type of modifications to be made. Once the new blank field is added you can click into the Header field under Content to apply a descriptive name. This same process can be repeated to add as many fields as needed.   Combo Box A Combo Box is added to a Custom Form just like the other box types. With a Combo Box, the Properties editor will display a new field called Items. Clicking the “…” will allow the operator to add the information that will be available when data entry is being performed. The completed form will look like this from the custom data menu on the cardholder.

Issue   A site has multiple locations in its instance. The goal is to restrict objects for a User in other locations by using permissions and tags which allow certain objects only for the local instance. The User also requires access to Event History, Live Monitoring and Floor plans.   After setting User permissions for specific objects, the object permissions work as expected, however clicking on Event History, Live Monitoring or a Floor plan shows: 'An error has occurred in the Live monitoring document while trying to execute initialize' Or Access Expert will show one of the following errors depending on which event object was selected: 'An error has occurred in the Event History document while trying to execute initialize' 'An error has occurred in the Floor Plan document while trying to execute initialize'   Product Line EcoStruxure Access Expert Environment Access Expert V3 Hosted Cause Event-level permissions function differently than object-level permissions Resolution User permissions set up with tags to restrict access to other locations will work as expected with objects like hardware, but these restrictions will not work with event objects.   The options to accomplish this are: 1. Buy an enterprise license and divide up the sites with their own instance. Each location should be represented by a shared instance with its controllers configured. Those controllers will publish their event to only their instances which can be controlled using permissions. This is the preferred method.   2. Allow ALL Type permissions for the hardware and event objects to be accessed. Using this method allows the event objects to work, but allows Users from other locations to access the hardware.   Event-level objects use an entirely different mechanism than regular objects. The technology under the hood requires that an enterprise license be used to accomplish event-level permission restrictions.

Issue The sequence numbers for Alarm Events are changing daily for all active alarms in the system. This can be a problem for applications using sequence number as alarm identifier. Product Line EcoStruxure Building Operation Environment Building Operation Enterprise Server. Building Operation Automation Server Premium Cause Every night there is a cleanup in the alarm table and alarms can then get new sequence numbers. Every night historic updates with old time stamps are removed in the alarm table.   When this cleanup takes place, there is a reorganization of sequence numbers of current alarms. They all get a new sequence number.   The new sequence numbers are always higher than the latest sequence number before the cleanup. Resolution Do not use alarm sequence number for alarm identifier, use triggered time stamp instead.

Issue The following error message appears when trying to change the system security settings of an Enterprise Server in Webstation:   An error has occurred Object protected ~/System/Security Manager/Global Security Settings     In Workstation the same settings are disabled (greyed out) and cannot be edited at all:   Product Line EcoStruxure Building Operation Environment Building Operation Enterprise Server Building Operation Webstation Building Operation Workstation Cause The probable cause of this issue is that the Enterprise server is part of an EC - ES multiserver system setup. Then some settings are in a Lead - Shadow relationship and can only be controlled from the top EC (Enterprise Central) server. Resolution Edit these settings on the top Enterprise Central server.

Issue An AS-P (SpaceLogic Server) is crashing; just before the crash, the memory usage in the AS-P increases until it reaches a level where the AS-P crash.  Product Line EcoStruxure Building Operation  Environment Building Operation Automation Server Premium (AS-P) Cause The issue was caused by a Notification report which was located in the ES to which the AS-P was connected, Every time this report was run, the AS-P crashed after a while.  This report included a search of all Modbus points in the system and all properties of the Modbus points. When running the report, the ES was setting up a lot of subscriptions to the AS-P in a very short time period. The AS-P could not handle this huge amount of subscriptions and crashed after a while when trying to process all subscriptions from the ES. Resolution In this particular case, the AS-P had around 2000 Modbus points. When the Notification report was running, the search for these 2000 Modbus points and all properties, which were around 20 per Modbus point, caused the ES to set up around 40 000 (2000*20) subscriptions to the AS-P in a very short time period, and it crashed. To solve this issue, the number of Modbus points in the AS-P was reduced to below 1000, and then the AS-P could handle the number of subscriptions (1000*20=20000) with no crash.   When running a Notification report, including a search, be careful not to search for too many objects and properties in the same report, like in the example above when a search was done for all Modbus objects and properties in an Automation Server.   This is only a problem when a search is done via a Notification report if doing a search from Workstation that is made differently and will not set up a subscription in the same way.

Issue EP series information not available in documentation Product Line Field Devices Environment EP Series Pressure Sensor Cause Required information for planning installation. Resolution The EP 3x series consumes maximum 20mA input power as determined in loop powered mode (4-20mA).  When in three-wire voltage output mode, up to 2 mA of additional current may be drawn from the load. Further information is available on the Schneider Electric Exchange - EP Series Pressure Sensors.

Issue With the same time interval as the trend log, the traffic on the LonWorks network increases for a short period. This can be seen by a spike in the LPA log when viewing the bandwidth. Product Line EcoStruxure Building Operation Environment Building Operation Workstation Lonworks Cause The LonWorks traffic increases with the same time interval as the trend log. Resolution To ensure we could log values in the trend log from a LonWorks device, a subscription is set up about 30 seconds before the value should be logged. After the value is logged, the subscription is removed until the next log interval. A good solution to flatten a spike caused by this issue is to stagger the times of the LonWorks trend logs. This will ensure the subscription for all the logs do not happen at the same time.

Issue Could we have 128 characters passwords in Struxureware?  Product Line EcoStruxure Building Operation Environment Building Operation Enterprise Server Building Operation Automation Server Premium Building Operation Automation Server Bundled Building Operation Workstation Cause In earlier versions of SBO (version 1.7), the password was limited to 100 characters.   Resolution In EBO version 2.0 and 3.0, 128 character passwords are allowed. Passwords have been tested with 500 characters.    

Issue When using the Find function to search for specific records the default size of the Find window can mislead the user to think there are no records to select from. Find Button Product Line EcoStruxure Security Expert Environment Security Expert Client Cause The default size of the Find window is too small for some of the field values to be displayed which can lead the user to think there are no records to search for. Resolution Resize the Find window by pulling down on the bottom right corner which reveals a list of selectable records and the right-hand side scroll bar. Expanded Find Window

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 attempting to update the firmware on the SP-MRDM module, the update process fails, and the module appears offline with the fault LED activated. A "Module not responding" error message is displayed that indicates the module should be disconnected, and a utility used to restore the firmware.   Product Line EcoStruxure Security Expert Environment SP-MRDM SP-MRDM2 Cause The module has lost its firmware during a failed firmware update attempt, leading to the offline status and fault LED activation. Resolution To resolve this issue, follow these steps: Establish a connection to the SP-C controller using a web browser. Force a module update operation from the Application Software tab. Note that it may be necessary to check the "Skip Verification" checkbox during the update process.

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 A system with multiple WebRequest calls appears to become erratic after upgrading the AS-P to EBO 2022 and above. After a reboot, multiple scripts execution are hanging.   In previous EBO versions, the script would be stopped and return an Unknown Exception error message.   Product Line EcoStruxure Building Operation Environment Building Operation Automation Server Premium Building Operation Automation Server Bundled Building Operation Enterprise Server Cause The Architectural Guidelines always recommended a maximum of 5 concurrent WebRequest calls. In EBO 2022, this limitation is enforced to limit the impact on the system resources and prevent scripts stopping due to Unknown Exception errors.   Architectural Guidelines    Web requests exceeding this number will be queued, and the scripts doing these calls will hang on that function as the queue is emptied. This will directly impact the execution of other scripts.   Resolution 1. Enforce a good scripting practice to prevent more than 5 concurrent Web Request calls. 2. Cascade the execution of scripts to make sure that after a reboot, the scripts are executed in a sequence to prevent simultaneous calls filling the queue and causing scripts to be stopped.  

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