On Sat, Oct 15, 2022 at 02:14 PM, Mike wrote:
NanoVNASaver.Hardware.Hardware - ERROR - No VNA detected. Hardware responded
to CR with:
too many arguments, max 4
ch>
This is a known bug of 1.2.0, see my issue report #34:
It was already fixed by DiSlord in June. I strongly recommend to follow his fast development on github, his x.y.00 release will be improved in x.y.nn iterations, where nn is > 00.
It is a simple task to clone is repo and update the Nano as soon as you see a advantage for you.
On Sat, Oct 15, 2022 at 07:15 PM, Roger Need wrote:
Version 5 of NanoVNA Saver has a lot of code changes and is buggy. I suggest
you try version 4.
Also consider using NanoVNA app instead. Much better graphics scaling and
sweep comparison features. Calibration works well and is reliable.
The current version 5 suffered greatly from regressions and stricter syntax requirements introduced by the transition from Python 3.9 to 3.10. The NanoVNASaver team has improved a lot in the last few days.
It has the great advantage that the saver as a python script it is platform independent and you can easily make changes on the fly while the app is targeted on windows (you can also translate for lin and mac, but you need an obscure build tool).
Ho-Ro