nanovna-saver icon indicating copy to clipboard operation
nanovna-saver copied to clipboard

Error with segmented calibrations and V2

Open zarath opened this issue 4 years ago • 1 comments

Unfortunately, I was too quick to close this ticket.

a) Yes I can do a 10 segment sweep of 101 points per segment with the nanovna V2 and with the latest nanovna-saver development version. But this will only work if I have calibrated with 101 points.

b) What does NOT work is a calibration based on 10 segment of 101 points per segment (so 10 segments - 1010 points total). The crash during the calibration procedure is systematic and very easy to re-produce. I am using the Wizard/Assistant to do the calibration.

c) Interesingly, please note that a calibration with single segments of 1021 points (select 1021 points under manage device) WORKS of course. However what does NOT work, is to do a 1 segment sweep of 101 point after this calibration of 1021 points (ie, change from 1021 to 101 points under managed device), even after stopping and restarting the application; I get the very SAME error

d) All of this works very well with the nanovna V1, so this problem is V2 specific

Objective: The idea is to do the calibration with a one segment sweeps of 1021 points or with 10 segment sweeps of 101 points/segment. Then depending on how long I am willing to wait during my measurements and depending on the resolution I want, I do a 1 segment sweep of 101 points, multiple segment sweeps of 101 points/segment or eventually a 1 segment sweep of 1021 points.

image

root@on7yi-ubuntu:/opt/nanovna-saver-d# nanovna-d NanoVNASaver 0.3.7-rc07

Copyright (C) 2019, 2020 Rune B. Broberg Copyright (C) 2020 NanoVNA-Saver Authors

This program comes with ABSOLUTELY NO WARRANTY This program is licensed under the GNU General Public License version 3

See https://github.com/NanoVNA-Saver/nanovna-saver for further details.

QStandardPaths: XDG_RUNTIME_DIR not set, defaulting to '/tmp/runtime-root' Settings: /home/peter/.config/NanoVNASaver/NanoVNASaver.ini 2020-08-11 12:30:35,193 - NanoVNASaver.Hardware.NanoVNA_V2 - ERROR - expected 3264 bytes, got 3168 2020-08-11 12:30:53,792 - NanoVNASaver.SweepWorker - ERROR - argument out of range Traceback (most recent call last): File "/opt/nanovna-saver-d/NanoVNASaver/SweepWorker.py", line 80, in run self._run() File "/opt/nanovna-saver-d/NanoVNASaver/SweepWorker.py", line 139, in _run self.app.vna.resetSweep(start, end) File "/opt/nanovna-saver-d/NanoVNASaver/Hardware/NanoVNA_V2.py", line 183, in resetSweep self.setSweep(start, stop) File "/opt/nanovna-saver-d/NanoVNASaver/Hardware/NanoVNA_V2.py", line 222, in setSweep self._updateSweep() File "/opt/nanovna-saver-d/NanoVNASaver/Hardware/NanoVNA_V2.py", line 228, in _updateSweep int(self.sweepStartHz - (self.sweepStepHz * s21hack))) struct.error: argument out of range

Originally posted by @satfan52 in https://github.com/NanoVNA-Saver/nanovna-saver/issues/270#issuecomment-671882264

zarath avatar Aug 13 '20 17:08 zarath

You see the strange peaks there on S11, are you getting the communication error (see my ERROR expected.....)

ok1vaw avatar Aug 21 '20 09:08 ok1vaw