Building Automation Knowledge Base

Issue Running Equalization on a PC that has SP4 (Service Pack 4) and the clients are unable to connect to the File Master Environment PC that has SP4 Cause There is a protocol setting that needs to be enabled for this to occur. Resolution The following steps show the path to MSQL Server where the protocol resides and how to get it enabled. Open Windows Explorer and go to C:\Program Files\Microsoft SQL Server\80\Tools\Binn\SVRNTCN.exe. Double click on this file and enable the following files, Named Pipes and TCP/IP. Apply the changes and then close the editor SQL Server Network Utility.  

Issue UNC was upgraded to R2 release 529 from an older version and when the station was started, the following error message was displayed in the Standard Output Window: ---------- Station Starting:   THU MAR 26 14:43:09 2009 ---------- Tridium Niagara Station, r2.301.529.v1 [GafbBldg857] ERROR: Reading FlexSnvtTempSetpt [3928] FlexSnvtTempSetpt#link: 60 *************************************************************** FATAL: Cannot boot station from sns java.io.UTFDataFormatException   Environment UNC-520 with release 522 or 529 software installed. Cause Incompatibility in the FlexSnvtTempSetpt object between the release 514 and release 529 versions of the jar file. Resolution The best way to correct this issue is to perform a manual upgrade of the existing version 514 station. Use the release 514 WorkPlace Pro "Admin Tool" DbAdmin function to backup the running station and get the station as a .sns file to the computer. Use the DbAdmin function to convert the station from .sns to .xml. In the release 529 installation folder, use the AdminInstall command to start the release 529 version of the NiagaraD service. Copy the station folder containing the station to be upgraded from the release 514 stations folder to the release 529 stations folder. Start the release 529 AdminTool and open the Localhost. Highlight the station to be converted. Select the DbAdmin tab and use the convert local function to convert the station from .xml to .sns The converted station is now ready to be installed into the UNC that has already been loaded with I/A Series R2 release 529 software. This same procedure can be used to convert a 514 station to 532 by substituting release 532 for the release 529 references. above.

Issue Using a large number of values in a Vista Report Environment Vista Reports with more than 100 individual values (not trends) Cause While Vista Reports are mainly used for reports on trend logs, it is possible to display values from your Vista database. If you elect to link to a large number of values in your report it is common to receive time out errors when it tries to validate the links or polls for the entire list of values.  Resolution The way to avoid these errors and speed this process up is to change the Watch Setting property to either WATCH or ALARM for each value in your report. This will instruct Vista to monitor the point values so that the validation of values or links can be accomplished much quicker when Excel and Vista Server interact. As a reference these types of errors were experienced with reports that included 100 point values.

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 When releasing an override in a UNC station, the object with a "command priority" barnacle is not functioning properly in the controller.  It should go to level 0 control but it is going to level 16 where a constant is connected. Environment UNC station Cause Constants connected to Command Priority inputs during normal operation. Resolution As stated in the WorkPlace Tech Tool 5.7 Engineering Guide Supplement page 114 "do not leave constants connected to Command Priority inputs during normal operation". When the priority array is written via BACnet at a priority level corresponding to a Command Priority object input that is connected to a constant value, the controller responds to the BACnet service with a “property-error: write-access-denied” and does not write the value to the priority array, application RAM, or EEPROM.

Issue Trend logs not working after upgrading from Vista 4.2.5 to Vista 5.1.6. Environment Vista 4.2.5 Vista 5.1.6 Non-english regional settings. Cause When upgrading from a Vista version older than 4.5.0, it is recommended (in the latest TPA) to upgrade first to Vista 4.5.0 and then to Vista 5.1.6. However with non-english /US regional settings this can cause problems, such as the trend logs not being upgraded and, due to this, not working. Resolution Follow these 2 simple steps: Change the regional setting to "Location" US and set the language to English (United States). Upgrade directly to Vista 5.1.6 (not via 4.5.0.)

Issue Attempting to upgrade an I/A Series R2 Enterprise Server station and the database conversion fails: java.lang.OutOfMemoryError Environment I/A Enterprise Server R2 (all versions) Cause The issue is related to the limitation of the Java Virtual Machine (JVM). The conversion process is attempting to perform the upgrade on the station database and is exceeding the 1GB Java heap during the process. This typically occurs on an Enterprise Server station where the station database (db) contains a large number of log objects and associated logged data records.  Even though the records are archived in the SQL, the running station (log objects) still maintains records within each object. Resolution Verify that the Java heap is configured to allocate the maximum memory. Use the Windows Explorer and locate the nre.properties file (\niagara\lib directory). Edit with a text editor and verify the setting is Java.options=-Xmx1024MB. If not, change and save then restart the Niagara service and try to upgrade again. If the upgrade or conversion still fails (out of memory error), logs will need to be cleared in the running station to decrease the number of logged records. Restart the station in the current version (prior to the upgrade). Open the station and save the current records to the associated SQL database.  Select the Log Service (double click) and perform an archiveAll command (WorkPlace Pro menu items - Command).  The archiveAll command causes the data currently held in every log object to be immediately archived (sent to the LogService archive destination). Note this applies even to logs that are not configured to archive (daily and/or near full). There are two methods of clearing the logs.  The first method involves selecting each log object (double click) and perform a clear command (WorkPlace Pro menu items - Command).  The clear command clears all log data currently held in the object’s log buffer. The second method utilizes the AdminTool object to globally modify the log buffer sizes to temporarily decrease the buffers that will subsequently remove records that currently exist in the log object.  The AdminTool object is a special “utility” apps object, available in the Local Library (tridium/apps/AdminTool). This object provides an admin-level command to “Search and Replace” property values for objects in the station database. Config properties define the property name to search, new value to write, plus other parameters for filtering and recursion. This operation automates what would otherwise be a manual process of opening and modifying multiple objects’ property sheets. Note: The adminTool will globally apply the changes to objects defined within the utility.  Multiple iterations of this process may be required if log objects are configured with different buffer sizes. Open the local library and copy the AdminTool object to the station's root directory. Open the AdminTool properties and select the Config tab. rootNode -- Configure the swid of the starting point (upper hierarchy) of the station database in which the AdminTool function operates. This can range from the station’s root (/db/stationName) to any container or primitive object in the station’s database. If the recurseChildren property is True, the AdminTool function applies to any and all objects under the rootNode swid.  In Tree View, a right-click “copy” on any object under the station captures its swid. Use CTRL-V to paste the swid into the rootNode field of the property sheet. propertyName -- The target property name, exactly as shown on the object(s) property sheet(s). The property should be a read-write type.  In this example, configure the propertyName to bufferSize. elementName -- Not required for most properties that specify a single value of type float, integer, boolean, or string.  In this example, leave unchanged "-". newValue -- The new value assigned to all matching properties in (and under) the specified rootNode.  In this example, configure the newValue to 1 (bufferSize temporarily changed to size of 1). recurseChildren -- Defines if the search-and-replace function is extended to all children (and subchildren, etc.) of the specified rootNode.  In this example, configure the recurseChildren to True. objectTypeFilter -- Defines a match filter, meaning only objects of this matching type are affected. The asterisk (*) is used as a “wildcard.”  Partial strings of object types are supported, for example, AnalogO* will apply to object types AnalogOutput and AnalogOverride.  In this example, configure the objectTypeFilter to *Log (modify all logs e.g. AnalogLog, BinaryLog, IntegerLog, MultistateLog, and StringLog).  Note: The entire log type could be specified to only apply the changes to a specific type. nodeNameFilter -- Defines a match filter, meaning only objects with matching name are affected.  The asterisk (*) is used as a “wildcard.”  In this example, leave unchanged "wildcard." propertyValueFilter -- Defines a match filter, meaning only objects with this exact value are affected.  In this example, leave unchanged "wildcard." Execute the search and replace command (WorkPlace Pro menu items - Command). Return the newValue to the required buffer size and execute the search and replace command.  The smaller database can now be saved and upgraded or converted as required.

Issue In a Niagara G3 station, attempts to send email fail with message:  invalid address error. Environment Niagara G3 Cause If spam filter is enabled the SMTP server will not route email, as long as the Reply to parameter is empty.  It will treat the message as spam. Resolution The Outgoing account under the email service should have an email address listed under the Reply to parameter. If an account is required in the Outgoing Account parameter, for example:  joe.jones@acme.com, the same email address can be entered in Reply to parameter. If no Account is required for the SMTP server to route email but the spam filter is enabled, enter a fictitious account.

Issue An initial calculation of KWH produced a artificially high value that was captured by a trend log and is now stored in Report Server. This anomaly is artificially skewing the auto scale feature. Environment Web Report Server Trend Log Extended Trend Log Extended Log Cause The trend data anomaly is artificially skewing the auto scale feature of the trend graph in Report Server. Resolution Open the associated extended trend log. Right click on the entry that is to be corrected and select edit record.  Change the value of the entry to some more acceptable value. Enter  a reason for the change in the comment field. Select save. The new value will appear in place of the original entry with an icon to show that the value was altered. Allow up to 24 hours for the data to be migrated into Web Reports Server.

Issue A computer running UltiVist locked up and was rebooted.  Each reboot brings it right back to its locked up state.  How can this be prevented? Environment OS/2 UltiVist Cause A task or program does not execute properly and causes OS/2 to lock up with no response from keyboard or mouse. Resolution Boot up from the installation diskettes to gain access to a command prompt.  On the hard drive, modify the config.sys file to include the following lines: set restartobjects=startupfoldersonly set autostart=programs,tasklist,folders,warpcenter These lines will prevent the computer from running programs or tasks that lead to its locked up state.

Issue Need to add some RTD sensors to a 7716 PCU. I need a P8RTD expansion card. Environment I/NET site Cause  Can I order a P8RTD expansion card? Resolution This expansion card is obsolete. Please refer to the TCON096 for current information on accessories and expansion for the 7716.

Issue Upgraded to 4.4.0 but don't see the SCPTs on a LonWorks Unit yet? Environment Vista 4.4.0 Lonworks units Cause When you upgrade your Vista database, it doesn't automatically create new database objects.  Resolution From Vista Workstation, navigate to a LonWorks unit Right click and select Properties. Click on the "Xif file" tab Click on the browse button (the one next to the "source file" field with 2 dots on it). Browse to the xif file for that unit, e.g. C:\lonworks\import\tac\x100\102AX101.XIF for an Xenta 102-AX Click "Open" then "OK" When you refresh that unit in the tree, you'll see the available objects/function blocks for that unit and they will contain most of the SNVTs, SCPTs and UCPTs in them. Some of them will not show up, e.g. ucpt_vavselection in the 102-AX.

Issue Where can the specifications for the MNB-300-ENC be found? Environment MNB-300-ENC Cause There is no separate specification sheet for the MNB-300-ENC. Resolution See the Installation Instructions for the MNB-300 (F-27345).

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 How many digits can the PIN number be when using card + PIN entry? Also how can it be viewed as it is displayed as stars in the Personnel Manager? Environment Access Controllers Card + PIN entry or exit Display PIN number Cause Leading zeros on a PIN number are not saved and how long can the number be? Also as the number is shown as * characters how can the number be seen? Resolution The PIN number for a personnel object can be in the range: 0 to 4,294,967,295 inclusive for the NC2 (9680) and ACX2 (ACX5720/40). For all other older controllers the PIN range is 0-65535 You are not allowed leading 0’s in a PIN number, they will be removed. i.e. 0010 will save as 10 0000 will save as 0 To view a persons PIN number, use the "Command Line" application and from the folder where the personnel are stored enter: P PersonName PIN This will print the value of the PIN attribute for the person named "PersonName".

Issue Logging off one user, logs another user on. Environment Sigma Users Logon Logoff Cause When a specific user logs off  the Sigma system, another user is logged onto the system. Resolution This issue is caused by corruption of the GenCNF.rec and user files, there are two options available. Locate a backup of the system files that was taken before the corruption occurred. Shutdown the Sigma server and all clients. Copy the GenCNF.rec file and the User folder from the system backup. Paste the copied files into the Data folder. Restart the Sigma server and clients. Test the user access operation. Rename the corrupted user. System users cannot be deleted, they can only be re-named. In the Sigma SSM / Users, highlight the User name and select to rename it Rename the user to an appropriate name. Create a new user to replace the old user, allocate the correct access levels. Test the user access operation.

Issue Changing the name of an object that is being logged. Environment Logging Object name Cause A system has been logging for several years, but now the customer needs to change an object name. When using Dataview to review the logged data, which name will be shown for the existing data? Resolution If an object name is changed and that object is being logged, then the new name is passed to the logging setup. From this point on it is this name that will be used in any log reviews containing this object. This applies to both new logged data and any archived data.

Issue How to calculate the polling time at the netcontroller / OPC server? How many nodes/ controllers can be put on each netcontroller to get to specific polling time. Environment Netcontroller OPC Server Cause The OPC server was designed to be performance tuned. Resolution It is hard to determine just how many controllers / polling time. It would be determined better by looking at the programming of the controllers, for example, Inputs / Outputs how many points in each group and the interval of the data that is required to be received. The "OPC Server Guide" has performance options and guidelines on setting up an optimal system. You can also add another OPC server if you need to do load balancing.

Issue Does the Xenta 555 update the time on MicroNet controllers under its LAN? Environment Xenta 555 MicroNet Controller Cause Time sync to Xenta 555 Resolution Yes, the Xenta can update the controller times. The Xenta utilizes a NTP (Network Time Protocol) server. A TCP/IP protocol used to synchronize the real-time clock in computers, network devices and other electronic equipment that is time sensitive.

Issue When purging alarm in AMT, and the I/O server is configured as serial port communication, there will be "No Reply" window popping up and Retry is useless. Environment I/NET Cause This may be caused the network communication issue. Or it may be due to other issues. Resolution Disconnect the Server from network or disable the serial port in I/O configuration. After the alarms are purged, return to the original setting.