|Anonymous | Login | Signup for a new account||2017-03-26 20:57 UTC|
|Main | My View | View Issues | Roadmap | Repositories|
|View Issue Details|
|ID||Project||Category||View Status||Date Submitted||Last Update|
|0000285||Firmware||GP IO and GP code||public||2011-10-02 20:53||2011-11-13 13:00|
|Target Version||0.5.0||Fixed in Version|
|Summary||0000285: Abstract Out Common Functionality In ADC Processing Code|
|Description||Migrate existing core vars code to use new GP ADC functions. Two main typs for a start:|
Lookup tables, provide 4, link IAT, CHT, and MAT to one of them by default. Allow users to connect any ADC channel to any lookup table with any data in it and log it or use it in other parts of the software.
Linear interpolations, BRV, WBO2, etc, make this be done with one piece of code that is unit tested and config driven.
Provide N config regions in fixed flash config for setting up these interps and allow the GP IO stuff to use those configs. EG, battery voltage settings can be shared across multiple ADC pin inputs for multiple voltage readings, assuming the circuits match, and if not, they can use custom ones.
Provide a lookup service of some kind to discover these for settings side stuff and present the outside application with an ID number with which the code can get a pointer (no direct memory refs outside the device)
This will be a solid start in the direction of top notch GPIO code/UI.
Burn time verification code should prevent pointers to ADC pins other than those assigned being used for core features where pins are fixed to guarantee compatibility and OOTB functionality (BRV, IAT, CHT, MAT, TPS, etc, see 0000190)
|Tags||No tags attached.|
|Issue Type||New Feature|
|Risk of Breakage||medium|
|Copyright © 2000 - 2011 MantisBT Group|