Building Automation Knowledge Base

Issue New use for nviAirFlowReset in Heat mode on an Xenta 102-AX - change the flow setpoint based on heating demand. Product Line TAC Vista Environment Xenta 102-AX 2.12 and later Cause Xenta 102-AX 2.12 introduced some new features with heating flow control. Before it would only provide the Heating Low Flow setpoint any time the unit was in heat mode. With 2.12, the warmup max was introduced which allows reset of flow setpoints between these two values in heat mode. The nviAirFlowReset signal allows for altering the effective flow setpoint based on a looped back output of the heating demand. Resolution

Issue Advanced Communication Settings Video Product Line TAC INET Environment I/NET Seven rev 2.13 and above Cause Video tutorial for Advanced Communications in I/NET Seven rev 2.13 and above. Resolution This video is about advanced communication settings using I/NET Seven rev 2.13 and above. I/NET now allows you to define which communication port the NPR2000 or Xenta 527-NPR will use. You can also enable communication encryption and set up IP filters.

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 How to create a new database or purge a full SQL (i.e. it has hit the limit of 2G) Product Line TAC Vista Environment TAC Vista 4.X Cause Log data has filled the 2GB limit of the SQL database. Resolution How to purge a full SQL (if you've hit the limit of 2G) Before deleting the database or creating a new one: Check the $queues/insertevents and $queues/insertlogvalues folders in the Vista database. This folder may contain "queued" files waiting to be written into the SQL database. If these queues have significant amount of data stored as a result of the SQL being full, you may delete these files if the data is not needed. If the data is needed, it will be written to the new SQL Database when Vista starts. In some cases, the $queue folders may be so large that even creating a new database won't allow the Vista Server to run. If this is the case and the $queued items are not needed, delete them from their directories. If you find that there is an abundant amount of queued files it may be easier to delete them using DOS. This can be done by navigating using the "cd" and "cd.." command prompts to c:\TAC\Vista\VistaDb\$queues. There you will find \insertevents and \insertlogvalues. You can clear both directories using the "del" command. It is recommended to stop the SQL Server and DSS Writer before attempting to delete any queued files. You can stop the SQL Server by double-clicking on the icon in the task bar and choosing to "Stop". You can locate the DSS Writer by right-clicking on My Computer and selecting "Manage". Navigate to "Services and Applications\Services" directory and look for "TAC DSS Writer Service". Right click on this service and select Stop. If the data is not needed: Simply go to ...Microsoft SQL Server/MSSQL$TACVISTA/Data and delete the old database. Before doing so, you may need to stop the SQL Server.  Then following steps in "If the data is needed" section below. If the data is needed: The simplest way to get a fresh DB is to create one. This is done using TAC Vista SQL Setup which can be downloaded from the Buildings Business Extranet: Global. Make sure that you download the SQL Setup for your Vista product version. In the Vista SQL Setup program, select your SQL Server - pcname\TACVISTA, Chose Windows Authentication if Vista is managing the Database (recommended in the Vista Install), "Login", enter the name of the database (perhaps "NEWtacdatalog" to be created, and select the login pcname\TACA_pcname, and "Create". This will create a new database to which you can now point the Vista Server. In Vista Server Setup, under the SQL Tab, change the database to this newly created database, click "OK". You can keep the old database to export for viewing or if you plan on upgrading to SQL Enterprise and merging the data in the future.   NOTE: Sometimes when this is done without first detaching or deleting the database from the SQL, the DSSwriter or TACA user stops working. Detach/Delete the database with SQL Management Studio Express and reinstall the system to solve this.  

Issue TAC Vista Uninstall Process fails. Environment TAC Vista Server Installation Cause During the uninstall process, a key in the registry does not get deleted that should.  This flags that the application is already installed, so the uninstall process won't proceed.  It is also impossible to use the "Add/Remove Programs" wizard to uninstall the application. Resolution What needs to be done when this occurs is to open the Registry Editor (Start > Run > regedit) and do the tasks described below: NOTE: Make sure that you do a backup of the registry since modifications in the registry can make your system unstable. Also make sure that you have a backup of the TAC Vista database and other important project files. Vista Server (You should perform this step if you can't uninstall the application from the control panel) Delete the following registry key: HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\{639465AE-9BAF-4D29-B824-D8BFD8615070} ToolPack (You should perform this step if you can't uninstall the application from the control panel) Delete the following registry key: HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\{5FFB2771-0543-42A6-AF2B-61FE41D880D4} These registry keys are the same regardless of versions (TAC Vista IV and later), just to prevent parallel installation of different TAC Vista versions. When those keys have been deleted, manually remove the program folder. (Default "C:\Program Files\TAC\TAC Vista X.X.X")

Issue ZBuilder will not open on certain commissioned Xenta 121s in Lonmaker. It will open on others in the same network. Environment ZBuilder LonMaker Cause Incorrect or corrupted configuration parameters prevent the ZBuilder plug-in from opening on specific Xenta 121s. Resolution Right-click on the device in LonMaker and choose Browse Take a screen capture of the various settings that will need to be re-entered Re-commission the Xenta 121 controller with default values (this will erase any configurations that have been made) ZBuilder will now work correctly. Re-enter any previously configured parameters

Issue Can not limit the setpoint offset high and low limits when using "offset" mode in the STR-350. Environment STR-350 LonMaker Cause When viewing the controller data in degrees Fahrenheit, an offset must be applied to each value. Resolution In the plug-in, set the STR to use setpoint offset mode instead of absolute setpoint. Browse the controller with the LonMaker browser. Scroll to nciSetpointHigh and nciSetpointLow. Start from 32 and set your two NCIs as desired. For example:  If you wanted your occupant to have the ability to adjust ±5°F, set nciSetpointHigh to 37 and nciSetpointLow to 27.

Issue Vista 5.0.3 Graphics Editor crashes when you right-click on a graphics page in Workstation and click edit. Here is the error message: Could not load file or assembly 'TAC.Interop.TacosOI, Version=5.0.0.0, Culture=neutral, PublicKeyToken=null' or one of its dependencies. The located assembly's manifest definition does not match the assembly reference. (Exception from HRESULT: 0x80131040) FileLoadException at TAC.Graphics.Windows.Vista.VistaSystemProxy.Create(String server, String user) at TAC.Graphics.Editor.EditorApplication.CreateApplicationForm(ReadOnlyCollection`1 commandLine) in C:\TAC\VistaSw\V5030\Graphics\Editor\EditorApplication.cs:line 90 at TAC.Graphics.Editor.SingleInstanceApplication.<>c__DisplayClass3.b__1(Object splashFormSender, EventArgs splashFormEventArgs) in C:\TAC\VistaSw\V5030\Graphics\Editor\SingleInstanceApplication.cs:line 79 at System.Windows.Forms.Form.OnShown(EventArgs e) at System.Windows.Forms.Form.CallShownEvent() at System.Windows.Forms.Control.InvokeMarshaledCallbackDo ThreadMethodEntry tme) at System.Windows.Forms.Control.InvokeMarshaledCallbackHelper(Object obj) at System.Threading.ExecutionContext.runTryCode(Object userData) at System.Runtime.CompilerServices.RuntimeHelpers.ExecuteCodeWithGuaranteedCleanup(TryCode code, CleanupCode backoutCode, Object userData) at System.Threading.ExecutionContext.RunInternal(ExecutionContext executionContext, ContextCallback callback, Object state) at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state) at System.Windows.Forms.Control.InvokeMarshaledCallback(ThreadMethodEntry tme) at System.Windows.Forms.Control.InvokeMarshaledCallbacks() Environment Vista Workstation 5.0.3 TAC TGML Graphics Editor 1.0.3 Cause An error occurred at installation and the Graphics Editor must be removed completely and reinstalled. Resolution Shutdown the Vista Server and Workstation. Uninstall the TAC Graphics Editor 1.0.3 from the Control Panel of the PC. Delete the entire C:\Program Files\TAC\GraphicsEditor directory that is left behind from the un-install. Download the TACGraphicsEditor103.exe from The Exchange. Re-install the TACGraphicsEditor103.exe

Issue Procedure for correcting duplicate LON device node numbers in a Niagara R2 UNC station Environment Niagara R2 UNC station Cause Occasionally, when a LON device has been removed from use at one site and installed at another site, the previously configured LON subnet and node number can be the same as an existing device in the new installation. The problem typically manifests itself when attempting to learn and commission the new controller using the Workplace Pro. Resolution Use the following steps to correct the problem. Open the "Lon Device Manager" from the right-click menu of the LonWorks Service. Click "Find" to get a list of all the LON controllers under the UNC. An error message will be displayed indicating that a device with a duplicated subnet and node number has been detected. Right-click on one of the devices that has the duplicate address. If no right-click menu is displayed, right-click on a different device with the same subnet and node number. From the right-click menu, select "Properties" then select the "General" tab then select the "Engineering" tab. In the "Node State" pulldown list, select "Unknown". Change the node number, displayed in the "NodeID" box, to a value that is not currently used. Click the "Apply" button to save the changes. Click the "back-arrow" button to return to the Device List screen. Reselect the device just changed then click the "Commission" button. In the pop-up window that is displayed, verify that the Neuron ID of the device is correct then click the "Apply" button. Wait for the commissioning process to complete. 10. If additional devices are shown with duplicated node addresses, repeat steps 3 through 9 for each additional pair of duplicate addresses.

Issue The Xenta 102-AX PWM_1 (one output PWM) setting is a true duty cycle output.  How can you control a PWM transducer? Environment Xenta 102-AX, Universal Output 2 PWM Transducer Cause The problem is that 0% on a duty cycle output is no pulse at all and 100% is continually on. All electronic transducers must have some pulse to control it to 0%, often 0.1 seconds. Many of them will not accept a continually on signal as 100%. Values for two of the most industry common PWM transducers are detailed below.  Calculations provided can be used to calculate any required duty cycle limits. Resolution This example assumes a PWM transducer that requires a pulse width modulated signal between 0.1 and 5.2 seconds. Set the stroke time to a value slightly larger than the required maximum pulse. UnivOut2_Object.SCPTdriveTime = 5.3 seconds Set the minimum range to a percentage of the drive time that will result in a 0.1 second pulsed output. UnivOut2_Object.nviUnvOutput2.SCPTminRnge = 1.885% 0.01885 * 5.3 = 0.099905 seconds Set the maximum range to a percentage of the drive time that will result in a 5.2 second pulsed output. UnivOut2_Object.nviUnvOutput2.SCPTmaxRnge = 98% 0.98 * 5.3 = 5.194 seconds Set the minimum pulse to 0.1 second. A 0-100% signal on Universal Output 2 will now modulate the pulse width between 0.1 and 5.2 seconds. This example assumes a PWM transducer that requires a pulse width modulated signal between 0.1 and 25.6 seconds. Set the stroke time to a value slightly larger than the required maximum pulse. UnivOut2_Object.SCPTdriveTime = 25.7 seconds Set the minimum range to a percentage of the drive time that will result in a 0.1 second pulsed output. UnivOut2_Object.nviUnvOutput2.SCPTminRnge = 0.39% 0.0039 * 25.7 = 0.10023 seconds Set the maximum range to a percentage of the drive time that will result in a 25.6 second pulsed output. UnivOut2_Object.nviUnvOutput2.SCPTmaxRnge = 99.61% 0.9961 * 25.7 = 25.59977seconds A 0-100% signal on Universal Output 2 will now modulate the pulse width between 0.1 and 25.6 seconds.

Issue "Can not initialize lontalk stack" message in LonMaker Environment LonMaker NL220 LonWorks Plug 'n Play Cause The PC card is either "asleep" or has gone bad. NL220 must be "Run as administrator." Resolution Run the program as Administrator by right clicking on the executable and "Run as administrator" from the Start Menu. If the error persists proceed. Open the LonWorks Plug 'n Play from your PC's control panel. Choose Diagnostics and click Test If you get an error message, then the card is "asleep" or bad. Go back to the plug and play and change your NI Application to something other than what it is currently on. Click apply. Then choose diagnostics again and repeat the test command. It should now be working. If not, your card is bad. Remember to change your NI application back to the correct one for your network.

Issue "Failed to Initialize Necessary Resources" error message when opening ZBuilder: XIF file Environment Xenta 121 ZBuilder Cause One way this error message can occur is if a Xenta 121 device has been added, but not associated with an XIF file. Resolution If this is a classic network, then you can browse to the C:\Program Files\TAC\TAC Vista x.x.x\$ini\ directory to find the XIF file which corresponds to the 121 you are using (HP or FC). In an LNS system you should check the template of the device to make sure it has the proper XIF file associated with the template.  

Issue An easier way to set all Xenta 102-AX dampers to maximum airflow setpoint Environment Xenta 102-AX rev 2.1.2 Cause Test and Balance often requires all Xenta 102-AXs open to max flow. It is preferable to not accomplish this by opening the plug-in, placing each damper in override and fiddling with it until airflow reads max flow. You could use nviManOverride, but at rev. 2.12 none of the flow options worked. Resolution The 102-AX was enhanced along the way with a better use of nviSpaceTemp. Before the enhancement, if that signal was bound, the controller always honored that input regardless of its value. The enhancement allows you to set the value back to invalid (e.g. 621.8°F) and then the controller will honor the hardwired space temp input. Next time you want to force them all, bind nviSpaceTemp on all of them from one SNVT output. Control it to some value above their cooling bands and they will all open to cooling high flow.

Issue What is the part number to order just the back plate for an MNB-300 or MNB-1000? Environment MNB-300 MNB-1000 Cause Replacement part number. Resolution The part numbers are: MNB-BASE-300 MNB-BASE-1000

Issue When attempting to bind to SNVTs from a LON Field Server device a service_type_error appears. Environment Field Server UNC network management tool Cause The UNC network management for bindings is set to the "standard" service type (Unacknowledged) by default. Resolution The Field Server device requires something other than the "Unacknowledged" service type. Either change the Field Server service type to Unacknowledged or change the default service type in the UNC network management tool to match their type. Review the Niagara LonWorks Integration Guide for more details.

Issue When trying to connect to a station running on a UNC an intermittent error appears: "Cannot Open station. Service Unavailable (503)". Environment Niagara UNC Cause This error indicates that the embedded UNC's web server is currently unable to handle the request due to a temporary overloading or maintenance of the server. In this case, it means that the web server is refusing the connection due to a thread overloading condition. More specifically, the UNC is out of web service threads. Resolution Starting in Niagara build 431, a line item was added to the system.properties file that sets the maximum thread pool size for the web services. Using the admin tool open the UNC's system.properties file. From the drop-down menu, select Admin Tool > Host > Edit File > System Properties.  Locate the line that defines the webServer.threadPoolSize. Increase the webServer.threadPoolSize from the default value of 15 to 30. Save the changes to the file and re-boot the UNC to initialize the new thread pool size.

Issue Upgraded a UNC-510 to Niagara version 522 and when trying to run the station, the following error appears: "Cannot load BACnet MSTP Driver" Environment Niagara version 522 UNC-510 Cause The upgrade process does NOT change the drivers.properties file. Resolution The error indicates the line: driver.mstp=tridium.nre.vxworks.mstp.VxWorksMstpDriver is missing from the driver.properties file. Copy the drivers.properties file from a UNC-520 running version 522 or higher or manually add this line into the drivers.properties file. Note that the UNC-510-2 has a maximum baud rate of 19.2 k for a BACnet MS/TP network.

Issue Are you trying to implement Groups within Groups and it is not functioning as programmed? Environment I/NET Access Cause The term “Groups within Groups” is where a user has access on one group e.g. 5-7 Mon-Friday but needs to get in on a Saturday but the application is permanent. So a Secondary schedule would not be applicable here, since this is only for a temporary period. Resolution To create a “Group within Group” application the following steps need to be followed: Go to Access Doors, select the door or doors that will have this Saturday schedule so that the group when created can access this schedule. Once created, exit out of this editor and go to Access Groups. Create a group that has access to the doors that will have access on the Saturday Schedule. All other doors need to be set to Unselect, close this editor. Now go to the main group that this group will be part of to create the “Groups within Groups” schedule. Modify the group and select Doors/Groups and now select the group that has the Saturday schedule on it. Keep in mind that the only schedule for the doors would be the Group Schedule; the Primary Schedule should be set to Unselect. If a Primary Schedule is selected, then it will take precedence over the Groups within Groups Schedule and would negate the application.  

Issue All Remote Clients share network functions with the server including auto-DCU save. Environment I/NET site with Filemaster and Remote Clients Cause Equalization Resolution Not only is the network configuration saved in the SQL database, but also the network functions. That means the server and ALL remote clients will check every controller on every link in the system and save any that have changed beginning at 3:15 AM everyday. If you have many hosts and many controllers, it could create quite a bit of network traffic. You might consider turning on auto-save on Fridays or once a month or some other strategic interval.  

Issue "Needs to be Commissioned" messages and Asterisks will not go away in Vista Classic Network Environment Vista Classic Network Cause The inability of the Asterisks and "Needs to be commissioned" to go away after a download to the controllers can be a sign that your LonWorks Network object has become corrupted. Resolution Create a new LonWorks Network object and a new port object. Move the Xenta and LonWorks groups under the new Network object. Delete the old LonWorks Network object. Move the new Network object under the existing port and rename the network to the old name. Commission and download to all of your controllers.

Issue TAC Xenta 121 Plug-in, Checkbox selections by mistake. Environment Xenta 121 Plug-In ZBuilder Cause Checkboxes in ZBuilder are sensitive for mouse click “outside” the checkbox.  Resolution When clicking on the same row as the checkbox might trigger the checkbox to be checked/unchecked by mistake. Changing the value of a checkbox might change the physical I/O configuration list, and the functionality of the TAC Xenta 121 device. This could happen by mistake if a user clicks the plug-in window to activate it or bring it to focus and might not be aware that the plug-in trigger this event as a checkbox selection. Be aware of this and double check your configuration settings and the physical IO configuration list before exiting the TAC Xenta 121 plug-in.