On Tue, Sep 30, 2014 at 12:24:36PM +0300, Janne Huttunen wrote:
> Hi!
>
> I own an LCR meter with a USB connection and I am contemplating
> about implementing support for it in sigrok.
Great !
> [...]
> 1. Dual display
>
> The meter in most modes shows two measurements at the same time
> and also exports both of those in the protocol. It looks like
> the serial DMM currently does not support this. It probably
> would not be too much work to add support for it, but is it
> "wanted"?
Yes, it is wanted !
Just have a look at the brymen-bm86x driver for how to do it. It is a
dual display DMM.
It is just a matter of sending 2 analog packets, each one with its own
MQ and unit.
> 2. Measured quantities
>
> The meter (obviously) measures inductance, capacitance and
> AC and DC resistance, but it can additionally calculate quality
> factor, dissipation factor, ESR and phase angle.
Yes, quite common for an LCR meter. Just add new MQs and units for the
ones that are not yet in sigrok.
> Furthermore
> in relative mode the meter calculates the difference between
> the reference and current measurements (in %) and supports
> alternating between the current measurement and the reference
> with a touch of a button.
This one looks a bit more special...
You might add a new MQ for it, but you could also leave it alone for now
until you have a first working version of your driver merged into
libsigrok, and think about it afterward...
> The measured quantity can also be either selected by the meter
> based on the dominating factor or forced by the user. In a way
> this information is similar to the "autoranging", but in this
> case it's just not about the "range". Should this be exported
> and if so, how?
A new flag, similar to autorange, would be good, even if not essential.
> 3. Test signal frequency
>
> The meter supports using different (user selectable)
> frequencies when making a measurement. This is not
> strictly a "measured" quantity (more like configuration),
> but the information is still present in the protocol.
> Should it be exported somehow?
It should definitely be exported !
Not sure what would be the best way. Maybe as a devopts ? Something like:
SR_CONF_FREQUENCY | SR_CONF_GET | SR_CONF_LIST,
> 4. Measurement model
>
> The meter can use either serial or parallel circuit model when
> making the measurement. The model can be either automatically
> selected by the meter or forced by the user. The protocol tells
> if autoselection is on and which model was ultimately used to
> get the result. Should this information also be exported
> somehow?
Yes, probably as a mqflag.
> 5. Sorting
>
> The meter has part sorting mode where a reference value and
> tolerance limits are entered to the meter and then every
> subsequent measurement returns PASS/FAIL status based on
> whether the value is between the tolerance limits. The set
> tolerances and the status are part of the serial protocol.
> Should this functionality be exported somehow?
I would forget about it for now.
> 6. Calibration mode
>
> There is also an internal calibration mode in the meter and
> the related statuses are shown in the serial protocol, but I
> don't think this is a relevant thing to export in sigrok.
> During the procedure the user needs to interact with the meter
> anyways and the wire protocol just shows the same statuses
> (what to do next and PASS/FAIL) as the display on the meter
> itself, so there doesn't seem to be any too interesting
> additional information present in there.
Agreed.
Aurel
------------------------------------------------------------------------------
Meet PCI DSS 3.0 Compliance Requirements with EventLog Analyzer
Achieve PCI DSS 3.0 Compliant Status with Out-of-the-box PCI DSS Reports
Are you Audit-Ready for PCI DSS 3.0 Compliance? Download White paper
Comply to PCI DSS 3.0 Requirement 10 and 11.5 with EventLog Analyzer
http://pubads.g.doubleclick.net/gampad/clk?id=154622311&iu=/4140/ostg.clktrk
_______________________________________________
sigrok-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/sigrok-devel
