Issue Lon values on the Sigma IC-LON controller intermittently go into and out of default, causing unreliable data communication. Product Line Satchwell BAS & Sigma Environment Satchwell Sigma IC-LON Satchwell Sigma IC3-LON Cause This behavior is typically due to mismatched heartbeat settings between the IC-LON controller and the field controller. Resolution Check Heartbeat Settings: Locate the gateway.txt file on the IC-LON controller. Compare the receive heartbeat setting in this file to the send heartbeat setting of the field controller. Recommended Configuration: Set the receive heartbeat to 2–5 times the send heartbeat. Start with 2× and increase incrementally if the issue persists. Special Case – No Heartbeat & Rare Value Changes: If the field controller does not send a heartbeat and the LON value changes infrequently: Disable the receiver heartbeat in the IC-LON’s gateway.txt file by setting the heartbeat value to 0 . Example Configuration: 2, 2, 112, 1293, 0, 0, 0 Additional Notes The Sigma system is no longer supported. Consider transitioning to EcoStruxure Building Operation for continued support and enhanced functionality.

Issue When attempting to connect to the Sigma 4.08 (3.46.57) Server via WebClient, the connection is successful, but the logon screen appears blank. Product Line Satchwell BAS & Sigma Environment Sigma WebClient 4.08 (3.46.57) Cause The issue occurs because the installed version of the LogonSE.swc file is blank in Sigma 4.08. Resolution To resolve the blank logon screen issue: Download the correct version of LogonSE.swc . (Refer to the attachment or contact support if needed.) Shutdown both the Sigma client and server. Navigate to: Sigma/Data/Graphics/Drawings Delete the existing LogonSE.swc file. Copy the downloaded version of LogonSE.swc into the same directory. Restart the Sigma client and server. Test the WebClient to confirm the issue is resolved.

Issue The battery in the IAC-TS or IAC-600 has failed and needs to be replaced. Product Line Satchwell MicroNet Environment IAC-600 IAC-TS Cause The internal lithium battery has reached the end of its service life and no longer retains data, requiring replacement. Resolution The replacement battery is a Lithium Crystal SNAPHAT M4T28-BR12SH1. Battery Details: Manufacturer: STMicroelectronics Manufacturer Part Number: M4T28-BR12SH1 RS Components Stock Number: 189-1239 Supplier: RS Components Specifications: Attribute Value Category Detachable Lithium Power Source Operating Temperature Range 0°C to 70°C Mounting Type Through Hole Pin Count 4 Dimensions (L x W x H) 21.84mm x 18.03mm x 8mm Package Type SNAPHAT Documentation TIMEKEEPER SNAPHAT Data Sheet (M4T28-BR12SH & M4T32-BR12SH) Statement of Conformity

Issue The IC-GEN OPC server fails to communicate with third-party OPC clients over Ethernet. Product Line Satchwell BAS & Sigma Environment Sigma IC-GEN OPC (all versions) Cause The IC-GEN OPC server is designed to support only local IP address configurations as defined in the gateway.txt file. This limitation restricts communication to OPC clients running on the same PC as the server. Resolution To ensure successful communication: Run the third-party OPC client on the same machine as the IC-GEN OPC server. Verify the IP configuration in the gateway.txt file to confirm it uses a local IP address (e.g., 127.0.0.1 or localhost ). For further technical details and examples: Release Note R4_05 SEB IC-GEN (PDF) ICGENOPC_EIB Example (PDF)

Issue After a cold start of the IC-Lon or IC3-Lon controller, communication with other Lon network devices is lost. Product Line Satchwell BAS & Sigma Environment Sigma IC-Lon Integration controllers Sigma IC3-Lon Integration controllers Cause The controller has undergone a cold start—either manually or automatically. When this happens, it may revert to a non-bound state if the necessary configuration file is not properly uploaded. Resolution To restore communication, ensure the NVConfig.bin file is uploaded from the controller to the Sigma server. This file contains the Lon binding information and is essential for proper network communication. Steps to Upload NVConfig.bin: Open System Diagnostics on the Sigma server. Select the appropriate controller number. From the Options menu, choose Upload Files. Select and upload NVConfig.bin. This action will overwrite the existing file in the controller folder. Upon the next cold start, the correct configuration will be downloaded to the controller, restoring its bound state. Additional Notes The NVConfig.bin file is modified during the binding process using LonMaker. For detailed guidance on the engineering process of IC-Lon/IC3-Lon, refer to the Engineering Process Documentation. End-of-Life Notice The Sigma system is now out of its support period. It is recommended to consider transitioning to SpaceLogic - EcoStruxure Building Operation for continued support and enhanced functionality.

Issue To ensure proper communication between Sigma components, specific port numbers must be configured and exempted in system firewalls. Product Line Satchwell BAS & Sigma Environment Satchwell Sigma Cause Sigma system components rely on predefined TCP and UDP ports for communication. If these ports are blocked or not correctly configured in the firewall or network settings, communication between the server, clients, and controllers may fail. This can result in: Inability to connect to the Sigma server Loss of data exchange between controllers and the server Web client access issues Resolution Below are the port numbers used by various Sigma system components: 1. Sigma Server ↔ Sigma NNN / Controller Protocol: UDP Port: 49152 Purpose: Facilitates communication between the Sigma server and field controllers. 2. Sigma Server ↔ Sigma Client Protocol: TCP Ports: 3614 , 8080 Purpose: Enables client access to the Sigma server for system operations. 3. Sigma Web Client Communications Protocol: TCP Ports: 80 , 8080 , 3614 Purpose: Supports web-based access to the Sigma system. Firewall Configuration Ensure the above ports are allowed through your firewall to avoid communication issues between Sigma components.

Issue Can two IC3-Modbus controllers be configured to interrogate a single Modbus TCP slave device? Product Line Satchwell BAS & Sigma Environment Satchwell Sigma IC3-Modbus Cause A backup or redundant configuration may be required for reliability or failover purposes, prompting the need to connect multiple IC3-Modbus controllers to a single Modbus slave. Resolution Yes, this configuration is acceptable when using Modbus TCP protocol. However, it is not supported in RS485 RTU environments. Modbus TCP Configuration: Each Modbus device on a TCP network must have a unique ID. Other parameters such as register address, data type, and Gateway IP address can be identical across controllers. This allows multiple IC3-Modbus controllers to query the same slave device without conflict. RS485 RTU Configuration: Only one master device is allowed per RS485 RTU network. Attempting to use multiple masters will result in communication conflicts and is not supported. Best Practices Ensure each controller has a distinct Modbus ID when configuring TCP. Avoid simultaneous polling from both controllers unless the slave device supports concurrent connections. Monitor network traffic to prevent overload or latency issues.

Issue After upgrading to Sigma 4.06 or above, graphics may not display correctly. Users report that graphics appear blank or fail to load after conversion from earlier formats. Product Line Satchwell BAS & Sigma Environment Sigma 4.06 or above Sigma Graphics Cause When upgrading to Sigma 4.06 or above, graphics originally created in SGI or DRW formats must be converted to the SWC format. If the conversion process is incomplete or incorrectly performed, graphics may not display as expected. Resolution Follow the appropriate steps below based on your current Sigma version and graphic file format: 1. Upgrading from BAS (DRW Format) Locate and Prepare Files: Copy all .drw files to: C:\bas\data\graphics\slides Ensure images are placed in the correct subdirectories (e.g., animations , pictures ) as per BAS structure. Backup Original Files: Copy the original .drw files to a secure location for backup. Convert DRW to SWC: Navigate to: C:\sigma\binutils Run: DrwSWCConvrt.exe Upgrade Graphics: In the same directory, run: SigUpgrade.exe 2. Upgrading from Sigma Versions Before 4.05 (SGI Format) Locate and Prepare Files: Copy all .sgi files to: C:\sigma\data\sgi\slides Ensure images are placed in the correct directories as referenced in the SGI graphics. Backup Original Files: Copy the original .sgi files to a secure location for backup. Convert SGI to SWC: Navigate to: C:\sigma\binutils Run: SgiConvert.exe Upgrade Graphics: Run: SigUpgrade.exe from the same directory. 3. Upgrading from Sigma 4.05 (SWC Format) Upgrade Graphics: Navigate to: C:\sigma\binutils Run: SigUpgrade.exe Additional Resources 📄 Download Sigma 4.06 Release Notes

Issue During the offline license activation process for EcoStruxure Building Operation, the process fails at Step 3 with the following error: FlexNet Embedded Error: FLXERR_RESPONSE_EXPIRED – The allowed time to process the response has expired. (Public Code: 1879048218 | Location: 4522804)  Product Line EcoStruxure Building Operation Environment EcoStruxure Building Operation Offline License Activation Cause This error occurs because the response file has exceeded its valid processing window. According to FlexNet documentation, the default expiration period for response files is 7 days from the time of generation. Additional contributing factors: System clocks on involved servers may be misaligned. The response file was not activated within the allowed time frame. Resolution Response file expiration is fixed and cannot be extended. Ensure that: All EBO servers involved in the activation process have accurate date/time settings. The response file is activated within 7 days of its creation. Best Practice: Always verify system time settings on all EBO servers before generating request files and activating response files.

Issue   The MN300 controller supports 0.1 unit resolution for setpoint adjustments when used with a SLink sensor. The MN350, MN450, MN550, and MN650 controllers (firmware versions 2 and 3) only support 1.0 unit resolution.   Product Line Satchwell MicroNet Environment MN350 MN450 MN550 MN650 Satchwell MicroNet Cause Firmware versions 2 and 3 of the MN350–MN650 controllers do not support 0.1 unit resolution. Resolution ⚠️ Important Notices The MicroNet 50 series controllers (MN350, MN450, MN550, MN650 LCD and Touchscreen) have been withdrawn from sale. The IAC 420, IAC 600, and Touchscreen models have also been discontinued. No direct replacements are currently offered. For more details, refer to: PA-00495 - Notice of Withdrawal - Satchwell Sigma (PDF) PA-00528 - End of Commercialization - Satchwell Sigma (PDF) Firmware Update Firmware version 5 (released August 2008) for MicroNet 50 controllers supports 0.1 unit resolution when used with: Updated SLink2.FCG file for VisiSat 2.1 Build 148

Issue A backup of the site is not available. Product Line Satchwell BAS & Sigma Environment Satchwell BAS2800+ Cause The site is operating in standalone mode, and no backup has been created or uploaded. Resolution To recover site data, follow these steps: Review Node Configuration Use the Pocket Terminal application to inspect the outstation node configuration. Configure Terminal Set up the BAS2800+ terminal to match the configuration observed from the node. Transfer Files Open BAS2800+ System Diagnostics. Select the relevant outstation number. From the Options menu, choose Transfer Files. Transfer the file PNTFLE.REC from the outstation to: C:\BAS\Data\osn??\PNTFLE.REC Run No Index Utility Shut down BAS2800+. Locate and run the No Index utility (download link below). This utility will create the index file. Restart and Verify Restart BAS2800+. Confirm that the points are now available and can be displayed. ⚠️ Note: The No Index utility does not name index segments automatically. You will need to name them manually. Downloads No Index Utility – NewUtils2.zip

Issue When attempting to directly connect to a MicroNet controller via VisiSat, communication fails. Product Line Satchwell MicroNet Environment MicroNet controller (MN300, MN440, MN500, MN620 or MN350, MN450, MN550, MN650) Satchwell VisiSat Cause The issue is typically due to an incorrect controller subnet setting. Resolution ⚠️ Important Notices The MicroNet 50 series controllers (MN350, MN450, MN550, MN650 LCD and Touchscreen) have been withdrawn from sale. The IAC 420, IAC 600, and Touchscreen models have also been discontinued. No direct replacements are currently offered. For more details, refer to: PA-00495 - Notice of Withdrawal - Satchwell Sigma (PDF) PA-00528 - End of Commercialization - Satchwell Sigma (PDF) To resolve the issue: Access the VisiSat Server Locate the VisiSat server icon in the taskbar near the system clock. Restart the Network Service Click the Network menu. Select Restart. This action resets the controller subnet setting to 1, allowing VisiSat to establish communication with the controller.  

Issue Sigma software installation fails due to an OCX registration error. Environment Satchwell Sigma Cause The error occurs because the Windows user account used during installation does not have administrative rights. Admin rights are required to register OCX components during the Sigma installation process. This requirement is documented in the Release Notes  Resolution To resolve the issue: Log in to Windows using an account with administrative privileges. Re-run the Sigma installation. Once the installation is executed with the correct permissions, the OCX components will register successfully, and the software will install without errors.

Issue Attempts to download controller operating files into a BAS outstation fail when using a terminal connected to Port 2 (e.g., an engineer’s laptop). Product Line Satchwell BAS & Sigma Environment Satchwell BAS2000 Satchwell BAS2800 Satchwell BAS2800+ Cause The failure occurs because the terminal number configured in the BAS setup does not match the terminal number assigned to Port 2 of the outstation. This mismatch prevents successful communication and file transfer. Resolution Verify Terminal Configuration: Perform a Commstats (F3) on the node to display a list of devices and their assigned numbers per port. Alternatively, check the site node file to identify the terminal number configured for Port 2 of the outstation. Identify Terminal Assignment: Look for entries with the letter “T” followed by a device number. This indicates a terminal has been assigned. Update BAS Setup: In the BAS setup page, update the terminal number to match the one identified in step 1. Save and exit the BAS setup. Retry File Download: Reopen BAS and attempt to download the controller operating files again. Additional Notes This issue only affects outstation files, not node files.

Issue When transitioning from Sigma to EcoStruxure Building Operation (EBO), duplicated segment and object names in Sigma can cause issues during data import. Unlike Sigma, EBO does not allow duplicate names within the same folder or segment. ⚠️ Important Notice Sigma is not supported in EBO 2022 and later. To continue supporting Sigma devices, you can implement a multi-version system: Keep Enterprise Servers with Sigma devices on Building Operation 3.2. Add a Building Operation 2022 or later Enterprise Central Upgrade the rest of the system to Building Operation 2022 or later. You will not be able to upgrade EcoStruxure Building Operation servers that contain unsupported protocols, objects, or devices. Attempting to do so will result in failed upgrades or loss of functionality. Product Line Satchwell Sigma Environment Ecostruxure Building Operation SigmaX 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 In Sigma, object names could be duplicated as long as their mnemonics were unique. However, EBO enforces stricter naming rules, disallowing duplicate names within the same context. This discrepancy can lead to import errors or unintended renaming during the transition. Resolution To ensure a smooth transition from Sigma to EBO: Understand EBO Naming Rules EBO requires unique object names within the same folder or segment. During data import, EBO automatically appends a postfix (e.g., room temperature2 ) to duplicated names to allow the import to proceed. Launch SigmaX. If you encounter issues such as Side-by-Side errors or missing SigmaX files, refer to the relevant Knowledge Base articles for troubleshooting. Use SigmaX to Identify Duplicates Generate a report to identify duplicated segment and object names. The report will list any duplicated index or object names that may cause issues during import. Rename Duplicates in SigmaX Within SigmaX, rename duplicated objects to unique names of your choosing. This ensures that the Data Import process uses the updated names without automatic postfixing. Watch the Tutorial Video. A step-by-step video is available demonstrating how to perform this check. This is the third video in a series: Video 1: Checking for Database Errors Video 2: Identifying Duplicated Names (this article) Video 3: Checking for Multiple RETURN Types

Issue Before transitioning a Sigma system to EcoStruxure Building Operation (EBO), it is essential to verify the integrity of the Sigma database using SigmaX. Failure to perform these checks may result in data loss or migration errors. ⚠️ Important Notice Sigma is not supported in EBO 2022 and later. To continue supporting Sigma devices, you can implement a multi-version system: Keep Enterprise Servers with Sigma devices on Building Operation 3.2. Add a Building Operation 2022 or later Enterprise Central Upgrade the rest of the system to Building Operation 2022 or later. You will not be able to upgrade EcoStruxure Building Operation servers that contain unsupported protocols, objects, or devices. Attempting to do so will result in failed upgrades or loss of functionality. Product Line Satchwell Sigma Environment Ecostruxure Building Operation SigmaX 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 Doctor checks are required to ensure the Sigma database is free of errors prior to transitioning to EBO. SigmaX provides diagnostic tools to identify issues such as duplicated names and inconsistent programmable object logic. Resolution Follow these steps using SigmaX to identify and report logical and database errors: Launch SigmaX. If you encounter issues such as Side-by-Side errors or missing SigmaX files, refer to the relevant Knowledge Base articles for troubleshooting. Run Doctor report. Use the SigmaX Doctor tool to scan for errors  Review the report Report. Review the generated report for any database errors. Review this report carefully and take corrective action before proceeding with the EBO transition. Watch the Tutorial Video. A step-by-step video is available demonstrating how to perform this check. This is the third video in a series: Video 1: Checking for Database Errors (this article) Video 2: Identifying Duplicated Names Video 3: Checking for Multiple RETURN Types

Issue Before transitioning a Sigma system to EcoStruxure Building Operation (EBO), it's essential to verify that Programmable Objects do not contain multiple types of RETURN statements. Failing to do so may result in data loss or unexpected behavior during or after the transition. ⚠️ Important Notice Sigma is not supported in EBO 2022 and later. To continue supporting Sigma devices, you can implement a multi-version system: Keep Enterprise Servers with Sigma devices on Building Operation 3.2. Add a Building Operation 2022 or later Enterprise Central Upgrade the rest of the system to Building Operation 2022 or later. You will not be able to upgrade EcoStruxure Building Operation servers that contain unsupported protocols, objects, or devices. Attempting to do so will result in failed upgrades or loss of functionality. Product Line Satchwell Sigma Environment EcoStruxure Building Operation SigmaX 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 SigmaX must validate that each Programmable Object uses only one type of RETURN statement. This is a prerequisite for a successful and error-free transition to EBO. Resolution Follow these steps using SigmaX to identify and report Programmable Objects with multiple RETURN types: Launch SigmaX. If you encounter issues such as Side-by-Side errors or missing SigmaX files, refer to the relevant Knowledge Base articles for troubleshooting. Run the RETURN Statement Check. Use the SigmaX tool to scan the Sigma database for Programmable Objects that contain more than one RETURN type. Generate a Report. SigmaX will create a report listing all affected objects. Review this report carefully and take corrective action before proceeding with the EBO transition. Watch the Tutorial Video. A step-by-step video is available demonstrating how to perform this check. This is the third video in a series: Video 1: Checking for Database Errors Video 2: Identifying Duplicated Names Video 3: Checking for Multiple RETURN Types (this article)

Issue Guidance is needed to enable reading of PIV (FIPS-201) cards using the AX-SSC controller and AC1 downstream devices within EcoStruxure Access Expert. Product Line EcoStruxure Access Expert Environment AX-SSC Cause Sites migrating from Continuum systems require a clear, step-by-step process to ensure PIV cards are properly enrolled and recognized in Access Expert. Resolution What is FASC-N? FASC-N stands for Federal Agency Smart Credential Number. It is a 25-byte (200-bit) identifier embedded in PIV cards, used to uniquely identify the cardholder across federal systems. It is composed of multiple fields, including: Agency Code System Code Credential Number Credential Series Credential Issue Person Identifier Organizational Category Organizational ID Person Org Association These fields are encoded using Packed Binary Coded Decimal (BCD) with odd parity, and together form a unique string used by access control systems to authenticate users. Understanding the FASC-N Structure In the Continuum Personnel object below, the fields highlighted are those that make up the FASC-N The PIV enrollment tool generates a character string when a card is presented. For example: 32013733334894141152472674132011 This string is composed of the following FASC-N fields: Field Value Agency Code 3201 System Code 3733 Credential Number 334894 Credential Series 1 Credential Issue 4 Person Identifier 1152472674 Organizational Category 1 Organizational ID 3201 Person Org Association 1 Note: If no enrollment tool is available, manually concatenate these fields in the order shown to create the FASC-N string. Configuration Steps 1. Card Format Setup Configure the card format in Access Expert as follows: Card Format Type: Standard Bit Length: 128 Large Encoded Card Number: ✅ Checked Convert 200 FASCN Bit to 128 Bit: ✅ Checked Card Number Starting Bit: 0 Card Number Bit Length: 128 2. AX-SSC Controller Configuration Ensure Enable Large Encoded Card Number is checked. Assign the card format created in Step 1 to the controller. 3. Person Object Configuration Navigate to Add Card Assignments. Paste the full FASC-N string into the Display Card Number field. This will auto-populate the Encoded Card Number field. Since the Encoded Card Number field is limited to 16 characters, truncate the string from the end until only 16 characters remain. Paste the full FASC-N string into the Hex Value field. ⚠️ Although labeled "Hex Value", enter the string as decimal digits. Save the Person object. Additional Notes Only the editors mentioned above require configuration for PIV card support. Editors such as Reader, Access Level, etc., do not need special configuration for PIV cards.

Issue The Xenta Repeater features two sets of terminals labeled identically, which may cause confusion during installation. Product Line TAC Vista Environment Vista Lon Network Cause The duplicate power supply and communication terminals are internally connected. This design allows flexibility in wiring but can be misinterpreted. Resolution   Both the upper and lower terminals are electrically connected and can be used interchangeably for power and communication. These duplicate terminals are provided for convenience, allowing easier access depending on installation layout. Connect one Lon network segment to COM1 and the other to COM2. Supply the repeater with 24V power.   Wiring Examples Example 1: Traditional Bus Topology Segment 1 enters via COM1 and ends at the repeater (terminated). Segment 2 exits via COM2, beginning a new segment (also terminated). Example 2: Terminal Flexibility Same as Example 1, but demonstrates that either the upper or lower terminals can be used due to internal connectivity. Example 3: Pass-Through Configuration Segment 1 enters and exits through COM1 (not terminated, as it's not end-of-line). Segment 2 begins at COM2 and is terminated at the repeater. Additional Information For a deeper understanding of the Xenta Repeater’s role in signal restoration and conditioning on LonWorks networks, refer to: 👉 The Xenta Repeater provides signal restoration and conditioning on LON networks

Issue LON networks may experience communication issues due to excessive physical length or a high number of connected devices. The Xenta Repeater helps mitigate these issues by restoring and conditioning signals, enabling longer network spans and supporting more devices. Product Line TAC Vista Environment Vista Lon Networks Xenta Repeaters (Part # 007309120) Cause LON communication failures often stem from: Exceeding recommended cable lengths Overloading the network with too many devices Resolution The Xenta Repeater: Uses a standard Xenta 400 base Splits a LON channel into two segments Connects one segment to COM 1 terminals, and the other to COM 2 terminals 🔍 Note: A LON channel is a section of the network separated by a router. A segment is a portion of a channel divided using a repeater. 📏 Cable Length Guidelines Cable Type Max Bus Length (Doubly Terminated) Max Node-to-Node (Singly Terminated) Max Segment Length (Singly Terminated) Belden 85102 2,700 m / 8,858 ft 500 m / 1,640 ft 500 m / 1,640 ft Belden 8471 2,700 m / 8,858 ft 400 m / 1,312 ft 500 m / 1,640 ft UL Level IV 22AWG 1,400 m / 4,593 ft 400 m / 1,312 ft 500 m / 1,640 ft Siemens J-Y(st)Y 900 m / 2,953 ft 320 m / 1,050 ft 500 m / 1,640 ft TIA568A Cat.5 900 m / 2,953 ft 250 m / 820 ft 450 m / 1,476 ft 📌 Design Rules Max 128 devices per LON channel Max 64 devices per segment Up to 2 repeaters per channel (max 3 segments) If no router is used, only 64 devices allowed (single segment) Recommended: ≤ 50 devices per segment for flexibility during installation 🔄 How It Works The Xenta Repeater contains: Two internally connected LON transceivers Transient suppression circuits It: Reads LON packets from one segment Re-broadcasts them to the next segment Filters out noise, ensuring clean signal transmission Unlike simple amplifiers, it does not amplify noise, resulting in strong, noise-free communication across segments.