Building Automation Knowledge Base

Issue Which SQL query can be used to identify the database layout being used? Environment Vista 5.1.X log database Cause With the release of Vista 5.1.7 came a new logdatabase layout which is designed to improve performance especially in the area of trend and event log management. This means that there are now 2 possible logdatabase configurations. It can be important to know which version is being used before running any queries or accessing the external log data with external tools. Resolution The following query will return the database layout version when run in SQL management studio: select taclogdata.dbo.DSS_SchemaVersion() More information can be found in the Vista 5.1.7 release notes.

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 When trying to open a report, you get an error message like below: Msg=DDL creation failed ex=Error creating DropDownddlTopCount The request failed with HTTP status 503: Service Unavailable Ex=ButtonRunReport The request failed with HTTP status 503: Service Unavailable   Product Line EcoStruxure Building Operation Environment Reports server Cause Cause 1: The Report Server Service is not started To check if this is the cause, open the report manager. If you get the error below, continue to resolution 1.   Cause 2: The Report Server Service takes too long to generate the report and thus times out The root cause should also be investigated. It can be a slow network connection, fragmented SQL database, antivirus software or memory limitation that is slowing the request to compile a report down. Resolution Resolution 1 Open "Reporting Services Configuration Manager" Start the server   Resolution 2 Increase the timeout for the report service Open Report Manager Click "Site Settings" Change the Report Timeout. Default is 1800 which is 30 seconds.   Check that the memory usage for the SQL server is not limited (Microsoft's How to: Set a Fixed Amount of Memory (SQL Server Management Studio)) Open SQL Management Studio Open the properties for the SQL Server Click "Memory" and check that the value is default (2147483647)   Reindex and defragment the SQL database e.g. using SBO Reports Agent Config.

Issue Getting javax.baja.xml.XException: Error parsing value error message when attempting to add a new driver network to the I/A Series G3 station's Drivers container. Drag and Drop - drag network container from palette and drop onto the Drivers container Copy and Paste - copy network container from palette and paste into the Drivers container Drivers Manager (New selection) - wizard to add new driver Error details displayed:  com.tridium.fox.session.ServerException: javax.baja.xml.XException: Error parsing value [38:4] Environment Enterprise Network Server, ENS, ENC, JACE Cause The module associated with the driver has not been installed in the local modules folder or remote station. Resolution Enterprise Network Server Stop Workbench Copy the missing module directly into ~\modules directory for the version of I/A Series G3 being used. Restart Workbench ENC or JACE Open the platform for the ENC/JACE Install the module using the Software Manager. A station reboot may be required.

Issue The functionality of the different tools and/or software does not operate as expected. Issues can appear related to controller functionality or possibly issues with how the standard programs work.  Product Line EcoStruxure Building Operation Environment Automated Engineering Tool (AET) Project Configuration Tool (PCT) EcoStruxure Building Operation (EBO) Cause When the latest versions of software and firmware are not being used, previously identified issues can cause problems with downloads or the operation of controllers. In other situations, it is possible that the proper steps or tools are not being used correctly. This could require further instruction and information.  Resolution In most situations, the troubleshooting steps below will address a majority of issues encountered while working with the AET and the standard applications. EBO software and SmartX firmware being used should be at the latest version Between updates and fixes to the software/firmware, you should be using the latest versions found on the Exchange.  AET software should be up to date Between updates and fixes, make sure you are using the latest version of the AET software which can be found on the Exchange.  AET templates should be up to date You can reference the AET Quick Help - Downloading AET Templates video or the SmartVAV: Software Engineering Process document for further direction.  Understanding the proper way to use the Automated Engineering Tool There exist a number of AET Quick Help Videos available on the Community to help with AET user skills. If there are any topics not covered in a video that you are searching for, be sure to leave a post with the new video idea.

Issue Procedures and processes to secure I/A Series Niagara 4 Systems Product Line TAC IA Series Environment  I/A Series Niagara 4 Systems Cause Users accessing system without permission Potential damage done by malicious entry to the system Resolution The attached document describes how to implement security best practices in an I/A Series Niagara 4 system.  While it is impossible to make any system completely impenetrable, there are many ways to build up a system that is more resistant to attacks. In particular, this document describes how you can help make an I/A Series Niagara 4 system more secure by carefully configuring and using: Passwords System Passphrase Platform Account Management Station Account Management Role and Permission Management Authentication TLS and Certificate Management Module Installation Additional Settings External Factors Please note that while all of these steps should be taken to protect your I/A Series Niagara 4 system, they do not constitute a magic formula. Many factors affecting security and vulnerabilities in one area can affect security in another; it doesn’t mean much to configure a system expertly if your JACE is left physically unsecured where anyone can access it. Note: Schneider Electric strongly recommends upgrading to the latest I/A Series N4 version maintenance build that implements numerous security updates.  Before updating any system, make sure to review the build-included documentation to understand the behavioral impacts of the security enhancements and JACE hardware platforms supported. Download the Niagara 4 Hardening Guide_2023 for more details.

Issue Downloads to the Controller are failing. When reviewing the Download Server Diagnostic Window, numerous Failed to load DAT file error messages are seen. Failed to load DAT file. Path='C:\ProgramData\Schneider Electric\SecurityExpert\Download\5.dat". Error code = 80070002 ***** Invalid Controller (5) version 0 Product Line EcoStruxure Security Expert Environment Security Expert SP-C Cause The Firmware version in the Controller is not compatible with the version of Security Expert being used. Resolution Upgrade the Firmware in the Controller to the latest Firmware build. From the main menu, select Sites | Controllers. Right click on a controller, and select Update Firmware. Click the [...] button and browse to the supplied firmware (.bin) file. Choose which controller(s) to update by selecting the Include option. Only the selected controller(s) will be updated. Click Update to commence the firmware update procedure. The update can take up to 10 minutes per controller to complete. Once complete, the controller is automatically restarted and normal operation resumed.

Issue How to properly configure Time Zone and UTC Offset settings in Cyberstations and controllers. Product Line Andover Continuum Environment Continuum Cyberstation Continuum Controllers Cause There are a number of locations for time configuration settings, creating uncertainty as to what needs to be set, and where, to maintain the correct time in all devices. Resolution How to sync controller time with WS time with Server time. Set the correct UTC offset (time zone) in all of the below locations: Confirm Cyberstation(s) PC time zone (UTC offset) and regional settings are correct. [This has no effect on time synchronization but does have an effect on what time alarms and events are written to the database as well as when alarms will be delivered to Cyberstations] Confirm the SQL Server PC time zone (GMT settings) and regional settings are correct. [same as 1 above] In Continuum, the Workstations Device object's Time tab has the correct time zone setting (be aware this is in minutes, ex. GMT+10 = +600 minutes.) In Continuum, the Network folder has a setting for the time zone, this needs to be configured to the time zone the controllers are located. If GMT+10 then this gets set to +600. Note1: To synchronize controller time to Workstations time a program needs to be created in one WS that sets the Date object of the Netcontroller (IP level controller) with the lowest ACCnet ID. This controller will then push any time changes out to all other IP level controllers and down to its subnet controllers (i2’s or b3’s). See Time sync controllers to workstations for details on this. Note2: At 38 minutes past the hour the Netcontroller will push its time down to its subnet (aka Field Bus) controllers. Note3: When time is set in the Netcontroller with a reload of the controller, the UTC settings of the WS doing the reload, and the Network folder the controller is in, are accounted for and the controllers time is set with these UTC settings taken into account. When time is set with a PE program using the WS Date object, this does not take into account the UTC settings of the various locations and just sets the controller Date object to the exact value of the WS Date object. If the controller is in a different time zone than the WS setting its time, then it will now have the wrong time in it. To compensate for this, it is suggested that time offsets must be added to the Time Sync program to accommodate those networks in a different time zone than the WS. Other UTC setting locations and what these settings effect IP level BACnet Device UTC Offset The UTC offset value on the Time tab of the BACnet Device object is only used when the BACnet time synchronization method is being used to set time. This setting then follows the BACnet specification where it needs to be the negative value of the GMT setting. For example, if the BACnet device is in the GMT+10 time zone, then set this offset to -(10*60) = -600. Note4: If using the PE program method, the UTC offset value on the Time tab of the BACnet Device object does not change how time is set in the controllers. However, if the UTC offset value on the Time tab of the BACnet Device object is changed, it will change the current time of the controller to coincide with the new time zone until the time is set again in the controller, or the UTC offset value is removed. UTC offset in controller configuration Time Settings webpage This doesn’t change how the time of the controller is set. It is used to set the time of sent email messages when using the SMTP option on this controller.

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 Web Service addition Script Web Service Product Line EcoStruxure Building Operation Environment StruxureWare Building Operation site with release 1.2 or later Cause What are Web Services and how to add to my existing StruxureWare Building Operation site. How to add Script Web Service files and how to add to a project or site How to create values from Script Web Service Files How to add values to graphic that uses the values from Script Web Service Resolution Wikipedia: A Web Service is a method of communication between two electronic devices over the web (internet). W3C: A "Web Service" as "a software system designed to support interoperable machine-to-machine interaction over a network." Web Services: 1. are hardware, programming language, and operating system independent 2. Applications written in different programming languages and running on different platforms can seamlessly exchange data over intranet or the internet using Web Services 3. Web Service interfaces are supported in both the AS and ES 4. Like BACnet, Lon, and Modbus, you can create a Web Service interface.      EWS Interface - EcoStruxure Web Services      Script Web Service - Generic Consume via Script      Simple XML Web Service - Rest Generic Consume via Binding Tool (Web Service addition Simple XML Web Service)      SOAP Web Service - SOAP Generic Consume via Binding Tool (Web Service addition SOAP Web Service) This article explains adding Sunrise and Sunset for a particular location data using Script Web Service: -Select New...Interface...Web Service...Script Web Service This first example is for a Calculation program for Results=A+B -Enter the WSDL Service and Endpoint are auto-filled Not necessarily all the time IP Cameras -Script Web Services Interface: -Script Programs can bind to the web service with the "Webservice" declaration. -When the name bound service is typed and a "." is put after it, intellisense drop down will show the available methods WSDL file is brought into the database Drop down methods become available even if the URL of the WSDL is not -The web service capabilities can be used within the code for manipulation, data gathering, or whatever else. -Script Web Services Post and Gets -Script programs can send requests directly to a web service with the SendWebRequest keyword. -The syntax requires 5 specific arguments BaseURL - URL that will be processing the message Method - Method of processing the POST and GET (dictated by URL) Headers - Defines certain parameters that are meaningful to the URL (IsMobileApp:True;IsAndroidClient:True) Content-Type - Defined by the URL Message - What is actually being sent to the URL -Script Web Services - Considerations -Bindings to a web service require a recompile -Display of captured information will get localized   Next, Create a Script Program for Calculations Here is a simple script program which defines the calc and values The below shot is the values A=12, B=3, and the Results of the calculation. Below are the binding for the Script Calc program to the Values The below shot is the binding of the Calc program to the Script Web Service The results are a calculation in which we supply value A and B and the Script Web Service performs the calculation with results of 15.   We can change the value of A to from 12 to a value of 13 which Results in 16 as shown in the shot below.

Issue Types of TAC Erie Pop Top valves and actuators available from Schneider Electric in the UK  Product Line Field Devices Environment Pop Top Valves Pop Top Actuators Cause Actuator Part no's available in the UK Valve Part No's and connection types available in the UK ZY valve and actuator replacement Resolution   Actuators AH13U230 - High Close Off - Spring Closed 230Vac Actuator c/w 36" Lead AH13U23A - High Close Off - Spring Closed - 230Vac Actuator c/w 36" Lead + Aux Switch AG13A230 - Spring Closed - 24Vac Actuator c/w 36" Lead AG13A23A - Spring Closed - 24Vac Actuator c/w 36" Lead + Aux Switch AG13U230 - Spring Closed - 230Vac Actuator c/w 36" Lead AG13U23A - Spring Closed - 230Vac Actuator c/w 36" Lead + Aux Switch AG23U230 - Spring Open - 230Vac c/w 36" Lead AG23U23A - Spring Open - 230Vac c/w 36" Lead + Aux Switch AG23A230 - Spring Open - 24Vac c/w 36" Lead AG23A23A - Spring Open - 24Vac c/w 36" Lead + Aux Switch Valves (Note:NPT is American connection) VT2222 - 2way - 1/2" NPT 2.5Cv VT2223 - 2way - 1/2" NPT 3.5Cv VT2231 - 2way - 1/2" BSP 1.0Cv VT2232 - 2way - 1/2" BSP 2.5Cv VT2233 - 2way - 1/2" BSP 3.5Cv VT2325 - 2way - 3/4" NPT 5.0Cv VT2327 - 2way - 3/4" NPT 7.0Cv VT2332 - 2way - 3/4" BSP 2.5Cv VT2333 - 2way - 3/4" BSP 3.5Cv VT2335 - 2way - 3/4" BSP 5.0Cv VT2337 - 2way - 3/4" BSP 7.0Cv VT2437 - 2way - 1" BSP 8.0Cv VT3231 - 3way - 1/2" BSP 1.5Cv VT3232 - 3way - 1/2" BSP 3.0Cv VT3233 - 3way - 1/2" BSP 4.0Cv VT3332 - 3way - 3/4" BSP 3.0Cv VT3333 - 3way - 3/4" BSP 4.0Cv VT3335 - 3way - 3/4" BSP 5.0Cv VT3337 - 3way - 3/4" BSP 7.0Cv VT3437 - 3way - 1" BSP 8.0Cv Erie™ PopTop™ Series Valve Bodies and Actuators - Installation Instructions.pdf for the VT and VS valve, AG and AH actuator. Note: Only those listed above are available in the UK.

Issue How many objects, users, devices, etc. per device with EcoStruxure Building Operation Product Line EcoStruxure Building Operation Environment Building Operation Enterprise Server Building Operation Automation Server Building Operation WorkStation Building Operation WebStation Cause How many objects per device and what are the limits of EcoStruxure Building Operation? Resolution The primary source of these details should be the Architectural Guidelines on WebHelp Topic for the version being used

Issue How to turn on and release a specific command priority on a BACnet point? Product Line EcoStruxure Building Operation Environment ES AS Bacnet interface Script programming Cause Wants an example script program to turn on/ off specific BACnet command priorities in a BACnet device. Resolution To control a specific Digital or Analog Output in a BACnet device, from a script program you would use a Numeric Output in the program that has its value set as required by the program. This Output from the program is then bound to the specific command priority attribute of the point to be controlled. To release control from that Command Priority the "Relinquish" keyword is used in the program to Null that specific command priority and allow lower commands to take control of the output.   Here is an example AS test program that turns on a Digital Output for 4 seconds and then releases it for 4 seconds. The Numeric Output DOControl should be bound to the required Output Command Priority 2, it is written as a fallthru program. Notice; the Relinquish command is releasing the output from Command Priority 2 as used in this example.   Numeric Output DOControl DOOnLine: DOControl = Active Wait4: If TS > 4 Then goto DOOffline Else goto Wait4 DOOffline: Relinquish(DOControl,2) Wait4More: If TS > 4 Then goto DOOnline Else goto Wait4More   This type of script program can be located in the Application of the BACnet interface and control outputs on 3rd party BACnet products or b3 controllers. Note: For control of b3 outputs it is often better to put an appropriate control program (Not the above code) within the b3 controller itself, making it more robust in case of comms failure and also reducing communications traffic. Also check out the Convert Continuum Plain English into SBO Script Quick-Help video on the Exchange.

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 "Communication Failed" Alarm occurs when Adding an AS. Source: /Server 1/Servers/ASL/System/Server Communications/Models/2deef04c-05d1-41ae-9c3f-f84a9f7e0b41 Alarm "cannot verify lead object" appears even though AS is online. Product Line EcoStruxure Building Operation Environment StruxureWare Alarm Queue Cause The AS is unable to communicate with the ES. The ES may be able to communicate with the AS allowing the user to view and control the AS, but Value Binds will not work. This type of error can also occur as a result of multiple networks being accessed by the same PC.  It is important that if you are using multiple networks that the ES be configured with the IP address for the correct network. Resolution Ensure that no Firewalls are blocking configured ES and AS ports Ensure all devices are on the same Windows Domain In workstation, select the Enterprise server's Communication Tab and verify that the IP address listed for the ES matches the ES PC IP address. Right click on the ES and select Advanced > Repair Server Communication For more information see Creating Windows Firewall rules to allow StruxureWare Building Operation to communicate on the TCP port

Issue How to create a proper XLSX/Excel template under Alarm Triggered Notification of EcoStruxure Building Workstation, in order to receive the Multi trend logs report in the XLSX/Excel format. Product Line EcoStruxure Building Operation Environment EcoStruxure Building Workstation Cause Additional information is needed to create a template for presenting multi-trend log information in Excel XLSX format.    Resolution Below screenshot shows where users can select the Report format and XLSX template.   The multi trend log containing four Interval Trend Logs 1 to 4 with their time stamp is shown as below as an example   In order to get the XLSX multi trend log report in XLSX/Excel format upon receiving a trigger, the following XLSX template needs to be used containing two rows: The first header row contains the column headers from the trend log. The second row include the <Multi Log List> command   Here is final report in Excel/XLSX format:  

Issue How to discover MNL Lon devices or other Lon devices in an SmartStruxure Automation Server. Product Line EcoStruxure Building Operation Environment Building Operation Workstation Building Operation Automation Server Cause Use the below instructions when you need to find all Lon devices on a Lon network. Resolution To discover a LonWorks device In WorkStation, in the System Tree pane, select the server that is connected to the device you want to discover. Click the Device Discovery view. In the Select device type box, select LonWorks. Select the Devices folder. Right click on the Devices folder and take "Scan network for devices" In the Device Discovery view, ensure that the LonWorks device is displayed in the Devices folder. This may take up to 5 seconds. Drag the discovered device to the System Tree pane: Drag to an existing device to associate it with the discovered physical device. Drag to the LonWorks network to create the device.   NOTE: You cannot drag a standard MNL LonWorks device to the System Tree pane if the discovered device is in an unconfigured state For more information, refer to the Creating and Configuring a LonWorks Network with MNL LonWorks Devices [102423].pdf document 

Issue How to bind BACnet Objects with Priority Levels Product Line EcoStruxure Building Operation Environment EcoStruxure Building Operation BACnet MPX, RPC, MPC Cause Servers (ES, AS) and other native devices (MPX, RPC) have slightly differing binding options. EcoStruxure Building Operation BACnet binding offers many options and the information below gives an example of how it can be achieved, it is not the only method. Resolution When binding between BACnet objects in EcoStruxure Building Operation (either external or within the device) it is usually better to utilize the BACnet Priority based control, often this facility is not fully exploited. Object Force and Overrides will use set priorities as in the BACnet Interface setting for the site (see System/Interface Manager/BACnet), the defaults are below. The example below shows a simple bind from a BACnet Schedule-value to a BACnet Binary-value Priority 16 (or other priority as required, as binding at Priority 16 can interfere with simple manual overrides). A BACnet datetime_value has no Priority array, so if you bind, for example, from a "BACnet Schedule Next transition" to "BACnet datetime_value Value" the bind to a Priority cannot be achieved, as below. In addition, the MPX & RPC have some constraints that Servers do not have. If you bind "Transfer Value to" an Object Value Property (rather than a Priority) then further bindings "Transfer Value to" binding to a Priority is inhibited. The screenshot below shows the error that is seen. This promotes using Priorities to control BACnet Objects.

Issue When attempting to enable .NET Framework 3.5 on Windows using the DISM command mentioned in the WebReport installation guide, the attempt fails with error 1910 Command: dism /online /enable-feature /featurename:NetFX3 /all /Source:e:\sources\sxs /LimitAccess Deployment Image Servicing and Management tool Version: 10.0.14393.0 Image Version: 10.0.14393.0 Error: 1910 The object exporter specified was not found. The DISM log file can be found at C:\WINDOWS\Logs\DISM\dism.log Product Line EcoStruxure Building Operation Environment WebReports Cause The Windows Modules Intaller service is not operating correctly, and has to be restarted. The service is however protected, so this can not be done through the services control panel. Resolution Kill "TrustedInstaller.exe" from the Windows task manager (CTRL+SHIFT+ESC) Start the "Windows Modules Installer" service from Windows services (Start->Run->services.msc) Try again, either using the command or the SBO Reports Preparation tool.

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.