Building Automation Knowledge Base

Issue The priority attribute was not specified as configurable. (Subsystem: NS Connections, #11) lcaErrConnPriNotConfigurable An attempt was made to modify the priority attribute; that attribute was not specified as configurable. For network variables, the priority keyword may be included as part of the connection information in the Neuron C variable declaration.  The config and nonconfig keywords specify whether the priority designation can be modified with a network management tool. The default is config. The priority keyword affects output or polled input network variables.  Please refer to the Neuron C Reference Guide for more information. Environment LonMaker Cause Applying a connection description to a new binding that causes a connection error, such as applying a connection description with the priority attribute set to a connection that does not support it, causes this error message to be displayed. Subsequent attempts to add any connection with the default connection description will result in the same error message. Resolution Exit LonMaker Re-open the LonMaker tool.  Then add the connection.  Alternatively, explicitly select a valid connection description other than "Default."

Issue Setpoint button may break if forced outside of movement range. Environment STR-106 Cause Excessive force used to turn setpoint button outside of movement range. Resolution Report faulty unit through Warranty Claim System. Replacement button carries component no 372069900.

Issue Xenta 104-A ships from factory with a resistor on terminals 7 and 8 Environment Xenta 104-A Cause Terminal 8 is input U1, which is used by the controller for outside air temperature in the economizer calculation. Resolution The resistor is 1.8kΩ A temperature sensor on U1 would be a 1.8kΩ thermistor, if this input was being used. The resistor is a place holder to keep the unit out of economizer during initial setup if a thermistor is not going to be used.

Issue Offline Xenta 401 Not Generating Alarms Environment Xenta 401 Xenta Group Cause Xenta Group Master is offline Resolution Determine if the Group Master is offline In the Vista System Plug-in TAC Network Pane, the Xenta Group Master will be the only controller in the Xenta Group that is underlined Determine if this controller is offline in LonMaker or NL220 If the group Master or any of the Xenta devices in that Xenta Group show an " * ", you will need to download application and parameters Change the Group Master to a more reliable controller Determine which controller in the Xenta group has the least amount of potential traffic In the Vista System Plug-in TAC Network Pane, Right-Click on this device and select "Set as Master". Download Application and Parameters to any device that shows and " * " after this change.

Issue Get "Invalid Data" error message when trying to change an Xenta Trendlog's setting from Man-On to Auto in Vista workstation. Environment Windows 2003 & XP (confirmed - possibly other operating systems). TAC Vista Workstation/Server 5.1.4. Cause Unknown. Resolution Upgrade to TAC Vista 5.1.6. This issue has been resolved in this version.

Issue Have (10) i2885-V-WL (Wireless Infinet) which need to be changed to regular RS-485 hard-wired (Infinet). How is this done? Environment CX9680 i2885-V-WL Cause Have (10) i2885-V-WL (Wireless Infinet) which need to be changed to regular RS-485 hard-wired (Infinet). How is this done? Resolution Simply flash any Infinet II –V VAV Controller from a wireless Infinet to a wired Infinet II or even to a wired BACnet or Wireless BACnet –VAV controller in just one step. The –V VAV Series are the first Andover Continuum controllers to allow a change in the controller operating system with a simple firmware upgrade. The hardware model number doesn't change. For example, an 866-V will always be an 866-V, but through software that same 866-V can change in firmware from an i2866-V to a b3866-V-WL with one upgrade in the field. Also, the i2 -V controller firmware type can be identified using two onboard LEDs (i.e. wired vs. wireless, BACnet vs. Infinet). Notes: The Roam-IO2 cannot be used to flash a wireless controller to a wired one. The Roam-IO2 cannot communicate to a wireless controller. Non -V controllers should not be flashed in the field. Trying to do this runs the risk of turning the controller into a brick.  To flash non-V controllers, send them to repair.

Issue Cannot upgrade the OS of i2 controller with the error message of "Controller Type Mismatch" . Environment NetController (bCX9640) InfinetController (i2xxx) Cause When upgrading the i2 controller to the latest version AND the version of NetController (bCX9640) is couple of versions older than the i2 controllers new version. Resolution Upgrade the NetController to the latest version of OS first, reload the NetController, reload the i2 controller and then upgrade the i2 controller to the latest version.

Issue When installing the site .plf license, Privilege Administrator states it is missing Developer Extension and terminates the installation. Environment Privilege Administrator / Licenser Developer Extension PLDevExt.pde Cause An error occurred during the installation of Privilege License Software where the Developer Extension was not executed. Resolution Manually execute the Developer Extension. Navigate using Windows Explorer to ..\System32\PLDevExt.pde Double click the PLDevExt.pde Restart Privilege Administrator Install site license by double clicking your .plf file Verify the licensed  TAC software starts successfully

Issue Documentation on the MSC-V-400 Microsmart controller. Environment Microsmart controller MSC-V-400 Cause n/a Resolution Click here to view a datasheet on the MSC-V-400.

Issue A jobsite of MNL controllers was done with WorkPlace Tech 4.x.  The original databases are no longer available.  Can they be uploaded with WorkPlace Tech 5.x and will the upload convert them from 4.x to 5.x? Environment WorkPlace Tech versions 4.x and 5.x MNL controllers Cause Loss of original controller databases Resolution Uploading a MNL controller's program does not change anything within the controller.  Only downloads do. If a MNL controller was programmed with WorkPlace Tech 4.x and is uploaded with WorkPlace Tech 5.x, the uploaded file can only work with version 5.x.  If the resulting file is then downloaded to the same controller, the program version in the controller will then be at 5.x.  It will no longer work with 4.x.

Issue RAM is unable to read the Sigma alarm record file. Environment Remote Alarm Manager 2.0 RAM 2.0 Sigma Alarms Cause Corruption has occurred in the files stored in the "Runtime Folder" Resolution Stop the Remote Alarm Manager services either via the "Services" window, or by selecting to change the RAM Computer Configuration, and when asked if you want to stop the services, answer yes. Locate the Remote Alarm Manager "Runtime Folder" and delete all of the files in this folder, make sure that the empty folder is left. The location of the "Runtime Folder" could vary from PC to PC and will be dependent on the operating system and installation, so it is best to use the "Search" function to locate it. Restart the Remote Alarm Manager services and test its operation.

Issue Incorrect image name is displayed in the download window. The IC-UNIFACT image is displayed in the download window instead of the IC-SNP image where Unifact URC1201/2201 controllers are installed on site. Environment Sigma IC and IC3 controllers Cause The site has Unifact 1201/2201 controllers integrated to an IC3-SNP, when the image is to be downloaded, the image file that is displayed is for an IC3-Unifact. Resolution IACs and Unifact 1201/2201 controllers use the IC SNP. Unifact Pro controllers use the IC UNIFACT. In this example the controller sub type was configured as IC UNIFACT when the correct setup should be an IC SNP. Only the specific image file will be displayed in the download window as determined by the controller version set in the controller setup.  1. Select the correct IC in System Setup > Network and Devices > Controllers as shown below and save. 2. Goto System Diagnostics > Options > Download Files. The correct image will appear.

Issue If having a Vista network and a OPC server installed on one Vista server can a OPC client connecting to the OPC server read values from another Vista server in the network?  Environment Vista 5.1.6 OPC server 1.6.2 Cause No it is only possible for the OPC client to read values on the Vista server where the Vista OPC server is installed. This is to avoid a lot of communication between the Vista server nodes which is pretty slow. Resolution Install a OPC server on every Vista server.

Issue TAC Xenta 300, How many I/O modules   Environment Vista Xenta Cause Trying to connect more then 2 I/O modules to a TAC Xenta 300.   Resolution Please look at TAC Xenta 300 Specification Sheet Always check the The Exchange Download Center for a more current release.

Issue How can the Microsmart Service in a Niagara R2 UNC be optimized for better performance? Environment Niagara R2 Microsmart Service Cause Slow / sluggish performance Resolution Keep the Poll Always count at the recommended level of 250. Observe the averageExecuteTime from the service's Poll - Status tab and increase the cycleTime (Poll - Config tab) to match plus one second.  This prevents poll overruns. For every Microsmart point shadow object, the setting minimumPollInterval should be reviewed and increased where possible from the default of 1000 ms.  For example, a shadow object displaying a space temperature can have its minimum poll interval increased anywhere from 30000 to 60000 ms. 

Issue When the mouse curser is hovered over bang in Continuum Explorer, the tool tip is not indicating what is wrong. Environment ACX57xx Cause Windows 7 is inhibiting tool tips on Bang indicators. Resolution The following registry entry is used to inhibit or expose the Tool Tips on a Mouse Over Note:  Always backup the registry before making any changes. HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Explorer\Advanced Data Type: REG_DWORD [Dword Value] // Value Name: ShowInfoTip Modify/Create the Value Name [ShowInfoTip] according to the Value Data listed below. Value Data: [0 - ShowInfoTip Disabled / 1 - ShowInfoTip Enabled] Exit Registry and Reboot following changes to the registry.

Issue MNL-V3 application configured with an external actuator of 390 seconds drive time shows an excessive setpoint deadband of almost 20% of control range. Environment MNL-V3 controller Cause Unknown - Issue has been reported to product management. Here is an application fragment showing the issue.  Note the 390 second drive time. Resolution Use the following application fragment in your application to eliminate the excessive >22%) deadband. Here is an application fragment showing a suggested workaround:

Issue According to the datasheet, there should be a DIP switch for output voltage adjustment for Veris CO sensor. But some of them haven't such DIP switch. Environment Veris Sensor Cause There are several models for Veris CO sensor. For example, GWVAS is the wall mount sensor with voltage output signal, while GDMAS is the duct mount sensor with current output signal. The sensor with current output signal hasn't such DIP switch for voltage output. Resolution This model of product hasn't such DIP switch.

Issue Vista is very slow after a TGML graphic is opened, it takes like 30 seconds to open a small folder. Environment Vista 5.1.6 Cause A Loytec NIC USB used as the Lon interface is not online because the engineers computer is not connected to the Lon network. But the Xentas and Lon network under the Lon interface are online in Vista for some reason. So Vista tries to read the values from the Xentas and this makes Vista hang for periods of time. Resolution Create a new Lon Network interface Drag and drop the Lon network to the newly created interface Drag and drop the Lon network back to the original interface Now the Xentas show up as offline

Issue Where can I information on accessories for a job that needs to meet a UL-864 (UUKL) project specification? Environment UL-864 UULK/UUKL project requirements Cause Need various approved accessories to meet a UL-864 job specification. Resolution Due to regulatory issues, all current UL-864/UUKL information is published in the latest version of the TAC I/A Series MicroNet BACnet Smoke Control Systems Manual, F-27419.  Always refer to an online version of that manual for the latest approved information.