开云体育

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

If you float either or both N connectors from the shielded enclosure, you largely
defeat the purpose of the enclosure.

My advice? Bond both connectors firmly to the enclosure, and run coax cable
within the enclosure from each N connectors to its existing SMA connector on
the nano. Then test to see how it works out. If unhappy, try putting ferrite "beads"
on both coax lines.

One problem area I see relates to the USB cable. That, too, should be treated
in a similar manner, and a shielded USB cable should be used between the
enclosure and the external computer. And don't spare the ferrite beads on that,
either, both inside and outside the enclosure. The trick might lie in finding a
USB bulkhead thru connector that can be bonded to the enclosure and which
effectively bonds the shield of at least the external cable (but preferably both)
to the enclosure wall.

Dana K8YUM

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:

If you want performance into the microwave range I'd wait for the nanoVNA V2:

<>

Mike N2MS

Dave,
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. It is the primary reason that whether you purchase hugen's clone or another Chinese seller's clone you get pretty much the same performance and is a testament to edy555's original design concept.

Edy555 produced an unassembled kit for the NanoVNA in 2016 that, except for some hard core hobbyists, never took off. Besides being in kit form it could only be operated when attached to a USB power source. As Larry noted, hugen added a charging circuit for battery operation, extended the measurement range to 900 MHz using harmonics and designed the current PCB. He started marketing the assembled unit earlier this year and as they say the rest is history. If the NanoVNA wasn't a hobbyist device it would be in contention for a design of the year award based on its performance to cost point.

Edy555 probably regrets not marketing an assembled version of his open source design. He is not crying over spilled milk and has indicated he has a version 2 design in the works. He maintains a web presence at where you can learn about the historical background of the original NanoVNA design. He has other commercial ventures going on and the best way to show support is to purchase one of his sdr kits if you have an interest in that area.

The best way to contribute to hugen is to purchase his current Nano-VNA-H product. It is basically the current design but includes some enhancements such as a case, resistors on the pcb for proper USB-C to USB-C connection, a diode on the pcb for battery voltage indication and the updated firmware for up to 1500 MHz operation. The cost is in the same ball park as the current NanoVNA's and even includes shielding on the ports. It currently differentiates units produced by hugen from all the other clone manufacturers, at least until they start copying his design or just drop the price of the current NanoVNA in half and compete on that basis.

Regards,

- Herb

Jos,
Do have you another computer you can run the DFUseDemo app from? The reason I ask is because I ran into a similar situation on a PC where Windows device manager showed "STM32 in boot mode and I could connect to the NanoVNA using nanovna-saver, but DFUseDemo couldn't detect the NanoVNA in the DFU mode. I eventually tried running DFUseDemo on another computer and it recognized the NanoVNA in the DFU mode without any sweat.

I later tried to determine why my other computer (WIN10, i7, 12GB Ram) failed to run DFUseDemo and a web search said it could be a corrupted or out of date run-time problem (I believe it was one of the Visual C + runtimes). I found a file on the web named "aio-runtimes_v2.4.8.exe" which uninstalled the runtimes and reinstalled new ones. After re-booting, DFUseDemo ran fine and connected to the NanoVNA when it was in the DFU mode.

Good luck,

-Herb

also if the link is connected.. power OFF the vna then back on again to get the stm into boot mode.
With dfusedemo running, this should make the handshake with the bootloader on stm32.
you should hear a couple of beeps and up it comes.

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

Thanks, QRP RX!

and just to add, v0.2.3 firmware is on the edge of not needing the link to induce thew bootloader of stm32.
Can't remember if needed or not on this version? if not then link has to be made.
what is happening on screen at the moment..is it white??
It sounds like the dfudemo is playing ball, but there is no handshake to the bootloader from the vna.

ok, i use win7 here.
just turning the nano nva with c usb lead connected i see thus in device manager
this shows device as teensy.
on entering dfu mode under 0.4.3
i get stm message in usb devices!
i now if i load Dfuse demo i get the device in the top window filled.
i did once convert a hex file to dfu, and for some reason it failed...
i just ended up with white display, so turned off nanovna , did the link and re inserted firmware.
everything was then back to normal.
don't know if any of this will help...

Hi Dean,

Yes I did, it makes no difference. Strange thing is that Windows device manager shows "STM32 in boot mode". So why does DFUseDemo not see it ???

Jos

Op 10-11-2019 om 22:07 schreef Dean Smith:

You can convert ,hex and .bin to ,dfu by using "DFU file manager".


Op 10-11-2019 om 21:38 schreef Oristo:

Hello Hans,

If you have downloaded and installed the DFU package from STI, there is? installed " DFU file manager", you can't see it in the folder you installed " DFUseDemo"? in, but when you type " DFU" in the magnifier glass of windows 10 you will see it .

Jos (PA3CCE)

Op 10-11-2019 om 21:21 schreef Hans , PA3HGT via Groups.Io:

Just a thought...
Have you tried doing the link on the nano vna to pop it into boot mode???

Thanks Oristo ! I succeeded now with your info. Dean thx too !

Hans