¿ªÔÆÌåÓý

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

Re: Dreaming a new option for nanoVNA

 

On 8/6/20 7:43 AM, David J Taylor via groups.io wrote:
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
==================================
It's not just how often the card is written, but the data quantity too. It depends on the card design, but each write can cause a much larger block of the card to be written.? With intelligent buffering as I suggested. with infrequent small writes, and throw-away cards I agree it's not an issue, but it's something which users may eventually discover - if not in this application then elsewhere.
BTW: the cheapest microSD card I spotted an Amazon were ~$24 for a pack of 5 x 2 GB, or $40 for a pack of 10 x 4 GB!
Cheers,
David
And those smaller cards are handy for things like flashing new images to Pis and Beagles.

The cards are wear leveled - SLC NAND flash is something like 30k-100k writes nominal life per "segment". So if you write every second, you go through that in a day, but since there are thousands and thousands of segments it could be "years" before you wear it out.

MLC NAND flash is a bit shorter 3000 cycles/sector. Super high density NAND is 500 cycles/sector

So if you have a wear leveled 16 GByte SD card, after you've written 16*3000 GB (or 48 TByte) to it, it is worn out.



Re: NanoVNA firmware user interface mod #mods

 

Yes. Because unfortunately it was disabled.
We hope it will be for a short time. They are important jobs.

========================================================

On Thu, Aug 6, 2020 at 12:16 PM, Roy J. Tellason, Sr. wrote:


On Thursday 06 August 2020 03:01:42 am OneOfEleven wrote:
On Wed, Aug 5, 2020 at 07:59 PM, Jos Stevens wrote:
@ OneOffEleven? Please where can I find your PC program for NanoVVNA-H4 ?
It's located here Jos ..

That link gets me a 404...

--
Member of the toughest, meanest, deadliest, most unrelenting -- and
ablest -- form of life in this section of space, ?a critter that can
be killed but can't be tamed. ?--Robert A. Heinlein, "The Puppet Masters"
-
Information is more dangerous than cannon to a society ruled by lies. --James
M Dakin


Re: NanoVNA firmware user interface mod #mods

 

On Thursday 06 August 2020 03:01:42 am OneOfEleven wrote:
On Wed, Aug 5, 2020 at 07:59 PM, Jos Stevens wrote:
@ OneOffEleven? Please where can I find your PC program for NanoVVNA-H4 ?
It's located here Jos ..

That link gets me a 404...

--
Member of the toughest, meanest, deadliest, most unrelenting -- and
ablest -- form of life in this section of space, ?a critter that can
be killed but can't be tamed. ?--Robert A. Heinlein, "The Puppet Masters"
-
Information is more dangerous than cannon to a society ruled by lies. --James
M Dakin


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

 

You can set freq 299-310MHz range

And see non stable work.
You can remember this issue before (i made measure in this range) i can solve it by add delays and new band range, but at this moment this solution not help.

Also AIC ADC work on 768k speed, and need find better mode.


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

 

On Thu, Aug 6, 2020 at 07:49 AM, <alain.pinchon46@...> wrote:

Thanks for the reply, and after some tests,it seems you are right with the switch ;o)
==========================
Alain,
Which tests did you perform to isolate the issue to the switch? Might be helpful to some of the other members.

- Herb


Re: NanoVNA-H4 4" LCD Display 50KHz-1.5GHz - is the right one sell on Amazon?

 

Hello Sir.

Thank you very much for your answer.

Best regards.
73 YO2MNE
Horia Morariu.


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

 

Thanks for the reply, and after some tests,it seems you are right with the switch ;o)


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
==================================

It's not just how often the card is written, but the data quantity too. It depends on the card design, but each write can cause a much larger block of the card to be written. With intelligent buffering as I suggested. with infrequent small writes, and throw-away cards I agree it's not an issue, but it's something which users may eventually discover - if not in this application then elsewhere.

BTW: the cheapest microSD card I spotted an Amazon were ~$24 for a pack of 5 x 2 GB, or $40 for a pack of 10 x 4 GB!

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


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

 

Trace on/off stored in calibration settings, so need save it in old, or new calibrstion slot.

About freeze, i think it come from fast band switch (in most cases on switch 300MHz).


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

 

On Thu, Aug 6, 2020 at 06:45 AM, Jim Lux wrote:

If it goes on for 6 months with only binary, and there's significant changes in functionality, with no source release - then start asking about whether the author is living up to the spirit and intent of GPL.
==========================================
Seems the developer should have wider latitude as to how and when he releases his source. DiSlord and OneOfEleven would sometimes release multiple beta binaries in a single day. All were experimental and not ready for distribution.

If the user thinks GPL is not being followed they always have the option of not participating in the in the developer's project. Since they are paying nothing, they shouldn't think they can demand anything.

- Herb


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

 

Agree with Jim.100%

We should not mix community assistance for a developer's Alpha testing using binaries with the GPL requirements.

It is easily solved for the purists with DiSlord doing his development and release Alpha level binaries for those of us that want to test with him.
Once he is certain of stability or confirmed the goal of the alpha release, he can move it to a stable, stepped version Beta version for true beta testing by the community and publish that source code on Github.

Regards
RandMental

-----Original Message-----
From: [email protected] <[email protected]> On Behalf Of Jim Lux
Sent: 06 August 2020 15h59
To: [email protected]
Subject: Re: [nanovna-users] Firmware and PC application stability #stability #nanovna-h4 #NanoVNA-H #specifications

On 8/6/20 2:57 AM, igor-m 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.
I'm not sure I agree, Igor-M - collaborative development often involves beta testers, and this forum provides a convenient mechanism to make untested betas available.

Given that the source does get regularly updated, I don't think this violates the spirit of open source - otherwise a *group* of developers would have to keep their internal development hidden. Why not use public fora as a means of communication.


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.
I think that's a strawman - Why don't you wait 6 months, and then complain about how there's still a stream of bug-free binaries, with no source.

Open source is wonderful, but there are plenty of open source projects that are 80% complete (the vast majority of projects developed by grad students, for instance - got the degree, no need to do bug updates any more, and anyway I have a real job that actually pays me now)

Let's focus our "why isn't source available" on pernicious evils - manufacturers who build custom versions for their products and have NEVER released source.




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.
yes it's open source - but I don't see a huge number of people stepping up to make changes. From what I see, there's a few folks grinding on the software, and dozens weighing in with testing, feature requests, etc.

I'm not sure what axe you're grinding here, Igor-M?


I think you're setting an artificial "intellectual purity" bar to participate in software development.

I think OneofEleven and DiSlord are doing good work, and should keep it up, in what ever release strategy they care to do. They say that it's a hobby for them, and let's let that be for now. If all of a sudden, you start seeing ads in trade magazines for DiSlord VNAs next to Anritsu and Keysight, then you can start complaining about GPL.


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

 

On 8/6/20 2:57 AM, igor-m 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.
I'm not sure I agree, Igor-M - collaborative development often involves beta testers, and this forum provides a convenient mechanism to make untested betas available.

Given that the source does get regularly updated, I don't think this violates the spirit of open source - otherwise a *group* of developers would have to keep their internal development hidden. Why not use public fora as a means of communication.


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.
I think that's a strawman - Why don't you wait 6 months, and then complain about how there's still a stream of bug-free binaries, with no source.

Open source is wonderful, but there are plenty of open source projects that are 80% complete (the vast majority of projects developed by grad students, for instance - got the degree, no need to do bug updates any more, and anyway I have a real job that actually pays me now)

Let's focus our "why isn't source available" on pernicious evils - manufacturers who build custom versions for their products and have NEVER released source.




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.
yes it's open source - but I don't see a huge number of people stepping up to make changes. From what I see, there's a few folks grinding on the software, and dozens weighing in with testing, feature requests, etc.

I'm not sure what axe you're grinding here, Igor-M?


I think you're setting an artificial "intellectual purity" bar to participate in software development.

I think OneofEleven and DiSlord are doing good work, and should keep it up, in what ever release strategy they care to do. They say that it's a hobby for them, and let's let that be for now. If all of a sudden, you start seeing ads in trade magazines for DiSlord VNAs next to Anritsu and Keysight, then you can start complaining about GPL.


Re: Useful frequency range of NanoVNA H-4?

 

By the way, I used the NanoVNA as an SWR meter on 1296 MHz. It worked fine.
I looked at the SWR of my antennas for 222, 432, 902 and 1296 MHz. I had
originally tuned these antennas with an SWR bridge and a transmitter. Now I
see the adjustments are a little off for all of them except the 902
antenna. Now all I need to do is re-tune them using the NanoVNA.

The NanoVNA agrees exactly with my AA-600 SWR meter for SWR across 5 to 30
MHz with my MFJ 1796 vertical antenna.

Zack W9SZ

On Tue, Jul 21, 2020 at 2:17 PM Zack Widup via groups.io <w9sz.zack=
[email protected]> wrote:

I thought I'd use my NanoVNA H-4 to tweak a 3-pole helical filter for 1296
MHz that I have for a transverter. The helical filter is mounted on a pc
board with SMA input and output. I calibrated the NanoVNA for 1280 to 1320
MHz and connected the filter to it. The NanoVNA displayed s11 as I expected
(a good dip which I could adjust to 1296 MHz). However, the s21 did not
display what I expected. I expected a response that a normal bandpass
filter would have. Instead, I had pretty much a straight line for s21
across the frequency range that fluctuated with each reading.

Is the performance poor at 1296 MHz?

Zack W9SZ


<

Virus-free.
www.avast.com
<

<#DAB4FAD8-2DD7-40BB-A1B8-4E2AA1F9FDF2>



<>
Virus-free.
www.avast.com
<>
<#DAB4FAD8-2DD7-40BB-A1B8-4E2AA1F9FDF2>


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

 

On 8/6/20 3:24 AM, DiSlord wrote:
Ok. I stop public binaries.
This is getting into the classic bike shed painting exercise -

If you want to make available binaries of test versions for someone to test (not actually "releases", per se) without the matching source code, then I suppose it's "technically" a GPL violation (IANAL and all that).

I think that the *intent* of GPL is satisfied by making source available for major *releases*.

In theory, DiSlord could arrange a group of beta testers, set up a private distribution channel, and send binaries (without source) back and forth and not get the GPL knickers in a twist. This would be no different from a group of developers at a company all working on various pieces of a product.

But why bother.

Yes, I understand "thin edge", "camel's nose", "slippery slope" arguments.

Ultimately, though, the question is whether *meaningful* source code releases are occurring (and I think they are).

I would say that this kind of (IMNSHO) bickering is why open source has a reputation for being a PITA.

Be open about what you're doing.
Publish binaries for test that are useful
Publish source for releases

If it goes on for 6 months with only binary, and there's significant changes in functionality, with no source release - then start asking about whether the author is living up to the spirit and intent of GPL.


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

 

DiSlord and OneOfEleven thanks so much for your contributions that have moved the NanoVNA a step forward. A few bad actors always seem to mess things up for the majority.

With all the recent demands on your time, primarily from one or two sources, I figured at some point you would wonder if its worth the effort. Some people don't seem to realize you both have other lives besides your voluntary coding activities.

Again, thanks for your many contributions and helping us to better understand the capabilities of the NanoVNA.

- Herb


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 !!