| Anonymous | Login | Signup for a new account | 2019-05-24 13:51 UTC |  |
| Main | My View | View Issues | Roadmap | Repositories |
| View Issue Details [ Jump to Notes ] | [ Print ] | ||||||||||
| ID | Project | Category | View Status | Date Submitted | Last Update | ||||||
| 0000273 | Firmware | Scheduler (Inj/Ign) | public | 2011-09-24 20:04 | 2014-02-18 23:06 | ||||||
| Reporter | Fred | ||||||||||
| Assigned To | Fred | ||||||||||
| Priority | normal | Severity | minor | Reproducibility | always | ||||||
| Status | acknowledged | Resolution | open | ||||||||
| Platform | OS | OS Version | |||||||||
| Product Version | 0.2.0-SNAPSHOT | ||||||||||
| Target Version | 0.2.1 | Fixed in Version | |||||||||
| Summary | 0000273: Split ADC Reading Force And Lose Sync Apart | ||||||||||
| Description | Currently they are done together and the time bases are not correct for either. Lose sync should have some short delay, perhaps configurable by the user inside some range of reasonable values such that a low RPM threshold can be set without negatively impacting delay to loss of sync. ADC force should work on a similar basis, but independently, furthermore once triggered it should read much more often, perhaps as fast as possible, to give a good picture in the log of what is going on when the decoder is not moving. | ||||||||||
| Tags | No tags attached. | ||||||||||
| FirmwareVersion | |||||||||||
| Issue Type | Improvement | ||||||||||
| Risk of Breakage | medium | ||||||||||
| Attached Files | |||||||||||
 Relationships |
|
 Relationships |
|
Notes |
| Copyright © 2000 - 2011 MantisBT Group |
 |
