Date   

Re: jtalert not logging to dxkeeper

Dave AA6YQ
 

+ AA6YQ comments below

This was all working before a hard drive crash. After a restore, it seems that all is working well except for the jtalert logging to dxkeeper.

No alerts seem to show up on jtalert and when I log a QSO in FT8, it seems nothing gets passed to dxkeeper.

+ When you're using JT-Alert, DXLab applications are relatively passive: they receive directives - like "lookup callsign" and "log QSO" from JT-Alert, and then execute them.

+ Focus first on getting JT-Alert to correctly interoperate with WSJT-X. When that's working, then configure JT-Alert to correctly interoperate - one at a time -- with DXKeeper, DXView, SpotCollector, and Pathfidner.

73,

Dave, AA6YQ


Re: jtalert not logging to dxkeeper

neil_zampella
 

I would take a look at WSJT-X to make sure that the UDP settings are correct.   Make sure all the checkboxes are checked.

Neil, KN3ILZ

On 11/19/2021 8:10 PM, Kurt Cathcart wrote:
This was all working before a hard drive crash.  After a resore, it seems that all is working well except for the jtalert logging to dxkeeper.

No alerts seem to show up on jtalert and when I log a QSO in FT8, it seems nothing gets passed to dxkeeper.

I've been through the config guid multiple times. https://www.dxlabsuite.com/dxlabwiki/GettingStartedwithK1JTModesWithJTAlert

Suggestions?


jtalert not logging to dxkeeper

Kurt Cathcart
 

This was all working before a hard drive crash.  After a resore, it seems that all is working well except for the jtalert logging to dxkeeper.

No alerts seem to show up on jtalert and when I log a QSO in FT8, it seems nothing gets passed to dxkeeper.

I've been through the config guid multiple times. https://www.dxlabsuite.com/dxlabwiki/GettingStartedwithK1JTModesWithJTAlert

Suggestions?


Re: Apparently self spotting my call in SpotCollector?

Ed
 

Thanks Dave

I now understand.

Regards,   Ed


Re: Apparently self spotting my call in SpotCollector?

Dave AA6YQ
 

In the message below, I meant to say

"As has been pointed out in this thread, you can configure SpotCollector to ignore callsigns decoded by skimmers"

On the "Special Callsigns" tab of SpotCollector's Configuration window, check the "Discard spots from spotting station callsigns ending in -#"

73,

Dave, AA6YQ

-----Original Message-----
From: DXLab@groups.io [mailto:DXLab@groups.io] On Behalf Of Dave AA6YQ
Sent: Friday, November 19, 2021 8:45 PM
To: DXLab@groups.io
Subject: Re: [DXLab] Apparently self spotting my call in SpotCollector?

+ AA6YQ comments below

A few years back, 90% of the time i used CW. Have not used SpotCollector for quite awhile, playing with FT-8. So In my Spot Sources, I had one Host Address as: dxc.ve7cc.net port 7373

VE7CC is causing this to happen with enabled checked. When not enabled, problem goes away. Will see how it goes.

+ There is no "self-spotting" problem. There are stations that continuously scan bands for CW and digital mode signals, decode these signals, and submit them to some nodes of the DX Cluster network; these stations are referred to as "skimmers". If one of your spot sources is connected to a skimmer, then the callsigns decoded by that skimmer -- including yours when you transmit -- will appear in your Spot Database Display.

+ As has been pointed out in this thread, you can configure SpotCollector to callsigns decoded by skimmers. For more information, see "Using the Reverse Beacon Network with DXLab" in

http://www.dxlabsuite.com/RBN/

73,

Dave, AA6YQ


Re: Apparently self spotting my call in SpotCollector?

Dave AA6YQ
 

+ AA6YQ comments below

A few years back, 90% of the time i used CW. Have not used SpotCollector for quite awhile, playing with FT-8. So In my Spot Sources, I had one Host Address as: dxc.ve7cc.net port 7373

VE7CC is causing this to happen with enabled checked. When not enabled, problem goes away. Will see how it goes.

+ There is no "self-spotting" problem. There are stations that continuously scan bands for CW and digital mode signals, decode these signals, and submit them to some nodes of the DX Cluster network; these stations are referred to as "skimmers". If one of your spot sources is connected to a skimmer, then the callsigns decoded by that skimmer -- including yours when you transmit -- will appear in your Spot Database Display.

+ As has been pointed out in this thread, you can configure SpotCollector to callsigns decoded by skimmers. For more information, see "Using the Reverse Beacon Network with DXLab" in

http://www.dxlabsuite.com/RBN/

73,

Dave, AA6YQ


Re: Apparently self spotting my call in SpotCollector?

Ed
 

A few years back, 90% of the time i used CW.  Have not used SpotCollector  for quite awhile, playing with FT-8.
So
In my Spot Sources, I had one Host Address as: dxc.ve7cc.net  port 7373    

VE7CC is causing this to happen with enabled checked.  When not enabled, problem goes away.   Will see how it goes.

ED  WA6WGS


Re: Enter call in WinWarbler

Daniel W9DGI
 

Thanks very much Dave; I had searched the WinWarbler documentation -- it hadn't occurred to me to look for the answer in the SpotCollector instructions. DXLabs is a wonderfully capable set of programs!
73
Daniel W9DGI


Re: Apparently self spotting my call in SpotCollector?

ve3ki
 

RBN spots do not come from your skimmer (if you had one); they come from someone else's skimmer (the callsign before the -# tells you whose skimmer spotted you). There may be a command you can send to the cluster node to turn RBN spots off, but regardless, these are not self-spots - you have been spotted by someone else, namely the station whose callsign appears as the source.

73,
Rich VE3KI


On Fri, Nov 19, 2021 at 06:28 PM, Ed wrote:
Hi Joe,

I have no skimmer software.
Looking in SpotCollector Configuration only Dxpots.com is checked for Spot,  Likewise WSJT-x is not enabled.

Ed


Re: Apparently self spotting my call in SpotCollector?

Joe Subich, W4TV
 

Go to Spot Collector -> Config -> Special Callsigns and *CHECK* the
"Discard spots from spotting station callsigns ending in -#"

This will cause SpotCollector to ignore any spots from skimmer stations
(being relayed by DXspots.com).

Or ... go to the Window for DXSpots and type in SET/NOSKIMMER <enter>
this will tell DXSpots not to send you skimmer originated spots.

73,

... Joe, W4TV

On 2021-11-19 6:28 PM, Ed wrote:
Hi Joe,
I have no skimmer software.
Looking in SpotCollector Configuration only Dxpots.com is checked for Spot,  Likewise WSJT-x is not enabled.
Ed


Re: Apparently self spotting my call in SpotCollector?

Ed
 
Edited

This is happening of 20 Meters.  Every time.
Just switched to 15 meters and no spots from me.
Went back to 20 meters, and started up gain.
Each 20 meter one is from network    "VE1DX"


??????

Ed


Re: Apparently self spotting my call in SpotCollector?

Ed
 

Hi Joe,

I have no skimmer software.
Looking in SpotCollector Configuration only Dxpots.com is checked for Spot,  Likewise WSJT-x is not enabled.

Ed


Re: Apparently self spotting my call in SpotCollector?

Joe Subich, W4TV
 

Are you sure one of your spot sources does not include *skimmer* spots?

<CALL-#> generally indicates a skimmer node.

73,

... Joe, W4TV

On 2021-11-19 6:13 PM, Ed wrote:
Good afternoon,
I have not run SpotCollector for quite awhile.
I am only running DXLabs and WSJT-X software, to isolate my apparent *self spotting????*
I have looked everywhere for a setting that I might have missed, and ran searches to find an answer.
What is happening is illustrated :
WA6WGS on 14074.0 in FT8 at 11/19/2021 2244Z (K: United States) *with the source field containing a callnumber-#  .
* I'm sure somewhere I have seen this mentioned, but for the life of me can't find anything.
Can someone please direct me in the right direction to stop this from happening.  Its driving me nuts.
Regards,  ED WA6WGS


Re: Apparently self spotting my call in SpotCollector?

Ken Bandy, KJ9B
 

I see this as well, Ed.  I have attributed it to an automatic RBN spot.  It’s actually kind of helpful to see what propagation is like at the time.  I notice the callsign of the spotting station changes periodically, with the signal report changing accordingly.

 

73,

Ken, KJ9B

 

From: DXLab@groups.io <DXLab@groups.io> On Behalf Of Ed
Sent: Friday, November 19, 2021 6:14 PM
To: DXLab@groups.io
Subject: [DXLab] Apparently self spotting my call in SpotCollector?

 

[Edited Message Follows]

Good afternoon,
I have not run SpotCollector for quite awhile.  
I am only running DXLabs and WSJT-X software, to isolate my apparent self spotting????
I have looked everywhere for a setting that I might have missed, and ran searches to find an answer.

Every time I transmit this happens.......................................What is happening is illustrated :

WA6WGS on 14074.0 in FT8 at 11/19/2021 2244Z (K: United States)  with the source field containing a callnumber-#  .  

I'm sure somewhere I have seen this mentioned, but for the life of me can't find anything.
Can someone please direct me in the right direction to stop this from happening.  Its driving me nuts.
Regards,  ED WA6WGS


Apparently self spotting my call in SpotCollector?

Ed
 
Edited

Good afternoon,
I have not run SpotCollector for quite awhile.  
I am only running DXLabs and WSJT-X software, to isolate my apparent self spotting????
I have looked everywhere for a setting that I might have missed, and ran searches to find an answer.

Every time I transmit this happens.......................................What is happening is illustrated :

WA6WGS on 14074.0 in FT8 at 11/19/2021 2244Z (K: United States)  with the source field containing a callnumber-#  .  

I'm sure somewhere I have seen this mentioned, but for the life of me can't find anything.
Can someone please direct me in the right direction to stop this from happening.  Its driving me nuts.
Regards,  ED WA6WGS


Re: Enter call in WinWarbler

Joe Subich, W4TV
 

Spend some time with the help files for SpotCollector ...

SpotCollector -> Config -> General -> Action with Digital Mode
Application connected ... *CHECK* the CW box under "Service"

73,

... Joe, W4TV

On 2021-11-19 5:27 PM, Daniel W9DGI wrote:
I've just moved to DXLabs -- I'm really happy with it -- and everything seems to be working as it should, but digging into the manual I can't find a way to automate the call entry in WinWarbler when using CW. If I double-click on a spot in SpotCollector it inserts the call, etc., in the Capture window, ready to log, but it doesn't put the other station's call into the corresponding WinWarbler call box. When I use a WinWarbler function key to transmit a message that includes <callsign>, nothing is returned for <callsign> -- understandably, because there's nothing populating WinWarbler's call box. The other parts of the message are transmitted, but not the callsign.  I'm using a WinKeyer, if that's relevant. Is there a way to quickly populate WinWarbler's call entry box (similarly to clicking on the callsign in the RTTY receive pane) or do I have to type it in? I apologize if the answer is in the documentation, but I couldn't find it!
Thanks!
Daniel W9DGI


Re: Enter call in WinWarbler

Dave AA6YQ
 

+ AA6YQ comments below

I've just moved to DXLabs

+ Welcome to DXLab, Daniel!

I'm really happy with it -- and everything seems to be working as it should, but digging into the manual I can't find a way to automate the call entry in WinWarbler when using CW. If I double-click on a spot in SpotCollector it inserts the call, etc., in the Capture window, ready to log, but it doesn't put the other station's call into the corresponding WinWarbler call box. When I use a WinWarbler function key to transmit a message that includes <callsign>, nothing is returned for <callsign> -- understandably, because there's nothing populating WinWarbler's call box. The other parts of the message are transmitted, but not the callsign. I'm using a WinKeyer, if that's relevant. Is there a way to quickly populate WinWarbler's call entry box (similarly to clicking on the callsign in the RTTY receive pane) or do I have to type it in? I apologize if the answer is in the documentation, but I couldn't find it!

+ See this section of the Reference Documentation

https://www.dxlabsuite.com/spotcollector/Help/ConfigurationGeneral.htm#Phone%20Modes%20Panel

+ Step-by-step instructions are here:

https://www.dxlabsuite.com/dxlabwiki/WinWarblerActivationOnCWSSBSpotDatabaseEntryDoubleClick

73,

Dave, AA6YQ


Re: Can DX Labs run on Windows 11 on ARM

Dave AA6YQ
 

# more AA6YQ comments below

+ You should connect "SDR Console" to Commander's Secondary CAT
Port, as shown in
>
> https://www.dxlabsuite.com/dxlabwiki/SDRConsoleCWSkimmerConfiguration

Dave, what he's saying is that he is using Eltima's virtual ports where
the diagram you reference shows "com0com".

# If that's the case, there is no problem.

73,

Dave, AA6YQ


Enter call in WinWarbler

Daniel W9DGI
 

I've just moved to DXLabs -- I'm really happy with it -- and everything seems to be working as it should, but digging into the manual I can't find a way to automate the call entry in WinWarbler when using CW. If I double-click on a spot in SpotCollector it inserts the call, etc., in the Capture window, ready to log, but it doesn't put the other station's call into the corresponding WinWarbler call box. When I use a WinWarbler function key to transmit a message that includes <callsign>, nothing is returned for <callsign> -- understandably, because there's nothing populating WinWarbler's call box. The other parts of the message are transmitted, but not the callsign.  I'm using a WinKeyer, if that's relevant. Is there a way to quickly populate WinWarbler's call entry box (similarly to clicking on the callsign in the RTTY receive pane) or do I have to type it in? I apologize if the answer is in the documentation, but I couldn't find it! 
Thanks!
Daniel W9DGI


Re: Can DX Labs run on Windows 11 on ARM

Joe Subich, W4TV
 

On 2021-11-19 4:16 PM, Dave AA6YQ wrote:

+ You should connect "SDR Console" to Commander's Secondary CAT
Port, as shown in

https://www.dxlabsuite.com/dxlabwiki/SDRConsoleCWSkimmerConfiguration
Dave, what he's saying is that he is using Eltima's virtual ports where
the diagram you reference shows "com0com".

I also use Eltima ports (just a simple port pair) in that application
(in my case that are created by my microHAM software).

73,

... Joe, W4TV


On 2021-11-19 4:16 PM, Dave AA6YQ wrote:
+ AA6YQ comments below
Just using the virtual com port for communication between DX Commander and SDR Console.
+ That's not reliable. Commander is not designed to tolerate another transceiver control application sending CAT commands to your transceiver behind its back.
+ You should connect "SDR Console" to Commander's Secondary CAT Port, as shown in
https://www.dxlabsuite.com/dxlabwiki/SDRConsoleCWSkimmerConfiguration
73,
Dave, AA6YQ

4501 - 4520 of 208968