开云体育

Another way to do this would be to package it up with an Android tablet and use NanoVNA WebApp as the user interface (remove or hide the built-in LCD).
I'd like to try this but the android app won't load on my older tablet, despite it having been updated to Android 6.1.

It would also be possible to build in a raspberry pi and use nanovna-saver, but the android app seems a better fit if you don't have a keyboard.

even if you cleaned your connector with alcohol, you're needs to perform calibration after that

any change, firmware or hardware requires a new calibration.

Hi Jos,
I haven't done anything in particular relating to the NanoVNA-Q firmware,
so any changes, assuming you are using the same version of NanoVNA-Saver,
is in the firmware. :-)

The individual buttons have never done any measurement - they save the
currently displayed data as the calibration data for that particular
standard.

--
Rune / 5Q5R

if firmware detects incompatible calibration it reset calibration and settings.

You're needs to perform calibration after firmware update.

Hi Rune

After Flashing NanoVNA-Q-0.4.4 I found that the calibration in Nan0VNA-Saver has changed.

I am used to set the sweep settings in the NanoVNA-Saver to a high number of segments and averaging while running a calibration, causing long sweep times

When doing so with this new firmware it took 1 minute and about ten seconds per calibration sweep only, it looks like VNA-Saver is not using the settings set by the user, and/or is using? the setting in the firmware.

I also noticed that it is no more possible to calibrate manually (without using the Calibration Manager), when you click "Short", "Open" or "Load" in the calibration screen it immedeately loads 1010 points of measurements and no measurement is performed.

Thanks for this great software.

Kind regards,

Jos

On Wed, Nov 27, 2019 at 01:28 PM, RFy wrote:

Q branch can not enter DFU mode via command

it can enter into DFU with no issue, this is your compiler issue.

Tested: original(191124), Q(191119), H(191125)
- Compiled with ARM-GCC/2019-Q4
- Each firmware flashed before FF overwrite & clearconfig & uncalibrated( cal reset & cal off ) nothing connected
- trace 0 scale:3/ref:13.746025507
- trace 1 scale:11/ref:11.5512126265

* Glitches at 6.5 MHz, 64 MHz( seems DC )
* "cal data" all terms returned 0.
* Q and H branch firmware "data 2 ~ 6" returns garbage( not zero-ed array )
* Q branch can not enter DFU mode via command( Not tested IAR precompiled version )
* "marker 1...4 off" -> "trace all off" -> Iterating "scan" & "data 0..1" : populates weird +22dB CH0 logmag

I tried to get it running on Linux Mint 18.3 (32bit)
The big fault was to deinstall Python 3.5. This crashed my system completely.
I installed a clean Mint 18.3 Cinnamon, installed Python 3.7, I followed the instructions on the nanovna-saver github and it worked fine. So Python 2.7, 3.5 and 3.7 can be on one machine in a co-existance. My advice is to do not upgrade 3.5 to 3.7!
The only thing I had to do, was to add the user to the dialout group.

I tried the same on a computer with an old and dirty setup of Mint 18.3 Cinnamon (64bit). But I didn't get it running there.

Under Linux Mint 19 everything seems to be fine from the scratch. But I couldn't test it for my purposes so far.

/g/nanovna-users/files/Hardware%20Mods/NanoVNA%20new%203.2%20LCD%20display%20Herman%20ON1BES.pdf

--
NanoVNA Wiki: /g/nanovna-users/wiki/home
NanoVNA Files: /g/nanovna-users/files
Erik, PD0EK

from what i can tell a 3.2" will fit,would one of these do the job?,ones resistive and one capacitive on the touchscreen

or:
I dont have mine yet but planing on making a metal case with a bigger screen for it. 73 m3vuv

On Tue, Nov 26, 2019 at 11:29 PM, Dom Baines M1KTA wrote:

" Is that gecko image on the cover linked to them in some way as I had problems with a basic NanoVNA with that logo."
=======================================================================

The 2.8" white NanoVNA with the gecko design has gotten good performance reviews by other members of this group. On the other hand, the gecko logo on the 4.3" NanoVNA-F is one of the warning flags that the device is a clone with subpar performance and should be avoided.

The clones are being sold at the same price point as the real NanoVNA-F which is even more of a reason to pass them up.

Seeing how fast clones of the NanoVNA-F have hit the marketplace probably means hugen has a small window before clones of his NanoVNA-H model start appearing.

- Herb

Is that gecko image on the cover linked to them in some way as I had problems with a basic NanoVNA with that logo.
Yes I know a logo isn't going to matter but maybe the 'dumb cloners' try to badge their product?

72
Dom
M1KTA

Exactly.

The nanovna-saver source code is there so on the Mint 17.3 host could you not do an altinstall of python 3.7 without tramping all over the 2.7 install and then use a python environment and switch between them, I always thought you could?

I bet you'll see less pain overall though if you don't code anything just upgrade the OS unless there are very major reasons for the older version. Or you could turn this on it's head and ringfince those requirements inside a mint 17.3 python 2.7 VM just as easily.

I was also a Mint 17.3 user in the shack but ended up updating to 19.1 and created a 17.3 VM for anything that 'seemed' to need it, in the end nothing did.

72

Dom
M1KTA

Connections with LCD incompatible, firmware has insufficient free space
See wiki /files for a possible retrofit
--
NanoVNA Wiki: /g/nanovna-users/wiki/home
NanoVNA Files: /g/nanovna-users/files
Erik, PD0EK

is it possible to retrofit a 4.3 inch screen to a nanovna that has a 2.3 inch one,has anyone tried this?.

Anyone contemplating purchasing a NanoVNA-F in the near future should be aware a rash of clones have hit the marketplace. According to BH5HNU , "Recently we found a bad clone of the -F machine on AliExpress / eBay. We have open sourced all the code on github, but this clone is still badly made.
As the picture shown in the attachment, We want enthusiasts to stay away from these crude products."

Buyer beware.

- Herb

Sam,
If I am doing an S21 measurement and I need to normalize for an added attenuator or preamp, I just do a quick through calibration with the attenuator or preamp in-line and that normalizes my measurement. If you don't save the configuration to one of the save locations then the normalization is only temporarily applied.

Works well for me.

- Herb

Has anyone thought about having a normalize mode? You could put it on the channel screen selection and indicate with a N added to the C#DRSTX with maybe a space between the X and the N to indicate to the user that S21 CH1 is in normalize mode.

Much easier that recalling when compensating for an attenuator or cable loss.

Sam
W3OHM