Ignition Timing Control Adapts to Fuel Type
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Conventional ignition timing control devices for watercraft internal combustion engines require manual selection of ignition timing characteristics based on fuel type, leading to potential inefficiencies and reduced fuel efficiency if the wrong setting is chosen, especially when using biofuels which are more environmentally friendly but can cause knocking.
Innovation Solution
An ignition timing control device with a processor and storage that automatically selects between different ignition timing maps based on the fuel type and rotational speed, applying timing retardation or advancement corrections to prevent knocking and optimize engine performance and efficiency.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If manual selection of ignition timing characteristics is implemented, then adaptability to different fuel types is improved, but ease of operation deteriorates due to potential user error
Solution Approach 1:
The ignition timing control device automatically detects the fuel type and selects the appropriate ignition timing map without requiring manual user input. The processor autonomously determines whether to apply the first ignition timing map (for fuels less likely to cause knocking) or the second ignition timing map (for fuels more likely to cause knocking), thereby eliminating user error while maintaining adaptability to different fuel types.
Solution Approach 2:
The system incorporates a knocking detection mechanism that provides feedback on actual engine knocking conditions. Based on this feedback, the processor dynamically adjusts the ignition timing selection, switching between the first and second ignition timing maps as needed. This closed-loop feedback ensures optimal ignition timing is maintained regardless of fuel type variations.
2Use of energy by moving object
If ignition timing is advanced for biofuel efficiency, then fuel efficiency is improved, but harmful factors increase due to knocking
Solution Approach 1:
The ignition timing control device dynamically adjusts ignition timing based on detected knocking conditions and rotational speed. The processor selectively applies timing advancement corrections from the second ignition timing map only when knocking is not detected, while applying timing retardation corrections from the first ignition timing map when knocking is detected. This dynamic adjustment optimizes fuel efficiency while preventing harmful knocking.
Solution Approach 2:
The system changes the ignition timing parameters by selecting between two distinct ignition timing maps stored in memory. The first map contains more conservative timing parameters for knocking-prone conditions, while the second map contains more aggressive timing parameters for optimal efficiency when knocking is absent. The processor switches between these parameter sets based on real-time knocking detection, thereby optimizing fuel efficiency while controlling knocking.
Data Source
AI summary
An ignition timing controller includes a storage and a processor configured or programmed to function as an ignition timing control section and a knocking determining section. The storage stores at least one of a first ignition timing map associated with a first fuel or a second ignition timing map associated with a second fuel more likely to cause knocking of an internal combustion engine than the first fuel. The ignition timing control section controls the ignition timing based on the first ignition timing map by executing a timing retardation based on the first ignition timing map when it is determined that knocking of the internal combustion engine has occurred. The ignition timing control section controls the ignition timing of the internal combustion engine based on the second ignition timing map by executing a timing advancement correction based on the second ignition timing map when it is determined that the knocking of the internal combustion engine has not occurred.