Building Automation Knowledge Base

Issue Difference found between 2 technical documents regarding the Universal Inputs of the b3810 and b3814 controllers. In the Controller Data Sheet the Universal Inputs are indicated 0-10VDC, 12 bit.  In the Family Controllers Brochure it's indicated Universal Inputs 0-5V, 10bit.  Which document is correct?   Environment BACnet b3810 and b3814 controllers Cause An older revision of the Family Controllers Brochure contains inaccurate / outdated information. Resolution The Universal Inputs for the b3810 and b3814 controllers are 12 bit,  0-10VDC.  The next revision of the BACnet Family of Controllers document will contain the correct voltage. Controllers available with 12 bit A/D Converters 0-10VDC are: i2/b3920 i2/b3810 i2/b3814 Other i2/b3 controller inputs have 10 bit A/D converters.

Issue Much of the literature being used for R2 and G3 reference the Niagara Jace model numbers.  Is there a cross reference list available to cross Jace model numbers to UNC model numbers? Environment Niagara R2 and G3 Cause The provided literature reference Jace model numbers. Resolution A cross of UNC to Jace controllers are as follow:  UNC-410-1                 JACE-403 UNC-500-1                 JACE-501 UNC-500-2                 JACE-502 UNC-510-1                 JACE-511 UNC-510-2                 JACE-512 UNC-520-2                 JACE-545 UNC-600-2                 JACE-NP UNC-610-2                 JACE-NX  ENC-410-1                 JACE-403-AX ENC-520-2                 JACE-545-AX Tridium reference to Ax is Schneider Electric’s G3.  

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 running the stored procedure sp_changedbowner to change the dbowner to "andover97", the following error message is received: "The proposed new database owner is already a user or aliased in the database". Product Line Andover Continuum Environment Continuum Microsoft SQL Server 2000 Microsoft SQL Server 2005 Microsoft SQL Server 2008 (Keywords: drop user ) Cause The Andover97 user already has access to the database through an existing alias or security account within the database. This can occur when the DB is not restored properly to the SQL server. The database may have been detached and then attached again, which is not the preferred method of restoring a ContinuumDB. Resolution Under the ContinuumDB there is a "security" and then "users" folder. Check to see if the Andover97 user is in this folder. Continuum does not put this user in this folder. If it is there, then it will need to be dropped from the database before trying to change the dbowner. Do the following: Do a complete full backup of your ContinuumDB. Run the following SQL script to drop the user from the ContinuumDB. USE [ContinuumDB] GO DROP USER [Andover97] GO Re-run the stored procedure to change the db owner below. USE [ContinuumDB] GO sp_changedbowner 'andover97' GO To minimize the chance of this occurring again, the correct procedure for moving or restoring a Continuum database is to do the following: Create a new ContinuumDB with Continuum's Database Initialization. This creates the DB, SQL jobs, stored procedures, adds Andover97 as an admin and a lot of behind the scenes security settings. Restore a previous backup over top of the ContinuumDB created in step 1. Change the db owner with the above query using the sp_changedbowner stored procedure. Re-initialize the Cyberstation into the Database using Continuum's Database Initialization.

Issue A program is entered in a point's alarm configuration but the program does not run when the point goes into alarm. Environment CyberStation All CXs All i2 and b3 devices Cause Event notification object not configured to run program. Resolution In the Event Notification's actions list, select the 'Run Program' action.

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 for assistance. Issue ASC stopped communicating Continuous Lost/Restore Reset the memory in an ASC Controller Product Line TAC INET Environment I/NET SubLAN Controllers All ASC Controllers Cause When the MR-AHU resides on a communication sub-LAN, it is susceptible to communication errors from external sources. These communication errors could result in corruption of the ASC's NOVRAM. When this occurs, the ASC will stop communicating, or will cause continuous Lost/Restore messages. For this reason, the ASC is provided with a means of clearing its NOVRAM. Caution: Clearing the MR-AHU memory causes the binary instruction set for the controller to be deleted. In order to reload the binary instruction set, you must have a TAC I/NET host with the appropriate UPD files, and the ASC Controller must be communicating through an interface controller (MRI, MCI, or I/SITE LAN). Resolution Prior to clearing NOVRAM of the ASC and you are using MR-VAV's and they have already been balanced, VAV parameters must be recorded (screenshot may be the quickest method). Follow the following steps to RESET the device  Remove power from the ASC. Set DIP switches 6 through 12 to the "On" position and restore power. Remove power again. Set DIP switches 6 through 12 to the "Off" position and restore power. Remove power again and reset the switches to their normal configuration. Normal communication should be restored to the ASC. If not, then the problem lies elsewhere. Once communication is restored, perform an "ASC Update" from the TAC I/NET host to restore the NOVRAM image to the ASC. Refer to the TAC I/NET System Operator Guide for ASC Update instructions.

Issue What is the maximum number of personnel records (cardholders) in an ACX controller? Environment Continuum ACX controller Cause Limitations within the ACX controller. Resolution The ACX 57XX series controllers can service up to 8 areas, and can hold a maximum of 480,000 personnel records. 

Issue List view configured with qualifier Value = NotSet yet shows objects with a value of 0 (zero) as well. Environment All CXs All i2s All b3s Cause In Continuum NotSet evaluates to zero Resolution There is no way in Continuum to show only the objects that have a value of NotSet, in Continuum NotSet and zero are the same value so a list view with a qualifier 'Value = NotSet' will show objects with value set to zero as well as value set to NotSet.

Issue In a Vista classic network, right click and edit a Xenta 121. Click the load button to load a .zbc file stored on the hard drive and there is no option but to cancel. It will not take a load. Environment Xenta 121 ZBuilder Vista Classic Network Cause Because the Xenta 121 type is stored in the Vista database at the time of the creation of the node, it will not allow a fan coil (FC) file to be loaded into a heat pump (HP) or vice versa. Resolution Right-click on the 121 Go to Properties > XIF File Look at the source file listed and make sure it contains either HP or FC and that matches the actual controller. Alternatively: Right-click on the 121 and select Edit Click on Load Unavailable templates will be grayed out -- see if it is the FC or the HP templates that are grayed out. Make sure the template .zbc that you are browsing to on the hard drive is set to the same type as the controller that is defined. If necessary, delete the existing controller and add it back as a different type.

Issue Can Continuum run on a Windows Server 2008 R2 system? Environment Continuum Cyberstation and webClient Cause Installing Continuum software on a Windows Server 2008 R2 operating system. Resolution Windows Server 2008 and Windows Server 2008 R2 is supported in Continuum version 1.91 and later.  It is supported in 32-bit and 64-bit environments only when used for a LAN system database server (neither Cyberstation nor webClient can be installed on the PC).  In addition, only the use of MS SQL 2008 is supported. 

Issue Operation of Xenta 121-HP Flow Feedback Error as sensed via hardwired flow input or nviSourceFlow network input. Environment Xenta 121-HP ZBuilder Cause For a heat pump, nvoSystemStatus bit 12 is set if an expected flow is missing. For example, when the isolation valve is open there should be a flow feedback, but when it is closed or opening, no signal is expected. Resolution Flow feedback error will disable cooling and heating outputs. There is no need to define an exception mode in ZBuilder in order to enable this safety override.

Issue How to configure an alarm to see when controllers go offline. Environment Continuum Continuum Controllers Cause Want to see an alarm when controllers go offline / online. Resolution There is a default EventEnrollment already created that does this. To setup controller offline alarms, do the following: Go to the "Templates" folder in Continuum Explorer where a number of default EventNotifications are found. Open the "ControllerStatus" EventNotification and go to the Delivery tab. Add in the Workstations that where this alarm is to be sent too. Now any time a controller goes offline or comes back online, an alarm entry will be received at the Workstation entered in step 2. The other EventNotifications in this folder can be used to provide alarms on the subnet controllers status (InfinetStatus), IOU modules (IOModuleStatus), etc... ***Important: CyberStations detect controller’s offline status via a mechanism that periodically probes the controllers for their communication statuses; the default period for the probe is 60 seconds. If data is consistently being passed then no probe goes out. A Probe will go out if the controller has not heard from the other controller after a minute and no data has been passed. If an ACK is not received then it will try 3 more times with a 5 second delay after each retry. If it does not get a response after the 3rd retry then it will mark the controller offline and register a node failure alarm. If a controller goes offline for a short period of time (60 seconds or less) it is possible that not all recipient CyberStations will see the controller offline. If the CyberStation designated as the logging CyberStation for the ‘ControllerStatus’ alarm misses the offline condition the alarm WILL NOT be logged in the database.  

Issue How to Integrate GSM/SMS functionality to TAC Vista using SysMan SMS Server Environment TAC Vista SysMan Server Cause What are the GSM modems can support to integrate with TAC Vista. Where to find the Installation/Product manuals.  How to Integrate SysMan SMS Server with TAC Vista Resolution For supporting modems/Documents/Integration details go to http://www.sysman.no/ Part Numbers: 1. SysManSMS ALERT SERVER: 900800600 2. SysManSMS GSM Modem: 900800610   In the UK when ordering please use the below part numbers. 1. SysManSMS ALERT SERVER: 802000 2. SysManSMS GSM Modem: 100002

Issue Is it possible to add a new font in the TGML graphics editor Environment Tac Vista 5.1.X TGML editor Graphics Editor TGML 1.1.X Cause There are a number of reasons why a customer would like a particular font. For example, the customer has a corporate font that they use on their existing website and they would like to this to be used in their TGML graphics. Resolution To add a new font, just add the .ttf file to C:\Windows\Fonts (or the equivalent in your language) and restart TGML editor. Please be aware that the font must support regular (non bold) line weight, otherwise it will not be read by TGML editor at startup.  

Issue When Continuum Starts after log on the page takes a long time to open. It seems the process is taking longer than expected. Environment Continuum 1.81 Windows XP sp2 Cause Use an Antivirus to scan the system. If viruses are detected, they can cause symptoms like this. Resolution Remove the detected viruses reported when AntiVirus scan was performed. While it is suggested to install Continuum with Admin privileges and also AntiVirus turned off, AntiVirus should be turned on when installation is complete. Any PC on a network, internet or USB and CD access is vulnerable to viruses.

Issue Where can older versions of Cyberstation software be downloaded from? Product Line Andover Continuum Environment CyberStation Cause Older version of Cyberstation software archived to FTP site. Resolution Log on to FTP server ftp://ftp.andovercontrols.com/ Customer UserName: andoverrep Password : andoverrep   Older CyberStation versions are found in the CyberStation_Revisions directory.

Issue Will Signal XP software run on Windows 7 in the XP mode? Environment Signal XP, Windows 7 Cause Will Signal XP software run on Windows 7 in the XP mode? Resolution SIGNAL XP software has not been tested or validated to be compatible with the Microsoft Windows 7 operating system or running in either Windows 7 XP or Virtual XP mode. Since the product is obsolete, no further engineering work will be done with the product.

Issue Downloading a save for a 7793 MCI to a 7798 MCI, what needs to be done to accomplish this task. Environment All versions of I/Net that uses both the 7793 MCI and 7798 MCI. Cause System running multiple controllers and wants to switch out one for another for functional purposes. Resolution Note: This only works if you are using the first address points of the 7793 MCI. Start I/NET and go to the Offline Editor Connect to the 7793 MCI and select copy Create the file and choose the 7798 MCI Once completed, connect to the 7798 MCI and go to Resident I/O point. Verify that the point addresses are correct Make necessary changes to names, add, delete, modify accordingly Once completed, save and exit. Connect to the 7798 MCI and select Software Restore, then download the new save file to the controller.

Issue How does the Xenta 121 indicate that a fan feedback failure condition has occurred? Environment Xenta 121-HP Xenta 121-FC Cause The fan failure signal could be used to trigger another sequence of events, to annunciate an alarm in the Workstation, or to send an email to the on-call mechanic. Resolution The output SNVT, nvoSystemStatus bit 15, represents a fan failure condition.

Issue In Vista 5.1, TGML graphics bindings can be bound using a multi-bind .[OBJECT] bindings. Dragging and dropping a single object can then automatically bind all other defined signals, for example. But there is a limitation of two network levels. Environment Vista 5.1 Workstation TGML Graphics Bindings window Cause Controllers with standard naming (especially application specific controllers with pre-defined naming) can be bound to graphics more quickly and efficiently with the use of multi-binding. There are limitations to what can be multi-bound simultaneously. Resolution Multi-binds can bind all defined signals for up to two levels of their database structure. For example: RoomTemperature.[OBJECT] can be used to bind: RoomTemperature.PV and RoomTemperature.OVR You can travel up one more level, though to get even more signals at once: SUMMARY.[OBJECT] can be used to bind: SUMMARY.RoomTemperature.PV and SUMMARY.RoomTemperature.OVR and SUMMARY.RoomSetpoint.PV You cannot travel up any more levels, so you could not do: LonworksNetwork.[OBJECT] in order to bind all signals in a network at once.  

Issue Attempts to login are unsuccessful and device reports that logins are blocked. Environment Xenta Server Xenta 511, 527, 555, 701, 711, 721, 731, 913 Cause The Xenta Server tracks attempts to log in by recording the IP address and Username of the login attempt. After 5 login attempts it will block any attempts to login to with that username and IP address for 10 minutes. Resolution Use a different user account on the Xenta Server to login and perform the necessary work or wait 10 minutes for the lockout to expire. If the lockout is continuing after 10 minutes then ensure that if the Xenta Server is in a Vista database that it is not running and trying to communicate to the Xenta Server with an incorrect username and password. Any changes to the root user password must also be changed in the Vista database to avoid perpetual blocking of login attempts on that computer and IP address.