I've built a new nanovna-saver.exe from Holger's repository. He has done a huge amount of rework so I can't speak to all of the changes or possible new issues, but for sure it now remembers where markers are (phew) and it connects more reliably to the comm port at startup.

See here: http://www.audua.com/Files/nanovna-saver_6_19.exe

Enjoy,
Mark

I've built a new nanovna-saver.exe from Holger's repository. He has done a
huge amount of rework so I can't speak to all of the changes or possible new
issues, but for sure it now remembers where markers are (phew) and it
connects more reliably to the comm port at startup.

See here: http://www.audua.com/Files/nanovna-saver_6_19.exe

Enjoy,
Mark
=================================

Mark,

Thanks for your efforts. Is that version only for the V2, or does it also
work on the original, and the -F variants.

Cheers,
David
--
SatSignal Software - Quality software for you
Web: https://www.satsignal.eu
Email: david-taylor@blueyonder.co.uk
Twitter: @gm8arv

Hi Mark,

Is it an official versuin to replace the 0.2.2-1 version or something else ?
Does this version is specific to the NanoVNA-v2 version or does it works
with the other versions?

73's
Pierre-François, F5BQP



Le 19/06/2020 à 15:00, David J Taylor via groups.io a écrit :

> I've built a new nanovna-saver.exe from Holger's repository. He has
> done a huge amount of rework so I can't speak to all of the changes or
> possible new issues, but for sure it now remembers where markers are
> (phew) and it connects more reliably to the comm port at startup.
>
> See here: http://www.audua.com/Files/nanovna-saver_6_19.exe
>
> Enjoy,
> Mark
> =================================
>
> Mark,
>
> Thanks for your efforts.  Is that version only for the V2, or does it
> also work on the original, and the -F variants.
>
> Cheers,
> David

This is not an official version. You'd have to talk to Holger but I assume it will also work for the other versions as well. I built it from his latest branch with a couple of small bug-fixes (that he'll probably incorporate into the repo).

AFAIK: The original maintainer seems to have stopped working on the software while Holger seems to be working on the software. He hasn't worked on creating binary releases that I could find, so, since I'm using it and prefer an .exe anyway, it seemed polite to post whatever I'm using. I've tested and run it a few times on my -2 and repaired a minor bug or two at his repository but that's all I really know.

Regards,
Mark

On Fri, Jun 19, 2020 at 04:20 AM, MarkZ wrote:

I've built a new nanovna-saver.exe from Holger's repository. He has done a huge amount of rework so I can't speak to all of the changes or possible new
issues, but for sure it now remembers where markers are (phew) and it connects more reliably to the comm port at startup.
==================================================
Mark,
Your previous 6_12 Beta exe runs on my Win10 x64 sytem, but the new 6_19 exe is only showing a third of the completed s21 sweep (see attachments).

- Herb

Hi Herb,

That looks like the vna-qt interference issue but that's been fixed for a while so I don't know what that could be. I can't replicate it. Can you maybe walk through the steps? The units seem to have some USB connection issues so maybe just try rerunning the program?

If you run the program from a command prompt with a -d suffix it will print debugging information into the console. Maybe try that and see what it says. If you copy that into a text file and attach to a message I'll take a look at it for you.

Regards,
Mark

Hmmm, it does look like he's added 'customizable data points' to the feature set to let you pick sweep length somehow. I have no idea if that's implemented but it's defaulting to 1024 data points, which imho is more than I need and runs a little slower.

-Mark

Hi Herb,

So, it's just a possibility but it may be this. Holger is adding the ability to select number of sweep points (yay) but it's partially implemented and so it allocates a bigger than required vector for data in case the point count goes up. However, there's currently no way for the count to go up and possibly the too-long vector matters since the code is incomplete. I've rebuilt with the right-sized vector (303) in case that helps. If it turns out that there is a way to change the sweep count this won't be a good thing : )

Anyway, I just updated the above URL file since I'm pretty sure the change I made is benign. I haven't talked to Holger nor attempted to push that change though, since it will conflict with adding changeable sweeps. I honestly don't think it's your issue, Herb, but it can't hurt.

fwiw I'm so wedded to this version because it keeps the markers in place, which I sorely need.

Regards,
Mark

Hi,

On 19.06.20 18:40, MarkZ wrote:
> Hmmm, it does look like he's added 'customizable data points' to the
> feature set to let you pick sweep length somehow. I have no idea if
> that's implemented but it's defaulting to 1024 data points, which
> imho is more than I need and runs a little slower.

It should be defaulting to 303 data points. Running nanovna-saver
in debug mode dumps dp selection to console.

The number of data points per scan are selectable if you click on
the "manage"-button beside the device selection. Next sweep
should use the new selected setting then.

If segments are selected in the sweep section, they should be scanned
successively. So as in Herb's screenshot the curves should be appear
in thirds of the range.

But I'll take a look what happens, if that is not the case.

73
Holger

P.S.:

I've not experienced that behaviour yet. Even reducing data points
after a hight number scan works for me [tm]...
Just kidding, I keep an eye on that.

Most current binary of my code is downloadabel via
https://github.com/zarath/nanovna-saver/actions/runs/141156633

As it is an github action asset, one has to be logged in to
github...

73
Holger, DG5DBH

Ah, I didn’t see the 3 segments choice. I never use more than 1. It’s very likely that imho.

Mark

On Fri, Jun 19, 2020 at 12:30 PM, MarkZ wrote:

Ah, I didn’t see the 3 segments choice. I never use more than 1. It’s very likely that imho.
================================================
Mark,
Yes, with 1 segment chosen there is no problem. I didn't realize Holger added an option for selecting multiple points which makes multiple segments less usefu -at least on the V2. Not sure how the other NanoVNA's react.

- Herb

So far it works on my H4 and -F. Still playing with it.

It crashed on me once when I swept at 101 data points (did I need to click Refresh in manage?) but otherwise worked consistently well and it's really nice being able to switch sweep length.
-Mark

By the way, the reason I don't use multiple segments is that Gabriel explained that the firmware calibrates when the sweep parameters change which halves the speed on a change. As a result, the multisegment sweeps - which change the parameters repeatedly - are always 1/2 the possible 'best' speed whereas a 1-segment sweep speeds up on the second and later runs. If you need the fine detail, so be it, I'm just impatient.

-Mark

Hi Herb,

Sure enough the multi-segment isn't working with that build. I've updated my _6_19.exe build to have the fix in it and submitted a pull to Holger (that he may want to do a different way).

Regards,
Mark