| Anonymous | Login | Signup for a new account | 2019-10-14 10:57 UTC |  |
| Main | My View | View Issues | Roadmap | Repositories |
| View Issue Details [ Jump to Notes ] | [ Print ] | ||||||||||
| ID | Project | Category | View Status | Date Submitted | Last Update | ||||||
| 0000247 | Firmware | Analogue Inputs | public | 2011-08-19 18:42 | 2014-02-18 23:05 | ||||||
| Reporter | Fred | ||||||||||
| Assigned To | Fred | ||||||||||
| Priority | normal | Severity | minor | Reproducibility | sometimes | ||||||
| Status | assigned | Resolution | open | ||||||||
| Platform | OS | OS Version | |||||||||
| Product Version | 0.2.0-SNAPSHOT | ||||||||||
| Target Version | 0.2.1 | Fixed in Version | |||||||||
| Summary | 0000247: Make MAP sensor configuration both more robust and more flexible. | ||||||||||
| Description | The ability to do a linear transfer from X kPa to some negative value in the bottom end to ensure the slope of the line is correct brings the possibility of a negative output value trying to squeeze into a positive field. Not good. Only an issue if V in goes below V of 0 kPa, though. Which should never happen with a correctly setup sensor. Sensor out of range stuff is on the list of TTD so now it's a likely side effect of this issue. Probably this will consist of simple out of range default values such as 0 for too low and max for too high. Later alarms can be triggered by such events, or cuts or whatever else the user desires, I guess. | ||||||||||
| Tags | No tags attached. | ||||||||||
| FirmwareVersion | |||||||||||
| Issue Type | Improvement | ||||||||||
| Risk of Breakage | low | ||||||||||
| Attached Files | |||||||||||
 Relationships |
||||||||||||||||
|
||||||||||||||||
 Relationships |
|
Notes |
|
| There are no notes attached to this issue. |
|
Notes |
| Copyright © 2000 - 2011 MantisBT Group |
 |