Anonymous | Login | Signup for a new account | 2021-01-25 10:13 UTC | ![]() |
Main | My View | View Issues | Roadmap | Repositories |
View Issue Details [ Jump to Notes ] | [ Print ] | ||||||||||
ID | Project | Category | View Status | Date Submitted | Last Update | ||||||
0000137 | Firmware | Scheduler (Inj/Ign) | public | 2011-06-15 15:21 | 2011-06-28 19:00 | ||||||
Reporter | Fred | ||||||||||
Assigned To | Fred | ||||||||||
Priority | normal | Severity | minor | Reproducibility | have not tried | ||||||
Status | assigned | Resolution | open | ||||||||
Platform | OS | OS Version | |||||||||
Product Version | |||||||||||
Target Version | Future | Fixed in Version | |||||||||
Summary | 0000137: Add double scheduling of actual ignition point | ||||||||||
Description | Once from within output code and again, overriding from within decoder scheduler to make timing more accurate where possible. Particularly useful on high event count stuff and almost not on distributor stuff depending on layout of pattern and engine. Add code to reschedule the ign time (end of dwell) at decoder time and override existing scheduling, think carefully about that, how far and close events and queues of sched data may need to work. Or other mechanisms of achieving this. Accuracy is already good, this will only affect dynamic accuracy. Need to think about cutting dwell short and consequences of that. Probably a configurable on/off feature for that reason. | ||||||||||
Tags | No tags attached. | ||||||||||
FirmwareVersion | |||||||||||
Issue Type | Improvement | ||||||||||
Risk of Breakage | very high | ||||||||||
Attached Files | |||||||||||
Copyright © 2000 - 2011 MantisBT Group |