This certainly doesn't look right:
2019-10-12 15:52:00,598 - NanoVNASaver.Hardware - DEBUG - Found version
info: 0.1.1.1-5-gd609fb2
2019-10-12 15:52:00,598 - NanoVNASaver.Hardware - DEBUG - Parsed
version as 1.1.1-5-gd609fb2
2019-10-12 15:52:00,598 - NanoVNASaver.Hardware - DEBUG - Testing against 0.2.0
2019-10-12 15:52:00,598 - NanoVNASaver.Hardware - DEBUG - Parsed
version as 0.2.0
2019-10-12 15:52:00,598 - NanoVNASaver.Hardware - DEBUG - Newer than
0.2.0, using new scan command.
This certainly doesn't look right. The 4-digit version number of Hugen's (I
think?) is parsed as 1.1.1 instead of 0.1.1. My software only supports
3-part (major/minor/revision) version numbers, and I guess I need to make
it more clear that it's only to read the first 3 parts, and to treat the
rest as text.
I will fix it for 0.1.3, but for now, you may have to stick with
NanoVNA-Saver 0.1.1. Or upgrade firmware to edy555's 0.2.3. ;-)
--
Rune / 5Q5R
On Sat, 12 Oct 2019 at 23:55, bryburns via Groups.Io <bryburns=
[email protected]> wrote:
On Sat, Oct 12, 2019 at 03:48 PM, Rune Broberg wrote:
-D logfile.txt
Rune,
The logfile.txt is attached. I ran the initial scan, one without a
calibration loaded, loaded a calibration, and then ran another scan before
closing the file. You can probably tell all that from the information in
the text file.
--
Bryan, WA5VAH
