Building Automation Knowledge Base

Issue Vista receives an I/NET transaction from a Xenta 527 as an alarm but not as a transaction Environment TAC Vista Workstation Alarm Queue Event Log I/NET Transactions Xenta 527 Cause If your time stamp is in the future, the events window (transactions window is really a filtered events window) will not display them but for some reason alarms come through. Resolution Open the Xenta 527 from Internet Explorer. Open the Events folder under I/NET. Look for the transactions. Note the date and time. Make sure the date and time in your 527 are set correctly and that the time zone is right in regional settings. Even though the SCU time stamps the transaction, the 527 shifts the stamp according to it's own settings.

Issue Displaying “??781”, “??782”, ”??787” or similar values. Environment Vista Workstation Cause The "??781," "??782," "??787" are in fact a Vista error codes, however, these codes are not documented. We have used the following approaches to get the device talking. Resolution In Vista right-click and upload parameters to the devices. Right-click > Properties > XIF File, browse in the XIF file to the Vista database.  In LonMaker Recommission the devices and Update the Vista Database. Try to delete the device from LonMaker, update the Database then reinstall the device. There is not a known proven method; these are things to try. Observe the results of the steps and please call if you are unsuccessful at seeing a change

Issue How to tell if an AC-1 Plus card reader has been tampered with Environment AC-1 Plus card reader Cause Knowing whether a card reader has been tampered with is an important security measure. Resolution Set up an InfinityNumeric. Name it anything. Set its IOU number the same as the entry IOU (or exit IOU) of the door and set the channel number to 6. Set the direction for IOInput. The value of the numeric represents the status of the reader. 0 = Normal 1 = No Reader Present 2 = Reader Voltage problem NOTE: This only works on the AC1Plus access control module.

Issue What parameters are used to regulate the speed of the LON trunk in a Niagara R2 integration? Environment Niagara R2 Cause Configuration of LON devices create unnecessary network traffic from changing values. Resolution There are two settings that can regulate LON traffic: 1. In the LocalLonDevice properties, the maxSendTime parameter specifies the maximum amount of time the local lon device (which is the UNC station) waits to send out a value that has not changed. 2. Also in the LocalLonDevice Properties, the minSendTime parameter specifies the minimum amount of time that must elapse between network variable updates for values that are changing rapidly. Consult the Niagara LonWorks Integration Guide for more information.

Issue With the MNL VAV controllers, does the integral damper motor perform a self calibration during which it cycles fully closed or fully open? Environment MNL VAV controllers Cause When main power is applied to the MNL VAV controller, the damper motor will cycle to a full closed position. Resolution Automatic Calibration: An internal calibration feature automatically synchronizes the actuator position whenever the actuator is commanded to the full closed (0.0%) or full open (100.0%) position by continuing to drive the actuator in the requested direction for a time period of at least one additional complete full stroke drive time. If during this “end of stroke” drive period the Input value changes to a value within the control range, the output drive to locate the true end of stroke operation is terminated. Drift Compensation Enable: Setting the Drift Compensation Enable configuration property to On (1) compensates for floating actuator mechanical drift whenever the actuator remains at the full open or full closed position for extended periods of time. Drift compensation is done by periodically driving the actuator in the commanded direction for a time period derived from the Drive Time assigned. Drift compensation does not occur whenever the actuator is within the actual control range between full open and full closed. Refer to the Floating Actuator Object in F-27254 for additional information.

Issue Use of Universal Input UI1 on a Microzone II as a pulse counter requires an external pull-up resistor. Environment Microzone II Cause High speed count input required a 10 K ohm shunt resistor. Resolution When UI1 on the Microzone II is used as a Pulse Counter, an external pull-up resistor must be added between UI1 and the 5.1 VDC output terminal. The resistor shall be a 10 K Ohm, 1/4 Watt or higher, +/- 10% tolerance or better. Universal Inputs UI2 - UI8 do not require the resistor.

Issue Can a Master schedule in a Niagara R2 Enterprise server station trigger slave schedules residing in a PollOnDemand object in a UNC station? Environment Niagara R2 Enterprise Server UNC station Cause To trigger slave schedule, be sure to link a slave calendar to the slave schedule. Resolution Schedule objects do not care that the folder is PollOnDemand. Only driver points (ie. shadow objects) will be affected by the fact that their parent is a PollOnDemand container. Be sure that there is a slave calendar linked to the slave schedule in the same station. Calendar to schedule links do not work across an external link.

Issue Installing Vista 5.0.x on Windows Vista and it failed. Environment Windows Vista Vista 5.0.x Cause Vista 5.0.x is not compatible with Windows Vista Resolution First, uninstall anything Vista 4.3.x to 5.0.x installed including Microsoft SQL and Microsoft Visual Runtime C++ stuff. If they won't all uninstall, you may have to do a system restore to some point previous to the TAC Vista install. Next remove the c:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\Data assuming that TAClogdata.* is there. It might be in MSSQL.2 or other. You should then be able to install.  

Issue Vista WebApps install incorrectly claiming that IIS is not installed Environment Windows IIS Cause On some custom configurations of Windows we have seen where Internet Information Services (IIS) is running on another driver letter and Vista WebApps is not finding the IIS operating directory and claiming that IIS is not installed. Resolution Open the Registry Editor (Start > Run > regedit) Navigate to HKEY_LOCAL_MACHINE\SOFTWARE\MICROSOFT\InetStp\ for the PathWWWRoot key. This registry key should show the directory that IIS is using for storage of the web server. (Default is C:\inetpub\wwwroot\) Correct the registry key with the correct path and the install should now succeed.

Issue A Niagara R2 UNC-520 time clock cannot maintain proper system time.  It is losing approximately 1 hour daily. Environment Niagara R2 UNC-520 Cause Inadvertently calibrated with an incorrect time clock. Resolution This issue can be corrected in the field.  For details, read TPA-RKFD-08-0003.00 "Slow Time Clock on UNC-520-2 and UNC-520-2-N" on The Exchange Download Center.

Issue What is the Analog to Digital Output resolution of the MNL controllers? Environment MNL Controllers Cause Analog/Digital conversion resolution Resolution The MNL controllers (with the exception of the MNL-800) have a 10-bit equivalent UI resolution and an 8-bit output resolution. The MNL-800 has a 12-bit equivalent UI resolution and an 8 bit output resolution.

Issue TAC Vista 5.1 installation hangs on installing Video Functions. CPU is at 100% and the installation will never finish. Environment Vista Installation Cause It seems like the MSI process for the Video components sometimes gets into a loop. Resolution Start the installation and let it run until it “hangs" Go into Task Manager-Processes and end the process “msiexec” that is using all the CPU. The installation should proceed and everything should be installed correctly

Issue On a computer, when booting up WorkPlace Tech, this error message appears:  "License date is newer than computer date". Environment WorkPlace Tech Cause Date change on host pc operating system prior to licensing date Resolution WorkPlace Tech keeps track of the time and date it was last accessed to prevent back dating to defeat the license. To regain access, run the Purchase WorkPlace Tech software icon, purchase the next available renewal and send the renewal file to Customer Care to obtain the unlock code.

Issue A previously functional MNL controller is not communicating and the RED LED is on solid. Environment MNL controllers - all revisions Cause Internal hardware failure Resolution The solid RED LED indicates that the LON processor Neuron application is not running. This is a hardware failure and is not field repairable. Replace the controller.

Issue Xenta 913 is communicating to BACnet MSTP device fine (shows online status), but no data will show up on values page.  All of the data will be zeros.  XBuilder does not give you an error or warning of this problem. Environment Xenta 913, Xenta 731, Xenta 511:B XBuilder Cause When using BACnet or Modbus in the 913/731/511:B you can not name the Modbus or BACnet port the same name as any of the devices below it. For example, if you name your BACnet MSTP port "RTU" and then name the slave device "RTU" the device will show an online status, but you will not see any information on a values page. All of the data will be zeros.  By default, XBuilder attempts to prohibit this from happening by adding a numeric to the end of a new device.  So by default the device name would be "RTU 1" and you would have had to rename it to "RTU." Resolution Name the slave device below the BACnet or Modbus port something different than the port itself. 

Issue The requested service cannot be provided in the current management mode.  Environment NL220 ZBuilder Xenta 121 Cause Attempts to download a ZBuilder configuration to a Xenta 121 on a network that is not "attached."  This is the incorrect management mode to perform a download. Resolution Make sure the network status is onnet and attached.

Issue When opening ZBuilder "Invalid OLE collection index(Subsystem: LNS, #15)" pops up a hundred times – seems to be one for each configuration value.  Exmucpt, exmappop, etc.  Environment Zbuilder Vista LNS Cause unknown Resolution Restoring a LonMaker backup should fix the issue.

Issue A Continuum database setup for IE. version 1.81 will only support Continuum software version 1.81. Environment Continuum all versions Cause Attempting to use different versions of the Continuum software on a Continuum database Resolution Using Continuum software version IE. 1.9 would not be able to access a database setup for ie... older Continuum version 1.81. This is true for all versions of Continuum. The Continuum software and database must be of the same version.

Issue Promoting a stand alone client from a host to an equalized client and it does not work. The snapshot is done on the Filemaster but the client would not connect. When we attempt to connect we receive a message stating that "the Filemaster snapshot is not ready and to try again in a few minutes" Environment Equalization Promotion from Stand Alone Host to Equalized Client in 2.40. Cause I/NET 2.40 has a problem promoting an equalize client. An indication of this problem is a perpetual “Pending” message seen at the Filemaster configuration editor. This state is caused when promoting an equalize client using the Filemaster’s IP address and not the host name. Resolution Once an attempt is made using the IP address and not the host name. The client’s snapshot is in some corrupt state and must be deleted. To correct this problem perform the following on the client From the Filemaster make sure the 'Pending' client is dropped from the Equalization list  Demote the client if not already demoted. Delete snapshot located on the Client’s “unc” folder. The "UNC" is located in C:\ INET Seven Data\ MSTR\unc Promote the client using the host name for the Filemaster and not the IP address. This should correct the problem

Issue Right-click on a device in LonMaker and choose "Browse...."  This should launch the LonMaker Browser.  Instead of launching, an error pops up that says "Unable to find a matching plug-in for device, use network properties to register the correct plug-in." Environment LonMaker Cause Echelon LonMaker Browser is a plug-in that must be registered like any other.  If it has not been registered properly, it will need to be registered, or re-registered. Resolution In LonMaker, choose the LonMaker toolbar menu Go to Network Properties > Plug-In Registration Tab Find "Echelon LonMaker Browser (Version X.X)" either in Already Registered or Not Registered window. Double click the plug-in, which adds it to the To Be Registered window. Click Apply or OK to register to plug-in. Launch the LonMaker browser again.