Hi Tom,
good suggestion! I'll have a look, and there should be plenty of room for
it! :-)
--
Rune / 5Q5R
toggle quoted message
Show quoted text
On Mon, 23 Sep 2019 at 07:31, Tom VA7TA <tma.7ta@...> wrote:
Hi Rune,
I have made a large number of routine impedance measurements using
your V0.0.10 exe binary under Windows 10 Pro 64b. I have not encountered
any stability problems and in general think it works wonderfully well -
thank you!
One part of the GUI that I didn't understand intuitively the first
few times I used it was the purpose of the "Segments" box. I changed it and
nothing seemed to happen. I of course noticed immediately that it is a
multiplier for the number of steps in the sweep once I changed it and then
happened to do a calibration which shows the number of steps in the sweep.
I decided I would like to make a suggestion that I hope is worthy of
consideration.
It occurred to me that it would be obvious to the user that the
segments setting increases the sweep frequency resolution if the number of
Hz per step could be shown. Additionally I think the provision of the
"Hz/Step" information would be useful in some situations. For example when
sweeping a network with narrow high Q responses the user may wish to select
a segments setting that provides a sufficiently small step size to ensure a
narrow peak or null is not missed without increasing the sweep time any
more than necessary. A second advantage for providing the "Hz/Step" data is
that it would provide immediate indication of how a change of the segments
setting changes the sweep resolution. This feedback would make the setting
more user intuitive I think.
Considering that the number of segments would never exceed two
digits and the number of Hz per step would never exceed 7 digits there
might be room to fit the two boxes on the existing segments line within the
GUI. If for example the "Segments" label were abbreviated to "Segs." with a
two digit box then possibly there would be room for another label something
like "Hz/Step" followed by a 7 (or 9 if 2 comma delimiters) digit box on
the same line. Just might be one of many possible ways to implement it
without impacting the existing GUI layout very much.
Thanks again for your great contribution - "NanoVNA-Saver" really
enhances the usefulness of my nanoVNA for what I intend to use it for!
Enjoy!
Tom
VA7TA