开云体育

That's just wrong.
Every time it connects, it reset the H4 to what someone else thinks it should be. The user should be the one to determine that. I even changed the Manage settings to agree with my device.
1. I could not change them until I had connected. Not good.
2. Even after connecting, changing settings, disconnecting....changed them back to some default.

I don't think I'll be using Saver much. Too many problems and bugs.

On 5/15/22 3:00 PM, Rich NE1EE wrote:

That's just wrong.
Every time it connects, it reset the H4 to what someone else thinks it should be. The user should be the one to determine that. I even changed the Manage settings to agree with my device.
1. I could not change them until I had connected. Not good.
2. Even after connecting, changing settings, disconnecting....changed them back to some default.

I don't think I'll be using Saver much. Too many problems and bugs.

Maybe it's not the way to go for your use case.

Have you tried editing the .ini file?

Yes, saver has some bugs. In particular I have noted some inconsistencies
when trying to set it for 401 pts on the H4 (it works better if I let it
use 201 or 101 pts and then let Saver control additional segments for more
points).

But please note that many of us who use it want Saver to be in control, and
do not want to worry about what state their device was left in before they
attach it. And we do any required setup through Saver.

You obviously have a different idea/use case. If you haven't tried
nanovna-app, you may find you like it better. In that app, you need to
understand that the many graphing and charting options are only seen after
right-clicking on a graph pane.

Stan

On Sun, May 15, 2022 at 04:20 PM, Stan Dye wrote:

Yes, saver has some bugs. In particular I have noted some inconsistencies
when trying to set it for 401 pts on the H4 (it works better if I let it
use 201 or 101 pts and then let Saver control additional segments for more
points).

Saver defaults to 101 points to maintain compatibility with older NanoVNA devices. I just go into Manage and set it to 401 points. Seems to work fine for me. What version of H4 firmware are you using? Which version of Saver?

But please note that many of us who use it want Saver to be in control, and
do not want to worry about what state their device was left in before they
attach it. And we do any required setup through Saver.

I think that is the best way to use Saver. Just power up the NanoVNA and use slot 0 so the same cal data is loaded every time. I keep slot 0 at 50 kHz. to 900 MHz. Then connect to Saver. That way when Saver calibrates it has the same NanoVNA configuration and you can reload the Saver calibrations at a later date. When I disconnect from Saver I power down/power up the NanoVNA because Saver leaves the NanoVNA in an unknown state. Saver supports multiple hardware versions of the NanoVNA and the software developers decided not to try and restore the NanoVNA to the state when it was initially connected.

You obviously have a different idea/use case. If you haven't tried
nanovna-app, you may find you like it better. In that app, you need to
understand that the many graphing and charting options are only seen after
right-clicking on a graph pane.

NanoVNA App by One-Of-Eleven is my preferred PC program for the NanoVNA. Better graph scaling and more features. I use the forked version by Owen Duffy because he fixed some bugs.


Roger

On Sun, May 15, 2022 at 03:01 PM, Rich NE1EE wrote:

That's just wrong.
Every time it connects, it reset the H4 to what someone else thinks it should
be. The user should be the one to determine that. I even changed the Manage
settings to agree with my device.
1. I could not change them until I had connected. Not good.
2. Even after connecting, changing settings, disconnecting....changed them
back to some default.

I don't think I'll be using Saver much. Too many problems and bugs.

I replied to your post on this issue a few days ago but you did not reply. Did you see my post?
/g/nanovna-users/topic/91082901#28066

Roger

On 2022-05-15 16:19:-0700, you wrote:

noted some inconsistencies when trying to set it for 401 pts on the H4 (it works better if I let it use 201 or 101 pts and then let Saver control additional segments for more points).

Not fond of "inconsistencies" here...but I see the point you make...

But please note that many of us who use it want Saver to be in control, <snip> And we do any required setup through Saver.

Problem for me is what I described in my email...the out-of-sync nature of the Manage dialog and its unpredictable (to me) behavior. If it works well for others, that's fine...it doesn't have to meet my expectations...but I was irritated when I wrote the email. Not using Saver should help w that :-)

If you haven't tried nanovna-app, you may find you like it better.

I have. I do. I don't expect perfect software at this level, but I like to be able to predict how it will behave, and not remember a bunch of steps. I documented that its behaviour is inconsistent. Being in control is one thing, and I appreciate that. And of course, the usual guessing game for newbies, because there is no good user manual that I have seen.

~R~

On 2022-05-15 18:06:-0700, you wrote:

Saver defaults to 101 points to maintain compatibility with older NanoVNA devices. I just go into Manage and set it to 401 points.

Didn't work for me, per email

Seems to work fine for me. What version of H4 firmware are you using? Which version of Saver?

nVNA-H4 v4.3_MS, firmware 1.1 , Saver 0.4.0, and your mod

I think that is the best way to use Saver. Just power up the NanoVNA and use slot 0 so the same cal data is loaded every time. I keep slot 0 at 50 kHz. to 900 MHz. Then connect to Saver. That way when Saver calibrates it has the same NanoVNA configuration and you can reload the Saver calibrations at a later date. When I disconnect from Saver I power down/power up the NanoVNA because Saver leaves the NanoVNA in an unknown state. Saver supports multiple hardware versions of the NanoVNA and the software developers decided not to try and restore the NanoVNA to the state when it was initially connected.

Yep. That long explanation is what I don't want to bother with.

I use the forked version by Owen Duffy because he fixed some bugs.

I don't because it does not work standalone as the other programs do. Personal preference.

On 2022-05-15 18:12:-0700, you wrote:

I replied to your post on this issue a few days ago but you did not reply. Did you see my post?
/g/nanovna-users/topic/91082901#28066

Yep. Del the ini file.
"In order to get faster sweeps the display was frozen on the NanoVNA"
I guess I have a second or two here and there... ;-) I am not bothered by sweep speed. I appreciate faster anything (almost ;-), but the H4 on bandwidth 100 is not too slow for me. 'Course I guess if I were spending hours with it, I'd appreciate any speedup....

Jim Lux mentioned editing the ini file, which had not occurred to me...I'll look into that.