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 Alarm messages generated by the Remote Alarm Manager (RAM) do not include the date and time by default. However, some sites require this information to be present in the alarm text messages for compliance or operational clarity. Product Line Satchwell BAS & Sigma Environment Remote Alarm Manager Cause By default, RAM's basic text message configuration does not include the alarm date and time. This omission may not meet specific site or regulatory requirements for timestamped alarm notifications. Resolution To include the date and time in the alarm message, follow these steps to modify the message script in the RAM Console: Open RAM Console. Navigate to Configuration and select the required Action. Click Edit on the selected Action, then go to the Messages tab. Select the Advanced option and click Edit Script. In the Script Editor: Go to File > Open File. Browse to and open the desired script file. Modify the script to include the required fields. Example Script Output Format For Alarm Messages: Message No (non-configurable), Alarm Priority, Alarm Date/Time, Mnemonic, Value (e.g., Plant On / Plant Off) For Alarm Cleared Messages: Message No (non-configurable), Alarm Date/Time, Mnemonic, Value (e.g., Plant On / Plant Off) 💡 Tip: An example script file is available for download: [RAM Script.zip]

Issue The GSM modem fails to send a text message when an alarm is generated in the Sigma Remote Alarm Manager. Product Line Satchwell BAS & Sigma Environment Remote Alarm Manager (RAM) Cause The issue is typically due to incorrect configuration within the Remote Alarm Manager, particularly in the recipient settings or interface selection. Resolution Verify Configuration Settings: Open the Remote Alarm Manager configuration interface. Navigate to the Recipient Configuration section. Check Interface Selection: Ensure the correct communication interface is selected for the GSM modem. Confirm that the modem is properly connected and recognized by the system. Test Modem Functionality: Attempt to send a manual test SMS from the Remote Alarm Manager. If the modem does not respond, check for error messages such as: "Unable to reset GSM modem" "Modem did not accept reset command" Review Common GSM Modem Compatibility: Refer to the list of commonly used GSM modems compatible with RAM. Ensure your modem model is supported and configured according to Schneider Electric guidelines. Restart and Retest: Restart the Remote Alarm Manager service. Trigger a test alarm to verify SMS delivery. Additional Resources Sigma - Remote Alarm Manager - Commonly used GSM modems

Issue When scrolling through an index in Sigma, the same index entry appears repeatedly. Product Line Satchwell BAS & Sigma Environment Satchwell Sigma Cause This issue typically occurs during software creation. The index entry has been mistakenly referenced to itself, resulting in a loop where no additional pages are created beneath the affected entry. Resolution To resolve the issue: Open SigmaX and navigate to: Doctor Utility > Index Edit Locate the problematic index entry. Choose one of the following actions: Delete the page: Only do this if there are no index entries following the one in question. Correct the page reference: Identify the intended destination page and update the page number accordingly. Example: BLD_HTP_ Heating Plant 0 0 22 0 0 0 0 🔐 Note: The password required to edit the index is ie .

Issue In BAS or Sigma, users may attempt to totalise multiple alarm points using the + add function in programmable points, such as: 10 XFlo = POINT 0|14 ALARM + POINT 0|15 ALARM + POINT 0|16 ALARM 20 YFlo = POINT 0|17 ALARM + POINT 0|18 ALARM + POINT 0|19 ALARM 30 RETURN VIA TEXT 91 VALUE XFlo + YFlo While this compiles in the programmable point editor, it does not function correctly in the BAS or Sigma controller. Product Line Satchwell BAS & Sigma Environment Satchwell BAS & Sigma Cause The Sigma controller does not support direct arithmetic operations on alarm points using the + operator. This limitation leads to compilation success but runtime failure. Resolution To correctly totalise alarms, rewrite the programmable point using conditional logic. Here's a working example: 10 XFLO = 0.0 20 IF POINT 0|14 ALARM THEN XFLO = XFLO + 1.0 30 IF POINT 0|15 ALARM THEN XFLO = XFLO + 1.0 40 IF POINT 0|16 ALARM THEN XFLO = XFLO + 1.0 50 IF POINT 0|17 ALARM THEN XFLO = XFLO + 1.0 60 IF POINT 0|18 ALARM THEN XFLO = XFLO + 1.0 70 IF POINT 0|19 ALARM THEN XFLO = XFLO + 1.0 80 RETURN VIA TEXT 91 VALUE XFLO If the number of alarm points exceeds the token limit for a single programmable point, split the logic across multiple points and combine them: 10 XFLO = (POINT 0|a + POINT 0|b + ...) 20 RETURN VIA TEXT 91 VALUE XFLO

Issue Upon logging into Sigma, users may notice that text elements on the start-up graphic are misaligned. This misalignment corrects itself only after the graphic is clicked. Product Line Satchwell BAS & Sigma Environment Sigma 4.05 SEB build 3.41.18 Cause This issue occurs intermittently and is isolated to the start-up graphic displayed immediately after login. It appears to be a rendering glitch specific to the mentioned build version. Resolution To resolve this issue: Recommended Fix: Upgrade Sigma to a later version where this issue has been addressed. Temporary Workaround: Clicking on the graphic manually realigns the text, but this is not a permanent solution.

Issue Uncertainty regarding the wiring connections for Digital Output Interface modules used with Sigma UNCX96 controllers. Product Line Satchwell BAS & Sigma Environment BAS or Sigma UNCX96 controller Cause Lack of documentation or clarity on how Digital Output Interface modules are connected to the controller. Resolution UNC 696 Controller Enclosure: Robust metal case, typically used in standalone installations. Module Capacity: Can house two Digital Output Interface modules internally—one on each side. Connection Method: Modules are connected to the motherboard via ribbon cables. These modules are associated with I/O Slot 1: Left Module: I/Os 1–8 Right Module: I/Os 9–16 Expansion: Only Slot 1 supports ribbon cable connections. Additional modules must be hard wired. UNC 796 Controller Connection Method: Digital Output Interface modules are typically hard wired to controller slots. Ribbon cables can be used, but this is uncommon.

Issue When editing objects on a remote Sigma client, the editing window takes approximately 10 seconds to open. Product Line Satchwell BAS & Sigma Environment Sigma client software Cause The delay is primarily due to the PC or laptop not meeting the recommended minimum specifications for running Sigma effectively. Resolution To improve performance and reduce latency when editing objects, ensure the client machine meets or exceeds the minimum system requirements: Minimum System Requirements for Sigma Server or Standard Client: Processor: 2.0 GHz (minimum) RAM: 2 GB Hard Disk: Minimum 16 GB free space Graphics Card: 128 MB SVGA Monitor: 1024x768 resolution, 17" Network Interface: Ethernet NIC with 100base-T connector (RJ45) Ports: Parallel Printer Port or USB (as appropriate) 1 spare USB port for Dongle (Server only) Optical Drive: CD-ROM (CD-Writer recommended) Input Devices: Mouse and keyboard Operating System: 32-bit OS (Note: Sigma does not benefit from more than 4 GB RAM due to OS limitations) Recommended for Larger Systems (10+ controllers): Processor: Pentium 3.2 GHz Quad Core RAM: 3–4 GB Hard Disk: High-speed SATA II, 7200 rpm, minimum 16 MB cache ⚠️ Note: While Sigma can run on lower-spec machines, performance will be significantly reduced. Always aim for the highest specification possible for optimal performance.

Issue What is the recommended method for implementing daylight saving time (DST) changes—such as summer/winter transitions—in Sigma? Product Line Satchwell BAS & Sigma Environment Satchwell Sigma Cause To ensure consistent and accurate time synchronization across Sigma servers and controllers during daylight saving time transitions. Resolution To configure DST changeover in Sigma effectively, follow these steps: 1. Configure Server Operating System On all Sigma server PCs, enable “Automatically adjust clock for daylight saving changes” in the Date and Time settings of the operating system. 2. Use Sigma Scheduler to Retime Controllers Create schedules in Sigma that retime controllers in staggered intervals to avoid system overload and ensure proper logging. Recommended Schedule Example: Time Action 02:00 Retime Sigma Server 02:02 Retime Controllers – Group 1 02:12 Retime Controllers – Group 2 02:22 Retime Controllers – Group 3 ... Continue in intervals as needed Tip: Avoid retiming all controllers simultaneously. Staggering helps ensure logs are returned to the server before the next retime. 3. Configure Actions and Schedules in Sigma Step 1: Create an Action in Sigma that targets a group of controllers for retiming. Step 2: Link the Action to a Schedule that executes at the appropriate time during the DST changeover. Additional Notes This method supports both spring forward and fall back transitions. It minimizes disruption and maintains accurate time synchronization across the Sigma system. Adjust the number of controller groups and intervals based on system size and performance.

Issue Users may need to access a UNC532 or UNC632 controller using its dedicated keyboard but are unsure of the default passcodes. Product Line Satchwell BAS & Sigma Environment UNCX32 Keyboard Cause The default passcodes for these keyboards are often forgotten or unknown, especially as keypads have been replaced by PDAs in newer systems. Resolution The default passcodes for UNC532 and UNC632 keyboards are: 2001 1066 1482 0338 8420 Note: These keyboards are designed to interrogate only the controller they are physically connected to. They are not interchangeable across different controller models. Additional Notes Keypads used in legacy BAS systems have largely been replaced by PDAs. These keyboards are only compatible with UNC532 and UNC632 controllers.

Issue In Dataview and Dynaview within Sigma 4.08, the AM/PM indicator is not displayed when using the crosshairs feature on a graph. This can lead to confusion when interpreting time-based data on graphs. Product Line Satchwell BAS & Sigma Environment Sigma 4.08 Cause The issue arises due to the time format settings in the Windows operating system. When the time format includes the 'tt' designator (used for AM/PM), the crosshairs feature in Dataview and Dynaview does not correctly display the AM/PM suffix. Resolution To resolve this issue, switch to a 24-hour time format in Windows. This avoids the need for AM/PM indicators and ensures accurate time display in the graph crosshairs. Steps to Change Time Format: Open Control Panel. Navigate to Region and Language. Go to the Formats tab. Click on Additional settings.... Under the Time tab: Change Short time and Long time formats to use the 24-hour format (e.g., HH:mm instead of hh:mm tt ). Click Apply and then OK.

Issue Users may encounter unexpected behavior when accessing certain applications via Windows Remote Desktop (RDP). These issues may appear to be product-related but are actually due to limitations or behaviors of RDP itself. Product Line Satchwell BAS & Sigma Environment Sigma ModBMS OPC Cause These issues stem from how Windows Remote Desktop handles hardware and graphical interfaces. It may not fully support certain device drivers or UI components, leading to inconsistent behavior. Resolution Affected Components and Symptoms Sigma – Dongle Configuration Error Symptom: When the dongle is checked from a remote PC, the configuration appears incorrect. Clarification: On the local server, the dongle is correctly configured. This discrepancy is due to how Remote Desktop interacts with hardware dongles. Sigma – Alarm Manager Operation Symptom: Alarm Manager does not function as expected when accessed remotely. Clarification: The application operates normally when used directly on the server. MatrikonOPC Client Symptom: OPC data is not displayed correctly via Remote Desktop. Workaround: Viewing the client through VNC instead of Remote Desktop resolves the issue. Recommendations Use Local Access: Whenever possible, access affected applications directly from the server. Alternative Remote Tools: Consider using VNC or other remote access solutions that better support hardware and graphical interfaces. Verify Locally: Always confirm configuration and functionality directly on the server before troubleshooting further.

Issue According to the product documentation, it should be possible to configure temperature and humidity offsets via Modbus or BACnet for SLP room sensors using specific registers. However, these registers are unresponsive (e.g., return errors or appear offline). Product Line EcoStruxure Building Operation Environment Building Operation SmartX Living Space Sensor Cause The customer is attempting to calibrate the temperature reading, which appears incorrect on the sensor display. However, not all SLP units support the offset feature. Resolution Supported Models: Only SLPSLX2 units produced after Week 26 of 2024 support the temperature and humidity offset feature. Unsupported Models: Units manufactured before Week 26 of 2024 do not support this feature and cannot be field-upgraded. Action Required: If the installed unit does not support the offset feature, it must be replaced with a newer unit that includes the updated firmware. Identifying Production Date: The production date is printed on the box label and on the SLP itself. Use this to verify whether the unit supports the offset functionality.

Issue A red border appears around the bindings window when interacting with the binding interface. Product Line EcoStruxure Building Operation Environment Building Operation Workstation Cause This behavior occurs when the cursor is pointing to a binding title (typically green in color) that is not editable. The system visually indicates this by displaying a red border around the bindings window. Resolution This is expected behavior and serves as a visual cue to the user. To avoid the red border: Ensure the cursor is not hovering over a non-editable binding title. Move the cursor to an editable field or outside the binding title area.

Issue The IP rating for the ETD200-6 is not specified in the product documentation. Product Line Field Devices Environment ETD200-6. Cause Documentation does not include the enclosure's IP rating, leading to uncertainty during specification or installation. Resolution The enclosure of the ETD200-6 has an IP10 rating. Note: IP10 indicates limited protection against solid objects greater than 50 mm and no protection against liquids. This rating may affect installation environments where higher protection is required.

Issue Supported Import and Export File Formats in Graphics Editor Product Line EcoStruxure Building Operation Environment TGML Cause Clarification of Supported File Formats in TGML Resolution TGML Overview TGML (TAC Graphics Markup Language) is an XML-based declarative language designed for creating dynamic 2D graphics within EcoStruxure Building Operation. Graphics developed in the Graphics Editor are saved with the .TGML file extension. When a graphic is created, a TGML root object is automatically generated and placed at the bottom of the Objects tree in the editor’s object pane. This root object also serves as the default layer in the Graphics Editor workspace and cannot be deleted. For more info: TGML File Format

Issue When attempting to rename a newly created Enterprise Server, the following validation error may be encountered: "Validation failed for property 'HttpPort' Path: 'Enterprise Server/HttpPort' Type: 'HttpPort' The value '0' is outside the range of allowed values" Product Line EcoStruxure Building Operation Environment Enterprise Server Cause Although the error message references an invalid HTTP port assignment, the underlying issue is typically related to the Enterprise Server's certificate configuration. This scenario often arises when a new Enterprise Server is created from a backup containing a base configuration, which includes an outdated or incompatible certificate. Resolution To resolve the issue: Remove the active certificate associated with the Enterprise Server. EBO WebHelp documentation for detailed instructions on certificate removal: Removing a Certificate Using WorkStation Once the certificate is removed, the renaming operation should proceed without triggering the validation error.

Issue Customers may require dynamic logging of alarm events, including specific values or metadata at the time of the event. Substitution codes provide a flexible way to embed such data directly into the file output. Product Line EcoStruxure Building Operation Environment EcoStructure Building Operation Cause When using write to file notification objects it may be desirable to have dynamic text containing actual values etc. Resolution Write-to-file notification objects in EcoStruxure Building Operation can be configured to include dynamic content using substitution codes. These codes allow insertion of real-time alarm properties into the message body written to the file, enabling more informative and context-aware logging. Summary Substitution codes are supported only in the message body, not in the file name. The syntax for substitution codes is: @([property]) where [property] corresponds to a valid alarm attribute. If an invalid or unsupported property is used, the system will replace the substitution code with an empty string. Example: Alarm triggered at @([TimeStamp]) with value @([Value]) from source @([Source]). Important Notes Ensure that the substitution code used is applicable to the specific alarm event type. For email-based alarm notifications, refer to: Displaying different properties of an alarm in an email notification.

Issue How to display custom text and properties of an alarm in the email notification. Product Line EcoStruxure Building Operation Environment Email Notification Substitution Codes Cause To enhance the clarity and relevance of alarm email notifications, EcoStruxure Building Operation supports the use of substitution codes. These codes allow dynamic insertion of alarm-specific properties—such as the value at the time of the alarm trigger—into the email subject or body. Resolution To customize alarm email content: Navigate to the Email Notification object in the system. In the Properties pane, locate the Subject and Text fields. Enter desired message, incorporating substitution codes where needed. Example: Subject: Alarm Triggered - %AlarmName% Text: The alarm '%AlarmName%' was triggered at %TimeStamp%. Value at trigger: %Value%. In scenarios where detailed context is required (e.g., documenting the exact value that caused an alarm state change), substitution codes enable automated inclusion of such data in the notification message. This is particularly useful for operational audits, troubleshooting, or real-time monitoring Available Substitution Codes Below is a list of commonly used substitution codes: Code Description %AlarmName% Name of the alarm %TimeStamp% Time the alarm was triggered %Value% Value of the monitored point at trigger %Priority% Alarm priority level %Source% Source object of the alarm For a complete list of supported codes: Alarms Substitution Codes

Issue Customer observed repeated logon/logoff events occurring within 1 second at 30-minute intervals for all Automation Servers. These events appear in the Event Viewer but do not impact system performance. Product Line EcoStruxure Building Operation Environment Building Operation Automation Servers Building Operation Device Administrator Building Operation WorkStation Cause When left open and connected to the server, the Device Administrator continuously polls the server status. This polling requires authentication, resulting in a logon followed by an immediate logoff. The behavior repeats at a fixed interval (approximately every 30 minutes) as part of the status check mechanism. Resolution Close Device Administrator when not actively in use. This will stop the periodic login attempts. If login events persist after closing Device Administrator, further investigation is required to identify other sources of admin logins.

Issue Is it possible to return an Engineering license from Device Administrator? Product Line EcoStruxture Building Operation Environment Device Administrator Cause Starting from version 7.0, EcoStruxure Building Operation introduced a Centralized Licensing Model. This model allows license management to be handled centrally via the Device Administrator, streamlining operations across BMS servers. Resolution Yes, Engineering Licenses can be returned using Device Administrator. Follow the steps below: Prerequisites Ensure the system is running EcoStruxure Building Operation version 7.0 or later. The Top Server must be added to Device Administrator. Steps to Return an Engineering License Open Device Administrator. Select the Top Server from the list. Locate the Engineering License you wish to return. Click Return. Choose either: Online Method – if the system is connected to the internet. Offline Method – if the system is not connected. Note: Only systems running version 7.0 and above support centralized licensing. Systems running versions prior to 7.0 use the legacy licensing model and are not compatible with this procedure.

Building Automation Knowledge Base

Improve your search experience:

Related Forums

Intelligent Devices Forum

Remote Alarm Manager – Including Date and Time in Alarm Messages

Remote Alarm Manager, GSM modem does not send text message.

Sigma - Repeating Index Entry

Totalising Alarms Using Programmable Points in BAS or Sigma

Text Alignment Issue on Sigma Start-Up Graphic

Sigma - Digital Output Interface module - Wiring connections.

Sigma - Editing objects on a remote Sigma client takes about 10 seconds.

Sigma - Daylight Saving Time (DST) Changeover Configuration

Password / Passcode for UNC532 or UNC632 Keyboard

Dataview and Dynaview

Known issues experienced when using Windows "Remote Desktop"

Temperature and Humidity offset on SLP room sensors

Why Does a Red Border Appear on the Binding Interface?

ETD200-6 - IP rating

Supported Import and Export File Formats in Graphics Editor

Validation Error When Renaming a New Enterprise Server

Substitution Codes for Write-to-File Notification Objects

Customizing Alarm Email Content Using Substitution Codes

Repeated logon/logoff events occurring for all Automation Servers

Centralized Licensing Model : Procedure for Returning an Engineering License

Ask our Experts

Email Us

Building Automation Knowledge Base

Related Forums

Ask our Experts

Email Us

Welcome!