The bandmap is now filled with spots from the DX-cluster. I think it would be very cool to have the bandmap filled with RBN spots. It would be a great operating aid, like looking for a clear spot. Of course filtering aids would be very helpful, like the RBN monitor is using now.
Regards,
Joop PG4I
It can generate big traffic.
Some Dx clusters , e.g. klub.sp2put.pl:7300 (google for others), already has option to include spots from RBN, just use commands set/skimmer to on and unset/skimmer to off. Further filtering is easy to do with cqrlog. Default set is on, but I am not sure here, you should check it.
Thanks Slav, was not aware of that. Will check it out!
I know that RUMLOG (Mac OS X) has a bandmap where you can choose to fill it with either cluster spots or RBN info.
73 de Joop PG4I
The default seems to be ON for SP2PUT, but the bandmap does not get filled in CQRLOG. Maybe it is the format of the incoming RBN data? I will check if there are other DX clusters available which use RBN.
Very strange. The bandmap does not work at all. It worked before... No idea what is going on...
I don't now whats going wrong. My bandmap is filled with both spots, from RBN and dx cluster. I wish but can't help you. Is not too much data coming to bandmap window?
For some reason (I needed to do a reboot, could be it), now it is working. Thanks Slav! Very cool!
Well, back to zero. The bandmap stopped working again... Nothing coming in, even though I am logged in to the DX cluster. Does anyone have an idea how to debug this?
Hi!
I just made a quick test by connecting telnet.reversebeacon.net:7000 and it seems that bandmap is filling up with rather high speed.
I think the only way to start debugging is to forward debug text to file.
cqrlog debug=1 > /tmp/debug.txt
Then write up some call seen, but not went to bandmap and try to dig them out from debug.txt after cqrlog is stopped.
From that point on examination of source is needed to find points that have produced debug lines under examination.
--
Saku
OH1KH