Issue Users may encounter problems when short text descriptions are not displayed correctly in Sigma. This typically occurs when the SHTTXT.REC file is not placed in the correct directory. Product Line Satchwell BAS & Sigma Environment Sigma server all version 4 releases. Cause Incorrect placement of the SHTTXT.REC file can prevent short texts from appearing when objects are displayed in the Sigma interface. Resolution In Sigma version 4.0 and later, there are two required locations for the SHTTXT.REC file: Primary Location (used by Sigma): C:/Sigma/Data/Locality/English United_Kingdom/ (Note: This path may vary depending on the language/locality settings.) Secondary Location (used by SigmaX): C:/Sigma/Data/ To ensure proper functionality: Copy the SHTTXT.REC file to both locations. Confirm that the file is not corrupted and matches the expected format. Additional Notes Always back up the original SHTTXT.REC file before replacing it. If using a non-UK locality, adjust the folder path accordingly. This file is essential for displaying object short texts in both Sigma and SigmaX environments.

Issue Guidance on configuring Sigma UNC 632, UNC 696, or UNC 796 controllers when connecting to a flat Ethernet network. Product Line Satchwell BAS & Sigma Environment All Sigma controllers connected to flat ethernet network. Cause This article provides general configuration advice for Sigma controllers on non-subnetted networks. Resolution A flat Ethernet network is defined as a network without subnets. For example, a network with the address range: Network Address: 10.158.0.0 Subnet Mask: 255.255.0.0 Usable IP Range: 10.158.0.1 to 10.158.255.254 On such networks, the Sigma controller requires only the following: IP Address Subnet Mask These settings, along with the controller’s Default Server information, should be configured using the Sigma Device Configuration Utility (SDCU) Additional Resources Sigma UNC 632, 696/796 controllers, connecting to a "Subnetted" Ethernet network SDCU Utility

Issue What entries are required in the INPUT_XLATE table for Sigma digital inputs to function correctly? Product Line Satchwell BAS & Sigma Environment Sigma gateway.txt IC GEN DDE IC GEN OPC Cause Sigma digital inputs operate using reverse logic, where: 100.0 = OFF 0.0 = ON This behavior must be accurately reflected in the gateway.txt file's XLATE table for proper operation. Resolution To correctly map digital input and output objects in the IC GEN gateway.txt file, configure the XLATE tables as follows: Input XLATE Table (Mapping to Digital Input Objects) [INPUT_XLATE] count=2 Item0=1 / 0.0 ; DDE input of 1 = DI ON Item1=0 / 100.0 ; DDE input of 0 = DI OFF Output XLATE Table (Mapping from Digital Output Objects) [OUTPUT_XLATE] count=2 Item0=0.0 / 0 ; DO OFF = DDE output of 0 Item1=100.0 / 1 ; DO ON = DDE output of 1

Issue How to configure Sigma images on a Sigma server so they can be downloaded by a Sigma client. Product Line Satchwell BAS & Sigma Environment Sigma Images Firmware System Diagnostics Cause Image downloads are performed via Sigma System Diagnostics. However, images must first be manually loaded onto the Sigma server. Resolution Download the latest Sigma controller images from The Exchange portal. Copy the image file to the Sigma server directory: C:\Sigma\Image Launch the Sigma Client and open System Diagnostics. Select ‘Node’ and enter the device number. Go to Options → Download Files or press F6. Choose the appropriate image file to download to the device. ⚠️ Important: Identify the controller type (V53 or ARM7) before selecting the image file. Mixing image and controller types is not supported. To verify the image transfer: On the Sigma server, click the Sigma Service icon Select ‘Toggle Debug (on/off)’ Monitor the transfer status in debug mode

Issue After upgrading to Sigma 4.08, the Sigma server ( SigmaSvr.exe ) fails to start. An error message may be displayed. Product Line Satchwell BAS & Sigma Environment Sigma 4.08 Build 3.46.57 Cause The issue occurs due to the absence of a valid licensing method on the Sigma server following the upgrade from Sigma 4.04. Resolution Resolution To resolve this issue, ensure that one of the following valid licensing methods is available: A valid Sigma dongle is connected to the server. The StruxureWare Building Operation License Administrator software is installed, along with a valid license. Additional Notes This issue is specific to Sigma 4.08 Build 3.46.57. If licensing is correctly configured and the issue persists, contact support for further assistance.

Issue Compatibility of USB-to-serial converters with Sigma and BAS2800+ systems. Product Line Satchwell BAS & Sigma Environment Sigma BAS2800+ Laptops without onboard RS232 serial ports Cause Modern laptops often lack built-in RS232 serial ports, necessitating the use of USB-to-serial converters. However, not all converters are compatible with Sigma and BAS systems. Resolution USB-to-serial converters vary in compatibility due to differences in chipset design. The two most common chipsets are Prolific and FTDI. Be aware of counterfeit versions of these chipsets. For reliable performance, use converters sourced from reputable distributors such as RS Components. Sigma Compatibility Sigma systems typically work only with Prolific-based converters. Ensure the converter is assigned a low COM port number (e.g., COM1). Confirm the COM port is not in use by other applications (e.g., Bluetooth). [Enhanced] Update the sigma.ini file settings to reflect the correct COM port when using serial communication. BAS Compatibility BAS systems generally require FTDI-based converters. These converters can operate on higher COM port numbers (e.g., COM7). No additional configuration files need to be modified for BAS compatibility. Additional Notes Local testing may be necessary to determine the most suitable converter for your specific setup. Always verify driver installation and COM port assignment in Device Manager.

Issue Sigma remote client software has been added to a new PC, but the client fails to connect reliably to the Sigma server. On some occasions, the connection is established, but the Sigma Client Menu options are unavailable. Product Line Satchwell BAS & Sigma Environment Sigma remote client (up to version 4.04) Cause Sigma software versions up to 4.04 rely on Windows File Sharing to enable remote client connections to the Sigma server. This dependency can fail due to misconfigured network settings, firewall restrictions, or incompatible Windows configurations. Resolution Recommended Solution Upgrade to Sigma version 4.05 or later, which eliminates the dependency on Windows File Sharing for remote client connections. Alternative Workarounds (if upgrade is not possible): 2.1. Ensure file sharing is enabled between the Sigma server and client PCs by using a common Windows username and password across all machines. Verify that the firewall and network settings allow TCP port 3614 to pass through. Unblock this port if necessary. If the PCs are part of a client-managed network, consult with the site's IT team to ensure TCP port 3614 is permitted through routers and firewalls. If Sigma communication must traverse a firewall, ensure UDP port 49152 is unblocked.

Issue Understanding the configuration and limitations of Device Monitoring alarms, including alarm priorities and functionality in Sigma systems. Product Line Satchwell BAS & Sigma Environment Sigma versions 4.04 and later. Cause Clarification is required on whether the Device Monitor alarm in Sigma can have its priority or functionality modified. Resolution Sigma 4.04 and Earlier The Device Monitor alarm is fixed at priority level 29. Alarm priority cannot be changed in these versions. Sigma 4.05 and Later A configuration file named deviceMonitor.xml is introduced. This file contains parameters such as polling frequency, retry attempts, and alarm priority. Example configuration snippet: <DeviceMonitor> PollFrequency="1001" NumberRetrys="3" AlarmPriority="29" MaxDelayResponse="5000" LogLongDelays="0" </DeviceMonitor> Note: Do not modify these settings without consulting support and fully understanding the implications. Important: Any changes to deviceMonitor.xml require a Sigma server restart to take effect. Functional Limitations The Device Monitor alarm is not controller-based, which means: It does not support routing like plant alarms. It cannot have “actions” applied. There is no object associated with each controller. It cannot be displayed on graphics or used in control schemes. Recommendation If enhanced functionality is required, consider using the legacy method where controllers are monitored by other controllers. This approach allows for more flexible alarm handling and integration into control strategies.

Issue How can more than 50 globals be transmitted from a Sigma controller when there are many digital object states to share between controllers? Product Line Satchwell BAS & Sigma Environment Sigma Controller (all) Cause Sigma controllers are inherently limited to broadcasting a maximum of 50 global variables. Resolution To overcome the 50-global limit, you can encode multiple digital object states into a single analogue value using a binary count method. This allows up to 16 digital states to be represented and transmitted as one global analogue value. This method leverages the MASK command in Sigma programmable objects to decode the analogue value back into individual digital states. Implementation Steps Create a Programmable Object in the Transmitting Controller Use binary counting to combine up to 16 digital objects into a single analogue value. Each bit in the binary representation corresponds to the on/off state of a digital object. An analogue value of 901 represents the binary value 0000001110000101, where each bit (1 or 0) indicates the state of a digital input (DI) object. Example: Create a program object in the transmitting controller that 'binary' counts up to 16 digital objects: 10 XINT = 0 20 IF POINT 0|180 ON THEN XINT = XINT + 1 1st condition 30 IF POINT 0|181 ON THEN XINT = XINT + 2 2nd condition 40 IF POINT 0|182 ON THEN XINT = XINT + 4 3rd condition 50 IF POINT 0|183 ON THEN XINT = XINT + 8 4th condition 60 IF POINT 0|206 ON THEN XINT = XINT + 16 5th condition 70 IF POINT 0|207 ON THEN XINT = XINT + 32 6tht condition 80 IF POINT 0|208 ON THEN XINT = XINT + 64 7th condition 90 IF POINT 0|209 ON THEN XINT = XINT + 128 8th condition 100 IF POINT 0|210 ON THEN XINT = XINT + 256 9th condition 110 IF POINT 0|214 ON THEN XINT = XINT + 512 10th condition 120 IF POINT 0|215 ON THEN XINT = XINT + 1024 11th condition 130 IF POINT 0|216 ON THEN XINT = XINT + 2048 12th condition 140 IF POINT 0|217 ON THEN XINT = XINT + 4096 13th condition 150 IF POINT 0|218 ON THEN XINT = XINT + 8192 14th condition 160 IF POINT 0|202 ON THEN XINT = XINT + 16384 15th condition 170 IF POINT 0|203 ON THEN XINT = XINT + 32768 16th condition 180 XFLO = FLOAT ( XINT ) 190 RETURN VIA TEXT 153 VALUE XFLO Set Up Bit Masking in the Receiving Controller In the receiving controller create up to 16 programmable objects to decode the transmitted analogue value. Use the MASK command to extract individual digital states from the binary representation. 1st load 10 XINT = NINT POINT 0|222 20 YINT = XINT MASK ( 1 ) 30 IF YINT = 1 THEN RETURN TRUE "load 1 on" 40 RETURN FALSE "load 1 off" -------------------------------------------------------------- 2nd load 10 XINT = INT POINT 0|222 20 YINT = XINT MASK ( 2 ) 30 IF YINT = 2 THEN RETURN TRUE "load 2 on" 40 RETURN FALSE "load 2 off" -------------------------------------------------------------- 3rd load 10 XINT = INT POINT 0|222 20 YINT = XINT MASK ( 4 ) 30 IF YINT = 4 THEN RETURN TRUE "load 3 on" 40 RETURN FALSE "load 3 off" -------------------------------------------------------------- 4th load 10 XINT = NINT POINT 0|222 20 YINT = XINT MASK ( 8 ) 30 IF YINT = 8 THEN RETURN TRUE "load 4 on" 40 RETURN FALSE "load 4 off" -------------------------------------------------------------- 5th load 10 XINT = NINT POINT 0|222 20 YINT = XINT MASK ( 16 ) 30 IF YINT = 16 THEN RETURN TRUE "load 5 on" 40 RETURN FALSE "load 5 off" -------------------------------------------------------------- 6th load 10 XINT = NINT POINT 0|222 20 YINT = XINT MASK ( 32 ) 30 IF YINT = 32 THEN RETURN TRUE "load 6 on" 40 RETURN FALSE "load 6 off" -------------------------------------------------------------- 7th load 10 XINT = NINT POINT 0|222 20 YINT = XINT MASK ( 64 ) 30 IF YINT = 64 THEN RETURN TRUE "load 7 on" 40 RETURN FALSE "load 7 off" --------------------------------------------------------------​ 🔗 Click here for detailed setup instructions

Issue The text on the programmable (prog) object updates correctly, but the associated graphic does not reflect the change. Product Line Satchwell BAS & Sigma Environment   Sigma – All versions BAS2000/2800 – All versions Cause The controller only updates server graphics when the object changes state or exceeds the set tolerance. If prog objects are written with the same condition but different return texts, the correct text may not display until the entire graphic is refreshed. Example of problematic code: 10 If P0|1 on then return true "Object 1 on" 20 If P0|2 on then return true "Object 2 on" 30 If P0|3 on then return true "Object 3 on" In this case, the graphic may not update unless the object state changes. Resolution To ensure the graphic updates correctly, modify the programmable object so that it changes state, prompting the controller to refresh the graphic. This may require creating a dedicated object specifically for graphic updates. Recommended approach using a timer to force state change: 10 If not time left then goto 50 20 If P0|1 on then return true "Object 1 on" 30 If P0|2 on then return true "Object 2 on" 40 If P0|3 on then return true "Object 3 on" 50 Set timer 10 60 If P0|1 on then return false "Object 1 on" 70 If P0|2 on then return false "Object 2 on" 80 If P0|3 on then return false "Object 3 on" This logic ensures the object state toggles, triggering the graphic to update accordingly.

Issue After configuring Link Addressing on a Sigma DNN3, communication with the DNN3 fails, and Link Addressing does not function as expected. Product Line Satchwell BAS & Sigma Environment Multiple Sigma controllers across at least two Ethernet VLANs DNN3 devices (version 1.h) connected to each VLAN Port 1 of each DNN3 connects to the VLAN Port 2 is configured as a virtual Serial PPP port (not physically connected to a device) Cause Although Link Addressing may be correctly configured, the DNN3 devices lack routing information (i.e., static routes). Without this, the DNN3 cannot transmit point-to-point global data to the appropriate router or default gateway. Additionally: With both ports configured, RIP (Routing Information Protocol) is enabled by default. RIP broadcasts misleading routing information, advertising port 2 as a valid route, which is incorrect. RIP must be disabled to prevent this false advertisement. Resolution To restore communication and proper Link Addressing functionality: Add a default static route to each DNN3 using Pocket Terminal 32 via the service port: SR+ 0.0.0.0/0 192.168.1.253 1 0.0.0.0/0 is the generic destination and mask 192.168.1.253 is the default gateway 1 is the DNN3 port number Disable RIP on port 1 of the DNN3: RIPD 1 Additional Notes Ensure that no devices are physically connected to port 2 if it's configured as a virtual PPP port. This configuration ensures that global data is routed correctly between VLANs and prevents routing conflicts.

Issue Can the S-x96-PSU be used as a replacement for the PSU card in UNC196 or UNC296 controllers that have separate communication and processor cards? Product Line Satchwell BAS & Sigma Environment S-x96-PSU UNC196 UNC296 Cause This question arises when upgrading or maintaining legacy BAS2000/2800+ systems, particularly when considering compatibility between PSU cards and processor board types. Resolution The S-x96-PSU is only compatible with V53-type processor boards in BAS systems. 📌 For BAS2800+, both the communication and processor boards must be replaced with the V53 version to use the S-x96-PSU. 🔶 Note 1: V53 processor boards for BAS2800+ are available only while stocks last. The recommended upgrade path is to Sigma. 🔶 Note 2: For BAS2000 and BAS2800, the upgrade path is also to Sigma. 📄 Download PIB 04.04.19_4+New+PSU+card+UNC596.pdf 

Issue Using the Pocket Terminal 32 utility to set the UNC532 default gateway via the command: GW 10.130.10.253 followed by configuring the node using SDCU, results in communication failure between the Sigma server and the controller. Upon inspection, the default gateway IP address appears to have unexpectedly changed to 10.130.10.240. Product Line Satchwell BAS & Sigma Environment   Sigma (All versions) SDCU (System Device Configuration Utility) Pocket Terminal 32 Cause When the controller node configuration is written using SDCU, it overwrites the previously set default gateway IP address, even if it was correctly configured earlier using Pocket Terminal 32. Resolution To avoid communication issues: First, configure the controller using SDCU. Then, set the default gateway IP address using Pocket Terminal 32. ⚠️ Important: If any changes are made to the controller using SDCU after setting the gateway, you must re-enter the default gateway IP address using Pocket Terminal 32. Additional Resources SDCU Utility  Pocket Terminal 32

Issue Unable to establish communication with an EF1 electricity meter via Modbus protocol. Product Line Satchwell BAS & Sigma Environment IC-Modbus EF1 Electricity Meter Cause Incorrect Modbus configuration or wiring setup may prevent communication with the EF1 meter. Resolution To ensure successful communication with the EF1 electricity meter, verify and apply the following settings: Modbus Communication Settings Protocol: Modbus RTU Baud Rate: 9600 Data Bits: 8 Parity: Even Stop Bits: 1 Termination: Fit a 120-ohm resistor across the RS-485 connections Gateway.txt Entry Point number,9,4,0,1,0x1102,0,0,0 Meter Wiring Configuration U+ (Power Supply): 7–24 VDC (tested with 12–15 VDC) B Connection: IC3-Modbus Terminal C2 A Connection: IC3-Modbus Terminal C1 GND (Power Supply 0V) Additional Resources EF1 Installation Instructions (PDF) Windmill ComDebug Software – Register to download the latest version.

Issue Information is required to identify the correct fuse type for replacing the fuse in an X96-BAT battery pack. Product Line Satchwell BAS & Sigma Environment   UNC-X96 Cause The fuse in the X96-BAT battery pack may need replacement due to wear, damage, or failure during operation. Resolution The X96-BAT battery pack includes a fuse holder containing a 5 Amp quick-blow fuse. When replacing the fuse, ensure the following specifications are met: Type: Quick-blow (fast-acting) fuse Rating: 5 Amps Location: Inside the fuse holder of the X96-BAT battery pack

Issue How to program software for automatic window modulation using BAS or Sigma. Product Line Satchwell BAS & Sigma Environment Satchwell BAS & Sigma Cause Standard window operations typically support only open/close functionality. However, in this case, the requirement is for staged modulation—windows should open or close in increments based on environmental conditions and manual overrides. Resolution To enable modulated control of windows (rather than simple open/close), the following setup is required: 1. Window Travel Time Determine the total time for the window to move from fully closed to fully open. Ensure symmetry: open and close times must be equal for accurate modulation. 2. Control Strategy Modulation is achieved in fixed stages (e.g., 25%, 50%, 75%, 100%). This allows granular control of ventilation and environmental conditions. 3. Override Functionality The system should allow manual override by the classroom teacher to open or close windows as needed. 4. Environmental Interlocks Integrate interlocks for wind direction and rain detection to ensure safe operation. These interlocks prevent window operation under adverse weather conditions. Implementation Example A sample configuration for a classroom includes all necessary objects and logic. Inputs P60 = Time schedule P15 = Fire P16 = Rain P17 = Teacher Override On P18 = Teacher Override Off P19 = Wind Direction P35 = Temperature control loop (set to Pb only) P34 = CO₂ control loop (set to Pb only) P33 = Calculation point (set to maximum of P34 and P35) Programmable Points P36 – CONTROL SLOW RAMP Tracks the max temp/CO₂ signal and ramps slowly. Timer must exceed window pulse timer. Also tracks overrides to resume control from the correct point. 10 XFlo = POINT 0|33 20 IF TIME LEFT THEN GOTO 50 30 IF XFlo > YFlo THEN YFlo = YFlo + 1.00000 40 IF XFlo < YFlo THEN YFlo = YFlo - 1.00000 50 IF YFlo CHANGED THEN SET TIMER 10 60 IF POINT 0|18 CLOSED THEN YFlo = 0.000000 70 IF POINT 0|15 CLOSED THEN YFlo = 0.000000 80 IF POINT 0|16 CLOSED THEN YFlo = 0.000000 90 IF POINT 0|19 CLOSED THEN YFlo = 0.000000 100 IF POINT 0|60 CLOSED THEN YFlo = 0.000000 110 IF POINT 0|17 CLOSED THEN YFlo = 100.000 120 RETURN VIA TEXT 92 VALUE YFlo​ P37 – CONTROL 10% INTERVAL Divides control loop into 10 stages. 10 XFlo = POINT 0|36 20 IF XFlo = 100.000 THEN YFlo = 100.000 30 IF XFlo < 100.000 THEN YFlo = 90.0000 40 IF XFlo < 90.0000 THEN YFlo = 80.0000 50 IF XFlo < 80.0000 THEN YFlo = 70.0000 60 IF XFlo < 70.0000 THEN YFlo = 60.0000 70 IF XFlo < 60.0000 THEN YFlo = 50.0000 80 IF XFlo < 50.0000 THEN YFlo = 40.0000 90 IF XFlo < 40.0000 THEN YFlo = 30.0000 100 IF XFlo < 30.0000 THEN YFlo = 20.0000 110 IF XFlo < 20.0000 THEN YFlo = 10.0000 120 IF XFlo < 10.0000 THEN YFlo = 0.000000 130 RETURN VIA TEXT 92 VALUE YFlo​ P38 – OPEN CONTROL Xref your Window Open DO to this point. Timer = 72s / 10 stages = 7s per stage. 10 XFlo = POINT 0|37 20 IF XFlo UP THEN SET TIMER 7 30 IF POINT 0|18 CLOSED THEN RETURN FALSE "TchO/R Close" 40 IF POINT 0|15 CLOSED THEN RETURN FALSE "FIRE" 50 IF POINT 0|16 CLOSED THEN RETURN FALSE "RAIN" 60 IF POINT 0|19 CLOSED THEN RETURN FALSE "WrgWind Dir'" 70 IF POINT 0|60 CLOSED THEN RETURN FALSE "Time Off" 80 IF POINT 0|17 CLOSED THEN RETURN TRUE " TchO/R Open" 90 IF TIME LEFT THEN RETURN TRUE "Move Open" 100 RETURN FALSE "Stationary"​ P39 – CLOSE CONTROL Xref your Window Close DO to this point. Same timer logic as P38. 10 XFlo = POINT 0|37 20 IF XFlo DOWN THEN SET TIMER 7 30 IF POINT 0|18 CLOSED THEN RETURN TRUE "TchO/R Close" 40 IF POINT 0|15 CLOSED THEN RETURN TRUE "FIRE" 50 IF POINT 0|16 CLOSED THEN RETURN TRUE "RAIN" 60 IF POINT 0|19 CLOSED THEN RETURN TRUE "WrgWind Dir'" 70 IF POINT 0|60 CLOSED THEN RETURN TRUE "Time Off" 80 IF POINT 0|17 CLOSED THEN RETURN FALSE " TchO/R Open" 90 IF TIME LEFT THEN RETURN TRUE "Move Close" 100 RETURN FALSE "Stationary"​ 📄 Download Configuration Files: Window.doc (Word Document) Window.pdf (PDF Document)

Issue When launching BAS2800+ V2.9 on a Windows XP system, the software fails to detect the dongle. A warning message appears: "No Dongle Driver Detected" Product Line Satchwell BAS & Sigma Environment   Windows XP BAS2800+ V2.9 Cause The issue occurs because modern PCs may operate too quickly for the dongle to be recognized during startup. Resolution To resolve this issue, follow these steps: Download the fast dongle driver Unzip the contents. Install the driver in the following directory: C:\bas\bin Run the executable: dk2wn32.exe Follow the on-screen instructions during installation. Restart your PC once installation is complete. After rebooting, the dongle should be successfully detected, allowing BAS2800+ to run normally.

Issue Which files can be safely backed up using automatic or manual methods? Product Line Satchwell BAS & Sigma Environment Sigma (All versions) Cause Backing up a live Sigma system is not recommended, as copying files that are currently open may compromise data integrity. Resolution To ensure a reliable backup process, follow these guidelines: Files Safe to Back Up While Sigma Is Running The following directories contain archive data and can be backed up safely without shutting down the system: C:\\Sigma\\Data\\ArchivedAlarms C:\\Sigma\\Data\\ArchivedLogs C:\\Sigma\\Data\\ArchivedTransactions ⚠️ Note: These files should only be removed for space-saving purposes. Sigma can be configured to access and view these archived files. Files Requiring System Shutdown Before Backup For all other Sigma files, it is strongly recommended to shut down both the Sigma server and all clients before initiating a backup. This ensures that no files are open or in use during the process. Restoring Data Data restoration must only be performed after the Sigma system has been completely shut down. Additional Notes This guidance applies to both automatic and manual backup procedures. Always verify that the Sigma system is offline before handling non-archived files.

Issue How to read a 32-bit integer value stored across two 16-bit registers using IC-Modbus. Product Line Satchwell BAS & Sigma Environment IC-Modbus IC3-Modbus Cause Prior to firmware release 4.05, IC3-Modbus did not natively support reading 32-bit integer values directly. Resolution IC3-Modbus 4.05 and Later Firmware version 4.05 introduced support for reading 32-bit values using Function Codes 03 (Read Holding Register) and 04 (Read Input Register). Supported 32-bit data types: Signed 32-bit Signed 32-bit (swapped) Unsigned 32-bit Unsigned 32-bit (swapped) Float 32-bit Float 32-bit (swapped) 🔹 Note: This is a special case of the “2 register read” and requires two consecutive Sigma object numbers. Refer to: Sigma - Release 4.06 - Firmware IC3-Modbus Release Note Section 11.4.2 – 32-bit Data Types Other Sigma Versions (Pre-4.05) To read a 32-bit integer from two 16-bit registers: Read both registers into separate Analogue Input (AI) objects. Combine the values using a programmable object: Multiply the high register by 65536 Add the low register value 💡 Example Code Snippet   10 XFlo = POINT 0|64 ; High register 20 YFlo = POINT 0|65 ; Low register 30 ZFlo = (XFlo * 65536.0) + YFlo 40 RETURN VIA TEXT 200 VALUE ZFlo ; Use a suitable text object Notes Ensure the register order (high vs. low) matches the device’s Modbus specification. Use Text 200 or a similar object to display the final 32-bit value.

Issue OPC values are visible via an OPC client on the local PC, but not accessible from another OPC client across the network. Product Line Satchwell BAS & Sigma Environment Sigma ModBMS Matrikon OPC Client Cause The DCOM settings on the OPC Server PC are not correctly configured for remote access. Resolution   Configure DCOM Settings Refer to the official Matrikon OPC documentation for detailed instructions. 👉 Download Matrikon OPC DCOM Configuration Guide Install Matrikon OPC Client 👉 Download Matrikon OPC Explorer Launch Matrikon OPC Explorer Navigate to Network Neighborhood Locate the OPC Server PC Select ModBMS-OPCserver Create a New Group Right-click and choose Add Group Name the group as needed Add required tags Validate Tags Right-click the group De-select Use Async I/O The OPC values should now be displayed Additional Resources 📎 Using OPC via DCOM with Microsoft Windows XP SP2