Re: NanoVNA newbie having problems with new unit
Herb,
I have no issues with the latest APK on my LG tablet (Android 7) or Chinese cellphone (Android 8.1).
Install the following USB utility and check to see if your Android device detects the nano:
Plug in your Nano and check the peripheral section. It should show everything connected.
Regards,??
Larry
toggle quoted message
Show quoted text
On Friday, November 8, 2019, 10:18:05 a.m. GMT-5, hwalker <herbwalker2476@...> wrote:
Thanks for the tip!? Unfortunately the off-line APK version still does not recognize the NanoVNA.? At least the on-line version allows Chromebooks with the latest OS to attach to the NanoVNA.
Samsung XE500C13 Chromebook 13
- Herb
|
Re: NanoVNA newbie having problems with new unit
Unfortunately the off-line APK version still does not recognize the NanoVNA. Experimenting with other Android apps using USB OTG, the problem appears to be ChromeBook Android emulation, perhaps simply USB dev path naming or permissions. No blame to cho45
|
You're right as far as I can tell - when you want to read data within the
previously calibrated span, you don't need to calibrate again, as long as
your setup is otherwise the same. For that very reason, I usually keep a
50kHz - 1500MHz calibration in C0 on my device.
Having the calibration purely within NanoVNA-Saver is certainly doable, and
something I could implement in the future, with the right support from the
firmware developers of course. :-)
But like others have mentioned: There is a difference between trying to get
the NanoVNA to the level of a high-level VNA, or trying to make it easier
to use for the use cases where the performance is already adequate. For
now, I'm working on some features for the latter, most notably mouse-based
zoom on the charts and logarithmic Y-axis scaling - but also some of the
former, like dialling in port extension in picoseconds within the software.
--
Rune / 5Q5R
toggle quoted message
Show quoted text
On Fri, 8 Nov 2019 at 16:18, Nick <g3vnc@...> wrote: Thanks Rune. I did not understand the relationship between device cals
and nvna-s cals.
Please allow me to check my understanding.
Let's say I want to measure a ferrite choke from 1 to 50MHz. I set up the
cables and do a device cal over that frequency range using an appropriate
cal kit. I save that cal to say C0.
With C0 selected on the device, I repeat the cal on nvna-s using the same
frequency range, same cables, same cal kit and save it to cal_0.cal.
I can then measure my choke over the same frequency range using nvna-s
with as many data points as I like using multiple segments.
Let's say I then want to measure a UHF filter over the range 100MHz to
900MHz. Obviously I cannot use C0 and cal_0.cal. So I set up with
different cables and a different cal kit. I do a device cal over that
frequency range and save it to C1.
With C1 selected on the device, I repeat the cal on nvna-s using the same
frequency range, same cables, same cal kit and save it to cal_1.cal..
I can then measure my filter over the same frequency range using nvna-s
with as many data points as I like using multiple segments and save the
results to s*p files.
What if I then want to measure the filter over a restricted frequency
range, say 400 to 500MHz?
Or a VHF filter with the same the cables and connectors from 100MHz to
200MHz?
Do I need a new pair of cals in either of these cases? (I would say not.)
Is it possible for nvna-s to detect what cal the device is set to i.e. C0
through C4, tell the user and set the correct scan range?
If nvna-s could read raw data from an uncalibrated nvna would that mean
that all cals for fixed bench work could be performed by, and saved in,
nvna-s if the user so wished?
Obviously for portable use the device cals are the only ones available.
On Fri, Nov 8, 2019 at 11:46 AM, Rune Broberg wrote:
by same I mean the *same*. The NanoVNA-Saver calibration is *not*
independent of the device calibration - on the contrary, it is in fact
dependent on that calibration staying the same.
The values returned by the NanoVNA to NanoVNA-Saver are the adjusted values
from the device calibration. NanoVNA-Saver further offers a calibration
based on these values - but it does not know the original raw values from
the device. I guess that could be implemented, but it is not currently.
|
Re: T-Check for my nanoVNA - Results look excellent below 150 MHz and acceptable up to 300 MHz
I need help from an expert.
My T-Check setup is now 2 x 50 cm RG402 coax cable and a SMA Tee with a 50 Ohm Load,
see picture NanoVNA_T-Check_SMA-Tee_RG402_DSC08175.jpg
The result, calculated with the spreadsheet from QRP is shown in
NanoVNA_T-CheckR-RG402.png
The S21 gain shows a big oscillation, see
NanoVNA_T-Check-T_RG402-50cm.png
If I remove the CH1 coax cable from the SMA Tee S11 looks like:
NanoVNA_50-Ohm-Load_RG402.png
So, I think the calibration was OK.
The attached file NanoVNA_T-Check-T_RG402.S2P can be
imported in VNWA, see VNWA_T-Check-T_RG402.png
How does that come?
What I am doing wrong?
73, Rudi DL5FA
|
Thanks Rune. I did not understand the relationship between device cals and nvna-s cals.
Please allow me to check my understanding.
Let's say I want to measure a ferrite choke from 1 to 50MHz. I set up the cables and do a device cal over that frequency range using an appropriate cal kit. I save that cal to say C0.
With C0 selected on the device, I repeat the cal on nvna-s using the same frequency range, same cables, same cal kit and save it to cal_0.cal.
I can then measure my choke over the same frequency range using nvna-s with as many data points as I like using multiple segments.
Let's say I then want to measure a UHF filter over the range 100MHz to 900MHz. Obviously I cannot use C0 and cal_0.cal. So I set up with different cables and a different cal kit. I do a device cal over that frequency range and save it to C1.
With C1 selected on the device, I repeat the cal on nvna-s using the same frequency range, same cables, same cal kit and save it to cal_1.cal..
I can then measure my filter over the same frequency range using nvna-s with as many data points as I like using multiple segments and save the results to s*p files.
What if I then want to measure the filter over a restricted frequency range, say 400 to 500MHz?
Or a VHF filter with the same the cables and connectors from 100MHz to 200MHz?
Do I need a new pair of cals in either of these cases? (I would say not.)
Is it possible for nvna-s to detect what cal the device is set to i.e. C0 through C4, tell the user and set the correct scan range?
If nvna-s could read raw data from an uncalibrated nvna would that mean that all cals for fixed bench work could be performed by, and saved in, nvna-s if the user so wished?
Obviously for portable use the device cals are the only ones available.
toggle quoted message
Show quoted text
On Fri, Nov 8, 2019 at 11:46 AM, Rune Broberg wrote: by same I mean the *same*. The NanoVNA-Saver calibration is *not*
independent of the device calibration - on the contrary, it is in fact
dependent on that calibration staying the same.
The values returned by the NanoVNA to NanoVNA-Saver are the adjusted values
from the device calibration. NanoVNA-Saver further offers a calibration
based on these values - but it does not know the original raw values from
the device. I guess that could be implemented, but it is not currently.
|
Re: NanoVNA newbie having problems with new unit
Thanks for the tip! Unfortunately the off-line APK version still does not recognize the NanoVNA. At least the on-line version allows Chromebooks with the latest OS to attach to the NanoVNA.
Samsung XE500C13 Chromebook 13
- Herb
|
Re: NanoVNA newbie having problems with new unit
NanoVNA Web client After most recent Chromebook updates, NanoVNA Web client now works with Acer CB5-571 Chromebook 15.
|
Re: how to see what firmware version?
Bob,
If your on-screen menu does not have a Version key, then you are running something less than 0.3.0 and you will need to use the console commands to find out how what version you're at.
Check the Wiki on how to access the console commands and how to connect the Nano to your PC via a USB connection.
...Larry
toggle quoted message
Show quoted text
On Friday, November 8, 2019, 8:58:13 a.m. GMT-5, bob <w9zv@...> wrote:
apologies if this has been answered before...? i scrolled thru many pages and didnt see it.
i would like to find out what firmware version my nanovna is currently running, in order to consider if an update is needed.
how can i find out what version of firmware is currently installed?
amazing and useful little device.? it becomes hard to imagine folks complaining about it for $50 or < $200 even, when only a few years ago you needed $10's of thousands of dollars invested in HP or similar to do much the same.? Get some perspective.
-bob
|
how to see what firmware version?
apologies if this has been answered before... i scrolled thru many pages and didnt see it.
i would like to find out what firmware version my nanovna is currently running, in order to consider if an update is needed.
how can i find out what version of firmware is currently installed?
amazing and useful little device. it becomes hard to imagine folks complaining about it for $50 or < $200 even, when only a few years ago you needed $10's of thousands of dollars invested in HP or similar to do much the same. Get some perspective.
-bob
|
Excellent work and document, Herman.
Thanks for sharing.
...Larry
toggle quoted message
Show quoted text
On Friday, November 8, 2019, 7:02:54 a.m. GMT-5, Herman De Dauw <on1bes@...> wrote:
Recently I have replaced my 2.8" LCD with a 3.5" version. Document is in the Files section.
'73 on1bes
|
Re: NanoVNASharp MOD v3 released
Hi QRP RX,
I would suggest a little improvement:
Let in the SWR window a routine find the best (minimal) SWR and it's frequency ! Set automatically the cursor to this position.
Also in the S11 window.
Best regards, Wolfgang Kiefer, DH1AKF
|
Hi Alan
Yes, If I was to use type N, which is not very likely, I have an HP 85032 Type N cal kit. For BNC I just made a short. My interests are HF so leaving the male BNC open is good enough and I use the 85032's load thru a BNC adapter. Thru a good Amphenol adapter the 50 ohm load is very good. There is no electrical length issue with the load. I am all set. I need no other software and just Nanovna Sharp. I down loaded a version of "saver" and it only seems to present more graphical representation. I take out the s1p file and that's it. From the s1p file I convert the mag and phase angle of the reflection coeff to any other parameter I need using a spreadsheet. I am pretty much only interested in Z and RL. I have used the nano with an HP 8721A directional coupler measuring S21 to measure RL. It works very nicely.
Pete
|
Recently I have replaced my 2.8" LCD with a 3.2" version. Document is in the Files section.
|
I have ordered a NanoVNA-F with 4.3 inch display. There is alo a special newsgroup: /g/nanovna-f
|
Hello,
This email message is a notification to let you know that the following files have been uploaded to the Files area of the [email protected]
group.
Uploaded By:
Herman De Dauw <on1bes@...>
Description:
Replace NanoVNA 2.8 LCD with a 3.2 one
Cheers,
The Groups.io Team
|
Hi Nick,
by same I mean the *same*. The NanoVNA-Saver calibration is *not*
independent of the device calibration - on the contrary, it is in fact
dependent on that calibration staying the same.
The values returned by the NanoVNA to NanoVNA-Saver are the adjusted values
from the device calibration. NanoVNA-Saver further offers a calibration
based on these values - but it does not know the original raw values from
the device. I guess that could be implemented, but it is not currently. So
for application calibration to work, you must use the same calibration on
the NanoVNA when you take your measurements as you did when you calibrated
NanoVNA-Saver.
In general, while it's useful to save the calibration if you are using a
fixed installation with the same cables etc., calibrations are by their
nature very dependant on the connectors, cables etc. used, and any changes
of these necessitate a new calibration if you want accurate results.
--
Rune / 5Q5R
toggle quoted message
Show quoted text
On Fri, 8 Nov 2019 at 12:34, Nick <g3vnc@...> wrote: On Fri, Nov 8, 2019 at 08:26 AM, Rune Broberg wrote:
You should always use the *same* calibration on the
NanoVNA itself when using NanoVNA-Saver's application calibration. Hi Rune
Your github page says
"Before using NanoVNA-Saver, please ensure that the device itself is in a
reasonable calibration state. A calibration of both ports across the entire
frequency span, saved to save slot 0, is sufficient. If the NanoVNA is
completely uncalibrated, its readings may be outside the range accepted by
the application."
I have experienced corrupted calibration data on the device which results
in big numbers that cannot be read by nvna-s which then disconnects, so I
understand the need to ensure some kind of device calibration before using
nvna-s.
I understand that nvna-s can use the device calibration, or use one of its
own calibration data sets which are independent of those stored on the
device in C0 through C4.
But I must admit that I am unclear as to what is meant by "reasonable" and
the "same" calibration.
Do you mean the same calibration kit, the same calibration regime i.e. SOL
or SOILT, the same frequency span, the same reference plane etc?
Please could you elaborate.
73
Nick
G3VNC
|
On Fri, Nov 8, 2019 at 08:26 AM, Rune Broberg wrote: You should always use the *same* calibration on the
NanoVNA itself when using NanoVNA-Saver's application calibration. Hi Rune Your github page says "Before using NanoVNA-Saver, please ensure that the device itself is in a reasonable calibration state. A calibration of both ports across the entire frequency span, saved to save slot 0, is sufficient. If the NanoVNA is completely uncalibrated, its readings may be outside the range accepted by the application." I have experienced corrupted calibration data on the device which results in big numbers that cannot be read by nvna-s which then disconnects, so I understand the need to ensure some kind of device calibration before using nvna-s. I understand that nvna-s can use the device calibration, or use one of its own calibration data sets which are independent of those stored on the device in C0 through C4. But I must admit that I am unclear as to what is meant by "reasonable" and the "same" calibration. Do you mean the same calibration kit, the same calibration regime i.e. SOL or SOILT, the same frequency span, the same reference plane etc? Please could you elaborate. 73 Nick G3VNC
|
Re: NanoVNA-saver and Windows XP
I'm running XP service pack 3 if that helps]
Does anyone have any suggestions please? FWIW, I have not tried it:
|
I see the same thing, and it has not caused me any problems.
--
Rune / 5Q5R
toggle quoted message
Show quoted text
On Fri, 8 Nov 2019 at 10:23, Lucio I?LYL <lucio.i0lyl@...> wrote: hello, when I connect the nanoVNA to nanoVNA Saver the letter "Cx"
(Calibration number) becomes lowercase. This tells me that nanoVNA is
calibrated but on another frequency range. Yet the on frequency has not
changed on the device and not in nanoVNA Saver. Is it all normal?
thanks
Lucio, I0LYL
|
hello, when I connect the nanoVNA to nanoVNA Saver the letter "Cx" (Calibration number) becomes lowercase. This tells me that nanoVNA is calibrated but on another frequency range. Yet the on frequency has not changed on the device and not in nanoVNA Saver. Is it all normal?
thanks
Lucio, I0LYL
|
Oristo
Wolfgang Kiefer
