Building Automation Knowledge Base

Issue Satchwell ALE series Linear Actuator requires replacement. Product Line Field Devices Environment Satchwell ALE series Linear Actuator installed on Satchwell MJF, MZ, MZF, VJF, VSF, VZ or VZF series Plug and Seat Valve Body.  Actuator type :- ALE series.  Cause Obsolescence of Satchwell ALE series Linear Actuator. Resolution Replace Satchwell ALE series Linear Actuator with Schneider Electric M800 Linear Actuator and Linkage Kit :-   Linkage kit to mount a M800 actuator to a Satchwell valve (MZ,MZF, VZ, VZF, VSF and MJF) = L2SV Replace ALE Actuator with M800 + L2SV combined part number 880-0650-000 Replace ALE with Auxilary Switch kit with M800-S2 + L2SV combined part number 880-0651-000 Just linkage kit = 880-0124-000 Just M800 = 880-0310-030 N.B.  Should the Satchwell ALE series Actuator include a wired Auxiliary Switch then the following Accessory should also be installed on the S-E M800 Actuator as appropriate :-  S2 - Two independent 24 volt 4amp AC-1 rated SPDT Auxiliary End Point Switches. (880-0104-000)   Particular care should be taken when selecting an Schneider Electric Forta M800 Actuator to replace an existing Satchwell ALE series Actuator. The Schneider Electric Forta M800 Actuator may be used to replace an existing Satchwell ALE series Actuator but it should be noted that where an existing Satchwell ALE series Actuator has been connected directly to a Satchwell Controller, an independent Transformer rated to provide the greater level of power required by a single Schneider Electric Forta M800 Actuator (50VA) will also be required. (e.g. Schneider Electric Transformer Type TR60)   Where an existing Satchwell ALE series Actuator has been connected via an independent Transformer, it is possible that the Transformer may have been rated to provide the level of power required by a single ALE series Actuator (9.5VA) only.   In such circumstances the existing independent Transformer may also require replacement by another independent Transformer, rated to provide the greater level of power required by a single Schneider Electric Forta M800 Actuator (50VA) (e.g. Schneider Electric Transformer Type TR60) Details of the Schneider Electric M800 Actuator may be viewed here Details of the Schneider Electric TR60 Transformer may be viewed here

Issue Once the occupied cooling and heating setpoints are written from a BMS, the user is not able to change the setpoint from the room controller Product Line EcoStruxure Building Expert, EcoStruxure Building Operation Environment Automation Server Enterprise Server SE8000 Series Room controller Viconics branding VT8000 Series Multi Purpose Manager (MPM) BACnet Cause By default, the occupied setpoint value is written to Room Controller with priority level 16 by the BACnet front end. Attempting to change the setpoint locally using the up and down arrows on the SE8000 Room controller will not be allowed since the Room controller uses the relinquish value internally (priority 17) which will be automatically overwritten by the BACnet front-end. Resolution The work around is to release the BACnet front-end control over the BACnet object using a LUA4RC script. The script can be uploaded using one of the following two methods: 1 - Uploader Tool A USB cable is required to upload the script. The uploader tool can be downloaded from the Exchange Download Script Download Uploader Tool   2 - BACnet The script can also be directly uploaded via BACnet using the "Description" field as shown in the image below if (ME.AV92 == 6 or ME.AV92 == 7) then ME.AV39_PV[16] =nil ME.AV39_PV[10] =nil ME.AV40_PV[16] =nil ME.AV40_PV[10] = nil ME.AV92_PV[17] =0 end Where, ME.AV92 is the Keyboard value ME.AV39 is the Occupied Heating Setpoint ME.AV40 is the Occupied Cooling Setpoint Using this method, the script can be uploaded to multiple SE8000 Room Controllers by following the steps in Bulk Lua4RC upload via BACnet (Mass upload) For more information about Lua4RC, refer to the Lua4RC Programming Guide

Issue Using a Demo License with Vista, Demo will not run on site PC. Error: lc_checkout failed: Cannot find license file. FLEXible License Manager lc_checkout failed: Cannot find license file. The license files (or license server system network addresses) attempted are listed below. Use LM_LICENSE_FILE to use a different license file, or contact your software provider for a license file. FLEXnet Licensing error:-1,359. System Error: 2 "No such file or directory" For further information, refer to the FLEXnet Licensing End User Guide, available here. For instructions on using a Site License when encountering this error, refer to Switching from the Demo license to the site License in Vista 5.1.7 or older. Product Line TAC Vista Environment Vista Licensing Flexnet Lmtools lc_ Cause Unlike using a Vista Site License, the Demo license does not require the use of the Flexnet License Server. . Resolution Select a location to store the Demo License on the site PC Start Vista Menta At the prompt to select between License Server or License File, Choose "Specify the License File" Select Browse and navigate to location where you stored the license file in step 1. Highlight the Demo License and select Open. Verify that Menta starts. Start Vista Server Start Vista Workstation Verify Vista Workstation starts.

Issue How to be redundant with your intelligent Building Management System (iBMS) Product Line Andover Continuum, EcoStruxure Building Operation, Field Devices, Satchwell Sigma, Security Expert, TAC INET Environment Existing intelligent Building Management System Open Mind High Availability Solutions (Deprecated by manufacturer) everRun MX ztC Edge Cause In engineering, redundancy is the duplication of critical components of a system with the intention of increasing the system's reliability. To be redundant with an intelligent Building Management System (iBMS) would take on two possibilities. Have an alarm on critical points alerting personnel who move into action quickly replacing control boards or devices in the event of failure. Have secondary backup controllers which upon failure, which are used to control devices resuming functionality. This is accomplished through programming the BAS with event sequences triggered from alarms or flags noting the failure. Redundancy capabilities and feasibility are site specific. Ascertaining failure in boards, points, or devices is crucial to creating secondary measures to keep seamless processes going and resume with functions.   Error detection and correction with maintenance is often the best practice for preventing failure. Worn components are the leading cause of failure, followed by a lack of planning and consideration in the protection of electrical components through power surges or failures.   For the database, backups including automated backups for MSDE, SQL Express, and Full SQL are available. For further information on database backups and options, take a look at Microsoft SQL Management Studio. For Host Computer backups, look at adding a secondary computer which replicates the database and can capture transactions and messages should a failure with the primary host computer take place. Also work with the local IT department to keep machines up to date, safe, and clean of 3rd party applications which may interfere with integrity. Schneider Electric’s building management systems are designed such that building control continues even when controller to server communication is disrupted. The BMS server is home to a database of alarm and historical data, as well as system parameters and programs. When a server or its network connection fails, the collection of data from building controllers halts until the problem is resolved. For data critical applications, this solution provides an environment capable of preventing the data loss that results from these types of failures.  Although we do support its use with EcoStruxure Building Operation, Security Expert, Continuum, I/NET, Vista, Sigma, and I/A Series as a disaster recovery solution, we do not provide direct support for EverRun. Resolution For Open Mind High Availability Solutions guide please look at the following link; Open Mind High Availability Solution guide For everRun MX solution guide please look at the following link; everRun MX guide For ztC Edge solution guide please look at the following link; ztC Edge guide   

Issue During some circumstances, an additional license may be needed for testing/evaluation/demo purposes. Product Line TAC Vista Environment TAC Vista 5 Cause During some circumstances, an additional license may be needed for testing/evaluation/demo purposes. PSS is creating demo license files with a monthly validity. Resolution Monthly demo license files are made by the Malmö PSS team, and may be requested from PSS. The "TS_OK" demo file is used for "Remote Desktop" applications, giving access equivalent to the demo file available for download from the The Exchange Download Center, usually valid until the end of the month. Additionally, a OPC Server license file with the same validity is also available by request. Evaluation license for TAC Vista 5.1 Demo TS License TAC Vista 5.1   More information can be found in Where to find Evaluation license for TAC Vista and Struxureware Building Operation.

Issue Is it possible to upgrade Vista's log database directly from SQL 2000 to SQL 2008? Version 5.1.7 no longer supports SQL MSDE or SQL server 2000. Environment Upgrade to Vista 5.1.7 from a vista version running with SQL 2000. Cause Upgrading older Vista sites to run with Vista 5.1.7 (or future versions). Resolution The simple answer is yes, it is possible to upgrade from SQL server 2000 but SQL server 2000 SP4 needs to be installed first. Follow the link below to go to Microsoft's download site: SQL 2000 SP4 There are a number of considerations which are explained in the attached White Paper from Microsoft.

Issue SER8000 series room controllers communications options Environment SER8000 series room controllers Cause Integration to SER8000 room controllers via Modbus is required.  Resolution Currently, the SER8000 series room controllers communications options are Zigbee Pro or BACnet MS/TP. Refer to the SER8300 datasheet.  To communicate on Modbus RS-485, an option would be to use the multi purpose manager (MPM-UN) as a gateway device.    * Updated July 2015 As per Product Annoucement PA-00428, the SE8000 with firmware 1.3 can now act as a Modbus slave using the RS-485 port. 

Issue Getting error message: “Login Failed - Could not connect to fox server. Check that fox and web SSL settings match or try connecting using https.” when trying to connect to G3 station via a web browser. Product Line TAC IA Series Environment In Niagara G3, Version 3.7.106 Cause Security setting for the Web browser and Fox Service do not match, or the FOX or FOXS port is being blocked. In Niagara G3, Version 3.7 and later, users can set up SSL for both HTTP and FOX connections. The intention is that, when using the applet, SSL settings for HTTP and FOX must match (i.e. HTTPS/FOX or HTTP/FOXS are not allowed). In Niagara G3 3.7 update1 and earlier, users can connect to the applet using the invalid HTTPS/FOX combination. In addition, when loading the applet while using HTTP/FOXS, users are redirected back to the login screen with no error message. In NiagaraAX 3.7 update2 and later, users attempting to use the applet with an invalid HTTPS/FOX or HTTP/FOXS connection will be redirected to the login screen. An error message will appear indicating what went wrong. The Web and Fox settings do not match. They must be set to either HTTP/FOX or HTTPS/FOXS. We’ve found that there is a condition where the error message still displays even though both Fox Service and HTTP match. Reason being is during login to a station via web browser, a check is performed to determine if the Fox Service match the HTTP setting be used. If accessing via HTTP, then port 1911 (FOX) is checked. If accessing via HTTPS, then port 4911 (FOXS) is checked. We found that the corresponding, FOX or FOXS, port were not opened.  Resolution Open the needed FOX or FOXs port: Depending on if HTTP or HTTPS is used, the correct port must be opened for the corresponding FOX or FOXS connection. Port 1911 needs to be open if using HTTP/FOX connections, and if using HTTPS/FOXS, port 4911 needs to be open. Port need to be open to bidirectional TCP traffic.

Issue Instructions on how to download an .MOT file into a Xenta Programmable controller Product Line TAC Vista, EcoStruxure Building Operation Environment Xenta Programmable Controllers Xenta 280, 281, 282, 283, 300, 301, 302, 401, 401:B Download Wizard Cause To reinstall or upgrade the firmware of a Xenta programmable controller, a .MOT file must be loaded using the Download Wizard. Resolution Get the latest (or desired) .MOT version onto the PC's hard drive. Download the appropriate .MOT for the controller requiring new firmware. To find the version of firmware in a controller, see How to view the current firmware version on a Xenta controller using the RS-232 cable. Go to the The Exchange Download Center and view the MOT files Locate the proper version and controller combination in the asset title. Download the desired .MOT version   Download the .MOT file into the controller Start the Download Wizard. Note: The download wizard is installed when Menta or EcoStruxure Building Operation Workstation is installed on the machine. Start > Programs > Schneider Electric > TAC Tools X.X.X > Download Wizard (For versions prior to 5.1.4, the path will be "TAC" instead of "Schneider Electric.") Follow instructions on the Download Wizard. System Choose to Retain Current .MOT or Download new.  Typically the choice will be to download a new .MOT. Ensure the device type is correct and matches the controller and .MOT file. Browse to the .MOT file downloaded from the Buildings Business Extranet. Application Choose to Retain Current, Clear memory, or Download New.  Typically the choice will be to clear memory. This is referring to the Menta application inside the controller.  If the application is cleared, the controller will be "applicationless" and cannot be downloaded through the Vista System Plug-in.  Some Menta application will need to be loaded through a Menta direct download before the controller can function again in a network. If you choose to load a Menta application through the Download Wizard, browse to the desired .MTA file.  Configuration If the application is set to clear memory, the configuration section will be grayed out.  No selections are necessary. This refers to the network description files.  The typical selection if the option is available is to retain current. Press Apply Download status is shown in % finished.  Do not interrupt this process! When the dialog states that the download has completed, close Download Wizard.  Load a Menta application if necessary through Menta direct download. For more information on Menta Cable needed to download, see Schematic for the RS-232 cable used to direct download Menta applications and system files.

Issue Knowing the types of licenses, differences between each one, and the revisions supported by the license. Product Line TAC Vista Environment Vista 5.X Cause There are three different types of licensing for a Vista system. Resolution There are three types of TAC Vista software licenses. TAC Vista Demo License This type of license is for temporary use. It expires every thirty days. It is the full version license excluding OPC server licenses. The demo license is available on Schneider Electric buildings business extranet. (Products >TAC Vista > Vista Software > Evaluation License File). No activation required, ready to use after downloading. (Store the license file into C:\Program Files\Schneider Electric\License Files, by default.) Monthly demo licenses only work locally for the PC where they are installed.  You cannot use a License Server to serve up remote Workstation licenses to a remote PC, for example. For remote Workstation usage, please use the TS version of demo license instead. Demo licenses contain unlimited TAC Vista Webstation seats which allow multiple people log into Webstation simultaneously on the server PC and other computers.   TAC Vista Engineering Dongle This type of license is for Schneider Electric engineers or partners use. It comes with the full version license besides the OPC server licenses.  Please read Part number for Vista 5 engineering dongle for more purchasing information. No activation required, ready to use after receiving. Simply put the engineering dongle into one of the USB ports. You may be asked to install some software upon first time use. Note:  Insert the engineering dongle prior to starting the TAC Vista server. Engineering dongles only work locally for the PC where they are plugged in.  You cannot use a License Server to serve up remote Workstation licenses to a remote PC, for example. Engineering dongles contain only one (1) TAC Vista Webstation seat. In addition, user can log into Webstation only on the sever PC.   TAC Vista Customer License This type of license is for end user use. Depending on the customer needs, different features of Vista software can be purchased standalone or in packages. For more information about each software feature or packages, please read the Vista 5 Software license packages and Vista 5 product catalog. Customer licenses are restricted to the minor revision of the Vista software or lower. A Vista 5.0 license will not function on a Vista 5.1 installation. However a Vista 5.1 license will work for all 5.1.x installations as well as all 5.0.x installations. Maintenance agreements ( XXXX 1 year licenses) are available for most TAC Vista 5.1 software modules. An active maintenance agreement ensures that the license has access to any new, minor and major, versions. Maintenance agreements are automatically renewed at the end of each 12 month period. The termination notice is three months. Minimum agreement time is three years. Activation of the license is required. You can generate the license on the https://schneider-electric.flexnetoperations.com website with the entitlement ID received via email after purchasing. The license needs to be locked to: Computer MAC address If you lock the license to a computer's MAC address, the license needs to be stored on this particular computer (C:\Program Files\Schneider Electric\License Files, by default), and it can only be used on this computer.   An onsite dongle (end-user dongle) The dongle needs to be purchased separately (name: Vista 5 Hardware Dongle, part number: 000857510 on the iPortal).  If you lock the license to the onsite dongle, you can use TAC Vista software on any computer as long as this dongle is plugged in. You can re-host the license to another MAC address or onsite dongle up to 4 times in a 1 year period. If you exceed this re-hosting limit you will need to contact Product Support with a valid reason why this occurred, and the limit can be reset. For additional customer licensing information please read TAC Licenses Installation Manual and TAC Vista 5.0 to 5.1.7 license does not work after installation for how to use LMTOOLS to manually read site license.

Issue Drayton Theta Autotherm Controller requires replacement. Environment Stand alone discreet Drayton Theta Autotherm Controller applications. Cause Obsolescence of Drayton Theta Autotherm Controller. Resolution A.  Controller - Overview The Drayton Theta Autotherm Controller was manufactured primarily for use in domestic heating applications. The Drayton Theta Autotherm Controller combined the following functions in a single stand alone discreet Controller :- Heating System Compensator HWS Programmer.  There is no simple like for like replacement currently available but the two functions may be replicated as shown below. B.  Controller - Replacement 1.  Suggested replacements for Autotherm Heating System Compensator function and associated Sensors :-  Compensator Controller = CSC5252 or CSC5352, details of which may be viewed here. (The CSC5352 may be programmed to provide automatic Night Set Back) Outside Air Temperature Sensor = STO600, details of which may be viewed here. Clamp-On Temperature Sensor = STC600, details of which may be viewed here. (Use of a Clamp-On Temperature Sensor eliminates the need for any pipework modifications) N.B. The existing Drayton Theta Autotherm Heating System Actuator and Valve Body may be retained should these both be in working order. Alternatively, suggested replacements for the Drayton Theta Autotherm Heating System Actuator and Valve Body are :- Actuator = MD10B-24 or MD10B-230, details of which may be viewed here. Linkage Kit = LMD/AR-MB (914-1071-000), details of which may be viewed here. Valve Body = MB (select size from ½” to 2” size), details of which may be viewed here. 2.  Suggested replacement for Drayton Theta Autotherm HWS (Hot Water Service) Programmer function :- We do not offer an independent Programmer but such a product should be available from the Distributor supplying the S-E Satchwell CSC Compensator Controller and associated Temperature Sensors.  N.B. Any existing Relays that are currently installed may also be retained, in order to complete the replication of the Drayton Theta Autotherm control scheme.

Issue Satchwell CD2201 Compensator Controller–Actuator requires replacement. Environment Stand alone discreet Satchwell CD2201 Compensator Controller–Actuator Cause Obsolescence of Satchwell CD2201 Compensator Controller–Actuator Resolution Replace Satchwell CD2201 Compensator Controller–Actuator with Schneider Electric Satchwell CSC Compensator Controller, compatible Temperature Sensors and MD Series Actuator and Linkage Kit. Replace Satchwell CD2201 Compensator Controller–Actuator with Schneider Electric Satchwell CSC Compensator Controller. N.B. Two models of the Schneider Electric Satchwell CSC Compensator Controller are available :- CSC 5252 Compensator Controller without Time Clock CSC 5352 Compensator Controller with integral Time Clock  Details of the Schneider Electric Satchwell CSC Compensator Controllers may be viewed here. It should be noted however that the CD2201 Compensator Controller–Actuator had no integral Time Clock. Replacement of Air Temperature Sensors It should be noted that the existing Satchwell Outside Air Temperature Sensor associated with the CD2201 Compensator Controller–Actuator is obsolete and should be replaced. Similarly, it should be noted that the existing Satchwell Inside Air Temperature Sensor associated with the CD2201 Compensator Controller–Actuator is obsolete and should be replaced. Details of replacement Schneider Electric STO600 Outside Air Temperature Sensor may be viewed here. Details of replacement Schneider Electric STR600 series Inside Air Temperature Sensor may be viewed here. N.B. It should be noted that the CSC Compensator Controller will perform entirely satisfactorily without the connection of an Inside Air Temperature Sensor. Replacement of Water Temperature Sensor. It should be noted that the existing integral Satchwell Water Temperature Sensor associated with the CD2201 Compensator Controller – Actuator cannot be re-used and should therefore be replaced. In order to minimise mechanical work it is suggested that a Surface Mounting Temperature Sensor is installed on the pipework, rather than an Immersion Temperature Sensor installed in a Pocket in the pipework. Details of replacement Schneider Electric STC600 Surface Temperature Sensor may be viewed here. Replacement of Actuator. Whilst the existing Satchwell MB Valve Body may be retained, a new Schneider Electric Actuator and Linkage Kit will need to be installed on the MB Valve Body in order to permit control from the CSC Compensator Controller. Details of the Schneider Electric MD10B Actuator may be viewed here. Details of the Schneider Electric LMD/AR-MB Linkage Kit may be viewed here. Please be aware: since July 2016 the CSC compensator and other descrete controllers were withdrawn from service. To see "PA-00479 - Discrete Controllers - Notice of Withdrawal - Satchwell" click here.

Issue What is the factory default IP address for a new I/A Series G3 JACE-6 or JACE-7? Product Line TAC IA Series Environment I/A Series G3 JACE-6 JACE-7 Cause Initial power up and connection to Workbench Resolution Two female 10/100-Mbit Ethernet connections are provided on the JACE-6 and JACE-7 hardware platforms. These are RJ-45 connectors labeled LAN2 and LAN1. Use a standard Ethernet patch cable for connecting to a hub or Ethernet switch. An activity LED for each Ethernet port is visible, and are labeled "LAN2" and "LAN1" on the cover. The factory-default IP address for LAN1 on the JACE-6 and JACE-7 is 192.168.1.12n, where the last numeral n in the address matches the last digit of the JACE's serial number, and subnet mask is 255.255.255.0. By default, LAN2 on the JACE-6 and JACE-7 is disabled. The factory default platform username and password is tridium / niagara.

Issue The ability and procedure to identify the version of Sigma software on a system. Product Line Satchwell Sigma Environment Release number: 1, 2, 3, 3.1, 3.3, 3.4, 3.6, 3.7, 3.7 SP2, 3.7 SP3, 3.10, 3.11, 4.00, 4.00 SP2, 4.00 SP4, 4.01, 4.01 SP1, 4.01 SP3, 4.01 SP4, 4.01 SP4a, 4.01 SP5, 4.02, 4.03, 4.03 SP1, 4.04, 4.04 SP1, 4.04 SP2, 4.04 SP3, 4.05, 4.05 SP1, 4.05 SP2, 4.05 SEB, 4.06, 4.07, 4.07 SP1, 4.07 SP2, 4.08 Build number: 1.52, 2.13, 3.12, 3.17, 3.3, 3.31.1, 3.32.10, 3.33.9, 3.33.11, 3.33.13, 3.34.11, 3.34.11, 3.36.11, 3.36.16, 3.36.20, 3.37.08, 3.37.09, 3.37.12, 3.37.13, 3.37.16, 3.37.18, 3.39.09, 3.40.06, 3.40.09, 3.41.14, 3.41.15, 3.41.16, 3.41.18, 3.41.19, 3.42.34, 3.42.43, 3.42.48, 3.43.18, 3.44.14, 3.44.16, 3.44.18, 3 45 48, 3 45 51, 3 45 58, 3.46.57, 3.46.62, 3.46.70, 3.46.72, 3.46.73, 3.46.79, 3.46.80 3.46.81, 3.46.85, 3.46.86, 3.46.89, 3.46.98, 3.46.104, 3.46.105, 3.46.107, 3.46.108, 3.46.110, 3.46.111 Cause Software installed is identified with a build number and not a release number. Resolution To view the Sigma build number, using a Sigma client running locally on the Sigma server, select About System Manager from the Help menu. The displayed window shows the Sigma release and build number Refer to the table below to find the Release No. Sigma Release No. Build No. Software/Firmware File Date   SigmaX   Release 1 1.52 Software/Firmware 22.06.2001 SigmaX 4.5 Release 2 2.13 Software/Firmware 14.02.2002 SigmaX 5.2 Release 2 3.12 Supplement 14.02.2002 SigmaX 5.2 Release 3 3.12 Software 31.07.2002 SigmaX 5.2 Release 3.1 3.17 Software 17.09.2002 SigmaX 5.2 Release 3.3 3.3 Software 30.07.2003 SigmaX 5.2 Release 3.4 3.31.1 Software 03.10.2003 SigmaX 5.2 Release 3.6 3.32.10 Software 19.11.2003 SigmaX 5.2 Release 3.7 3.33.9 Software 22.12.2003 SigmaX 5.2 Release 3.7 SP2 3.33.11 Software 27.01.2004 SigmaX 5.2 Release 3.7 SP3 3.33.13 Software 19.02.2004 SigmaX 5.2 Release 3.10 3.34.11 Software 21.04.2004 SigmaX 5.2 Release 3.11 3.34.11 Supplement 31.08.2004 SigmaX 5.2 Release 4.00 3.36.11 Software 16.12.2005 SigmaX 6.0.1 Release 4.00 SP2 3.36.16 Software 02 03 2006 SigmaX 6.0.1 Release 4.00 SP4 3.36.20 Software 23.05.2006 SigmaX 6.0.1 Release 4.01 3.37.08 Software 07.09.2006 SigmaX 6.0.1 Release 4.01 SP1 3.37.09 Software 26 09 2006 SigmaX 6.0.1 Release 4.01 SP3 3.37.12 Software 20 10 2006 SigmaX 6.0.1 Release 4.01 SP4 3.37.13 Software 13 08 2006 SigmaX 6.0.1 Release 4.01 SP4a 3.37.16 Software 17 11 2006 SigmaX 6.0.1 Release 4.01 SP5 3.37.18 Software 05 01 2007 SigmaX 6.0.1 Release 4.02 3.39.09 Software 26 01 2007 SigmaX 6.0.1 Release 4.03 3.40.06 Software 06 06 2007 SigmaX 6.0.1 Release 4.03 Sp1 3.40.09 Software 09 08 2007 SigmaX 6.0.1 Release 4.04 3.41.14 Software 27.02.2008 SigmaX 6.0.1 Release 4.04 SP1 3.41.15 Software 09.05.2008 SigmaX 6.0.1 Release 4.04 SP2 3.41.16 Software 15 09 2008 SigmaX 6.0.1 Release 4.04 SP3 3.41.18 Software 08 01 2009 SigmaX 6.0.1 Release 4.04 SP4 3.41.19 Software 08 01 2009 SigmaX 6.0.1 Release 4.05 3.42.34 Software 06 11 2009 SigmaX 6.0.1 Release 4.05 SP1 3.42.43 Software 22 03 2010 SigmaX 6.0.2 Release 4.05 SP2 3.42.48 Software 26.08.2010 SigmaX 6.0.2 Release 4.05 SEB 3.43.18 Software 08 12 2010 SigmaX 6.0.2 Release 4.06 3.44.14 Software 01 12 2011 SigmaX 6.0.2 Release 4.06 SP1 3.44.16 Software 01 12 2011 SigmaX 6.0.2 Release 4.06 SP1 3.44.18 Hotfix 01 02 2012 SigmaX 6.0.2 Release 4.07 3 45 48 Software 20 08 2012 SigmaX 7.0.6 Release 4.07 SP1 3 45 51 Service Pack 09 12 2012 SigmaX 7.0.6 Release 4.07 SP2 3 45 58 Service Pack 20 12 2013 SigmaX 7.0.6 Release 4.08 3.46.57 Software 10 04 2014 SigmaX 7.0.7 Release 4.08 3.46.62 Hotfix 21.05.2014 SigmaX 7.0.7 Release 4.08 3.46.70 Hotfix 23 07 2014 SigmaX 7.0.7 Release 4.08 3.46.72 Hotfix 04 08 2014 SigmaX 7.0.7 Release 4.08 3.46.73 Hotfix 12 08 2014 SigmaX 7.0.7 Release 4.08 3.46.79 Hotfix 08 10 2014 SigmaX 7.0.7 Release 4.08 (**1) 3.46.80 Software 10 04 2014 SigmaX 7.0.7 Release 4.08 3.46.81 Hotfix 17 02 2015 SigmaX 7.0.7 Release 4.08 3.46.85 Hotfix 19 03 2015 SigmaX 7.0.7 Release 4.08 3.46.86 Hotfix 19 03 2015 SigmaX 7.0.7 Release 4.08 (**2) 3.46.89 Software 10 04 2014 SigmaX 7.0.7 Release 4.08 3.46.98 Hotfix 14 12 2016 SigmaX 7.0.7 Release 4.08 (**3) 3.46.104 Software 28 02 2017 SigmaX 7.0.9 Release 4.08 3.46.105 Hotfix 10 03 2017 SigmaX 7.0.9 Release 4.08 (**4) 3.46.106 Software 28 03 2017 SigmaX 7.0.9 Release 4.08 3.46.107 Hotfix 08 08 2017 SigmaX 7.0.9 Release 4.08 3.46.108 Hotfix 01 05 2018 SigmaX 7.0.9 Release 4.08 (**5) 3.46.110 Software 13 05 2019 SigmaX 7.0.9 Release 4.08 (**6) 3.46.111 Hotfix 15 11 2019 SigmaX 7.0.9 Release 4.08 (**7) 3.46.131 Software 29 01 2020 SigmaX 7.0.9 Notes:   **1 Sigma build 4.46.57 with StruxureWare Building Operation v1.5 or 1.6 transition support program installed. **2 Sigma build 4.46.57 with StruxureWare Building Operation v1.8 transition support program installed. **3 Sigma build 4.46.57 with StruxureWare Building Operation v1.9 transition support program installed. **4 Sigma build 3.46.57 with StruxureWare Building Operation v2.01 transition support program installed. **5 Sigma build 3.46.57 with StruxureWare Building Operation v3.0.1, v3.0.2 and v3.0.3 transition support program installed.. **6 Sigma build 3.46.57 with StruxureWare Building Operation v3.0.4, v3.1 and v3.2 transition support program installed. **7 Sigma build 3.46.57 with StruxureWare Building Operation v3.2 or later transition support program installed.   Notes: 1. SigmaX version 7.0.9 is now available and can be used on any Sigma version that supported SigmaX version 7.0.6. 2. This information can be downloaded as a PDF file: Sigma Build Numbers 2023 3. When SigmaX 6.0.2 is installed, the build information provided by Sigma (Help > About) can be wrong (later than the actual version). This arises because SigmaX installs a file with Build 3.42.47 in the c:\sigma\bin folder. This is only a problem prior to Sigma Release 4.05 SEB.

Issue "Communication failure due to routing device not available" errors when trying to view BACnet controllers or the objects they contain. Product Line Andover Continuum Environment Continuum v1.74 and above. Cause The Cyberstation is unable to route to the desired device(s). This can occur due to changes in the network, network settings, or blocking software on the PC.  Resolution Check that the IP settings of all devices are configured so they can see each other. Specifically that the subnet mask configured for each device allows them to be seen on the same logical network. Also see the following articles: Communication failure due to routing device not available Eaton IP BACnet Lighting Panels go offline with error "Communications failure due to routing device not available" Simple BBMD setup

Warning Potential for Data Loss: The steps detailed in the resolution of this article may result in a loss of critical data if not performed properly. Before beginning these steps, make sure all important data is backed up in the event of data loss. If you are unsure or unfamiliar with any complex steps detailed in this article, please contact Product Support for assistance. Issue During the installation of PCT 2 and 'Starting VM pct' step, one encounters the error: "Error: System.InvalidOperationException: Failed to run: Start-Vm -Name pct". Open Hyper-V Manager and confirm the 'pct' VM was created. Manually trying to start produces this error: Product Line EcoStruxure Building Operation Environment Project Configuration Tool 2.0 Cause Hyper-V is not set to start on boot automatically. Resolution DO NOT perform these instructions if PCT 1 is installed on the same OS. Contact Product Support for assistance. Launch Command Prompt as Administrator. Type: bcdedit /enum​  Ensure 'Hypervisorlaunchtype' is not 'Off' and set to 'Auto' by running the following command: bcdedit /set hypervisorlaunchtype auto​ Reboot the PC Rerun PCT 2 installer

Issue Using the Function Block Program Macro Library Product Line EcoStruxure Building Operation Environment Building Operation Workstation Cause The need for program examples on creating Function Block Programs Resolution To assist with creating Function Block Programs, the EBO Function Block Program Macro Block Library is included in the EBO Workstation installation. Here's how you can leverage the Macro Library: Access the Macro Library: Open the EBO Workstation. Navigate to the Function Block Program section. Locate and access the Macro Library. Incorporate the Macro Library: Once inside the Macro Library, explore the various pre-built Function Block Program macros available. Select the desired macro that aligns with the specific function you intend to program. Integrate the selected macro into your Function Block Program to enhance its functionality. Learn by example: The Macro Library also serves as an excellent resource for learning and understanding how to program specific functions. Study the structure and logic of the included macros to gain insights into effective programming practices. Utilize the examples as a starting point to develop your own customized Function Block Programs. The EBO Function Block Program Macro Block Library is designed to simplify and accelerate your programming tasks within EcoStruxure Building Operation. Leverage the library's resources and example programs to enhance your programming skills and efficiency.  

Issue Requirements / specifications on cables used in a LonWorks network Environment LonWorks Cable Wire Guide LonMark Cause There are special requirements on cables used for LonWorks networks between Lon devices. Resolution LonMark organisation is recommending cables according to their specification. An example of this is the Belden LonWorks cable guide. Also, Echelon has a Wiring Guideline and Users Guide.

Issue Cannot open the FlexNet License Admin, the TAC license server is not running as a service, or the vendor daemon is down. Product Line TAC Vista Environment Vista LMAdmin FlexNet License Administrator Cause If the TAC Vista Server installation option "Use the local TAC License Server" is not selected during installation, the license server will be installed but not successfully configured. When the license server is not running it will prevent the LMAdmin web interface from launching. If the license file is not in the correct location when the license server is started, then the vendor daemon must be started manually. For general information on the new license system, see LMTools Licensing Administrator program is replaced with LMAdmin in Vista 5.1.8 or greater. Resolution Remember that a valid and un-modified License File is necessary for the following troubleshooting steps to work. If the License file was manually manipulated in any way, please revert to a File specifically licensed for the machine where the License Server resides. Before proceeding, make sure the setup of the license system is made correctly following No license after reboot when TAC Vista Server (TACOS) runs as a service Check out this video about the new Vista 5 licensing system on the Community website. Check out the TAC License Server Setting tool below for the new license system. Click here to download the zip file.       Could not reliably determine the server's fully qualified domain name This is a bug in the lmadmin.exe file. Either replace the lmadmin.exe file with the newest available or install the newest version of the license system available. You can have a newer version of the license system installed than the TAC Vista version installed. E.g. TAC Vista 5.1.8 will work together with a license server version 5.1.9 Cannot Open the Flexnet License Admin Ensure that the TACLicenseServer is running as a service. Right Click on the Computer icon on the desktop and click on manage. In the system tree on the left, go to Services and Applications > Services. Scroll down and select TACLicenseServer. Click Start in the top left corner of the window. Make sure that the site license is the only file in the license server path. If there is a demo license in the file path when trying to start the license server, it will fail to start. Sometimes you will get the following Windows error. Error 1067: The process terminated unexpectedly. Note: TAC License Server with spaces is not the correct license server. If TACLicenseServer is not found in the list then move on to the next troubleshooting section titled "Setting up the TAC License Server as a Service".   If the TAC License Server will not start then it may be due to another program using the 8080 TCP port. Use TCPView to search for programs running on local port 8080 and either stop this program or use the TACLicenseServer Settings tool at the top of this page to change the port that the TAC License Server uses. If the TACLicenseServer still does not run then continue to the next section below, Setting up the TAC License Server as a Service.    Setting up the TAC License Server as a Service LMAdmin.exe must be registered as a service. When first installing Vista the option "Use the local TAC License Server" should be selected. When this option is selected it will install the license server, register it as a service and start it. When "Use a license file" is selected it will only install the license server without configuring its settings. This can be corrected by reinstalling Vista and making the proper selection or by a manual configuration procedure. The manual procedure steps are listed below. Note: The option "Use a license file" only applies to a demo license, not a site license file. Manual Procedure to Register the License Server as a Service Start a command prompt as an administrator. To do this go to Start > All Programs >  Accessories and right-click on Command Prompt, then select Run as Administrator. In the command prompt go to path C:\Program Files\Schneider Electric\License Server\ (This can be done by entering "cd" and then the directory path listed here.) For 64-bit OS go to "C:\Program Files (x86)\Schneider Electric\License Server\" Run the command: "LMAdmin.exe -InstallService TACLicenseServer".   Manually copy the license files that are to be used to the new license file folder location. 32 bit - C:\Program Files\Schneider Electric\License Server\taclic\licenses 64 bit - C:\Program Files (x86)\Schneider Electric\License Server\taclic\licenses   In the command prompt type, the following command to start the license server "net start TACLicenseServer". Note: If the license files are not copied prior to starting the license server, the vendor daemon will not be started successfully and must be manually started after the license files have been copied to the new license file location. For instruction on how to do this, follow the steps in the next section Vendor Daemon is Down When the license server is installed but not configured, as mentioned above, the TAC Vista Server installer will not create a shortcut to the license administration tool in the start menu; since the shortcut will not work. A shortcut is created in the installation folder and can be used to create a shortcut in the start menu manually. The shortcut can be found here "C:\Program Files\Schneider Electric\License Server\FlexNetLicenseAdmin". For 64-bit OS the shortcut is found in "C:\Program Files (x86)\Schneider Electric\License Server". Vendor Daemon is Down   Note: If working on a 64 bit PC, replace "Program Files" with "Program Files (x86)" in the file paths below. Go to All Programs > Schneider Electric > TAC Tool 5.X.X > Flexnet License Admin. Click on Administration in the top right corner of the screen and login with admin/admin (If logging in for the first time it will prompt you to change the password). Click on the Vendor Daemon Configuration tab and then select the taclic daemon. Verify that the path in the License File or Directory field matches the location of the site license. The first half of the file path is C:\Program Files\Schneider Electric\License Server\ followed by what is in the License File or Directory field. Verify that the taclic.exe is located in the path found in the Vendor Daemon Location field. The first half of the file path is C:\Program Files\Schneider Electric\License Server\ followed by what is in the Vendor Daemon Location field. If changes were made then click Save and then Start. If the Vendor Daemon still does not start after checking the file paths, verify that the site license has been hosted to the correct MAC address. For help finding the MAC address, see How to locate a computer's MAC address. NOTE: Also make sure there are no other Flexnet License Servers installed on this same machine (SmartStruxure, Power Manager, etc). If there is another license server running on the same machine then this can cause a conflict. SmartStruxure license and TAC Vista license on the same PC can walk you through merging them together. If IPV6 is enabled, you may need to disable it and reboot the machine. Switching from a site license to a demo license Log into LMadmin and stop the license server Save the Demo License file in C:/Program Files/Schneider Electric/License Server/Licenses Open the desired engineering tool and point Vista to the Demo file When finished, log into LMAdmin and start the License Server.  This will tell Vista to continue using the site license. A site that has worked with the installation from a remote desktop or the different user logged in Open task manager Check for process "lmgrd" of 2 of them are running the FlexNet server might try to read from the wrong server. Shutdown down both processes and restart the FlexNet server Log in to FlexNet admin and start the vendor Reread the license file Also, check License Administrator error "EXITING DUE TO SIGNAL 28 Exit reason 5"

Issue When running VisiSat 2.1 build 196 (200 or 201) a message is displayed - “Unable to Load the Schneider Electric CET Style DLL” and VisiSat fails to launch. Product Line Satchwell MicroNet Environment Windows (Windows, XP Professional, Windows 7, Windows Vista Ultimate) Microsoft Visio Cause .NET Framework 2.0 is not installed. Resolution Check that the version of VisiSat installed is either v2.1 196 or for SP1 build 200 or for SP2 build 201 on a computer running with a supported operating system and Microsoft’s Visio version.   MicroNet Software Datasheet   The suggested procedure to correct the “Unable to Load the Schneider Electric CET Style DLL” issue as follows: - Uninstall VisiSat Install .NET Framework 2.0 Install VisiSat 2.1 196, add service packs 1 and 2 files as required. Re-boot computer Run VisiSat. Links to VisiSat software and information:   The VisiSat main software can be downloaded from the link below: https://ecoxpert.se.com/search?documentUUID=c93346a7-9d82-48e7-9b54-a866ac75bb71&title=VisiSat%202.1%20Build%20196%20-%20Software   VisiSat service pack 1 can be downloaded from the link below: https://ecoxpert.se.com/search?documentUUID=fd2e9849-1ffe-4c10-b3a6-5f27bac91870&title=VisiSat%20Release%202.1.196%20Service%20Pack%201%20(2.1.200)%20-%20Software   VisiSat service pack 2 can be downloaded from the link below: https://ecoxpert.se.com/search?documentUUID=839c09d2-400d-4434-8b1e-97f339545034&title=VisiSat%20Release%202.1.196%20Service%20Pack%202%20(2.1.201)%20-%20Software   VisiSat documentation can be downloaded from the link below: https://community.se.com/t5/Building-Automation-Knowledge/Download-latest-VisiSat-Data-Sheets-Engineering-Guides/ta-p/6110