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 (**6) 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 a user attempts to connect to the Sigma 4.08 (3.46.57) Server using a WebClient, the client connects, but the screen remains blank. Product Line Satchwell Sigma Environment Sigma WebClient 4.08 (3.46.57) Cause When Sigma 4.08 is installed, the installed version of LogonSE.swc is blank. Resolution Download the correct version of LogonSE.swc. Shutdown the Sigma client and server. Navigate to Sigma/Data/Graphics/Drawings and delete LogonSE.swc. Copy the downloaded version of LogonSE.swc to Sigma/Data/Graphics/Drawings. Restart the Sigma client and server, and then test the Web Client.

Issue Sigma parallel port dongle or USB dongle upgrade to software license Product Line Satchwell Sigma Environment Sigma version 4.08 Cause It is becoming increasingly harder to purchase computers with parallel ports. With the increase use of virtual computer operating systems USB ports may not be available either. ∴ A different type of Sigma licensing will be required. Resolution Product Support Services (PSS) can arrange for an upgrade from your existing parallel port or USB type Sigma dongle to an SBO/EBO software license entitlement for Sigma 4.0.8. Sites running Sigma 4.07 or older do not support software licensing and would need to be upgraded to Sigma version 4.08.57 or later to include the software option. Sigma Software license type availability is documented on page 8 in the Sigma 4.08 release note. For engineers using Sigma 4.08: The StruxureWare Building Operation Evaluation License, available from the Schneider Electric Download Center, will unlock the Sigma 4.08 for testing etc for the period of the Evaluation License (maximum 3 months or until the expiry of the downloaded license).   For customer sites using Sigma 4.08: To reduce the Sigma system downtime, currently PSS operate on a trust basis and provide the software license in advance. PSS require you to send the old Sigma dongle back to the PSS representative that is assisting you with your license upgrade. This should be completed within 30 days of receiving your software license. Once you receive the software license entitlement for Sigma. Install the SBO License Server version 1.6 or later. (it is recommended that the latest available version of the SBO License Server compatible with the computer's operating system is used). Procedure: Download the Sigma Dongle Replacement - Required Data 2020 form. Complete the cells that are highlighted/filled in blue. Open a case with PSS. Supply the completed spreadsheet. PSS will escalate a Sigma transitions site for the software license. If the site is a stand-a-lone Sigma site, PSS will need to get approval from the regional category manager before escalating for the software license. Note: If your current Sigma dongle contains Remote Alarm Manager licensing, Remote Alarm Manager does not support the EBO license server option. The USB dongle can still be used or a TAC license server type license can be used instead of the dongle. To install the software licensing option for Sigma 4.08: - Stop the Sigma server service. Install SBO/EBO License Administrator. Add your entitlement to the SBO/EBO License Server. Start the Sigma server service. Sigma should now be licensed.

Issue Where Sigma utilizes the site Ethernet network, and that the network consists of multiple subnets, or is using Sigma DNN's with ARCnet or ethernet secondary LANs. Global object values are not received at the receiving controller when it is on a different subnet to the sending controller. Product Line Sigma Environment Ethernet networks containing subnets. Cause Global Values not being passed from controller to controller on different subnets. General advice on the configuration of Link Addressing. Resolution PIB 05 105 Link Addressing explains how to configure Link Addressing on a Sigma system utilizing a customers Ethernet network,

Issue Duplicated SFE Short Form Edit graphics Product Line EcoStruxure Building Operation Environment Building Operation Enterprise Server Sigma Cause A duplicated set of Short Form Edit graphics are created but are in a different language appear along side the original SFE graphics when using Data Import with a Sigma transition into EBO The example below shows the original DataImport was completed in English, the second DataImport was completed in Danish. Resolution Before a Sigma DataImport is undertaken, ensure that the correct language is set in EBO. Delete the Sigma Interface, set the correct language and start the transition again. Note: By deleting the Sigma Interface, this will delete all the SFE graphic links on the objects and a clean set of SFE graphics will be created on all the objects.

Issue Many LonWorks network installation problems can be avoided if the appropriate network design rules are followed when the network is being designed. Product Line Satchwell Sigma, TAC IA Series, TAC Vista Environment I/A Series MicroNet (LON) Controllers Sigma MicroNet series LON Controllers Vista Xenta Cause The I/A Series MicroNet System Engineering Guide (F-26507) was written as a resource of information for the installation of the I/A Series MNL-100, 200 & VAV controllers as well as the Sigma MicroNet 440 and 620 controllers.  This document is no longer in print.  The Resolution, below, is a summary of the LON design rules presented in that document. Resolution FTT-10 LON network wiring must be installed using Echelon approved wire.  The most common type of wire used is described as Category 4  cable.  This wire is normally unshielded stranded twisted-pair 22AWG (0.65mm).  An example of this wire is the W221P or W222P series cable from Connect-Air International (http://www.connect-air.com).  This type of cable is normally available both in plenum rated and non-plenum rated types.  Consult the job specifications to determine if plenum rated or shielded cable is required. The LON network can be wired using "Free Topology" or "Bus Topology" wiring segments.   A.  BUS Topology Guidelines BUS Topology LonWorks wiring extends from device to device (daisy chain format) with no branches or stubs. A LON-TERM-2 terminator must be installed at each end of the LON bus. When using standard Category 4 LON cable with the recommended terminators, the bus may be up to 4593 feet (1400 meters) in length. When extending LON wire to the MN-Sx sensor base in a bus topology network, the sensor base must be wired as part of the daisy-chain and not as a stub connection. B. FREE Topology Guidelines Free Topology imposes essentially no restrictions on the layout of the network -- some controllers may be wired point to point and others branching from a common point.  The free-topology LON network must be terminated at one point with a LON-TERM-1 terminator. When using standard Category 4 LON cable, the total wire length in a free topology LON network may not exceed 1641 feet (500 meters).  In addition, the longest wire path between any two controllers on a free topology LON network may not exceed 1312 feet (400 meters). C. Common LON Network Wiring Guidelines LON wiring can not be part of an active bundled telephone trunk even if the telephone trunk is wired with Category 4 wire. Shielded Category 4 wire may be used in high EMI/RFI environments.  The shield must be wired continuously and grounded through a 470 Kohm resistor at one end. LON wiring must not be bundled with or housed in the same conduit as controller I/O and power wiring.  D. LonWorks Network Wiring and Addressing Guidelines When the number of controllers on a LonWorks network exceeds 60, the network must be split into segments with not more than 64 controllers or devices per segment using LonWorks Repeaters or Routers.  When counting the controllers and devices on a LonWorks network segment, a LonWorks Network Interface Device and the repeater itself must be included in the device count in each segment. In a LonWorks network containing repeaters or routers, each LonWorks network segment must be properly terminated, as described above. Domain / Subnet / Node addressing is used when configuring the LON controllers. A LonWorks Subnet consists of a series of LonWorks controllers all configured within the same LON Subnet number. A single LonWorks Subnet can have a maximum of 127 device and controller Node addresses.  This Node address count includes the LonWorks Network Interface, all controllers on the subnet, and repeater and/or router node addresses.  An allowance is typically made for additional addresses to be used by LonWorks tools connected to the Subnet.

Issue Temperature Sensor Resistance Charts Product Line Andover Continuum, EcoStruxure Building Operation, Field Devices, Satchwell MicroNet, Satchwell Sigma, TAC IA Series, TAC INET, TAC Vista Environment Temperature Sensors Cause Temperature (°C) to Resistance Charts (ohms). Upgrading the site BMS, but retaining the existing sensors and the sensor resistance values are not known. Resolution The resistance of a sensor at a specific temperature can be downloaded here. The devices covered are Schneider-Electric's range including Andover, TAC and Satchwell and other manufacturers temperature sensors. All are detailed below. For the standard thermistor, tables click here, where the INET, I/A, and BALCO resistance tables are detailed. This is the chart for the Precon Thermistors - ACCTemp 10K Type III thermistor also known as the 10K4A1 Thermistor. For EcoStruxure I/O Module universal inputs, the type of thermistor bead is classed as a: "10k Type I (Continuum)" Satchwell T range is now known as STR600, STP660, STD600, STO600 10K3A1 with shunt Drayton DC1000, DC1100 30K6A1 is now known as STR600D, STP600D, STO600D Andover 10K4A1 TAC Inc. Vista 1.8KA1 I/A series 10K3A1 with 11K shunt INET 10K2A1 (10k Dale) BALCO 1000 ohm RTD Older Satchwell ranges: Satchwell DW1204, DW1305, DWS1202 Satchwell DO Satchwell DD/DR Other manufacturers include: Allerton 3K3A1 Ambiflex 2012, Honeywell Aquatrol, Jel/Thorn, Trend, York 10K3A1 Schlumberger (air) 5K3A1 Schlumberger (immersion) 100K6A1 Automatrix, York, Sibe 10K4A1 Honeywell 20K6A Landis & Gyr PT100A, PT1000A For I/A Series Controllers (MNL/MNB) Compatible sensors that have a built-in 11k shunt resistor include the TS-5711-850, TS-57011-850, TS-57031-850, and TSMN-90110-850 Series. Any sensor that matches resistance to temperature curve for a 10K Thermistor Type G (U.S. Sensor), Type 9 (Dale/Vishay) or Type III (ACI Series AH) can be used with the I/A Series MNL and I/A Series MNB series controllers, provided that a 11k ± 0.1% 1/8 watt resistor is wired in parallel with the sensor. The input has a range of -10 to 135 °F (-23.3 to 57.2 °C) with an accuracy of ±1% of span. Temperature / Resistance Reference Values Temperature Deg F (Deg C) Resistance Resistance Incl. 11k Shunt 32 (0) 25490 8,012 68 (20) 12,260 5,798 75 (25) 10,000 5,238 104 (40) 5,592 3,707 140 (60) 2,760 2,206 The full temperature / resistance table for the US Sensor 10K Thermistor R-T Curve Type G sensor can be found here. Please note that the controller may not be able to use the full temperature range shown in the table.  

Issue The Echelon LonTalk PCC-10 PCMCIA Network Adapter will not work with a Dell E6410 laptop. Product Line Satchwell MicroNet, Satchwell Sigma, TAC IA Series, TAC Vista Environment Echelon LonTalk PCC-10 PCMCIA Network Adapter Dell E6410 laptop Cause Dell E6400 Chipset Resolution To correct this, an entry needs to be added into the Windows registry. Option 1 Download a Windows registry import file from The Exchange. Navigate through Products > Satchwell > Sigma or MicroNet > Downloads > Hot Fix (Or you can download the file here RegedittoaddPCMCIACard.zip). Once downloaded, double click the file and the entry will automatically be added. Reboot the computer before the entry is read. Option 2 Manually add the entry into your registry. Use caution when making changes to the Windows registry. Mistakes can be fatal to the operating system. To manually add the entry, carry out the following: Go to Start > Run and use “regedit” to open the Windows registry. Navigate through to HKEY_LOCAL_MACHINE\SYSTEM\ CurrentControlSet Services Pcmcia Parameters Add a new DWORD entry called “IrqRouteToPciController” Modify the new entry and give it a hexadecimal value of 8 Reboot the computer before the entry is read. If option 1 or 2 do not resolve the issue, it may be necessary to perform the following:  Option 3 Open the registry editor. Go to the registry entry HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Class\{68EE3401-D4CA-11D3-8DBB-0060082936F2} or HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Class\{68EE3401-D4CA-11D3-8DBB-0060082936F2}\0000 and look for the key name "PcmciaExclusiveIrq". Delete the key name "PcmciaExclusiveIrq" (If it exists). You may need to reboot the PC. Further information may be available in the Echelon Knowledge Base on the Echelon website. This information can be found in Solution: KB763. For more information, please refer to TPA-SACH-10-0009.00 - LON PCC-10 PCMCIA Card with Dell E6410 Laptop

Issue Alarms being generated on the Sigma system are not displayed in the Sigma local, or remote client Alarm Manager window. Product Line Satchwell Sigma Environment Sigma 4.04 or later Cause The Sigma local, or remote clients have not been correctly configured in the Sigma server. Resolution Confirm that the Sigma client has been selected to receive alarms. Open the Sigma System Setup and from the tree structure select "Clients". Identify and select the required client , confirm that the correct Sigma server is selected from the list of servers shown.   Select Controllers from the tree structure, then choose "Routesets". For each routeset make sure that the client has been selected.   If changes have been made to the routesets, download them to all of the Sigma controllers.

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 When Data Import is used in the Sigma Interface, the Data Importer fails to connect with the Sigma server. Product Line EcoStruxure Building Operation, Satchwell Sigma Environment Building Operation Workstation Sigma Cause Sigma requires the correct release of Sigma software to be installed as well as the Sigma Transition Tool. Installing the Sigma Transition Tool onto a Sigma server machine can mask the true version of Sigma server and client installed. Resolution The release of Sigma client and server that is to be transitioned into EBO should be Sigma 4.08 (build 3.46.nnn) before the Sigma Transition Tool is installed. However installing the Sigma Transition Tool will overwrite the Sigma version in the Sigma application and in the Sigma splash window when launched.   To check the true version: 1. Go to Windows Explorer and locate the directory c:\sigma\bin. 2. Identify SigOp.exe (or other files) and hover over or right click and open 'Properties' and the tab 'Details',  3. The version number should be at least 3.46.57     If the version identified is below e.g. 3.45.nnn, then Sigma needs to be upgraded to the correct release. The Sigma Transition Tool will need to be uninstalled first, the Sigma upgraded and the Transition Tool reinstalled.   When complete, rerun the Sigma Data Import in EBO.   Note: Remote Sigma clients that are connected to the Sigma server will also need to be upgraded.

Issue Sigma graphic only updates when first opened and no regular updates occur there after or only some graphic data values update. Product Line Satchwell Sigma Environment Sigma Controllers Cause A Sigma graphic update is controlled by the tolerance setting on the Sigma object and defines when the new value is transmitted from the controller to the server.  If the update does not occur, then the Tolerance value could be set to high. Resolution Reduce the tolerance value via the Sigma object editor. Download the object to the controller. Restart the graphic. Note:  Reducing the tolerance too far can lead to graphic updates dominating communications resources in the controller. For example; A temperature object can be set to 0.05 to give an update for every 0.1 degrees. A change of state programmable object should be set to 0.5 as it will returned true/false statement (equivalent to 1/0). A pressure sensor measuring Pascal’s (100's) may need the tolerance setting higher (e.g. 10) as pressure can change rapidly at higher values.  For globally changing the tolerance values for the Sigma objects, download the Sigma Tolerance Utility

Issue When a Sigma data import is carried out, the following messages are displayed on the SBO ES computer. On the Sigma server computer, the Sigma server service has stopped. Product Line EcoStruxure Building Operation Environment Sigma 4.08 Building Operation Workstation Building Operation Enterprise Server Cause The Sigma database’s longtext file contains unsupported characters. Resolution Option 1: If Sigma longtext is no longer required: On the Sigma computer. 1)      Stop the Sigma server service. 2)      Delete the longtext.rec file from the Sigma Data folder (C:\Sigma\Data\longtext.rec). 3)      Start the Sigma server service. On the SBO computer Carry out the data import again. Option 2: If Sigma longtext is required: On the Sigma server computer. 1)      Start the Sigma server service. Open a Sigma client, either on the Sigma server computer or the SBO ES computer or other. 1)      Log into Sigma’s operator panel 2)      Go to the System Alarm manager 3)      Under the menu “Configure” select Longtext 4)      Open each longtext entry and remove the unsupported characters 5)      Add the longtext message your require. (You may find copies of the original longtext messages you can copy the text from, under “C:\Sigma\Data\Longtext” used by Sigma before the system was upgraded. On the SBO computer 6)      Carry out the data import again.   The data import should now complete.

Issue Every time the computer reboots, LMGRD errors are shown at startup.   LMGRD encountered a problem and needed to close. lmgrd.exe - Application Error The instruction at "0x0012e854" referenced memory at "0xffffff91". The memory could not be "written". Product Line Other, Satchwell MicroNet, Satchwell Sigma, TAC Vista Environment Vista Server 5.0 FlexNet Licensing Remote Alarm Manager Sigma BAS2800+ Micronet Errors Cause There is a known issue with the new license server from Flexnet. The LMGRD.exe is actually crashing during shut down of the PC. Resolution This is nothing dangerous. What happens is that when you turn off the PC, something is happening with the license server during the shutdown phase. Since LMGRD runs as service, it can not display this error message during this shut down. The error message is shown the next time the PC is started. It will not affect anything since the error messages is queued from the last shutdown sequence, NOT during the startup. We think it has something to do with having a license server installed and not using only an entitlement license. In some situations, placing a customer license file from any project into the license folder along with the monthly demo license stops the LMGRD error. The license server may read the customer license, note that it is invalid, then use the monthly license. Flexnet is looking into this issue. Look for a fix in upcoming versions. On Sigma, BAS2800+, and Micronet systems where Remote Alarm Manager is installed, the TAC license server can be uninstalled as it is not used.

Issue Error message when starting SigmaX, says "Failed to Create Object", once accepted SigmaX works correctly. Product Line Satchwell Sigma Environment Sigma SigmaX Tools Utilities Cause Sigma Graphics has not correctly registered in the system registry. Resolution This issue is rectified as detailed below. 1 - Close SigmaX if running. 2 - Start the Sigma server and client. 3 - Open the Sigma graphics editor, and either open an existing graphic, or start a new one. 4 - Modify the graphic and then save the changes. 5 - Shutdown the Sigma client and server, Start SigmaX and confirm its operation.

Issue After loading SigmaX on to a new laptop it does not run.  An error appears "The file SigInterfaceMfc.dll is not found." If accepted then another error message occurs, "The file SigShell.dll is not found." Product Line Satchwell Sigma Software Environment Sigma SigmaX Windows XP, 7, 10 Cause The Windows Environment Path "C:\sigma\bin" is not set when SigmaX was installed. Resolution Manually add the setting “c:\sigma\bin” to the Windows Environment Path. On Desk Top find the icon "My Computer". Using right hand mouse button select "Properties". Select the "Advanced" tab. Select the "Environment Variables" button. In the "System variables" window highlight the "Path" variable. Select the "Edit" button Scroll to the end of the "Variable value" text box and append the text string with “;C:\Sigma\bin\” Select "OK" buttons to close and save the changes (three times).

Issue Replacements for Satchwell sensors Product Line Satchwell MicroNet, Satchwell Sigma, Field Devices Environment DR DR3253 DRT DRT3451 DRT3453 DRT4453 DRT3651 DRT3652 DRT3801 DRT3851 DU DU4301 DUS DUS4302 DUSF DUSF4351 DUSF4352 DRTE DRTE2201 DRTE2801 DRTE2851 DRH DRH7702 DRH7703 DRTH DRTH7712 DRTH7713 DOT DOT0001 DOT0002 DOS DOS0002 DDT DDT1701 Cause Replacements for Satchwell Room sensors Resolution DOT0001/0002 Outside temperature sensor For CSC, KMC, MMC, IAC, MNN New part number: STO600/5126060000 DOS0002 Outside solar sensor For CSC, KMC, MMC, IAC, MNN New part number:  SSO600/5126050000 DR3253 Room sensor non-adjustable For SVT New part number: STR614/004604900 DRT3451 Room sensor exposed adjustment For CZU, CSC New part number: STR612/004604700 DRT3452 Room sensor concealed adjustment For CZU, CSC New part number: STR611/004604600 DRT3453 Room sensor non-adjustable CZU, CSC, CXR, CZT, KMC, MMC, IAC, MNN New part number: STR600/004604100 DRT4451 Room sensor non-adjustable As DRT 3453 in S-Link housing Obsolete with no Schneider Electric replacement Suggestions: Try Titan Products or Sontay DRT3651 Room temperature sensor exposed adjustment For CXR, CZT, KMC, MMC, IAC, MNN New part number: STR602/004604300 DRT3652 Room temperature sensor exposed + LED For MMC, IAC, MNN Obsolete with no Schneider Electric replacement Suggestions: Try Titan Products or Sontay DRT3801 Room temperature sensor fan switch On/off for CZU, MNN, IAC Obsolete with no Schneider Electric replacement Suggestions: Try Titan Products or Sontay DRT3851 Room temperature sensor fan speed switches As above plus medium and high Obsolete with no Schneider Electric replacement Suggestions: Try Titan Products or Sontay DU4301 Room sensor temperature For MNN & URC New part number: STR601/004604200 DUS4302 Room sensor temperature setpoint advanced basic sensor New part number: STR613/004604800 DUSF4351 Room sensor temperature setpoint adjustable fan auto/on/off fan override New part number: STR609/004604400 DUSF4352 Room sensor temperature setpoint advanced fan Auto/1/2/3 fan override New part number: STR610/004604500 DRTE2201 Active room detector Basic sensor Obsolete with no Schneider Electric replacement Suggestions: Try Titan Products or Sontay DRTE2801 Active room detector On/off Obsolete with no Schneider Electric replacement Suggestions: Try Titan Products or Sontay DRTE2851 Active room detector Off/low/medium/high Obsolete with no Schneider Electric replacement Suggestions: Try Titan Products or Sontay DRH7702 2% 0-10V DC humidity only For KMC, MMC, IAC, MNN New part number: SHR100/006902340 DRH7703 3% 0-10V DC humidity only For KMC, MMC, IAC, MNN New part number: SHR100/006902340 DRTH7712 2% 0-10V DC humidity with Satchwell NTC TEMP OUTPUT For KMC, MMC, IAC, MNN New part number: SHR100-T6/006902420 DRTH7713 3% 0-10V DC humidity with Satchwell NTC temperature output For KMC, MMC, IAC, MNN New part number: SHR100-T6/006902420 DDT DDT1701, DDT1702 and DDT0001 Duct sensor non-adjustable New part number: STD660 5126030000 Contact Details: Titan Controls: http://www.titancontrols.net/ Sontay Controls https://www.sontay.com

Issue Information not available in product documentation. Product Line Satchwell Sigma Environment Windows versions Cause Documentation not updated to show additional operating systems now supported. Resolution Sigma 4.0.8.57, as a front-end user interface, is supported on the following operating systems: Windows XP Pro Service Pack 3 Windows 7 Professional Windows 7 Ultimate Windows Server 2003 Windows Server 2003 R2 Windows Server 2008 Windows Server 2008 R2 Sigma 4.0.8 (build 80 – 89), as an engineering tool for Sigma when transitioned into SBO/EBO Sigma is supported on: Windows XP Pro Service Pack 3 Windows 7 Professional Windows 7 Ultimate Windows Server 2003 Windows Server 2003 R2 Windows Server 2008 Windows Server 2008 R2 Sigma 4.0.8 (build 104 onwards), as an engineering tool for Sigma when transitioned into SBO/EBO system Sigma is supported on: Windows XP Pro Service Pack 3 Windows 7 Professional Windows 7 Ultimate Windows Server 2003 Windows Server 2003 R2 Windows Server 2008 Windows Server 2008 R2 **1 Windows 10 **1 Windows Server 2012 **1 The additional operating systems support is only applicable when Sigma is part of a SBO/EBO installation. (This confirmation was provided to PSS by R and D).

Issue EcoStruxure Building Operation - Sigma logging does not work. Product Line EcoStruxure Building Operation, Sigma Environment Building Operation Enterprise Server Satchwell Sigma Cause Sigma logging has been transitioned to EcoStruxure Building Operation, but does not work. Resolution  The Procedure is as follows; Import the log data sets from Sigma to EcoStruxure Building Operation. Highlight "Log Sets" in the system tree under the Sigma Interface and select to "Send log sets" To confirm that the controller has started logging, select the appropriate controller, and choose "Diagnostics" and "Log Set Statistics" where you can see the statistics which include the log set/object details. To upload the logging, highlight the required log set and select "Retrieve Logged values". To review the uploaded data, highlight the required log value and view it as required Once that the logging in the Sigma controllers is working correctly to EcoStruxure Building Operation, logging from the Sigma server should be disabled.

Issue Sigma Transition issues upon Data Import the Sigma Server fails Product Line EcoStruxure Building Operation, Satchwell Sigma Environment Sigma Building Operation Enterprise Server Cause Sigma server fails when an EBO data import is initiated. Resolution It is important that the Sigma Database is checked with the Doctor utility (found in SigmaX) before a Sigma transition into EBO is undertaken. Longtext - Longtext file contains 'mandarin' type characters - probably from previous BAS/Sigma upgrades. If the file contains these, then Longtext has probably not been used in the past or currently. Delete File, it will self re-create. Shorttext - Shorttext contains an incorrectly formatted entry. Find entry and correct. To find, delete 1 -250, if it continues to fails, the entry in question will be in the range 251 to 500 and keep halving until the entry is found. Index A errors - index contains a looping segment, where the page references itself. Correct index as necessary. Index A errors - page is referenced more than once, i.e. the index page can be opened via two (or more) routes. Correct Index as necessary. Note: the Index should be checked with SigmaX before a transition. Object corruption - open object in Sigma, if it fails to open, then correct by whatever means that is required. Note, Sigma server will fail at a point during the Data Import. Log Sets - Fail to import log sets. To find, in Sigma, locate the logset.rec in the c:\sigma\data\server...folder file, take a copy. In Sigma, delete 50% of the log sets and try the import again. If it fails, delete another 50% and repeat. Or if it succeeds, then the issue may lie in the 50% of log sets originally deleted, re-instate these using the copied logset.rec file and try again by deleting the other 50% and so forth.

Issue Faulty operation of BMS equipment due to electrical interference from other equipment can be difficult and costly to identify and fix.  Guidance is required for the best installation practices to minimize the source of the interference and to protect against it when it occurs. Product Line Andover Continuum, EcoStruxure Building Operation, Field Devices, OTHER, Satchwell MicroNet, Satchwell Sigma, TAC IA Series, TAC Vista Environment All electrical equipment Cause Poor installation can cause equipment to generate high and low-frequency electromagnetic interference that can disrupt the operation of other systems. Resolution Schneider Electric has produced a document Practical Installation Guidelines which discusses the theory and offers practical guidelines to protect against and minimize the generation of, electromagnetic interference.