Interface Device Command Grouping for Fieldbus Delay Bottlenecks

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

The low data rate of field level communication protocols creates a bottleneck at interface devices in industrial automation, preventing simultaneous execution of commands on field devices due to delays.

Innovation Solution

Implementing a method where interface devices cache commands and group them by field device, allowing for simultaneous execution of commands on multiple field devices while minimizing channel switching, thereby reducing overall execution time.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Productivity

If multiple field devices are connected to a single interface device using multiplexing schemes, then infrastructure costs are reduced and efficiency is improved, but a bottleneck is created at the interface device due to low data rate of field level communication protocols

Engineering Contradiction:
Improvecommand execution throughputVSAvoidcommand execution delay
Core Design Contradiction:
ProductivityVSLoss of time

Solution Approach 1:

The interface device receives and caches multiple commands from the control device before executing them on field devices. By performing preliminary actions (receiving and storing commands) before the actual execution, the system prepares commands in advance during idle periods, enabling faster response when field devices are ready and reducing overall execution delay.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The interface device acts as an intermediary between the control device and field devices. It buffers and manages the command flow, decoupling the high-speed control device from the low-speed field devices. This intermediary role allows the interface device to regulate command transmission rates and prevent bottlenecks by processing commands at optimal timing.

Inventive Principle:
Principle #24Intermediary (Mediator)

2Ease of operation

If commands are executed sequentially on field devices due to protocol delays, then communication simplicity is maintained, but overall execution time increases

Engineering Contradiction:
Improvecommunication simplicityVSAvoidcommand execution time
Core Design Contradiction:
Ease of operationVSDuration of action of moving object

Solution Approach 1:

The interface device segments the command execution process into distinct phases: command reception phase, caching phase, and execution phase. By dividing the overall process, the system can receive multiple commands during idle periods without interfering with the sequential execution requirement, thereby reducing total execution time while maintaining communication simplicity.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The interface device maintains continuous useful action by receiving and caching commands during idle periods when field devices are not ready. This continuous preparation ensures that when field devices become available, commands are already ready for immediate execution, eliminating waiting time and reducing overall execution duration.

Inventive Principle:
Principle #20Continuity of useful action

3Reliability

If the interface device waits for field device responses before receiving new commands, then communication reliability is ensured, but productivity decreases due to idle time

Engineering Contradiction:
Improvecommand execution reliabilityVSAvoidcommand processing efficiency
Core Design Contradiction:
ReliabilityVSProductivity

Solution Approach 1:

The interface device performs preliminary command reception and caching actions while field devices are processing previous commands. By preparing subsequent commands in advance during what would otherwise be idle time, the system ensures reliability (commands are properly received and buffered) while improving productivity (no idle waiting time).

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The interface device dynamically adjusts its operation mode based on system state: it actively receives and caches commands when field devices are busy, and switches to execution mode when they are ready. This dynamic behavior maintains reliability by ensuring commands are properly managed while maximizing productivity through continuous operation.

Inventive Principle:
Principle #15Dynamics

Data Source

PatentEP4002032B1A method for communicating with one or more field devices
Publication Date: 2023.08.09 SIEMENS AG
  • EP4002032B1 patent drawingFigure 1
  • EP4002032B1 patent drawingFigure 2
  • EP4002032B1 patent drawingFigure 3

AI summary

Accordingly, the current disclosure describes a method of communicating with one or more field devices using an interface device. Each field device is connected to a channel of the interface device. The method comprises receiving a first command associated with a first field device, from an industrial device, communicating with the first field device over a first communication channel for executing the received first command, receiving one or more commands associated with the one or more field devices, from the industrial device wherein the one or more commands includes at least one command associated with a second field device from the one or more field devices, and caching the one or more commands in a memory module prior to the execution of the first command.