Combine Display Runtime Capture Before Kill-Stall Data Loss
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Agricultural combine operators face challenges in optimizing performance settings due to the obscuration of real-time data during the kill-stall procedure, leading to errors in data recall and subjective analysis, which affects crop losses and operational efficiency.
Innovation Solution
A method and system that captures and records runtime data before initiating the kill-stall procedure, ensuring the data is saved without prompts, allowing for accurate documentation and analysis post-harvest.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Ease of operation
If the display shows digital prompts and menus during the kill-stall procedure, then the operator can confirm and control the kill-stall operation, but the real-time output data related to crop losses, vehicle performance, and vehicle settings becomes obscured and inaccessible
Solution Approach 1:
The system creates a visual copy (screenshot) of the display data before the kill-stall procedure obscures it. This copy is then made available to the operator after the procedure completes, allowing review of the real-time output data without requiring the operator to remember values during the procedure. The screenshot serves as an accurate record that can be analyzed later.
Solution Approach 2:
The system performs the data capture action preliminarily - taking the screenshot before the kill-stall procedure begins or during its initial stage when data is still visible. This preliminary capture ensures the data is preserved before the display transitions to showing only kill-stall prompts and menus.
2Productivity
If the operator relies on mental recall of display data during the kill-stall procedure, then the procedure can be completed quickly, but errors increase and accuracy decreases
Solution Approach 1:
Instead of relying on the operator's memory, the system automatically creates and preserves an accurate visual copy of the display data. This eliminates the need for mental recall while maintaining procedural speed, as the operator can review the screenshot afterward without having memorized values during the procedure.
Solution Approach 2:
The system provides feedback by presenting the captured screenshot to the operator after the kill-stall procedure. This allows the operator to verify the recorded data against their expectations and use the accurate information for analysis, eliminating the errors associated with imperfect memory recall.
3Adaptability or versatility
If multiple kill-stall procedures are performed throughout a harvesting session, then performance optimization can be achieved, but the accumulation of unrecorded data losses increases
Solution Approach 1:
The system creates and stores visual copies of display data from each kill-stall procedure performed during the harvesting session. These screenshots serve as historical records that can be reviewed later, allowing the operator to analyze performance across multiple procedures without losing any data information.
Solution Approach 2:
Rather than allowing data to be lost when the display transitions during multiple procedures, the system recovers and preserves the data in screenshot form. This enables the operator to recover and analyze historical performance data from any number of kill-stall procedures performed throughout the day.
Data Source
AI summary
A method of operating an agricultural vehicle includes the steps of: generating active runtime data based on performance of the vehicle, receiving a signal to activate a kill-stall procedure of the vehicle, recording the active runtime data as recorded runtime data prior to kill-stalling the vehicle, and kill-stalling the vehicle.