开云体育

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

On Mon, Nov 11, 2019 at 04:14 AM, <hugen@...> wrote:

For the enthusiasts to provide a schematic is enough, I will soon update my
PCB to NanoVNA-H V3.4

Hi hugen, could you please share schematic for PCB rev V3.1. This is my NanoVNA PCB, but I don't have schematic for it.

The only schematic that I found is V3.0 (thanks to Larry Rothman). I know, the difference probably is not significant, but I want to know what exactly is different.

Next time to reboot PC. If it doesn't helps and you don't hear USB connected device "ding" sound when you connect USB cable in DFU mode, then go to Control Panel => Device Manager, click on computer with rigth mouse button and select context menu "Scan for hardware changes".

In most case it will solve issue.

I have learned that three clone manufacturers have copied four different NanoVNAs, they are reverse engineering of my earlier versions and claim that they are doing improvements, but they don't know what to do to make NanoVNA work better. .Once I publish the PCB files they can be used directly for manufacturing, but they may sell unqualified products, making it difficult for users to identify what the merchant is selling through photos. I also noticed that some irresponsible merchants showed photos of the versions I made on ebay or aliexpress, but the actual sales were bad clones, I didn't have the ability to stop them, but I could make my PCB better to distinguish. Some regular users may not understand NanoVNA as well as active users in this group, and they will leave a bad impression when they receive a bad clone. For the enthusiasts to provide a schematic is enough, I will soon update my PCB to NanoVNA-H V3.4, the UART port will be connected to the 2.54mm pins, Geeks can make their ideas through the UART interface . I am actively communicating with edy555 and we will bring some group ideas to NanoVNA.
Looking at the images shared by the group users, the version sold by Nooelec should be the version I sold in September. I don't know where they bought the version and sold it, but it was made by me.

hugen

I read that nanoVNA-V2 feels stuck in a price box, so they
won't be upgrading the display size.

I don't get that at all.

Why not offer various versions, e.g. V2a, V2b, V2c with different
display sizes, and perhaps -4, 8, 16 (or whatever) for onboard
memory or some other significant option?

David KD4E

Just calibrate the touch screen and it will work well.

hugen

Hi Herb,

Thank you for the response. Regarding your statement "Did you check out the ttrftech GitHub repo that Larry referenced? Specifically . The schematics and firmware for the hugen clone that all the other clone manufacturer's are using is located there." This is actually not true, and is exactly the reason that I am looking to create a more transparent release of the hardware design. The schematic at the link you mentioned is for edy555's original design. So is the picture of the board. The boards that are in edy555's current designs at Nooelec, and the clone designs on Amazon are not using these schematics. They are all using the rev 3.x hugen79 design that can be found here instead. .

Additionally, these are not board designs, they are only schematics. A complete board design package would also include PCB layout files, netlists, bill of materials, etc. from an application such as KiCAD. It may be that hugen79 will not feel comfortable publishing this information, and I would understand that given that he is also selling it. My previous point was that the clones (at least the one I purchased) have already reverse engineered this information. They already have it. This means that the time is approaching where keeping this information hidden actually benefits the Chinese manufacturers more than the community supporting the real designers.

I would agree with the design of the year award recommendation. This design is a great contribution to hobbyists and ham radio enthusiasts everywhere, and I would like to see both designers rewarded for all of their work.

Dave

#77: On the current explanation of full one-port "error" model
in our sow - facupov, as always - with an Application to the
Measurements of Two-Port Devices

Hello,

Well, after the previous related messages, we think that we are
now enough prepared to ask you to allow us, please, to attempt a
presentation of the current explanation of the so called full
one-port "error" model in our sow - facupov, as always.

- - - - - - (c) gin&pez@arg (cc-by-4.0) 2019 : start - - - - - -

In our sow, the full one-port "error" model is an Abstract or
Virtual Two-Port V2P located inside [AnyVNA] (incl. [NanoVNA])
and having as its ports the Virtual Measurement Port VMP [#74]
and the Real Load Port RLP.

This V2P is obviously characterized by the [LeastVNA]
description of G-mini:

G = (g-l)*(o-s)/[(g-o)*(s-l)-(g-s)*(l-o)]

Therefore, using the above concepts, we can measure, indirectly
- as in the case of one-port - : (a) either the S11, S12S21, and S22
parameters of any Two-Port Device appropriate to be connected
by the one port of its two ports to the RLP of the V2P and/or
(b) any unknown One-Port G' appropriate to be connected to the
other port of this Two-Port Device, using this very same G-mini:

G' = (g'-l')*(o'-s')/[(g'-o')*(s'-l')-(g'-s')*(l'-o')]

- - - - - - - end : (c) gin&pez@arg (cc-by-4.0) 2019 - - - - - -

REFERENCE

[#74] The Virtual Port - "Revealing" the Most Confusing
"Secrets" of "Error" Models - 7 November 2019 :
/g/nanovna-users/message/6604

Sincerely,

gin&pez@arg

:77#

Jos, you might want to try going back to an earlier windows restore point to when it was working and detecting dfu.?



On Sun, 10 Nov 2019 at 6:57 PM, Jos Stevens<jrs@...> wrote: Hi Herb,

Thanks for your reply,

Unfortunately I do not have another computer to do that, but as you
describe it it looks very simular , I'm unning Win10 on a HP i7, 8 GB of
RAM, NanoV.BNA runs OK using the NanoVNA-Saver software and DFUse dos
not detect the device, touch the device manager shows STM32 "
bootloader" so my gutfeeling says the problem is in the DFUseDemo
installation, though it performed well before. I will do some more
investigation tomorrow for now it's very late.

Thanks for your info best regards

Jos

Op 10-11-2019 om 23:26 schreef hwalker:

Hi David,
Publishing the PCB design won't really help as there are many ways to layout that will let someone create the same device. The biggest issue is crosstalk and bridge design. Have a look at the 'dead bug' designs that Erik K has put together (photos in the forum archive) and you'll see what can be done with a little ingenuity.?

The ttrftech design was partially copied from a similar device created by a couple of Hams from Texas. In fact, there are many designs using Sa612 mixers and si5351 clock.? It's just that hugen's design shrunk it all down to the size of a deck of cards and priced it so as to make it available to the masses.?

The NanoVNA has essentially now become a 'blackbox' where new features are all being created through firmware tweaks.?
Wait for NanoVNA-V2.....

73... Larry


On Sun, 10 Nov 2019 at 5:23 PM, dhu1342@...<dhu1342@...> wrote: Hi Larry,

That’s OK about the misunderstanding. I totally get it. The history and ownership of the NanoVNA is very confusing given all of the inaccurate information available. After my initial research into the NanoVNA, I tried to be good, and purchase from the “original designer”, thinking that all other designs were fakes, but when I tried to upgrade the D2 diode to get battery level, I realized that all of the designs, including the one that I purchased from Nooelec, and the clone my friend purchased from Amazon, were actually based on the hugen79 hardware design. Technically, that seems to make hugen79 the “current designer” of the NanoVNA hardware.

Part of the confusion and lack of clarity between the designs seems to originate from both designers wanting to productize the design to make money. That seems to be getting in the way of true collaboration. Neither designer seems to have good purchasing options however. The nooelec site only sells the NanoVNA as part of an expensive bundle, and the Alibaba site (despite the beautiful packaging and presentation of the hugen79 product) requires registration and mandatory acceptance of spam emails for purchasing. I can’t imagine that these are effective approaches compared to the Chinese clones that have saturated places like Amazon, come up first in NanoVNA searches, and are easily purchased by themselves with no registration at all.

This is getting off topic (sorry), but I wonder if both edy555 and hugen79 would consider adding a donate button at the bottom of their GitHub pages (similar to the mihtjel/nanovna-saver page). I would like to thank both of them for their contributions in making this wonderful product. I can’t express how much I appreciate what they’ve done, but I would rather send them a donation directly than try to choose between whose distributor to purchase from.

Along those lines, both designers have something that the Chinese manufacturers don’t. Authenticity and the following of an interested group of enthusiast. I am not sure whether trying to fight the Chinese manufacturers at their own game is a winning strategy. If the designers could align on a common NanoVNA purchasing option, then the rest of us could help spread the word to ham radio clubs and beyond of where to buy the authentic NanoVNA.

Back to my original topic. If monetization of the design didn’t depend on secrecy and hiding the design details from the Chinese manufacturers, then we could all collaborate on both the firmware and hardware designs. At the moment, it seems that the clones have caught up to the current hardware, so hiding the hardware design isn’t providing the protection that it did before. Perhaps the time is right to publish the hardware design, so that the community can help upgrade and maintain it.?

I'd certainly be interested in helping with this.

Dave