Help
  • Explore Community
  • Get Started
  • Ask the Community
  • How-To & Best Practices
  • Contact Support
Notifications
Login / Register
Schneider Electric
Community
Community
Notifications
close
  • Categories
  • Forums
  • Knowledge Center
  • Blogs
  • Ideas
  • Events & Webinars
Help
Help
  • Explore Community
  • Get Started
  • Ask the Community
  • How-To & Best Practices
  • Contact Support
Login / Register

Contact Support

Close

Ask our Experts

Have a question related to our products, solutions or services? Get quick support on community Forums

Email Us

For Community platform-related support, please email us

New Community Ranking System
Our Community ranking system has recently been updated. You may notice changes in user rankings and receive system messages or notifications. If you have questions about how the new ranking works, please refer to the announcement post for more details (click here).

High Infinet traffic and communication issues when using direct bindings in EBO

Building Automation Knowledge Base

Schneider Electric Building Automation Knowledge Base is a self-service resource to answer all your questions about EcoStruxure Building suite, Andover Continuum, Satchwell, TAC…

Search in

Improve your search experience:

  • Exact phrase → Use quotes " " (e.g., "error 404")
  • Wildcard → Use * for partial words (e.g., build*, *tion)
  • AND / OR → Combine keywords (e.g., login AND error, login OR sign‑in)
  • Keep it short → Use 2–3 relevant words , not full sentences
  • Filters → Narrow results by section (Knowledge Base, Users, Products)
cancel
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Showing results for 
Show  only  | Search instead for 
Did you mean: 

Select a Country

Please select a country to continue with beta search.

  • Home
  • Schneider Electric Community
  • Knowledge Center
  • Building Automation Knowledge Base
  • High Infinet traffic and communication issues when using direct bindings in EBO
Options
  • Bookmark
  • Subscribe
  • Email to a Friend
  • Printer Friendly Page
  • Report Inappropriate Content
Invite a Co-worker
Send a co-worker an invite to the portal.Just enter their email address and we'll connect them to register. After joining, they will belong to the same company.
You have entered an invalid email address. Please re-enter the email address.
This co-worker has already been invited to the Exchange portal. Please invite another co-worker.
Please enter email address
Send Invite Cancel
Invitation Sent
Your invitation was sent.Thanks for sharing Exchange with your co-worker.
Send New Invite Close

Related Forums

  • Intelligent Devices Forum

Previous Next
Contributors
  • AbeMeran
    AbeMeran

Invite a Colleague

Found this content useful? Share it with a Colleague!

Invite a Colleague Invite
Back to Building Automation Knowledge Base
Start a Topic
Options
  • Bookmark
  • Subscribe
  • Email to a Friend
  • Printer Friendly Page
  • Report Inappropriate Content
2 Likes
342 Views

Link copied. Please paste this link to share this article on your social media post.

Trying to translate this page to your language?
Select your language from the translate dropdown in the upper right. arrow
Translate to: English
  • (Français) French
  • (Deutsche) German
  • (Italiano) Italian
  • (Português) Portuguese
  • (Русский) Russian
  • (Español) Spanish

High Infinet traffic and communication issues when using direct bindings in EBO

AbeMeran Mentor
‎2026-06-04 10:02 AM

Issue

Direct bindings between Automation Server (AS-P) and Infinet (I2) controllers in EcoStruxure Building Operation (EBO) generate excessive Infinet traffic due to polling behavior. As the number of bound points increases, this can lead to network slowdowns and communication issues.

Product Line

EcoStruxure Building Operation

Environment

  • EcoStruxure Building Operation
  • AS-P (Automation Server)
  • Infinet network
  • I2 controllers

Cause

Direct bindings configured through the EBO binding window or reference tab rely on polling mechanisms. For certain data flows (such as I2 to AS-P and I2 to I2 on the same network), values are polled at the configured interval (default 10 seconds), increasing network traffic. These bindings do not utilize the Continuum Import/Export (IE) system, resulting in inefficient, polling-based communication rather than event-driven updates.

Note that for data flow from the AS-P to the I2 device, a direct binding maybe used because the AS-P will ensure data will be transferred only when the value changes.

When doing DIRECT bindings via the binding window in EBO to/from I2 devices here is a summary of how the transfer is done for the different data paths

  • ASP to I2 (Irrespective of whether the value resides under the Infinet interface or not)
    • The value is transferred only when it changes
  • I2 to AS-P
    • Value is polled per the binding interval
  • I2 to i2 on same Infinet network
    • Value is polled per the binding interval
  • I2 to I2 on the second Infinet network of the parent AS-P
    • The value is transferred only when it changes
  • I2 on Infinet of AS-P to I2 on Infinet of second (remote) AS-P
    • No support for Continuum IE system, value is transferred by AS-P only when it changes. 

Resolution

For data paths that result in polling, use script program-based bindings to transfer data between controllers. This approach leverages the Continuum Import/Export system, where values are transferred only when they change, eliminating continuous polling and significantly reducing Infinet traffic.

For optimal performance:

  • Use script programs for I2 to AS-P and I2 to I2 data transfers.
  • For data paths that result in polling, direct bindings may be used for a small number of points where traffic impact is minimal.
  • When using the Import/Export system via Scripts, for values that do not change frequently (such as occupancy schedules), implement a periodic refresh or forced export in the script program to ensure updates are re-transmitted in case for whatever reason an update failed to reach one or more devices.

This approach ensures efficient, event-driven communication and helps maintain stable Infinet network performance.

Labels (1)
Labels:
  • EcoStruxure Building Operation
Tags (1)
  • Find more articles tagged with:
  • AbeMeran26
Was this article helpful? Yes No
100% helpful (1/1)

Link copied. Please paste this link to share this article on your social media post.

You’ve reached the end of your document

WHAT’S NEXT?

Ask our Experts

Didn't find what you are looking for? Ask our experts!

My Dashboard

Check out the new Feeds and activities that are relevant to you.

To The Top!

Forums

  • APC UPS Data Center Backup Solutions
  • EcoStruxure IT
  • EcoStruxure Geo SCADA Expert
  • Metering & Power Quality
  • Schneider Electric Wiser

Knowledge Center

Events & webinars

Ideas

Blogs

Get Started

  • Ask the Community
  • Community Guidelines
  • Community User Guide
  • How-To & Best Practice
  • Experts Leaderboard
  • Contact Support

    Ask our Experts

    Have a question related to our products, solutions or services? Get quick support on community Forums

    Email Us

    For Community platform-related support, please email us

Subscribing is a smart move!
You can subscribe to this board after you log in or create your free account.
Forum-Icon

Create your free account or log in to subscribe to the board - and gain access to more than 10,000+ support articles along with insights from experts and peers.

Register today for FREE

Register Now

Already have an account? Login

Terms & Conditions Privacy Notice Change your Cookie Settings © 2026 Schneider Electric

Welcome!

Welcome to your new personalized space.

of

Explore