Building Automation Knowledge Base

Issue Webstation static graphic viewer no longer works in Chrome, FireFox or on smart phones. The "Loading..." image never goes away. Environment Webstation Cause The file "xmlHttpImageLoader.js" located in "C:\inetpub\wwwroot\TACVistaWeb519\Modules\Graphics\ImageLoader" (519 being the version of TAC Vista installed) uses the name "status" for a variable in the script. This variable name is a reserved word. The name is actually not a reserved JavaScript word, but a reserved Windows word: http://www.w3schools.com/js/js_reserved.asp Resolution As only Internet Explorer is supported, this is not going to be fixed. There is however a workaround that will enable viewing graphics in static mode. 1. Rename the file C:\inetpub\wwwroot\TACVistaWeb519\Modules\Graphics\ImageLoader\xmlHttpImageLoader.js 2. Paste this corrected file to the same location

Issue Registering/Unregistering TAC Vista Server as a Windows service will allow the server to start automatically and run in the background of the PC (it won't show up on the Windows taskbar). This is not the same as having it run on Startup (for information on that, please see Configuring Vista Server to run on Startup). Product Line TAC Vista Environment Vista Server Microsoft Windows -- All versions Windows XP Windows Vista Windows 7 Windows Server 2003 Windows Server 2008 Cause Reference Chapter 16.3 of the TAC Vista Technical Manual "Running TAC Vista Server as a Service in Microsoft Windows XP" for more information. When you log out of Microsoft Windows or restart the computer, all running processes, for example, Vista Server, are shut down. These processes are not resumed at log on or at restart. You have to start Vista Server manually again. To get Vista Server to remain running at log off and automatically start up when the computer restarts, you can run Vista Server as a service. Running a program as a service means that it runs in the background, but it is not visible on the Windows task bar. Before you start Vista Server as a service, you must first install and configure your Vista Servers and your network and have everything running satisfactorily. It is not advisable to start Vista Server as a service until you have completed all the settings (including security and authority) and the TAC Vista system is running well. Resolution Register Vista Server to run as a Windows service Go to Start > Run Register the service by typing: Tacos.exe /service When you register TAC Vista Server as a Windows service, it will default to run under the "Local system" account.  This is not supported by TAC Vista Server. Right-click on My Computer and select Manage. Browse to Computer Management (local) > Services and Applications > Services Find TACOS, right-click and select Properties On the Log On tab, specify "This account:" with admin authority.  It is ideal to use a domain account with local administration authority if your system is a member of a domain. At this point, if you would like to start the service, highlight TACOS in the Services window and select Start the service. If you choose to run Vista Server as a service in a multi-computer network, we recommended that you run every Vista Server as a service. Change from running as a service to running as interactive Go to Start > Run Unregister the service by typing: Tacos.exe /unregserver You must then register the server back to interactive by typing: Tacos.exe /regserver Helpful Utility This utility will read in the current run mode of the Vista Server and allow you to switch between running as a service and an application. It also lets you set the user to run the service under. Click the image to the right to go to a Community post containing the utility .exe file. Accessing Vista Server Menus and Dialog Boxes Once the service has started, it is not possible to use the Vista Server menus and dialog boxes. To be able to use these, you have to unregister the service and start Vista Server in the normal way. LonTalk Adapter from Loytec When TAC Vista is running as a service and you are using a LonTalk adapter from Loytec, you must ensure that the program LConfig is also running as a service. You do this when you configure the network interface card. TAC Vista Tools and Microsoft Windows Vista Some of the tools installed in the installation folder of TAC Vista cannot run if TAC Vista is running as a service in Windows Vista. These are TAMIAN, CIPCL, SYSDOC, TADRAW, and DBGEN. Related Articles: Unable to save periodic report to network drive when Vista is running as a service Regional settings might differ when TAC Vista server runs as a service Dependencies for Vista Server running as a service Upgrading Vista while running Server as a service

Issue Error "Ensure that Vista Server is started" when the server is already running. Product Line TAC Vista Environment Vista Server Windows XP Windows 7 Windows Server 2003 Windows Server 2008 Cause Refer to Chapter 3.5 of the TAC Software Installation Manual for the network security and permissions settings required to run Webstation (DCOM). test Resolution These are some utilities created by Benjamin Roswall at Schneider Electric Denmark. They are not official releases nor are they supported by Schneider Electric. While they have been tested and used successfully, they should be used at your own risk.   DCOM Config 1.0.3.0.exe: Configure DCOM for TAC Vista Network If you want to run TAC Vista Web Applications on Windows Server 2003 Standard Edition, both Internet Information Services (IIS) and ASP.NET 2.0 must be installed. ASP.NET 2.0 must be installed and activated before you start installing TAC Webstation. Refer to Chapter 4 of the TAC Software Installation Manual for more information. If you've made it this far, then it's time to refer to Chapter 3.5 of the TAC Software Installation Manual for the network security and permissions settings required to run Webstation (DCOM). Or just run this utility. Click the picture to download the utility.   Webstation installations will use Option 3. If Webstation doesn't come right up and start working after this, also download the next utility.   WEB.exe: Corrects common problems with Vista Webstation This utility will install and register the versions of ASP.NET required for running Webstation on the server PC. There are other articles on the command prompt commands to accomplish this, but this utility will take care of it for you. Click the picture to download the utility.   After this utility finishes running, restart the PC as instructed.

Issue The status of a TAC Xenta 301 or 302 does not go 'online' in TAC Vista, although the Neuron Status property of the controller is 'online' and 'Commission and Download' from TAC Vista is apparently successful. Values read "Failed to Read Signal" in a values page of a classic network. Values read "Invalid Address" in a values page of an LNS network (also see [Invalid Address]) Controllers without /N/P (networking and presentation) designation cannot communicate in a Network. Product Line TAC Vista Environment Vista Workstation Vista Server Xenta 301 Cause Attempt to commission a standalone (non-/N/P) TAC Xenta 301 or TAC Xenta 302 in a TAC Vista Classic LON network.  Non-/N/P controllers are designed to run stand-alone and be configured/interact only with a Xenta OP. Resolution Check the sticker on the side of the controller where the controller type, hardware version, and neuron ID are found. Example of a 302/N/P label. Example of a non-/N/P 302 label.    If the sticker does not have /N/P following the controller type, this is not a network presentation controller.  It will never communicate on a network Replace the non-/N/P controller with an /N/P enabled version.

Issue The TAC Vista OPC server does not function using the evaluation license file for TAC Vista. Product Line TAC Vista Environment TAC Vista Server Evaluation License TAC Vista OPC Server Cause The TAC Vista OPC Server license is a separate license needed when a third-party program should read values from TAC Vista via OPC.  The TAC Vista OPC Server license is not included in the Evaluation License for TAC Vista.  Resolution If you had an existing OPC Server license and this needs to be transferred to a new PC, rehost the license as shown in the article Rehosting a Vista 5 License on the FlexNet License Server. If you need an evaluation license for TAC OPC Server, please contact your country-level Product Support.

Issue If I add a TAC Xenta device to an existing TAC Xenta group, do I have to update other Xenta devices as well? Product Line TAC Vista Environment Xenta programmable controller (e.g. 401, 301, 281) Xenta groups TAC Vista system plugin Cause Each programmable Xenta device needs to know the name of all the other Xenta groups, as well as all the Xenta device names in its own group. Each time a new group member is added, all Xenta devices in that group need to be downloaded. If a new Xenta group is added, all Xenta devices in all groups need to be downloaded.   This provides new network description files to the controllers so they can communicate properly. Resolution All Xenta devices in that group must be updated. LonMaker or NL220 and your Vista databases need to be updated as well. TAG bindings will also need to be added to the new TAC Xenta device if an LNS database is being used. The TAC Vista System plugin has the feature under the LNS Network menu. "Create Group Bindings" If this is a large site this will take some time and cause offline devices during this process. In this case, these bindings can be added manually to the new controller. This will prevent all the other devices having there TAG bindings deleted and the new TAG bindings created. The following articles show the process for manually adding TAG bindings. Manually adding a Xenta Device with Group bindings in NL220 Manually Adding Xenta device with Group bindings in Lonmaker

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 for assistance. Issue Error: "Could not create remote directory" or "Failed to establish connection with the target device" when trying to upgrade/downgrade a Xenta 5/7/9xx controller     Product Line TAC INET, TAC Vista, Satchwell MicroNet Environment Xenta Servers Xenta 511, 527, 527-NPR, 555, 701, 711, 721, 731, 913 XBuilder Cause This error can be caused by any of the following reasons: Trying to downgrade a Hardware version 2.x Xenta Server device to System Program version 2.10 or older Internet Options are configured to use a proxy server IP communication is not properly established due to incorrect IP settings, a bad cable or a faulty device The controller is 5.1.8 or lower and Microsoft KB 2661254 or KB 2661254-V2 is installed on the PC. In this upgrade Microsoft has changed the criteria for the certificate Key. Service packs are available on the extranet to correct this issue. Download blocked because of other Windows updates SSL 2 and 3 is not activated Resolution First, establish that the System Program that you are attempting to load is compatible with hardware version of the device. The older HW 1 versions can be upgraded to System Program 5.1.2 or older. Only system program versions 2.2.0 and newer can be loaded into devices that are hardware version 2.X. Hardware Version System Program 1.0 5.1.2 or older 2.X 2.2.0 or newer 3.X 5.1.6 SP1 or newer Note: Hardware version 1 devices are not labeled as HW 1 since only one version of hardware existed at the time. Hardware devices can be identified by the lack of any hardware version printed on the Neuron ID sticker. Note: If running the firmware update software, ensure you are running as an administrator. Next, check to verify that IP communications are configured properly and are functional: Check the IP address defined in XBuilder Verify a good connection to the IP port of the controller (10Base-T port on the far right) with a crossover cable. If that is all good, then a reformat of the controller may be necessary. Connect via Hyperterminal to the unit and at the dsh> prompt type format and press enter command . This will recreate the directory structure of the controller and allow you to attempt the upgrade/downgrade again. Finally, verify that the Internet Options are not configured to use a proxy server or, if they are, temporarily change them as follows: To temporarily change this setting follow these steps: In Internet Explorer select the Tools Menu and select Internet Options. Or select Internet Options from your Control Panel. Go to the Connections tab. Click the LAN settings button. Uncheck the Use a proxy server for your LAN box. Click Ok in the LAN settings window and the Internet Options window. Complete the System Program download. Return to the Internet Options window and re-check the Use a proxy server for your LAN box in the LAN Settings found in the Connections tab. Another Matrix explaining the compatibility of each with Vista versions can be found in Xenta-Server-firmware-versus-Vista-Server-versions If you have the Xenta FW 5.1.8 or lower and KB 2661254 or KB 2661254-V2 were installed during a Windows Update you will need install the service packs. These new service pack builds have been released and are available on the extranet. See TPA-VSTA-12-0028.00 - TAC Xenta Servers, Not Possible to Download Firmware for more info. Another issue has been reported to support relating to the bit length of the Xenta server boot certificate. The Xenta server installer uses a 512 bit key length of the boot certificate, and Windows in some instances can be configured for a 1024 bit length certificate. If the issue still exists after removing the above mentioned Windows Updates, or if you are getting this error and the Windows Updates are not on your machine. Download the attached tool, Allow Weak Certificates.zip, and execute the file, chose "Allow Weak Certificates", and "Update".   Here is what the tool set: Windows Registry Editor Version 5.00 [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Cryptography\OID\EncodingType 0\CertDllCreateCertificateChainEngine\Config] "EnableWeakSignatureFlags"=dword:00000002 "minRSAPubKeyBitLength"=dword:00000200 If taking the preceding steps fails to resolve the issue then see the following articles for additional steps that can be taken: Xenta Server "Run" light is solid red, with no communication via Ethernet,  Fail to upgrade the TAC Xenta Server system software (firmware)  An unexpected error occurred while downloading using a Xenta Server

Issue When having issues with a specific NCI (SCPT or UCPT) in a XIF file it can be hard to understand the FILE definition in the XIF file in order to troubleshoot a given issue For information regarding NCI's that are not part of a FILE definition, refer to Understanding the NVVAL part of a XIF file Product Line EcoStruxure Building Operation, Satchwell MicroNet, Satchwell Sigma, TAC IA Series, TAC Vista Environment LonWorks XIF Cause The FILE definition can be somewhat cryptic - here is an example   FILE template 0 2 "1.1;" "2,23.24.25.26.27.28.29.30.31.32.33.34.35.36.37.41.42.43.45.46,0\x80,49,2;" "1,1,0\x80,60,12;" "1,1,0\x80,52,2;" "2,0.2.3.5.6.7.8.9.10.16.17.18.19.20.21,0\x80,48,2;" "1,0,0\x80,17,31;" "1,1,0\x80,34,2;" "1,1,0\x80,23,2;" "1,1,0\xA4,169,1;" "1,1,4\x80,3,8;" "1,1,4\x80,5,17;" "1,1,3\x80,1,2;" "1,1,4\x80,4,9;" "1,1,4\xA4,13,1;" "1,1,4\xA4,14,1;" "1,1,4\xA4,15,1;" "1,1,4\xA4,16,1;" "1,1,4\xA4,17,1;" "1,1,4\x80,18,1;" "1,1,0\x80,42,2;" "1,1,0\x80,36,2;" "1,1,0\x80,193,2;" "1,1,4\x80,8,2;" "1,0,3\x80,2,2;" "1,0,0\x84,165,1;" "1,0,0\xA4,166,1;" "1,1,6\xA4,2,8;" FILE value 1 1 116 0x0B, 0xB8, 0x09, 0x1D, 0x09, 0xFB, 0x0B, 0x80, 0x08, 0x77, 0x07, 0x98, 0x06, 0x13, 0x00, 0x02, 0x23, 0x28, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x78, 0x7F, 0xFF, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x80, 0x80, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x01, 0x00, 0x00, 0x00, 0x00, 0x00, 0xFF, 0xFF, 0x7F, 0xFF, 0x7F, 0xFF, 0x13, 0x88, 0x00, 0x00, 0x02, 0x0B, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00 Resolution The FILE section describes the configuration variables (or SCPT's and UCPT's) for a device. Here is an explanation of the various parts of the FILE section.

Issue TAC Xenta 527 - Embedded Web Server Product Line TAC INET, TAC Vista Environment I/NET Seven or Vista site Cause Need information concerning the TAC Xenta 527 - Embedded Web Server Resolution Information Technology Brief: The TAC Xenta® 527 is a web based presentation system for TAC Vista LONWORKS and I/NET Seven® networks. In addition, to supplementing the host workstation interface with web access, the TAC Xenta 527 can also be used as the sole operator interface into I/NET Seven and TAC Vista LONWORKS systems. A single Xenta 527 will handle small to midsized systems, and several devices can be used to handle larger networks. The web pages are based on standard Internet technology as HTML and Java™ Applets. Alarms can be forwarded as e-mail. Please use the following link: Xenta 527-23 June.doc

Issue Step-by-step instructions for calibrating airflow on a Xenta 102-AX (or I/NET MR-VAV-AX) using the M/STAT. Test and air balance procedure for balancing airflow Product Line EcoStruxure Building Operation, TAC INET, TAC Vista Environment Xenta 102-AX MR-VAV-AX M/STAT Cause The preferred method for calibrating airflow in Xenta 102-AX or MR-VAV-AX is through the plug-in.  However, this is not always an option, especially when the responsibility for calibrating is given to a third party test and balance company.  Pocket references exist for navigating through the M/STAT menu, but there aren't clear step-by-step instructions to tell exactly how to perform the calibration. Resolution Click here to download this document in Microsoft Word format Connect M/STAT Plug the M/STAT into the jack on the thermostat. The initial display shows the set temperature.   Enter Password Press the Service button. This prompts you to enter the service mode password. Default password is 183. Use the +/- keys to set each digit and the enter key to submit. If the password is incorrect, the display will blink. Airflow Parameters If the password is correct, the first menu option – Unit Parameters (UP) – is displayed. Hit the select button down twice until Airflow Parameters (AP) is displayed. Press enter. Cooling Low Flow Setpoint The first option is Cooling Low Flow Setpoint (CLF). Press enter to view the setpoint (divided by 1000). Record this value. Press the service key to escape out of the menu. Cooling High Flow Setpoint Navigate to Cooling High Flow Setpoint (CHF). Press enter to view the value (divided by 1000). Record this value. Press the service key to escape out of the menu. Reset Factory Calibration Navigate to Factory Calibration Settings (FCS) and press enter. Use the change keys to display “YES” and press the enter key. This will set the box back to default settings. This is a good idea to do prior to every calibration. Press the service key to escape out of the menu. Calibrate Low Airflow Navigate to Calibrate Low Airflow (CPL). Press enter and the current airflow is displayed. Wait for the airflow to reach the CLF and level out. Once the value is steady at setpoint, press the enter key only once. The display does not change. Enter Actual Low Airflow Measure the actual airflow. Use the change keys to set the display value to the measured value. Press the enter key. Choose One or Two-Point Now Calibrate High Airflow (CPH) is displayed. If one-point (offset only) calibration is desired, press the service key to escape out of this mode and calibration is complete. If two-point (gain and offset) calibration is desired, press enter to continue to the next step. Calibrate High Airflow The current airflow is displayed again. Wait for it to rise to meet the CHF and level out. Once the value is steady at setpoint, press the enter key only once. The display does not change. Enter Actual High Airflow Measure the actual airflow. Use the change keys to set the display value to the measured value. Press the enter key. CPH is displayed again, this time as a general menu item. Escape Service Mode Press the service key to escape out of the menu. If you are finished configuring the box, escape all the way back out of the service menu before disconnecting the M/STAT. Disconnecting in configuration mode can leave the stat displaying “00” or other incorrect numbers.

Issue In the event of a lost or broken connection between the Vista Server and SQL server, the Vista Server will begin to queue up its events and log values in the $queues\insertevents and $queues\insertlogvalues directories. Once your connection has been re-established those queued files will then be written to the Vista DB, however this process can take an extremely long time,  and possibly cause the Vista server to hang at start up and even crash.  Product Line TAC Vista Environment Vista 4.3.0 or higher with SQL  Cause Broken SQL connection between Vista and local or remote SQL server. Resolution If you are not in the need to this queued event and log data you can manually delete all of these queued files. Opening this directory with Windows, highlighting all files and deleting them usually does not work, because of the enormous amount of files that may be stored in their respective directories. The best way to delete these files is to use DOS. Remember stopping both TAC Vista Server and the DSS Writer service before deleting the files.   Method 1: The proper steps to delete these files with DOS using the "rmdir" command are: Click Start > Run Type "cmd" and press enter Use the DOS command "cd.." followed by enter to navigate up one folder in the hierarchy.  Repeat this command until the prompt is at the root directory and shows C:\> Use the DOS command "cd " to navigate to the Vista database folder location and the $queues folders.  For example: C:\>cd Projects C:\Projects>cd School C:\Projects\School>cd VistaDB C:\Projects\School\VistaDB>cd $queues Type "rmdir /S /Q insertevents" - all files and folders including the "insertevents" folder will be deleted Use the cd.. and cd commands to navigate up one folder and back down into the insertlogvalues folder C:\Projects\School\VistaDB\$queues\insertlogvalues> Repeat step 5.   Method 2: The proper steps to delete these files with DOS using the "del" command are: Click Start > Run Type "cmd" and press enter Use the DOS command "cd.." followed by enter to navigate up one folder in the hierarchy.  Repeat this command until the prompt is at the root directory and shows C:\> Use the DOS command "cd " to navigate to the Vista database folder location and the $queues folders.  For example: C:\>cd Projects C:\Projects>cd School C:\Projects\School>cd VistaDB C:\Projects\School\VistaDB>cd $queues C:\Projects\School\VistaDB\$queues>cd insertevents C:\Projects\School\VistaDB\$queues\insertevents> Type "del *.*" and then "Y" to confirm that all files on that directory will be deleted. C:\Projects\School\VistaDB\$queues\insertevents>del *.* C:\Projects\School\VistaDB\$queues\insertevents\*.*, Are you sure (Y/N)? y Use the cd.. and cd commands to navigate up one folder and back down into the insertlogvalues folder C:\Projects\School\VistaDB\$queues\insertlogvalues> Repeat step 5. Now both of these directories should be emptied and if your SQL connection issue has been rectified your events and logs will write as normal to SQL.     Alternatively, this utility will split the queued files into folders of 4,000 files each.  Windows can handle each of these folders and make the task of deleting the queued files more manageable.  Click the screen capture below to download the utility.  

Issue When creating a Modbus device template in XBuilder Device Editor which Modbus register data type should be used? Product Line Satchwell MicroNet, TAC INET, TAC Vista Environment Xenta Servers Xenta 511, 527, 701, 711, 721, 731, 913 XBuilder Modbus Register Bitmask Cause Lack of consistency between Modbus slave manufacturers there is a large number of data formats that can be selected. Each register format interprets the value differently based on byte order or purpose of the specific bits. Resolution Consult Modbus slave product documentation Use trial and error to find the correct register format. Perform communication logging to capture the raw data and compare with a known value to determine the format. As a tool to assist with these steps please consult the Definition of Modbus Registers.

Issue Instructions and programming example for using nviEmergCmd to control the damper on the Xenta 102-AX Environment Xenta 102-AX Menta Cause In some situations it is necessary to have the Xenta 102-AX damper open to 100% for smoke control, or other sequence of operations specific tasks. There are different emergency modes which all perform a different function. Resolution The damper position on the 102-AX can be controlled to 100% or to 0% by using the SNVT input nviEmergCmd. Please see the attached Menta file as a programming example. The enumeration breakdown and controller actions of nviEmergCmd are as follows: 0 = Emerg Normal - Normal operation of the controller without any emergency command. 1 = EmergPressurize  - 102-AX will control to its max cooling CFM setpoint. 2 = EmergDepressurize - 102-AX will control its damper to 0% and shut off all other outputs. 3 = EmergPurge - 102-AX will control the damper to 100% 4 = EmergShutdown - 102-AX will pause control on the damper and disable all other outputs. 5 = EmergNull - Null SNVT value NOTE: Any value change on nviEmergCmd will initiate a damper resynchronization. This will cause the controller to fully close its damper, fully close any floating control outputs, and disable any other hardwired outputs for their full stroke time (throttling range).

Issue General use of the Wireshark program. Product Line Access Expert, Andover Continuum, EcoStruxure Building Expert, EcoStruxure Building Operation, Pelco, Satchwell MicroNet, Satchwell Sigma, TAC IA Series, TAC INET, TAC Vista Environment Ethernet Networks Cause General Information on using WireShark. Resolution Wireshark is an Ethernet packet analysis programme, Which can be downloaded from: Latest version available from Wireshark Locally stored version 1.0.9 Installing Wireshark If necessary, unzip the WireShark executable file to a suitable location on the PC/Laptop you wish the programme to be installed on. Run the executable file and follow the on-screen instructions. Rules for capturing LAN traffic using Wireshark: Do not use a switch or router to connect the LAN capture PC to the network as these will filter important network activity that you will need to see. You will want to capture everything that is passing over the network at the point of concern. Usually, this means tapping into the ethernet at the Controller or controllers, that is having an issue. midBit-Technologies-LLC-10-100 is an example of a device that can be used to easily tap into the network to take the capture. The monitoring PC must see all traffic from the controller's point of view. The monitoring PC can be connected in either two ways: Connected to the network at the controller The customers IT department can mirror all the network traffic from the controllers port to another port the PC can be connected to. If connected to the network at the controllers, the connection must be made through a true ethernet hub. A hub will not selectively filter important network traffic as a switch or a router will do. More information on what a "true ethernet hub" can be found at http://wiki.wireshark.org/HubReference There are however some switches that feature port mirroring, please see How to Configure a NETGEAR Prosafe Plus Switch for Mirroring. If connected to a mirrored port, the port must mirror 100% of the network traffic to and from the controller. No filtering should be done. Once a complete capture file has been obtained it can be filtered after the fact using WireShark or EtherReal. Using Wireshark Run WireShark Start a trace by choosing the "Capture" menu and then select "Interfaces" Choose the appropriate interface. Generally, this can be identified by its IP Address, but if not, then the packets increasing are an indication. Press the "Start" button. The trace will start and will be similar to the following screenshot. After an appropriate time, the trace can be stopped by selecting "Capture" menu and "Stop" To save the capture file, choose "File" menu and "Save As".

Issue This utility, TAC Vista Check References, will check references (every binding and every link) on every graphic at once and provide a summary of any empty or invalid database paths. It will also allow you to correct these broken or missing links and bindings. Environment TGML Graphics Vista Workstation Links/Bindings Cause Viewing the bindings or links of a TGML graphic can traditionally only be done on individual graphics one at a time. In addition, to see if a network path is invalid, it must be clicked on and will turn red if there is a problem. Resolution This utility was created by Benjamin Roswall at Schneider Electric Denmark. It is not an official release, nor is it supported by Schneider Electric. While it has been tested and used successfully, it should be used at your own risk. Download the TAC Vista Check References Utility by clicking here. Unzip the file onto the harddrive, view extracted files Double click TAC Vista Check References.exe Make sure Vista Server is running, click Login and log in to the database Choose whether to check for empty paths, and whether to validate .[OBJECT] bindings Click Check A summary of the network can be viewed and saved by switching between tabs.

Issue Need a M-bus device template for Multical 602 to use in Xbuilder Environment Vista 5.1.8 Xbuilder 5.1.8 Cause an Xbuilder device template for Multical 602 is required to integrate it with a Xenta Server (such as Xenta 913) Resolution Here is a M-bus device template for the Multical 602

Issue Set extra DCOM Settings when TAC Vista Server and Remote Work Station in Workgroup. Environment TAC Vista Server Remote Workstation Cause Cannot access TAC Vista Server from Remote Workstation, even though DCOM's set properly (in Workgroup). Resolution When using Remote Workstation and TAC Vista Server in same Workgroup and completing the DCOM settings based on the TAC Vista Installation Manual (04-00001-xx) and you still cannot access the TAC Vista Server PC, try the settings in the attached the document. Click here to download. Also refer these articles for more information: Helpful Vista Utilities - Configure DCOM instantly, Register ASP.NET Error: The RPC server is unavailable. Connecting from a TAC Vista Remote Workstation says "Ensure that TAC Vista Server is started" error, even though DCOM is set correctly Necessary Accounts for DCOM and Firewall Security Settings

Issue Example Menta Programming using a STR as Setpoint adjustment to an Xenta I/O Module Environment Adjustable 10k Thermostats Menta STR-102 STR-103 STR-104 STR-105 STR-106 STR-107 STR-201 STR-202 STR-203 Cause Interfacing a STR to Xenta I/O Resolution Program an Analog Input to a Universal Input of an I/O Module Click on the HFB above to download this .MTA file.   The Expression Block is taking the hard coded -9 to 9 input and making it adjustable from the front end.   In simulation with a Calibrated Range of 5 the following setpoint results are produced: Analog In -9 -8 -7 -6 -5 -4 -3 -2 -1 0 1 2 3 4 5 6 7 8 9 Setpoint -2.5 -2.2 -1.9 -1.6 -1.3 -1.1 -0.8 -0.5 -0.2 0 0.2 0.5 0.8 1.1 1.3 1.6 1.9 2.2 2.5 Note: This example is for a non-linear input, with a setpoint adjust of +/-9. For a metric calculation, use a setpoint adjust of +/-5  and change the calculation in the expression block to A*B/10.  

Issue When running TAC Vista in a Network environment, there are several ways of setting up the license system. Sometimes, TAC Vista nodes (Vista users) "steal" license modules for each other. Environment Vista in network Flexnet license Cause When various TAC Vista systems are pointed to the same license server, one server can take or "steal" e.g. an OPC Client license which another server should use. Resolution For a complete explanation about the license system and how to setup the system and control licenses, refer to this video. A useful tool to use is the Options file, with the .opt file extension. Located in the License files folder, its easily monitored in a text editor, and could be used for Reserving or Excluding license modules for other TAC Vista nodes. Other features available for the Options file can be found in the Flexnet Licensing End User Guide. 1: Make a file called taclic.opt and place it in the same directory as the license files. 2: Edit the file with notepad and make the reservations you need. The syntax for each line in the file is "command amount feature HOST host". The feature names can be seen in the license files. Here is an example on how to reserve an OPC Client license for a PC called "BMS_SERVER_1" RESERVE 1 Vista.Server.OPCClient HOST BMS_SERVER_1 3: Restart the license server.

Issue What NEMA or IP rating is a specific product? Environment All devices Cause Is a product protected against water and access by foreign objects? Resolution The Degrees Of Protection document details both the IP rating and NEMA Enclosure charts. The IP rating is made up of 2 digits, the first is the level of protection to foreign objects, the second is the level of protection to water. If a product does not specify any rating for water ingress in it's datasheet then the the second digit will be 0. The first digit relates to the size of a foreign object that can be inserted into the product. Typically many Buildings products will not allow the insertion of a finger (12.5mm approx' 1/2") and offer no water protection, so they would be rated as IP20, however it would be IP10 should they have holes of up to 50mm (approx' 2").