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 Dates displayed in the Sigma ODBC database do not match the expected format based on the system’s regional settings. This discrepancy can lead to confusion or misinterpretation of logged data. Product Line Satchwell BAS & Sigma Environment Sigma ODBC Cause Although the Sigma logging interface correctly reflects the desired date format, the ODBC database shows dates in an incorrect format. This issue arises because one critical setting in the Windows regional configuration was not applied universally. Resolution To ensure consistent date formatting across all users and system components: Open Regional Settings on the Windows Server. Navigate to the Administrative tab. Click “Copy settings…”. In the dialog box, ensure “Welcome screen and system accounts” and “New user accounts” are both checked. Confirm that the correct regional and language format is selected. Apply and restart the system if necessary. This step ensures that the regional settings are propagated to all system accounts and new users, resolving the date format inconsistency in the ODBC database.

Issue There is a need to compare two temperature readings taken at different times—for example, at 10:00 AM and 4:00 PM. The goal is to determine whether the temperature has increased or decreased over that period. If the 4:00 PM temperature is higher, the output should be TRUE; if lower, FALSE. Product Line Satchwell BAS & Sigma Environment Satchwell Sigma Cause Users require guidance on how to implement a programmable object that performs this time-based temperature comparison. Resolution The following Sigma programmable object logic fulfills the requirement: 10 IF TIME = 10:00 THEN XINT = 1 20 IF TIME = 16:00 THEN XINT = 2 30 IF XINT UP THEN GOTO 50 40 GOTO 100 50 IF XINT = 1 THEN XFLO = POINT 1 60 IF XINT = 2 THEN YFLO = POINT 2 70 IF XINT <> 2 THEN GOTO 90 80 IF XFO > FLO THEN YINT = 1 ELSE YINT = 0 90 XINT = 0 100 IF YINT = 1 THEN RETURN TRUE "Higher" ELSE RETURN FALSE "Lower" Explanation of Logic Lines 10–20: Set a flag ( XINT ) based on the current time. Line 30: Checks if the time flag has incremented. Lines 50–60: Store the temperature readings at the respective times. Line 70: Ensures comparison only occurs after both readings are captured. Line 80: Compares the two temperatures and sets the result flag ( YINT ). Line 100: Returns the final result: TRUE if the temperature increased, FALSE if it decreased.

Issue Users need to access related documents directly from a Sigma graphic or object within the Sigma system. Product Line Satchwell BAS & Sigma Environment Satchwell Sigma Cause The site requires quick access to documentation associated with specific Sigma objects or graphics for operational or troubleshooting purposes. Resolution To enable document access from a Sigma graphic or object using Pop-up Menus and Commands, follow these steps: 1. Configure Pop-up Command in Sigma System Manager Open Sigma System Manager (SSM). Navigate to: System Setup → General → Pop-up Menus Commands. Click New to create a new command. Assign an appropriate Name to the command (e.g., View Controller Info). Highlight System Information and configure the command as follows: Command Line: C:\Sigma\Data\System Information\Controller {Unc No}.txt Note: Replace {Unc No} by highlighting the Controller number format field and selecting "Select". Ensure the folder C:\Sigma\Data\System Information\ exists. Place the relevant text files in this folder. File names must follow the format: Controller xxx.txt where xxx is the correct controller number. Tip: While the configuration example below opens the file in Windows Notepad, you can configure it to open with other programs if needed. 2. Create a New Pop-up Menu In SSM, go to Pop-up Menus and click New. Assign a suitable Menu ID and Name. Add the previously created command to this menu. 3. Assign the Pop-up Menu to a Sigma Object or Graphic Select the desired Object or Graphic Reference. Set the Menu ID to the one created in the previous step. Testing the Configuration Right-click on the Sigma object. Select the newly created menu. The associated document (e.g., Controller 001.txt ) should open in Notepad or the configured application.

Issue When upgrading Sigma, improperly handled Longtext messages can cause the Sigma server to shut down unexpectedly. Product Line Satchwell BAS & Sigma Environment Satchwell Sigma Cause During the upgrade process, new Longtext messages were added correctly. However, existing messages from the previous version were copied over without being properly upgraded. This mismatch in message formatting or structure leads to instability, causing the Sigma server to stop periodically. Resolution To prevent this issue during an upgrade from a version earlier than 4.05: Verify the Longtext folder exists in the Sigma Data directory. Run the Sigma upgrade program to ensure all Longtext messages—both new and existing—are correctly upgraded. ⚠️ Important: Do not manually copy old Longtext messages into the upgraded system without proper conversion.

Issue How to correctly program the scan rate object for UNC696/796 controllers. Product Line Satchwell BAS & Sigma Environment Sigma UNCX96 controllers Cause The scan rate object in UNC696/796 controllers requires specific configuration to function correctly. Users may be unsure how to set this up within the Sigma system. Resolution To program the scan rate object for UNC696/796 controllers, follow these steps: Object Allocation The scan rate object is assigned to Object Number 252. Create a New Analogue Input (AI) Object Navigate to a suitable location within the index structure of the controller. Create a new AI object using Object Number 252. Configure the Lookup Table Set the Lookup Table to 2000. Assign a Short Text Description Choose an appropriate short text label. If none exists, create a new one, such as: Scan %1.0f SPM (This format displays the scan rate in Scans Per Minute.) Download the Object Save and download the newly created object to the controller. Wait approximately 1 minute and then verify the scan rate value.

Issue A utility is being used to record Sigma log data and store it in the cloud. There is a requirement for log timestamps to occur every 15 minutes, precisely synchronized to the hour (e.g., 00:00, 00:15, 00:30, 00:45). Product Line Satchwell BAS & Sigma Environment Satchwell Sigma Cause Sigma does not provide a native mechanism to define the exact start time for a log set. When configured to log at timed intervals, the log bucket file is downloaded to the controller and begins processing from that moment—resulting in unsynchronized timestamps. Resolution An engineering workaround can be implemented to achieve synchronized 15-minute logging. This involves using a program point for each value that needs to be logged. Sample Program Code 10 XFlo = POINT 0|41 ; Object to be logged 20 IF MINUTE = 0 OR MINUTE = 15 OR MINUTE = 30 OR MINUTE = 45 THEN GOTO 40 30 RETURN VIA TEXT 92 VALUE YFlo 40 IF SECOND DOWN THEN GOTO 60 50 RETURN VIA TEXT 92 VALUE YFlo 60 YFlo = XFlo 70 RETURN VIA TEXT 92 VALUE YFlo Instructions Replace POINT 0|41 with the actual object reference you wish to log. Configure the log set to use "Change of Value" as the logging trigger. Ensure each required value has its own program point using the logic above. Additional Notes This method ensures that values are captured exactly at 15-minute intervals aligned with the hour. It is particularly useful when integrating with external systems or cloud-based analytics that rely on consistent timestamping.

Issue What is the maximum number of global objects that can be received by a Sigma controller or Integration Controller (IC)? Product Line Satchwell BAS & Sigma Environment Sigma UNCX96 controllers Sigma UNCX32 controllers Sigma Integration controllers - All types Cause This limitation is due to configuration and engineering constraints within the Sigma system architecture. Resolution Maximum Received Globals: Each Sigma controller or IC can receive up to 50 global objects. Transmitted Globals: There is no fixed limit on the number of global objects a controller or IC can transmit. However, when designing and engineering a Sigma system, it is essential to consider: Controller communication load System performance impact Network traffic and latency Proper planning and testing are recommended to ensure optimal system performance when transmitting a large number of global objects. Additional Notes This limitation applies only to received global objects. Engineering best practices suggest minimizing unnecessary global object usage to reduce controller load and improve system reliability.

Issue What are the data types of the newly introduced fields “Alarm Type” and “Secondary Value” in Sigma ODBC Release 4.06? Product Line Satchwell BAS & Sigma Environment Sigma ODBC Cause The data types for the new fields were not documented in the initial release notes, leading to uncertainty during database configuration. Resolution Both “Alarm Type” and “Secondary Value” fields are of Text data type. These fields appear in the Sigma ODBC editor and must be manually selected for inclusion in the ODBC database. Refer to the screenshot below for visual confirmation of the new entries. 📌 Note: Ensure these fields are mapped correctly when configuring your ODBC connection to avoid data retrieval issues.

Issue When attempting to start a program, an error message appears indicating that communications port 1 (Comm 1) is already open. Product Line Satchwell BAS & Sigma, Satchwell MicroNet Environment Satchwell BAS 2800+ Satchwell Sigma Satchwell Visisat Cause The error occurs because Comm 1 is already in use by another application. A common culprit is Microsoft ActiveSync, which may reserve the port even if not actively used. Resolution Step 1: Check for Microsoft ActiveSync Open the ActiveSync connection settings window. Either: Change the Serial port number, or De-select the Serial port to release Comm 1. 💡 If ActiveSync is no longer required, consider disabling or uninstalling it to prevent future conflicts. Step 2: Check BIOS Settings If ActiveSync is not the issue: Restart the system and press F2 during startup to enter the System BIOS. Review the settings for communications port 1. Ensure it is enabled and not reserved by the system unnecessarily. ⚠️ Disabling Comm 1 in BIOS may also trigger the error. Re-enable it if needed.

Issue After a prolonged period of computer inactivity, alarms are no longer routed to the Sigma Server. However, once a user interacts with any point in the Sigma System Manager, alarm routing resumes. Product Line Satchwell BAS & Sigma Environment Satchwell Sigma Cause This issue is caused by the Power Management settings of the Network Interface Card (NIC) on the Sigma Server. Specifically, the setting “Allow the computer to turn off this device to save power” is enabled, which can disable the NIC during periods of inactivity, interrupting alarm routing. Resolution To prevent the NIC from being powered down during inactivity, follow these steps: Open Network Connections: Navigate to Control Panel → Network Connections. Locate the Local Area Connection used by the Sigma Server. Access Network Adapter Settings: Right-click the connection and select Properties. Under the General tab, locate the “Connect using” section. Click the “Configure” button next to the network adapter name. Modify Power Management Settings: In the Properties window, go to the Power Management tab. Uncheck the box labeled “Allow the computer to turn off this device to save power.” Click OK to apply the changes. Restart the Sigma Server (if necessary) to ensure the new settings take effect.

Issue When attempting to register a Sigma CE device, the 16-digit unlock code is not accepted. Product Line Satchwell BAS & Sigma Environment Sigma CE Sigma PE Cause The unlock code is not recognized due to incorrect formatting during input. Specifically, the required spaces between each set of four characters in the 16-digit code are often omitted. Resolution When entering the unlock code, ensure that it is formatted correctly with spaces between every four characters. ✅ Correct Format Example: B6E8 1234 0789 7AB4 ❌ Incorrect Format Example: B6E8123407897AB4 Failure to include spaces will result in the unlock code being rejected.

Issue Reading registers from an ATV600 via Modbus TCP in EcoStruxure Building Operation (EBO) Product Line EcoStruxure Building Operation Environment Building Operation Enterprise Server Building Operation Automation Server Modbus Cause Users may need to access and monitor data from an ATV600 drive using Modbus TCP but require guidance on configuration steps and tools. Resolution Step 1: Download Required Tools SoMove: Software for configuring ATV600 Download SoMove DTM Library for ATV600: Install the correct model Download ATV6xx DTM Library Step 2: Configure Password The default password for ATV600 is in the manual. Change the password via the device menu 8.7 or through a web browser. How do I access the embedded web page on an ATV630 drive? | Schneider Electric USA Step 3: Log In and Configure IO Mapping Use the DTM tool to log in to the device. Navigate to IO Mapping. Add the register table according to your requirements. Step 4: Configure Workstation Protocol: Modbus TCP Device ID: 255 (for logical register mapping). Create points in Workstation and enter CHANNEL information based on the IO mapping list. Example: In DTM: CHANNEL 1 corresponds to register number 3203. In Workstation: Enter 1 to access the logical register map. ✅ Tip: Always verify that register addresses in Workstation match the IO mapping in ATV600.

Issue Clarification needed on the correct configuration of jumpers for the Analogue Input (AI) card. Product Line Satchwell BAS & Sigma Environment Sigma Analogue Input (AI) Cards Cause Users may be unsure how to correctly configure jumpers on the AI card to support different input types. Resolution The jumper configuration on the Sigma Analogue Input card supports three types of inputs: Resistance Voltage Current Each input type requires a specific jumper setting. Refer to the screenshot below for visual guidance on jumper positions. Tip: Ensure the jumper settings match the sensor type connected to the input channel to avoid incorrect readings.

Issue When the Remote Alarm Manager (RAM) sends an SMS message via GSM modem to a mobile phone, the message is truncated—the end portion of the message is missing. Product Line Satchwell BAS & Sigma, Satchwell MicroNet Environment Remote Alarm Manager Cause The issue occurs due to the length of the message being sent. SMS messages have a character limit of 160 characters. If the message exceeds this limit, it may be truncated or not delivered in full, depending on the mobile carrier and device. This is especially common when: The message type is set to Long Message (multi-line descriptive format). The Index Title or Point Title used in the message is excessively long. Resolution To prevent message truncation, consider the following actions: Use Shorter Message Types: Change the message type from Long Message to Normal or Short Message. Shorten Titles: Abbreviate long Index or Point Titles. Example: Change "Temperatures" to "Temps" . Review Message Content: Ensure the total message length does not exceed 160 characters.

Issue You need to generate a list of input/output (I/O) points for each device in a TAC Vista system for documentation, troubleshooting, or commissioning purposes. Product Line TAC Vista Environment TAC Vista Menta Vista Workstation Cause There is no direct built-in report in TAC Vista that provides a consolidated list of I/O points per device in a printable format. Resolution To print out a list of I/O for each device in TAC Vista, follow these steps: Ensure the Vista Server is running. 🛠️ Note: These steps must be performed on the computer where the Vista Server is installed and running. Open the System Documentation tool: Navigate to the Start Menu → TAC Tools → System Documentation. Create a new I/O list: In the System Documentation tool, go to the File menu. Select New List → Inputs/Outputs. Select the device: In the Input/Output dialog box, click Browse. The Object Selection dialog box will appear. Filter and choose the device: At the bottom of the Object Selection window, change the Object Type to TAC Xenta Devices (or another applicable type). In the Units field, navigate through the Vista Server object tree to locate and select the desired device. Click OK to confirm your selection. Generate the list: Click OK again in the Input/Output dialog box to generate the I/O list for the selected device. You can now view, save, or print the generated list for documentation or analysis purposes.

Issue What is the difference between XIF and NXE files in LON controllers? Product Line TAC Vista, TAC I/A Environment LNS LON Controllers NL220 LonMaker Cause Users working with LON devices may encounter both XIF and NXE files and be unsure of their respective roles and how to use them effectively. Resolution XIF File (External Interface File) Format: Text-based Purpose: Describes the network interface of a LON device Contents: Device type Network variables (NVs) Configuration properties (CPs) Functional blocks Usage: Used by network management tools during device integration Created by: Device manufacturer or LON development tools Editable: Yes (with caution) Use Case: Used during integration to map and understand the device’s capabilities. NXE File (Neuron Executable File) Format: Binary Purpose: Contains the firmware and application logic for a LON device Usage: Used to download or update the device’s application Created by: Development tools like NodeBuilder or LonBuilder Editable: No (compiled code) Use Case: Used when deploying or updating the logic on a LON controller. Comparison Table Feature XIF File NXE File Format Text-based Binary Purpose Describes device interface Contains executable application Usage Integration and configuration Firmware/application deployment Editable Yes (with caution) No (compiled code) Created By Manufacturer or tools NodeBuilder, LonBuilder Best Practices Ensure the XIF file version matches the corresponding NXE file to avoid integration issues. Avoid manual editing of XIF files unless necessary and fully understood. Maintain version control for both file types to ensure traceability and consistency.

Issue Users are unable to access Webstation due to the system reaching its maximum number of concurrent user sessions. Product Line TAC Vista Environment TAC Vista Webstation Cause Webstation enforces a limit on the number of simultaneous user sessions based on the license configuration. When this threshold is reached, additional login attempts are blocked. License Types and Limits License Type Description 0-008-8270-1 Vista 5.1 Webstation 1 CAL – One concurrent user 0-008-8271-1 Vista 5.1 Webstation 3 CAL – Three concurrent users 0-008-8272-1 Vista 5.1 Webstation 6 CAL – Six concurrent users 0-008-8273-1 Vista 5.1 Webstation 12 CAL – Twelve concurrent users 0-008-8274-1 Vista 5.1 Webstation Unlimited – Unlimited users Additional Considerations Operating System & IIS Limits: These may impose additional restrictions not directly related to Webstation licensing. Windows XP: Limited to 10 connections due to TCPIP.SYS, resulting in error 403.9 – Access Forbidden: Too many users. Windows 7 (SP2): Connections beyond the limit are queued, causing delays but no error messages. Windows Server Editions: No connection limits – recommended for hosting Webstation. Note: Each Webstation session uses 1 connection. Each open TGML page also uses 1 connection. For example, 1 Webstation + 5 TGML pages = 6 connections. Resolution Recommended OS Configurations OS Version IIS Version Connection Limit Notes Windows Server 2008 R2 IIS 7.5 No Limits Recommended Windows 7 (Ultimate/Enterprise/Business) IIS 7.5 10 Allows multiple sites Windows Vista (Ultimate/Enterprise/Business) IIS 7.0 10 Allows multiple sites Windows XP Professional IIS 5.1 10 Only one site Windows 2000 Professional IIS 5.0 10 Only one site Windows NT 4 Workstation IIS 4.0 No IIS PWS installs via NT Option Pack Best Practices Use Windows Server OS for production environments to avoid connection limits. Monitor TGML usage to optimize connection consumption. Consider upgrading license if user demand exceeds current CAL limits.

Issue How to add a new system alarm filter in the Sigma Alarm Manager? Product Line Satchwell BAS & Sigma Environment Satchwell Sigma Cause Users may need to create custom alarm filters to better manage and monitor specific alarm types or system events within the Sigma Alarm Manager. Resolution To add a new system alarm filter in the Sigma Alarm Manager, follow these steps: Open Sigma Alarm Manager. Navigate to the Configure menu. Select System Filters. → The list of existing standard filters will be displayed. Click Add to create a new filter. Name the new filter appropriately. Highlight the newly created filter and click Edit. Configure the filter settings as required for your system needs. From the Configuration menu, select Controls. Enable the new filter by checking the appropriate box. Restart the Sigma client to apply and view the changes in the Alarm Manager.

Issue Analogue input (AI) channels are not displaying the correct values. Product Line Satchwell BAS & Sigma Environment Sigma Analogue Input Cause The issue is observed across multiple analogue input channels, cards, and controllers. This widespread behavior suggests the root cause is likely external to the individual AI objects or hardware components. Resolution Follow the steps below to isolate and resolve the issue: Scenario 1: Issue Occurs on a Single Controller Isolate Inputs: Disconnect all inputs to the AI card except one. Use a known resistive input for testing. Test Input Stability: Replace the connected analogue input with a fixed resistor. Observe the reading—if it stabilizes, investigate the other inputs for faults. Verify Voltage Reading: Change the object lookup table entry to 2000 . Measure the voltage across the resistor. Compare the measured voltage with the maximum input voltage (2V). Example: If measured voltage = 1.5V Calculation: 1.52.0=0.75×100=75\frac{1.5}{2.0} = 0.75 \times 100 = 752.01.5=0.75×100=75 The AI object should display 75. Check Earthing: Ensure the controller’s earth bar is properly connected to a good earth. Hardware Checks: If the issue persists, consider replacing the AI card. If unresolved, consider replacing the CPU card. Scenario 2: Issue Occurs on Multiple AI Cards in One Controller Repeat Isolation Steps: Disconnect all AI inputs on all cards. Connect only one resistive input to a single card and observe behavior. Repeat Steps 3–5 from Scenario 1. Scenario 3: Issue Occurs Across Multiple Controllers Check Earthing: Confirm all controller earth bars are securely connected to a good earth. Inspect Power Supply Boards: Older power supply boards (especially in BAS-to-Sigma upgrades) may cause various issues. Overheating of voltage regulator ICs due to loose securing bolts can lead to ‘current limit’ mode. Action: Retighten bolts securing the regulator tabs and TO3-type regulators. Allow the heatsink to cool down.

Issue Can Sigma devices be connected to an Ethernet Cat7 network? Product Line Satchwell BAS & Sigma Environment Satchwell Sigma Cause There is uncertainty regarding the compatibility of Sigma devices with newer Ethernet cabling standards, particularly Cat7. Resolution Yes, Sigma devices can be connected to a Cat7 Ethernet network, provided that the network switches support 100 Mbps (100Base-T) communication. Sigma devices typically operate at 100 Mbps, which is well within the capabilities of Cat5e, Cat6, and Cat7 cabling. The key factor is not the cable category itself, but whether the network infrastructure (especially switches) supports the required communication speed. Cable Category Overview Cable Type Frequency Max Speed Shielding Notes Cat5/5e 100 MHz Up to 100 Mbps Unshielded Common in older installations Cat6 250 MHz Up to 1 Gbps Improved insulation Suitable for Gigabit Ethernet; max 55m for 10 Gbps Cat7 1000 MHz Up to 10 Gbps Shielded (per pair and overall) Enhanced protection from interference and crosstalk Key Considerations Ensure network switches are configured to support 100 Mbps communication. Cat7 cables offer superior shielding and higher frequency handling, but do not inherently improve Sigma device performance beyond their 100 Mbps capability. Using Cat7 may be beneficial in environments with high electromagnetic interference (EMI), but it is not a requirement for Sigma devices.

Building Automation Knowledge Base

Improve your search experience:

Related Forums

Intelligent Devices Forum

Sigma – Dates in the ODBC Database Display Incorrectly for Regional Settings

Sigma – Creating a Programmable Object to Compare Temperatures at Two Different Times

Sigma - How to Open a Document from a Sigma Graphic or Object

Sigma Server Shutdown Due to Improper Longtext Message Upgrade

Sigma - UNC696/796 Scan Rate Objects

Sigma Log Data Recording Every 15 Minutes Synchronized to the Hour

Maximum Number of Global Objects in Sigma Controllers and Integration Controllers (ICs)

Sigma ODBC – Data Types for “Alarm Type” and “Secondary Value” Fields

Programmes using communications port 1 are unable to access this port.

Alarms Stop Being Routed to the Sigma Server After Extended Computer Inactivity

Unlock Code Not Accepted When Registering Sigma CE Device

Modbus TCP Integration with ATV600

Sigma – New Style Analogue Input Configuration Jumpers

RAM - SMS Messages Are Truncated

How to print out a list of I/O for each device.

Understanding the Difference Between XIF and NXE Files in LON Controllers

Managing Concurrent User Limits in Vista Webstation

Sigma – Adding a New System Alarm Filter into the Alarm Manager

Sigma – Analogue Input Channels Display Incorrect Values

Can Sigma Devices Be Connected to a Cat7 Ethernet Network?

Ask our Experts

Email Us

Building Automation Knowledge Base

Related Forums

Ask our Experts

Email Us

Welcome!