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

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

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

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

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

Issue 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 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 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.