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 The Short Form Editor (SFE) fails to operate on the local Sigma client, causing the application to crash when accessed via the Sigma index or graphics. A button labeled "SigPntSF" appears at the bottom of the screen, and the Sigma client becomes unresponsive. Users must use Ctrl+Alt+Del to terminate the application. Product Line Satchwell BAS & Sigma Environment Sigma 4.05 SEB Cause The issue is triggered by a corrupted user file, which disrupts the normal operation of the Short Form Editor. Resolution Option 1: Restore Backup Files Shutdown the Sigma client and server. Copy the backup User folder and GenCNF.rec file to the Sigma\Data directory. Restart the Sigma server and client. Test the Short Form Editor functionality. Option 2: Reinstall Sigma Shutdown the Sigma client and server. Backup the current Sigma\Data folder to a secure location. Uninstall Sigma and delete the Sigma folder. Restart the PC and reinstall Sigma. Rename the new Sigma\Data folder to 4.05 SEB Data copy . Restore your site’s data: Copy your original site data folder back to the Sigma directory. Copy the User folder and GenCNF.rec file from 4.05 SEB Data copy to the Sigma\Data folder. Restart the Sigma server and client. Test the Short Form Editor. ⚠️ Note: The GenCNF.rec file contains critical Sigma configuration data. Reconfiguration may be required after restoration.

Issue Can a USB-connected printer be used as a Live Alarm Printer configured for continuous printing? Product Line Satchwell BAS & Sigma Environment USB-connected printers Satchwell Sigma Cause Sigma’s continuous alarm printing feature requires a persistent connection between the print queue and the printer. This connection keeps the communication port open at all times to ensure uninterrupted printing of alarms. However, USB ports are designed to operate in a session-based manner. They do not support maintaining an open port indefinitely, which is essential for continuous printing. As a result, USB printers cannot fulfill the requirements for Live Alarm continuous printing. Resolution USB printers are not compatible with Sigma’s continuous Live Alarm printing feature. USB “Page Printing” mode functions correctly and can be used for non-continuous alarm printing. For continuous printing, use a printer connected via a parallel or serial port, or a network printer that supports persistent connections.

Issue Where can I find documentation and network architecture diagrams for the Building Analytics service? Product Line EcoStruxure Building Analytics Environment Building Analytics Cause Users require access to product documentation and network architecture information to support: Deployment Configuration Troubleshooting Resolution Documentation and diagrams for Building Analytics are available through the following resources: 📂 Schneider Electric Download Center Access product manuals, guides, and technical documentation. Visit the Download Center 🗺️ Network Architecture Diagrams A diagram illustrating typical Building Analytics network architectures is available: Building Analytics Network Architecture PDF

Issue The controller begins to cold start repeatedly after functioning normally for several months. During each cold start, only part of the pntfle.rec file is loaded before another cold start is triggered. Product Line Satchwell BAS & Sigma Environment UNC X96 - V53 Processor Boards with Image 5s Cause This behavior is typically caused by an incorrect or missing default gateway (GW) address in the controller configuration. Resolution Verify Gateway Address: Use Pocket Terminal 32 to check the controller’s default gateway setting. If no gateway is required, set the address to 0.0.0.0 . Reference Setup Guide: See the setup document: 📄 050803-3 Sigma V53 Processor Card - Initial Set-up.pdf Update Controller Image: Download the image release 6a or later Switch the controller to use this image as the active version. 📎 Attachments 050803-3 Sigma V53 Processor Card - Initial Set-up.pdf

Issue The Device Monitor window in Sigma shows no devices. Product Line Satchwell BAS & Sigma Environment Sigma version 4.05 (all releases) Device Monitor utility Sigma Ping utility Cause Starting from Sigma version 4.00, the Device Monitor functionality has been fully integrated into the Sigma platform. If the legacy Sigma Ping utility is still installed, it may interfere with the integrated Device Monitor. Resolution To resolve the issue and properly configure Device Monitor: Uninstall Sigma Ping Utility If previously installed, remove the Sigma Ping utility to avoid conflicts. Configure Device Monitor in Sigma Navigate to: System Setup > Network and Devices Select Your Site Highlight your site in the list. Access Device Monitor Tab Use the right-hand tab labeled Device Monitor. Choose Sigma Server From the drop-down menu, select the Sigma server where monitoring should occur. Omit Devices (Optional) Use the checkboxes to exclude any devices from monitoring as needed.

Issue After upgrading from Sigma 4.04 to Sigma 4.05 or above, pictures, animations, and bitmaps in Sigma graphics may fail to appear. Product Line Satchwell BAS & Sigma Environment Sigma 4.04 Sigma 4.05 and above Cause During the upgrade process, graphics originally in .sgi format are converted to .swc format. If the original graphic had broken or missing links to image files, these links will not be carried over. As a result: The viewer window may appear empty or show placeholder content. The image files are not created in the new path: C:\Sigma\Data\Graphics\ This typically occurs if the image was not installed correctly or saved after the link was lost. Resolution Option 1: Pre-upgrade Fix (Recommended) Open the graphic in .sgi format. Highlight an image and right-click → Properties. Verify the image link: If the link is active, the image will be highlighted with a grey background. If not, re-establish the link by locating the correct image file. Save the graphic. Proceed with the upgrade to .swc format. Option 2: Post-upgrade Fix Manually copy the image folders from: C:\Sigma\Data\Sgi\ to: C:\Sigma\Data\Graphics\ Open the graphic in .swc format. Re-establish the image links by locating the correct files. Save the graphic.

Issue Is SigmaCE available as a mobile app for Apple iPad, iPhone, or Android devices? Product Line Satchwell BAS & Sigma Environment SigmaCE Cause SigmaCE relies on technologies that are not supported by Apple mobile devices: iOS does not support JavaScript in the way required by SigmaCE. There is no equivalent ActiveX component for Apple operating systems. SigmaCE was designed for Windows Mobile 5 and 6, which are no longer widely supported. Resolution SigmaCE is not compatible with iPad, iPhone, or Android devices. Only Windows Mobile 5 or 6 devices may support SigmaCE. Refer to the Sigma Compact Edition Release 4.05 notes for further details on supported platforms.

Issue Clarification on the maximum impedance and maximum distance specifications for ARCNET LAN installations. Product Line Satchwell BAS & Sigma Environment Sigma all versions using ARCNET. Cause ARCNET LAN issues often stem from excessive cable impedance, overly long cable runs, or using non-compliant cables. These factors can degrade signal quality, leading to communication errors or network failure. Resolution To ensure optimal performance and reliability of ARCNET LAN networks in Sigma systems, adhere to the following guidelines: 1. Maximum Impedance The total impedance of the ARCNET LAN should be less than 100 ohms. 2. Maximum Distance At a baud rate of 156 Kbps, the maximum recommended cable length is 800 meters. This distance is based on using the preferred cable type: Belden 8762, which has a resistance of approximately 25 ohms. Additional Recommendations For detailed information on baud rates, cable types, distance limitations, and installation best practices, refer to the Satchwell Sigma Cabling Guide 2.2

Issue When modifying a Sigma multi-stage control loop, users often ask whether it's necessary to download all control object stages individually. Product Line Satchwell BAS & Sigma Environment Satchwell Sigma Cause The Sigma Object Editor does not differentiate between individual control stages during the download process. This means that even if only one stage is modified, the editor treats the multi-stage control object as a single entity. Resolution No, you do not need to download each control stage separately. When you initiate a download from the Sigma Object Editor, all stages of the multi-stage control object are downloaded automatically. This ensures consistency and avoids partial updates that could lead to unexpected behavior.

Issue Users need to interpret the Diagnostic LED indicators on various UNC controllers and DNN modules to assess device status and troubleshoot effectively. Product Line Satchwell BAS & Sigma Environment Sigma Devices Controllers UNC X96 UNC 532 DNN3 Cause Diagnostic LEDs are designed to provide visual feedback on the operational status of the controller. Misinterpretation or lack of documentation can lead to confusion during diagnostics. Resolution Refer to the following LED behavior chart to understand the controller's current state:

Issue A system fault alarm is triggered with a message similar to: ****System Fault Priority 27**** Date/Time: 28/09/2011 at 09:29:00 Source: Controller 60 Description: Up to 4 global objects unavailable from Controller 255 . Product Line Satchwell BAS & Sigma Environment Sigma BAS Cause This alarm may be triggered due to one of the following reasons: An incorrect global object has been mistakenly entered and downloaded to the controller. A referenced global object no longer exists. A large controller value or object number appears in the alarm message, but there is no corresponding reference in the object file. Resolution For Causes 1 & 2: Correct the object reference in the configuration. Perform a coldstart on the affected controller. Ensure all files are downloaded to the controller. Check the Alarm Manager for any additional or recurring alarms. For Cause 3: Clear the node and re-node the controller. Then follow the same steps as above (coldstart and file download).

Issue A SigmaX Doctor report may display Category A errors such as: UNC = 92 Object No. = 97 INDEX.REC ERROR Index entry does not have a matching point file entry UNC = 92 Object No. = 98 INDEX.REC ERROR Index entry does not have a matching point file entry Product Line Satchwell BAS & Sigma Environment Sigma SigmaX Cause These errors occur when an Index entry exists in the database, but the corresponding Outstation point file does not contain the object. This typically happens when: A technician deletes objects in the field using a laptop. The modified point file is uploaded to the server. The server retains outdated index entries for the deleted objects. Resolution Once confirmed that the objects should not exist, follow these steps to safely delete the orphaned index entries using the Doctor Index Editor: ⚠️ Important: There is no undo or confirmation prompt in this utility. Always back up your data before proceeding. Steps to Delete Orphaned Entries Open SigmaX and launch the Doctor utility. Run the Index Editor. In the Find field, enter the UNC and Object Number using a pipe separator (e.g., 92|97 ). Click Point to locate the corresponding line in the index file. In the Edit area, enter the Index Editor password: IE . Click the Delete button to remove the entry. Repeat steps 3–6 for any additional orphaned entries. Once complete, click the index.bin button to generate a new index.bin file. Close the Index Editor. Run the Doctor Error Check again to verify the issue is resolved.

Issue When an alarm arrives in the Alarm Manager, it is highlighted and can be acknowledged. However, if the user clicks elsewhere, the focus is lost from the alarm. Clicking the Alarm Acknowledge button does not re-select the alarm, unlike the behavior in the BAS2800+ system. Product Line Satchwell BAS & Sigma Environment Satchwell Sigma (all versions) Cause This behavior is by design. The alarm acknowledgement and focus handling were intentionally changed between BAS2800+ and Sigma. Resolution The Sigma alarm acknowledgement process is functioning as intended. If an alarm loses focus, it can be re-highlighted by selecting Update Alarm Totals. Users should be aware that clicking outside the alarm area will deselect it, and the Acknowledge button will not reselect it automatically.

Issue The release notes for the IC3-SNP do not include object mapping details for IAC 420 controllers, which are essential for configuring the gateway.txt file during integration. Product Line Satchwell BAS & Sigma Environment Satchwell Sigma IAC Controllers Cause The omission of table and offset information in the IC3-SNP release notes has led to confusion during setup and integration of IAC controllers. Resolution To resolve this, refer to the IAC Mapping Table document linked below. Although it originates from an older release note, the object mapping details remain valid and unchanged. 📄 Download: IAC Mapping Table.pdf This document provides: Table numbers Offset values Object mapping references used in gateway.txt

Issue Users may need to create a custom menu command in Sigma that opens specific PDF files, but no default command exists for this purpose. Product Line Satchwell BAS & Sigma Environment Satchwell Sigma Cause Sigma does not include a built-in command to open PDF files directly from popup menus. Resolution To create a new popup menu command that opens PDF files: Step-by-Step Instructions Open Sigma System Setup From the Sigma System Manager window, navigate to Sigma System Setup. Access Popup Menu Commands Select General → Pop-up Menu Commands. Create a New Command Go to File → New. Enter a descriptive name for the new command (e.g., Open PDF Drawing). Configure Command Properties Select the newly created command. User Access: If needed, configure access permissions using the Browse function. Built-In Functions: Choose any relevant built-in functions and assign a record name. Set External Function Executable Path: Enter the full path to the PDF viewer application. Example: C:\Program Files\Adobe\Reader 9.0\Reader\AcroRd32.exe Define Command Line Options Specify the command and path to the target PDF file. Example: C:\Sigma\Data\Graphics\Drawings\Test File {Graphic Num}.pdf This setup opens a file named Test File X.pdf, where X corresponds to the graphic number associated with the Sigma object. Insert Formal Field In the Formal Fields options box, select Graphic Number, then click Select to insert {Graphic Num} into the command line. Save and Apply Save the new command configuration. Add the command to the desired popup menu. Example Use Case If a Sigma object has a graphic number of 10, the command will open: Test File 10.pdf

Issue Where should the third-party RS-485 LAN connect on the BAS PIU? Product Line Satchwell BAS & Sigma Environment BAS PIU based on UNC532 controller RS-485 communication Type D hardware Cause The original documentation incorrectly specified the RS-485 connection points as B1, B2 on PL10, which led to confusion during installation and troubleshooting. Resolution To correctly connect the RS-485 LAN: Use C1 (+) and C2 (-) on PL2 for RS-485 communication. Additionally, create a link between TXD and RXD on PL4 to ensure proper data transmission. ⚠️ Note: Always verify wiring against the latest hardware documentation before installation.

Issue A newly created lookup table for a Sigma Analogue Output (AO) object was designed to provide output in 10% increments. However, the object continues to display values in 1% steps. Product Line Satchwell BAS & Sigma Environment Sigma Controller (All Versions) Cause The AO object uses its value as the input to the lookup table. The output from the lookup table is then passed to the Digital-to-Analog (D/A) converter, which drives the physical output. However, the Sigma front end displays the AO object’s input value—not the processed output from the lookup table—resulting in the appearance of 1% steps. Resolution To display the processed output value (i.e., the result of the lookup table) on the Sigma front end, a programmable object must be used. This object will apply the lookup table to the input value and then reference a standard AO object for output. Example of a Programmable Object Configuration 10 XFLO = POINT 0|51 20 YFLO = LOOKUP (1812, XFLO) 30 RETURN VIA TEXT 92 VALUE YFLO POINT 0|51 : The control/input object 1812 : The lookup table number YFLO : The processed output value to be displayed Verification To confirm the output value: Use a multimeter connected to the physical output of the AO object. Ensure the programmable object is correctly configured to reflect the desired output steps.

Issue Clarification is required regarding the compatibility of the Sigma S-UNC-AO analogue output card with BAS2800+ outstations, specifically UNC 196 and UNC 296 models. Product Line Satchwell BAS & Sigma Environment UNC 196 UNC 296 UNC 496 UNC 596 S-UNC-AO Cause The original BAS2800+ part numbers for UNC input and output cards have been discontinued. This has raised concerns about the availability and compatibility of replacement parts, particularly the analogue output (AO) cards. Resolution New designs of Analogue Input (AI) and Analogue Output (AO) cards have been developed and are available from production code 200705 onwards. These updated cards offer several improvements: RoHS Compliance: Fully compliant with the Reduction of Hazardous Substances directive. Surface Mount Technology: Enhances reliability and manufacturing efficiency. Improved Features: Designed for easier and faster site replacement and commissioning. Compatibility: These new AI and AO cards are fully compatible with the legacy BAS 2000, BAS 2800, BAS 2800+, and Sigma systems. No software changes are required when replacing the older cards with the new versions. Additional Resources 📄 Download Bulletin: New AI/AO OTechnicalutstation Controller Cards (070206_1)

Issue The Remote Alarm Manager (RAM) engine either: Fails to start, or Shuts down unexpectedly during normal operation. Product Line Satchwell BAS & Sigma Environment Satchwell Sigma Satchwell BAS 2800+ TAC Vista Satchwell Micronet Remote Alarm Manager Cause The issue is typically caused by the Log.mdb file growing excessively large. This file logs: System alarms User actions RAM system actions Since there is no size limit on this file, it can consume excessive memory, leading to RAM instability or shutdown. Resolution Manage the Log.mdb File To prevent the file from growing uncontrollably: Stop RAM services. Navigate to the Log.mdb file location (commonly found at: Sigma\\Data\\Remote Alarm Manager ). Delete or rename the Log.mdb file. Restart RAM services – a new Log.mdb file will be automatically created. 🔁 Best Practice: Perform this cleanup regularly if the system is stable. Adjust Logging Settings Reduce the frequency and verbosity of logging to minimize file growth: Navigate to the Debugging screen for the relevant interface (e.g., GSM Modem). Set the logging level to one of the following: Nothing – No logging (recommended if RAM is stable) Errors – Logs only error messages (recommended) Normal – Logs low-level operational info Detailed – Logs more in-depth data Verbose – Logs all available information (not recommended for production) ✅ Recommendation: Use “Nothing” or “Errors” for stable systems to reduce log file size and improve performance.

Issue The BAS2800+ system has been discontinued. Users may need to reference legacy operating system compatibility for maintenance or migration purposes. Product Line Satchwell BAS & Sigma Environment BAS2800+ version 2.9 / 2.10 Cause As outlined in the official product announcement, Satchwell BAS2800+ has reached end-of-life. This article provides validated operating system information for versions 2.9 and 2.10 to support legacy system users. Resolution According to Product Information Bulletin 04.04.02-2, BAS2800+ versions 2.9 and 2.10 have been validated to run on the following Microsoft Windows platforms: Windows NT 4.0 Windows 2000 Professional Windows 2000 Server Windows XP Professional Windows Server 2003 ⚠️ Note: These operating systems are no longer supported by Microsoft. Use in secure environments only and consider upgrading to supported platforms where possible.

Building Automation Knowledge Base

Improve your search experience:

Related Forums

Intelligent Devices Forum

Sigma - Short Form Editor will not work on the local Sigma client.

Why USB Printers Cannot Be Used for Continuous Live Alarm Printing in Sigma

Accessing Documentation and Network Architecture Diagrams for Building Analytics

Controller Repeatedly Cold Starting

Device Monitor – No Devices Appearing in Window

Pictures, animations and bitmaps in a Sigma graphic fail to appear when upgraded from Sigma 4.04 to Sigma 4.05 or above.

Sigma CE for iPad or iPhone

ARCNET LAN – Maximum Impedance and Distance Guidelines

Do I Have to Download All Control Object Stages After Making Changes to a Sigma Multi-Stage Control Loop?

Sigma - Diagnostic LED's on the UNC 532 / 632 and the UNC 496 / 596 / 696 / 796 controllers and DNN / DNN3.

Global Object Alarms

Deleting Orphaned Index Entries with SigmaX

Sigma - Alarm Acknowledgement

Object Mapping Information for IAC Controllers Using IC-SNP

Sigma - Popup Menus - Creating a New Menu Command to Open PDF Files

BAS PIU RS-485 Connection

A New Lookup Table Used on a Sigma Analogue Output (AO) Object Does Not Work

Is a Sigma S-UNC-AO Compatible with BAS2800+ UNC 196 and 296?

Remote Alarm Manager (RAM) – Engine Fails to Start or Shuts Down Unexpectedly

Supported Operating Systems for BAS2800+

Ask our Experts

Email Us

Building Automation Knowledge Base

Related Forums

Ask our Experts

Email Us

Welcome!