开云体育

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

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

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<>

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.

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

Howdy Sam,
I ordered this one from US ebay seller lemontree017 in Kentucky. He shipped same day via USPS 1st Class mail and I received in 4 days to Texas. He has sold 119 units and 99.5% user rating.
The unit I received is identical to the one NooElec is selling (but w/o the attenuators they add) and is ~$60.
It's the one with blue PCB, T-handle rocker, soldered battery wires, no diode, and snap-in shields.
Of course, that is no guarantee you'd get the same one.
73, --kv5r

I was gifted a brand new nanoVNA unit which was purchased from eBay. I had difficulty with doing the calibration step because the ut came without a 50 ohm SMA load and female thru connector. I found a BNC terminator and SMA adapter cable plus t-piece which I m using as a barrel connector to attach the 50 ohm load. No ideal, but at least I could in this way complete the calibration steps. However there are a number of problems which I am not sure whether are normal or whether the unit is defective which I would like to ask about.

Firstly, the little rocker switch is very poor and sticks when pushed to the left. Pushing down is temperamental. This is probably already a basis for asking for a replacement. I’m no sure whether the 50 ohm connector should have been included but that would presumably be another.

The other issues are less clear. For example, I disabled trace 3 and set a start and stop frequence and saved the config, but when I power back on, the config is lost and I’m back to default settings.

If I connect an antenna (airband) and scan from 100MHz to 150MHz I see the dip that indicates its resonant frequency on the top yellow trace, but this shifts about if I put my hand anywhere near the nanoVNA unit so that it becomes impossible to move the pointer to the peak to determine the frequency. I don’t see this happening in either of the three videos that I have watched so far. The SMA to BNC cable that I am using to connect the antenna is about 20cm long and is a standard far east product.

Any feedback would be appreciated. If these are easy to fix issues that might be expected given the cost of the product then I am happy to try and fix, otherwise I can arrange to get it sent back to the seller.

Thanks Larry,
I have a NanoVNA-H on order that has the USB resistors installed. When it arrives I'll be able to verify for certain if Android 7.0+ phones and tablets with USB-C connectors are dependent on the resistors being installed for use with the NanoVNA-Web-Client. I'll provide feedback to the forum unless someone else does first. That information should probably go under a separate hash tag NanoVNA-Web-Client topic.

BTW,
The NanoVNA-H was $48.50 delivered from China. If you don't mind a delivery date towards the end of November, I would definitely purchase 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 will translate to $60 or less from U.S. dealers.

2. The NanoVNA-H comes installed in a nice protective case. Similar 3-D printed cases on eBay sell for over $10.00.

3. The marketing photos show besides the two SMA cables and USB-C to USB-A, a UAB-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 at his NanoVNA-H GitHub page at the time of shipping.

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

I am a HF guy and plan to use the nanoVNA testing antennas and filters, matching ckts and projects in the 1-30 MHz range almost exclusively. I would be just as happy if the vna worked in this area only. Guys wanting capabilities in the 100MHz plus range seem to have plenty of options.
Wayne Reed, K9NE
Linton IN

11:04am #5728
Oristo wrote:

Draft nanoVNA shell [ab]user guide list - in order returned by shell 'help' …..

-----------------------------------------------------------------------
Some comments regarding the draft :

time - unique; perhaps useful for timing other commands? but less useful for that than e.g. linux time(1)

[per NanoVNA_Console_Commands_Oct-24-19a.pdf: Cannot be set, it is the Linux "time" command - Useful only if you have a RTC in the system]
- Do Linux and MAC systems have a RTC? Don't believe many windows systems do (industrial maybe?).

dac - unique; seemingly not associated with ADC gain for DSP. >>perhaps<< it may be related to touchscreen calibration ??

[per NanoVNA_Console_Commands_Oct-24-19a.pdf: It seems to set the output voltage of an analog output of the STM uP]
- Is this used internally to control a voltage controlled oscillator (VCO) or voltage controlled amplifier (VCA)?

data - with no args, scatter inphase and quadrature [for current port?] With args 0-6 "internal calibration table"
- "data 0" seems to return s-params for port 0 and "data 1" for port 1. Not specified what " Data 2-6" return.

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. May someone can
translate the C-Sharp code for dealing with the returned image data to Python.

vbat - unique; comparable to CONFIG-VERSION bottom line. IMO waste of space; should be in info..
- It would be informative if "vbat" and any other new commands added since the original Aug retail release included a blurb showing which firmware versions are required (i.e. 2.3.1+). Would also short circuit the inevitable, "I don't see that command on my NanoVNA." In the special case where additional hardware, such as the diode for vbat, that info would also be useful.

Regards,

-Herb

On Fri, Oct 25, 2019 at 08:17 PM, Oristo wrote:

Is some GitHub issue logged?

Herb,I don't have any USB-C devices (other than the nano).
If you read the specs on the adapter, it has the 5.1K pull-up resistors that tells the cellphone/tablet to become a USB host.
That means there will be 5V available on the USB-A port.
That is really all you need to supply the nano with power and a data connection.
Have a look at this TI document:

...Larry

ZL4AI replies: Yes you can do a lot with SP1 Files. The following software allows directly reading:

SWR - Standing Wave Ratio
Rs - Resistance, series form
Xs - Reactance, series form
Zmag - Impedance magnitude
Theta (deg) - Impedance angle
Rho (mag) - Reflection coefficient magnitude
RL (dB) - Return Loss, plotted as a negative number to show "reverse" scale (see note below)
Phase (deg) - Reflection coefficient angle
% Reflected Power
Q - Quality factor, |Xs| / Rs
Rp - Resistance, parallel form
Xp - Reactance, parallel form
Ls (?H) - Equivalent inductance for series Xs, both positive and negative
Cs (pF) - Equivalent capacitance for series Xs, both positive and negative
Lp (?H) - Equivalent inductance for parallel Xp, both positive and negative
Cp (pF) - Equivalent capacitance for parallel Xp, both positive and negative


Download:
Zplots.xlsx from AC6LA


and Rigexpert


and Sim Smith


From ZL4AI

On Fri, Oct 25, 2019 at 10:21 AM, Larry Rothman wrote:
….
All you need is a small USB-C to USB-3 adapter on the phone-end and use the cable that comes with the nano.

-------------------------------------------------------------------------------------------------------------------------------------

Larry,
What's the difference between that adapter and the similar USB-C to USB-A OTG cable that I have not had success with? Also, which smartphone or tablet with a USB-C connector were you able to get working with the adapter?

Tks,

Herb

A couple of the consolecommands aren't clear to me

Join the club!
... Wiki page .. table format seems to me not ideal

Draft nanoVNA shell [ab]user guide list - in order returned by shell 'help'
mostly tested on NanoVNA-Q-usb-test.dfu
Some functions are possible or easier by shell commands?than screen menus,
while others are unique. Listing includes questions and complaints:

help - response is as poorly organized as screen menus
exit - unique; restarts shell; inapplicable to screen menu
? ? ? ? ?( although it might be nice to have a screen reset menu option)
info - comparable to lower part of CONFIG-VERSION
threads - unique, but mostly useful for firmware development
version - comparable to one line in CONFIG-VERSION
reset - comparable to device power off/on; a waste IMO
? ?but may be useful for apps that get lost..
reset dfu - comparable to CONFIG-DFU
? ?also IMO a waste, given DFU may require hardware jumper
? ?when firmware configuration is corrupted.
freq - comparable to STIMULUS-CW FREQ, in theory
? a waste IMO; why not just `sweep` with one point?
? My testing discovered no use for it...
? 'frequencies' after still returns 101 values in sequence...??!!
offset - unique; I suppose this sets IF (stimulus - LO)
? ? ? /g/nanovna-users/message/2597
time - unique; perhaps useful for timing other commands?
? but less useful for that than e.g. linux time(1)
dac - unique; seemingly not associated with ADC gain for DSP ? ?
? ? >>perhaps<< ?it may be related to touchscreen calibration ??
saveconfig comparable to CONFIG-SAVE
clearconfig unique; claimed to clear ALL (e.g. cal, touchscreen) settings..
data - with no args, scatter inphase and quadrature [for current port?]
? ? ? ?- with args 0-6 "internal calibration table"
frequencies - unique alternative to TRACE display for current 'sweep'
? ? ?or (if pause) 'scan' setting; needed for building Touchstone files.
stat - unique; returns firmware developer stats
gain - unique; sets but does not return tlv320aic3204 ADC gains
power - unique; sets but does not return Si5351A output level
sample - unique; (partly) presumably works with 'port'
? ? appears broken in my firmware, always returns usage when passed options??
scan - unique; like sweep, but for pause
scanraw - unique; like scan, but more options:
? ? {channel(0|1)} {start(Hz)} {step(Hz)} {count} [average]
sweep - comparable to STIMULUS; sets and returns
test - unique, dead? watch this space - developers??
touchcal - comparable to CONFIG-TOUCH CAL
touchtest - comparable to CONFIG-TOUCH TEST
pause - comparable to STIMULUS-PAUSE SWEEP
resume - comparable to unsetting STIMULUS-PAUSE SWEEP
? ? ?IMO, ?'pause' should have 'on' ?'off' options
cal - comparable to CAL, but what is 'in' option
save - comparable to CAL-SAVE
recall - comparable to RECALL
trace - comparable to TRACE; returns, but does not set, options:
? ?TRACE0-4 FORMAT CH0-1 scale offset
edelay - comparable to DISPLAY-SCALE-ELECTRICAL DELAY
? ? ? ? ? which IMO is crazy to be under DISPLAY,
? ? ? ? ? because I suppose edelay are associated with CAL..?
marker - comparable to MARKER, except actually usable
? ? ? ? ?set marker number and index,
? ? ? ? ?returns active marker numbers, indices and frequencies
capture - unique; currently broken for my python scripts, since not ASCII;
? ? ? ? returns display buffer in some(??) bitmap format.
vbat - unique; comparable to CONFIG-VERSION bottom line
? ? ? ? IMO waste of space; should be in info..
transform - comparable to DISPLAY-TRANSFORM
? ? ?don't know why here; does shell return TDR data? How??
threshold - unique; sets frequency for switching to Si5351A harmonics

dump - unique; deprecated ?or disabled
? ? ? returns buffer with audio data from is ADC output of SA602 mixers

Folks,
All you need is a small USB-C to USB-3 adapter on the phone-end and use the cable that comes with the nano.


...Larry

this is well known bug of NanoVNA firmware.

Is some GitHub issue logged?