Hello.
I have a condition, when few SDRs are connected to the same host and used by different applications. Some tools are using only specified devices and not able to scan-and-add new ones, but development version of this one is "greedy" and tries to catch everything it see. As result, it causes 'race conditions', when it locks devices, which are not planned to be used. In my situation it is self-made tool, which makes records by CRON and does not holds SDR permanently. When I put 'disable device' trigger in Configuration, it works only for a while and may be sporadically reset. So, it will be cool to have some 'killer switch', when scanner part will be not looking for all available SDR and work only with configured ones.
P.S. At all, thanks for this cool solution. It is very helpful to monitor HAM activity.
Hello. I have a condition, when few SDRs are connected to the same host and used by different applications. Some tools are using only specified devices and not able to scan-and-add new ones, but development version of this one is "greedy" and tries to catch everything it see. As result, it causes 'race conditions', when it locks devices, which are not planned to be used. In my situation it is self-made tool, which makes records by CRON and does not holds SDR permanently. When I put 'disable device' trigger in Configuration, it works only for a while and may be sporadically reset. So, it will be cool to have some 'killer switch', when scanner part will be not looking for all available SDR and work only with configured ones.
P.S. At all, thanks for this cool solution. It is very helpful to monitor HAM activity.