Issue Spare Satchwell valve gland kit & grease, reconditioned 'O' rings and lug nuts options. Satchwell packing kits, Satchwell gland kits, Satchwell stuffing glands. Product Line Field Devices Environment Satchwell valve Gland kits Packing kits Stuffing Gland Part Numbers: 0617-9-410, 0617-9-411, 0617-9-412, 0617-9-413 0618-9-210, 0618-9-510, 0618-9-511, 0618-9-512 0623-9-201 0626-9-203, 0626-9-204, 0626-9-310, 0626-9-311, 0626-9-312, 0626-9-313 0667-9-201 Cause Spare item part numbers Resolution   Valve(size) Part No Description Stock 1/2"…..1" 0626-9-313 LUG NUT AVAILABLE   0626-9-312 LUG NUT AVAILABLE   0617-9-410 RECON KIT "O" RINGS & TOOL AVAILABLE MB 1 1/4" 0617-9-411   AVAILABLE MB 1 1/2" 0617-9-412   TOOL AVAILABLE MB 2" 0617-9-413   AVAILABLE MBF 65mm 0618-9-510   AVAILABLE MBF 80mm 0618-9-511   AVAILABLE MBF 100mm 0618-9-512 RECON KIT "O" RINGS AVAILABLE MEU, FEU & VEU 0623-9-201 REPLACEMENT GLAND KIT & GREASE OBSOLETE MJF 0626-9-203 REPLACEMENT GLAND KIT & GREASE AVAILABLE MZ 1"..2" series 3       VJF       VSF 15..25mm       VZ 0.5" .. 2" series 1 & 2               MZX 0.5" .. 2" 0626-9-204 REPLACEMENT GLAND KIT & GREASE AVAILABLE VZX 0.5" .. 2"               MZ 0.5" .. 2" series 1 0626-9-310 REPLACEMENT GLAND KIT & GREASE AVAILABLE VZ 1" .. 2" series 1               MZF 65 .. 150mm 0626-9-311 REPLACEMENT GLAND KIT & GREASE AVAILABLE VZF 65 .. 150mm series 1               VSF 32 .. 50mm 0667-9-201 REPLACEMENT GLAND KIT & GREASE AVAILABLE VV 0618-9-210 RECONDITIONING KIT AVAILABLE Download the drawing for the MB 0617-9-410 (0.5" to 1") Download the drawing for the MBF 0618-9-511 (80mm) Download the drawing for the MZX 0626-9-204 Download the drawing for the VZ/MZ 0626-9-310

Issue SmartStruxure integration with BMS, CRM, SQL, SCADA, PLC, HMI, TouchPanels, Citrix, or UNIX types of systems Product Line EcoStruxure Building Operation Environment SmartStruxure Site Cause Can SmartStruxure integrate or be used with other BMS, CRM, SQL, SCADA, PLC, HMI, TouchPanels, Citrix, or UNIX types of systems? Resolution Integration and use with third party systems is sometimes possible with SmartStruxure. The question is how much is the third party system willing to integrate or be used with SmartStruxure? OnQ, which is a proprietary CRM or Contact Resource Management built by the Hilton company and deployed to more than 2,100 hotels worldwide, is using the same communication protocol than Micros Fidelio/Opera so you can use a Bacnet to Fidelio gateway. Fingi Operational Services(FOS) All features of the Fingi Mobile Platform operate from within FOS server. There has not been an integration with FOS for an example. We have several references with these systems (Hilton Manchester, Hilton Copenhagen, Hilton America, ...) - some information are in the Solution Toolbox/Hotel under BMS to PMS integration. Some gateway examples are available: Hotels Gateway - Lonbox PFG4000 is a Fidelio Lonworks® hotel booking gateway The Lonbox PFG4000 Users Guide IntesisBox BACnet gateway catalogue - designed to allow supervision and bidirectional control of all the parameters and functionality of systems and equipment with KNX, ModBus, LonWorks and Fidelio systems from BACnet/IP networks IntesisBox BACnet Server – Fidelio IP - Datasheet Citrix - Building Operation is not Citrix verified, nor has it been put through the process of Citrix Ready. The Building Management WorkStation and WebStation have not been tested on a Citrix platform. One solution would be to inquire through your local sales/marketing channel to see if this is something they want to pursue with the business case which has been put together. Integration is a proposed TVDA for 2013 - to be confirmed depending on resources on StruxureLab.

Issue Integration to the Veris H80xx Entercept power meter with the Xenta 5/7/9xx and Modbus RTU Environment Xenta 511, 527, 701, 711, 721 (5.1.5 up) Xenta 731, 913 (all versions) XBuilder Veris H80xx Entercept Power Meter Cause Integration instruction and programming example for integration to the Veris Entercept power meter. Resolution Please use the following .dev files as a starting point and a guide to the integration of a 100 amp or 200 amp Veris Entercept meter. This .dev file contains a set list of registers that PSS assumed would be seen as critical and important to the integration process. If any other data is needed please see this supported document to make the necessary changes to the modbus mapping or this supporting document for data scaling changes. If mapping for larger amp meters is needed, please contact product support.   100 AMP .dev file 200 AMP .dev file   To use these files in XBuilder please follow these steps: Extract the .dev file from the .zip file in the link above, and place it on the harddrive. In Xbuilder, right click on the Modbus Master device and choose Add Device Browse to the needed .dev file and click Open. Rename the newly added device to a unique name within the Modbus Master network.   Disclaimer: This device template is intended to provide a starting point for an integrator, and is in no way written to be the mandatory points list for your integration effort. Product Support has written this device template in an effort to give our customers a starting point and solid example of how to develop a device template for the above product. The integrator will be responsible for any additions or modifications to this device template.  

Issue In firmware 2.19.1, the MPM Modbus Generic Driver feature has been introduced with little to no explanation on how to use it Product Line EcoStruxure Building Expert Environment Multi Purpose Manager (MPM) Cause Sample CSV file not available on MPM Resolution In order to establish communication with a modbus device, a CSV (comma separated values) file of a certain format must be uploaded to the GMC1 object. Once uploaded the file will be visible in the drop-down list.   Requirements and Limitations Only holding registers are supported at this time (Modbus function codes 3 and 16) The CSV file mast be renamed Modbus_[label].csv where label is the name of the device or a label to help identification (e.g. Modbus_SE8000.csv) Write only registers are not supported It is not possible to use a more than 32 bits variable in write mode It is not possible to leave a blank column in CSV register configuration file except the last column It is not possible to create a continuous register table using different variable types   The CSV file must have the following format: modbus_addr,register_type,label,access,factor,unit Download example here (The text file can be viewed in a text editor but its extension must renamed to csv before uploading it to the MPM) modbus_addr: modbus register address (Decimal number between 1 and 65535) register_type: "uint" (UI16) "int" (SI16) "float" (F32) "ulong" (UI32) "int64" (SI64) "uint64" (UI64) label: name for this register, this will also be used to populate the associated object in the MPM Alphanumeric value between 1 and 32 characters. No special characters (comma, simple quotes, double quotes,%,&,@,#, etc.) access: read or read_write. read will only poll register based on driver availability (30 seconds typical) read_write will monitor for a change of value of the associated point, which will then generate a write event to the device with this new value factor: multiplier / gain Float number, typical between 0.001 and 65535. Typical use are factors of 10: (1,10,100, etc) This factor is multiplied when reading and is divided when writing.     unit: BACnet unit, used for the object units in the MPM. Number from the following list: 169 ampere square meters 3 Amperes 167 amperes per meter 168 amperes per square meter 55 bars 20 BTUs 50 btus per hour 117 btus per pound 24 btus per pound dry air 179 candelas 180 candelas per square meter 118 centimeters 60 centimeters of mercury 57 centimeters of water 79 cubic feet 84 cubic feet per minute 142 cubic feet per second 80 cubic meters 135 cubic meters per hour 165 cubic meters per minute 85 cubic meters per second 105 currency1 114 currency10 106 currency2 107 currency3 108 currency4 109 currency5 110 currency6 111 currency7 112 currency8 113 currency9 25 cycles per hour 26 cycles per minute 70 days 65 degree days celsius 66 degree days fahrenheit 90 degrees angular 62 degrees celsius 91 degrees celsius per hour 92 degrees celsius per minute 64 degrees fahrenheit 93 degrees fahrenheit per hour 94 degrees fahrenheit per minute 63 degrees kelvin 181 degrees kelvin per hour 182 degrees kelvin per minute 14 Degrees Phase 120 delta degrees fahrenheit 121 delta degrees kelvin 170 farads 33 feet 77 feet per minute 76 feet per second 38 foot candles 28 grams of water per kilogram dry air 155 grams per minute 154 grams per second 133 hectopascals 171 henrys 27 hertz 51 horsepower 71 hours 158 hundredths seconds 81 imperial gallons 86 imperial gallons per minute 32 inches 61 inches of mercury 58 inches of water 183 joule seconds 16 Joules 127 joules per degree kelvin 128 joules per kilogram degree kelvin 23 Joules/Kilogram Dry Air 147 kilo btus 157 kilo btus per hour 39 kilograms 186 kilograms per cubic meter 44 kilograms per hour 43 kilograms per minute 42 kilograms per second 129 kilohertz 122 kiloohms 17 Kilojoules 151 kilojoules per degree kelvin 125 kilojoules per kilogram 149 kilojoules per kilogram dry air 75 kilometers per hour 54 kilopascals 9 Kilovolt Amperes 12 Kilovolt Amperes Reactive 19 Kilowatt Hours 48 kilowatts 6 KVs 138 kw hours per square foot 137 kw hours per square meter 82 liters 136 liters per hour 88 liters per minute 87 liters per second 36 lumens 37 luxes 148 mega btus 130 megahertz 126 megajoules 152 megajoules per degree kelvin 150 megajoules per kilogram dry air 140 megajoules per square foot 139 megajoules per square meter 10 Megavolt Amperes 13 Megavolt Amperes Reactive 146 megawatt hours 49 megawatts 123 megohms 31 meters 164 meters per hour 163 meters per minute 74 meters per second 166 meters per second per second 78 miles per hour 2 Milliamperes 134 millibars 30 millimeters 59 millimeters of mercury 162 millimeters per minute 161 millimeters per second 145 milliohms 159 milliseconds 124 millivolts 132 milliwatts 72 minutes 68 months 7 MVs 153 newton 160 newton meters 187 newton seconds 188 newtons per meter 95 no units 172 ohm meters 4 Ohms 97 parts per billion 96 parts per million 53 pascals 131 per hour 100 per minute 101 per second 98 percent 143 percent obscuration per foot 144 percent obscuration per meter 99 percent per second 29 percent relative humidity 56 pounds force per square inch 40 pounds mass 46 pounds mass per hour 45 pounds mass per minute 119 pounds mass per second 15 Power Factor 102 psi per degree fahrenheit 103 radians 184 radians per second 104 revolutions per minute 73 seconds 173 siemens 174 siemens per meter 116 square centimeters 1 Square Feet 115 square inches 0 Square Meters 185 square meters per newton 175 teslas 21 Therms 22 Ton Hours 41 tons 156 tons per hour 52 tons refrigeration 83 us gallons 89 us gallons per minute 8 Volt Amperes 11 Volt Amperes Reactive 5 Volts 176 volts per degree kelvin 177 volts per meter 18 Watt Hours 47 watts 189 watts per meter per degree kelvin 34 watts per square foot 35 watts per square meter 141 watts per square meter degree kelvin 178 webers 69 weeks 67 years

Issue Can not find Controller Web Server documentation on the web sites. Product Line Andover Continuum Environment Continuum Custom Web Server pages Infinity Web Server Cause Unable to find Continuum Web Server documentation. Resolution The attached Web Server chapter is extracted from a Plain English programming guide.  The Infinity Web Server User Guide is also relevant to Continuum. Also an example program can be seen in How to create custom web pages in the CX controller using Plain English.

Issue Using provisioning Niagara to schedule (automated) ENC station backup Product Line TAC IA Series Environment I/A Series G3 (AX) version 3.3 and above Cause The station in an ENC (Enterprise Network Controller) can be copied to the ENS (Enterprise Network Server) computer for backup. This can be done by a user using the ENC's Platform Station Copier. There is a need to have an automated process to back up the ENC's station periodically. Resolution Use provisioning Niagara and configure an automated station backup. Provisioning Niagara means an administrator can configure the Enterprise Network Server automation of the following: one or more pre-defined tasks (station backups, install software, update licenses, and copy files) against one or more (potentially many) stations in its Niagara Network done from the Enterprise Network Server in a way where results are recorded and can be referred to later. Refer to this document for a summarized procedure. You should refer to the technical document 'Niagara Ax 3.5 Provisioning Guide for Niagara Networks' for detailed information on using provisioning in Niagara. This document is included with the installation of the I/A Series G3 software and it is located in '\niagara\niagara-3.x.xx\docs\docProvisioningNiagara'. 

Issue Distinguishing whether an xDriver-enabled commport on a controller is set for Modbus RTU or Modbus TCP/IP. Environment CX9900, CX9940 CX9680 bCX4040 Cause How does one know if the xDriver-enabled commport on a controller is for Modbus RTU or Modbus TCP/IP? Resolution Open the controller editor and go to the Options tab. At a minimum the Modbus RTU XDriver, like all Xdrivers, requires Bit 0 for the commport be Xdriver enabled. The most common example would look like this: Xdrvr Commx: 00000001(####). In the above example x = commport number. The four digit number in parentheses indicates whether an Xdriver file is loaded into the port. If it is 0000 then no Xdriver file is loaded into the port. A number such as 4767 corresponds to "Xdriver Valid" line at the end xdriver XDR file. You can edit the XDR file with a text editor and go to the bottom to see this.   In addition to Bit 0 being enabled for the commport, the Modbus TCP/IP Xdriver requires Bit 3 to be Xdriver enabled.  A common example of this would look like this: Xdrvr Commx: 00000009(####). The 00000009 is in hexadecimal format -  converting this to an 8-bit binary number you get 00001001. The furthest right bit is Bit 0 and the 4th from the right is Bit 3. Both are set to 1 which means they are Xdriver enabled. For a further explanation see page 15 of the linked Modbus TCP/IP Xdriver User Guide.   Note: Since Bit 0 is enabled in both of the above examples, the Modbus RTU Xdriver will work on either. But only the second example will load the Modbus TCP/IP Xdriver.      

Issue Create a true PWM output from a Xenta programmable controller using a DOPU block in Menta. Environment Menta Cause Menta does not have a built in PWM functionality, so to control a PWM actuator, some additional programming is required to utilize a DOPO block as desired. Resolution Click the image above to download the Menta Macro. Load the macro into the Menta file. The HFB takes a percent signal input and outputs the required values to control a DOPU block, which in turn will pulse the physical DO on the Xenta controller to control a PWM actuator.

Issue Site looking for a sample program to monitor the thermostat and alarm if it stops updating the temperature. Environment AS PE Script MPM EnOcean Cause Documentation Resolution Write a PE script to monitor the temperature and alarm as necessary. Click HERE for sample PE Script program.

Issue Is it possible to see how many simultaneous users are logged in via for example Webstation, Workstation and iPad to an ES? Product Line EcoStruxure Building Operation Environment Building Operation License Administrator Cause This information is not saved in any file or any object in the ES. Resolution Within the Enterprise Server this is not possible. An enhancement has been written for this function to be implemented in the future. However, it can be achieved by using the FlexNet Licensce Administrator, see Number-of-client-licenses-used Knowledge Base article.

Issue Network administrator needs a document explaining the impact of GCM NIM communications on his Ethernet network. Environment GCM-86xxx with GCM-ETH-001 network interface Cause Customer wants to know impact of adding GCMs to his Ethernet network. Resolution GCM NIM configuration information and general Ethernet networking information is in the "NIM Networking and Configuration Guide", F-25955-4.  This document is available via the Publication Zone on iPortal. Bulletin 96-42, provides answers to frequently asked questions regarding the GCM NIM communications. NOTE: This information is based on the use of firmware version 11.2T in the GCM-NIM-001 interface.

Issue The technical documentation for the RP-C-EXT-DALI-M-PD states a guaranteed DALI current limitation of 64 mA. It is unclear whether this limitation applies per DALI port or to the controller as a whole. Product Line EcoStruxure Building Operation. Environment RP-C-EXT-DALI-M-PD. Cause The product documentation lists two current values: 250 mA: Theoretical DALI standard maximum bus current. 64 mA: Guaranteed current output of the RP-C-EXT-DALI-M-PD module. This discrepancy has led to confusion regarding whether the 64 mA applies to each port individually or to the total output across all ports. Resolution The RP-C-EXT-DALI-M-PD module provides a total guaranteed DALI current of 64 mA, which is shared across all four DALI ports. Key points: If only one port is used, it may utilize the entire 64 mA. If multiple ports are used, the combined current draw must remain within the 64 mA limit. This limitation is enforced by hardware and cannot be exceeded, even with external devices. Use of external DALI repeaters with integrated power supplies (e.g., Helvar 405) is not supported due to certification constraints and potential conflicts with the module’s internal power supply. The 250 mA figure refers to the DALI standard, not the module’s actual output capability. As illustrated in the attached diagram, all four DALI ports are powered by a single internal DALI driver, which is the source of the 64 mA limitation.    

Issue Users encounter the following error when launching Device Administrator: “The following error(s) occurred while reading the server list file: - The site-specific server password could not be loaded. It will be set to the default password ‘admin’. - One or more SSH public keys are invalid.” Additionally, devices may show: - “SSH public key fingerprint changed!” - “Wrong logon” errors for connected Servers  Product Line EcoStruxure Building Operation Environment EcoStruxure Building Operation Device Administrator Access Method: Remote Desktop Multiple Windows user accounts or sessions 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. Cause This issue is caused by shared use of a single server list file across multiple Windows user accounts or sessions. When another user opens Device Administrator—even without modifying or saving the server list—the SSH keys become invalid due to security hardening measures. This behavior is by design to prevent unauthorized access and is part of Schneider Electric’s cybersecurity strategy. Resolution Recommended Workflow  Create and Save the server list on the original user account or PC. Export the server list using the built-in export feature in Device Administrator. Import the server list on the target user account or PC. ⚠️ Do not copy the XML file manually between users or systems. This will invalidate SSH keys and passwords due to security restrictions. Best Practices Use unique filenames when exporting server lists (e.g., include user initials). Avoid using shared server list files across users or sessions. If the server list becomes corrupted or invalid: Re-import the previously exported working server list. If unavailable, recreate the list and export it immediately for future use. Additional Notes This issue can occur even if only one user accesses the system, especially if the server is accessed via Remote Desktop and multiple sessions are involved. The server list file ( Servers.xml ) should always be managed through the export/import functionality to preserve encryption and key integrity. Affected devices may require re-authentication or re-adding if the server list is corrupted and cannot be recovered. References Import and Export a List of Field Server Workflow

Issue Cisco switches are reporting connected Sigma devices using more than one MAC address. This results in error alarms such as: %PORT_SECURITY-2-PSECURE_VIOLATION: Security violation occurred, caused by MAC address 0050.b401.1e46 on port FastEthernet1/0/35 Product Line Satchwell BAS & Sigma Environment All ARM7 Sigma Ethernet devices Cisco Catalyst 3550 Series Switches Cisco Catalyst 3560 Series Switches Cisco Catalyst 3560-E Series Switches Cisco Catalyst 3750-E Series Switches Cause   Sigma controllers are broadcasting a high volume of Sigma global data (typically ~40 broadcasts/sec). Upgrading BAS2800+ systems to Sigma increases the volume of global data. Cisco switches set to 10Mb half duplex may misinterpret the source MAC address of Sigma globals, causing cross-port MAC confusion. Layer 2 Security features on Cisco switches may trigger violations. High collision rates may also be observed on affected switch ports. Resolution Identify High-Rate Sigma Objects: Use Wireshark to trace Ethernet traffic and identify Sigma objects broadcasting at high rates. Capture traffic per Ethernet sub-LAN. Submit for Analysis: Email the capture files to your local product support team for a global analysis report. Optimize Network Configuration: If feasible, increase the port connection speed on Cisco switches. Avoid using 10Mb half duplex settings. Firmware Update: New firmware for ARM processors has been released to address this issue. Refer to the Exchange for firmware and release notes.

Issue Can the Sigma Web Client be used effectively on Apple mobile devices such as iPads and iPhones? Product Line Satchwell BAS & Sigma Environment Sigma Web Client iPhone iPad Cause Apple mobile devices (iPhone and iPad) do not support ActiveX components, which are required for rendering Sigma Web Graphics. Resolution Due to the lack of ActiveX support on iOS devices: Sigma Web Graphics will not function properly on iPads or iPhones. Users should access the Sigma Web Client from a Windows-based device with a compatible browser that supports ActiveX (e.g., Internet Explorer). Additional Notes This limitation applies to all iOS versions and is not specific to a particular model or software update. Android devices may also face similar limitations depending on browser compatibility and support for Active

Issue After upgrading to Sigma 4.05 SEB and Remote Alarm Manager (RAM) 2.0, alarms from Sigma are no longer visible in the Sigma interface. Product Line Satchwell BAS & Sigma Environment Remote Alarm Manager 2.0 Sigma 4.05 SEB Cause The issue is caused by an incorrect DLL file being used by Sigma to interface with RAM. Resolution To restore alarm visibility in Sigma, replace the existing DLL with the correct version: Stop Services Stop both RAM 2.0 and Sigma services. Backup Existing DLL Navigate to the Sigma/Bin directory. Locate the existing SigInterfaceRAM.dll . Rename it to OldSigInterfaceRAM.dll for backup purposes. Replace DLL Download the attached  SigInterfaceRAM.dll . Copy the new DLL into the Sigma/Bin folder. Restart Services Start the RAM 2.0 and Sigma services. Launch the Sigma client to verify alarm functionality. Attachments SigInterfaceRAM.ZIP

Issue Guidance on merging index files from two separate Sigma sites into a single unified site. Product Line Satchwell BAS & Sigma Environment Sigma - all releases. Cause When consolidating two Sigma systems, it's necessary to merge their respective index files ( index.rec and index.bin ) without duplicating controller numbers or introducing system errors. Resolution Pre-Merge Preparation Backup Always create backup copies of both site index files before proceeding. Error Check Use SigmaX > Doctor Error Check on both site indexes . Ensure both sites are free of “A” errors. Save or print the error reports for documentation. Merge Procedure Directory Setup In SigmaX > Sigma Utilities > Merge Index Files, use the default directories or create your own: Master Index directory → for the main site index files Secondary Index directory → for the new site index files File Placement Place the respective index.rec and index.bin files into the appropriate directories. Merge Execution Click “Merge Index” to initiate the process . Post-Merge File Handling Copy the newly created index files from the output directory to C:\Sigma\Data . Also copy all controllers from both sites into C:\Sigma\Data . Validation Perform a visual check of the merged index structure. Run another Doctor Error Check to confirm the final index is error-free . Save or print the final error report. Index Conversion In SigmaX > BasConv  : Set Start Release to Sigma 2 Set End Release to Sigma 4 Check the “Index File” box Click “Convert” to generate IndexEx.rec Important Notes This article focuses solely on merging index files. Additional components such as: Controller operating files Route sets Access classes Graphics Must be handled separately when combining two sites.

Issue Sigma data logging has stopped recording unexpectedly. Product Line Satchwell BAS & Sigma Environment Sigma all versions Cause The issue may stem from: Changes to the Sigma server PC (e.g., IP address, hostname) Network configuration changes Controller misconfiguration Network communication issues Logging configuration missing from the controller Resolution   Verify Server Configuration Changes Check if the Sigma server PC has undergone any of the following: IP address change Hostname change Network reconfiguration If changes occurred, update all affected controllers with the correct configuration files. Isolate the Scope If multiple controllers are affected, it likely points to a server/network-wide issue. If only one controller is affected, consider: Controller misconfiguration Network issues preventing data transmission Logging configuration missing on the controller Controller Diagnostics Use System Diagnostics > Logging Servers from the controller to check: Num Log Buckets – Number of objects being logged Num of Log Records in Use – Tracks in use or full Num of Log Records Free – Available records Num of Log Records Waiting Transmission – Records pending transmission (should be zero if on the same network) Server – Indicates log configuration received Use System Diagnostics > Logging Objects to verify: Object numbers being logged Associated data sets If objects are missing from the list: Re-download the log configuration to the controller Note: Objects will only appear after the first log action Additional Tips Ensure the controller can communicate with the Sigma logging server. Check for alarms or data routing conflicts that may block log transmission. Confirm that the logging configuration is present and active on the controller.

Issue Customers have requested clarification on how Enthalpy is calculated within a Sigma Programmable Object. Product Line Satchwell BAS & Sigma Environment Satchwell Sigma Cause Need for transparency and understanding of the internal formula used for Enthalpy calculations in Sigma. Resolution  The Sigma Programmable Object calculates Enthalpy (I) using the following formula: I = 1.006 * t + x * (2501 + 1.8 * t) Where: t = temperature in °C x = humidity ratio, calculated as: x = 0.62198 * (í * pdm) / (p - í * pdm) Assuming standard atmospheric pressure p = 101.325 kPa , the formula simplifies to: x = 0.62198 * (í * pdm) / (101.325 - í * pdm) Where: í = relative humidity (as a decimal) pdm = saturation vapor pressure, calculated as: pdm = p' = 101325 * 10^A With: A = A0 - (A1 / T) - A2 * log10(T) - A3 * 10^(-T / A4) + A5 * 10^(A6 / T) Constants: A0 = 20.82648355 A1 = 2948.997118 A2 = 5.02808 A3 = 29811.33781 A4 = 32.923061 A5 = 25.21934913 A6 = 1302.8503 Temperature in Kelvin: T = 273.15 + t Additional Notes This formula is based on psychrometric principles and is used to calculate the total heat content of moist air. Ensure temperature and humidity inputs are accurate for reliable results.

Issue After a power failure, a large number of hardware alarms may be triggered by Sigma Integration Controllers (ICs), potentially overwhelming the system or operators. This article explains how to disable these alarms when necessary. Product Line Satchwell BAS & Sigma Environment Sigma Integration Controllers Cause Hardware alarms are designed to notify users of system issues. However, in some scenarios—such as after a power outage—these alarms may become excessive or non-critical, prompting the need for temporary suppression. Resolution To disable hardware alarms on Sigma ICs, you must modify the Gateway.txt configuration file. This file defines how the controller communicates with connected devices and includes parameters for alarm behavior. Steps to Disable Hardware Alarms: Locate the Gateway.txt File: This file is typically found in the configuration directory of the Sigma IC. Understand the Entry Format: Each line in the file represents an object and can contain up to nine fields. The format is: Sigma_Object, Controller_Address, Modbus_Command, Register_Address, Polling_Interval, Object_Count, Min_Value, Max_Value, Alarm_Suppression_Flag Focus on the 9th Field – Alarm Suppression Flag: 0 or omitted: Hardware alarms are enabled (default behavior). 1: Hardware alarms are suppressed (disabled). Example Entry: 55,1,3,101,1,2,0,0,1 In this example, the 9th field is set to 1, which disables hardware alarms for this object. Save and Apply Changes: After editing, save the file and restart the relevant controller to apply the changes. Important Notes Review IC Documentation: Different Sigma IC models may have variations in configuration. Always consult the specific documentation for your controller. Use with Caution: Disabling hardware alarms may prevent visibility into critical system issues. Only suppress alarms when absolutely necessary and ensure alternative monitoring is in place.