Embedded Instrument Control with Periodic Status Packet Synchronization

Resolve Bottlenecks,
Find Innovative SolutionsGenerate Solutions

Solution Overview

Problem

The command-response paradigm for controlling instruments with embedded controllers is inefficient, leading to slowed operations, complex troubleshooting, and synchronization issues between instrument hardware and host computer software, particularly due to the need for frequent commands and insufficient state data reporting.

Innovation Solution

Implementing a system where the embedded controller periodically sends complete status packets to the host computer, allowing the host to monitor parameter values and detect command completion without additional requests, and preventing conflicting commands by locking resources during task execution.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Loss of information

If the host computer frequently sends commands to read parameters from the embedded controller, then the host computer can monitor instrument parameters, but the embedded controller's scheduled task execution is perturbed and operations slow down

Engineering Contradiction:

Improveparameter monitoring capabilityVSAvoidoperation speed

Core Design Contradiction:

Loss of informationVSProductivity

Solution Approach 1:

Instead of the host computer requesting parameters from the embedded controller (traditional command-response), the embedded controller proactively pushes complete status packets to the host computer at scheduled intervals. This inversion eliminates the need for frequent host-initiated read commands while maintaining full parameter monitoring capability.

Inventive Principle:

Principle #13The other way round (Inversion)

Solution Approach 2:

The embedded controller prepares and sends complete status packets containing all current parameter values before the host computer would need to request them. This preliminary action ensures the host always has up-to-date information without interrupting the embedded controller's scheduled task execution.

Inventive Principle:

Principle #10Preliminary action

2Loss of information

If back-channel status reporting mechanisms are added to enable instrument monitoring, then parameter reporting capability is improved, but system complexity particularly of the embedded controller increases

Engineering Contradiction:

Improvestate data reportingVSAvoidembedded controller complexity

Core Design Contradiction:

Loss of informationVSDevice complexity

Solution Approach 1:

The periodic complete status packet mechanism serves multiple functions simultaneously: it provides comprehensive state data reporting, acts as an acknowledgment channel for commands, enables diagnostic tracking, and synchronizes host-computer and instrument hardware state. This single mechanism replaces multiple separate back-channel mechanisms, reducing overall system complexity.

Inventive Principle:

Principle #6Universality (Multi-functionality)

Solution Approach 2:

The patent combines status reporting, command acknowledgment, and state synchronization into a single unified status packet exchange mechanism. This merging eliminates the need for separate back-channel mechanisms and reduces the complexity of the embedded controller by consolidating multiple functions into one streamlined process.

Inventive Principle:

Principle #5Merging (Combining)

3Reliability

If the host computer and embedded controller track command-response pairs, then command execution can be monitored, but control of concurrent activities becomes complex

Engineering Contradiction:

Improvecommand execution trackingVSAvoidconcurrent activity control

Core Design Contradiction:

ReliabilityVSDevice complexity

Solution Approach 1:

Instead of the host computer tracking responses to its commands, the embedded controller proactively includes command execution status in its periodic status packets. This inversion shifts the tracking burden from the host to the embedded controller, which already maintains internal state information, thereby simplifying concurrent activity control.

Inventive Principle:

Principle #13The other way round (Inversion)

4Reliability

If synchronous command-response communication is used, then command completion can be detected, but the load on the embedded controller increases particularly during diagnostic tests

Engineering Contradiction:

Improvecommand completion detectionVSAvoidembedded controller load

Core Design Contradiction:

ReliabilityVSProductivity

Solution Approach 1:

The embedded controller proactively sends periodic complete status packets that include command execution status, eliminating the need for the host to send frequent read commands. This reduces the embedded controller's communication load and allows it to focus on executing scheduled tasks and processing commands without interruption.

Inventive Principle:

Principle #13The other way round (Inversion)

Data Source

PatentUS20100332953A1Instrument control system and methods

Publication Date: 2010.12.30 AGILENT TECHNOLOGIES INC

AI summary

Methods, systems and computer readable media for controlling an instrument in communication with a host computer are provided. Operations of an instrument that must be completed on schedule are controlled via an embedded controller embedded in the instrument. A complete status packet is sent to a host computer from the embedded controller Periodically, the embedded controller repeats the sending of a complete status packet to the host computer, wherein status values in the complete status packet are updated with each iteration of sending a complete status packet.