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 When using the ribbon cable provided with Satchwell MicroNet Touchscreens or LCDs to supply power from a MicroNet 50 series controller powered by 24VDC, the display units may not function correctly due to hardware incompatibility. Product Line Satchwell MicroNet Environment Satchwell MicroNet Touchscreens Satchwell MicroNet LCDs Satchwell MicroNet 50 series controllers Warning Hazard of Electric Shock: Remove all power from all devices before removing any covers or doors of the system. Disconnect power at the device and at the power source. 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 MicroNet 50 Series controllers support both 24VAC and 24VDC input. The Touchscreen and LCD displays are adapted from MicroNet 100 Series hardware, which does not support 24VDC power input. Using the ribbon cable to supply 24VDC from the controller to the display can result in malfunction or damage. 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) Do not use the ribbon cable to power the display from a 24VDC-powered controller. Instead, use a separate 24VAC transformer to power the Touchscreen or LCD.

Issue Can the IC GEN OPC Server communicate with an OPC XML-DA server? Product Line Satchwell BAS & Sigma Environment IC GEN OPC Server Third-party OPC Clients OPC DA and OPC XML-DA protocols Cause The IC GEN OPC Server is designed to support OPC DA (Data Access) only. It does not natively support OPC XML-DA, which is a different protocol standard used by some third-party OPC servers. Resolution To enable communication between the IC GEN OPC DA client and a third-party OPC XML-DA server, a protocol translation gateway is required. Recommended Solution: Use a third-party gateway from Advosol, which acts as a bridge between OPC DA and OPC XML-DA. This allows the IC GEN OPC DA client to access data from XML-DA servers. For more information and to obtain the gateway, refer to Advosol’s OPC XML-DA Gateway (external link). Configuration Example: In the IC GEN OPC gateway.txt configuration file, reference the third-party OPC XML-DA server using the following format: Item0=4^IndigoVision^192.168.246.95^Fromlv.analysis.motionalarm1^0 Explanation of fields: IndigoVision : Name of the third-party OPC XML-DA server 192.168.246.95 : IP address of the server Fromlv.analysis.motionalarm1 : OPC item path 0 : Item index or priority (as required by IC GEN) Additional Notes Ensure the third-party gateway is installed and configured correctly on a supported operating system. IC GEN OPC version 4.05 or later is recommended for compatibility.

Issue What Ethernet port speeds are supported by Sigma controllers? Product Line Satchwell BAS & Sigma Environment Sigma controllers ARM 7(S-696, S-x96CPU-AE, S-796, S-x796CPU-AE, S-DNN3, S-DNN3-DT, S-632-E, S-632-AE and S-IC3's) V53 (S-ETH, S-496, S-596, S-532, S-DNN and S-IC's) Cause Sigma controllers come in different hardware generations. The newer ARM-7 based controllers support more Ethernet connection speeds and auto-negotiation features compared to the older V53-based controllers, which are more limited. Resolution Supported Ethernet Speeds by Hardware Type Hardware Type Ethernet Speed Duplex Mode Auto-Scan Support ARM-7 (New) 100Base-T 100M Half Duplex ✅ Yes 10Base-T Full/Half Duplex ✅ Yes V53 (Old) 10Base-T 10M Half Duplex ❌ No 🔌 Cable Type Requirements for Direct Connection Hardware Type Straight Cable Cross-over Cable ARM-7 (New) ✅ Supported ✅ Supported V53 (Old) ❌ Not Supported ✅ Required 📘 Additional Notes Most modern Ethernet switches and hubs auto-negotiate the best speed and duplex settings. When troubleshooting connectivity issues, verify: Cable type used (especially for older V53 hardware) Switch port configuration (fixed speed vs auto-negotiation) Controller hardware version

Issue Bindings between: Enterprise Server and Automation Server, or Two Automation Servers ...appear as "Unresolved" in the system. Product Line EcoStruxure Building Operation Environment Building Operation Enterprise Server Building Operation Automation Server Binding Diagnostics Cause This issue is typically caused by: Incorrect communication configuration Firewall or antivirus blocking communication Port conflicts or usage by other applications Network adapter misconfiguration Unsupported architecture (e.g., EC and ES on same PC) Resolution 🔒 1. Firewall Configuration Ensure Windows Firewall is correctly configured: Use the Firewall Config Tool to set inbound/outbound rules. Refer to: Creating Windows Firewall Rules for Building Operation. If unsure, temporarily disable the firewall to test connectivity. Watch for network profile switching (Private ↔ Public) during commissioning. ⚠️ Even if ASs appear online, unresolved bindings may still occur due to firewall issues. 🧩 2. Special Character in Server Name For v1.4 or v1.5 servers with an ampersand (&) in the name: Request hotfix: v1.4: R1.4.1.16201 or later v1.5: R1.5.0.1601 or later 🌐 3. Network & IP Configuration Confirm ES IP address matches the PC’s active NIC IP. If not, follow: How to Set the Enterprise Server IP Address. Use IP address instead of domain name if DNS resolution is unreliable. Ensure all required ports are open between ES and AS. Refer to: Information Technology System Planning Guide → Search “Network Ports”. Disable unused network adapters (e.g., Wi-Fi, VMware, VirtualBox). ES should use the primary NIC. 🔄 4. Repair Communication Right-click the ES → Advanced > Repair Server Communication This refreshes the communication tables. Detach and re-add ASs to the ES if needed. See: Unable to Add an Automation Server Underneath an Enterprise Server. 🛡️ 5. Antivirus & Security Software Disable network monitoring features in antivirus software. For Schneider laptops: Right-click Trellix in system tray → Enable Firewall Timed Groups. ⚠️ 6. Unsupported Architecture Enterprise Central (EC) and Enterprise Server (ES) should not run on the same PC with default ports. If testing: Stop EC service or Reconfigure ports to avoid conflicts. 🔍 Additional Tips Use the Communication tab on each server to verify peer visibility.

Issue The default Unifact Pro stencil in VisiSat only includes items for the BB*3 range of controllers. It does not include the older BB*2 range, which may still be in use in legacy systems. Product Line Satchwell MicroNet Environment VisiSat Unifact Pro Cause VisiSat’s default stencil set excludes the obsolete BB*2 Unifact Pro controllers. These must be manually added to the drawing environment. Resolution To access and use the older BB*2 Unifact Pro controllers in VisiSat, follow the steps below based on your version of Microsoft Visio: For Visio 2003/2007: Open Visio. Go to the File menu. Select Stencil > Open Stencil. Navigate to: C:\Satchwell\Binary\VisiSat\EN\Visio Select the file: Obsolete.vss The stencil will now include the older BB*2 Unifact Pro controllers. For Visio 2010 and Later: Under Shapes, click More Shapes. Select Open Stencil. Navigate to: C:\Satchwell\Binary\VisiSat\EN\Visio Choose: Obsolete.vss Additional Notes These stencils are installed by default during the VisiSat installation process. If the Obsolete.vss file is missing, you can download it from the VisiSat 2.1 Build 196 (200, 201) Obsolete Stencil Archiv You may store the stencil anywhere on your system, but the default location is: C:\Satchwell\Binary\VisiSat\EN\Visio

Issue Your laptop does not have a native serial (RS232) port. Can a USB-to-Serial adapter be used to connect to a Sigma controller via the SDCU utility? Product Line Satchwell BAS & Sigma Environment Satchwell Sigma Controllers SDCU Cause Modern laptops typically omit legacy RS232 serial ports in favor of USB interfaces. The SDCU utility requires a serial connection to communicate with Sigma controllers. Without a native serial port, a USB-to-Serial adapter is needed to emulate the required RS232 interface. Resolution Yes, a USB-to-Serial RS232 adapter can be used to SDCU a Sigma controller. Follow these steps to ensure proper setup: 🔧 Step-by-Step Instructions Connect the USB-to-Serial Adapter Plug the USB-Serial lead into your laptop. For first-time use, install the driver provided with the adapter (typically from the manufacturer like FTDI or Prolific). Verify COM Port Assignment Navigate to: My Computer > View System Information > Hardware > Device Manager > Ports (COM & LPT) Note the COM port number assigned to the adapter (e.g., COM3). ⚠️ This port number may change each time the adapter is reconnected. Connect to the Controller Use the SDCU lead to bridge between the USB-Serial adapter and the Sigma controller. Launch SDCU Utility Open the SDCU software. Set the communication port to match the COM port identified in Step 2. Configure the Controller Proceed with controller configuration as required. SDCU Cable Pinouts ✅ Compatibility Notes Supported Adapters: FTDI and Prolific chipsets are commonly compatible. Troubleshooting Tip: If communication fails, verify driver installation and COM port settings. Try a different USB port if needed. 🔗 Related Articles USB Serial Adapter Compatibility with Sigma

Issue Can multiple Modbus devices be mapped to the same IP address when communicating over TCP/IP? Product Line Satchwell BAS & Sigma Environment Sigma IC3 Modbus Cause This configuration is not documented in the official release notes, leading to uncertainty about its feasibility and implementation. Resolution Yes, multiple Modbus devices can be mapped to the same IP address using appropriate configuration in the gateway.txt file. This setup is particularly useful when simulating multiple Modbus devices using tools like ModSim or when interfacing with a gateway that multiplexes device IDs. Example Configuration ; gateway.txt entries 1,1,3,1,1,0x0001,0,0,1 ;Modsim1 40001 2,1,3,2,1,0x0001,0,0,1 ;Modsim1 40002 3,2,3,1,1,0x0001,0,0,1 ;Modsim2 40001 4,2,3,2,1,0x0001,0,0,1 ;Modsim2 40002 5,3,3,1,1,0x0001,0,0,1 ;Modsim3 40001 6,3,3,2,1,0x0001,0,0,1 ;Modsim3 40002 7,4,3,1,1,0x0001,0,0,1 ;Modsim4 40001 8,4,3,2,1,0x0001,0,0,1 ;Modsim4 40002 ; IP_ADDRESS_TABLE 1,10.158.72.254 2,10.158.72.254 3,10.158.72.254 4,10.158.72.254 Each entry maps a unique Modbus device number to the same IP address ( 10.158.72.254 ) but differentiates them using the device ID and register offset. Important Notes Single Gateway Limitation: IC3 Modbus can only be mapped to a single IP gateway or PC application. No Dual Mapping: It is not possible to map to two applications running on the same PC simultaneously.

Issue After installing or launching SigmaX on a new machine, users may encounter one or more of the following error messages: "The file SigInterfaceMfc.dll is not found." "The file SigShell.dll is not found." These errors prevent SigmaX from running correctly. Product Line Satchwell Sigma Environment SigmaX Windows XP, 7, 10 Cause The root cause is the absence of the SigmaX binary path ( C:\Sigma\Bin ) in the Windows Environment Variables. Without this path, Windows cannot locate the required DLLs during runtime. Resolution To resolve the issue, manually add the SigmaX binary path to the system environment variables: Step-by-Step Instructions: Open System Properties: Right-click This PC or My Computer on the desktop. Select Properties → Advanced system settings. Edit Environment Variables: Click Environment Variables. Under System Variables, locate the variable named Path . Click Edit. Add SigmaX Path: Append the following to the end of the variable value: ;C:\Sigma\Bin Ensure there is a semicolon ( ; ) separating entries. Apply and Restart: Click OK to save changes. Restart the computer to apply the new path. Verification After rebooting: Launch SigmaX. Confirm that the application starts without DLL errors. Notes This fix applies to all SigmaX versions where the installation does not automatically set the environment path. If additional DLL errors occur (e.g., SigShell.dll ), they are typically resolved by the same path update. Ensure that C:\Sigma\Bin contains all required DLLs. If files are missing, reinstall SigmaX or copy them from a working installation.

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)

Building Automation Knowledge Base

Improve your search experience:

Related Forums

Intelligent Devices Forum

Satchwell MicroNet Touchscreen or LCD with 24VDC MicroNet 50 series controllers

IC GEN OPC and XML-DA Data Type Compatibility

Ethernet Connection Speeds for Sigma Controllers

Enterprise Server and Automation Server Bindings Show "Unresolved"

Adding Older Unifact Pro Range With BB*2 Firmware to VisiSat

Using a USB-Serial Lead to SDCU a Sigma Controller

Using a Single IP Address for Multiple Modbus Device Numbers over TCP/IP Communications

SigmaX Fails to Launch Due to Missing DLL Files

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

Ask our Experts

Email Us

Building Automation Knowledge Base

Related Forums

Ask our Experts

Email Us

Welcome!