FT8 and Spotcollector issue


Ted Boerkamp
 

Hello all…..I just managed to get FT8 running here with WSJT and I have linked it to DXKeeper through Spotcollector

to transfer my logged contacts from WSJT to DXKeeper automatically. However, I am now seeing endless FT8 spots

being posted with me VE3SS as the spotter. Why is this happening? Do I have something turned on that I don’t need

to have on??? This cant be normal as I see only a few other spotter calls and the majority are me.

Any help is appreciated. I do have the automatic transfer of contacts working between the two programs but

these endless posted spots are worrying me.

Thanks 73 Ted VE3SS

 


Virus-free. www.avg.com


Dave AA6YQ
 

+ AA6YQ comments below

Hello all…..I just managed to get FT8 running here with WSJT and I have linked it to DXKeeper through Spotcollector

to transfer my logged contacts from WSJT to DXKeeper automatically. However, I am now seeing endless FT8 spots

being posted with me VE3SS as the spotter. Why is this happening? Do I have something turned on that I don’t need

to have on??? This cant be normal as I see only a few other spotter calls and the majority are me.

Any help is appreciated. I do have the automatic transfer of contacts working between the two programs but

these endless posted spots are worrying me

+ With WSJT-X directly interoperating with DXlab, any station decoded by your instance of WSJT-X will be conveyed to SpotCollector as a "local spot" with your callsign as the source.. Like local spots you generate by clicking the Local button in SpotCollector's "Outgoing Spots" panel, the information is incorporated in the Spot Database, but is not sent to the DX Cluster network.

+ Take a look at Network and Source columns in the first screenshot in

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

+ and the text that immediately precedes it.

         73,

              Dave, AA6YQ


dl8le
 

I like this function, i.e. the interoperation between WSJT-X and Spotcollector and those which are possible by this interoperation, e.g. direct logging into DXKeeper, DXView information populated etc. There is only one feature missing which I would appreciate very much to see if ever possible: in Spotcollector's Config Window Spot Sources - WSJT-X there should be a function to be enabled by checking a box "DXKeeper Lookup" as exists already for "Callbook Lookup" to see if a station shown as local spot has been worked before or not.

I don't ask for mode (if this would be limited to the modes of WSJT-X would be ok for me) or band or whatever else, just to see if worked at all. Reason for this is that the FTx activity has increased significantly over time and the bands are pretty crowded already. Therefore it is hard to remember it the station has been worked already or not, even on the same day.

My present work around is to double click on a call in the band activity window (then the call and available DXKeeper information will pop up) and after a look at this information I iniate the call in FTx. This means I don't use the settings "Double click on call sets TX enable" which is quite inconvenient and takes time, not so nice. Another way using N1MM together with the DXLab gateway is also not very convenient but possible of course.  To update the ADIF file in WSJT-X all the time (I did this already) and using the information provided by WSJT-X's colour code is possible as well, therefore my enhancement proposal is not a "must have" but more a "nice to have", but it would help significantly. Please note that I don't ask for a contest logger function, just a support for working other stations and to avoid duplicate calls on crowded bands. Missing calls for e.g. DXCC are already displayed in red, i.e. the information transfer from DXKeeper (via Spotcollector?) to WSJT-X works already without any problem.

Best solution would be that I would miss one settings in DXLab which already exists ...

73

Juergen, DL8LE


Dave AA6YQ
 

+ AA6YQ comments below

I like this function, i.e. the interoperation between WSJT-X and Spotcollector and those which are possible by this interoperation, e.g. direct logging into DXKeeper, DXView information populated etc. There is only one feature missing which I would appreciate very much to see if ever possible: in Spotcollector's Config Window Spot Sources - WSJT-X there should be a function to be enabled by checking a box "DXKeeper Lookup" as exists already for "Callbook Lookup" to see if a station shown as local spot has been worked before or not.

+ That's the function of the Lookup checkbox in the WSJT-X panel on the "Spot Sources" tab of SpotCollector's Configuration window.

snip<
My present work around is to double click on a call in the band activity window (then the call and available DXKeeper information will pop up) and after a look at this information I iniate the call in FTx. This means I don't use the settings "Double click on call sets TX enable" which is quite inconvenient and takes time, not so nice.

+ WSJT-X does not provide any other way of conveying a "decoded callsign of interest" to another application. With the WSJT-X "Double click on call sets TX enable" option disabled, it takes only one mouse click on the WSJT-X Main window to click the "Enable TX" button if you're interested in working the station after seeing the DXKeeper lookup.

73,

Dave, AA6YQ


dl8le
 


+ WSJT-X does not provide any other way of conveying a "decoded callsign of interest" to another application. With the WSJT-X "Double click on call sets TX enable" option disabled, it takes only one mouse click on the WSJT-X Main window to click the "Enable TX" button if you're interested in working the station after seeing the DXKeeper lookup.
 
Comment DL8LE:

++ It's only 1 mouse click if there is only one call sign in the band activity window, but there are many double clicks plus the additional mouse click if there are many stations for which you are not sure if you worked them already or not. Tonight there are more than 50 stations decoded on 14.074 in FT8 in one time slot and more than 45 on 18.100 in FT8, just to give you an example. Therefore I still consider my assessment of "not convenient" is very valid.

On the other hand all decoded calls are listed as local spots more or less immediately in Spotcollector. Therefore I wonder if there is not any chance to look not only in the LotW- and eQSL-Member database but also in the log database and to have a certain color code in Spotcollector for those which are already in that database as worked.

As mentioned before: this is not any replacement of a contest logger such as N1MM or similar, it is just significantly improving the operating of FTx in WSJT-X (and this is different than working CW, SSB or RTTY in which I never felt the need of such a function outside of a contest and I am very happy in using DXLab a very long time already).

Anyway, thanks for looking into this topic.

73

Juergen, DL8LE


Joe Subich, W4TV
 

If you want a display of previously worked stations, look into
JT-Alert.

73,

... Joe, W4TV

On 2022-08-04 6:31 PM, dl8le wrote:
+ WSJT-X does not provide any other way of conveying a "decoded callsign of interest" to another application. With the WSJT-X "Double click on call sets TX enable" option disabled, it takes only one mouse click on the WSJT-X Main window to click the "Enable TX" button if you're interested in working the station after seeing the DXKeeper lookup.
Comment DL8LE:
++ It's only 1 mouse click if there is only one call sign in the band activity window, but there are many double clicks plus the additional mouse click if there are many stations for which you are not sure if you worked them already or not. Tonight there are more than 50 stations decoded on 14.074 in FT8 in one time slot and more than 45 on 18.100 in FT8, just to give you an example. Therefore I still consider my assessment of "not convenient" is very valid.
On the other hand all decoded calls are listed as local spots more or less immediately in Spotcollector. Therefore I wonder if there is not any chance to look not only in the LotW- and eQSL-Member database but also in the log database and to have a certain color code in Spotcollector for those which are already in that database as worked.
As mentioned before: this is not any replacement of a contest logger such as N1MM or similar, it is just significantly improving the operating of FTx in WSJT-X (and this is different than working CW, SSB or RTTY in which I never felt the need of such a function outside of a contest and I am very happy in using DXLab a very long time already).
Anyway, thanks for looking into this topic.
73
Juergen, DL8LE


Dave AA6YQ
 

# AA6YQ comments below

+ WSJT-X does not provide any other way of conveying a "decoded callsign of interest" to another application. With the WSJT-X "Double click on call sets TX enable" option disabled, it takes only one mouse click on the WSJT-X Main window to click the "Enable TX" button if you're interested in working the station after seeing the DXKeeper lookup.

Comment DL8LE:

++ It's only 1 mouse click if there is only one call sign in the band activity window, but there are many double clicks plus the additional mouse click if there are many stations for which you are not sure if you worked them already or not. Tonight there are more than 50 stations decoded on 14.074 in FT8 in one time slot and more than 45 on 18.100 in FT8, just to give you an example. Therefore I still consider my assessment of "not convenient" is very valid.

# Disabling the WSJT-X "Double click on call sets TX enable" setting costs you exactly one extra click of the "Enable TX" button after you've identified a station you wish to work -- no matter how many stations you evaluated by double-clicking them. What you are objecting to is the need to double-click a callsign in the WSJT-X "Band Activity" panel to determine whether or not you should work it - because SpotCollector only highlights callsigns with which a confirmed QSO would advance your progress towards the DXCC, IOTA, Leaderboard, Marathon, WAS, WAZ, and WPX awards on bands you've specified, in the modes you've specified.

On the other hand all decoded calls are listed as local spots more or less immediately in Spotcollector. Therefore I wonder if there is not any chance to look not only in the LotW- and eQSL-Member database but also in the log database and to have a certain color code in Spotcollector for those which are already in that database as worked.

# You are suggesting that DXLab's Realtime Award Tracking (RAT) functionality be expanded to support a "Worked All Callsigns" objective. This is technically feasible, but would require a significant development effort. The fact that there is no actual award associated with this objective makes this effort difficult to justify. Expanding RAT to support SOTA, POTA, and/or WWFF would at least by justified by the existence of award sponsors.

As mentioned before: this is not any replacement of a contest logger such as N1MM or similar, it is just significantly improving the operating of FTx in WSJT-X (and this is different than working CW, SSB or RTTY in which I never felt the need of such a function outside of a contest and I am very happy in using DXLab a very long time already).

# One could aspire to Work Every Callsign in CW, SSB, RTTY, or PSK. I don't recall anyone ever requesting this capability.

73,

Dave, AA6YQ


Dave AA6YQ
 

+ AA6YQ comments below

If you want a display of previously worked stations, look into JT-Alert.

+ Step-by-step instructions are here:

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

73,

Dave, AA6YQ