I'm a newbie to sigrok/pulseview, so take my comments with a grain of
salt. In fact, I didn't even know about the timing PD until this post.
That's a hallmark of good software: There's always new, useful features
to discover. I'm also on pulseview 0.4.2 which seems not to have some of
the (more recent?) features mentioned in this thread.
But if anyone's interested in my comments ...
On 1/23/21 4:26 AM, Gerhard Sittig wrote:
I also keep finding myself disabling the average feature (set
period to zero) as one of the first steps after adding this
decoder. Am using the cursor when I'm interested in a single
period, or between conditions that a human can identify but a PD
cannot. Am using the 'timing' PD when I need "all" (actually:
many or most) distances of edges or periods of waveform cycles,
like during creation of another decoder, or when comparing
hardware implementations of clocked protocols to software
bitbang. Have never used the frequency nor the averaging parts,
but there will be users who do, and do a lot of that, for sure.
Me too. My first reaction using the decoder was, "I don't need these
averages. How do I get rid of them?" On a total guess I set "Averaging
period" to zero, and, voila! But very non-intuitive. I'd suggest a
separate on/off checkbox, and would like the default to be off, but the
latter is just me (and maybe Gerhard Sittig).
My vote is to keep it as a single decoder. I don't think there are too
many options, and even if there were it's simpler to have them all in
one place instead of remembering/experimenting to see if timing PD
flavor "A", "B", or "C" is the one you want. Even if they're
informatively named.
I'd like to see an option for "only high"/"only low" periods, i.e.
"Edges to check" with "from rising to falling"/"from falling to rising".
I can't figure out any way to do this with the current (again, possibly
old) version I have.
That's about it. Otherwise, the timing PD is great. As is the rest of
pulseview. Except for the trace colors. :( Someday I'll find the time
and see if I can hack in bright, saturated trace colors on a black
background, like every other logic analyzer GUI in the world. Much more
readable. (But then you can't tell a constant high from a constant low?
Easy: Dim white lines separating the traces, or alternating black and
dark gray backgrounds, like the green and white stripes on dinosaur-era
mainframe fanfold tractor feed paper.)
But that's another issue entirely. ;)
_______________________________________________
sigrok-devel mailing list
sigrok-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/sigrok-devel
