Building Automation Knowledge Base

Notifications

Community

Notifications

Categories
Forums
Knowledge Center
Blogs
Ideas
Events & Webinars

Share Your Feedback – Help Us Improve Search on Community!
Please take a few minutes to participate in our Search Feedback Survey. Your insights will help us deliver the results you need faster and more accurately.
Click here to take the survey

Building Automation Knowledge Base

Schneider Electric Building Automation Knowledge Base is a self-service resource to answer all your questions about EcoStruxure Building suite, Andover Continuum, Satchwell, TAC…

Search in

Invite a Co-worker

Send a co-worker an invite to the portal.Just enter their email address and we'll connect them to register. After joining, they will belong to the same company.

Send Invite Cancel

Related Forums

Intelligent Devices Forum

Previous Next

Invite a Colleague

Found this content useful? Share it with a Colleague!

Invite a Colleague

Building Automation Knowledge Base

Issue Users may encounter a Run-up/down influence node error when working with MN50 Controller Optimisers. Product Line Satchwell MicroNet Environment Satchwell MicroNet 50 Series Controller Cause This issue is caused by a firmware limitation in earlier versions of the MN50 controller software. Resolution To resolve the error: Upgrade the MN50 Controller firmware to Version 5.02. This version includes a fix specifically addressing the Run-up/down influence node error.

Issue Clarification is required on the appropriate cable types to use for MicroNet LAN communications to ensure reliable and compliant system performance. Product Line Satchwell MicroNet Environment Satchwell MicroNet Cause Selecting the correct communication cable is critical for maintaining signal integrity and ensuring proper operation of the MicroNet LAN. Using incorrect cabling may result in communication failures or degraded performance. Resolution For optimal performance and compliance with MicroNet LAN communication standards, the following cable specifications are recommended: Standard One-Pair Communications: Use Belden 8762 or an equivalent cable. Belden 8762 is a shielded, twisted pair cable suitable for general communication wiring. Isolated LAN Communications: Use Belden 9502 or an equivalent cable. Belden 9502 is a shielded, twisted pair cable designed for applications requiring electrical isolation. 📎 Attachments: Belden 8762 Data Sheet (PDF) Belden 9502 Data Sheet (PDF) Additional Information: Always ensure that the selected cable meets or exceeds the specifications of the recommended Belden models. Proper installation practices, including grounding and shielding, are essential for optimal communication performance.

Issue Micronet LCDs may fail to upload configurations from MicroNet controllers correctly, leading to incomplete or missing display data. Product Line Satchwell MicroNet Environment MicroNet LCD Displays MicroNet Controllers VisiSat Configuration Tool Cause The upload failure typically occurs when the LCD configuration is not properly transferred from the controller’s RAM to the LCD’s EEPROM. This can happen due to: Power cycling or resetting the controller before LCD connection Incorrect connection sequence Locked configuration settings in VisiSat Resolution Follow these steps to ensure successful upload and avoid data loss: How the Upload Process Works Download to Controller: LCD configuration is first downloaded to the controller’s RAM. Transfer to LCD: When the LCD is connected, it detects the configuration file and transfers it to its EEPROM. RAM Clearance: After transfer, the controller’s RAM copy is deleted. Important: If the controller is powered off or reset before the LCD is connected, the configuration will be lost. LCD Download Procedure Power On Controller: Ensure the controller is powered before starting. Download Configuration via VisiSat. For Standalone NCP Controllers: Disconnect communications before connecting the LCD. Ensure LCD comms links are properly fitted. For Networked NCP Controllers: Install an MNN-COM card. LCD must be remotely mounted. Connect LCD: Keep controller power ON. Apply power to the LCD. Note: Do not press any keys during connection unless using firmware revision J or earlier. Wait for Configuration Load. Troubleshooting: If upload fails, check that the controller’s “Configuration Locked” property is set to No in VisiSat. Final Step: Remove the protective strip from the LCD battery.

Issue To outline the process for replacing a Satchwell MicroNet MN300, MN440, MN500 or MN620 controller with a Satchwell MicroNet 50 series controller — MN350, MN450, MN550 or MN650 — using VisiSat software. Product Line Satchwell MicroNet Environment Satchwell MicroNet Controllers: MN300, MN440, MN500, MN620 Satchwell MicroNet 50 Series Equivalents: MN350, MN450, MN550, MN650 VisiSat v2.1 or later Cause Satchwell MicroNet series MN300, MN440, MN500 and MN620 are replaced by the MN350, MN450, MN550 and MN650 controllers respectively. MN300, MN440, MN500 and MN620 controllers installed on existing installations may need to be replaced with newer 50 series controllers. Resolution Upgrade the VisiSat Project If the original project was created in VisiSat 1.2 or 2.0: Use the Project Upgrade Utility to convert it to VisiSat 2.1 format. Refer to VisiSat 2.1 Engineering Guide, pages 47–50, for instructions. 2. Upgrade the Controller Object Open the project in VisiSat. Right-click the legacy controller (e.g., MN300) and select “Upgrade Controller.” Save the controller configuration (.CLC file) when prompted. The controller object will be updated to the corresponding MicroNet 50 series model (e.g., MN350). 3. Install the Replacement Controller Physically install the new MicroNet 50 series controller. Confirm jumper settings are correct. Transfer any communication cards from the old controller if applicable. 4. Download Configuration In VisiSat, open the Configuration Library. Select the controller and click “Download Configuration” (second button from the left). This will transfer the configuration to the new controller. Refer to pages 135–140 of the Engineering Guide for more details. Tip: The “Upgrade Controller” button in the Configuration Library performs the same function as the upgrade option in step 2.

Issue Can the SHO2XA2A humidity sensor be safely exposed to hydrogen peroxide (H₂O₂) during decontamination procedures? Product Line Field Devices. Environment SHO2XA2A. Cause The SHO2XA2A, along with SHD2 and CP series humidity sensors, are not resistant to hydrogen peroxide. Exposure to H₂O₂ can degrade sensor components, leading to inaccurate readings or device failure. Resolution For environments requiring decontamination with hydrogen peroxide, use the SH5 or ST5 series instead. These models feature probes specifically designed to withstand H₂O₂ exposure.

Issue You need to integrate both: VingCard lock MTH-G-5045 / WDC-G-5045 window and presence contacts …into a Zigbee network on the same RP-C (Room Controller) device. Product Line EcoStruxure Building Operation. Environment Building Operation Room Controller (RPC) 24 V. Zigbee Cause When performing device discovery: If using Zigbee VingCard Network, the MTH-G-5045 / WDC-G-5045 devices are not found. If using Zigbee Standard Security Network, the MTH-G-5045 / WDC-G-5045 devices are found. This occurs because the two Zigbee networks are fundamentally different in protocol and device compatibility. Resolution It is not possible to use both Zigbee VingCard Network and Zigbee Standard Security Network simultaneously on the same RP-C device. You must choose one Zigbee network type per RP-C: If you need VingCard lock integration, use Zigbee VingCard Network. If you need MTH-G-5045 / WDC-G-5045 integration, use Zigbee Standard Security Network. ⚠️ Important: These networks are mutually exclusive on a single RP-C. Consider deploying separate RP-C devices if both network types are required in the same installation.

Issue When using MZ20A or MZ20A-R actuators with the surface-mounted S-UNC-AO card, the actuator may stop functioning, and the analogue output remains at 0 volts after a power cycle. Product Line Satchwell BAS & Sigma Environment Satchwell Sigma S-UNC-AO Card MZ20A Actuators Cause If both the controller power and battery switches are turned off, upon restoring power, the analogue output may fail to resume normal operation, remaining at 0V. This is due to the absence of a discharge path for the analogue output channels. The precise root cause of the controller lock-up is currently undetermined. However, it has been observed that certain conditions during editing can trigger this behavior. Resolution To prevent this issue: Install a 2.2kΩ resistor (2K2 ohm) between each analogue output channel and the common 0V rail . The resistor provides a discharge path, ensuring the output voltage returns to normal after power is restored. Resistor Specifications: Type: Carbon Film Rating: ¼ watt, 5% tolerance Example: RS Stock No. 135-881 (or equivalent) 💡 Note: This modification is only required for MZ20A actuators. If the actuator is replaced with a different model, the resistor should be removed.

Issue Editing Multi-Stage control objects in Sigma may cause the controller to lock up unexpectedly. Product Line Satchwell BAS & Sigma Environment Satchwell Sigma Cause The precise root cause of the controller lock-up is currently undetermined. However, it has been observed that certain conditions during editing can trigger this behavior. Resolution To mitigate the risk of controller lock-up when working with Multi-Stage control objects, follow these best practices: Download the Complete Object File Periodically Before and during editing sessions, ensure you download the full object file to maintain a stable configuration and reduce the risk of corruption or lock-up. Disable Contingency Logging Temporarily If contingency logging is enabled on the Multi-Stage control object, disable it before making any changes. This has been shown to reduce the likelihood of controller instability.

Issue Users may observe that AI (Analog Input) object temperatures in Sigma controllers suddenly increase or fluctuate unexpectedly when viewed through system logging. Product Line Satchwell BAS & Sigma Environment Sigma controllers Cause This issue is typically caused by a faulty processor (CPU) card within the Sigma controller. The fault leads to incorrect readings being processed and displayed. Resolution To resolve this issue: Replace the CPU card in the affected Sigma controller. After replacement, monitor the AI object values to confirm stability and accuracy.

Issue After upgrading to Sigma 4.05 SEB, the log configurations are not visible in the configuration window. Product Line Satchwell BAS & Sigma Environment Satchwell Sigma Cause The LogCNF.rec file was not properly upgraded during the transition to Sigma 4.05 SEB. This results in the log configuration not being displayed. Resolution To restore visibility of the log configuration: Shutdown Sigma Services Close both the Sigma client and server applications. Restore the Configuration File Locate a backup of the LogCNF.rec file. Copy it to the following directory: C:\Sigma\Data\ServerXXX\ Replace XXX with the appropriate server number. Run the Upgrade Utility Execute the Sigma upgrade tool: C:\Sigma\BinUtils\SigUpgrade.exe Restart Services Restart both the Sigma server and client. Verify Open the configuration window to confirm that the log configuration is now visible.

Issue The Requested Clients window in Sigma displays a remote client as being off-line, even though it is active. Product Line Satchwell BAS & Sigma Environment Satchwell Sigma Cause This behavior is due to Sigma defect 3174, where the status shown in the Registered Clients window may be incorrect. The issue arises when the remote client is started before the local client, leading to a misrepresentation of its online status. Resolution To resolve this issue, you have two options: Upgrade Sigma: The defect was been corrected in Sigma release 4.05 SEB. Upgrade the site to this release or any later version to permanently fix the issue. Workaround (if upgrade is not possible): Shut down Sigma. Restart the local client first, then start the remote client. This sequence ensures accurate status reporting in the Requested Clients window.

Issue After upgrading Remote Alarm Manager from version 1.2 to 2.0, site-specific configuration settings are not retained. Additionally, the software fails to detect the license. Product Line Satchwell BAS & Sigma Environment Remote Alarm Manager 2.0 Cause The upgrade path included multiple version changes over time. Earlier versions (prior to 1.001) stored configuration data alongside source system data, typically in: C:\Sigma\Data\Remote Alarm Manager\ Newer versions store data in OS-specific default locations: Windows XP: C:\Documents and Settings\All Users\Application Data\Schneider Electric\Remote Alarm Manager Windows Vista and later: C:\ProgramData\Schneider Electric\Remote Alarm Manager Resolution There are two recommended methods to resolve this issue: Option 1: Update Data Location via Configuration Utility After installing Remote Alarm Manager 2.0, launch the Computer Configuration Utility (runs by default). Navigate to the Data Location tab. Uncheck the Windows Common Application Data checkbox. Manually enter the path to the current Remote Alarm Manager data location. Option 2: Manually Copy Configuration Files After installation and running the Computer Configuration Utility: Copy the following files from the current data location to the default location used by the software: setup.mdb log.mdb Default locations: Windows XP: C:\Documents and Settings\All Users\Application Data\Schneider Electric\Remote Alarm Manager Later OS versions: C:\ProgramData\Schneider Electric\Remote Alarm Manager

Issue How can logging configuration be removed from a controller in Sigma release 4.04? Product Line Satchwell BAS & Sigma Environment Sigma Release 4.04 Cause Sigma 4.04 does not provide a direct method to download an empty logging configuration file to a controller. This limitation requires a manual workaround to effectively remove logging configurations. Resolution There are two recommended methods to delete logging configurations from a controller: Method 1: Manual File Deletion via Explorer Open Sigma and navigate to the Logging Configuration section. Delete the unwanted logging data set from the configuration. Using Windows Explorer, go to the controller’s folder location. Locate and delete the logging configuration file. Example filename: T0025400.100 T00254 = Server 00.100 = Controller In Sigma System Diagnostics, re-download the logging configuration to the controller to apply the changes. Method 2: Minimal Logging Configuration In Sigma, go to Logging Configuration. Open the required log data set. Delete all objects in the data set except one. Set the remaining object to log very infrequently. Save and download the configuration as usual. Optionally, delete the log data set entirely. This will result in the controller logging only one object at a minimal rate. Upon the next download of controller files, logging will be effectively removed.

Issue In Sigma System Manager, the object associated with the first entry in the Gateway.txt file of an S-IC3-SNP integration controller consistently displays its default value, rather than the expected mapped value. Product Line Satchwell BAS & Sigma Environment Sigma IC3-SNP Cause This issue arises due to the way the S-IC3-SNP controller processes the object mapping file ( Gateway.txt ). Specifically, the first line in the file is not correctly interpreted, causing the first object to revert to its default value. Note: This behavior does not affect earlier versions such as S-IC-SNP. Resolution Steps to Resolve: Edit the Gateway.txt file. Insert a dummy line at the beginning of the file. This placeholder prevents misinterpretation of the first actual object. Example Original Gateway.txt : 51,13,R,114,2,0,0,3,1 ;Room temperature 52,13,R,114,28,0,0,3,1 ;PIR Status 53,13,R,160,6,0,0,3,1 ;Heating Valve Open Revised Gateway.txt with Dummy Line: 51,13,R,114,2,0,0,3,1 ;Dummy text entry 51,13,R,114,2,0,0,3,1 ;Room temperature 52,13,R,114,28,0,0,3,1 ;PIR Status 53,13,R,160,6,0,0,3,1 ;Heating Valve Open Save and reload the configuration in Sigma System Manager. ✅ The first object should now display its correct mapped value.

Issue Can Sigma operate in a network environment using Layer 3 switches? Product Line Satchwell BAS & Sigma Environment Satchwell Sigma Layer 3 switches Cause The site is transitioning from Layer 2 switches to Layer 3 switches, prompting a need to understand Sigma’s compatibility with Layer 3 networking. Resolution Yes, Sigma products support IPv4 Layer 3 networking. Routing Protocol: Sigma uses RIP version 1 (Routing Information Protocol) for message routing. IP Communication: Sigma devices communicate using 32-bit IPv4 addresses with various subnet masks. Ensure that the Layer 3 switches are configured to support RIP v1 to maintain proper routing between Sigma devices. Additional Notes RIP v1 is a classful routing protocol, which may limit subnet flexibility. Consider network design implications when planning your Layer 3 migration. If your infrastructure requires more advanced routing protocols (e.g., RIP v2, OSPF), Sigma may not be compatible without additional configuration or hardware.

Issue Recipients are receiving inactivated alarm messages from the Sigma Remote Alarm Manager (RAM). These messages typically resemble the example shown below. Product Line Satchwell BAS & Sigma Environment Satchwell Sigma Remote Alarm Manager Cause These messages are not nuisance alarms. They occur because the original Sigma alarms have not been acknowledged in the Sigma Alarm Manager. By default, if an alarm remains unacknowledged for 3 days, it is removed from the RAM active alarm list and an inactivation message is sent to recipients. Resolution While you cannot prevent the inactivation message from being sent, you can extend the time before the alarm is removed from the active list. To adjust this setting: Open the Sigma R4 interface configuration. Locate the “Days before inactivation” setting. Modify the value to the desired number of days. Additional Notes These messages serve as a reminder that alarms require acknowledgment. Adjusting the inactivation period can help reduce message frequency but does not eliminate the need for proper alarm management.

Issue A customer needs a small number of I/O points at the location of the Integration Controller and wants to know if Sigma Integration Controllers support onboard I/O. Product Line Satchwell BAS & Sigma Environment Sigma Integration Controllers Cause The customer is evaluating the feasibility of using an Integration Controller (IC) to handle limited I/O requirements locally, without deploying additional hardware. Resolution The IC3 Integration Controller does not have any onboard I/O capabilities. Therefore, it cannot be used in applications where direct I/O is required at the controller location.

Issue Alarms generated by Sigma controllers are sometimes delayed in appearing at the Sigma server. This behavior is inconsistent—manual alarm tests display correctly, but real-time alarms may not appear until other activities are performed. Product Line Satchwell BAS & Sigma Environment Satchwell Sigma Cause There are two recommended solutions depending on your network setup: Option 1: Disable Windows Firewall If the Sigma server is not connected to the Internet, you can safely disable the Windows Firewall to allow uninterrupted alarm communication. ⚠️ Note: The method to disable the firewall varies by operating system. Use the system's Help feature for guidance. Option 2: Add a Firewall Exception If disabling the firewall is not viable, configure a firewall exception for Sigma: Open Windows Firewall. Navigate to the Exceptions tab. Select Add Port. Enter the following details: Name: Sigma UDP Port Port Number: 49152 Protocol: UDP ✅ This allows Sigma alarm messages to pass through even when the firewall is active. Additional Notes Port 49152 is specific to Sigma and must be configured as a UDP port.

Issue How to configure the new surface mount Analogue Output boards to provide a 0–20 mA control signal instead of the default 0–10 V output. Product Line Satchwell BAS & Sigma Environment Sigma UNCX96 Outstations New style surface mount Analogue Output boards Cause Some connected field devices require a 0–20 mA signal for proper operation. The new AO boards support both 0–10 V and 0–20 mA outputs but require manual configuration to switch between these modes. Resolution To configure the AO board for 0–20 mA output: Identify Channels: Only Channels 15 and 16 on the new surface mount AO board support 0–20 mA output. Locate Link LK1: On the AO board, find the LK1 jumper associated with each channel. Set Output Mode: To enable 0–20 mA output, move the LK1 jumper to the 0–20 mA position. To revert to 0–10 V output, place the jumper back to the 0–10 V position. ⚠️ Important: Ensure power is turned off before adjusting the jumper settings to avoid damage or incorrect configuration.

Issue The Analogue Input (AI) Objects were functioning correctly but suddenly failed. Instead of displaying the expected default value of 20.0, they now show their last recorded value. Upon testing, the inputs return different values, and temperature detectors consistently read 150°C, while heat flow rates show 0 m³/hr. Product Line Satchwell BAS & Sigma Environment Sigma UNCX96 Analogue Input (AI) card Cause The issue stems from incorrect controller slot allocation. The slot is mistakenly configured as empty, which prevents the AI card from functioning properly. Resolution To resolve the issue: Access the controller configuration. Verify the slot allocation. Ensure the slot is correctly assigned as an Analogue Input (AI). Download the updated configuration to the controller.

Building Automation Knowledge Base

Improve your search experience:

Related Forums

Intelligent Devices Forum

MN50 Controller Optimisers – Run-up/down Influence Node Error

What Specification of Cable Should Be Used for MicroNet LAN Communications?

MN-LCD Uploading – Best Practices

Replacing Satchwell MicroNet Controllers with MicroNet 50 Series Equivalents

Does SHO2XA2A (Humidity Sensor) Withstand Decontamination with Hydrogen Peroxide (H₂O₂)?

Using Zigbee VingCard Network and Zigbee Standard Security Network on the Same RP-C

Sigma – Using MZ20A Actuators with the Surface Mount Version of the S-UNC-AO Card

Sigma – Working on Multi-Stage Control Objects Can Cause Controller Lock-Up

Sigma – Sudden Increase in Displayed Temperatures

Sigma 4.05 Log Configuration Not Displayed

Sigma - Requested Clients Window Shows a Remote Client as Being Off-line

Remote Alarm Manager Settings Lost After Upgrade

Sigma - How to Delete Logging Configuration from a Controller (Release 4.04)

First object in a Sigma IC3-SNP always displays it's default value

Sigma – Can a System Run on a Layer Three Subnet?

Sigma - Remote Alarm Manager – Inactivated Messages Are Received by Recipients

Sigma Integration Controllers – Are I/O Available on an IC?

Sigma – Delayed Alarms at the Sigma Server

Sigma – Configuring 0–20 mA Outputs on New Surface Mount Analogue Output Boards

Sigma - Analogue Input Card Does Not Display the Correct Values

Ask our Experts

Email Us

Building Automation Knowledge Base

Related Forums

Ask our Experts

Email Us

Welcome!