Building Automation Knowledge Base

Issue It is unclear how to unlock a door from a graphic. Product Line EcoStruxure Access Expert Environment V2   Hosted Instance & Premise Install See Premise Installs on Windows OS for supported Windows OS Cause In order to unlock a door from a graphic, the door reader must first be added to that graphic. Resolution To add a door reader to a graphic, do the following: From the “General Configuration” tab navigate to “Floorplans” and select the correct floorplan, then go to the hardware tab. Add the appropriate reader by clicking the green +, then drag it to the correct location on the floorplan graphic. Save the change to the floorplan graphic. From the “Access Control” tab navigate back to the newly updated floor plan. Now you can right-click on the reader and select “Unlock”. This will unlock the corresponding door.

Issue When attempting to login to the hosted instance, the below error is received indicating that the user is already logged in. Product Line EcoStruxure Access Expert Environment V2 Hosted Instance Cause There are two things that can cause this- A user can only be logged into a single instance at any given time. The user may currently be logged into a different instance. The user did not correctly log out of the instance they are attempting to access, and therefore is still logged in.  Resolution Take the following steps to resolve each of the two causes: Ensure that the user is not logged into any other instances. When closing out the web browser it is necessary to log the user out, as opposed to just closing the web browser. Failure to log out prior to closing the browser will result in this error.

Issue A control room requires that someone is physically in the room at all rimes. Require a sample programming solution for triggering an alarm output if the Area is empty for a specified amount of time.  Product Line EcoStruxure Security Expert Environment Security Expert Cause Sample programming solution. Resolution There are a number of ways to do this depending on the exact requirements. The easiest solution is to have an input trigger an alarm that then triggers an output. In my example I will create: Area - System Input - Motion Sensor Input Type - No Motion Detected Alarm Output - VO No Motion Alarm Bell 1. Create new Input Type, in my example mine is called "No Motion Detected Alarm". 2. On the OPTIONS (1) tab enable Generate Alarms, Generate 24HR Alarms and Report Alarms. 3. On the OPTIONS (3) tab enable Activate Input Control Output On Alarm and Deactivate Input Control Output On Restore. 4. On the Input set the Control Output field to your output you want to trigger. Set the Alarm Input Speed to 10m or 30m. (This is the caveat here, we do not have 15m selection with this option. If 15m is the required time then we will need to use another solution utilizing automation.) Set the Restore Input Speed to 0s or your preferred selection. 5. On the AREAS AND INPUT TYPES tab set the Area, in my case this will be System. Set the Input Type to the new one you created earlier, in my case this is No Motion Detected Alarm. You may need to change the Contact Type (on the OPTIONS tab) depending on what action the PIR is doing. Note1: You could also use the Bell output field in the Area (on the OUTPUT tab) as that will be triggered when the Area goes into alarm and reset when it restores to normal.  

Issue Continuum Analyzer Failure  (sample) [-] Alarm Integrity Looks for ghost alarm enable flags in the AlarmInfo table Failed Point AlarmEnrollment ObjectIDHi ObjectIDLo FireSmk19Closed DigitalOnALM 1015028650 1086324775 Product Line Andover Continuum Environment Continuum 1.92 Windows XP Cause File Configuration Resolution download file from here then unzip and rename to .xml* The patch is only for versions 1.92 and V1.93 Shut down CyberStation Go to C:\Program Files\ContinuumUtilities\Continuum Analyzer\Queries\System Reports\Alarms folder Rename the file 'Alarm Integrity.xml' to 'Alarm Integrity Old.xml' Copy the new file to the folder Run Continuum Analyzer and verify you no longer get the error. *To download you can RIGHT click on the link and select Save As

Issue How to create Elevator Access and Floor Override on Version 3 Product Line EcoStruxure Access Expert Environment Access Expert Applet Win 10 and above Cause There is no help or direction on how to perform this task. Resolution In order to do Elevator Controls, here is a link below to a video as well as some screen shots for clarification: Firstly there needs to have a Schedule, Access Level and Elevator Access created based on the application as seen on the screen shots Schedules Access Levels Elevator Access Elevator Reader Settings Elevator Floor Settings Floor Override Settings  

Issue To assist locating data sheets if you do not have access to the Schneider Electric BBE and other company storage areas. Product Line Satchwell MicroNet Environment IAC 400 420 600 TS data sheet Cause To assist customers that do not have access to our internet or partner websites Resolution Download the Data Sheets for Satchwell IAC 400 Controllers. Download the Data Sheets for Satchwell IAC 420 Controllers. Download the Data Sheets for Satchwell IAC 600/ Controller and Touchscreen. Download the Data Sheets for Satchwell MIU interface. Download all of the above: IAC Data Sheets.zip (file size 6.9 MB) Update: Jan 2018 The IAC 420, 600 and IAC Touchscreen have also been withdrawn from sale. Currently no direct replacement is offered. For more information, see PA-00528

Issue When logging into TAC Vista Webstation or ScreenMate, error message: Error Information The following errors have occurred. Please correct these errors and/or contact the system administrator. The Vista.Server.WebApps.Access license is missing. This license is required for the Vista Server to allow connections to the Web Applications. Product Line TAC Vista Environment TAC Vista 5.1 Vista Webstation 5.1 Vista ScreenMate 5.1 Vista Standalone package license Cause If the customer purchased the Vista Standalone license package, the Server-to-Server network and ability to be used with Webstation and ScreenMate is disabled. Two licenses are required in order to use Webstation or ScreenMate. Vista Server web function ability license: This license is required for Vista Server to communicate with Vista Webstation or ScreenMate. This license comes with the Vista Server license or some Vista package licenses, and cannot be purchased individually. It should look like something below in your license file: INCREMENT Vista.Server.WebApps.Access  taclic 5.1   Actual Webstation or ScreenMate seats. This license is required for users to log into Webstation or ScreenMate. This license comes with the Vista Enterprise package license or being purchased separately. It should look like something below in your license file: INCREMENT Vista.Webstation taclic 5.1, or INCREMENT Vista.ScreenMate taclic 5.1 Vista Standalone license package does not include the first type of license; therefore, when user log into the Webstation or ScreenMate, license is missing error message is displayed. Resolution Customer has two options to solve this issue: Purchase a full version of  Vista 5.1 Server license. Part number: 000882501 Part name: VISTA 5.1 SERVER   Purchase another package license which includes the full version of Vista Server license and replace it with the Vista standalone license. The standalone license can be rehost to another computer which does not need the web function for future usage. Read additional package license information in the “Software License Packages” document.

Issue Satchwell CZU Mk3 Zonemaster Controller requires replacement. Product Line Field Devices Environment Stand alone Fan Coil Unit Temperature Controller. Satchwell CZU Mk 3 Zonemaster Controller. CZU 3201 CZU 3202 CZU 3203 Cause Obsolescence of Satchwell CZU Mk3 Zonemaster Controller. Resolution Replacement of Satchwell CZU Mk 3 Zonemaster Controller with S-E Satchwell CZU Mk 4 Zonemaster Controller. The CZU 4201 may be used to replace the following CZU Mk 3 Controllers :- CZU 3201, CZU 3202, CZU 3203 N. B. CZU 3201 Controllers provided an additional -9 to +9 V d.c. output enabling connection to peripherals such as the Satchwell NSU 1401 Night Set-back Override Unit, TSU 1402 Two Step Auxiliary Unit and SSU 1403 Signal Selector Unit. CZU 3202 and CZU 3203 Controllers provided an additional -0.5 to +9 or -9 to +0.5 V d.c. output enabling connection to the Satchwell NSU 1401 Night Set-back Override Unit. Additional outputs are not provided on the CZU 4201 Controller and in those applications where these are required then it will be necessary to consider an alternative Controller to the CZU 4201. Details of the CZU 4201 may be viewed  here. A remote Satchwell Adjustable Room Temperature Sensor such as the DRT 3451, or a remote Satchwell Duct Temperature Sensor from the DDU range of Sensors may have been installed and connected to the Controller. Any existing remote Satchwell Temperature Sensor may be retained for connection to the CZU 4201. Should the remote Satchwell Adjustable Room Temperature Sensor require replacement then this may be replaced by an S E STR 612 Adjustable Room Temperature Sensor. Details of the STR 612 may be viewed here. Should the remote Satchwell Duct Temperature Sensor require replacement then this may be replaced by an S E STD 670 Duct Temperature Sensor. Details of the STD 670 may be viewed here.

Issue Operation of multiple Satchwell CZU Fan Coil Unit Controllers from a common Temperature Sensor. Product Line Field Devices Environment Fan Coil Unit installations comprising multiple Satchwell CZU Fan Coil Unit Controllers. Stand alone discreet Satchwell CZU Mk 1, Mk2, Mk3 and Mk4 Zonemaster Controllers CZU1201 CZU1202 CZU1203 CZU2201 CZU2202 CZU2203 CZU3201 CZU3202 CZU3203 CZU4201 Cause From time to time the need arises for office partition layouts within a building to be revised in order to reflect changes in occupancy requirements. This can result in the combination of numerous individual controlled spaces into a common controlled space. This in turn may result in the need to revise associated Fan Coil Unit control systems installed in the controlled spaces affected. Such revisions may require multiple Fan Coil Unit control systems to be controlled from a common Temperature Sensor installed in the common controlled space. This form of control may be achieved by adopting the installation method described in the Resolution. Should the common controlled space be of such a size as to benefit from the installation of averaging Temperature Sensors then this may be achieved by installing 4 non-adjustable Temperature Sensors.  The 4 non-adjustable Temperature Sensors should be wired in a series-parallel configuration in order to ensure compatibility with the associated Satchwell CZU Fan Coil Unit Controller. The series-parallel wiring configuration may be achieved by adopting the installation method described in the Resolution. Resolution 1.  Operation of multiple Satchwell CZU Fan Coil Unit Controllers from a common Temperature Sensor.  Multiple Satchwell CZU Fan Coil Unit Controllers should not be connected directly to a common Temperature Sensor. Instead the common Temperature Sensor should be connected to a single Satchwell CZU Fan Coil Unit Controller. The single Satchwell CZU Fan Coil Unit Controller should then be connected to the associated Fan Coil Unit Heating Coil Control Valve Actuators and / or Cooling Coil Control Valve Actuators. Up to 7 Heating and / or 7 Cooling Control Valve Actuators may be wired to a single Satchwell CZU Fan Coil Unit Controller in accordance with the method shown here 2.  Averaging Temperature Sensor control. Should the controlled space be of such a size as to benefit from the installation of averaging Temperature Sensors then 4 non-adjustable Temperature Sensors may be wired in series-parallel configuration in order to ensure connection compatibility with the associated Satchwell CZU Fan Coil Unit Controller. The 4 non-adjustable Temperature Sensors may be wired in series-parallel configuration to a common Satchwell CZU Fan Coil Unit Controller in accordance with the method shown here

Issue How does Visitor Management work in V3? Product Line EcoStruxure Access Expert Environment Hosted Premise Version 3 Cause No directions on how to configure Visitor Management in V3 Resolution In order to use Visitor Management in V3, here are the steps to get it configured: Open up a Chrome browser and enter this url http://ax.accessxpert.com Once the site comes up, enter the instance name and necessary user credentials From the AX Header, Select Visitor Management Tab Select the Kiosk Tab and Enter the visitor's name and email address and click Next to proceed Enter the person who the Visitor is seeing, system will automatically pull up the person, click on Next Capture the Photo of the Visitor and Crop accordingly Sign into the Window and click on Check in to see "Person" An email will be generated to that person to let them know that they have a Visitor A badge will be shown on the screen which has the Visitor's Photos and information Click on the Print Button to Print a badge that can be displayed on the Visitors body Depending on the printer (eg. Dymo being used), there are some settings that may need to be set for a good picture to be captured and Printed Choose the right paper source as well as scaling value.  In this case, it is set to 70 Once everything is correct click on the Print button to send to the respective Printer Attach to the Visitor for duration of the Visit Upon completion of the Visit, select Check Out and this will Check the Visitor Out of the system

Issue Digital Sentry and Endura VMS systems have specific cameras and firmware that are supported by the Continuum Integration Product Line Andover Continuum Environment Continuum Digital Sentry Endura 2.0 Cause In the past the video compatibility matrix was very specific about what vms firmware versions and cameras were tested and supported by Continuum. As of 2.02 and above, Continuum is relying on Pelco's testing of specific cameras with either Digital Sentry or Endura and this article lists those specific links. Only the Digital Sentry link was in the 2.02 Video Compatibility Matrix. Resolution Video Matrix for 2.02 - Download Here Pelco cameras supported by Digital Sentry v7.15 : http://partnerfirst.pelco.com/content/digital-sentry#sthash.ZkEtYiZd.w16va5xk.dpbs Pelco cameras supported by Endura 2.0: http://partnerfirst.pelco.com/content/endura#sthash.ii8IYPqC.dpbs Pelco support indicates that the camera compatibility lists are for specific models, not for a certain series of camera. i.e. IME22 doesn't mean the IME22x is supported.

Issue Satchwell "M 1301" Actuator forming part of combined Actuator / 3-port Valve Body assembly requires replacement. Product Line Field Devices Environment Stand alone Satchwell “M 1301” Actuator forming part of combined Actuator / 3-port Valve Body assembly M 1301 Actuator 3-port Valve Body Cause Obsolescence of Satchwell "M 1301" forming part of combined Actuator / 3-port Valve Body assembly. Resolution There is no direct replacement for the "M 1301" Actuator and as a result both the "M 1301" Actuator and the 3-port Valve Body to which it is connected will also require replacement.  Replace Satchwell “M 1301” combined Actuator & 3-port Valve Body assembly with Schneider Electric MD10B-230 Actuator, LMD-MB Linkage Kit and Satchwell MB series 3-port Valve Body of appropriate size. Details of the original Satchwell “M 1301” combined Actuator & 3-port Valve Body assembly may be viewed here. Details of the replacement Schneider Electric MD10B-230 Actuator may be viewed here. Details of the replacement Schneider Electric LMD-MB Linkage Kit may be viewed here. Details of the replacement Satchwell MB 3-port Valve Body may be viewed here. N.B. It is possible that the "M 1301" Actuator may have been fitted with an Auxiliary Switch. If so then an MD-S1 Auxiliary Switch may be fitted to the MD10B-230 Actuator if required. Details of the MD-S1 Auxiliary Switch may be viewed here.

Issue Installation and configuration for SE8600 heat pump application Product Line EcoStruxure Building Expert Environment  SE8600 Cause Installation and configuration errors for heat pump application Resolution SE8600 terminal identification In typical HP application, you shall connect to following terminals below: Y2 = Compressor 2 | Y1 = Compressor 1 | G = Fan | RC = 24 Vac positive | C = Common << 24Vac common >> W1 = Auxiliary Heating stage | W2 = O/B = First stage heating | UI22 = Supply temperature sensor | UI23 = Outdoor temperature sensor Depend on specification document, the application may require addition controls and connections. Application shall be set to: HP for heat pump From winter to summer season, high BP is the outdoor temperature value ABOVE which the system transfer from auxiliary heat <> and maintain heating setpoint with the heat pump << default 32°C >>. Temperature shall be set per system geographical localization. From summer to winter season, low BP is the outdoor temperature value BELOW which the system transfer from heat pump <> and maintain heating setpoint with the auxiliary heat << default -24.5°C >>. Temperature shall be set per system geographical localization. * Outdoor temperature sensor shall be installed   Heat pump reversing valve operation O: energize valve in cooling operation << default position >> B: energize valve in heating operation Heat pump system

Issue Unable to control Door output on SP-C when configured as onboard Reader Expander. Manual control of the Door outputs work but the Reader Expander will not control the Door outputs when a valid card is read. Product Line EcoStruxure Security Expert Environment Security Expert SP-C Cause The Controller was not registered as a Reader Expander. This is not done automatically for you when configuring the Controller through the wizard and needs to be done manually to be able to use the onboard readers. Resolution 1. Go to Sites > Controllers and on the Configuration tab select the address to Register as Reader Expander and the configuration of the Onboard Reader Lock Outputs. 2. Update modules and download. Note: In later Security Expert versions, it will say "Controller Relay 3/4 outputs" under "Onboard Reader Lock Outputs".  

Issue How to upgrade remote MPMs with a Canbus, Zigbee network. Product Line EcoStruxure Building Expert Environment SmartStruxure Lite Multi-Purpose Manager MPM Cause Cannot connect to an MPM directly to perform a firmware upgrade Resolution This procedure explains how to perform a firmware upgrade on multiple remote devices at once, in order to save time and standardize the firmware versions across your deployment. This process will induce traffic on the network, therefore it is recommended that this procedure be performed after-hours or when it is less likely to disrupt normal operations. Step 1: Verify your monitor Manager's firmware version Ensure monitor MPM has the same or higher firmware version than the the version intended to be installed on the remote MPMs. Highlight the MPM in the Network Panel on the left side of your screen and either click on the "About" button or navigate to CFG1 object to verify firmware version. Step 2: Download and rename the firmware file The firmware can be downloaded from the Exchange then firmware file must be renamed "upgrade.bp" Step 3: Upload the firmware file to your Manager Choose the File Manager tab and click on the “Upload File” icon. A dialog box will open to select the firmware file on your local PC. Browse to the correct file and select it. Click the “Upload” button to send the file from your computer to the controller. When the file upload is completed, the file will be shown in the Upload Manager list.   Step 4: Initiating the remote upgrade Inside the File Manager panel, either right-click on the firmware file that was just uploaded and select “Add to all” to copy the same file to all the remote nodes, or drag and drop the file from the left panel onto the desired Manager on the right panel. The file will be displayed under each of the remote nodes (or a single node if the file was copied using drag and drop) under the Network panel, on the right side of the window.   In order to initiate the file transfer to the remote nodes, click the Start button. The status will change to “In Progress” and you will be able to follow the progress of each node in the Network panel. Once the file transfer is complete, the remote nodes will reset and perform the firmware upgrade. Step 5: Verify the firmware version of the remote nodes You can verify that the upgrade process completed successfully by highlighting the remote node in the left panel and then select the “Controller Configuration” (CFG1) object. The version # will be displayed in the bottom section.

Issue A prospective customer requires their active directory be integrated into Continuum to eliminate duplication of data entry. Product Line Andover Continuum Environment CyberStation Active Directory LDAP Personnel Import Utility (PIU) Cause How can Continuum be integrated to an existing active directory for access control cardholder purposes? Resolution Yes, it can be integrated. The Personal Import Utility is a CyberStation application based on Active Directory.  Active Directory is a Microsoft Windows directory service that provides a unified view of complex networks.  Active Directory is installed on a Microsoft Windows Server, known as the domain controller.  CyberStation uses the Lightweight Directory Access Protocol (LDAP) to read and extract Active Directory user information. The above is from the CyberStation v1.93 Help System, a portion of which is attached here for reference.

Issue It is possible to have a timing issue with the start up of the license server as it relates to the start up of the TACOS.exe.  If TACOS starts before the license server the license server may not be able to read the license file and access to the your Vista products may be denied. Sometime the Workstation or other components can be launched, but all the points are offline. An error "No license for LonWorks communication" will show up. Product Line TAC Vista Environment Vista License Server TACOS.exe Cause TACOS.exe starts before the license server fully started.  When this happens, the License Server may not be able to read the license file properly and access to the your Vista products may be denied. Resolution This tool is a part of TAC Vista Run Mode TACOS Startup Delay is developed to help you set the startup delay for TAC Vista Server, whether it is running as an application or a service. You might find it necessary to delay the startup of TACOS to ensure that the license server or 3rd party software is fully started, before TAC Vista server starts. NOTE: This program allows you to set a delay from 0 to 240 seconds. Click Here: TACOS Startup Delay Utility Download the .zip file by clicking the link above Double click the TACOS Startup Delay 1.0.0.2 Application file When the window pops up you can enter up to 240 seconds into the delay field   Click "Set" button Reboot PC

Issue   A calibration certificate is sometimes requested by the end customer Product Line Field Devices Environment Veris sensors Cause   To ensure that a sensor is keeping measurement values within specification, a certificate is sometimes requested by the end customer. Resolution Calibration certificates are available for some Veris models and must be requested at the time of ordering by selecting  “N” in NIST block for 1% and 2% humidity transmitters. Temperature transmitters can be ordered with 1 or 2 point calibration certificates by selecting 1 or 2 in the in the Temp Cert Block. The following example shows how the model numbers are built up: As can be seen in the second example above the model HD2NVCTC2 has a 2% accuracy RH element with a NIST traceable certificate, it also has a 1K platinum RTD with a 2 point  calibration certificate. For information on NIST traceability see the National Institute of Standards and Technology website

Issue The Domain was upgraded to Windows Server 2008 and now the Workstations Windows firewall causes Andover  Controllers to go Off line. Product Line Andover Continuum Environment Windows 7, Windows Server 2008 R2 9680,9640 CX 75XX  9900, 9200 Cause Enhanced Security in the MS Server 2008 series domain enforces port blocking above ports 5000  and above. Resolution Add components , ports to the firewall exception list for Windows Firewall and for Anti-Virus Download List:

Issue Alarms need to be sent to specific Workstations and then escalated to other Workstations if they have not been acknowledged within a specific amount of time. Product Line EcoStruxure Building Expert Environment Security Expert Cause Documentation does not describe specific steps for how to configure alarm escalation. Resolution You will be able to do the alarm escalation with Security Expert by using the Alarm Routing options under the Events Menu. 1. Create your Workstations by going to Events | Workstations. The name of the new Workstation object in Security Expert will need to correspond to the actual Windows PC name for alarms to be routed properly. 2. After you have created all of the Workstations you will need to create Workstation Groups under the Events menu. One group for each level of alarm routing that you want to do. If you have three workstations and want to route from one to the next to the next, then you would need to create three Workstation Groups and add one Workstation to each of them. 3. Next you will need to create an alarm routing list under Events | Alarm Routing. On the Workstation Groups tab add the time for Transfer After (this is in seconds) which is when the alarms will be routed to the Workstations in the next Workstation Group. Set the Routing Order for those groups, the first group is 0. Next set the Transfer Priority if you have specific alarms that are to be routed to these Workstation Groups, leave blank if all alarms are to be routed. Set the routing group active to enable routing. 4. The last bit is to go to your Alarms that you want to route and add the routing list you created in step 3 to the Alarm Routing List field. This will now route these alarms to the Workstations you've configured.