Building Automation Knowledge Base

Issue "Access Denied" errors are reported during the re-installation of the Niagara R2 software. Environment Niagara R2 software Cause The files installed in the nre\modules folder are write protected. Resolution If an attempt is made to reinstall Niagara R2 software on a computer, an installation error frequently occurs. The Niagara installer (second installation program) progresses one tick on the progress bar then displays a "Module Install Error" window containing the message "Access is Denied". Clicking the OK button to acknowledge the error results in the message window reappearing multiple times. This occurs because the files installed in the nre\modules folder are write protected when installed. To prevent this problem before attempting to reinstall any release of the Niagara R2 software, Open Windows Explorer ("My Computer") Select all files in the niagara\nre\modules folder Right-click on the selected files Select "properties" from the displayed menu. The Properties window appears.  Clear the mark in the "Read-only" box Click the OK button.

Issue Which antivirus software is compatible with Niagara R2 and G3? Environment Niagara R2 Workplace Pro (all versions), Niagara G3 Workbench (all versions) Cause Antivirus software can block ports and services used by Niagara R2 and G3 Resolution By default, Niagara R2 software needs the following ports/services/applications "open", or unblocked: Port 80 (station communications & Web access) Port 3011 (Admin Tool) Niagara Service (Control Panel > Administrative Tools > Services) Files in the C:\ < niagara r2 release number > \nre\bin directory By default, Niagara G3 software needs the following ports/services/applications "open", or unblocked: Port 80 (Web access) Port 1911 (station communications) Port 3011 (Platform access) Niagara Service (Control Panel > Administrative Tools > Services) Files in the C:\ < niagara g3 release number > \bin directory Various antivirus software products by default will block one or more of the above, and need to be configured to allow or "unblock" them.  Niagara R2 and G3 software will work with any antivirus program that allows unblocked communication to the above ports, services, and files.   NOTE: The specified ethernet ports must be open bidirectionally for both TCP and UDP traffic.

Issue Opening and running a Seven Report that uses the Calendar to define the date range feature for data after entering the values, and nothing happens. It does not pull up any data. Business Objects error is seen in the Calendar picker.  Product Line TAC INET Environment I/NET Seven revision 2.31 and higher. Seven Reports (Crystal Reports) Cause Crystal Reports has not been set up correctly on the host PC. An additional file has to be installed to handle scripts in Seven Reports. This file can be found under >Support>Sevenreport/CR_XI/PostCRSetup on the INET CD.  A read me is also located there to assist with the installation procedure: Resolution To resolve this issue, the following steps need to be implemented: Close I/NET and I/O Server Open up Windows Explorer and select the original CD Open up the Support Folder and expand it Select the CR-XI folder and run the SetupCrystalReportsXI.exe Once completed, go back into the folder again and run the Post CRSetup.exe Once this is completed, restart I/Net and I/O Servers again Open up Seven Reports again and run the associated report

Issue During startup of the Lon FlowBalance software, an error is displayed indicating that the program "cosmo.exe" failed to register Product Line TAC IA Series Environment MNL-FLOW-BAL 3.0 - MicroNet Software Microsoft Vista, Windows 7, and Windows 10 (64-bit installations) Cause The software installer installed the software into the C:\Program Files (x86) folder on the Windows system drive. When the software is started up, it needs to initialize some internal driver and data modules. These modules are expected to be in the C:\Program Files\TAC folder, however, that folder was not created during the installation of the software. The LON FlowBalance version 3 software is not supported on 64-bit versions of Windows because fully-supported Echelon (LON interface) drivers are not yet available. Resolution Reinstall the LON FlowBalance software on a computer or virtual machine running Windows XP, Windows Vista (32-bit) or Windows 7 /10 (32-bit).

Issue Troubleshooting guide for LON bus communications Environment MNL controllers (MNL-50, MNL-100, MNL-110, MNL-130, MNL-150, MNL-200, MNL-V1R, MNL-V2R, MNL-V3R) Cause Troubleshooting guide for LON bus communications Resolution TPA-RKFD-09-0011.00 is a checklist which provides several settings/configurations to review when faced with a communication problem at the controller level. The content was compiled from different resources, summarized, and laid out in an easy-to-use manner so as to provide a quick-reference document.

Issue Site needs to change the IP address in Cyberstation Environment Continuum Windows XP Windows Vista Windows 7 Windows Server 2003 Windows Server 2008 Cause There is a need to be able to change the IP address in Cyberstation Resolution Shut down Cyberstation Go to the PC's network/LAN/TCPIP connection properties and enter the new static IP address Verify the IP address change by going to Start>Run>Cmd (DOS Prompt) and type Ipconfig/all. The IP address will show under the network card similar to the following: Description . . . . . . . . . . . : Intel(R) 82577LM Gigabit Network Connection Dhcp Enabled. . . . . . . . . . . : No Physical Address. . . . . . . . . : 5C-26-0A-45-7C-D8 Autoconfiguration Enabled . . . . : No IP Address. . . . . . . . . . . . : 192.168.203.2 Subnet Mask . . . . . . . . . . . : 255.255.255.128 Default Gateway . . . . . . . . . : 192.168.203.1   Launch Cyberstation Open the Workstation object using Continuum Explorer (Right click>Edit) Click on the "Teach" button (Distributes the New IP address to the controllers)

Issue StatusBackup "State" system variable is not able to be manually changed and attempting to set this variable to Enabled produces a script error instead of resetting the flash circuit breaker. Product Line EcoStruxure Building Operation Environment Building Operation v1.8 and below. b3/i2 Controllers Cause Feature to reset flash circuit breaker was not implemented in the earlier versions of Building Operation Resolution A new feature to reset the flash circuit breaker was implemented in Building Operation v1.9 to address this issue. The b3 BACnet Device Memory on-line help topic shows how this is manually reset from the WorkStation in the Device menu.

Issue Changes to COV and ReadProperty in bCX from v4.500048 Product Line Andover Continuum Environment bCX b3 Controllers Cause New feature to allow user flexibility for using Forced Polling and not COV Resolution From bCX version v4.500048, all Controllers will have the option of forcing a poll of points from other Continuum and third party BACnet controllers. This new feature: allows programmers to decide which data exchange method to use by the syntax in which they write their data-sharing programs. provides a method for forcing point-to-point polling from a device that does not support COV and sends an invalid error message when the subscription is attempted. This previously caused Continuum to reject polling, resulting in a failure to share data. allows programmers to decide to poll a point only when needed, even if the device supports COV subscriptions. This ensures that data from a device is only sent when necessary instead of always being sent on a “change of value”. The following Plain English formats force polling: "Local point = Infinity Remote Point Value" "Local point = BACnet Remote point Value" "Local point = ReadProperty(BACnet Remote point Value)" The second argument, Value, ensures that polling is commanded – now for BACnet, as well as Continuum/Infinity. (The third example shows the use of Plain English’s ReadProperty system function.) If the Value argument, shown in these examples, is left out, Continuum BACnet will operate as it always has – always attempting a COV subscription and only falling back to the polling method if the target device sends the appropriate COV subscription failure message. Caution: If you have a device that does not support COV subscriptions or you have chosen to use the polling syntax, you must be careful how you write your Plain English programs. A program that runs every scan and polls a point from another controller will cause major problems. For instance, if your scan is running at 100 milliseconds and you try to poll any BACnet device at that rate, you will most likely knock the device offline. It will also cause the program to disable and seriously slow down the scan in your controller that is requesting the data (since the scanner waits for an answer to a poll before continuing). You should also use a line E in your programs, since any communication problem to the target device will cause the polling program to disable.

Issue Does a single controller (2nd generation controllers such as NC2 and bCX) support two(2) Modbus TCP/IP xDrivers on two(2) different comm ports?    Product Line Andover Continuum Environment Modbus TCP/IP XDriver NC2 (CX9680) bCX4040 Cause Need to have Modbus TCP/IP interface with 3rd party devices for both Server mode (Slave mode) and Client mode (Master mode).  Resolution You can have only one Modbus TCP/IP XDriver on a Controller(NC2 or bCX).  In order to have Modbus TCP/IP XDriver for both Server mode and Client mode, there should be two different CX controllers, and  different mode of Modbus TCP/IP XDriver should be installed and configured on different controller.   Note: This also includes any IP XDrivers. You can only enable one IP XDriver per Controller. (Ex. You can not enable a BACnet IP XDriver on one comm port and a Modbus IP XDriver on another, you would need two Controllers for this - one IP XDriver on each)

Issue Cannot establish communications to Modbus RTU using BCX X-Driver on Comm2 Environment BCX 4040 Modbus RTU Cause Configuration of BCX to communicate with Modbus RTU device Resolution This excerpt from the Modbus RTU guide describes the parameters to configure the X-driver for Modbus RTU communications using the BCX. Click Here

Issue In Webstation, when clicking on a hyperlink located on a TGML that references another TGML, nothing happens. Product Line EcoStruxure Building Operation Environment Webstation Cause Sometimes when a graphic is saved, it gets compiled incorrectly. When this happens, the graphic will generally work inside Workstation because Workstation is a closed environment and much more forgiving then Webstation. Resolution Edit the graphic that you cannot open Save it again It will get recompiled correctly

Issue ACX5740 controller going on and offline when the WebClient Cyberstation is started Environment LAN System CyberStation 1.90 WebClient Cause Both the regular CyberStation and WebClient CyberStation were configured with the same ID information Resolution Reconfigure the WebClient CyberStation with unique ID information

Issue Recommended method for replacing an MR-VAV-AX controller. Where to get ASC Parameters for the new device. Environment I/NET software all versions MR-VAV-AX controller Cause An MR-VAV-AX needs to be replaced on an existing VAV box. Resolution The ideal way to change an MR-VAV-AX or similar would be to use an airflow hood to calibrate when the device must be changed. However, if no airflow hood is available, see the options below: Obtain the ASC parameters of the existing MR before removing the device from service. Re-use the original settings. If these values cannot be recovered, then ask the customer for the original drawings or T&B reports on the device in an effort to properly establish correct duct diameter and total airflow. Rarely is this information readily available at the time of the change. Without such info, an estimation will have to be made. A rule of thumb is: 250 CFM per diffuser and an eyeball estimate of the duct diameter The pickup factor is left at factory default (3) or compared to other similar devices and an average of other pickup factors is used. For setting CHF, base it on the above estimate of 250 CFM per diffuser and make sure that the box just reaches 100% damper at the maximum airflow it is physically capable of at the AHU's normal static CLF is an estimate based on the use of the space and the temperature needs of the occupants. CLF is about 10% of the CHF.

Issue Cannot connect network variable point from a third party LON device to a graphic within an XBuilder project.  XBuilder will not allow the drag and drop of LON network variable between the network pain and the system pain when you attempt to create connections. Product Line EcoStruxure Building Operation, TAC Vista Environment XBuilder Vista Lon Device .xif Cause XBuilder is very particular about the format of an .xif file and it will not allow certain characters in the function block name. Vista and LonMaker have far less limitations and these programs are able to parse these characters without causing problems. This explains why your values may show up in the LNS management tool and Vista Workstation. However, once you import the network into XBuilder you are unable to connect the SNVTs to your graphic. Resolution Replace the incorrect characters in the function block line of the .xif and reload the new .xif into your LonWorks Network.  Please see LON device can communicate in Vista, but fails in a Xenta Server / XBuilder for more information about incorrect characters in an xif file. INCORRECT FUNCTION BLOCK EXAMPLE: File: MP580.XIF generated by NODEUTIL Revision 1.46, XIF Version 4.0 Copyright (c) 1997 by Echelon Corporation All Rights Reserved. Run on Fri Oct 31 16:30:28 2003 80:00:2A:52:00:03:04:03 2 15 1 618 0 8 8 4 4 11 11 0 0 0 0 3 0 16 0 0 1 65536 618 0 0 0 0 0 0 0 0 0 0 0 0 10000000 1 7 1 0 4 4 4 15 200 0 78125 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 1 5 8 5 12 14 15 * "&3.4@0,20000-MP580,8500-SCC,8610-DAC The problem is the three dashes  between the object numbers and the object names in the self doc string.  This is "allowed" in Vista and LonMaker in some sense.  For  example, Vista "replaces this "-" to a "/" but then XBuilder can't handle this situation properly. CORRECTED EXAMPLE: File: MP580.XIF generated by NODEUTIL Revision 1.46, XIF Version 4.0 Copyright (c) 1997 by Echelon Corporation All Rights Reserved.  Run on Fri Oct 31 16:30:28 2003 80:00:2A:52:00:03:04:03 2 15 1 618 0 8 8 4 4 11 11 0 0 0 0 3 0 16 0 0 1 65536 618 0 0 0 0 0 0 0 0 0 0 0 0 10000000 1 7 1 0 4 4 4 15 200 0 78125 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 1 5 8 5 12 14 15 * "&3.4@0,20000MP580,8500SCC,8610DAC;Tracer MP580 The dashes 3 x (-)s have been removed from the function block name

Issue The I/A Series G3 Platform Software Manager indicates "Not Available Locally" when connected to the remote platform (ENC or JACE). Environment I/A Series G3 - All versions Cause Upon start of Workbench, the modules residing in the local Workbench module folder are scanned by the software.  During this process, new and/or updated modules are copied and saved into the local software database.  "Not Available Locally" indicates the associated module is missing from the local Workbench software database.  The following example finds the Installed Version of tacMs at TAC 3.4.64.4 with the Available Version missing with the comment "Not Available Locally." Resolution There are two methods to correct this issue. Method 1:  Copy the module directly into ~\modules directory. This makes the module(s) available in your Workbench environment, and also available to install in other remote platforms.  When the installer runs, the module(s) are also copied into your software database, available for installation. This is the typical choice. Method 2:  Copy the module into your ~\sw\inbox directory (or, use the equivalent “Software Import” feature in the Software Manager). In this case, the module(s) are not used in your Workbench environment, but are available in your software database for installation in remote platforms. If the module is invalid or corrupt, the software manager will generate and place the module in the "failed_imports" folder (e.g. unable to read the manifest files, class files, etc.).  Verify the module is valid. Reference the Niagara AX Platform Guide - Software Manager for additional details.

Issue What files are saved, to where and why is this used. Product Line EcoStruxure Building Expert Environment SmartStruxure Lite Multi-Purpose Manager (MPM) All variants: VA, UN, GW Cause The running database of a SmartStruxure Lite MPM controller is in the controllers volatile memory (RAM), in order for this data to be preserved during a power failure or reboot this needs to be saved to non volatile memory (Flash) Resolution The save period is for backing up the controller database to flash memory, this can be set to Never, Hourly or Daily. All programming and runtime information is then saved to the controllers flash memory so that it is not lost during a power failure or controller reset. Stored data includes Controller status, configuration changes, updates such as trended information or setpoint changes, and Lua scripts.

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 After upgrading, it now asks for the security key when launching Continuum. Product Line Andover Continuum Environment Continuum Cause Continuum stand-alone is not working in Demo mode after upgrading. Resolution Completely uninstall Continuum and re-install using the following steps. Warning: Incorrectly editing the registry may severely damage your system. At the very least, you should back up your current settings and any valued data on the computer before making changes to the registry. Go to Control Panel > Add or Remove Programs. Remove Continuum. Reboot the PC. Remove EPI Builder Run-Time. Reboot the PC. Remove Sentinel System Driver Installer if installed. Reboot the PC. Remove the Continuum entries in the registry using Regedit. Start > Run > regedit Browse to HKEY_LOCAL_MACHINE\SOFTWARE\Andover Controls. Select the "Andover Controls" key, right-click and select "Export" to backup the reg key. Select the "Andover Controls" key, right-click and select "Delete" to delete the reg key. Reboot PC. Install Continuum without a security key attached to the PC.  You should now be able to start Continuum in stand-alone demo mode.

Issue When ordering an I/A Series R2 (Niagara) UNC-520-2, is web browser support included? Environment UNC-520-2 UNC-520-WEB Cause UNC-520-WEB is a separately purchased upgrade. Resolution No, it is not included. Order the UNC-520-WEB upgrade in order to add web browser support to the UNC-520-2. See the Specifications Data sheet, "Models", page 3.

Issue This is a guideline to do air balance settings (airflow calibration) on a VAV ASC using a I/STAT or M/STAT. Product Line TAC INET Environment MR-VAV-AX MR-VAV-X1 MR-VAV-X2 Cause The air balance company needs a procedure to properly set up the MR-VAV-AX products for the air balance settings. Resolution Understand the cooling setpoint is 75°F, and the heating setpoint is 70°F. This information is important in knowing which state the system is trying to control. While in the PP mode of the I/STAT, it is important to verify the setpoint is 75°F. This allows Test & Balance to set the temperature to: 77°F for maximum cooling 72°F for minimum cooling with no fan 68°F for heating mode - minimum primary airflow with fan To verify the current setpoint, use the Select key and scroll up to Set Temp. The I/STAT will display the current setpoint. For testing purposes as described in Step 1, if the temperature setpoint is not 75°F, press the + or - key to raise or lower the setpoint to 75°F. In order to enter the Service Mode, press the Service key. Enter the I/STAT password 183. Press the + or - key to see the left most digit change accordingly. Press the + key to scroll to 1 and press Enter. The cursor on the I/STAT will move to the center digit. Press the - key to 8 and press Enter. Now the cursor will move to the right most digit. Press the + key to 3 and press Enter. You are now in the Service Mode. While in the Service Mode, the Service key is the escape key and the Enter key will allow the controller to accept your desired changes. The first step in the calibration process is to make sure the controller is at the Factory Calibration Setting (FCS). Press the Select keys to scroll to Airflow Parameters (AP) and press Enter. CLF is displayed on the I/STAT. Press the Select keys to scroll to FCS, press Enter. The I/STAT will display NO. Press the + key to change the display to YES and press Enter. Press the Service key to back up one screen. To verify duct diameter (dd) press the Select key and scroll to Unit Parameters (UP). The I/STAT will display the current duct diameter as 10.0 (default of 10 inches) unless the value has already been changed. Press the + or - key to raise or lower the value, and the Select keys to move between the right most and center digit. Sample: 8 inch box is displayed as "08.0" Press the Enter key to allow the changes to take place. Press the Service key to back up one screen. To verify Cooling Low Flow (CLF) and Cooling High Flow (CHF) setpoints, press the Select keys to scroll to Airflow Parameters (AP) and press Enter. CLF is displayed on the I/STAT. Press Enter, the I/STAT will display the current value. Note that CFM is displayed as KCFM, for example 0.50 = 500 CFM. If the values are correct, press Enter. If the values need to be changed, use the + and - keys to change the values and the Select keys to move the cursor from the left most digit to the right most digit. Once you have the desired value displayed, press Enter. The I/STAT is now displaying CLF. Press the Select keys to scroll to CHF and press Enter. If the values are correct, press Enter. If the values need to be changed, use the +, -, and Select keys to change the CHF to the desired value then press Enter. CHF is displayed on the I/STAT. Press the Select keys to scroll down to Calibrate Primary Low (CPL), press Enter. The VAV controller will modulate the damper to maintain its design CLF. The I/STAT is currently displaying the CFM the controller is reading. Note that during this process, the CFM value may go to -0.1, 0.0, etc.; the controller is calibrating itself to the 100% actual closed position. Once the CFM comes within 10% of the CLF setpoint, the ON/OFF LED will turn on. While the LED is on, the controller is not modulating the damper and the controller has the damper in a fixed position for approximately 60 to 90 seconds. (Do not attempt to enter any values at this point. When the LED goes off, the controller takes back control of the damper and will modulate it to maintain CLF.) Once the airflow has stabilized and the I/STAT is displaying the CLF CFM, measure the airflow and input the actual value (do this as soon as possible because once the + or - key has been pressed, it freezes the damper into a fixed position to allow enough time to enter the actual value and to minimize chances of the actual CFM changing), into the I/STAT using the +, -, Select and finally the Enter key as described in Step 8. Important: Even if the current reading is correct, press Enter. The I/STAT will display Calibrate Primary High (CPH), press Enter. The VAV controller will modulate the damper to maintain its design CHF. Again, once the CFM comes within 10% of the CHF setpoint the controller's ON/OFF LED will come on and the controller will perform as described in Step 9. When the LED goes off, the controller takes back control of the damper and will modulate it to maintain CHF. Once the airflow has stabilized and the I/STAT is displaying the CHF CFM, measure the airflow and input the actual value (again, do this as soon as possible) into the I/STAT using the +, -, and Select and finally the Enter key as described in Step 8. Important: Even if the current reading is correct, press Enter. The I/STAT should be displaying CLF. Once the low and highs have been calibrated, press the Service key. Press the Select key to scroll to Operational Parameters (oP), press Enter. Press the Select key again to scroll to Prove Performance (PP). This mode will place the program's Room Temperature in a test state. The I/STAT display will toggle between the current CFM and the room temperature. This step will allow the balance engineer to verify proper operation of the VAV controller to maintain the design maximum and minimum airflow. Press the + and - keys to increase or decrease the room temperature in order to manipulate the system to control between cooling and heating as described in Step 1. Once the VAV has controlled the damper to design minimum CFM, the balance engineer can adjust the fan (if applicable) to design airflow. Important: If at any time during the calibration process, (not during Prove Performance (PP)) a mistake is made, make sure that the controller is reset back to the Factory Calibrated Settings (FCS), (see Step 4) and restart the calibration process. Also, if the VAV box does not control the CFM within the maximum allowable percentage, normally within 10%, go back to Step 4 and restart the calibration process. For further information see the following: TCON126 (Micro Regulator Controllers and I/STAT) TCON147 (ASC MR-VAV-AX) TCON155 (ASC MR-VAV-X1) TCON165 (ASC MR-VAV-X2) Go to TCON Number and Title Cross Reference (with links) and download the TCONS above.

Issue When closing Continuum 1.9x SU (SQL 2005 Express engine on a stand alone workstation),  it shows MFC error message of ACCDataServices and the Windows Event Log shows AlmUtil.dll error message. Environment Continuum SU 1.82 and higher version. Cause There are 3 Windows Schedule Tasks which are created during the DBInitialization->Creation of the Continuum SU workstation. Some possible causes are: If these Schedule Tasks are missing The Windows Schedule Tasks cannot be executed due to that fact that the current login userID is different than the one setup for the Schedule Tasks The password is not correct Resolution Manually create these 3 Schedule Tasks in the SU Cyberstation Alternatively: Uninstall SQL engine, Continuum Reboot the Workstation Reinstall Continuum SU, create a new DB from DB Initialization. Verify these 3 Schedule Tasks are created as below: CS_Distn CS_hrly CS_Minute