开云体育

Hi Herb and others

As soon my SAA-2 arrives (I ordered it on the very first day it was offered by Tindie, and it has left sender country on the way to me) I will issue relevant data for the SDR-Kits of female Rosenberger parts. I have measurements to 8GHz for these part derived from a 4 port brand new R&S VNA. These data are stable for short open and thru adaptor and for the load there is minor differences for the shunt C. The R values for the load are measured individually by SDR- Kit with a 4 wire measuring test equipment against a 0.01% 50 ohm resistor. I will also issue a general document how to fine tune this shunt C by a sweep of a rigid cable based on a reference s1p Touchstone file generated by SimSmith and same open rigid line used to test a sweep round the Smitchart, to see if the average shunt C in the files provided already is OK.

I might also provide data for a male kit, time will show

I expect this to be successful ?

Kind regards

Kurt



-----Oprindelig meddelelse-----
Fra: [email protected] <[email protected]> P? vegne af hwalker
Sendt: 22. marts 2020 17:49
Til: [email protected]
Emne: Re: [nanovna-users] V2 Design #NanoVNA-V2

Don't forget, NanoVNA-Saver also runs natively on Mac OSX 10.12 and (presumably) all later versions. It runs great for me on 10.14 (but didn't work on 10.10 because PyQt5 wasn't compatible prior to 10.12).

-Larry/NE1S

On Sun, Mar 22, 2020 at 09:28 AM, n2msqrp wrote:

Is there a developer approved site where we can purchase the NanoVNA-V2?
====================================

Mike,
I far as I know the HCXQS group in collaboration with OwOComm funded the development of the NanoVNA-V2. The HCXQS group is selling the NanoVNA-V2 at . Members of this group have reported that purchases from Tindie are filled fairly fast but are delayed in transit at the Shanghai postal point, most likely due to shipping delays caused by impact of the Coronavirus.

No matter where you order I wouldn't count on delivery until late April or early May.

- Herb

Herb --- yes agree --- of course cal kit parts are the frame of reference for measurements (parts from an old HP 85033C cal kit here may suffice for starters) - hopefully the device gets here this year! -- Dave

On Sun, Mar 22, 2020 at 07:42 AM, David Feldman wrote:

... Battery (size per the hcxqsgroup page) and pigtail cable (type per the hcxqsgroup page) were ordered separately from domestic suppliers ..
==============================================
Dave,
More important than battery and the cables are the OSL standards. A VNA without accurate standards is like a computer without software -- pretty to look at but limited in use. Since you purchased the S-A-A-2, I assume you intend on using it to 3 GHz. In that case, you should look into the purchase of a quality OSL kit rated to 3 GHz or better. Coaxial adapters rated to 3 GHz are more expensive than those used for the NanoVNA. If you already have a NanoVNA you can use its standards and adapters, but don't expect great performance much past 1.5 GHz.

I haven't found a user review of the S-A-A-2 yet, so I can't say if it is delivered fully calibrated (50k - 3 GHz, 201 pts). If it is delivered not calibrated, or calibrated at less than its full range, then that makes the availability of an OSL kit even more important.

Looking forward to you receiving your V2 and providing a review to the group.

- Herb

Herb,

Is there a developer approved site where we can purchase the NanoVNA-V2?

Mike N2MS

FYI I had ordered nanovna-v2 from Tindie 6 March 2020 for US delivery.

It appears the parcel was shipped via China Post. The tracking number provided yielded (via t.track17.net) most recent status of "your package has been handed over to the carrier", with last update 13 March 2020 (tracking history began on 8 March 2020 so hcxqsgroup dispatched the order quickly.)

I inquired of Tindie yesterday 21 March 2020 and their reply (this morning 22 March 2020) said "Hi, The typical delivery time is 30 days." and referred me back to t.track17.net URL for the parcel.

Battery (size per the hcxqsgroup page) and pigtail cable (type per the hcxqsgroup page) were ordered separately from domestic suppliers and have already arrived.

Dave

For those members who have an affinity to eBay, the V2 (S-A-A-2) has begin started showing up for sale, .

Good news: Another option for purchasing.
Bad news: Almost 3x higher in cost ($140 usd) than the same product on Tindie.

Without USB cable, SMA cables, OSL standards, and without a battery. Probably an "I don't think so" at that price.

- Herb

On Sun, Mar 22, 2020 at 05:06 AM, Jos Stevens wrote:

Does the? edy555 release work on -H4 ? I guess not.
=================================================
Jos,
Always remember that the -F and -H4 use different processors than the NanoVNA (-H), therefore; require different firmware. All firmware from edy555 is currently only for the NanoVNA (-H).

hugen is the only developer currently releasing firmware for the -H4, so unless the firmware comes from him and is designated as for the -H4, be wary.

- Herb

i Herb

Does the? edy555 release work on -H4 ? I guess not.

Jos

Op 21-3-2020 om 21:27 schreef hwalker:

On Sat, Mar 21, 2020 at 09:02 PM, Nbridgema wrote:

So I then tried using ch.bin, and that worked. The Terminal command was

<your_machine_name>:build <user_name>$ dfu-util -d 0483:* -a 0 -s
0x08000000:leave -D ch.bin
(where "build" is the folder

It gave a warning:
dfu-util: Invalid DFU suffix signature
dfu-util: A valid DFU suffix will be required in a future dfu-util release!!!
Opening DFU capable USB device...

You will then need to use the ST-LINK utility with the following memory parameters:
- Address: 0x08000000
- Size: 0x20000
- Data width: 8 bits
It seems that on MAC OSX, ST-Link is available with the terminal program, so the .bin file can be uploaded - no need to convert .dfu.
This is confirmed by the stlink install description on MAC OSX.
DfuSe Demo use .dfu is the Device Firmware Upgrade option, while STMicroelectronics using the Utility from the .bin file is an upgrade option. Both are products of STM.

73, Gyula HA3HZ

I got a new car with USB-C instead of normal USB sockets
I tried to connect Android Auto with my XIAOMI MI A2
this one doesnt work

but it works for USB stick with audio files

this one is working fine


the same behavior with NaNo VNA :-), Ugreen cable does it
73 Alex

Hello Rune / 5Q5R

From all the firmware versions for the nanovna-H (original) what firmware do you recomend to take the most from the nanovna-saver?

Cheers,

Luis CT2FZI

On Sat, Mar 21, 2020 at 01:02 PM, Nbridgema wrote:

All I can say is that worked for me, without a dfu file.
==============================================
Quite right. A dfu file is only needed if you are using the STMicrolelectronic's DfuSeDemo utility to upgrade your NanoVNA (-H or -H4) on the Windows platform.

- Herb

My apologies, re-posting this b/c I didn't know it would show in a different topic...

The latest firmware is at

I was hoping to find a .dfu file for Edy555's latest version, because I previously updated NanoVNA-H fw on my Mac that way. (So Terminal already had Homebrew and dfu-util installed from the earlier work.)

I'm illiterate in 'code-speak' [as those who helped me can testify] and don't remember much at all about running a CLI terminal — hey, it's more than 40 years ago. So I was surprised to find that the fw can be updated using the ch.bin file contained in the "nanovna-firmware-0.7.1.zip" download. Unzip that to reveal the build folder.

Because of my complex file system organization but CLI ineptitude, to minimize jockeying around I copied the "build" folder to the top-level directory on the machine.

I then managed to change the working directory, and verified I was in the "Build" folder with pwd, then ls - l to make sure the correct files were there: ch.bin, ch.elf and ch.hex.

I first tried to update the using the ch.hex file. Something happened, but after several seconds the result was
dfu-util: Last page at 0x08037c12 is not writeable

So I then tried using ch.bin, and that worked. The Terminal command was

<your_machine_name>:build <user_name>$ dfu-util -d 0483:* -a 0 -s 0x08000000:leave -D ch.bin
(where "build" is the folder

It gave a warning:
dfu-util: Invalid DFU suffix signature
dfu-util: A valid DFU suffix will be required in a future dfu-util release!!!
Opening DFU capable USB device...

Go to 'ask-a-geek' if you want to know what that means. Nonetheless, it succeeded:
Download done.
File downloaded successfully
Transitioning to dfuMANIFEST state
<machine_name>: build <user_name>$ /usr/bin/ruby -e "$(curl -fsSL )

The VNA ** instantly ** reverted to an operational display with traces. There is no splash screen with this firmware.

It happened so quickly I had to be sure it worked using the display tab Version:
Version: 0.7.1
Build Time: Mar 21 2020 - 00:42:52
followed by geek details I can't explain.

All I can say is that worked for me, without a dfu file.
Good luck!!

I_B_Nbridgema

--
I_B_Nbridgema

I was hoping to find a .dfu file for Edy555's latest version, because I previously updated NanoVNA-H fw on my Mac that way. (So Terminal already had Homebrew and dfu-util installed from the earlier work.)

I'm illiterate in 'code-speak' [as those who helped me can testify] and don't remember much at all about running a CLI terminal — hey, it's more than 40 years ago. So I was surprised to find that the fw can be updated using the ch.bin file contained in the "nanovna-firmware-0.7.1.zip" download. Unzip that to reveal the build folder.

Because of my complex file system organization but CLI ineptitude, to minimize jockeying around I copied the "build" folder to the top-level directory on the machine.

I then managed to change the working directory, and verified I was in the "Build" folder with pwd, then ls - l to make sure the correct files were there: ch.bin, ch.elf and ch.hex.

I first tried to update the using the ch.hex file. Something happened, but after several seconds the result was
dfu-util: Last page at 0x08037c12 is not writeable

So I then tried using ch.bin, and that worked. The Terminal command was

<your_machine_name>:build <user_name>$ dfu-util -d 0483:* -a 0 -s 0x08000000:leave -D ch.bin
(where "build" is the folder

It gave a warning:
dfu-util: Invalid DFU suffix signature
dfu-util: A valid DFU suffix will be required in a future dfu-util release!!!
Opening DFU capable USB device...

Go to 'ask-a-geek' if you want to know what that means. Nonetheless, it succeeded:
Download done.
File downloaded successfully
Transitioning to dfuMANIFEST state
<machine_name>: build <user_name>$ /usr/bin/ruby -e "$(curl -fsSL )

The VNA ** instantly ** reverted to an operational display with traces. There is no splash screen with this firmware.

It happened so quickly I had to be sure it worked using the display tab Version:
Version: 0.7.1
Build Time: Mar 21 2020 - 00:42:52
followed by geek details I can't explain.

All I can say is that worked for me, without a dfu file.
Good luck!!

I_B_Nbridgema

On Sat, 21 Mar 2020 10:39:19 -0700, you wrote:

On Sat, Mar 21, 2020 at 08:27 AM, Helmut Wabnig wrote:

No way to get the software without goin' through a tedious registration procedure.
===========================================
Helmut,
From the initial release of the NanoVNA, hugen has provided the STM software at his google drive support site. No registration required.

A link to that site is provided at this groups Wiki firmware topic, " /g/nanovna-users/wiki/home#Source "

A direct link is .

- Herb

Thank you very much!

wabi

On Sat, Mar 21, 2020 at 08:27 AM, Helmut Wabnig wrote:

No way to get the software without goin' through a tedious registration procedure.
===========================================
Helmut,
From the initial release of the NanoVNA, hugen has provided the STM software at his google drive support site. No registration required.

A link to that site is provided at this groups Wiki firmware topic, " /g/nanovna-users/wiki/home#Source "

A direct link is .

- Herb

Thanks for all the tips. I unscrewed the screws a half turn and it works great now.

Hi Doug,
Same problem with OTG interface. I continue....