NanoVNA V2 Forum

Note: this page is a mirror of https://groups.io/g/NanoVNAV2.
Click here to join and see most recent posts.

Settings not savable


Klaus Wörner 2020/08/11 11:35

Hello,
I'm a user of NanoVNA1 and now bought the SAA2.
I tried to disable traces and save it, so that there will be only two traces after powering on.
I know it from V1 that I have to save the calibration for some settings, save the settings for other settings. But none of that works for me. I updated the firmware to the version from 2020-05-25.
I think it's a bug and hope that it will be fixed in the next release. Maybe it will be possible to implement some improvements in the GUI, too, like the actual changes from OneEleven in V1?

CT2FZI 2020/08/11 19:46

Hello,

On V2, every time you change the frequencies one must either calibrate
again or reload the calibration data.

This is a "feature" by design, not a bug.

Cheers



A terça, 11/08/2020, 19:37, Klaus Wörner <dl5kv@darc.de> escreveu:

hwalker 2020/08/11 15:00

On Tue, Aug 11, 2020 at 11:37 AM, Klaus Wörner wrote:

.. I tried to disable traces and save it, so that there will be only two traces
after powering on...
=================================
Klaus,
The V2 does not automatically recall SAVE 0 when you power-on like the NanoVNA does. You have to manually recall the Save location you saved your changes to when you power-on. You get used to it after a while.

Also as Luis noted, the V2 does not interpolate between points when you change settings as the NanoVNA does, so you have to perform another calibration whenever you change settings.

- Herb

Klaus Wörner 2020/08/12 00:51

On Wed, Aug 12, 2020 at 12:00 AM, hwalker wrote:

>
> On Tue, Aug 11, 2020 at 11:37 AM, Klaus Wörner wrote:
>
> .. I tried to disable traces and save it, so that there will be only two
> traces
> after powering on...
> =================================
> Klaus,
> The V2 does not automatically recall SAVE 0 when you power-on like the
> NanoVNA does. You have to manually recall the Save location you saved your
> changes to when you power-on. You get used to it after a while.
>
> Also as Luis noted, the V2 does not interpolate between points when you
> change settings as the NanoVNA does, so you have to perform another
> calibration whenever you change settings.
>
> - Herb
>
Thanks Herb,
that's the solution. You have to get the idea, first.

Hugo 2020/08/13 08:36

Are developers currently working on the firmware so that the recordings are done automatically and that the data is recalled when there are changes of settings?

aleks07111971 2020/08/13 09:20

not

Hugo 2020/08/14 05:01

Currently no developer working on V2? That's right?
However, adding the function of recalling calibration data shouldn't be super complicated to program ...

The product is going into perdition? 😟

aleks07111971 2020/08/14 05:10

There is no place in the memory!

Hugo 2020/08/14 05:29

Is it a question of hardware memory or simply the software is not yet rendered as in V1? So he can't have more options?

aleks07111971 2020/08/14 07:52

You can try to free up space, but it takes a lot of effort and time.

reuterr 2020/08/14 07:54

On Fri, Aug 14, 2020 at 02:01 PM, Hugo wrote:
> Currently no developer working on V2? That's right?
> However, adding the function of recalling calibration data shouldn't be super
> complicated to program ...
>
Hello Hugo,

If you think it is not so complicated, you are the best suited person to program it.

73, Rudi

Hugo 2020/08/14 08:05

Ok, I just wanted to know the reason and if there was any further development. If it is then a hardware limitation then it will be necessary to rewrite the code to try to make room ... More complex let's say ... Too bad the limit has already been reached ...

aleks07111971 2020/08/14 08:10

I hope dislord becomes interested in V2 and fixes the firmware anyway

Hugo 2020/08/14 08:16

Yes I really wish! The whole community will be grateful to him !!! It is surely one of those which could most quickly and easily correct the biggest gaps.

I hope that some will go over the small discords which concern only a minority in order to help a whole group or places to punish it for no reason!

reuterr 2020/08/14 08:56

On Fri, Aug 14, 2020 at 05:16 PM, Hugo wrote:
>
> to punish it for no reason!
>
The reason DiSlord retired was because of outrageous demands or opinions.

73, Rudi DL5FA

aleks07111971 2020/08/14 08:59

Is that a question?

CT2FZI 2020/08/14 09:31

Hugo,

As you should be aware, and as I mentioned before, this is not an issue, its a feature by design since the beginning. This subject was extensively discussed already.

Also, if one considers the bigger (read more expensive VNA) also have same feature.

If anything else, it will remind you that you are using older calibration data.

If one uses nanovna-saver, all these issues go away and the V2 will exponentially increase its potential.

Siegfried Jackstien 2020/08/14 16:56

the bigger displays most of the time have an sdr card slot ... what if
that slot would hold a card where you can:

store sweeps AND store calibration data ... and when switched on with a
button pressed soft looks for "vnav2.frm" (or similar) on the sd card
and update firmware that way (besides using vna qt soft)

with an "external" memory added (like that sd card) it would be simple
to store calibration data there and when unit is switched on it reloads
that data ... even a big big table with lots of calibration points could
be saved there (so no recalibration needed if you change sweep range or
centre frequency) ... just do a very long sweep for each setup (no
cable, short cable, mid cable, long cable) with lots and lots of
calibration points (yes that may take a while!!) ... but at the end
saves you a lot of time

when switch on fw asks user what cable is used ... and then uses the
calibration from that table ... only if the user wants to use "manual"
calibration it does the open short load thingy ... but if not the soft
should use caibration data out of that table (that is stored before on
the sd card) ... i hope you understand the idea behind that :-) ... do a
fine stepped long sweep for each setup you regularly use ... and store
that calibration data on a big table ... and reload the needed
corrections without the need to do a calibration run each time you wanna
use the unit

just an idea for a "v3" ... grin (besides using big screen, n connectors
... and increase tunig range to 6 gig plus continuous cw generator)

greetz sigi

Am 14.08.2020 um 16:31 schrieb CT2FZI:

Hugo 2020/08/14 10:16

On the other hand, this proposal does not work with V2 at present, even for the V2N 4 inch version. But indeed, there are several lessons to be learned for the rest of V3 ...

aleks07111971 2020/08/14 10:41

V3??? 6ggz
https://github.com/jankae/VNA

Siegfried Jackstien 2020/08/14 18:03

nice project ... but i thought just replace the clock with the max2871
(and maybe a small fw change to extend the range upwards) ... and check
if we can use a bit better circuit on the rf end (better baluns maybe?!?)

the max2871 has same pin layout so swapping it should be an easy job :-)

the project from jankae is a complete different design (but a nice idea)
... like reinvent a wheel hi hi ... i thought usage of the design we
have but improve it a bit ... maybe even modding of an already bought
unit should be possible (with some smd soldering skills) ...

repositioning of some parts could improve the isolation and increase
dynamic range a bit (more distance and better shieldings) ... but that
would mean a new pcb layout

greetz sigi dg9bfc

Am 14.08.2020 um 17:41 schrieb aleks07111971@yandex.ru:

To reply to this topic, join https://groups.io/g/NanoVNAV2