Issue What happens to an alarm message when local time shifts due to daylight saving changes (e.g., clocks moving back or forward)? Product Line Satchwell BAS & Sigma, Satchwell MicroNet, TAC Vista Environment Remote Alarm Manager Cause This issue relates to how RAM handles time changes on the host PC. If an alarm is triggered before the time change and cleared after the system clock has shifted (e.g., moved back one hour), it may result in inconsistencies in how the alarm timestamps are displayed. Scenario Example An alarm is triggered at 15:46 local time. The system clock is manually adjusted back by one hour (e.g., due to daylight saving ending). The alarm is cleared at 14:52 (which is technically before the original alarm time). RAM logs show the alarm raised at 15:46 and cleared at 14:52. However, in the alarm properties, the cleared time may incorrectly display as 15:52, due to how the system reconciles time changes. Resolution Testing confirms that RAM handles this scenario without functional issues. Although timestamp discrepancies may appear temporarily in the alarm properties, the system normalizes once the time progresses past the original alarm time. This ensures accurate historical logging and alarm status.

Issue The network interface card (NIC) on a desktop or laptop shows no link LED activity, indicating no network connection. Product Line Andover Continuum, Satchwell BAS & Sigma, Satchwell MicroNet, TAC IA Series, TAC INET, TAC Vista Environment Windows Operating System Devices with built-in or external NICs (Network Interface Cards) Cause The NIC may have power management features enabled. These features can automatically disable the NIC under the following conditions: No network activity is detected Battery power is low Battery connection is intermittent This behavior is designed to conserve power but can result in the NIC appearing inactive or disconnected. Resolution To resolve this issue, disable the NIC's power management settings: Open Device Manager. Expand the Network Adapters section. Right-click your NIC and select Properties. Go to the Power Management tab. Uncheck the box that says “Allow the computer to turn off this device to save power.” Click OK to apply the changes. Additional Notes This issue is commonly observed on laptops running on battery power. Disabling power management may slightly reduce battery life but ensures consistent network connectivity.

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 After installing and launching Remote Alarm Manager 2.0 (RAM 2.0) for the first time, the application starts in Demo mode, providing only a 2-hour trial period. Product Line Satchwell BAS & Sigma, Satchwell MicroNet, TAC Vista Environment Remote Alarm Manager Cause This behavior is expected. RAM 2.0 enters Demo mode by default upon initial startup because it has not yet detected a valid license. Resolution To exit Demo mode and activate the full version of RAM 2.0: Create the Input Interface (e.g., Sigma R4). Once the interface is created, RAM 2.0 will: Detect the customer’s dongle or Read the engineer’s PC ID code (if applicable). Upon successful detection, the software will exit Demo mode and operate under the licensed configuration.

Issue This article provides guidance on integrating the Schneider Electric PM710 Power Meter with the following Xenta controllers using Modbus RTU: Xenta 511, 527, 555, 701, 711, 721 (Firmware version 5.1.5 and above) Xenta 731, 913 (All versions) Product Line TAC Vista Environment XBuilder Schneider Electric PM710 Power Meter Xenta 5xx / 7xx / 9xx series controllers Cause Integration is required when PM710 Power Meters are used in systems managed by Xenta controllers via Modbus RTU. To support this, Product Support has developed a device template to assist with configuration. This template is intended as a starting point and may require customization to meet specific project needs. It is not a comprehensive points list. Note: For assistance with template customization or troubleshooting, contact your local Schneider Electric Support team. Resolution To integrate the PM710 Power Meter with Xenta controllers using XBuilder, follow these steps: Download and Extract the Device Template Download the .zip file containing the .dev file from the link below. Extract the .dev file to a convenient location on your hard drive. Add the Device in XBuilder Open your XBuilder project. Right-click on the Modbus Master device. Select Add Device. Browse to the extracted .dev file and click Open. Configure the Device Rename the newly added device to ensure it has a unique name within the Modbus Master network. Adjust the device template as needed to match your specific integration requirements. Downloads Modbus Device Template – PM710 (.zip) PM710 User Manual (PDF)

Issue Understanding the meaning of various LED indicator lights on the front panel of Xenta Server controllers. Product Line TAC Vista Environment Xenta Server Controllers 511, 527, 555, 701, 711, 721, 731, 911, 913 Cause The LED indicators on Xenta Server controllers provide visual feedback about the device's operational status and communication activity. Interpreting these indicators correctly is essential for troubleshooting and system monitoring. Resolution The Xenta Server controller features multiple LED indicators that display the status of the device and its communication ports. Below is a detailed explanation of each LED and its meaning. LED Indicator Overview Position Indicator Description 1 Neuron Status Indicator - Off: Normal mode - Red, blinking: Unconfigured mode - Red, steady: Hardware fault 2 Serial RS-232 B Port - RX: Data is being received - TX: Data is being transmitted 3 Overall Run Indicator - Green, steady: Normal mode - Green, blinking: Start mode - Red, steady: Fail-safe mode - Red, blinking: Unit fault 4 Serial RS-232 A Port - RX: Data is being received - TX: Data is being transmitted 5 Serial RS-485 C Port - Activity Indicator: Shows communication activity 6 Ethernet 10Base-T Port - Activity Indicator: Shows Ethernet communication activity Note: The LEDs for the RS-232 A interface (Position 4) do not indicate communication when using the RS-485 A interface, even though both share the internal Port A. Diagrams Figure 1: LED Layout on Xenta Server Device Figure 2: Internal Serial Ports and RS-232/485 Interfaces

Issue When upgrading a TAC Vista site to EcoStruxure Building Operation (EBO), LonWorks devices may not be discovered during the device discovery process in the AS-P. Product Line EcoStruxure Building Operation Environment Building Operation Automation Server Premium (AS-P). Cause This issue typically occurs when the original TAC Vista database was configured using a third-party network management tool such as LonMaker or NL220. These tools can assign a custom domain ID to the LonWorks network. Default Domain ID in TAC Vista: 1/11 Default Domain ID in EBO: 1/254 If the domain ID used during the initial setup differs from EBO’s default, the AS-P will not detect devices on that domain. Resolution Identify the Current Domain ID Use the existing TAC Vista database to determine the domain ID configured on the LonWorks devices. Alternatively, use NodeUtil to identify the domain ID. Refer to the article: Finding LON devices under a different domain length with NodeUtil  Configure a Spare AS-P Set the domain ID on a spare AS-P to match the existing domain ID used in the site. For guidance, see: How to locate and change the LonWorks domain ID  Discover Devices Use the spare AS-P (now configured with the matching domain ID) to perform device discovery. The previously undetected devices should now appear and be accessible. Decommission Devices In the AS-P, navigate to the Actions menu for each discovered device. Select Decommission to revoke the device’s address and stop communication. Reintegrate Devices After decommissioning, re-add the devices to the LonWorks network. They should now be discoverable by an AS-P configured with the standard EBO domain ID (1/254).

Issue In Remote Alarm Manager (RAM) 2.0, the “Stop transmission of the Alarm Message” setting within an Action may be unintentionally lost when reviewing or modifying the configuration. This setting is part of the “What should be done when an alarm is acknowledged” menu. Product Line Satchwell BAS & Sigma, Satchwell MicroNet, TAC Vista Environment Remote Alarm Manager (RAM) 2.0 Cause The issue arises due to the way the Action configuration is navigated. Depending on the method used to review or edit the Action, the setting may be deselected without user awareness. Resolution There are two methods to modify an Action, each with different implications: Sequential Navigation (Using “Next” Button): Open the Action and proceed through each page using the Next button until reaching Finish. If you repeat this process, the “Stop transmission of the Alarm Message” option may become deselected, even if it was previously enabled. Direct Page Selection (Using Left-Side Navigation): Open the Action and directly select the desired page using the navigation boxes on the left. Important: If this method is used, always verify that the “Stop transmission of the Alarm Message” checkbox is ticked before clicking Finish. Best Practice Tip: When modifying Actions in RAM, always double-check the status of the “Stop transmission of the Alarm Message” setting before finalizing changes. This ensures alarm behavior remains consistent and avoids unintended message transmission.

Issue Windows displays an error indicating that Remote Alarm Manager (RAM) services do not start or stop in a timely manner. This may occur during system startup, shutdown, or when manually starting/stopping the service. Product Line Satchwell BAS & Sigma, TAC Vista Environment Remote Alarm Manager (RAM) Cause This issue is typically caused by a corrupted or misconfigured RAM configuration file ( setup.mdb ). Reinstalling RAM alone does not resolve the issue if the configuration file remains unchanged. Resolution To resolve this issue, follow these steps: Backup Configuration (if possible): Launch the RAM Console. Record or export the current RAM setup for reference. Uninstall RAM: Use the standard Windows uninstallation process to remove RAM from the system. Remove or Archive Configuration Files: Navigate to the Remote Alarm Manager installation directory. Locate the setup.mdb file and either: Delete it, or Move it to a backup location for safekeeping. Reinstall RAM: Download and install the latest version of RAM (2.1.025 or newer if available). Reconfigure RAM: Use the previously recorded setup to reconfigure the system. Ensure all settings are correctly applied and saved. Additional Notes This issue may also present as the service being stuck in a “Starting” or “Stopping” state in the Windows Services console. Always ensure you have a backup of your configuration before making changes.

Issue The Remote Alarm Manager (RAM) system does not behave as expected when processing “Off Duty” and “On Duty” messages from a reciprocator’s mobile device. Product Line Satchwell BAS & Sigma, Satchwell MicroNet, TAC Vista Environment Remote Alarm Manager (RAM) 1.2 and 2.0 Cause When a reciprocator sends an “Off Duty” message via mobile to the RAM interface, a duty exception is correctly created and displayed on the RAM console. However, when the same reciprocator sends an “On Duty” message, the system fails to cancel the previously created duty exception. This results in inaccurate duty status representation within the RAM system. Resolution A workaround is available to ensure proper handling of duty status changes: To allow users to remotely issue “On Duty” or “Off Duty” commands effectively: Navigate to the User Access Page in the RAM interface. Locate the user account in question. Set the user’s Local Access Level to ‘Privileged User’ or higher. This access level ensures that the system correctly processes both “On Duty” and “Off Duty” messages from the user’s mobile device. Note: This workaround must be applied individually to each user requiring remote duty status control.

Issue Startup programs can slow down system boot time and cause application conflicts if loaded in the wrong order. Product Line Andover Continuum, EcoStruxure Building Expert, EcoStruxure Building Operation, Satchwell BAS & Sigma, Satchwell MicroNet, TAC IA Series, TAC INET, TAC Vista Environment Windows XP, Vista, 7, 8, 8.1, 10, 11 Cause Applications configured to launch at startup may: Increase boot time Cause system instability or delays Load in an incorrect sequence, affecting performance Resolution Windows XP, Vista, 7 Click Start → Run Type msconfig and press Enter Go to the Startup tab Uncheck items you want to disable Click Apply → OK Restart your computer 🔹 Windows 8, 8.1, 10, 11 Press Ctrl + Shift + Esc to open Task Manager Click the Startup tab Right-click any item and choose Disable Restart your computer for changes to take effect 💡 Tip: Only disable items you recognize. Disabling essential services may affect system functionality. Additional Notes Disabling startup items is useful for troubleshooting slow boot times or software conflicts. For persistent issues, consider using tools like Autoruns from Microsoft Sysinternals for deeper analysis.

Issue A licensing error appears in the RAM log when Sigma is installed. Dongle failure 30 day limited mode entered Product Line Satchwell BAS & Sigma Environment Sigma Remote Alarm Manager (RAM) Cause The error occurs due to incorrect licensing configuration in Sigma. RAM licensing relies on the Sigma dongle, and the appropriate license scheme must be selected during setup. Resolution To resolve the licensing error: Open the Remote Alarm Manager Computer Configuration Wizard. Navigate to: Start > Licence Scheme Ensure the checkbox for Legacy Licence Schemes is selected. This enables compatibility with the Sigma dongle-based licensing system.

Issue The SMS Nokia mobile phone simulator does not function in RAM 2.0 / 2.1 and Windows 7. Product Line Satchwell BAS & Sigma, Satchwell MicroNet, TAC Vista Environment Windows 7 Remote Alarm Manager (RAM) Cause When using RAM 2.0 or 2.1 on Windows 7, the SMS test interface fails to display the Nokia dummy phone on the desktop after sending a test SMS. This is due to the Interactive Services Detection service being disabled by default in Windows 7, which prevents interactive elements from appearing on the desktop. Resolution To enable the SMS Nokia mobile phone simulator to function correctly: Enable Interactive Services Detection: Press Windows + R , type services.msc , and press Enter. In the Services window, scroll down to Interactive Services Detection. Set the Startup type to either Manual or Automatic. Click Start to run the service. Send a Test SMS: In RAM, send a test SMS message to the dummy Nokia phone. An icon will appear in the Windows taskbar indicating a message is available. Click on “View the message” to open the dummy SMS phone interface. The message should now be visible on the simulated phone. Additional Notes This issue is specific to Windows 7 due to changes in how interactive services are handled. This workaround may not be applicable to newer versions of Windows where Interactive Services Detection is deprecated or removed.

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 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 How is a subnet defined, and what role does it play in IP networking? Product Line EcoStruxure Access Expert, EcoStruxure Building Operation, EcoStruxure Security Expert, TAC I/NET Environment This explanation is based on principles outlined in TCP/IP Network Administration by Craig Hunt, published by O’Reilly & Associates, Inc Cause Subnetting is a method used to divide a larger IP network into smaller, more manageable segments called subnets. This segmentation helps optimize IP address usage, improve routing efficiency, and enhance network security and organization. Resolution What Is a Subnet? A subnet (short for subnetwork) is a logical subdivision of an IP network. It is defined by applying a subnet mask to an IP address, which determines how the address is split into: Network portion – identifies the specific network. Host portion – identifies individual devices (hosts) within that network. How Subnet Masks Work A subnet mask is a 32-bit binary pattern that accompanies an IP address. It uses binary values to indicate which part of the IP address refers to the network and which part refers to the host: A bit set to 1 in the subnet mask means the corresponding bit in the IP address is part of the network. A bit set to 0 means the corresponding bit is part of the host. Example IP Address: 192.168.1.10 Subnet Mask: 255.255.255.0 (binary: 11111111.11111111.11111111.00000000 ) CIDR Notation: /24 This means: Network Address: 192.168.1.0 Broadcast Address: 192.168.1.255 Usable Host Range: 192.168.1.1 to 192.168.1.254 CIDR Notation Modern networks often use CIDR (Classless Inter-Domain Routing) notation to define subnets. CIDR expresses the subnet mask as a suffix (e.g., /24 ), indicating the number of bits used for the network portion. Common CIDR Blocks CIDR  Subnet Mask Hosts per Subnet /30 255.255.255.252 2 usable hosts /24 255.255.255.0 254 usable hosts /16 255.255.0.0 65,534 usable hosts Additional Notes Subnets are local constructs: They are meaningful within the internal network and typically not visible to external networks unless explicitly routed. Subnetting supports hierarchical addressing, which simplifies routing tables and improves scalability. Proper subnetting is essential for network performance, security segmentation, and efficient IP address management.

Issue Where can I obtain the technical information, manuals, guides or other documents on Continuum? (or other product lines) Product Line Andover Continuum, EcoStruxure Building Operation, Satchwell Sigma, TAC Vista Environment Continuum Cause Manuals and documentation can be used for training or self-help troubleshooting for Continuum. (or other product lines) Resolution Review the course notes The notes and document gathered during training can be very useful and a great source of information. Technical Documentation is available on the EcoBuilding Download site at: https://www.se.com/myschneider/content/ww/en/gc/general/ecoxpert-landing-page.jsp For technical data/PDFs installed with Continuum, Go to Start > All Programs > Continuum > Documentation The discs and downloaded zip files that are used to install Continuum also include technical PDFs. Some of these are installed when Continuum is installed. (CONTINUUM) Most of the online help is context based, thus if you click help within a InfinityNumeric, then InfinityNumeric help is given. This help file can also be searched in the normal way. It is an excellent source of information. (CONTINUUM) Bookmark this Knowledge Base:  https://community.se.com/t5/Knowledge-Base/tkb-p/knowledge-base_public New articles are added daily and should be used as a first stop for self help. The Exchange Community site has a community space just for Continuum, SmartStuxure, Sigma, Vista etc.  for posing questions, sharing solutions, https://community.se.com/ (CONTINUUM) The Continuum catalogue also provides a good overview of the product range Some documentation is freely accessible, see https://www.schneider-electric.com/en/work/products/building-automation-and-control.jsp If an end user has problems on site, they should first contact Schneider Electric local support or service department (In the UK contact Support Bureau 0870 606 2800, cs.bureau@uk.schneider-electric.com) SmartStruxure For Building Operation help can be found online at: http://help.sbo.schneider-electric.com/home/index.castle?locale=en-US&productversion=1.8   CONTINUUM ONLY Always ensure the site fits within the Continuum Compatibility Matrix, this includes:  For PC requirements see the relevant Installation Instructions included with the Continuum Software Controller firmware (Continuum, BACnet, Infinet), use the most up to date available (of the correct version) Workstation operating systems, service packs and .NET framework versions SQL versions See Software and Firmware compatibility matrix for older versions of I/NET, Vista, Andover Continuum, Satchwell Sigma, I/A Series, and StruxureWare Building Operation for other system data The Continuum.chm file found in the Continuum directory include the "online help" It is usually worth ensuring the latest Continuum service pack is applied to ALL workstations on site (Cyberstation and WebClient) Click Here