Hi Erik,
I found another minor nuisance: When changing mode from Low to High the default frequencies also changes, which is nice, but the CW frequency not, which is ok being CW mode not allowed in High mode, which is grayed out, but it gives an exclamation mark alarm (error:? invalid CW frequency), which I must clear entering a "in range" value such as 500 in order to allow the scan. When changing back to Low mode, the value persist and I got the same alarm.? I think that the range check in the CW field should be disabled when in High mode.
I'm quite good finding software bugs, as a friend used to say "I have a sexual finger: anything that I touch, I screw it".
Regards,
Ignacio EB4APL
toggle quoted message
Show quoted text
El 05/10/2020 a las 13:44, EB4APL via groups.io escribi¨®:
Hi Erik,
Everything you mention works, but if I try to close the program once I made a scan, I got the message "Range check error" and the comms disconnects. In order to be able to quit I have to connect again and close the program without doing any sweep this time.
I saw a nice feature: the frequency settings are got by the tinySA and effective when the App scan is finished
Kind regards,
Ignacio EB4APL
--
El software de antivirus Avast ha analizado este correo electr¨®nico en busca de virus.
