On Thu, 2021-07-01 at 23:44 +0100, Martin Ling wrote:
>
> On Thu, Jul 01, 2021 at 07:12:45PM +0100, John wrote:
> >
> > A previous version of the fluke-45 driver did check for the echo
> > as you noticed. But did so in an inappropriate location, where a
> > workaround for one rarely used device kept breaking several other
> > people's more popular devices. That's why the test got disabled,
> > and recently was removed. The available information at the time
> > strongly suggested that automatic detection would not be
> > possible. Would be nice if we could have the best of all: other
> > devices unaffected,_and_ reliable operation for the fluke-45
> > device,_and_ helpful diagnostics to users when a known fatal
> > condition is seen. Can we get there, please?
>
> The current architecture of libsigrok makes this difficult at the
> moment. Please see the following bugzilla entry for some previous
> thoughts on this:
> https://sigrok.org/bugzilla/show_bug.cgi?id=1276
Don't think that this is related (the Bugzilla item that you
reference above is about unified or common SCPI device
identification, which is totally not the issue here).
The Fluke-45 problem with the echo breaking the measurements is
different. Available information only allows to _guess_ what the
actual issue is, but it's none of what was assumed before. Only
the log can eliminate the doubt and unblock the issue, but the
user specifically chose to not provide the information. Not by
coincidence or lack of awareness, but (reported by himself)
consciously and intentionally so, to "protect" others from the
evil information. And no level of escalation from "show the log"
to "SHOW the log" to "SHOW THE LOG, DAMMIT!" has made the
information available. That's why I'm so bitter. Don't know how
else to communicate that the data is so important to have, to
actually help any user of that device.
I'd really prefer to fix the actual problem and rub the cause of
failed measurements in every future user's face, instead of
putting a weak comment on a wiki page that users will keep
missing. But without the essential information, and no apparent
way of getting it ... all hope of fixing the issue is lost, and
all future users are condemned to face the same issue and have to
guess again, or give up. :( That wiki comment is just a nice
addition, but totally not the solution.
If anyone knows how to communicate to Stuart that making the log
available that he has is the most important help he can provide,
PLEASE go ahead and help getting it. See the June thread for the
motivation.
virtually yours
Gerhard Sittig
--
If you don't understand or are scared by any of the above
ask your parents or an adult to help you.
_______________________________________________
sigrok-devel mailing list
sigrok-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/sigrok-devel
