Issue Poor communications, communications failure or packet being corrupted Product Line Andover Continuum,EcoStruxure Building Expert,EcoStruxure Building Operation,Satchwell MicroNet,Satchwell Sigma,TAC INET,TAC Vista Environment Communications networks, BACnet MSTP, LON FT10, Infinet, Modbus RTU, Ethernet EMC (Electromagnetic compatibility) VSD Variable Speed Drive, VFD Variable Frequency Drive, Inverter Drive Cause Electrical Interference from Inverter (variable speed drives or VSD) Radiated or Induced RFI (Radio Frequency Interference) Resolution A VSD has the potential to create a large amount of electrical noise, to avoid causing issues it is vital they are installed as the manufacturer's instructions.  (Other devices also have this potential) Our systems are often used to control VSDs on fan motors, so if poor communications is found during the commissioning process, then try stopping all the fans in the area then re-testing the communications. A recent example was seen where LON FT10 communication was working ok until some VSDs were started, at this point LON devices and Object went offline intermittently. When all the VSDs were stopped the communication become completely stable. It was then possible to find which VSD was causing the problem and correct the VSD installation. In this case a LON analyzer would also have helped diagnose the issue.

Issue A specification for a power meter states that it provides KYZ pulse outputs. What is a KYZ pulse output? Product Line All Product Lines Environment Utility Meter with KYZ pulse outputs Cause Some meter specification sheets may state that the device outputs KYZ pulses. Resolution KYZ is a designation given to a relay used to create pulses for electrical metering applications. It is commonly a Form C relay (SPDT). The term KYZ refers to the contact designations: K for common, Y for Normally Open, and Z for Normally Closed.

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 SigmaX - checking for duplicated segment and object names prior to EBO transition Product Line Satchwell Sigma Environment SigmaX Cause Checking for duplicated segment and object names prior to transitioning Sigma to EBO. Resolution With EBO, names cannot be duplicated within the same folder or segment, however in Sigma they could be, it was only the mnemonic that had to be different. When Data Importing into EBO, duplicated names are revised by adding a postfix to the duplicated name e.g. if there are two ‘room temperature’ then the 2nd one is revised to ‘room temperature2’ so that the Data Import can continue to proceed. In SigmaX, a report can be generated that will itemize any duplicated index or object names. Within SigmaX, these duplications can be renamed to a name of your choosing. Once, this is done, the Data Import will use the new names. This video with SigmaX the 2nd one of three videos, the 1st SigmaX Quick Help Video will check for database errors primarily 'A' errors. When launching the SigmaX application, see the Knowledge Base articles for Side by Side errors and errors regarding missing SigmaX files should they occur.

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 SigmaX checks prior to transition into EBO Product Line Satchwell Sigma Environment SigmaX Cause Doctor checks required prior to transitioning Sigma to EBO. Resolution Preliminary checks steps to be taken to check a Sigma database is error free prior to a transition to EcoStruxure Building Operation (EBO). This video will demonstrate how to use SigmaX, but it will not resolve any errors in the database. Any database errors can have been caused by a number of different reasons and will provide a report listing the errors so that they can be corrected. This video with SigmaX is in two parts, the 2nd SigmaX Quick Help Video will check for Duplicated Names. When launching the SigmaX application, see the Knowledge Base articles for Side by Side errors and errors regarding missing SigmaX files should they occur.

Issue A backup device is required for an IC3-Modbus. Product Line Satchwell Sigma Environment Sigma IC3-Modbus Cause Is it possible to use two IC3-Modbus controllers to interrogate one Modbus slave device? Resolution This configuration is acceptable where TCP is used, it cannot be used for RS485 RTU communications. Each Modbus device on a TCP network must have a unique ID but everything else (such as register address, type, Gateway IP address) may be identical. In a RS485 RTU modbus environment, there can only be one master device. IC3-Modbus datasheet

Issue Firewall issues when trying to reach out to the activation server for a license Product Line EcoStruxure Building Operation, Satchwell Sigma, TAC Vista Environment Licensing Firewall Cause If the corporate network has a very restricted firewall policy/ rules, the port needed to reach and activate a license may be blocked. Note: The same license server is used for StruxureWare, Sigma and Vista software licenses. Resolution Open both (Http) Port 80 and (https) Port 443 for the server hosting the license server, and ensure that the routing paths to the Flexnet Licensing server URL's are all fully open. There are URL should be opened on the site, and it is: Licensing server URL: https://schneider-electric.flexnetoperations.com If the site has issues with the non secure comms of the old server or the communications forward between the previous and new server, there is a tool available to configure SBO to only use the new server. See the Exchange Community article for the download: SBO License Setup Note: From SBO V2.0 only the new licensing server will be required.

Issue Need to capture steps taken to reproduce a problem or a solution Product Line Andover Continuum, EcoStruxure Building Expert, EcoStruxure Building Operation, Field Devices, OTHER, Satchwell MicroNet, Satchwell Sigma, TAC IA Series, TAC INET, TAC Vista Environment Windows 7 Windows 10 Windows Server 2008, 2012, 2016 Cause A series of screen captures will help to demonstrate the steps needed to reproduce a problem or a solution. You can use this tool to capture the steps you take as a problem occurs and send the output to someone so they can see a screenshot of each step. Resolution In Windows click on the Start menu button  Type "PSR" Windows 7 Windows 10, 2012, 2016 Open the Problem Steps Recorder Windows 7 Windows 10. 2012, 2016 Click Start Perform the desired tasks Click Stop Choose a location to save the file output The .zip file will contain a .mht file which can be opened in a web browser The screenshots will appear in order  This will be followed by a detailed output of keystrokes and mouse movements. For additional information please refer to Microsoft webpage on this topic: Record steps to reproduce a problem 

Issue When SigmaSvr is started for the first time after a Sigma 4.08 install, a Windows error 1067 error appears Product Line Satchwell Sigma Environment Satchwell Sigma Software (Sigma 4.08) Cause If SigmaSvr is started for the first time after a Sigma 4.08 install without the USB dongle plugged in the Sigma Server may fail to start. As a result, a dump file will be created in the Sigma directory after each start attempt. Resolution Before starting SigmaSvr, plug the Sigma USB dongle in. Let the driver install. Start the Sigma Server Delete the .dmp files in the Sigma directory.

Issue The following errors are seen when trying to run SigmaX, RegSigmaX or SigView.  The application has failed to start because its side-by-side configuration is incorrect. Please see the application event log or use the command-line sxstrace.exe tool for more detail.  Application event log: Activation context generation failed for "C:\ SigmaX \Bin\RegSigmaX.exe". Dependent Assembly Microsoft.VC80.MFC, processorArchitecture =" x86 ", publicKeyToken =" 1fc8b3b9a1e18e3b ",type=" win32 ",version="8.0.50727.762" could not be found. Please use sxstrace.exe for detailed diagnosis. Product Line Satchwell Sigma Environment SigmaX 7.0.6 on Windows 7 32-bit SigmaX 7.09 on Windows 10 64bit SigView Cause Microsoft Visual C++ 2005 redistributable  has not been installed. It appears that SigmaX requires this version to run. Resolution Either the Microsoft C++ 2005 is not installed, or if it is, then the Service Pack 1 (SP1) is required to be installed. This can be checked under the Windows 'Apps and Features'. Install Microsoft Visual C++ 2005 SP1 Redistributable Package (x86). In some cases, Microsoft Visual C++ 2005 SP1 Redistributable Package Security Update (x86) is required to resolve the issue. The 32bit (x86) version should be installed if installing Microsoft Visual C++ 2005 SP1 does not fix the problem. 

Issue Sigma and Windows Server 2012 Product Line Satchwell Sigma Environment Sigma 4.08 Windows Server 2012 Cause Is Sigma 4.08 supported on windows Server 2012 Resolution No version of Sigma is supported on a Windows Server 2012 platform except: Sigma 4.08 can only be installed on Windows Server 2012 when the software is used as a transition into EcoStruxure Building Operation ( EBO ) and used with the correct version of transition component. For full details of Sigma 4.08 versions, build numbers and operating systems supported, see What operating systems is Sigma 4.08 supported to run on?.

Issue What speed and type of comms do Sigma controllers communicate using Ethernet. Product Line Satchwell Sigma Environment Sigma V53 type controllers e.g. UNC496/596, UNC532, IC, DNN ARM7 type controllers e.g. UNC696/796, UNC632, IC3, DNN3 Cause What speed and type of comms do Sigma controllers communicate using Ethernet. Resolution V53 type controllers communicates at 10MB and is half duplex. ARM7 type controllers communicates at 100MB and is half duplex. 

Issue BAS terminal receives system messages from a PIU with no explanation and is asked to contact Product Support. For example "Message No. 19920 not available. Please contact Product Support" Product Line Other, Satchwell Sigma Environment BAS PIU  and Sigma Pre-release 4 System Messages BAS (1 - 10499) SNP Gateway ( 10500-10999 ) CHUBB Remote Access Management ( 11000-11499 ) CEGELEC ( 11500-11999 ) OTIS   ( 12000-12499 ) CCURE ( 12500-12999 ) WORMALD ( 13000-13499 ) ASIC ( 13500-14999 ) SIMPLEX ( 14000-14499 ) CARRIER DATAPORT  ( 14500-14499 ) EXPRESS LIFT ( 15000-15499 ) CARDKEY ( 15500-15999 ) Mitsubishi ( 16000-16499 ) Liebert ( 16500-16999 ) IMPACC ( 17000-17499 ) YORK ( 18000-18499 ) AUTOFLAME (19000 - 19100) AUTOMETERS (19100-19199) MITSUBISHI PLC (19200 - 19299) SIEBE MICRONET (19400 - 19499) CROWCON (19500 - 19599) MNI (MicroNet Interface) ( 19700-19799 ) Colt OPV ( 19800-19899 ) MODBUS ( 19900-19999 ) MCQUAY (20000 - 20199) FIDELIO (20200 - 20299) ATLAS COPCO ( 20301-20399 ) UNIFACT PRO ( 20500-20599 ) Cause Due to a size limit (64Kb) not all the PIU error messages are included in the Messages.ini file. Resolution A more complete list of the of BAS error messages can be found here. Copy the appropriate section Paste into the C:\Bas\Data\Messages.ini file into the correct sequence as by message number The maximum size of the message.ini file must not exceed 64Kb Example:

Issue Epson LQ-300+ II Printer does not work correctly in Windows 7 when used as an Alarm printer. Epson LQ-300+ II fails to print. Product Line Satchwell Sigma Environment Epson LQ-300+ II Sigma Windows 7 64-bit Cause When the printer is set to Continuous Print, alarms are spooled but the printer fails to print. The printer only prints if a change is made within Sigma > Alarm Manager > Configure > Live Printers. Resolution In this example the Epson LQ-300+ II printer was used. Remove the printer from the Devices and Printers window. Re-install the printer by "Add Printer." Use the CD that came with the printer and load the Windows XP 32-bit driver. Do not use the Windows 7 driver. Note: the printer name will be slightly different! Set the Printer Properties > Advanced tab > Print Processor to "Raw [FF auto]" Set the Printer to "Spool directly to the printer" Set the paper, fanfold or A4. Shut down the Sigma Client and Sigma Server, delete the printerconfigsnn.rec file in C:\sigma\data folder. (This will remove the old printer name in Sigma with the Windows 7 driver and avoid any confusion) Start Sigma Server and the Sigma Client, in Alarm Manager, highlight and re-assign the printer, set to continuous, tick LF and CR boxes.

Issue ARCNET Cable Requirements. Product Line Satchwell Sigma Environment Sigma 4.05 and earlier versions V53 and ARM7 Processor Boards Cause Sigma ARCNET Network cabling advice. Resolution The following Sigma Cabling Guide should be followed when installing an ARCNET network for Sigma:  Sigma Cabling Guide 2.2 Network biasing and earthing arrangements will be required and further information about cabling can be found in the following guides: For V53 Processor Boards (UNC496, 596, UNC532, DNN and IC integration controllers): Sigma Configuration Guide - Chapter 26a For ARM7 Processor Boards (UNC696, 796 & UNC632): Sigma Configuration Guide - Chapter 32; Sigma Configuration Guide - Chapter 31 For ARM7 Processor Boards (DNN3 Decentralised Network Node): Sigma Configuration Guide - Chapter 33 For ARM7 Processor Boards (IC3 Integration Controller): Sigma Configuration Guide - Chapter 34

Issue Doctor and SigmaX Index edit password Doctor and SigmaX Binary file edit password Environment BAS Doctor Sigma SigmaX Doctor Cause Need a password that allows access to edit an index or binary file. Resolution IE is the password for index edit. BE is the password for binary file edit. These passwords are not case sensitive. Either IE/BE or ie/be can be used.

Issue What batteries and PSU cards can be used in a x96 Controller? Product Line Other, Satchwell Sigma Environment S-x96-STD S-x96-BAT Sigma BAS Cause What batteries and PSU cards can be used in a x96 Controller or BAS controller? Resolution See TPA-LOND-08-0017.02 S-ARM7-BAT is the Sigma UNC PCB Battery Spare for the ARM7 CPU Board. The battery itself is a Ni-MH 2-Button Cell, 2.4v, 80mAh. S-V53-BAT is the Sigma UNC PCB Battery Spare for the V53/V25 CPU Board. The battery itself is a Ni-MH 3-Button Cell, 3.6v, 150mAh. S-X96-BAT is the Sigma UNCx96 Hi-Capacity Battery for the x96 products. The battery itself is a Ni-MH D-Cell pack, 10.8v, 5Ah (12-Hour). S-X96-STD is the Sigma UNCx96 Standard Capacity Battery for the x96 products. The battery itself is Ni-MH AA-Cell pack, 10.8v, 1500mAh (1.2-Hour) Due to UK legislation in 2006 NiCad batteries could not be used and changes were made where NiMh batteries are used instead 2016-01-22: - Confirmed both the S-X96-STD and the S-X96-BAT battery packs are currently available. Note: Schneider sales do not understand dashes, so when asking for price and availability you need to remove the dashes or they will not find the parts. Specification Sales need Price provided by sales S-X96-STD SX96STD £ 198.05 S-X96-BAT SX96BAT £ 541.19 General Rules for battery replacement and PSU card replacement/modification are: 11/2008 to present - The controller was originally shipped with the NIMH battery and PSU card suitable for charging the NiMH battery. These PSU cards are suitable for charging both NiMH and NiCad batteries. 04/2004 to 10/2008 x96 BAS/V53 PSU cards - The PSU card have to be replaced to fully charge NiMH batteries. 1999 to 03/2004 x96 BAS/V53 PSU cards - The PSU card have to be replaced to fully charge NiMH batteries. Pre 1999 BAS PSU cards - 2 resistors are required, the TPA explains how. The resistors are shipped with the NiMh battery. Note: If upgrading to Sigma then the Upgrade kit S-x96-UPKIT should be used which includes a new PSU card.

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

Issue How to correctly configure the Live Alarm Printer filtering in Sigma Product Line Satchwell Sigma Environment Sigma release 4.05 SP1, SP2 and SEB Cause General configuration advice Resolution The Sigma Live Alarm Printer filters provide the option of which alarms to print, and which to print immediately. It is only possible to select one filter, per function per printer. In the Sigma Alarm Manager select the "Configure" option, and then select "Printer Filters" Create a maximum of two printer filters, one to "Filter Alarms to Printer" and the second to "Filter Alarms to print now". In reality only one filter might be necessary, but this will depend on site printing requirements. In the Sigma Alarm Manager select the "Configure" option, and then select "Live Printers" Select a "Live Alarm Printer" from printer list. Select a filter in the "Filter Alarms to Printer" option. Select a filter in the "Filter Alarms to print now" option. This is the configuration completed for this printer. If another printer is also required to print "Live Alarms" then repeat the above process again, making sure that the printer is highlighted first.

Issue The Remote Alarm Manager sends a message to the recipient indicating that an alarm has been inactivated. The screen shot below shows how a typical message will appear on the receiving mobile phone. Product Line Other, Satchwell MicroNet, Satchwell Sigma, TAC Vista Environment Remote Alarm Manager version 1.2 Cause An alarm message is generated, and the Remote Alarm Manager processes it in the normal way. After three days and at midnight, the Remote Alarm Manager will send a inactivation message to the on-call recipient, indicating that this alarm has been inactivated. Resolution This is not a fault with the system, it is operating as designed. When a new alarm is received by the Remote Alarm Manager, it is acted on in the way the configuration dictates. If the alarm remains on the system, without being retransmitted, then after three days the inactivation takes place. The 3 days is the default setting and can be changed if required.

Issue When SigUpgrade is run at Release 4.08, a DeviceCnf.rec file that was created at Release 4.04  (as opposed to being the result from a SigUpgrade from Release 4.03) fails to upgrade to 4.08 correctly, and leaves the file unchanged in the 4.04 format. Product Line Satchwell Sigma Environment Sigma Cause Occasionally, at Release 4.04 when a new DeviceCnf.rec file is created it is tagged "Version 0" instead of the correct "Version 1" Resolution The DeviceCnf.rec file can be still be upgraded to Release 4.08 but by completing an intermediate upgrade from Release 4.04 by any one of following releases: Sigma Release Build Number Release 4.05 3.42.34 Release 4.05 SP1 3.42.43 Release 4.05 SP2 3.42.48 Release 4.05 SEB 3.43.18 Release 4.06 3.44.14 Release 4.06 SP1 3.44.16 Release 4.06 SP1 3.44.18 Release 4.07 3 45 48 Release 4.07 SP1 3 45 51 Release 4.07 SP2 3 45 58   Then finally upgrade again to Release 4.08.57 before continuing with the upgrade..