Notifications

Join our "Ask Me About" community webinar on May 20th at 9 AM CET and 5 PM CET to explore cybersecurity and monitoring for Data Center and edge IT. Learn about market trends, cutting-edge technologies, and best practices from industry experts.
Register and secure your Critical IT infrastructure

Building Automation Knowledge Base

Schneider Electric Building Automation Knowledge Base is a self-service resource to answer all your questions about EcoStruxure Building suite, Andover Continuum, Satchwell, TAC…

Invite a Co-worker

Send a co-worker an invite to the portal.Just enter their email address and we'll connect them to register. After joining, they will belong to the same company.

Send Invite Cancel

Related Forums

Intelligent Devices Forum

Previous Next

Invite a Colleague

Found this content useful? Share it with a Colleague!

Invite a Colleague

Building Automation Knowledge Base

Issue How can multiple licenses work simultaneously in Vista 5? Product Line TAC Vista Environment Vista 5 Licensing LMTools Cause Licenses may have been purchased separately and either contain different features, or additional seats. The license server can read multiple licenses and serve them up appropriately. Resolution Option 1 - Use multiple .lic files Since the filenames are the same for all .lic files sent via schneider-electric.flexnetoperations.com, you must first rename the files Put them in the License Files folder Make sure the license server is pointing to that folder (not an individual file) Reboot or Stop/Start/Reread license server using the LMTools utility. Option 2 - Merge into one .lic file Complete instructions in Manually Consolidating License Files Open each license file using a text editor. Cut and paste the "Features" into one of the files (Do not copy the file "header") Place this file in the License Files folder Reboot or Stop/Start/Reread license server using the LMTools utility.

Issue It may be desirable to change the default name of an NPR as it appears in I/NET (ie XentaXB2435) to something more descriptive. Product Line TAC INET Environment I/NET I/O Server Config Xenta 527, Xenta 527-NPR, Xenta 731, Xenta 913 Cause I/NET generates a unique default name for each NPR. While the default name differentiates the NPRs it may be helpful to have a descriptive and relevant name for each NPR. Resolution Open the I/NET IO Server Config. Select the IP Port connection of the NPR to be changed and select Modify to open the Configuration Profile. Click on NP Routers to open the NetPlus Routers Summary. Select the router that you want to change and click Modify to open the NetPlus Router Configuration. Enter a new name for the NetPlus Router and click OK. The NPR will now re-initialize and will have the new name. If you are still having issues, see How to change the name of a 527 Link or DLA site.

Issue If a customer's Vista PC crashes, how is the software recovered, and is it necessary purchase all software again? Product Line TAC Vista Environment TAC Vista Cause If a PC with Vista software installed crashes, all software needs to be reinstalled, and if necessary a rehost of licenses is required. The rehost procedure is covered in Rehosting a Vista 5 License on the FlexNet License Server. Resolution The TAC Vista 5.x software itself is free and available for download from The Exchange Download Center. If the software licenses are purchased once, they are still available and no repurchase is necessary. If licenses were locked to a hardware dongle, just reinstall the license file(s) again when installation is completed. If licenses were locked to a Host ID and Host ID is changed due to configuration changes on PC, you need to login to https://schneider-electric.flexnetoperations.com and rehost the licenses to the new Host ID.

Issue Is it possible to limit the number of Vista workstation instances that can be opened on a PC? Product Line TAC Vista Environment TAC Vista 5.1.X Cause On a site with a number of workstation and workstation remote it is possible that all licenses will be checked out by one user on one PC, if multiple instances are running, leaving no licenses available for other users in the network. Resolution It is possible to use a license options file to reserve licenses for specific users. In this way it is possible to guarantee that a license will be available for each user. There is also an option to set the maximum number of licenses a user can use. Click on the following link to open Controlling distribution of license modules in Vista 5which contains a link to the FlexNet Licensing User Guide.

Issue Sigma and BAS - Out of Range value displayed on an AI point when configured as a 0-10V input. Product Line Other, Satchwell Sigma Environment Sigma BAS Cause If a 0-10V analogue input rises to above 10Vdc then the point default value is displayed. Resolution There are several ways to prevent this happening as follows: Follow the example in SHD100 / SHD101 - Humidity Sensors can give a DC voltage signal of greater than 10 Volts using a resistor and lookup table. Or use a Zener diode fitted as per the diagram. Note the maximum input will be the rating of the Zener diode e.g if the Zener diode rating is 9.1V then any voltage from the device higher 9.1V will be pulled back down to 9.1V. Zener diodes are available with fixed voltages, the nearest to 10V is 9.1V. The Zener diode can be fitted at the sensor end (normally slightly easier) or at the controller. The upper limit of the normal operating range of the sensor needs to be below 9.1V. Note: normally a resistor is fitted when using a Zener diode, but because the impedance of the sensor is high, the current will be small, hence the resistor is not used. Or use a diode, this will work to where the maximum input rises to 10.6V. The diode needs to be fitted in series with the device BMS signal. A diode will drop 0.6V across it, therefore in this case a revised lookup table needs to be created. e.g 10V in will be 9.4V out and so forth. Or in the case of feedback from an actuator, the output to the actuator can be restricted to a value e.g 9.5V, this will then restrict the feedback signal. Care must be taken with this method if the actuator is connected to a valve then the performance of the valve and the system it is connected to will be slightly reduced.

Issue Steps to setup a NIC-IP for Vista Product Line TAC Vista Environment NIC-IP Cause Setting UP a NIC-IP Resolution 1. Download and install the latest NIC software. Here is a link to this site 2. Start the LConfig application. This is located in the LOYTEC Network Interfaces menu. 3. Select the NIC-IP/RNI tab. 4. Select the Assignment & Configure button. 5. The next popup screen will search for the NIC-IP. If your NIC-IP is powered up and plugged in to the network it should appear in this list. 6. Select the NIC-IP and then select the Configure button. 7. Setup the IP address, IP Netmask, IP Gateway and DNS servers if required. Select the OK and the device will write the new configuration to the NIC-IP 8. Take note of the Assignment and change if required. Press OK and the Assignment & Configure screen will close. 9 In the LConfig application select the Device from drop down list that matches the notes assignment from step 8. 10. Press the Test Device/Serial Number button to check for the correct setup of the NIC-IP. The return screen should look like this. 11.Close the LConfig application by selecting the OK button. 12. Start the Vista server and log into Vista workstation 13. Under the Vista server object add a new Device-communications Port - Loytec 14. Select the properties of the new Communication port and select the Network interface from the dropdown list. this should be the same interface noted in step 8. 15. You can the add Lonworks networks under the NIC-IP device. If your NIC-IP does not appear in the dropdown list, Configuring Loytec NIC in Vista discusses this related issue.

Issue How to check the amount of used memory in a TAC Menta/TAC Xenta application. Product Line TAC Vista Environment TAC Menta Xenta 281 Xenta 301 Xenta 401 Cause When programming applications for TAC Xenta, you may want to be able to check the size of your application, to verify that it can be downloaded to the device. Resolution To be able to check how much memory an application is using, the application needs to generated. In TAC Menta, edit mode: Select Option, Simulate to enter Simulate mode. In Simulate Mode, select Commands, Generate, to generate the application. To be able to check the Memory usage, you have to return to Edit mode, Select Options, Edit. Now you can check the Memory usage by selecting Options, Memory Usage... As this calculation is done on your PC, and not in the device, and that the memory in the TAC Xenta device is dynamic allocated, it is a recommendation to have at least 10% free memory in each category to avoid future problems. For more information about the Advanced button, please see TAC Menta Advanced Memory Usage: BPR Size Calculator.

Issue XIF and Device Resource files for the Schneider Electric SE7000 Series Room Controllers Product Line EcoStruxure Building Expert, Field Devices, TAC IA Series Environment SE7000 Series Room Controller Cause In order to commission Schneider Electric SE7000 Series Room Controllers into an LNS system, the XIF is required. Resolution LonWorks External Interface Files (XIF) SE72_73_PIR.XIF (80:00:10:55:00:04:04:20) SE76_PIR.XIF (80:00:10:55:00:04:04:21) SE76RH_PIR.XIF (80:00:10:55:00:04:04:22) Device Resource File for XIFs listed above. For Datasheets for the SE7000 Series Controllers, see Where to find datasheets and information on the SE7000/SE8000 series room controllers.

Issue Has the AC256 Xdriver been qualified or modified to work on any second generation controllers (NC2, bCX)? Product Line Andover Continuum Environment bCx9640 CX9680 Xdriver AC256 LA-1 Cause With the obsolescence of the NetC (CX99xx), will the AC256 Xdriver be updated to work with NC2 and/or bCX controllers? Resolution There are no plans to upgrade the AC256 Xdriver for the NC2 and/or bCX. One option, if a site only has AC256 IOU boards, is to use the NC2 and the LA-1 LBus Adapter module or the NC2 with built in LBus support (on comm4 or comm1 with an RS232-to-RS422 converter) to communicate over the LBus with Plain English programming in the NC2. Note: If you configure the controller for Lbus (using the LA-1 or directly to comm1 or comm4) you cannot use Continuum IO modules on that controller. For further information on X Driver compatibility and how to request new drivers/ upgrades, please see Will Continuum communicate with a third party system?

Issue It is not possible to make any configurations or calibrations within a Xenta controller that will reflect on the STR-150. Product Line TAC Vista Environment STR-150 Vista Xenta 121 Xenta 104-A Cause Communication between any Xenta controller and STR-150 is only one-way. The STR-150 can communicate to the controller but the controller cannot communicate back to the STR-150. Resolution Any parameters that can be changed on the STR-150 must be changed at the stat itself. Complete information on the various available parameters can be found in STR-150 Manual Configuration. It is not possible to perform a calibration on the STR-150 stat in a way that will affect the readout of the STR-150 in a version prior to 1.4. The Xenta 104-A can have the space temperature calibrated within the application by changing nciTempOffset. However, when a version prior to 1.4 of the STR-150 is used with the Xenta 121 the space temperature cannot be calibrated. For more information see STR-150 Calibration Feature.

Issue What are the limitations of using ID Works with I/NET Seven? Can a "begin time" or an "end time" be assigned to a temporary card from ID Works (Card Access Control Data Entry)? Can an individual’s record be made a "DPU Resident" from ID Works? (I/NET Seven 1.0x) What is the format of the CardID entry in the ID Works system? Can assign PIN numbers be used with an ID Works system? Product Line TAC INET Environment I/NET Seven ID Works - For details of what version of Datacard ID Works Software integrates correctly with I/NET Seven refer to Datacard ID Works Software versions for integrating with I/NET Seven. Cause I/NET Seven provides support for Datacard ID Works identification software. I/NET Seven provides a database view specifically designed for use with ID Works. This view contains tenant and individual data used by the ID Works Video Badging application. It allows you to add individuals, assign key/cards, edit individual parameters, or even delete individuals. The limitations described below are imposed anytime that you use ID Works to modify your I/NET Seven access control system. Resolution The limitations described below are imposed anytime that you use ID Works to modify your I/NET Seven access control system. ID Works does not allow you to add or modify multiple cards for a single individual. ID Works does not allow you to remove a card from an individual without deleting the individual record in I/NET Seven. You cannot disable an individual’s card without disabling the individual in the I/NET Seven. You cannot create a new group or a new tenant from within ID Works. You cannot assign a begin time or an end time to a temporary card from ID Works – only dates can be entered. I/NET Seven will use a default time of 00:00 (Midnight) on the dates specified. If you need to change this default time, it requires you to go into I/NET Seven > Access > Individuals editor. You cannot make an individual’s record be DPU resident from ID Works. You cannot assign a decimal card number to an individual from within ID Works. The format for this entry has to be a hexadecimal number. You cannot set and individual’s APB scheme (i.e., hard, soft, or graced antipassback) from within ID Works. You cannot assign a PIN to an individual from within ID Works. These can be access via the I/NET individual editor. For further information refer to TCON301 Chapter 5.

Issue From time to time TAC Vista Server stops communicating with LonWorks devices and needs to be restarted. Product Line TAC Vista Environment TAC Vista Server LonWorks Cause There can be various reasons for this. One of the reasons can be, that one or more devices is flooding TAC Vista Server with communication, and the communication finally stops. Among other things, this can be due to one or more TAC Xenta's suffering from the rare memory fault issue described in TAC Xenta 401 - Rare Memory Fault Issue - TPA-MALI-09-0011.01, or that the system program in the TAC Xenta device has become corrupt. To identify the issue, make a communications log as described in Start TAC Vista Communications Log, and open the log with the "TAC Vista Comm. Log Decoder". Filter on "C1" messages, and check if there's extensive communication from one or more devices. If that's the case, you have identified that file transfer loop is the issue. Resolution The first thing to try, is to update the system program in the Xenta. Follow article Download an .MOT file into a Xenta Programmable controller for instructions on how to do that. If that doesn't work, replace the Xenta device(s) causing the massive file transfer.

Issue Renaming a Vista Server. Product Line TAC Vista Environment Vista Server Cause The Vista Server name will default to the PC name where the database is created. To rename the server to any desired name of fewer than 40 characters. This can be customer-appropriate or more generic than an individual's PC name; follow the steps below. Resolution Shut down Vista Server Open Vista Server setup and navigate to the Vista Database tab. Enter the desired server name in the text field "Rename Vista Server to" Click OK Restart Vista Server. Within a few seconds, the server's name shown at the top of the window will be updated to reflect the new name. It will also show up in the folder view of the Vista Workstation. Note: Changing the Vista Server name after graphics have been created and bound will break the binding path for all points. To fix up the binding paths for all graphics at once, use Change References, as shown in Change all bind paths for all bindings on a TGML or OGC graphic at once.

Issue How can I determine what version of SQL I/NET is using? What version of SQL is installed on the I/NET PC? Product Line TAC INET Environment I/NET Seven 2.10 and above For previous versions of I/NET refer to How to determine the SQL version you are running with I/Net Seven. Cause To find out what version of SQL is installed and used by I/NET Seven site PC. Resolution A new feature was introduced in I/NET Seven Revision 2.10 that allows you to view both the I/NET revision and SQL revision installed. To view this all I/NET applications and the IO Server must be shutdown before performing the following steps: Start DBCreate >Start> All Programs> INet>DBCreate Login screen is shown, select either Windows login or enter the SQL Server Authentication details and click OK Right-click on the Title area shown in red below: After Right-clicking, select from the menu options About... The About DBCreate screen will then be shown and you can see both the I/NET Seven Version and SQL Versions as shown and highlight below: For I/NET Revisions prior to 2.10 then refer to How to determine the SQL version you are running with I/Net Seven on how to view what version of SQL is installed.

Issue DBCreate database restore fails with error message: "The backed-up database has on-disk structure version 611. The server supports version 539 and cannot restore or upgrade this database. [Microsoft][ODBC SQL Server Driver][SQL Server]RESTORE DATABASE is terminating abnormally." Product Line TAC INET Environment I/NET Seven SQL Server 2000 all editions and SQL 2005 all editions Cause It is not possible to restore a SQL Database which was backed up using SQL 2005 back into a SQL 2000 database. Resolution The simplest method to rectify this problem would be to uninstall I/NET and SQL (Refer to Procedure for uninstalling I/NET Seven on a stand-alone host on how to do this) and then re-install I/NET using SQL 2005. The second method would be to upgrade the installed MSDE Default instance to SQL 2005 Express. There is a published white paper from Microsoft on this and is attached here: MSDEtoSQLExpress.doc. Refer to the steps on page 11 to 14. The SQLExpress installation file is available on the I/NET CD under the folder SQLExpress\.SQLEXPR32.EXE. After performing these steps its advisable to run up DBCreate and upgrade the SQL database.

Issue Which licenses are required when TAC Vista is used in a virtual environment? Environment TAC Vista Cause Running a TAC Vista system in a virtual environment. Resolution No special end user licenses are necessary. License requirements are the same as if run in regular environment. Also, please see: Problems installing Vista on virtual PC and Running Vista software on an emulated environment for more details on the subject of running TAC Vista in a virtual environment.

Issue In order to make page links between different I/NET graphic folders work fine, the same folder structure needs to be created manually in EcoStruxure / SmartStruxure. Refer to Converting I/NET graphics to TGML using the "Create Source Tree" option to realize this. Product Line EcoStruxure Building Operation, TAC INET Environment EcoStruxure / SmartStruxure 1.4 or higher I/NET Cause The I/NET graphic folder structure will not be created automatically before SmartStruxure 1.4.0. Resolution Starting in version 1.4.0, there was a new feature called Data import for I/NET graphic. Using this feature, all the converted I/NET graphic folders structure can be imported at one time without any need for manual work. Here are the steps to make it work: Convert the I/NET graphics according to Converting I/NET graphics to TGML using the "Create Source Tree" option, but do not create the folder structure manually in EcoStruxure / SmartStruxure. Create the default Inet Graphics folder by right clicking on I/NET Interface-->New. Right click on Data Import and choose the root folder of all of the I/NET graphics. Click OK. Data importer will check all the file names and bindings. If any error happens, check and fix it before importing again. (Currently apostrophe is not supported in SmartStruxure. Change the name and relative link and do it again. It may be fixed in later version) Check whether all the bindings and links work fine. Important: Currently this feature doesn't support export/import in SmartStruxure. It will fail to import if any sub folders are contained under INET interface. This may be fixed in later version. The workaround is to still create the whole structure according to Converting I/NET graphics to TGML using the "Create Source Tree" option.

Issue Have Cyberstations and BCXs and/or 3rd party devices on different subnets Product Line Andover Continuum Environment Cyberstations BCX 40xx 3rd Party MSTP/IP BACnet Cause Unable to communicate with B3 devices or get B3 point values. Resolution Review LAN configuration. Each separate subnet requires a single BBMD for communication. See BACnet documentation on line via Cyberstation or "Introducing BACnet" document in Cyberstation. See Simple BBMD setup.

Issue Regional settings might differ when TAC Vista server runs as a service. Product Line TAC Vista Environment TAC Vista Server set to run as a service Cause If TAC Vista Server is configured to run as Windows service it might have different regional settings. This is because the TAC Vista server service needs to be configured to use a specific user account (See Registering/Unregistering TAC Vista Server as a Windows service). One common symptom would be that the date and Time stamp might have another format. Resolution To make sure that TAC Vista server is using the correct regional settings: Log on to the system once using the credential that TAC Vista server is configured to use Check the regional settings for this account.

Issue The TAC Xenta operator panel will not display controllers on the network even though it has the correct StruxureWare Domain ID entered and is set to manual mode. Product Line EcoStruxure Building Operation Environment TAC Xenta Operator Panel StruxureWare Cause StruxureWare Building Operation sets its LonWorks Domain ID to a decimal value. The TAC Xenta Operator Panel needs the hexadecimal value in order to operate properly. The decimal value must be converted to hexadecimal. Resolution In order to locate the domain ID of a LonWorks Network, see How to locate and change the LonWorks domain ID. Converting a decimal value to hexadecimal using a calculator Open the calculator on your computer. If Windows go to Start > All Programs > Accessories > Calculator. In the View menu, select Programmer. Enter in the decimal value of the domain ID. Select the Hex button on the left side of the calculator. The domain ID has been converted to hexadecimal. In the example, the domain ID 0B should be entered into the operator panel and set to manual mode.

To The Top!

Building Automation Knowledge Base

Related Forums

Intelligent Devices Forum

Use multiple license files simultaneously for Vista 5

How to change the name of a NetPlus Router (NPR) in I/NET

How restore software after a Vista PC crashes

Limit the number of Vista workstation instances that can be opened on a PC

Out of Range value displayed on Sigma AI point

Configuring a NIC-IP to be used in Vista

Memory Usage in TAC Menta/TAC Xenta

XIF and Device Resource files for the Schneider Electric SE7000 Series Room Controllers

Does the AC256 Xdriver work on the NC2?

STR-150 does not support full duplex communication with base unit

ID Works Limitations when configured with I/NET Seven

TAC Vista Server stops communicating with LonWorks devices

Rename a Vista Server

DbCreate now displays the revision level and description of SQL in the Help About box

I/NET DBCreate database restore fail

TAC Vista end user licenses in virtual environment.

Import all converted I/NET graphic folders into EcoStruxure at one time

Cannot see B3 Controllers

Regional settings might differ when TAC Vista server runs as a service

Xenta Operator Panel will not recognize Xenta controllers in a SmartStruxure network

Building Automation Knowledge Base

Related Forums

This is a heading