toggle quoted message
Show quoted text
On Mar 4, 2023, at 09:25, bowxyz@... wrote:
? Help. Newly purchased Nano VNA H4 March 2, 2023.
I've read several posts on the H4 model about firmware and each mention
identifying the proper version and the URL that is listed. ?Mine does not
have a URL listed. Version is 1.1.01 [p:401, IF20k, ADC:384k, Lcd480x320.
Build Time Dec 30, 2021.
I'm sure there are probably newer versions but I am unsure as to the
process to properly update.
Any help would be greatly appreciated.
|
Re: NanoVNA firmvare, compiled by DiSlord
#firmware
Scale factor for SWR = 0.250 = 250m (milli)
|
Re: NanoVNA firmvare, compiled by DiSlord
#firmware
I was also wandering why the SWR scale says 250m. FW version 1.2.14.
|
Help. Newly purchased Nano VNA H4 March 2, 2023.
I've read several posts on the H4 model about firmware and each mention identifying the proper version and the URL that is listed. Mine does not have a URL listed. Version is 1.1.01 [p:401, IF20k, ADC:384k, Lcd480x320.
Build Time Dec 30, 2021.
I'm sure there are probably newer versions but I am unsure as to the process to properly update.
Any help would be greatly appreciated.
|
Regarding noisy plots, I have used NanoVNA-App on both Raspberry Pi and Windows laptop. The RPi gave noticeably more noise but it was reduced in both cases with a ferrite clamp on the USB cable close to the NanoVNA.
--
Mike G8GYW
|
On Fri, Mar 3, 2023 at 05:54 PM, Siegfried Jackstien wrote:
if you calibrate the cable out then all should show near similar results
.. not??
measure without cable calibration can not work good so question is ...
did you calibrate out that 3m cable??
if calibrated (and calibration IS LOADED ALSO!!) then nanovna_app shows
near perfect results compared to internal calibration
only slight variations depending how high you have set averaging in the
device
higher average gives smoother curves but also a more exact calibration ...
dg9bfc sigi
This was a comparison of how well each one calibrated the same cable and measured a 1K DUT. A new calibration using the same cal loads was done at the end of the 3M cable for each test and then they were compared. The results for NanoVNA App, NanoVNA Saver and Standalone VNA should all be very close because they all are all calibrated the same and used the same 1K SMD resistor as the DUT. Averaging was not used in these tests - just one sweep. The standalone NanoVNA-H4 and NanoVNA Saver gave very similar results. NanoVNA did NOT do well. As "btomek" pointed out in hos first post there is something wrong with the NanoVNA App calibration algorithm. Try it your self and see what you get and post your results... Roger
|
if you calibrate the cable out then all should show near similar results .. not??
measure without cable calibration can not work good so question is ... did you calibrate out that 3m cable??
if calibrated (and calibration IS LOADED ALSO!!) then nanovna_app shows near perfect results compared to internal calibration
only slight variations depending how high you have set averaging in the device
higher average gives smoother curves but also a more exact calibration ...
dg9bfc sigi
Am 02.03.2023 um 23:09 schrieb Roger Need via groups.io:
toggle quoted message
Show quoted text
Follow-up to last post. Here are some more measurements of a 1K SMD DUT. Using NanoVNA -H4 (1.2.19 fw) in standalone mode (no PC) and comparing it to NanoVNA Saver and OD NanoVNA app. Measurements made on H4 were exported as a s1p file and imported into NanoVNA app for plotting.
1. Compare NanoVNA-H4 and NanoVNA Saver using 3M coax cable.
2. Compare NanoVNA-H4 and NanoVNA App using 3M coax cable.
3. Compare NanoVNA-H4 using 3M and 15 cm coax cables.
What is evident is close agreement between the 15 cm and 3M results when using the NanoVNA-H4 in standalone mode. So the long cable de-embedding works nicely on the -H4 firmware by DiSlord. Comparison between Saver and -H4 in standalone mode with 3m coax also showed good results. However NanoVNA app does not do well on 3m tests.
Roger
|
Follow-up to last post. Here are some more measurements of a 1K SMD DUT. Using NanoVNA -H4 (1.2.19 fw) in standalone mode (no PC) and comparing it to NanoVNA Saver and OD NanoVNA app. Measurements made on H4 were exported as a s1p file and imported into NanoVNA app for plotting.
1. Compare NanoVNA-H4 and NanoVNA Saver using 3M coax cable.
2. Compare NanoVNA-H4 and NanoVNA App using 3M coax cable.
3. Compare NanoVNA-H4 using 3M and 15 cm coax cables.
What is evident is close agreement between the 15 cm and 3M results when using the NanoVNA-H4 in standalone mode. So the long cable de-embedding works nicely on the -H4 firmware by DiSlord. Comparison between Saver and -H4 in standalone mode with 3m coax also showed good results. However NanoVNA app does not do well on 3m tests.
Roger
|
Thanks for the reply and information.
I did recalibrate and saved them to SD. But the RECALL FROM SD menu item isn't there in 1.2.14. I rolled back to 1.2.0 for now.
Regards
|
On Wed, Mar 1, 2023 at 10:05 PM, DiSlord wrote:
Calibrate device in measured range.
Interpolation not give good results for long cables (on big phase change for
measured points)
I agree that you should calibrate for the measured range and that interpolation must be used carefully. Here are two examples where I calibrate over 50k to 900 MHz and want to measure some 0805 SMD resistors. I am not using interpolation. Test conditions: --------------------- - NanoVNA-H4 was calibrated for 50 to 900 kHz. but measurements were made using OD NanoVNA app and NanoVNA Saver version 5.3 - Calibration in both programs was done using 401 points and without sweep averaging - 3m of RG-316 coax was used with SMD test jig on far end. Calibration load was 50 ohm 0805 SMD resistor (see attached for photo of setup). Two 0805 SMD resistors were tested (100 and 1k ohms) - NanoVNA Saver test results saved as s1p file and imported into NanoVNA app for plotting comparison. Results are attached. It is easy to see that something is wrong with NanoVNA App calibration on longer cables. Roger
|
Hi david
I am not at home right now so not near my laptop but this might help?
toggle quoted message
Show quoted text
On 2 Mar 2023, at 4:44 pm, David Reams <dwr.kj4de@...> wrote:
?It looks like it is conflicting with another port. Below is what I am
seeing on my laptop:
[image: image.png]
[image: image.png]
It appears that it is trying to conflict with Port 3. What is the best way
to solve the port contradiction?
Again, thanks for your help!!!
David
On Wed, Mar 1, 2023 at 4:36?AM robert miles <bob@...> wrote:
Hi David
If you right click on the STM Device in dfu mode and select properties.
Go to update driver.
Browse to the install directory for the STM software ( prob in programs
x86) and press enter.
That should fix it.
Other thing to check is that the com port assigned to the STM USB driver
is correct and not clashing with another in device manager.
Worked for me with W10 on 64 bit machine.
On 1 Mar 2023, at 12:35 am, David Reams <dwr.kj4de@...> wrote: ?I am still unable to get the nanoVNA to assign a port. I have Windows 10
and the nanoVNA will not automatically assign a port and the program
suggested above does not assign a port. When I place the nanoVNA in DFU
mode it does show "STM Device in DFU Mode". under Universal Serial bus
Controllers. Otherwise it shows "Unknown device" if not in DFU mode. No
port assignment is indicated at all. I might be having a problem with
the nanoVNA equipment itself. When not connected to a PC, the device
works
fine.
Maybe this problem can be solved, but if there is, in fact, a problem with
the device, no solution would be forthcoming.
Again, thanks for all of your help!!
David
.
On Tue, Feb 28, 2023 at 1:31?PM Roger Need via groups.io <sailtamarack=
[email protected]> wrote:
On Mon, Feb 27, 2023 at 06:33 PM, David Reams wrote:
Can you give me some more information on the STM boot loader and a source to
download?
David,
There are two different drivers required when using a NanoVNA-H or
NanoVNA-H4. One is required to get a COMxx: port so that your PC can
exchange data with a NanoVNA. The other driver is required when you want
to do firmware updates on your device.
COM port driver
---------------------
With Windows 10 and Windows 11 the required driver will be installed by
Windows when you connect your NanoVNA to a USB port. With Windows 7 and
Windows 8 you have to manually install the driver and then plug in your
NanoVNA. If Windows 10 fails to install the driver (rarely happens) you
can use the Windows 8 driver. You can check that the driver is working
by
plugging in and turning on your NanoVNA and then going into Device
Manager
and looking under ports to get the COM port number that has been
assigned
If you power off the NanoVNA the COM port should disappear from Device
Manager. I have put a copy of the drivers on my BOX account for you to
download. Here is a link where you can download it >>
Unzip and select the 32 or 64 bit version for your computer.
Firmware Upgrade driver
---------------------------------
This driver is only required when you want to upgrade your firmware. It
does not assign a COM port when the NanoVNA is plugged in and in DFU
mode.
DFU mode is activated in different ways depending on your device and the
firmware installed. Old devices had to be put in DFU mode by opening
the
case and shorting the Boot0 and DFU pins. In other cases DFU was
accessed
by a Menu selection. DFU mode on the -H4 is activated by depressing the
rocker switch down and powering on the anoVNA. When in DFU mode the
screen
will be black. You can check that the driver is installed correctly by
looking under USB controllers and seeing if it shows that your device
is in
DFU mode (see attached screenshot). I have posted a link to the DfuSe
package on my Box account for you. It will install the DFU driver and
the
DfuSe firmware upgrade application.
The Absolute Beginners Guide in the file section of this group tells you
how to install the DFU drivers that are needed for firmware update and
how
to install the latest firmware.
/g/nanovna-users/files/Absolute%20Beginner%20Guide%20to%20The%20NanoVNA/Absolute_Beginner_Guide_NanoVNA_v1_6.pdf
You don't have to register to get the DFU program and drivers. I have
put
a copy on my Box account for you...
Roger
<image.png>
<image.png>
|
I agree. A tiny bias above 1 along with noise. I plotted it just to compare with the earlier NanoVNA-App plot.
Brian
|
@Brian - It may be relevant. Comparison of Open in calibrated NanoVNA-App and calibrated NanoVNA-Saver. In Saver it looks better, oscillating around 1 and in NanoVNA-App it is > 1 for all points.
|
On Thu, Mar 2, 2023 at 07:52 AM, <btomek@...> wrote:
For OPEN and SHORT calibrators, such values are correct because ideal
OPEN = {1.0000000 0.0000000i}
SHORT = {-1.0000000 0.0000000i}
Adding the measurement noise and interference, we can get |Sij|>1
It's not due to noise. The data is noisy, but the real part is > 1 for all points. I have seen this in other VNAs. I don't think it's pertinent to your calibration issue. Brian
|
It looks like it is conflicting with another port. Below is what I am
seeing on my laptop:
[image: image.png]
[image: image.png]
It appears that it is trying to conflict with Port 3. What is the best way
to solve the port contradiction?
Again, thanks for your help!!!
David
toggle quoted message
Show quoted text
On Wed, Mar 1, 2023 at 4:36?AM robert miles <bob@...> wrote: Hi David
If you right click on the STM Device in dfu mode and select properties.
Go to update driver.
Browse to the install directory for the STM software ( prob in programs
x86) and press enter.
That should fix it.
Other thing to check is that the com port assigned to the STM USB driver
is correct and not clashing with another in device manager.
Worked for me with W10 on 64 bit machine.
On 1 Mar 2023, at 12:35 am, David Reams <dwr.kj4de@...> wrote:
?I am still unable to get the nanoVNA to assign a port. I have Windows 10
and the nanoVNA will not automatically assign a port and the program
suggested above does not assign a port. When I place the nanoVNA in DFU
mode it does show "STM Device in DFU Mode". under Universal Serial bus
Controllers. Otherwise it shows "Unknown device" if not in DFU mode. No
port assignment is indicated at all. I might be having a problem with
the nanoVNA equipment itself. When not connected to a PC, the device works
fine.
Maybe this problem can be solved, but if there is, in fact, a problem with
the device, no solution would be forthcoming.
Again, thanks for all of your help!!
David
.
On Tue, Feb 28, 2023 at 1:31?PM Roger Need via groups.io <sailtamarack=
[email protected]> wrote:
On Mon, Feb 27, 2023 at 06:33 PM, David Reams wrote:
Can you give me some more information on the STM boot loader and a source to
download?
David,
There are two different drivers required when using a NanoVNA-H or
NanoVNA-H4. One is required to get a COMxx: port so that your PC can
exchange data with a NanoVNA. The other driver is required when you want
to do firmware updates on your device.
COM port driver
---------------------
With Windows 10 and Windows 11 the required driver will be installed by
Windows when you connect your NanoVNA to a USB port. With Windows 7 and
Windows 8 you have to manually install the driver and then plug in your
NanoVNA. If Windows 10 fails to install the driver (rarely happens) you
can use the Windows 8 driver. You can check that the driver is working
by
plugging in and turning on your NanoVNA and then going into Device
Manager
and looking under ports to get the COM port number that has been
assigned
If you power off the NanoVNA the COM port should disappear from Device
Manager. I have put a copy of the drivers on my BOX account for you to
download. Here is a link where you can download it >>
Unzip and select the 32 or 64 bit version for your computer.
Firmware Upgrade driver
---------------------------------
This driver is only required when you want to upgrade your firmware. It
does not assign a COM port when the NanoVNA is plugged in and in DFU
mode.
DFU mode is activated in different ways depending on your device and the
firmware installed. Old devices had to be put in DFU mode by opening
the
case and shorting the Boot0 and DFU pins. In other cases DFU was
accessed
by a Menu selection. DFU mode on the -H4 is activated by depressing the
rocker switch down and powering on the anoVNA. When in DFU mode the
screen
will be black. You can check that the driver is installed correctly by
looking under USB controllers and seeing if it shows that your device
is in
DFU mode (see attached screenshot). I have posted a link to the DfuSe
package on my Box account for you. It will install the DFU driver and
the
DfuSe firmware upgrade application.
The Absolute Beginners Guide in the file section of this group tells you
how to install the DFU drivers that are needed for firmware update and
how
to install the latest firmware.
/g/nanovna-users/files/Absolute%20Beginner%20Guide%20to%20The%20NanoVNA/Absolute_Beginner_Guide_NanoVNA_v1_6.pdf
You don't have to register to get the DFU program and drivers. I have
put
a copy on my Box account for you...
Roger
|
On Thu, Mar 2, 2023 at 07:05 AM, DiSlord wrote:
Calibrate device in measured range.
Interpolation not give good results for long cables (on big phase change for measured points)
@DiSlord - But that's exactly right. The measurement range is identical to the calibration range, the number of points is also the same, the calibration frequencies are equal to the measurement frequencies, and the result in NanoVNA-App is incorrect. Note that your "GOOD" files also have invalid |S11| values. @Brian - For OPEN and SHORT calibrators, such values are correct because ideal OPEN = {1.0000000 0.0000000i} SHORT = {-1.0000000 0.0000000i} Adding the measurement noise and interference, we can get |Sij|>1 Another little error may have been added by a malfunctioning calibration in the NanoVNA-App.
|
This is how my (bought in 2023) H4_MS Model looks
Note the _MS at the end of the HW Version
And yes ... You can change the setting in the GUI too , if you have loaded the wrong one.
Just remember to do a save after changing it.
|
Thank you all for the valuable information. The NanoVna works with the new firmware without any problems.
73 Zdenek
|
Remember state - allow save some device settings after power off like:
Start/stop frequency
Bandwidth
Backlight
Options
Threshold - this option set frequency threshold after this device use harmonic mode for measure
Old calibration not possible load on new firmware, need recalibrate and save new
|
Hi there, I¡¯m running Hugen¡¯s 1.2.14 firmware, which I like because it lets you save more calibrations. It will also do more data points across the sweep.
But I lost some of the defaults along the way, so I have some questions.
What Expert settings do people use for stuff like Electrical Delay and Threshold?
And what does REMEMBER STATE do?
Lastly, I can save my calibrations to the SD card, but can¡¯t find a way to recall them from it!
Any guidance gratefully accepted. Thanks
|
Roger Need
Carsten F (OZ1FTG)
Zdenek OK2BQN