Building Automation Knowledge Base

Issue Upgraded Site to Continuum 2.01, now get %N and %D in Alarm Message as seen in the message field in the snapshot below: Product Line Andover Continuum Environment Cyberstation Keywords %D %N Cause This is caused by the Enhanced Alarm Logging and Enhanced Alarm Delivery being unchecked Resolution This can be resolved by using the following steps: Close all the cyberstations Initialise the database making sure you have Enhanced Alarm Logging and Enhanced Alarm Delivery ticked as shown below:  

Issue Offline alarms received from Continuum controllers every few minutes and log error 0x00006c0e Broadcast Storm AKA Error transmitting and/or 0x00006c03 Driver fatal error during operation. Product Line Andover Continuum Environment Continuum Net Controller II Continuum ACX 4 Controller Continuum CX Gen 1 Continuum bCX4040 Continuum bCX9640 Continuum BCX4000 Cause Excessive ARPs and/or other broadcast traffic on the network. Resolution When troubleshooting controller offline issues that are suspected to have excessive broadcast traffic as the root cause it is important to understand how to interpret Wireshark capture to determine whether too much broadcast on the VLAN  is indeed the problem. Note that taking the percentage of broadcast traffic in a Wireshark capture while a good starting point cannot in itself be solely used as proof that excessive broadcast is indeed the root cause of the controllers going offline, this is because in the absence of much unicast traffic the broadcast traffic will make up most of the packets resulting in a misleading high percentage. A much better way to determine whether the controller maybe going offline due to excessive broadcasts is to look at the average broadcast packets per second over a 15-20-minute capture. The screen capture below shows the statistics from a 20 minute capture filtered by broadcast traffic (eth.dst == ff:ff:ff:ff:ff:ff)  The capture shows that about 63% of the traffic is made up of broadcast at an average of 24 packets per second. The Continuum controllers on the network were going offline multiple times an hour. Note that the Continuum controllers are initially able to handle a much higher rate of broadcast traffic, tests performed in the PSS lab show a CX9680 can handled about 10 times  the amount shown here sustained for 5-10 minutes but over a much longer period of time such as several days or weeks the amount of broadcast traffic shown was enough to cause the controllers  to go offline. The screen capture below shows the statistics after the root cause of the excessive broadcast was identified and fixed. The problem at the site in question here was a defect in the network switch that was making the switch duplicate ARP traffic. Note that Cisco switch model Catalyst 4500 is also effected by the firmware bug. Current version which fixed the issue: Catalyst 4500 L3 Switch  Software (cat4500e-UNIVERSALK9-M), Version 03.08.05.E RELEASE SOFTWARE (fc2)   Previous version which caused the broadcast problems: Catalyst 4500 L3 Switch  Software (cat4500e-UNIVERSALK9-M), Version 03.08.02.E RELEASE SOFTWARE (fc2)

Issue When a Sigma data import is carried out, the following messages are displayed on the SBO ES computer. On the Sigma server computer, the Sigma server service has stopped. Product Line EcoStruxure Building Operation Environment Sigma 4.08 Building Operation Workstation Building Operation Enterprise Server Cause The Sigma database’s longtext file contains unsupported characters. Resolution Option 1: If Sigma longtext is no longer required: On the Sigma computer. 1)      Stop the Sigma server service. 2)      Delete the longtext.rec file from the Sigma Data folder (C:\Sigma\Data\longtext.rec). 3)      Start the Sigma server service. On the SBO computer Carry out the data import again. Option 2: If Sigma longtext is required: On the Sigma server computer. 1)      Start the Sigma server service. Open a Sigma client, either on the Sigma server computer or the SBO ES computer or other. 1)      Log into Sigma’s operator panel 2)      Go to the System Alarm manager 3)      Under the menu “Configure” select Longtext 4)      Open each longtext entry and remove the unsupported characters 5)      Add the longtext message your require. (You may find copies of the original longtext messages you can copy the text from, under “C:\Sigma\Data\Longtext” used by Sigma before the system was upgraded. On the SBO computer 6)      Carry out the data import again.   The data import should now complete.

Issue The STR-150 Installation Instructions state that the stat wires into D1, X1, and M of the Xenta 100 series controller. However, this is not applicable to the Xenta 121 and 122, which does not have a D1 input. Product Line TAC Vista Environment Xenta 122 STR-150 Cause The correct terminal for the mode input from the STR-122 is labeled differently on the Xenta 122 versus all other Xenta 100 series controllers. Resolution Wire the stat as follows: STR-150 Xenta 122 Label Terminal Label Terminal Mode 11 Y1 5 Data 12 X1 7 M 13 M 9 If you are looking for the wiring diagram for an STR-150 into a Xenta 121 the click here. The Purpose of output Y1 The only function that the STR-150 uses Y1 for is to get an effective occupancy signal from the Xenta 122. When the Xenta 122 is occupied, the man symbol will be displayed on the STR-150. If Y1 is already in use then the Status LED can be moved to a K output as explained is it possible to use an analog valve on the TAC Xenta 121-FC/HP and still have the effective occupancy active on the STR-150?. In order to activate this feature, the Hardwired status LED option must be selected. This can be found under the Configuration tab > Connected devices > Room unit in ZBuilder. If this feature is not desired then unselect Hardwired status LED and only wire up X1 and M. The STR-150 will still be able to send the controller the temperature, setpoint, bypass signal, and fan speed.

Issue Opening Controller Web Pages (such as those hosted by a bCX) using an external browser,  generates a 'pop up window' where you must enter authenticating credentials (username and password) before access to the controller's various settings is granted. . Using an ES, AS or AS-P Hyperlink however you can log onto to the bCX Main page, but when selecting any option from the menu, you do not see this 'pop up window' to enter your credentials and are instead greeted with an immediate Access Denied message Product Line EcoStruxure Building Operation Environment External web pages and/or controller web pages Cause Technically speaking the 'popup window' is a Frame within the web page which web servers of this kind commonly use.   Unfortunately, the ES, AS and AS-P do not easily handle such Frames or i-Frames and as such logging on becomes complicated. Resolution There is usually as single Frame which handles the Authentication which can be identified looking at the web server (in this case bCX) web page via Chrome + F12 which puts it into Developer Mode.    In this case if you allow the Authentication Frame to open in Chrome and then select cancel the Access Denied message is seen and Frame B4000MainMenu is highlighted Which can then be tested using that specific Frame in Chrome to be sure it does indeed cause the authentication window to appear every time. Once you know that this is the Frame which generates the Authentication you can create a logon Hyperlink in SBO which directly opens this Frame only After entering the correct log on credentials, you can then use a second SBO Hyperlink that connects to the Main web page of bCX and navigate to where ever you need to make changes.  CAUTION:  This authorisation will then remain active allowing access to bCX settings for anyone using that Workstation until the Workstation Session is closed (logging off is not enough)  

Issue Access Expert V2 configured MR52 Interface with inputs and outputs showing as Not attached (See snapshot) Product Line EcoStruxure Access Expert Environment V2 SSC MR52 Interface Cause The MR52 interface was previously configured with elevator controls but now has been detached in some manner. Resolution Remove the configured elevator references on each input and output individually and resave the point. Delete and re-add the points and configure the I/O as needed.  V3 works differently then V2. V3 allows for a more granular configuration so that the I/O selection just allows for the specific elevator other I/O selections. In V3 the assignments doesn't need to be released, only reselected.

Issue What is the procedure for adding an MR52 to a system. Product Line EcoStruxure Access Expert Environment Access Expert in Cloud or Premise Microsoft Windows 7, Windows 8, Server 2012, Server 2014 Cause Unable to find documentation of the installation process for the MR52. Resolution In order to add an MR 52 sub device to an SSC, the following steps need to be followed:   1. Address the board with proper address via dip switch settings (address switches should be pointing to the numbers on the board) 2. Power up the device and verify that LEDS are displaying correctly 3. Once the controller is Online, click on Add Interface 4. Open up the Live Monitoring Window to check the status of the controller 5. If the devices show offline, Right Click on the controller and select Reboot 6. The Live Monitoring Window will show what is actually being sent to the controller 7. Once completed the status will change to reflect what state the controller is in 8. If correct it will be Online (Green), if not check the configuration and/or wiring again

Issue Issues resizing SBO graphic editor frames with Windows 10 Lenovo P51 or T470 laptop with a Schneider Electric image. The following picture shows that the Graphic Editor did not re-filled the screen after resizing either the component/snippet area or the Object/property area, a border can be seen to the right and below the editor’s frame. Product Line EcoStruxure Building Operation Environment Lenovo P51 or T470 Schneider Electric imaged laptop. Cause Scale and layout: Microsoft .NET Framework version: Resolution 1. Scale and layout: Right mouse click on the desktop and select “Display settings” Set Scale and layout to 100% Re-boot computer   2. Microsoft .NET Framework 4.7.2: Download and install Microsoft .NET Framework 4.7.2 (Microsoft .NET Framework 4.7.2. can be downloaded from the Microsoft support site) Re-boot computer If these suggestions do not provide a solution or if you would like to provide some other feedback, please contact your local product support entity

Issue When the Ethernet is removed from an AX-SSC controller, all of the devices underneath that controller inexplicably lose their connection to the controller. Product Line EcoStruxure Access Expert Environment AX-SSC Cause The firmware of the SSC is outdated. Resolution The firmware of the SSC needs to be upgraded to version 24.01.241 or newer. This can be accomplished with the following procedure:   1. From Access Expert (the firmware of the SSC can only be updated within Access Expert, not from the Device Administrator), select the "Hardware Provisioning" tab. 2. Click "Controllers", and then select the correct SSC controller. 3. Under "General Info" verify the "Reported Version Number". If less than 24.01.241, the firmware needs to be updated. Click "Update Firmware".

Issue Unable to locate where to configure the SMTP Server in an Acess Expert V3 Instance. Product Line EcoStruxure Access Expert Environment V3 Premise Cause The earlier versions of the on-premise server/client did not have SMTP functioning properly. As a result, the tab to Configure the SMTP server settings was left out of the software. Resolution Newer versions of the software have SMTP functionality working properly. After upgrading the Server and Client software to the newest versions available, the SMTP Configuratiuon tab will be available as shown below.  Note: For Instructions on how to upgrade the Premise Server and Client software, please see Upgrade Premise Software to Latest Version.

Issue The Drayton Theta YBL1A Valve Body / Actuator assembly is to be replaced. Product Line Field Devices Environment Replacement Drayton Actuator Valve YBL1A Cause The Drayton Theta YBL1A Valve Body / Actuator assembly is obsolete. Resolution OVERVIEW The Drayton Theta YBL1A Valve Body / Actuator assembly is obsolete, and there is no purpose built replacement. The Valve Body was available in 1.1/4", 1.1/2" and 2" B.S.P. sizes and was normally installed as a mixing valve in variable temperature, constant volume, compensated heating circuits. No Valve Body / Actuator assemblies are currently available in these sizes. Details of the YB Valve Body may be viewed here.   VALVE BODY REPLACEMENT To replace the YBL1A Valve Body the following is required:- S-E SatchwellMB Valve Body of appropriate size - MB1552 (1.1/4"), MB1602 (1.1/2"), MB1652 (2") Details of the MB Valve Body may be viewed here.   ACTUATOR REPLACEMENT (6-WIRE INSTALLATION) The YBL1A Actuator normally comprised a 6-wire electrical connection enabling it to be operated by a Theta Potentiometric Controller as follows :-  Terminal M1 – Open signal Terminal M2 – Close signal Terminal M3 – Common  Terminal M4 – 135 ohm Feedback Potentiometer – winding Terminal M5 – 135 ohm Feedback Potentiometer – wiper Terminal M6 – 135 ohm Feedback Potentiometer – winding Where 6 wires are connected to the YBL1A Actuator then the Actuator may be replaced by one or other of the following S-E Actuators :- MD10B-24 MD20B-24 (if MD10B-24 not available) Details of the MD10B-24 Actuator may be viewed here Details of the MD20B-24 Actuator may be viewed here. N.B. The YBL1A Actuator also included an additional 3-wire electrical connection associated with an integral S.P.C.O. Auxiliary Switch wired as follows :-  Terminal S1 – Normally Closed Contact Terminal S2 – Common Terminal S3 – Normally Open Contact Where external wiring is connected to the YBL1A Actuator Auxiliary Switch then an Auxiliary Switch Kit containing a S.P.C.O. Auxiliary Switch should be installed on the MD Actuator. Auxiliary Switch Kit MD-S1 (914-1060-000) Details of the MD-S1 Auxiliary Switch Kit may be viewed here. The MD-S1 Auxiliary Switch Kit should be wired as follows :-. Terminal S1 – Common Terminal S2 – Normally Closed Contact Terminal S3 – Normally Open Contact   LINKAGE KIT A Linkage Kit will also be required in order to enable the MD Actuator to be mounted on the MB Valve Body. Linkage Kit LMD/AR-MB (914-1071-000) Details of the LMD/AR-MB Linkage Kit may be viewed here   IMPORTANT NOTE In such 6-wire installations not only will the YBL1A Valve / Actuator assembly need to be replaced but the associated Theta Potentiometric Controller and its Sensors will also need to be replaced.   CONTROLLER REPLACEMENT The Theta Potentiometric Controller may be replaced by the S-E Satchwell CSC5252 or the CSC5352 Compensator Controller. Details of the CSC Controllers may be viewed here.   SENSOR REPLACEMENT Theta 3-wire Temperature Sensors may be replaced by S-E Satchwell 2-wire Temperature Sensors compatible with the S-E Satchwell CSC 5252 or CSC5352 Compensator Controllers selected from the following as appropriate. Outside Air Temperature Sensor (STO 600) Contact Temperature Sensor (STC 600), or alternatively :- Immersion Temperature Sensor (STP 660) + Sensor Pocket Adaptor (DWA 0001) Room Temperature Sensor (STR 600) – OPTIONAL ONLY Details of the STO 600 Outside Air Temperature Sensor may be viewed here. Details of the STC 600 Contact Temperature Sensor may be viewed here. Details of the STP 660 Water Temperature Sensor may be viewed here. Details of the DWA 0001 Sensor Pocket Adaptor may be viewed here. Details of the STR 600 Room Temperature Sensor may be viewed here.   N.B. ACTUATOR REPLACEMENT (3-WIRE INSTALLATION) Should only 3 wires be connected to a YBL1A Actuator then the Actuator may be replaced by one or other of the following S-E Actuators :- MD10B-24 MD20B-24 (if MD10B-24 not available) Details of the MD10B-24 Actuator may be viewed here. Details of the MD20B-24 Actuator may be viewed here. N.B. The YBL1A Actuator also included an additional 3-wire electrical connection associated with an integral S.P.C.O. Auxiliary Switch wired as follows :-  Terminal S1 – Normally Closed Contact Terminal S2 – Common Terminal S3 – Normally Open Contact Where external wiring is connected to the YBL1A Actuator Auxiliary Switch then an Auxiliary Switch Kit containing a S.P.C.O. Auxiliary Switch should be installed on the MD Actuator. Auxiliary Switch Kit MD-S1 (914-1060-000) Details of the MD-S1 Auxiliary Switch Kit may be viewed here. The MD-S1 Auxiliary Switch Kit should be wired as follows :-. Terminal S1 – Common Terminal S2 – Normally Closed Contact Terminal S3 – Normally Open Contact   LINKAGE KIT A Linkage Kit will also be required in order to enable the MD Actuator to be mounted on the MB Valve Body. Linkage Kit LMD/AR-MB (914-1071-000) Details of the LMD/AR-MB Linkage Kit may be viewed here In such 3-wire installations the YBL1A Valve / Actuator assembly only will need to be replaced, while any associated Controller and Sensors may be retained.

Issue Having difficulties integrating an SED-T stat with the MPM (Stat not being "learned" by the MPM) Product Line EcoStruxure Building Expert Environment SmartStruxure Lite Multi-Purpose Manager SED-T00 SED-TS0 SED-TH0 SED-THS Cause Installation manual does not provide enough information Resolution Commissioning tips and recommendations   Dip Switches: SED-T series stats come directly from production with all dip switches set to 0. The dip switches settings must be changed otherwise the device will not send any telegrams. Tip: When pairing an EnOcean Temperature Sensor with the MPM, always set at least one pin of the DIP switch to the ON position before learning it in. Otherwise the MPM will not display any readings regardless of dip switch configuration even if the Enocean ID had been populated in the EODC object. The workaround at this point would be to click on the learn button again, the device will be learned successfully when the “RSSI” value and a “Last Communication” time stamp are displayed.   Example on how to use the dip switches: If the dip switches are set to 1= OFF, 2 = ON, 3 = ON, 4 = OFF, the stat would wake up every 10 seconds and take a look at the values. if they changed, the stat will send a new telegram with the new value. if the value did not change however, the stat will go back to sleep until the next 10 seconds elapse (first iteration). If the value did still did not change before the 7th iteration, then the stat will randomly send a telegram with the unchanged value at any time between the 7th and the 14th iteration. that is a minimum of 10*7 = 70 seconds and maximum of 10*14 = 140 seconds.   Solar cell: When removing the unit from the box for the first time, its energy banks (super capacitor) need to be charged using one of the methods below in order to be able to learn the device. A minimum of 2.1VDC is required before the stat can wake up and send a telegram and Ideally, the Super cap voltage should be between 4 to 5Volts. Method 1: Power the sensor with 24VAC for 1 hour (3volts/hour) Method 2: expose the solar cell to light for x amount of time depending on the light source: 1- Room with LED panels: 24hr minimum charging time (0.1Volts/hour) 2- Lit room with day light: 3-4 hours minimum charging time (0.7Volts/hour) 3- Direct sunlight: 1/2 hour minimum charging time (3.5Volts/hour)   Battery: The 20mm coin cell battery does not charge the super capacitor, however it slows down the depletion of super capacitor once its charge drops below 2.1Volts.

Issue When you're having issues with Continuum you need to check if the Windows account you are logging on with is part of the Local Administrators Group. Product Line Andover Continuum Environment Windows XP Windows Vista Windows 7 Windows 2008 Server Continuum 1.9X Cause Permission issues running or installing Continuum 1.9X Resolution Download the attached TestUserAdmin.zip file unzip the TestUserAdmin.exe file to your Desktop Open the Command window (DOS prompt) and run the TestUserAdmin.exe  The program will indicate if the logged on Windows user is a member of the Local Administrators Group or not.  

Issue No license is available for Vista Webstation Webstation installation issues ASP.NET Authority issue Product Line TAC Vista Environment Vista Windows 2003 Windows 7 Windows 2008 R2 Cause Sometimes it is not enough to let ASP.NET be run by NetworkServices. The user LocalSystem needs to be used instead. Resolution Windows 2003:  Go to Start and administrative tools. Click Internet Information Services (IIS) Manager. Expand application Pools Right click on  "SE ASP.NET v4.0 Classic" and choose Properties. Under "Identity" choose user "LocalSystem" from the Predefined drop list. Click OK and restart webstation. Windows 7: Right click on my Computer and choose "Manage" Go to Services and Application Click on Internet Information Services Click on application pools Right click on  "SE ASP.NET v4.0 Classic" and choose Advanced settings Under "Identity" choose user "LocalSystem" Click ok Restart webstation Windows 2008R2: Go to Start and administrative tools. Click Internet Information Services (IIS) Manager. Click Application Pools under the serve Right click on SE ASP.net v4.0 Classic and choose Advanced setting. See attachment IIS manager 1 Click the button beside Identity under the process model. See attachment IIS manager 2 Change the built-in account from networkservice to LocalSystem. Click OK and restart the webserver in Internet Information Services (IIS) Manager. If the problem persists, please see Problems installing Vista Webstation 5.1.5 or newer for additional helpful information.

Issue Can't communicate with more than 1 device on LG Gateway at the same time. Updated with solution on 12/15/2017 Product Line EcoStruxure Building Operation Environment LG Gateway Model:PQNFB17C1 Firmware version: 1.11.4 Cause The gateway can only provide one source address when there are multiple device IDs. The wireshark capture confirmed that no unique source ID provided by the gateway with different device IDs. Resolution Update the firmware version to 5.08.1h Configure the "BACnet Type Setting" to "B Type".

Issue Installed the tool under Windows 10 but was unable to assign a port in the tool's connection settings because there are no ports showing in Windows Device Manager. Product Line Andover Continuum Environment RoamIO2 BACnet Service Tool Cause Windows legacy hardware configuration. Windows 10 by default does not include the legacy ports. Resolution Legacy ports must be added to the Device Manager. 1. Open Device Manager from Windows Control Panel. 2. Select 'Action' then 'Add legacy hardware' or Go to "Start" and type hdwwiz.exe then press Enter 3. Next 4. Next 5. Next 6. Select 'Ports (COM & LTP) then Next 7. Select Microsoft/Standard Serial over Bluetooth link then NEXT 8. Complete the legacy hardware installation, Device Manager will then show the ports. 9. In the Service Tool select the appropriate port.   When the connection has been established from Windows PC to RoamIO2 device, the BlueTooth settings in Windows will indicate 'Connected'  NOTE that if it only indicates paired there will be no data transfer even though the blue LED is illuminated on the RoamIO2 device. (see screenshot below)

Issue The local time inside a Xenta programmable unit is dependent upon server time, time zone, and daylight savings time settings.  Incorrect DST settings result in incorrect times in the controller which causes problems from incorrect start times on HVAC equipment, to incorrect alarm time stamps in alarm queues. Product Line TAC Vista Environment Xenta Programmables version prior to 3.74 Xenta 280, 281, 282, 283, 300, 301, 302, 401, 401:B Cause In 2007, most of the United States and Canada changed when DST is observed to the second Sunday in March to the first Sunday in November.  Because it had never changed prior to that, programmable controllers retained the old settings (first Sunday in April to last Sunday in October). Resolution The issue was resolved with the release of firmware MOT version 3.74.  Upgrading your controllers to 3.74 is a viable solution, however not always cost effective.  There are two ways to work around the issue. Note: For information on how to download firmware to Xenta programmable devices using the Download Wizard please see Download an .MOT file into a Xenta Programmable controller. Configure TAC Xenta Central DST Settings Refer to the TAC Vista Technical Manual Chapter 19.6 In the folders pane, right-click the folder where you want to place the time event object. Point to New, point to Object, and then click Time Event – Object. Type the name. Open the time event object. On the General tab, type a description. On the Time Event Settings tab, set a suitable repeat interval, for example, first Monday in each week. Click OK. In the folders pane, right-click the folder where you want to place the Central Daylight Settings – Xenta object. Point to New, point to Object, and then click Central Daylight Settings – Xenta. Type the name. Open the Central Daylight Settings – Xenta object. Two options are available. You can use Windows start and end times for the daylight saving time or specify your own start and end times. If you want to specify your own start and end times: Clear the Use Windows settings check box. In the Daylight saving starts box, set the start time for the daylight saving time. In the Daylight saving ends box, set the end time for the daylight saving time. In the Update schedule box, browse to the time event object that triggers the push to the TAC Xenta devices. Click Select. Click OK. Note: You must select Manual DST Mode and Central DST for each controller in the system for a global change to take effect. Manually set DST Settings for each controller The DST Xenta object is not available in all versions of Vista.  If that is not an option, DST settings on each controller can be manually set for the start day and stop day.  Unfortunately, time settings do not allow for designations of "first Sunday" or "last Sunday," only calendar dates.  So each controller will have to be edited each year to maintain correct time settings. In order to facilitate this, this utility:  ODXentaTimezoneChanger was created.  It must be used each year to update the settings, but it will allow you to change all time settings on all controllers in a Vista database simultaneously, greatly reducing the time it takes to correct a system. NOTE: If the Lonworks network has not been properly commissioned & downloaded the tree will not properly communicate with the Vista Server. Check your network tree for asterisks to see if any downloads are 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 Services for assistance. Issue Is it possible to have a link on a GxPage to run an executable file to launch an external application outside of the web browser? Product Line TAC IA Series Environment I/A Series R2 graphics Firefox web browser Cause To launch an external application via a link on graphics page in a web browser. Resolution It is not possible to launch an external application from an I/A Series R2 GxPage. Two suggested workarounds are as follows. Create a hyperlink on a GxPage that links to a standard HTML web page. There would be a link to run a script on the standard HTML page to launch the external application. If the site graphics has a HTML tree created, create a new link in the tree which will run a script to launch an external application. * Take note that the HTML web page with the script link has to reside on the same computer as the external application. As an example the following script and procedure which will launch an external application in a Firefox web browser. In this case, the script will launch Windows notepad.exe. This method has been provided as a workaround but you should use and troubleshoot any information given below at your own discretion. Example of a script to launch an Notepad in Firefox: Right Click on this link and select "Save target as" to download this script as a text file We also need to configure Firefox to allow Java script to run. Run Firefox and type in 'about:Config' at the address field. Set the 'signed.applets.codebase_principle_support' to true. Be careful not to make any other changes. NOTE: This script and browser configuration may or may not work in other web browsers. Further changes may be required for this functionality in any other web browser other than Firefox.

Issue User is not being logged out of the Keypad after the log out time. Product Line EcoStruxure Security Expert Environment Security Expert SX-KLCS (Security Expert Keypad) Cause The User had an access level with a Menu Group that had the "Installer Menu Group" option enabled. This option disables the logout time for the keypad so the user is not logged out while the system is being configured. Resolution 1. Disable the "Installer Menu Group" option under the associated Groups | Menu Groups | Option menu; 2. Which will allow the keypad to log the user out after the (10s) "Time User Is Logged In (Seconds)" [2] value set under Expanders | Keypads | Configuration.

Issue A method to remove access from a large number of Personnel by changing the Expiration Date using a Template. Product Line Andover Continuum Environment Continuum Access Control Cause Need to know how to disable large numbers of Personnel at one time using the Personnel Expiration Date. Resolution The Personnel Expiration Date is distributed down to the Controllers and used to allow or deny access at the Door. If a future date is set then the Personnel has normal access, if a past date has been set then they do not have access and a "Person Expiration Date Passed" error will be displayed when they are refused access. See the steps below on how to use a template to mass set this Expiration Date field for a large number of Personnel at the same time.   1. Create a Personnel Template in the Personnel Templates Folder. Notice that the Expiration Date defaults to a future date of "12/31/2099 11:59:59 AM". 2. Go to the Attribute Data Source tab and set the ExpirationDate attribute to InheritFromTemplate. 3. Use this Template to create your Personnel objects. 4. Notice that Personnel created from this template should show the Expiration Date in Blue which is also un-editable in the Details tab. 5. Edit the Template and change the Expiration Date to a date that has already past. After saving the Template the changes will be made to all attached Personnel and those Personnel distributed to all online controllers. Viewing the Distribution Properties, you should see an entry for each object refreshed by the Template. 6. Looking at the Access Distribution View you should see that the Personnel have been redistributed down to the controllers successfully. 7. Test your Personnel at the Door and they should no longer have access. Looking in an active Event View you can see that the Personnel are not being granted access with the Message "Person Expiration Date Passed". When setting the ExpirationDate back to a future time they will now have normal access.