Issue In the Security Expert v4.3.285.42 (current release), there is an issue assigning an OSDP Reader to an Elevator. With the reader expander port Network Type set to RS485, when configuring the Smart Reader record to use the OSDP reader, the option to assign it to an elevator is not available.   Product Line Security Expert Environment Elevator OSDP Security Expert Smartcard Reader Security Expert Server Cause The configuration steps are not obvious and a temporary workaround is required until the issue is fixed. Resolution This is a temporary workaround as the issue is fixed in a future version. Change the reader expander port network type to Third Party Generic and click save Navigate to the Smart Reader record and change the reader mode to the elevator and assign the elevator, click save Then change the reader expander port back to RS485.   *Note* The saved elevator settings on the Smart Reader’s Reader tab will not be visible but the settings you saved will be properly downloaded to the controller.

Issue Cannot find documentation on how to use the new Graphic components release with EBO 2.0 Getting the following errors when previewing my graphic page: "Script error in function "onLoad" .... ReferenceError: "_firstRun" is not defined "Script error in function "onChange" ... ReferenceError: "_setVisuals" is not defined Product Line EcoStruxure Building Operation. Environment Building Operation Graphic Editor 2.0 and above GlobalScripts V2.0.0262 and above Cause With the release of EBO 2.0, a set of new components/snippets have been released which are different to those issued in earlier releases, although visually there is very little change. The scripting, in most cases but not all, has been removed from the components themselves and put into single scripts, this means we can take advantage of the global scripts functionality. This requires the user to set the UseGlobalScripts attribute to True within the TGML graphic editor, this can be on a per graphic basis and ensures that existing graphics will still function. Once turned to True, all components that have scripts, and have requirements for other global scripts to function correctly, can function as designed. For example, the setpoint box requires global scripts to ensure units and decimal places are displayed as designed/required due to the scripts. There are also two binds available on the box, one for reading, one for write. Both need to be bound to enable the component to function correctly.  The components are designed in this way to allow use in BACnet where it may require to read the resultant Value but Write at a specific Priority. Without the scripts added to the graphic, the component cannot function. For further details/questions refer to the following Community Posts which also includes the current PDF documentation: Help-with-an-EBO-2-0-component EcoStruxure-Building-Operation/Graphic-Component-Library-Rev-AB1-002-pdf This article provides the necessary steps required to enable and get these new components working and does not provide in-depth functionality. With the release of EBO 2.0, a set of new components/snippets have been released in the latest build which are different to those previously issued although visually there should be very little change for your customer. In summary, the scripting, in most cases but not all, has been removed from the components themselves and put into single scripts which then means we can take advantage of the global scripts functionality. This requires the user to set the UseGlobalScripts attribute to True within the TGML graphic editor, this can be a per graphic basis and ensures existing graphics still function. Once turned to True, all components that have scripts, and have requirements for other global scripts to function correctly, can indeed function as designed. For example, the setpoint box requires global scripts to ensure units and decimal places displayed as designed/required due to the scripts. There are also 2 binds available on the box, one for reading, one for write. Both need to be bound to enable the component to function correctly. The components are designed in this way to ensure use in BACnet where we may require to read the resultant Value but Write at a specific Priority. Without the scripts added to the graphic, the component cannot function. For further details/questions refer to the following Community Posts which also includes the current PDF documentation: • https://exchangecommunity.schneider-electric.com/t5/EcoStruxure-Building-Operation/Help-with-an-EBO-2-0-component/m-p/107342 • https://exchangecommunity.schneider-electric.com/t5/EcoStruxure-Building-Operation/Graphic-Component-Library-Rev-AB1-002-pdf/td-p/149876 This article provides the necessary steps required to enable and get these new components working and does not provide in-depth functionality. Resolution Within Graphics Editor enable UseGlobalScripts. To do this: Select the -Tgml object shown in the Objects pane In the Properties pane Change the UseGlobalScripts from False to True In the Global Graphic Snippets: Drag the GlobalScripts V2.0.xxxx onto the -Tgml object.  GlobalScripts then appends as shown below. Note: This must be done before doing adding any components and ONLY once on each Graphic page. Add Component by dragging it into the Design window Example showing the Component: Analogue Single Line Text, 100W Add Snippets to allow the relevant Bindings to be added to this component.  To do this: Select Snippets tab, Select Select Global Bind Snippets Drag the appropriate snippet onto the Component. EcoStruxure Analog Value bind snippet is added to the Analogue Value component Save the graphic Preview - no errors should appear.  If there are errors: Ensure that the scripts/components have been added in the correct order Ensure the correct Snippet has been added to the correct Component.  Refer to the Graphic-Component-Library-Rev-AB1-002-pdf documentation for the tested snippets/component combinations. Open WorkStation and Edit Bindings on the saved graphic page Note: The default binding name displayed View the graphic page   Example: Showing forced value      

Issue How to control an output with one or more inputs. Product Line EcoStruxure Security Expert Environment Security Expert Cause Unsure how to program one or more inputs to directly control an output. Input Control Output Resolution The below guide details how to use an Input to activate an Output on Security Expert and SP-C-WEB systems. An output can be assigned to the Input Type and to the Input allowing many to one and one to many configurations.   In order for an Input to activate an Output it needs two things: To be inside an always armed area - This can be an Automation/Dummy area with its only purpose being to activate the output. To have an Input Type that tells it to activate an Output   Single/Multiple Input Activating the same Output If one or more inputs are required to activate the same output, this output can be defined by the input type. The below is a simple scenario where when the Input turns ON the Control Output turns ON, when the Input turns OFF the Control Output turns OFF. Other types of output activations can be configured if required. Creating the Area Navigate to Programming > Areas Add a new area and name it Automation Area, set the Entry and Exit Delay Times to 0. All other settings can be left default. Creating the Input Type Navigate to Programming > Input Types. Create a new Input Type Set the Control Output to the required output Under Options 2 enable the required control options for your scenario e.g. to have the output follow the input exactly enable "Activate Control Output on Alarm" and "Deactivate Control Output on Restore". To have the output activate for a time simply enable "Activate Control Output on Alarm" and set the "Activation Time" under the General tab of the Input Type Menu (Control Output Time) Set any other options that may be required Configuring the Input Navigate to Programming > Inputs select the Input and set the following: Set the Area to the Automation Area created in Step 1 Set the Input Type to the Input Type created in Step 2 Testing Check for any related health status messages that need to be resolved Arm both portions of the Area Activate the Input to confirm Output Activates   Multiple Inputs Activating Different Outputs When multiple inputs are required to activate different outputs, one input type can be used and the outputs can be defined at each input. The below is a simple scenario where when the Input turns ON the Control Output turns ON, when the Input turns OFF the Control Output turns OFF. Other types of output activations can be configured if required. Creating the Area Navigate to Programming > Areas Add a new area and name it Automation Area, set the Entry and Exit Delay Times to 0. All other settings can be left default. Creating the Input Type Navigate to Programming > Input Types. Create a new Input Type Under 'Options 3' enable the required control options for your scenario. e.g. to have the output follow the input exactly enable Activate Input Control Output on Alarm and Deactivate Input Control Output on Restore. To have the output activate for a time simply enable Activate Input Control Output on Alarm and set the Activation Time at the Output itself Set any other options that may be required Configuring the Input Navigate to Programming > Inputs select the Input and set the following Set the Control Output to the appropriate Output Set the Area to the Automation Area created in Step 1 Set the Input Type to the Input Type created in Step 2 Testing Arm both portions of the Area Activate the Input to confirm Output Activates

Issue What is "Verbose" within Vista Server Setup? Documentation refers to "certain dialogs and messages." What are these certain dialogs? Product Line TAC Vista Environment TAC Vista Server Setup TAC Vista Workstation Cause The documentation states that this setting: "Enables or disables the display of certain dialogs and messages for operator communication."  Resolution Verbose turns on questions that ask if you really want to do something. An example, "Do you really want to quit?" when closing Vista server.

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 Both the STAT LED and the BEAT LED is off on the Jace controller and cannot successfully ping the JACE 8000 IP address Product Line TAC IA Series Environment I/A Series JACE 8000 Cause The STAT and BEAT LED remaining in an off state is an indication that no SD card is installed in the JACE card carrier.  When the Micro SD card is installed the STAT LED is solid Green, and BEAT LED is blinking Amber. Resolution Make sure to insert the SD card prior to startup commissioning of the JACE 8000. See JACE-8000 Install and Startup Guide

Issue Display options now the DCX250 is no longer available Product Line Andover Continuum Environment Continuum DCX250 Touch Screen Display part number 01-0008-300 Cause The DCX250 is not available from January 2012: Discontinuation of Infinity 01-0008-300 (DCX 250) - PA-00184 Resolution There is no direct replacement for the DCX250 and there is no other display that works directly on Infinet.   The Continuum display options are- Netcontroller IO Bus - Infistat or LD-1 Direct connection to some controllers - Smart sensor or xP-Display A Continuum Cyberstation could be used if more information and input is required. Another option would be a Bacnet or Lon display. Or, the L-VIS from Loytec using bacnet MSTP may be such an option (LonWorks and BACnet Touch Panels Release - PA-00106). http://www.loytec.com/products/lvis (LON via NC2-F- port16 would also be an option, see Can LONMark Devices be used with Continuum?) NOTE - All support for this product is via Loytec. The EMX170 was a small display and keyboard available for some older Infinity Controllers (i1) This unit is obsolete, although it may be possible to repair one. There is no replacement for this unit. If the i1 controller is being replaced with an i2 unit then either a smart sensor or an xP Display plus room sensor could be used

Issue Troubleshooting steps for the Infinet and MSTP bus. Product Line Andover Continuum, EcoStruxure Building Operation Environment Continuum SmartStruxure RS-485 Infinet BACnet MSTP Cause Methods are needed to troubleshoot the Infinet and MSTP bus Resolution This is not a comprehensive list of all methods for troubleshooting, but a starting point. The Infinit-mstp troubleshooting document is available here.

Issue What are VOCs and which ones are detected by our SLA/SLP sensor? Product Line Field devices Environment SpaceLogic SLA series and SpaceLogic SLP Series VOC Sensors Cause Unsure what substances are detected by the Space Logic SLA/SLP VOC sensors Resolution What are VOCs? Volatile organic compounds (VOCs*) are a wide range of carbon based (organic) chemicals (compounds) found in various man-made and naturally occurring solids and liquids. They evaporate easily at ordinary room temperature** which is why they are termed volatile. VOCs are numerous, varied, and ubiquitous. They include both human-made and naturally occurring chemical compounds. Most scents or odors are of VOCs. Some VOCs are dangerous to human health or cause harm to the environment. Respiratory, allergic, or immune effects in infants or children are associated with man-made VOCs and other indoor or outdoor air pollutants. Government regulations have prompted several companies in the paint and adhesive industries to adapt with VOC level reductions in their products. * VOCs play an important role in communication between plants, and messages from plants to animals. ** For example, formaldehyde, which evaporates from paint and releases from materials like resin, has a boiling point of only –19 °C (–2 °F). Typical Indoor VOC Sources There are over 600 VOCs that can be found in the air. The following are commonly encountered in buildings: Anthropogenic*** VOCs are regulated by law, especially indoors, where concentrations are the highest. Harmful VOCs typically are not acutely toxic (result in throat irritation and headaches) but can have serious compounding long-term health effects(damage to internal organs). Because the concentrations are usually low and the symptoms slow to develop, research into VOCs and their effects is difficult. *** Relating or resulting from the influence of human beings on nature   How Are VOCs Measured? VOC sensors normally present their measurement in Total Volatile Organic Compounds (TVOC) which corresponds to the sum of volatile organic compounds. VOC contamination is an established concept in regulatory and scientific literature. It is a practical method (time and cost-effective) of surveying indoor environments for contamination. The specific TVOC composition varies between different ambient indoor environments and indoor air is always composed of different volatile organic substances. Therefore, it is helpful to consider TVOC concentrations as statistical reference values which help to indicate indoor air quality.   The World Health Organization (WHO) guidelines for TVOC are shown below and these are in line with the AQI table published in our specification sheets. Indoor Air Quality Level Guidelines for Europe by the World Health Organization (WHO)   The sensing principle of the VOC sensor is based on a heated film of metal-oxide nano-particles. In clean air, donor electrons in tin dioxide are attracted toward oxygen which is adsorbed on the surface of the sensing material, preventing electric current flow. In the presence of reducing gases, the surface density of adsorbed oxygen decreases as it reacts with the reducing gases. Electrons are then released into the tin dioxide, allowing current to flow freely through the sensor. VOC sensors are normally calibrated while using only one VOC (Ethanol).   Summary There are over 600 identified VOCs that may be present in indoor air and the sensing element used by VOC sensors reacts to any of these compounds. Therefore it's not possible to state what VOC is responsible for a raised reading.

Issue Need to delay an Input from going into alarm before sending that alarm to an email recipient. Product Line Security Expert Environment Security Expert Cause Have a requirement to email alarms for Door inputs that are not actually tied to Door records. Resolution One method of configuring this is to use an Area: Add the Input to the Area to trigger an alarm Configure that alarm event into an Email using an Action.  See the following detailed steps:  Under Programming: Inputs Configure the Alarm Input Speed option for the Input. This will be the delay time before the input triggers an alarm event. Set this to how long the door needs to be open before the alarm is generated. Under Events Create an Event Filter and add Area <Area_Name> Alarm Activated Create an Alarm and add the Event Filter to it. Create an Action. Configure the Type as Send E-mail Configure the Event Filter to that created previously. Set the Email Settings as required. Under Programming Create an Area On the Configuration tab set all timings to 0. Within the Input On the Areas and Input Types tab add this new Area to Area 1 field Set the Input Type 1 to Instant. In the Options enable Log to Event Buffer so the activations are reported. This setting can be reverted after testing.

Issue Transferring an I/NET Seven system from one PC to another Product Line TAC I/NET  Environment I/NET Seven Site Cause Customer needs to transfer I/NET between two computers Resolution Perform the following steps: Install I/NET Seven on the new PC. Using DBCreate.exe, create a backup of the I/NET database. Copy the backup to the new PC and restore it using DBCreate. If the database needs to be upgraded it will prompt you.  Proceed with the upgrade.  Copy the save files, graphic pages, archives, any custom reports, custom symbols, and custom BIN files (ICI bin files) to the new PC using the same directory path as the previous PC to guarantee that graphic links will still work. The following are default paths for these files assuming it was not an upgrade from I/NET 2000. If it was an upgrade from I/NET 2000 please consult TCON298 the Getting Started guide which includes I/NET 2000 paths. Default location for Archives: C:\Program Files\INET Seven\Arch\ Default location for BIN Files: C:\Program Files\INET Seven\Data\ Default location for Reports: C:\Program Files\INET Seven\Reports\ Default location for Save Files: C:\Program Files\INET Seven\Sav\ Default location for Bin Files: C:\Program Files\INET Seven\Data\ Default location for Graphics: C:\Program Files\INET Seven\ Take a screen capture or write down the active configuration profile in I/NET configuration and manually fill this information into I/NET configuration on the new PC and make it the active configuration profile. Transfer the communication medium to the new PC (serial cable or Ethernet cable) and if communicating via NPR’s set the IP address of the new PC to match that of the old PC and remove the old PC from the network to avoid IP address conflict. Start up I/NET, login, and edit the Host Computer->Network Configuration to verify that the PC is communicating with the controllers.

Issue How to Lockdown your facilities using Continuum area/door lockdown functionality. Product Line Andover Continuum Environment CyberStation CX9680 ACX5740/20 Cause Need a fast and efficient way to lock down multiple areas in one operation when a threat is perceived at a site. Resolution The Continuum Physical Access Control System supports an advanced feature that allows for quickly locking down parts of or an entire building or campus via the areas/doors that are under physical access control by the Continuum system. This functionality is available in second-generation access controllers such as the CX9680 (NC2) and the CX5720/5740(ACX2) In Continuum, lockdown of an area or door means that access to the area/door via the physical access control system is restricted in such a way that prevents the movement of individuals into the locked-down area/door as well as keeping individuals from leaving the area/door under locked down. Locking down an area automatically locks down all doors associated with the area; Continuum also allows doors to be locked down individually. When a door/area is locked down, all credential access attempts and exit requests are denied. The only way to gain access into the locked-down door/area is by the use of a credential that has been designated with ‘Executive Privilege’ in the system. Note though, that a person with executive privilege may gain access into a locked-down area/door via the credential reader but if the mode of egress from the area is via Exit Request then such person would not be able to exit the door thru the normal exit request mechanism as there is no way for the person to indicate her ‘executive’ privilege by any means other than presenting the proper credentials (card or PIN) at a reader. This document outlines several methods of implementing area lockdown for a building or campus such as a school, the methods outlined in the document are provided for illustration purposes only and are not to be taken as a complete solution but rather as general guidelines. On legacy controllers that do not support the Area Lockdown feature (CX99xx, ACX7xx), we can still secure the doors by setting their state to disabled which prevents the doors from processing credential access attempts as well as Request to Exit, please note that in this case, NO ONE (including executive privilege personnel) will be able to gain access to the door until it is re-enabled How to Lockdown your facilities using Continuum area lockdown outlines several methods of implementing area lockdown for a building or campus such as a school, the methods outlined in the document are provided for illustration purposes only and are not to be taken as a complete solution but rather as general guidelines.

Issue There is a Schneider Electric 37-Bit Reader Format in the Security Expert system.   Product Line Security Expert Environment Reader Formats Cause Is the Schneider Electric 37-Bit Reader Format in the Security Expert system the same as the Infinity 37-Bit Wiegand Format used in Continuum, then can this be selected for transitioning systems? Resolution The Schneider Electric 37-Bit Reader Format in the Security Expert system is NOT the same as the Infinity 37-Bit Wiegand Format used in Continuum. Infinity 37-Bit cards transitioning to a Security Expert system will need to be accommodated using either Custom Formats or Custom Credentials.

Issue PCT fails to open, presenting four 'could not connect' error messages.   Product Line Project Configuration Tool Environment Windows 10 version 1909 Windows 10 version 2004 Cause The cause maybe a firewall, scripts or group policy not allowing PCT to install correctly. Resolution Raise a case with your region's IT2929 (UK = 020 7660 2747), requesting IT install the patch to correct the issue. IT2929 have a knowledge base article on the IT2929 system to help their representatives with this issue (KB0014074).   IT2929 will advise you to take a backup of your PCT projects, uninstall PCT and Oracle VM VirtualBox. IT2929 will then install the patch. Re-boot the laptop. Install PCT and Oracle VM VirtualBox (run as administrator). Restore your PCT projects. Re-boot the computer. If PCT still does not work after this, update the CCC case you have or create a new case with product support, providing your IT2929 KSR number is you do not have a case.

Issue When a disabled card is presented to a reader the Door name of that reader is not included in the User Record Disabled events.  Product Line Security Expert Environment Security Expert Disabled User Card Cause Once the user has been disabled the User object no longer resides in the controller. Resolution The information in the User Record Disabled event can be used to determine which reader the user has badged at. The Controller column has the controller that registered this event and the Description will tell you the Reader Expander and Port on that Expander. Record Disabled Event In the above example event, we can determine Bill has badged at Reader Port 1 of Reader Expander address 1 on controller QCA02 - ADM.

Issue Security Expert Client crashes when attempting to browse to the Status Page Editor. Unable to create Status Pages for system monitoring. When viewing Status Pages none are shown and the word "Frame" is displayed in the view. Product Line Security Expert Environment Security Expert Client Status Pages Cause The problem is due to the site database not containing the default id=0 objects, as there is no Status Page for your site the client crashes when it tries to load this when browsing to Monitoring | Setup | Status Page Editor. This can occur when the original default controller is not created when the Site is first configured. Part of this process is that a number of default objects are created as well as the first controller. If you have a look at the site database again you will see that it also does not contain any Event Filters or Actions which means that there are no events being logged as well. Status Page Resolution There are two options to resolve these missing default records: Start with a new Security Expert database and ensure that when creating your Site that the first controller is created with the Controller Wizard. At the end of this process, the default site objects are also created. Setup a support case with Product Support to arrange for a remote connection with R&D where they will create the missing records with the use of the DataSync Service. The site's SSN will need to be provided so that SOAP and DataSync service are enabled for the session.

Issue When configuring an Input to control an Output in an Input Type, what are the differences between using the "Control Output" or "Input Control Output" options? Product Line Security Expert Environment Security Expert Cause When configuring Input Types there can be some confusion with the terminology used to describe the two types of Outputs that can be controlled from an Input event.  Control Output options on the Input Types Options (2) tab Input Control Output options on the Input Types Options (3) tab Resolution The "Control Output" options refer to the Control Output defined in the Input Type's General tab. Control Output The "Input Control Output" options refer to the Control Output defined in the individual Inputs General tab. Input Control Output An explanation for a related example would be: If a common output for all inputs of the Input Type then; On the Options (2) tab enable the Activate Control Output On Alarm and Deactivate Control Output On Restore. On the Configuration tab of the Input Type, set the Control Output to the output you want to trigger. Else if each input has a separate output then; On the Options (3) tab enable the Activate Input Control Output On Alarm and Deactivate Input Control Output On Restore. In each Input set the Control Output to the output you want to trigger.

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 (**4) 3.46.105 Hotfix 10 03 2017 SigmaX 7.0.9 Release 4.08 (**5) 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 (**6) 3.46.110 Software 13 05 2019 SigmaX 7.0.9 Release 4.08 (**7) 3.46.111 Hotfix 15 11 2019 SigmaX 7.0.9 Notes:         **1 Sigma build 3.46.57 with StruxureWare Building Operation v1.5 or 1.6  transition support Program installed. **2 Sigma build 3.46.57 with StruxureWare Building Operation v1.8  transition support Program installed. **3 Sigma build 3.46.57 with StruxureWare Building Operation v1.9  transition support Program installed. **4 Sigma build 3.46.57 with StruxureWare Building Operation v1.9 Hotfix to Support Program installed. **5 Sigma build 3.46.57 with StruxureWare Building Operation v2.01 transition support Program installed. **6 Sigma build 3.46.57 with StruxureWare Building Operation v3.0.1, v3.0.2 and v3.0.3 transition support Program installed. **7 Sigma build 3.46.57 with StruxureWare Building Operation v3.0.4, v3.1 and v3.2 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 2021 01 21 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 When using SBO 1.9, the registration website opened allows the user to login and enter new system ID, however, the user then cannot proceed any further. Product Line EcoStruxure Building Operation Environment SmartStruxure Building Operation 1.9 Cause The link https://registration.smartstruxure.schneider-electric.com/ , which redirects to the  https://registration.smartstruxure.schneider-electric.com/WebConnectUI/RegisterUser/home This page may not allow the user to complete the site’s registration with their new system ID. Resolution Register the site’s SBO 1.9.x new system ID using the following website address. https://registration.smartstruxure.schneider-electric.com/ebo/Home

Issue What HID Corporate 1000 card formats are supported by Security Expert? Product Line Security Expert Environment Security Expert Server Security Expert Controller Security Expert Smart Card Reader Cause Information about HID Corporate 1000 card formats is needed to configure the card readers correctly. The existing documentation does not mention this. Resolution HID Corporate 1000 35-bit format has been validated with Security Expert. To use this go to Expanders | Reader Expanders | Reader 1 and set the Reader 1 Format setting to HID Corp 1000 as shown below. Other HID Corporate 1000 formats may work however they have not been validated.  If the format specification is known, it is possible to program the cards in a custom format. As an example, below are the custom format settings used for the HID Corporate 1000 48-bit format cards. Go to the Custom Reader Format tab of your controller and enter the following values. HID Corporate 1000 48-bit format 1 HID Corporate 1000 48-bit format 2 If the format is different from the above two examples or is not known, please provide support with the output from Any Bit RAW card reads from at least three different cards to help determine the format. Refer to article Show raw card data of a badged card in Security Expert for further details on this.

Warning Hazard of Electric Shock: Remove all power from all devices before removing any covers or doors of the system. Disconnect power at the device and at the power source. Electrostatic Discharge Required: Always discharge static electricity from your person by touching metal prior to handling any hardware. Failure to do so may result in damage to devices. Issue ACX5740 controller randomly re-boots and restore from flash, the controller does not attempt warm start but instead jumps directly to cool start.  Product Line Andover Continuum Environment Continuum ACX 2 Controller Continuum ACX 4 Controller Continuum Net Controller II Cause Door striker creating an electrical spike that can travel back down the output wiring to the controller. When this happens, it generally will not damage any of the hardware in the controller but it could cause it to reset or cause its memory to get scrambled. The fact that the controller does not attempt warm start but instead skips directly to cool start is a strong indication that memory corruption is taking place, on startup, the controller verifies RAM memory is intact and will not attempt warm start otherwise. Resolution Install Metal Oxide Varistor (MOV ) to add voltage suppression to the controller's output driving the door striker. ( Put the MOVs at the end device and not the controller end)   Another option is to add an isolation relay to keep the electrical noise from reaching the controller's output.