Re: New user: NanoVNA-H how to determine hardware version
Just open it up - its only 4 screws. You will see the board version on the PCB and also will see if D2 is installed or not. Mine arrived a few days ago. PCB is v3.3 and the firmware was dated November 25. D2 was installed as well.
|
Re: New user: NanoVNA-H how to determine hardware version
Hi Alan,You most likely have hardware version 3.3 which is OK. V3.4 is the latest and that came out in Dec.
You should update to the latest firmware that came out over the weekend. Please review the last 20 posts or so for the link or just go to
Please refer to the forum Wiki for all the info you'll need in order to use the NanoVNA.
toggle quoted message
Show quoted text
On Monday, January 20, 2020, 11:29:43 a.m. GMT-5, Alan G3XAQ <alan@...> wrote:
I got a Nano-VNA-H off eBay for Christmas. It has a black plastic case with a Q-code on the label that just seems to contain nanovna.com according to my iPhone. The label also has a serial number 19110234. The label lists 3 frequency ranges covering 50KHz-1.5GHz .
When powered up CAL->Version gives the firmware version as 0.2.3-3-g8ac9166 and build time October 18 2019
None of this seems to tell me which hardware version I have received. I've trawled the messages on here and can't see how to find it. I would like to know because I want to update to later firmware and there are comments in the release notes about 1N4148 or? schottky diodes in different hardware versions needing battery voltage calibration commands. Do I really need to pull the hardware to bits and examine the PCB?
Thanks, Alan G3XAQ
|
Re: Firmware Won't Update
Hi Gyula
Eric provided the solution, I was basically saving and reusing my existing firmware, but all sorted now, so thanks to all for your help.
Dennis G8IMN
|
Re: Improving the performance of a pre-V3.4 original Hugen nanoVNA
Hi Eric,
Thanks for your experiments to improve the nanoVNA.
And buy some flux remover to clean up the mess
Reinier
Op 20-1-2020 om 17:31 schreef erik@...:
toggle quoted message
Show quoted text
Just for reference the locations of the resistors you have to change
|
Not sure why you created a rtf file for the screenshot, the result is poor
quality, the details are unreadable.
toggle quoted message
Show quoted text
On Mon, Jan 20, 2020, 10:08 AM n2msqrp <mstangelo@...> wrote: I've been checking my coax using NanaVNA Saver 0.2.2-1 on a NanoVNA-H with
Hugen 0.4.5-4-g96e7efe firmware.
I have a piece of 75 ohm Commscope F-11 coax going to a junction box in
the yard, I believe thet the far end is open.
I ran the TDR function. The Estimated cable length 41.104m (134ft 10.3in)
seems correct but I don't understand why I get this stair step graph with
reflections at multiples of the 41.1m length.
I've attached a screenshot named TDR Commscope F-11 in the files section.
Mike N2MS
|
Re: Improving the performance of a pre-V3.4 original Hugen nanoVNA
|
New user: NanoVNA-H how to determine hardware version
I got a Nano-VNA-H off eBay for Christmas. It has a black plastic case with a Q-code on the label that just seems to contain nanovna.com according to my iPhone. The label also has a serial number 19110234. The label lists 3 frequency ranges covering 50KHz-1.5GHz .
When powered up CAL->Version gives the firmware version as 0.2.3-3-g8ac9166 and build time October 18 2019
None of this seems to tell me which hardware version I have received. I've trawled the messages on here and can't see how to find it. I would like to know because I want to update to later firmware and there are comments in the release notes about 1N4148 or schottky diodes in different hardware versions needing battery voltage calibration commands. Do I really need to pull the hardware to bits and examine the PCB?
Thanks, Alan G3XAQ
|
I've been checking my coax using NanaVNA Saver 0.2.2-1 on a NanoVNA-H with Hugen 0.4.5-4-g96e7efe firmware.
I have a piece of 75 ohm Commscope F-11 coax going to a junction box in the yard, I believe thet the far end is open.
I ran the TDR function. The Estimated cable length 41.104m (134ft 10.3in) seems correct but I don't understand why I get this stair step graph with reflections at multiples of the 41.1m length.
I've attached a screenshot named TDR Commscope F-11 in the files section.
Mike N2MS
|
Re: nanovna-saver cal panel won't fit gnome screen
Nick,
I have a "beautiful" Flat Screen Sony, it was a Christmas gift from a dear lady friend. Back when LCD flat Screen Monttors were $250+. I was living in New England and left there 14 years ago. It keeps playing. It is 4:3 screen format.. I use it with a 4 port KVM in the hamshack. (Win Server, Win 7, Linux Mint, Win 10)
The calibration box on Win 7 on that 4:3 screen does exceed the screen size, but I can "drag" it around. at pop-up 75% is visable, So I'm ahead of you, as far as my GUI... My graphs are not perfectly formatted to my screen, perhaps better looking on a widescreen.
I hope the author places this on his "Honey do list" but More important is the "real" nuts and bolts of VNA that we so appreciate of the program to date.. I can click and drag just fine..
I also appreciate multi platform versions the author is working with.. goes beyond my pay grade indeed.
|
Sorry, I think I got it wrong. Then the ST-Link v2 dongle remains.
|
On Mon, Jan 20, 2020 at 04:07 PM, <brianbgarber@...> wrote:
Thank you both for the information! I think my issue may be a bit different
(maybe) because I am able to enter DFU mode on the nanoVNA, it's just that the
DfuSe Demo software no longer recognizes the device once in that mode. Also, I
can connect via the STM32CubeProgrammer program over USB (see attached png).
Thankfully my nano isn't bricked, but I can't seem to update it over DfuSe
Demo.
If you don't recognize it, you can use USBDeview Utility to see what's preventing it. If your mouse and keyboard are both usb, do not delete it! Delete and reinstall the troublesome or unnecessary driver. I hope this is the solution.
|
Re: We started selling nanoVNA-H4 using STM32F303CCT6 and 4-inch LCD
|
Re: Firmware Won't Update
Hi Dennis,
To date, I've only upgraded the firmware once with the ST-Link dongle because it was in my account for a different reason.
I had no problem with that, otherwise someone would recommend it if DfuSE fails the upgrade.
You can also find a detailed description in the wiki or on my site (ha3hz.hu).
Hope I was able to help with upgrades.
73, Gyula HA3HZ
|
Re: We started selling nanoVNA-H4 using STM32F303CCT6 and 4-inch LCD
I would like to purchase one using paypal..as others have done..sent two emails to Maggie king with no response ?
|
Thank you both for the information! I think my issue may be a bit different (maybe) because I am able to enter DFU mode on the nanoVNA, it's just that the DfuSe Demo software no longer recognizes the device once in that mode. Also, I can connect via the STM32CubeProgrammer program over USB (see attached png). Thankfully my nano isn't bricked, but I can't seem to update it over DfuSe Demo.
|
Re: Improving the performance of a pre-V3.4 original Hugen nanoVNA
On Mon, Jan 20, 2020 at 09:24 PM, hwalker wrote:
A similar discussion in Japanese (use Google translate or similar)
. His follow-up
discussions in January of this year are also an interesting read.
- Herb
I checked the content of this blog and some of the issues mentioned come from the wrong shield of the bad clone. Some modifications may not apply to a good NanoVNA. Our manufactured NanoVNA-H has good isolation.If you have better suggestions for improvements that can be feedback on github, we will try it and apply it to the next version of NanoVNA-H after verification, and send you the improved version to verify the modified effect. hugen
|
Re: Firmware Won't Update
This may be a stupid remark but: The DFU "Upload" is for making a backup of your nanoVNA flash memory to you PC Use the "Choose" and "Upgrade" keys to update the firmware -- NanoVNA Wiki: /g/nanovna-users/wiki/homeNanoVNA Files: /g/nanovna-users/filesErik, PD0EK
|
Re: Firmware Won't Update
Hi Guyla, I'm sure it's connecting with the pc, it works with vnasaver, and when placed in dfu mode, shows up correctly in usb devices, also the upgrade software shows complete success.
Dennis G8IMN
|
Re: Improving the performance of a pre-V3.4 original Hugen nanoVNA
|
Re: Improving the performance of a pre-V3.4 original Hugen nanoVNA
That is abt the Tx output inpedance not the RX
Jos
Op 20-1-2020 om 14:24 schreef hwalker:
toggle quoted message
Show quoted text
A similar discussion in Japanese (use Google translate or similar) . His follow-up discussions in January of this year are also an interesting read.
- Herb
|
Larry Macionski
Gyula Molnar
Brian Garber
