开云体育

@Rich: as it has been discussed off line - in case the Cable calculation (phase method) depends on the velocity factor and the exact frequency of the phase jump only, the limiting the freq range around the 180deg jump should give you the best result. Theoretically the increasing the velocity fact input precision (like 69.5%) and the printed out number of digits of the length (like 5 instead 4) would give you even better practical resolution then. 73

I bought this for Christmas abut 1 1/2 years but was too busy to learn how to use it.

I got it out today after my new TinySA arrived today, and tried to learn a few things. But the Control Knob will not work. I can't scroll the menus with the Control Knob, and I can't get it to calibrate the screen. It keeps rejecting my finger or stylus presses.
Is there a way to RESET it?

Or is there something simple to look for if I open the case?

Thanks,

Ken - NM9P

Hello everyone in NanoVNA land
Newbie here Having trouble upgrading firmware from
v0.2.3-2-g8ac9166 date of the build was oct 18, 2019
to the latest firmware.
I am able to enter into DFU mode from the menu of the NanoVNA
following the instruction in the Absolute Beginner's Guide on
page 45 , But when I start DfuSe Demo nothing shows on the Available DFU Devices
menu Block.

Using Windows 10 Operating system
System shows NanoVNA using STMicroelectronics Virtual Com Port
(COM3), but when I put the device in DFU mode, virtual com port disappears
any help with this problem will be greatly appreciated.

Hello everyone in NanoVNA land
Newbie here Having trouble upgrading firmware from
v0.2.3-2-g8ac9166 date of the build was oct 18, 2019
to the latest firmware.
I am able to enter into DFU mode from the menu of the NanoVNA
following the instruction in the Absolute Beginner's Guide on
page 45 , But when I start DfuSe Demo nothing shows on the Available DFU Devices
menu Block.

Using Windows 10 Operating system
System shows NanoVNA using STMicroelectronics Virtual Com Port
(COM3), but when I put the device in DFU mode, virtual com port disappears
any help with this problem will be greatly appreciated.
Thank You in advance for any help with this matter.

Vince,
In addition to reading the Beginner's Guide, please refer to the forum's WIKI page.
There is a lot of info there that points to message threads that cover questions already answered over the last 3 years.

You will also find links to HOW-TOs and info that provides more in-depth coverage of your new tool.

Also - you can't brick the device. I tried to.
If a F/W update fails, you just put the device back into DFU mode and try again.
Install the latest DiSlord firmware but beware - an H device can only use H FW - don't try H4, Lite, F or any other 'Nano' FW out there.
Install V1.1.00 firmware and you'll be all set to use the various PC interface applications.
Also note that a number of device owners have found the USB cables supplied with their units to be flaky. so in case you have any issues connecting to a PC, try another cable.

Finally - READ, Read some more, then read more after that.
Play/experiment with the unit.

Roger,
Thanks for the link, and I will check out the beginners guide.
vince

On Thu, Jun 2, 2022 at 03:30 PM, Vince Loschiavo wrote

I purchased from a local my NanoVNA-H
has version: > v0.2.3-2-g8ac9166 > date of the build was oct 18, 2019

so I don't brick this OG, what are the chances of updating the firmware to
something newer?

You can use the latest firmware by DiSlord for your -H. make sure you download the -H version (not the -H4).
It is available at this link....


I suggest you read the Absolute Beginners Guide in the Files section of this group. It describes the firmware update process.

Roger

Hi all,
newbie,
I purchased from a local my NanoVNA-H
has version:
v0.2.3-2-g8ac9166
date of the build was oct 18, 2019

so I don't brick this OG, what are the chances of updating the firmware to something newer?
I've checked the files section, but nothing this old..
any recommendations?
Thanks
Vince
N2AIE

@igor-m: that happens when you do not calibrate the specific frequency range prior the Measure->Cable (calibration made directly at the S11 connector). I've tried here with H4 and v1.2 flashed in (built from sources) with my H4's stock RG316 cable and the length difference is 1mm.
I set the Stop frequency (aprox 330MHz) such the phase on the Smith is pretty close to 180deg.

On Tue, May 31, 2022 at 09:47 PM, DiSlord wrote:

On Tue, May 31, 2022 at 06:02 AM, igor-m wrote:

Hi, out of curiosity I've made a measurement of my nanovna H4 stock RG316
cable (of length 163mm end to end, incl connectors).
NanoVna App shows 158.4mm, while H4 (Measure->Cable) shows almost identical
picture as Dislord's one, but with Z0=9k and length 1.6meter (instead of
~Z0=50ohm as on his picture below.). Both measurements done with open end.

H4

flashed with today's v1.2.

Set start frequency more low (cable impedance measured on half frequency from
point then smith rotate on 180 degree)

Hi Dislord, I posted 2 messages yesterday but they were not published here (no idea why).
Also pictures did not pass through.
H4 v1.2 (built form sources): It was my bad - I forgot to calibrate the range where I did the Cable measurement.
With calibration (and the phase just around180deg - such you see the jump before end of the graph) was Z0=49.75ohm and L=162mm.
Great result, imho!

Ok, my bad, I did not calibrate the range before the cable measurement, now the H4 measurement shows Z0=49.71ohm and length=162mm. Fantastic!

Your picture shows you do with 51 points. Did you try with 101 or 201?

Et voilà Roger, thanks to you !!

73's jean Marie F5VLB

On 2022-05-31 05:50:-0700, you wrote:

Hi, out of curiosity I've made a measurement of my nanovna H4 stock RG316 cable

I flashed v1.2 last night. Using cal from 2.5-32.5 MHz, 401 p. Changed freq range to 3-5 MHz
I have 3X RG316
3660mm
4580mm
4580mm
One connected M-F, and the other connected M-M, for a total length of
12.820m

Following the user manual...
Mult length X 4 = 51.280

Initial VOP estimate 70% yields frequency
4095164 Hz

So I chose a freq range of 3-5 MHz.
Initial length reported as 13.20m. When I removed a M-M adapter on the end, the length lost 10mm, which is reasonable.
13.2-12.820=0.38 which is significantly off, but VOP is a possible reason.
remove M-M adapter > 13.19m
VOP 70>68 > 12.82m.
So changing the VOP from 0.70 to 0.68 changed the reported length to what I physically measured.

Screen and s1p attached.

The phase might have been more accurate for finding the exact distance, but I just threw this together for example.

Continuing...
I got interrupted for 30 minutes, during which the nVNA was running and charging.
Returning, I reconnected the coax in exactly the same way and at the same location on the bench.
This time reported length is 12.88m, a change of 60mm.
I turned on phase, and moved the marker to the phase change. f = 3.955 MHz, vs my estimated 4.095164. Close enough.

I changed the freq range to 3.8-4.2 MHZ, with the understanding that the new range would use interpolated values.
Orig range 2.5-32.5 MHz = 75 kHz/step.
New range 3.8-4.2 MHz >> 400 kHz, meaning that only 3-4 original cal points are included in the interpolation. At least the target is in the middle of that range.

I recalibrated 3.8-4.2 MHz, 401 p. SOLI.
Length still reported as 12.88m. Phase f = 3.956 MHz.
Screen images and s1p files attached.
Note that changing VOP to 67% >> 12.69m, 69% >> 13.07mm, so this is as close as I can get.

The uncertainties are the changing length reported over time, the actual coax VOP, and the accuracy of the nVNA (see changing length).

I didn't have time to compare with TDR.

~R~
72/73 de Rich NE1EE
The Dusty Key
On the banks of the Piscataqua

Thanks for the link, Roger. I'm going to try using it with NanoVNA App. If
I feel adventurous, I may try fixing the screen. Thanks for your help.
Perry

On Tue, May 31, 2022 at 5:42 PM Roger Need via groups.io <sailtamarack=
[email protected]> wrote:

On Tue, May 31, 2022 at 02:11 PM, Perry Westberry wrote:

A few days ago, I was able to get the unit into DFU mode and it was
recognized in Device Manager. I installed the latest Firmware and was

still

getting a white screen. At the suggestion of another post, I left the
analyzer off for a few days with the battery disconnected. I powered it
back up today with the results that it now shows in Device Manager and I
was just able to run a calibration through NanoVNA Saver but the screen

is

still white.

This sounds like you may have a defective screen issue. I recall others
had this problem and opened up the unit and checked the solder
connections. Some cured it by gently re-soldering connections.

If you are going to use it as is with a PC program use NanoVNA App. It
will use raw uncalibrated data during calibration while Saver depends on a
calibrated NanoVNA. NanoVNA app also does firmware flashing. If you are
new to nanoVNA app see my previous post on it >>>
/g/nanovna-users/topic/91143866#28096

Roger

Thank you Roger, my friend F5WK Michel followed the procedure and all is working for him. Will do the same today.
Regards Jean Marie

The following files and folders have been uploaded to the Files area of the [email protected] group.

* /user manual and menu maps/nVNA-H4 v4.3_MS firmware 1.2 menu map 0100 AN14.zip ( /g/nanovna-users/files/user%20manual%20and%20menu%20maps/nVNA-H4%20v4.3_MS%20firmware%201.2%20menu%20map%200100%20AN14.zip )

*By:* Rich NE1EE <TheDustyKey@...>

*Description:*
nVNA-H4 v4.3_MS firmware 1.2 menu map 0100 AN14 Initial version of firmware 1.2 menu map

Thanks Rich, that's very helpful for those of us using EXCEL for data manipulation or graphing. Your equations are much tidier than what I was using.
Rudy N6LF

On Tue, May 31, 2022 at 02:11 PM, Perry Westberry wrote:

A few days ago, I was able to get the unit into DFU mode and it was
recognized in Device Manager. I installed the latest Firmware and was still
getting a white screen. At the suggestion of another post, I left the
analyzer off for a few days with the battery disconnected. I powered it
back up today with the results that it now shows in Device Manager and I
was just able to run a calibration through NanoVNA Saver but the screen is
still white.

This sounds like you may have a defective screen issue. I recall others had this problem and opened up the unit and checked the solder connections. Some cured it by gently re-soldering connections.

If you are going to use it as is with a PC program use NanoVNA App. It will use raw uncalibrated data during calibration while Saver depends on a calibrated NanoVNA. NanoVNA app also does firmware flashing. If you are new to nanoVNA app see my previous post on it >>> /g/nanovna-users/topic/91143866#28096

Roger

I'm using the latest version installed a few days ago.
Perry

On Tue, May 31, 2022 at 2:26 PM Roger Need via groups.io <sailtamarack=
[email protected]> wrote:

On Tue, May 31, 2022 at 06:33 AM, Jean-Marie Polard wrote:

I have a problem with the NanoVNA-H(4) and NanoVNA-App

I can connect it on com5 but it does not read the data and mention
always a number of points error

Does someone has a trick to solve this problem ?

What version of H4 firmware are you using?

The NanoVNA app uses a binary protocol to transfer sweep data. This is
different than the old ASCII protocol that was initially used by the
NanoVNA. If your firmware is over a year old you need to update it.

Roger