Building Automation Knowledge Base

Issue Is the MNL-110 or MNL-130 controller available in any profile other than Fan Coil profile (F3)? Environment MNL controllers (MNL-110, MNL-130) Cause The MNL-110 and MNL-130 controllers are only available with the Fan Coil profile (F3).  The profiles cannot be modified in the field. Resolution Review alternative hardware platforms (MNL-50, -100, -150, or -200) in the following profiles ... Rooftop profile (R3) Fan Coil profile (F3) Heat Pump profile (H3) Satellite profile (S3) Satellite profile (S4)

Issue When an object is edited the Apply button becomes selectable, but when selected no changes are saved. Environment Continuum ContinuumDB SQL ContinuumServer Cause Insufficient space on hard drive. Resolution Move database backup files. Truncate log tables. Install automated log table truncation routines. 

Issue I/A Series R2 Optimum Start Stop program object may improperly calculate start time when outdoor air temperature compensation is used. Environment I/A Series R2 (all versions) Cause Optimum start / stop compensation is performed through the use of a program object. The object could calculate a negative start lead time when outdoor air temperature compensation was used. Resolution A check was added to the program object to prevent a calculated negative start leadTime due to outdoor air temperature compensation.  The revised object is available for download from The Exchange Download Center. Download the file >> OSS for Niagara 08_03_11.zip In addition, the object includes the following change history. 10-Nov-00  Moved the parameter reset control to an external stimulus 16-Aug-01  Changed reset input from BooleanPriority to DateTime 20-Dec-02  Added check for command time > next event time to account for a large leadtime calculation that results in a start time prior to midnight 14-Sep-05  Added safety check to prevent dynamically adjusted runtime factors from becoming too large 25-Apr-06  Corrected the following stop-time issues:            1) stop-time calculation when earliestStopTime is after schedule stop time            2) stop-time calculation when start/stop times span midnight            3) determining when to perform stop-time analysis    05-Nov-08  Added changes from 2002 and 2003            Added prestart (maxStartLimits) and comfortLimit inputs 18 Nov 02            Added the ability to use OA temperature for OSS calculation 24 Feb 03 12-Dec-08  Added OA temperature to message strings.  Added output for calculated command time. 19-Feb-09  Corrected issues with stop-time analysis:            1) lastStartTime was being used for stop-time calculation            2) analysis for heating was adjusting drift time for cooling            3) analysis for cooling was adjusting drift time for heating            Corrected issues with stop time calculation:            1) heating mode failed to drift when > upper comfort limit            2) cooling mode failed to drift when < lower comfort limit            3) stop mode calculation always reflected the next event time 15-Oct-09  Added properties and check to prevent dynamically adjusted drift time factors from exceeding a specified maximum value. 03-Aug-11  Added check to prevent calculated negative start leadTime due to outdoor air temperature compensation.

Issue What licensing is required for the I/A Series LON Flow Balance tool? Environment I/A Series LON Flow Balance Tool Cause The LON Flow Balance Tool has been downloaded and provided to the air balancer. Resolution The LON Flow Balance Tool software does not require a license.

Issue The RoamIO2 does not seem to be able to communicate with an ACX5740, why? Environment RoamIO2, RoamIO Cause What must be done to get a RoamIO2 to communicate with an ACX57xx controller? Resolution The ACX57xx must have comm1 configured as Infinet. This is because the RoamIO2 hardware only communicates via the Infinet protocol (when running the InfinetServiceTool software) or BACnet protocol (when running the BACnetServiceTool software). An ACX57xx is not communicating either of these protocols unless comm1 is configured for Infinet.

Issue The Vista installation procedure completes with errors.  Vista Server and Workstation may appear to be installed but SQL Server Express is not installed. Environment Vista 5.1.7 SQL Server 2008 R2 Express VMWare Player 3,4 Cause The default hard disk space allocated to a guest OS in VMWare Player is 8GB.  When installing Vista 5.1.7 on Windows XP or above this may not be enough space for Vista to install properly.  The OS requires 5-6GB and SQL Server 2008 R2 Express requires 2.2GB Resolution Increase the disk space allocated to the guest OS in VMware Player 1.  Ensure that the virtual machine state is 'Powered Off'.  To change the state, play the virtual machine. Then go to the VMware player 'Virtual Machine' menu and select Power - Power Off. 2.  Choose 'Virtual Machine Settings...' from the 'Virtual Machine' menu. 3.  On the Hardware tab select 'Hard Disk (IDE)' in the device column. 4.  From the Utilities drop-down list select 'Expand...'.  You can then increase the hard disk size in 1GB increments.  I would suggest 10GB as a minimum. 5.  Please note that the additional space is not immediately available to the guest OS.  To claim this space you must run a disk management tool within the guest OS to increase the size of the existing partition on the virtual hard disk to match the expanded size.  Windows Vista and Windows 7 have built-in disk management tools, but on XP you can run third party tools such as Symantec/Norton PartitionMagic, EASEUS Partition Master, Acronis Disk Director and the open-source tool GParted.

Issue When upgrading Continuum Cyberstation to a higher version on a webClient machine without uninstalling webClient first, the installation will not be successful. Error 1311, Source file not found, pls verify the file "....\Cyberstation1.94\continuum\webcli~1.cab" existed and can access it. Environment Windows XP SP3 webClient 1.93 Cyberstation 1.94 Cause The webClient was not uninstalled successfully. The Cyberstation install process interprets the installation as an upgrade and tries to find the webClient install file "webcli~.cable." When the file is not found in the Continuum folder, the error is encountered. Resolution Uninstall Webclient and delete Continuum folder from the machine From Windows Control Panel, click "add/remove program" and find  "Continuum" then click. Click "yes" button from the pop-up alarm dialogue window. After uninstallation finished, go to  C:\program files\continuum, and then delete the whole folder. Restart the machine Re-Install Cyberstation

Issue With the V221 no longer available (withdrawn in 2004) a replacement valve is requested. Environment V221 VG221F V222 Cause Replacing existing installed V221 valves Resolution V221 can be replaced by VG221F and V222. Flange bolt pattern and measurements should be the same (designed according to DIN standards), and actuator (Forta) can be used with the exception of V222 DN125-DN150 where M22/M50 is required. Please see each products data sheet for more information and details.

Issue Continuum entries in the windows application events occasionally shows error related to the database connection. A database fault warning state was detected and cleared. This is an indication that the connection to the Continuum database was lost for a moment. "wuaueng.dll (46108) SUS20ClientDataStore: The database engine stopped the instance (0)". "wuaueng.dll (46108) SUS20ClientDataStore: The database engine started a new instance (0)."   Environment CyberStation Windows Event Viewer SQL Server Cause Informational entries in the windows application event viewer frequently refer to Continuum reporting a database fault warning. The warning may or may not be accompanied with other information such as: ClientDataStore: The database engine stopped the instance (0) ClientDataStore: The database engine started a new instance (0) These events can occur in the ordinary operation of the SQL Server environment, or they may be associated with errors. Resolution If a 'stopped' instance warning is immediately followed by a 'restarted' instance warning and not associated with an error then the event took place in the context of ordinary operation of the SQL server and can be ignored. If on the other hand there is an error reported such as ‘The database instance ran out of disk space.’ then corrective action will be required.

Issue Each time an I/O module is commissioned the NetController II goes offline. Environment IO modules NetControllerII CX9680 Cause If there is a problem with the controller configuration it may be possible to commission the IO modules on an empty controller.  The controllers would then have to be reloaded by class or may have to be rebuilt manually. Resolution Access the controllers webpage. Select Clear Database Backup Commit changes to the controller. Do not reload the controller. Commission the IO modules on the empty controller.

Issue If the schedule for a personnel area assignment is in a different network to the door that uses the area it does not work. Environment ACX5740, ACX5720 Access Control Cause Objects can not be passed between different Continuum networks.   Resolution For sites with 2 or more networks, when a schedule is linked to the area assignment of a person, that schedule must reside in the same network as the door that uses the area. It is also good practice to locate schedules within the controller for that door, that way should it go offline the schedule will still operate correctly.

Issue NetController 2 IO Modules not powering up when using third party power supply Environment NetController 2, NC2, NCII, IO Modules Cause When using a third party power supply (ac or dc) for a NC2, the IO modules need to be powered separately Resolution When using a third party power supply (ac or dc) for a NC2, the modules need to be powered separately. The IO modules are only powered via the NC2 connector if the Continuum Power supply is used NOTE This is all as the NC2 documentation.

Issue ROAMIO2 fails to connect to i2 controller when the controller is connected to Infinet.  But it succeeds to connect to the i2 controller when Infinet is disconnected from the controller. Environment Netcontroller - CX9900, CX9940, CX9702 Infinet controller - i2 controllers Cause When the netcontroller (CX9900, CX9940, CX9702)  version is old , the ROAMIO2 does not communicate well with the Infinet with the CX connected. Resolution Upgrade the Netcontroller OS (firmware) to the latest version.

Issue When is an "additional 500 points" license required for an Enterprise Network Server? Environment I/A Series G3 ENS-1 Enterprise Network Server Cause The basic Enterprise Network Server license does not include any external point driver licenses.  Driver licenses are required for each 500 or fraction thereof points of any of the four supported driver types. Resolution An Enterprise Network Server can be licensed to directly communicate with BACnet, OPC, MODbus or SNMP points by the addition of the specific driver license option.  Each of these driver licenses support communication with up to 500 points of that specific type of points. The four driver licenses are as follows: ENS-BAC (BACnet IP or BACnet Ethernet) ENS-OPC (OPC Client), ENS-MOD (Modbus TCP) ENS-SNMP (Simple Network Management Protocol).  Each of these driver licenses will support the communications with up to 500 points of the specific type.  For each additional block of 500 points of a specific type, you need to purchase an additional points license, ENS-BAC-500, ENS-OPC-500, ENS-MOD-500 or ENS-SNMP-500.  Here is an example of how these licenses are used.  The Enterprise Network Server needs to communicate directly with 1250 BACnet IP points and 60 SNMP points.  The following licenses will be required: ENS-1 -- Enterprise Network server license ENS-SNMP -- allows ENS to communicate with the 60 SNMP points, technically allowing communications with 500 SNMP points. ENS-BAC -- allows the ENS to communicate with 500 BACnetIP points ENS-BAC-500 -- allows the ENS to communicate with an additional 500 BACnet points bringing the total to 1000 BACnet points ENS-BAC-500 -- this second ENS-BAC-500 license will allow the ENS to communicate with the additional 250 BACnet points, actually bringing the total allowable BACnet point count to 1500 points

Issue After upgrading the WorkPlace Tech Tool software to release 5.8 and requesting / installing a new TIP demo license, the license is still shown as expired. License request was generated using the "Purchase WIBS Software" icon on the computer desktop. Environment I/A Series WorkPlace Tech Tool software, release 5.7.2 or newer including release 5.8.x. Cause The WIBS Purchase program is used for licensing all WIBs product family software and the WorkPlace Tech Tool software, prior to release 5.7.2.  This licensing software is not compatible with Windows 7. The licensing subsystem software used with the WorkPlace Tech Tool software, release 5.7.2 and newer uses a new licensing subsystem that is compatible with Windows XP, Windows Vista and Windows 7. Resolution After installing the WorkPlace Tech Tool software, version 5.7.2 or newer, the "WIBS Purchase" icon can no longer be used to request a new or updated license for the WorkPlace Tech Tool software.  The "WIBS Purchase" licensing program does not work with the newer version of the WorkPlace Tech Tool software. During the installation of the WorkPlace Tech Tool software, a new license request program is installed on the public desktop, if not already installed.. This license request program is named "Purchase WorkPlace Tech Software".  This icon must be used to create the license request and install the new license for the current version of the WorkPlace Tech Tool Software.  Depending on the computer configuration and user permissions, the "Purchase WorkPlace Tech Software" icon may have not been created on the computer's desktop.  If the program is not on the desktop, the corresponding program, WPTLPurchase.exe can be found on the computer in the folder C:\Program Files\WorkPlace Tech\Licensing\Core".  A shortcut to this program should be created on the computer desktop.

Issue Hardware address Wrong address Direct connect Environment I/NET Direct Connect Cause Hardware addresses where used with the old TAPs and this address needed to be the same as the address configured on the TAP set by their dip switches. These TAPs are hardly used anymore and when you use a Direct connect to say a 7798C and a hardware address are set, you will get unknown address data in AMT Resolution Right click I/O server and choose properties and modify your profile Modify your Direct connect settings Set hardware address to "0" Software address can still be used

Issue An initial calculation of KWH produced a artificially high value that was captured by a trend log and is now stored in Report Server. This anomaly is artificially skewing the auto scale feature. Environment Web Report Server Trend Log Extended Trend Log Extended Log Cause The trend data anomaly is artificially skewing the auto scale feature of the trend graph in Report Server. Resolution Open the associated extended trend log. Right click on the entry that is to be corrected and select edit record.  Change the value of the entry to some more acceptable value. Enter  a reason for the change in the comment field. Select save. The new value will appear in place of the original entry with an icon to show that the value was altered. Allow up to 24 hours for the data to be migrated into Web Reports Server.

Issue How calculate the accuracy? Environment SHD100: 006902320 006902321 SHD100-T: 006902330 006902331 Cause In the documentation, both "Accuracy" and "Temperature Dependence" is listed. The Temperature Dependence is varying (see data sheet for chart), while the Accuracy is constant across the scale. Resolution The Accuracy and Temperature Dependence needs to be added together in order to calculate the correct total accuracy/deviation.

Issue When an alarm in Xenta Server or a Xenta device under a Xenta server that are configured to send alarms via mail,  the mail receivers will get  an extra mail when that alarm is acknowledged. Environment TAC Vista TAC Xenta Server Cause This behaviour is due to a bug in earlier versions of the Vista Server software Resolution There is no known workaround to this issue, but it is fixed from Vista v5.1.3 (and later versions),  i.e. an upgrade will solve it. 

Issue The temperature readings from the space temperature sensor on the TAC Xenta 120 device is not stable, is it possible to damp the readings? Environment TAC Xenta 121-FC TAC Xenta 121-HP Cause In some application, it is not possible to get a stable reading from the temperature sensor. Resolution It is possible to activate a filter for the space temperature readings. Set the nciNodeAppOp2.bit14 to 1, this could be done from TAC Vista or from LonMaker. please note that the first bit is bit zero. This will make the device to use 80% of the old value and 20% of the new reading.