Building Automation Knowledge Base

Issue IIS is a Microsoft product that is included on your typical Microsoft OS software but is not active by default. Product Line TAC Vista Environment Webstation Windows 7 Windows Vista Cause Webstation requires for IIS to be active in your OS before you complete the installation of Webstation. Resolution Follow these steps to initiate your IIS service in Windows 7 or Windows Vista. How to Activate IIS 7: To open the Windows Features dialog box, click Start, and then click Control Panel. In the Control Panel, click Programs. Click Turn Windows features on or off. You may receive the Windows Security warning. Click Allow to continue. The Windows Features dialog box is displayed. Expand Internet Information Services. Additional categories of IIS features are displayed. Select Internet Information Services to choose the default features for installation. Expand the additional categories displayed, and select any additional features you want to install, such as Web Management Tools. Click OK to start installation. The progress indicator appears. When the installation completes, the Windows Features dialog box closes, and the Control Panel is displayed. IIS 7 is now installed with a default configuration on Windows Vista or Windows 7. To confirm that the installation succeeded, type the following URL into your browser, http://localhost Use Internet Information Services Manager to manage and configure IIS. To open IIS Manager, click Start, type inetmgr in the Search Programs and Files box, and then press ENTER. See Problems installing Vista Webstation 5.1.5 or newer for more information on configuring Webstation.

Issue Get error message "OPC communication error" when trying to view Vista OPC server objects in OPC tool. Product Line TAC Vista Environment TAC Vista 5.1.X TAC Vista OPC server 1.6.1 Cause Incorrect version installed or DCOM settings. Resolution Confirm which version of Vista OPC server is installed. Go to control panel\add remove programs and double check that it is version 1.6.1. that is installed. Confirm that OPC server setup account settings aren't being saved. Go to Start\Programs\Schneider Electric\TAC Vista OPC server\Tac OPC Server setup. Under Login to TAC Vista server, change to Login using the following TAC Vista account and fill in the appropriate user details. Click OK and close the dialogue. Re-open the TAC OPC server setup dialogue and see if the account details added in b are still there. If so then there is probably a problem with DCOM settings (see TAC Vista OPC Server Technical Manual). If the option Login using the windows account which is running the TAC Vista OPC server is re-selected TAC Vista OPC server 1.6.0 must first be installed according to OPC server for TAC Vista will not keep the login settings in the TAC Vista OPC Server setup.

Issue "No license for LonWorks communication" Error when starting Workstation. Product Line TAC Vista Environment Windows 2008 Server X64 TAC Vista 5.1.5 Cause Windows Server is member of a domain. Configure the TAC Vista Server to run as a service, with a local user set as administrator to logon. Results in "No license for LonWorks communication" when starting Workstation. If starting the service with a domain user or local system, it works.  Resolution Windows Security Policy This may have something to do with UAC (User Account Control) in Windows. The user that launches TAC Vista was already as a local administrator, but it seems that a log out with the user, log in with a local user, and log back in with a domain user is necessary for some policies to be set. Licensing Registry The Vista licensing requires registry information on where to find a license file. This registry key is found in the following location: HKEY_CURRENT_USER\Software\FLEXlm License Manager\TACLIC_LICENSE_FILE If the user has not been logged in and configured to run Vista software, this key might be missing or misconfigured. Ensure that it has a proper value by launching Vista Workstation or running the TAC License Setup. Log in with the user that will run the TACOS service and run the License Server Setup application to ensure the correct file path is defined in the Registry.   Related Articles: "No license for LonWorks communication" with TAC Vista Server LE "No license for LonWorks communication" error when using a non LE dongle "No license for LonWorks communication" - LonMaker Recovery Folder "No license for LonWorks communication" error message in Classic Network "No license for LonWorks communication" in Vista Workstation TACOS startup delay utility

Issue Is there any way to get the Xenta Server trend log data without TAC Vista? How to get the Xenta Server trend log values from the web interface How to e-mail the Xenta Server trend log values Product Line Satchwell MicroNet, TAC Vista Environment TAC Xenta Server TAC Xenta 511, 527, 555 TAC Xenta 711, 731 Cause The TAC Xenta Server is installed standalone and TAC Vista can not be used to view or save the trend logs. However if you want to collect and store data from multiple trend logs on a regular basis we do strongly recommend using TAC Vista. Resolution There are two ways to get the trend log data from a Xenta Server (except for TAC Vista): 1. Manually copy the trend log values from the Xenta Server web interface In XBuilder, create a trend log page and drag the trend log to it Log in to the web interface and go to the trend log page Right click the trend log signal name and choose "view values" Copy/paste the values to for example Excel.   2. Forwarding the trend log data as an e-mail First make sure that the SMTP settings in XBuilder are correct. For troubleshooting on this, see Troubleshooting sending emails from a Xenta Server Create a receiver group and define one or more e-mail addresses to receive the trend log data. Highlight the trend log.  Under Log Data Transfer Settings, click the Receiver Group box, and select the Receiver Group list. In the Subject box, type a suitable subject. If desired, also type a suitable text in the Body box. In the Log Events Included box, click Yes to attach log events to the e-mail message. You must also specify when the log data is forwarded. For this, create a time object which you drag to the "send data" signal on the trend log. When the trend log data is forwarded, the receiver group e-mail addresses will receive the trendlog data as an attached .log file. For more information, see chapter 8.2.2. in the TAC Xenta Server – Web Server, Technical Manual

Issue When trying to view values in a Classic Network, "[No license for LonWorks communication]" message shows up in the Value tab and the alarm window. Product Line TAC Vista Environment Vista Classic Network Cause Though you are using Classic network, it's still using LON standards. You still need the license for TAC Vista Server. If the Server license is missing or invalid, you will get this kind of message. Resolution Check your license file and make sure you have the server license included. The server license should look something like listed below:  INCREMENT Vista.Server taclic 5.1 permanent 1 ISSUER=TAC \ If you do not have the line above, it means you do not have the proper license for TAC Vista server. Thus, you get the error message saying "No license for LonWorks communication."  The solution is to purchase the TAC Vista Server license, or use the demo license or an engineering dongle. Related Articles: "No license for LonWorks communication" with TAC Vista Server LE "No license for LonWorks communication" error when using a non LE dongle "No license for LonWorks communication" - LonMaker Recovery Folder "No license for LonWorks communication" Error in Windows 2008 Server X64 "No license for LonWorks communication" in Vista Workstation TACOS startup delay utility

Issue Save time in the field by using the different functions Newron NL220 has to offer. This article contains some tips, tricks, suggestions and ideas. Product Line TAC IA Series, TAC Vista Environment NL220 Cause By not using all of the different tools within NL220 it can take much longer to complete a checkout of a database or resolve a problem. There are a number of shortcuts and hotkeys that can save a substantial amount of time. Some examples include database searches, browser window functions, filters, attaching documents, and meanings behind network menu options. Any addition questions or information can be found by contacting Newron here. Resolution Other Helpful NL220 Articles and PDFs NL220 Manual - Click here Starting a NL220 database - Click here Echelon LonMaker and Newron NL220 on 64-bit operating systems Ordering more LNS credits Ordering more Newron NL220 credits The difference between NL220I and NL220M dongles How to Rehost an NL220 Dongle to another PC LOYTEC NIC-USB in NL220 Creating LNS database in NL220 and transferring it into TAC Vista procedures outline Adding a Xenta Programmable Controller to an NL220 System Downloading new NXE or APB files using NL220   Searching the Database There are multiple ways to perform a search in the NL220 database depending on what is trying to be found. At the top of the NL220 window there is a search bar as seen above. The buttons found on this toolbar are defined below. When performing a search there are four different ways that a name can be searched. Using an asterisk after the name means that NL220 will search for anything that begins with those characters. Example: Name*   Using an asterisk before the name means that NL220 will search for anything that ends with those characters. Example: *Name   Using an asterisk before and after the name means that NL220 will search anything with those characters somewhere in the name. Example: *Name*   If no asterisks are used then NL220 will search for an exact match of those characters. Example: Name   General Toolbar The general toolbar at the top of the NL220 window has many useful shortcuts and features. Descriptions of some of these tools can be found below.    To use the automatic browser feature , the desired network variables must first be selected in the device templates. Select the template tab at the bottom of the database tree window.   Double click on the template that is desired for automatic browse. This example is using the 102-AX template.   Select the NVs tab in the device template settings window. Check the box in the browse column next to all network variables to include in automatic browse.   Click on the Subsystem tab  at the bottom of the database tree window.   Select the automatic browse button and click on a controller that is using the template that was modified. It will automatically open up the browse window with only those network variables.   Filter Toolbar The filter toolbar seen above is found at the top of the tree window. This toolbar contains the ability to look at nodes in a specific state like commissioned or uncommissioned, only display specific types of network variables, or even filter nodes and variables by name.    Network Functions Right clicking on objects in the tree window gives the pop up menu that contains the Network menu.  The functions of these icons are defined in the chart below.       Network Variables If changes have been made to the XIF file of a controller, the change needs to be applied to the network variables of the application devices that use the template. Click on the Templates tab at the bottom of the tree window. Right click on the template that needs to updated and select "Rename variables of all application devices" A prompt will open that says "Do you want to rename all network variables of the application devices with the template name?". By clicking yes, this will rename all of the network variables of the devices that reference this template to match the names found in the template. Note: Once this has been completed double check the SNVT connections that have been created already. After the rename, it may change the SNVT order if a SNVT was renamed or removed  from the programming. This will cause connections to be binding the wrong variables together.   Creating a New Device Template If adding a new device to the database, a new device template may need to be created. See Adding a Xenta Programmable Controller to an NL220 System for instruction on how to add a Xenta programmable controller to a NL220 system. Click on the Templates tab at the bottom of the tree window. Right click anywhere in the Templates pane and click on "New device template..." In the New device template box, enter the name of the new template and browse the XIF file into the "Description file" box.    

Issue When attempting to update Vista Database in Vista System Plug-In, there is a failure producing the error  "Update Vista database failed". Product Line TAC Vista Environment NL220 LonMaker Vista System Plug-In Cause There are multiple causes for this error including LonWorks Network name not matching, signal names in Menta have too many characters, the use of an invalid alarm controller object in a Menta alarm block, and orphaned/unnecessary constants left in the Menta constants table. Resolution LonWorks Network name does not match If the LonWorks Network name in vista does not match the name in the system plug-in then the update will fail. In Workstation, right click on the LNS Network object Rename the LonWorks Network to match the name in the LNS side of the Vista System Plug-In. *If this occurs during the addition of a LNS port into a Vista database with an existing LNS port, ensure each LNS port is using a unique name. Insufficient Vista user account privilege An update to the Vista database cannot be performed if not logged in with an administrator level user account. Too many characters in a Menta point name If there is a signal name that is longer than 20 characters it can cause the Menta file to fail to update to the Vista server. Invalid alarm controller object If there is a Menta alarm block that is referencing an alarm controller object using a $ (other than the default $Alr_Cntrl) it can cause the update to fail. TAC Vista will try to add the object even though objects with $ can not be added. Orphaned or Unnecessary constants For more information on this cause and how to correct it, see Updating the Vista Database fails when trying to transfer a specific MTA object.

Issue Is it possible to get a XIF from Lonmaker when you have commissioned it by "upload" from device? Product Line TAC Vista Environment TAC Vista Toolpack TAC Vista Server LonMaker Cause If you don't have the XIF you can upload from the device in Lonmaker. Resolution There is no way to get the XIF from LonMaker but the system plug-in will create a new XIF when you add the device to the TAC Vista db. Refer to SNVTs, SCPTs, or Module Names are missing from Vista after device is added to database from System Plug-in. Compare XIF stored in Vista for instructions on how to locate the XIF generated by the system plugin.

Issue Animations, gifs, updating values, hover overs or mouse event scripts work in Workstation but do not work in Webstation. Product Line TAC Vista Environment Vista Webstation TGML graphics   Dynamic values       Cause Various reasons can cause TGML graphics to not function the same in TAC Vista Webstation as in Workstation. Typical reasons can be: Using "Static TGML viewer" vs. "Dynamic TGML viewer". Under Static view, all animations are prohibited. Using unsupported script functions can cause animation to not work in Webstation. Sizes and the number of animated .GIF images used on a single TGML graphic page. Resolution Check if the Webstation is running under Dynamics view. Go to Start->All Programs->Schneider Electric->TAC Vista Web Applications -> Vista Web Setting. (For Vista 5.1.3 or prior, go to Start->All Programs->TAC->TAC Vista Web Applications -> Vista Web Setting instead.) Click on "Graphics/TGML Views" in the left panel. Make sure the TGML View is either “AutoDetect” or “Dynamics” in the right panel.  If it is “Static”, click on the drop down manual and choose a different display viewer.   Check if using any unsupported Java script. Please reference Vista Webstation unsupported TGML functions for more information.   If a TGML graphic page contains many animated GIF images, it can cause the animation on that graphic page to run slow, discontinuously, or not run at all.  The amount of animated GIF images that can be put on one single TGML graphic page various case by case. Therefore, the best way to test it is deleting all animated GIF images and add them back on one by one.

Issue The reason for TAC dummy nodes and the logic behind the number of dummy nodes created. Product Line TAC Vista Environment Vista NL220 LonMaker TAC Vista System Plug-In Cause TAC dummy nodes are added to Xenta groups automatically in the LNS network. The dummies are made after group bindings have been created. Resolution The TAC dummy nodes are created when group bindings are made. For more information about group bindings see Verifying Xenta Group Bindings in an LNS system. Vista requires that the TAC Group and the TAC Xenta group differ in the number of devices. If you only have one Xenta group in your system, TAC Vista System Plug-In will create a dummy device and use its tag_0 (also first row of the address table) in the group binding for the TAC Group. This will allow Vista to differentiate between the TAC and Xenta groups. Notice that in both LonMaker and NL220, this dummy node that is created to represent a second Xenta group appears to be located in the same Xenta Group as the rest of the controllers. This is fine, the system plug-in is not going to create a new group to put it in, just realize why the dummy node is there. Modules do not count in the group bindings therefore the example below only has three devices in Xenta group 1.   Xenta Groups must consist of at least three Xenta devices. If you only have two Xentas in a Xenta group, TAC Vista System Plug-In will also use a dummy device, since a binding between just two devices is not considered a group binding. To create a group binding, a third device is needed. Consequently, you will need two dummy devices if you only have one Xenta in your Xenta group. Thus, if just one Xenta device exists in a single Xenta group, three dummy devices will be needed: one to separate the TAC group binding from the Xenta group binding and two more to form a Xenta group.

Issue Error messages appear in graphics that have worked in previous versions. Environment TAC Vista TGML graphics editor/ workstation graphics 5.1.8 and newer Cause There are a number of changes made in TGML in version 5.1.8, but one of the changes in the way we handle scripts being run when in a graphic when a link is invoked may cause errors.  Resolution One of the commonly used menu-components invokes a link via a script within a script. Previously the scripts remained in the cache memory and all running functions were completed, but in 5.1.8 the cache is emptied as soon as a new graphic is invoked. In this case evt.stopPropagation() should be used to terminate any scripts that could potentially run after invoking a link, for example when using nested scripts. A fix has been posted on the Graphics Exchange that addresses this issue. This is not an official Schneider Electric fix and Schneider Electric takes no responsibility for issues arising from it's use (Go to Community Post).

Issue The Vista administrator user account (system manager) is created; however, that account does not have administrator rights such as add/edit/delete any user, cannot change time schedules, graphics, etc. Product Line TAC Vista Environment TAC Vista Workstation 5 Cause When adding a system manager account in Vista, that account also needs to be added into the administrator group ($Administrators). If the system manager account is not listed under the administrator group, it will not be able to behave as the administrator. Resolution Maker sure the user account is set as a “System manager” Log into Workstation as an administrator and click on the root project folder in the left panel, right click on the user account in the right panel, and then select property. Under “General/Authority level”, it should say “System manager”. If not, change to “System manager”.                             NOTE: If the textbox is grayed out, it means the current logged in account does not have the permission to make changes to that user account. Please read Cannot edit or delete a user account in TAC Workstation to add the control rights. If this articele fails also, please go to step 2.   Click on the root project folder in the left panel, and right click on the “$Administrators” in the right panel, then select “Properties”. Under “Users”, all administrators should be listed here. Make sure the desired user account name is listed. If not, use “Add” function to add the user account. If the text box is grayed out, log in as one of the system manager account listed under “Users” to process this step.                  NOTE: If all system managers listed under “Users” are no longer available. Please contact product support to unlock the database.

Issue Unless the correct format is used when defining a dongle as locking property in https://schneider-electric.flexnetoperations.com web site when activating license, the license will not work. Product Line TAC Vista Environment Vista 5.x Cause Defining a dongle as locking property in schneider-electric.flexnetoperations.com web site when activating license. Resolution It is important that the format is entered in the following format: TAC_HL_ID=1234567890. If the "TAC_HL_ID=" part is not entered, it will not work, and you will need to rehost the licenses again, this time using the correct format as stated above. Complete instructions can be found in Rehosting a Vista 5 License on the FlexNet License Server.

Issue If there are already TAC Xenta 104-A devices commissioned in an LNS database, then it may not be possible to add TAC Xenta 104-A controllers of different system versions into the same database. Nor is it possible to do a replace. Certain firmware versions of the 104-A controller are not compatible with one another. Trying to add a different system version to an existing database will produce an interface does not match error. For more information on this error, see The new program interface does not match the previously defined program interface. (Subsystem: NS, #59). Product Line TAC Vista Environment NL220 LonMaker Vista Cause The incompatibility between different system versions of the TAC Xenta 104-A controller is due to a change that was made in the size of the SNVT declaration area residing in the device memory. The change in device memory occurred between version 1.10 and 1.20. For the same Program ID, LNS requires this size to be the same as previously commissioned devices. Resolution The first action that should be taken is to update the LNS network to the most recent version. It has been confirmed that newer LNS versions have addressed this issue so that no further action is required. With newer LNS software, different version types of the TAC Xenta 104-A may be added to the same database.  If upgrading the LNS software is not an option, the firmware in the controllers can be upgraded as a work around to correct the issue. In order for a TAC Xenta 104-A controller with version 1.10 to reside in the same database as version 1.20, the 1.20 controller must be upgraded to version 1.20A. In similar fashion, version 1.21 must be upgraded to version 1.21A to coincide with version 1.10. To add a 104-A controller with version 1.21 to a database with version 1.20 already on it, no further action need be taken. Version 1.20 and 1.21 are compatible. It is important to reference the compatibility matrix found below. Changing the firmware to an "A" version will then make the controller incompatible with versions 1.20 and 1.21. Also note that it is not possible to upgrade from system version 1.10 to 1.20/1.21 due to the memory configuration. The modified "A" versions will not be loaded into the controllers from the factory. These NXE/APB files will only be available on the Buildings Business Extranet. To download the NXE/APB file for v1.20A or v1.21A, go to The Exchange Download Center. Perform a search for TAC Xenta 104-A Firmware. The 1.20A version will be labeled "TAC Xenta 104-A Version 1.20 (78 Kb)" and the 1.21A version will be labeled "TAC Xenta 104-A Version 1.21A (45 Kb)".

Issue Necessary Accounts for DCOM and Firewall Security Settings. Product Line TAC Vista Environment TAC Vista Webstation TAC Vista Remote Workstation DCOM Configuration Cause DCOM Parameters must be set to allow for remote connectivity to the Vista Server. Resolution You will notice in the "Security Settings for MS Windows XP SP2 and MS Windows Server 2003 SP1" instructions that several changes are needed for the accounts "ANONYMOUS LOGON" and "Everyone". If these accounts do not exist, they must be created and set to allow local launch and remote activation permissions. See also Helpful Vista Utilities - Configure DCOM instantly, Register ASP.NET for an automatic DCOM utility.

Issue Error message "Invalid Object Name" Error message "Failed to transfer application file to TAC Vista"   Product Line TAC Vista Environment LonMaker NL220 Menta TAC Vista System Plug-In Cause Error message "Invalid Object Name" appears when browsing in a Menta file in TAC Vista. Add it via the System Plug-in results in an error saying "Failed to transfer application file to TAC Vista"  Resolution This could have different causes. There could be a signal name that is to long (longer than 20 characters). The problem can also be that there is an ALARM that have an alarm controller object defined that are using a $ (other than the default $Alr_Cntrl). TAC Vista will try to add the object and you are not allowed to add objects with $ in them. For more help see "Update Vista database failed" Error in Vista System Plug-In.

Issue When adding points to your OPC Client from a Schneider Electric Vista OPC Server that contains points from Xenta Servers error "The item definition does not conform to the server syntax". Product Line TAC Vista Environment Vista 5.x Vista OPC Server 1.6.x Xenta Server 511-B, 731, 527, 913 Cause There are certain characters that are invalid in an OPC Server environment which are allowed in the Vista Server database. Invalid names include I/NET, RS232/485 A, and TCP/IP. Resolution Create a folder in the Vista database and create shortcuts for the points that are suffering this problem. This avoids any invalid characters, but grants full functionality for the data in question. For more OPC Server issues please see Vista OPC Server Installation and Known Issues.

Issue When a specific application request exceeds the standard capability of I/NET it is sometimes possible to use XBuilder to expand possible applications. Product Line TAC INET, TAC Vista Environment I/NET XBuilder I/NET Host Tool Cause When a specific application request exceeds the standard capability of I/NET it is sometimes possible to use XBuilder to expand possible applications. Resolution This is a sample access control application to demonstrate the possibility. Minimum requirements for this are :Xenta 527 Web Server. If you wish to use Menta Programming, use a Xenta 731 or Xenta 913. Application: Customer Requests an Audible Buzzer be triggered when a door is forced open, but not shut off until the alarm has been acknowledged. Create a DO point to controller your buzzer/light/alarm indicator (buzzer DO) Create an internal AO point to function as a translator (logic AO) Add a Calc to the buzzer DO: ~(P0=C0) where P0 is the logic AO and C0 is 80 Perform a Station save In XBuilder, create a project for the 527 Web Server Insert or re-insert the I/NET network Add a connection object Drag the Flags attribute of the Doors DO point to the "from" part of the connection object Drag the Value attribute of the logic AO point to the "to part of the connection object Generate the Project and Send to Target. The response time of the buzzer coming on or going off is dependent on the Scan interval of the buzzer DO.  The reason it works is that the flag attribute of the Door point will equal exactly 80 if you have an alarm flag and the point is still in alarm (the alarm has a value of 64 and unack has a value of 16 totaling 80. See Decoding the I/NET signal "flags" attribute for more information). The door point will stay in alarm until it is acknowledged so this will stay at 80 until someone acknowledges the alarm, or puts the point in Manual/Test.  The Buzzer will not activate if the point is in Manual or Test The above solution will trigger off any alarm specified from the door editor (Door Open To Long, Door Forced, Bad Card read, etc).  Turn off the other possible alarms, or create an addition internal point labeled Door Forced.  The Door DO point can trigger an event sequence based on Forced door to control the additional point. If you do this the calc will need to be modified to ~((P0=C0)|(P0=C1)|(P0=C2))  C0=16 C1-64 C2=80. This will allow for the buzzer to be on until the point has been acknowledged and return to normal

Issue Commission and Download command from Vista Workstation on a controller/network beneath a Xenta 911 communication port results in "Error: Failed to connect to TAC Xenta 911 - Invalid User/Password" Product Line TAC Vista Environment Vista Classic Network Communication Port - Xenta 911 Xenta 511/911 Cause Vista port properties has User name and Password stored.  If the user name or password are changed in the controller, these changes must be made to the Vista server settings as well. Resolution Obtain the most current user name and password for the Xenta hardware device If the password is not known and cannot be obtained, a temporary password can be assigned.  Please see Receive a temporary session password for a Xenta 5/7/9xx if the password has been lost. Right-click on the Xenta 911 communication port and select Properties Enter the new user name and password under TCP/IP settings Attempt the Commission and Download command again.

Issue Where can I obtain the technical information, manuals, guides or other documents on Continuum? (or other product lines) Product Line Andover Continuum, EcoStruxure Building Operation, Satchwell Sigma, TAC Vista Environment Continuum Cause Manuals and documentation can be used for training or self-help troubleshooting for Continuum. (or other product lines) Resolution Review the course notes The notes and document gathered during training can be very useful and a great source of information. Technical Documentation is available on the EcoBuilding Download site at: https://ecobuilding.schneider-electric.com/ For technical data/PDFs installed with Continuum, Go to Start > All Programs > Continuum > Documentation The discs and downloaded zip files that are used to install Continuum also include technical PDFs. Some of these are installed when Continuum is installed. (CONTINUUM) Most of the online help is context based, thus if you click help within a InfinityNumeric, then InfinityNumeric help is given. This help file can also be searched in the normal way. It is an excellent source of information. (CONTINUUM) Bookmark this Knowledge Base:  https://community.se.com/t5/Knowledge-Base/tkb-p/knowledge-base_public New articles are added daily and should be used as a first stop for self help. The Exchange Community site has a community space just for Continuum, SmartStuxure, Sigma, Vista etc.  for posing questions, sharing solutions, https://community.se.com/ (CONTINUUM) The Continuum catalogue also provides a good overview of the product range Some documentation is freely accessible, see https://www.schneider-electric.com/en/work/products/building-automation-and-control.jsp If an end user has problems on site, they should first contact Schneider Electric local support or service department (In the UK contact Support Bureau 0870 606 2800, cs.bureau@uk.schneider-electric.com) SmartStruxure For Building Operation help can be found online at: http://help.sbo.schneider-electric.com/home/index.castle?locale=en-US&productversion=1.8   CONTINUUM ONLY Always ensure the site fits within the Continuum Compatibility Matrix, this includes:  For PC requirements see the relevant Installation Instructions included with the Continuum Software Controller firmware (Continuum, BACnet, Infinet), use the most up to date available (of the correct version) Workstation operating systems, service packs and .NET framework versions SQL versions See Software and Firmware compatibility matrix for older versions of I/NET, Vista, Andover Continuum, Satchwell Sigma, I/A Series, and StruxureWare Building Operation for other system data The Continuum.chm file found in the Continuum directory include the "online help" It is usually worth ensuring the latest Continuum service pack is applied to ALL workstations on site (Cyberstation and WebClient) Click Here