Building Automation Knowledge Base

Issue What protocol of the Ziton ZP3 Fire Detection System does our Xdriver utilize? Environment Continuum Xdriver - Ziton Fire Panel Cause Need to confirm that the XDriver is able to communicate to third party fire panel. Resolution The Ziton XDriver has been developed to the ZCP2 communications protocol V2.01. Contact the manufacturer to confirm whether the panel supplied supports this version of the protocol.   Further information on the XDriver can be found at the link below. Clymac - Ziton Fire Panel

Issue When working with numbers that are 7 digits or longer the number is displayed in exponential format and there is a loss resolution in the lower digits that can cause an issue with metering applications. This can be an issue when using pulse counter inputs. Product Line Andover Continuum Environment All Continuum controllers and modules that support Pulse counting with Counter inputs Cause The number formatting throughout the Continuum product is 32 bit IEEE Floating point notation, for numbers up to 7 digits long they will be displayed as a regular decimal number, for larger numbers they will be displayed in exponential format: Significant digits × base exponent This allows Continuum to work with huge numbers like 123.45 x 10 67 but has the disadvantage that as the numbers get larger there will be a loss of resolution in the lower digits starting with the units. Resolution When working with pulsed inputs from meters try to keep the size of the numbers down, putting scaling factors of x10 and x100 only makes the numbers bigger, so where possible scale the numbers down and upscale the units. For example when scaling an input where you would enter a conversion of: Value+(ElecValue * 10) Instead use: Value+(ElecValue*0.1) and change the units to Kilo Units, Mega Units etc. If you have to measure large pulsed numbers another option is to split the large numbers across 2 Numerics, so in Plain English when a value gets to 999,999 then add 1 more pulse, you get 1 in the upper number and 0 the lower number. This can then be displayed on a graphic with 2 adjacent text boxes. Where very accurate metering is required the best solution is to use meters with an intelligent data interface that supports one of the common open protocols supported by Continuum (i.e. BACnet MS/TP, Modbus or M-Bus via X Drivers). This solution means there is no chance of missing a pulse or Continuum getting out of sync' with the meter. Note: If you need to set the lower number back to zero, then the object first needs to be disabled. If this is a BACnet bCX then the BACnet name (eg BACnetDevices\bCX25\Counter2) needs to be used within the PE Program

Issue Adding a device through the System Plug-in results in missing SNVTs, SCPTs, or Module/Functional Block Names in the Vista database. Environment Vista 5.x.x Cause The XIF file is either incorrect or parsed improperly. Resolution Right click on the device and select properties. Click on the XIF file tab. View the XIF file name (this can be found in the $thisfil directory of the Vista database) and either browse in a renamed copy of the existing file or an independent copy of the file by clicking the ... button. Click Ok Log out of Workstation Log into Workstation to see the changes. Note: For a change to be detected the filename or location of the file must be different.

Issue The pressure drop across the valve is required. Environment Valve Pressure Drop Cause Customer needs to know what the pressure drop across a 32mm valve will be. Resolution Example: two 32mm V211T valves with flows of 0.549 l/s and 0.483 l/s through them. To calculate the pressure drop use this formula - Pressure drop = (Flow rate in M3/Hr / KVs) squared. Flow rate of 0.549 l/s 32mm V211T has a KV of 16 Converting flow to M3/Hr - 0.549 * 3.6 = 1.9764 Pressure Drop = 1.9764 / 16 = 0.123525 squared = 0.015258 Bar * 100 = 1.526 kPa Flow rate of 0.483 l/s 32mm V211T has a KV of 16 Converting flow to M3/Hr - 0.483 * 3.6 = 1.7388 Pressure Drop = 1.7388 / 16 = 0.108675 squared = 0.0118102 Bar * 100 = 1.181 kPa To review the Satchwell Valve sizing data sheet, please click HERE.

Issue Need to activate an Output when access is denied to a User at a Door. Product Line Security Expert Environment EcoStruxure Security Expert Cause In the Door object, there is a facility for triggering Outputs on Pre Alarm, Door Left Open, and Door Forced Open but nothing for when a User is denied access. Resolution There were new Door commands added to SP-C firmware 2.08.1018 and newer to add this functionality. AccessDeniedTime = # has been added to the Door commands which will specify the duration in seconds that an output or output group will be activated for when access to the door has been denied. This must also be paired with one of the following 2 commands in order for the functionality to occur. AccessDeniedOutput = # has been added to the Door commands which will specify the output that will be activated when access to the door has been denied. The # will be the database ID of the output/output group. AccessDeniedOutputGroup = # has been added to the Door commands which will specify the output group that will be activated when access to the door has been denied. The # will be the database ID of the output group. As an example, if you wanted the Output with an Id = 3 to turn on for 5 seconds when access is denied at the Door, the following lines would need to be added to the Door object in the Commands section. AccessDeniedTime = 5 AccessDeniedOutput = 3 Door Command - Access Denied Output  

Issue Menta file Simulates (F12) and Generates OK and even downloads from Vista apparently OK, but monitored values shown the message 'Failed to read signal'. Connecting to the controller with the serial lead and entering online simulation mode gives a 'PARSER ERROR'. The Memory Usage stats show less free space than would be expected for a file of this complexity. Environment Vista Menta Xenta Cause The Menta file has some corruption that is not visible when viewing the Functional Block Diagram. Resolution Some files may be rescued by copying the FBD into a new empty Menta file: Create a new empty Menta file with the same Device and Program Specifications as the corrupted file. Open the corrupted file in a second instance of Menta. Drag a selection box around the entire visible FBD and enter Ctrl+C to copy. Switch to the new Menta file and enter Ctrl+V to paste the FBD. Please note that this procedure will copy references to named constants across to the new file, but it will not copy the constant definitions. Selecting F12 will highlight the function blocks containing the references to the missing constant definitions.  Edit the block and press 'OK'.  A dialog box will pop up for each constant where you can fill in the value, unit and public parameters.  Repeat this procedure by selecting F12 until Menta enters simulation mode without errors.  You will also need to create the OP tree and any trend logs from scratch. If you are lucky, the new file will download and run without errors.

Issue If an Automation Server should be used as a LON Device in an OpenLNS Database using the OpenLNS Commissioning Tool? Is that possible to do? Product Line EcoStruxure Building Operation Environment Automation Server 1.4.1.68 or newer   Cause Some sites may wish to use other Lonworks configuration tools than EcoStruxure Building Operation Workstation. Resolution This is possible in 1.4.1.68 and newer. Add a Lonworks Local FT-10 interface and then add an Externally Managed Lonworks Network.

Issue Tolerances for resistors when used for RS485 bus termination and EOL for double balanced inputs. Product Line Security Expert Environment Wiring Cause Resistor specification required for ordering purposes. Resolution 330 ohm EOL resistors are required for the RS-485 bus and 1K ohm resistors for EOL zone (input) configuration. 330 ohm = 5% tolerance, Metal film 1000 ohm = 1% tolerance, Metal Film

Issue I/NET will run in application mode, but will quickly shut down when in service mode Product Line TAC INET Environment I/NET Configuration Profile I/NET Seven Cause The I/O Server can be configured to auto shutdown whenever the I/NET Workstation application is closed. If this setting is used, the service will stop whenever I/NET Workstation is closed as well. Resolution Open the I/NET Configuration application. [Start>All Programs>I/NET>INET Config] Click on the Radial button so that I/O Server is maintained when no clients are present. Do NOT use the shutdown option when using I/NET as a service  

Issue Need to use the Emulated Hand Held Console software to setup a DPU, can it be downloaded? Product Line TAC INET Environment Inet Configuration tool Windows Cause Could not find the HHC software. Resolution The HHC software can be found on the Inet install CD under the folder "Support" > "HHC." It can also be downloaded from the Download Center here: TAC INET Seven Software Emulated Hand Held Console for 7798C - Firmware.zip

Issue Can the Personnel Manager be launched without using Continuum Explorer? Environment Continuum CyberStation Cause Require quick launch. Resolution Opening Personnel Manager without opening an existing personnel record. Create a button in the graphic to launch Personnel Manager. Edit the button in the Object Properties Action: Start Windows Program Windows Program: C:\Program Files\Continuum\Launch.exe Command Line Arguments: -C –SPersonnel –Offline “-FRoot” If you want to include a Owner folder location use the following arguments Command Line Arguments: -C –SPersonnel –Offline “-FRoot” “-Proot\FolderName” Result: This will launch Personnel Manager from the button on the graphic with no cardholder information configured.   Create a graphic and set it up to launch for the user upon login Create a button in the graphic to launch Personnel Manager. Edit the button in the Object Properties Action: Open object Object: Select a default cardholder to bring up in Personnel Manager Result: This will launch Personnel Manager from the button on the graphic to the cardholder selected.   Create a graphic button from the main menu that launches Personnel Manager to a specific cardholder If you have made any modification to the Main Continuum menu. Make a copy of the file before editing. i.e. the default is c:\program files\continuum\userprofile\continuum.mnu Right click the main page. Create a new hot spot or edit the Personnel hot spot according to instructions in the Configuration manual on Menu Pages. C:\Program Files\Continuum\Launch.exe -O -SPersonnel "-N\Cardholders\Test_Card" (Note:Cardholders is a folder) Result: Personnel Manager will open to that card   Launch the command line and use the Show command This is similar to option 2 except the button config is different In the Personnel button change the parameters to C:\Program Files\Continuum>cmdline Result: This will launch the Command line Type in Show Test_Card (some cardholder the user knows exists) Ex. R> show test_card Personnel Manager will open to that card   Change the Continuum Menu Personnel button that launches a listview to select a cardholder This is similar to option 2 except the button config is different Create a listview called Launch_PM In the listview place the following qualifier. (Name is like Prompt("Name is like", "*")) For the Personnel button configure the command and arguments lines to be: C:\Program Files\Continuum\Launch.exe -O -Slistview "-N\Launch_PM" Result: This will run the listview, the user can then type in the name of the personnel they know exists after the "*". The listview will find the user and then they can double click on the user in the listview to bring up Personnel Manager.  

Issue How to get BACnet B3xx controllers to know whether its parent BCX1 is online with its MSTP network or not. Product Line Andover Continuum Environment BACnet B3xx BCX1 MS/TP Network Cause There may need to be some action taken if communication is lost with the parent controller. Resolution Use the BACnet attribute of System_Status of the BCX1 with BACnet full path in the B3xxx's PE program. Make sure that you need to delay the program with enough waiting time, otherwise, it could make the MSTP congested. For example: Line Checking If BACnetDevices\MyBCX4040 System_Status = Operational then Goto Wait10Secs Line Wait10Secs If TS > 10 then Goto Checking Line E 'Do something to process the BCX offline situation in the b3 controller. Goto Wait10Secs

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 When Starting I/NET you get a blank error message with a Red Hand. Environment I/NET Remote Client Configuration Cause You are getting the Red Hand error because the active configuration is a Remote Client Configuration and the primary Server cannot be reached or the Network is down. The Red Hand may also appear when I/NET cannot connect to the currently configure SQL database Resolution Option 1 - Check that you are connected to the network. Ensure that the Server you are remoted into is started and online Option 2- Open I/NET Configuration Change the Active Profile to one that is Standalone

Issue Installing I/NET on a PC using MSDE and MSDE won't start. Product Line TAC INET Environment I/NET Version 2.40 and above Windows 7 MSDE Cause MSDE does not run on Windows 7. Resolution If the user has attempted this, more than likely the OS has corrupted SQL. There are a couple of things that can be done as described in Verify in Windows Registry all items are deleted after uninstall of I/NET Seven and MS SQL. However to return the PC to its original state the best bet would be to reinstall the OS, or a backup prior to the installation of I/NET.

Issue Controllers Comm port has previously been used for Infinet and it is now required to change its operation to Modbus or another X Driver. Environment All CX controllers that support X Drivers CX9200, CX9400, CX9900, CX9940, bCX1, NC2 Cause When connected to a controller whose comm port is in infinet mode the mode can not be changed. Resolution Delete any Infinet controllers under that comm port in the database Go to offline editing, change the mode from Infinet to Autoset or Printer, apply the change. Go online. Reload the controller. You can now select X Driver mode and select the required X Driver file.  

Issue I/A Series R2 / G3 graphics are not displayed when using web browser after the Java version is updated to Java 7 Update 51 or later. A dialog box indicates "Application Blocked - Application Blocked by Security Settings." Product Line TAC IA Series Environment I/A Series R2 I/A Series G3 Cause From Java 7 Update 51 and onwards, Java has enhanced the security model to make user system less vulnerable to the external exploits. The new version of Java does not allow users to run the applications that are not signed (Unsigned), Self signed (not signed by trusted authority) and the applications that are missing permission attributes. Risks involved in running each kind of applications Unsigned applications: An application without a certificate (i.e. unsigned apps), or missing application Name and Publisher information are blocked by default. Running this kind of application is potentially unsafe and present higher level of risk.    Self signed application (Certificate not from trusted authority) An application with self-signed certificate is blocked by default. Applications of this type present the highest level of risk because publisher is not identified and the application may be granted access to personal data on your computer. Jar file missing Permission Attribute Permissions Attribute verifies that the application requests the permission level that developer specified. If this attribute is not present, it might be possible for an attacker to exploit a user by re-deploying an application that is signed with original certificate and running the application at a different privilege level. Resolution As a workaround, the user can use Exception Site list feature to run the applications blocked by security settings. By adding the URL of the blocked application to the Exception Site list allows it to run with some warnings. Steps to Add URL to the Exception Site list: In control panel go to the Java Control Panel Click on the Security tab and verify that the Security Level is set to "High" or "Medium". Click on the Edit Site List button Enter your site details (This example http://www.SBO-Site.com) where www.SBO-Site.com is the address of the R2 Enterprise Server or UNC serving graphics, expressed either by name or by IP address. Click the Add in the Exception Site List window. Select continue Repeat the process, adding the addresses of all the site's Enterprise Servers and UNCs/JACEs. If this computer is used for browsing I/A Series G3 site graphics or StruxureWare for Building Operation site graphics, the addresses of those sites may be added as well.

Issue Lua script to convert a thermistor input on a SEC-TE to a temperature reading Product Line EcoStruxure Building Expert Environment SEC-TE MPM Cause When a temperature sensor is wired to a SEC-TE Smart Terminal controller, it can only be displayed as ohms. There is no option to use an AIC (Analogue Input Configuration) object to convert the reading. Resolution A Lua script is required to convert the input to a temperature value. 1. Import the Lua script At the top of the script in Section 1: 2. Edit the ME.AV17 input to the input used. 3. Edit the ME.AV48 to the Analogue Variable used to display the value. At the bottom of the script in Section 3: 3. Edit the AIC number to the AIC used to convert the value. Download here the Import File Download here the Txt File

Issue I/NET Seven elevator control configuration and setup. (Traditional versus Extended elevator control) Product Line TAC INET Environment I/NET Seven Extended elevator control: DPU Firmware 3.20 or above. (DPU7920 with 48K MIP or SCU1284) Cause There are two types of elevator control that you can implement within TAC I/NET: Traditional Elevator Control – Tradition elevator control allows each elevator to support up to 62 floors. This type of control has been used for as long as elevators have been supported within TAC I/NET. Extended Elevator Control – Extended elevator control does away with floor mapping and allows you to assign floors directly to tenants. Using this type of elevator control, each elevator can support up to 79 floors. Resolution Elevators The Elevator control function will work with the access control parameters and personnel schedules to control access to banks of elevators. Activating () the elevator option in the Door Extension editor will cause the DPU to process each reader transaction as though it were an entry into an elevator cab. Note: An elevator DPU will support only one door reader. Changing a Door from elevator to non-elevator, or vice versa will cause the DPU to purge its database. In addition to supplying the above parameters at the door (DPU) level, it will also be necessary to supply the DPI/MCI with the information required to associate an elevator cab with the discrete output points that enable the floor relays, and the discrete input points that monitor the button selection. There will be an elevator extension on each door point in the DPI/MCI that is assigned as an elevator. After adding the extension to the point, you must define the Elevator parameters such as floor selection time, floor designation description, button enable point, and button selection point. Elevator Control Schemes There are two types of elevator control that you can implement within I/NET Seven: Traditional Elevator Control – Tradition elevator control allows each elevator to support up to 62 floors. This type of control has been used for as long as elevators have been supported within I/NET. Extended Elevator Control – Extended elevator control does away with floor mapping and allows you to assign floors directly to tenants. Using this type of elevator control, each elevator can support up to 79 floors. You can use either type of control, or a combination of both, to implement elevators within your system. By allowing you to mix both types of control, I/NET gives you the ability to begin using extended elevator control without reconfiguring your traditional elevator control system. The following sections describe each elevator control type. Traditional Elevator Control Traditional elevator control allows each elevator to support up to 62 floors. To implement this type of control, you assign the elevator door point to one or more tenants. You then create floor maps that associate floors with personnel schedules (see “Defining Floor Maps”, below). After performing these tasks, any individual (or group) assigned to the elevator can gain access to the floors that are associated with their personnel schedule Assigning the Elevator to Tenants Traditional elevator control requires you to assign the elevator to one or more tenants. Until you perform this task, the Floors button in the Elevator editor will not be available (i.e., it remains grey). Defining Floor Maps Floor maps are only necessary when configuring your I/NET system for traditional elevator control. Floor maps determine which floors are enabled during each schedule that a tenant defines for the elevator. For example: Tenant 1 has a personnel schedule named “24 Hour” defined for the elevator. This schedule provides 24-hour access, seven days a week. The elevator’s floor map associates the floor enable points for floors 1 and 2 with Tenant 1’s “24 Hour” schedule. This allows Tenant 1 individuals using the “24 Hour” schedule to select floor 1 or floor 2 at any time. Use the Floors button in the Elevator editor to create floor maps as follows: Choose a tenant. Select a schedule from up to 31 personnel schedules defined for the elevator. Select an entry from up to seven access intervals defined for the schedule. Assign floor enable points to the schedule’s access interval. Floor enable points cause the elevator buttons for those floors to be enabled for selection by the key/card holder. Up to 62 floor enable points can be assigned to each access interval. Any floor enable points beyond 62 are unavailable when using traditional elevator control. These higher floor enable points are only available for use with extended elevator control, as described below. Note: Extended elevator control is only available with the 7920 48k DPU. Repeat these steps as necessary to create floor maps for each of up to 31 personnel schedules assigned to the elevator by a tenant. Extended Elevator Control I/NET Seven now offers an alternative to the traditional elevator control just described. Enhancements to the I/NET system support up to 79 floors per elevator. Instead of assigning the elevator door point to the tenant, you can implement extended elevator control by assigning floors to the tenant. The DI/DO pairs that you add to an elevator from the Elevator editor are listed in the Tenant editor, much like normal door points. Select the floors that you wish to assign to the tenant. Implementing Elevator Control Note: Extended elevator control is only available with the 7920 48k DPU. Adding an elevator extension to the door point provides access to elevator-related features and editors within I/NET and allows floors to be assigned. Each floor assigned to an elevator must have an associated DO and DI point. The DO point enables the elevator button for the specific floor. The DI point provides feedback indicating whether the floor button has been selected. Preliminary Requirements Before defining an elevator, you must do the following: Define a door point as an elevator in the Door Extensions editor. Use the Resident I/O Points editor to define a floor enable point (DO) and a floor selection point (DI) for each floor that will be assigned to an elevator. Use the Personnel Schedules editor to define up to 31 schedules for the selected elevator door point. Adding an Elevator Extension Use the following procedure to add an elevator extension: Select Edit Controller Elevators from the main menu. The system displays the Resident I/O Points Editor. This screen lists the available door (elevator) points. Choose a point that does not have a Y in the EL column and select the Add button. The system displays the Elevators window. Enter a Floor selection time (sec) (1 to 255). This is the amount of time in seconds that the key/card user has to make a selection from the floor buttons in the elevator cab. The default is 5. Select Add. The system displays the Elevators - Floor Parameters window. This window allows you to define the floor index attached to this elevator extension. Enter the Floor index number (1 to 62). This is the line number in the list. Enter the Floor designation (up to two characters). This identifies the floor. For example, the first level of a basement could be represented as B1. For each elevator floor extension assigned to a point in the DPI/MCI, there must be an associated DO and DI point attached to the elevator extension. This association of DO and DI points produces closed-loop feedback allowing the controller to identify an elevator floor selection with each successful key/card reader access. In the Button enable field to choose a point from the drop-down list of all possible discrete output points in the controller  In the Button selection field, choose a point from the list of all possible discrete input points in the controller. Select OK. The system returns to the Elevators window. How you proceed from this point will depend upon the type of elevator control you are implementing. Use the appropriate steps below: Traditional Elevator Control: From the Elevators window, select Floors. The system displays the Tenant Selection window. Choose a tenant from the list and select the Select button. The system displays the Elevators - Floor Schedules window. Choose a schedule from the list and select the Select button. The system displays the Elevators - Access Intervals window. Choose an access interval from the list and select the Select button. The system displays the Elevators - Floor Map editor. Choose the DO points which enable the floor selection buttons for the appropriate floors. Points marked with "[X]" will enable their respective floor selection button in the elevator cab. When you have finished choosing the appropriate DO points, select OK. The system returns to the Elevators - Access Intervals window. You may continue assigning floors to access intervals, or you may back out of the elevator functions by selecting Close at each window. Extended Elevator Control (See also article Extended Elevator control (Step by step instructions) ) From the Tenant Editor, assign floors (i.e., door enable points) to the tenant. Assign floors to individuals and/or groups as necessary.

Issue User Definable Buttons and Tools Product Line TAC INET Environment I/NET Seven site Cause How to make user-defined buttons that will allow the user to set up shortcuts for reports and events Resolution Configuring User Buttons I/NET now has the ability to add a User-defined button that will allow the user to set up shortcuts to reports and events. I/NET displays this editor when you select Tools Define Buttons from the main menu. Use this editor to create up to 16 user-defined buttons. Configure user buttons as follows: Highlight one of the 16 user button entries from the list and select Modify. The system displays the User Tool Configuration editor. If the desired tool has already been configured, highlight it in the list and select OK. The User Tool Configuration editor closes and the selected tool is added to the user button. Skip the following step and proceed with step 4. If the desired tool has not already been configured, configure the user tool now (refer to User Tool Configuration). Then highlight the user tool and select OK. The User Tool Configuration editor closes and the selected tool is added to the user button. Select OK to accept these settings. The button is now available when you select Tools from the main menu. Configuring User Tools I/NET displays this editor when you select Tools Define Buttons from the main menu, or when you highlight a button entry in the User Button Configuration editor and select Modify. Use this editor to define tools that you can assign to any of 16 user-defined buttons, or that you can activate from live graphic pages. Two kinds of tools are available: Event – Use this tool to execute an event sequence defined in a controller. Shortcut – Use this tool to launch another application, open a file, visit a website, etc. Options The following options are available in the User Tool Configuration editor: Add – Use this option to create a new tool. The system displays the User Tool Type dialog. Delete – Delete a tool by choosing a tool from the list and selecting Delete. The system prompts you to confirm the delete request. Select Yes to delete the selected tool or select No to cancel the Delete request. Modify – Use this option to modify an existing tool. Highlight a tool in the list and select Modify. The system displays the User Tool Type dialog. Copy – Use this option to create a new tool by copying the selected tool. The system displays the User Tool Type dialog.