¿ªÔÆÌåÓý

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

Re: Dreaming a new option for nanoVNA

 

On 8/6/20 12:30 AM, OneOfEleven wrote:
On Wed, Aug 5, 2020 at 04:27 PM, Piero Tognolatti wrote:

is anyone able to implement a new feature in the nanoVNA menu?? I need
to locate the nanoVNA inside a mokup of a cubesat to take S11
measurement for a while (10 minutes, for example). I cannot use have any
cable running out from the satellite (to not disturb measurement), so I
would like to set the nanoVNA in order to take and store measurements,
for example a measurement every minute.

Is it a dream? Is there anyone able to create this feature?
That could be done Piero if you have an SD card socket fitted on your NanoVNA. Does your VNA have the SD card socket fitted ?
Could add a firmware option to record the measurement onto an SD card every so often easily enough, though the problem we have with the small NanoVNA now is that we've run out of flash area to add more options/features, but for your needs a firmware could be compiled with other features disabled in order to make room.
Another option would be to enable one of the hardware serial ports in the firmware on the VNA CPU, and then attach say a cheap (HC5 as an example) serial port bluetooth module to the VNA board.
I think separating the "instrument functions" (on the nanoVNA) and the "data collection funtions" (on the Pi) is actually how you want to do it.

Focus on instrument capability, not data logging. There's myriad different data logging applications, and most of them will not want "snapshot ever N seconds" - often, there will be other things that need to happen (external configuration of the unit under test).


Re: Firmware and PC application stability #stability #nanovna-h4 #nanovna-h #specifications

 

@DisLord and @OneOfEleven

It is unfortunately significant nowadays that many users are using free software but constantly ask for new features and also complain about this and that.
You can't please everyone!

But I want to say as many of us: please stay and go ahead! You did excellent work in the last month/weeks and we ALL do have advantages from your work.
The community and also the little VNA's need people like you!
Don't let such users put you under pressure and loose the fun!

We all will be very sad if you both will leave... Don't go!

Chris


Re: Firmware and PC application stability #stability #nanovna-h4 #nanovna-h #specifications

 

Those of you that have cloned the repository, please provide the links to
your copies.

On Thu, 6 Aug 2020 at 12:42, DiSlord <dislordlive@...> wrote:

I delete my NanoVNA git, and cleanup all provided binaries from this forum

Continue fix for self, GPLv3 allow it




Re: NanoVNA firmware user interface mod #mods

 

On Thu, Aug 6, 2020 at 09:40 AM, Jos Stevens wrote:


Thank you Igor, I got an 404 Error on Github !

Op 6-8-2020 om 14:35 schreef Igor Jobim:
Unfortunately OneOfEleven disabled his collaborations on Github.
This is the last file FW and SW.
73 !!
============================================================
Yes. Because unfortunately it was disabled.
We hope it will be for a short time. They are important jobs.


Re: NanoVNA firmware user interface mod #mods

 

Thank you Igor, I got an 404 Error on Github !

Op 6-8-2020 om 14:35 schreef Igor Jobim:

Unfortunately OneOfEleven disabled his collaborations on Github.
This is the last file FW and SW.
73 !!


Re: NanoVNA firmware user interface mod #mods

 

Archives are today's collaborations. The latest update.


Re: Dreaming a new option for nanoVNA

 

David,
The writing to the SD card is every few seconds which will do nothing to prematurely wear out the device. I use an SD card in my dashcam that is written to regularly and it's been good for 3 years now
Besides, you don't put a 128gb part in the Nano, you use a small capacity card that costs $2
... Larry



On Thu, 6 Aug 2020 at 6:46 AM, David J Taylor via groups.io<david-taylor@...> wrote: I've added the ability to auto save to SD card every 'n' seconds for those
that have SD cards on their nano's.

The option is in the "SD CARD" menu. A setting of '0' seconds disables auto
save.

You can find the NanoVNA-H firmware (and windows software to upload the
firmware) in the "Release" folder here ..



I can't do H4 firmware because I don't have a H4 to test with.
===========================

Good way to take the life out of the SD card!? But I hope you only save when
a change is detected?

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


Re: NanoVNA firmware user interface mod #mods

 

Unfortunately OneOfEleven disabled his collaborations on Github.
This is the last file FW and SW.
73 !!


Re: NanoVNA firmware user interface mod #mods

 

Hi Dave,

Thank you ver, very much? Dave , I went there and foud nanovna.exe, but I cannot download the binairy, I'm directed to the soutce files, I'm just learning how to do in Github. I will see hhow to mange..

Jos

Op 6-8-2020 om 14:07 schreef Dave_G0WBX via groups.io:

It's located here Jos ..



------------------------------------------------------------------------

That results in a 404 error, and a nice GitHub image looking confused...?? (At 12:06 UTC from the UK, August the 6th.)

Dave G0WBX.


Re: Firmware and PC application stability #stability #nanovna-h4 #nanovna-h #specifications

 

I fully support this content, please DiSlord and OneOffEleven stay for the good willing community, please please .


Op 6-8-2020 om 13:59 schreef CT2FZI:p

@OneOfEleven and @DisLord,

You know the dynamics of this wonderful users group "nanovna users".

After thousands of posts/replies/interactions between users we already know that this group is very technical, very deep sometimes and very dynamic.

Some (new) users caught the train while it was in full speed, making the nanovna even greater than anyone suspected.

So, don't mind these users. We all know what effort and time you spent, your patience repeating many times the same things.

One of the developer's nightmares happened in this topic, but you already experienced users demanding for new features, or timelines HIHI

Please understand that you have a big community supporting you in many ways, its not because of one particular situation you should take radical actions.

I personally thank DisLord for his invaluable dedication to the nanovna, and more recently OneOfEleven that I also praise the good sense of humor :)

So, read my words as both encoragement and a request to continue your line of work: we thank you and we will back you up.


Re: Firmware and PC application stability #stability #nanovna-h4 #nanovna-h #specifications

 

Igor,
DiSlord and others post interm releases on the forums in order to have members conduct tests and provide feedback.?
This is a hobby for him, not a business.

DiSlord updates his GitHub repo every few weeks which is fine for everyone on the forum except maybe 2-3 members out of 6880 members!

You are free to fork DiSlord's software and develop and test your own improvements and release them on the forum...so?
Have patience.?
... Larry


On Thu, 6 Aug 2020 at 5:57 AM, igor-m<mikki@...> wrote: On Wed, Aug? 5, 2020 at 05:58 PM, DiSlord wrote:


On Wed, Aug? 5, 2020 at 07:50 AM, igor-m wrote:


@Dislord: do you still consider the project open-source?
Not understand. All my code open on git you can use it.
Last stable code (96k mode and SD card support, and UI) also on github and
open.
When you distribute the 1.0.XX binaries (like here on this forum or on cqham.ru or vrtp.ru) you shall provide the source code on your github too.
It does NOT matter whether those binaries are called "final" or "beta".
For example - with "1.0.14" beta binary the community has to be able to build the "1.0.14 beta" out of the source code on your github.

Or i must add on my github every my test option?
Yes. Otherwise one can distribute "test" or "beta" binaries for next 10years without providing source code. And the "open-source" project bites the dust.

Or ... i should support code? But sorry for this need a lot of time, and this
not my main work.
Nobody can ask you to support the code, this is an open source project.
HTH


Re: New topic for test new nanoVNA features #nanovna-h #nanovna-h4 #beta #test

 

Hi DiSlord
is it normal that the on / off configuration of the traces is not saved?
When I browse the menus I often have freezes with version 1.0.13 and 1.0.14. it is not systematic. This often happens with the "Version" menu
I have never seen this before with version 1.0.11


Re: Firmware and PC application stability #stability #nanovna-h4 #nanovna-h #specifications

 

Very well expressed, and you have my 100% agreement!

I can see NO non-compliance with the GPL in the way that beta testing has been conducted via this forum, and NO need to change behaviour in any way.

PLEASE continue, guys.

Mike - M0MLM

On 06/08/2020 12:59, CT2FZI wrote:
@OneOfEleven and @DisLord,

You know the dynamics of this wonderful users group "nanovna users".

After thousands of posts/replies/interactions between users we already know that this group is very technical, very deep sometimes and very dynamic.

Some (new) users caught the train while it was in full speed, making the nanovna even greater than anyone suspected.

So, don't mind these users. We all know what effort and time you spent, your patience repeating many times the same things.

One of the developer's nightmares happened in this topic, but you already experienced users demanding for new features, or timelines HIHI

Please understand that you have a big community supporting you in many ways, its not because of one particular situation you should take radical actions.

I personally thank DisLord for his invaluable dedication to the nanovna, and more recently OneOfEleven that I also praise the good sense of humor :)

So, read my words as both encoragement and a request to continue your line of work: we thank you and we will back you up.


 

Using the NanoVna-H4 with the Nano Saver I have a question about the way of calibrating.

Using the NanoVna stand alone, then after opening the Calibration menu I see the Open on top of the menu, then the Short and then the Load.
When I use the Calibration Assistant in the Nano Saver or the Calibrate Section then the order is Short, Open and Load.

Is this order essential for a good calibration, or can I use the calibration components in a random order?

Kees


Re: NanoVNA firmware user interface mod #mods

 

It's located here Jos ..



------------------------------------------------------------------------

That results in a 404 error, and a nice GitHub image looking confused...?? (At 12:06 UTC from the UK, August the 6th.)

Dave G0WBX.


--
Created on and sent from a Unix like PC running and using free and open source software:


Re: Firmware and PC application stability #stability #nanovna-h4 #nanovna-h #specifications

 

@OneOfEleven and @DisLord,

You know the dynamics of this wonderful users group "nanovna users".

After thousands of posts/replies/interactions between users we already know that this group is very technical, very deep sometimes and very dynamic.

Some (new) users caught the train while it was in full speed, making the nanovna even greater than anyone suspected.

So, don't mind these users. We all know what effort and time you spent, your patience repeating many times the same things.

One of the developer's nightmares happened in this topic, but you already experienced users demanding for new features, or timelines HIHI

Please understand that you have a big community supporting you in many ways, its not because of one particular situation you should take radical actions.

I personally thank DisLord for his invaluable dedication to the nanovna, and more recently OneOfEleven that I also praise the good sense of humor :)

So, read my words as both encoragement and a request to continue your line of work: we thank you and we will back you up.


Re: Firmware and PC application stability #stability #nanovna-h4 #nanovna-h #specifications

 

Please stay Dislord and OneOfEleven. Get rid of the complainers and abusers.

On 6 Aug 2020, at 8:54 pm, OneOfEleven <cmoss296@...> wrote:

OK, after reading various messages on here I have decided I no longer want to be involved, it's far too messy and unpleasant, all I want and now need in my now later years of life is for it to be nice and trouble free and pleasantly quiet.

I'm more than happy just doing my own code for my own personal needs.

Their are lots of other people who can contribute though, so all is not lost.

xx



Re: Firmware and PC application stability #stability #nanovna-h4 #nanovna-h #specifications

 

Hi,

I'm so sorry to hear this, this is a great loss, someone or too many have been offensive I suppoose :'(.

Jos

Op 6-8-2020 om 13:21 schreef Igor Jobim:

Everyone loses at this point.
DiSlord and OneOfEleven took the nanovna to another level.
Thank you for all your contribution to the growth of the project.
I would like to continue following the work, so if there is a way, tell me where to find it.
73!


Re: NanoVNA firmware user interface mod #mods

 

Please reread my msg...my coax is 1m long. It's the PC SW that is not right.



On Wed, 5 Aug 2020 at 9:37 PM, cldp@...<cldp@...> wrote: On Wed, Aug? 5, 2020 at 08:07 PM, Larry Rothman wrote:


I was playing with the TDR on my H along with using your NanoVNA.exe 0.1.67
and they don't match.
The Nano shows the correct length of my coax at just over a meter but your app
shows close to 4X as much.
Is there an issue or did I mis-configure your app?
See the two images.

Thanks,
Larry
Larry, you should set the nanovna software to a way higher frenquency stop, the picture I see display 494m (which is a low frequency stop), if you set the stop frequency at 900MHz, you should have a maximum of around 4m which is a much more realistic measuring range for the coax lenght I see on the other picture...

You should set CH0 trace to LINEAR and clear all other traces, then go to DISPLAY, MORE, TRANSFORM, turn ON LOW PASS IMPULSE and set TRANSFORM ON. Set start frequency at 50kHz and stop frequency at 900MHz, you should get the right lenght on both VNA and software. The lower the stop frequency is, the longer measure you will get. At 900MHz stop, you should see around 4m which fit the lenght of coax you currently have.


Re: Firmware and PC application stability #stability #nanovna-h4 #nanovna-h #specifications

 

Everyone loses at this point.
DiSlord and OneOfEleven took the nanovna to another level.
Thank you for all your contribution to the growth of the project.
I would like to continue following the work, so if there is a way, tell me where to find it.
73!