Building Automation Knowledge Base

Notifications

Community

Notifications

Categories
Forums
Knowledge Center
Blogs
Ideas
Events & Webinars

Share Your Feedback – Help Us Improve Search on Community!
Please take a few minutes to participate in our Search Feedback Survey. Your insights will help us deliver the results you need faster and more accurately.
Click here to take the survey

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 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.

Issue After restarting Sigma, the Alarm Manager fails to start. Product Line Satchwell BAS & Sigma Environment Sigma release 4.04 Cause In Sigma release 4.04, the archiving process may occasionally fail. As a result, the AlarmsLog.rec file can grow excessively large—sometimes exceeding 2 GB—which prevents the Alarm Manager from running properly. Resolution To resolve this issue, follow these steps: Stop both the Sigma Client and Sigma Server. Open Windows Explorer and navigate to the following directory: C:\Sigma\Data Locate the file named AlarmsLog.rec. Perform one of the following actions: Rename the file (e.g., AlarmsLog_old.rec ) OR Delete the file (if no longer needed). Restart the Sigma Server and Client. Note: A new AlarmsLog.rec file will be automatically created when the next alarm is received by the server. Alternative Solution Consider upgrading to the latest release of Sigma, which includes improvements to the archiving process and prevents this issue from occurring.

Issue Sigma Server fails shortly after startup. This issue occurs on a machine where anti-virus software is also installed. Symptoms Sigma services fail to start. Windows Event Viewer logs show Sigma service failure. Anti-virus logs may show Sigma files as quarantined or deleted. Product Line Satchwell BAS & Sigma Environment Satchwell Sigma Cause The Sigma Server previously operated normally but now crashes consistently upon startup. This is typically due to a recent update to the anti-virus definitions, which may incorrectly flag a Sigma file as suspicious. Resolution Check Anti-Virus Logs: Review logs to identify if any Sigma files have been quarantined or deleted. Look specifically in: Quarantine directory Deletion logs Restore or Reinstall Sigma Files: If files are quarantined, restore them. If files are deleted, reinstall Sigma to recover missing components. Adjust Anti-Virus Settings: Exclude the following directories from real-time scanning: C:\Sigma\Data C:\Sigma\Bin Note: Coordinate with site IT for approval and implementation of exclusions.

Issue What is the most effective method for retrieving logged data from Sigma controllers? Product Line Satchwell BAS & Sigma Environment Sigma controllers and ICs Sigma server Cause Sigma logged data is not always immediately available for viewing. Users may need access to data that has not yet been uploaded to the Sigma server. Resolution Sigma controllers and ICs can upload logged data to the Sigma server when their internal data tracks reach a certain capacity. While this automatic upload is the default and recommended method, it can be unpredictable. For more controlled access, two manual retrieval methods are available: Method 1: Manual Upload via System Diagnostics Open System Diagnostics. Select the desired controller. From the Options menu, choose: Upload All Logged Data, or Upload Selected Logged Data. The retrieved data will be available for review. ✅ Use this method when immediate access to specific controller data is required. Method 2: Scheduled Retrieval via System Setup Navigate to System Setup. Select Scheduled Actions. Create a new action: Choose Retrieve Controller Logs. Specify the target controllers e.g. All Controllers e.g. A defined group such as Controllers Add a schedule: Ensure retrieval actions are spaced at least 15 minutes apart to avoid system overload.

Issue Users want to create a custom shape using multiple lines in Sigma Graphics and fill it with color. Product Line Satchwell BAS & Sigma Environment Satchwell Sigma Graphics Cause Shapes created by combining multiple lines into a single object cannot be directly filled with color in Sigma Graphics. Resolution To achieve a filled shape, use the Polygon Tool as a workaround. Although slightly more complex, it allows for color filling once the shape is completed and closed. Step-by-Step Instructions: Design the Shape: Sketch your desired shape using lines as a reference. Use the Polygon Tool: Select the Polygon Tool. Click on each corner of your reference shape to replicate it. Terminate the Polygon Function: Press the Escape key to end the polygon drawing. The shape may temporarily disappear. Save and Reopen: Save the graphic. Close and reopen the file. Clean Up: Delete the original reference shape made of lines. Connect and Fill: Highlight the new polygon shape. From the right-hand menu, select Connect Closed. Then choose Shape Fill and select your desired color. Result: You now have a custom shape filled with color, created using the Polygon Tool.

Issue What authentication method does Sigma ODBC use when connecting to a SQL Server? Product Line Satchwell BAS & Sigma Environment Sigma ODBC Cause There is a requirement for two Sigma servers to pass data to a dedicated SQL Server. However, authentication issues arise during configuration. Resolution Sigma ODBC does not support authentication. To ensure successful communication between Sigma and SQL Server: Use NT AUTHORITY/ANONYMOUS for the SQL Server configuration. Do not select Mixed Mode Authentication during SQL Server setup. Ensure Windows Authentication Mode is selected, as shown in the screenshot below: This configuration allows Sigma to connect without requiring explicit authentication credentials.

Issue Sigma Server crashes, and the hard drive becomes full due to an accumulation of archived Alarm Logs, all timestamped around the same time. Alarm Fail Safe window displays: "Logging Database is 100% full" "Unable to archive" Product Line Satchwell BAS & Sigma Environment Satchwell Sigma Cause The Sigma Server crashes because the Logging Database is full. Normally, this database is automatically archived. However, if the folder C:\Sigma\Data\ArchivedLogs is missing, the archiving process fails repeatedly. Each failed attempt generates a System Message, which further fills the Alarm Log Database, triggering another archiving attempt—creating a loop that eventually crashes the server. Resolution Step 1: Recreate Missing Folders Ensure the following folders exist under C:\Sigma\Data . If not, manually recreate them: ArchivedAlarms ArchivedLogs ArchivedTransactions Step 2: Test Archiving Functionality Create an Action and Schedule to archive the logs. Allow the schedule to run. Verify that a file named Sigma0nnnn.dbs appears in the ArchivedLogs folder. ✅ If successful, you may either remove the daily schedule or leave it in place for ongoing archiving.

Issue A customer requires a program that records the outside temperature every hour and maintains a rolling 48-hour average. Product Line Satchwell BAS & Sigma Environment Satchwell Sigma Cause The need to monitor and analyze temperature trends over a 48-hour period for operational or environmental insights. Resolution A Sigma program has been developed to: Record the outside temperature hourly. Maintain a rolling average over the past 48 hours. Controller Compatibility: Designed for UNC632. Can be modified for X96, but object sequence must remain unchanged to ensure correct functionality. Version Info: Created using Sigma 4.05 SEB (Build 3.42.18). Download: 👉 UNC632-48Hr Avg.zip

Issue An object appears in the Pntfle.rec file but does not have a corresponding entry in the Index. This mismatch prevents the object from being deleted through standard procedures. Product Line Satchwell BAS & Sigma Environment Satchwell BAS2800+ Satchwell Sigma 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 BAS and Sigma require both a Pntfle.rec entry and a matching Index entry to manage and delete objects. If the Index entry is missing, the system cannot locate the object properly, resulting in deletion failure. Resolution To resolve this issue and enable deletion of the orphaned object, follow these steps: Review Object Details Use an appropriate tool to inspect the Pntfle.rec file. Record the following details: Mnemonic Object Type Object Number Controller Number Backup Existing Files Navigate to the relevant controller folder using Windows Explorer. Rename the following files: Pntfle.rec → OLDPntfle.rec Pointer.bin → OLDPointer.bin Recreate the Missing Index Entry Add a new object in the correct location within the Index. Ensure the new entry matches the recorded mnemonic structure, object number, controller number, and object type. Restore and Clean Up Navigate again to the controller folder. Delete the newly created: Pntfle.rec Pointer.bin Rename the backups back to their original names: OLDPntfle.rec → Pntfle.rec OLDPointer.bin → Pointer.bin Delete the Object With the Index entry now restored, the object can be deleted using standard procedures.

Building Automation Knowledge Base

Improve your search experience:

Related Forums

Intelligent Devices Forum

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?

Sigma - Alarm Manager Will Not Run

Sigma Server crashes soon after startup. Anti-Virus is also on the same machine.

Sigma – Best Practices for Retrieving Logged Data

Sigma Graphics – How to Create and Fill a Shape from Multiple Lines

Sigma ODBC – Authentication Method

Sigma Server crashes and the hard drive has filled with archived Alarm Logs.

Sigma – Programme to Provide a 48-Hour Average Value

Deleting a BAS or Sigma Object Without a Matching Index Entry

Ask our Experts

Email Us

Building Automation Knowledge Base

Related Forums

Ask our Experts

Email Us

Welcome!