Issue Is the Operators Panel TAC OP1500 still available? Environment TAC Vista 5.1.X Cause N/A Resolution The TAC OP1500 is no longer available from Schneider Electric Buildings Business. It may be available from other Schneider Electric branches. See Product Announcement PA-00138 for details.

Issue Is the Continuum Cyberstation a B-OWS (BACnet Operator Workstation)? Product Line Andover Continuum Environment Continuum Cyberstation BACnet Cause Can't find reference to Continuum Cyberstation being defined as a B-OWS. Resolution The Continuum Cyberstation is a B-OWS and complies with ANSI/ASHRAE standard 135-2004.  However, the Continuum Cyberstation has not been BTL tested, please see the Schneider Electric BTL Listing of Tested Products.    The following selection is taken from the Andover Continuum Family of User Interfaces document describing Continuum's Cyberstation capabilities. Native BACnet B-OWS CyberStation communicates with the BACnet devices using BACnet/IP in strict accordance with ANSI/ASHRAE standard 135-2004 and is designed to function as a BACnet Operator Workstation (B-OWS) and BACnet Broadcast Management Device (BBMD). The CyberStation can communicate to all Andover Continuum BACnet Devices as well as any third party BACnet Device on the BACnet network.

Issue Is it possible to use DC voltage to power the 7793, 7798, and the DPUs (7910, 7920)? Environment 7793 7798 7910 DPU 7920 DPU DC power Cause Although this is not the preferred method of powering these devices they are capable of this configuration. We strongly recommend the use of DC voltage be reserved for emergency backup power. Resolution The 7798B Controller, 7910, and 7920 DPUs can be powered by +24 VDC. The DC voltage should be at least +24 VDC - +27 VDC is best. Refer to the following TCONs for specific wiring detail and installation instructions: 7798B TCON 138 7910 TCON 116 7920 TCON 117

Issue Is a controller shipped from the factory with the latest firmware revision supported in older versions of Continuum? Environment Continuum 1.xx Cause Running an older version of Continuum (1.74sp2) and bought a new Netcontroller II, that has 2.10000xx for a firmware version. Resolution Please refer to the Continuum Compatibility Matrix for Continuum versions and Controller firmware versions. Andover Continuum Software and Firmware Compatibility Matrix Versions 1.94 SP1 Example: Running Continuum 1.74sp2, first Continuum version to support the Netcontroller II 9680. Bought a new Netcontroller II 9680 and the current version of Continuum available is 1.92. The firmware installed on the controller (2.10000xx) is the latest available, and for older installations of Continuum you would need to down rev the firmware a version support per the Continuum Compatibility Matrix and in the instance of 1.74sp2 that would be 2.00000xx.

Issue Is Windows 7 supported in CyberStation? Environment CyberStation Cause Is Windows 7 supported in CyberStation? Resolution Versions of Continuum Cyberstation prior to 1.93 do not support Windows 7. See our Continuum Compatibility Matrix for supported OS and version Windows 7 is supported starting in Cyberstation v1.93

Issue Virtualization using VMWare, Virtual Server or other products is useful when deploying applications Is virtualization supported with Continuum?  Will Continuum work in a virtual environment?  Environment Continuum WMWare Virtual Server Windows XP Windows Vista Windows Server 2003 Windows Server 2008 Cause Continuum compatibility with Virtual Machines (virtualization - VMWare) Resolution VMWare VSphere 5.5 and 6.0 has now been qualified to work with Cyberstations and Web.Client in Continuum v2.0 and above. Note that this will require a software licence and that the virtual environment must comply with the minimum system requirements for Cyberstation and Web.Client Server. See the latest Continuum v2.0 Compatability Matrix for details.                                                         There have been reports from the field from engineers that  have used Continuum and SQL server with various virtual software not currently qualified. If there are any issues with this implementation with an unqualified solution, then it would be necessary to install Continuum on a supported configuration (see the Continuum Compatibility Matrix) prior to involving engineering to evaluate any problems. This solution has not been tested and is outside of what we currently support. These include: Other VMWare environments, Microsoft Virtual PC (HyperV), Citrix, Windows 7 XP Emulation, etc. Marathon Redundant SQL Servers is a very specific solution which does use virtual machine. This is an isolated case and does not apply to standard implementations of Continuum or Webclient.

Issue Internet Explorer 9 will not work with webClient Product Line Andover Continuum Environment webClient Windows 7 Windows Server 2003 Windows Server 2008 Cause Internet Explorer 9 isn't compatible with webclient 1.93 and below Resolution Certain versions of webclient are compatible with specific versions of Internet Explorer. Download Andover Continuum Software and Firmware Compatibility Matrix from The Exchange Download Center. Internet Explorer 9 has not been tested against webclient 1.93 or below, but there have been reports that it will not work with webpinpoint graphics. Two options to resolve: Downgrade Internet Explorer according to the Continuum compatibility matrix. web.Client v1.94 SP1 - Software (Release Date: 2013-Jul-14) for webClient 1.94 includes support for Internet Explorer 9.  

Issue Can an I/NET control system be connected to a Firefighters Smoke Control Station (FSCS)? Which I/NET product is often recommended as a Fire Alarm Panel (FAP) Interface? Environment I/NET FSCS UL 864 Cause Smoke control in an HVAC application. Resolution I/NET can be connected to a UL 864 listed panel providing contact inputs (for Lamps/Enunciator) and contact outputs delivering override switch status. Only the 7797-12-U8 is approved for use as the primary means of serial alarm reception in a listed smoke control system. Refer to TCON 231, Smoke Control Systems Manual, FSCS Interface Options for more details.

Issue Many customers still have a requirement to run Lonmaker 3.13, but have project specific issues related to software fixes in newer version of LNS Server, and an LNS Server upgrade is required. Product Line TAC Vista Environment Echelon Lonmaker LNS Cause Older versions of Lonmaker 3.1 and LNS server had multiple defects that were addressed in later version of Lonmaker Turbo and LNS Server Turbo. However, it is possibly to run Lonmaker 3.1 and only upgrade the LNS server engine to take advantage of software fixes over time. Resolution NOTE: Any LNS Server version older than 3.10 needs to first be upgraded to 3.2x before 3.2x service packs can be installed. Also, please take into consideration that after upgrading the LNS Server on a system that any other system that needs to open that same database will have to be at the same version or higher. For example: a database upgraded to 3.27 can not be opened on the machine running 3.08.   Please follow these steps for upgrading LNS server to 3.22 and finally up to 3.27: Identify what version of Lonmaker and LNS server are currently running on the system. Please see How to determine what version of LonMaker and LNS Server on a computer for instructions on how to find the current version of Lonmaker and LNS Server currently running. As seen in the screen shot below the system is running Lonmaker 3.13.10 with LNS Server version 3.08. Download LNS Server 3.22. Once this file is downloaded please unzip all of the contents to the desktop of the local machine. Run setup.exe from the extracted files in the LNS Server 3.22.zip, and step through the installation process. Once the installation of 3.22 is complete please reboot the machine. After the machine has rebooted please verify that the system is now running LNS Server 3.22. Using How to determine what version of LonMaker and LNS Server on a computer for instructions on how to find the current version of Lonmaker and LNS server the system should now show LNS Server version 3.22 like below: Now that the system is upgraded from LNS Server 3.08 to 3.22, service pack 7 should be installed to upgrade the system to LNS Server 3.27. Please download LNS Server/Turbo edition Service Pack 7 file to your local machine. Unzip the contents of the LNSServerTurboSp7.zip to the desktop of the local machine, and run the LNSturboServerSp7.exe file. Step through the installation process. When the installation is completed please reboot the machine. After the machine has rebooted please verify that the system is now running LNS Server 3.27. Using How to determine what version of LonMaker and LNS Server on a computer for instructions on how to find the current version of Lonmaker and LNS server the system should now show LNS Server version 3.27 like below:

Issue 5.1.5 is now packaged into two different spanned archives because of how large the installer files have become. At this point there is a 300 MB file limit on exchange online and the 5.1.5 installer package is now 336 MB, hence the reason the installation package had to be split into two archives. Because the installation package is a spanned archive it will need to be opened with WinZip or a compatible archive program. In these instructions we will be downloading and installing WinRar to open the installation archives. Note 1: WinRar is technically not free software, but it does allow its demo license to extend on past the demo period. It is at the customer’s discretion on what legal and compatible archiving software they chose to use. Note 2: The built in zip archive program in Windows 7 will open this spanned archives without fail. Product Line TAC Vista Environment Vista 5.1.5 software download on any operating system older than Windows 7 Cause File limit set on exchange online and the built in .Zip extractors in older operating systems do not have the capabilities to open these spanned archives. Resolution Create a folder on your local C: drive and name it 5.1.5 To download and install WinRar please visit http://www.rarlabs.com/download.htm and find the appropriate version. If you would like to use Winzip instead, please visit http://www.winzip.com/win/en/downwz.htm to download and install the appropriate version Navigate to exchange online at Download Center login, and click the links Product > TAC Vista > Vista Software > TAC Vista 5.1.5 > Downloads Click the file named TAC Vista Server 5.1.5 with Workstation (File 1 of 2) and save. Save the file to the 5.1.5 folder created in step 1. Click the file named TAC Vista Server 5.1.5 with Workstation (File 2 of 2) and save. Save the file to the 5.1.5 folder created in step 1. Allow the downloads to finish and navigate to the location of the 5.1.5 folder. Right click on the file named TACVistaServer515.zip and select Open With > WinRar archiver WinRar should open the archive file and you can now double click and run the TACVistaServer515.exe file within it. This exe file will access the other file (TACVistaServer515.z01) within the 5.1.5 folder automatically during the install process.

Issue Only one Xenta Server can be installed in Vista on a single Lonworks network. Product Line TAC Vista Environment TAC Vista Lonworks Xenta 511, 527, 555, 701, 711, 721, 731, 913 Cause When a Xenta 500/700/913 is installed in Vista as a Xenta Server, it is intended to act as the Lonworks network interface for Vista. By default, the Xenta 500/700 also handles the alarms generated in devices on the Lonworks network.  Only one Xenta Server can, therefore, exist on a single Lonworks network.  To enforce this, Vista does not allow you to add a Xenta Server to an existing Lonworks network. Resolution Install the first Xenta 500/700/913 device as a Xenta Server. Install any additional Xenta 500/700/913 as Lonworks Devices on the network. As the Xenta Server handles the alarms generated in devices on the Lonworks network, the additional Xenta 500/700s must be prevented from handling alarms. This is done by changing the Alarm Server setting in XBuilder to 'Disabled'. The XBuilder projects for the Xenta 500/700/913 configured as Lonworks Devices cannot be accessed from Vista.  In A LNS environment, SNVTS will be able to be seen through Vista workstation but no XBuilder parameters. These XBuilder projects must be treated as standalone and an XBuilder project backup is managed from outside the Vista database.   For details on configuring multiple Xenta 500/700/913s in Classic and LNS networks see these manuals: TAC Vista - Classic Networks - Technical Manual TAC Vista - LNS Networks - Technical Manual TAC Xenta Server - TAC Networks - Technical Manual TAC Xenta Server - Gateway - Technical Manual

Issue Necessary steps to successfully install a "Stand Alone" versions of the Vista suite where a full Vista installation is not required. Product Line TAC Vista Environment Menta XBuilder Graphic Editor TGML MTA XBP Cause Sometimes a site may not require a full Vista package but will require the ability to edit associated Vista programs. This is the proper way to install only a portion of the Vista Software Suite. Resolution Create a account to the Download Center. Download the needed "stand alone" programs of the desired version, download here: Menta XBuilder Graphic Editor Download a matching version of the "stand alone" License Server, download here. Execute the downloaded programs on the host PC Order appropriate licenses using following program part numbers to validate the software (links to iPortal) Menta 000882401 XBuilder 000882411 Graphic Editor 000882221 (For an existing site requiring an upgrade from older Vista IV or Vista 5.0) Menta Upgrade Pricing 000883401 XBuilder Upgrade Pricing 000883411 Graphic Editor Upgrade Pricing 000883221 An Entitlement will be mailed which must first be Hosted to the PC. This is performed on the schneider-electric.flexnetoperations.com website by following How to Host a Vista Site License. License the Software on the License Server (Stand-alone Licensing for Vista 5 Applications)

Issue When attempting to install the Signal-XP software on a Windows XPsp2 computer, the installation aborts without displaying any error messages. Environment Windows XP-sp2 computer Cause The installation of the Signal-XP software requires that the HASP security plug be connected to the computer and be recognized before the Signal-XP software can be installed.  Due to changes made by Microsoft in the Windows-XP service pack 2 upgrade, the HASP software included with the Signal-XP installation cannot read the HASP security plug. Resolution Download and install the updated HASP4 driver per the instructions include in Technical Alert TA06-03.  Please note that the referenced (Aladdin) web site may have changed its visual layout since the bulletin was published.  The noted version of the driver software may not be available.  Use the latest Win32 driver that is available on the Aladdin website.

Issue Installation cable requirements Product Line Andover Continuum Environment Continuum Cause Need to specify a cable type for a site Resolution Installation cables have to be chosen taking in to account the local regulations and legislation, the installation environment and the electrical requirements. The Continuum specifications give the electrical requirements. For this reason actual cable types, makes or Belden numbers can not be stated, only as helpful guidance as a cable that may meet the electrical requirements only. BACNET MSTP - See What cable type should be used for BACnet MS/TP communications?. INFINET - See What cable type should be used for Continuum Infinet bus communications. CARD READER - See the manufacturers requirements for the cables, also Maximum Cable Length Between ACX and Card reader. ANALOGUE and DIGITAL INPUTS - See the relevant Continuum specification eg. I/O Modules. See Andover Continuum IO System Reference (especially note screening and grounding requirements) I/O MODULE (RS-485 & LON) - See the relevant Continuum specification eg. I/O Modules See Andover Continuum IO System Reference For ETHERNET, LON, MODBUS RTU, OTHER THIRD PARTY BUS/NETWORK - See the relevant external documents

Issue Files required to install EcoStruxure Building Operation Web Reports Server Product Line EcoStruxure Building Operation Environment Building Operation WebReports up to version 3.2.  Note: WebReports is no longer included in Building Operation 2022 and above. Cause Tutorial for configuring Web Reports Resolution EcoStruxure Building Operation WEB Reports Server Release To start installation, download WebReports Operating Guide and WebReports Reference Guide Installation Outline: The WebReports Reference Guide provides detail information about hardware, software requirements, and steps required to configure the applications. The following steps are an overview of the complete installation. Points 1-4 are easily and/or automatically done using "SBO Reports Preparation" available from the Buildings Community. This tool is not officially supported, but has proven to be helpful in many cases. Install and Configured required Windows applications, roles, and features. Outlined in Sections 3.4 of the WebReports Reference Guide Download and install SQL Server 2008 R2 Standard with Advanced Services it requires version 10.5 or later. Follow configuration steps found in Section 3.5-3.6 of the WebReports Reference Guide SQL 2008 R2 Standard with Advanced Services file name SQLEXPRADV_x64_ENU.exe Install .NET framework 4 per WebReports Reference Guide section 3.7 Ensure that the Enterprise server is running on another machine, or at this point install and configure it on the local machine Install WebReports Server using the processes defined in WebReports Reference Guide section 3.9 and 3.10 The online help guide for EcoStruxure has a tutorial which will walk you through configuring the report Server, and running reports: WebReports Overview  If you wish to create custom reports. Please follow the instructions as outlined in How to create custom reports in Building Operation WebReports APPENDIX A: Verifying system is ready for reports installation Before installing WebReports, but after configuring Windows Roles and Features, SQL and install .NET 4.0,(SBO 1.5 uses .NET 4.5) the user should always: Check to see that SQL Server is up and running Check that the user you are planning on installing WebReports with can connect to SQL and Microsoft Reporting Services. Log into SQL using SQL Server Management Studio User should be able to connect and view databases. Connect to the MS Reporting Services URL You can obtain the URL by: Start->All Programs-> Microsoft SQL Server 2008 R2->Configuration Tools->Reporting Services Configuration Manager. Once logged into Reporting Services Configuration Manager click on “Report Manager URL” and click the URL Verify that Reporting Services Manager page loads without error. If you run into issues with the above, a possible solution is to turn of User Account Control Settings. This can be disabled by going to the Windows Control Panel, selecting User Accounts, selecting "Change User Account Control Settings" and moving the slider all the way down. You must restart the PC for this change to take affect. Repeat the above steps and contact PSS if you are still unable to validate the system. APPENDIX B: Upgrading a report server installation As described in appendix A, the logged in Windows user is used to install the report server, and this user must have access to the SQL database. That is also true when upgrading the report server installation, so make sure you are logged into Windows with the correct user. Another option is to SHIFT + right click the installer, and select "Run as other user".

Issue What are the input and output options for the Multical 602 heat meter? Product Line Field Devices Environment Standalone LonWorks M-Bus Cause The current datasheet, F-27718-2, for the Multical 602 & Ultraflow 54 Heat Meter is not clear about what input and output options are available and how they can be combined. Resolution The Multical 602 can be supplied with two internal modules - a top module with clock backup, pulse outputs or M-Bus and a base module with M-Bus or Lonworks.  Either or both modules may be omitted. There are several options for both the top and base modules. Use the Order Specifications chart in section 8 of the datasheet to place the initial order.  Section 9 of the datasheet lists the individual parts, if you want to modify the meter later. The current datasheet, F-27718-2, lists four top modules with pulse outputs.  Of these, only one is now available -  MAPULSEOPTOPC  c/w RTC + Hourly Data Logger + 2 Pulse O/Ps + Scheduler. MAPULSEOPTOPA, MAPULSEOPTOPB and MAPULSEOPTOPD are all obsolete. It is possible to combine any of the available top modules with any of the available base modules.  However there are restrictions on the power supply with some combinations.  See the following table: Top-> Base     ˅ without top module MAPULSEOPTOPC MAMBUSTOP without base module Battery or Mains Battery or Mains Battery or Mains MAMBUSBASE Battery or Mains Mains only Mains only MALONBASE Mains only Mains only Mains only MA4-20BASE Mains only Mains only Mains only Mains supply options: MA230VSUPPLY or MA24VSUPPLY Battery supply option: MABATTDCELL

Issue In what positions can Continuum controllers be mounted? Environment Continuum Product Line Cause Not sure if the controllers can be mounted on both the vertical and horizontal plane. Resolution There may be some specific mounting instructions for some of the controllers, but for the most part they can be mounted in any direction in the vertical plane. Controllers with relays should not be mounted with the edge the outputs are on facing down. Consult the installation instructions (found here) for each controller for any specific mounting requirements.

Issue An Infinity Program object appears In the Occupancy Point field of the schedule editor. When an attempt is made to browse, select apply the proper occupancy numeric, the same Infinity Program object reference reappears. Environment Continuum 1.74 Schedules Occupancy Point Database Cause This behavior was related to the behavior described in TPA-BOST-08-0005.00.  Resolution Apply the Cyber 1.74 SP2 HotFix For TPA-BOST-08-0005.00.

Issue Importance of correct selection / installation of Satchwell 3-port Valve Body to provide Mixing function or Diverting function. Environment Satchwell 3-port Valve Body to provide Mixing function or Diverting function in heating or cooling circuit.   Satchwell MB, MBF, MJF, MZ, MZF, MZX Cause Incorrect selection / installation  of Satchwell 3-port Valve Body to provide Mixing function or Diverting function may result in poor control, damage to the Valve Body, damage to the Valve Actuator or damage to the hydraulic installation. Resolution Determine which of the following types of hydraulic circuit the Satchwell 3-port Valve Body is to be installed in. Constant Temperature Variable Volume (CT) circuit e.g. AHU Heating / Cooling Coil or Calorifier Coil  Variable Temperature Constant Volume (VT) circuit e.g. Radiator System For Constant Temperature circuit application install Satchwell 3-port Valve Body as follows :- MJF, MZ, MZF, MZX install in RETURN pipework. Port 3 - Connect to Bypass (IN) Port 2 - Connect to Coil Return (IN) Port 1 - Connect to System Return (OUT) MB, MBF install in RETURN pipework. Port 3 - Connect to Bypass (IN) Port 2 - Connect to Coil Return (IN) Port 1 - Connect to System Return (OUT) OR MB, MBF may alternatively be installed in FLOW pipework Port 3 - Connect to Bypass (OUT) Port 2 - Connect to Coil Flow (OUT) Port 1 - Connect to System Flow (IN) For Variable Temperature circuit application install Satchwell 3-port Valve Body as follows :- MJF, MZ, MZF, MZX install in FLOW pipework. Port 3 - Connect to Bypass (IN) Port 2 - Connect to Boiler Flow (IN) Port 1 - Connect to System Flow (OUT) MB, MBF install in FLOW pipework. Port 3 - Connect to Bypass (IN) Port 2 - Connect to Boiler Flow (IN) Port 1 - Connect to System Flow (OUT) OR MB, MBF may alternatively be installed in RETURN pipework Port 3 - Connect to Bypass (IN) Port 2 - Connect to System Return (IN) Port 1 - Connect to Boiler Return (OUT) N.B. It should be noted that the alternative installation methods are valid for the MB and MBF Valve Bodies due to the ROTARY SHOE construction of the MB and MBF Similarly it should be noted that the alternative installation methods are not valid for the MJF, MZ, MZF and MZX Valve Bodies due to the PLUG AND SEAT construction of the MJF, MZ, MZF and MZX . Failure to install MJF, MZ, MZF and MZX Valve Bodies correctly in the pipework may result in VALVE VIBRATION in the pipework caused by WATER HAMMER    INSTALLATION OPTIONS - MJF, MZ, MZF and MZX 3-PORT PLUG AND SEAT VALVES MAY BE INSTALLED TO MIX IN THE FLOW VALVE BODIES USE TWO “IN” PORTS (Ports 2 & 3) AND ONE “OUT” PORT(Port 1)   3-PORT PLUG AND SEAT VALVES MAY BE INSTALLED TO DIVERT (BY MIXING) IN THE RETURN VALVE BODIES USE TWO “IN” PORTS (Ports 2 & 3) AND ONE “OUT” PORT(Port 1)   INSTALLATION OPTIONS - MB, MBF  3-PORT ROTARY SHOE VALVES MAY BE INSTALLED TO MIX IN THE FLOW USING TWO “IN” PORTS (Ports 2 & 3) AND ONE “OUT” PORT (Port 1) 3-PORT ROTARY SHOE VALVES MAY BE INSTALLED TO MIX IN THE RETURN.USING ONE “IN” PORT (Port 1) AND TWO “OUT” PORTS (Ports 2 & 3)) 3-PORT ROTARY SHOE VALVES MAY BE INSTALLED TO DIVERT IN THE RETURN USING TWO “IN” PORTS (Port 2 & 3) AND ONE “OUT” PORT (Port 1) 3-PORT ROTARY SHOE VALVES MAY BE INSTALLED TO DIVERT IN THE FLOW USING ONE “IN” PORT (Port 1) AND TWO “OUT” PORTS (Port 2 & 3)   RELATED INFORMATION - DIVERTING IN THE FLOW It should be noted that some manufacturers produce 3-Port Plug and Seat Valve Bodies specifically designed to DIVERT in the FLOW.  Such Valve Bodies have 1 IN Port and 2 OUT Ports   Please check the latest catalog for current equipment.  

Issue Import/ Export functions of Tree Tech 3.2 on Windows XP SP3 were disabled by recent Microsoft update. No .GDF file exported, no error message displayed. Environment Tree Tech revision 3.2 installed on Windows XP SP3 computer Cause Believed to have been caused by a recent Microsoft update.  Resolution There are two work-around options: Run Tree Tech 3.2 on Windows 7 , 32-bit machine If the project database is backed up from the Windows XP computer, it can be reloaded on the Windows 7 computer. The project database path on the Windows XP computer is: c:\Documents and Settings\All Users\Schneider Electric\TreeTech\Jobs\Projects\  On a Windows 7 computer, the file path for the TreeTech database is c:\Program Data\Schneider Electric\TreeTech\Jobs\Projects\    Un-install Tree Tech 3.2, install Tree Tech 3.1 on Win XP SP3 machine if no Win 7 machine available. Tree Tech 3.1.exe is available on The Exchange Download Center Run the WIBs purchase, generate license request for IV-DEMO-CDE, send file to us to create a license. OK to export GCM database already uploaded in 3.2