¿ªÔÆÌåÓý

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

Re: Would like to buy NanoVNA #nanovna-matlab

 

I believe this is the official Hugen one

Lucio, I0LYL


Would like to buy NanoVNA #nanovna-matlab

 

First of all apologize if I'm repeating the same question. But I browsed many messages to see howto buy, but lost in topics.
I would like to buy Hugen version but could not able to manage buying from Tabao site. Then I found a product in Aliexpress claiming @Hugen version in description. But I need to make sure it is real Hugen version



If Hugen can see my message here I can pay via Paypal or Payoneer directly and send my postal address or can get it from Aliexpress if he has official sales in there.
--
Regards,

Erhan, TA1LSX, 73


Re: NanoVNA vs. NanaVNA-Saver #calibration

 

On 08/11/2019 15:18, Nick wrote:
Thanks Rune. I did not understand the relationship between device
cals and nvna-s cals.

Please allow me to check my understanding.

Let's say I want to measure a ferrite choke from 1 to 50MHz. I set
up the cables and do a device cal over that frequency range using an appropriate cal kit. I save that cal to say C0.

With C0 selected on the device, I repeat the cal on nvna-s using the
same frequency range, same cables, same cal kit and save it to cal_0.cal.

I can then measure my choke over the same frequency range using
nvna-s with as many data points as I like using multiple segments.
Yes

Let's say I then want to measure a UHF filter over the range 100MHz
to 900MHz. Obviously I cannot use C0 and cal_0.cal. So I set up with different cables and a different cal kit. I do a device cal over that frequency range and save it to C1.
No. According to my understanding from Rune. On connection nvna-s reads cal data from Memory 0 only, so unless your calibration originally covered the whole of the frequency range and was saved to C0 then as far as I understand that would not work.

With C1 selected on the device, I repeat the cal on nvna-s using the
same frequency range, same cables, same cal kit and save it to cal_1.cal..

I can then measure my filter over the same frequency range using
nvna-s with as many data points as I like using multiple segments and save the results to s*p files.

What if I then want to measure the filter over a restricted frequency
range, say 400 to 500MHz?

Or a VHF filter with the same the cables and connectors from 100MHz
to 200MHz?

Do I need a new pair of cals in either of these cases? (I would say
not.)

I would say that unless you make a full span course cal and use that from C0 then you would need to save manual cals for the other ranges and store them in C1..C3 and copy them to C0 before disconnecting from the nvna and reconnecting to pick up each new cal from C0.

Maybe Rune can clarify whether or not I have misunderstood his comments in


Barry
G4MKT


Re: NanoVNA-Saver 0.1.5

 

On 11/11/19 10:51 AM, David J Taylor via Groups.Io wrote:

Unfortunately, quartz filters have a ripple.


???? Especially if they are not properly terminated.


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

 

Do you remember those huge Fresnel lenses that used to be sold so you could 'enlarge' your 14" TV to 30" or more??
?Maybe someone should design a 3d printed housing for the NanoVNA with a Fresnel lens over display ?



On Mon, 11 Nov 2019 at 7:06 PM, hwalker<herbwalker2476@...> wrote: On Mon, Nov 11, 2019 at 03:47 PM, Larry Rothman wrote:


Herb,
The slightly larger display that Herman installed is identical to the 2.8" it
just has bigger pixels.
The resolution and driver IC are the same as in the 2.8" LCD. Hence the direct
swap.?

Larry,
Thanks for the clarification.? Too bad there isn't a similar 4 or 5 in display, although at that size I would think you would want more pixels instead of larger ones for better resolution.

- Herb


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

 

On Mon, Nov 11, 2019 at 03:47 PM, Larry Rothman wrote:


Herb,
The slightly larger display that Herman installed is identical to the 2.8" it
just has bigger pixels.
The resolution and driver IC are the same as in the 2.8" LCD. Hence the direct
swap.?

Larry,
Thanks for the clarification. Too bad there isn't a similar 4 or 5 in display, although at that size I would think you would want more pixels instead of larger ones for better resolution.

- Herb


Re: Any plans to publish the NanoVNA board files

 

On Mon, Nov 11, 2019 at 08:43 PM, <dhu1342@...> wrote:


Trying one more time to add the attachments.
I made both versions. After communicating with edy555, I changed the nanovna label to nanovna-h label. You can check the nanovna-h label under the battery.


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

 

Herb,
The slightly larger display that Herman installed is identical to the 2.8" it just has bigger pixels.
The resolution and driver IC are the same as in the 2.8" LCD. Hence the direct swap.?



On Mon, 11 Nov 2019 at 5:55 PM, hwalker<herbwalker2476@...> wrote: Herman,
The 2.8 in display uses a 320 * 240 * 2 bytes to transfer data and I assume the 3.2 in display requires more.? Therefore I am? I right in also assuming that program features that depend on display size, such as screen capture, do not work correctly with the 3.2 in display?

Not a big issue since you can always use your smartphone camera to capture a screen image, but it is a caveat when stating that the 3.2 works with the same software,

- Herb


Re: NanoVNA does not want to start -solved

 

Yes, but now you created another problem for the rest of us: you didn't post the link where you purchased the new chips from ?.??
Thanks for playing around with this until you solved it.??
RegardsLarry



On Mon, 11 Nov 2019 at 5:42 PM, Herman De Dauw<on1bes@...> wrote: After almost half a year of using my NanoVNA that did not want to start with the on / off, an old problem has been solved. After replacing the IP5303 earlier, my NanoVNA still did not start (the IP5303 did not see the increased power when switching on). Now I have received a number of IP5305, and have placed one of them in the NanoVNA. After this procedure, the NanoVNA wanted to start up normally for the first time, and all functions of the IP5305 function normally. The device is now fully portable with battery. Problem solved.
on1bes Herman


Re: My NanoVNA is not recognised by DFUse wh

 

This UmbrelaSmart app does recognise and display the NanoVNA usb info in DFU mode and it does perform a full erase.
It might be the version number coded into the DFU file. I'm going to try playing with that.?
BTW, there is a java disassem that I've been playing with from the Play store.It's called Show Java.?
Show Java - A Java Decompiler - Apps on Google Play
|
|
|
| | |

|

|
|
| |
Show Java - A Java Decompiler - Apps on Google Play

A decompiler to extract the source code of an APK (android app), jar & dex file. Features ? Select either CFR 0.138, JaDX 0.8.0 or FernFlower (analytical decompiler) to use as the decompiler. ? Runs directly on your android device ? Select apk/jar/
| |

|

|






On Mon, 11 Nov 2019 at 4:55 PM, Oristo<ormpoa@...> wrote: >> I found this GitHub project for DFU installation by Android app
?
I've been trying to get this working - keeps coming back and saying the ID
doesn't match even though it does.
Just as well; source includes comments like:
"this is limited to stm32f405RG and will fail for other future chips."

Since the last commit to this was several years ago
Well, it is newer than Android apps that I worked on, pre-Gradle and pre-IntelliJ IDEA.
As bad as were ant and eclipse, at least Android's wretched documentation was relevant.
Now, build docs badly prescribe doing things that are doomed.

Thanks at least in part to Gradle, it appears no longer possible to publish
a GitHub Android project that can be simply cloned and built

- there is most likely some bugs introduced by newer version of Android.
I expect bugs in this Java.? If I eventually sort build issues,
then it can be tested on nearly the oldest Android device with USB OTG.


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

 

Herman,
The 2.8 in display uses a 320 * 240 * 2 bytes to transfer data and I assume the 3.2 in display requires more. Therefore I am I right in also assuming that program features that depend on display size, such as screen capture, do not work correctly with the 3.2 in display?

Not a big issue since you can always use your smartphone camera to capture a screen image, but it is a caveat when stating that the 3.2 works with the same software,

- Herb


Re: NanoVNA does not want to start -solved

 

After almost half a year of using my NanoVNA that did not want to start with the on / off, an old problem has been solved. After replacing the IP5303 earlier, my NanoVNA still did not start (the IP5303 did not see the increased power when switching on). Now I have received a number of IP5305, and have placed one of them in the NanoVNA. After this procedure, the NanoVNA wanted to start up normally for the first time, and all functions of the IP5305 function normally. The device is now fully portable with battery. Problem solved.
on1bes Herman


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

 

I recently replaced my display with a 3.2 version that works with the same software (see the Wiki Files). Replacement with an even larger display is not possible without rewriting the firmware. And currently almost all memory space is used, I see that does not happen immediately. So I'm also waiting for the V2 version, and hope for a larger display.
on1bes Herman


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

 

I found this GitHub project for DFU installation by Android app
I've been trying to get this working - keeps coming back and saying the ID
doesn't match even though it does.
Just as well; source includes comments like:
"this is limited to stm32f405RG and will fail for other future chips."

Since the last commit to this was several years ago
Well, it is newer than Android apps that I worked on, pre-Gradle and pre-IntelliJ IDEA.
As bad as were ant and eclipse, at least Android's wretched documentation was relevant.
Now, build docs badly prescribe doing things that are doomed.

Thanks at least in part to Gradle, it appears no longer possible to publish
a GitHub Android project that can be simply cloned and built

- there is most likely some bugs introduced by newer version of Android.
I expect bugs in this Java. If I eventually sort build issues,
then it can be tested on nearly the oldest Android device with USB OTG.


Re: Duplexfilter tuning question

 

Yes, I checked it when I came home, I use different modes.
But, the attenuators are on the way, so I can test more deep then now is possible.

What a nice software, that's what I mean, with this software I can tune more accurate.

Nice things to study and learn!
Thanks for the link QRP RX!


Re: coax fatigue #test-jig

 

All network analyzers that I have worked on (repaired, calibrated and use nearly every work day) since 1977 (8409, 8505, 8753, 8510.......) have the test ports connected to and thru the same front panel (built in or on the S-parameter test set). I see absolutely no reason to isolate them on the nano. I have not used the isolation part of the cal yet but isn't that the reason for doing isolation?
I thought about mounting my unit in an enclosed box as well but I had this old HP radar test set with everything right there and ready to go plus I do every thing at HF and have not seen any leakage problems there.
K6JCA's set up looks nice but I again I see no reason to separate the connectors. It might even lead to cross talk when doing S21 creating a ground path loop.
Last night, after finally getting a second HF antenna lashed up before the winter snows, I checked the isolation between the two antennas using S21 for the first time (except for a quick functional check when I rec'd the nano in late August). On 40 meters there is only 20 dB of isolation and on 20 meters and 160 meters there is about 29 dB of isolation. For each band I retuned the transmatch on the one antenna that needs a transmatch. When I de-tuned the transmatch even by a small change, the coupling dramatically decreased showing the impedance match was critical for max radiation from one antenna into the other.


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

 

reports "you have the latest version"
Zadig software simply ignores such misleading messages
to install the >>correct<< driver, namely:
right-click on DfuSeDemo icon, select "Open file location"
* start in the Bin folder that has DfuSeDemo.exe
* nanoVNA wants driver in that Driver folder

You can right-click on the device, select "Update Driver Software"
* "Browse my computer for driver software"
* browse to the location above for your Windows version


Re: NanoVNA-Saver 0.1.5

 

Hello Rune,

Unfortunately, quartz filters have a ripple. In the Attachment the plot of an IF quartz filter.
One possibility might be to select rising and falling edges.
Otherwise, I currently have no solution.

Viele Gr????e

Hans-Peter Prast, DL2KHP
=========================================

Hans-Peter, yes, I appreciate the ripple issue.

Perhaps one approach might be to scan for Fmax, Smax and then approach upwards from a low frequency until Smax - 3 dB is reached, and then approach downwards from a high frequency until Smax - 3 dB is reached. I've not programmed that, though, just a suggestion.

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


Andy
 

Also I do not use the "jog" switch.
I drag and drop the markers / and use all menu's by the touch screen.
I also use a simple and very cheap PDA stylus.
It makes life very easy and simple.

73 de Andy


Re: NanoVNA-Saver 0.1.5

 

Hello Rune,

Unfortunately, quartz filters have a ripple. In the Attachment the plot of an IF quartz filter.
One possibility might be to select rising and falling edges.
Otherwise, I currently have no solution.

Viele Gr¨¹?e

Hans-Peter Prast, DL2KHP