Numerical Control Apparatus Event-Triggered Diagnosis Logging
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing numerical control systems face increased CPU load and performance deterioration due to continuous logging of diagnosis information, even when no malfunction occurs, and struggle with setting accurate logging start and end conditions for unknown malfunction timings.
Innovation Solution
A numerical control apparatus with a detection unit to identify preset events, a condition generation unit to generate determination conditions based on changing numerical control information, and a logging processing unit to initiate logging when specific conditions are met, allowing for efficient acquisition of diagnosis information near malfunction occurrences without continuous logging or fixed user-set timings.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Loss of information
If continuous logging of diagnosis information is performed, then complete diagnosis data is available, but CPU load increases and performance deteriorates
Solution Approach 1:
The system performs logging periodically or event-triggered rather than continuously. The detection unit monitors for specific events (malfunction occurrences) and triggers logging only when needed, converting continuous action into periodic or conditional action to reduce CPU load while maintaining necessary diagnostic capability
Solution Approach 2:
The system prepares logging buffers and detection mechanisms in advance before malfunction occurs. The detection unit continuously monitors for events, and logging resources are pre-allocated, so when a malfunction is detected, the system can immediately start logging without continuous operation, reducing overall CPU burden
2Adaptability or versatility
If logging is performed for multiple kinds of malfunction, then comprehensive diagnosis information is acquired, but large amount of data must be logged continuously
Solution Approach 1:
The system segments the logging process by malfunction type or event category. The detection unit identifies specific event types, and the logging unit segments data collection to only log information relevant to the detected event type, reducing overall data volume while maintaining comprehensive coverage across multiple malfunction kinds
Solution Approach 2:
The system applies different logging strategies or data collection depths based on the type of malfunction detected. For certain critical malfunctions, detailed logging is activated, while for less critical events, simplified logging is used, optimizing the balance between diagnostic coverage and data volume
3Ease of operation
If user sets fixed logging start and end conditions, then logging can be controlled, but it is difficult to forecast and set conditions for unknown malfunction timings
Solution Approach 1:
The system performs self-diagnosis and automatically determines when to start and end logging based on detected events. The detection unit monitors system state and autonomously triggers logging when malfunction indicators are detected, eliminating the need for users to manually forecast and set conditions for unknown malfunction timings
Data Source
AI summary
A numerical control apparatus has a detector, a condition generator, and a logging processor. The detector detects occurrence of a preset event. The condition generator acquires, as a reference value, first numerical control information at a timing when the occurrence of the event is detected, and performs preset first arithmetic processing by using the reference value to generate a first determination condition. When the first numerical control information satisfies the first determination condition, the logging processor starts a process of logging second numerical control information.