Mobile Machine Test Drive Scripts for Reliable Repair Verification
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
The increasing complexity of computer-controlled systems in mobile machines requires technicians to perform test drives with tools that provide drive cycle procedures to ensure proper repair, but existing solutions do not efficiently provide this functionality.
Innovation Solution
A method and system that determine a test drive script with an ordered sequence of drive cycle procedures, monitored by a tool during a test drive, to guide the technician in controlling the mobile machine and verifying the repair effectiveness.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If a technician uses a tool with drive cycle procedures to monitor ECU controlled systems during test drive, then the reliability of repair verification is improved, but the device complexity increases
Solution Approach 1:
The system allows the mobile machine itself to provide the drive cycle procedures through its own electronic control units. The ECU controlled systems generate and manage the test protocols, eliminating the need for external tools to contain complex drive cycle logic. The technician simply needs to connect the tool to retrieve and execute procedures that are already stored in the vehicle's own control systems.
2Measurement precision
If a technician brings a monitoring tool during test drive, then the measurement precision of electronic system status is improved, but the ease of operation deteriorates
Solution Approach 1:
The system merges the monitoring tool with the mobile machine's own diagnostic capabilities. The tool communicates with the ECU controlled systems that are already integrated into the vehicle, combining external monitoring hardware with the vehicle's embedded control software. This integration allows precise monitoring without requiring the technician to manually manage separate monitoring and control systems.
3Productivity
If the test drive script includes detailed drive cycle procedures, then the productivity of repair verification is improved, but the device complexity increases
Solution Approach 1:
The drive cycle procedures are prepared and stored in advance within the mobile machine's ECU controlled systems. All the complex test sequences, timing requirements, and monitoring parameters are pre-configured in the vehicle's own control units before the technician arrives. This eliminates the need for the external tool to contain or process complex drive cycle logic during the actual test drive.
Solution Approach 2:
The ECU controlled systems act as an intermediary between the simple external monitoring tool and the complex requirements of drive cycle execution. The vehicle's own control units interpret and manage the detailed test procedures, translating high-level monitoring requests into specific drive cycle actions and evaluations, thereby shielding the external tool from complexity while maintaining high productivity.
Data Source
AI summary
A method includes determining a test drive script (TDS) to perform while a tool monitors an electronic system in a mobile machine during a test drive of the mobile machine. The TDS includes an ordered sequence of drive cycle procedures (DCPs). The ordered sequence of DCPs begins with an initial DCP and ends with a final DCP. Each DCP is indicative of a respective mobile machine state. The TDS includes a first particular DCP associated with both a first particular mobile machine state and a first condition pertaining to the first particular mobile machine state. The method also includes outputting a representation of at least a portion of the TDS. Additionally, the method includes determining and outputting one or more of: status information corresponding to achieving the first particular mobile machine state or status information corresponding to achieving the first condition pertaining to the first particular mobile machine state.