Building Automation Knowledge Base

Issue A message saying "no license available" or starting the license finder popup.  Sometimes Flex license system needs a little extra time to load the licenses. Product Line TAC Vista Environment FLEXnet Licensing Cause The problem is in the Flex license system and not in TAC Vista, the same issue occurs on other Software vendors using the same license system. Resolution Make sure that you are logged in as an admin on the computer. Right-click on This PC > Properties > Advanced system settings Click the button in the lower-left corner labeled "Environment variables" Add a new system variable named FLEXLM_TIMEOUT Give it the value 3000000, press OK Restart TAC Vista Server and Workstation, the Flex license system will now have 3 more seconds before throwing out a message saying "no license available" or starting the license finder popup.

Issue Many LonWorks network installation problems can be avoided if the appropriate network design rules are followed when the network is being designed. Product Line TAC IA Series, TAC Vista, Satchwell Sigma Environment I/A Series MicroNet (LON) Controllers Satchwell Sigma MicroNet series LON Controllers Vista Xenta Controllers Cause The I/A Series MicroNet System Engineering Guide (F-26507) was written as a resource of information for the installation of the I/A Series MNL-100, 200 & VAV controllers as well as the Sigma MicroNet 440 and 620 controllers.  The Resolution, below, is a summary of the LON design rules presented in this document. Resolution FTT-10 LON network wiring must be installed using Echelon-approved wire.  The most common type of wire used is described as Category 4  cable.  This wire is normally unshielded stranded twisted-pair 22AWG (0.65mm).  An example of this wire is the W221P or W222P series cable from Connect-Air International (http://www.connect-air.com).  This type of cable is normally available both in plenum rated and non-plenum rated types.  Consult the job specifications to determine if plenum-rated or shielded cable is required. The LON network can be wired using "Free Topology" or "Bus Topology" wiring segments.   1.  BUS Topology Guidelines BUS Topology LonWorks wiring extends from device to device (daisy chain format) with no branches or stubs. A LON-TERM-2 terminator must be installed at each end of the LON bus. When using standard Category 4 LON cable with the recommended terminators, the bus may be up to 4593 feet (1400 meters) in length. When extending LON wire to the MN-Sx sensor base in a bus topology network, the sensor base must be wired as part of the daisy chain and not as a stub connection. 2. FREE Topology Guidelines Free Topology imposes essentially no restrictions on the layout of the network -- some controllers may be wired point to point and others branching from a common point.  The free-topology LON network must be terminated at one point with a LON-TERM-1 terminator. When using standard Category 4 LON cable, the total wire length in a free topology LON network may not exceed 1641 feet (500 meters).  In addition, the longest wire path between any two controllers on a free topology LON network may not exceed 1312 feet (400 meters). 3. Common LON Network Wiring Guidelines LON wiring can not be part of an active bundled telephone trunk even if the telephone trunk is wired with Category 4 wire. Shielded Category 4 wire may be used in high EMI/RFI environments.  The shield must be wired continuously and grounded through a 470 Kohm resistor at one end. LON wiring must not be bundled with or housed in the same conduit as controller I/O and power wiring.  4. LonWorks Network Wiring and Addressing Guidelines When the number of controllers on a LonWorks network exceeds 60, the network must be split into segments with not more than 64 controllers or devices per segment using LonWorks Repeaters or Routers.  When counting the controllers and devices on a LonWorks network segment, a LonWorks Network Interface Device and the repeater itself must be included in the device count in each segment. In a LonWorks network containing repeaters or routers, each LonWorks network segment must be properly terminated, as described above. Domain / Subnet / Node addressing is used when configuring the LON controllers. A LonWorks Subnet consists of a series of LonWorks controllers all configured within the same LON Subnet number. A single LonWorks Subnet can have a maximum of 127 device and controller Node addresses.  This Node address count includes the LonWorks Network Interface, all controllers on the subnet, and repeater and/or router node addresses.  An allowance is typically made for additional addresses to be used by LonWorks tools connected to the Subnet.

Issue When a SE7000 is setup in Vista you cannot configure the device using the nciCfg1FcuZn and nciCfg2FcuZn Product Line EcoStruxure Building Operation, EcoStruxure Building Expert Environment Building Operation Workstation Building Operation Automation Server SSL SE7000 Cause The configuration NCI's are not made available for Vista. Resolution To edit these values the lonworks plugin can be used or the front keypad on the sensor itself.

Issue There is only 1 input available, but the end-user wants more than 1 sensor to be connected, where the reading will be averaged. Product Line EcoStruxure Building Operation, EcoStruxure Building Expert Environment Building Operation Workstation Building Operation Automation Server SSL SE8000 Cause The wrong sensor type or incorrect wiring might have been used. Resolution 4 resistive sensors of the same type are required. Depending on scenario, 2 sensors may have to be fitted adjacent to each other, or fit 2 sensors into 1 sensor housing to achieve the correct number of zones to be monitored. For wiring follow the drawing below:

Issue Windows System Information may be requested by Technical Support to assist with a reported issue. Product Line All Product Lines Environment Microsoft Windows Operating System Cause Unspecified cause. Resolution Press WINDOWS + R on the keyboard of the Windows system that you wish to obtain the report from. The Windows key is usually located between the CTRL and ALT keys and has a picture of a flag on it. Type Msinfo32.exe and click OK The System Information tool will start. Click on File > Sav When prompted, save the *.nfo file to an accessible location. Email the *.nfo file to your support representative.    Note: This application can also be accessed from Start, All Programs, Accessories, System Tools, and System Information. Using this method will open the System Information for XP and Windows 7, 32 and 64-bit computers. Refer to: Description of Microsoft System Information (Msinfo32.exe) Tool

Issue Windows update KB4519976 causes all Xenta servers to go offline in TAC Vista every few minutes. Product Line TAC Vista Environment TAC Vista Server Microsoft Windows 7 or Microsoft Windows 2008 Server Xenta 500 Xenta 700 Xenta 900 Cause After the Windows update, KB4519976 is installed, the SSL handshake behavior is changed. This affects TAC Vista and its communication with the TAC Xenta server. Resolution There are two workarounds available at the moment. Solution 1: Uninstall Windows update KB4519976 Solution 2: Turn off SSL for the communication between TAC Vista and the TAC Xenta server using the registry setting shown below. This means that only the login will be encrypted when TAC Vista is communicating with the TAC Xenta servers. Run the utility TacosTweak.exe, located in the program folder where TAC Vista is installed. Set "Only use SSL for login to TAC Xenta Servers(5xx/7xx)" to 1 to run the communication between TAC Vista and TAC Xenta servers without SSL. Restart the TAC Vista server for the changes to take effect.

Issue The specifications and setup details of the EH series humidity sensors. Product Line Andover Continuum, EcoStruxure Building Operation, Field Devices, TAC IA Series, TAC INET, TAC Vista Environment Humidity Sensor Cause The EH Series Room, Duct and Outside humidity sensors are a universal Relative Humidity transmitter that can be powered with either a +15 to 36 Vdc or 24 Vac supply voltage. The EH series sensors are designed with a field selectable 4-20 mA, 0-5 Vdc, or 0-10 Vdc output signal that is equivalent to 0 to 100% RH. The EH Series is used in building automation system, humidity chambers, and OEM applications and is compatible with Vista, Continuum, I/Net, I/A, and SmartStruxure systems. Resolution EH Series Humidity Sensors Click the below links to look at the documentation for these sensors including the dip switch settings. EH Series Humidity Sensor Data Sheet EH Series Humidity Sensor Installation and Operation Instructions Old EH Series Humidity Model For information on the older style of dip switches (models with two separate sets of dip switches), see the document below. Old EH Series Humidity Sensor Installation and Operation Instructions

Issue A Trend chart in TAC Vista Workstation is opened and set to show values for the last 4 months, but not all values are shown in the Trend chart. Product Line TAC Vista Environment TAC Workstation Cause The Trend chart can display maximum 50 000 values. So if you log often and want to display for example the last 4 months, only the latest 50 000 values will be displayed. Resolution There is no way around the 50 000 values limit for the Trend chart. To see all values for the last 4 months you need to create several Trend charts.

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 Point values are not displayed in Vista Workstation.  Instead, all of them say [??787]. Product Line TAC Vista Environment Vista Workstation Cause The most common cause of the ??787 error message is a mismatch in the XIF between the device and the Vista database.  It may also be duplicate SNVT names in the XIF. Resolution There are a few common troubleshooting techniques that have been applied successfully to the ??787 error and resolved the issue.  The first is to upload parameters from the device.  The second is to browse the correct XIF to the device to eliminate any mismatch. Upload parameters Right-click on the device in Vista Workstation. Select Upload Parameters. Shut down Vista and restart. Make certain you are using the correct XIF The only way to be absolutely certain that the XIF in the device matches the one in the database is to upload the XIF from the device.  You may need to create a dummy LNS database to do so.  Add a generic device and commission with the option to upload the XIF from the device. Update the Vista database.  Again, this may need to be a dummy Vista database. To obtain that XIF, right-click on the device in Workstation and select Properties.  The XIF File tab lists the database copy of the XIF file (hexadecimal file name) that can be found in the Vista database directory in the $thisfil folder. Browse the correct XIF into the Vista Workstation If you are certain you have the correct XIF, right-click on the device in Vista Workstation.  Select the XIF File tab. At the bottom under Source File, click the "..." button and browse to the XIF file. Click okay.  Log out of Workstation and log back in to see the changes take effect. It may then be necessary to right-click on the controller and select Commission and Download. Remove duplicate SNVTs Open the XIF in a word editor (Notepad, Wordpad) Find the duplicate SNVT name using the Find feature Rename one of the SNVTs to a unique name. Use the above steps to browse this new XIF into Vista Workstation. XIF file contains internal variables Open the XIF in a word editor (Notepad, Wordpad) Search for the variable whose value displayed as [??787] If the variable is not listed in the XIF file, it is possible that this is an internal variable which Vista cannot read a value from Contact the manufacture of this device and ask if they can expose the value with a network variable in order for Vista to read it.

Issue What TAC Xenta I/O modules could act as a Stand-Alone LonWorks device? Product Line EcoStruxure Buildings Operation, TAC Vista Environment EcoStruxure Building Operation  LonWorks TP/FT-10 Network TAC Xenta 420A TAC Xenta 421A TAC Xenta 422A TAC Xenta 450A TAC Xenta 451A TAC Xenta 452A Cause It is only TAC Xenta 421A, 422A, 451A, and 452A that can act as Stand-Alone LonWorks devices. Resolution It is only TAC Xenta 421A, 422A, 451A, and 452A that can act as Stand-Alone LonWorks devices. TAC Xenta 400 I/O modules without -A, will not work as Stand Alone LonWorks devices. Once communication has been established with the Xenta I/O module the green status led will flash on for 1 second every 10 seconds indicating it is in Stand-Alone mode.   In Building Operation, the Lonworks devices list will show devices without an "A" after it. This may lead to the wrong conclusion that these devices can be added as stand-alone devices, but that is not the case. These devices are listed so that they can be added manually to a programmable Xenta device as an IO module.

  Issue TAC Xenta I/O modules working as LonWorks device, indicates offline, flashes fast after power restore. Product Line TAC Vista, EcoStruxure Building Operation Environment XENTA421A XENTA451A Cause When the TAC Xenta I/O modules are used as Lonworks devices, this is indicated by the LED that flash once every tenth second. After a power failure, the device will indicate offline by 5 flashes per second.   The device will indicate offline until it gets an update to any nvi or nci variable. Resolution As soon as the device gets an update on any nvi or nci, it will again start to flash once every tenth second. This means, that if you only read variables from the device, that is, only uses its inputs, it may indicate offline until the next time the configuration is changed.   A workaround for this issue could be to just use a dummy output, that is updated regularly.  

Issue What does that controller/device look like Product Line Andover Continuum, EcoStruxure Building Expert, EcoStruxure Building Operation, Field Devices, Satchwell MicroNet, Satchwell Sigma, TAC IA Series, TAC INET, TAC Vista Environment Site with TAC or Schneider Electric Controller(s) Cause Questions concerning what a controller looks like, or if there are no labels on the controller which help identify. Are photographs or drawings available? (This is an article in progress. Have one that is not listed? Please help by taking a good picture(s) and including or send to Product Support) Resolution I/NET: 7728 7728 Left side 7728 Right side  7790 7790 side 7790 older model  7790 older model side  7798C Top 7716 7920 7920 side  MR-AHU MR-AHU left side MR-AHU right side P8UI8DO Expansion board  SCU1284 SCU1284 side Continuum: ACX5720 ACX5720 Open CX9702  b4920 b4920 Open BCX1 BCX1 open i2-600 Series i2.600 Series Open  i2_850 i2_850_Open i2_887_L_115  i2_920 i2_920_open CX9400 with three 32s and two 16s in 8 card rack CX9400 CPU front CAD Drawings for the Continuum controllers are also available on The Exchange Download Center: Link Here.

Issue When EcoStruxure Building Operation (EBO) is installed after TAC Vista on the same PC, changes to the national character set in the OP Configuration Tool in Menta cause an error preventing the generation of the MTA file. The error appears when the Generate command is selected in Menta. Depending on the combination of versions of EBO and TAC Vista, the error message is: "National character set not selected" "Cannot open file: struxureware path\ national.dec" (where struxureware path is the location of the Schneider Electric StruxureWare\ Building Operation 1.x installation folder) "ERROR! Failed to create OLE dispatcher: GraphOP.Application.320, GraphOP.Application.NSP" Product Line TAC Vista, EcoStruxure Building Operation   Environment Building Operation Workstation Vista Workstation Cause The installation of EBO overwrites settings in Menta regarding character sets. When Menta is opened with normal user rights, changes to character sets in the OP Configuration Tool are not saved due to the OS user security settings. Resolution Right-click on Menta in the program list and select "run as administrator". Then select your required character set in the OP Configuration Tool ("Formats | Character set file"). The changes can now be saved and Menta will generate successfully. This procedure is only required the first time you run Menta after installing EcoStruxure Building Operation. Normal user rights can be used for subsequent editing sessions.

Issue TAC Xenta I/O modules do not come online after a download from System Plug-In Rapidly blinking green light on I/O modules show offline status (fast blink) Product Line TAC Vista Environment Xenta 400 series I/O modules Cause No I/O assigned to the module in the Menta file Needs a power cycle after download to associate with the base unit Resolution Verify that at least one hardware input or output is assigned to a terminal on the I/O module. If the I/O module is a spare that has been added for later expansion capabilities, it will never associate with the master or report an online status. If this is the case, assign a "dummy" input to the module temporarily if the rapidly blinking LED is a concern. Sometimes even if all of the correct information is downloaded to the TAC Xenta controller, the green light is still blinking rapidly (not configured) on the TAC Xenta I/O module. If this happens try to power cycle the TAC Xenta controller.

Issue Need to capture steps taken to reproduce a problem or a solution Product Line Andover Continuum, EcoStruxure Building Expert, EcoStruxure Building Operation, Field Devices, OTHER, Satchwell MicroNet, Satchwell Sigma, TAC IA Series, TAC INET, TAC Vista Environment Windows 7 Windows 10 Windows Server 2008, 2012, 2016 Cause A series of screen captures will help to demonstrate the steps needed to reproduce a problem or a solution. You can use this tool to capture the steps you take as a problem occurs and send the output to someone so they can see a screenshot of each step. Resolution In Windows click on the Start menu button  Type "PSR" Windows 7Windows 7 Windows 10, 2012, 2016Windows 10, 2012, 2016 Open the Problem Steps Recorder Windows 7Windows 7 Windows 10. 2012, 2016Windows 10. 2012, 2016 Click Start Perform the desired tasks Click Stop Choose a location to save the file output The .zip file will contain a .mht file which can be opened in a web browser The screenshots will appear in order  This will be followed by a detailed output of keystrokes and mouse movements. For additional information please refer to Microsoft webpage on this topic: Record steps to reproduce a problem 

Issue The License Server is not working and may show Vendor Daemon Down errors. The LMadmin log shows the error. LicenseEngine (taclic) exited with status 28 Product Line TAC Vista EcoStruxure Building Operation Environment Vista Building Operation Enterprise Server License server Cause Data Execution Prevention (DEP) is activated. Antivirus or other software can scan/use the port used by the vendor daemon. If the time drifts over two minutes and a time synch occurred, the vendor daemon can stop. https://support.citrix.com/article/CTX137111 Resolution First, check that DEP is not activated. Make sure that there is no antivirus program that has portscan activated Make sure there is no other software that uses the same port as the vendor daemon Make sure that the time does not drift too much, if the time drifts two or more minutes and then a resynch occurs the vendor daemon can stop This is more likely on VMware where time synch can occur from either the domain or VMware tool. Check Windows event log (Security) for time synch messages. NOTE: It can also appear just by stopping the server manually.

Issue .xif file not available for download. Product Line Field Devices, Other, TAC Vista Environment MF20-24M 1M54 00 MF20-24L actuator Cause When configuring the MF20-24L in LonWorks, .xif file is necessary.  Resolution All necessary files for LON connectivity are available here: lon_actuator_v3.0 (1).zip

Issue What are the setup requirements for a L-switch on a classic network Environment Loytec L-Switch Cause What is the best way to setup a L-switch in a Vista classic network. Resolution The best option for a L-Switch on a classic network is in the Smart Switch Mode. In this mode the L-Switch decides based on the destination address of the message, which port(s) the message will be forwarded to. This functionality isolates network traffic. The dip switch settings for this setup are shown here.  Here is a link to the Loytec manual for the wiring configurations.

Issue Where can I get information and documents on the Building Analytics service? Environment Building Analytics Cause Information and documentation is required on this product. Resolution Available documentation is available on the Download Center A diagram of network architectures can be seen Here.