Date   

Re: Lotw failure to update status of LotW QSOs when DXKeeper claims one QSO is "Already Uploaded"

ART W2NRA
 

Hi Dave,

Your wrote:

+ The most common cause of this situation? You have one or more duplicate QSOs in your log, possibly from importing a file of QSOs that you had already imported. But let's not jump to conclusions; please filter the Log Page Display to show all QSOs with AA2IL. Is there more than one copy of your QSO on 20m CW on 2022-06-14 at 03:23:24Z ?

YOU ARE RIGHT! And it is probably multiple duplicate QSOs.
How do I fix that?
Which dups do I delete? Some have been uploaded. Or does it matter if I delete a QSO that has been uploaded and then upload the other QSO again?

Thank you!

73, Art W2NRA CWOPS #1955




Re: Lotw failure to update status of LotW QSOs when DXKeeper claims one QSO is "Already Uploaded"

Dave AA6YQ
 

+ AA6YQ comments below

Thank you, Ed, but that didn’t work.

+ If your log contained a QSO with no callsign specified, the BROKE filter would have identified it.

+ The problem is not that you are submitting a QSO with a missing callsign, it's that you are submitting a QSO that has already been submitted. The diagnostic task is to determine why that's happening.

+ The most common cause of this situation? You have one or more duplicate QSOs in your log, possibly from importing a file of QSOs that you had already imported. But let's not jump to conclusions; please filter the Log Page Display to show all QSOs with AA2IL. Is there more than one copy of your QSO on 20m CW on 2022-06-14 at 03:23:24Z ?

73,

Dave, AA6YQ


Re: Lotw failure to update status of LotW QSOs when DXKeeper claims one QSO is "Already Uploaded"

ART W2NRA
 

Thank you, Ed, but that didn’t work.

One thing I tried is to try one QSO Upload and sometimes that works for that one QSO.  But eventually it stops working.  Even if it did work I still have almost 500 QSOs to upload to LOTW.

73, Art W2NRA
CWOPS #1955

On Aug 5, 2022, at 11:42 AM, Earl Needham <earl.kd5xb@...> wrote:


Go to the bottom left in DXKeeper and click on "CALL".  This sorts in call order -- so look at the top of the display to see if there is one up there with a blank callsign.

Earl
KD5XB

On Fri, Aug 5, 2022 at 9:24 AM ART W2NRA via groups.io <w2nra=me.com@groups.io> wrote:
Hi Joe,

I clicked that button and it showed NO BROKE QSOs!

Good suggestion anyway.  I didn’t know that.

Thank you!

73, Art W2NRA
CWOPS #1955

> On Aug 5, 2022, at 11:10 AM, Joe Subich, W4TV <lists@...> wrote:
>
> 
> > I do not know how to find the QSO with the missng
> > callsign.
>
> Click the "Broke" button in the filter area at the bottom of
> the log page display.
>
>> I wonder why do all of the updated LotW QSLs is cancelled when only
>> one is in error?
> Because tQSL will not "sign" a log upload with QSOs that have been
> previously uploaded thanks to the lids who continuously upload the
> same QSOs (their entire log) regularly and the idiots who upload
> their entire logs with a new QTH when they move.
>
> 73,
>
>   ... Joe, W4TV
>
>
>> On 2022-08-05 10:57 AM, ART W2NRA via groups.io wrote:
>> DXKeeper msg:
>> - - - - - - - - - - - - - - - - - - - - - - - - - - - -
>> TQSL Version 2.6.4 [v2.6.4]
>> Signing using Callsign W2NRA, DXCC Entity UNITED STATES OF AMERICA
>> Already Uploaded QSO suppressed on line 5
>> CALL: AA2IL
>> TIME_ON: 032324
>> QSO_DATE: 20220614
>> MODE: CW
>> BAND: 20M
>> FREQ: 14.0344
>> BAND_RX: 20M
>> FREQ_RX: 14.0344
>> Signing aborted
>> No records to upload
>> Final Status: User Cancelled(1)
>> - - - - - - - - - - - - - - - - - - - - - - - - - - - -
>> I also get a small window with:
>> - - - - - - - - - - - - - - -
>> No QSOs were uploaded to LoTW
>> cancelled by user
>> *
>> - - - - - - - - - - - - - - -
>> I didn't cancel anything!
>> Last time this happened (some time in June 2022) you said it was caused by one QSO whose callsign is blank and the callsign of the QSO after it was used by DXKeeper. I do not know how to find the QSO with the missng callsign.
>> I wonder why do all of the updated LotW QSLs is cancelled when only one is in error?
>> 73 Art W2NRA
>
>
>
>
>
>






Re: Lotw failure to update status of LotW QSOs when DXKeeper claims one QSO is "Already Uploaded"

Dave AA6YQ
 

+ AA6YQ comments below

DXKeeper msg:

- - - - - - - - - - - - - - - - - - - - - - - - - - - - TQSL Version 2.6.4 [v2.6.4]

Signing using Callsign W2NRA, DXCC Entity UNITED STATES OF AMERICA

Already Uploaded QSO suppressed on line 5
CALL: AA2IL
TIME_ON: 032324
QSO_DATE: 20220614
MODE: CW
BAND: 20M
FREQ: 14.0344
BAND_RX: 20M
FREQ_RX: 14.0344

Signing aborted

No records to upload

Final Status: User Cancelled(1)
- - - - - - - - - - - - - - - - - - - - - - - - - - - -

+ The "DXKeeper msg" above is relayed from TQL, which reports

"Already Uploaded QSO suppressed on line 5"

+ and proceeds to describe the "already-uploaded QSO":

AA2IL on 20m CW on 2022-06-14 at 03:23:24Z

+ The presence of this "already uploaded" QSO caused TQSL to reject all QSOs in the batch that DXKeeper sent it to upload. As Joe W4TV mentioned, this capability was added to TQSL back in 2013 to stop users who were re-submitting their entire logs each time they made a few new QSOs. Doing so reduced the load on the LoTW server by about 50%.

+ Diagnostic step 1: filter the Log Page Display to show all QSOs with AA2IL. Is there more than one copy of your QSO on 20m CW on 2022-06-14 at 03:23:24Z ?

73,

Dave, AA6YQ


Re: Lotw failure to update status of LotW QSOs when DXKeeper claims one QSO is "Already Uploaded"

Earl Needham
 

Go to the bottom left in DXKeeper and click on "CALL".  This sorts in call order -- so look at the top of the display to see if there is one up there with a blank callsign.

Earl
KD5XB

On Fri, Aug 5, 2022 at 9:24 AM ART W2NRA via groups.io <w2nra=me.com@groups.io> wrote:
Hi Joe,

I clicked that button and it showed NO BROKE QSOs!

Good suggestion anyway.  I didn’t know that.

Thank you!

73, Art W2NRA
CWOPS #1955

> On Aug 5, 2022, at 11:10 AM, Joe Subich, W4TV <lists@...> wrote:
>
> 
> > I do not know how to find the QSO with the missng
> > callsign.
>
> Click the "Broke" button in the filter area at the bottom of
> the log page display.
>
>> I wonder why do all of the updated LotW QSLs is cancelled when only
>> one is in error?
> Because tQSL will not "sign" a log upload with QSOs that have been
> previously uploaded thanks to the lids who continuously upload the
> same QSOs (their entire log) regularly and the idiots who upload
> their entire logs with a new QTH when they move.
>
> 73,
>
>   ... Joe, W4TV
>
>
>> On 2022-08-05 10:57 AM, ART W2NRA via groups.io wrote:
>> DXKeeper msg:
>> - - - - - - - - - - - - - - - - - - - - - - - - - - - -
>> TQSL Version 2.6.4 [v2.6.4]
>> Signing using Callsign W2NRA, DXCC Entity UNITED STATES OF AMERICA
>> Already Uploaded QSO suppressed on line 5
>> CALL: AA2IL
>> TIME_ON: 032324
>> QSO_DATE: 20220614
>> MODE: CW
>> BAND: 20M
>> FREQ: 14.0344
>> BAND_RX: 20M
>> FREQ_RX: 14.0344
>> Signing aborted
>> No records to upload
>> Final Status: User Cancelled(1)
>> - - - - - - - - - - - - - - - - - - - - - - - - - - - -
>> I also get a small window with:
>> - - - - - - - - - - - - - - -
>> No QSOs were uploaded to LoTW
>> cancelled by user
>> *
>> - - - - - - - - - - - - - - -
>> I didn't cancel anything!
>> Last time this happened (some time in June 2022) you said it was caused by one QSO whose callsign is blank and the callsign of the QSO after it was used by DXKeeper. I do not know how to find the QSO with the missng callsign.
>> I wonder why do all of the updated LotW QSLs is cancelled when only one is in error?
>> 73 Art W2NRA
>
>
>
>
>
>






Re: Lotw failure to update status of LotW QSOs when DXKeeper claims one QSO is "Already Uploaded"

ART W2NRA
 

Hi Joe,

I clicked that button and it showed NO BROKE QSOs!

Good suggestion anyway. I didn’t know that.

Thank you!

73, Art W2NRA
CWOPS #1955

On Aug 5, 2022, at 11:10 AM, Joe Subich, W4TV <lists@...> wrote:


I do not know how to find the QSO with the missng
callsign.
Click the "Broke" button in the filter area at the bottom of
the log page display.

I wonder why do all of the updated LotW QSLs is cancelled when only
one is in error?
Because tQSL will not "sign" a log upload with QSOs that have been
previously uploaded thanks to the lids who continuously upload the
same QSOs (their entire log) regularly and the idiots who upload
their entire logs with a new QTH when they move.

73,

... Joe, W4TV


On 2022-08-05 10:57 AM, ART W2NRA via groups.io wrote:
DXKeeper msg:
- - - - - - - - - - - - - - - - - - - - - - - - - - - -
TQSL Version 2.6.4 [v2.6.4]
Signing using Callsign W2NRA, DXCC Entity UNITED STATES OF AMERICA
Already Uploaded QSO suppressed on line 5
CALL: AA2IL
TIME_ON: 032324
QSO_DATE: 20220614
MODE: CW
BAND: 20M
FREQ: 14.0344
BAND_RX: 20M
FREQ_RX: 14.0344
Signing aborted
No records to upload
Final Status: User Cancelled(1)
- - - - - - - - - - - - - - - - - - - - - - - - - - - -
I also get a small window with:
- - - - - - - - - - - - - - -
No QSOs were uploaded to LoTW
cancelled by user
*
- - - - - - - - - - - - - - -
I didn't cancel anything!
Last time this happened (some time in June 2022) you said it was caused by one QSO whose callsign is blank and the callsign of the QSO after it was used by DXKeeper. I do not know how to find the QSO with the missng callsign.
I wonder why do all of the updated LotW QSLs is cancelled when only one is in error?
73 Art W2NRA





Re: Lotw failure to update status of LotW QSOs when DXKeeper claims one QSO is "Already Uploaded"

Joe Subich, W4TV
 

I do not know how to find the QSO with the missng
callsign.
Click the "Broke" button in the filter area at the bottom of
the log page display.

I wonder why do all of the updated LotW QSLs is cancelled when only
one is in error?
Because tQSL will not "sign" a log upload with QSOs that have been
previously uploaded thanks to the lids who continuously upload the
same QSOs (their entire log) regularly and the idiots who upload
their entire logs with a new QTH when they move.

73,

... Joe, W4TV


On 2022-08-05 10:57 AM, ART W2NRA via groups.io wrote:
DXKeeper msg:
- - - - - - - - - - - - - - - - - - - - - - - - - - - -
TQSL Version 2.6.4 [v2.6.4]
Signing using Callsign W2NRA, DXCC Entity UNITED STATES OF AMERICA
Already Uploaded QSO suppressed on line 5
CALL: AA2IL
TIME_ON: 032324
QSO_DATE: 20220614
MODE: CW
BAND: 20M
FREQ: 14.0344
BAND_RX: 20M
FREQ_RX: 14.0344
Signing aborted
No records to upload
Final Status: User Cancelled(1)
- - - - - - - - - - - - - - - - - - - - - - - - - - - -
I also get a small window with:
- - - - - - - - - - - - - - -
No QSOs were uploaded to LoTW
cancelled by user
*
- - - - - - - - - - - - - - -
I didn't cancel anything!
Last time this happened (some time in June 2022) you said it was caused by one QSO whose callsign is blank and the callsign of the QSO after it was used by DXKeeper. I do not know how to find the QSO with the missng callsign.
I wonder why do all of the updated LotW QSLs is cancelled when only one is in error?
73 Art W2NRA


Lotw failure to update status of LotW QSOs when DXKeeper claims one QSO is "Already Uploaded"

ART W2NRA
 

DXKeeper msg:
- - - - - - - - - - - - - - - - - - - - - - - - - - - -
TQSL Version 2.6.4 [v2.6.4]
Signing using Callsign W2NRA, DXCC Entity UNITED STATES OF AMERICA

Already Uploaded QSO suppressed on line 5
CALL: AA2IL
TIME_ON: 032324
QSO_DATE: 20220614
MODE: CW
BAND: 20M
FREQ: 14.0344
BAND_RX: 20M
FREQ_RX: 14.0344

Signing aborted
No records to upload
Final Status: User Cancelled(1)
- - - - - - - - - - - - - - - - - - - - - - - - - - - -

I also get a small window with:

- - - - - - - - - - - - - - -
No QSOs were uploaded to LoTW
cancelled by user
*
- - - - - - - - - - - - - - -

I didn't cancel anything!
Last time this happened (some time in June 2022) you said it was caused by one QSO whose callsign is blank and the callsign of the QSO after it was used by DXKeeper. I do not know how to find the QSO with the missng callsign.

I wonder why do all of the updated LotW QSLs is cancelled when only one is in error?

73 Art W2NRA




Re: SpotCollector and WAS?

David Reed
 

Thanks Dave! I’ll get right on it!

73 de W5SV - Dave

On Aug 4, 2022, at 23:47, Dave AA6YQ <aa6yq@...> wrote:

+ 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


Re: Solar Flux

Willem Van gaalen
 

No worries... with 30 Watts output FT8, into a halve wave wiredipole, I worked 41 DXCC on 6m, confirmed by QRZ/LOTW!

Good dx hunting and 73 de Wim, pa0wjg

Op 4-8-2022 om 21:51 schreef 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!

Virusvrij. www.avast.com


DXKeeper 16.7.5 is available

Dave AA6YQ
 

This version

- in the QRZ panel on the Configuration window's Callbook tab, expands the name of the "Ignore geocoded grid squares" option to
"Ignore geocoded grid squares, latitudes, and longitudes"

- provides a "Preferred Location Source" panel on the Configuration window's Callbook tab that operates as described in
https://groups.io/g/DXLab/message/209060 (tnx to Stewart G0LGS and Joe W4TV)

- corrects a regression introduced in DXKeeper 16.3.7 that gives Callbook data preference over data from previous QSOs when logging
via the Main window's "Log QSOs" tab (tnx to Stewart G0LGS)

- corrects a regression introduced in DXKeeper 16.5.7 that fails to initialize a new QSO's Propagation Mode item if "Default
Propagation Mode by Band" is not enabled on the Configuration window's Defaults tab (tnx to Julio W4HY)

- eliminates unnecessary DXView and Pathfinder lookups during invocations of the "Sync LoTW QSOs", "Sync LoTW QSLs", and "Sync eQSL
QSLs" functions (tnx to Jon KM8V)

- corrects the regression in DXKeeper 16.7.1 that generated an erroneous "invalid gridsquare" error message when importing a QSO or
receiving a QSO from another application (tnx to Jim N7US)

- corrects the regression in DXKeeper 16.7.1 that failed to populate the latitude and longitude of a QSO received from another
application (tnx to Mike K9UW, Henk PA5KT, Henry N4HB, Dan KI6X, Wray AB4SF, Rich VE3KI, Joe W4TV, Mike K6MKF, and Jose N4BAA)

- handles invalid grid squares and or latitudes and longitudes found in an imported or received QSO or reported by the selected
callbook

- if a Spot Database Entry is double-clicked with DXKeeper's "New QSO on DX Spot activation" option enabled, populates the new QSO's
latitude, longitude, and distance (tnx to Charles N2SO)

- updates the Configuration.htm, Import.htm, and QSL.htm documentation files


Notes:

1. Update your firewall and anti-malware applications to consider this new version of DXKeeper to be "safe"

a. JOTTI virus scan: 0 of 15 scanners detected malware in this version's executable

b. VirusTotal: 0 of 70 scanners detected malware in this version's executable

c. submitted to Microsoft for analysis by Windows Defender: no malware detected in this version's executable


2. To view QSOs with missing Propagation Mode items as a result of the regression in DXKeeper 16.5.7, filter the Log Page Display
with the SQL expression

(QSO_BEGIN>#2022-05-21#) and (LEN(PROP_MODE)=0)


2A. If all the Propagation Mode items of all of these QSOs should be set to the same value -- e.g. F2 -- then

2A1. backup your log (Configuration window, Log tab, Backup button)

2A2. in the "Modify QSOs" panel at the bottom of the "Advanced Sorts, Filters, and Modifiers" window,

2A2a. set the "Item name" selector to PROP_MODE

2A2b. set the "Item new value" selector to the correct propagation mode (e.g. F2)

2A2c. click the Mod button


2B. If all the Propagation Mode items of all of these QSOs should be set to different values as a function of Band or Date Range,
then make the corrections in segments. For example, to set PROP_MODE as a function of Band:

2B1. backup your log (Configuration window, Log tab, Backup button)

2B2. filter the Log Page Display with (QSO_BEGIN>#2022-05-21#) and (LEN(PROP_MODE)=0) and (Band = '6M')

2B3. use the "Modify QSOs" panel to set the PROP_MOD in all QSOs in the Log Page Display to ES

2B4. filter the Log Page Display with (QSO_BEGIN>#2022-05-21#) and (LEN(PROP_MODE)=0) and (Band <> '6M')

2B5. use the "Modify QSOs" panel to set the PROP_MOD in all QSOs in the Log Page Display to F2


3. If this upgrade doesn't work correctly, see the "After an Upgrade" section of

http://www.dxlabsuite.com/dxlabwiki/ApplicationStoppedWorking


4. After upgrading, to revert to the previous version of DXKeeper, see

http://www.dxlabsuite.com/dxlabwiki/RevertApplicationVersion


DXKeeper 16.7.5 is available via the DXLab Launcher and via

http://www.dxlabsuite.com/download.htm

73,

Dave, AA6YQ


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

1721 - 1740 of 211204