Hi Erik -
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
.. then how will "scan" differ from "sweep"?
I intend to change my "scan" command to "scanraw"
that will be the same as what already has been implemented by another firmware developer
If there is/has been only one "scanraw" behavior,
then host apps need only test for "scanraw ?" response to determine support
This seems less problematic than coding rules based on e.g. parsing version string.
If edy555 shell recognizes some >>other<< command that Erik's firmwares do NOT (or vice versa)
then testing for '?' in response to that could sort "scan" behaviors.
Oristo