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 Upgrading a MicroNet 100 series LON controller to a MicroNet 50 series LON controller results in the loss of reference in/out objects and LON SNVT bindings. Product Line Satchwell MicroNet Environment Satchwell VisiSat Software Cause The upgrade process removes various items and objects from the original scheme, which can disrupt system functionality and data integrity. 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) Upgrade Guidance To minimize disruption during the upgrade: Review the full upgrade precautions in the document: MicroNet 100 to 50 Series Upgrade Precautions (PDF) Backup your existing configuration before initiating the upgrade. Document all reference in/out objects and SNVT bindings to manually reconfigure them post-upgrade. Validate compatibility of your VisiSat software version with the target controller. Consider alternative solutions if your application relies heavily on features removed during the upgrade. Additional Resources MicroNet 50 Series Controller MLis and Data Sheets MicroNet 100 Series Controller MLis and Data Sheets Tables and Offsets for MicroNet 50, 100 Series, and IACs Replacing Satchwell MicroNet Controllers with MicroNet 50 Series Equivalents See MicroNet 100 to 50 series upgrade precautions.pdf to view more detailed information.

Issue When launching SigmaX, the following error appears: "This application failed to start because side-by-side-configuration is incorrect." Reinstalling SigmaX does not resolve the issue. Product Line Satchwell Sigma Environment SigmaX Cause This error typically occurs due to: Missing or corrupted system files. Missing Microsoft Visual C++ Redistributable packages required by SigmaX. Resolution Run System File Checker (SFC) Use the System File Checker tool (SFC.exe) to identify and repair corrupted system files. Steps: Open an elevated Command Prompt: Click Start > All Programs > Accessories Right-click Command Prompt and select Run as administrator If prompted, enter the administrator password or click Allow Type the following command and press Enter: sfc /scannow This command scans all protected system files and replaces incorrect versions with correct Microsoft versions. Do not close the Command Prompt window until the verification reaches 100%. For more details, refer to Microsoft’s documentation: KB929833 Install Microsoft Visual C++ Redistributable The SFC scan will not detect missing Visual C++ Redistributables. Ensure the appropriate version of Microsoft Visual C++ Redistributable is installed. Refer to the article: Error when trying to run SigmaX.exe and RegSigmaX.exe for guidance on which version to install. Additional Notes The error may also affect RegSigmaX and SigView. Ensure your Windows installation is fully updated before running SigmaX.

Issue Users are unable to locate the documentation for the IC3-Modbus controller used in Sigma systems. Product Line Satchwell BAS & Sigma Environment Sigma IC3-Modbus Cause Documentation for the IC3-Modbus controller is not easily accessible or clearly linked within the Sigma support resources. Resolution The following resources are available for download to assist with IC3-Modbus configuration and integration: 📄 IC3-Modbus Gateway Configuration File Download Gateway_IC3-Modbus_R4_05.txt 📘 IC3 Configuration Guide Download Cguide34_IC3.pdf 📑 IC3-Modbus Data Sheet Download DS-13.684_0610_Modbus-Integration-Controller_Data-Sheet.pdf

Issue Clarification is needed regarding which Modbus data types are compatible with Sigma IC3-Modbus, particularly concerning 64-bit support. Product Line Satchwell Sigma Environment Satchwell Sigma IC3 Modbus Cause Documentation does not explicitly mention support for 64-bit data types, leading to uncertainty. Resolution ✅ 16-bit Registers: Fully supported across all Sigma versions. ✅ 32-bit Registers: Supported from Sigma Release 4_05-SEB (Build 3_43_18) onwards. Refer to Sigma IC-Modbus - Reading 32 Bit Integer values from two 16 Bit registers for engineering guidance. ❌ 64-bit Registers: Not supported with Sigma IC3-Modbus.

Issue How to decode individual on/off states from a Modbus analogue register (e.g., Holding or Input registers) using bit masking. Each bit represents the status of a coil and needs to be read separately. Product Line Satchwell Sigma Software Environment Sigma IC Modbus and IC3 Modbus controllers Cause Modbus registers are 16-bit values. Each bit (0 or 1) represents the on/off state of a coil. To interpret these states, bit masking is used to isolate and evaluate each bit. Resolution Each Modbus register contains 16 bits. For example, a value of 901 in Sigma translates to the binary 0000001110000101 , where: 1 = ON 0 = OFF To decode each bit: Create a Sigma analogue input object to read the Modbus value. Create a programmable object for each bit (up to 16 per register). Example Code Snippets Assuming POINT 0|222 is the Modbus value object, here’s how to decode each bit: Bit 1 (LSB) 10 XINT = INT POINT 0|222 20 YINT = XINT MASK ( 1 ) 30 IF YINT = 1 THEN RETURN TRUE "Bit 1 = on" 40 RETURN FALSE "Bit 1 = off" Bit 2 10 XINT = INT POINT 0|222 20 YINT = XINT MASK ( 2 ) 30 IF YINT = 2 THEN RETURN TRUE "Bit 2 = on" 40 RETURN FALSE "Bit 2 = off" `` Bit 3 to Bit 16 Repeat the pattern above, updating the mask value as follows: Bit Mask Value 3 4 4 8 5 16 6 32 7 64 8 128 9 256 10 512 11 1024 12 2048 13 4096 14 8192 15 16384 16 (MSB) 32768

Issue Unwanted hardware alarms (and other alarms) are being received at the Enterprise Server from Sigma controllers. Product Line Satchwell BAS & Sigma, EcoStruxure Building Operation Environment EcoStruxure Building Operation Sigma Release 4_08 (Build 3_46_57) Cause Sigma controllers are configured to send hardware and other system alarms to the Enterprise Server, which may not be required in certain operational contexts. Resolution To disable these alarms: Access the Sigma Interface: Navigate to the Sigma interface within EcoStruxure Building Operation. Locate the Controller (OSN): Identify the controller from which you want to disable alarms. Modify Device Monitoring Settings: Select the controller. Go to the Basic tab in the Properties panel. Locate the Device Monitoring setting. Set it to Disabled to stop hardware and system alarms from being sent. Bulk Update (Optional): If multiple controllers need to be updated: Multi-select the required controllers. Open the Property Panel. Change the Device Monitoring setting for all selected controllers simultaneously.

Issue Guidance is needed for configuring the Remote Alarm Manager (RAM), including understanding its components, available documentation, and script customization. Product Line Satchwell BAS & Sigma, Satchwell MicroNet, TAC Vista Environment Remote Alarm Manager Cause RAM configuration involves multiple components such as: Configuration Controller Monitoring Scripts Output Interfaces Users may encounter challenges due to the complexity of these elements or lack of familiarity with scripting in RAM. Resolution To assist with setup and customization, three key guides are available: Operator’s Manual Basic usage and interface overview Ideal for day-to-day operations Engineer’s Manual More comprehensive than the Operator’s Manual Covers advanced configuration and troubleshooting Script Editor’s Guide Details on customizing and adapting scripts Useful for tailoring RAM behavior to specific site needs 📁 Location of Scripts: Scripts used by RAM are located in: C:\Satchwell\Binary\Remote Alarm Manager File extension: .scr Best practice: Copy and rename scripts before editing to preserve originals.

Issue Customers without access to the EcoXpert Extranet or internal storage systems may struggle to locate data sheets for MicroNet 100 series products. Product Line Satchwell MicroNet Environment MicroNet 100 series products Cause To support customers who do not have access to Schneider Electric’s internal or partner websites. Resolution Please note, Satchwell MicroNet has been withdrawn from sale and no direct replacements are available. For more details, refer to: PA-00495 - Notice of Withdrawal - Satchwell Sigma (PDF) PA-00528 - End of Commercialization - Satchwell Sigma (PDF) Available Downloads You can download individual MLis and data sheets for the following components: Displays & Interfaces MicroNet LCD Displays MicroNet Touch Screens MicroNet Touch Screen User Guide MicroNet Manager Interfaces Sensors S-Link Sensors Mounting & Expansion Kits MN Trunking Kits (MN-TK) MN Wall Mounting Kits (MN-DK) Plug-In Cards Controllers Satchwell MicroNet MN300 Satchwell MicroNet MN440 Satchwell MicroNet MN500 Satchwell MicroNet MN620 💾 Download All Files (ZIP, 10.50 MB) For MicroNet 50 Series documentation, visit: MicroNet 50 Series Controller MLis and Data Sheets

Issue TCustomers without access to the EcoXpert Extranet or internal storage systems may struggle to locate data sheets for MicroNet 50 series products. Product Line Satchwell MicroNet Environment MicroNet 50 series products Cause To support customers who do not have access to Schneider Electric’s internal or partner websites. Resolution Please note, Satchwell MicroNet has been withdrawn from sale and no direct replacements are available. For more details, refer to: PA-00495 - Notice of Withdrawal - Satchwell Sigma (PDF) PA-00528 - End of Commercialization - Satchwell Sigma (PDF) Available Downloads You can download individual MLis and data sheets for the following components: Displays & Interfaces MicroNet LCD Displays MicroNet Touch Screens MicroNet Touch Screen User Guide MicroNet Manager Interfaces Sensors S-Link Sensors Mounting & Expansion Kits MN Trunking Kits (MN-TK) MN Wall Mounting Kits (MN-DK) Plug-In Cards Controllers Satchwell MicroNet MN350 Satchwell MicroNet MN450 Satchwell MicroNet MN550 Satchwell MicroNet MN650 💾 Download All Files (ZIP, 10.50 MB) For MicroNet 100 Series documentation, visit: MicroNet 100 Series Controller MLis and Data Sheets

Issue When launching the Sigma Client, the error "HTTP connection failed" is displayed, preventing the client from starting. Product Line Satchwell Sigma Environment Satchwell Sigma release 4.05 and later Cause The Sigma Client fails to establish a connection with the Sigma Server due to various system, network, or software-related issues. Resolution Below are the recommended troubleshooting steps, organized by category for clarity: Operating System Compatibility Windows XP: Ensure Service Pack 3 is installed and all updates are applied. Windows 7: Only Ultimate and Professional editions are supported. Installation & Permissions Sigma software must be installed by a user with Administrator privileges. Verify that the SigmaSVR service is running. If missing, reinstall Sigma as an Admin user. If user profile corruption is suspected, create a new Windows Admin user and test Sigma. Firewall & Network Settings Disable Windows Firewall or configure exceptions as per the Sigma 4.05 SP1 release notes. If using a proxy server (common in school networks): Go to Control Panel > Internet Options > Connections > LAN Settings Check "Bypass proxy server for local addresses" On SE laptops, update McAfee/Trellix firewall settings: Right-click McAfee/Trellix icon > Quick Settings > Enable Firewall Timed Groups Add a reason (e.g., "Sigma") to allow a 1-hour access window. Virtualization & Hardware If using a VMware image, try rebooting the image. If Sigma was installed while connected to Wi-Fi, uninstall it, disable Wi-Fi, enable Ethernet, and reinstall. Third-Party Software Conflicts Sophos Antivirus may quarantine Sigma DLLs. Uninstall Sophos and Sigma, reinstall Sophos (latest version), then reinstall Sigma. Flexera License Software may conflict on port 8080. Stop Flexera or change Sigma to use port 8081. StruxureWare Building Operation PCS also uses port 8080. Stop PCS to avoid conflicts. System Configuration Check the port number in C:\\Sigma\\bin\\setupsvr.exe . Default is 8080. On DELL PCs, vendor-specific background services may interfere. Reinstall Windows without vendor apps and reinstall Sigma. If the computer name contains extended ASCII or Unicode characters (e.g., “P á st”), rename it to a standard ASCII name (e.g., “Past”). Clean Reinstallation Backup Sigma data. Uninstall Sigma via Add/Remove Programs (XP) or Programs and Features (Win 7). Rename or delete the C:\\Sigma folder (e.g., rename to Sigma1 ). Reinstall Sigma using right-click > Run as Administrator on SigmaSetup.exe . Reboot the PC and verify the Sigma Server is running.

Issue Integrating a MicroNet 100 series LON controller/network into EcoStruxure Building Operation (EBO). Product Line Satchwell MicroNet Environment Satchwell MicroNet MNN-30-100 Satchwell MicroNet MNN-44-100 Satchwell MicroNet MNN-50-100 Satchwell MicroNet MNN-62-100 Satchwell MicroNet MNL-C 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 MicroNet 100 series LON networks are not natively supported in EcoStruxure Building Operation. Since the release of the MicroNet 50 series in 2008, support for MicroNet 100 series controllers with LON cards has been discontinued. Resolution Option 1: Use a Third-Party LON Management Tool Bind MicroNet 100 series LON controllers to a standard LON network using tools like LonMaker® for Windows® (by Echelon). Import the network into AS-P as a standard LON network. Option 2: Convert to NCP Network ⚠️ Important: MicroNet NCP networks are not supported in EBO version 2022 (4.0) and later. This option is only viable for systems running EBO 3.x or earlier. If using EBO 3.x or earlier: Remove LON Cards Detach LON cards from MicroNet 100 series controllers. Restore Jumpers Reconnect jumpers on the top two pairs of pins of the auxiliary card plug. Replace Cabling Replace LON cabling with RS-485 compatible cable (e.g., Belden 8762 or equivalent). Reconfigure Controllers Use VisiSat to reprogram controllers for NCP communication. Import into AS-P Import the reconfigured network into AS-P under a MicroNet NCP interface. Touchscreen Limitation MicroNet LON touchscreens cannot be converted to NCP and must be removed. Resources MicroNet 100 Series Controller MLi's and Data Sheets VisiSat 2.1 Build 196 – Software VisiSat Release 2.1.196 Service Pack 1 VisiSat Release 2.1.196 Service Pack 2 Additional Notes For systems running EBO 4.0 and later, Option 1 is the only viable integration path. Ensure compatibility of cabling and controller firmware before conversion.

Issue The Sigma Compact Edition previously supported specific Windows CE-based hand-held devices, including: iPAQ 114 iPAQ 214 iPAQ 2490b Dell Axim X51 These devices are now obsolete and no longer available in the market. Product Line Satchwell BAS & Sigma Environment Sigma Compact Edition Sigma WinCE Cause The rapid evolution of the PDA market has led to frequent discontinuation of supported devices. This created ongoing compatibility challenges and limited long-term support options. Resolution To address this issue and improve future compatibility, Sigma 4.05 Compact Edition shifted its support strategy. While no new hand-held devices are supported in this release, users can now utilize more widely available and sustainable alternatives such as: Mini PCs Netbooks Notebooks These devices offer greater flexibility, availability, and longevity compared to legacy PDAs. Resources Release Note – Sigma Compact Edition 4.05 User Guide – Sigma Compact Edition 4.05

Issue A failed IAC 400 controller requires replacement, but only an IAC 420 is available. This article provides guidance on using the IAC 420 as a substitute, including key differences and configuration considerations. Product Line Satchwell MicroNet, Satchwell Sigma Environment IAC 400 IAC 420 Cause The IAC 400 controller is no longer manufactured or supported, making direct replacements unavailable. In legacy systems, the IAC 420 may be the only remaining compatible controller on hand, despite also being obsolete. However, differences in hardware and configuration between the two models can lead to confusion or improper operation if not addressed. Resolution Key Differences Between IAC 400 and IAC 420 Feature IAC 400 IAC 420 Input Types 3 x Temperature Inputs 2 x Analogue Inputs 1 x Digital Input 6 x Universal Inputs Communication Cable Screening Terminal 3 used for earthing the communication cable screen Screen must be connected to a good earth, not to Terminal 3 Tables & Offsets Specific to IAC 400 input types Different due to universal inputs—review updated tables and offsets ⚠️ Important: Because the IAC 420 uses universal inputs, existing configurations from the IAC 400 will not directly transfer. You must update the input tables and offsets accordingly. Refer to the document: IAC Controllers – Tables and Offsets for detailed guidance. Wiring Information IAC 400 Wiring Details: Download IAC400A.pdf IAC 420 Wiring Details: Download IAC 420 - DS2801A-1205.pdf Recommendations Compatibility Check: Ensure the IAC 420’s universal inputs can be configured to replicate the IAC 400’s original input types. Documentation Review: Carefully consult wiring diagrams and configuration tables to avoid miswiring or misconfiguration. Testing: After installation, verify all inputs and outputs function as expected. Additional Notes Both the IAC 400 and IAC 420 are obsolete. For long-term reliability, consider migrating to a supported controller platform within the EcoStruxure Building Operation suite.

Issue How do you configure VisiSat to communicate with MicroNet or IAC controllers using a port-powered RS-232 to RS-485 converter? Product Line Field Devices, Satchwell MicroNet Environment Satchwell VisiSat Any port-powered RS-232 to RS-485 converter Cause Proper configuration of the RS-232 to RS-485 converter is required to establish communication between VisiSat and field controllers. Resolution Port-powered RS-232 to RS-485 converters such as the LIB-4-485 allow serial communication between a PC and RS-485-based controllers without requiring an external power supply. Power Requirements Powered directly from the PC’s RS-232 port. Ensure the PC’s serial port complies with RS-232 voltage specifications. Most modern PCs (e.g., Dell) are compatible, but some laptops or USB-to-serial adapters may not supply sufficient power. Wiring Guidelines TD (A) → Connect to negative (-) terminal of the controller. TD (B) → Connect to positive (+) terminal of the controller. GND → Connect the shield/screen only at the converter end, not at the controller. ⚠️ Always refer to the converter’s datasheet for pinout and wiring specifics. VisiSat Server Configuration Open the VisiSat Server Client from the system tray. Go to Network Menu → Settings. In the Configure Network Settings window: Set Transport Type to Serial Port Click Configure Serial Port Settings Choose the appropriate configuration based on the controller type: MicroNet Controllers: Use the following MicroNet-specific settings. IAC Controllers: Use the following IAC-specific settings. Click OK to apply settings. VisiSat is now ready to communicate with the controller via the RS-485 converter. Additional Notes The VisiSat Engineering Guide contains additional information regarding the VisiSat server. If using a USB-to-serial adapter, ensure it supports port-powered converters. For long cable runs, consider using isolated converters to prevent ground loops.

Issue There is a need to connect a legacy MicroNet system to the EcoStruxure Building Operation (EBO) platform. The traditional MN-MI interface is now obsolete, prompting the search for alternative integration methods. Product Line EcoStruxure Building Operation Environment Automation server Enterprise Server MicroNet interface Cause The MN-MI interface, previously used to bridge MicroNet systems with EBO, is no longer supported. A replacement solution is required to maintain system connectivity and functionality. Note: In EBO 2022 (4.0) and later, Satchwell MicroNet Integration is no longer supported. Resolution MicroNet systems operate using one of two communication protocols: Native Communications Protocol (NCP) Attached Resource Computer Network (ARCnet) If using NCP: The MicroNet LAN can be connected directly to the AS-P or ES. A MicroNet interface can be added and configured within EBO. If using ARCnet: The MN-MI is required to convert RS-232 to ARCnet. The MN-MI connects to the AS-P/ES via an RS232-to-RS485 converter. 100 Series MicroNet Controllers: These may allow removal of auxiliary ARCnet cards and reconfiguration to NCP protocol, enabling direct connection to AS-P/ES. 50 Series MicroNet Controllers: These cannot be reconfigured due to integrated communication components on the main board. Reference: For detailed connection options and configurations, refer to document PA-00246.

Issue There is no official internet download available for VisiSat documentation since the withdrawal of the Satchwell MicroNet and IAC products Product Line Satchwell MicroNet Environment Satchwell VisiSat Cause Documentation is no longer available for download. Resolution Further information and configuration details can be found in the following resources: VisiSat V1.2 Documentation Engineering Guide: Covers configuration for: IAC 400 IAC 420 IAC 600 IAC Touchscreen VisiSat V2.1 Documentation Engineering Guide (185 & 196 builds): Includes configuration for: MN300, MN440, MN500, MN620 MN350, MN450, MN550, MN650 MNLCD and MN Touchscreens Installation and User Guide Data Sheet Release Notes Attachments VisiSat V1.2 Engineering Guide.zip VisiSat V2.1 (185) Engineering Guide.zip VisiSat V2.1 (196) Engineering Guide.zip VisiSat 2.1 (196) Installation and User's Guide-0713.pdf VisiSat 2.1 (196) Data Sheet DS10202-0713.pdf VisiSat 2.1 (196) Release Note.pdf Related Articles MicroNet 100 Series Controller MLIs and Data Sheets MicroNet 50 Series Controller MLIs and Data Sheets Where can VisiSat software and license be purchased and what Version/Build is supplied?

Issue As of June 2019, the current version of VisiSat available is 2.1 Build 196. This version is compatible with specific Windows and Microsoft Visio versions and may not work with all system configurations. Product Line Satchwell MicroNet Environment Satchwell VisiSat Cause Different versions of VisiSat are only compatible with specific combinations of: Windows operating systems Microsoft Visio versions Using an incompatible version may result in installation or operational issues. Resolution Software Availability VisiSat 2.1 Build 196 is available for download from the Exchange Extranet. Since January 2018, VisiSat no longer requires a license and can be used freely. Refer to PA-00597 - MN-VSCORE End of Commercialization - Satchwell MicroNet for more details. Service Packs Two service packs are available for Build 196: Service Pack 1 (Build 200): Fixes ARCnet debug Excel spreadsheet property editor issue. Allows longer names (32 characters) and descriptions (50 characters) when exporting to MicroNet View or Xenta Xbuilder. Prevents export/import of MicroNet Interfaces in SBO/EBO WorkStation. Resolves error when saving blank point lists. Fixes memory leaks during export to SBO/EBO. Service Pack 2 (Build 201): Corrects character encoding issues during import. Ensures proper handling of alarms and trends in imported files. Both service packs are available on the Exchange Extranet. Compatibility Matrix VisiSat Build Windows OS Microsoft Visio Versions 185 / 196 Windows 7 2003 / 2007 / 2010 XP Professional 2003 / 2007 148 Vista Ultimate 2003 / 2007 XP Professional 2003 137 XP 2002 / 2003 17 XP 2002 14 XP 2002 Product Lifecycle Updates The MicroNet 50 series (MN350, 450, 550, 650 LCD and Touchscreen) and IAC 420, 600, and Touchscreen have been withdrawn from sale. No direct replacements are currently offered. Refer to: PA-00495 – Notice of Withdrawal – Satchwell Sigma PA-00528 – End of Commercialization – Satchwell Sigma Additional Resources PA-00597 - MN-VSCORE End of Commercialization - Satchwell MicroNet (PDF) VisiSat Data Sheets, Engineering Guides, Installation & User Guides Service Pack 1 (Build 200) Service Pack 2 (Build 201)

Issue How to locate and download the latest firmware image versions for Sigma Controllers and Integration Controllers (ICs). Product Line Satchwell Sigma Environment 3.46.57 3.46.66 3.46.80 3.46.89 3.46.100 3.46.104 3.46.105 3.46.106 3.46.107 3.46.108 3.46.110 3.46.111 3.46.131 Cause Users may need to identify and download the correct firmware image version for their specific Sigma hardware (e.g., UNC, IC, IC3) to ensure compatibility and optimal performance. Resolution Refer to the table below for the latest firmware versions and associated release notes for each Sigma controller and integration controller type: Device Firmware Version Release Note Sigma UNC (V53) 6b UNC596 6.b – Release Note Sigma UNC3 (ARM7) 1.p.0 UNC3 1.p.0 – Release Note UNC 532 (V25) 6b UNC532 6.b – Release Note IC-Modbus V5h IC-Modbus v5h – Release Note IC3 Modbus 1.n.2 IC3 Modbus – Release Note IC SNP 5d IC-SNP v5d – Release Note IC3 SNP 1.g.1 Sigma 4.05 Firmware Supplement No specific release note available IC York V3e (Not available for download) IC-York v3e – Release Note IC3 York 1.d.0 IC3 York 1.d.0 – Release Note IC3 Unifact 1.d.0 IC3 Unifact (RTC) – Release Note IC3 Unifact Pro 5h IC3 Unifact Pro 5h – Release Note 🔗 Note: Some firmware files or release notes may not be available for direct download. Please contact Schneider Electric support for assistance if needed.

Issue When launching VisiSat 2.1 build 196, 200, or 201, the following error message appears: “Unable to Load the Schneider Electric CET Style DLL” As a result, VisiSat fails to launch. Product Line Satchwell MicroNet Environment Satchwell VisiSat Windows (Windows, XP Professional, Windows 7, Windows Vista Ultimate) Microsoft Visio Cause The error occurs because the Microsoft .NET Framework 2.0 is not installed on the system. VisiSat requires this framework to function correctly. Resolution To resolve the issue, follow these steps: Uninstall VisiSat from your system. Install Microsoft .NET Framework 2.0. Reinstall VisiSat 2.1 build 196. If needed, apply the following service packs: Service Pack 1 (Build 200) Service Pack 2 (Build 201) Reboot your computer. Launch VisiSat. Downloads VisiSat 2.1 Main Software VisiSat Service Pack 1 (Build 200) VisiSat Service Pack 2 (Build 201) VisiSat Documentation & Data Sheets Additional Notes Ensure that your system meets all the minimum hardware and software requirements for VisiSat.

Issue Building Management System (BMS) equipment may malfunction due to electromagnetic interference (EMI) from nearby electrical devices. Diagnosing and resolving such issues can be complex and costly, making preventive installation practices essential. Product Line Andover Continuum, EcoStruxure Building Operation, Field Devices, Satchwell MicroNet, Satchwell Sigma, TAC IA Series, TAC Vista Environment All electrical equipment Cause Improper installation can lead to the generation or exposure to high- and low-frequency EMI, which may disrupt system performance or cause equipment failure. Resolution To ensure reliable operation and minimize EMI-related issues, follow these key EMC installation practices: Key EMC Practices Follow Manufacturer Recommendations Always adhere to the installation guidelines provided by equipment manufacturers, as they are tailored to the specific EMC requirements of each product. Proper Cable Routing Separate power and signal cables. Avoid parallel runs near high-interference sources (e.g., motors, transformers). Shielding Use shielded cables for sensitive signals. Ground shields correctly—typically at one end to prevent ground loops. Grounding and Bonding Establish a low-impedance ground path. Bond all equipment to a common ground reference. Surge Protection Install surge protection on power and communication lines. Protect against lightning and switching transients. Filtering Use EMI filters on power inputs. Apply ferrite beads or chokes on signal lines where needed. Physical Separation Maintain spacing between high-voltage and low-voltage components. Isolate noisy equipment from sensitive electronics. Enclosure Design Use metal enclosures for shielding. Ensure proper sealing and grounding of enclosure panels. Installation Environment Avoid placing equipment near strong EMI sources (e.g., radio transmitters, welding equipment). Maintain clean, dry conditions to prevent corrosion and poor connections. Compliance Testing Verify installations against relevant EMC standards (e.g., IEC, EN). Conduct site surveys if persistent issues arise. Reference Document: Practical Installation Guidelines for Electromagnetic Compatibility

Building Automation Knowledge Base

Improve your search experience:

Related Forums

Intelligent Devices Forum

Precautions When Upgrading MicroNet 100 Series to MicroNet 50 Series Controller

SigmaX Error: "This application failed to start because side-by-side-configuration is incorrect"

Sigma - IC3-Modbus Documentation.

Sigma IC3-Modbus: Data Type Compatibility (16-bit, 32-bit, 64-bit)

Sigma Programmable Object Bit Mask to Decode Modbus Register

How to Disable Sigma Controller Offline Hardware and Other Alarms

Remote Alarm Manager (RAM) – Configuration Overview

MicroNet 100 Series Controller MLis and Data Sheets

MicroNet 50 Series Controller MLi's and Data sheets

Sigma Client Reports a "HTTP connection failed" error"

Satchwell MicroNet 100 Series LON Controllers Communicating with Automation Server (AS-P)

Sigma Compact Edition – Supported Hand-held Devices Are No Longer Available

Using IAC 420 as a Replacement for Obsolete IAC 400 Controllers

Configuring a Port-Powered RS-232 to RS-485 Converter for VisiSat Communication

Can an EBO AS-P Be Used Instead of MicroNet Manager MN-MI?

Accessing VisiSat Engineering Guides and User Documentation

Where can VisiSat software and license be purchased, and what Version/Build is supplied?

Sigma Controller and IC Latest Image Versions

VisiSat: Unable to Load the Schneider Electric CET Style DLL

Installation Guidelines for Electromagnetic Compatibility (EMC)

Ask our Experts

Email Us

Building Automation Knowledge Base

Related Forums

Ask our Experts

Email Us

Welcome!