Summary: | libsigrok does not communicate precision and accuracy data | ||
---|---|---|---|
Product: | libsigrok | Reporter: | mrnuke <mr.nuke.me> |
Component: | Other | Assignee: | Nobody <nobody> |
Status: | RESOLVED DUPLICATE | ||
Severity: | normal | CC: | martin-sigrokbugs, stefan.bruens, uwe |
Priority: | Normal | ||
Version: | unreleased development snapshot | ||
Target Milestone: | --- | ||
Hardware: | All | ||
OS: | All |
Description
mrnuke
2012-12-19 19:38:52 CET
Merging this with #640. Parts of the "analog2" support was implemented already, the remaining parts are tracked in #640. *** This bug has been marked as a duplicate of bug 640 *** Although the current metadata for analog samples is quite good already, I miss one attribute: range or min/max Multimeters provide data as integers, but both an 22000 and an 6000 count DMM will output an int16_t. Scopes output 8 to 16 bit of sample data, but an 14 bit value may be left or right aligned, thus range may be either 0...65532 or 0...16383. Float samples are typically in a -1.0 ... +1.0 range, but may as well be outside of this range. This is an attribute mostly useful for visualization, it does not affect physical interpretation. It should be specified as either two integers (min/max) or two doubles, depending on is_float, and refer to the raw sample value. (In reply to comment #2) Stefan, yours is a good point and I have filed a new bug #729 for this. |