开云体育

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@...:

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

Trying one more time to add the attachments.

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.

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

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

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

To put some facts in this discussion I measured the S11 of a a 25 ohm resistor from 0.5MHz to 1500MHz.
The nanoVNA was connected via USB to a PC but running from a clean 5 Volt supply and TX power is fixed at 2
The light blue line in the first picture starts at 25 ohm at 0.5MHz and stays at aprox 25 ohm till around 1100MHz
Also the phase is stable so nanoVNA is usable for S11 till at least 1100MHz.
Although the calibration till 1500MHz looks good (see second picture for S11 if a open just after calibration) real measurements no longer have a lot of relevance, most probably due to some non-linearity in the mixers above 1100MHz
--
Erik, PD0EK

On Sun, Nov 10, 2019 at 02:49 PM, Andy wrote:

OK, so I see quite a lot of firmware updates appear to include 1500Mhz now.

Is it really usable ?

73 de Andy

There are many versions of nanoVNA on the market. My black nanoVNA is fine up to 900 MHz. At frequencies above 1 GHz the track is dirty, uneven, unusable compared to other instruments.
Lucio, I0LYL

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

On Mon, Nov 11, 2019 at 8:07 AM Gabriel Tenma White <
OwOwOwOwO123@...> wrote:

The reality is the bigger screen variants don't sell, as people always
seem to go for lowest price. However I do expect other players (probably
flyoob or hugen) to fill in the niche at some point, as no one has a
monopoly on V2 and I expect to see more different designs (unlike V1 which
is all based on the edy555 design).

On Mon, Nov 11, 2019 at 08:34 AM, Ron Johnson-K7UV wrote:

Just curious...what IS the approximate transmit level of the Nano VNA?

65 mVrms for 50 Ohm load (-10 dBm)
182 mVpp for 50 Ohm load
324 mVpp for 1 MOhm load

About -9 to -13 dBm

Just curious...what IS the approximate transmit level of the Nano VNA? Thanks, K7UV 73

They are the same, the difference between V3.1 and V3.0 only increases C38, V3.3 increases R41, R42.
hugen

Re: open source.
V2 design files *will* be open source, both schematics and layout designs (gEDA PCB), and a few simulation files as well (RFSim99 & LTSpice & PLL simulations). The firmware is already on GitHub. The hardware designs will be published at product release time. If anyone wants to look at the designs *now*, you can send me a PM or add me on discord (スメグマ#2236), but please keep it to yourself until V2 is available for order as cloners can work faster than we do and rush a half baked design to market earlier than us.

Re: DL9CAT version 0.4.0-2? I have encountered the following problem. CW FREQ once started can not be stopped,you have to shut down the device.

73 Corneliu
On Saturday, November 9, 2019, 06:03:41 PM GMT+2, DL9CAT <groups.io@...> wrote:

> The only little problem I see in reald is it doesn't reverse text colors (fg/bg) to show which trace is selected, as hugen does.

Should be fixed now. Please test.

73 DE DL9CAT

No further differences with 3.0 / 3.1
I already checked it before
/g/nanovna-users/message/2148

Roland,
I think the computer is set for logarithmic scaling, but the
NanoVNA display is set for linear scaling. Values near zero cause
deep downward spikes on a logarithmic display.
--John Gord