Closed PA3CCE closed 4 years ago
@RandMental - a hint: you may attach your debug.txt file to your message by dragging and dropping.. No need to paste the raw debug text into the message. That would make this thread much shorter then :)
@ RandMental ....Very strange, I'm running NanoVNA-H4 on DiSlord's version 0.9.3.4 on NanoVNA-Saver 3.6 pre as well and can't get it connected, ....It crahes while doing the initial sweep on the default settings....Switching the device on and off before does not help.
FYI - enclosed are some logs where it crashed here (latest 036pre, H4-0847fw, Win10, 10Segments).
Validation Error.
Sorry I have no clue why Rune had added an exception if a data value is out of an arbitrarily range. The value was raised several times.. I don't know if there was a discussion about set setting in the early state of the software...
Can be disabled in the manage device window
Correction - calibration still fails with a crash when clicking Apply after the Wizard finished the SOL calibration sequence. 10 Segments by 201 points sweep selected
Debug attached
regards
Describe the bug Strange behaviour after having fllled the markers tn the main window of NanoVNA-Saver 3.4..
To Reproduce Steps to reproduce the behavior:
Connect your 2-port device , switchon NanoVNA and startup NanoVNA-Saver.
Click on ''Connect to Device" Wait unti;l the sweep has finished. The marker data- AND start/stop area in the main window have been filled with erratic data.
Fill in the sweep range I used 50M to 900M Fill the marker frequency 1 to 6 bars, I used 50M, 100M 200M 300M 500M, 900M
Start the sweep, I had set for 20 Segments in NanoVNMA-Saver.
The sweep starts and fills all marker areas wiith data of MARKER 1
Expected behavior Marker areas have to be filled wit data. of markers being set