Building Automation Knowledge Base

Issue Doors need to be released when a fire alarm is triggered. Environment Continuum Access Control Doors on ACX57xx, AC1 range, CX9702, ACX7xx Cause Automatic door release is required. Resolution Doors can be released either electrically by releasing the power to the doors directly from a Fire system or other 3rd party system output. Alternatively it can be done in software, Use the "Door Force Unlock Schedule" in the Door options tab to link to an Input point or Numeric value that signifies the doors should be released. When this point turns on the door will be released. Multiple doors can be linked to the same point if required. No Schedules or Plain English programming is required to achieve this functionality. Note: Always ensure any fire alarm control is in accordance with local regulations and legal requirements.

Issue Trying to create an Infinity Schedule under ACX5720, when saving the object an error window comes up. The error window does not contain an error message, only the word ERROR and an OK button. The error happens even if creating the object in offline edit mode. No problem creating the object under a different controller. Environment CyberStation Cause Corruption in database. Resolution Dump the controller to an ASCII file then delete the controller. Import the dump file into the Continuum network to re-create the controller. Deleting and re-creating the controller clears up the corruption in the particular controller object in the SQL database.

Warning Hazard of Electric Shock: Remove all power from all devices before removing any covers or doors of the system. Disconnect power at the device and at the power source.  Issue The C20 series cameras have the BNC and neutral ground for 24VAC tied to the same ground plane. This can cause a power supply short if the ground and hot are connected out of phase at the power supply. This can also cause ground loop bars in the video if connected to a supply that is not on the same ground plane as the camera. This also causes problems with some third party UTP brands connections. Product Line Field Devices, Pelco Environment C20 cameras connected  to common power supply and/or ground planes that are different. Cause The 24 VAC on the C20 cameras are connected to a common ground plane and the BNC connection is grounded to the same ground plane Resolution When installing the C20 cameras use single isolated transformers for each camera, or make sure the wiring is tied with the same phase. This is done by making sure the same wire leg of each camera is connected to the same wire side of the transformer on the power supply. Also when connecting to the power supply use a meter to test for voltage potential differences. Check that the cameras will work with the third party UTP brand you are using

Issue Explain the difference between the I/A Series R2 timezone settings like CST vs CST6CDT, or PST vs PST8PDT and the Americas/City time zones. Each of the following examples shows the three different ways that the four American time zones can be specified: America/New York or EST or EST5EDT America/Chicago or CST or CST6CDT America/Denver or MST or MST7MDT America/Los_Angeles or PST or PST8PDT   Environment I/A Series R2 UNCs and Enterprise Servers Cause Various ways to specify the location in terms of the time zone and the daylight savings start/end dates. Resolution Each of the following three entries specify the same part of the United States and the usual daylight savings time dates (2:00 AM on the second Sunday of March through 2:00 AM on the first Sunday of November) America/New York or EST or EST5EDT America/Chicago or CST or CST6CDT America/Denver or MST or MST7MDT America/Los_Angeles or PST or PST8PDT For parts of the Unites States that do not observe daylight savings time or have different daylight savings time rules, specify the appropriate "America/City" selection, for example: America/Indianapolis for those parts of the state of Indiana that are in the Eastern Time Zone. America/Phoenix is used for the entire state of Arizona, which does not observe any daylight savings time. To specify a time zone where no daylight savings time is observed, you would select the appropriate entry from the entries that begin with Etc/GMT+xx or Etc/GMT-xx where xx specifies the hours from GMT or UTC (Coordinated Universal Time).

Issue WAV file is attached to Alarm Enrollment (Feedback page) but sound file does not play when point goes into alarm. Environment Feedback Audio Sound file Alarm Enrollment Event Notification Cause Configuration was not completed. Resolution Whether the audio file is attached to the Alarm Enrollment or to the Event Notification, the Play Audio checkbox must be selected on the associated Event Enrollments Action page. Note: A sound file can configured to play when an alarm is received by Cyberstation either by attaching the audio file to the Alarm Enrollments Feedback page or by attaching the audio file to the Event Notification Feedback page.  If an audio file is attached to both the Alarm Enrollment and its associated Event Notification, the Alarm Enrollment audio files take precedence.

Issue Are spare parts available for the Xenta series base plates / terminal parts / plug in terminal blocks? Environment 007309010 007309020 007309140 Cause Sometimes the locking pin in the base plate breaks and needs to be replaced. Resolution No spare parts are available. The complete parts needs to be purchased. Part no 007309010 is for Xenta 300 series controllers Part no 007309020 is for Xenta 400/500/700/900 series controllers, and I/O modules. Part no 007309140 is for Xenta 100 series controllers.

Issue Does the part number for Modbus RS-485 (IA-DRV-MOD) have to be purchased four times in order to support all four available RS-485 ports? Environment Niagara R2 all versions Cause Job site will integrate to four different vendor products using Modbus to one UNC-520. Resolution A UNC-520 supports up to four separate Modbus Async Networks each using a separate ModbusAsyncService. Only one part number has to be ordered for the UNC (part # IA-DRV-MOD).

Issue The ability to add a second card is available in webclient, but there is no where to add the second card Environment Windows XP Windows Vista Windows 7 Windows Server 2003 Windows Server 2008 Cause Steps are needed to configure dual credentials to show in webclient, but those steps have not been completed. Resolution Steps to configure dual credential access in webclient: 1. Right click on Continuum icon in the system tray and select Allowed Credentials and select 'Credential1And2' Note: Say yes to enable on the controllers and distribute 2. Open Personnel Manager, click configure, click the right arrow to add ‘Card#2’ and ‘Card2 Type’, click Ok 3. Once that is done, go back into webclient and you will now see an additional tab added called ‘Credential2’

Issue Creating an InfinityController fails with error  "The object type specified is invalid" Environment CyberStation Cause CyberStation with duplicate NetworkId in the Continuum SQL database. Resolution From the Continuum Explorer delete the offending CyberStation object then delete the folder associated with the CyberStation.

Issue Can I run multiple connections with Remote Desktop Services or Microsoft Terminal Server Services to allow more simultaneous sessions of I/A Series G3 Workbench on a computer? Environment I/A Series G3 Enterprise Network Server, ENS, Workbench Cause This occurs when a computer with a single Enterprise Server is configured with Remote Desktop or Terminal Server Services to allow multiple users to have concurrent sessions of the Workbench running simultaneously. Resolution The Tridium EULA (End User License Agreement) does not permit Workbench concurrent sessions. Per the EULA, each session should originate from a separately purchased and licensed version of Workbench.

Issue Is it possible to open a time schedule from a OGC graphic when the graphic is opened from Webstation? Environment TAC Vista 5.1.x  Cause In older versions of TAC Vista a "Command Point" object could be used to link to a time schedule and it worked fine in booth Webstation and Workstation.  And that still works fine in Workstation but to get it to work in later versions(5.1.x) a "Dynamic Value" object must be used in the graphic editor to get it to work in Webstation. Resolution Use a "Dynamic value" object in the OGC editor when linking to a time schedule to get it to work in TAC Webstation.

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 Trend logs are not being saved to SQL after upgrading the SQL database. There are no error messages and Vista can read old (pre upgrade) values from the taclogdata database. The insertlogvalues keeps growing. Product Line TAC Vista Environment Vista 5.1.X SQL 2005 or 2008 server with a database that has been upgraded to layout 2 (the new schema used from version 5.1.7). Cause The database schema is out of date. The database schema is a blueprint of how a database will be constructed. Resolution Shut down Vista. Go to services and stop the TAC DSS writer service. Right-click on My Computer (Computer in Win 7 and Win Server 2008) and select manage. Locate services in the console that opens up. Locate the TAC DSS Writer service, select and then click on stop. This service is responsible for writing events and trend log data to the SQL database. Update the database schema. Open Vista sever setup and locate the SQL server tab. Click on the Custom radio button (if not already selected) and then change the name (e.g. add "_1" to the end of the current name) of the database in the SQL Server Name field. Click on Apply, OK and  then Yes to create the new database. Once complete, change the name of the database back to the original name (or click on the Typical radio button if using default settings) and click on Apply. A message will appear "Log database found but needs to be reconfigured. Reconfigure Log database?". Click on Yes. The database schema should now be updated. Right-click on My Computer (Computer in Win 7 and Win Server 2008) and select manage. Locate services in the console that opens up. Locate the TAC DSS Writer service, select and then click on Start. This service is responsible for writing events and trend log data to the SQL database. Check to see that the logs are now being written to the log database. It may take some time to process the backlog.

Issue Will there be any problems wiring two HID iClass RP40 readers to one reader channel?  Environment ACX57xx, AC-1 Cause Need two readers on a vehicle entrance at different heights Resolution Tested (2) HID RK40 (iClass with keypad). The RP40 uses less power but should be very similar. Not recommended to power the two readers from the same reader input unless you are sure the reader input can handle the combined peak mA rating of the two readers. ACX5720 - worked fine. The RK40s were powered with different reader channels and then just doubled up the 1-DATA, 0-CLK and LED1 terminals on the ACX with the DATA1, DATA0 and Green LED leads from the readers. AC1 - worked fine. The AC-1 terminals are small so a single piece of wire was used off the DATA/1, CLK/0, and LED terminals of the AC-1 and landed on a terminal block with DATA1, DATA0 and Green LED leads from the readers. The RK40s were powered with an external power supply.  

Issue Get error message, "taclogdata is not a valid TAC Vista logdatabase" at installation of TAC Vista. Environment TAC Vista 5.1.0 and later versions. Cause When installing Vista and using a custom SQL installation a SQL database is specified. If this SQL database is created manually and not by Vista the database will not be recognized as a valid TAC Vista log database.   Resolution Let TAC Vista create the SQL database at the installation or use the Vista server setup to create a SQL database. 

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 When many trend logs are linked to the same time object for emailing via a Receiver Group, some of the trend logs may not be sent. Environment Xenta Server Xenta 511, 527, 555, 701, 711, 721, 731, 913 Cause The Xenta Server cannot send more than approx. 50-60 simultaneous emails before some are lost.  The limit appears to be dependent on the size of attached trend logs and the number of addresses in the Receiver Group list. Resolution For a single email address, split the trend logs into groups of no more than 40.  Link the logs in each group to a different time object and stagger the times at which they are sent.  If the Receiver Group definition contains multiple email addresses, reduce the number of trend logs in each group accordingly.

Issue Prior to XBuilder 5.1.1, it was not possible to change the type of an Xenta Server in an XBuilder project once it had been created.  Sometimes there is a need to move the project to a different type of Xenta Server without losing all the links and bindings within the project. Environment Xenta Server XBuilder 5.1.0 or earlier Xenta 511, 527, 555, 701, 711, 721, 731, 913 Cause In XBuilder 5.1.0 or earlier, it is not possible to edit the Xenta Server type in the network pane of the XBuilder project Resolution Upgrading to Vista/XBuilder 5.1.1 or later will allow you to easily change the device type directly from XBuilder.  Note that this must be done from an XBuilder project that is saved to the computer. If the project is in a Vista database start by opening the XBuilder project, clicking on File > Save as and then save it to the computer. Then, close XBuilder, reopen XBuilder and open up the saved copy of the XBuilder project from the PC. In the XBuilder Project menu select 'Change Target type...'.  Choose your preferred target device from the drop-down list.   If it is not possible to upgrade, the following instructions allow an XBuilder project to be transferred to a different type of Xenta Server without losing graphic bindings or bindings between objects on the System pane and the Network pane.  The one proviso is that the target Xenta Server's hardware must be able to support any network defined in the source project and have the same or better Menta and User graphic capabilities.   There are many different combinations of Server types and BMS platforms that these instructions could apply to in general.   The example given here transfers an Xenta 555 project to an Xenta 731.  The Xenta 555 has a Lonworks network and a Modbus network and is part of a Vista database.   Creating the Xenta 731 in the Vista database: Open the Vista database containing the Xenta 555 project. Right-click on the 555 and select Edit from the dropdown menu. The XBuilder project opens.  Keep this open for the following steps. In the Vista database create a new Xenta 731.  The name is not important but it should be similar but not identical to the 555 it will replace. Transferring the Lonworks network to the Xenta 731: In Vista, drag and drop the LON network from the 555 to the 731. Right-click on the 731 and select Edit from the dropdown menu. The 731 project opens in a new instance of XBuilder.  Rename the default folder in the system pane to the same name as the top level folder in the 555 project. In the 731 project right-click on the LON object in the Network pane.  Select 'Refresh network from TAC Vista'. Transferring the Modbus network to the Xenta 731: In the 555 project, right-click a Modbus device and select 'Edit Device template' When the device editor opens, select File | Save as.. Save the file in the default location with the default name. Repeat steps 2 to 3 for all Modbus devices in the network. In the 731 project recreate the Modbus network using the templates just saved.     Transferring the System objects to the Xenta 731: In the 555 project, right-click an object below the top level folder and select 'Copy'. Move focus to the 731 project, right-click on the top level folder and select 'Paste'. Repeat steps 1 and 2 for each object and folder below the top level in the 555 project.  Selecting a folder also selects all the objects and folders beneath it.  Although it is possible to copy the top level folder in the 555 project, it is not possible to paste it into the 731 project. Graphics bindings are retained and the reference paths are automatically updated with the new network tree i.e. 'TAC_Xenta_555' is replaced with 'TAC_Xenta_731'. Some object bindings will be broken e.g. Time objects.  These must be rebound manually. When all objects have been copied across and rebound if necessary, close the 555 project. Deleting the Xenta 555 and downloading the project to the Xenta 731: In the Vista database, delete the Xenta 555. Generate the 731 project.  There will be a warning message offering to copy the original TGML files to the new default location.  Select 'Yes'. The 731 project should now generate without errors. Download the project to the Xenta 731.   If the 555 only contains a Modbus network, a similar methodology will also work with standalone 555 and 731 projects.  

Issue Do the I/ A Series (MNL- or MNB-) controllers support more than one S-Link sensor? Environment I/A Series controllers: MNL-50, MNL-100, MNL-200, MNL-V1, MNL-V2, MNL-V3, MNL-800, MNB-V2, MNB-300, MNB-1000 S-Link sensors; MN-S1, MN-S1HT, MN-S2, MN-S2HT, MN-S3, MN-S3HT, MN-S4, MN-S4HT, MN-S5, MN-S5HT Cause Want to connect 2 S-LINK sensors to an I/A series controller Resolution No, only one S-Link sensor per controller is supported. Currently, there are no plans to add the capability of supporting a second sensor.

Issue Do we have any fast (10 sec) damper actuator in our portfolio? Environment Damper actuator Cause In some application, a fast actuator is requested. Resolution Unfortunately, we do not cover this type of applications. An actuator of this type will have to be sourced locally. Belimo has a line of very fast-running actuators: http://www.belimo.eu/CH/EN/Product/Actuators/SuperFast.cfm?TopCatNr=0206

Issue If not considering the design of the sensor housing, can a duct sensor function also in a room application? Environment Duct style sensors Cause A specific application is requesting this type of setup Resolution In general it is possible to use these sensors also for room applications. Maybe the time constant will be a little bit higher because of lower velocity which in room applications usually is irrelevant. For the SHD it might be that the sinter filter can absorb some radiant heat (if there is any).

Issue A Niagara R2 UNC will not keep time accurately.  The time doesn't just drift a few seconds.  It is jumping around by hours.  Trying to change the time in the Admin Tool does not work.  The following error appears in the standard output window on startup of the UNC:  ERROR: Cannot load /tffs/rel//nre/lib/timezones.txt ---------- Station Starting:   THU FEB 28 14:41:44 2013 ---------- ERROR: Cannot load /tffs/rel//nre/lib/timezones.txt   java.lang.NumberFormatException Tridium Niagara Station, r2.301.532.v1 [B_Floor_1] MESSAGE: ErrorLogService installed [/B_Floor_1/services/ErrorLogService] GcmCommService Revision 2.304.532.v1 Start service: ControlEngineService [19] ControlEngineService Start service: UiEngineService [20] UiEngineService Start service: NotificationService [2] NotificationService Start service: LogService [21] LogService Start service: AuditLogService [22] AuditLogService Start service: ErrorLogService [23] ErrorLogService Start service: TimeSyncService [26] TimeSyncService Start service: LonWorksService [28] LonWorksService Opened lon / LON1 >>> Lon Driver opened! Start service: GcmCommService [24] GcmCommService Comm Ports:   COM1 (serial)   COM2 (serial)   COM3 (serial)   COM4 (serial)   COM5 (serial)   COM6 (serial) Start service: VserialService [25] VserialService MESSAGE: Station started successfully. (HTTP port=80) [/B_Floor_1] Environment Niagara R2 Cause Corrupt timezones.txt file Resolution The timezones.txt file is corrupt.  Copy and paste the contents of this file from a functional UNC and paste it into the problem UNC. The timezones file can be accessed via the Admin Tool dropdown menu.