Using IRC as spot source


David Reed
 

I am trying to use IRC as a spot source in SpotCollector. I have tried it with and without specifying Username and First Name.

No spots show either way (Telnet DXClusters work fine, but I have them disabled while I am trying to get this source working.

So, if it is up and working for you, what else do I need to do to get it working for me?

--
Thanks & 73 de Dave, W5SV


Dave AA6YQ
 

+ AA6YQ comments below

I am trying to use IRC as a spot source in SpotCollector. I have tried it with and without specifying Username and First Name.

No spots show either way (Telnet DXClusters work fine, but I have them disabled while I am trying to get this source working.

So, if it is up and working for you, what else do I need to do to get it working for me?

+ In the IRC panel on the "Spot Sources" tab of SpotCollector's Configuration window:

Host address: US.WorldIRC.Org

Channel: CQDX

Caption: CQDX

Username: AA6YQ

First Name: AA6YQ

Robot: DXS

+ This spot source takes several minutes to connect.

73,

Dave, AA6YQ


David Reed
 

Thanks Dave; mine is configured exactly the same except for our Username and First Name...

I do now see a connected message in green, repeated every 2 minutes, but still no spots from 1731 - 1839, so after  over an hour.

I guess my question is "is there any activity on this source, or am I just missing it?",

Thanks again Dave!

73 de Dave, W5SV

On 30-01-23 06:58, Dave AA6YQ wrote:
+ AA6YQ comments below

I am trying to use IRC as a spot source in SpotCollector. I have tried it with and without specifying Username and First Name.

No spots show either way (Telnet DXClusters work fine, but I have them disabled while I am trying to get this source working.

So, if it is up and working for you, what else do I need to do to get it working for me?

+ In the IRC panel on the "Spot Sources" tab of SpotCollector's Configuration window:

Host address: US.WorldIRC.Org

Channel: CQDX

Caption: CQDX

Username: AA6YQ

First Name: AA6YQ

Robot: DXS

+ This spot source takes several minutes to connect.

73,

Dave, AA6YQ






Dave AA6YQ
 

+ AA6YQ comments below
Thanks Dave; mine is configured exactly the same except for our Username and First Name...

I do now see a connected message in green, repeated every 2 minutes, but still no spots from 1731 - 1839, so after  over an hour.

I guess my question is "is there any activity on this source, or am I just missing it?",

+ When I filter the "Spot Database Display" with the expression

Network='CQDX'

+ I see many Spot Database Enrieds.

+ As noted in

https://www.dxlabsuite.com/spotcollector/Help/SourceConnection.htm#Connecting%20to%20the%20#CQDX%20IRC%20channel

"Make sure your firewall and anti-malware applications do not block TCP port 6667."

      73,

            Dave, AA6YQ

 

 

 

 


David Reed
 

That was it; that port was not getting through! All is well!

Heartfelt thanks, once again!

73 de Dave, W5SV
On 30-01-23 21:34, Dave AA6YQ wrote:

+ AA6YQ comments below
Thanks Dave; mine is configured exactly the same except for our Username and First Name...

I do now see a connected message in green, repeated every 2 minutes, but still no spots from 1731 - 1839, so after  over an hour.

I guess my question is "is there any activity on this source, or am I just missing it?",

+ When I filter the "Spot Database Display" with the expression

Network='CQDX'

+ I see many Spot Database Enrieds.

+ As noted in

https://www.dxlabsuite.com/spotcollector/Help/SourceConnection.htm#Connecting%20to%20the%20#CQDX%20IRC%20channel

"Make sure your firewall and anti-malware applications do not block TCP port 6667."

      73,

            Dave, AA6YQ

 

 

 

 


Steve, W7WM
 

I have apparently messed up a setting in SpotCollector. Previously, I have had CQDX IRC receiving spots from DXSummit. Yesterday, I stopped receiving spots. All of the Telnet DX clusters are behaving normally.

I am connected and all that I am receiving are 'xxx has joined', and 'yyy has quit' messages. The /CTCP DXS SH/DX command returns spots as expected.

Any suggestions on what I "changed"?

Thanks,

-Steve, W7WM

Connected to US.WorldIRC.Org @ 2/5/2023 2201
*** Looking up your hostname
*** Checking Ident
*** Found your hostname
:Welcome to the WorldIRC IRC Network, W7WM
:Your host is Newark.NJ.US.WorldIRC.Org, running version u2.10.11.WI_asuka
:This server was created Tue Jun 14 2005 at 23:07:35 BST
Newark.NJ.US.WorldIRC.Org u2.10.11.WI_asuka dioswkgxXInR biklmnopstvrDcCNu bklov
WHOX WALLCHOPS WALLVOICES USERIP CPRIVMSG CNOTICE SILENCE=15 MODES=6 MAXCHANNELS=15 MAXBANS=45 NICKLEN=20 MAXNICKLEN=20 :are supported by this server
TOPICLEN=160 AWAYLEN=160 KICKLEN=160 CHANTYPES=#& PREFIX=(ov)@+ CHANMODES=b,k,l,imnpstrDdcCNu CASEMAPPING=rfc1459 NETWORK=WorldIRC :are supported by this server
:There are 3 users and 184 invisible on 3 servers
3 :operator(s) online
7 :unknown connection(s)
22 :channels formed
:I have 182 clients and 2 servers
Highest connection count: 248 (246 clients)
:- Newark.NJ.US.WorldIRC.Org Message of the Day -
: Type /MOTD to read the AUP before continuing using this service.
:The message of the day was last changed: 2010-7-7 12:57
:End of /MOTD command.
on 1 ca 1(5) ft 10(10) tr
W7WM has joined @ 2/5/2023 2201Z
#cqdx : 04,00 Amateur Radio DXing - visit http://dx.qsl.net for info
#cqdx N6RT 1673374004
@ #cqdx :W7WM KX7DX KE7FHI W4TV WD8JJA K3IE VK3EW NZ4N W8ZF N8WCR-2 NA6JD KC7DC SQ9HT-DPcP W9DGI WA2ILB K6OJ WS7L W2EQ W2JU LA1DBA WB4OSS-2 KI0KB DL4SDW N2DPF N0PB DL5NO W9PDS AK4NG W9RF VK3BDX AE9LL W0MN WW9P AB8M WA7AMJ W4UM W4RJF ON7KR K7UT K5JRW K7JNX W6BXQ DL9GT35 W7WES KM8AM W9AJ N9NY K1KD WA8OJR AJ6T N4BAA KD4ADC K2UF SM7IUN K8UMF N3SL IZ2AMW @dxs
.
.
@ #cqdx :hive-mind odroid mquin W4DXA _2e1gw-vp N8QQ @X
#cqdx :End of /NAMES list.
NA6JD has quit
LX2KA has joined


Dave AA6YQ
 

+ AA6YQ comments below

I have apparently messed up a setting in SpotCollector. Previously, I have had CQDX IRC receiving spots from DXSummit. Yesterday, I stopped receiving spots. All of the Telnet DX clusters are behaving normally.

I am connected and all that I am receiving are 'xxx has joined', and 'yyy has quit' messages. The /CTCP DXS SH/DX command returns spots as expected.

Any suggestions on what I "changed"?

+ What leads you to conclude that you aren't receiving spots from DX Summit? SpotCollector does not show DX Summit spots in its CQDX "Spot Source" window.

+ What happens when you filter the "Spot Database Display" with this SQL expression?

network='cqdx'

73,

Dave, AA6YQ


Steve, W7WM
 

IRC has allowed me to connect again. 

No spots are coming into the CQDX window or the Spot Collector Display window.

Here is a snapshot of what is in my CQDX window:
.
.

SolarMonitor hive-mind odroid mquin _2e1gw-vp N8QQ @X
#cqdx :End of /NAMES list.
W4VIC has joined
K6PBF has joined
KE7FHI has quit
NO0B has joined
.
.
.
K5JRW has quit
WY9V has quit
WA2ILB has quit
<dxs> 07 Feb IK5PWJ-6 (0015Z) : * DXCLUSTER IK5PWJ-6: telnet://ik5pwj-6.dyndns.org:8000
NZ4N has joined
W8ZF has joined
WA2ILB has joined
.
.
.
 


Dave AA6YQ
 

+ AA6YQ comments below
IRC has allowed me to connect again. 

No spots are coming into the CQDX window or the Spot Collector Display window.

+ As stated in my previous post, SpotCollector does not display incoming spots in the CQDX window.

+ Please filter the "Spot Database Display" with the SQL expression I posted,. How many Spot Database Entries appear?

     73,

             Dave, AA6YQ


David Reed
 

Steve,

I am suffering the same issues... so far no luck getting to the bottom of it.

If I do I will post here and try to remember to copy you on it.

73 de Dave, W5SV
On 07-02-23 00:23, Steve, W7WM wrote:

IRC has allowed me to connect again. 

No spots are coming into the CQDX window or the Spot Collector Display window.

Here is a snapshot of what is in my CQDX window:
.
.

SolarMonitor hive-mind odroid mquin _2e1gw-vp N8QQ @X
#cqdx :End of /NAMES list.
W4VIC has joined
K6PBF has joined
KE7FHI has quit
NO0B has joined
.
.
.
K5JRW has quit
WY9V has quit
WA2ILB has quit
<dxs> 07 Feb IK5PWJ-6 (0015Z) : * DXCLUSTER IK5PWJ-6: telnet://ik5pwj-6.dyndns.org:8000
NZ4N has joined
W8ZF has joined
WA2ILB has joined
.
.
.
 


Steve, W7WM
 

Sorry I missed the comment about the window not displaying spots.

I have set the filter (as shown in SQLfilters.txt) and no spots are appearing in the SpotCollector Display window in the last 10 minutes.


Dave AA6YQ
 

+ AA6YQ comments below

Sorry I missed the comment about the window not displaying spots.

I have set the filter (as shown in SQLfilters.txt) and no spots are appearing in the SpotCollector Display window in the last 10 minutes.

+ Please paste

network='CQDX'

+ into the textbox in the Filter panel at the bottom of SpotCollector's Main window, and then depress the CTRL key while striking the S key.

+ How many Entries appear now appear in the Spot Database Display? What is the "First" time for the most recent Entry?

73,

Dave, AA6YQ


Steve, W7WM
 
Edited

On Mon, Feb 6, 2023 at 06:18 PM, Dave AA6YQ wrote:
network='CQDX'
I think I have some interesting information. I was having trouble connecting to CQDX. I had turned off all of my Telnet sources, leaving only IRC for troubleshooting. Reliably, IRC would timeout and not connect. Enabling one of the Telnet sources caused CQDX to connect. I was able to monitor this behavior with mIRC.

When IRC was connected (with one Telnet source enabled), and the SQL expression network='CQDX' spots began appearing in the display window - all with network parameters marked as CQDX.

Also, monitoring CQDX with mIRC, I see MANY stations join and then quit (ping timeout), over and over again. I wonder if CQDX is getting overloaded. I am not an expert, but it looks that way.

I don't know what that all means, but with one Telnet enabled and CQDX enabled, things seem to work - as evidenced by spots coming in assigned to network CQDX.

-Steve, W7WM

BTW, what prompted me to use mIRC was the fact I could not connect, in order to collect the information you requested.


Dave AA6YQ
 

+ AA6YQ comments below
I think I have some interesting information. I was having trouble connecting to CQDX. I had turned off all of my Telnet sources, leaving only IRC for troubleshooting. Reliably, IRC would timeout and not connect. Enabling one of the Telnet sources caused CQDX to connect. I was able to monitor this behavior with mIRC.

When IRC was connected (with one Telnet source enabled), and the SQL expression network='CQDX' spots began appearing in the display window - all with network parameters marked as CQDX.

Also, monitoring CQDX with mIRC, I see MANY stations join and then quit (ping timeout), over and over again. I wonder if CQDX is getting overloaded. I am not an expert, but it looks that way.

I don't know what that all means, but with one Telnet enabled and CQDX enabled, things seem to work - as evidenced by spots coming in assigned to network CQDX.

-Steve, W7WM

BTW, what prompted me to use mIRC was the fact I could not connect, in order to collect the information you requested.

+ Are you reporting that SpotCollector could not connect to CQDX until your first connected with MIRC?

+ What host address have you specified for CQDX on the Spot Sources tab of SpotCollector's Configuration window?

+ Did you confirm that IP Port 6667 is "open", as suggested in the 5th paragraph of

https://www.dxlabsuite.com/spotcollector/Help/SourceConnection.htm#Connecting%20to%20the%20#CQDX%20IRC%20channel

?

      73,

             Dave, AA6YQ

 

 

 


David Reed
 

Steve, I am interested and have been following this thread...

Like you, I have found that odd anomaly of requiring a TELNET source to be connected to get IRC to show connection and produce spots...

I am curious,how can you tell where a specific spot came from?

I ask because I am interested in determining which sources are most productive for my purposes.

Thanks & 73 de Dave, W5SV
On 07-02-23 03:01, Steve, W7WM wrote:

On Mon, Feb 6, 2023 at 06:18 PM, Dave AA6YQ wrote:
network='CQDX'
I think I have some interesting information. I was having trouble connecting to CQDX. I had turned off all of my Telnet sources, leaving only IRC for troubleshooting. Reliably, IRC would timeout and not connect. Enabling one of the Telnet sources caused CQDX to connect. I was able to monitor this behavior with mIRC.

When IRC was connected (with one Telnet source enabled), and the SQL expression network='CQDX' spots began appearing in the display window - all with network parameters marked as CQDX.

Also, monitoring CQDX with mIRC, I see MANY stations join and then quit (ping timeout), over and over again. I wonder if CQDX is getting overloaded. I am not an expert, but it looks that way.

I don't know what that all means, but with one Telnet enabled and CQDX enabled, things seem to work - as evidenced by spots coming in assigned to network CQDX.

-Steve, W7WM


Dave AA6YQ
 

+ AA6YQ comments below

I am curious, how can you tell where a specific spot came from?

I ask because I am interested in determining which sources are most productive for my purposes.

+ A Spot Database Entry's Network field records the caption of the spot source from which it was created or most recently updated.

73,

Dave, AA6YQ


David Reed
 

I must be overlooking the Spot Database Entry's Network field somehow; I don't see it anywhere on the main display window even when I scroll ti the right to examine all the fields displayed.

Is there some control I am missing that I have set incorrectly; where would I see it?

Sorry for such elementary question...

Thanks & 73 de Dave, W5SV

On 07-02-23 05:48, Dave AA6YQ wrote:
+ AA6YQ comments below

I am curious, how can you tell where a specific spot came from?

I ask because I am interested in determining which sources are most productive for my purposes.

+ A Spot Database Entry's Network field records the caption of the spot source from which it was created or most recently updated.

73,

Dave, AA6YQ


Steve, W7WM
 

I have responded to your questions in line.
I have also replied with a way to recreate the issue that I am seeing and that Dave, W5SV is as well.

+ Are you reporting that SpotCollector could not connect to CQDX until your first connected with MIRC?

**  No. MIRC has nothing to do with the situation except that it was a tool to help see what was going on. Only a diagnostic tool

+ What host address have you specified for CQDX on the Spot Sources tab of SpotCollector's Configuration window?

**    US.WorldIRC.Org Channel = CQDX

+ Did you confirm that IP Port 6667 is "open", as suggested in the 5th paragraph of

https://www.dxlabsuite.com/spotcollector/Help/SourceConnection.htm#Connecting%20to%20the%20#CQDX%20IRC%20channel

**  Yes


Steve, W7WM
 

To see the situation that I am seeing:
  • connect to a single Telnet DXCluster
  • connect to IRC CQDX
  • disconnect from the Telnet DXCluster
    • IRC CQDX will timeout and eventually Disconnect
  • reconnect to a single Telnet DXCluster
  • IRC CQDX will reconnect and resume sending Spots

A similar situation occurs if one tries to start IRC CQDX with no Telnet DXClusters enabled. CQDX times out and Disconnects.

MIRC has nothing to do with any of this. I only used it as a diagnostic tool.

The obvious solution is: 'if it hurts', don't do it'.

-Steve, W7WM


Steve, W7WM
 

Dave, W5SV -

  • Go to the Spot Database Display tab on Spot Collectors config page.
  • Go to the last entry in the list of displayed fields
  • Select the 'network' parameter

You may want to move the new field to the left so you can view it without inducing auto-scroll.

-Steve, W7WM