Recently when I call CQ my spots are showing up on the DX cluster in RBN and greyline. I have not changed any settings and I would rather not see my spots in the DX cluster window. Have I missed a new feature?
73, Bill NZ0T
Fri, 2021-02-19 17:18
#1
My spots on DX cluster
This is an example of what I am seeing on my DX Cluster:
DX de KM3T-#: 3548.5 NZ0T CW 15 dB 20 WPM CQ 0055Z United States
DX de KO7SS-#: 3548.5 NZ0T CW 19 dB 20 WPM CQ 0055Z United States
DX de W8WWV-#: 3548.5 NZ0T CW 25 dB 20 WPM CQ 0055Z United States
DX de K9LC-#: 3548.5 NZ0T CW 14 dB 20 WPM CQ 0055Z United States
DX de W2AXR-#: 3548.5 NZ0T CW 23 dB 20 WPM CQ 0055Z United States
DX de WE9V-#: 3548.5 NZ0T CW 25 dB 20 WPM CQ 0055Z United States
These spots are in among the DX spots I usually see. I see this happening with both clusters I use. Again, I have not made any changes to my settings.
You are connected to RBN, not to DXCluster.
At DXCluster window press button "Select". Then opens window "choose dxcluster". I think you have reversebeacon now selected. Select another DXCluster or add a new one if you favorite is not in the list.
--
Saku
OH1KH
Hi Saku,
I have my regular cluster selected, there is no reversebeacon selection even listed. I have not changed any settings - this started happening on it's own. I Have noticed though that since the upgrade to v 2.5.2 hat even though I have the grayline window selected. Maybe a setting there has changed?
When cqrlog is running look at ~/.config/cqrlog folder. You should find there file named Xcqrlog.cfg where X is the log number currently open.
Open that with text editor and find section
[DXCluster]
There should be lines that show what telnet dxcluster is connected:
Your log configuration may be broken. Fix all needed then close cqrlog. It should update configuration.
Desc=oh1af
Addr=oh1af.dy.fi
Port=8000
User=OH1KH
Are they ok (as your own values)?
Try to switch to another cluster, try connect and then back you previous one. Does that help?
--
Saku
OH1KH
I have feeling, that your clusters have taken skimmer options in use..
Try command set/noskimmer at your cluster... This is only a hount...
<p>Jarmo</p>
It all looks OK to me. Here is what I see:
[DXCluster]
NewCountry=255
NewBand=0
NewMode=0
NeedQSL=0
Show2190M=0
Show630M=0
Show160M=1
Show80M=1
Show60M=1
Show40M=1
Show30M=1
Show20M=1
Show17M=1
Show15M=1
Show12M=1
Show10M=1
Show6M=1
Show4M=0
Show2M=0
Show125M=0
Show70CM=0
Show33CM=0
Show23CM=0
Show13CM=0
Show9CM=0
Show6CM=0
Show3CM=0
Show125CM=0
Show6MM=0
Show4MM=0
CW=1
SSB=1
NotShow=
ConAfterRun=1
ShowDxcCountry=1
AlertCmd=
StartCmd=
Tab=1
Desc=dxspots
Addr=dxspots.com
Port=23
User=nz0t
Pass=
Font=DejaVu Sans Mono
FontSize=10
AlertEnabled=1
AlertRegExp=0
Hi Bill,
correctly reconfigure the telnet port of dxspots.com which is not 23 but 7300.
--
Giuseppe
IKØDWJ
Sorry Bill.
I did some tests with the dxspots cluster. Although the dxspots.com site specifies to use the telnet port 7300, the standard port 23 is also open. So your configuration seems correct.
--
Giuseppe
IKØDWJ
Yes Giuseppe - I have been using dxspots for years and either port is OK.
73, Bill NZ0T
HI !
Connect manually to telnet dxspots.com 7300 and give command
set/noskimmer (turns off Skimmer spots)
If you have skimmer spots on your spot prompt include hash (#), if not spots are "ordinary" format.
--
Saku
OH1KH
Hi Saku,
I disabled skimmer spots and that did not work. I also checked my configuration in VE7CC and it is OK too.
OK - fixed it! I entered command "set/noown" which turns off spots for my call. I have no idea how it got turned on.
Thanks for all the help everyone.
73, Bill NZ0T