Vacuum Pump Controller Event-Triggered State Data Collection

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Existing vacuum pump systems face challenges in timely collection of state information, leading to incomplete or missed event data due to inappropriate collection cycles, which hinders effective cause analysis during failures.

Innovation Solution

A vacuum pump and controller system that collects state information at specific points when the operating state of internal devices is switched, allowing for timely data recording in a non-volatile memory, thereby ensuring comprehensive event capture.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Ease of operation

If state information is collected periodically with a fixed collection cycle, then the collection process is simple and continuous, but the timing of collection may miss short-duration events or capture incomplete event data

Engineering Contradiction:
Improvesimplicity of collection processVSAvoidcompleteness of event data
Core Design Contradiction:
Ease of operationVSLoss of information

Solution Approach 1:

The system combines periodic collection with event-triggered collection. The information collection portion collects state information both periodically (at predetermined time intervals) and event-triggered (when operating state switches occur). This dual approach maintains the simplicity of periodic collection while adding the capability to capture complete event data including short-duration events that would be missed by periodic collection alone.

Inventive Principle:
Principle #19Periodic action

Solution Approach 2:

The control portion provides feedback about operating state changes to the information collection portion. When the control portion detects a switch in operating state (e.g., from gas inflow to gas outflow), it triggers the information collection portion to collect state information at that specific moment. This feedback mechanism ensures that event-triggered collection occurs only when necessary, maintaining efficiency while improving data completeness.

Inventive Principle:
Principle #23Feedback

2Reliability

If the collection cycle is shortened to capture faster events, then more events can be captured, but the storage burden increases and the system becomes more complex

Engineering Contradiction:
Improveevent capture capabilityVSAvoidcollection system complexity
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The system uses the control portion's existing operating state detection capability to trigger information collection. Instead of requiring a separate complex timing system to detect events, the control portion already monitors operating states and can trigger collection when switches occur. This self-service approach leverages existing system resources, avoiding additional complexity while improving event capture reliability.

Inventive Principle:
Principle #25Self-service

Solution Approach 2:

The information collection portion dynamically adjusts its collection behavior based on system state. Rather than using a fixed collection cycle, the system collects information both periodically and event-triggered. When operating state switches occur, collection is activated immediately. This dynamic approach allows the system to adapt its collection timing to actual event occurrences, improving reliability without requiring overly complex timing mechanisms.

Inventive Principle:
Principle #15Dynamics

3Quantity of substance

If only the latest state information is stored in non-volatile memory, then storage space is optimized, but historical event data is lost and cause analysis becomes difficult

Engineering Contradiction:
Improvestorage capacity utilizationVSAvoidavailability of historical data
Core Design Contradiction:
Quantity of substanceVSLoss of information

Solution Approach 1:

The system performs preliminary collection of state information at the moment of operating state switches before any potential failure occurs. By collecting state information event-triggered when switches occur, the system preserves historical data context that is crucial for cause analysis. This preliminary action ensures that when failures happen, the necessary historical state information is already captured and stored in the non-volatile memory.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The storage approach segments data collection into two types: periodic state information and event-triggered state information. The event-triggered collection captures specific moments when operating states change, creating discrete, meaningful data segments. This segmentation allows the system to store only the most relevant historical data points (state changes) rather than continuous data streams, optimizing storage space while maintaining adequate historical information for cause analysis.

Inventive Principle:
Principle #1Segmentation

Data Source

PatentUS12152605B2Vacuum pump and controller
Publication Date: 2024.11.26 EDWARDS JAPAN
  • US12152605B2 patent drawing
  • US12152605B2 patent drawing
  • US12152605B2 patent drawing

AI summary

A vacuum pump and a controller are provided with which state information of the vacuum pump is collected in a timely manner. In a controller, control portions control operating states of internal devices (such as a motor, a heater, and a cooling valve) located in a vacuum pump main body. An information collection portion collects the state information of the vacuum pump main body, and a recording processing portion records, in the non-volatile memory, the state information collected by the information collection portion. Also, the information collection portion collects the state information of the vacuum pump main body at a point in time at which a control portion switches the operating state of an internal device.