开云体育

I wish that Saver would not automatically change the H4 when it connects.
I think the sequence should be to read the H4, and then we can change Saver and send that to the H4.

Not sure how to do that, because there is a Manage dialog, but its use is not clear, and when I try to use it I get errors.

On Fri, May 13, 2022 at 08:12 AM, Rich NE1EE wrote:

I wish that Saver would not automatically change the H4 when it connects.
I think the sequence should be to read the H4, and then we can change Saver
and send that to the H4.

The initial releases of NanoVNA Saver were developed by Rune B. Broberg for the NanoVNA-H and nanoVNA-H4. Unfortunately he became ill and development stopped at version 2. Further development of V3 codewas done by "zarath" and many changes and bug fixes were done with input from others. Other NanoVNA products like the V2 and -F were now supported and DiSlord's new transfer protocol was added to give faster sweeps. In order to get faster sweeps the display was frozen on the NanoVNA and unfortunately operation was not restored on the nanoVNA after exiting the program. So users have to power off and on again after using Saver.

Not sure how to do that, because there is a Manage dialog, but its use is not
clear, and when I try to use it I get errors.

The Manage entry screen was enhanced so that the number of data points used by Saver in transfer mode could be selected by the user. It defaults to 101 to be compatible with older NanoVNA devices and older firmware. With the -H4 you can increase the number of data points transferred in one sweep to 401.

If you are having problems with NanoVNA Saver it can sometimes be due to a corrupted .ini file. Just delete it and a new one will be created when the program starts. You will find it in this directory in Windows.
C:\Users\Your-User-Name-Here\AppData\Roaming\NanoVNASaver\NanoVNASaver.ini

Roger