Building Automation Knowledge Base

Issue Upgrading Digital Sentry breaks the Video Server connection or cameras won't learn or video streams do not work Product Line Andover Continuum, Pelco Environment Pelco Digital Sentry 7.9 or greater Continuum Video Integration 1.94 SP1 up to 2.01 Windows 7 Windows Server 2008 Windows Server 2012 Cause Pelco released a newer version of Control Point that is used in Digital Sentries Video Recorders 7.9 and above. This newer API is not currently supported in any version Continuum, up to version 2.01. Resolution Available as of July 2017, install version 2.02 of Continuum, it is a full install. R&D has worked on revising the Continuum Video Integration to work with the newer versions of Control Point 7.15 and above. The only work around prior to this to get the video Integration to function was to downgrade the Digital Sentry to Control point 7.8 Uninstall the DS ControlPoint software using Add/Remove programs (MS Windows XP) or Programs and Features (MS Windows 7). Install: How to install the DS ControlPoint client software Note: Upgrading the Continuum Security Key to an Endura Key will not allow the newer API to be used with a Digital Sentry with Continuum. A copy of the latest Video Compatibility Matrix can be downloaded from the Download Center in PA-00568.

Issue Error importing a StruxureWare Building Operation export file. Below is an example of the error.  ERROR: Import failed to commit changeset transaction with an exception. RecoverableException: /home/ci/ci-build/rb-rb-1.8.1-system/source/server/nsp_servers/csc/changesetmanager/source/ChangeSetTransaction.cpp(1442) Invalid Data Error: File_Extension_Not_Permitted (0x10048) in module Security_Manager(74). "Not permitted to store the file "htgseqintro.wmv" with the current Document Policy." - Stack Environment StruxureWare Building Operation 1.8 Cause The export file contains a document file extension that is not permitted in the Document Policy Permitted File Extensions Resolution The file extension has to be added to the Permitted File Extensions list. See Adding a File Extension to the Permitted File Extensions List on Web Help. For the error example shown in the issue of this article, the extension wmv has to be added to the Document Policy Permitted File Extensions. list. 

Issue Controllers are unable to get online after configuration and being added to the relative instance. Product Line Access Expert Environment Access Expert in Cloud or Premise Installations Win 7, Win 8, Server 2012, Server 2014 SSC Controller Cause There are two reason why this could happen: The controller is not communicating with the Feenics Host Service. Outbound Ports are being blocked. Resolution To resolve the issues, please check the following: The controller is not communicating with the Feenics Host Service. The panel may have lost power or network communication. Dip switches may be set incorrectly (Refer to the Mercury Installation Manuals for operating modes) Network Firewall may be blocking outbound communication over port 3001 (Give our Network Tester tool a try, find it within the downloads) Configured DNS server may be unable to resolve at the correct IP.       2.    The user is unable to see events through the Feenics Event Publishing Service. Outbound port 4502 may be blocked. (Give our Network Tester tool a try, find it within the download section) The client has lost internet connection.

Issue After a card is created and added to a user, card is read and the credentials are invalid and not working. Product Line Access Expert Environment Access Expert, Server 2012 R2 and above. Version 2 Version 3 Cause There are several reasons that  could cause Access Denied to occur as listed below. Resolution To resolve the issue please follow the steps below: Access Denied – Invalid Card Format The intelligent controller has no configured card format which matches the number of bits sent from the credential reader. Opening this event inside the live monitor or event history view will display the card bit length of the credential along with its hexadecimal encoding. Access Denied – Invalid Facility Code The intelligent controller has a card format which matches the bit length of the card, however there are no card formats which match the facility code. Opening this event inside the live monitor or event history view will display the interpreted card numbers & facility code based off of the card format with matching bit length. Access Denied – Card/PIN Not Found The intelligent controller has matched the card format & facility code, but has no matching card number value. Opening this event inside the live monitor or event history view will display the interpreted card number & facility code based off of the format with matching bit length. When receiving this event with a card believed to have been programmed correctly, Users may issue a clear/reload cards on the controller to update the database. Access Denied – No Door Access The intelligent controller has acknowledged that this card has access on this intelligent controller, but not to this particular reader.     Access Denied – Door Schedule The intelligent controller has acknowledged that this card has access to this reader, but it is outside the allowed schedule. This event may also trigger if the interface dip switches are not configured correctly. **Don't forget to take advantage of Mercury’s Simulated Card Read functionality to ensure that the controller is making the correct access decision. In V3 the Card Formats needs to be added to the Controller in Order for this to work. **If a reader produces no audible response or LED change when a credential is presented it means that either the reader is powered incorrectly, or that it cannot read the credential technology.

Issue Access Denied NO access at the door Product Line Access Expert Environment Win Server 2012 R2 and above Cause 1) The cardholder does not have sufficient Access Levels assigned. 2) The Max access levels has been reached by the intelligent controller. 3) The access levels were not successfully downloaded to the controller. Resolution To resolve this, the following steps need to be followed: 1. Ensure that the access levels contains a door group which consists of the trouble reader. 2. Check that the person has the correct access level assignment, 3. Try saving the access level again so that it is pushed to the controller. 4. If possible, issue a reboot command to the intelligent device to ensure database synchronization. OR if the system database limit on access levels has been reached, take the following steps. Verify the user has permissions on the Role Go to the General Configuration Select System Settings Select the Hardware Tab on the bottom Change the Max Access Level to a higher level than the default (100). Save and Reboot the controller for the changes to take effect

Issue The communication with TAC Xenta controllers is slow or inconsistent Product Line EcoStruxure Building Operation Environment TAC Xenta LonWorks communication Cause The Non group receiver timer is not properly set. Every device has a timer called Non group receive timer. The Non group receive timer is used to make sure that a re-sent Lon package will not be treated as a new message and to determine when a receiver buffer can be released. It is used in Acknowledged, Repeated and Request/Response transactions, but not in Unacknowledged ones. If this timer is set too low, a re-sent package, like Unacknowledged repeated message, may be treated as new messages, that will be sent on to the application. The communication buffers will not be released until the timer has expired. If the timer is set too long, that may result in the device running out of buffers, and new messages will not be received during this time. If a device has many SNVTs or TACNV’s being transferred there may be a need to increase the value of the Non group receiver timer. The default value for a programmable Xenta device is 768 ms. Resolution Change the Non group receive timer of the Xenta devices. The default value for a programmable TAC Xenta device is 768 ms. The recommended timer values are:   Number of network variables Non group receive timer value < 50 768 ms (default) 50 – 100 1024 ms > 100 1536 ms     The default value for the AS and AS-P  is 8,092 ms. There is no need to change that value.

Issue Creating new user roles and knowing the access that is needed for it to become active. Product Line Access Expert Environment Cloud or Premise Installations V2 Win 7 Win 8 Server 2012 Server 2014 Cause Knowing what the role the user is playing would determine what selections need to be activated for them. Resolution To achieve this the following steps need to be followed: Open up General Configuration Select the Roles icon Click on the tab for New Role (everything is blank by default) Name and configure accordingly Check all tabs to make sure everything is Viewable and Editable Save and close Now this role can be selected for any user once created

Issue Some actuator datasheets do not specify the impedance of the 0-10V control signal, this is required to determine fan out from a controller. Product Line Field Devices Environment MB3 Range - MB3-24M, MB3-SO-24M, MB3-SC-24M MZ20 Range - MZ20A, MZ20A-R MVT56 Range Cause Information not defined on the specification sheet. Resolution MB3 Range 0-10V control signal input impedance = 200K Ohms. MZ20 and MVT56 Ranges 0-10V control signal input impedance = 32K Ohms.

Issue If a Variable status alarm is setup on a BACnet point it never triggers. Environment Workstation V1.8.1  and earlier Cause The reason is that the 3 available triggers (Forced, Overridden and Offline) do not apply to the BACnet protocol. If you open up the bindings page for a BACnet point you will see that none of the BACnet point attributes are the same as these 3 trigger statuses. Resolution Although from the SBO side you can force a point, what actually happens is that the value becomes commanded at "Command priority 8" (by default). The BACnet protocol does not have a Forced attribute. There is also no attribute listed for Overridden and Offline point in the BACnet standard. Because of this the Variable Status Alarm does not apply to a BACnet point.  

Issue Why isn't the OpenLNS a full, un-limited license? Environment OpenLNS OpenLNS CT Cause Renewing OpenLNS CT Annual Maintenance You can renew your annual maintenance for OpenLNS Server and OpenLNS CT before they expire. Renewing your OpenLNS and OpenLNS CT annual maintenance enables you to continue installing software updates and upgrades. If you do not renew the products’ maintenance, you can still use the products; however, you will not be able to upgrade it with updates or upgrades released after your annual maintenance expired. You cannot renew your annual maintenance after it has expired. Once it has expired, you must purchase a new activation key to be able to install any updates or upgrades released after your maintenance expired. To renew your annual maintenance, purchase an OpenLNS Commissioning Tool Professional One-Year Maintenance Renewal (Echelon model number 93800) or an OpenLNS Commissioning Tool Standard One-Year Maintenance Renewal (Echelon model number 93810). Echelon will process your order, and your maintenance coverage will be extended so that you can continue updating and upgrading OpenLNS and OpenLNS CT for an additional year. Resolution If paying the annual maintenance fee, you have access to updates and upgrades. Not paying still means that the program could be used, however it could not be updated with the latest patches.

Issue MPM rebooting with message in the log like: MASTER_MAN (id= 9) 361893.721> FAULT: core_watch.c:333; code:0; time:2017-02-13 15:34:25; Message:Task ID 38:Lua_User_PGs expired at 361886.5; Top Of Stack:0x000000F3 0x20D4BE7C 0x71B73B76 0x0000007A 0x00000000 0x60000013 0x60000013 0x00000000 0x2084D224 0x08080808 0x09090909 0x10101010 0x11111111 0x00000015 0x2006FD91 0x2006FD91 0x20D48D3C 0x20062159 0x00000000 0x00000000 0x20EE8248 0x20D48D3C 0x00000000 0x00000000 0x22D50000 0x00000000 0x20D1E8E4 0x000007D0 0x00000000 0x2084D238 0x00000000 0x00000000 ; Product Line EcoStruxure Building Expert Environment MPM Cause This is an error in one of the PG object (user written Lua script) possibly an infinite loop. Resolution Disable or delete 1 by 1 your Lua PG's to identify the PG with the issue.

Issue BACnet Input shows "Out of Service". When attempting to set a value or remove the out of service flag an error is seen. "An attempt has been made to write to a BACnet property with a value that is outside the range of values defined for the property." Environment bCX4040 b3 Controllers Cause An xP Module attached to the Controller was malfunctioning and the inputs on this board were not functioning. Resolution Powering everything down, re-seating the xP Module board and powering the Controller back up resolved the problem.

Issue How to automatically have b3 controller backup to flash. Product Line EcoStruxure Building Operation Environment b3 Script Program Cause Script program syntax is a bit different to how it was done in Continuum, specific details needed on how to set this up.  Resolution This is a sample script program to enable automatic backup to flash when the controller database is different to what is currently stored in Flash. Create the below Script Program in the b3 controller. Make sure to bind both the input and output variables to statusbackup/value. 'bind statusbackupin and statusbackupout to the systemvariable statusbackup/value. numeric input statusbackupin numeric output statusbackupout init: if ts >= 5 then goto checking checking: if statusbackupin = backupneeded Then   statusbackupout = backupnow Endif goto wait1day wait1day: if td >= 1 then goto init

Issue When a controller goes Offline, no email is being generated from the system when set up. Product Line Access Expert Environment Access Expert Server2012 SQL2012 R2 Hosted Instance Premise Instance Cause There is no email server set up in the User interface for the system to use. Resolution To resolve this issue please follow these steps: On the General Configuration tab, click on System Settings Verify these settings or use the default Click on User Interface Tab Use a valid email address e.g. Name@Domain.com Verify that the system is generating the email by Triggering an Alarm  e.g (Controller Disconnected Long Time)             

Issue Configuring the SSC to use Comm Port B on an SSC. Product Line Access Expert Environment Server 2012 SQL 2012R2 Hosted Instance Version 2, Version 3 Premise Install Cause The SSC is not configured to work on Comm Port B for the RS-485 connections, all communications to downstream devices are done through Comm Port A. If you have done so and it functions, please note that this is not supported. Resolution All communications on an SSC for RS-485 in Access Expert needs to be done on Comm Port A.

Issue A Pelco IWP221-1ES IP camera is being used and configured as a direct camera in Security Expert but the image from the camera is not being displayed in the Security Expert. Product Line Security Expert Environment Security Expert Pelco IWP221-1ES IP camera Cause The wrong URL to the image feed was used. When we use the IP address of camera to display the camera image in a web browser, it requires the Pelco Media plug in or Quicktime but these cannot be used in Security Expert. Resolution Use a direct URL to the camera stream. For the Pelco IWP221-1ES IP camera, use "http://camera.ip.address/jpeg/pull".

Issue After setting up an SSC controller, it does not come online even after multiple Resets and putting it into DFU Mode. Product Line Access Expert Environment Access Expert Windows Server 2012 Cause The device was previously set up, maybe at the office. Now, when taken out to site, it shows that it already exists on another instance. Resolution Open up the initial instance that it was set up on Right click and Delete the device Open up the new instance that it will be current on If already created, then communication should start automatically Once online, program accordingly

Issue Sites need guidance on how to setup custom ABA cards in Continuum. Environment CyberStation NetController I (CX99xx) NetController II (CX9680) AC1Plus IOU Module ACX57xx Cause The implementation of ABA cards in Continuum access control systems was designed to comply with the ISO 7811 ABA standard for magnetic stripe card. Because of this, the system only reads  one field (the PAN or Primary Account Number) from the ABA card, this field contains a number of up to 19 digits which is used as the card number. Continuum Custom ABA feature provides for maximum flexibility by allowing the 19 digit PAN field on track 2 of the mag stripe to be organized in sub fields such as site code etc. Resolution A summary of the steps to configure Custom ABA cards in Continuum is available through the CyberStation Online Help.  Open the help on the Continuum workstation and search for "Defining a Custom ABA String Format"          

Issue Under objects such as Doors and Inputs what is the "Commands" option used for? Product Line Security Expert Environment Security Expert Cause Unsure how to use the Commands option showing in some of the objects options. Resolution These cannot be adapted for general use by installers/integrators. These are mostly used for controller instructions that have been included in the firmware but have not been built into the UI yet, as well as internal testing. Leave these alone unless you have a specific need and the instructions from Product Support on how to configure the command.

Issue Using a non-default SQL Server port with Continuum. Environment Continuum Workstation SQL Server Cause SQL Server has been changed from the default port setting and  confirgured with a specific static port for incoming SQL connections. Resolution Continuum doesn’t care if the SQL Server is using a default port or not. As long as the Database can be created/updated using the Database Initialization application it will work fine. This has not been tested or qualified but should work fine. After the port is changed, the user should perform the Database Update process to ensure that the connection can be made from Continuum to SQL Server and vice versa. Here’s a Microsoft article on how to change the SQL port. https://support.microsoft.com/en-us/help/823938/how-to-configure-sql-server-to-listen-on-a-specific-port