Hi Erik,
The scanraw command was created by QRP-RX and I have it documented in the console command doc.Since your scan is different from edy555's version, should I change scan reference to what the edy555 scan performs and just leave QRP's scanraw command in place instead of yours ?
toggle quoted message
Show quoted text
On Wednesday, October 23, 2019, 9:27:16 a.m. GMT-4, erik@... <erik@...> wrote:
If you want to use this command sequence for the edy555 and hugen firmwares:
pause
scan startfreq endfreq count
frequencies
data
resume
you can insert the "cal" and "edelay" command if needed and these apply as on screen
For maximum multi measurements speed you should not "resume" but keep the nanoVNA paused
There is (because of a bad decision by me) possibly confusion on what the "scan" command does.
Edy555 original implementation was scan being equal to sweep and wait till the data was available.
I changed that to have scan doing an on demand scan with unlimited amount of points and NO calibration/edelay being apply
As this lead? to two different "scan" command Rune had to sort out the mess.
I intend to change my "scan" command to "scanraw" that will be the same as what already has been implemented by another firmware developer (sorry, forgot your name....)
scanraw will pause the "on screen" measurements as these interfere with realizing maximum speed.
So "scan" will always be in all firmwares an on demand measurement of maximum 101 points with everything (e.g. calibration and edelay)? the same as on the screen
