Building Automation Knowledge Base

Issue Read Raw Data events are being shown in the Event view when a valid card is presented at a reader Product Line EcoStruxure Security Expert Environment Security Expert Cause If a User does not have an access level for at least one object on an SP-C controller then the user record is not downloaded to the controller Resolution If the requirement is to stop the message appearing there is a setting on the Reader Expander that can be unset.  If using this method, there is no indication the user has attempted to access the door.   Navigate to Expanders -> Reader Expanders and select the appropriate Expander.  Select the Reader tab for the door that the Read Raw Data event should be removed from.  At the bottom under Misc Options un-check the ‘Display Card Detail when Invalid’ option. This option will need to be set for each reader connected to a door where the Read Raw Data event is to be removed. In this example the option was un-checked for the Office 01 Entry door and as seen in the image below, in comparison to the same sequence of events shown in the Issue section, the Read Raw Data event is only recorded for the Office 01 Stores door and not recorded for the Office 01 Entry door. Note: When the ‘Display Card Detail when Invalid’ option is enabled (by default) the reader expander will send the details of any unrecognized card (facility and card number) to the controller.  Un-checking the option means that Read Raw Data will not appear for that reader.

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 Card being denied access at a Reader when attempting Simulated Card Read Product Line EcoStruxure Access Expert Environment Access Expert Hosted V3 Cause Card format is not assigned or created in the Controller Resolution To resolve an Access Denied Invalid Card format, the Card Format must be present in the System and assigned to the controller. The following steps shows how to accomplish this: If the card is read, a Message will show up on the Live Monitoring Window with the Raw Data from that card Use the Raw Data to decipher what format the card is as well as the Facility Code and Card Number From the Access Configuration Tab, Click on the Card Format to Create a new Format Assign it to the Controller, then reboot it to push the changes down Note: If there are multiple card formats, please ensure there are not more than 8 assigned. Add the necessary Access Levels for that card as well as the user To test use the Simulated Card Read function in the Reader Right Click on the Reader, Simulate Card Read Enter the values and card number and verify in Live Monitoring that the card has worked Once presented to the Reader, an Access Granted message would show in the Live Monitoring Window, depending on Hardware Configuration for Door Contacts etc.

  Issue Extending a User/Cardholder Expiry Date Product Line EcoStruxure Access Expert Environment Access Expert Hosted V3 Cause Steps needed to Extend an Expiry date for a cardholder Resolution In Access Expert, there needs to be a way to extend cards that are about to expire after the default time has been entered initially. This can be done for single users or badge types depending on the circumstances. The following steps describe how this can be accomplished:   Open and log on to the Users instance Once opened, select Access Control and click on the List Tab then select View Expiring Cards A list will appear that shows all the cards that are about to expire based on the parameters entered When this list comes up, Select the Extend All button to bring up the Editor that will extend the time Enter the New Expiry Date that allows the card to function accordingly Click OK and the cards listed will then have the New Expiry Date listed    

  Issue Understanding the EP1501 and LP1501 downstream device limitations Product Line EcoStruxure Access Expert Environment Access Expert Hosted V3 Cause Downstream device limitations determine how many upstream controllers are required when using these controllers Resolution When choosing to use the EP1501 or LP1501, knowing the limitations of the downstream devices plays an important part in determining the number of controllers needed for a job. The limitation is 8 I/O devices, so if the downstream controller is an MR 50 then a total of 9 readers including the onboard reader can be utilized. Keep in mind that no matter what the mixture is, including MR51e's or MR52's, a total amount of 17 readers can be used or licensed on these controllers  

Issue On many occasions with PC upgrades and replacements, there is the need to re-download the link for the application software as it gets somewhat difficult to know where to go and find it from the Feenics website Product Line EcoStruxure Access Expert Environment Access Expert Hosted software V3 Cause Unable to find the correct link Resolution The following steps show the URL address that is needed as well as how to log on to the instance once the software is downloaded and installed: 1. Enter https://www.feenics.com/training/lesson/downloads/ on internet browser as seen  2. Once completed and installed, launch the app and log on the instance

Issue Extended Logs have stopped updating on the Enterprise Server. Product Line EcoStruxure Building Operation Environment Extended Trend Logs Cause Extended Trend logs have been set up on the site for some time and have operated correctly. Now some of them have stopped updating.  Resolution This issue can be caused by a Server backup being restored. Trend logs and Extended Trend logs are allocated sequence numbers, and if the sequence numbers do not follow the correct sequence, the Extended Trend log may not update. To confirm that this is the issue; Trend Log. Navigate to the Trend log and open it in a "Trend Log List" view. Add an additional column to show the Sequence number. Note the highest sequence number used. Extended Trend Log. Navigate to the Extended Trend log that is referencing the above Trend Log. Open it in a Extended Trend Log properties. Press and hold down the "ALT" key and click where the dot is indicated on the screen shot below, (just below the Basic tab).       This will show some more properties for the Extended Trend Log, the one you are interested in is “Last transferred sequence number”.   If the last transferred sequence number on the Extended Trend Log is higher than the Trend log’s highest sequence number, then that is why the Extended Trend Log has stopped. How can this issue be resolved? Increase the sample interval of the Trend log until it has caught up. The Extended Trend Log will only fetch new records that has a sequence number higher than the last transferred sequence number. So until the sequence has caught up, you will not see any new records in the Extended Trend Log, and only records created after you have caught up in sequence numbers will be fetched. Re-create the Extended Trend Log. The new Extended Trend Log will fetch every record the log has and continue from there, but you will lose the records the old Extended Trend Log had that the log does not have anymore. Backup / restore on the AS. The Trend log will be cleared but the Extended Trend Log will start fetching new records.    

Issue Is it possible to let the ES directly write the write to file notification into the Windows event database? Is there a rotation for the Write To File Notification file so that a new file is written when the file is bigger than xMB?   Product Line EcoStruxure Building Operation  Environment EcoStruxure Building Operation - ES Cause Write to file notification can only be written to a file in the "db / notifications" folder on the server where the notification object is located. Unfortunately there is no rotation either. Resolution At this time it is not possible for an Enterprise Server to write directly to the Write to File notification in the Windows event database. There is also no rotation for the Write to File notification file so that a new file is written when the file is bigger than xMB.

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 3rd party BACnet device can send a reinitialize device request to an EBO server. Product Line EcoStruxure Building Operation Environment Building Operation Automation Server Building Operation Automation Server Premium Building Operation Automation Server Bundled Building Operation Enterprise Server Cause EBO servers support the "ReinitializeDevice-B" Bacnet device management service. This allows BACnet clients, such as BACnet browsers or operator WorkStations, to initiate ReinitializeDevice requests, i.e. Warm Start or Cold Start. Resolution EBO currently does not support passwords for the ReInitializeDevice service. It is possible to create a whitelist for the EBO server and exclude a 3rd party BACnet device from that list, but this will block all communication with the 3rd party BACnet device.

Issue When changing values like Check-in interval (s) under Poll Control for Zigbee device SED-MTH-G-5045, the value seams not to have been change when opening the dialog again. Product Line EcoStruxure Building Operation. Environment Building Operation Automation Server Premium (AS-P) Building Operation Room Controller (RP-C) non-Greenpower sensors SED-MTH-G-5045 Cause Setting is sent to the sensor only once every tenth minute. Resolution Open the dialog box again after 10 minutes to verify your changes.

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 ACX57xx Continuum controller frequently reboots itself, loses configuration and/or stop granting access to doors until reloaded.     In the controller error log frequent and spontaneous re-starts of the controller can be observed without an apparent cause such as power failure for example.     Here is another error log from different controller with same issue, a similar signature can be observed in the following screen shot   Product Line Andover Continuum Environment Continuum ACX 2 Controller Continuum ACX 4 Controller Cause Electrical noise coming from door striker corrupting controller's memory.   Resolution An external Varistor may be installed for Noise Suppression of a Door Strike. Here is a link to a part that may be used for this purpose:   https://www.digikey.com/en/products/detail/bourns-inc./MOV-07D470KTR/13420467?utm_adgroup=General&utm_source=google&utm_medium=cpc&utm_campaign=PMax:%20Smart%20Shopping_Product_Zombie%20SKUS&utm_term=&utm_content=General&gclid=Cj0KCQjwteOaBhDuARIsADBqRei7ZmpR8CRYf12zRH1bfTIK7GHk3NC6XStbVoCBrPizkZvEPDlCaFEaAjLFEALw_wcB    The part should be installed at the Door Strike, from the switched 24VDC terminal to the common 24VDC terminal, like this:  

Issue Using Download Wizard 32 with Application set to Clear Memory, one will get an error that "The application file could not be found! Product Line EcoStruxure Building Operation Environment Building Operation Workstation Xenta Programmable Controller Cause EBO Workstation does not include the Lonm<Model Number>.MTA file. Resolution There are two solutions: Create a minimal MTA file for the device type. Open Menta Editor Change the device specification for the appropriate Xenta Type. Add one PVR block Save the file. In DWiz, change Application selection to Download New and Browse in the new file. Perform the steps again with the expected files in the same folder as DWiz. Download the attached Lonm.zip (derived from Menta 5.1.9) Extract the files in the zip to the same Workstation folder where Dwiz.exe is found. Sample Location: "C:\Program Files (x86)\Schneider Electric EcoStruxure\Building Operation 3.2\WorkStation\DWiz.exe" Perform the download again with the same Clear Memory selection under the Application section.

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 Correcting failed links between programming objects after upgrading files from .vsd to .vsdx Product Line TAC IA Series, EcoStruxure Building Operation Environment I/A Series WorkPlace Tech Building Operation Workstation (WorkPlace Tech Editor) Cause After existing .vsd files from pre-WorkPlace Tech 5.10 versions can have corrupted links that stay red when programming objects are added or modified. Resolution This video demonstrates how to correct binding failures that can occur when existing Visio drawings are converted from .vsd to .vsdx format when upgrading to Workplace Tech 5.10 and EBO 4.0 and newer WorkPlace Tech Editor. Note: The objects in the original drawing will no longer show a Master Shape reference (below) The frame around the object appears a little different as well.  The Mega Master will not be changed so this has no effect on the performance of these objects.

Issue Pop-up error message displayed when trying to create ContinuumDB on stand-alone system. Unable to get past this to create the database. Error message similar to below: "Microsoft SQL Server 2005 Setup The sa password must meet SQL Server password policy requirement. For strong password guidelines, see Authentication Mode, in SQL Server Books Online."   Product Line Andover Continuum Environment Continuum Stand-alone SQL Express Cause When SQLExpress was installed a "strong" SA password was not defined. Resolution As per Microsoft SQL password policy Strong passwords must meet the following guidelines: The password does not contain the account name of the user. The password is at least eight characters long. The password contains characters from three of the following four categories: Latin uppercase letters (A through Z) Latin lowercase letters (a through z) Base 10 digits (0 through 9) Non-alphanumeric characters such as: exclamation point (!), dollar sign ($), number sign (#), or percent (%). Passwords can be up to 128 characters long. Use passwords that are as long and complex as possible.   To change the SQL password: Download and install management studio express. http://www.microsoft.com/download/en/details.aspx?id=8961 Change SA password so that it now complies as a strong password. Find the SA user under Security\Logins. Change the Password. Run Database Initialization again and create the new database using this new SA password.

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 A combined keypad reader works with a valid card swipe, but the keypad does not work. The keypad does not allow a valid pin to be entered to engage the door output even though the door, area and personnel objects are setup correctly. This issue could also happen with a keypad only, without the combination reader. Product Line Andover Continuum Environment Keypad Keypad/Reader Combination Cause A keypad or keypad/reader combination can be ordered with the keypad output set to work in a number of different modes.  Continuum requires the output mode to be ordered as follows: Buffer one key add compliment 8 bit message (Dorado) This is also known as 8 bit burst A keypad that has a different configuration than this will not work with Continuum   Resolution 1. Order a keypad or keypad/reader combination with the 8 bit burst output mode set 2. Contact the keypad manufacturer's technical support (Eg. HID), to see if they will send a Configuration Card that allows the output mode to be changed retrospectively in the field.

Issue Receive error "Property value out of range" when creating a BACnet interface on the Enterprise Server   Following problems after upgrading SmartStruxure servers to 1.5: Attaching an Automation Server to or detaching it from an Enterprise Server will fail with “Property value out of range” error. Changes to the ~/System/Interface Manager/BACnet fail to be propagated lead-shadow functions through to the child servers. Automation Server controllers dropping offline following an upgrade to 1.5 (BACnet command priority related  also may see numerous "Changeset Rollback errors") Product Line StruxureWare Building Operation 1.1, 1.2, 1.4, 1.5 and above Environment Enterprise Server (ES) BACnet IP Interface Windows XP, Windows 7 and Windows Server 2008 R2 Cause Their may be various items that generate this error, checking the Enterprise Server (ES) system log in the Software Administrator may assist in pin pointing the error.  If you see an error that ends with ~/BACnet Interface/IP Network, then this error is generated when their is no valid IP Network.  For SmartStruxure 1.5 or above or planning to upgrade from 1.4 to 1.5 (and above)  This issue only occurs if a BACnet interface is used and the site has changed the BACnet "Default Priority Level" from the default value of 16, to 8 or a smaller numeric value in the Automation Server while running in V1.4. The "Property value out of range" message relates to the new Force priority level in 1.5 and the Default priority level in 1.4.1 being mismatched. Resolution The ES must be connected to an IP network. To resolve this error follow these steps: Close all Workstations (if running) Connect the Enterprise Server to a valid IP network (with a valid IP address). Stop and Restart the Enterprise Server service through the Software Administrator application. This should now allow the BACnet Interface to be created successfully For SmartStruxure 1.5 or above or planning to upgrade from 1.4 to 1.5 (and above) Please refer to TPA-SBO-14-0005.00 Before upgrading to 1.5 make sure the "Default Priority Level" within the Automation Server is set to 9 or higher.  If the system has been upgraded with the incorrect values, then: If the site uses single servers, or the ES/AS communication still operates correctly, then this can be corrected by changing the setting in both the AS and the ES to a value of 9 or higher.   If after upgrading a multi server configuration and the AS does not stay online, then a Hotfix can be used fix the problem using the following steps: Apply the hot fix #1.5.0.4301; available from Product Support Services Fix the multi-server (by detaching/re-attaching the servers) Correct the two properties (AS and ES). WARNING: It is essential for any BACnet system at 1.5 or later that the "Default Priority Level" must have a larger numeric value than the "Force Priority Level, otherwise some BACnet functions may not behave as expected. Note: This also applies even if the hot fix has been installed. The effects of not setting the Default above the Force Priority level are: If Force Priority Level is equal to the Default Priority Level: Changing the Value of a BACnet value or a BACnet output object will cause the Value to appear Forced. This applies to the BACnet objects in both SmartStruxure servers and those in 3rd party BACnet devices.   If Force Priority Level has a larger numeric value than the Default Priority Level: Changing the Value of objects mentioned above will cause the Priority Override icon overlay to be turned on next to the Value property in the WorkStation’s property grid.   

Issue Steps on how to setup BACnet Time Synchronization to 3rd Party BACnet controllers. Product Line EcoStruxure Building Opertaion Environment SmartX Enterprise Server (ES) SmartX Automation Server (AS) BACnet Cause It is not always clear what is required to setup BACnet Time Synchronization and how to confirm that EcoStruxure Building Operation is actually performing it properly. Resolution To use the Time Synchronisation you will need to bring the 3rd Party BACnet device (Eg. Continuum bCX) under the EBO BACnet Interface -> IP Network: Go to the BACnet Interface Time Synchronization Recipients Tab. Add a new Local time synchronization recipient with the '+' button. Select recipient type as 'reference' In the Recipient device object reference field browse for your BACnet Device. Press OK and then save the changes. Right-click on the BACnet Interface and select send time sync now. This will send out an unconfirmed-req TimeSynchronization to that specific Device only.   Test Scenario with a bCX setup as a third-party BACnet controller You will see a unconfirmed-req TimeSynchronization packet being sent from the ES in WireShark but with no response from the bCX.  You may not see responses back from other 3rd party devices. The time in the bCX should be seen to change from within Continuum, (assuming it was incorrect in the first place)