Hi QRP - capture - unique; currently broken for my python scripts, since not ASCII;
returns display buffer in some(??) bitmap format. - QRP seems to have gotten this working in his latest NanoVNA-Sharp branch
with latest -Q firmware.
Wrong information. capture command is not unique, it is available in all
firmware versions, except these which is very-very old,
completely outdated with a bunch of bugs.
Sorry, key part of message was: "broken for my python scripts, since not ASCII" - problem is in >>MY<< Python code, NOT firmware - I need to add some Python that correctly handles 'capture' response, e.g. from : def capture(self): from PIL import Image self.send_command("capture\r") b = self.serial.read(320 * 240 * 2) x = struct.unpack(">76800H", b) # convert pixel format from 565(RGB) to 8888(RGBA) arr = np.array(x, dtype=np.uint32) arr = 0xFF000000 + ((arr & 0xF800) >> 8) + ((arr & 0x07E0) << 5) + ((arr & 0x001F) << 19) return Image.frombuffer('RGBA', (320, 240), arr, 'raw', 'RGBA', 0, 1)
|
Re: UI Suggestion: Big Numeric Display Forma
An absolutely EXCELLENT idea.? Thanks!! On Sat, 26 Oct 2019 at 6:38 AM, DL9CAT<groups.io@...> wrote: Hi, On Sun, Oct 13, 2019 at 12:29 AM, KV5R wrote: he typical use case of radio hobbyists fine-tuning antennas (usually to lowest
SWR at resonance), a "big" text-only screen would be very useful when used
with CW fixed frequency mode.
I imagine it would display 3-4 numeric lines -- Frequency, SWR, R+-jX, and
maybe one more parameter. maybe this is interesting for you:I added a big info screen for CH0 on top of the normal screen: Select Config -> "Info CH0": Firmware: (but be aware, this is still a beta release) This should be especially helpful measuring antennas while beeing outdoors. It?s readable in sunlight now. 73 de DL9CAT
|
Re: NanoVNA newbie having problems with new
He dropped the last r on the filename...
On Sat, 26 Oct 2019 at 5:57 AM, Rune Broberg<mihtjel@...> wrote: Hi,
the file name is "nanovna-saver.py". So the error you got seems to have
been because you tried to run a file that did not exist?
If the application works, then I don't think anything important has failed.
You don't mention which commands you tried running in which order, so I
can't tell what caused the "bdist_wheel" problem.
--
Rune / 5Q5R
toggle quoted message
Show quoted text
On Sat, 26 Oct 2019 at 11:37, <subs@...> wrote: It seems then, that the firmware version that I have is the latest by
Hugen.
With regards to the Save, thank you for the link, and this one makes more
sense as it is consistent with the menu I have. It seems that Trace setting
status rather oddly is saved in the calibration settings along with Marker
setting status. I just didn't envisage that as a calibration factor. As you
pointed out, it needs to be saved in SAVE 0, but under calibration rather
than the general system settings SAVE, which doesn't seem to save much
except:
- Touch panel calibration information
- Grid color
- Trace color
- Calibration data number loaded by default
That's sorted that one out.
I ran into difficulties with nanovna saver though. I already had the
pre-requisistes:
`python3-serial`
* `python3-pyqt5`
* `numpy`
The last of these is ambiguous which I will come to in a moment. I
followed the process in the readme and got this at the end of the output:
-------------------
? Running setup.py bdist_wheel for NanoVNASaver ... error
? Complete output from command /usr/bin/python3.7 -u -c "import
setuptools,
tokenize;__file__='/tmp/pip-bd9ju62f-build/setup.py';f=getattr(tokenize,
'open', open)(__file__);code=f.read().replace('\r\n',
'\n');f.close();exec(compile(code, __file__, 'exec'))" bdist_wheel -d
/tmp/tmp_eemos37pip-wheel- --python-tag cp37:
? /usr/lib/python3.7/distutils/dist.py:274: UserWarning: Unknown
distribution option: 'long_description_content_type'
? ? warnings.warn(msg)
? usage: -c [global_opts] cmd1 [cmd1_opts] [cmd2 [cmd2_opts] ...]
? ? ? or: -c --help [cmd1 cmd2 ...]
? ? ? or: -c --help-commands
? ? ? or: -c cmd --help
? error: invalid command 'bdist_wheel'
? ----------------------------------------
? Failed building wheel for NanoVNASaver
? Running setup.py clean for NanoVNASaver
Failed to build NanoVNASaver
Installing collected packages: PyQt5-sip, PyQt5, numpy, pyserial,
NanoVNASaver
? Running setup.py install for NanoVNASaver ... done
Successfully installed NanoVNASaver-0.1.4 PyQt5-5.11.2 PyQt5-sip-4.19.19
numpy-1.17.3 pyserial-3.4
-------------------
I then ran:
$ python3.7 nanovna-save.py
and got:
python3.7: can't open file 'nanovna-save.py': [Errno 2] No such file or
directory
I had python-numpy installed, but I then tried installing python3-numpy
and then ran the install again. This time I still got the same warning at
the end of the install output, but the program ran. It would therefore seem
that python3-numpy is the required package.
The program does seem to connect to the nanoVNA and I was able to set the
start and stop frequency and run a scan which seemed to work. However, it
would seem that some component has failed. Any help would be appreciated.
|
Re: UI Suggestion: Big Numeric Display Format for CW Stimulus Mode
Hi,
On Sun, Oct 13, 2019 at 12:29 AM, KV5R wrote:
> he typical use case of radio hobbyists fine-tuning antennas (usually to lowest
> SWR at resonance), a "big" text-only screen would be very useful when used
> with CW fixed frequency mode.
> I imagine it would display 3-4 numeric lines -- Frequency, SWR, R+-jX, and
> maybe one more parameter.
maybe this is interesting for you:I added a big info screen for CH0 on top of the normal screen:
Select Config -> "Info CH0":
Firmware:
(but be aware, this is still a beta release)
This should be especially helpful measuring antennas while beeing outdoors. It?s readable in sunlight now.
73 de
DL9CAT
|
Re: NanoVNA newbie having problems with new unit
I would also suggest you are too close to the antenna you are trying to
test. With a 20cm cable your body is very close. If you are also testing
indoors it can also scew your results.
Paul G0VKT
toggle quoted message
Show quoted text
On Sat, 26 Oct 2019, 10:56 Rune Broberg, <mihtjel@...> wrote: Hi,
the file name is "nanovna-saver.py". So the error you got seems to have
been because you tried to run a file that did not exist?
If the application works, then I don't think anything important has failed.
You don't mention which commands you tried running in which order, so I
can't tell what caused the "bdist_wheel" problem.
--
Rune / 5Q5R
On Sat, 26 Oct 2019 at 11:37, <subs@...> wrote:
It seems then, that the firmware version that I have is the latest by
Hugen.
With regards to the Save, thank you for the link, and this one makes more
sense as it is consistent with the menu I have. It seems that Trace setting
status rather oddly is saved in the calibration settings along with Marker
setting status. I just didn't envisage that as a calibration factor. As you
pointed out, it needs to be saved in SAVE 0, but under calibration rather
than the general system settings SAVE, which doesn't seem to save much
except:
- Touch panel calibration information
- Grid color
- Trace color
- Calibration data number loaded by default
That's sorted that one out.
I ran into difficulties with nanovna saver though. I already had the
pre-requisistes:
`python3-serial`
* `python3-pyqt5`
* `numpy`
The last of these is ambiguous which I will come to in a moment. I
followed the process in the readme and got this at the end of the output:
-------------------
Running setup.py bdist_wheel for NanoVNASaver ... error
Complete output from command /usr/bin/python3.7 -u -c "import
setuptools,
tokenize;__file__='/tmp/pip-bd9ju62f-build/setup.py';f=getattr(tokenize,
'open', open)(__file__);code=f.read().replace('\r\n',
'\n');f.close();exec(compile(code, __file__, 'exec'))" bdist_wheel -d
/tmp/tmp_eemos37pip-wheel- --python-tag cp37:
/usr/lib/python3.7/distutils/dist.py:274: UserWarning: Unknown
distribution option: 'long_description_content_type'
warnings.warn(msg)
usage: -c [global_opts] cmd1 [cmd1_opts] [cmd2 [cmd2_opts] ...]
or: -c --help [cmd1 cmd2 ...]
or: -c --help-commands
or: -c cmd --help
error: invalid command 'bdist_wheel'
----------------------------------------
Failed building wheel for NanoVNASaver
Running setup.py clean for NanoVNASaver
Failed to build NanoVNASaver
Installing collected packages: PyQt5-sip, PyQt5, numpy, pyserial,
NanoVNASaver
Running setup.py install for NanoVNASaver ... done
Successfully installed NanoVNASaver-0.1.4 PyQt5-5.11.2 PyQt5-sip-4.19.19
numpy-1.17.3 pyserial-3.4
-------------------
I then ran:
$ python3.7 nanovna-save.py
and got:
python3.7: can't open file 'nanovna-save.py': [Errno 2] No such file or
directory
I had python-numpy installed, but I then tried installing python3-numpy
and then ran the install again. This time I still got the same warning at
the end of the install output, but the program ran. It would therefore seem
that python3-numpy is the required package.
The program does seem to connect to the nanoVNA and I was able to set the
start and stop frequency and run a scan which seemed to work. However, it
would seem that some component has failed. Any help would be appreciated.
|
Re: Questions about Firmware
A couple of questions.
How can I tell which version of firmware I have?
My NanoVna works fine as far as I can see.
Also works ok with the latest version of nanonva-saver.
I am mainly interested in HF. What advantages would I get by upgrading firmware?
Don m5aky
|
Re: Yet another NanoVNA PC app
On Fri, Oct 25, 2019 at 05:24 PM, QRP RX wrote: This data corruption happens due to errors in the NanoVNA firmware. You're
needs to upgrade to more fresh firmware, it has less errors.
First versions of NanoVNAsharp just hide these errors, so you don't know that
the data is corrupted.
MOD V3 shows you warning, because you're needs to know, that the data is
corrupted and you cannot believe it. Thanks for confirming that. Both edy555 and Hugen79 0.2.3 are fine with Mod3.
|
Re: NanoVNA newbie having problems with new unit
Hi,
the file name is "nanovna-saver.py". So the error you got seems to have
been because you tried to run a file that did not exist?
If the application works, then I don't think anything important has failed.
You don't mention which commands you tried running in which order, so I
can't tell what caused the "bdist_wheel" problem.
--
Rune / 5Q5R
toggle quoted message
Show quoted text
On Sat, 26 Oct 2019 at 11:37, <subs@...> wrote: It seems then, that the firmware version that I have is the latest by
Hugen.
With regards to the Save, thank you for the link, and this one makes more
sense as it is consistent with the menu I have. It seems that Trace setting
status rather oddly is saved in the calibration settings along with Marker
setting status. I just didn't envisage that as a calibration factor. As you
pointed out, it needs to be saved in SAVE 0, but under calibration rather
than the general system settings SAVE, which doesn't seem to save much
except:
- Touch panel calibration information
- Grid color
- Trace color
- Calibration data number loaded by default
That's sorted that one out.
I ran into difficulties with nanovna saver though. I already had the
pre-requisistes:
`python3-serial`
* `python3-pyqt5`
* `numpy`
The last of these is ambiguous which I will come to in a moment. I
followed the process in the readme and got this at the end of the output:
-------------------
Running setup.py bdist_wheel for NanoVNASaver ... error
Complete output from command /usr/bin/python3.7 -u -c "import
setuptools,
tokenize;__file__='/tmp/pip-bd9ju62f-build/setup.py';f=getattr(tokenize,
'open', open)(__file__);code=f.read().replace('\r\n',
'\n');f.close();exec(compile(code, __file__, 'exec'))" bdist_wheel -d
/tmp/tmp_eemos37pip-wheel- --python-tag cp37:
/usr/lib/python3.7/distutils/dist.py:274: UserWarning: Unknown
distribution option: 'long_description_content_type'
warnings.warn(msg)
usage: -c [global_opts] cmd1 [cmd1_opts] [cmd2 [cmd2_opts] ...]
or: -c --help [cmd1 cmd2 ...]
or: -c --help-commands
or: -c cmd --help
error: invalid command 'bdist_wheel'
----------------------------------------
Failed building wheel for NanoVNASaver
Running setup.py clean for NanoVNASaver
Failed to build NanoVNASaver
Installing collected packages: PyQt5-sip, PyQt5, numpy, pyserial,
NanoVNASaver
Running setup.py install for NanoVNASaver ... done
Successfully installed NanoVNASaver-0.1.4 PyQt5-5.11.2 PyQt5-sip-4.19.19
numpy-1.17.3 pyserial-3.4
-------------------
I then ran:
$ python3.7 nanovna-save.py
and got:
python3.7: can't open file 'nanovna-save.py': [Errno 2] No such file or
directory
I had python-numpy installed, but I then tried installing python3-numpy
and then ran the install again. This time I still got the same warning at
the end of the install output, but the program ran. It would therefore seem
that python3-numpy is the required package.
The program does seem to connect to the nanoVNA and I was able to set the
start and stop frequency and run a scan which seemed to work. However, it
would seem that some component has failed. Any help would be appreciated.
|
Re: NanoVNA newbie having problems with new unit
Hi John I had a look at the file "nanoVNA User Guide 2019-07-11 (PDF)|"
but the settings do not correspond to what I have on the device. Here are 3 menu maps for different firmware versions: /g/nanovna-users/wiki/User-GuidesUnder CONFIG there is just SAVE which I assumed would save the settings. That SAVE is nominally for touch screen calibration. It is possible that I need to update my firmware, but having reviewed that information
I am totally confused as to which firmware I actually require? Unless you identify problems with firmware you have, other than confusing/missing documentation and poorly organized menus, what you have should be good enough. Recent messages are more likely about recent firmwares. .. for which documentation is more likely outdated. There seem to be various versions by different people
and I am not sure which one is the de-facto or "official" version?
My current firmware version is: 0.2.3-1-g145a034 That is between 6 and 19 days old, per I have different problems with every version tried. For using nanoVNA standalone, I install Hugen's most recent AA dfu version from here:
|
This version has a larger screen. What do folks who have one think of it. Does it need any firmware upgrade ? Thanks, Dick, W1KSZ ======================================= Dick, Yes, I have one of these and been pleased with it. I updated to the current 0.0.3 firmware. It support's Rune's invaluable PC software: Gyula already mentioned the dedicated group: /g/nanovna-f/73, David GM8ARV -- SatSignal Software - Quality software for you Web: Email: david-taylor@... Twitter: @gm8arv
|
Re: NanoVNA newbie having problems with new unit
It seems then, that the firmware version that I have is the latest by Hugen.
With regards to the Save, thank you for the link, and this one makes more sense as it is consistent with the menu I have. It seems that Trace setting status rather oddly is saved in the calibration settings along with Marker setting status. I just didn't envisage that as a calibration factor. As you pointed out, it needs to be saved in SAVE 0, but under calibration rather than the general system settings SAVE, which doesn't seem to save much except:
- Touch panel calibration information
- Grid color
- Trace color
- Calibration data number loaded by default
That's sorted that one out.
I ran into difficulties with nanovna saver though. I already had the pre-requisistes:
`python3-serial`
* `python3-pyqt5`
* `numpy`
The last of these is ambiguous which I will come to in a moment. I followed the process in the readme and got this at the end of the output:
-------------------
Running setup.py bdist_wheel for NanoVNASaver ... error
Complete output from command /usr/bin/python3.7 -u -c "import setuptools, tokenize;__file__='/tmp/pip-bd9ju62f-build/setup.py';f=getattr(tokenize, 'open', open)(__file__);code=f.read().replace('\r\n', '\n');f.close();exec(compile(code, __file__, 'exec'))" bdist_wheel -d /tmp/tmp_eemos37pip-wheel- --python-tag cp37:
/usr/lib/python3.7/distutils/dist.py:274: UserWarning: Unknown distribution option: 'long_description_content_type'
warnings.warn(msg)
usage: -c [global_opts] cmd1 [cmd1_opts] [cmd2 [cmd2_opts] ...]
or: -c --help [cmd1 cmd2 ...]
or: -c --help-commands
or: -c cmd --help
error: invalid command 'bdist_wheel'
----------------------------------------
Failed building wheel for NanoVNASaver
Running setup.py clean for NanoVNASaver
Failed to build NanoVNASaver
Installing collected packages: PyQt5-sip, PyQt5, numpy, pyserial, NanoVNASaver
Running setup.py install for NanoVNASaver ... done
Successfully installed NanoVNASaver-0.1.4 PyQt5-5.11.2 PyQt5-sip-4.19.19 numpy-1.17.3 pyserial-3.4
-------------------
I then ran:
$ python3.7 nanovna-save.py
and got:
python3.7: can't open file 'nanovna-save.py': [Errno 2] No such file or directory
I had python-numpy installed, but I then tried installing python3-numpy and then ran the install again. This time I still got the same warning at the end of the install output, but the program ran. It would therefore seem that python3-numpy is the required package.
The program does seem to connect to the nanoVNA and I was able to set the start and stop frequency and run a scan which seemed to work. However, it would seem that some component has failed. Any help would be appreciated.
|
Re: Questions about Firmware
|
On Sat, Oct 26, 2019 at 03:16 AM, Dick wrote:
This version has a larger screen. What do folks who have one
think of it. Does it need any firmware upgrade ?
Thanks, Dick, W1KSZ
Sent from Outlook< >
Hi Dick, Try getting more information after logging in to nanovna-f group. ( /g/nanovna-f/) I know 2 versions have been released so far. () 73, Gyula HA3HZ
|
Re: NanoVNA newbie having problems with new unit
John, Glad you are making progress. The NanoVNA Web client is primarily used by people who want to save data from their NanoVNA while taking measurements in the field or away from their PC. The page by the author, , gives some sparse directions for Linux (Ubuntu). My advice is to go straight to Rune's excellent NanoVNA-saver application. Plenty of users in this group have it working under Linux and will be able to assist you if you have installation problems. The user guide at /g/nanovna-users/files/NanoVNA%20User%20Guide-English-reformat-Oct-2-19.pdf is the most recent English translation of the official on-line help document by cho45. The latest firmware release by hugen at should probably be considered the stable release and other releases later than his as experimental or beta. Hugen eventually merges some all or some of the features of the experimental releases into his master branch. If you are not seeing a proximity effect with your receive antenna then I'm not sure why your measurements are varying when you interact with the NanoVNA. Since you were able to fight through the variations then I'm glad you were able to get things to work out for you. -Herb
|
Re: NanoVNA newbie having problems with new unit
Thank you for your kind reply. My apologies for not checking out the "Files" and "Wiki" section. It does indeed have a lot of information and contains my answer regarding the issues with the switch and lots more!
Regarding your points:
1. Answered by WiKi. Thanks.
2. I had a look at the file "nanoVNA User Guide 2019-07-11 (PDF)|" but the settings do not correspond to what I have on the device. There is no RECALL/SAVE item, just RECALL under which there are 4 Recall options 0 - 4. Under CONFIG there is just SAVE which I assumed would save the settings. There is no SAVE 0. Under CAL there are SAVE options with SAVE 0 thru SAVE 4 and which I presumed relate to saving calibration setting profiles. It is possible that I need to update my firmware, but having reviewed that information I am totally confused as to which firmware I actually require? There seem to be various versions by different people and I am not sure which one is the de-facto or "official" version?
My current firmware version is: 0.2.3-1-g145a034
3. Yes, I am aware of the hand effect. I am using a shielded co-ax only 20cm long so the end of the antenna is approximately that distance away from the nanoVNA. The nanoVNA is also shielded well with metal plates front and back so I didn't expect that to be a problem. The guy in the video was plugging antennas directly into the nanoVNA, handling them and moving them about and yet the traces seemed to be rock steady. On mine, the peaks completely shift away from their position when my hand gets anywhere near the unit so was very prone to the hand effect. Looking at the Hardware Versions section on the WiKi, I believe that I do have the genuine article. I avoided the white version and have a black unit like the genuine one in the picture with NanoVNA written in the bold and with the correct font (no rounded V). On the board, everything seems properly shielded. I haven't yet removed the cellophane from the screen.
4. Thanks for confirming that. I will order in the items that I need.
I take your point about the learning curve which is why I was only going through the basics at this stage, i.e. calibration and a quick test following step by step with the help of a video. I just used a couple of my scanner antennas. In time I intend to make a further study. I don't have any other basis for comparison. I was hoping one day to get a spectrum analyser, but can't afford one for now and this nanoVNA should suffice for my present hobbyist needs. Even with the hand effect, I think I have managed to work out the best configuration for my loaded telescopic whip to pick up the frequencies of interest on the scanner, although it would have been much easier and more accurate if the trace remained steady.
Incidentally, I tried the Web client on my PC but without success. Firefox just gives a blank screen. With Chromium I was able to get to the web page at and it showed part of the menu with most of the options greyed out and blank frames. When I clicked Connect for the first time it listed a virtual USB device and paired it, but, I then got: "failed to open: Error: failed to open device". Unfortunately there is no troubleshooting info on the authors website and I couldn't find anything more generic elsewhere, for example on Google Chrome or Chromium. There is helpful information telling you how to pair and connect, but not in relation to this error, so any help here would be appreciated. Since I'm on Linux, I will probably also have a look at NanoVNA Saver.
John.
|
NanoVNA-F works fine with Rune's VNAsaver program. It is in a very sturdy metal case and I prefer it over the original nano. Frequency range is not an issue especially since the original nano extended performance above 1000Mhz is mediocre at best. Firmware upgrade is a breeze, none of the clunky and inconvenient way of the original nano. The best however is the screen size...it is well worth the extra money spend. My old eyes are happy. If they come out with a larger screen version of the new design sometimes down the road I buy it...otherwise it is of no interest to me.
Just my 2 cents.
Bilbo
|
This version has a larger screen. What do folks who have one
think of it. Does it need any firmware upgrade ?
Thanks, Dick, W1KSZ
Sent from Outlook<>
|
Re: Would anyone please recommend a good USA stocked Seller for NanoVNA
Sam,
I know you asked for a USA stocked seller but I wanted to ensure you are aware that the NanoVNA-H is already shipping from Chinese sellers and it probably wont be long before USA resellers start carrying them. They are manufactured by hugen who was the first NanoVNA OEM.
My NanoVNA-H cost $48.50 delivered from China. You should definitely consider purchasing it over the current NanoVNA's.
Advantages:
1. Cost is not much more than the current NanoVNA's. I expect $48.50 from Chinese sellers should translate to approx. $60 or less from U.S. dealers.
2. The NanoVNA-H comes installed in a nice protective case (See attachment). Similar 3-D printed cases for the current NanoVNA sell for over $10.00 on eBay.
3. The marketing photos show that besides the usual two SMA cables and USB-C to USB-A cable, a USB-C to USB-C cable is included.
4. Whatever your opinion regarding their necessity, the 5.1 k USB-C resistors, battery voltage diode, and Port RF shields are in place.
5. Hugen usually delivers his units with the latest firmware located at his NanoVNA-H GitHub page at the time of shipping. From the marketing photo's, it appears the new battery status firmware is loaded.
6. Hugen's units are usually pre-calibrated and ready to use.
7. Hugen is a member of this board and usually makes time to respond to NanoVNA-H and NanoVNA-H ver 2.0 related questions.
- Herb
|
On Fri, Oct 25, 2019 at 11:41 PM, hwalker wrote:
capture - unique; currently broken for my python scripts, since not ASCII;
returns display buffer in some(??) bitmap format.
- QRP seems to have gotten this working in his latest NanoVNA-Sharp branch
with latest -Q firmware.
Wrong information. capture command is not unique, it is available in all firmware versions, except these which is very-very old, completely outdated with a bunch of bugs. If you're still using so ancient and buggy firmware, I strongly recommend to update. You will get significant improvements.
|
Re: NanoVNA newbie having problems with new unit
subs,
As a newbie the first thing you want to do is check out the "Files" and "Wiki" sub-sections of this group. The icons to access either sub-section is located in the left margin of the page. There is a lot of info that has taken time and effort to assemble. If you don't find the info you are looking for in either of those subsections then try the "Search" button at the top of the page. This group is closing in on 6000 messages and odds are someone else has already "been there, done that".
There should probably be a hash tag "Newbie" topic as a lot of users are experienced with antenna analyzers but initially get lost when first trying to use the NanoVNA. A vector network analyzer can be used as an antenna analyzer but because it has so much more capability it has to be set-up correctly to give you the information you want to measure.
With an antenna analyzer you turn it on, tune to the frequency of interest and read the results off the display. There is usually only one connector on the antenna analyzer so it pretty obvious where you hook the antenna two. The NanoVNA has two connectors, Ch0 and Ch1. Complex impedance measurements, from which typical antenna measurements are made, are done at Ch0. Transmission measurements are done at Ch1. In order to make accurate complex impedance or transmission measurements you have to ensure the NanoVNA is properly calibrated. There is a ton of information in the Wiki sub-section on performing a calibration. There is also User guides and Menu quick operating guides to show you how to select only the displayed information you want. At first the displayed information is daunting, but with use you learn to get only what you need displayed.
As far as your specific questions:
1. A search through the messages for "switch" will show you that the multifunction switch is the least liked feature of the NanoVNA. The primary problem is that is polled rather than interrupt driven. That means the microprocessor doesn't respond as soon as you operate the switch. It may be performing other operations and gets around to checking if there is input from the switch when there is a break in those operations. This causes the operation of the switch to appear "laggy". For menu selection and numerical input, the touchscreen is more of a pleasure to use. The only time I use the switch is for marker movement, as trying to "drag" the markers using the touchscreen can be a chore. Having said all that, if the rocker switch is physically stuck to the left of right when you release it then that is a mechanical problem and I would see to exchange it.
2. You should thoroughly read the user manual on the Wiki subsection on saving and recalling configurations. "Save 0" always holds the configuration information that is displayed when the NanoVNA is powered on. If you changes are not specifically made using "Save 0" then they will not show at power on.
3. I am sure you've heard the term "hand effect". If the antenna is not in close proximity to the NanoVNA and the cable connecting the antenna and the NanoVNA is properly shielded then you shouldn't observe any noticeable "hand effect". If either of those conditions is not true then you will observe the effects of your body detuning the antenna as your hand approaches the NanoVNA.
4. Some of the NanoVNA's are sold without cables or OSL standards to lower their selling price. Is you already have those items then you can cut your cost that way. If you don't have those items then you generally pay more in purchasing them after the fact.
Hope you don't get discouraged. Like any other piece of test equipment, the NanoVNA takes time to learn to operate properly. If you have some past measurements on any antennas or other devices, compare that data with the NanoVNA . That is a good check of whether the NanoVNA is operating as it should.
- Herb
|
Oristo
David J Taylor
Gyula Molnar
Dick
