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 IC-Lon controller objects intermittently revert to displaying default values after a period of normal operation. Product Line Satchwell BAS & Sigma Environment Sigma IC-Lon controller Cause This issue typically arises due to limitations in the IC-Lon controller, particularly related to: The number of output SNVTs (Network Variable Outputs) configured. The frequency of heartbeat transmissions for these SNVTs. By default, each NVO has a heartbeat interval of 300 seconds. If too many NVOs are configured with the same or low heartbeat intervals, the controller may become overloaded, leading to objects reverting to their default values or appearing to go offline. Resolution To mitigate this issue: Review the gateway.txt configuration file for the IC-Lon controller. Adjust the heartbeat settings for each NVO: Ensure that heartbeat intervals are set to the maximum acceptable value for your application. Stagger the heartbeat intervals across different NVOs to reduce simultaneous network traffic and controller load. Monitor the controller’s performance after making changes to ensure stability and proper communication with the LonWorks network.

Issue The Remote Alarm Manager (RAM) system does not behave as expected when processing “Off Duty” and “On Duty” messages from a reciprocator’s mobile device. Product Line Satchwell BAS & Sigma, Satchwell MicroNet, TAC Vista Environment Remote Alarm Manager (RAM) 1.2 and 2.0 Cause When a reciprocator sends an “Off Duty” message via mobile to the RAM interface, a duty exception is correctly created and displayed on the RAM console. However, when the same reciprocator sends an “On Duty” message, the system fails to cancel the previously created duty exception. This results in inaccurate duty status representation within the RAM system. Resolution A workaround is available to ensure proper handling of duty status changes: To allow users to remotely issue “On Duty” or “Off Duty” commands effectively: Navigate to the User Access Page in the RAM interface. Locate the user account in question. Set the user’s Local Access Level to ‘Privileged User’ or higher. This access level ensures that the system correctly processes both “On Duty” and “Off Duty” messages from the user’s mobile device. Note: This workaround must be applied individually to each user requiring remote duty status control.

Issue Startup programs can slow down system boot time and cause application conflicts if loaded in the wrong order. Product Line Andover Continuum, EcoStruxure Building Expert, EcoStruxure Building Operation, Satchwell BAS & Sigma, Satchwell MicroNet, TAC IA Series, TAC INET, TAC Vista Environment Windows XP, Vista, 7, 8, 8.1, 10, 11 Cause Applications configured to launch at startup may: Increase boot time Cause system instability or delays Load in an incorrect sequence, affecting performance Resolution Windows XP, Vista, 7 Click Start → Run Type msconfig and press Enter Go to the Startup tab Uncheck items you want to disable Click Apply → OK Restart your computer 🔹 Windows 8, 8.1, 10, 11 Press Ctrl + Shift + Esc to open Task Manager Click the Startup tab Right-click any item and choose Disable Restart your computer for changes to take effect 💡 Tip: Only disable items you recognize. Disabling essential services may affect system functionality. Additional Notes Disabling startup items is useful for troubleshooting slow boot times or software conflicts. For persistent issues, consider using tools like Autoruns from Microsoft Sysinternals for deeper analysis.

Issue A licensing error appears in the RAM log when Sigma is installed. Dongle failure 30 day limited mode entered Product Line Satchwell BAS & Sigma Environment Sigma Remote Alarm Manager (RAM) Cause The error occurs due to incorrect licensing configuration in Sigma. RAM licensing relies on the Sigma dongle, and the appropriate license scheme must be selected during setup. Resolution To resolve the licensing error: Open the Remote Alarm Manager Computer Configuration Wizard. Navigate to: Start > Licence Scheme Ensure the checkbox for Legacy Licence Schemes is selected. This enables compatibility with the Sigma dongle-based licensing system.

Issue Users may need to display the current date as a formatted object within Sigma. Product Line Satchwell BAS & Sigma Environment Satchwell BAS & Sigma Cause Sigma does not natively format date objects for display. A programmable point must be configured to represent the date in a readable format. Resolution Option 1: Display Day and Month (Format: dd.mm ) Use the following programmable logic: 10 XFlo = FLOAT ( MONTH ) 20 XFlo = XFlo / 100.000 30 YFlo = FLOAT ( DAY ) 40 RETURN VIA TEXT 449 VALUE XFlo + YFlo Shorttext Format: %2.2f → Displays as 17.07 Date:%2.2f → Displays as Date:17.07 Option 2: Display Day, Month, and Year (Format: ddmmyy ) Use the following programmable logic: 10 XFlo = FLOAT ( MONTH ) 20 XFlo = XFlo * 100.000 30 YFlo = FLOAT ( DAY ) 40 YFlo = YFlo * 10000.0 50 ZFlo = FLOAT ( YEAR ) 60 RETURN VIA TEXT 449 VALUE XFlo + YFlo + ZFlo Shorttext Format: Date:%2.0f → Displays as Date:170712 Notes Ensure the correct formatting is applied in the Shorttext field to match the desired output.

Issue During the installation of SigmaX, the following error message appears: Module C:\Sigma\Bin\SigToolsCntrl.dll failed to register. HRESULT -2147024769. Contact your support personnel. Selecting "Try Again" repeats the error. Choosing "Continue" allows installation to complete, but SigmaX fails to display Sigma data. Product Line Satchwell BAS & Sigma Environment SigmaX Cause The installer attempts to register SigToolsCntrl.dll but fails. This is commonly due to: The DLL already being registered. Version mismatch between Sigma and SigmaX. Missing or corrupted DLL file. Resolution Verify DLL Presence Navigate to C:\Sigma\Bin Confirm SigToolsCntrl.dll exists. Check Version Compatibility Ensure the installed Sigma version matches the SigmaX version. Manual DLL Registration Open Run from the Start menu. Type: regsvr32 "C:\Sigma\Bin\SigToolsCntrl.dll" Click OK. Unregister DLL (if needed) Open Run. Type: regsvr32 /u "C:\Sigma\Bin\SigToolsCntrl.dll" Click OK. Clean Reinstallation Uninstall SigmaX. Delete the SigmaX folder. Run a registry cleaner. Reboot the system. Reinstall SigmaX. Full Reinstallation (if issue persists) Uninstall both Sigma and SigmaX. Delete both folders. Run a registry cleaner. Reboot. Reinstall Sigma, then SigmaX.

Issue The Remote Alarm Manager (RAM) displays the following error message: "Alarm on GSM modem – Unable to reset GSM modem – modem did not accept reset command" This issue indicates that the GSM modem has stopped responding and cannot be reset via the standard command. Product Line Satchwell BAS & Sigma Environment Remote Alarm Manager (RAM) Cause This issue typically occurs when the GSM modem interface becomes unresponsive. It may be due to: Communication failure between RAM and the GSM modem Incompatibility or malfunction of the serial PCI / PC Express card Incorrect or incompatible driver installation Insufficient retry attempts or timeout settings in the modem configuration Resolution Verify Modem Configuration: Check the modem type and ensure it is supported. Navigate to the Advanced tab in the modem settings. Increase the number of retries and response timeout values to allow more time for the modem to respond. Use a USB to Serial RS232 Adapter (Workaround): If the issue persists, consider replacing the PCI / PC Express card with a USB to Serial RS232 adapter. Ensure the correct driver is installed for the adapter. For example: StarTech FTDI USB to Serial RS232 Adapter (Part No. ICUSB2321FIS) requires the FTDI driver, not the Prolific driver. After installation: Open Device Manager in Windows. Locate the newly created serial COM port assigned to the USB device. Reassign the GSM modem in RAM to use this new COM port.

Issue When a USB tractor feed printer is connected to a remote Sigma client, the client may appear to freeze or become unresponsive if the printer is unable to print. Product Line Satchwell BAS & Sigma Environment Sigma 4.05 SEB Cause This issue typically occurs when the connected printer encounters one of the following conditions: Paper jam No paper loaded Printer is powered off These conditions prevent the printer from processing print jobs, which in turn causes the Sigma remote client to hang or freeze. Resolution To resolve this issue, follow these steps on the affected remote Sigma client: Deselect the Printer as the Alarm Printer: Open the Alarm Manager. Navigate to the printer settings. Deselect the USB tractor feed printer as the designated alarm printer. Delete Any Existing Alarm Filters: In the Alarm Manager, locate and remove any alarm filters that may have been configured for the printer. Remove the Printer Driver: Go to Devices and Printers in the Windows Control Panel. Locate the USB tractor feed printer. Right-click and select Remove device. Optionally, uninstall the associated printer driver from Print Server Properties.

Issue When generating a 'List Object' report using SigView_ATK (or SigView), object titles and segment titles appear duplicated throughout the report columns. Product Line Satchwell BAS & Sigma Environment Sigma 4.05 SP1/SP2 Sigma SEB Sigma ATK SigView ATK Cause Sigma version 4.05 no longer automatically generates the pointer.bin file. This file is essential for SigView_ATK to retrieve object data (e.g., Object Titles) from the Sigma Index file. Resolution To resolve the duplication issue, manually generate the pointer.bin file using one of the following methods: Option 1: For Engineers Run SigmaX (v6) on your laptop. This will create the required pointer.bin file. Option 2: For Customers Using Sigma 4.05 SEB Copy the utility GeneratePointerBin.exe to: C:\Sigma\Binutils Run the utility from this location. Option 3: For Customers Using Sigma 4.05 SP1/SP2 Copy GeneratePointerBin.exe to: C:\Sigma\Bin Run the utility from this location. Note: The utility requires Fileutils.dll to operate correctly, which is why the specified directories must be used. Additional Information The Sigma 4.05 Pointer Bin Generator utility is available for download from the Exchange Download Center.

Issue ModBMS intermittently fails to update certain data points from controllers, leading to potential data inconsistencies. Product Line Satchwell BAS & Sigma Environment Satchwell ModBMS 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 Services for assistance. Cause ModBMS may occasionally fail to update specific controller points due to issues in the RUD update mechanism. Resolution To diagnose and troubleshoot the issue, enable debug logging in ModBMS: Steps to Enable Debug Logging Locate Configuration File: Navigate to the ModBMS installation directory. Open the ModBMS.cfg file using Notepad or a similar text editor. Modify Debug Settings: Find the [General] section. Look for the entry Debug . If it does not exist, add it manually. Set the value as follows: <Debug>0</Debug> : No debug logging (default) <Debug>2</Debug> : Logs only changes in RUD updates <Debug>4</Debug> : Logs all RUD updates (recommended for troubleshooting) Save and Restart: Save the changes to ModBMS.cfg . Restart the ModBMS application to apply the new settings. Collect Debug Logs: After reproducing the issue, locate the ModBMS.txt file. Send this file to Product Support for analysis. Disable Debug Logging (Optional): Based on Product Support's recommendation, you may disable debug logging by setting <Debug>0</Debug> and restarting ModBMS. Additional Notes Turning on debug logging increases the size of log files. Monitor disk space if left enabled for extended periods. Always follow up with Product Support for guidance on interpreting logs and next steps.

Issue The SMS Nokia mobile phone simulator does not function in RAM 2.0 / 2.1 and Windows 7. Product Line Satchwell BAS & Sigma, Satchwell MicroNet, TAC Vista Environment Windows 7 Remote Alarm Manager (RAM) Cause When using RAM 2.0 or 2.1 on Windows 7, the SMS test interface fails to display the Nokia dummy phone on the desktop after sending a test SMS. This is due to the Interactive Services Detection service being disabled by default in Windows 7, which prevents interactive elements from appearing on the desktop. Resolution To enable the SMS Nokia mobile phone simulator to function correctly: Enable Interactive Services Detection: Press Windows + R , type services.msc , and press Enter. In the Services window, scroll down to Interactive Services Detection. Set the Startup type to either Manual or Automatic. Click Start to run the service. Send a Test SMS: In RAM, send a test SMS message to the dummy Nokia phone. An icon will appear in the Windows taskbar indicating a message is available. Click on “View the message” to open the dummy SMS phone interface. The message should now be visible on the simulated phone. Additional Notes This issue is specific to Windows 7 due to changes in how interactive services are handled. This workaround may not be applicable to newer versions of Windows where Interactive Services Detection is deprecated or removed.

Issue Users may encounter 'Operlist.txt file missing' alarms in the Sigma Alarm Manager, even though the file appears to exist on the controller. Product Line Satchwell BAS & Sigma Environment Sigma 4.07 (upgraded from BAS2800+ or Sigma versions prior to 4.04) Cause Starting from Sigma version 4.04, the system no longer requires manually created operlist.txt files. Instead, the Sigma server automatically generates a dummy operlist.txt file for each controller. However, if a manually created operlist.txt file already exists in the controller’s or outstation’s folder, Sigma will use that file instead of the dummy one, potentially triggering the alarm. Resolution To resolve the issue: Delete existing operlist.txt files from all controller and outstation folders: Use Windows Search to locate all instances of operlist.txt within the directory: C:\Sigma\Data Delete all found files. Download the dummy operlist.txt file to all controllers: Open Sigma System Diagnostics. Initiate the download process for operlist.txt . The system will automatically create and deploy a dummy file to each controller/outstation folder.

Issue When replacing or upgrading the Sigma server PC, it's essential to ensure that user credentials are preserved. This article outlines which files and folders must be backed up to retain user names and passwords. Product Line Satchwell BAS & Sigma Environment Satchwell Sigma Cause During server replacement or upgrade, user credentials may be lost if the correct files are not backed up. This can lead to access issues and configuration loss. Resolution User names and passwords in Sigma are stored in specific locations within the Sigma/Data directory. To ensure a complete backup, copy the following: Required Files and Folders: Entire contents of the User folder GenCNF.rec file Labels file These files contain encrypted credential data and configuration references necessary for restoring access post-migration.

Issue After upgrading a Building Automation System (BAS) site to Sigma, controllers are not returning correct values when using legacy Lookosn.rec files. Product Line Satchwell BAS & Sigma Environment Satchwell Sigma Cause Sigma does not support the use of Lookosn.rec files. These files are specific to older BAS systems and are incompatible with Sigma’s architecture. Resolution To ensure correct controller behavior in Sigma: Use Lookup.rec Instead of Lookosn.rec : All controller-specific tables must be migrated to the universal Lookup.rec file. Valid Table Range: Ensure that the tables fall within the valid range of 1000 to 1999. Deploying the Tables: Use the Download Lookup Tables feature available in System Diagnostics to send a local copy of Lookup.rec to the controller.

Issue How can a faulty IC-LON or IC3-LON be replaced in LonMaker for Windows without requiring new bindings or additional LNS credits? Product Line Satchwell BAS & Sigma Environment LonMaker Sigma IC-LON Sigma IC3-LON Cause When replacing a faulty IC-LON or IC3-LON, the new hardware will have a different Neuron ID than the original device. This typically raises concerns about re-binding and LNS credit usage. Resolution LonMaker for Windows includes a Replace Device feature that allows you to substitute a device without affecting existing bindings or consuming additional LNS credits. Replacement Procedure Install the Replacement IC3-LON Use SDCU to configure the new IC3-LON on the Sigma network. Coldstart the Device The IC3-LON should automatically coldstart and retrieve necessary files from the Sigma server. If it doesn’t, manually initiate a coldstart. Open the LonMaker Project Launch the LM4W project used to engineer and commission the original IC-LON. Select the Device in the Drawing Right-click the IC-LON device (not the function block) and choose “Replace…”. Run the Replace Device Wizard Select “Use existing template” and click Next. Leave the next screen unchanged and click Next. Set the initial state to “Online” and choose “New device values” for Configuration Properties. Click Next. Choose your preferred method for entering the new service pin and click Finish. Commission the New Device When prompted, press the Service Pin on the IC3-LON LonWorks daughter card. The device will be commissioned and all bindings reasserted. Upload Configuration to Sigma Server Ensure the NvConfig.bin file is uploaded to the Sigma Server. This step is critical to retain binding information after future cold starts.

Issue During an upgrade to Sigma 4.05 SEB, the User and Network device configurations may be lost. This typically occurs when the DeviceCNF.rec and GenCNF.rec files are not properly upgraded. Product Line Satchwell BAS & Sigma Environment Sigma 4.05 SEB Cause Sigma 4.05 SEB introduced changes to the format of the DeviceCNF.rec and GenCNF.rec files. If these files are not correctly upgraded, the system may lose general configuration data, including network and device settings. Resolution To ensure a successful upgrade and preserve configuration data, follow these steps: Shutdown Sigma Services Close both the Sigma Client and Sigma Server on the Sigma 4.05 SEB machine. Prepare a Clean Data Folder Use a clean Sigma 4.05 Data folder—this means a folder created during the original Sigma client/server installation. Do not use complete Data folders from earlier Sigma versions. Copy Backup Files Copy your site-specific Sigma backup files into the clean Data folder. Run the Upgrade Utility Navigate to: C:\Sigma\Binutils\SigUpgrade.exe and run the SigUpgrade.exe utility. Verify File Updates Check the following files in C:\Sigma\Data\ : DeviceCNF.rec GenCNF.rec Confirm that their file dates reflect the recent update. Restart Sigma Services Start the Sigma Server and Sigma Client. Verify that the configuration is intact and functioning as expected.

Issue An outdated site backup was mistakenly used instead of the most recent version. This has led to inconsistencies due to changes made between the two backups. Product Line Satchwell BAS & Sigma Environment Satchwell Sigma Cause A previous version of the site backup was used to add new equipment. As a result, discrepancies may exist between the current site configuration and the outdated backup, potentially causing system errors or data conflicts. Resolution There are two possible approaches to resolve this issue: Option 1: Use the “Doctor” Tool to Identify and Resolve Errors Run Doctor on the current site files to generate an error report. Backup the existing site index files to preserve the current state. Copy the modified (older) backup files onto the system. Run Doctor again and compare the new error report with the original. Investigate any discrepancies: If errors are minor and can be easily corrected, proceed with manual fixes. If errors are significant or cannot be resolved easily, proceed to Option 2. Option 2: Use SigmaX and SigUtils to Rebuild and Merge Site Data Launch SigmaX. Navigate to SigUtils and select “New Site Setup”. Use this function to extract the new equipment from the outdated backup. Create a new site with the extracted equipment. Merge the new site data with the current site to integrate the changes properly.

Issue Understanding the maximum pulse repetition rate and minimum pulse width for pulse/meter points configured on digital inputs. Also, identifying where pulse points can be configured on x96 controllers. Product Line Satchwell BAS & Sigma Environment BAS or Sigma Controllers: UNC532, UNC632, UNCx96 Digital Input Modules (e.g., S-UNC-DI) Cause Clarification needed on configuration limits and locations for pulse/meter points in various controller models. Resolution UNC532 Channels: 1–2 Object Numbers: 81–82 Repetition Rate: 10 Hz Minimum Pulse Width: 50 ms Note: Channels 3–10 (Object Nos. 83–90) configured as pulse objects have a reduced repetition rate of 0.5 Hz UNC632 Channels: 1–10 Object Numbers: 81–90 Repetition Rate: 10 Hz Minimum Pulse Width: 50 ms UNCx96 (with S-UNC-DI module) Channels: 1–16 Object Numbers: 81–96 Repetition Rate: 10 Hz Minimum Pulse Width: 50 ms Important: Pulse objects can only be configured in slot 6 of the controller.

Issue After installing Sigma 4.05 SP1 on a new machine, the client fails to seat (i.e., acquire a license), preventing the application from running. Product Line Satchwell BAS & Sigma Environment Sigma 4.05 SP1 Cause The issue occurs when the Sentinel Protection driver—required for Sigma licensing—is not present on the system. Sigma 4.05 SP1 does not automatically install the Sentinel Protection driver if it is missing. Resolution To resolve this issue: Verify Sentinel Protection Driver Installation Navigate to Control Panel > Programs and Features. Check if Sentinel Protection Installer is listed. If not present, proceed to step 2. Download and Install Sentinel Protection Driver Contact Product Support to obtain the correct version of the Sentinel Protection Installer. Run the installer and follow the on-screen instructions. Restart the computer after installation. Launch Sigma 4.05 SP1 After rebooting, open the Sigma client. Confirm that the client successfully seats and operates as expected. Additional Notes This issue is commonly encountered during fresh installations where the Sentinel driver was not previously installed. For upgrades from earlier Sigma versions, the driver may already be present, avoiding this issue. Ensure administrative privileges are used during installation of both Sigma and the Sentinel driver.

Issue There is no dedicated repeater available in the Sigma product range to extend the maximum distance of a Sigma ARCnet LAN. Product Line Satchwell BAS & Sigma Environment Satchwell Sigma ARCNET communications Cause Sigma does not offer a standalone repeater device. Therefore, alternative methods must be used to extend ARCNET LAN distances beyond standard limitations. Resolution To extend the ARCNET LAN: Use an additional Sigma DNN on the backbone LAN. Connect an ARCNET cable from the first DNN (port 1) to a second Sigma DNN (port 6). Ensure no Sigma controllers are present on the joining LAN segment. The DNN used must be a dual trunk version to support this configuration. 📌 Note: The maximum cable length depends on the baud rate and cable type used. Refer to the ARCNET distance tables for specific limits. ARCNET distances

Building Automation Knowledge Base

Improve your search experience:

Related Forums

Intelligent Devices Forum

Sigma - Integration Controller (IC-Lon): Objects Displaying Default Values

Remote Alarm Manager - System does not respond correctly to "Off Duty" and "On Duty" messages.

Disable Startup Items in Windows (XP to Windows 11)

Licensing Error in RAM Log

How to Display the Date as an Object in Sigma

SigmaX - DLL Registration Failure During Installation

RAM Remote Alarm Manager Message: Alarm on GSM Modem – Unable to Reset GSM Modem

Sigma - USB Tractor feed printer connected to a remote Sigma client.

The SigView_ATK (or SigView) 'List Object' report shows duplicated Object Titles.

ModBMS RUD (Request for Unsolicited Data) Updates Debug

The SMS Nokia mobile phone simulator does not function in RAM 2.0 / 2.1 and Win7

Sigma Low Level Alarm – Operlist.txt File Missing

Sigma – Backing Up User Names and Passwords: Required Files and Folders

Controllers Not Returning Correct Values After BAS Upgrade to Sigma

Replacing a faulty Sigma IC-LON in Lonmaker for Windows.

Sigma - Upgrading the DeviceCNF.rec and GenCNF.rec files.

Sigma - Old site backup has had new site information added to it, but site system has been changed.

Meter Points, Pulse Points Frequency, and Pulse Point Width Configuration

Sigma 4.05 SP1 Client Does Not Seat After New Install

Using a Sigma DNN (Distributed Network Node) as a repeater

Ask our Experts

Email Us

Building Automation Knowledge Base

Related Forums

Ask our Experts

Email Us

Welcome!