开云体育

Now, my question would be: "What's the difference between the nanoVNA and the nanoVNA-H? Any difference in the
hardware or is it the firmware?

BruceN

Barry, looks like you are from UK.
I'm planning to buy one of NanoVNAs. Where did you buy your device, eBay ? Which firmware did you use for it?
I will be using my NanoVNA for the same purpose as you, to calibrate my antenna at 1090 MHz. So, ideally will be nice to have 1500MHz range. Thanks in advance for support.

In addition to all the fast and furious releases, it befuddles me as to which version of whose firmware to use.
I've seen several posts about folks bricking their nanovna because they either chose the wrong firmware or
screwed up installing it.

I've read about how to properly install it so I'm not afraid of that. But, which version to choose? Does it depend on
what you wish to do with it? Do some folks find the features given by one better than another? I haven't found that
comparison as yet. Or, maybe I missed it. I do browse the Wiki and it's been a help.

So, my question would be, which one should I start with.

BruceN

Good to know - I've updated the user and console manuals.
Thanks

Thank you, Rune!
Now also the TDR function is correct and even delivers the impedance as function of the distance. Great!
Wolfgang, DH1AKF

I have released a new version of NanoVNA-Saver, 0.2.1:


This release is a minor update to the 0.2.0 release:
New feature: Capacitance and Inductance charts
These new charts display the calculated series equivalent Capacitance and
Inductance against frequency.

New feature: Panning and modified zooming
You can now hold the middle mouse button to pan a zoomed chart, or hold
shift or control to only zoom the value or frequency axis when zooming
using the mouse wheel.

Moving markers using the arrow keys
After placing a marker on a chart by clicking with the mouse, it's now
possible to move the marker immediately using the arrow keys.

Experimental feature: Port extension/Offset delay
The calibration window has a new experimental feature. You can set an
offset delay, which I'm told is useful for compensating for cables used
when measuring without doing a full calibration. The value is applied
immediately when changed, and is not connected to the other calibration
features. Feedback on this feature is specifically requested.

Additionally, a number of bugfixes have been made, based on your feedback -
Thank you! A lot of tidying has happened on the back end of the code, as
well as the introduction of some automatic testing - thanks to Holger
Müller and David Hunt!

As ever, I look forward to hearing all your feedback and suggestions!

--
Rune / 5Q5R

Thank you wofgang,it worked a treat,ive now got the firmware with bigger fonts,at least now i can see it with just my glasses and not a loupe! 73 m3vuv.

Hi Paul -

ive updated the wiki

I have calibrated after installing NanoVNA-Q many times,
and SAVE->SAVE [0-3] is NOT required after CAL->RESET

RF CALIBRATE can fail for several reasons, but that is not one.
Here are some calibration failures that I personally experience:

1) Immediately after firmware installation,
failure to (by terminal command) `clearconfig 1234` followed by power off/on

2) After `clearconfig 1234` followed by power off/on, failure to `touchcal` and `touchtest`
If touch calibration is off, based on your personal touch style,
then it is too easy for one or more of the OPEN/SHORT/LOAD/ISOLATION/THRU/DONE
presses to NOT be detected. When press is detected, the next button highlights...
Watch for that, retry if not sure.

3) Failure to verify e.g. Smith plot change for each termination change during calibration
- may not get SHORT, LOAD or THRU termination properly connected

4) Connector crimp to coax failure
- I am always calibrating with RG-316 leads, and 2 have failed since July
- Crimp failure may be detected by LOGMAG or other plot change by touching connector
or by SHORT not registering correctly on Smith plot

I do many successful RF calibrations without saving, but still fail 1 of 4 or so, with or without saving.

For new users, I recommend that you use the search key, short sentences or key words written there before asking a question.
Here's an example of a user on the same topic because he couldn't solve something: he opened five topics in a row and asked the question five times with a small modification. OK, I understand that anyone who does not know the solution cannot ask well.
Because only those who know the solution know the right questions.
But you shouldn't split TOPICS like that.
It is true that the WIKI and FILES folders are large, but they are linked thematically, but they are also large and multi-layered.
Thank you for your attention.

73, Gyula HA3HZ

Hi Paul,
based on my memories, the best professional can handle the task when a new thing comes up. In the middle of the summer, when we had a translation from Japanese to Chinese and then Chinese to English, we didn't know these things. Herb has just described the solution for you.
But many people were curious about the structure, and we worked out a solution together.
You just have to apply this.
Because of bad insertion, you may need to do something else.
Remote repair is the worst thing not many people do because they have to see what you can do wrong or otherwise.
If you have the patience, please read what I wrote on my page, set the language in the upper left corner. I keep trying to improve the description because more eyes see the same thing differently. ()
Thank you for your attention.

73, Gyula HA3HZ

I had yellow exclamation mark on SMT32 BOOTLOADER (Windows 7 Professional 64-bit).
I found driver in C:\Program Files (x86)\STMicroelectronics\Software\DfuSe v3.0.6\Bin\Driver\Win7\x64
- right mouse click then Update Driver Software...

Hope that helps.

Regards
Martin

On Sat, Nov 30, 2019 at 01:15 PM, UlrichKraft wrote:

I did not realize that I also need to SAVE to Cx right after Reset. Otherwise
the data isn't really cleared and remains in the memory.

There is no needs to SAVE after CAL RESET. You're just doing something wrong.

On Wed, Dec 4, 2019 at 09:06 AM, paul larner wrote:

its my understanding you reset then save to whatever slot you chose,then do
your calibration and resave it in the same slot,doing it as you say gives me
rubbish results!

There is no needs to save after CAL RESET. You can perform calibration with no save at all and use it until reboot.

On Tue, Dec 3, 2019 at 04:10 PM, Larry Rothman wrote:

Next, while in Console mode, calibrate the touchscreen using TOUCHCAL and then
SAVECONFIG

Larry, you forgot to mention that there is needs power off and power on just after clearconfig command.
If you use any kind of save command with no power off, it will leads to restore old bad config.

clearconfig command clears flash memory with configuration, but not RAM. The old config remains in the RAM and if you make save it will be stored back into flash. When you power off NanoVNA after clearconfig, and then power on. The firmware will see at boot time that there is no config in the flash and default config will be loaded.

its my understanding you reset then save to whatever slot you chose,then do your calibration and resave it in the same slot,doing it as you say gives me rubbish results!

Paul,
You only read the brief procedure but not the whole calibration procedure. The <RESET> before calibration clears things out and doing a save a this point is rather pointless. The proper save comes after the whole calibration is complete at which point you have the choice to save to locations 0, 1, 2, 3, or 4. If you don't do a save at this point then the calibration will not stick.

If you don't do a reset before starting the calibration then when you perform a save at the end you will retain data from the previous calibration. That sounds like the situation you were experiencing.

This is the procedure from the developer and that is in all the operating manuals. It works for everyone else.

-Herb

i found the issue,bad cal routine,ive updated the wiki,was someting the guides didnt mention/make clear!,its now spot on on all 3 ranges!

If i followed your advice id still be having issues,you proc is wrong,dont you see it??you have to reset and save before doing a cal,ie reset then save that cal position before you do any cal routines on that save slot,compair the 2 methods!,yours saves bad data!!

ive a lenovo tab,it wont run on it!,seems a half baked solution!

Hi Paul,
please take the button "Upgrade" instead of "Upload" !