Building Automation Knowledge Base

Issue What is the difference between the three stretch behavior buttons in the TAC Vista graphic viewer.   Product Line TAC Vista Environment Vista Workstation Cause The explanation of what these buttons do has never been explained well. Resolution TAC Vista Workstation   There are five types of stretch&zoom buttons in TAC Vista Workstation (see figure below).   The three stretch behavior buttons are: Reset the strech behavior to what is defined in the TGML document. Set image to uniform size, which means that the image is stretch out to show it as large as possible and still show the whole image and with correct aspect ratio. Fill the entire client area/window, which means that the image is strechted out as large as possible to fill the whole area without maintaining the correct aspevct ratio.   The two zoom buttons are used for zooming in and out. To use them, one selects one of the buttons and then click on the TGML image to do the actual zooming. Or one can use the plus (+) or minus (-) keys to do the zooming when the TGML windo has the focus.     TAC Vista Graphics Editor TGML In the graphics editor there are two ways of looking at the TGML image; Design or Preview mode. The second view should simulate what is shown in the Workstation.   Design mode: When starting the editor, the TGML image is shown in its actual size -100% (i.e., no stretching or zooming is done).   By clicking on the Zoom button one can get to the rest of the sub-buttons for stretching/zooming. When this sub-toolbar is shown (and only then) the shortcut keys for the strecth/zoom button works (Ctrl-Asterisk, Ctrl-Plus and Ctrl-Minus). The restore stretch button (Ctrl-Asterisk) resets the strech behavior 100%.   The two zoom buttons are used for zooming in and out. To use them, one selects one of the buttons and then click on the TGML image to do the actual zooming. Or one can use the plus (+) or minus (-) keys to do the zooming when the TGML windo has the focus. By using the shortcuts Ctrl-Plus or Ctrl-Minus, selects the correct button (and the cursor changes to the spyglass when moved) and then one can click in the image to zoom.       Preview mode: When the preview mode is entered, the strech behavior will follow what is defined in teh TGML document.  By changing the behavior in the TGML document, the stretch mode changes in the preview window (unless zoomimg has been performed - se below).   In preview mode there are no strech/zoom buttons to use in Vista (the zoom buttons are present in Struxureware). However the shortcut keys plus (+) and minus (-) can be used for zooming if the TGML image has the focus.   In Struxureware's version of the graphics editor one can use Ctrl-Asterisk to reset the strech behavior to what is defined in the TGML document if the zooming has been used. However, in Vista's version the Ctrl-asterisk does not work in preview mode. But it seems that most shortcut keys for the toolbar buttons does not work in Vista.   Note: The stretch button has different meaning in the two views.          

Issue Error: 8000401a Retrieving the COM class factory for component with CLSID {2B768E20-89F2-11D2-99FD-00104B6D2299} failed due to the following error: 8000401a.Server process could not start because the configured identity is incorrect. Check username and password. (Exception from HRESULT: 0x8000401A).Code: -2147467238 When starting Vista Server, a fatal error happens: TACOS: COM Initializing failed, error code: -2147417831 Product Line TAC Vista Environment Remote desktop TAC Vista Windows 2008 Server or Windows 7 Cause When using Remote Desktop with a Windows 2008 Server and disconnecting, the TACOS process may end up in a "sandbox" and can not be reached by other people trying to log in remotely. Or, the Vista Server can't be started. Resolution The attached Tacos RDP Disconnect contains scripts that will disconnect a Remote Desktop session back to the physical session if tacos.exe is running. If tacos.exe is already running on the physical session or is not running at all, nothing happens.

Issue How can I add a SmartStruxure Automation Server to TAC Vista using BACnet/IP and what is needed Product Line TAC Vista, EcoStruxure Building Operation Environment TAC Vista Xenta 913 Automation Server Cause Building Operation versions earlier than 3.2 are not FDA 21 Part 11 approved, In instances where the version is lower than 3.2 it can be achieved by using  TAC Vista as a front end, and having Automation Servers as field controllers. In Building Operation version 3.2 and later an optional Regulated Industries Compliance Pack is available that can be used without the need for  TAC Vista as a front end. Resolution 1. Create a BACnet interface in Automation Server. 2. Create BACnet points in the "Application" folder 3. Browse the Automation Server with a BACnet browser (Here is a free tool) 4. Note the instance id's of the points 5. In TAC Vista, create a Xenta 913 6. Edit the Xenta 913 7. Create a "BACnet IP Client" interface and give it the IP address of the Automation Server 8. Create a BACnet device template containing the points you need - refer to the id's previously discovered 9. Add the device template to the "BACnet IP Client" interface in XBuilder 10. Save and download the project 11. Now you get the live values from the Automation Server in TAC Vista

Issue Needs to know how often Vista (or Xenta Servers) do online/offline polls for Modbus and MBus devices Product Line TAC Vista Environment Xenta Server Modbus Mbus Cause The devices may go offline for several different reasons. It's not possible to give a precise answer to this question, since it depends on your setup and the number of devices. Resolution In general, if a Modbus device has been detected as offline by the Xenta Server, it will wait 60 seconds until it tries polling that device again. That doesn't mean that a device will come online after 60 seconds if it has been offline because as described below, other factors comes into play, such as the number of devices and registers, and invalid registers. Mbus: The Mbus protocol is designed so that all information in the device will be received at every poll, regardless of what is defined in the device template. If the Xenta Server doesn't receive any information it will retry twice and if still no reply it will set the device to offline. All offline devices will be transferred to an offline queue in the Xenta Server, and at every new poll one device (the oldest) will be moved to the poll queue again. The reason for not retrying all is that if you have lots of devices that are offline at the same time, each poll would take very long time to complete and if using a short poll interval it may not be finished in time before the next poll. That will also mean that if you have many offline devices and have set a long poll interval in Xbuilder (default 1 min) it may take quite a while until all devices are online again. Note: In Xbuilder 5.1.9 and later it's possible to set the number of offline devices to poll each cycle. In some cases, for example when there are few meters and/or long poll times you may want to increase this number. Modbus/TCP: You will have a Server address for the TCP Client and if that server's ip address can't be reached all the Modbus devices below it will go offline. However as soon it can be reached again (will be tried constantly), it will scan all devices below it, and if they reply they will be set to online. If there's no response from a single device, it will retry twice before it's set to offline. The time it will take depends on the slave timeout setting in Xbuilder (default 3 seconds). As for Mbus, you have an offline queue where 1 device will be moved to the poll queue every poll cycle. The total poll time also depends on how many devices and registers you have defined (many devices/registers = longer poll time = longer time to detect if a device is offline/online). Modbus/RTU: It works similar to Modbus IP, except for the server part (which is not present). Besides that, you also have the "transmit delay" setting in Xbuilder (default 0 ms, max 1000 ms) which may effect the time it takes for a device to be reported as online/offline

Issue How to set the neuron ID of an I/O Module in a Vista classic network. Product Line TAC Vista Environment Vista Classic Network Xenta I/O modules Cause Xenta I/O modules beneath a base unit (300 or 400 series) do not show up in the Folder view tree structure.  You cannot right-click and set a neuron ID the same way you do for a base unit. Resolution Click on the Xenta base unit (300 or 400 series controller) in the tree structure. This brings up a list of modules inside the Menta file as well as two option modules that cannot be seen from the tree structure-- $IO and $LOGS. Double click the $IO module. All of the I/O modules defined in the Menta file are listed here.  Right-click, properties, to set the neuron ID.

Issue In the Xenta Servers, it is possible to set the communication port to RS232 or RS485. In EBO this is not possible on the Automation Server (AS) Product Line EcoStruxure Building Operation Environment Building Operation Automation Server Premium (AS-P) Building Operation Automation Server  Xenta 500 Xenta 700 Xenta 900 Cause The AS serial ports are RS-485, not RS-232. Resolution There are two solutions to consider when Xenta is using an RS-232 connection: If the connected device also has a RS-485 connection switch to that. (Optionally replace the device with one that has RS-485.) Use a RS-232/RS-485 converter. The converter must have automatic data direction detection and control on the RS-485 side, since our Automation Server devices have no RTS signal (to enable the transmitter) available externally.

Issue If a Xenta 913 with SNVT(s) is added as a Lon device to an Automation Server Lonworks network the commission process fails in the last step with error 0 Product Line EcoStruxure Building Operation Environment Building Operation Automation Server TAC Xenta 913 TAC Xenta 700 Cause This is a bug in the Xenta Server firmware. Resolution This issue will be fixed in Xenta 913 firmware version 5.1.9, however  hotfixes have been made for 5.1.8 and can be requested from PSS (TACXenta913-5.1.8.15 and TACXenta700-5.1.8.47). Note: All data will be lost in the Xenta Server when applying the hotfix.

Issue When converting an OGC graphic to TGML an error saying that the binding name is too long is displayed. Product Line TAC Vista Environment Vista Workstation Cause When a OGC graphic is converted to a TGML the bindings are named after the path to the value in the objects in the OGC graphic. Resolution After the conversion is done change the binding name in the TGML editor.  

Issue Certain Xenta controllers and I/O modules can accept 10k thermistor temperature inputs. Product Line EcoStruxure Building Operation,TAC Vista Environment Xenta 102-AX Xenta 420A, Xenta 450A Cause The Xenta 102-AX has always used 10k thermistors. Now some of the I/O modules and programmable controllers also have an option for 10k thermistor inputs. A common question is -- what type of 10k thermistors? Type 2? Type 3? Resolution The reason there is no reference to 10k Type 2 or 10k Type 3 is because these are Continuum-specific terms. The 10k thermistor that is compatible with Xenta 42XA and 45XA I/O modules are the same that I/NET uses. They are Vishay Dale Curve #1. View this PDF for the Resistance vs. Temperature Conversion Tables for this thermistor.

Issue When launching a program or when working with a program, you get an error from "Microsoft .NET Framework".   Product Line EcoStruxure Building Operation, Satchwell MicroNet, TAC INET, TAC Vista Environment Windows .NET Framework Cause Microsoft .NET Framework is used in almost all larger applications, and there can be various reasons why you see an error. One reason can be application specific, meaning that there is an actual issue with the software and the way the software is using .NET Framework, but another reason can be that the .NET Framework installation itself is corrupted. If it's an application specific issue, you need to contact product support, but in many cases simply repairing the .NET Framework installation has proven to solve the issue. Resolution 1: Close all applications 2: Make sure you have the correct version of .NET Framework installed for the software you use referencing the product's data sheet. You can use this tool to check what versions you have. Here is a direct download link. 3: Install versions that might be missing. You can download the various versions from the tool linked above. 4: Download Microsoft's .NET Framework repair tool and run it applying all fixes the tool suggests. Here is a direct download link.

Issue GSM modems that can be used with the Remote Alarm Manager. Product Line Satchwell BAS & Sigma,Satchwell MicroNet,TAC Vista Environment Remote Alarm Manager. BAS Sigma Micronet Vista  GSM RAM Siemens TC35i Siemens MC52i Multi-Tech MTCBA-G-F4-GB/IE Cinterion MTX-65+G-V53 Cause Not all GSM modems will allow the full functionality of message acceptance in the Remote Alarm Manager. Resolution The following GSM modems are known to provide the full message acceptance of the Remote Alarm Manager. Siemens TC35i GSM modem terminal. In the Remote Alarm Manager configuration select the C35i driver. This modem is now being replaced be the Cinterion (Siemens) MC52i GSM/GPRS Dual band modem terminal, which has not been tested, but appears to be a direct replacement with added functionality. TC35i GSM/GPRS modem terminal data sheet MC52i GSM/GPRS modem terminal data sheet Multi-Tech MultiModem MTCBA-G-F4-GB/IE modem terminal. In the Remote Alarm Manager configuration select the Brodersen UCM 91/92. This modem is still available, but seems expensive and difficult to source. MultiTech MultiModems MTCBA-G-F4 data sheet Cinterion MTX-65+G-V53 modem terminal.In the Remote Alarm Manager configuration, allow the software to locate the modem and use a generic driver. Cinterion MTX-65+G-V53 modem terminal data sheet   Remote Alarm Manger is no longer a support solution, it is recommended transitioning or upgrading to EcoStruxure Building Operation.

Issue TAC Vista Server fails to start or "hangs" during startup. "Ensure TAC Vista Server is started" error, after having just started Vista Server and attempting to open Workstation. Product Line TAC Vista Environment Vista Server Cause Corrupt Vista database Bad installation of TAC Vista Resolution Troubleshooting technique to determine if you have corruption of the TAC Vista Database or TAC Vista Software. Determine if the TAC Vista Server is starting by observing the Tacos.exe process in Windows Task Manager. Server is crashing if Tacos.exe is not present or disappears after starting the Server. From the Start Menu, navigate to TAC Vista Server Setup and browse the Vista Server database location to a test location, i.e. :\DBTest. This will create a new "blank" database at that location. Attempt to start TAC Vista Server and observe results in Windows Task Manager. You should get one of two results: If TACOS.exe process is running and the Server seems to start correctly, you may have a corrupted Vista Database. You may further investigate by copying the site Vista Database folder structure and placing it on another computer (with the same Vista Software version) to see if the Server will start. In some cases, it may be successful, a backup can be made and restored to site machine. In most cases, it will also fail. Restoring to a known good backup is the only recourse.   If TACOS.exe process is not running and the Server seems to start incorrectly, you may have corrupted Vista Software. It is recommended to follow the uninstall/ reinstallation procedure for your version of Vista. You may further investigate by copying the site Vista Database folder structure and placing it on another computer (with the same Vista Software version) to see if the Server will start. In this case, it should be successful.

Issue BACnet MSTP Capture Application Product Line Andover Continuum, EcoStruxure Building Operation, TAC IA Series, TAC Vista Environment Any Bacnet MSTP Network Cause The BACnet MSTP capture application provides the ability to analyze data communications between devices anytime issues are suspected on the network. Resolution Download the latest version. Browse to Steve Karg's  BACnet Protocol Stack - Browse /bacnet-tools at SourceForge.net Select the version folder Select bacnet-tools-[n.n.n].zip file to download it From the zip file, extract mstpcap.exe Now you can use it via command prompt as described below or install it in C:\Program Files\Wireshark\extcap if want to use with modern Wireshark version.   To capture data follow these steps: Unzip file Open command prompt with window pointing at location of mstpcap.exe file.  For example:  c:\MSTP Tool> Daisy chain RS-485 adapter to trunk or connect Roam I/A to jack on MNB device. Command syntax is as follows:  mstpcap comx baudrate# do not type baudrate just speed. Control C to stop Example: If Using Roam I/A it requires highest baudrate available on the interface. ROAM I/A Serial port mstpcap comx 115200 If using Roam I/A Bluetooth mstpcap comx 76800 If using an RS-485 adapter it will not support 76,800. This is a PC hardware limitation not a software limitation for further information or instructions on how to use baudrate 76,800 consult text file titled mstpcap.txt or Steve Karg's website: http://steve.kargs.net/bacnet/wireshark-and-bacnet-mstp .  Example: mstpcap comx baudrate speed The capture file can be analyzed with WireShark Protocol Analyzer.  WireShark software is available at: http://www.wireshark.org

Issue How to backup and restore Vista databases Product Line TAC Vista Environment Vista Server Cause There are three different ways to backup/restore a Vista database. Each method has its own unique procedures. Resolution Vista database backup methods: Copy the database folder, you can compress the database into a ZIP or RAR file (ZIP preferred method of Product Support) Use the built in database backup feature (this is commonly used for scheduling an automatic database backup) Use the built in export feature (this is commonly used for partial database backup) Vista database restore methods (referring to backup methods accordingly): Restore from a copy of the database folder: Change the database path in Vista Server setup to the copy of the database folder. Restore from the .fvb file Use Vista restore database feature Restore from the exported filed Use Vista import feature

Issue Java 8 is only supported together with TAC Vista 5.1.9 Product Line TAC Vista Environment Webstation Xenta Server web Cause The current version was developed and tested together with Java version 7, but not Java version 8 as Java 8 was released subsequently After the latest update of Java (Java 8u31) SSLv3 has been disabled by default in Java. If updating to that version of Java, the Xenta Server web (graphics and schedules) will not work, as the Xenta Server relies on SSLv3. Resolution Making the proper configurations has enabled a number of sites to use Java 8 with the TAC Vista product range. Java 8 is supported for TAC Vista 5.1.9 according to TPA-VSTA-15-0000.03 Refer to this video for settings required: Download video - View on YouTube   The proper settings in Java are: [1] Install the newest version of Java. If you are working on a 64 bit operating system, it's crucial that you install both the x86 and the x64 versions: https://java.com/en/download/manual.jsp [2] Make sure all older versions are removed: https://java.com/en/download/uninstallapplet.jsp [3] Make sure Java is enabled in your browser: https://java.com/en/download/help/enable_browser.xml [4] Add all addresses to the site exception list in the "Security" tab. Both http and https addresses are needed for Xenta Servers. If a special port is used (not 80 for http and 443 for https), the port needs to be entered, e.g. http://IP_ADDRESS:81 if port 81 is used for HTTP communication. [5] Click "Restore Security Prompts" in the "Security" tab. [6] In some cases you might need to add the IP address of the PC or Xenta Server to trusted sites in Internet Explorer   TAC Xenta Server web uses SSLv3 for Java if high security is set in XBuilder. The workaround for SSLv3 being disabled in Java 8u31 and above is: (read Java's own release note) [1] Edit the following two files: C:\Program Files (x86)\Java\jre1.8.0_31\lib\security\java.security C:\Program Files\Java\jre1.8.0_31\lib\security\java.security [2] Scroll down to the last line where it says: jdk.tls.disabledAlgorithms=SSLv3 In both files, comment that line so it says: #jdk.tls.disabledAlgorithms=SSLv3 [3] Edit the file: C:\Users\%username%\AppData\LocalLow\Sun\Java\Deployment\deployment.properties [4] Add the following line: deployment.security.SSLv3=true

Issue This is the error message that is displayed when you attempt a connection. You get a LonMaker Error message when applying a connection. "this connection would violate a network variable selector constraint, which limits the number and type of NVs a device that may use the same selector. The automatic use of NV aliases was unable to avoid this) there may be no aliases available). Product Line TAC Vista Environment LonMaker Cause One NVO is attempting to be connected to multiple NVI's in one device. LonMaker does not allow the same NVO to be connected to the same receiving device more than once. Resolution Add extra NVO's in the sending device to allow for a one-to-one binding with the receiving NVI's.

Issue If the points of the 3 rd party system are integrated into Vista through OPC, how to create a Vista alarm for these points? Product Line TAC Vista Environment Vista OPC Server Vista Server Cause Sometimes OPC points also need to trigger alarms in the system. Resolution Create a Change of State object for the point that needs to trigger an alarm. In the Alarm tab, choose the alarm control for this alarm, while typing the Text for tripped alarm and reset the alarm. For analog value, alarm Low limit, High limit, and Minimum change can be set for the triggering boundary. For digital alarm, just keep the default setting for the limitation set. In the Object tab, choose the signal that needs to trigger an alarm. And also select the Referenced property to "Value".   Open the Property window of the signal and set the Watch Setting to "Alarm" or "Watch". Toggle the OPC point manually into the alarm and return to normal once to verify the alarm is in the queue.   For specific settings for I/NET points integration, refer to Additional settings necessary to receive Vista Alarms from an I/NET point for detailed information.

Warning Hazard of Electric Shock: Remove all power from all devices before removing any covers or doors of the system. Disconnect power at the device and at the power source. Issue Setting up a Xenta 121-HP to properly control a heat pump that has an internal reversing valve control, separate termination blocks for heating and cooling, and an isolation valve. Typically a unit with this configuration is designed to operate with a standalone thermostat that will signal a cooling call or heating call separately depending on the setpoint. A manufacturer in which this specific situation has been documented in the past has been McQuay heat pumps. Product Line TAC Vista Environment ZBuilder LonMaker NL220 Vista Cause If the 121-HP is configured in ZBuilder without a reversing valve but still has an isolation valve, it causes the isolation valve to close in certain situations. As seen in the screen capture below, when the reversing valve is unchecked, ZBuilder activates the "Compressor operation" setting box. The choices are either for the compressor to operate in cooling mode or heating mode. If cooling mode is selected then the 121-HP will close the isolation valve in heating mode and vice versa. Resolution There are two options that can be used to allow the 121-HP to control this specific kind of heat pump setup. Turn the 121-HP into a 121-FC Note: Using this method will completely change the controller and all bindings will be lost. It is suggested that the controllers be labeled 121-FC to help minimize future confusion. This method does not allow for a time delay between the isolation valve opening and the compressor command. Instead each goes off of different terminal load levels. Download the latest NXE-APB files for the 121-FC off of the Exchange Extranet. Then download the 121-FC APB file into the controller. Reference Downloading new NXE or APB files using Lonmaker for LonMaker and Downloading new NXE or APB files using NL220 for NL220 download help. Once the 121-HP has been converted into a 121-FC, set the template up with the following settings. Cooling set to On/off Primary heating set to On/of Fan set to On/off The final setting is to create a point that can be used as the isolation valve. Go to the Configuration tab > Free I/O > Function input and activate aux pump function. Underneath the activation, check aux pump active in heating mode and aux pump active in cooling mode. This aux pump feature will turn on whenever there is a terminal load and turn off in the deadband. Use a Relay with Traditional Heat Pump Setup In order to accommodate this type of setup, the following items and settings need to be in place. A relay needs to be installed off of the 121-HP The ZBuilder template needs to be configured in a typical heat pump configuration with a reversing valve present, isolation valve, and a single point dedicated to the heating/cooling compressor command. Under the configuration tab > Application > Valve configuration > Reversing valve, it should be set to a closed contact in heating mode The wiring diagram below is how the unit needs to be wired up to run properly. In this example K1 is the fan command, K2 is the reversing valve command, K3 is the heating/cooling compressor command, and K4 is the isolation valve command.

Issue Need to download the XIF and NXE files for a SVEA Lon I/O Module DR-N-3D1M (0-10V) module, but having difficulty locating these files on the Extranet. Product Line Andover Continuum, EcoStruxure Building Expert, EcoStruxure Building Operation, Satchwell Sigma, TAC Vista Environment SVEA XIF NXE Cause The difficulty in locating these files, is due to them being identified by their article number, in this case DR-N 3DIM. This number was used when these were classified as the SVEA devices. The Schneider version is now known as MTN881001, and not DR-N 3DIM. Resolution The Schneider Electric (MTN881001) files are located on The Exchange Download Center Download the XIF / NXE files for the SE MN881001 Download the XIF / NXE files for the SVEA DR-N 3DIM Note: It appears that although these devices are both classified as Lon I/O Module 1-10V, the XIF / NXE files are different.

Issue When you view a Xenta Log through Vista you get estimated values in the Log. Product Line TAC Vista Environment Vista 4.x.x Vista 5.x.x Cause If the site has many Xenta logs in 200,300 or 400 controllers you maybe exceeding the limit for trend uploads to Vista. The maximum limit is 4 uploads of Xenta logs per minute to Vista. If you exceed this value estimated values may appear in the Xenta logs. Here is a link to a white paper description on this topic TAC Xenta Trend Logs Whitepaper Resolution Here are some steps to check if the estimated values are caused from excessive Xenta trend upload.   Calculate the amount of uploads that are occurring in the database. As an example if a Xenta log is set to store information in the controller for 1 hour and upload at 80% full. This equates to 0.8 uploads per hour or 0.013 uploads per minute. If you work out this rate for all the xenta logs in the database you can then calculate how many uploads are occurring per minute. To extract all the Xenta Logs in the Vista database follow these steps also shown in the video. From TAC Vista workstation select View and then Search from the toolbar. select the browse option for the field "Type of devices or objects" Expand the heading labeled Files. Expand the heading labeled Trend Logs under the Files heading. Expand the heading labeled Trend Log Vista under the Trend Log heading Check the Trend Log Xenta box Select OK In the Property value dropdown list select the" Log size byte " option. This is the Xenta Log duration in seconds. Select the search Button The search results now show all the Xenta Logs. You may need to uncheck the "interrupt search if more than 1000 results" to capture all Xenta trends In the Search output Pane right mouse click and select "Additional properties" Expand the list and select "Retrieve at % Full option" The Search results then show all Xenta trends with Xenta Log duration and retrieve % full. Copy this list in Excel and calculate the uploads per minute from this Database. Below is an image showing the data pasted into Excel, displaying the equation to calculate the upload per minute value per log:  If you find your total "uploads per minute" exceed 4 then reducing this may remove the estimated values. Some ways to do this are. Extend the Xenta log storage time in the Xenta device if memory permits. Change the upload percentage to a greater number if it has been decreased below 80%  Increase the Xenta sample rate which will allow for the Xenta storage to be extended as in point 1.