Issue Clarification is required on whether BACnet/IP communication for MP-C, AS-P, and EcoStruxure Building Operation can use TCP instead of UDP, and which devices must be whitelisted in firewall configurations. There may also be uncertainty regarding BACnet/SC support and communication paths for BACnet/IP Controllers, such as the MP-C, RP-C range of devices, and third-party devices. Product Line EcoStruxure Building Operation Environment EcoStruxure Building Operation (EBO) 3.2 or later Automation Servers BACnet/IP, BACnet/SC, BACnet MS/TP SpaceLogic MP‑C / MP‑C Pro / MP‑V SpaceLogic RP‑C / RP‑C Pro / RP‑V Cause BACnet/IP communication runs over UDP and does not support TCP. BACnet/SC is a separate communication method that uses TCP-based secure connections. Additionally, standard EcoStruxure Building Operation communication routes MP-C traffic through the AS-P rather than directly to the Enterprise Server. Resolution BACnet/IP must remain UDP-based and cannot be changed to operate over TCP. If TCP-based communication is required, BACnet/SC must be used as it provides TLS-encrypted WebSocket communication over TCP and requires certificate-based trust between devices. For firewall configuration: For BACnet/SC: All devices that need to communicate with the BACnet/SC hub must be allowed through the firewall, as communication uses a hub-and-spoke architecture with outbound connections to the hub. For standard EcoStruxure Building Operation communication (non-BACnet/SC), MP-C devices communicate via the AS-P, so only the AS-P needs to be whitelisted on the Enterprise Server firewall. If a third-party device does not support BACnet/SC, it cannot participate in BACnet/SC communication.   Other considerations:  Before recommending firewall rules or BACnet/SC adoption, ensure the customer's complete network and security requirements are understood. Requests for "whitelisting" or replacing UDP with TCP can sometimes indicate a broader network segmentation or security requirement rather than a BACnet protocol limitation. Consider gathering additional information regarding: The overall system architecture and communication paths. The specific security or compliance requirement driving the request. Whether network segmentation, isolation, or traffic restriction is the primary objective. Alternative approaches that may satisfy the requirement include: Network switch-based access controls, such as MAC address filtering, port security, or other switch-level whitelisting mechanisms. VLAN segmentation to isolate BACnet/IP networks, including secondary or site-specific BACnet networks. Deploying edge servers with multiple network interfaces, where a secondary BACnet network can be connected through a dedicated interface or VLAN. Isolating the Building Management System (BMS) / Operational Technology (OT) network within the network infrastructure rather than relying solely on host-based firewall restrictions. Understanding the customer's full architectural requirements helps ensure the most appropriate network design is recommended rather than focusing only on protocol-level configuration options.

Issue An Operator Display connected to an AS-P or AS-B is not discovered in EcoStruxure Building Operation and cannot be added to the system. Product Line EcoStruxure Building Operation Environment Building Operation Automation Server (AS-B, AS-P) SpaceLogic Operator Display (HMIST6400SL) Cause Adding an Operator Display to AS-B or AS-P Resolution Connect to the AS-B or AS-P with EBO Device Administrator version 3.0.1 or later. In the AS-B/AS-P configuration, navigate to Ethernet 2 Configuration and configure: Ethernet 2 Mode: Dual IP DHCP Mode: Server Verify that the default IP address for Ethernet 2 is 10.110.210.1.   Apply and save the configuration changes. Connect the Operator Display to Ethernet Port 2 on the AS-B or AS-P. Verify that the Operator Display establishes communication with the server by confirming that the three red Offline indicators at the top of the display are no longer shown. Connect an Building Operation WorkStation to the AS-B or AS-P. Create a BACnet Interface. Create a second IP Network beneath the BACnet Interface. Select the server in the System Tree and open the Device Discovery tab. Device Discovery and locate the Operator Display in the discovered devices list. Drag and drop the Operator Display onto the second IP Network. Validation The Operator Display appears in Device Discovery. The Operator Display can be added to the second IP Network. The display is online and communicating with the AS-B or AS-P.

Issue Additional troubleshooting information is required for issues involving Mercury controllers in Access Expert. Product Line EcoStruxure Access Expert Environment Mercury controllers LP Series controllers Cause Controller issues require additional diagnostic information for troubleshooting and analysis. Resolution 1. Use Live Monitoring Use Live Monitoring while the issue is occurring to identify any error messages being generated.   2. Collect SEQ Logs SEQ logs provide more detailed error information than Live Monitoring. Install and collect SEQ logs for additional diagnostics.   3. Configure Controller Diagnostics with Acre Schedule a troubleshooting session with Schneider Electric Product Support, who will coordinate a phone call and remote session with Acre/Feenics support. During this session, the controller will be pointed to their debugging server. This allows diagnostic logs to be collected and provided to HID/Mercury for further analysis. This step is typically only required after Live Monitoring and SEQ log collection have been completed and is rarely used.   4. Collect a Syslog from the Controller For LP Series controllers, use the Syslog button on the Diagnostic page of the controller web interface. The downloaded syslog is an encrypted system log used by HID/Mercury support for advanced troubleshooting. The file must be provided to HID/Mercury support for analysis. The syslog is erased each time the controller reboots and therefore does not contain historical information from before the last reboot. Syslog files have the .aes file extension. This method should only be used when requested by HID/Mercury support and is very rarely required.

Issue Downstream interfaces/controllers appear as Unknown or remain Offline in Access Expert and cannot be brought online. Product Line EcoStruxure Access Expert Environment Downstream controllers/interfaces Cause Offline downstream interfaces can occur for several reasons: The downstream controller has not been set to Active after being added to the system. Interfaces were added after the controller was already activated, and the controller has not been rebooted to receive the new configuration. DIP switch settings or device addressing are incorrect. RS-485 wiring is incorrect. End-of-line (EOL) termination is not configured correctly. Duplicate addresses or baud rate mismatches exist on the RS-485 network. Power supply issues prevent downstream devices from communicating reliably. Resolution 1. Verify Device Activation Navigate to the controller configuration page. Confirm that the downstream interface/controller is set to Active. If the interface was recently added, perform a Full Download or reboot the main controller to force the updated configuration to download. 2. Reboot the Controller Reboot the controller associated with the offline interface. This allows the controller to download and apply the correct configuration. 3. Verify DIP Switch Settings and Addressing Check that the DIP switch configuration matches the settings configured in Access Expert. Switches 1–5 define the device address in binary (addresses 0–31). The address configured in Access Expert must match the physical DIP switch address. Switches 6 and 7 define the baud rate. The default setting is 38400 baud with both switches ON. Switch 8 should be OFF to disable AES key encryption. Communication is encrypted through TLS 1.2. Note: DIP switch orientation may appear inverted compared to labels on other connectors. For example, on an MR52 board, the ON label is located below the switch bank. 4. Verify RS-485 Wiring Ensure all panels are wired correctly according to the hardware installation guide. Verify RS-485 communication wiring polarity and continuity. Use a true daisy-chain topology. Avoid star configurations and wiring stubs. 5. Verify End-of-Line (EOL) Termination Confirm that EOL termination jumpers are configured according to the hardware installation guide. Enable termination only on the last physical controller in the RS-485 chain. 6. Verify Address and Baud Rate Consistency Inspect the physical DIP switches on all downstream controllers. Ensure each downstream controller has a unique address. Verify that software-configured addresses match the physical settings. Confirm that all devices on the same RS-485 segment use the same baud rate. 7. Isolate the Affected Controller Disconnect the second downstream controller from the RS-485 network. Verify whether the first controller remains online. Connect only the second controller to the main board. If the controller still fails to communicate, investigate: Duplicate addressing RS-485 communication hardware faults Local power supply issues 8. Verify Power Supply Health Measure voltage at the downstream controller power input. Confirm voltage remains stable between 12 VDC and 13.8 VDC under load. Low or unstable voltage can cause controllers to go offline, especially when readers, door strikes, or other peripherals draw power.

Issue Insight Sensors were not counting people as expected, even though the sensors were online and other sensor functions such as PIR operation appeared to be working. Troubleshooting, resets, firmware upgrades, and recommissioning did not resolve the issue. Product Line EcoStruxure Building Operation Environment Insight Sensor Cause After troubleshooting with the Insight Sensor Engineering Tool, removing masks for testing, and verifying that other sensor functions were operating correctly, the affected sensors were determined to be faulty. Resolution Use the Insight Sensor Engineering Tool to verify configuration and test the sensor with no masking applied. If the sensor remains online, other sensor functions like PIR operate correctly, and people counting still does not function, replace the affected sensor. In this case, replacing the sensor resolved the people-counting issue, which ruled out any configuration issues.

Issue Receive "Initialization error" when trying to start I/NET with SQL 2008 When we installing SQL Server 2008 Standard for I/NET Filemaster, what are the main components we should include? When editing / adding a new I/NET Configuration Profile the Database Server section is blank DBCreate does not start.  Appears in task Manager but no user interface is shown. Within DBCreate the restore option is grayed out Product Line TAC INET Environment I/NET Seven 2.4x Microsoft Windows Server 2003, Windows XP, Windows Vista, and Windows 7/10 families of operating systems. (both 32 and 64 bit) Microsoft SQL 2008 Standard or Express Editions Microsoft SQL 2008 R2 Standard or Express Editions Cause I/NET must have the SQL 2005 Backward compatibility file installed.  If this is not installed I/NET will not locate the SQL Server and hence will issue an “initialization failure” error.  This is can also be identified in either the DBCreate or I/NET Configuration application editors which will show no entries in their "Database Server" settings. The document also details information that is necessary for a Standard or Express editions of SQL 2008 / SQL 2008 R2. Resolution Follow the instructions below extracted from the document called "SQL2008 Expr Install Inst.pdf".  This document is found on I/NET Seven CD under the 'SQLExpress' folder.  For SQL 2008 R2 installations refer to the following document SQL2008 R2 Expr Install.pdf, also found in this same folder .  Installing SQL Server 2005 Backward Compatibility SQL Server 2005 backward compatibility must be installed for SQL 2008. To install SQL Server 2005 Backward Compatibility Navigate to the SQLBcm directory on the TAC I/NET Seven installation CD. Launch the SQLServer2005_BC.msi file. Follow the prompts on each screen and accept all defaults. After the install check the SQL Server Services SQL Server Browser is RUNNING SQL Server (MSSQLSERVER) is RUNNING Check the SQL Server Network Configuration Protocols Enable Named Pipes Enable TCP/IP Completing the Installation Proceed with the installation of TAC I/NET Seven on your PC. For installation instructions, refer to TCON298, TAC I/NET Seven Getting Started. Note: Run Inetcfg.exe before starting TAC I/NET Seven for the first time. This is necessary to attach TAC I/NET Seven to the database and avoid an “Initialization failure” error. Note: Before file equalization will operate, the system must be rebooted or the INETEQZMERGE service must be manually started.   Also refer to Installing I/NET 2.42 or higher and Vista 5.1.7 or higher on a 64-bit operating system for additional details on installing I/NET with SQL 2008 R2.

Issue How to create a detailed report that contains added and deleted card numbers in users. Product Line EcoStruxure Security Expert Environment Security Expert Cause The requirement is to review historical changes made to user records, specifically card numbers that have been added or removed. Standard Event reports indicate that a user record was modified but do not provide details of the specific fields that were changed, making it necessary to use a report that includes modification history. Resolution The Record modified history report shows all user records modified within the selected time frame, grouped by user. It includes the settings that were modified, the old and new values, and the operator.  Create a new User report set the Report type to "Record modified history report" set the Period If set to Custom period with Prompt for data selected, the Report will prompt the operator for a date range defaulting to the last week save the report and then run it Modified users report

Issue How to get answers for project specification responses or how to get a product enhancement implemented. Product Line EcoStruxure Security Expert, EcoStruxure Building Operation Environment Security Expert EcoStruxure Building Operation Cause Unsure who to go to for help with specification replies or how to get a potential product enhancement added to the offer. Resolution Create an idea on The Exchange Community for your specific Offer. The more Likes an idea floated on the Community receives, the more attention it is given by offer management for that associated product line. Even if you do not yourself have an Enhancement Request, help raise the profile of others by Liking theirs Contact your local solution category manager for the Offer as they will be able to point you in the right direction for answers to specification questions and can help escalate enhancement requests to Product Management. Americas: Americas.EcoStruxureBuilding@schneider-electric.com EMEA: EMEA.EcoStruxureBuilding@schneider-electric.com Asia Pacific & India: AsiaPac.EcoStruxureBuilding@schneider-electric.com When providing your feature request make sure to include as much detail as possible about the feature as well as any specifics that might help justify the need for the new feature.

Issue Security Expert and Security Expert Data Sync Service are running and operational. After a while, the Data Sync Service stops synchronizing. Reviewing the Data Sync Service log file indicates that the connection was lost and that the operator username or password are incorrect. [WARN ] [0 ] - Failed to get Operator where ID = 6. Error Code: 8 (Connection lost/not logged on) [ERROR] [0 ] - Incorrect username or password, or the operator does not have access. Error Code: 0 (Error). Restarting the entire system or the Security Expert Data Service resolves the problem. Product Line EcoStruxure Security Expert Environment Multiple Security Expert Clients Security Expert Data Sync Service Cause The number of concurrent clients has exceeded the licensed limit.   The Data Sync Service will make a connection each time it synchronizes and then close that connection when finished. If there are no client licenses available for it to use when attempting to connect then it will fail and present the following events in the log file. [INFO ] [0 ] - Verifying product license information... [WARN ] [0 ] - Failed to get Operator where ID = 6. Error Code: 8 (Connection lost/not logged on) [ERROR] [0 ] - Incorrect username or password, or the operator does not have access. Error Code: 0 (Error). [INFO ] [0 ] - Next sync will begin at 24/07/2019 9:42:59 AM Each Security Expert Client connection will take up a client license. If the SSN is enabled for three concurrent client connections this will allow for two Security Expert Clients and one Data Sync Service. Resolution Purchase more client licenses (SX-CLNT) for the sites SSN. Ensure that no more than [one less than the maximum concurrent clients number] Security Expert Clients are running when the Data Sync Service is also running.

Issue After upgrading an MP/RP controller to firmware 7.0x.xx, Bluetooth commissioning from Building Commission (EBC), on phone and PC versions, fails. The PIN can be entered and the controller appears in the paired Bluetooth devices list, but the connection does not progress further. Product Line EcoStruxure Building Operation Environment Building Commission MP/RP Controller  Cause The External Application Whitelist was enabled. When Bluetooth is enabled while the whitelist is active, the Bluetooth connection is secured for the Engage mobile application and is not available for commissioning through the commissioning tool. Resolution Disable the External Application Whitelist on the controller and reconnect using Bluetooth. After the whitelist was disabled, the Bluetooth connection is established and the controller can be commissioned through EBC. If needed, assign a new Bluetooth PIN and remove the controller from the paired devices list before attempting to reconnect. Refer to: RP Controller Settings Properties - Basic Tab

Issue Create a solution with an alarm definition and event filtering that will pulse an output to a phone dialer for alarm monitoring. Trigger the dialer when another output is active and when any of the inputs for door contacts, motion sensors, etc. have become active. Perform this solution on an Access Expert Intrusion only system without any readers. Product Line EcoStruxure Access Expert Environment AccessXpert Intrusion system with no readers Cause Without Security Readers, there is less hardware to process and monitor the logic required for a solution. Event filters cannot reliably evaluate both an input event and the current state of a separate output together. Resolution The following approach can be implemented using hardware I/O-level logic. This method combines the required conditions externally and presents them to the system as a single input event, eliminating the dependency on multi-event evaluation within the filter query.   Concept Create a single system input that activates only when: The original input condition (GC/PIR/DC) is active, and The Notification Active output is active. This is achieved by using outputs and relay contacts wired in series, allowing the system to see a single input that represents both conditions being true.   Wiring Logic Once dry contacts are available, wire the following relay contacts in series: Output driven by the input condition (GC/PIR/DC) Notification Active output The series relay path is then connected to a spare input, referred to as the Notification Alarm Input.  The Notification Alarm Input will only activate when both relay contacts are closed, meaning: The original input condition is active, and The Notification Active output is active. Implementation Step 1: Create an Output for the Original Input Condition Configure the original input condition (GC/PIR/DC) to activate a dedicated output. This output will serve as a representation of the input condition in the relay wiring scheme. Step 2: Obtain a Dry Contact from the Notification Active Output Depending on how the Notification Active output is configured: Scenario A – Dry Contact Relay If the Notification Active relay is being used strictly as a dry contact and is not switching external voltage, it can be used directly in the series wiring. Scenario B – Power-Switched Relay If the Notification Active relay is switching power (for example, 12VDC to a device), it should not be used directly in the input circuit. An isolated relay should be added to provide a dry contact interface. Scenario C – No Spare Outputs Available If no spare outputs are available, an external relay may be driven from the existing Notification Active output. The dry contacts from this relay can then be used to complete the series wiring.   Alarm Workflow The resulting sequence is as follows: A GC/PIR/DC input event occurs. The event activates the dedicated input-driven output. The Notification Active output remains active for its configured timer duration. The input-driven output and the Notification Active output are wired in series. When both conditions are present, the signal is sent to the Notification Alarm Input. The Notification Alarm Input triggers an Alarm Definition. The Alarm Definition activates the Alarm Monitoring Service Notification Output. The Alarm Monitoring Service Notification Output generates a pulse to the dialer. Workflow Diagram C/PIR/DC Input        │        ▼ Input-Driven Output        │        ├──── Series Wiring ────► Notification Alarm Input        │ Notification Active Output        │        ▼ Alarm Definition        │        ▼ Alarm Monitoring Service Notification Output        │        ▼ Dialer Pulse   Testing Results This approach has been tested and confirmed in a lab environment to produce consistent results, allowing the system to trigger only when both conditions are present.   Conclusion When Alarm Definition Filters cannot reliably evaluate an input event and a separate output state together, combining the logic at the hardware I/O level offers a reliable alternative. By wiring the input-driven output and Notification Active output in series to a dedicated Notification Alarm Input, the system can accurately trigger the Alarm Monitoring Service Notification Output and generate the required dialer pulse. Note: The above multi-step solution is needed for success. When attempting to create this with a single Trigger and Procedure, it would not work and would produce an error in Access Expert. “Filter references element that is not in the event data. Element 'Output' not found.” This occurs when a filter attempts to evaluate both input and output conditions together and fails to trigger as expected.   The filter references the “Output” field in event data where that field does not exist. Input-driven events (such as DC, PIR, or GC) typically only contain “Input” and “Status” fields and do not include “Output.” As a result, combining input and output conditions within a single filter causes the evaluation to fail because both cannot be processed together in the same event context.

Issue Intermittent latency with mobile app push notifications. Notifications are typically received within seconds of an alarm but occasionally experience delays of 1 to 3 minutes. Windows application logs indicate that the controller hosting the push notification service intermittently loses connection to the cloud service and then reconnects. Product Line EcoStruxure Security Expert Environment Security Expert Mobile App SP-C controller hosting push notification service Android and iOS mobile devices Cause Intermittent loss of connection between the controller and cloud service, potentially due to mobile device network switching between WiFi and cellular connections. Resolution Enable additional logging on the controller to gather more information about push notification behavior as follows: Navigate to Programming > Services, locate the service named PUSH - DO NOT TOUCH, and open it. In the Options tab, enable the following options: Log message retries and Log reporting failure. Save the changes and allow the system to download. After the download completes, confirm that the service restarts automatically; if not, manually stop and restart the service. Monitor logs to identify conditions contributing to notification latency.

Issue The Media Gateway Card fails to transmit panel messages to the converter used for Modbus or BACnet translation. This results in loss of communication between the Esmi Ultima fire panel and the BMS. Product Line ESMI Fire Detection. Environment Esmi Ultima System Media Gateway Card (FFSULH1007) Integration with Modbus or BACnet Warning Electrostatic Discharge Required: Always discharge static electricity from your person by touching metal prior to handling any hardware. Failure to do so may result in damage to devices. If you are unsure about any of the technical steps, or if you are not familiar with the Media Gateway Card configuration, contact Product Support for guidance before continuing. Cause The TCP/IP port on the Media Gateway Card is not functioning correctly, causing communication failure between the fire panel and the BMS interface. Resolution 1. Verify Firmware Version Navigate to Engineer Options → System Information. Confirm cabling: LAN cable connected to Media Gateway Card LAN port. Check the installed firmware version. Expected firmware: S794_V01.109 If the firmware version is missing, unreadable, or outdated: Perform a firmware update. Refer to the article: Esmi Ultima Media Gateway Card Firmware Update 2. Configure Graphics / Third‑Party & VR Settings Graphics / Third‑Party Settings Navigate to Engineer Options → Configuration → Panel Module → Media Gateway Card Select Graphics / Third‑Party Settings. Apply configuration values as shown in the reference images. Submit the settings. VR Settings In the same menu, open VR Settings. Apply configuration values as per the reference images. Submit the settings. Outcome After completing the firmware verification and applying the required Graphics and VR settings, the Media Gateway Card should resume sending messages to the converter, restoring normal Modbus/BACnet communication with the BMS.

Issue Dynamic Authority Control is available on Allegion Engage LE wireless locks, but this feature is not supported when the locks are integrated with EcoStruxure Security Expert. This leads to confusion about access behavior during communication loss. Product Line EcoStruxure Security Expert Environment Security Expert Allegion Engage LE Wireless Locks Allegion Engage Gateway (GWE) Cause Allegion Engage LE locks include a built‑in mechanism for storing Users and Access Levels locally. However, the current Security Expert integration does not utilize or support Allegion's Dynamic Authority Control. Instead, the integration treats Engage LE locks as smart readers, with all authentication, access logic, and user database management performed entirely by the Security Expert SP‑C controller. Because local credential storage is not used in this mode, the locks cannot make independent access decisions when communication with the SP‑C is lost. Resolution Per Application Notes 182 and 272, Dynamic Authority Control is not supported when using Allegion Engage LE locks with the Security Expert integration. When integrated, the system operates as follows: Normal Operation Engage LE locks act as smart readers All access control logic resides on the SP‑C controller Cardholder data is stored centrally on the SP‑C Event Behavior An “Allegion 485 Reader Offline” event is generated when communication is lost No door events are generated or cached while the Allegion interface module is offline Communication Loss Scenarios Condition Result SP‑C loses communication with the server Card access continues. The SP‑C uses its local cache and maintains control. GWE loses communication with the SP‑C Card access fails. The lock cannot authenticate because it does not store credentials in this integration mode.   Note: Ensure that the mobile app is disconnected from the lock before connecting to the SPC. The mobile app and the SPC cannot be connected at the same time. Because Dynamic Authority Control is not supported, there is no configuration option in Security Expert to store credentials locally on the Engage LE locks.

Issue How to configure the EcoStruxure BMS External Log Storage feature using PI System. Product Line EcoStruxure Building Operation Environment Building Operation Enterprise Central Building Operation Enterprise Server Building Operation Automation Server Premium Building Operation Automation Server Bundled Building Operation Edge Server Cause Need EBO to send selected trend logs and the event log to AVEVA PI System directly without the need for intermediate storage or specialized PI System connectors. Resolution The following video will illustrate how to: Install and configure AVEVA PI system (PI Server and PI Web API) for testing. Configure PI system settings in EBO. Configure trend logs to be written to PI system. View and organized the data in PI system Explorer. Things you need: EBO 2023 (V5.0.3) or higher with valid AVEVA PI System connection license or demo license (Enterprise Server, AS-P, AS-B or Edge Server). AVEVA PI server and PI web API with valid license (Check EBO Information Technology System Planning Guide for tested versions). For more information about PI system recommended architectures, system requirements and installation instructions, please check AVEVA documentation, PI System™ | AVEVA, OSIsoft - PI System and YouTube video published by AVEVA for detailed instructions about installing and setting up PI system Setting up a PI System Development Environment From Scratch - YouTube Note: In EBO V7.0.1 or higher, values can also be read and hosted from an AVEVA PI System, refer to: Hosting Points from AVEVA PI System Note: Starting with EBO version 7.1.2 and later, disabling the "EnableCSRFDefense" setting on the AVEVA side is neither required nor recommended. Hotfixes are available for EBO 6.0.4 and EBO 7.0.3. Please contact Technical Support to obtain the appropriate hotfix. Refer to: EBO cannot connect to AVEVA PI when EnableCSRFDefense is enabled - Schneider Electric Community

Issue Extended Logs have stopped updating on the Enterprise Server. Product Line EcoStruxure Building Operation Environment EcoStruxure Building Operation Enterprise Server Automation Server Trend Logs (TL) Extended Trend Logs (ETL) Architecture Note In typical deployments, Trend Logs reside on Automation Servers, while Extended Trend Logs are hosted on the Enterprise Server. Data is transferred from TL to ETL using a subscription-based mechanism driven by sequence numbers. Any inconsistency in this synchronization can result in ETL not updating even when TL continues logging. Cause Extended Trend logs have been configured on-site and have been operating reliably over an extended period. A subset or all of the Extended Trend Logs has stopped updating. The issue can occur after a Server backup is restored.  Trend logs and Extended Trend logs are allocated sequence numbers, and if the sequence numbers do not follow the correct sequence, the Extended Trend log may not update. How to verify the issue: Trend Log: Navigate to the corresponding Trend log and open it in a "Trend Log List" view. Add an additional column to show the Sequence number. Note the highest sequence number used. Extended Trend Log: Navigate to the Extended Trend log that is referencing the above Trend Log. Open the Extended Trend Log properties. Press and hold down the "ALT" key and click where the dot is indicated on the screen shot below, (just below the Basic tab).      This will show some more properties for the Extended Trend Log, the one you are interested in is “Last transferred sequence number”.   If the last transferred sequence number on the Extended Trend Log is higher than the Trend log’s highest sequence number, then that is why the Extended Trend Log has stopped. Resolution Option 1 - When Historical Data is Required Increase the sample interval by reducing the interval time of the Trend log until it has caught up with Extended Trend Log's Sequence Number. The Extended Trend Log will only fetch new records that has a sequence number higher than the last transferred sequence number. Until the sequence of Trend Log has caught up with the sequence of Extended Trend Log, you will not see any new records in the Extended Trend Log. The Log records that are created after you have caught up in sequence numbers will only be fetched to Extended Trend Log.   Option 2 - When Historical Trend and Extended Trend Data Are Not Required Create a new Extended Trend Log and associate the corresponding Trend Log. The new Extended Trend Log will fetch every record that the Trend log has and continue from there, but you will lose the records of the old Extended Trend Log had that the Trend log does not have anymore.   Option 3 - When Historical Trend Data Is Not Required but Extended Trend Data Must Be Retained Backup & restore the AS on the same AS. The Trend log will be cleared but the Extended Trend Log will start fetching new records.   Important Note - Extended Trend Log:  The extended trend log cannot log a variable. The extended trend log gets the initial value of the connected trend log. Do not connect more than one extended trend log to a trend log or another extended trend log. If a trend log is connected to two or more extended trend logs, critical conflicts can occur. The extended trend log must have the same unit as the monitored trend log to correctly display values.

Issue Esmi FDP Repeater Panel (FMP Sense Fireman's Panel) Showing fault in power input no 2 (PI 2). Product Line ESMI Fire Detection. Environment FFS00702606xx (FMP Sense Fireman's Panel). Warning Hazard of Electric Shock: Remove all power from all devices before removing any covers or doors of the system. Disconnect power at the device and at the power source. Cause The repeater panel is designed to monitor dual 24 VDC power inputs (PI1 and PI2). The PI2 fault occurs when the second power input is: Not connected, or Not properly bridged when only a single power supply is used. Resolution Perform the following steps: Connect the 24 VDC power supply to the primary power input terminal If only one power source is used: Install a jumper wire across both power input terminals (PI1 and PI2) This ensures both inputs are electrically present to the panel. .

Issue A user wants to configure a static IP address on a SpaceLogic Twisted Pair Adapter (SXWTPAE10001). After installing the Twisted Pair Adapter Engineering Tool, no option is available to modify the adapter IP configuration or change it from DHCP to a fixed IP address. Product Line EcoStruxure Building Operation Environment SpaceLogic Twisted Pair Adapter (SXWTPAE10001) Twisted Pair Adapter Engineering Tool Ethernet infrastructure over existing twisted-pair cabling Cause No mechanism is available to modify the adapter's maintenance IP address or configure the adapter for DHCP or a user-defined static IP address. The adapter uses a fixed maintenance IP address (192.168.0.249) for engineering access and operates as a Layer 2 Ethernet bridge/switch rather than a configurable Layer 3 network device, and this is the key reason why configurable IP addressing is not relevant to its normal operation. Resolution Configuring the SXWTPAE10001 with a user-defined static IP address is not supported. The maintenance IP address (192.168.0.249) is fixed and intended only for engineering access through the Twisted Pair Adapter Engineering Tool. During normal operation, the adapter transparently forwards Layer 2 Ethernet traffic while connected devices retain their own operational IP addresses. If engineering access is required, configure a secondary IP address on the engineering workstation within the 192.168.0.x/24 subnet and connect using the Twisted Pair Adapter Engineering Tool as noted in the Twisted Pair Adapter Engineering Tool v1.0.0 Release Notes. This maintenance IP is not used for normal runtime communications. How the Twisted Pair Adapter operates The TPA is a Layer 2 device and it's role is simply to transport Ethernet frames across the existing twisted-pair infrastructure. From the perspective of the connected IP devices, the adapter is largely transparent. To put this into context: Layer 2 (Data Link Layer) works with Ethernet frames and MAC addresses. Layer 3 (Network Layer) works with IP addresses. Routers operate at Layer 3 and make forwarding decisions based on IP addresses. Switches and bridges operate at Layer 2 and make forwarding decisions based on MAC addresses. A useful analogy is a standard Ethernet switch. When you connect an AS-P or RP-C to an Ethernet switch, the switch itself does not participate in the BACnet/IP communications. The switch simply learns which MAC addresses are connected to each port and forwards Ethernet frames accordingly. The BACnet/IP communication occurs through the switch, not with the switch. The Twisted Pair Adapter performs a similar function. The AS-P, RP-C, and other IP devices retain their own operational IP addresses and communicate normally using BACnet/IP or BACnet/SC.   

Issue User is unable to log in to Building Advisor and receives the error message: "Account Unavailable – Permission Required. Please contact your account administrator.". The user requires access to the platform. Product Line EcoStruxure Building Advisor Environment Building Advisor (BA) portal User account  Cause The issue is typically caused by one or more of the following: The user has not been granted access to the specific Building Advisor site. Required permissions or roles have not been assigned by the site administrator. Resolution Follow these steps to resolve the issue: Inform the user to contact the Building Advisor Site Administrator: Support teams do not create or grant user access due to security policies. The Site Admin must add the user to the relevant site and assign permissions. If the Site Administrator is unknown: Ask the user to provide the Building Advisor site name. Assist in identifying the appropriate administrator. After access is granted and the account is active, the user should be able to log in successfully.

Issue There is uncertainty whether the controller output between terminals V1, G, and V2 should provide a constant 24V signal or an intermittent signal when the actuator reaches the end position, and whether this behavior is configurable. Product Line TAC Vista Environment TAC Xenta 100 controller Cause The controller operates using increase/decrease control logic and does not track the exact position of the actuator between fully open and fully closed. As a result, it continues sending control pulses even when the actuator has reached its end position. Resolution The output from the TAC Xenta 100 controller to motorized valves is not a steady 24V signal. Instead, it sends intermittent pulses to incrementally open or close the actuator. This behavior is inherent to the controller design and is not configurable. Most motorized actuators are designed to handle this type of control signal and include internal mechanisms, such as limit switches or magnetic clutch, to stop movement when end positions are reached. Note: The TAC Xenta 100 is an outdated product and is no longer supported.