would be nice to have a userdefined black list for the cluster. The reason is that guys like F8DGY do spot only it´s own frequencies. If you go to look for a spotted DX ther is no DX. A "filter" like this possible
73´s ....
73´s .. Juergen ... ALT-512 SDR (10W) , 50 m random wire at SG-211 autotuner, 2 x Xiegu G90 (20W HF TRX) one as portable Radio. Also TS-790E (40 W) for VHF/UHF with X-50 vertical and Duoband 4-Element LPDA.
the User himself has to manage those "Blacklist". Some guys need spots like F8DGY sent others not. So it only needs a textfile or something like this and the user can write the calls in it.
73´s .. Juergen ... ALT-512 SDR (10W) , 50 m random wire at SG-211 autotuner, 2 x Xiegu G90 (20W HF TRX) one as portable Radio. Also TS-790E (40 W) for VHF/UHF with X-50 vertical and Duoband 4-Element LPDA.
I use the integrated cluster modules in L4O and not need a separate browser to use the filteroptions of a ve7cc cluster. Should be possible to connect to ve7cc via the L4O cluster module but to use the different filters i have to send some commands in each of the different sessions. Would be easier to have a blocklist in the L4O cluster module. Each user can enter the spotter callsigns he would like to block in a seperate file.
@ Nino
As first call in the list F8DGY was o.K. Think "Nino" does not spotting the contacts of it´s own QRG and use the cluster as a "Logbook" or a "Chatroom"
73´s .. Juergen ... ALT-512 SDR (10W) , 50 m random wire at SG-211 autotuner, 2 x Xiegu G90 (20W HF TRX) one as portable Radio. Also TS-790E (40 W) for VHF/UHF with X-50 vertical and Duoband 4-Element LPDA.