¿ªÔÆÌåÓý

ctrl + shift + ? for shortcuts
© 2025 Groups.io
Date

Re: NanoVNA-Saver 0.1.5

 

Hello Rune,

First of all many thanks for this great software!
Maybe you can watch the bandwidth calculation again.
A ripple on a bandpass does not capture the filter width correctly.
In the attachment a comparative measurement.

Best regards

Hans-Peter Prast, DL2KHP


Re: Wait for NanoVNA-V2.....

 

F-2 might be a nice instrument to wait for... hopefully w/full 4 port setup extended f range and the larger display.

Really I think there are solutions for the current display issue including the android and laptop/PC software.


Re: Wait for NanoVNA-V2.....

 

I for one would like to see options to hack in a larger screen. Even one
the size of the screen used on the HP/Agilent/Keysight HP8753D. It would be
great to be able to turn one of these into a bench instrument. Maybe a DVI
compatible output or standard VGA. After being used to a HP8753 screen size
it's hard to go back and having the response time of the built in display
is a must.

The smaller ones are great for field work but even those could use a larger
screen. Something like an option to use one of the ones used with the
Raspberry Pi like below would be wonderful.
These displays are very inexpensive:





Sam Reaves
ARS W3OHM
Owner and Moderator of:
LeCroy Owners Group on Groups.io (Current and Future Group)


Re: 1500Mhz, usable ?

Andy
 

Mine appears to be 100Hz steps.
Test method, use receiver, listen to span set for 300Hz and I can hear 3 distinct tones.
Does the newer firmware use lower steps ?

73 de Andy


Re: My NanoVNA is not recognised by DFUse when using V 0.2.3 firmware

 

I've been trying to get this working - keeps coming back and saying the ID doesn't match even though it does.?

Since the last commit to this was several years ago - there is most likely some bugs introduced by newer version of Android.
It would be really nice if CHO45 could integrate this into his webUSB app
...Larry

On Monday, November 11, 2019, 8:13:50 a.m. GMT-5, Oristo <ormpoa@...> wrote:

> Unfortunately I do not have another computer to do that

I found this GitHub project for DFU installation by Android app


Re: 1500Mhz, usable ?

 

I have heard that there are frequency rounding errors on some versions,
but I cannot determine if I have that issue because
I'm not sure how to set it up for a sweep, and advice greatfully received.
If you are using original firmware and touchscreen control, then this map shows
where to set START and STOP frequencies (under STIMULUS)


These settings can be saved, either under CAL or RECALL / SAVE


Re: Duplexfilter tuning question

 

I ordered a set of attenuators on Ebay.
Logarithmic and linear... I'm not at home right now but when I get back, I'll try it on the computer.


Re: 1500Mhz, usable ?

Andy
 

Thanks everyone for the info.

I have what appears to be a two trace version, 900Mhz, and to be honest it appears to be satisfactory.

No crashes etc.

Although there is one thing that I have not yet played with, and that is how to sweep a small signal range for xtal filters.

I have heard that there are frequency rounding errors on some versions, but I cannot determine if I have that issue because
I'm not sure how to set it up for a sweep, and advice greatfully received.

Not too fussed about a battery indicator, since I think it already has one, if I turn it on and there's no display then battery = dead ;-)

I quite like the idea of an auto find lowest SWR etc function, that could be useful, but no deal breaker, I just zoom in a bit more.

So, I guess that I may have aplay at some time,but I'm not in a rush.

73 de Andy


Re: Any plans to publish the NanoVNA board files

 

Google searches don't find specific details about the V2 design
Gabriel is the layout designer and RF engineer
/g/nanovna-users/message/3420
/g/nanovna-users/message/3984
/g/nanovna-users/message/4092
/g/nanovna-users/message/6544


Re: Any plans to publish the NanoVNA board files

 

You said that the firmware is already on GitHub


Re: My NanoVNA is not recognised by DFUse when using V 0.2.3 firmware

 

Unfortunately I do not have another computer to do that
I found this GitHub project for DFU installation by Android app


Re: Wait for NanoVNA-V2.....

 

The github page you refer to is from Henrik Forsten, so it is not "mostly a copy of this nice design", it is the very same design!

Op 11-11-2019 om 13:19 schreef erik@...:

Do have a look here:

30MHz - 6GHz, I do not see a SI5351 (yet?)

For now its mostly a copy of this nice design


Re: Any plans to publish the NanoVNA board files

 

Hi Gabriel,

What you are saying sounds fantastic. That is the kind of project that I would like to be a part of. I don't have a need to see the designs early. I'll be patient, and get involved when the product releases, and after I buy one. You said that the firmware is already on GitHub. Can you provide a link? Who is the designer for that? Google searches don't find specific details about the V2 design, just people talking about what they think it will be.

Thanks,

Dave


Re: Any plans to publish the NanoVNA board files

 

Trying one more time to add the attachments.


Re: Any plans to publish the NanoVNA board files

 

Hi Hugen,

Thanks for joining the conversation. I appreciate all of the work that you have put into this design, and for your efforts to turn it into an actual product. Your work seems to have been the trigger that made the NanoVNA so popular this year, and why I now own a NanoVNA. I love it. It¡¯s just what I needed.

I understand the things that you said in your post, but I don¡¯t agree with everything that you said. I do understand your reluctance to release the board files, but eventually that hurts your community more than the cloners. It is greatly appreciated that you share your schematics, but the photos of the PCA on your GitHub page are wrong. It seems that you do this on purpose to misdirect the cloners, but the only people that are really confused by it are the ones who want to support you.

It may have taken the cloners a little while to copy your designs, but it seems that they have finally gotten there. I¡¯ll attach photos. This is what they do, and they are fast at it. In fact, the clone from Amazon was at v3.2, while the official Nooelec board was still v3.1. You say that you could make your PCB better to distinguish, but the performance between the clone and Nooelec board was identical. My point is that the cloners will always eventually catch up. It¡¯s what they do. Trying to misdirect them by not providing accurate photos of your PCAs doesn¡¯t really slow them down.

The people in this group however rely on you to be open with what you are doing so that they can collaborate on the designs with you. That is why many of them are here. That is what makes this group a community.

I would suggest that you try a different tactic than misdirection to fight the cloners. Use authenticity and this community. These are two things the cloners don¡¯t have. I would suggest updating your GitHub page to provide accurate photos of the PCA, remove the complaints about cloning, and then do better marketing. Have people from the group write some articles for RTL-SDR, ARRL, etc. Have people on this group spread the word at Ham meetings, and so on. Focus on the things the cloners can¡¯t copy.

That¡¯s all I have to say. I hope you don¡¯t take offense to my comments.


 

How to overcome the need to turn off/on every time we plug the USB cable to PC?
Use QRP firmware:

Based on my own trivial experiments, metal enclosure for worse unshielded clone
makes things somewhat worse above 600MHz.
Otherwise, limitations appear to be from internal crosstalk and e.g. mixers' nonlinearity.


Re: Looking for firmware with battery indicator, 1500 and big font

 

On Sun, Nov 10, 2019 at 08:33 AM, KV5R wrote:


I will also note that your vbat offset works well for the 1N4148 diode I
installed; it indicates full for most of the cycle, then 2/3, 1/3, and when it
turns red there are only a few minutes before it shuts down. So it does what
it should! :)
if you worrying about battery indicator, you can try NanoVNA-Q:


it has allows to calibrate battery offset. So, you can tune it for your diode. In addition it shows real usage time battery percent, so if it shows 50%, it means that battery will be discharged after 1 hour (for 450 mAh which has 2 hours discharge time).


 

Hello Team,

Did anyone sucessfully inserted the nanovna inside a metal enclosure? Will that improve any accuracy and/or stability?

How to overcome the need to turn off/on every time we plug the USB cable to PC?

May I see some examples?

Cheers and thanks in advance!

Luis, CT2FZI


Re: 1500Mhz, usable ?

 

On Sun, Nov 10, 2019 at 06:47 PM, Andy wrote:


I'm not exactly seeing overwhelming evidence that I should upgrade to a
1500Mhz firmware.
I'd probably be better off with an old GDO and a field strength meter up there
;-)
As Rune mentioned above, 1500 MHz is not the main goal for newer firmware. The main goal is to fix errors, bugs, make more stable and more precise measurements, add new features (such as TDR and Group Delay track, which is missing from old firmware).

For example, old firmware have terrible spikes at 300, 600 and 900 MHz, also it returns unstable measurements and errors, sometimes it freezes and don't respond, it don't allows to enter exact frequency and may show wrong frequency (not these which is actually used).

In addition, old firmware don't allows to check Crystal filters, because it has limitation for minimum frequency span.

If you are ok with firmware which has a lot of bugs and errors and don't needs to measure filters, don't needs TDR and Group Delay track, you can stay with old firmware :)

Regarding to 1500 MHz range, new firmware is just allows to use it, but you can setup 50 kHz - 900 MHz range and it will works the same as old firmware. With exception, that a new firmware will have less bugs and errors. The new firmware just allows to use extended range, but if you don't want to use it, you can just don't use it. Just setup 50k - 900 M and it will works the same as old firmware.

For example NanoVNA-Q:
allows to use frequencies from 10 kHz. It works well from 10 kHz. For example, I tested ultrasonic transducers which working on 24 kHz. You can see in attachment. And as you can see I can check resonant frequency (24100 Hz) and even sound wave propagation delay between TX and RX ultrasonic transducers. Note, this is frequency range 20 kHz - 30 kHz :)

It will be just impossible with old firmware


Re: Wait for NanoVNA-V2.....

 

I would pay a double price to have bigger screen, appropriate internal
storage, and wireless capabilities.
Maybe somebody can set up a vote :-)

73 Ady
===========================

I've already paid double to get the nanoVNA-F. With the larger screen, and in a proper metal enclosure, it's a much more useful instrument than the toy smaller variant.

I would be happy to buy a wide-range instrument, but not without a larger screen and a boxed enclosure. I guess that the V2 will be more expensive anyway, so the difference for large screen and boxed should be less.

Cheers,
David
--
SatSignal Software - Quality software for you
Web:
Email: david-taylor@...
Twitter: @gm8arv