Distributed Axis Motion Synchronization Across Fieldbus Controllers

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

In distributed automation systems, the determination of motion data for axes by different programmable automation controllers induces delays due to the lack of immediate sharing of computed data between controllers, leading to suboptimal control performance.

Innovation Solution

A configuration where motion data for multiple axes are determined simultaneously in a single fieldbus cycle using trigger events to synchronize the computation across controllers, eliminating the need for additional cycles to account for dependent motion data.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If motion data for multiple axes are determined by different programmable automation controllers in a distributed automation system, then the system can achieve distributed control and improved scalability, but delays occur due to lack of immediate data sharing between controllers

Engineering Contradiction:
Improvedistributed control capabilityVSAvoidmotion data determination delay
Core Design Contradiction:
Adaptability or versatilityVSLoss of time

Solution Approach 1:

The patent merges the motion data determination process across multiple controllers by having them simultaneously determine motion data for different axes within the same fieldbus cycle. This is achieved through a coordinated approach where controllers share the determination process, eliminating sequential delays while maintaining distributed control architecture.

Inventive Principle:
Principle #5Merging (Combining)

Solution Approach 2:

The patent implements preliminary action by having controllers prepare and share motion data within the same fieldbus cycle before the cycle ends. This allows subsequent motion data determinations to use already-computed data from the same cycle, preventing propagation delays to future cycles.

Inventive Principle:
Principle #10Preliminary action

2Reliability

If motion data is determined sequentially across different controllers in separate fieldbus cycles, then data consistency is maintained, but control performance becomes suboptimal due to delayed availability of motion data

Engineering Contradiction:
Improvedata consistencyVSAvoidreal-time control performance
Core Design Contradiction:
ReliabilityVSProductivity

Solution Approach 1:

The patent enables continuous useful action by having multiple controllers simultaneously determine motion data for different axes within the same fieldbus cycle. This parallel determination process eliminates idle time and ensures that motion data becomes available immediately for real-time control applications without sequential waiting periods.

Inventive Principle:
Principle #20Continuity of useful action

Solution Approach 2:

The patent implements feedback mechanisms where controllers share computed motion data within the same fieldbus cycle. This allows other controllers to immediately access and use the shared motion data for their determinations, creating a feedback loop that maintains data consistency while improving response time.

Inventive Principle:
Principle #23Feedback

3Manufacturing precision

If additional fieldbus cycles are used to account for dependent motion data from other axes, then accurate motion control is achieved, but the system complexity and cycle time increase

Engineering Contradiction:
Improvemotion control accuracyVSAvoidfieldbus cycle structure
Core Design Contradiction:
Manufacturing precisionVSDevice complexity

Solution Approach 1:

The patent merges multiple determination processes into a single fieldbus cycle by coordinating controllers to simultaneously determine motion data for different axes. This consolidation eliminates the need for additional cycles while maintaining the accuracy required for dependent motion data, simplifying the overall cycle structure.

Inventive Principle:
Principle #5Merging (Combining)

Data Source

PatentEP4575687A1Distributed industrial automation systems
Publication Date: 2025.06.25 SCHNEIDER ELECTRIC IND SAS
  • EP4575687A1 patent drawingFigure 1
  • EP4575687A1 patent drawingFigure 2
  • EP4575687A1 patent drawingFigure 3

AI summary

Examples include automation system comprising a first controller, a second controller, at least an automation device, and a fieldbus; wherein the automation system is configured to determine motion data of a plurality of axes associated with the at least an automation device; and wherein, during a given cycle of the fieldbus: - the first controller is configured to determine motion data of a first axis of the plurality of axes; to transmit the motion data of the first axis to the second controller; and to transmit a trigger event enabling the second controller to start determining motion data of a second axis of the plurality of axes; and upon receiving the trigger event, the second controller is configured to determine the motion data of the second axis based on the motion data of the first axis.