Re: New user: NanoVNA-H how to determine hardware version
On Mon, Jan 20, 2020 at 08:29 AM, Alan G3XAQ wrote:
" 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. "
==============================================================
Alan,
I have both NanoVNA-H versions 3.3 and 3.4. I found the easiest way to tell the difference between versions, without opening the case, is turning the unit off and observing the power LED. On ver 3.4 the LED extinguishes immediately, whilst on ver 3.3 it stays illuminated for a few moments like the original NanoVNA.
- Herb
|
Re: Improving the performance of a pre-V3.4 original Hugen nanoVNA
Well, I did the component changes on my version 3.3 to version 3.4 NanoVNA-H (resistors only).
Using my 4 point precission LCR measuring device I measured @ 10kHz? directly on the connectors, VNA power off :
CH0 = 68.82 Ohms (not so good)
CH1 = 50.268 Ohms (good)
I did a low frequency symulation of the in- and output-circuits and the results are conform my measurements.
For what it's worth, certainly not for HF and high up.
Jos
I
Op 20-1-2020 om 15:49 schreef hugen@...:
toggle quoted message
Show quoted text
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: We started selling nanoVNA-H4 using STM32F303CCT6 and 4-inch LCD
I just had contact with Maggie less then 3 hours ago, and made payment via paypal.
Also she sayd its CNY overthere so will be at work again for shipping the goods February 4
|
Re: *** FIX FOR NANOVNA-SAVER PYQT5 INSTALLATION PROBLEMS ON LINUX MINT 19.3 ***
#nanovna-saver
toggle quoted message
Show quoted text
Le lun. 20 janv. 2020 ¨¤ 12:19, Larry Rothman <nlroth@...> a ¨¦crit : Just looked - your file isn't there.
On Monday, January 20, 2020, 12:14:21 p.m. GMT-5, Nick <g3vnc@...>
wrote:
Just uploaded into Files/NanoVNA PC
Software/NanoVNA-Saver/nvna-s-pve-rev-a.pdf.
Documents a no compromise fix for the pyqt5 installation problems recently
reported by many users on various Debian based distributions.
|
Re: *** FIX FOR NANOVNA-SAVER PYQT5 INSTALLATION PROBLEMS ON LINUX MINT 19.3 ***
#nanovna-saver
OK, Here is the full link: /g/nanovna-users/files/NanoVNA%20PC%20Software/NanoVNA-SaverFolks, When uploading files, please try to NOT use spaces in the filename. Use dashes, underscores or periods. The problem here is that the Groups.IO website replaces all spaces with %20 and the filename becomes muddled. Thanks! Larry
|
Re: *** FIX FOR NANOVNA-SAVER PYQT5 INSTALLATION PROBLEMS ON LINUX MINT 19.3 ***
#nanovna-saver
I will test this when I will be home tonight.
But this seem to be a very good solution.
Pierre VE2PF
toggle quoted message
Show quoted text
Le lun. 20 janv. 2020 ¨¤ 12:14, Nick <g3vnc@...> a ¨¦crit : Just uploaded into Files/NanoVNA PC
Software/NanoVNA-Saver/nvna-s-pve-rev-a.pdf.
Documents a no compromise fix for the pyqt5 installation problems recently
reported by many users on various Debian based distributions.
|
Re: nanovna-saver cal panel won't fit gnome screen
On Sun, Jan 19, 2020 at 03:09 PM, Nick Kennedy wrote: Anyone got a suggestion for this? Hold down the Alt key then left click, drag the window. HTH Nick G3VNC
|
*** FIX FOR NANOVNA-SAVER PYQT5 INSTALLATION PROBLEMS ON LINUX MINT 19.3 ***
#nanovna-saver
Just uploaded into Files/NanoVNA PC Software/NanoVNA-Saver/nvna-s-pve-rev-a.pdf.
Documents a no compromise fix for the pyqt5 installation problems recently reported by many users on various Debian based distributions.
|
Re: We started selling nanoVNA-H4 using STM32F303CCT6 and 4-inch LCD
nanoVNA-H4 (using STM32F303CCT6 and 4-inch LCD) arrived today via UPS.
Now we need to study and understand the differences compared to the previous version.
--
*73, Lucio I0LYL Rome, Italy*
|
Re: Firmware compatibility
Hi Hugen Just got the NanoVNA-H4 delivered to day. I have some issues which I have raised to the manufacturer as the USB C entry is blocked by the upper half of the case (a rim is not milled away). Then also there is stray lines as residual if previous traces and also single pixels of different colors is glowing. Eventually these disappear again when written sometime later, when a new trace is "passing by" else they are permanent. Just to let you know if you do not know this or you know a fix. The mechanical issue may be fixed by taking the unit apart and mill the excess part away if the case is easy to take apart. Anyway it look very fine and looking forward to try it out. I have pictures if you are interested so mail me directly to kurt@... Kind regards Kurt -----Oprindelig meddelelse----- Fra: [email protected] < [email protected]> P? vegne af hugen@... Sendt: 20. januar 2020 04:18 Til: [email protected]Emne: Re: [nanovna-users] Firmware compatibility NanoVNA-H rev3.4 is fully compatible with previous versions of NanoVNA firmware. The NanoVNA-H4 uses a Cortex-M4 MCU and a 4-inch LCD, so it is no longer compatible with previous firmware versions. hugen
|
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.
|
Kurt Poulsen
Larry Macionski
Gyula Molnar