Issue Recipients receive a message from the Remote Alarm Manager (RAM) indicating that an alarm has been inactivated, even though no manual action was taken to clear the alarm. Product Line Satchwell MicroNet, Satchwell Sigma, TAC Vista Environment Remote Alarm Manager version 1.2 Cause The Remote Alarm Manager is designed to automatically send an inactivation message after a fixed period if an alarm remains active but is not retransmitted. By default, this period is three days, and the message is sent at midnight to the on-call recipient. This behavior is part of the system’s design to prevent stale alarms from remaining indefinitely without notification. Resolution This is expected behavior and not a fault. To manage or modify this behavior: Understand the default configuration: RAM sends inactivation messages after 3 days of no retransmission. This helps ensure recipients are aware that the alarm is no longer considered active. Adjust the inactivation timer if needed: The default 3-day period can be changed in the RAM configuration settings. Consult the Remote Alarm Manager documentation or configuration interface to modify this value. Review alarm retransmission settings: Ensure alarms are configured to retransmit if they remain active and require ongoing attention.

Issue How to configure a single RAM engine to monitor and manage alarms from multiple building automation systems across a site. Product Line Satchwell MicroNet, Satchwell Sigma, TAC Vista Environment Remote Alarm Manager Cause Some sites operate multiple BMS platforms concurrently. Rather than deploying separate RAM engines for each system, a centralized approach using one RAM engine can streamline alarm management and reduce system complexity. Resolution To configure RAM to monitor multiple systems from a single engine: Install RAM on the Master System Choose a primary system (e.g., Sigma) to host the RAM engine. Follow the installation and configuration steps outlined in the RAM Engineering Guide. Configure Alarm Actions Set up alarm actions on the master system (e.g., Sigma) to handle events from remote systems. Integrate Remote Systems Connect additional systems (e.g., BAS2800+, Micronet, Vista) to the master RAM engine. Ensure communication paths and alarm routing are correctly configured. Test and Validate Confirm that alarms from all connected systems are received and processed by the master RAM engine. Monitor for any communication or processing issues.

Issue MicroNet controller objects have a maximum allowable value of 10,000, which is insufficient for some energy meter readings that exceed this limit. Product Line Satchwell MicroNet Environment Satchwell MicroNet Cause MicroNet controller objects are limited to a maximum value of 10,000. When meter readings exceed this threshold, the controller cannot represent the full value using a single object. Resolution To represent meter readings above 10,000, implement a rollover counting mechanism using two counter objects and Menta logic: Create Two Counter Objects in VisiSat Counter 1: Handles the 0–999 part of the meter count. Counter 2: Increments by 1 every time Counter 1 rolls over (i.e., reaches 1000). Link the Rollover Pulse Output of Counter 1 to the Count Input of Counter 2. Diagram: Configure Menta Logic in Xenta 731 Use a Menta block to calculate the total meter reading: This allows representation of values up to 9,999,999. Display the Result The calculated total can be displayed on value pages, graphics, or used in further logic. Downloadable Examples VisiSat Project Xbuilder Project Vista Database All Files Bundle

Issue When importing IAC400 or IAC600 controllers into Building Operation via the Micronet Interface, digital outputs cannot be overridden or forced to a different value. Product Line EcoStruxure Building Operation, Satchwell MicroNet Environment IAC400 IAC600 Building OperationServer Cause During the import process, the Digital Output Override State is incorrectly configured in the XML export file. Specifically, the <P1="IsNonVolatile"...> line contains a value that prevents the output from being overridden. Resolution ⚠️ 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. To enable digital output override functionality: Create the SBO Export File in Visisat Use Visisat to generate the XML configuration file for the controller. Edit the XML File Before Importing into SBO Open the XML file using a text editor such as Notepad++. Locate the line containing: <P1="IsNonVolatile" Value="1" ...>​   Change the value from "1" to "0" : <P1="IsNonVolatile" Value="0" ...> Import the Modified XML File into SBO/EBO Use the Data Import function in the MicroNet Interface to bring the corrected configuration into Building Operation. Note This issue does not affect IAC420 controllers.

Issue Users need to transfer VisiSat licenses from one PC to another, typically due to hardware replacement or system upgrades. Product Line Satchwell MicroNet Environment Satchwell VisiSat 2.x Cause Licenses are tied to the original PC and must be exported and re-imported to function on a new machine. This process is necessary when: Replacing or upgrading a PC Consolidating engineering tools Migrating from VisiSat v2.0 to v2.1 Resolution Follow these steps to transfer VisiSat licenses: Export License from Original PC Use the VisiSat license management tool to export each license file. Save the exported files to a secure location (e.g., USB drive or network share). Transfer License Files to New PC Copy the exported license files to the target PC. Import License on New PC Use the license management tool on the new PC to import the license files. Ensure VisiSat v2.1 is installed before importing v2.0 licenses. Reference Documentation For detailed steps, refer to the Moving VisiSat Licenses PDF extracted from the VisiSat Engineering Guide. Also see: Transferring VisiSat version 2.0 license to Computer running VisiSat 2.1

Issue A user needs to transfer a VisiSat version 2.0 license to a new computer that will run VisiSat version 2.1, but the license transfer process is unclear. Product Line Satchwell MicroNet Environment VisiSat 2.1 Cause VisiSat licenses are version-specific and stored in the Windows registry. To transfer a license from v2.0 to v2.1, the license must first be installed and registered using the older version before upgrading. Resolution Follow these steps to successfully transfer the license: Install VisiSat v2.0 on the target machine. This step is necessary to register the license correctly. Transfer the license from the original machine to the target machine. Use the standard license transfer method (e.g., USB drive or license file, depending on your setup). Once the license is successfully registered on the target machine, uninstall VisiSat v2.0. Install VisiSat v2.1 on the same machine. The license will remain valid because it is stored in the system registry.

Issue Clarification is needed regarding which communication protocols and hardware interfaces are supported when using VisiSat software on Windows 7 operating systems. Product Line Satchwell MicroNet Environment Satchwell VisiSat Windows 7 32/64 bit Cause There is ambiguity around the compatibility of various communication protocols and hardware interfaces with VisiSat when installed on Windows 7 systems. Additionally, some legacy hardware components are no longer supported or available. Resolution The following communication options are supported for VisiSat on Windows 7: SNP Protocol Via computer’s native RS232 port Via USB to RS232 converter Via PCMCIA to RS232 converter Via ExpressCard to RS232 converter IP tunneling through Xenta 555/731 or AS/AS-P LAN network Remote site connection NCP Protocol Via computer’s native RS232 port Via USB to RS232 converter Via PCMCIA to RS232 converter Via ExpressCard to RS232 converter IP tunneling through LAN network Remote site connection ARCnet Protocol Via RS232 port connected through a null modem cable to a MicroNet Interface Unit (MN50-MI-ARC) Via PCI120U-485 PCI card (no longer manufactured) Note: USB22 Series (USB to ARCnet adapters) are not supported with VisiSat IP tunneling through LAN network Remote site connection LON Protocol Not supported on Windows 7 (both 32-bit and 64-bit)

Issue Clarification is needed on how to correctly wire and connect Micronet LCDs to various Satchwell MicroNet controllers.  Product Line Satchwell MicroNet Environment Micronet LCD / Micronet 50 series LCD Micronet 300 / 350 series controllers Micronet 440 / 450 series controllers Micronet 500 / 550 series controllers Micronet 620 / 650 series controllers Cause Micronet LCDs have multiple wiring and connection options depending on: The specific controller model in use Communication type (e.g., direct, networked) Installation method (e.g., panel mount, wall mount) This variability can lead to confusion or miswiring during installation or maintenance. Resolution Refer to the Micronet LCD Connections document (updated July 2012), which provides a comprehensive summary of connection options for Micronet LCDs across different controller models. 📎 Attachment: MN LCD connections (updated July 2012).pdf This document includes: Wiring diagrams Supported controller models Communication interface details Installation best practices Ensure that: The correct controller model is identified before wiring Communication settings (e.g., bit switch configurations) are verified Power supply requirements (e.g., 24VDC) are met

Issue Fault Finding on an IC-SNP / IC3-SNP and associated IAC controllers. Product Line Satchwell BAS & Sigma Environment IC-SNP IC3-SNP IAC controllers Cause Communication faults on the SubLAN may be caused by: Cause Description Incorrect LAN Termination Missing or improperly placed 120-ohm resistors can cause signal reflections and data corruption. Biasing Misconfiguration Bias jumper not set to “D” (Full Biasing) can result in unstable idle voltage levels. Faulty Controller Driver A single IAC controller with a failed RS-485 driver can hold the RX line low, blocking communication. Corrupted gateway.txt Entries Invalid or misconfigured entries can prevent the IC-SNP from initializing communication properly. Physical Layer Issues Damaged cables, poor connections, or incorrect wiring can interrupt signal transmission. Power Supply Problems Inadequate or unstable power to controllers can cause intermittent or complete communication loss. IC-SNP Hardware Failure Internal faults in the IC-SNP or IC3-SNP can prevent proper LAN operation. Excessive LAN Length or Load Too many devices or long cable runs without repeaters can degrade signal quality. Environmental Interference Electrical noise from nearby equipment can disrupt RS-485 signals. Resolution 1. Use of Alarm Manager Access via Sigma default/backup server. Review system messages (priorities 22–30) for controller-specific errors. Look for messages like “Unable to Communicate with Controller ???”. 2. Troubleshooting gateway.txt File Symptoms: “Unable to open gateway.txt file” error. Steps: Start with a minimal gateway.txt (1–2 entries). Use a known-good version from Exchange-On-Line. If errors persist: Remove all entries except one. Download and warm-start the controller. Gradually reintroduce entries to isolate the faulty line. 3. Controller Not Responding Single Controller: Check local communication using Visisat and LIB-4-485. Verify LAN wiring and power supply. Multiple Controllers: Indicates partial or full SubLAN failure. Begin investigation at the IC-SNP. 4. IC-SNP Hardware Checks Component Expected Behavior Bias Jumper Set to D (Full Biasing) Termination 120-ohm resistors at both ends Channel 2 TX LED Flashes after warm-start (gateway.txt processing) Channel 2 RX LED Flashes if receiving replies RX LED Permanently On: Indicates a faulty IAC controller driver disrupting LAN comms. 5. IC-SNP Retry Mechanism Retries each controller 3 times before marking offline. Sends error to Alarm Manager. Retries offline controllers every 30 minutes (on the hour and half-hour). 6. Binary Chop Method for LAN Isolation Purpose: Efficiently isolate faulty segments or controllers. Steps: Identify LAN midpoint. Disconnect twisted pair at nearest controller. Observe RX LED behavior: LED Off: Fault lies beyond midpoint. LED On: Fault lies before midpoint. Repeat by halving LAN again (25% or 75%) until fault is found. 7. Voltage Testing Guidelines Use a DC voltmeter to measure: Measurement Expected Voltage +ve to 0V ~2.5 V –ve to 0V ~0.15 V +ve to –ve ~2.31 V Note: Negative voltages suggest LAN faults. Compare readings across segments to identify anomalies. 8. RX LED Not Flashing at All Possible Causes: Faulty IC-SNP Faulty SubLAN Faulty Controllers Steps: Disconnect LAN after first controller. Warm-start IC-SNP. Observe RX LED: If flashing resumes, use binary chop to isolate fault. If not, test cable and controller individually. 9. Cable Testing Procedure Disconnect both ends and separate cores. Measure resistance: Between cores: ∞ Each core to earth: ∞ Short cores at one end. Measure resistance at other end: Between cores: ~0 Ω Each core to earth: ∞ 10. Controller Testing Use LIB-4-485 and Visisat Engineering software. Confirm controller responds to direct communication. Final Steps: Once faults are resolved: Download full gateway.txt. Warm-start IC-SNP. Monitor Alarm Manager for new errors.

Issue When Remote Alarm Manager (RAM) attempts to initialize the GSM modem, it fails during the reset command. However, the modem responds correctly when the same commands are sent via a terminal emulation program. Product Line Satchwell MicroNet, Satchwell BAS & Sigma, TAC Vista Environment Remote Alarm Manager (RAM) GSM Modem Cause The GSM modem returns result codes in a format that is not compatible with RAM’s GSM driver. RAM expects numeric result codes, but the modem may be configured to return verbose or generic error messages. Resolution To ensure compatibility, configure the modem to return numeric error codes using the AT+CMEE command. Steps to Configure the Modem: Connect to the GSM modem using a terminal emulation program (e.g., HyperTerminal or PuTTY). Check current error format: AT+CMEE? Returns the current setting (0, 1, or 2). Set error format to numeric: AT+CMEE=1 Save the setting to non-volatile memory: AT&W Disconnect the terminal program and retest with Remote Alarm Manager. AT+CMEE Format Options: Value Description 0 Disable result codes; returns ERROR 1 Enable numeric result codes 2 Enable verbose (text) result codes

Issue IAC touch screens unexpectedly reset to their default address (65) every Sunday when time broadcast is enabled. Product Line EcoStruxure Building Operation, Satchwell MicroNet Environment Building Operation Enterprise Server Building Operation Automation Server MicroNet transition IAC touch screen Cause When the AS or ES broadcasts time to MicroNet devices, the day number is incorrectly sent as 0 on Sundays instead of 7. The IAC touch screen does not recognize day 0, which triggers a reset to factory defaults, including its network address. Impact: The touch screen resets to address 65. If the original address was not 65, communication with controllers on the SubLAN fails. Manual reconfiguration is required to restore connectivity. Resolution The issue is resolved in SBO version 1.8 and later. ⚠️ 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 Not all features are seen when a BMS platform is viewed using remote control software e.g. RealVNC Product Line Andover Continuum, EcoStruxure Building Operation, Satchwell BAS & Sigma, Satchwell MicroNet, TAC IA Series, TAC INET, TAC Vista Environment Remote Tools: RealVNC, TeamViewer, LogMeIn, UltraVNC, etc. Cause Remote control software may not fully render graphical elements or interactive UI components of BMS applications. This is often due to: Graphics acceleration limitations UI rendering differences between local and remote sessions Security or permission restrictions in remote sessions Example: When using RealVNC to access the SmartStruxure License Administrator, the dropdown menu for adding license details may not appear, even though it functions correctly in a local session. Resolution Local Verification: Run the BMS application directly on the host machine to confirm full functionality. Remote Software Settings: Enable full desktop rendering or mirror driver (if available). Disable any performance optimizations that reduce UI fidelity. Alternative Access Methods: Use Remote Desktop Protocol (RDP) instead of third-party remote tools. Consider web-based access if supported by the BMS platform. Additional Notes These issues are not specific to one remote control tool; they may occur across various platforms.

Issue Customers or internal teams require documentation for Unifact Pro controllers or the NCP Palm engineering tool, but these resources are no longer publicly available due to product obsolescence. Product Line Satchwell MicroNet Environment Unifact Pro NCP Palm Cause The Satchwell MicroNet product line has been officially retired. As a result, associated documentation is no longer hosted on public platforms or Schneider Electric’s external portals. Resolution The following documents can be downloaded directly: 📄 Document 🔗 Download Link Unifact Pro Controller MLi MLI13303-1205.zip Unifact Pro Controller Data Sheets Unifact Data sheets.zip NCP Palm Engineering Guide NCP Palm Engineering Guide-0106.zip ✅ These documents are useful for understanding controller specifications, wiring, and communication setup using IR tools or RS-485 converters. Additional Notes These resources support field engineers and partners working with legacy Satchwell MicroNet systems. For long-term support and cybersecurity compliance, consider recommending migration to EcoStruxure Building Operation (EBO).

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 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 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 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 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)