Common Rail PRV Event Counting During Engine Shutdown
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Common rail fuel systems face challenges in accurately detecting pressure relief valve (PRV) opening events, particularly when the controller resets or turns off before the engine speed reaches zero, leading to potential system damage due to undetected PRV openings.
Innovation Solution
Implementing a controller with sensors and modules to monitor rail pressure and engine speed, incrementing a PRV opening events counter, and determining if the counter exceeds a threshold to trigger repairs or replacements.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Measurement precision
If the controller monitors PRV opening events using traditional methods, then the system structure remains simple, but the detection accuracy of PRV opening events deteriorates when the controller resets or turns off before engine speed reaches zero
Solution Approach 1:
The system performs preliminary actions by detecting engine stop conditions and predicting potential PRV openings before they occur. The controller monitors engine speed and identifies when the engine is stopping, then proactively checks for PRV opening events that may have occurred during the shutdown transition, ensuring accurate detection even when the controller resets.
Solution Approach 2:
The system implements feedback mechanisms by continuously monitoring engine speed, controller status, and pressure differential data. When the engine stops or the controller resets, the system uses feedback from these parameters to determine whether a PRV opening event occurred, ensuring accurate detection through continuous system state evaluation.
2Reliability
If the controller continuously monitors engine operation to detect PRV openings, then the reliability of PRV status tracking improves, but the energy consumption increases
Solution Approach 1:
The system employs periodic monitoring instead of continuous monitoring by checking for PRV opening events at specific intervals and at critical transition points (engine start, engine stop, controller reset). This periodic approach maintains reliable detection of PRV openings while significantly reducing the energy consumption associated with continuous monitoring.
Solution Approach 2:
The controller performs preliminary checks at predetermined moments (such as when the engine stops or during shutdown transitions) to detect PRV opening events. By focusing monitoring efforts on these critical moments rather than continuously monitoring, the system maintains high reliability in PRV status tracking while minimizing energy consumption.
3Measurement precision
If the system implements comprehensive monitoring of controller reset conditions, then the accuracy of PRV opening event detection improves, but the device complexity increases
Solution Approach 1:
The system extracts and isolates the specific monitoring function for PRV opening events from the overall controller operations. By creating a dedicated detection mechanism that focuses solely on identifying PRV openings during controller resets or engine shutdowns, the system achieves high detection accuracy without adding significant complexity to the overall control system.
Solution Approach 2:
The system implements preliminary detection logic that activates specifically when controller reset conditions are anticipated (such as during engine shutdown sequences). This targeted approach allows the system to accurately detect PRV opening events at critical moments without requiring comprehensive monitoring of all controller operations, thereby maintaining detection accuracy while limiting complexity increases.
Data Source
AI summary
In one instance, disclosed herein is a common rail fuel system for an engine system including an engine, the common rail fuel system comprising a controller configured to: detect a start of the engine; increment a PRV opening events counter; determine if a low speed condition of the engine was met before the controller turns off based on sensor data received from a rail pressure sensor or sensor data received from an engine speed sensor; in response to determining that the low speed engine condition was met before the controller turned off, decrement the PRV opening events counter; determine if the PRV opening events counter has exceeded a PRV opening events threshold; and in response to determining that the PRV opening events counter has exceeded the PRV opening events threshold, output a signal indicating that the PRV should be repaired or replaced.