Building Automation Knowledge Base

Notifications

Building Automation Knowledge Base

Schneider Electric Building Automation Knowledge Base is a self-service resource to answer all your questions about EcoStruxure Building suite, Andover Continuum, Satchwell, TAC…

Search in

Invite a Co-worker

Send a co-worker an invite to the portal.Just enter their email address and we'll connect them to register. After joining, they will belong to the same company.

Send Invite Cancel

Related Forums

Intelligent Devices Forum

Previous Next

Invite a Colleague

Found this content useful? Share it with a Colleague!

Invite a Colleague

Building Automation Knowledge Base

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.

Issue Communications with Sigma controllers are noticeably slow. Object displays may initially appear correctly, but repeated access or overriding objects can cause the server to lock up or become unresponsive. Product Line Satchwell BAS & Sigma Environment Satchwell Sigma Cause The issue was traced to two programmable Sigma objects that were being globally transmitted at a high frequency—approximately 12 times per second. The root cause was incorrect programming logic that failed to define a Boolean return value ( TRUE or FALSE ), which is essential for proper global transmission behavior. Original (Incorrect) Code: 10 IF POINT 0|108 = 0.000000 THEN RETURN "Ch1 Off" 20 IF POINT 0|108 = 1.00000 THEN RETURN "Ch1 Start" 30 IF POINT 0|108 = 2.00000 THEN RETURN "Ch1 Running" 40 IF POINT 0|108 = 3.00000 THEN RETURN "Ch1 Shutdown" 50 IF POINT 0|108 = 4.00000 THEN RETURN "Ch1 Service" `` This logic causes the global object to transmit on every scan, regardless of state change, leading to excessive communication traffic and system performance degradation. Resolution Update the object logic to include explicit Boolean return values. This ensures that the global object only transmits on a true state change, significantly reducing unnecessary traffic. Corrected Code: 10 IF POINT 0|108 = 0.000000 THEN RETURN FALSE "Ch1 Off" 20 IF POINT 0|108 = 1.00000 THEN RETURN TRUE "Ch1 Start" 30 IF POINT 0|108 = 2.00000 THEN RETURN TRUE "Ch1 Running" 40 IF POINT 0|108 = 3.00000 THEN RETURN TRUE "Ch1 Shutdown" 50 IF POINT 0|108 = 4.00000 THEN RETURN TRUE "Ch1 Service" Best Practices Always include TRUE or FALSE in programmable object logic to control global transmission behavior. Monitor global object transmission rates to identify potential performance bottlenecks. Use diagnostic tools to trace excessive communication patterns in the Sigma environment.

Issue The Scheduled Action created to retime Sigma controllers does not appear to function as expected. Product Line Satchwell BAS & Sigma Environment Satchwell Sigma Cause The Scheduled Action may not be correctly configured, or the schedule may not be triggering as intended. Resolution Step 1: Create the Scheduled Action In Sigma Setup, navigate to: General → Scheduled Actions → Actions Highlight Actions and click New. Enter a descriptive title, e.g., Retime Controllers. Highlight the newly created action. In the Select Required Actions window, choose Retime Devices. Save the changes. Step 2: Create the Schedule Highlight Daily and click New. Enter a title for the schedule, e.g., Retime Controllers. Highlight the new schedule. In the Actions window, select Retime Controllers. Choose the desired Days/Times for execution. Save the schedule. Step 3: Test the Schedule You can verify the schedule in two ways: Option A: Passive Verification Allow the system to run normally. Use Transaction Logging or check controller times to confirm retiming occurred. Option B: Manual Time Shift Test Change the PC’s time to simulate the schedule. Example: Set the retime action for 00:05. Adjust PC time to 23:55. Ensure the PC clock passes through midnight automatically. Confirm the Scheduled Action executes at 00:05.

Issue In scenarios where no Digital Input (DI) channels are available, users may need to simulate digital input functionality using Analogue Input (AI) cards. Product Line Satchwell BAS & Sigma Environment Sigma Analogue Input cards. Cause Sigma Analogue Input cards are not designed to function as Digital Input cards. However, a workaround can be implemented to simulate digital input behavior using available analogue channels. Resolution To configure an Analogue Input to behave like a Digital Input: Create an Analogue Input Object In Sigma System Manager, define an Analogue Input object using a free point number. Configure a Lookup Table Create a lookup table to translate analogue values into digital states: Input Output 0 1 15 0 20 0 Assign this lookup table to the Analogue Input object. Add Short Text for Display Create a Short Text (e.g., On/Off = %2.f ) to represent the digital state. Link this Short Text to the Analogue Input object. Hardware Setup Fit a 1000-ohm resistor across the Analogue Input channel. This resistor acts in parallel with the digital input wiring. Result When the connected digital input changes state, Sigma will interpret and display the result as either 1 (On) or 0 (Off), effectively simulating a digital input. Notes This method is a workaround and should be used only when DI channels are unavailable. Ensure proper calibration and testing to avoid misinterpretation of analogue signals.

Issue Sigma configurable data location compatibility with Remote Alarm Manager (RAM). Product Line Satchwell BAS & Sigma Environment Sigma 4.05 SEB and later Remote Alarm Manager (RAM) versions 1.2 and 2.0 Cause Starting with Sigma 4.05 SEB, configurable data locations are supported. However, Remote Alarm Manager does not support custom data paths. This mismatch can lead to alarm failures or system instability if the default path is changed. Resolution To maintain compatibility and system reliability: For Sigma 4.05 SEB and later Always use the default Sigma data location: C:\Sigma\ RAM versions 1.2 and 2.0 do not support custom data paths, even if Sigma allows configuration. Additional Notes Release notes may suggest compatibility with configurable paths, but this applies only to Sigma—not RAM.

Issue Users report that the Print option in the graphics menu is greyed out when logged into the system. Product Line Satchwell BAS & Sigma Environment Satchwell Sigma Graphics Cause The issue occurs due to user account settings that do not permit print functionality while logged in. Resolution To resolve this issue: Access System Setup. Navigate to User Groups. Highlight the User Account experiencing the issue. In the Basic Settings section, enable the "Logged On" option. ✅ This change will activate the print functionality for all users associated with the selected account.

Issue When using Sigma on Windows 7, the holiday schedule dates do not fit properly within the display windows. Product Line Satchwell BAS & Sigma Environment Sigma Client Cause The issue is caused by Windows 7 screen settings, specifically the default theme, which affects how Sigma renders its holiday schedule interface. Resolution This is considered a minor fault. A workaround is available: To resolve the display issue: Right-click on the desktop. Select "Personalize". Scroll down and choose "Windows Classic" theme. This change replicates the Windows XP display style, allowing the holiday schedule to render correctly.

Issue Clarification needed on how alarm archiving works in Sigma release 4.05 SEB and subsequent versions. Product Line Satchwell BAS & Sigma Environment Sigma 4.05 SEB or later Cause The alarm archiving mechanism in Sigma 4.05 SEB and later is not clearly documented, leading to confusion about how and when alarms are archived. Resolution Sigma 4.05 SEB and later provide two types of alarm archiving mechanisms: 1. Automatic Alarm Archiving This process is triggered based on user-defined thresholds: Alarm File Sizes Configuration: Current (Max): Defines the maximum number of alarm records (in thousands). Archive (%): Specifies the percentage (between 20% and 50%) of the “Current (Max)” value to be archived. These settings are located in: System Setup > General > Archive Sizes Behavior: Archiving occurs automatically when thresholds are met. A low-level informational alarm is generated during archiving. This does not require user acknowledgment. Archived alarm files are stored in: C:\Sigma\Data\ArchivedAlarms Files are named using a sequential reference number. 2. Timed Alarm Archiving This method allows scheduled archiving based on user-defined actions: Configuration Steps: Navigate to: System Setup > General > Scheduled Actions Create a new Action. Define a Daily or Once Only schedule: Note: Even with scheduled archiving, the system still adheres to the limits set in Archive Sizes.

Issue Users need to understand the power supply requirements for Sigma controllers to ensure proper installation and operation. Product Line Satchwell BAS & Sigma Environment Sigma UNC Controllers Cause Clarification required on the acceptable operating voltage and frequency range for Sigma controllers. Resolution Sigma controllers are designed to operate under the following electrical specifications: Supply Voltage: 230 Vac ±10% Supply Frequency: 50/60 Hz ±10% Power Consumption: 25 VA maximum These specifications ensure reliable performance within standard building automation environments.

Issue Short Text entries in Sigma Version 4 display correctly on the local client, but not on remote clients. Product Line Satchwell BAS & Sigma Environment Sigma Version 4.0 Cause Sigma stores Short Text files based on the regional settings of the PC. The file path is typically: C:/Sigma/Data/Locality/English United_Kingdom (if UK) If the Sigma Server and Sigma Client have different regional settings, Short Text entries added on one may not appear correctly on the other. Example: Server locale: UK Remote client locale: US → The remote client will look for Short Text in the US folder, which may not contain the new entries added on the UK server, resulting in incorrect object display. Resolution Ensure consistent regional settings across all Sigma machines: For Windows XP / Server 2003: Go to Control Panel > Regional and Language Options Tab 1 (Regional Options): Set Standards and Formats and Location to the correct region. Tab 3 (Advanced): Set Language for non-Unicode programs to the correct region. For Windows 7 / Server 2008: Go to Control Panel > Region and Language Tab 1 (Formats): Set Format to the correct region. Tab 2 (Location): Confirm Location is correct. Tab 4 (Administrative): Set Language for non-Unicode programs to the correct region. Summary To ensure Short Text displays correctly across all Sigma clients: Align regional settings on all Sigma PCs. This prevents mismatches in folder paths and ensures consistent object display.

Issue A new Lookup Table has been created. When and how should it be downloaded to the controller? Product Line Satchwell BAS & Sigma Environment Satchwell Sigma Cause Clarification is needed on the correct sequence for downloading new Lookup Tables to ensure proper controller operation. Resolution Follow the steps below to correctly download a new Lookup Table: Create the Lookup Table Use Sigma System Setup to create the new Lookup Table with the required configuration. Assign the Table to the Object Allocate the new Lookup Table number to the appropriate Sigma object. Download the Table Download the object with the assigned Lookup Table to the controller. Build and Download via Diagnostics Open Sigma System Diagnostics. Select the correct controller number. Choose "Build and Download Lookup Table". This action generates a new Lookup.rec file in the OSN??? folder. The file will include the new table and any other tables required by the controller.

Issue The network interface card (NIC) on a desktop or laptop shows no link LED activity, indicating no network connection. Product Line Andover Continuum, Satchwell BAS & Sigma, Satchwell MicroNet, TAC IA Series, TAC INET, TAC Vista Environment Windows Operating System Devices with built-in or external NICs (Network Interface Cards) Cause The NIC may have power management features enabled. These features can automatically disable the NIC under the following conditions: No network activity is detected Battery power is low Battery connection is intermittent This behavior is designed to conserve power but can result in the NIC appearing inactive or disconnected. Resolution To resolve this issue, disable the NIC's power management settings: Open Device Manager. Expand the Network Adapters section. Right-click your NIC and select Properties. Go to the Power Management tab. Uncheck the box that says “Allow the computer to turn off this device to save power.” Click OK to apply the changes. Additional Notes This issue is commonly observed on laptops running on battery power. Disabling power management may slightly reduce battery life but ensures consistent network connectivity.

Issue A customer has purchased an incorrect type of Interface Controller (IC) — specifically, a Sigma IC-Unifact — and is seeking to convert it to an IC-SNP. Product Line Satchwell BAS & Sigma Environment Sigma IC / IC3 Cause The request arises due to a mismatch between the purchased IC type and the required application. The customer intended to use an IC-SNP but mistakenly acquired an IC-Unifact. Resolution Unfortunately, conversion between IC types is not possible. Each IC or IC3 has a unique personality embedded in its hardware, which is tightly coupled with its firmware. Even if the firmware is changed, the underlying hardware personality remains unchanged. This mismatch prevents the IC from functioning correctly in a different role. Therefore, to ensure proper operation, the correct IC type must be procured from the outset.

To The Top!

Building Automation Knowledge Base

Improve your search experience:

Related Forums

Intelligent Devices Forum

Sigma Logging – Impact of Object Name Changes on Logged Data

Sigma - Incorrect Image Name Displayed in Download Window

Sigma – Remote Alarm Manager Compatibility with Release 4.06 and Later

BAS 2800+ – How to Merge Index Files from Two Sites

How to Use Secondary Values and Forecasts in Sigma Programmable Points

Remote Alarm Manager 2.0 - RAM is unable to read the Sigma alarm record file.

Is the Lookup Table Associated with a Sigma Object Automatically Downloaded with the Object?

Sigma – Digital Outputs Not Operating as Expected After Upgrade

Sigma - Communications with the Controllers is Very Slow

Retiming Sigma Controllers on a Daily Basis

Sigma - Using an Analogue Input Card to Display Digital Inputs.

Sigma – Releases 4.05 SEB and Later When Used with the Remote Alarm Manager

Print Menu is Greyed Out on the Graphics Menu When a User is Logged In

Sigma Holiday Schedule Display Issue on Windows 7

Sigma – Understanding Alarm Archiving in Release 4.05 SEB or Later

What Voltages Will a Sigma Controller Operate Under?

Sigma - Short Text Not Displaying Correctly

Downloading New Lookup Tables to a Sigma Controller

No link LED on a Desktop's and Laptop's Network Interface Card (NIC).

Sigma ICs – Can a Sigma IC-Unifact IC Be Converted to an IC-SNP?

Building Automation Knowledge Base

Related Forums

Welcome!