Issue After transitioning from Sigma to EcoStruxure Building Operation (EBO), users may notice that alarm clears require acknowledgements. This occurs because the Type of Acknowledgement on Sigma Interface object alarms and hardware alarms is set to 'Extended' and cannot be changed directly to 'Single' within EBO. Product Line EcoStruxure Building Operation, Satchwell Sigma Environment Building Operation Enterprise Server Satchwell Sigma Cause The Sigma Alarm Manager settings are incorrectly configured during the data import process into EBO. Specifically, the Alarm Clear Controls are set to require acknowledgements, resulting in the 'Extended' acknowledgement type. Resolution To ensure that only alarms (not alarm clears) require acknowledgement in EBO, follow these steps on the Sigma server: Open Sigma Alarm Manager. Navigate to: Configure > Alarm Controls Uncheck the box labeled: 'Alarm Clears Acknowledgeable' Redo the Data Import into EBO. After re-importing, the Type of Acknowledgement should now be set to 'Single'. If it instead shows 'No', refer to the related article: Type of Acknowledgement set to 'No' on Sigma Interface object alarm for further guidance.

Issue Users attempting to use a USB to Parallel converter to connect the BAS2800+ dongle report that the dongle is not detected by the system. Product Line Satchwell BAS & Sigma Environment Satchwell BAS 2800+ Cause The BAS2800+ dongle relies on direct communication with a true parallel port. USB to Parallel converters do not replicate the full functionality of a native parallel port, resulting in the dongle not being recognized. Resolution Despite multiple investigations, USB to Parallel converters are not compatible with the BAS2800+ dongle. To ensure proper operation: Recommended Action: If the BAS2800+ terminal needs replacement, purchase a PC that includes a native parallel port or install a dedicated parallel port expansion card. Alternative Option: If sourcing a PC without a parallel port, search online (e.g., via Google) for PCI or PCIe parallel port cards that are compatible with your system. These cards typically offer better compatibility than USB converters.

Issue When launching SigmaX, the following error appears: "This application failed to start because side-by-side-configuration is incorrect." Reinstalling SigmaX does not resolve the issue. Product Line Satchwell Sigma Environment SigmaX Cause This error typically occurs due to: Missing or corrupted system files. Missing Microsoft Visual C++ Redistributable packages required by SigmaX. Resolution Run System File Checker (SFC) Use the System File Checker tool (SFC.exe) to identify and repair corrupted system files. Steps: Open an elevated Command Prompt: Click Start > All Programs > Accessories Right-click Command Prompt and select Run as administrator If prompted, enter the administrator password or click Allow Type the following command and press Enter: sfc /scannow This command scans all protected system files and replaces incorrect versions with correct Microsoft versions. Do not close the Command Prompt window until the verification reaches 100%. For more details, refer to Microsoft’s documentation: KB929833 Install Microsoft Visual C++ Redistributable The SFC scan will not detect missing Visual C++ Redistributables. Ensure the appropriate version of Microsoft Visual C++ Redistributable is installed. Refer to the article: Error when trying to run SigmaX.exe and RegSigmaX.exe for guidance on which version to install. Additional Notes The error may also affect RegSigmaX and SigView. Ensure your Windows installation is fully updated before running SigmaX.

Issue Users are unable to locate the documentation for the IC3-Modbus controller used in Sigma systems. Product Line Satchwell BAS & Sigma Environment Sigma IC3-Modbus Cause Documentation for the IC3-Modbus controller is not easily accessible or clearly linked within the Sigma support resources. Resolution The following resources are available for download to assist with IC3-Modbus configuration and integration: 📄 IC3-Modbus Gateway Configuration File Download Gateway_IC3-Modbus_R4_05.txt 📘 IC3 Configuration Guide Download Cguide34_IC3.pdf 📑 IC3-Modbus Data Sheet Download DS-13.684_0610_Modbus-Integration-Controller_Data-Sheet.pdf

Issue Clarification is needed regarding which Modbus data types are compatible with Sigma IC3-Modbus, particularly concerning 64-bit support. Product Line Satchwell Sigma Environment Satchwell Sigma IC3 Modbus Cause Documentation does not explicitly mention support for 64-bit data types, leading to uncertainty. Resolution   ✅ 16-bit Registers: Fully supported across all Sigma versions. ✅ 32-bit Registers: Supported from Sigma Release 4_05-SEB (Build 3_43_18) onwards. Refer to Sigma IC-Modbus - Reading 32 Bit Integer values from two 16 Bit registers for engineering guidance. ❌ 64-bit Registers: Not supported with Sigma IC3-Modbus.  

Issue How to decode individual on/off states from a Modbus analogue register (e.g., Holding or Input registers) using bit masking. Each bit represents the status of a coil and needs to be read separately. Product Line Satchwell Sigma Software Environment Sigma IC Modbus and IC3 Modbus controllers Cause Modbus registers are 16-bit values. Each bit (0 or 1) represents the on/off state of a coil. To interpret these states, bit masking is used to isolate and evaluate each bit. Resolution Each Modbus register contains 16 bits. For example, a value of 901 in Sigma translates to the binary 0000001110000101 , where: 1 = ON 0 = OFF To decode each bit: Create a Sigma analogue input object to read the Modbus value. Create a programmable object for each bit (up to 16 per register). Example Code Snippets Assuming POINT 0|222 is the Modbus value object, here’s how to decode each bit: Bit 1 (LSB) 10 XINT = INT POINT 0|222 20 YINT = XINT MASK ( 1 ) 30 IF YINT = 1 THEN RETURN TRUE "Bit 1 = on" 40 RETURN FALSE "Bit 1 = off" Bit 2 10 XINT = INT POINT 0|222 20 YINT = XINT MASK ( 2 ) 30 IF YINT = 2 THEN RETURN TRUE "Bit 2 = on" 40 RETURN FALSE "Bit 2 = off" `` Bit 3 to Bit 16 Repeat the pattern above, updating the mask value as follows: Bit Mask Value 3 4 4 8 5 16 6 32 7 64 8 128 9 256 10 512 11 1024 12 2048 13 4096 14 8192 15 16384 16 (MSB) 32768

Issue Unwanted hardware alarms (and other alarms) are being received at the Enterprise Server from Sigma controllers. Product Line Satchwell BAS & Sigma, EcoStruxure Building Operation Environment EcoStruxure Building Operation Sigma Release 4_08 (Build 3_46_57) Cause Sigma controllers are configured to send hardware and other system alarms to the Enterprise Server, which may not be required in certain operational contexts. Resolution To disable these alarms: Access the Sigma Interface: Navigate to the Sigma interface within EcoStruxure Building Operation. Locate the Controller (OSN): Identify the controller from which you want to disable alarms. Modify Device Monitoring Settings: Select the controller. Go to the Basic tab in the Properties panel. Locate the Device Monitoring setting. Set it to Disabled to stop hardware and system alarms from being sent. Bulk Update (Optional): If multiple controllers need to be updated: Multi-select the required controllers. Open the Property Panel. Change the Device Monitoring setting for all selected controllers simultaneously.

Issue Guidance is needed for configuring the Remote Alarm Manager (RAM), including understanding its components, available documentation, and script customization. Product Line Satchwell BAS & Sigma, Satchwell MicroNet, TAC Vista Environment Remote Alarm Manager Cause RAM configuration involves multiple components such as: Configuration Controller Monitoring Scripts Output Interfaces Users may encounter challenges due to the complexity of these elements or lack of familiarity with scripting in RAM. Resolution To assist with setup and customization, three key guides are available: Operator’s Manual Basic usage and interface overview Ideal for day-to-day operations Engineer’s Manual More comprehensive than the Operator’s Manual Covers advanced configuration and troubleshooting Script Editor’s Guide Details on customizing and adapting scripts Useful for tailoring RAM behavior to specific site needs 📁 Location of Scripts: Scripts used by RAM are located in: C:\Satchwell\Binary\Remote Alarm Manager File extension: .scr Best practice: Copy and rename scripts before editing to preserve originals.

Issue When launching the Sigma Client, the error "HTTP connection failed" is displayed, preventing the client from starting. Product Line Satchwell Sigma Environment Satchwell Sigma release 4.05 and later Cause The Sigma Client fails to establish a connection with the Sigma Server due to various system, network, or software-related issues. Resolution Below are the recommended troubleshooting steps, organized by category for clarity: Operating System Compatibility Windows XP: Ensure Service Pack 3 is installed and all updates are applied. Windows 7: Only Ultimate and Professional editions are supported. Installation & Permissions Sigma software must be installed by a user with Administrator privileges. Verify that the SigmaSVR service is running. If missing, reinstall Sigma as an Admin user. If user profile corruption is suspected, create a new Windows Admin user and test Sigma. Firewall & Network Settings Disable Windows Firewall or configure exceptions as per the Sigma 4.05 SP1 release notes. If using a proxy server (common in school networks): Go to Control Panel > Internet Options > Connections > LAN Settings Check "Bypass proxy server for local addresses" On SE laptops, update McAfee/Trellix firewall settings: Right-click McAfee/Trellix icon > Quick Settings > Enable Firewall Timed Groups Add a reason (e.g., "Sigma") to allow a 1-hour access window. Virtualization & Hardware If using a VMware image, try rebooting the image. If Sigma was installed while connected to Wi-Fi, uninstall it, disable Wi-Fi, enable Ethernet, and reinstall. Third-Party Software Conflicts Sophos Antivirus may quarantine Sigma DLLs. Uninstall Sophos and Sigma, reinstall Sophos (latest version), then reinstall Sigma. Flexera License Software may conflict on port 8080. Stop Flexera or change Sigma to use port 8081. StruxureWare Building Operation PCS also uses port 8080. Stop PCS to avoid conflicts. System Configuration Check the port number in C:\\Sigma\\bin\\setupsvr.exe . Default is 8080. On DELL PCs, vendor-specific background services may interfere. Reinstall Windows without vendor apps and reinstall Sigma. If the computer name contains extended ASCII or Unicode characters (e.g., “P á st”), rename it to a standard ASCII name (e.g., “Past”). Clean Reinstallation Backup Sigma data. Uninstall Sigma via Add/Remove Programs (XP) or Programs and Features (Win 7). Rename or delete the C:\\Sigma folder (e.g., rename to Sigma1 ). Reinstall Sigma using right-click > Run as Administrator on SigmaSetup.exe . Reboot the PC and verify the Sigma Server is running.

Issue The Sigma Compact Edition previously supported specific Windows CE-based hand-held devices, including: iPAQ 114 iPAQ 214 iPAQ 2490b Dell Axim X51 These devices are now obsolete and no longer available in the market. Product Line Satchwell BAS & Sigma Environment Sigma Compact Edition Sigma WinCE Cause The rapid evolution of the PDA market has led to frequent discontinuation of supported devices. This created ongoing compatibility challenges and limited long-term support options. Resolution To address this issue and improve future compatibility, Sigma 4.05 Compact Edition shifted its support strategy. While no new hand-held devices are supported in this release, users can now utilize more widely available and sustainable alternatives such as: Mini PCs Netbooks Notebooks These devices offer greater flexibility, availability, and longevity compared to legacy PDAs. Resources Release Note – Sigma Compact Edition 4.05 User Guide – Sigma Compact Edition 4.05

Issue A failed IAC 400 controller requires replacement, but only an IAC 420 is available. This article provides guidance on using the IAC 420 as a substitute, including key differences and configuration considerations. Product Line Satchwell MicroNet, Satchwell Sigma Environment IAC 400 IAC 420 Cause The IAC 400 controller is no longer manufactured or supported, making direct replacements unavailable. In legacy systems, the IAC 420 may be the only remaining compatible controller on hand, despite also being obsolete. However, differences in hardware and configuration between the two models can lead to confusion or improper operation if not addressed. Resolution Key Differences Between IAC 400 and IAC 420 Feature IAC 400 IAC 420 Input Types 3 x Temperature Inputs 2 x Analogue Inputs 1 x Digital Input 6 x Universal Inputs Communication Cable Screening Terminal 3 used for earthing the communication cable screen Screen must be connected to a good earth, not to Terminal 3 Tables & Offsets Specific to IAC 400 input types Different due to universal inputs—review updated tables and offsets ⚠️ Important: Because the IAC 420 uses universal inputs, existing configurations from the IAC 400 will not directly transfer. You must update the input tables and offsets accordingly. Refer to the document: IAC Controllers – Tables and Offsets for detailed guidance. Wiring Information IAC 400 Wiring Details: Download IAC400A.pdf IAC 420 Wiring Details: Download IAC 420 - DS2801A-1205.pdf Recommendations Compatibility Check: Ensure the IAC 420’s universal inputs can be configured to replicate the IAC 400’s original input types. Documentation Review: Carefully consult wiring diagrams and configuration tables to avoid miswiring or misconfiguration. Testing: After installation, verify all inputs and outputs function as expected. Additional Notes Both the IAC 400 and IAC 420 are obsolete. For long-term reliability, consider migrating to a supported controller platform within the EcoStruxure Building Operation suite.

Issue Users need to determine the version or build number of the Sigma software installed on their system. Product Line Satchwell Sigma Environment Satchwell Sigma Cause Sigma software installations are identified by build numbers, not just release numbers. This can cause confusion when troubleshooting or verifying compatibility. Resolution To identify the Sigma release and build number: Open the Sigma Client on the Sigma Server. Navigate to Help > About System Manager. A window will display both the release number and build number. Reference Table Use the table below to match build numbers with their corresponding release versions and file dates. Sigma Release No. Build No. Software/Firmware File Date   SigmaX   Release 1 1.52 Software/Firmware 22.06.2001 SigmaX 4.5 Release 2 2.13 Software/Firmware 14.02.2002 SigmaX 5.2 Release 2 3.12 Supplement 14.02.2002 SigmaX 5.2 Release 3 3.12 Software 31.07.2002 SigmaX 5.2 Release 3.1 3.17 Software 17.09.2002 SigmaX 5.2 Release 3.3 3.3 Software 30.07.2003 SigmaX 5.2 Release 3.4 3.31.1 Software 03.10.2003 SigmaX 5.2 Release 3.6 3.32.10 Software 19.11.2003 SigmaX 5.2 Release 3.7 3.33.9 Software 22.12.2003 SigmaX 5.2 Release 3.7 SP2 3.33.11 Software 27.01.2004 SigmaX 5.2 Release 3.7 SP3 3.33.13 Software 19.02.2004 SigmaX 5.2 Release 3.10 3.34.11 Software 21.04.2004 SigmaX 5.2 Release 3.11 3.34.11 Supplement 31.08.2004 SigmaX 5.2 Release 4.00 3.36.11 Software 16.12.2005 SigmaX 6.0.1 Release 4.00 SP2 3.36.16 Software 02 03 2006 SigmaX 6.0.1 Release 4.00 SP4 3.36.20 Software 23.05.2006 SigmaX 6.0.1 Release 4.01 3.37.08 Software 07.09.2006 SigmaX 6.0.1 Release 4.01 SP1 3.37.09 Software 26 09 2006 SigmaX 6.0.1 Release 4.01 SP3 3.37.12 Software 20 10 2006 SigmaX 6.0.1 Release 4.01 SP4 3.37.13 Software 13 08 2006 SigmaX 6.0.1 Release 4.01 SP4a 3.37.16 Software 17 11 2006 SigmaX 6.0.1 Release 4.01 SP5 3.37.18 Software 05 01 2007 SigmaX 6.0.1 Release 4.02 3.39.09 Software 26 01 2007 SigmaX 6.0.1 Release 4.03 3.40.06 Software 06 06 2007 SigmaX 6.0.1 Release 4.03 Sp1 3.40.09 Software 09 08 2007 SigmaX 6.0.1 Release 4.04 3.41.14 Software 27.02.2008 SigmaX 6.0.1 Release 4.04 SP1 3.41.15 Software 09.05.2008 SigmaX 6.0.1 Release 4.04 SP2 3.41.16 Software 15 09 2008 SigmaX 6.0.1 Release 4.04 SP3 3.41.18 Software 08 01 2009 SigmaX 6.0.1 Release 4.04 SP4 3.41.19 Software 08 01 2009 SigmaX 6.0.1 Release 4.05 3.42.34 Software 06 11 2009 SigmaX 6.0.1 Release 4.05 SP1 3.42.43 Software 22 03 2010 SigmaX 6.0.2 Release 4.05 SP2 3.42.48 Software 26.08.2010 SigmaX 6.0.2 Release 4.05 SEB 3.43.18 Software 08 12 2010 SigmaX 6.0.2 Release 4.06 3.44.14 Software 01 12 2011 SigmaX 6.0.2 Release 4.06 SP1 3.44.16 Software 01 12 2011 SigmaX 6.0.2 Release 4.06 SP1 3.44.18 Hotfix 01 02 2012 SigmaX 6.0.2 Release 4.07 3 45 48 Software 20 08 2012 SigmaX 7.0.6 Release 4.07 SP1 3 45 51 Service Pack 09 12 2012 SigmaX 7.0.6 Release 4.07 SP2 3 45 58 Service Pack 20 12 2013 SigmaX 7.0.6 Release 4.08 3.46.57 Software 10 04 2014 SigmaX 7.0.7 Release 4.08 3.46.62 Hotfix 21.05.2014 SigmaX 7.0.7 Release 4.08 3.46.70 Hotfix 23 07 2014 SigmaX 7.0.7 Release 4.08 3.46.72 Hotfix 04 08 2014 SigmaX 7.0.7 Release 4.08 3.46.73 Hotfix 12 08 2014 SigmaX 7.0.7 Release 4.08 3.46.79 Hotfix 08 10 2014 SigmaX 7.0.7 Release 4.08 (**1) 3.46.80 Software 10 04 2014 SigmaX 7.0.7 Release 4.08 3.46.81 Hotfix 17 02 2015 SigmaX 7.0.7 Release 4.08 3.46.85 Hotfix 19 03 2015 SigmaX 7.0.7 Release 4.08 3.46.86 Hotfix 19 03 2015 SigmaX 7.0.7 Release 4.08 (**2) 3.46.89 Software 10 04 2014 SigmaX 7.0.7 Release 4.08 3.46.98 Hotfix 14 12 2016 SigmaX 7.0.7 Release 4.08 (**3) 3.46.104 Software 28 02 2017 SigmaX 7.0.9 Release 4.08 3.46.105 Hotfix 10 03 2017 SigmaX 7.0.9 Release 4.08 (**4) 3.46.106 Software 28 03 2017 SigmaX 7.0.9 Release 4.08 3.46.107 Hotfix 08 08 2017 SigmaX 7.0.9 Release 4.08 3.46.108 Hotfix 01 05 2018 SigmaX 7.0.9 Release 4.08 (**5) 3.46.110 Software 13 05 2019 SigmaX 7.0.9 Release 4.08 (**6) 3.46.111 Hotfix 15 11 2019 SigmaX 7.0.9 Release 4.08 (**7) 3.46.131 Software 29 01 2020 SigmaX 7.0.9 Notes:   **1 Sigma build 4.46.57 with StruxureWare Building Operation v1.5 or 1.6 transition support program installed. **2 Sigma build 4.46.57 with StruxureWare Building Operation v1.8 transition support program installed. **3 Sigma build 4.46.57 with StruxureWare Building Operation v1.9 transition support program installed. **4 Sigma build 3.46.57 with StruxureWare Building Operation v2.01 transition support program installed. **5 Sigma build 3.46.57 with StruxureWare Building Operation v3.0.1, v3.0.2 and v3.0.3 transition support program installed.. **6 Sigma build 3.46.57 with StruxureWare Building Operation v3.0.4, v3.1 and v3.2 transition support program installed. **7 Sigma build 3.46.57 with StruxureWare Building Operation v3.2 or later transition support program installed.   Notes: 1. SigmaX version 7.0.9 is now available and can be used on any Sigma version that supported SigmaX version 7.0.6. 2. This information can be downloaded as a PDF file: Sigma Build Numbers 2023 3. When SigmaX 6.0.2 is installed, the build information provided by Sigma (Help > About) can be wrong (later than the actual version). This arises because SigmaX installs a file with Build 3.42.47 in the c:\sigma\bin folder. This is only a problem prior to Sigma Release 4.05 SEB.

Issue How to locate and download the latest firmware image versions for Sigma Controllers and Integration Controllers (ICs). Product Line Satchwell Sigma Environment 3.46.57 3.46.66 3.46.80 3.46.89 3.46.100 3.46.104 3.46.105 3.46.106 3.46.107 3.46.108 3.46.110 3.46.111 3.46.131 Cause Users may need to identify and download the correct firmware image version for their specific Sigma hardware (e.g., UNC, IC, IC3) to ensure compatibility and optimal performance. Resolution Refer to the table below for the latest firmware versions and associated release notes for each Sigma controller and integration controller type: Device Firmware Version Release Note Sigma UNC (V53) 6b UNC596 6.b – Release Note Sigma UNC3 (ARM7) 1.p.0 UNC3 1.p.0 – Release Note UNC 532 (V25) 6b UNC532 6.b – Release Note IC-Modbus V5h IC-Modbus v5h – Release Note IC3 Modbus 1.n.2 IC3 Modbus – Release Note IC SNP 5d IC-SNP v5d – Release Note IC3 SNP 1.g.1 Sigma 4.05 Firmware Supplement No specific release note available IC York V3e (Not available for download) IC-York v3e – Release Note  IC3 York 1.d.0 IC3 York 1.d.0 – Release Note IC3 Unifact 1.d.0 IC3 Unifact (RTC) – Release Note IC3 Unifact Pro 5h IC3 Unifact Pro 5h – Release Note   🔗 Note: Some firmware files or release notes may not be available for direct download. Please contact Schneider Electric support for assistance if needed.

Issue Building Management System (BMS) equipment may malfunction due to electromagnetic interference (EMI) from nearby electrical devices. Diagnosing and resolving such issues can be complex and costly, making preventive installation practices essential. Product Line Andover Continuum, EcoStruxure Building Operation, Field Devices, Satchwell MicroNet, Satchwell Sigma, TAC IA Series, TAC Vista Environment All electrical equipment Cause Improper installation can lead to the generation or exposure to high- and low-frequency EMI, which may disrupt system performance or cause equipment failure. Resolution To ensure reliable operation and minimize EMI-related issues, follow these key EMC installation practices: Key EMC Practices Follow Manufacturer Recommendations Always adhere to the installation guidelines provided by equipment manufacturers, as they are tailored to the specific EMC requirements of each product. Proper Cable Routing Separate power and signal cables. Avoid parallel runs near high-interference sources (e.g., motors, transformers). Shielding Use shielded cables for sensitive signals. Ground shields correctly—typically at one end to prevent ground loops. Grounding and Bonding Establish a low-impedance ground path. Bond all equipment to a common ground reference. Surge Protection Install surge protection on power and communication lines. Protect against lightning and switching transients. Filtering Use EMI filters on power inputs. Apply ferrite beads or chokes on signal lines where needed. Physical Separation Maintain spacing between high-voltage and low-voltage components. Isolate noisy equipment from sensitive electronics. Enclosure Design Use metal enclosures for shielding. Ensure proper sealing and grounding of enclosure panels. Installation Environment Avoid placing equipment near strong EMI sources (e.g., radio transmitters, welding equipment). Maintain clean, dry conditions to prevent corrosion and poor connections. Compliance Testing Verify installations against relevant EMC standards (e.g., IEC, EN). Conduct site surveys if persistent issues arise. Reference Document: Practical Installation Guidelines for Electromagnetic Compatibility

Issue Prior to XBuilder 5.1.1, it was not possible to change the Xenta Server type in an existing XBuilder project. This limitation made it difficult to migrate projects between different Xenta Server models without losing links, bindings, or configurations. Product Line Satchwell BAS & Sigma, Satchwell MicroNet, TAC INET, TAC Vista Environment Xenta Server XBuilder 5.1.0 or earlier Xenta 511, 527, 555, 701, 711, 721, 731, 913 Cause Earlier versions of XBuilder (prior to 5.1.1) did not support changing the Xenta Server type directly within the project’s network pane. This limitation required a manual workaround to migrate projects between different server types. Resolution Option 1: Upgrade to XBuilder 5.1.1 or Later If possible, upgrade to XBuilder 5.1.1 or newer, which allows direct modification of the target device type: Save the Project Locally: If the project is stored in a Vista database, open it in XBuilder. Go to File > Save As and save the project to your local machine. Reopen the Project: Close XBuilder. Reopen XBuilder and load the saved project from your PC. Change Target Device: In the Project menu, select Change Target Type... Choose the desired Xenta Server model from the drop-down list. Option 2: Manual Transfer (If Upgrade Is Not Possible) This method allows transferring an XBuilder project to a different Xenta Server while preserving graphics and object bindings. Ensure the target server supports the same or better Menta and User Graphic capabilities and can handle the existing network types. Example: Migrating from Xenta 555 (with LonWorks and Modbus networks) to Xenta 731. Step-by-Step Instructions 1. Create the New Xenta Server in Vista Open the Vista database containing the Xenta 555 project. Right-click the Xenta 555, select Edit to open the XBuilder project. In Vista, create a new Xenta 731 (name it similarly but not identically to the 555). 2. Transfer the LonWorks Network In Vista, drag and drop the LON network from the 555 to the 731. Right-click the 731, select Edit to open its XBuilder project. Rename the default folder in the System pane to match the top-level folder of the 555 project. In the 731 project, right-click the LON object in the Network pane and select Refresh Network from TAC Vista. 3. Transfer the Modbus Network In the 555 project: Right-click each Modbus device, select Edit Device Template. In the Device Editor, go to File > Save As... and save the template. In the 731 project: Recreate the Modbus network using the saved templates. 4. Transfer System Objects In the 555 project: Right-click each object under the top-level folder and select Copy. In the 731 project: Right-click the top-level folder and select Paste. Repeat for all objects and folders (note: selecting a folder includes all nested items). Do not copy the top-level folder itself; it cannot be pasted. Note: Graphics bindings are preserved. Reference paths are automatically updated (e.g., TAC_Xenta_555 becomes TAC_Xenta_731 ). However, some bindings (e.g., Time objects) may break and need to be manually rebound. 5. Final Steps Close the 555 project. In Vista, delete the Xenta 555. Generate the 731 project. When prompted to copy original TGML files, select Yes. Download the project to the Xenta 731. Tip: If the 555 project only contains a Modbus network, a similar process can be followed for standalone projects. Additional Notes Ensure compatibility between source and target servers regarding network types and resource capabilities. Always back up your projects before performing any migration.

Issue What are the NEMA or IP ratings for a specific product? Product Line Andover Continuum, EcoStruxure Building Operation, Field Devices, Satchwell BAS & Sigma, Satchwell MicroNet, TAC IA Series, TAC INET, TAC Vista Environment All devices Cause Users often need to know whether a product is protected against: Water ingress Intrusion by foreign objects (e.g., dust, fingers) Resolution To determine a product’s protection level, refer to the Degrees of Protection document, which includes: IP Rating Chart NEMA Enclosure Rating Chart 🔹 Understanding IP Ratings An IP rating consists of two digits: First digit: Protection against solid foreign objects Second digit: Protection against water Examples: IP20: Protected against fingers (≥12.5 mm), no water protection IP10: Protected against objects up to 50 mm, no water protection If a product datasheet does not specify water ingress protection, the second digit defaults to 0. 🔹 Typical Building Products Many building automation products: Prevent insertion of fingers (≥12.5 mm) Do not offer water protection → Common rating: IP20 📎 Attachment Degrees of Protection.pdf (Includes full IP and NEMA charts)

Issue When using a Windows PC with Microsoft Visual Studio installed, an unexpected error message appears referencing Just-In-Time (JIT) Debugging. This can interrupt normal operations and confuse users unfamiliar with debugging tools. Product Line Andover Continuum, EcoStruxure Building Operation, Satchwell BAS & Sigma, Satchwell MicroNet, TAC IA Series, TAC INET, TAC Vista Environment Windows Operating System Cause Visual Studio includes a feature called Just-In-Time Debugging, which attempts to launch the debugger when a program crashes or encounters a critical error. If enabled, this feature can interfere with other applications or workflows by prompting unexpected debug dialogs. Resolution To disable Just-In-Time Debugging, follow these steps: Open Visual Studio. Go to the Tools menu and select Options. In the Options dialog box: Expand the Debugging section. Select the Just-In-Time page. In the Enable Just-In-Time debugging of these types of code box, uncheck the relevant options: Managed Native Script Click OK to apply changes. Note: Disabling JIT debugging modifies a registry key. You must have Administrator privileges to make this change.

Issue When attempting to run LonMaker, the following errors may occur in succession: Could not listen on poet/tcp: The address specified is already in use (Error -2532) Database error: (Subsystem: LNS, #25) [DB #-2506] The global database is not open. (Subsystem: LNS, #64) Additional errors that may be caused by the same underlying issue: Problem connecting with the database server process: (Subsystem: LNS, #36) [DB#-2523] Error opening LCA Global database Product Line EcoStruxure Building Operation, Satchwell BAS & Sigma, TAC IA Series, TAC Vista Environment LonMaker for Windows 3.1 and 3.2 Sentinel Protection Installer 7.6.1 Cause  The issue is typically caused by a conflict between the Sentinel Protection Server and the POET Server, as both attempt to use the same port(s). Sentinel Protection Installer 7.6.1 installs the Sentinel Protection Server, which manages Sentinel SuperPro and UltraPro keys used with Satchwell Sigma and other products This service is not required for the dongle driver to function and can interfere with LonMaker’s operation. Refer to: Error: LNS #25 lcaErrDatabase for more technical details. Resolution To resolve the issue: Stop the Sentinel Protection Server: Open the Windows Services console: Press Windows + R , type services.msc , and press Enter. Locate Sentinel Protection Server. Right-click and select Stop. (Optional): Disable the service if not needed: Right-click > Properties > Set Startup type to Disabled. ✅ This will allow POET Server to operate without port conflicts.

Issue How to estimate the thermal load (in BTU/hr or Watts) that your controllers and equipment will produce. Product Line Andover Continuum, EcoStruxure Building Operation, Field Devices, Satchwell BAS & Sigma, Satchwell MicroNet, TAC IA Series, TAC INET, TAC Vista Environment Applicable to all electrical equipment used in building automation systems. Cause Understanding the thermal load is essential for: Sizing air conditioning systems Ensuring proper ventilation Avoiding overheating in enclosures Not all equipment datasheets provide thermal dissipation values, so manual calculation may be necessary. Resolution You can estimate the thermal load using the power consumption of each device. Formula To convert power (in Watts) to thermal load: BTU/hr = Power (W) × 3.412141633 Watts = Power (W) (already known) Note: 1 Watt = 3.412141633 BTU/hr Example Calculation Using the Continuum AC-1 I/O module: Power consumption: 2.6 W (without attached reader) Thermal load: BTU/hr = 2.6 × 3.412141633 = 8.87 BTU/hr Watts = 2.6 W If the reader is powered by the AC-1, include its power consumption in the total. International Units Reference Unit Conversion 1 Watt 3.412 BTU/hr 1 BTU/hr 0.293 Watts Additional Notes Use this method for any device where power consumption is known. For grouped equipment, sum the total wattage before converting. Consider using an online calculator for quick conversions.

Issue A BS5308 Part 1 Type 1 cable was installed under the assumption it would be used for Modbus communications. However, it was later determined that the application required M-Bus communication. This raised the question: Is the BS5308 cable suitable for M-Bus? Product Line Andover Continuum, EcoStruxure Building Operation, Satchwell BAS & Sigma, TAC Vista Environment M-Bus communication systems BS5308 Part 1 Type 1 cable (2-pair, individually screened) Cause The incorrect assumption that the communication protocol would be Modbus led to the installation of a BS5308 cable. Upon discovering that M-Bus was required, concerns arose regarding the cable’s compatibility with M-Bus communication standards. Resolution While the recommended cable for M-Bus communication is J-Y(ST)Y, which is specifically designed for indoor telephone applications and optimized for analog/digital signal transmission, the BS5308 Part 1 Type 1 cable can still be used for M-Bus under certain conditions. Key characteristics of J-Y(ST)Y cable: Designed for indoor telephone and data transmission Aluminium-laminated plastic foil static screen with tin-plated drain wire to minimize high-frequency electromagnetic interference Twisted pair (TP) structure to reduce crosstalk BS5308 Part 1 Type 1 cable considerations: Originally designed for instrumentation and control applications Features individually screened pairs, which can help reduce interference Electrical characteristics must be evaluated to ensure compatibility with M-Bus requirements Conclusion: Yes, the BS5308 Part 1 Type 1, 2-pair individually screened cable can be used for M-Bus communications, provided that its electrical characteristics meet the M-Bus system requirements. Refer to the attached calculation chart and datasheets for detailed compatibility analysis.