Issue Users may encounter a situation where object information is not visible in the SSM display window within the Sigma interface. Product Line Satchwell BAS & Sigma Environment Satchwell Sigma Cause This issue typically occurs when: The SSM display area is full, and additional data is requested. The display area does not support scrolling, so newly requested data is not shown. The font type or size used in the display window may contribute to the visibility problem. Resolution   To resolve the issue, try the following steps: Maximize or Resize the Display Window Enlarging the window may allow more data to be shown within the visible area. Change the Font Type or Size Adjusting the font settings can help fit more information into the display area: Navigate to the Display Settings. Select a smaller font size or a different font type that optimizes space usage.  

Issue You need to restrict access to specific graphics in Sigma WebClient so that only designated users can view them. Product Line Satchwell BAS & Sigma Environment Sigma WebClient Cause Sigma WebClient allows users to access graphics based on their account configuration. Without proper setup, users may inadvertently access graphics not intended for them, including the main site or other user-specific areas. Resolution To restrict a graphic to a specific user in Sigma WebClient, follow these steps: Create a User Account In Sigma, create a new user account. Assign a startup graphic to this user. This graphic should represent the specific area (e.g., building or plant) the user is authorized to view. Design the Graphic Create the graphic with a unique startup number (e.g., a building index page). Ensure no “Chain” command or reference links point back to the main site or other shared graphics. Prevent Navigation to Unauthorized Areas If the graphic links to other pages, ensure those pages also do not contain “Chain” commands back to the main site. If other users need access to the main site, consider duplicating the graphic set for the restricted user and removing the “Chain” command from this version only. User Experience When the user logs into WebClient, they will be directed to their assigned startup graphic. Navigation will be limited to the graphics explicitly linked within their assigned set.

Issue What happens to an alarm message when local time shifts due to daylight saving changes (e.g., clocks moving back or forward)? Product Line Satchwell BAS & Sigma, Satchwell MicroNet, TAC Vista Environment Remote Alarm Manager Cause This issue relates to how RAM handles time changes on the host PC. If an alarm is triggered before the time change and cleared after the system clock has shifted (e.g., moved back one hour), it may result in inconsistencies in how the alarm timestamps are displayed. Scenario Example An alarm is triggered at 15:46 local time. The system clock is manually adjusted back by one hour (e.g., due to daylight saving ending). The alarm is cleared at 14:52 (which is technically before the original alarm time). RAM logs show the alarm raised at 15:46 and cleared at 14:52. However, in the alarm properties, the cleared time may incorrectly display as 15:52, due to how the system reconciles time changes. Resolution Testing confirms that RAM handles this scenario without functional issues. Although timestamp discrepancies may appear temporarily in the alarm properties, the system normalizes once the time progresses past the original alarm time. This ensures accurate historical logging and alarm status.

Issue The Sigma IC-Lon Plugin crashes when multiple function blocks use identical SNVT (Standard Network Variable Type) names. Product Line Satchwell BAS & Sigma Environment Sigma IC-Lon Plugin Cause In LonMaker, if a controller contains multiple function blocks and each block uses the same SNVT name, the IC-Lon Plugin fails to handle this duplication and crashes. Resolution To prevent the plugin from crashing, SNVT names must be manually modified to be unique across all function blocks before using the IC-Lon Plugin. Steps to Resolve: Open the controller configuration in LonMaker. Identify function blocks with duplicate SNVT names. Rename each SNVT to ensure uniqueness across all blocks. Save the configuration and re-import into the Sigma IC-Lon Plugin. Example: Original SNVT Name: SNVT_temp Modified SNVT Name: SNVT_temp_01 , SNVT_temp_02 , etc. This ensures the plugin can correctly parse and manage the SNVTs without conflict.

Issue What is the behavior of Sigma controllers using global communications when the network fails? Product Line Satchwell BAS & Sigma Environment Satchwell Sigma Cause A site is preparing for a planned network shutdown or has experienced an unexpected network failure. Understanding how Sigma controllers respond is critical for maintaining operational continuity, especially for systems controlling critical plant equipment. Resolution When the network fails: Sigma controllers continue to operate using the last known value of the global variable. No updates or changes to global values will be received or processed during the outage. Controllers will not respond to changes in global variables until communication is restored. Best Practice Recommendations Design with resilience in mind: If a controller manages critical systems, ensure fallback logic or local overrides are programmed. Document expected behavior during outages for operational teams. Test failover scenarios to validate controller responses and ensure safety.

Issue When configuring BACnet alarms in EcoStruxure Building Operation (EBO), users may encounter a potentially misleading message in the Monitored Variable description: Monitored variable: Choose the method for referencing the property that you want to monitor. Select System reference to define a path-based reference to an object or property that is currently located on the EcoStruxure BMS server. While technically correct, this statement may cause confusion. It suggests that any object or property on the EBO server can be used as a monitored variable for BACnet alarms. However, only specific BACnet objects and properties are supported for each alarm type. Product Line EcoStruxure Building Operation Environment EcoStruxture Building Workstation Bacnet Alarms Cause The ambiguity arises from the assumption that all BACnet objects and properties are valid for alarm monitoring. In reality, only a subset is supported depending on the alarm type. Misconfiguration can lead to unexpected behavior or non-functional alarms. Resolution To ensure proper configuration, refer to the table below for supported combinations of BACnet objects and properties for each alarm type: Alarm Type Monitored Variable Object Monitored Variable Property Change of State BACnet Digital Input Value BACnet Digital Output Value BACnet Digital Value Value BACnet Multistate Input Value BACnet Multistate Output Value BACnet Multistate Value Value Change of Value BACnet Analog Input Value BACnet Analog Output Value BACnet Analog Value Value Floating Limit BACnet Analog Input Value BACnet Analog Output Value BACnet Analog Value Value Floating Limit Setpoint Reference BACnet Analog Input Value BACnet Analog Output Value BACnet Analog Value Value BACnet Loop Setpoint Out of Range BACnet Analog Input Value BACnet Analog Output Value BACnet Analog Value Value BACnet Digital Input Value BACnet Digital Output Value BACnet Digital Value Value BACnet Multistate Input Value BACnet Multistate Output Value BACnet Multistate Value Value Buffer Ready BACnet Trend Log (Any) — Additional Reference For more details, see: 🔗 BACnet Alarm Types and Monitored Variables Table

Issue What is the maximum density of people that the Insight sensor (SXWREISBLE10001) can detect? Product Line Field Devices, EcoStruxure Building Operation Environment Insight sensor. Cause There is no official specification available that defines the exact density of people the Insight sensor can detect. This limitation makes it difficult to provide a precise number for maximum detection density. Resolution The maximum raw count for the people counter is 32 individuals within the detection area. Accuracy of detection is up to 90%, but it decreases as the number of people increases within the detection zone. The detection area is influenced by the mounting height of the sensor. A higher mounting position typically results in a larger detection area but may reduce accuracy in crowded conditions. Additional Notes For optimal performance, ensure the sensor is mounted according to published guidelines. Consider environmental factors such as lighting, movement patterns, and obstructions that may affect detection accuracy. If higher accuracy or density detection is required, consider deploying multiple sensors.

Issue After commissioning HID Signo OSDP readers in Security Expert, they do not log card events. Readers cannot be brought online in Security Expert. Product Line EcoStruxure Security Expert Environment Security Expert HID Signo Smart Card readers HID Reader Manager App Warning Hazard of Electric Shock: Remove all power from all devices before removing any covers or doors of the system. Disconnect power at the device and at the power source. Electrostatic Discharge Required: Always discharge static electricity from your person by touching metal prior to handling any hardware. Failure to do so may result in damage to devices. 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 Both sides of the commissioning process require proper installation steps: HID Signo reader configuration using the HID Reader Manager App Security Expert configuration Resolution Confirm Cards Work with Reader Before starting OSDP commissioning: Set the HID Signo reader to Wiegand mode. Connect it to the Security Expert SP-C Reader Expander port. Configure the Reader Expander and Door records for the correct format and credential. Badge a card at the reader and check events in Security Expert to confirm the reader is reading the correct format. Once confirmed, proceed to Commissioning HID Signo OSDP readers.   Commissioning HID Signo OSDP readers involves two main steps: Reader configuration in the HID Reader Manager App Security Expert configuration Step 1: Configure Reader in HID App for OSDP Install Mode Open the HID Reader Manager App. Navigate to: Inspection Report → Detailed Configuration → Communication Protocol Inspect Reader Enable Install Mode:  Scroll down and select Add to Template. Select Apply Selected Items. Enable OSDP Wait for the reader update to complete, then exit the menus. Writing changes Step 2: Configure Reader Expander in Security Expert In Security Expert, go to: Reader Expander → General tab Set Port Network Type to OSDP.  Saving changes creates two new Smart Reader records. Configure the Smart Reader:  Set the Address correctly (1 + the address value set in the HID Reader App). Under the Reader tab, set:  Reader One Format to the correct format. Reader One Door to the correct Door record. Activate OSDP Install Mode:  Right-click the Reader Expander record → Activate OSDP Install Mode. Expected Events Install Mode Activation by <operator> on Module <module> Module <module> Registered With Serial No (####) These indicate the command was processed and the expander attempted to register. Important: These events appear whether the OSDP handshake succeeds or fails. The only way to confirm success is to badge a card and check for events. OSDP Install Mode may need multiple attempts for successful handshaking. When successful, the HID Reader Manager App will automatically disable Install Mode, which can be confirmed in the App. Key Notes Always verify card functionality before starting OSDP commissioning. Multiple attempts may be required for OSDP handshake. Successful commissioning is confirmed by card events in Security Expert.  

Issue When viewing an optimiser point, the value for “Minutes to Next Switch” appears unusually large. Product Line Satchwell BAS & Sigma Environment Satchwell BAS Satchwell Sigma Cause The optimiser is unable to accurately calculate the time to the next switch due to one or more of the following reasons: The associated time schedule is in a “Manual” condition. The optimiser point is correctly cross-referenced to a time schedule, but that schedule is further cross-referenced to another point (e.g., a programmable point) via: Low Action (LA) High Action (HA) Holiday point that is not correctly configured as a holiday schedule. This misconfiguration prevents the optimiser from determining the next switch time, resulting in a default large value. Resolution To resolve this issue, review and adjust the hierarchy of overrides and actions in the software. The goal is to ensure the optimiser can directly interpret the time schedule without unnecessary layers of overrides. Recommended Configuration Examples Example 1 Instead of: Holiday > Overrides (e.g., Programmable Points) > Time Schedule > Optimiser > Plant Level Use: Holiday > Time Schedule > Optimiser > Overrides (e.g., Programmable Points) > Plant Level Example 2 Instead of: Overrides (e.g., Programmable Points) > HA or LA xref > Time Schedule > Optimiser > Plant Level Use: Time Schedule > Optimiser > Overrides (e.g., Programmable Points) > Plant Level Additional Notes Ensure that holiday schedules are correctly defined as holiday points. Avoid placing overrides or programmable actions above the optimiser in the control hierarchy.

Issue A Longtext number appears when a DI Object is displayed in System Manager, even though no alarm is configured on the object. Product Line Satchwell BAS & Sigma Environment Satchwell Sigma Cause This issue occurs when a DI object previously had an alarm configured with a Longtext number. Even after the alarm is removed, the Longtext number may still be retained and displayed. Note: This behavior does not occur with AI (Analog Input) objects. Resolution To remove the Longtext number from the DI object display: Re-enable the alarm on the DI object. In the Alarm tab, set the Longtext number to "0" . Disable the alarm again. Download the object to the controller to apply the changes.

Issue You need to create a programmable object in Sigma that: Monitors an existing object (Object 1). Uses a time schedule (Object 2) to determine when to hold and output the value from Object 1. Maintains the output until the next time schedule "off" period, at which point the value is reviewed again. Product Line Satchwell BAS & Sigma Environment Satchwell Sigma Cause Assistance is required to implement a programmable object that dynamically responds to both an object’s state and a time schedule. Resolution The following logic fulfills the requirement. Ensure you use the correct controller and object numbers for your specific setup. Object Definitions Object 1: The existing object whose value is to be monitored. Object 2: The time schedule controlling when the value is held and reviewed. Programming Logic 10 IF P (2) ON THEN XINT = 1 ELSE XINT = 0 20 IF XINT DOWN THEN GOTO 40 30 GOTO 50 40 IF P (1) ON THEN YINT = 1 ELSE YINT = 0 50 IF YINT = 1 THEN RETURN TRUE "HW" 60 RETURN FALSE "CW" Explanation Line 10: Checks if the time schedule (Object 2) is ON. Line 20: If the time schedule transitions from ON to OFF, proceed to line 40. Line 40: Evaluates the state of Object 1 and sets YINT accordingly. Line 50–60: Returns TRUE or FALSE based on YINT, outputting either "HW" or "CW". Additional Notes This logic ensures the value from Object 1 is captured and held when the time schedule turns OFF. The value is only updated during subsequent OFF transitions of the time schedule.

Issue When a specific user logs off the Sigma system, another user is automatically logged on without manual intervention. Product Line Satchwell BAS & Sigma Environment Satchwell Sigma Cause This behavior is typically caused by corruption in the GenCNF.rec file and user configuration files. These corrupted files can result in unexpected user session behavior, including automatic logins. Resolution You have two options to resolve this issue: Option 1: Restore from Backup Locate a backup of the system files taken prior to the corruption. Shutdown the Sigma server and all connected clients. Copy the following from the backup: GenCNF.rec file Entire User folder Paste the copied files into the Sigma Data folder. Restart the Sigma server and all clients. Test user access to confirm resolution. Option 2: Rename and Replace the Corrupted User Note: System users cannot be deleted, only renamed. In Sigma SSM > Users, highlight the affected username. Select Rename and assign a new, appropriate name. Create a new user to replace the old one. Assign the correct access levels to the new user. Test user access to ensure proper login/logout behavior.

Issue A customer has a system that has been logging data for several years. They now need to change the name of an object that is actively being logged. The question arises: What name will appear in the logs when reviewing historical data using Dataview? Product Line Satchwell BAS & Sigma Environment Satchwell Sigma Cause Changing the name of a logged object can raise concerns about data continuity and traceability, especially when reviewing historical logs. Resolution When an object name is changed in the system: The new name is immediately passed to the logging setup. From that point forward, all log reviews—including archived and new data—will display the updated object name. This ensures consistency in log presentation but may affect traceability if historical context is needed. Important Note: If maintaining historical naming context is critical (e.g., for audits or legacy references), consider documenting the name change separately or exporting logs prior to the change.

Issue When attempting to download an image file for a controller, the IC-UNIFACT image is incorrectly displayed in the download window instead of the expected IC-SNP image. This occurs on sites where Unifact URC1201/2201 controllers are installed. Product Line Satchwell BAS & Sigma Environment Sigma IC and IC3 controllers Unifact URC1201/2201 controllers IC3-SNP integration Cause The controller subtype was mistakenly configured as IC-UNIFACT instead of IC-SNP. As a result, the system displays the image file associated with the configured controller subtype, not the actual hardware installed. Resolution To ensure the correct image file appears in the download window: Verify and Correct Controller Subtype Configuration Navigate to: System Setup > Network and Devices > Controllers Select the correct IC subtype: IC-SNP Save the configuration Download the Correct Image File Navigate to: System Diagnostics > Options > Download Files The correct image file for IC-SNP will now be displayed Additional Notes Unifact 1201/2201 controllers use IC-SNP Unifact Pro controllers use IC-UNIFACT Image files are determined by the controller version set in the configuration

Issue After upgrading to Sigma 4.06 or later, the existing Remote Alarm Manager version 1.2 no longer functions as expected. Product Line Satchwell BAS & Sigma Environment Sigma 4.06 and later Remote Alarm Manager Cause Sigma 4.06 introduced changes that are incompatible with earlier versions of the Remote Alarm Manager. Specifically, RAM version 1.2 is not supported in Sigma 4.06 and later releases. Resolution To ensure compatibility and continued functionality of alarm management features, Sigma 4.06 and later only support Remote Alarm Manager version 2.1. ✅ Action Required: Upgrade the Remote Alarm Manager to version 2.1 when using Sigma 4.06 or any subsequent release.  

Issue Users need to merge Index files from two separate BAS 2800+ sites, but the standard BasFiles tool does not support this directly. Product Line Satchwell BAS & Sigma Environment Satchwell BAS 2800+ Cause BasFiles, in its default mode, does not provide the functionality to merge Index files. A special launch switch is required to enable this feature. Resolution To merge two BAS site Index files using BasFiles, follow these steps: Launch BasFiles in Merge Mode: Click the Windows Start button. Select Run. Browse to the location of BasFiles.exe . In the Run dialog, enter: BasFiles.exe scs This command launches BasFiles in a special mode that enables the Merge option. Use the Merge Option: Once BasFiles is running in merge mode, a new menu option labeled Merge will appear. Select Merge to begin the process. Prepare Directory Structure: Ensure the required directory structure exists before initiating the merge. The tool relies on this structure to correctly combine the Index files. Best Practices Always back up existing Index files before performing a merge. Validate the merged file in a test environment before deploying to production.

Issue Understanding how to utilize secondary values and forecasting in programmable points within BAS and Sigma systems. Product Line Satchwell BAS & Sigma Environment Satchwell BAS Satchwell Sigma Cause Certain objects in BAS and Sigma support secondary values that provide additional operational insights. These values can be used to optimize system performance and scheduling. Examples of Secondary Values Object Type Secondary Value Description Use Case Example Time Schedule Minutes to next switch Preheat plant 30 minutes before AHU starts Optimiser Minutes to next switch Start boiler plant 30 minutes before VT circuit starts Rotation Lead load number Identify lead load for modulating burner signal DO / DI Hours run Perform pump changeover based on runtime Resolution Time Schedule Example 10 xflo = P100 (Time Schedule object)forecast 20 if P100 off and xflo < 30.0 then return true "Plant PreHeat" 30 if P100 on then return true "Time On" 40 return false "Time Off" Rotation Object Example (2 Loads) 10 xflo = P120 (Rotation object)forecast 20 if aflo = 1.0 then return true "Boiler1 Lead" 30 if aflo = 2.0 then return true "Boiler2 Lead" 40 return false "false" Note: aflo is a global variable referencing another object within the same controller. If not needed, substitute with xflo .

Issue Remote Alarm Manager (RAM) 2.0 is unable to read the Sigma alarm record file. Product Line Satchwell BAS & Sigma Environment Remote Alarm Manager 2.0 Satchwell Sigma Cause Corruption has occurred in the files stored in the Runtime Folder used by RAM. Resolution To resolve the issue, follow these steps: Stop the RAM Services Open the Services window and stop the Remote Alarm Manager service. Alternatively, initiate a change in the RAM Computer Configuration. When prompted to stop services, select Yes. Locate the Runtime Folder The location of the folder may vary depending on the operating system and installation path. Use the Search function in Windows to locate the folder named Runtime . Delete Contents of the Runtime Folder Navigate to the Runtime Folder. Delete all files inside the folder, but do not delete the folder itself. Restart RAM Services Return to the Services window and restart the Remote Alarm Manager service. Verify that RAM is now able to read the Sigma alarm record file correctly.

Issue When configuring Sigma objects, users may encounter display issues with analogue values. This is often due to the absence of the required lookup table in the controller. Product Line Satchwell BAS & Sigma Environment Satchwell Sigma Cause The lookup table assigned to a Sigma object is not automatically downloaded when the object itself is downloaded. This can result in incorrect or missing analogue value representations. Resolution To ensure proper functionality and accurate display of analogue values: Manually download the lookup table using the following steps: Navigate to System Diagnostics. Select Download Files. Choose Lookup.rec from the available options. Confirm that the lookup table is successfully downloaded to the controller before deploying or testing the Sigma object.

Issue After upgrading Sigma firmware or replacing the CPU card, digital outputs may fail to operate correctly Product Line Satchwell BAS & Sigma Environment Satchwell Sigma Digital Output (DO) Cause This issue typically arises in two scenarios: Hardware Change: A Sigma V53 CPU card is replaced with an ARM7 processor card. Firmware Upgrade: A newer version of Sigma firmware is installed. In both cases, the Hysteresis function in DO objects may be unintentionally enabled due to an early version of SigmaX. In older Sigma versions, this setting had no effect. However, in newer firmware, the Hysteresis function is active and can interfere with DO operation. Resolution To resolve the issue, follow these steps: Start Sigma Client and Server. Navigate to: Display menu → Object Types → Select CMD. Starting from the top of the index: Browse through all folders to locate CMD objects. For each CMD object: Open the object. Go to the General tab. Deselect the Hysteresis Control checkbox. Repeat for all affected CMD objects. Download the updated objects to the controller.