Issue After enabling HTTPS on Security Expert controllers and rebooting, HTTPS access does not work and the expected Public Key/Certificate is not generated. The HTTPS option may appear enabled, but the controller cannot be accessed using HTTPS. Product Line EcoStruxure Security Expert Environment Security Expert SP-C controllers Single Record Download Service (SRDS) Warning Potential for Data Loss: Ensure all important data is backed up before proceeding. Cause The controller HTTPS configuration may not be retained when certificates do not match, when no certificate is loaded on the controller, or when the controller does not have a factory default certificate. A known issue may also prevent generation of a new certificate when SRDS has previously been connected to the controller using HTTPS. Resolution Reinstall the HTTPS certificate on the controller by following the HTTPS certificate configuration procedure described in the AN 314 Security Expert - HTTPS Connection to the Security Expert Controller - Integration Guide application note. Factory default the controller to remove existing custom certificates and reload the factory certificate. Re-enable HTTPS and encrypt the controller again with HTTPS active. If the controller has previously been connected to Single Record Download Service (SRDS) using HTTPS, review the known certificate regeneration workaround documented in the AN-309 Single Record Downloads in Security Expert application note.

Issue Server data may be combined in Building Advisor if a server connected to Building Advisor is cloned or detached without first disabling Cloud Connectivity (Cloud Plugin) and resetting its System ID. This can result in duplicate System IDs and incorrect data associations between servers. Product Line EcoStruxure Building Advisor, EcoStruxure Building Operation Environment EcoStruxure Building Operation Enterprise Server (ES) Enterprise Central (EC) EcoStruxure Building Advisor Cloud Connectivity (Cloud Plugin) Cause Cloud Connectivity (Cloud Plugin) was not disabled, and the System ID was not reset before the server was cloned or detached. As a result, the new server retained the original server's identification, which can lead to duplicate System IDs and combined server data in Building Advisor.   Resolution   Identifier terminology: In EcoStruxure Building Operation, the identifier is displayed as Server Id. In the tracelog, the same identifier is shown as sysID. Because the tracelog provides the most accurate and current value, this article refers to it as the System ID. The System identifier field shown in EcoStruxure Building Operation is a different value. Although it may be used when connecting a server to the Building Advisor Portal, it is not used in this cloning or detaching procedure. Do not reset or modify the System identifier field for this process. Before adding a new top server, cloning a server, or detaching a server connected to Building Advisor: Disable Cloud Connectivity (Cloud Plugin). Reset the Server Id shown in EcoStruxure Building Operation. This is the value identified as sysID in the tracelog and is referred to as the System ID in this article. Figure 1. Reset the value labeled Server Id. Do not modify the System identifier field for this procedure. Perform the server architecture change, such as adding a new top server, cloning the server, or detaching the server.   Resetting the Server Id/System ID allows the new server to generate a unique identifier and establish its own Building Advisor registration. The System identifier field is not part of this procedure. Following this procedure helps prevent duplicate System IDs and prevents data from multiple servers from being combined in Building Advisor. This is especially important when the servers belong to different customers. If a server was cloned, detached, or a new top server was added before Cloud Connectivity was disabled and the System ID was reset, open a PSS ticket for assistance with separating the server data.

Issue A replacement b3 controller cannot be commissioned or downloaded in EcoStruxure Building Operation.   The following error is reported: Property inconsistent selection criterion BACnet The trace log shows: Commission Canceled Model Number in DB does not match B3 on MS/TP Network. Product Line EcoStruxure Building Operation Environment EBO version 7.1 AS-P - Automation Server Premium HW Ver 062 b3 on MS/TP Legacy conversion / transition project Cause The b3 controller hardware model does not match the controller model configured in EcoStruxure Building Operation. In this case, the physical controller was a b3865-V, while the device was configured in EcoStruxure Building Operation as a b3866-V. The trace log indicated that the model number in the database did not match the b3 controller detected on the MS/TP network. Resolution   In this case, the configured controller model was updated to match the actual controller hardware. The device was exported to an XML file, removed from EcoStruxure Building Operation, modified in the XML file by changing the model from 866 to 865, and then recreated by importing the updated XML file. After the configured model matched the physical controller hardware, the issue was resolved.   Note: The difference between the b3865 and b3866 controller models is that the b3866 supports damper feedback. If the differences between the configured controller and the installed hardware are more significant, the hardware may need to be replaced to match the configuration.   Validation: After updating the configured model to match the physical controller hardware and re-importing the device, the controller commissioned successfully and the download completed without the "Property inconsistent selection criterion BACnet" error.

Issue When selecting a building in the Clients view, the message "Building no longer available for selection" is displayed, even though the building was available when the Clients view was initially opened. Product Line EcoStruxure Building Advisor Environment Building Advisor Portal Cause The building was available when the Clients view was opened, but an administrator has since either restricted access to the building or deleted the building. Resolution Refresh the browser to update the organization tree. Validate that the building is visible and accessible after the organization tree has been refreshed.

Issue A user cannot access the Building Advisor Portal or view the organizations, clients, buildings, or resources they are expected to access. The user may be unable to log in or may have insufficient permissions to perform required actions. Product Line EcoStruxure Building Advisor Environment Building Advisor Portal Cause The user account does not have the required access privileges assigned for the target organization, client, building, or portal. Note: Admin privileges are required to add users and assign access privileges. Resolution To add a user and configure access in Building Advisor Portal: Open the Menu and select Users. In the Users view, select Add User. Enter the user's email address in the Email Login field. If the user should only access Customer Portal, select User is a customer. This disables access to Building Advisor Portal. To grant Customer Portal access, expand the appropriate resource in the Portfolio column and select the checkbox in the Customer Portal column. To grant Building Advisor Portal access, expand the appropriate organization, client, or building in the Portfolio column and select the required access type in the Access column. Click Save. Admin users can assign access privileges that are equal to or less than their own privileges. Validate the configuration by confirming that the user can log in and access the assigned resources.

Issue A user is unable to create or delete other users within the system. Product Line EcoStruxure Building Advisor Environment User Roles and Organization Permissions Cause The assigned role does not provide the required administrative permissions. Users with View or Edit privileges only have access to clients and buildings where Effective Access is not set to None. Administrative functions such as creating or deleting users require Admin privileges at the organization level. Resolution Verify the user's role assignment within the organization. View and Edit privileges apply only to clients and buildings that the user already has access to (Effective Access not equal to None). Admin privileges apply to all clients and buildings in the organization, future clients and buildings added to the organization, and the organization itself. None provides no access to the organization, clients, or buildings. If the user needs to create, modify, or delete other users, assign the user an Admin role for the organization. After updating the role, validate that the user can perform the required user management actions.

Issue After upgrading EcoStruxure Building Operation, Modbus communication performance may change, older devices may generate offline alarms, and Modbus bindings between Enterprise Server and attached servers may no longer function correctly. Systems using Modbus bitmask objects may require binding updates after upgrade. Product Line EcoStruxure Building Operation Environment EcoStruxure Building Operation 5.0 and earlier EcoStruxure Building Operation 6.0 and later EcoStruxure Building Operation 7.0 and later Modbus TCP devices Modbus Serial Client Enterprise Server Attached field servers Cause Changes to Modbus communication architecture introduced in version 6.0 and the Modbus bitmask structure introduced in version 7.0 can affect communication behavior and existing Modbus bindings. External bindings between Enterprise Server and attached servers are not automatically converted during upgrade. Resolution After upgrading from version 5.0 or earlier to version 6.0 or later, run Modbus diagnostics after several days of operation to evaluate device performance and connectivity. Based on the diagnostic results, adjust settings or configurations on Modbus devices if required. Be aware of the following Modbus Serial Client changes in version 6.0 and later: Silent character is fixed at 3.5 and cannot be changed. Poll delay defaults to 10 ms and cannot be changed. Existing customized values from earlier versions are retained but hidden. Poll delay (%) is obsolete because compatible Modbus devices communicate in parallel. When upgrading to version 7.0 or later, valid Modbus objects configured with bitmasks are converted to the new bitmask structure. Internal server bindings are updated automatically. External bindings between Enterprise Server and attached field servers must be updated manually on the server that owns the binding. To update Modbus bindings between EcoStruxure Building Operation servers: In WorkStation, expand the System folder and select Upgrade history. Open Moved objects properties and save the content as a text file. Open the objects that contain external Modbus bindings. Right-click the object and select Edit bindings. Copy the existing binding path. Open the Moved objects file from the target server. Search for the copied binding path. The old and new paths are separated by "->". Copy the new binding path from the target server entry. Paste the updated binding path into the Edit bindings view on the source server. After the binding path is updated, the binding is corrected.   Validation Verify previously affected Modbus devices remain online and no recurring offline alarms are generated

Issue IEEE 802.1X Operational Certificate on a Linux-based Edge Server using Device Administrator. Product Line EcoStruxure Building Operation. Environment Linux-based Edge Server Device Administrator BACnet/SC certificate management Cause IEEE 802.1X is not supported on Edge Servers. IEEE 802.1X operates at Layer 2 of the OSI model and is intended for authentication between physical network devices and network infrastructure. Resolution Edge Server is a software-only component and does not function as a Layer 2 network device.

Issue A license violation warning is displayed in WorkStation after configuring both the local License Server and a secondary License Server address. When only the local License Server is configured, the license violation warning does not occur. Product Line EcoStruxure Building Operation Environment EcoStruxure Building Operation 6.0.x - 7.1.x Enterprise Server License Administrator License Server Cause When the secondary License Server address is getting added, License Administrator displays a warning indicating that WorkStation, Enterprise Server, or Enterprise Central was still running on the computer. The license server address change may not be applied successfully when EBO components are running. A full license reset and reconfiguration resolves the issue.     Resolution Perform the following steps to reset and reconfigure the licensing setup: Close all WorkStation sessions or windows on the local machine. Stop the Enterprise Server service. Return the current license. Uninstall License Administrator. Perform an SBO full according to License server Reset   or Manual License server Reset Install License Administrator. Activate the license. Add the secondary License Server address after a semicolon in the address field and apply the changes. Start the Enterprise Server service using Software Administrator. Launch WorkStation.  

Issue A customer asks whether events generated by an SP-C controller while it is offline from Security Expert will be uploaded when communication is restored. Product Line EcoStruxure Security Expert Environment SP-C Controller EcoStruxure Security Expert Cause The SP-C controller stores events locally when it is offline from the Security Expert Event Server. The controller retains up to 50,000 events in its event buffer using a FIFO (first in, first out) method. Resolution When the SP-C controller reconnects to the Security Expert Event Server, the buffered events are uploaded to the Security Expert server. The controller can store up to 50,000 events while offline. If the buffer reaches capacity, older events are overwritten by newer events. For extended offline periods, only the most recent 50,000 events are retained. Be aware that performing a firmware update clears the controller event buffer, so ensure required events have been logged to the event database before updating firmware.

Issue After reinstalling Project Configuration Tool (PCT), the user is unable to log in using the "admin" account and receives an invalid login attempt. The issue may also be accompanied by installation-related errors such as: "The setup has detected no version of SBO Project Configuration Tool is installed" Error code 1603 Error code 1722 Product Line Project Configuration Tool Environment Project Configuration Tool (PCT) 2.x Cause The default password may not be used after reinstallation, or residual PCT installation files may remain on the system and prevent the login issue from being resolved.   Starting a new PCT installation before removing the existing PCT folder can leave residual files in place and may prevent the login issue from being resolved. Where project data must be retained, export projects and create any necessary server backups before removing the PCT virtual machine or performing cleanup activities required for reinstallation. Resolution Verify that you are using the correct default administrator password for PCT. If the issue persists, fully remove the existing PCT installation: Open Hyper-V Manager Shut down and delete the PCT virtual machine. Delete the PCT installation folder: C:\ProgramData\Schneider Electric EcoStruxure\Building Operation\Project Configuration Tool If installation or uninstallation errors occur, back up the Windows Registry and remove the registry key. HKEY_LOCAL_MACHINE\SOFTWARE\Classes\Installer\Products\B2A4F0AEC8BB0E2438706F07E2E2560B Reinstall PCT 2.3.1 and log in using the default password Admin-11. If the issue remains unresolved, contact local Schneider Electric support.    

Issue After upgrading previously licensed AS-P controllers to EcoStruxure Building Operation 7.1.2, JCI/N2 SmartDriver licenses were no longer recognized correctly by the Enterprise Server. The Enterprise Server reported license deficits and licensing alarms, while AS-P controllers appeared licensed locally. Product Line EcoStruxure Building Operation Environment EcoStruxure Building Operation 7.1.2 Enterprise Server (ES) AS-P controllers SmartDriver license supporting communications with N2 bus and devices using AS-P for one COM port and TCP Cause In EcoStruxure Building Operation 7.0 and later, the SmartDriver license no longer functions as an AS-P local license in the previous manner. Upgrading AS-P controllers does not automatically migrate SmartDriver licenses from the AS-P controllers to the Enterprise Server, resulting in a licensing mismatch where the Enterprise Server reports deficits while the AS-P controllers appear licensed. Resolution Return the existing SmartDriver license entitlement, re-add and reactivate the license using Device Administrator 7.1, and assign the license to the top-level Enterprise Server. After the license is assigned to the Enterprise Server, allow the Enterprise Server to distribute the licensing to the AS-P controllers. After the license was returned, reactivated, and assigned to the Enterprise Server, the licensing error was resolved.

Issue Older controllers and takeover installations may not provide access to the Connection Type field in the controller web page. This field contains the communication settings required to connect the controller to the Access Expert host server. When the Connection Type field is unavailable, the controller cannot be commissioned or brought online.  Product Line EcoStruxure Access Expert Environment Access Expert Client Panel Utility (PanelUtil.exe) OEM Conversion Tool Cause When using older versions of firmware, the controller web interface does not provide access to the Connection Type setting required for host communication configuration. In some cases, the controller is configured as IP Server when IP Client is required. Older firmware versions may also prevent the Panel Utility from accessing or displaying all communication settings. Resolution Acre recommends using the Panel Utility to modify the controller communication settings and configure the controller for IP Client operation. The PC running PanelUtil.exe must be connected to the same local network as the controller. 1. Obtain and Launch the Panel Utility Request a copy of the Panel Utility from Product Support. Extract the utility files. Launch PanelUtil.exe. 2. Discover the Controller Click Discover. If no controllers appear, disable TLS through the controller web page (Data Security Field) Note: SSC controllers do not appear in the discovery list. 3. Attach to the Controller Select the desired controller. Click Attach. Verify the communication details. Click OK. Note: The example shown displays the Communication Type as 103 IP Server, which must be changed to IP Client. 4. Change Communication Settings Select Comm Settings. Open the Host Comm tab. Select IP Client as the Connection Type. Configure the required host communication settings. Click Apply Settings. Reboot the controller. 5. Browser Access from Panel Utility Selecting Browse while a controller is highlighted launches the controller web page. The utility is known to work with Microsoft Edge and Mozilla Firefox. Google Chrome may not function correctly. Multiple attempts may be required before establishing a successful connection.  6. OEM Conversion and OEM Credits Once the controller communication type is configured as IP Client, OEM Credits can be applied directly from within Access Expert. The OEM Conversion Tool displays available OEM codes and automatically assigns a code when available from within Access Expert.  7. Blank Communication Settings For very old controllers, the Panel Utility may not provide access to the required settings. In these cases, use the OEM Conversion Tool. (Request via PSS). If all communication settings appear blank after attaching to the controller, upgrade the controller firmware using the OEM Conversion Tool. After the firmware upgrade, the communication settings should become visible and editable. Open the Access Expert Client. Open the controller. Click Update OEMCode. Allow the system to assign an available OEM code. Proceed with normal commissioning. 8. Additional Troubleshooting if having issues connecting to the Panel Utility The controller is not on the same subnet as the PC running the Panel Utility. The controller firmware is too old for the Panel Utility to access all settings. TLS remains enabled during configuration. A firmware upgrade is required before communication settings can be modified. 9. Validation After the Connection Type is changed to IP Client, the host settings are configured, and an OEM code is applied if required, the controller can be commissioned through the standard Access Expert workflow. 

Issue During upgrades of AS-B controllers, some controllers upgrade successfully while others fail multiple times before eventually succeeding. Reported errors include timeout messages, download failures and connection loss during file transfer. In some cases, the controller became unresponsive after a failed upgrade and required recovery before another upgrade attempt. Product Line EcoStruxure Building Operation Environment Automation Server Bundled(AS-B) Cause Finding from the investigation was that a process timed out because an operation on the AS-B side was taking too long to complete. Resolution Recommendation if similar issues is seen. Perform a power cycle of the AS-B before the upgrade. Running the upgrade with the AS-B disconnected from the network and field bus connections where possible. If an upgrade fails, restore a backup taken before the upgrade and retry the process. . 

Issue Does EcoStruxure Building Operation (EBO) support virtualization? Can Enterprise Server, Enterprise Central, and Reports Server be deployed in virtual machines? Can EBO be deployed in containerized or cloud-hosted environments? Product Line EcoStruxure Building Operation Environment VMware Microsoft Hyper-V OCI-compliant container platforms Docker-compatible runtimes Kubernetes Microsoft Azure Amazon Web Services (AWS) Private Cloud Environments EcoStruxure Building Operation 2.0 through current release. Cause Customers increasingly deploy applications using virtualized, containerized, and cloud-hosted infrastructure to improve scalability, resiliency, system management, and operational efficiency. Questions often arise regarding the supportability of EcoStruxure Building Operation in these environments and where Schneider Electric support responsibilities begin and end. Resolution Virtualized Environments Virtualization allows multiple operating systems or servers to run on shared physical hardware through software platforms such as VMware and Microsoft Hyper-V. EBO has been successfully deployed in virtualized environments for many years. Enterprise Servers, Enterprise Centrals, Reports Servers, WorkStations, and other EBO components may be installed within virtual machines, provided the deployed operating system and allocated resources meet the requirements specified in the applicable product documentation and specification sheets. Benefits of virtualization can include: Reduced hardware footprint Simplified backup and recovery Improved scalability Easier system lifecycle management Enhanced infrastructure resiliency Schneider Electric supports the operation of the EBO software itself. Customers and system integrators remain responsible for the design, configuration, maintenance, and operation of the virtualization platform. Containerized Environments Current EBO offerings support deployment models utilizing Linux operating systems and OCI-compliant container technologies where described in the applicable product specification sheets and deployment documentation. Examples of OCI-compliant container technologies may include: Docker-compatible runtimes Kubernetes-based container platforms Container runtimes, orchestration platforms, host operating systems, storage infrastructure, and supporting services remain the responsibility of the customer, hosting provider, or system integrator. Cloud Environments The supportability of cloud-hosted deployments has evolved across EBO releases. EBO 6.x and Earlier EcoStruxure Building Operation versions 6.x and earlier were not developed, qualified, or supported for deployment in public cloud environments such as Microsoft Azure or Amazon Web Services. Customers who choose to deploy EBO 6.x or earlier releases in cloud environments do so at their own risk. Schneider Electric Product Support may not be able to provide assistance when cloud infrastructure, cloud networking, or cloud platform services are contributing factors to the reported issue. EBO 7.x and Later With EcoStruxure Building Operation 7.x, support for modern hosted deployment architectures has significantly evolved. Current EBO offerings support deployment models utilizing supported operating systems, Linux-based deployments, OCI-compliant container technologies, and hosted infrastructure environments when deployed according to published product requirements and specification sheets. Cloud-hosted deployments may include: Microsoft Azure Amazon Web Services (AWS) Private cloud environments Hosted infrastructure services The deployed operating system, allocated resources, network configuration, storage configuration, and connectivity requirements must comply with the applicable EBO documentation and specification sheets. Support Boundaries Schneider Electric Product Support provides support for issues determined to be within the EcoStruxure Building Operation software itself. Support is provided regardless of whether EBO is installed on: Physical hardware Virtual machines Containerized environments Supported cloud-hosted infrastructure However, Schneider Electric does not provide support for the design, administration, configuration, or troubleshooting of third-party infrastructure technologies. Examples include: VMware administration and configuration Hyper-V administration and configuration Kubernetes administration and orchestration Container runtime troubleshooting Microsoft Azure infrastructure configuration Amazon Web Services infrastructure configuration Cloud networking and routing Firewall and security policy configuration Operating system administration Storage platform administration Third-party backup solutions If an issue is determined to originate from the underlying infrastructure rather than the EBO application, customers may be required to engage their cloud provider, virtualization administrator, operating system administrator, or other infrastructure specialists for further investigation. Additional Considerations Successful deployment of EBO in virtualized, containerized, or cloud-hosted environments requires careful consideration of: Network latency and bandwidth DNS and name resolution Internet connectivity requirements Time synchronization Storage performance Backup and recovery strategies Cybersecurity requirements High availability and disaster recovery design Schneider Electric recommends that all deployments follow the requirements and recommendations documented in the applicable EBO product specification sheets and deployment guides.

Issue A customer needs to upgrade a legacy Automation Server (AS) to an Automation Server Premium (AS-P). When attempting the upgrade using PCT, the process fails with the following error:  "Upgrade failed"  What is the best way of doing the upgrade? Product Line EcoStruxure Building Operation Environment Building Operation Automation Server Premium(AS-P) Building Operation Classic Automation Server (AS) Cause Classic Automation Server backups cannot be upgraded directly to an AS-P. The backup must first be converted to an AS-P backup format before the upgrade can be completed. Resolution When converting a Classic AS backup it is better to use Device Administrator(DA) as the AS will be converted to an AS-P backup and upgraded to the version of DA at the same time. Open Device Administrator for the target version. Open the function "Convert backup set server type" Browse to the AS backup in "Backup set to convert" and click "Convert" The backup is converted to an AS-P and upgraded to the target version, the converted backup and be found in "Converted backup set output path" location. Refer to the EBO Webhelp Convert Backup Set Server Type Dialog Box for further information.

Issue A door created using the SOAP API was successfully added, but the ControllerID stored in the database was 1 instead of the expected controller. The issue was reproduced using both a Python script and SOAP UI. Product Line EcoStruxure Security Expert Environment Security Expert SOAP API (SX-SOAP-SDK) Python script SOAP UI Cause This behavior is expected when creating a door using the SOAP API AddRecord/AddRecordSC methods. The SOAP API automatically determines the controller assignment for doors based on the assigned hardware, including reader expanders and configured inputs/outputs. The HostController is not directly assigned by the AddRecord/AddRecordSC request for door records. If the required hardware relationships are not established at creation time, the system may fall back to a default controller association. Resolution Ensure that the door is linked to a reader expander and inputs/outputs that belong to the intended controller when the door is created, or immediately afterward. Confirm that the reader expander, inputs, and outputs used by the door are created before the door is created using SOAP. The SOAP API specification states that the host controller is automatically assigned based on the inputs/outputs associated with the record, and there is no need to specify the HostController directly.

Issue Security Expert operators need to use Windows Authentication while maintaining TLS 1.2 encrypted communications between Security Expert clients and the server. Product Line EcoStruxure Security Expert Environment Security Expert Server SX-AD-OPR Cause Windows Authentication requires specific installation and configuration settings. When TLS 1.2 is also required, additional configuration changes must be made to both the Security Expert server and client configuration files. Resolution To use both Windows Authentication and TLS 1.2 in Security Expert: Install Security Expert with Enable Windows Authentication on DataService/Client Communications selected during installation. If this option was not selected, Security Expert must be uninstalled and reinstalled with Windows Authentication enabled. Verify that Windows Authentication logins are working correctly before enabling TLS 1.2. Ensure the Security Expert Data Service machine is joined to the Windows domain and that clients are logged into the same domain. Configure TLS 1.2 on the Security Expert server and all client workstations. Update the  SecurityExpertSV.exe.config  file on the server and the  SecurityExpert.exe.config  file on all clients with the following security configuration: <security mode="TransportWithMessageCredential"> <transport clientCredentialType="none" protectionLevel="EncryptAndSign" sslProtocols="Tls12"/> <message clientCredentialType="Windows"/> </security> Save the configuration files and restart the Security Expert Data Service. Configure the operator accounts for Windows Authentication and map them to the appropriate Active Directory user accounts. When logging in, specify the Security Expert server machine name. Do not leave the Server field blank or use localhost. Validate that operators can successfully log in using Windows Authentication while TLS 1.2 communication remains enabled.  You can find more details in AN 288 Security Expert - Using Active Directory - Integration Guide.

Issue Can Execution Precedence be used to determine the priority of a program that is bound to a value? Application Task shows the "Conflicts" property set to true High Memory/CPU values causing performance issues with Automation Servers running a large number (100+) of applications (Function Block Programs and Script Programs)  Product Line EcoStruxure Building Operation Environment Building Operation Automation Server (AS. AS-B, AS-P, AS-P-3)  Function Block programs Script programs Cause The behavior of the Execution Precedence property is often misunderstood. Execution Precedence is intended to help the Application Scheduler establish a valid execution sequence between dependent programs. It does not provide a program priority mechanism and cannot be used to determine which program has control of a value when multiple programs are bound to the same output. Incorrect assumptions about its purpose can result in dependency-cycle issues, application conflicts, or unexpected control results Resolution Execution Precedence is a program property available in both Function Block and Script programs. It is configured from the program Properties on the Basic tab. How Execution Precedence Works Execution Precedence controls the order in which programs are executed. Programs with lower Execution Precedence values execute before programs with higher values. Program execution is coordinated by the Application Scheduler. For synchronized tasks, the scheduler normally determines execution order by analyzing dependencies between program inputs and outputs. Applications that provide data are generally executed before applications that consume that data. Programs with the Same Execution Precedence If multiple programs have the same Execution Precedence value, Execution Precedence does not establish an execution-order preference between them. In this situation, the Application Scheduler determines the execution order based on program dependencies. Important: Programs with equal Execution Precedence values should not be assumed to execute in a specific order unless that order is defined by their dependencies. Using Execution Precedence for Dependent Programs Execution Precedence can be used when one program generates a value that is required by another program. Example Program A calculates a compensated setpoint. Program B is a PID control program that uses the compensated setpoint as its reference value. Program B must have a higher Execution Precedence value than Program A so that the compensated setpoint is calculated before the PID program executes. Resolving Dependency Cycles A dependency cycle occurs when two or more programs depend on each other, preventing the Application Scheduler from determining a valid execution order. Example To resolve a dependency cycle: Identify the program that should execute first. Assign that program a uniquely lowest Execution Precedence value. The Application Scheduler uses that value to establish a valid execution order. Example Program A: Execution Precedence = 10 Program B: Execution Precedence = 20 Result: Program A executes first. Program B executes second. Note: If multiple programs within the dependency cycle share the same lowest Execution Precedence value, Execution Precedence does not provide a tie-break mechanism and cannot be used to resolve the cycle. What Execution Precedence Does Not Do Execution Precedence affects execution order only. It does not affect program priority. If two programs are bound to the same value output, both programs attempt to control that value, resulting in an indeterminate outcome. Combining Outputs from Multiple Programs When outputs from multiple programs must be combined, use appropriate logic. Binary values AND OR XOR Other logical operators Analog values Maximum Minimum Average Other methods appropriate for the application requirements References EcoStruxure Building Operation WebHelp: Application Scheduler Program Cycles in EcoStruxure Building Operation Software Script Programs  

Issue Guidance is required on how to add and bind SNVTs to a Local Node. High bandwidth usage on FT10 LonWorks network causing slow system response Product Line EcoStruxure Building Operation Environment LonWorks FT10 network Cause FT10 network bandwidth utilization is high because server-side objects such as TGML graphics and trends poll points on the LonWorks network at a high frequency. Each poll generates communications on the FT10 segment. When a large number of points are polled frequently, network bandwidth can become saturated, resulting in slow system response. A Local Node can reduce polling traffic by allowing server objects to read values locally while field devices update the Local Node through SNVT bindings. Resolution The Local Node resides within the Automation Server and can be bound to SNVTs from LonWorks devices. After binding, field devices update the Local Node at the configured SNVT transmission rate. Graphics, trends, and other server-side objects can then reference the Local Node instead of directly polling devices on the FT10 network. This reduces polling traffic on the FT10 segment and can improve overall network performance when high-frequency data access is required.   Here is a link to a Quick help Video showing how to set up and bind to a Local node