Building Automation Knowledge Base

Issue Having issues adding a SNVT to an existing controller in a NL220 system? Or possibly a new device template is not showing up after the .xif change? Environment NL220 Cause In some cases, when you are uninstalling (or decommissioning) a controller, it get into an unconfigured state, not allowing it to take a download.   Resolution Take the database offnet Use the Tools drop down and Uncheck the "Attached to Network" option. Do an "uninstall" or decommission the controller Browse in the Menta file with the new SNVT to the System Plug-in and NL220 should have a new device template for the controller.   

Issue Can the Network 8000 Microflo or CVV-80000 series controller be integrated using the Niagara R2 GCM driver? Environment Niagara R2 Network 8000 CVV-80000 Cause Information on integrating Network 8000 Microflo or CVV-80000 series using GCM driver Resolution Yes. Architecturally, it connects to the GCS bus of a GCM-84000 controller. The GCM database will contain VVBOX blocks which interact with the Microflo controllers. The VVBOX block can be read from and written to using GcmGeneric objects in a UNC station.

Issue What's the latest version available in Pocket I/A? What make/model of handheld device was used in testing? Environment Pocket I/A Cause Would like to confirm the device is running the latest version of Pocket I/A. Resolution Pocket I/A Version 4.1 (Release B) is an update to previous versions of Pocket I/A to support the Microsoft Windows Mobile 5.0 Operating System used with newer handhelds. The features and applications in previous versions of Pocket I/A will continue to operate in Pocket I/A Version 4.1 (Release B). This version was tested using an HP IPAQ HX 2490B with MSMobile 5.0 operating system. Pocket I/A 4.1 can be downloaded from The Exchange Download Center.

Issue What BACnet Command priority does a Cyberstation program use in changing value of BACnet points? Environment Cyberstation Cause Change the value of BACnet points Resolution When you use the WriteProperty() function, you must use the BACnet path of the object for WriteProperty() function. - If the priority# is given in the WriteProperty() function, it sets the value of the point with the given priority#. - If the priority# is not given in the WriteProperty() function, it sets the value with priority#16 by default. When you don't use WriteProperty() function. - If you use BACnet path ( Ex; BACnetDevices\BCXName\MyNum = 12.340), it sets the value with the priority# that is defined in the attribute of BACnet Command Priority for Cyberstation Programs in the BACnet Preferences. - If you use Infinity path ( Ex; MyNetworkName\BCXName\MyNum = 12.340), it sets the value with priority# 10 by default.

Issue When "learning" an MNB controller into a Niagara R2 UNC station that has an MN-Sx sensor, a read failure occurs and several WARNING messages appear  in the Standard Output Window. These errors did not occur in uploads with BACnet jar files previous to 527i. Environment MNB controller Niagara R2 UNC station MN-Sx sensor BACnet jar file (527i) Cause A change that occurred in the 527i BACnet jar file. Resolution These messages occur with BACnet jar file 527i and later and are legitimate. They are a result of uploading the S_LK_Display1 object. The read failure for description property occurs because there is no description in this object and the subsequent warnings are because Niagara R2 does not support the files listed. This was true of previous BACnet jars as well but was not reported.

Issue How to export histories from a Niagara G3 ENC to a Niagara G3 Enterprise Network Server (ENS) Environment I/A Series G3 (Niagara) ENC and Enterprise Network Server (ENS). Cause Technical tip. Resolution To export a history to the ENS, expand the ENC's Niagara network and locate the ENS station. Expand the station, right-click Histories, and choose "View > Niagara History Export Manager"  Click the "Discover" button to discover the histories in the ENC station. Highlight the desired histories, and click the "Add" button. Select the desired Execution Time (Daily, Manual, Interval), set the "Enabled" field to True, then click OK.  Send initial history data to the ENS by clicking on the "Archive" button. In the Nav tree, open the ENS station. Expand the server's History folder. Verify that the histories from the ENC station are there.

Issue The Workplace Tech Tool 4.0 Engineering Guide (F-27254), Chapter 3 - "S-Link Sensor Tags", states "PBOccMode" is 0 following a download or reset.  This is incorrect.  Following a download or reset, the PBOccMode tag comes back as NA. Environment Lon and BACnet controllers with MN stats Cause error in documentation Resolution There is a work around if a 0 is required following a download or reset. If the existing logic is not able to handle the "NA", then link PBOccMode into Input[1] of a two input "Priority Object". Set Input[2] to a constant of 0. The Priority object will output a 0 following a download or reset.

Issue When creating piping graphics using the Niagara G3 kitPxHvac palette, how can elbows and tees be lined up exactly? Environment Niagara G3 Cause To line up pipe and elbow, snap option must be turned off. Resolution Turn off “snap” and place the objects close to each other. Then, while holding down the “Ctrl” button, use the arrow keys to move the selected pipe or elbow until it lines up perfectly.

Issue Online Messages on an SLI Environment I/NET site Cause Messages coming from the Sub Lan Interface (SLI) Resolution A door controller (DPU) has a limited amount of memory space available for storing individual records and messages. "Resident in DPU" individual records are given priority in storage: they are never discarded. Transient (non-resident) individual records and messages are stored on a space-available basis. If a communication outage between the SLI and the door controller causes the door controller's memory capacity to be reached, older records must be discarded as new messages continue to be generated. All records are discarded on a first-in, first-out (FIFO) basis, so that the remaining records are the most recent ones. A "DPU queue ovflw" message will also be generated to warn that data was lost. Records are discarded in the following order: Transient individuals. Messages. If there are no more transient individuals to discard, routine messages will be lost. When communications between the SLI and the door controller are restored, the contents of the door controller's queue (including the "DPU queue ovflw" message) will be delivered, freeing memory in the door controller. The SLI continually requests messages from its door controllers. Retrieved messages are queued within the SLI until they can be sent to appropriate host workstation(s). When the SLI queue is full, it will continue to accept messages from door controllers (i.e., the SLI will not cause its door controllers to discard messages). With its memory queue full, the SLI will discard older messages as newer messages are received. This ensures that the remaining records are the most recent ones. A "DCU queue ovflw" message will be generated to warn that data was lost. When communications between the SLI and the host PC are restored, the contents of the SLI's queue (including the "DCU queue ovflw" message) will be delivered, freeing memory in the SLI. There is also a TPA-DALL-09-0001.00 that was written on this issue.

Issue Editing any time schedule weekly charts in Vista Webstation 4.5 results in the schedule being ON ALL DAY regardless of what changes were specified in the editor. Environment TAC Vista Webstation 4.5 Cause Webstation is configured to use the wrong ASP.NET version. Resolution Open IIS Manager Open the properties window of the Webstation application by right clicking on it. On the ASP.NET tab change the version to 1.1.4322 and click OK. Stop the website and restart it in IIS Manager and the problem will now be fixed.  

Issue The Niagara G3 Microsmart Driver Installation and Configuration Guide (F-27523) lists "Applicable Documentation" on page iv. Is that documentation available for download? Environment Niagara G3 MicroSmart Drive (Installation and Configuration Guide) Cause Manuals (F-25695, SOFT-MCN-101) are not available. Resolution Two documents in the list are obsolete and were inadvertently listed as available. They are: DCT MicroSmart Reference Manual (F-25695) MicroSmart Application Manual (SOFT-MCN-101). The remaining documents are available in iPortal > Publication Zone.

Issue Link Summary Indicator in Netcon during Equalization Environment Netcon Cause During equalization, when a Client is connected to the File master, who is either directly or over Ethernet connected to the system, a – sign is displayed in the cnf column in Network Configuration, Link Summary. Normally, this indicates that there is no communications from the Client PC to the controllers. However, if you penetrate the link you are able to see all the controllers and their sub-lan devices. Resolution In order to get rid of the – sign in the cnf column, the following steps needs to be followed: Shut I/NET and I/O Server down on the Client Open Windows Explorer and browse to C:/Program Files/INET Seven/Data folder and delete all files with .dat extensions Restart I/NET and I/O Server again Go to Edit/Host Computer/Network Configuration and in the Link Summary, the – sign in the cnf column would be gone Note: The dat files will get rebuilt when I/NET is restarted.

Issue Crystal Reports in I/NET Seven Version 2.21 Environment I/NET Seven version 2.21 Crystal Reports XI Cause Beginning with I/NET Seven version 2.21, the I/Net Seven Reports application uses Crystal Reports XI as the reporting engine. Resolution In order to create and run reports using Seven Reports, you must first install Crystal Reports XI support files unto your PC. An installation program named SetupCrystalReportsXI.exe is included on I/Net’s installation disk for this purpose. When you execute this file, Microsoft Installer will launch and the necessary support files will be loaded onto your PC. We recommend that you install Crystal Reports XI support files immediately after completing the I/NET Seven host software installation. If you forget to install the support files, you will receive the following message when you launch Seven Reports: Crystal Reports Support files must be installed. Run CrystalReportsX1_Support Files.msi found on the Support Folder on the CD. If you see this message, click OK and install the support files from I/Net’s installation disk. To install Crystal Reports XI support files: Prepare to install the support files as follows: Close all other applications running on your system, including virus-checking software. Insert the I/NET Seven CD-ROM into your CD-ROM drive. If I/Net’s Setup program automatically launches, cancel it at the first screen that offers a Cancel button. Explore the CD-ROM and locate the following folder: d:\Support\SevenReports\CR_XI (where d: is the letter designation of your CD-ROM drive) Within this folder, execute the following file:SetupCrystalReportsXI.exe. This causes Microsoft Installer to launch and begin installing the support files. Follow the onscreen prompts to complete the installation process.

Issue Will VisiSat work with Windows Vista? Environment VisiSat Windows Vista Cause Compatibility with Microsoft OS Resolution VisiSat Version 2.1 build 148 service pack 1 can either be used on a computer running Windows XP Pro with Visio 2003 or it can be used on a computer running Windows Vista with Visio 2007. As detailed in the VisiSat 2.1 Configuration Tool Datasheet, available via Exchange OnLine, where you will also find the Installation/User's guide and the VisiSat Engineering Guides. VisiSat Version 2.1 Build 148 service pack 1 is available for download via Exchange OnLine. Note: File size = 41.5 Mb.

Issue Will VisiSat work with Visio 2002 Environment VisiSat Visio 2002 Cause VisiSat Version 2.1 build 148 service pack 1 will not work with Visio 2002. Resolution Although we would recommend using the latest version, VisiSat Version 2.1 build 137 can be used with Windows XP Pro and Visio 2002. VisiSat Version 2.1 Build 137 is available for download via Exchange OnLine. Note: File size = 30 Mb.  

Issue Initiate Xenta 102-AX service pin messages (Neuron ID) from an M/STAT It is not required to hit the service pin button on the Xenta 102-AX itself, this can be done remotely from the room stat, provided it has an M/STAT jack (STR-250). Environment Xenta 102-AX M/STAT Cause If the Xenta 102-AX is installed up in the ceiling out of arms reach (which is typical) it can be cumbersome to get to each board to press the service pin button. Resolution Plug in an M-STAT to the room sensor (assuming you ordered the sensors with the M-STAT jack) Hold the service button in for about 5 seconds. This will tell the controller to broadcast its Neuron ID.

Issue Unoccupied mode on an Xenta 102-ES is really shutdown mode. Unoccupied setpoints are not maintained in the unoccupied mode. Heat and damper are forced to 0%. Standby setpoints are used in the unoccupied mode. Environment Xenta 102-ES Cause The structure of SCPTsetpoints includes unoccupied setpoints. That is the only reason they are available for a Xenta 102-ES. Resolution If the controller is in occupied or bypass mode, it uses the occupied setpoints. All other modes use the standby setpoints. When unoccupied, all heat operations are forced to minimum (locked out) and so is the damper. In the end, standby mode may provide more desirable results than unoccupied.

Issue How do I select an actuator and valve combination? Environment Actuator Valve Cause Select the correct actuator and valve part numbers. Resolution Refer to the TAC Catalog F-27414-*. Read the section on valve part numbers. Select the valve body needed. Refer to Catalog F-27382-*. Read through the actuator selection for MA, MC, MF, MK, MM, Mp, and MS to identify the desired actuator. Refer to TAC Catalog F-27414-*. find the page with the chosen actuator valve combination. Verify from the close off table that the actuator will meet the valve performance requirements. Turn to the actuator assembly code table and select the assembly code needed to complete the valve assembly number. ie: Vx-XXXX-XXX-X-XX. Order valve. If valve is not available as a factory assembly, order the individual parts and field assemble. The valve close off table provides the correct linkage kit required to couple the actuator and valve body, not all actuators require linkage kits.

Issue Recover deleted graphic files Environment Vista Server TGML Graphics Cause You can recover graphic files deleted from your Vista database. Resolution TAC Vista stores a cache for quicker opening of graphic files. C:\Documents and Settings\your_initials\Local Settings\Temp\TemporaryGraphicFiles C:\Documents and Settings\your_initials\Local Settings\Temp\TgmlCache

Issue After creating a new station using the "New Station Wizard" in Niagara G3 Workbench, it fails to copy into the ENC using the "Station Copier". This error message appears: "The local station database file config.bog is currently in use, and cannot be copied". Environment Niagara G3 Workbench Cause It's because a "Save Bog" was not done. Resolution Go back to Workbench and open the station, make a change and do a "Save Bog". The station should now copy without issue.