Building Automation Knowledge Base

Issue In Vista 5.1.8 the line break character of the internal trend log file format was changed from the previous CR+LF to LF.  This can break some third party reporting and editing tools. Environment Vista 5.1.8 Cause In Vista 5.1.8 the line break character of the internal trend log file format was changed from the CR+LFof previous versions to LF Resolution Apply Hotfix 38 to Vista 5.1.8.  This restores the trendlog file format used in previous versions.

Issue Not all features are seen when a BMS platform is viewed using remote control software e.g. RealVNC Environment Remote Control Software. Cause Not all features are seen when a BMS platform is viewed using remote control software. One example is: When the SmartStruxure License Software application is used, the drop down menu for adding the license detail is not available when viewed remotely using RealVNC. Resolution When the SmartStruxure License Software application is used, the drop down menu for adding the license detail is not available when viewed remotely using RealVNC. The above example is one scenario. There are a number of other remote control software applications where similar instances may occur. If such an issue occurs, check that the BMS software is functioning correctly by both being viewed and ran in the same environment. Because of the number of different remote control software options that are available, anomalies will prevail.

Issue When an alarm is sent to a printer Alarm Receiver, the printer prints several pages for one alarm. Environment Vista Printer Cause A normal, modern laser printer does not have coding that allows it to take a break in the middle of a page and start again later. When a print job starts it will consume the whole piece of paper. An alarm in Vista will print one page for just that one alarm. Depending on the alarm it could span multiple pages. Resolution Only a dot matrix printer can be used because they can print on impact. Correctly programmed you will get one alarm on each row. The programming needs to be done with the printer manual.

Issue When running TAC Vista as an application it is not possible to start it as it can't find the files PLPSU.DLL and PLSERV.EXE.   Environment TAC Vista 4.XX Cause A antivirus program called Avast have blocked PLPSU.DLL and PLSERV.EXE. Resolution Don't use this antivirus program when running TAC Vista or mark the files as safe in the antivirus program.

Issue Does the TAC Vista OPC server have a certificate from OPC foundation? Product Line TAC Vista Environment TAC Vista OPC server Cause The OPC Foundation established the OPC Certification program to help vendors verify that their products meet end-user requirements of plug-and-play interoperability, robust behavior and meet minimum performance expectations by providing well-defined behavior, documentation and test tools for the testing of OPC Servers and Clients. Resolution TAC Vista OPC server have not been tested and certified by OPC foundation, but TAC Vista OPC server is following the OPC specifications established by OPC foundation.

Issue XBuilder crashes when opening a project or simply opening the editor Environment TAC Vista 5.1.8 and earlier Windows 7 32-bit computers Cause Due to some Windows issue, XBuilder may crash on SOME Windows 7 32-bit computers. Resolution This issue is solved in TAC Vista 5.1.9.

Issue Vista Workstation error log has "Netfunc errors." Environment Vista Vista multi server system Cause The Netfunc message in the log means that the master node is already working on the subscription that the node is sending. This can be caused by an overloaded network. The node has not received an acknowledgement from the master in a timely manner. It could also mean that the Master and its node are not synchronised correctly.   Resolution If the error continues to appear in the log: Make sure the network is not overloaded.  Close down the server and the nodes and restart them so they will resynchronize.

Issue  Tacos not responding when starting Workstation Environment Vista Tacos.exe Cause If a trendlog is manually on but does not have a value to log, it can cause Tacos to crash (not responding). Resolution Go to the TAC Vista Installation folder Find the file named TACaddon01.DLL Rename TACaddon01.DLL to TACaddon01OLD.DLL and start Vista Server and Workstation again. Search for all trendlogs and make sure they have a point to read from, if not set them to manually off.

Issue When you edit a OGC standard graphic and then attempt to save you get the error "Cannot save graphic object. Cause: FILE-service not available" Environment Vista 5.1.x Cause The OGC standard graphic does have this unknown issue on some sites. Resolution To allow the edit of the OGC edit the standard graphic and save out of the database. The open with the OGC editor and make the changes that are required and save back into the vista database.

Issue The Triac (V) outputs on the TAC Xenta 120-FC device goes ON, but never OFF. In this case, it can open the valve, but the device could not close the valve. Environment TAC Xenta 121-FC TAC Xenta 121-HP Cause If the device is powered with 24 VDC, the Triac will not work properly. According to the datasheet, the TAC Xenta 121-device should always be powered by AC, not DC. Triac is an acronym for Triode for Alternating Current, and could only be working with AC power supply. Resolution Correct the power supply to the device to use AC, not DC.

Issue How does the documented minimum pulse width translate into maximum pulses per minute? Environment All software/ firmware versions Cause The documentation defines the minimum pulse duration, not the number of pulses per minute. Resolution The documented 20ms min pulse duration for the Xenta 411 applies to both On and Off states. A complete min pulse cycle would be 20ms On + 20ms Off (50% Duty cycle), which equals 40ms. Therefore the max number of pulses per minute is 1000*60/40 = 1500 pulses/min or 25 pulses/ Second (25Hz).  

Issue Vista Server trends, logging BACnet, M-bus or modbus values, are not updating. The same value being logged over and over. Environment TAC Vista Xenta 700 TAC Xenta 913 Cause This is due to a bug in the Xenta Server firmware, and happens if you have a menta application that uses other modbus values than the ones being logged. If you open a graphic or the value columns the log works.   Resolution This issue will be fixed in 5.1.9. 5.1.8 hotfixes for Xenta 913 and Xenta 700 are available on request from PSS.

Issue Webstation closes by itself Environment Webstation  Internet Explorer 9 32bit Cause Vista webstation and TGML do have some compatibility issues with Internet Explorer 32 bit that can cause the webstation to log out itself or even close down when login in. Also a Internet Explorer 32 bit needs to have Java 32 bit installed. On a 64 bit machine if you want to run 32 bit make sure the Java 32 bit client is installed. A normal error to see when those happen is:  --- A fatal error has been detected by the Java Runtime Environment: EXCEPTION_ACCESS_VIOLATION (0xc0000005) --- Resolution Following workarounds have been confirmed to help.  Enable the compatibility view in Internet Explorer 9 Upgrade to Internet Explorer 10  Make sure you have Java 32 bit installed.  Use Internet Explorer 64 bit

Issue The TAC200 heat controller is obsolete, but data sheet and handbook may still be useful. Environment TAC200 Cause An obsolete product is still in use on sites. Resolution Documentation is available on The Exchange Download Center by searching for "TAC 200."

Issue Sometimes when you add some LonWorks nodes in Vista Workstation under one Xenta Server, and click Edit on the Xenta Server to open Xbuilder, the content of Xbuilder doesn't update, and the ones in XBuilder and Workstation doesn't match. Environment Vista Workstation Xbuilder Cause The Xbuilder failed to update according to Workstation Resolution Right click on the "LON" under the Xenta Server in Xbuilder and click "Refresh network from TAC Vista". It will manually update the content in Xbuilder with Vista Workstation. Then Workstation and Xbuilder will match each other.

Issue When logging in, user sees error: "BC client Path from registry" If the error is acknowledged, everything works except for the Alarmview. Product Line TAC Vista Environment Vista Cause If a created user does not have access to the Alarmview when logging in, the error appears. Resolution Give the user access to view the Alarmview: Go to $Alarmview Right click on $Alarmview and choose "Authority" Give the user/group that has the problem at least read rights

Issue Font size is very large in Xenta Server and Webstation TGMLs, both in the web interface and when viewing from Vista Text in TGML graphics is too large, it word wraps when it shouldn't Environment TAC Xenta 700 TAC Xenta 511 TAC Xenta 527 TAC Xenta 555 TAC Vista TAC Vista Webstation Cause Windows Font Size is set to more than 100%. It has been found set to 125% as default on some PCs. Resolution In Windows 7 and 2008 Server: Goto Control Panel -> Appearance --> Display Click "Smaller - 100%" option and then apply settings The font in TGMLs should now display normally

Issue The thermostat appears to be in OFF mode and can't be cycled through the modes as indicated by the manufacturer's directions.   Environment Venstar T2700, VST2700 thermostats for red-wire control connected physically to a controller Cause It seems that the polarity of the dry contact was set to the default Normally Open (NO) state. Using the Venstar EZ-Programmer to apply the correct settings for use with an occupancy point did not overwrite the polarity of the Venstar's dry contact, but did overwrite the Dry Contact Operation. Also, by wiring everything up first, we did not power up the thermostat to change the mode before it got the closed dry contact command from the BAS. So when we did power everything up, the dry contact was closed, but the thermostat understood that this was an "unoccupied" command since it was still set to NO. Even though the security settings allowed the mode to be changed, when Dry Contact Operation is enabled, the mode can only be changed in occupied mode. When the thermostat goes unoccupied, it stays in whatever mode it was in previously, and controls to the unoccupied setpoints. By not realizing that the EZ Programmer didn't overwrite the polarity, we assumed the dry contact operation and polarity were correct and a closed dry contact would enable the occupied mode.   Resolution This issue can be resolved by powering up the thermostat before connecting the dry contact relay and changing the mode to "auto". If already wired, make sure the dry contact polarity is set to Normally Closed (NC) and Dry Contact Operation is "Yes". Then the modes can be cycled while occupied. < acc0432manualrev1.pdf="" manuals="" support="" www.venstar.com="">

Issue Do we have any official statements if Windows updates should be installed on computers running a Vista server?  Environment TAC Vista Cause As TAC Vista is using Windows components there is always a very small risk that TAC Vista could run in to trouble when installing a Windows update. But on the other hand if not installing Window updates the computer could run in to trouble and then Vista will crash too. Resolution There is no official statement saying if Windows updates should be installed on a TAC Vista site, it is up to the engineers on site to take that decision.

Issue How can a TAC Vista system communicate with a Profibus device? Environment TAC Vista system 3rd Party Profibus device Cause A site may have existing devices that communicate via the Profibus field bus protocol and these are to be kept and integrated into the TAC Vista system Resolution There is no standard way to do this, but one way would be to use a Modbus to Profibus converter. On one side of the converter a X913 can communicate via Modbus and on the other side the Profibus device would communicate with the converter via Profibus. The X913 can then be integrated into Vista if/as required.