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

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

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

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

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

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

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

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

Issue Sigma server is unable to retrieve communication statistics from the DNN or the controllers downstream of the DNN. Product Line Satchwell BAS & Sigma Environment Satchwell Sigma Cause The Sigma server relies on RIP (Routing Information Protocol) messages broadcast by the network DNNs to learn the network topology. This process depends on the RIP Listener service or equivalent routing configuration, which is: Disabled by default on Windows XP Deprecated or removed in later versions of Windows (Vista through 10) Resolution To restore communication between the Sigma server and the ARCNET/Ethernet subnets via the DNN, choose the appropriate method based on the operating system: For Windows XP Enable RIP Listener: Open Control Panel. Select Add or Remove Programs. Click Add/Remove Windows Components. Highlight Network Services → click Details. Check RIP Listener → click Next and Finish. For Windows Vista, 7, 8, 10 Use Persistent Static Routes (Recommended): Since RIP Listener is no longer supported, configure static routes manually: Open Command Prompt as Administrator. Use the following command to add a persistent route: route -p add <destination_network> mask <subnet_mask> <gateway_ip> Example: route -p add 192.168.100.0 mask 255.255.255.0 192.168.1.1 Verify routes using: route print Refer to the article: Persistent Routing on the Sigma Server for detailed steps. Additional Notes RIP v1 is considered insecure and obsolete in modern networks. Static routing is more predictable and secure in environments where dynamic routing is not feasible. Always validate connectivity after changes using ping , tracert , or route print .

Issue When attempting to ping an ARCNET controller from a server using the DOS ping command, the operation fails with the error: "Destination host unreachable" Product Line Satchwell BAS & Sigma Environment Satchwell Sigma Cause This issue typically occurs due to incorrect or missing routing configurations. Specifically: The route to the ARCNET sub-net is not defined. Sigma DNN broadcasts RIP v1 messages for the Sigma server to interpret. By default, RIP Listener is disabled on Windows XP and later systems, preventing dynamic route updates. Resolution To resolve this issue, follow one or both of the steps below: Enable RIP Listener on the Server This allows the Sigma server to receive and process RIP v1 messages from the DNN. Refer to: Sigma server communication to ARCNET/Ethernet sub-nets via a DNN failing Add Persistent Routes to the Sigma Server Manually define static routes to ensure reliable communication with ARCNET controllers. Refer to: Persistent routing on the Sigma server

Issue Guidance on how to add a persistent route to a Sigma server PC connected to a flat Ethernet network, particularly when RIP (Routing Information Protocol) cannot be used on DNNs. Product Line Satchwell BAS & Sigma Environment Satchwell Sigma Server Cause In environments where the Sigma server communicates via Ethernet or Arcnet through DNNs, and RIP cannot be run, manual configuration of persistent routes is required to ensure reliable communication. Resolution Understanding Routes A route in networking defines how data packets travel from one device to another across networks. Each device maintains a routing table, which acts like a GPS for network traffic—guiding packets to their destination based on IP addresses. Static Route: A manually defined path that doesn’t change unless updated. Persistent Route: A static route that remains active even after a reboot (enabled using the -P flag). Default Gateway: A fallback route used when no specific route matches the destination. In the Sigma environment, adding persistent routes manually imay be necessary to ensure the server knows how to reach each DNN subnet. Network Example A flat Ethernet network has no subnets. Example: Network Address: 10.158.0.0 Subnet Mask: 255.255.0.0 Valid IP Range: 10.158.0.1 to 10.158.255.254 Adding a Persistent Route Open Command Prompt: Click Start Select Run Type CMD and press Enter Use the ROUTE ADD Command: ROUTE ADD -P <Subnet Address> MASK <Subnet Mask> <DNN Ethernet IP Address> Example: DNN Subnet: 192.168.1.0 Subnet Mask: 255.255.255.0 DNN Ethernet IP: 10.158.1.6 Command: ROUTE ADD -P 192.168.1.0 MASK 255.255.255.0 10.158.1.6 This tells the Sigma server: “To reach any device in the 192.168.1.x range, send traffic to 10.158.1.6 .” Verify the Route: Type ROUTE PRINT at the command prompt Confirm the route appears at the bottom of the list Repeat for Each DNN: Add a separate route for each DNN in the network Additional Notes This configuration ensures persistent routing even after system reboots. It’s essential in systems where dynamic routing protocols like RIP are not feasible or supported.

Issue When Sigma operates over a site-wide Ethernet network with multiple subnets—or when Sigma DNNs use ARCnet or Ethernet secondary LANs—global object values may not be received by controllers located on different subnets. This results in communication failures between controllers. Product Line Satchwell BAS & Sigma Environment Sigma Ethernet networks containing subnets. Cause Global values are broadcast messages that are not routed across third-party Ethernet routers. Without proper configuration, these messages are blocked, preventing communication between controllers on different subnets. Resolution To enable global data transmission across subnets, Link Addressing (LA) must be configured. This process encapsulates broadcast messages into IP packets, allowing them to traverse routers and reach the intended devices. Refer to PIB 05.01.05-3 – Rules for Using Link Addressing for full technical guidance. 📎 Attachment: PIB050105_3 Link Addressing.pdf Key Concepts What is Link Addressing? Sigma uses broadcast messages for global data exchange. Routers block these broadcasts to prevent network flooding. Link Addressing converts broadcasts into directed IP packets. Firmware Requirements Ensure controllers and DNNs are running firmware version 5s (controllers) and 5t (DNNs) or later. Earlier versions may not support Link Addressing reliably. Configuration Commands (via Pocket Terminal) LA+ <IP> — Add a Link Address LA- <IP> — Remove a Link Address LAD — Display all Link Addresses LAC — Clear all Link Addresses ⚠️ Maximum of 5 Link Addresses per device ⚠️ On older firmware, Link Addresses may be deleted when downloading the CO??.SET file Examples of Link Addressing Scenarios 1. Basic Two-Subnet Configuration Node 10: LA+ 10.44.101.20 Node 20: LA+ 10.44.100.10 Required for bidirectional global data exchange. 2. DNNs Bridging Subnets Node 100 (DNN): LA+ 10.44.101.20 Node 101 (DNN): LA+ 10.44.100.10 DNNs rebroadcast global messages to their subLANs. 3. Multi-Subnet Circular Configuration Treat the network as a circle. Link Addressing should be configured clockwise and anti-clockwise, but avoid loops unless using advanced group configurations. 4. Using DNNs for Re-Broadcasting Add DNNs to subnets with multiple controllers. Only DNNs need Link Addresses; they rebroadcast to all local controllers. Advanced Configuration Global Message Lifetime Each global message starts with a Life Time Count of 15. Each DNN hop decrements the count. Messages are discarded when the count reaches 0. Large Networks (15+ Subnets) Use grouped DNNs with “Daisy Chain” Link Addressing. Interconnect groups with selected DNNs to form a resilient ring. Monitoring and Maintenance Use Sigma Device Monitoring to ensure DNNs are operational. Monitor for DNN failures which can disrupt global data flow. DNN Configuration for Re-Broadcasting Configure DNN as a router using Port 2. Add a new serial network in Sigma System Manager. No physical connection is needed on Port 2. Best Practices Avoid loops unless using grouped DNNs. Limit global traffic to prevent network performance issues. Use DNNs to simplify Link Addressing in complex subnet environments.

Issue When attempting to connect a Sigma client to the Sigma server, the connection fails and displays the error: "No Seats Available" Product Line Satchwell BAS & Sigma Environment Satchwell Sigma Cause The Sigma server is not licensed for the number of client connections being attempted. Resolution To resolve this issue, follow these steps: 1. Verify License Capacity From a working Sigma client, go to Help > About. Check the number of licensed clients shown in brackets () . Compare this with the number of currently connected clients. 2. Operating System Connection Limits Windows XP / Windows 7: Maximum 5 client connections Windows Server 2003 / 2008: Maximum 10 client connections 3. Check Setup Configuration Run C:\Sigma\bin\Setupsvr.exe For local clients (same PC as server): Ensure "My Computer" is ticked. For remote clients: Ensure "My Computer" is unticked and the correct Sigma server IP address is entered. Confirm that the HTTP Server Port matches the Sigma server (default is 8080). 4. Free Up a Seat Close an active client session to release a license seat.

Issue When using the IC_LON Plug-in, an error is reported: Unknown SNVT Type: nn This indicates that the SNVT (Standard Network Variable Type) is not supported by the IC3-LON controller. Product Line Satchwell BAS & Sigma Environment Sigma IC-LON Version 1.E Cause The Sigma IC3-LON controller is designed to work with LONMARK Resource Files Version 11. However, not all SNVT types defined in this version are supported by the controller.  Resolution To resolve this issue: Verify Supported SNVTs Refer to the IC3-LON Release Notes to confirm which SNVT types are supported. Avoid Unsupported SNVTs If an unsupported SNVT is required, consider alternative approaches such as: Using a supported SNVT with similar functionality. Reconfiguring the device or network to bypass the unsupported SNVT. Firmware Reference See the attached document: 📎 Release_Note_4-05 Firmware_IC3-LON.pdf

Issue Sigma communications may intermittently fail on Microsoft operating systems starting from Windows Vista due to changes in the default dynamic TCP/IP port range. Product Line Satchwell BAS & Sigma Environment Microsoft Windows Vista Microsoft Windows 7 Microsoft Windows 8 / 8.1 Microsoft Windows 10 Microsoft Windows Server 2008 / 2012 Ethernet communications Sigma as part of an SBO/EBO front-end system Cause To comply with IANA (Internet Assigned Numbers Authority) recommendations, Microsoft increased the dynamic client port range for outgoing connections starting with Windows Vista. The new default range is: 49152 to 65535 This change affects Sigma, which uses port 49152 for communication between the Sigma server and controllers. The overlap can cause intermittent communication issues. Resolution Option 1: Reserve Sigma Port Use SE Legacy Port Reservation to reserve port 49152 for Sigma, preventing conflicts with dynamic port allocation. Option 2: Redefine Dynamic Port Range Modify the dynamic port range to avoid overlap with Sigma’s communication port. Recommended range: Start Port: 50000 End Port: 65535 Use the following netsh commands to view and set port ranges: View Current Dynamic Port Range netsh int ipv4 show dynamicport tcp netsh int ipv4 show dynamicport udp netsh int ipv6 show dynamicport tcp netsh int ipv6 show dynamicport udp Set New Dynamic Port Range netsh int ipv4 set dynamicport tcp start=50000 num=15535 netsh int ipv4 set dynamicport udp start=50000 num=15535 netsh int ipv6 set dynamicport tcp start=50000 num=15535 netsh int ipv6 set dynamicport udp start=50000 num=15535 Note: Minimum range: 255 ports Minimum start port: 1025 Maximum end port: 65535 To replicate Windows Server 2003 behavior: netsh int ipv4 set dynamicport tcp start=1025 num=3976 netsh int ipv4 set dynamicport udp start=1025 num=3976 Additional Considerations Firewall Configuration: Ensure internal firewalls allow traffic in the dynamic port range (49152–65535) to avoid RPC communication issues. Exchange Server 2007: On Windows Server 2008, the default port range is 1025–60000. Adjust accordingly if Sigma is deployed alongside Exchange. References Microsoft KB Article 929851 – Details on dynamic port range changes.

Issue Communication failures occur when connecting a MicroNet ARCnet system via a MicroNet Manager Interface (MNMI) to Xenta 555/731, VisiSat, or SBO servers. Product Line Satchwell MicroNet, TAC Vista, EcoStruxure Building Operation Environment Xenta 555 or Xenta 731 communicating to a MicroNet ARCnet LAN VisiSat communicating to a MicroNet ARCnet LAN Building Operations Server communicating to a MicroNet ARCnet LAN Cause Incorrect bit switch configuration on the MicroNet MI interface. Resolution Cold Starting the MicroNet MI ⚠️ Caution: This procedure will erase all configuration data from the device’s EEPROM and restore factory defaults. Steps: Power On the Device Ensure the RUN LED flashes approximately once per second. Disconnect Communication Ports Unplug any connections to 9-pin plug 3 and 9-pin plug 4. Reset Switches Set all bit switches (S1) to the OFF position. Initiate Cold Start Toggle bit switch 8 ON, then OFF. No visible change will occur at this stage. Configure for Xenta 555 Direct Connection Set only switch 1 to ON; all others must remain OFF. Toggle bit switch 8 ON, then OFF again. Verify LEDs RUN, WINK, and MODEM LEDs should light up for ~1.5 seconds. RUN LED should resume flashing once per second. 🔍 Note: This cold-start procedure differs from that of a controller, which only requires toggling switch 8. Refer to data sheet DS10217A for detailed specifications.

Issue Communication failures between MicroNet View and MicroNet Manager Interface(MNMI) devices. Product Line Satchwell MicroNet Environment MicroNet View HMI MicroNet MI connected via ARCnet or NCP LAN Cause Incorrect bit switch configuration on the MicroNet MI device. Resolution Cold Starting the MicroNet MI ⚠️ Caution: This procedure will erase all configuration data from the device’s EEPROM and restore factory defaults. Steps: Power On the Device Ensure the RUN LED flashes approximately once per second. Disconnect Communication Ports Unplug any connections to 9-pin plug 3 and 9-pin plug 4. Reset Switches Set all bit switches (S1) to the OFF position. Initiate Cold Start Toggle bit switch 8 ON, then OFF. No visible change will occur at this stage. Configure for Xenta 555 Direct Connection Set only switch 1 to ON; all others must remain OFF. Toggle bit switch 8 ON, then OFF again. Verify LEDs RUN, WINK, and MODEM LEDs should light up for ~1.5 seconds. RUN LED should resume flashing once per second. Set switches 1 to 4 to ON for compatibility with NCP/ARCnet I/O Server (MicroNet View v1.0+). 🔍 Note: This cold-start procedure differs from that of a controller, which only requires toggling switch 8. Refer to data sheet DS10217A for detailed specifications.

Issue Where can I download the MicroNet View Monitor Tool (dongleless version) as referenced in document PA-00145 – Satchwell MicroNet Range Rationalisation? Product Line Satchwell MicroNet Environment MicroNet View Monitor Tool  Cause The MicroNet View dongleless Monitor Tool software is no longer available for purchase. However, it is now provided as a free download to support existing installations. Resolution You can download the required software directly via the links below: Available Downloads MicroNet View Monitor Tool (v3.38): Download MicroNet MNMonitor 3_38.zip SNP I/O Server (v3.14): Download MicroNet SNP IO Server 3_14.zip NCP/ARCnet I/O Server (v3.12): Download MicroNet NCP_ARCnet IO Server 3_12.zip USB Dongle Driver (for faster PCs): Download SPI 7.6.3.zip 💡 Note: The USB dongle driver may be required for compatibility with newer or faster PCs. Additional Resources 📄 PA-00145 - Satchwell MicroNet Range Rationalisation (PDF)

Issue The Sigma Release Note for version 4.07 references the Sigma Standard Edition Installation and Users Guide, but does not specify where to obtain it. Product Line Satchwell BAS & Sigma Environment Satchwell Sigma Cause Users may be unaware of the location or availability of the referenced guide due to lack of direct links or visibility in the release notes. Resolution The Sigma Standard Edition Installation and Users Guide is attached to this article Attachments: Sigma Standard Edition Installation and Users Guide-0111.pdf

Issue The Epson LQ-300+ II dot matrix printer fails to print alarms correctly when configured with Sigma on Windows 7. Alarms are spooled but not printed unless manual changes are made in Sigma's Alarm Manager. Product Line Satchwell BAS & Sigma Environment Epson LQ-300+ II Satchwell Sigma Windows 7 64-bit Cause When the printer is set to Continuous Print, Sigma spools the alarms, but the printer does not initiate printing. This issue is linked to driver compatibility and printer configuration settings. Resolution To resolve the issue and enable reliable alarm printing: Remove Existing Printer Configuration Go to Devices and Printers. Remove the Epson LQ-300+ II printer. Reinstall the Printer Use Add Printer to reinstall. Important: Use the Windows XP 32-bit driver from the original CD. Do not use the Windows 7 driver, as it causes compatibility issues. Configure Printer Settings Go to Printer Properties > Advanced tab. Set Print Processor to: Raw [FF auto] . Set the printer to Spool directly to the printer. Choose appropriate paper type: Fanfold or A4. Clean Up Sigma Configuration Shut down Sigma Client and Sigma Server. Navigate to C:\sigma\data and delete the file: printerconfigs nn.rec . This removes outdated printer references and avoids confusion. Reassign Printer in Sigma Restart Sigma Server and Sigma Client. In Alarm Manager, highlight and reassign the printer. Set to Continuous Print. Tick the LF (Line Feed) and CR (Carriage Return) boxes. Additional Notes The printer name may appear slightly different after reinstalling with the XP driver.