Date   

Re: SpotCollector and WAS?

Dave AA6YQ
 

+ AA6YQ comments below

I am seeking several variations of WAS from my new QTH, and am wondering how I could use SpotCollector to help...

Any ideas of how to display STATE for a US State? and even better, if it is needed (not in my log / or confirmed yet)?

+ Relevant reference documentation is here:

https://www.dxlabsuite.com/spotcollector/Help/SpotDatabase.htm#Identifying%20%22Needed%22%20Spot%20Database%20entries

+ and here:

https://www.dxlabsuite.com/spotcollector/Help/SpotDatabase.htm#Filtering%20by%20Callsign,%20DXCC%20entity,%20Frequency,%20and%20Need


+ Step-by-step instructions are here

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

+ and here:

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

+ On the Databases tab of DXView's Configuration window, be sure the USAP database is present; this database specifies a State for each station licensed by the FCC.

+ If you still have questions after reviewing the above articles, don't hesitate to post them here.

73,

Dave, AA6YQ


SpotCollector and WAS?

David Reed
 

I am seeking several variations of WAS from my new QTH, and am wondering how I could use SpotCollector to help...

Any ideas of how to display STATE for a US State? and even better, if it is needed (not in my log / or confirmed yet)?

Thanks!

--
73 de Dave, W5SV


Re: FT8 and Spotcollector issue

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


Re: Problem Recurs - atemp to upload LOTW duplicates QSO

Dave AA6YQ
 

+ AA6YQ comments below

I have a large group to upload to Lotw. They all load fine into my computer. If I try to upload them one of the QSOs stops the whole process.

+ What does "stops the whole process" mean, exactly? Is an error message displayed? If so, what are its contents?

73,

Dave, AA6YQ


Re: FT8 and Spotcollector issue

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


Re: FT8 and Spotcollector issue

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


Re: Problem Recurs - atemp to upload LOTW duplicates QSO

ART W2NRA
 

Hi Dave,

I have a large group to upload to Lotw. They all load fine into my computer. If I try to upload them one of the QSOs stops the whole process. I think one QSO somehow doesn’t have a callsign and uses the callsign of the next QSO.

I have some ideas to try.

73, Art W2NRA
CWOPS #1955

On Aug 4, 2022, at 5:46 PM, Dave AA6YQ <aa6yq@...> wrote:

+ AA6YQ comments below

This also happened in June. Uploading LOTW causes a duplicate QSO, I think because one QSO somewhere in my 74,549 QSOs has no data or Callsign and DXKeeper adds the next QSO and creates a dupe. I THINK!

+ That's not correct:

1. DXKeeper won't attempt to upload a QSO to LoTW if that QSO lacks a callsign.

2. TQSL won't accept a QSO for uploading to LoTW if that QSO has already been uploaded to LoTW.


FYI - all my QSOs are loaded in DXKeeper via N1MM Logger.

I've misplaced the complicated info you sent last time this happened.

Please help!

+ Exactly what is it that isn't working as expected?

73,

Dave, AA6YQ






Re: FT8 and Spotcollector issue

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


Re: Problem Recurs - atemp to upload LOTW duplicates QSO

Dave AA6YQ
 

+ AA6YQ comments below

This also happened in June. Uploading LOTW causes a duplicate QSO, I think because one QSO somewhere in my 74,549 QSOs has no data or Callsign and DXKeeper adds the next QSO and creates a dupe. I THINK!

+ That's not correct:

1. DXKeeper won't attempt to upload a QSO to LoTW if that QSO lacks a callsign.

2. TQSL won't accept a QSO for uploading to LoTW if that QSO has already been uploaded to LoTW.


FYI - all my QSOs are loaded in DXKeeper via N1MM Logger.

I've misplaced the complicated info you sent last time this happened.

Please help!

+ Exactly what is it that isn't working as expected?

73,

Dave, AA6YQ


Problem Recurs - atemp to upload LOTW duplicates QSO

ART W2NRA
 

Hi Dave,

This also happened in June.  Uploading LOTW causes a duplicate QSO, I think because one QSO somewhere in my 74,549 QSOs has no data or Callsign and DXKeeper adds the next QSO and creates a dupe.  I THINK!

FYI - all my QSOs are loaded in DXKeeper via N1MM Logger.

I've misplaced the complicated info you sent last time this happened. 

Please help!

73, Art W2NRA CWOPS #1955



Re: FT8 and Spotcollector issue

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


Re: Solar Flux

Peter Dougherty
 

Interesting. I have DXCC on 80, 40, 30, 20, 17, 15, 12 and 10 meters,
but I've only worked 15 DXCC entities on 6 meters. That was using FT8
with 100 watts and a hex beam. I guess DL is the farthest I've worked. 
Not F2 propagation?  Doubt I'll get DXCC on 6 meters in my lifetime.
Don't be so sure about that! I started on 6m in 2005 with a 6M5 Yagi at 35', and using SSB and CW, I managed to get to about 70. I went QRO to 1500W, changed the 6M5 out for a 6 element LFA, and this season not only did I hit 100, but I'm up to 111 entities and just shy of 850 grid squares. If you can get even a little 3 or 4 element Yagi or preferably a Loop Fed Array, and a bit more than 100W there's no reason you can't hit 100 entities in a few years with typical seasonal Es and a bit of luck and time at the radio. You can do it!


Re: FT8 and Spotcollector issue

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


Re: ODX / OMDX / ?

Dave AA6YQ
 

+ AA6YQ comments below

I'm trying to understand the difference between ODX and OMDX.

Looking at:

KX4I on 50313.0 in FT8 at 8/4/2022 1510Z (K: United States)

ODX is shown as 325 and OMDX is 500.

Looking at the definitions -- well, I just don't "get it".

ODX: the distance from the center of the Maidenhead gridsquare of the closest station to spot the DX station and the Operator's latitude and longitude in miles or kilometers; if no DX station or spotting station gridsquare is known, this value is set to -1 (displayed as a blank entry in the Spot Database Display)

OMDX: the maximum distance from the center of the Maidenhead gridsquare of the closest station to spot the DX station and the Operator's latitude and longitude in miles or kilometers

Does this mean that ODX is the distance from me to the center of the gridsquare the spotting station is in? And how can the maximum be a different value if both reference the center of his gridsquare?

+ The ODX field is as you describe it: the distance from the center of the Maidenhead gridsquare of the closest station to spot the DX station and the Operator's latitude and longitude.

+ SpotCollector's "Band Filter" window provides the ability to specify a "Max origin DX" for each band. You can, for example, configure this filter to hide active 6m stations that haven't been spotted by at least one station within 500 miles of your QTH.

+ When SpotCollector creates or updates a Spot Database Entry for a station operating on band B, it consults the "Band Filter" window to see if "Enable Start/End & Max Origin DX Filtering" is enabled, and if it is enabled for band B. If so, the Entry's OMDX field is populated with the "Max origin DX" specified for band B in the "Band Filter" window; if not, the Entry's OMDX field is set to the circumference of the earth. Thus when filtering the Spot Database Display with the Band Filter, any Spot Database Entry whose ODX field is greater than its OMDX field should be hidden.

+ I have updated the description of OMDX in

https://www.dxlabsuite.com/spotcollector/Help/SpotDatabase.htm#SDB%20OMDX

+ to better describe its functionality. Thanks!

73,

Dave, AA6YQ


ODX / OMDX / ?

Earl Needham
 

I'm trying to understand the difference between ODX and OMDX.

Looking at:

KX4I on 50313.0 in FT8 at 8/4/2022 1510Z (K: United States)

ODX is shown as 325 and OMDX is 500.

Looking at the definitions -- well, I just don't "get it".

ODX: the distance from the center of the Maidenhead gridsquare of the closest station to spot the DX station and the Operator's latitude and longitude in miles or kilometers; if no DX station or spotting station gridsquare is known, this value is set to -1 (displayed as a blank entry in the Spot Database Display)

OMDX: the maximum distance from the center of the Maidenhead gridsquare of the closest station to spot the DX station and the Operator's latitude and longitude in miles or kilometers

Does this mean that ODX is the distance from me to the center of the gridsquare the spotting station is in?  And how can the maximum be a different value if both reference the center of his gridsquare?

Tnx
KD5XB


Re: CAT PTT help needed for Commander - Vara AC

Alan Hyde
 

OK thanks Dave, that explains it!

All the best
Alan VK2ATW


Re: CAT PTT help needed for Commander - Vara AC

Dave AA6YQ
 

+ AA6YQ comments below
Would appreciate some help please. I have Commander setup to work with Thetis SDR software using TCP/IP. Works very well, no problems. 

I am starting to experiment with Vara AC using the Vara HF modem software. Vara AC will only connect via COM ports so i have configured Commander to use the Secondary CAT serial port and have used both Kenwood and FlexRadio protocol as I can select either of these in Vara AC. I have frequency changes working correctly so i know the com port connection is working. However i cannot get PTT working at all and am stumped on what to try next.

I can get Vara AC working correctly by connecting directly by Serial CAT to Thetis so i know Vara AC CAT is ok. My preference however is to have all my CAT control going via Commander so i can use the command scripting etc

+ Commander does not provide the ability to switch its Secondary CAT port between RX and TX. The Secondary port is intended to support connection to a second radio that tracks the primary radio's frequency (for diversity reception), a panadaptor that tracks the primary radio's frequency, or an external device like an amplifier, tuner, or antenna switch that tracks the primary radio's frequency.

        73,

             Dave, AA6YQ


Re: New MYQTHID

Dave AA6YQ
 

+ AA6YQ comments below
Yes to TQSL Station Location. Which is what I changed. Probably too soon.

In court tomorrow and at Pacific DX Conv this weekend. If I can let me put it on hold til next week when I'll have enough bux to pay attention and work your suggestions.

+ Take a look at the Wiki Article I cited. If that doesn't make the corrective action clear, let me know.

          73,

                 Dave, AA6YQ


CAT PTT help needed for Commander - Vara AC

Alan Hyde
 

Hi everyone
Would appreciate some help please. I have Commander setup to work with Thetis SDR software using TCP/IP. Works very well, no problems. 

I am starting to experiment with Vara AC using the Vara HF modem software. Vara AC will only connect via COM ports so i have configured Commander to use the Secondary CAT serial port and have used both Kenwood and FlexRadio protocol as I can select either of these in Vara AC. I have frequency changes working correctly so i know the com port connection is working. However i cannot get PTT working at all and am stumped on what to try next.

I can get Vara AC working correctly by connecting directly by Serial CAT to Thetis so i know Vara AC CAT is ok. My preference however is to have all my CAT control going via Commander so i can use the command scripting etc.

Thanks for any pointers.

Regards Alan  VK2ATW


Re: New MYQTHID

k6xt
 

Thanks Dave

Yes to TQSL Station Location. Which is what I changed. Probably too soon.

In court tomorrow and at Pacific DX Conv this weekend. If I can let me put it on hold til next week when I'll have enough bux to pay attention and work your suggestions.
73 Art

1681 - 1700 of 211153