Building Automation Knowledge Base

Issue Licenses are becoming damaged repeatedly over time and/or licenses are going in to a disabled state. Product Line EcoStruxure Building Operation, TAC Vista Environment SmartStruxure License Administrator Virtual Machine Cause Damaged Licenses: If the license server / license administrator is installed on a virtual machine, the common reason for damaged licenses is that the MAC address of the virtual machine is not set to be static. Every time the MAC address changes, the license will become damaged. Disabled Licenses: This is usually caused when the license fails to complete a process such as a return or repair. This could be due to an intermittent internet connection or the process timed out while trying to communicate with the license server. Resolution Repair License with License Administrator The first step to take with a damaged or disabled license is to use the repair function in license administrator. Follow the steps from WebHelp topic Repairing an EcoStruxure Building Operation Software License. If the repair function does not work, then the license server will need to be reset.  Reset License Server (Unable to Repair License) Below are the steps to remove the damage or disabled licenses before reactivating the permanent licenses again: Put a SBO demo license on the site to get it back up and running right away. Locate the Entitlement ID and/or activation ID of the impacted licenses. Open a case with your local BMS support group and provide them this information. This information will be used to release the licenses to prepare them to be rehosted. There are then two potential methods to  reset the license server: Download and run the SBO License Server Reset tool from the Community Manually reset the License Server Stop the License Server. In the License Server application folder, remove all files:                 - File path for Windows 7, Windows 8.1, and WIndow 10: \ProgramData\FLEXnet                 - File path for Windows Server 2008 and Windows Server 2012: \ProgramData\FLEXnet   Start the License Server Reactivate the returned network licenses.   Note: When you reactivate all returned network license, new License Server .data files are created together with the activation of the first license. For more detail, reference WebHelp: Resetting the License Server.

Issue Which SpaceLogic Sensors could be used with the TAC Xenta 100 series controllers? Product Line TAC Vista Environment ZBuilder Xenta 122 Cause The STR100-series sensors will be withdrawn, and SpaceLogic Sensors have been identified as suitable replacements. Resolution Only TAC Xenta 122 controllers can be configured to use 10K Type 3 Thermistor.   To integrate SpaceLogic Sensors with the TAC Xenta 122 controllers, follow these steps in ZBuilder: Access the Configuration tab. Navigate to the Room unit settings. Locate the checkbox labeled "Use STR-5xx series" and select it.   Please note that only the SLASXXX, SLABXXX, and SLAWXXX models are compatible with the TAC Xenta 122 controllers. These sensors, however, do not feature buttons for setpoint adjustment or fan control.  

Issue What is the minimum pulse duration for the digital inputs (X1 - X3) on the TAC Xenta 121-FC? Product Line TAC Vista Environment Vista Server Xenta 121 Cause The device requires a certain pulse duration to be able to register the feedback signal from another device, such as a fan running signal. Resolution The minimum pulse input duration is 250ms. Click here to open the datasheet for Xenta 121-FC

Issue TAC Vista Error Codes in Plain Text Product Line TAC Vista Environment Vista Server Vista Workstation Cause Vista will sometimes give an error code. This list decodes the TAC Vista Family Error Codes. Resolution For a list of TAC Vista Error Codes in plain text click here.

Issue nvoSpaceTemp from TAC Xenta 100 series used with the room unit STR150 does not read temperatures greater than 33.4 °C (92.3 °F). Product Line TAC Vista Environment ZBuilder Xenta 121 Xenta 122 STR Sensor Cause The STR150 and the Xenta 100 line of controllers are capable of displaying temperatures greater than 33.4 °C (92.3 °F) or less than 8 °C (46.4 °F). However, the communication protocol between the STR150 and the Xenta 100 series is limited and thus restricts the temperature that the TAC Xenta 100 can read from the STR150 device. Resolution The STR150 data sheet states that temperature range transferred to a TAC Xenta 100 device is limited to 8 °C through 33.4 °C (46.4 °F to 92.3 °F). If temperatures outside of that range are needed an STR100 (simple 1.8k thermistor) or an STR-350 (communicating Lon stat with display) could be substituted. The ranges of those devices connected to a TAC Xenta 100 device are as follows: STR100: –10 °C to +50 °C (14 °F to 122 °F) STR350: 5 °C to 45 °C (41 °F to 113 °F)

Issue Using Xenta Controllers with a Tridium Jace Product Line TAC Vista, TAC IA Series Environment Xenta programmable controllers Xenta 280, 281, 282, 283, 300, 301, 302, 401, 401:B Tridium AX / N4 Jace Cause By default, the Tridium Jace acts as a network manager which will disrupt controller addresses, SNVT bindings, and Group bindings previously set up in LonMaker. Resolution  To disable this feature provide these steps to a Tridium Integrator: Use Niagara WorkBench Connect to Jace Under the Services Folder, find "LonNetwork" Go to  "Local Lon Device" Set the "External Config" property to "true" Hit "Save"  

Issue Unable to create a file with a certain name such as "x". Get a message that the object already exists. The object does however not exist in the Vista database when viewed in Workstation. It seems that there are invisible objects in Vista. Product Line TAC Vista Environment TAC Vista Workstation/Server 5.1.X Cause This has been seen in older databases that have been created or edited using older editing tools such as TAMain. These system objects should disappear automatically but if they don't they will cause the error described under "Issue". Resolution This can be removed by starting the TAC Vista Database generator tool from workstation (Tools\TAC Vista Database Generator). Once started, do the following: Select Database\Export from Database. Click on the browse button in the Object field. In the field "Current object ID" type "x" (or the name of your invisible object" and the buttons on the right of the tool should be activated. Click on delete, and the object will be deleted. After this, you can check in workstation that the object has been removed by creating a new folder named "x".  

Issue Locate the Evaluation license for TAC Vista or EcoStruxure Building Operation Product Line EcoStruxure Building Operation, TAC Vista Environment TAC Vista EcoStruxure Building Operation Cause There is an evaluation license available for TAC Vista valid one month and an Evalauation license for EcoStruxure Building Operation valid 3 months.  Resolution Evaluation or demo license files are available for licensed partners on the EcoXpert Extranet. Follow the link and search for "evaluation". You must first register using your business email (i.e. CustomerName@partnerdomain.com) address to gain access to these files. Note: You may use any email address to register and view content, but downloads will only be granted to approved partner domain names.

Issue The reconfiguration of the log database (run from TAC Vista Server Setup) times out. Configuring the settings, for the first time after upgrading Vista, on the SQL server tab of TAC Vista Server Setup an then clicking on apply makes the following message appear: "Log database found but needs to be reconfigured. Reconfigure Log database?". After clicking yes the reconfiguring process starts, but times out. The message states the following:  Lock request time out period exceeded. (Microsoft SQL Server, Error: 1222) Environment TAC Vista 5.1.X SQL server  Cause The SQL server is busy. When a reconfigure of the database layout (or schema) is done, all connections to the database must be stopped to prevent corruption of data. If a number of applications/clients are trying to write data to the database, the request to lock the database will time out. Resolution Close the open connections to the database and try again. Generally speaking this shouldn't occur with just Vista running. It is when 3rd party clients access the SQL data directly that this problem can occur. To help identify the problem, the Activity monitor in SQL server management studio can be used.

Issue Temperature Sensor Resistance Charts Product Line Andover Continuum, EcoStruxure Building Operation, Field Devices, Satchwell MicroNet, Satchwell Sigma, TAC IA Series, TAC INET, TAC Vista Environment Temperature Sensors Cause Temperature (°C) to Resistance Charts (ohms). Upgrading the site BMS, but retaining the existing sensors and the sensor resistance values are not known. Resolution The resistance of a sensor at a specific temperature can be downloaded below, there are a number of tables collated from different sources for a number of Schneider Electric sensors and other BMS suppliers.   In EBO, the thermistor selection in the IO module or controller does not represent the thermistor bead type, an example is the Continuum Type I in EBO, but the bead is a Type 3,. For further information regarding this see the KB article  Thermistor type selection in EBO.   The document All Sensors covers the following:   Satchwell DxT sensors are replaced by STR600, STP660, STD600, STO600 type T with shunt, and use the Satchwell T range chart Drayton DC1000, DC1100 30K6A1 is now known as STR600D, STP600D, STO600D Andover 10K4A1 TAC Inc. Vista 1.8KA1 I/A series 10K3A1 with 11K shunt INET 10K2A1 (10k Dale) BALCO 1000 ohm RTD   Older Satchwell ranges: Satchwell DW1204, DW1305, DWS1202 Satchwell DO Satchwell DD/DR Other manufacturers included: Allerton 3K3A1 Ambiflex 2012, Honeywell Aquatrol, Jel/Thorn, Trend, York 10K3A1 Schlumberger (air) 5K3A1 Schlumberger (immersion) 100K6A1 Automatrix, York, Sibe 10K4A1 Honeywell 20K6A Landis & Gyr PT100A, PT1000A   Further information regarding INET, IA, the document Thermistor Types Tables (Veris Industries) is available.  The 1k Balco resistance chart is also available.   Further information for the Continuum ACC Temp 10K Type 3 also known as 10K4A1, the document Thermistor Temp Resist Chart (Precon Thermistors) is available.   TC900 series TC900 RS-03 sensor chart   For I/A Series Controllers (MNL/MNB) Compatible sensors that have a built-in 11k shunt resistor include the TS-5711-850 TS-57011-850 TS-57031-850 TSMN-90110-850 Series Any sensor that matches resistance to temperature curve for a 10K Thermistor Type G (U.S. Sensor), Type 9 (Dale/Vishay) or Type III (ACI Series AH) can be used with the I/A Series MNL and I/A Series MNB series controllers, provided that a 11k ± 0.1% 1/8 watt resistor is wired in parallel with the sensor. The input has a range of -10 to 135 °F (-23.3 to 57.2 °C) with an accuracy of ±1% of span. Temperature / Resistance Reference Values Temperature Deg F (Deg C) Resistance Resistance Incl. 11k Shunt 32 (0) 25490 8,012 68 (20) 12,260 5,798 75 (25) 10,000 5,238 104 (40) 5,592 3,707 140 (60) 2,760 2,206 The full temperature/resistance table for the US Sensor 10K Thermistor R-T Curve Type G sensor. Please note that the controller may not be able to use the full temperature range shown in the table.  

Issue Rehosting is defined as the process of moving a license from one machine to another. Is there a limit to the number of rehosts allowed per year? Product Line EcoStruxure Building Operation,TAC Vista Environment Building Operation Licensing Cause Re-hosting means that the license bindings to the physical hardware or its substitutes on a Virtual Machine are moved i.e. the host ID is changed. This can be required if the license is moved to a new computer or Virtual Machine.  A maximum of 4 license re-hosts are allowed in 12 months. Resolution If the re-hosting limit is exceeded and further re-hosting is justified and necessary, the policy can be overridden by Product Support. When contacting support please provide the entitlement details so that the license policy can be overridden.

Issue How much ethernet bandwidth do lonworks systems consume using Loytec L-IPs, iLons, etc.? Environment TCP/IP ethernet network LNS System Cause IT professionals will sometimes hesitate to allow the control system to use the same TCP/IP network as the internet, phones, etc. They may ask what the expected bandwidth usage will be before granting access. Resolution It is impossible to explicitly state how much bandwidth a LonWorks system will consume on the ethernet. It depends heavily on the amount of LON traffic being sent by the controllers. The routers themselves do not produce traffic, they only pass the traffic onto and off of the ethernet. The traffic is created by the LON devices, Xenta controllers, Vista and LonMaker or other HMIs. Vista can create a maximum of 15 LON telegrams/second. This is very little traffic with respect to IP bandwidth. Unless you have made bindings into the LNS NI (which we never do in a Vista-scenario, since Vista cannot read these) there is basically nothing at all going out from LonMaker/LNS unless you are commissioning devices. Starting the LonMaker Browser also generates traffic. But this is also normally just in the design phase of the network, not in "operating mode". SNVT bindings or TAC network variables from one LON network to another over the IP channel also generate traffic. A typical Xenta can produce 2 SNVTs propagation/second and/or maybe 10 TACNV. This is not much (as IP-traffic), but if there are hundreds of nodes communicating simultaneously all passing through L-IP gateways, the amount of IP traffic will grow. If you are using a Loytec L-IP, it uses a protocol feature called "packet bunching". Before it sends out a packet on the IP side, it waits for an adjustable time (Aggregation Time, default = 16ms) if some packets are following, which have to be sent to the same IP addresses. If some packets are following, it puts the packets in the same IP frame and sends it all together in a single IP packet. The receiving node unpacks it and makes multiple EIA-709 (Lonworks) packets again.

Issue Firewall issues when trying to reach out to the activation server for a license Product Line EcoStruxure Building Operation, Satchwell Sigma, TAC Vista Environment Building Operation Licensing Firewall Cause If the corporate network has a very restricted firewall policy or rules, the port needed to reach and activate a license may be blocked. Note: The same license server is used for EcoStruxure Building Operation, Satchwell Sigma and TAC Vista software licenses. Resolution Open Port 443 (HTTPS) for the server hosting the license server, and ensure that the routing paths to the Flexnet Licensing server URL's are all fully open. The Licensing Server URL should be opened from the site, and it is: https://schneider-electric.flexnetoperations.com If the site of the old server has issues with the non secure communications or the communications forwarding between the previous and the new server, there is a tool available to configure EBO to only use the new server. See the Exchange Community article for the download: SBO License Setup Note: From EBO V2.0 only the new license server is used, port 80 is no longer required and HTTP is redirected to HTTPS.

Issue Is it possible to set/change the time for a time schedule in TAC Vista from a OPC client? Product Information TAC Vista Environment Vista Server Vista OPC Server Cause  In the OPC standard supported by TAC Vista time schedules are not included Resolution No it is not possible to set/change the time for a time schedule in TAC Vista from a OPC client?

Issue Extended LonTalk is supported In Vista 5.1.5 but it doesn't work, it is possible to read but not write to the device. Error message when writing: "Local network management failure" Product Line TAC Vista Environment Vista Server Cause When adding a Extended LonTalk device in to TAC Vista, TAC Vista will see in the xif file that this is a Extended LonTalk device and set a Extended LonTalk device flag for that device. It is possible to see the flag if hold down shift+Ctrl and click in properties for the lon device, it is called "EXTENDEDLONTALK".  If the xif file is imported to a TAC Vista with a version earlier than Vista 5.1.5 the Extended LonTalk will not work. Resolution Make sure the "EXTENDEDLONTALK" flag for the lon device is set, if not import the xif file again in Vista 5.1.5.  

Issue Nothing happens when starting the OGC editor Product Line TAC Vista Environment Vista Server Vista Workstation Cause The issue is with data execution prevention (DEP) not allowing the tacdraw application to run.  Resolution If DEP is not required on your system follow these steps: Go to Control Panel > System > Advanced > Performance Settings > Data Execution Prevention Choose "Turn on DEP for essential Windows programs and services only" Reboot the computer and the editor should launch like normal.  If DEP is required on your system follow these steps: Go to Control Panel > System > Advanced > Performance Settings > Data Execution Prevention Choose "Turn on DEP for all programs and services except those I select" Then click the add button and navigate to: For Vista 5.1.4 and up: C:\Program Files\Schneider Electric\TAC Vista 5.1.4 and choose the tacdraw.exe file. For Vista 5.1.3 and prior: C:\Program Files\TAC\TAC Vista 5.1.X and choose the tacdraw.exe file. Reboot the computer and the editor should launch like normal.  

Issue Error "Not enough space in RTI device"   Product Line TAC Vista Environment Aladdin Privilege Administrator 2.01 Vista IV Licensing Cause Memory in PSU is corrupt. Resolution Run Dongleutil, a dongle reset utility software. This utility resets the memory in the PSU that is connected to the PC. You need to install the license file again after this operation. This problem is usually seen when Inhouse PSU is used. In TAC Vista version 4.10 and later, it’s no longer necessary to install the engineering file when Inhouse PSU is in use. Just connect the PSU to the PC, and everything should work fine.

Issue TGML numeric presentations rounded to integers with no decimals displayed. Product Line TAC Vista Environment Vista Workstation Vista Server   Cause Depending on the component being used to display the numeric data, it may be as simple as a property not set to display decimals. It may also be due to presentation values. Resolution If using the default Numeric Presentation from the provided Snippets library, change the property in TAC Graphics Editor for 'Decimals' to the number of decimals to be presented i.e. 4 decimals = .0001, 2 decimals = .01, etc. If not using this Snippet, check to see if getPresentationValue() is being used in a script, or if the binding itself has the Format attribute set to Presentation instead of None. Presentation value will inherit all formatting from the Vista database and not from the TGML source file.

Issue There was a problem with the SQL server and the logs and events were queued in the $Queues folder.  The SQL problem is resolved but the $Queues folder has grown so much that it can't be opened to check. Is there a way of checking if Vista has restarted logging to SQL? Product Line TAC Vista Environment TAC Vista Server Microsoft SQL Server Cause When a problem occurs with the SQL server, the log values and events are saved in the $Queues folder in the TAC Vista database, so that no information is lost. As long as there is no connection to SQL, the logs and events will be queued in $Queues. Once a connection to SQL is re-established, Vista will start logging all the values in the $Queues folder, gradually emptying the folders, although this may take some time if the SQL server has been down for a while. Resolution Query the SQL database and check for logs with today's date. Download & install Microsoft SQL management studio (2005 or 2008 depending on which version of SQL is being used) Query the trend log table for logs using the following query: Start SQL management studio and log in to the TACVISTA sql instance. Click on New Query and type in the following query: use taclogdata go select * from TrendLogValue where LogTime > '2011-11-03 00:00:00.000' Note: if you have a custom configured SQL database change taclogdata to your database name. -Change the date to today's date and execute the query. If the query doesn't return any matches, change the date to an earlier date and repeat.   -Keep going until the date when contact with SQL was lost. If no matches are returned, check that the service TAC DSS writer is running. If it is then it maybe that the Vista is till trying to clear the backlog. Try again later.

Issue How many Modbus TCP Clients can be connected to Vista via an Xenta 913? Product Information TAC Vista Environment Vista 5.1.X Xenta 913 5.1.X or later Xenta 511 5.1.5 or later Xenta 701 5.1.5 or later Xenta 711 5.1.5 or later Xenta 721 5.1.5 or later Xenta 731 5.1.5 or later Cause When planning a system it's important to know how many devices are required. Resolution A maximum of 40 Modbus TCP clients are supported when communicating via a Xenta 913, Xenta 511 or Xenta 700. Each TCP Client may have up to 100 Modbus devices (see page 4 in the datasheet).