Building Automation Knowledge Base

Issue Over the years, a few dongles (both LPT and USB) has broken for various reasons. Sometimes its internally, other issues has been that they have been exposed to violence (dropped laptops...) and to be able to run the Vista software, the dongles needs to be replaced. Environment Vista IV LPT dongle Enduser 000878560 USB dongle Enduser 000878570 LPT dongle Inhouse, Engineering 000879310 USB dongle Inhouse, Engineering 000879320 Cause Broken dongle (PSU) hardware.  Resolution The Vista IV product portfolio was withdrawn in 2011-12-31, and support is now very limited. It is strongly recommended to upgrade the Vista system to latest possible version in order to secure support possibilities onwards.

Issue When "Exporting Data" from a multi-history chart there are many nan's in the data. Environment I/A Series G3 (Niagara) Cause The timestamp in the history data has a millisecond component that is not shown on the data displays.  When the Export data is displayed history values are provided with the timestamp.  If the timestamps for all the histories samples are exactly the same (to the millisecond) the data value is displayed, if not "nan" is displayed.  Resolution This condition occurs only when the "rollup" for the chart is left at the default of none.  Changing the "rollup" to a value other than none will bring the data into order.  Setting the rollup to the sample interval of the histories gives the best results in the Export data.

Issue Even though the "Suppress form feeds when printing alarms" option is selected in the Workstation Preferences, alarm printer is printing only one alarm per page. Environment CyberStation Alarms Printer Cause The alarm printer is issuing a form feed at the end of every alarm message. Resolution If the "Suppress form feeds when printing alarms" option is set to true in the Workstation Preferences, this issue has to be handled at the printers internal settings by adjusting the page length and other settings. 

Issue A program turns on an output based on a comparison of a door's forced entry attribute and the value of a schedule numeric.  The program is disabling and throws an error. Environment AC1 AC1 Plus Plain English CyberStation Continuum Cause An Infinity Numeric and the Forced Entry attribute of a Continuum door object are incompatible value types.  Resolution Use an If/Then/Else expression to evaluate the value of the doors Forced Entry attribute, and the Infinity Numeric's value separately.  Then Switch the state of the output based on the result of the evaluation. Original Code   If (AHCASECACC100A ForcedEntry and PerimeterDoors) then Goto AlarmOutputOn Corrected Code   If (AHCASECACC100A ForcedEntry = True) and (PerimeterDoors = On) then Goto AlarmOutputOn

Issue How many IE entries can Continuum controllers have? Environment CX controllers Infinet controllers Cause Limitations of IE entries in Continuum controllers Resolution Infinet controllers = 255 CX level controllers = 65535

Issue The error message "BACnet is not enabled!" is displayed in the Standard Output Window of the UNC when a whoIs is performed in BACnetService. No devices are displayed. Environment Niagara R2, UNC-410, UNC-520 Cause The BACnet instance number in the UNC was set at its default of -1. It must be configured with an unique number between 0 - 4,194,302 Resolution Assign the unique instance number for the UNC. Open the UNC’s station and expand its Services container Right-click BACnetService and select Properties Open the General and Config tab Enter a unique number in the Instance Number property and then click Apply The BACnet devices will be populated when a whoIs is performed.

Issue When re-entering the Neuron ID of a controller, an  error appears indicating that this Neuron ID already in use. Environment Vista 4.4.2 Cause If the System Plug-In fails at the time a Xenta controller is being worked on sometimes a default controller is created using the Neuron ID of the controller you were working on. Resolution In the Network management tool look for a device that has a name that does not make sense or follow the site naming convention. When you find this device check the neuron ID to ensure this is the device that has been assigned the Neuron ID of the Xenta device you were working on. When this is confirmed delete this device from the LNS network. Then refresh the LNS side of the System Plug-in and assign the Neuron ID to the Xenta controller you were working on at the time of the crash.

Issue Selecting the correct actuator for the VTRE valves. Environment VTRE M9B EM9 Cause The data sheet for VTRE is currently listing the following suitable actuators: M9B-24:  860-1010-000 M9B-230:  860-1020-000 EM9:  860-1110-000 Also, it states the following: "NOTE! The VTRE valves require that the  actuators be adjusted for 90° rotational travel." However, the EM9 listed in the data sheet is 180° rotational. Resolution The correct actuators should be the following: M9B-24:  860-1010-000 M9B-230:  860-1020-000 EM9:  860-1100-000

Issue This alarm is trigged every day "trendlog object...log point can not be read" how do I get rid of it? The trendlog is a Vista server trendlog logging a point in a Xenta 400 Environment Vista 5.1.6 Cause When a Vista server trendlog is started Vista reads the chosen value according to the log interval, if one reading is missed you will see this alarm. The missed reading could have several reasons but the most common is a bad Lon network or high traffic on the Lon network.  Resolution Investigate why the logged value can't be read, check the Lon network with a analyzer.  

Issue Unable to override an ASD point from a Niagara G3 Enterprise Server. . Environment Niagara G3 Cause TAC/ASD module is missing from Enterprise Server Niagara Modules folder. Resolution Download TAC/ASD module from The Exchange Download Center Download the matching revision module and copy the file in the Niagara Modules folder. Restart the Niagara Service and Workbench to register the module.

Issue After the rehost process, is it possible to use both the old and new licenses (PCs) at the same time? Environment TAC Vista 5 Cause After rehosting a license, nothing prevents you from using both the original and new license file at the same time, since there is no feedback from the system that synchronizes the usage of licenses from the same Entitlement. Resolution It is strictly against the license agreement, and should not be used at any time. If a temporary license is required, use the existing demo license files or contact PSS for other temporary solution. 

Issue Frequently see Java.lang.Exception errors in the UNC error log or Standard output window that reads, in part,      "At tridiumx.gcm.GcmUnsolicitedReceive.run (bytecode xxx)" Environment I/A Series R2 UNC I/A Series GCM 84xxx or GCM 86xxx connected to UNC Cause The GCM does send unsolicited messages all the time, more or less depending on how you have the logging configured in the GCM. Depending on the source of the message, some will simply be reported to the Standard Output Window as "Unsolicited GCM message received" or "Processing Unsolicited Message"'. Other messages will be reported as a part of an error message written to the Standard Output Window and / or the Error log. Resolution You can minimize these messages by insuring that none of the print groups in the GCM are configured to use the serial port to which the UNC is connected. You also need to confirm that all of the Exception Print Flags in the GCM are set to NO. The remaining messages that cannot be eliminated are almost always GCM Network communications protocol messages that have no meaning to the UNC.  

Issue An end customer wants to use SSL on his Niagara R2 control system.  Is it supported? Environment Niagara R2 Cause Security policy changes by end customer's IT department Resolution SSL is not supported in the Niagara R2 environment.

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 install / add WebClient to existing SU installation of Continuum. Environment Continuum WebClient Cause Existing Continuum SU Cyberstation installed and site is being upgraded with WebClient support. Resolution Perform the following steps to install WebClient on your Single-User installation. Backup the ContinuumDB, Graphics files, and Menus to a safe location. (For detailed steps on how to backup / restore your ContinuumDB see here.) Upgrade security key to allow WebClient. (from supplied serialized upgrade code from Repairs) Uninstall Continuum. Install WebClient from scratch following the Planning and Installation Guide. (IIS then WebClient) Restore your ContinuumDB, graphics files and Menus. Test

Issue The customer have some rooms with consumption logs. The customer wants to easily select from and to date, and then be presented with the total consumption in this period. Is this possible in Vista? Environment TAC Vista 5.1.7 Cause You can't do any programming in any objects in Vista(except java script) which you need here. There is no standard object in Vista doing what the customer want.   Resolution It would be possible to do using a report but then the customer need to create a new report where the trendlog and the input dates is specified every time he need the energy consumption for a certain period. This is not really what the customer requests so no this is not possible in Vista today.  

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 When changing name of a trendlog in Vista will the name of the trendlog in the SQL server also change? This is when using Vista 5.1.7 and have upgraded the SQL database. Environment TAC Vista 5.1.7 Cause The name of the trendlog in the SQL database will change when the next value for that trendlog is written in to the SQL database. Resolution The name of the trendlog in the SQL database will change when the next value for that trendlog is written in to the SQL database

Issue What happens with the output VDC value if the measured value goes outside of the specified range?  Environment SPD310 SPD360 Cause The selected value is specified by the position of the jumper. Signal output is set to 0-10V. Resolution If jumper is set to 500Pa and read value exceeds this value, the output signal will still show 10VDC. Any control signal above 10VDC is marginal, and should not be used as a measurement reference.

Issue When to  Sigma Remote Client is started a Runtime Error is reported, the error is as follows; Programme c:\Sigma\Bin\Sigop.exe - Application requested runtime to terminate in an unusual way. When OK is selected, the following is returned Software exception 0x40000015 occurred in this application at location 0x7857bb47   Environment Sigma Remote Client Error Cause The incorrect Sigma Client software has been installed onto the remote client PC. Resolution The site has Sigma 4.05 SEB software installed, but the Remote Client had been loaded with Sigma 4.06. Note - Sigma software releases cannot be mixed across Sigma Client/Servers and Remote Clients, therefore before adding a new Remote Client to a system, the existing site software must be established. To establish the current release of software, go to the Sigma System Manager, select "Help" and "About Sigma", there you will find the Sigma build number.  

Issue Vista Workstation crashes when the content of a column in any View (Alarms, Events, Search Results etc.) exceeds 259 characters. Environment Vista 5.1.7 Cause In the unlikely event that the content of a column in a Vista View exceeds a limit of 259 characters, Vista Workstation crashes and must be restarted.  Vista Server is not affected. The problem was discovered while doing a search for TGML graphics, with the property "Bindings" selected.  The search returns one graphic on each row and all the bindings for that graphic are displayed in the property column on that row.  Resolution Upgrade to Vista 5.1.8, when available.  The issue is fixed by truncating the contents of any View column to 259 characters. The issue is highly unlikely to occur in normal use.  In the case of the Bindings search, the workaround is to use the "Change Reference" tool instead