Building Automation Knowledge Base

Issue How is time synchronized between the Controllers and Security Expert Server?  Product Line EcoStruxure Security Expert Environment Security Expert Server Security Expert Controllers (SP-C, SP-ACX, SP-AC1, SP-DCU) Cause Require details on different ways the Controllers can have their time set. Resolution There are two methods for synchronizing time on the Controllers. Periodically updated by the SNTP Time Server configured under the controllers Time Update tab. SNTP Time Server The controller polls its SNTP Time Server every 11 minutes.) A third-party NTP server such as Meinberg NTP, can be used. These servers synchronize with four or more internet time sources and are considered reliable. Ensure that UDP Port 123 is open on any firewalls, as this port is required for NTP communication. Without an SNTP Time Server configured, time is updated on the Controllers by the following methods. Time is updated manually by the Operator right-clicking the controller and selecting Set controller date/time. This will set the controllers time to the current time of the Workstation. Set Controller Time Time is updated to the server time whenever a “Force Download” is initiated for that controller. Force Download

Issue The Otis Destination Dispatch integration with Access Expert is not enforcing badge requirements for access to restricted floors. Users can select any elevator key without presenting a badge. Product Line EcoStruxure Access Expert Environment Access Expert Hosted V3 Mercury EP/LP4502 controller Otis Destination Dispatch elevator Compass System Cause The issue stems from missing routing table entries in the Mercury EP/LP4502 controller. These entries are essential for enabling communication between the Otis system and the Access Expert controller, which is required to enforce badge-based access restrictions. Resolution To resolve the badge enforcement issue: Verify Routing Table Entries on the LP/EP4502 controller’s web interface. Ensure the following entries are present: 192.168.50.0 – Enables communication with the Otis Compass Server. 192.168.1.0 – Enables communication with the Otis Destination Entry Computer. Important: If either entry is missing, the systems will not communicate properly, and badge enforcement will fail. Refer to the Hardware Setup section in the integration guide for detailed instructions: Access Expert Otis Elevator Integration Guide   Detailed instructions for installing the Otis Destination Dispatch Access Expert Integration can be found in the Access Expert Otis Elevator Integration with Destination Dispatch Knowledge Base article.

  Issue It is not clear if an INET SubLAN device, such as an MCU, is counted as a connected device for licensing purposes. Product Line EcoStruxure Building Operation Environment EcoStruxure Building Operation version 7.0 onwards Cause With the re-introduction of INET in EBO 7.0, it is unclear how INET SubLAN devices contribute to the connected device license count.  Resolution INET SubLAN devices below a host INET device increase the connected device count. As a result, a connected device license is required for each SubLAN device. Ensure that your system has sufficient connected device licenses to accommodate all INET SubLAN devices added under host INET controllers.

Issue How is the Otis elevator destination dispatch system configured in Access Expert? Product Line EcoStruxure Access Expert Environment Access Expert Hosted V3 Otis elevator system Mercury controller LP4502/EP4502 Cause Configuration steps needed for Otis Destination Dispatch in Access Expert Resolution An Otis Elevator Compass Destination Dispatching System model allows the LP/EP4502 to inform Access Expert if a cardholder is allowed and authorized for specific floors.   Elevator Control Types in Access Expert There are 2 main types of Elevator control in Access Expert: Basic - does not track the destination of the elevator and cardholder Destination Dispatch - tracks the destination of the elevator and the cardholder Licensing & Hardware Requirements License required: FN-DEST-OTISRS Controllers: LP4502 or EP4502 Mercury Recommended Adapters: LP4502: Micro-B USB adapter (Pluggable USB2-OTGE100) EP4502: USB 2.0 adapter (Pluggable USB2-E100 Hardware Setup: Connect the USB adapter to the controller and connect the Ethernet cable for the NIC2 to the Otis network. Log in to the controller page and navigate to the Network page Under Interface 2 (NIC2), select Static IP Type 192.168.50.250 in the IP address field. Type 255.255.255.0 in the subnet mask field. Click on Accept at the bottom of the page. Navigate to Apply Settings. The controller should reboot to apply the changes. Mercury Controller Configuration Ensure the following routes are configured in the Mercury Controller web interface. Feenics Setup From the Controller Page in Feenics: On the LP/EP4502 controller page, navigate to the "Destination Dispatch" Tab, located on the bottom of the page. Select Otis. Update the floor offset to reflect your Otis setup. The offset must be greater than or equal to 0. Make sure to take into consideration this offset when assigning elevator floor access. Enable "Has front and rear floors" if your Otis setup has front and rear floors.  Make sure to take into consideration this flag when assigning elevator floors access. Enable the "Primary Otis controller" option. Press Save. Issue a "Push Controller Database" command.   Note: The Otis Destination Dispatch Systems can only support one EP/LP4502. In order to support multiple EP/LP4502’s, a Primary and Secondary needs to be configured. The Primary EP4502 will manage communications to the Otis DDS. Communications between the Otis DDS and the Secondary EP4502’s will have to go through the Primary EP4502.   Reader Page: On the reader page, navigate to the "Elevator" tab and select "OTIS Destination Dispatching" as the Elevator Type. In the Dispatch IP enter the DEC (Destination Entry Computer "Touch screen or Keypad") IP address. For the Elevator Dispatch Mode, select the desired mode. You can hover over the tool-tip to read a description of the mode. If desired, select an Override Elevator Access Level. This will allow a set of floors to be public during defined schedules. Press Save. Look for an "Otis DEC {Reader} is Online" event in Live Monitoring that reports the controller communication with the DEC. The controller will report "Otis DEC {Reader} is Offline" if the communication between it and the DEC drops. Person Page: On the person page, navigate to the "Destination Dispatch Settings" tab. On the "Otis Settings" tab, click on "Add Otis Setting". Select the Otis controller and press OK. Select a Default Floor and Floor side. This floor will be served when a DEC is set to Mode 1. Select User flags. Note that Standard and ADA are mutually exclusive. Cardholder Flag selection descriptions: Standard - Standard access, speed and features. Disability - When checked, this indicates the cardholder has a disability. The Otis system recognizes this indicator and cab be set up to provide special accommodations (such as dispatch an adjacent car, extended time to board an elevator car, provide audible announcements at each floor). VIP - When checked, this indicates the cardholder is a VIP. The Otis system can be set up to dispatch an empty elevator car that runs non-stop to the destination floor. Vertigo - When checked, this indicates the cardholder experiences vertigo. The Otis system can be set up to accommodate this passenger by not dispatching them to a glass elevator. SplitGroup - When checked this indicates the cardholder belong to a split group. The Otis system is set up to recognize this person as belonging to a separate group of passengers who use a separate elevator car(s) that is not used by the general population (such as service elevators where technical or service staff do not mix with regular guests). Vertigo2 - no description  CartSvc - no description CIMOverride - Compass Inter-floor Matrix override. This overrides the segmentation used to place certain tenants into certain elevators. Technical Notes DECs must be represented by readers which can be connected to "fake" downstreams such as the MR52. The Cab used will be sent by the Otis system to Feenics upon access granted and displayed in event data.

  Issue RP-C contains 2 Modbus devices of the same type on the Modbus interface, one of the Modbus devices reports error 'Value Invalid reference type for HMI' when points with HMI as control mode are downloaded.       Product Line EcoStruxure Building Operation Environment Detected in version EBO 6.0.3.112 and above Cause Modbus point with Control Mode set to HMI will fail to download to RP-C if its reference is invalid. Create a folder in an RP Application folder called 'Test 1'. Create an Analog Value object in the ‘Test 1’ folder. Create a Modbus Device and add a Modbus Analog Output Point to it. Click on the gear to the right of the ‘Value’ property in the new ‘Modbus Analog Output Point’ and reference the Analog Value/Value from step 2. Set the ‘Control mode’ of the ‘Modbus Analog Output Point’ to HMI.   Edit the reference from step 2. so that it manually looks for ‘Test 2’. A warning appears indicating that the reference is invalid and Control mode is automatically set back to ‘Write only’. Change the ‘Control mode’ back to ‘HMI’ and Save, the system displays 'Value Invalid reference type for HMI' error.   Resolution A valid reference must be defined to a Modbus point with control mode set to HMI so that it can be downloaded to RP-C.   From step 4. set the reference back to a valid one ' Test1/Analog Value/Value ' and download the object to RP-C.  

Issue The “User Last Active” field does not update when users access controlled elevators using their access cards. As a result, users who primarily use elevators are incorrectly marked as inactive and automatically disabled after 90 days, despite regular use. Product Line EcoStruxure Security Expert Environment Security Expert Elevator integrations (e.g., OTIS, low-level relay) User inactivity policies (e.g., auto-disable after 90 days) Cause The “User Last Active” feature is designed to track access events at doors or keypads. When a reader expander is configured in elevator mode, the system does not associate elevator access with standard access events. Therefore, elevator usage does not update the “User Last Active” timestamp. Note: The current documentation does not clearly state that elevator access is excluded from this feature. It only references doors and keypads, which may lead to confusion. Resolution If tracking elevator access as part of user activity is required, we recommend submitting a feature request through your local Solution Category Management team. This ensures the request is formally reviewed and prioritized for future development.   Workaround: Create a Report of Disabled Users Open the User Report. Add a filter: Disable User equals Yes disabled user filter Save the report layout for future use. For detailed steps on applying filters in reports, refer to the Security Expert Community Post Security Expert User Reports.

Issue Clarification needed on whether AC-1A door modules are supported in Security Expert. Product Line EcoStruxure Security Expert Environment SP-AC1 Controller Andover Continuum door modules: AC-1 AC-1 Plus AC-1A Cause The AC-1A door module is not explicitly listed in the Continuum Transition documentation, leading to uncertainty about its compatibility. Resolution Although the AC-1A door module is not specifically mentioned in the documentation, it is supported by the Continuum Transition Tool. This means it can be used with Security Expert when transitioning from a Continuum system.   For detailed transition steps, refer to the Continuum Transition documentation available on the Schneider Electric Exchange portal.

Issue After successfully logging in, the controllers' web page is only partially displayed, showing broken image links and incorrectly formatted text. Resetting the controller does not resolve the problem. SP-C Configuration Web Page Product Line EcoStruxure Security Expert Environment Security Expert SP-C SP-AC1 SP-ACX Cause Incorrect controller web page files have been cached in the browser. This may occur if different controller firmware versions are viewed/commissioned on the same PC.  Resolution Clear the web browser's cache and try again.  Connect directly to the controllers' configuration page. For a controller with default settings, browse to 192.168.1.2.

Warning Potential for Data Loss: The steps detailed in the resolution of this article may result in a loss of critical data if not performed properly. Before beginning these steps, make sure all important data is backed up in the event of data loss. If you are unsure or unfamiliar with any complex steps detailed in this article, please contact Product Support for assistance. Issue Security Expert Installation steps for separate SQL, SX application Server, and Client for use with Windows Authentication and Active Directory Product Line EcoStruxure Security Expert Environment Microsoft SQL Server Microsoft Windows10 Security Expert Server and Client  Cause Access Denied error appears when attempting to log into Security Expert with Windows Authentication with a multiple PC Security Expert Installation Resolution Important considerations when connecting Security Expert to an external SQL Server: Machines should be on the same network and Domain. When you install Security Expert, reference the SQL database in this form:  Machine Name\SQL Instance Name The Windows user account doing the installation must have admin rights on both machines. The windows login you're using to install on the Security Expert machine has to have admin privileges to alter the SQL Database on the remote machine. The easiest way to do this is to use the same account to set up all machines. Different accounts can be used, but the accounts have to have privileges added to the SQL Database manually. (Not covered in this document)   Assumptions: Active Directory server has a domain user that can be used to install the applications on all machines. Licenses cover all machines Security Expert users are set up to use Windows Authentication (snapshots at the end of the document) If the SQL server ever had Security Expert Installed on it, uninstall Security Expert and reboot. If the Security Expert application server had SQL on it, uninstall SQL, reboot and reinstall Security Expert without local SQL. If the Client PC had Server components installed, uninstall Security Expert, reboot and install the client only.   Perform the SQL Server Installation onto a separate Server per the Security Expert Installation Instructions Security Expert Application Server/Client installation (No SQL) If this box is selected, the install may fail because the service has not been installed yet. With this option selected, the install will finish and then the service can be configured later. 3. Change the database server to NOT be localhost\SecurityExpert Use machinenameofSQLServer\SecurityExpert (Ex. SECEXPERTVM\SecurityExpert) 4. Select Windows Authentication Complete the installation.   5. Open Windows Services on the Security Expert Application Server (Run> services.msc) Right-click on Security Expert Data Service> Properties Select the Log On tab Deselect Login As Local System Account Select This account and then click browse to search for the domain admin user   Start the service. Security Expert Data Service, Security Expert Event Service, and Security Expert Update should all start   Client only setup - Ensure the Server option is deselected In the following dialog select Custom   7. Select the drop-down next to Server> then select “This feature will not be available” Complete the installation   A successful login with the domain admin account using Windows Authentication from the Security Expert machine and also the client PC should work.   From the Client PC – Security Expert application server = 10.169.90.170 From the Security Expert Server/Client SecurityExpertSV.exe.config (Server) – This file did not have to be changed    SecurityExpert.exe.config (Client) - This file did not have to be changed   Note: There may be circumstances where these files do need to be configured. See LL https://community.se.com/t5/Knowledge-Base/Security-Expert-Error-Server-Has-Rejected-Client-Credentials/ta-p/698   Domain Tab example set up in Security Expert for Active Directory Windows Authentication   Operator Example setup in Security Expert for Windows Authentication   Global Support Lab Testing SX Application Server (Windows10 1803) SQL Server – Server 2012 R2 with SQL 2016 SP1 (VM) SX Client – Window 8.1 Pro

Issue An SP-RDM2 will be used to add doors to an I/NET-transitioned site. The readers connected to the SP-RDM2 will need to read Hex Card Number credentials. Product Line EcoStruxure Security Expert, TAC INET Environment Security Expert Controller (SP-C) Security Expert Reader Module (SP-RDM2). Cause After transitioning an INET site to Security Expert, you may find it necessary to add one or more new doors. In Security Expert, you add doors to your system by attaching one or more SP-RDM2 modules to the RS-485 bus of an SP-C (up to two doors per SP-RDM2). That is still true for the transitioned system; however, some configuration tasks must be performed to allow the SP-RDM2 to coexist with the SCUs and DCUs that are already communicating with the SP-C.  You will also configure the SP-RDM2 to use the custom Hex Card Number credential you created as part of the INET transition process. Resolution For an SP-RDM2 module to work in conjunction with I/NET modules it must be configured in a specific way. You will need: SP-C firmware 2.08 build 911 or later SP-RDM2 firmware 1.12 build 546 or later Configuring the SP-RDM2: To the existing transitioned I/NET site, add a new Reader Expander for the additional SP-RDM2 reader module. (Note that the last reader expander defined in your existing system may be assigned to a dual-address SCU. If this is the case, make sure the address you assign to the SP-RDM2 is at least two addresses higher than the SCU to avoid address conflict.)  Set the Reader 1 Format and the Reader 2 Format to "Custom Credential". (Note that if the Port 1 Network Type or Port 2 Network Type is set to "Schneider Electric RS485" then this will need to be changed to "Wiegand" to allow you to set the reader format; it is greyed out otherwise. The network type can be set back to "Schneider Electric RS485" afterward.) Set the Port 1 Network Type and Port 2 Network Type according to the type of readers that are connected. In order to correctly convert the card read to the hexadecimal credential format that is programmed for the users, the reader expander must know what card format is being presented. This is done using commands. For the reader on port 1, add the command "R1RawFmt = #" where # is one of the descriptions shown in the table below. Similarly for the reader on port 2, add the command "R2RawFmt = #" where # is one of the descriptions shown in the table below.  If the command is absent, then Wiegand 26 is used as a default. Command Card Type R1RawFmt = Wiegand 26 26-bit Wiegand R1RawFmt = Wiegand 32 32-bit Wiegand R1RawFmt = Wiegand 34 34-bit Wiegand R1RawFmt = Wiegand 66 66-bit Wiegand R1RawFmt = Custom Wiegand Any Wiegand card - parity check is skipped Additionally, the SP-C controller must know which reader expanders to expect on the I/NET network and which reader expanders to expect on the Security Expert module comms network. By default, if the controller command "INET = true" is present in the SP-C, then all modules are considered to be on the I/NET network. Adding an SP-RDM2 to the Security Expert module comms network with no additional commands will result in partial operation but there will be problems. To use a mixture of I/NET modules and Security Expert modules, a command must be added to the programming of all I/NET modules. This command is: "HardwareType = INET" If this command has never been added to any module, and the command "INET = true" is present in the SP-C, then all modules are treated as I/NET. This maintains backward compatibility with existing sites. As soon as the "HardwareType = INET" command has been added to even one module, then it must be added to the programming of all I/NET modules from then on for the site to function as expected. Configuring the SP-RDM Doors to Accept Hex Card Number Credentials Create a new Door Type for reading cards as a Hex Card Number credential and configure it as follows. In the Entry section on the General tab, set the Entry Reading Mode to "Custom". In the Entry Credential Types section, add the "Hex Card Number" credential type. Save the Door Type. Configure each door on the SP-RDM2 to use the new Door Type as follows: In the Setup section on the General tab of the door, set the Door Type to the name of the Door Type you just created in step 1. Save the door.

Warning Hazard of Electric Shock: Battery terminals and leads are not power-limited. Short circuits can cause a fire or an explosion. Use extreme caution while connecting or disconnecting standby batteries. 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. Issue The panel displays a Low Battery Voltage (With Charger Trouble) condition. This is accompanied by General Trouble and Power Trouble LEDs being ON. Product Line ESMI Fire Detection. Environment FFSULH1001. FFSULH1002. FFSULH1003. Cause Possible causes of this issue include: Battery impedance exceeds acceptable limits This can occur after several years of use as batteries degrade. Mixing different battery brands or using batteries of the same brand but with different ages (e.g., one new and one old) can also cause this issue. Faulty power supply If the power supply is malfunctioning, it may not charge the batteries correctly, triggering the fault. Resolution Step 1: Replace the existing batteries with a new set from the same brand. This often resolves the issue if battery impedance was the root cause. Step 2: If the issue persists after replacing the batteries, the power supply may be faulty. In this case, replace the power supply unit. After replacing either the batteries or the power supply, the panel should return to normal operation.

Warning Hazard of Electric Shock: Battery terminals and leads are not power-limited. Short circuits can cause a fire or an explosion. Use extreme caution while connecting or disconnecting standby batteries. 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. Issue The panel displays a Low Battery Voltage (No Charger Trouble) condition. This is accompanied by General Trouble and Power Trouble LEDs being ON. Product Line ESMI Fire Detection. Environment FFSULH1001. FFSULH1002. FFSULH1003. Cause The issue may arise due to one of the following scenarios: Newly Installed Batteries Battery voltage may be low initially. Allow the system to charge for a few hours. The trouble condition should clear automatically. Panel Running on Batteries (No AC Supply) Extended battery use without AC supply can drain voltage. Once AC power is restored, charge for a few hours. The issue should resolve itself. Panel on AC Supply but Still Showing Trouble Batteries may be aged or degraded. If the issue persists after charging, replace the batteries. After replacement and charging, the panel should return to normal operation.   Resolution Scenario Action New batteries Charge for a few hours No AC supply Restore AC supply and charge Aged batteries Replace and charge

Issue Access to the Platform on a PC without administrative privileges is, by default, not allowed. Product Line TAC IA Series Environment I/A Series N4 /AX Workbench Cause Default Platform access is restricted to persons logging on to the PC with administrative privileges Resolution To run a station on a Workbench, you must open the Platform to install and start the station. Consult with your IT department about getting a temporary local admin account or have them assist you with this process.   Start the daemon you wish to run the station in Open Workbench of the running daemon Open the Platform  Follow the steps in the screen capture Now you can open the Platform and run stations without having administrative rights on your PC.           Notes: This must be done for each version of Niagara Workbench If you have a Schneider Electric laptop with CyberArk EPM installed, obtain a CyberArk JIT for administrative privileges from SE Support. If you have a Schneider Electric laptop, when logging in to the "Update Authentication" in the Platform, use your SESA login.

Issue There is currently no summary KB article for all the data collection available in EBO systems. Product Line EcoStruxure Building Operation Environment Building Operation Enterprise Server Building Operation Enterprise Central Building Operation Workstation Building Operation Webstation Building Operation Automation Server Premium Building Operation Automation Server Bundled Cause Identified the need to review data from EBO to analyze performance or issues. Resolution Purposes for Data Collection Provide visual information about the issue Screenshots (from Windows Snip & Sketch or other tools) Video Capture or Mobile Device Video Device LEDs, provide any information about them and when they change. Provide information about your configuration/installation Network devices, including routers, switches, and any configuration you can provide BMS Routers Site Topology, including all devices included in the communications path Provide server (EC/ES/AS) XBK backup Configuration only is smaller and useful when investigating configuration, bindings, and/or programming All Data is larger and recommended when need to see trends or events to help investigate the issue's timeline. Provide any information to replicate the issue. Provide as specific as possible steps used to create that outcome Provide VERSIONS of ALL software, hardware, and protocols involved If submit any captures or logs, perform the following: Provide any steps performed in EBO during the capture or log with the date & time, so these events can be matched.   Servers (EC/ES/AS) Collect logs from an Automation Server Collect logs from the Enterprise Server and Enterprise Central Backing Up EcoStruxure BMS Servers Manually  (Configuration Only or All Data) Server Fieldbus Protocols Infinet: Gathering Trace Log information for the Infinet bus in EBO Lon: (Video included) Analyze Lon communication using trace log in EBO Modbus: Capture a Modbus trace log in EBO/SBO   Software EBO Webstation Collect EBO Webstation browser logs EBO Workstation Collect EBO Workstation logs EBO Project Configuration Tool (PCT) Collect log files from Project Configuration Tool (PCT) Windows Review the Windows Event Logs. What specifically happens when an error occurs? Follow this KB article to view and save the Windows Events: Viewing, Saving, Sharing Windows Event Logs for Troubleshooting Purposes Wireshark For extended period capturing, use this article to set up a Ring Buffer in Wireshark. Wireshark capture ring buffer for continuous capturing Hardware b3/Infinet Controller Collect log from a b3 or Infinet controller BACnet/IP Controller Workstation method - BACnet/IP Controller Diagnostics Building Commission method - Viewing and Exporting Diagnostic Files (WebHelp) or Viewing Diagnostic Files (YouTube)   Protocols & Electrical Interfaces Ethernet Capture any ethernet traffic, including IP: Using WireShark to analyse communications on an Ethernet network Capture Loopback (127.0.0.1) traffic between applications and/or servers running on the same host OS: How to capture localhost traffic with Wireshark to help troubleshoot EWS communication issues Lon Using Loytec LPA with SpaceLogic Server AS-P RS-485 Fieldbuses include BACnet MS/TP, I/Net, Infinet, Modbus RTU BACnet MSTP Capture Application - Communities (se.com) aka mstpcap.exe BACnet - PicoScope Basics Picoscope Configuration for Modbus RTU capturing and decoding Modbus RTU capturing in Wireshark

Issue Need to analyze Modbus RTU communication packets for SpaceLogic controllers. Product Line EcoStruxure Building Operation Environment Building Operation Automation Server Building Operation Multi-purpose Controller (MPC) Building Operation Room Controller (RPC) Cause MP and RP controllers do not support packet logging or viewing on their modbus serial ports. Additionally, RP controllers lack transmit/receive LEDs for Modbus, making diagnostics more difficult. For differences between Automation Server and MP/RP controller Modbus operations, refer to the article: Modbus in the MP and RP Controller Introduction  Resolution Wireshark Installation Install the latest Wireshark application from: Wireshark • Go Deep | Download Click on the "download" icon and select your operating system Launch the downloaded setup file to install Wireshark. The default installation options can typically be used, unless the user has a specific reason to select others. Modbus RTU capture extension for Wireshark The Github project can be found at: GitHub - jzhvymetal/WiresharkSerialAdapter: Wireshark Serial Adapter for Windows Navigate to the latest version and download WireSharkSerialAdapter.exe  With this file downloaded, navigate to the Wireshark application folder and locate the following subfolder. If it does not exist, create it.  Copy WireSharkSerialAdapter.exe into this folder. NOTE: This is not an executable to be launched by the user. Wireshark will execute it as an additional capture option. USB-to-RS485 communications adapter Install the USB-to-RS485 adapter to PC. Wire the RS-485 adapter to the SpaceLogic RS-485 port to be captured. Check Device Manager -> Ports to determine the COM port number it is using. Wireshark Configuration Launch the Wireshark application. The initial start-up screen will list the available capture ports. This list will be different for each user’s computer, depending on its configuration. Below is an example of what this screen looks like:  In this list, Serial Port Adapter (WireSharkSerialAdapter.exe) should be an option. Click on the settings icon  to the left to bring up the setup options:  Launch Windows Device Manager to confirm the COM port assigned to the connected USB-485 adapter Select this COM port and set the baud rate, byte size, parity and stop bits of the Modbus RTU channel to be monitored. Use the Interframe settings shown in the screenshot above. Select User DLT 147 as the Wireshark DLT. Save these settings. Returning to the main screen, select Preferences from the Edit pull-down menu and navigate to Protocols:  Expand Protocols and select DLT_User. Click on Edit to add an entry to the Encapsulation Tables. Click the “+” button to add a DLT  Select User 0 (DLT = 147) and manually edit the Payload dissector to be mbrtu:  Click OK and return to the main screen Wireshark Capturing With the COM port properly configured, a traffic capture is initiated by double-clicking the selected COM port. The content of the capture will depend on the connected devices. The following is an example of the active window panes:  The main pane is an overall summary of the Modbus RTU traffic, with a brief description of each message type. When a frame is selected in this pane, the lower-left pane contains a breakdown of the packet content by field-type, and the lower-right packet is the packet content in hexadecimal format. The selected frame number is displayed in the packet details frame on the lower left, as well as the contents of the Modbus message. In this example, the results of the Modbus Read Holding Request for 6 registers is shown. The Wireshark capture is stopped by clicking on the red square, second from the left

Issue You need to forward specific events from Security Expert to a third-party Syslog server for monitoring or logging purposes. Product Line EcoStruxure Security Expert Environment Security Expert software Syslog server (e.g., SolarWinds) Cause There is a requirement to send filtered Security Expert events (e.g., operator activity, user access, door unlocks, output activations) to an external system for analysis or integration. Resolution Security Expert allows you to forward events using the Send Event action. Follow these steps to configure it: Step 1: Create an Event Filter In Security Expert, go to the Events menu. Create a new Event Filter that captures the specific events you want to forward. Example: Filter for events like  Output <PGM_NAME> On By <DOOR_NAME> Function <DOOR_FUNCTION> . Tip: You can trigger these events by manually unlocking a door from the client to test the filter. event filter Step 2: Create a Send Event Action Still under the Events menu, create a new Action. Set the following parameters: Type:  Send Event Event Filter: Select the filter you created in Step 1. IP Address: Enter the IP address of the Syslog server. Port: Enter the port number used by the Syslog server (e.g., 514 for standard Syslog, or a custom port used by Packet Sender). action Step 3: Test with Packet Sender Use Packet Sender to simulate a Syslog server. In Packet Sender: Note the TCP port number shown in the bottom right corner. Ensure this matches the port configured in your Security Expert Action. The IP address should be the one assigned to your Security Expert server (e.g., your laptop’s IP if testing locally). Manually trigger the event (e.g., unlock a door or activate a relay). status page Confirm that the event is received in Packet Sender’s log window. packet sender

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. 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. Potential for Data Loss: The steps detailed in the resolution of this article may result in a loss of critical data if not performed properly. Before beginning these steps, make sure all important data is backed up in the event of data loss. If you are unsure or unfamiliar with any complex steps detailed in this article, please contact Product Support for assistance. Issue Installing a Flex server/gateway that supports multiple industrial and building automation protocols (e.g., BACnet IP, BACnet MSTP, Modbus RTU, Modbus TCP/IP, SNMP, OpenThread, and LoRaWAN) at a live site is complex and requires careful planning. Product Line EcoStruxure Building Activate Environment EcoStruxure Building Activate Flex Server EcoStruxure Building Activate Partner Portal Cause Improper installation often leads to degraded performance or unreliable device behavior Resolution Site Survey & Environmental Considerations Physical Location: Choose a secure, climate-controlled, and accessible location (e.g., equipment room or control panel). Install in a locked cabinet or secure room to restrict access. Power Availability: Ensure a dedicated, stable power supply with proper grounding. Use a UPS for critical applications to prevent data loss during outages. Network Infrastructure: Confirm availability of Ethernet ports for BACnet/IP, Modbus TCP/IP, and internet access. Install Ethernet cables in wall cavities or conduits. For cellular networks, monitor data usage and set up alerts to avoid over usage charges. RF Environment (LoRaWAN & OpenThread) LoRaWAN: Conduct a radio-mapping survey to determine optimal gateway placement. Use high placement, clear line-of-sight, and low-loss coaxial cables (e.g., LMR-400). Select appropriate antenna gain (e.g., 6 dBi for urban areas). Consider multiple gateways for redundancy. OpenThread: Identify interference sources (e.g., Wi-Fi, Bluetooth in the 2.4 GHz band). Ensure strong signal strength for reliable mesh networking. RS-485 Cabling (BACnet MSTP, Modbus RTU) Cable Type: Use shielded twisted-pair cables (e.g., Belden 3105A). Termination: Install 120-ohm resistors at both ends of the bus. Topology: Use a daisy-chain layout. Avoid star or stub configurations. Length Limits: Follow RS-485 specs (typically up to 1200 meters). Grounding: Maintain a common ground to prevent loops. Polarity: Verify A (+) and B (-) connections. Device Compatibility & Data Mapping Object/Register Mapping: Map BACnet objects, Modbus registers, and SNMP MIBs to internal gateway points. Document data types, scaling factors, and offsets. Device IDs & MAC Addresses: Assign unique IDs for Modbus (1–255) and BACnet MS/TP (1–127). Document all assignments. Adjust network priority if BACnet uses Ethernet and Wi-Fi is used for internet. Baud Rates & Serial Settings: Match baud rate, data bits, stop bits, and parity across all serial devices. Disable unused interfaces to reduce noise and resource usage. Conclusion By following these best practices, you can ensure a successful and reliable Flex server/gateway installation, enabling seamless communication across diverse automation protocols.

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. 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. Potential for Data Loss: The steps detailed in the resolution of this article may result in a loss of critical data if not performed properly. Before beginning these steps, make sure all important data is backed up in the event of data loss. If you are unsure or unfamiliar with any complex steps detailed in this article, please contact Product Support for assistance. Issue When the Flex Server/Gateway is unable to connect to the internet, it's important to verify the network priority settings to understand how the device attempts to connect to the cloud. Product Line EcoStruxure Building Activate Environment EcoStruxure Building Activate Flex Server EcoStruxure Building Activate Partner Portal Cause The Flex Server/Gateway is not designed for direct exposure to public networks. Improper network priority settings may cause the device to go offline when connected to the internet. Resolution The Flex Server/Gateway supports multiple internet connectivity options: Cellular (GSM): Supports two SIM cards for redundancy. Ethernet Wi-Fi (via Wi-Fi receiver) USB Tethering (via the top USB port, usb0, for troubleshooting) Learn more about USB tethering: USB Tethering for Flex Server   Connectivity Priority (Default Order) USB Tethering (usb0) Cellular (GSM) Ethernet Wi-Fi Note: If GSM fails and Ethernet is connected, the server will automatically switch to Ethernet. If both GSM and Ethernet are unavailable, it will switch to Wi-Fi (if configured). SIM Card Failover If one SIM card loses internet connectivity, the server automatically switches to the second SIM after a few minutes.   Best Practices Install the server in a secure location to prevent tampering (e.g., unplugging Ethernet or removing LTE antenna). Avoid direct exposure to public internet to maintain security and stability.

  Issue Unable to perform AET license registration online Product Line Automated Engineering Tool Environment Automated Engineering Tool Cause If a license file for AET is not found on the computer, the License Registration screen will be displayed when AET is started. By default, the New Registration button launches an online registration process, if the computer is offline or there is a problem contacting the AET License server then Offline registration is needed. Resolution AET Offline license registration process If a license file for AET is not found on the computer, the License Registration screen will be displayed when AET is started. Click the "Offline registration" button. Fill in your name, company, email address and select the license type you want. Then click "Save to file". Select a location to save the license request file, once the file has been saved to the computer, instruction on how to proceed are shown. Click OK and AET will close. Email the saved file to aet.support@schneider-electric.com the AET Support team will respond with a license. Place the supplied license in the C:\ProgramData\Schneider Electric\AET\License File folder on the computer and run AET.

  Issue When viewing the Modbus property in EcoStruxure Building Operation, the status displays "Attention". Product Line EcoStruxure Building Operation Environment Building Operation Automation Server Building Operation Enterprise Server Cause The "Attention" status is not documented in the Web Help, which can make it unclear what is causing this state. This status typically indicates that there is an issue occurring within the Modbus system. One common cause is an unrealistic poll rate set on a Modbus group. . Resolution If the poll rate on a Modbus group is set too fast for the server to handle—especially in large Modbus networks—this can trigger the "Attention" state. Recommended Action: Review the poll rate configured for the Modbus group. If it is set to a very low value (e.g., 1 second), increase it to a more realistic interval. For busy networks, a poll rate of 5 seconds or more is typically more achievable. Once the poll rate is adjusted to a manageable value, the Modbus status should return to "Online".