开云体育

Thanks, Rune. I didn't realize there was an alpha setting in the
color-selection window. Good to know!

Playing some more with the 0.0.5 release (and really enjoying it), here
are some more comments...

First, a possible bug: I cannot import and display an S1P file as my
reference plot (note: this file opens in other apps I have that read S1P
files), and when I try this my currently-displayed sweep is then overlayed
on itself as the reference sweep. I am attaching the S1P file and a
screenshot of the console window. (The number of points and frequency
span that the NanoVNA has been set to are the same as the sweep I've made
(1-60 MHz, 101 points). Perhaps your import routine is getting confused by
the comment lines at the start of the file?)

Additional items for the wish list...

1. If importing a file as reference or sweep, it would be nice to display
the file name(s) in the window, too. (I will often use screen-captures of
my VNA data to illustrate a point, and having the file names visible in the
screen captures makes the data traceable back to the original files, and
thus verifiable, should there be a question, months or years later).

2. For the mouse-cursor, also calculate the equivalent series and
parallel components. I'm attaching a screenshot of an S1P viewer I often
use that includes this feature -- the data is on the right (note that the
series reactive component is shown as a negative inductance. This is a
bug, in my opinion. It should be shown as a positive capacitance).

3. Somewhere show (or be able to show) the number of points in the sweep.

4. The ability to place multiple independent cursors on either the
reference and/or the current sweep, and display info for all cursors, would
be nice. Perhaps four or five cursors, total, each of which could be
placed on either sweep.

5. By the way -- can the reference sweep be a different number of points
than the displayed sweep (just wondering what will happen if I want to
compare a NanoVNA sweep with a capture from my 8753C, whose default is 201
points)?

Again, great work!

- Jeff, k6jca

Hi Rune,

Here's the error messages

$ python3.7 nanovna-saver.py
Traceback (most recent call last):
File "nanovna-saver.py", line 19, in <module>
from PyQt5 import QtWidgets
ModuleNotFoundError: No module named 'PyQt5'

$ python3.7 NanoVNASaver.py
Traceback (most recent call last):
File "NanoVNASaver.py", line 22, in <module>
import numpy as np
ModuleNotFoundError: No module named 'numpy'

Strange thing is, I have the required modules installed, as I needed them
for another application.

So I'm not sure why the three required modules appear to be invisible for
your Nano VNA software.

Strange...

73 de Andy

Just for info, I am having difficulty getting the Python software to run
the app.

Same errors as other posters have mentioned.

Upgrade Python on my Linux Mint and I appear to have all the correct
additional modules.
Tried the same on my Raspberry Pi, same errors.

Other Python apps appear to work fine.

Not complaining (I think it's a joy to see all the enthusiasm and
"overnight" software pop up), so this message is just to let others who
are struggling to know that they are not the only ones ;-)

73 de Andy

Try as I might, I cannot keep the pin+back assembly still while screwing
the short and/or load calibration piece down in the SMA socket!

Should I add some grip to their backs, with glue or solder? Should I file
out a slit for a screwdriver?

Or just give up?

you initially waved around a complaint which might as well be a
surrealist's dream: your HT will be un-burnt when you fill your bathtub
with brightly colored screwdrivers. and now you make rude demands? consider
yourself lucky the group may respond kindly to you.

back to the matters at hand: a technique for measuring output impedance of
an audio amp may not at all be used with the Ailunce HT for the simple fact
the audio amplifier will happily operate open circuit, while the HT may be
very unhappy indeed and release all the magic smoke from its power
amplifier.

except for the aforementioned magic smoke release warning, the simple and
direct method of measuring output impedance (or "source impedance") is to
compare the open circuit operating voltage with operating voltage under
load.

the load value will be equal to the source value when the operating
voltage under load is one-half of the open circuit operating voltage.

- 1001001 (base 2) -

Hi Rune,

I have downloaded your release 0.0.5 and am checking it out. Some
comments:

1. At first I thought the Mouse Cursor was broken -- I was clicking in
the S11 Smith Chart plot and I wasn't seeing its marker. Then I discovered
accidentally that its marker would appear if I instead clicked in the S11
Return Loss plot. Any chance to get this marker to appear no matter which
plot we first click our mouse in?

2. Also, in the version I downloaded this morning from the master (not
release) folder (a version without the verbose Mouse cursor and dots for
Markers in lieu of triangles), I could move the mouse cursor in the S11
Smith Chart plot. I cannot do this now -- I have to go to the S11 Return
Loss plot to move it.

3. Reference Plot color -- works fine, but I notice that the color
displayed in the "color button" is a very grayed-out version of the color I
select. Not sure why it's grayed-out, as the color of the actual reference
plot is fine.

4. The only way I seem to be able to get Markers 1 and 2 to appear on the
screen is if I first type a frequency into their boxes, and then the
markers appear (which might be your intention). But I know that the
frequency I type isn't the actual frequency that the marker is pointing to
(which I can read by ovelaying the mouse cursor on top of either Marker 1
or 2). For example, for Marker 2 I had typed in 500000000 (i.e. 500 MHz).
But the actual frequency of the sample is 506.936 MHz. Would be nice if
the displayed frequency were the actual frequency.

5. Being able to transfer the mouse cursor's frequency into either Marker
1 or Marker 2 would be a nice feature.

6. Would be nice to step the mouse cursor (and/or the markers) with the
keyboard arrow keys for "fine tuning".

7. Heartily agree with adding averaging.

8. A word of caution regarding adding C0 (and C1, C2, C3) for the open
calibration standard. As has been mentioned in other threads, there might
be a 50 femtofarad value already hard-coded into the NanoVNA software as
C0. Adding an external C0 parameter, without being able to zero out the
existing C0, will defeat the purpose of adding the new C0 value. (If this
is an issue, I would suggest contacting Hugen -- he might be able to
confirm the existance of this hard-coded value. If it an existing
compensation already exists, there might be some way to cancel out its
effect -- maybe by adding to it a negative (!!!) 50 femtofarad value?).

9. It would be nice if the release version appeared someplace in the app.

And finally...excellent job!

- Jeff, k6jca