开云体育

Hello Dick,

No, reset is confined to the register you are working. It will clear cal data in only that register. The frequency display range you entered will stay in tact. After reset, begin the cal.

Regards, Alan

Very nice.

You may want to post your system to the message group that is discussing test fixtures.
Part of the discussion raises the query on testing devices so full 2 port data is required.

I raised the TRL piece as I have used a combination of TRL and SOL or SOM on another vna.
David is correct that at lower frequency the cal is problematic. However, my fixtures lend themselves to TRL since there is no easy way to equip the DUT to coax.

So going forward with the nanovna will require a pair of decent bias tees or least ones that can be made part of the calibration process with minimum error and a switching system to turn the device end for end.

Thanks,

bryburns via Groups.Io wrote:

It seems to me that when the user clicks "Load" to pick a set of stored "Calibration standards" that you should "Apply" them automatically and not require the user to click "Apply." Just a thought.

Just a different thought. I might be incorrecr here, but from what I have seen of this machine in the last half-day, not automatically "applying" means you can look through the various calibration data -before- it gets applied to the machine, allowing one to pick out the correct (or at least the desired) set of numbers before committing them to the running memory (wiping out what was there).

One "extra" click does not seem all that onerous to me.

--
Wes Will
N9KDY

It looks like I cant add hash tag afterwards

On Wed, 16 Oct 2019 at 13:59, bryburns via Groups.Io <bryburns=
[email protected]> wrote:

On Wed, Oct 16, 2019 at 01:08 AM, Dr. David Kirkby from Kirkby Microwave
Ltd wrote:

I agree that the resistance of the short is unlikely to be an issue, but
the resistance will increase with frequency due to the skin effect.

Dave,

You are correct. I can't measure the skin effect resistance with anything
I have available. So, I am stuck with the best measurement I can make of
the short I use.

--
Bryan, WA5VAH

I would not worry about it.

I was mainly making the point that measuring DC resistance to 1 milli ohm
resolution is not hard with equipment most hobbyists would have.

Dave

--

Dr. David Kirkby,
Kirkby Microwave Ltd,
drkirkby@...

Telephone 01621-680100./ +44 1621 680100

Registered in England & Wales, company number 08914892.
Registered office:
Stokes Hall Lodge, Burnham Rd, Althorne, Chelmsford, Essex, CM3 6DT, United
Kingdom

Hi Bryan,
it does indeed help - I will be making better input validation for that
part of the interface. In fact, it's already on the list for 0.1.4. ;-)

If you want to save a log file, you should use -D logfile.txt - whereas -d
gives you console logging. I don't think traceback messages like the one
you posted here get saved to the log file, though, so it's better for me to
get your console log in crash cases like this.

Thank you very much! And I hope you try out 0.1.3 as well ;-)

--
Rune / 5Q5R

On Wed, 16 Oct 2019 at 15:51, bryburns via Groups.Io <bryburns=
[email protected]> wrote:

Rune,

I have noticed that you save the "Calibration standards" information in
the ".ini" file for nanoVNA-Saver. Great idea. I also observe that after
loading the information from the ".ini" file you still have to click
"Apply" on the Calibration window for the new values to be used even though
you can see them on the "Calibration" form. It seems to me that when the
user clicks "Load" to pick a set of stored "Calibration standards" that you
should "Apply" them automatically and not require the user to click
"Apply." Just a thought.

I started nanoVNA-Saver 0.1.2 in a command window using
"nanovna-saver.v0.1.2.exe -d testlog.txt" Here is the last several lines
on the screen after the crash when changing values on the Calibration form
in the "Calibration standards" box.

2019-10-16 07:38:41,567 - NanoVNASaver.SweepWorker - DEBUG - Sending
"updated" signal
2019-10-16 07:38:41,567 - NanoVNASaver.SweepWorker - DEBUG - Resetting
NanoVNA sweep to full range: 50000 to 900000016
2019-10-16 07:38:41,636 - NanoVNASaver.SweepWorker - DEBUG - Sending
"finished" signal
2019-10-16 07:38:54,382 - NanoVNASaver.Calibration - DEBUG - Loading
calibration no 0
2019-10-16 07:38:54,383 - NanoVNASaver.Calibration - INFO - Loading:
HighOrderForBNC
Traceback (most recent call last):
File "NanoVNASaver\Calibration.py", line 447, in calculate
ValueError: could not convert string to float:

The log file I specified after -d did not get saved.

I hope this helps you find the issue that caused the crash.

--
Bryan, WA5VAH

Rune,

I have noticed that you save the "Calibration standards" information in the ".ini" file for nanoVNA-Saver. Great idea. I also observe that after loading the information from the ".ini" file you still have to click "Apply" on the Calibration window for the new values to be used even though you can see them on the "Calibration" form. It seems to me that when the user clicks "Load" to pick a set of stored "Calibration standards" that you should "Apply" them automatically and not require the user to click "Apply." Just a thought.

I started nanoVNA-Saver 0.1.2 in a command window using "nanovna-saver.v0.1.2.exe -d testlog.txt" Here is the last several lines on the screen after the crash when changing values on the Calibration form in the "Calibration standards" box.

2019-10-16 07:38:41,567 - NanoVNASaver.SweepWorker - DEBUG - Sending "updated" signal
2019-10-16 07:38:41,567 - NanoVNASaver.SweepWorker - DEBUG - Resetting NanoVNA sweep to full range: 50000 to 900000016
2019-10-16 07:38:41,636 - NanoVNASaver.SweepWorker - DEBUG - Sending "finished" signal
2019-10-16 07:38:54,382 - NanoVNASaver.Calibration - DEBUG - Loading calibration no 0
2019-10-16 07:38:54,383 - NanoVNASaver.Calibration - INFO - Loading: HighOrderForBNC
Traceback (most recent call last):
File "NanoVNASaver\Calibration.py", line 447, in calculate
ValueError: could not convert string to float:

The log file I specified after -d did not get saved.

I hope this helps you find the issue that caused the crash.

--
Bryan, WA5VAH

There has been mention of the high price of SMA adapters. The standard
here is N but it appeared that the package described below, that
included BNC and TNC, would be the best way to go.


Adapters for taking SMA to N and to BNC were ordered from Shenzhen
Yishitonga Trade Co., Ltd. through Aliexpress. The "Model Number" was
517A103102. The price was US$17.52 when ordered on 20190805. That was
the all up price delivered. They came through customs into Canada
without charge.

The adapters furnished in the package can be seen on the Yishitonga web
site, u.r.l. below. The adapters, as delivered here, are documented in
the included photograph.

Visually and by handling and mating, the fit and finish are satisfactory
to a user who has seen a few r.f. connectors in his day.

For the h.f. operator, these adapters appear to be suitable. A test at
v.h.f. produced normal results. No statement can be made about
performance at u.h.f. and beyond. No statement can be made about fine
mechanical tolerances or about dielectric.

For the h.f. ham radio station, these adapters seem to be just
fine...particularly at that price.


? ?





John

at radio station VE7AOV


--

On Wed, Oct 16, 2019 at 01:08 AM, Dr. David Kirkby from Kirkby Microwave Ltd wrote:

I agree that the resistance of the short is unlikely to be an issue, but
the resistance will increase with frequency due to the skin effect.

Dave,

You are correct. I can't measure the skin effect resistance with anything I have available. So, I am stuck with the best measurement I can make of the short I use.

--
Bryan, WA5VAH

I just released NanoVNA-Saver 0.1.3!



This release adds a couple of much requested features:

Popout charts
All charts can now be popped out as separate windows: Right click them, and
select "Popout chart" to get a copy of it. As a side effect of implementing
this, the main window can now also contain multiple charts of the same
type. Want a zoomed in version of an existing chart next to it? Now you can.

VSWR markers
Under Display setup, you now have the option of adding a number of VSWR
markers, to be shown on both the S11 Smith chart, the S11 Return Loss
chart, and obviously the S11 VSWR chart. The colour can be selected, and
you can add however many you need. The markers are saved between startups.

Logarithmic frequency span
All frequency-dependent charts can now be changed to show logarithmic
frequency span instead of linear. Right click, select Frequency axis, and
choose linear or logarithmic.

Shortcuts
You can now start a new sweep by pressing Ctrl-W, or stop a sweep by
pressing Escape while within the main window.

Line thickness and point size
Line thickness and point size can now be configured within the Display
setup window. Default values are 1 pixel for lines, 2 pixels for data
points.


Additionally, there are minor changes, such as -60 dB points being
automatically estimated from -10 dB and -20 dB points when doing filter
analysis, and a number of bugfixes and stability improvements. This
version should also work better with the NanoVNA-F, though there may still
be some niggles.

I look forward to hearing your feedback on the software, and I hope you
enjoy using it!

--
Rune / 5Q5R

I've been thinking about a test jig for measuring capacitors and inductors.

Ideally, this would have built in calibration modes and support all
three DUT measurement configurations with the VNA.

On Wed, Oct 16, 2019 at 5:57 AM Starsekr via Groups.Io
<Starsekr@...> wrote:

Can't see why it is off topic. Much of the calibration is about test jigs or extensions of the reference plane. See hash tag #test-jigs. BTW, hashtags are active in this group. BUT they can only be created by a person starting a topic. There are several links in the wiki to practical uses of the VNA, many have test jig examples. Look under other VNA and related links. Issues with jigs are often calibration and error reduction.

Hi Sala,

Some test jig ideas can be found here:

I found if leads are pushed into the breadboard hard enough, they will short to foil. Better to flip single sided PWB. Breadboard from Mouser. PWB blank from Amazon.

John KN5L

"I measured a simple class A common emitter amplifier and theory and test results do not match."

Beware of signal levels, especially when measuring active devices.

Regards,

Martin - G8JNJ

On Tue, Oct 15, 2019 at 11:58 PM, Starsekr wrote:

Saw this on eBay.

I ordered these to hack:

By the time you get the boards made and get the connectors, you have spent at least as much as Marcus is asking.
He has done the research and gotten the line section correct for the board material.

Glenn

--
-----------------------------------------------------------------------
Glenn Little ARRL Technical Specialist QCWA LM 28417
Amateur Callsign: WB4UIV wb4uiv@... AMSAT LM 2178
QTH: Goose Creek, SC USA (EM92xx) USSVI LM NRA LM SBE ARRL TAPR
"It is not the class of license that the Amateur holds but the class
of the Amateur that holds the license"

If I could get past this driver problem then I think the rest would fall into place.

The windows operating system needs an STMicroelectronics driver installed.

'DfuSeDemo.exe' installed for me in a folder that also includes a 'Driver' folder,
in which are folders for Win7-10, in each of which are subfolders for x64 and x86 (AKA 32-bit).
In each of those driver subfolders is an installer .exe
Run >>only<< the one that matches your Windows version and bit-depth.

Alternatively:
* right-click on "My PC" icon, select 'Properties'
* select 'Device Manager'
* attach and turn on nanoVNA, open:
> Ports (COM & LPT)
* select the appropriate COM port
- if you do not know which one, simply turn nanoVNA off/on to see which disappears and reappears
* right-click and select "Update Driver Software..."
* browse that back to the DfuSeDemo.exe installation folder

Can't see why it is off topic. Much of the calibration is about test jigs or extensions of the reference plane. See hash tag #test-jigs. BTW, hashtags are active in this group. BUT they can only be created by a person starting a topic. There are several links in the wiki to practical uses of the VNA, many have test jig examples. Look under other VNA and related links. Issues with jigs are often calibration and error reduction.

I measured a simple class A common emitter amplifier and theory and test results do not match.

So, it will be fun and interesting to measure some amplifiers. Have you ideas for test jigs What to include, where to buy and so on. (And what forum to use, because I think this is a bit OFF-TOPIC here).
I think I need to have card edge SMA connectors, SOT23, SOT89 and SOT143 pads, what else? Inductors have to be tested also. I can make my own PCB, but I can some also.

There is a how-to, linked in Wiki Application Notes:

I like it the fact that I can use it non-interactively.

Non-interactively, after downloading the four *.p files from above:
* One time only, to generate gridpoint data file `smithgrid.dat`, run:

C:\Users\ormpoa>gnuplot smithgrid.p

* modify plotsmith.p to generate Smith charts from wanted Touchstone files,
adding rectangular plots e.g. per

C:\Users\ormpoa>gnuplot plotsmith.p

being able to generate all the PDF plots from a single unix shell script
makes the process much easier.

* .. so you already know how in a gnuplot script to generate PDF, e.g.

set term push
set term pdfcairo
set output 'YourFilename.pdf'
replot
set term pop

Hello Gyula
I also have Rune's fantastic application running on a 32 bit Windows7 machine but battled to get running on a 32bit version of Ubunu (latest LTS v18) and after a remote session with Ohan (ZS1SCI - a VERY knowledgeable software developer), established that not possible on a 32 bit Linux machine as per note from Rune.

I wish you a great time using the nanovna + nanovna-saver, LOTS to experiment with for sure!

73

Nigel ZS6RN ex G8DEV