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 Not all legacy Satchwell MicroNet devices using the SNP protocol and Intelligent Advanced Controllers (IAC) are supported by Building Operation. This article outlines which MicroNet devices are compatible. Product Line EcoStruxure Building Operation, Satchwell MicroNet Environment Building Operation Satchwell MicroNet devices Cause Not all variants of older Satchwell MicroNet devices that use the SNP protocol and IAC are supported by StruxureWare Building Operation. Resolution To determine compatibility, refer to the Webhelp MicroNet Devices topic (login required). In Building Operation, the term MicroNet device encompasses the following categories: 1. Standard MicroNet Devices MN300 MN440 MN500 MN620 MN LCD MN Touch Screen MicroNet Manager Interface 2. MN 50 Series Devices MN350 MN450 MN550 MN650 MN LCD MN Touch Screen MicroNet Manager Interface 3. SNP & Intelligent Advanced Controller (IAC) Devices MMC3601 MMC4601 IAC400 IAC420 IAC600 IAC Touch Screen Modem Interface Unit 4. Unifact Devices URC2201 URC1201 5. Unifact Pro Devices URC-40N-100 URC-41N-10x URC-50N-100 URC-51N-10x All listed devices are supported within Building Operation versions up to EBO 3.2. ⚠️ Important Notice Satchwell MicroNet is not supported in EBO 2022 and later. To continue supporting MicroNet devices, you can implement a multi-version system: Keep Servers with MicroNet devices on Building Operation 3.2. Upgrade the rest of the system to Building Operation 2022 or later. You will not be able to upgrade EcoStruxure Building Operation servers that contain unsupported protocols, objects, or devices. Attempting to do so will result in failed upgrades or loss of functionality.

Issue After upgrading a site containing MicroNet or IAC controllers from SmartStruxure (SBO) to EcoStruxure Building Operation (EBO), Time and Holiday Schedules no longer display the expected time periods. Product Line EcoStruxure Building Operation Environment Building Operation Workstation (from v2.0.1) Building Operation WebStation (from v2.0.1) Building Operation Enterprise server (from version 2.0.1) Building Operation Automation Server (AS Classic from v2.0.1 to v3.1 and AS-P from v2.0.1) Cause Starting with EBO v2.0.1, support for MicroNet Time and Holiday schedules in WebStation was introduced. This enhancement replaced the legacy SBO schedule objects with TGML-based graphics for both WorkStation and WebStation. As a result, existing schedule objects are no longer automatically visible post-upgrade unless the new TGML graphics are generated. ⚠️ Important Notice Satchwell MicroNet is not supported in EBO 2022 and later. To continue supporting MicroNet devices, you can implement a multi-version system: Keep Servers with MicroNet devices on Building Operation 3.2. Upgrade the rest of the system to Building Operation 2022 or later. You will not be able to upgrade EcoStruxure Building Operation servers that contain unsupported protocols, objects, or devices. Attempting to do so will result in failed upgrades or loss of functionality. Resolution To restore visibility and functionality of MicroNet and IAC schedules: Run the Data Importer on each MicroNet interface. This process generates new TGML schedule objects for all existing MicroNet and IAC Time and Holiday schedules. Verify the Import: After running the Data Importer, confirm that the TGML graphics are created. The trace log will be saved to: C:\ProgramData\Schneider Electric EcoStruxure\Building Operation n.n\DataImport\Trace.DataImport.MicroNet Interface.txt Look for entries such as: Source: C:\Satchwell\Projects Processing XML... Committing to server... Creating object editor graphics (3) ... Object editor graphics created Post-Import: The new TGML graphics will be visible in both WorkStation and WebStation. These graphics represent the updated schedule objects and allow continued use of Time and Holiday scheduling. Additional Notes Refer to the EBO 2.0.1 Release Notes for more details on TGML schedule support. Ensure backups are taken before performing the Data Import. If schedules still do not appear, verify that the MicroNet interface is correctly configured and reachable.

Issue When using a BAS terminal connected to a PIU (Protocol Interface Unit), users may encounter unexplained system messages such as: “Message No. 19920 not available. Please contact Product Support.” These messages indicate that the terminal received a system message from the PIU that is not defined in the local Messages.ini file. Product Line Satchwell BAS & Sigma Environment BAS PIU and Sigma Pre-release 4 System Messages Cause The Messages.ini file used by the BAS terminal has a maximum size limit of 64KB. Due to this constraint, not all possible PIU error messages are included by default. As a result, some messages—especially those from less commonly used subsystems—may be missing. Message Number Ranges by Subsystem Below is a breakdown of message number ranges associated with various subsystems: Subsystem Message Range BAS 1 – 10499 SNP Gateway 10500 – 10999 CHUBB Remote Access 11000 – 11499 CEGELEC 11500 – 11999 OTIS 12000 – 12499 CCURE 12500 – 12999 WORMALD 13000 – 13499 ASIC 13500 – 13999 SIMPLEX 14000 – 14499 CARRIER DATAPORT 14500 – 14999 EXPRESS LIFT 15000 – 15499 CARDKEY 15500 – 15999 Mitsubishi 16000 – 16499 Liebert 16500 – 16999 IMPACC 17000 – 17499 YORK 18000 – 18499 AUTOFLAME 19000 – 19100 AUTOMETERS 19100 – 19199 MITSUBISHI PLC 19200 – 19299 SIEBE MICRONET 19400 – 19499 CROWCON 19500 – 19599 MNI (MicroNet Interface) 19700 – 19799 Colt OPV 19800 – 19899 Resolution To resolve missing message errors: Obtain the full message list: A more complete set of BAS error messages is available in the messages.doc attachment. Update the Messages.ini file: Copy the relevant section from the full message list. Paste it into the C:\Bas\Data\Messages.ini file. Ensure messages are inserted in correct numerical sequence. File Size Limitation: The updated Messages.ini file must not exceed 64KB. If necessary, prioritize messages relevant to your system configuration. Example If your system uses MODBUS and you encounter message 19920, locate the MODBUS section in the full message list and add it to your Messages.ini file.

Issue When performing a Sigma data import into Building Operation, the following error appears on the Enterprise Server (ES) machine: "Failed to connect to server" Simultaneously, the Sigma Server service on the Sigma machine has stopped unexpectedly. Product Line EcoStruxure Building Operation Environment Sigma 4.08 Building Operation Workstation Building Operation Enterprise Server Cause The Sigma database contains a longtext.rec file with unsupported characters, which causes the Sigma Server service to crash during the import process. Resolution Option 1: Longtext Not Required If the Sigma longtext entries are no longer needed: On the Sigma Server: Stop the Sigma Server service. Navigate to C:\Sigma\Data\ and delete the longtext.rec file. Restart the Sigma Server service. On the SBO ES: Retry the Sigma data import. Option 2: Longtext Required If longtext entries are still needed: On the Sigma Server: Start the Sigma Server service. Open a Sigma client (can be on the Sigma server, SBO ES, or another machine). Log into the Sigma Operator Panel. Go to System Alarm Manager → Configure → Longtext. Review each longtext entry and remove unsupported characters. Re-enter the required longtext messages. You may find backup copies in C:\Sigma\Data\Longtext . On the SBO ES: Retry the Sigma data import. Once the unsupported characters are removed or the file is deleted, the Sigma Server service remains stable, and the data import completes successfully.

Issue Users running VisiSat 2.1 Build 185 or 196 on Windows XP Pro with Visio 2003 may encounter the following error: Internal Error 0x86DB08A9 VisiSat “CustomiseUI” add-on not found or not registered in Visio. Environment VisiSat 2.1 Build 185 / 196 Visio 2003 Windows XP Professional Cause Visio 2003 may fail to recognize or register the CustomiseUI component during VisiSat installation. This is typically due to: Missing or corrupted installation files. Residual file path entries in Visio that interfere with VisiSat integration. Resolution To resolve the issue, follow these steps: Open Visio 2003 (not VisiSat). Navigate to: Tools → Options → Advanced tab → File Paths . Delete all entries in the File Paths dialog. Click OK to confirm and close all dialogs. Close Visio 2003. Launch VisiSat. ✅ VisiSat should now start correctly. 🔁 If you reopen Visio 2003, the file paths should reappear, confirming successful integration. Additional Recommendations If you're running Windows XP + Visio 2003, consider using VisiSat 2.1 Build 148, which has broader compatibility. For Windows 7 users, upgrading to Visio 2007 or 2010 may improve stability and compatibility with newer VisiSat builds. 📥 Download VisiSat 2.1 Build 148 (42 MB) Note: You’ll need your original VisiSat registration form (v2.0/2.1) to unlock this version. Related Articles VisiSat 2.1 Build 196 Installation Guide – Visio 2010/2016 Compatibility

Issue After installing VisiSat 2.1 Build 196, users report that the VisiSat tools are not visible within Visio. Product Line Satchwell MicroNet Environment Visio 2010 Visio 2016 VisiSat 2.1 Build 196 Cause Visio 2010: May require macro and file trust settings to be adjusted. Visio 2016: Not officially supported by VisiSat 2.1 Build 196; compatibility is unverified and may result in inconsistent behavior. Resolution For Visio 2010: Install Visio 2010. Launch Visio and navigate to: File → Options → Trust Center → Trust Center Settings Under Macro Settings, select: Enable All Macros Save changes and close Visio. Restart Windows. Install VisiSat 2.1 Build 196. Open Visio — the VisiSat tab should now be visible. ⚠️ For Visio 2016 (Unsupported Configuration): Although not officially supported, some users have attempted the following steps: Install Visio 2016. Navigate to: File → Options → Trust Center → Trust Center Settings Under Macro Settings, select: Enable All Macros Under File Block Settings, uncheck file types you wish to open/save. Save changes and close Visio. Restart Windows. Install VisiSat. Open Visio — the VisiSat tab may appear. ⚠️ Note: Occasional errors may occur when accessing the VisiSat “Options” menu. These errors are typically non-critical and do not affect functionality. Additional Notes: Visio 2016 is not officially tested or supported with VisiSat 2.1 Build 196. Use at your own risk.

Issue The sort order of Areas displayed on different keypads is inconsistent when scrolling through them. Product Line EcoStruxure Security Expert Environment Security Expert SX-KLCS Keypad Cause In the keypad configuration, the "Area this LCD belongs to" setting determines the primary Area associated with the keypad—typically the Area where the keypad is physically installed. This Area is intended to appear first when a User logs in. Keypad Area If this setting is left as <not set>, the keypad will default to sorting Areas by their Area ID, rather than prioritizing a specific primary Area. Resolution The order in which Areas appear on the keypad is determined by the Access Levels assigned to the User who logs in. Specifically: The keypad displays Areas in the order they are defined within the User’s Access Levels. To ensure consistent Area sort order across all keypads, the Access Levels must be assigned in the same order for each User record. Important: Once Access Levels are added to a User record, they cannot be re-ordered. To change the order: Remove all Access Levels from the User record. Reassign them in the desired order.

Issue When attempting to start SigmaSvr for the first time after installing Sigma 4.08, the following error appears: Windows could not start the SigmaSvr service on Local Computer. Error 1067: The process terminated unexpectedly. Product Line Satchwell Sigma Environment Satchwell Sigma Software (Sigma 4.08) Cause This issue typically occurs when the Sigma USB dongle is not plugged in during the initial startup of the Sigma Server. Without the dongle, the service fails to initialize properly, and a .dmp (dump) file is generated in the Sigma directory after each failed attempt. Resolution Insert the Sigma USB Dongle Ensure the dongle is securely connected to the machine. Allow Driver Installation Wait for Windows to detect and install the necessary drivers for the dongle. Start the Sigma Server Launch the SigmaSvr service from Windows Services. Clean Up Dump Files Navigate to the Sigma installation directory and delete any .dmp files created during previous failed attempts.

Issue The MN50-RTC battery power is low, requiring a replacement to maintain proper timeclock and memory functions. Product Line Satchwell MicroNet Environment MN50-RTC Warning Electrostatic Discharge Required: Always discharge static electricity from your person by touching metal prior to handling any hardware. Failure to do so may result in damage to devices. Cause The internal CR1632 battery has depleted due to age or extended use, resulting in insufficient power retention. Resolution Replace the internal battery with a CR1632 3V 125mAh lithium coin cell. ⚠️ Important Notices The MicroNet 50 series controllers (MN350, MN450, MN550, MN650 LCD and Touchscreen) have been withdrawn from sale. The IAC 420, IAC 600, and Touchscreen models have also been discontinued. No direct replacements are currently offered. For more details, refer to: PA-00495 - Notice of Withdrawal - Satchwell Sigma (PDF) PA-00528 - End of Commercialization - Satchwell Sigma (PDF)

Issue Guidance is required for configuring a Sigma Distributed Network Node (DNN) when connecting it to a "Flat" Ethernet network. Product Line Satchwell BAS & Sigma Environment Satchwell Sigma Ethernet network Ethernet or ARCnet subnets Cause General configuration advice for ensuring proper communication between Sigma controllers and the network via the DNN. Resolution What Is a Flat Ethernet Network? A flat Ethernet network is a network architecture where all devices share the same broadcast domain and IP subnet. There are no routers or subnets separating groups of devices. All devices can communicate directly without routing. Typically uses a single IP range and subnet mask, such as 10.158.0.0/16. Simplifies configuration but may lead to scalability and performance issues in larger environments. Network Configuration On a flat Ethernet network, the DNN requires only: IP address Subnet mask These settings, along with the DNN’s “Default Server” information, should be configured using the Sigma Device Configuration Utility (SDCU). Routing Configuration RIP (Routing Information Protocol) is enabled by default on the DNN. If RIP is enabled, the DNN will broadcast the route to the sublan. If RIP is disabled, a persistent route must be manually added to the Sigma server. Refer to the article: Persistent routing on the Sigma server for detailed steps. Modifying RIP Settings via Pocket Terminal Disable RIP on port 5: Launch Pocket Terminal Enter: RIPD 5 Click Send Enable RIP on port 5: Launch Pocket Terminal Enter: RIPE 5 Click Send Check RIP status: Enter: RIPS Click Send

Issue Some SNVTs (Standard Network Variable Types) are not updating correctly within the Sigma IC-LON. Product Line Satchwell BAS & Sigma Environment Satchwell Sigma IC-LON / IC3-LON Cause The issue arises when LON bindings are not configured using the correct “Sigma” connection type. If the IC-LON Plug-in does not create or apply this connection type properly, SNVT updates may fail or behave inconsistently. Resolution Review the IC-LON Configuration Document Refer to the attached document: 01.08.22-4_PIB ICLON Configuration.pdf This guide includes detailed steps for setting up the IC-LON Plug-in and selecting the correct connection type. Ensure “Sigma” Connection Type is Used The IC-LON Plug-in must create a connection type labeled “Sigma”. The Service Type should be set to “Unackd” and "Use Broadcast" set to Yes in the advanced settings. Verify Bindings Confirm that all SNVT bindings use the correct connection type. Incorrect types will prevent proper communication and updates.

Issue Sigma controllers require accurate interpretation of resistive analogue input (AI) signals. When using non-standard sensors such as 10k Type 2 or Type 3 thermistors, incorrect resistance values can trigger hardware alarms or result in inaccurate readings. A custom lookup table must be created to ensure proper operation. Product Line Satchwell BAS & Sigma Environment Satchwell BAS & Sigma UNC controllers Cause Sigma controllers interpret resistance values as a percentage of a 2V signal at the A/D converter. The default lookup tables are designed for specific sensor types (e.g., D?T range). When integrating other resistive sensors like 10k Type 2 or Type 3 thermistors, the controller may not recognize the input correctly, leading to hardware alarms or misread values. A custom lookup table is required to translate resistance values into valid input percentages. Resolution Step-by-Step Process to Create a Lookup Table Gather Sensor Data Obtain resistance values at various temperatures from the sensor’s datasheet Use the Sigma Calculation Formula R1*250 / R1+14700 Where: R₁ = Sensor resistance 14700 = Resistor value on the AI card The circuit shown below is a typical example of an AI channel for a resistance input. To ensure the circuit resistance does not exceed 10kΩ, it is recommended to place a 10kΩ shunt resistor in parallel with the sensor. Create the Lookup Table Object Enter the calculated input values into a new lookup table object in Sigma. Ensure the table covers the full operating temperature range of the sensor. Assign the Table to the AI Object Link the custom lookup table to the relevant analogue input object in Sigma. Download and Apply Use Sigma System Setup and Diagnostics to build and download the new lookup table to the controller. Verify Operation Check that the AI object displays correct temperature values. Use programmable objects if additional formatting or scaling is needed. Examples Type 2 Resistances.pdf Type 3 Resistances.pdf Lookup Table Details Column C: Raw sensor resistance Column D: Controller input resistance with 10kΩ shunt resistor Columns E & F: Example lookup table values (percentage of 2V signal)

Issue Is the BAS2800+ software compatible with Windows Vista, Windows 7, or newer operating systems? Product Line Satchwell BAS & Sigma Environment Satchwell BAS 2800+ Cause Customers may attempt to install BAS2800+ versions 2.9 or 2.10 on modern Windows platforms. Clarification is needed regarding supported environments and potential risks. Resolution BAS2800+ versions 2.9 and 2.10 have been officially tested and supported only on the following operating systems: Windows NT Windows 2000 Windows XP Windows Server 2003 The software has not been tested or validated on: Windows Vista Windows 7 Windows 8 Windows 10 ⚠️ Important Notice: Installing BAS2800+ on unsupported operating systems may result in unpredictable behavior. Schneider Electric does not guarantee functionality and will not accept liability for any issues encountered. Recommendations Preferred Option Install BAS2800+ on a physical machine running Windows XP or Windows Server 2003 for full compatibility. 💡 Alternative Option: Use a Virtual Machine (VM) If a legacy physical system is unavailable, consider running BAS2800+ inside a virtual machine configured with a supported operating system. ⚠️ Note: While this method can be effective, it is not officially supported or tested by Schneider Electric. Use at your own discretion. Additional Notes The BAS2800+ product was discontinued in 2008. No further updates or compatibility testing will be conducted for newer operating systems.

Issue Can Sigma system controllers sit on multiple VLANs?Can Sigma system controllers operate across multiple VLANs? Product Line Satchwell BAS & Sigma Environment Sigma UNC controllers Cause This is a common question raised by IT departments when planning to upgrade BAS systems to Sigma. Resolution Yes, Sigma controllers can be deployed across multiple VLANs. However, there are important considerations to ensure proper communication between devices: 1. Global Data Communication Sigma global data is transmitted using the Ethernet broadcast address. Most routers block broadcast messages between VLANs. To enable global data exchange across VLANs, Link Addressing must be configured. 2. Link Addressing Requirements Link Addressing acts as a tunneling mechanism to allow broadcast data to traverse VLAN routers. A DNN (Data Network Node) must be added to each sub-LAN to support Link Addressing. For detailed configuration steps, refer to Link Addressing on a Sigma System 3. Default Gateway Configuration All Sigma devices must be configured with appropriate default gateway IP addresses: Controllers: Use the Pocket Terminal command: GW + 192.168.0.1 (Replace 192.168.0.1 with the actual default gateway of the local network.) DNNs: Set a Static Route as defined in the article: "Having set Link Addressing in a Sigma DNN3 can no longer communicate..." Sigma Servers: Set the default gateway via: Network Settings > Internet Protocol (TCP/IP) > Properties Recommendation While Sigma controllers can operate across VLANs, a flat VLAN architecture is generally simpler to configure and maintain. Use multiple VLANs only when necessary and ensure all Link Addressing and gateway configurations are correctly implemented.

Issue Battery replacement required for MicroNet LCD units. Product Line Satchwell Micronet Environment Satchwell MicroNet LCD Cause The MicroNet 50 series (MN350, MN450, MN550, MN650) LCD and touchscreen models, along with IAC 420, IAC 600, and touchscreen variants, have been withdrawn from sale due to product obsolescence. No direct replacements are currently offered. Resolution Although the devices are no longer commercially available, the replacement battery is still obtainable. Battery Type: LS14500 Recommended Supplier: RS Components For further details on product withdrawal, refer to the following official notices: PA-00495 - Notice of Withdrawal - Satchwell Sigma PA-00528 - End of Commercialization - Satchwell Sigma

Issue Cannot commission an IC3 LON controller in LonMaker. It has become applicationless and the red service LED is flashing or permanently lit. Product Line Satchwell BAS & Sigma Environment Satchwell Sigma IC-LON/IC3-LON Cause The Echelon chip may become 'locked' due to: Corrupted controller files Excessive LON network traffic (>50% bandwidth) Cold start or startup mode triggering a reset Resolution Although hardware replacement is no longer an option due to the discontinuation of the S-LON plug-in card, the following recovery steps may help restore controller functionality: For Flashing Red LED Download a clean set of controller files to the IC3 controller. Launch NodeUtil.exe on a laptop with an FTT-10 Echelon adapter. Connect the LON cable to the controller. Press the onboard reset button on the controller. Activate the service pin on the LON card; the Neuron ID should appear in NodeUtil. In NodeUtil, select R to reboot the 3150 node and enter the Node ID. Confirm the reset when prompted. The service LED should stop flashing, indicating the controller is no longer applicationless. ⚠️ Note: If repeated resets and service pin activations fail to generate a response, and hardware replacement is not an option, the controller may no longer be recoverable. Consider isolating the device and consulting with technical support for further guidance. For Permanently Lit Red LED Download clean controller files. Repeat the NodeUtil reset procedure as above. If the Echelon chip locks again, repeat the reset process. Alternative Recovery Procedure (Customer-Provided) If the standard reset does not resolve the issue, the following steps have been reported to help: Disconnect the IC LON from both the LON and Sigma networks. Use the SCDU tool to re-node the IC LON to a temporary IP address. Power off the IC LON and remove the LON daughterboard. Power on the mainboard without the daughterboard, then reinstall the daughterboard. Reconnect using NodeUtil and clear the LON communication buffers. Verify that the red service LED is off and the green LON heartbeat LED is active. Re-node the IC LON to its original IP and verify operation. Important Notice The Sigma IC-LON plug-in card (S-LON) has been discontinued as of 29 December 2017 and is no longer available for replacement. All troubleshooting must be performed using existing hardware.

Issue When attempting to upgrade a MicroNet legacy controller to a MicroNet 50 Series controller in VisiSat, the upgrade option appears grayed out and unavailable. Product Line Satchwell MicroNet Environment VisiSat version 2.0 VisiSat version 2.1 Cause VisiSat version 2.1 introduced support for upgrading legacy MicroNet controllers (MN300, MN440, MN500, MN620) to 50 Series controllers (MN350, MN450, MN550, MN650). However, if the original project was created using VisiSat 2.0 or earlier, the upgrade option will be disabled (grayed out) due to missing stencil data for the 50 Series. Resolution ⚠️ Important Notices The MicroNet 50 series controllers (MN350, MN450, MN550, MN650 LCD and Touchscreen) have been withdrawn from sale. The IAC 420, IAC 600, and Touchscreen models have also been discontinued. No direct replacements are currently offered. For more details, refer to: PA-00495 - Notice of Withdrawal - Satchwell Sigma (PDF) PA-00528 - End of Commercialization - Satchwell Sigma (PDF) To enable the upgrade path in VisiSat 2.1: Save the configuration of the existing MicroNet *00 Series controller to disk. Delete the controller from the project. Insert a new MicroNet legacy controller onto the main page. Assign the original address to the new controller. Load the saved configuration from step 1. Once these steps are completed, the upgrade option should now be available.

Issue The Sigma Web Client uses an ActiveX interface, which is only compatible with specific versions of Microsoft Internet Explorer (IE). Later versions of IE and other modern browsers (e.g., Edge, Chrome, Firefox) do not support ActiveX, leading to display or functionality issues. Product Line Satchwell BAS & Sigma Environment Sigma 4.3 and later Cause ActiveX is a legacy technology supported only by Internet Explorer. As Microsoft phases out IE in favor of Edge and Chromium-based browsers, compatibility issues arise when accessing Sigma Web Client interfaces. Resolution Sigma 4.3 introduced the ActiveX-based web client. The following table outlines compatibility between Sigma versions and Internet Explorer across various Windows operating systems: Operating System/Sigma Version 4.08 4.07 4.06 4.05 4.04 4.03 Microsoft ® Windows 2000 IE6 IE7 IE6 IE7 Microsoft ®Windows XP IE7 IE8 IE7 IE8 IE7 IE8 IE6 SP3 IE7 IE8 IE6 IE7 IE6 IE7 Microsoft ® Windows Server 2003 IE7 IE8 IE7 IE8 IE7 IE8 IE6 SP3 IE7 IE8 IE6 IE7 IE6 IE7 Microsoft ® Windows 7 IE8 IE9 IE8 IE8 IE8 Microsoft ® Server 2008 N/A N/A N/A N/A Note: Later versions of Internet Explorer may work in Compatibility View, but are not officially supported. Recommendations for Later Operating Systems (Windows 10/11) Use Internet Explorer Mode in Microsoft Edge: Microsoft Edge (Chromium) includes an IE Mode that supports legacy ActiveX controls. To enable IE Mode: Open Edge and go to Settings > Default Browser. Enable Allow sites to be reloaded in Internet Explorer mode. Restart Edge and reload the Sigma Web Client in IE Mode. Virtual Machine Workaround: If IE Mode is not viable, consider running a virtual machine with Windows 7 or Windows XP and a compatible version of IE. Long-Term Strategy: Consider migrating to newer platforms or interfaces that do not rely on ActiveX, as support for IE and ActiveX is being deprecated across the industry. Additional Notes ActiveX is not supported in Chrome, Firefox, or Safari. Ensure that ActiveX controls are enabled in IE security settings. Compatibility View may help with rendering issues in newer IE versions.

Issue After a Schneider Electric domain policy update, some engineer laptops experience issues where the Sigma client fails to connect to the server, despite previously functioning correctly. No error message or HTTP error is displayed. Product Line Satchwell BAS & Sigma Environment Satchwell Sigma Scheider Electric Computer Cause The issue has been linked to firewall updates pushed via Schneider Electric's domain policies. These updates include changes to the Trellix firewall (formerly McAfee), which may block Sigma from launching or connecting properly. Resolution Access to firewall settings is typically restricted on Schneider Electric engineer laptops. However, a temporary workaround is available: Locate the Trellix icon in the taskbar near the system clock. Right-click the icon and select Quick Settings. Choose Enable Firewall Timed Groups. Enter a reason when prompted. This will disable the firewall for one hour, allowing Sigma to launch and connect successfully.

Issue Multiple defects were identified in VisiSat 2.1 Build 196, affecting functionality, export reliability, character encoding, and memory management. These issues impacted integration with StruxureWare Building Operation and the handling of MicroNet engineering files. Product Line Satchwell MicroNet Environment Satchwell VisiSat 2.1 build 196 Cause Legacy limitations in character handling and export formatting Improper object disposal during export routines Encoding mismatches for non-ASCII characters Incomplete validation logic for interface exports Lack of error handling for blank point lists Resolution Service Pack 1 (Build 200) Fixes Included: ARCnet Debug Tool Property editor now functions correctly in the ARCnet debug Excel spreadsheet. (Defect 1633) Export Enhancements Point names now support up to 32 characters; descriptions up to 50 characters. (Defect 1706) MicroNet Interface Handling MicroNet Interfaces are no longer exportable/importable via StruxureWare WorkStation. All engineering must be completed in VisiSat before import. (Defect 1765) Point List Stability Blank point lists can now be saved without triggering errors. (Defect 1784) Memory Leak Fix Exporting to StruxureWare no longer causes memory leaks. (Defect 1808) Installation Instructions: Ensure VisiSat 2.1 Build 196 is installed. Download and apply Service Pack 1. Note: Control Panel may still display build as 2.1.196 after installation. Service Pack 2 (Build 201) Fixes Included: Character Encoding Correction Non-ASCII characters in import files are now correctly converted. (Defect 31467) Alarm and Trend Point Import Points with alarms and trends are now properly included in import files. Installation Instructions: Ensure Service Pack 1 is already installed. Shut down VisiSat and VisiSat-Server. Run VisiSat 2.1.196 Service Pack 2.exe . Extract to the VisiSat installation root (or extract elsewhere and move the Satchwell folder to C:\ ). When prompted to replace existing files, select "Yes to All". Restart VisiSat. After installation, build number updates to 2.1.201, but may still appear as 2.1.196 in Control Panel. Download Service Pack 2.

Building Automation Knowledge Base

Improve your search experience:

Related Forums

Intelligent Devices Forum

Building Operation: Supported MicroNet Devices

MicroNet and IAC Time and Holiday Schedules Not Functioning After Upgrading from SBO to EBO

Sigma IC & BAS PIU Error Messages

"Failed to Connect to Server" During Sigma Data Import to EBO

VisiSat 2.1 Build 185/196 – “CustomiseUI” Add-on Not Found in Visio

VisiSat 2.1 Build 196 Installation with Visio 2010 / 2016 – Compatibility and Setup Guide

How Areas are sorted when viewed on a Keypad

Windows Error 1067 When Starting SigmaSvr in Windows Services

What is the replacement battery for the MN50-RTC

Sigma DNN Configuration for Flat Ethernet Networks

Sigma IC-LON: SNVTs Not Updating Due to Incorrect Connection Type

Creating and Using Lookup Tables for Resistive AI Devices in Sigma Controllers

Satchwell BAS 2800+ Operating System Compatibility

Considerations for Sigma System Controllers on Multiple VLANs

Where Can a Replacement Battery for a MicroNet LCD (Low Cost Display) Be Purchased?

Sigma LON Card is Applicationless and Cannot Be Reset by IC3 LON Controller

Upgrade to a MicroNet 50 Series Option Grayed Out in VisiSat

Sigma Web Client Browser Compatibility

Sigma Will Not Launch – No Error Message or HTTP Error Displayed

VisiSat Version 2.1 Build 196 – Service Pack 1 & 2 Overview

Ask our Experts

Email Us

Building Automation Knowledge Base

Related Forums

Ask our Experts

Email Us

Welcome!