Hi John,
if you experience crashes, please try:
- Running the program for a command prompt, which preserved the crash
message,
- Running using "-D logfile.txt" as a parameter, which saves debug data to
a file, which you can then pass to me for further analysis.
It *may* happen if you have not calibrated the NanoVNA itself, and it sends
values that are so unrealistic, the program doesn't know how to parse it.
Generally, measurements indicating severely positive gain (more than 30dB
maybe?) are rejected as corrupted. If the same measurement shows bad values
more than 20 times in a row, the program stops (and reports an error on the
console). It's not supposed to *crash* when it does this, but ... I think
sometimes it does. :-(
--
Rune / 5Q5R
toggle quoted message
Show quoted text
On Fri, 27 Sep 2019 at 21:47, John AE5X <ae5x@...> wrote:
Tried it on two different Windows 10 machines - it seems some combinations
of sweep settings cause the program to close suddenly. This occurred on
both PC's.
Calibration was done (400kHz - 5MHz), amateur bands selected to show and
sweep was set to 3.5 - 15 MHz.
