Hi Petr,
the RBN monitor is a great feature! Just found a bug or two while using it ...
When I try to change entries in the filter criteria window of the RBN monitor, CQRLOG crashes. When it shows me the 'Access Violation' window and I can keep on using CQRLOG without any problems, but sometimes it crashes completely without any notification. It seems to be a problem whether the RBN monitor is connected to the RBN (no crash) or if its not connected (crashes).
Another thing:
I started a DXCluster connection and then the RBN monitor. After some seconds, the DXCluster window got somehow messed up. See this:
http://5tx.de/dev/null/DXCluster.png
Happens with normal CLX and RBN nodes.
And:
When I try to reproduce the above thing and take an RBN node for the DXCluster, the RBN monitor simply doesn't work.
step 1:
connect DXCluster to cluster.dl9gtb.de:8000
Works. Spots are coming, bandmap gets full.
step 2:
connect RBN Monitor to n8nie.us:7373
Works as I can see in the terminal with --debug option, but no spots are shown in the RBN Monitor. And DXCluster windows gets messed up again after a minute or so.
Is there a way for the RBN Monitor to use an existing CLX+RBN connection of the DXCluster window? This would be great, as you don't have to open two RBN connections at the same time.
73
Ulf DK5TX
Just noticed that the DXCluster window gets messup up also, when connected to some CLX+RBN node, while RBN monitor not in use at all....
73
Ulf DK5TX
Double-click on the RBN monitor window crash
http://imgur.com/gEXIm5g
http://imgur.com/OFmnW4t
This is strange. I've been using RBN monitor for two months or more and never had this problem. Right now started CQRLOG, connected to RBN, double clicked to a spot and it works :(.
Could you take a screenshot before the error message appeard? Thank you!
73 Petr
--
http://HamQTH.com/ok2cqr
https://ok2cqr.com
the RBN monitor does not display spots
http://imgur.com/ECtyEv9
http://imgur.com/spZuILz
What RBN cluster are you using?
--
http://HamQTH.com/ok2cqr
https://ok2cqr.com
Hi Petr,
it seems my problems are somehow related to one of the used RBN nodes. In my case it's DL9GTB (cluster.dl9gtb.de:8000) which I use in the DXCluster windows and my best guess is, CQRLOGs parser it being confused by "corrupted" lines being sent by DL9GTB. Maybe by the word "BEACON", which sometimes comes instead of "CQ" after the WPM? Example:
DX de WZ7I-#: 14029.9 CN2AA CW 41 dB 36 WPM CQ 1846Z
DX de KO7SS-#: 21016.9 W9SN CW 15 dB 31 WPM CQ 1846Z
DX de WZ7I-#: 28203.1 K4MTP/B CW 21 dB 18 WPM BEACON 1846Z
Now I'm using arcluster.reversebeacon.net for the DXCluster and telnet.reversebeacon.net for the RBN Monitor and everything seems to work fine. At least for the past 15 minutes.
I understand that these two telnet nodes are not for end users, but the distributing nodes. Unfortunately most of the distributing nodes are not available right now (VE7CC, AB5K) probably due to CQ WW CW Contest and high amounts of spots.
Question:
Is there any possibility, that the RBN monitor and the DXCluster window share the same RBN connection? Like using only VE7CC.net, which provides normal spots (entered by hand) and RBN spots at the same time. So I don't have to be connected to two nodes at once.
73
Ulf DK5TX
It seems the massive amounts of both connections (during CQWWCW) leads to a crash of the DXCluster windows. It just stopped showing spots, although they're received by the telnet node (which I can see in the terminal with --debug option).
I know CQRLOG must not handle this massive amounts of spots. It's just for your information.
73
Ulf DK5TX
http://imgur.com/mKoo3eQ
Try current test build, please.
http://cqrlog.com/node/1535
--
http://HamQTH.com/ok2cqr
https://ok2cqr.com
Hi Petr,
I've loaded the tar.gz down and exctracted it to /usr/bin/ after renaming original 'cqrlog' to 'cqrlog_origin', because from the home directory it started with an error message (greymap image could not be found) and after selecting my logbook database it simply crashed.
But copying to /usr/bin and starting with debugging from terminal works fine. I'm right now connected to ve7cc.net:23 in the DXCluster windows (as DK5TX) and to the same CLX+RBN in the RBN monitor (as DK5TX-1). This seems to work fine. I let it run an hour or two, to see if it is stable.
Tnx & 73!
Ulf DK5TX
Runs now for 2 hrs 30 mins without any problems. Seems to be fine.
Let me know, if I should check other things or newer versions.
73
Ulf DK5TX