Date   

Something going on at LotW ...

Mike Flowers
 

Trying to Sync LotW QSOs yielded “Unable to download from LotW: invalid request:

 

QRZ.COM log sync reports:  “LOTW Uploads and Downloads are not currently available, We are actively working to restore LOTW integration”

 

Club Log just worked fine doing a LotW Sync ..

 

Just a FYI …

 

- 73 and good DX de Mike, K6MKF, NCDXC Secretary

 


Re: VP9I

Dave AA6YQ
 

* more AA6YQ comments below

Yes it was contest log from ARRL dx using N1MM+. Never had this happen
before.

Log file is attached. It is the last contact in log at 2111 UTC.

* This group does not convey attachments, which is why I asked you to attach the ADIF file to an email message and send the message to me via

aa6yq (at) ambersoft.com

73,

Dave, AA6YQ

On 3/12/2020 1:41 PM, Dave AA6YQ wrote:
+ AA6YQ comments below

Just checking log upload from the ARRL DX SSB contest

+ What does "checking log upload" mean?

and found that the contact with VP9I will not let me save it. It says that the country code is incorrect. But it showing 64, DXCC is VP9 and the entity is Bermuda.

What am I missing?

+ Did you log the QSO using DXKeeper, or did you log it with another application? If the latter, how are you conveying the QSO from the other application to DXKeeper? If you're importing an ADIF file, please attach the ADIF file to an email message, and send the message to me via

aa6yq (at) ambersoft.com

73,

Dave, AA6YQ




--
N4EK Extra Class
FCC GROL PG-7T-5869
Broadcast Engineer
--
This email has been checked for viruses by AVG.
https://www.avg.com


Re: VP9I

N4EK Ed
 

Yes it was contest log from ARRL dx using N1MM+. Never had this happen before.
Log file is attached. It is the last contact in log at 2111 UTC.
Ed

On 3/12/2020 1:41 PM, Dave AA6YQ wrote:
+ AA6YQ comments below

Just checking log upload from the ARRL DX SSB contest

+ What does "checking log upload" mean?

and found that the contact with VP9I will not let me save it. It says that the country code is incorrect. But it showing 64, DXCC is VP9 and the entity is Bermuda.

What am I missing?

+ Did you log the QSO using DXKeeper, or did you log it with another application? If the latter, how are you conveying the QSO from the other application to DXKeeper? If you're importing an ADIF file, please attach the ADIF file to an email message, and send the message to me via

aa6yq (at) ambersoft.com

73,

Dave, AA6YQ



--
N4EK Extra Class
FCC GROL PG-7T-5869
Broadcast Engineer
--
This email has been checked for viruses by AVG.
https://www.avg.com


Re: VP9I

Dave AA6YQ
 

+ AA6YQ comments below

Just checking log upload from the ARRL DX SSB contest

+ What does "checking log upload" mean?

and found that the contact with VP9I will not let me save it. It says that the country code is incorrect. But it showing 64, DXCC is VP9 and the entity is Bermuda.

What am I missing?

+ Did you log the QSO using DXKeeper, or did you log it with another application? If the latter, how are you conveying the QSO from the other application to DXKeeper? If you're importing an ADIF file, please attach the ADIF file to an email message, and send the message to me via

aa6yq (at) ambersoft.com

73,

Dave, AA6YQ


Re: VP9I

N4EK Ed
 

Just checking log upload from the ARRL DX SSB contest and found that the contact with VP9I will not let me save it. It says that the country code is incorrect. But it showing 64, DXCC is VP9 and the entity is Bermuda. What am I missing?
Ed, N4EK


--
N4EK Extra Class
FCC GROL PG-7T-5869


--
This email has been checked for viruses by AVG.
https://www.avg.com


Re: LoTW Confirmed QSOs

Dave AA6YQ
 

+ AA6YQ comments below

Thanks Rich, That appears to be exactly what is going on. I should have recognized that when I looked at my search in LoTW for those QSOs. ie, they do in fact NOT show anything in the QSL column.

+ The file I asked you to send me shows that your QSO has been accepted by LoTW, but not confirmed. Thus the logged QSO status in your initial post below is correct.

73,

Dave, AA6YQ

On Thursday, March 12, 2020, 9:03:33 AM MDT, ve3ki <ve3iay@...> wrote:


"...they are there showing that I worked them": What exactly do you mean by this?

If you log in to LotW, select "Your QSOs" and do a search for your QSOs with VP8PJ, you should see all of the QSOs you uploaded, but is there anything in the "QSL" column? If there isn't anything in the QSL column, VP8PJ has not yet uploaded those QSOs and they are not confirmed in LotW, which would be consistent with the field contents you reported.

If, on the other hand, the "QSL" column contains entries like "SOUTH ORKNEY ISLANDS", then VP8PJ has uploaded those QSOs and they have been confirmed in LotW, in which case the Sync QSLs or Update from LotW should update those fields.

73,
Rich VE3KI




On Thu, Mar 12, 2020 at 09:37 AM, Rod Greene wrote:
Need a little help regarding LoTW and DXKeeper Codes -

I worked VP8PJ three times, once on each of SSB, CW, and FT8. I logged the Qs and submitted them to LoTW via Keeper. I have recently looked them up on LoTW and they are there showing that I worked them.

I have completed the "Sync" process on Keeper.

However, now when I look at them in Keeper, the fields show as follows:
APP_DXKeeper_LoTW_QSL_SENT = Y
APP_DXKeeper_LoTW_QSL_RCVD = R
APP_DXKeeper_LoTWConfirmation = blank

I looked at the flow chart but didn't understand it in regard to the above. Am I looking at the wrong fields? Why doesn't Keeper show them as Y for RCVD and Confirmed?

Thanks! 73, Rod/w7zrc

ps: Something was asked about this on here a few days ago and I have tried to find it, but no luck.


Re: LoTW Confirmed QSOs

Rod Greene
 

Thanks Rich, That appears to be exactly what is going on. I should have recognized that when I looked at my search in LoTW for those QSOs. ie, they do in fact NOT show anything in the QSL column. So the dxpedition has not uploaded yet.

My mistake - thanks everyone. Super support!

73, Rod/w7zrc

On Thursday, March 12, 2020, 9:03:33 AM MDT, ve3ki <ve3iay@...> wrote:


"...they are there showing that I worked them": What exactly do you mean by this?

If you log in to LotW, select "Your QSOs" and do a search for your QSOs with VP8PJ, you should see all of the QSOs you uploaded, but is there anything in the "QSL" column? If there isn't anything in the QSL column, VP8PJ has not yet uploaded those QSOs and they are not confirmed in LotW, which would be consistent with the field contents you reported.

If, on the other hand, the "QSL" column contains entries like "SOUTH ORKNEY ISLANDS", then VP8PJ has uploaded those QSOs and they have been confirmed in LotW, in which case the Sync QSLs or Update from LotW should update those fields.

73,
Rich VE3KI




On Thu, Mar 12, 2020 at 09:37 AM, Rod Greene wrote:
Need a little help regarding LoTW and DXKeeper Codes -
 
I worked VP8PJ three times, once on each of SSB, CW, and FT8. I logged the Qs and submitted them to LoTW via Keeper. I have recently looked them up on LoTW and they are there showing that I worked them.
 
I have completed the "Sync" process on Keeper.
 
However, now when I look at them in Keeper, the fields show as follows:
APP_DXKeeper_LoTW_QSL_SENT = Y
APP_DXKeeper_LoTW_QSL_RCVD = R
APP_DXKeeper_LoTWConfirmation = blank
 
I looked at the flow chart but didn't understand it in regard to the above. Am I looking at the wrong fields? Why doesn't Keeper show them as Y for RCVD and Confirmed?
 
Thanks! 73, Rod/w7zrc
 
ps: Something was asked about this on here a few days ago and I have tried to find it, but no luck.


Re: LoTW Confirmed QSOs

ve3ki
 

"...they are there showing that I worked them": What exactly do you mean by this?

If you log in to LotW, select "Your QSOs" and do a search for your QSOs with VP8PJ, you should see all of the QSOs you uploaded, but is there anything in the "QSL" column? If there isn't anything in the QSL column, VP8PJ has not yet uploaded those QSOs and they are not confirmed in LotW, which would be consistent with the field contents you reported.

If, on the other hand, the "QSL" column contains entries like "SOUTH ORKNEY ISLANDS", then VP8PJ has uploaded those QSOs and they have been confirmed in LotW, in which case the Sync QSLs or Update from LotW should update those fields.

73,
Rich VE3KI




On Thu, Mar 12, 2020 at 09:37 AM, Rod Greene wrote:
Need a little help regarding LoTW and DXKeeper Codes -
 
I worked VP8PJ three times, once on each of SSB, CW, and FT8. I logged the Qs and submitted them to LoTW via Keeper. I have recently looked them up on LoTW and they are there showing that I worked them.
 
I have completed the "Sync" process on Keeper.
 
However, now when I look at them in Keeper, the fields show as follows:
APP_DXKeeper_LoTW_QSL_SENT = Y
APP_DXKeeper_LoTW_QSL_RCVD = R
APP_DXKeeper_LoTWConfirmation = blank
 
I looked at the flow chart but didn't understand it in regard to the above. Am I looking at the wrong fields? Why doesn't Keeper show them as Y for RCVD and Confirmed?
 
Thanks! 73, Rod/w7zrc
 
ps: Something was asked about this on here a few days ago and I have tried to find it, but no luck.


Re: LoTW Confirmed QSOs

Dave AA6YQ
 

+ AA6YQ comments below

From the log page display, right click on the QSO and choose Update from LoTW.

+ After this operation completes, please attach the file

LoTW_UpdateSingle_ADI.txt

+ from DXKeeper's Databases folder to an email message, and send the message to me via

aa6yq (at) ambersoft.com

+ so that I can see what's going on.

73,

Dave, AA6YQ


Re: Reporting question.

Dave AA6YQ
 

+ AA6YQ comments below

I worked DS5USH last night on FT4 and he has confirmed on LoTW. LotW QSL says mode FT4 and my log says FT4 and all matched up. But the LotW status report says MFSK.

Date Time Call Band Mode Station Call Result

2020-03-11 23:03:08 DS5USH 20M MFSK N9LJX new confirmation for Republic of Korea: DIGI

Is this because it is reporting the Parent Mode and not the Submode?

+ When DXKeeper queries LoTW for the status of an FT4 QSO confirmed via LoTW, LoTW correctly reports

<MODE:4>MFSK
<SUBMODE:3>FT4

+ The report that DXKeeper displays after a "Sync LOTW QSLs" function displays the reported mode, as your example above demonstrates.

+ I have extended the next version of DXKeeper to include the submode in import, eQSL sync, and LoTW sync reports.

73,

Dave, AA6YQ


Re: Trouble with 2 Radio Control in Commander

Dave AA6YQ
 

+ AA6YQ comments below

I'm having an issue with Commander controling my two radios.

I'm running a Ten-Tec Orion 2 and a Kenwood TS-890.

Whenever I select the radio button to move from the Orion 2 to the TS-890, after a few seconds the TS-890 goes into transmit. When I go back to the Orion 2 the TS-890 returns to receive and I can operate the Orion 2. If I select the TS-890 again she goes into transmit until I go back to the Orion 2.

If I turn off the TS-890 then select the TS-890 in Commander and turn the TS-890 back on again I can control the TS-890 fine until I swap back & forth between the radios again and the TS-890 will go into transmit.

Any ideas. I must have messed up my Commander configuration.

+ Please do the following:

1. place your TS-890 on a clear frequency, and reduce its RF output power to 0

2. make a screenshot of Commander's Configuration window's MultiRadio tab, and attach it to an email message

3. select the radio button to move from the Orion 2 to the TS-890

4. make a screenshot of Commander's Configuration window's Ports tab, and attach it to the email message you created in step 2

5. select the radio button to move from the TS-890 to the Orion 2

6. send the email message to me via

aa6yq (at) ambersoft.com

73,

Dave, AA6YQ


Re: LoTW Confirmed QSOs

ND9G Mike
 

From the log page display, right click on the QSO and choose Update from LoTW.

Does that change the status?

73,
Mike ND9G


On Thu, Mar 12, 2020 at 8:37 AM Rod Greene via Groups.Io <w7zrc=yahoo.com@groups.io> wrote:
Need a little help regarding LoTW and DXKeeper Codes -

I worked VP8PJ three times, once on each of SSB, CW, and FT8. I logged the Qs and submitted them to LoTW via Keeper. I have recently looked them up on LoTW and they are there showing that I worked them.

I have completed the "Sync" process on Keeper.

However, now when I look at them in Keeper, the fields show as follows:
APP_DXKeeper_LoTW_QSL_SENT = Y
APP_DXKeeper_LoTW_QSL_RCVD = R
APP_DXKeeper_LoTWConfirmation = blank

I looked at the flow chart but didn't understand it in regard to the above. Am I looking at the wrong fields? Why doesn't Keeper show them as Y for RCVD and Confirmed?

Thanks! 73, Rod/w7zrc

ps: Something was asked about this on here a few days ago and I have tried to find it, but no luck.


Re: LoTW Confirmed QSOs

David Bunte
 

Rod -

I think I am near the end of my short list of ideas... but here are two more things to look at:

1:     Make sure the dates under the LoTW sync buttons are the dates on which you invoked those sync actions. If not, click those buttons again and see if the date changes to the current date... if not that is a problem for Dave.

2:     Look at VP8PJ on DXV and see if those three QSOs are still showing 'W', or if they are showing 'C'. 

Tha's all I can think of... I am getting curious to find out what is causing the behavior you are seeing, and what the fix will be.

Again... GL de Dave - K9FN



On Thu, Mar 12, 2020 at 9:48 AM Rod Greene via Groups.Io <w7zrc=yahoo.com@groups.io> wrote:
Yes, I did both sync processes as well as I did one manually by right clicking on it. 




On Thursday, March 12, 2020, 7:42 AM, David Bunte <dpbunte@...> wrote:

Rod -

You say you have completed the sync process... but did you sync both LoTW QSOs AND  LoTW QSLs?

If you only synced LoTW QSOs I believe you would see the results you have.

GL de Dave - K9FN

On Thu, Mar 12, 2020 at 9:37 AM Rod Greene via Groups.Io <w7zrc=yahoo.com@groups.io> wrote:
Need a little help regarding LoTW and DXKeeper Codes -

I worked VP8PJ three times, once on each of SSB, CW, and FT8. I logged the Qs and submitted them to LoTW via Keeper. I have recently looked them up on LoTW and they are there showing that I worked them.

I have completed the "Sync" process on Keeper.

However, now when I look at them in Keeper, the fields show as follows:
APP_DXKeeper_LoTW_QSL_SENT = Y
APP_DXKeeper_LoTW_QSL_RCVD = R
APP_DXKeeper_LoTWConfirmation = blank

I looked at the flow chart but didn't understand it in regard to the above. Am I looking at the wrong fields? Why doesn't Keeper show them as Y for RCVD and Confirmed?

Thanks! 73, Rod/w7zrc

ps: Something was asked about this on here a few days ago and I have tried to find it, but no luck.


Re: LoTW Confirmed QSOs

Rod Greene
 

Yes, I did both sync processes as well as I did one manually by right clicking on it. 




On Thursday, March 12, 2020, 7:42 AM, David Bunte <dpbunte@...> wrote:

Rod -

You say you have completed the sync process... but did you sync both LoTW QSOs AND  LoTW QSLs?

If you only synced LoTW QSOs I believe you would see the results you have.

GL de Dave - K9FN

On Thu, Mar 12, 2020 at 9:37 AM Rod Greene via Groups.Io <w7zrc=yahoo.com@groups.io> wrote:
Need a little help regarding LoTW and DXKeeper Codes -

I worked VP8PJ three times, once on each of SSB, CW, and FT8. I logged the Qs and submitted them to LoTW via Keeper. I have recently looked them up on LoTW and they are there showing that I worked them.

I have completed the "Sync" process on Keeper.

However, now when I look at them in Keeper, the fields show as follows:
APP_DXKeeper_LoTW_QSL_SENT = Y
APP_DXKeeper_LoTW_QSL_RCVD = R
APP_DXKeeper_LoTWConfirmation = blank

I looked at the flow chart but didn't understand it in regard to the above. Am I looking at the wrong fields? Why doesn't Keeper show them as Y for RCVD and Confirmed?

Thanks! 73, Rod/w7zrc

ps: Something was asked about this on here a few days ago and I have tried to find it, but no luck.


Re: LoTW Confirmed QSOs

David Bunte
 

Rod -

You say you have completed the sync process... but did you sync both LoTW QSOs AND  LoTW QSLs?

If you only synced LoTW QSOs I believe you would see the results you have.

GL de Dave - K9FN

On Thu, Mar 12, 2020 at 9:37 AM Rod Greene via Groups.Io <w7zrc=yahoo.com@groups.io> wrote:
Need a little help regarding LoTW and DXKeeper Codes -

I worked VP8PJ three times, once on each of SSB, CW, and FT8. I logged the Qs and submitted them to LoTW via Keeper. I have recently looked them up on LoTW and they are there showing that I worked them.

I have completed the "Sync" process on Keeper.

However, now when I look at them in Keeper, the fields show as follows:
APP_DXKeeper_LoTW_QSL_SENT = Y
APP_DXKeeper_LoTW_QSL_RCVD = R
APP_DXKeeper_LoTWConfirmation = blank

I looked at the flow chart but didn't understand it in regard to the above. Am I looking at the wrong fields? Why doesn't Keeper show them as Y for RCVD and Confirmed?

Thanks! 73, Rod/w7zrc

ps: Something was asked about this on here a few days ago and I have tried to find it, but no luck.


LoTW Confirmed QSOs

Rod Greene
 

Need a little help regarding LoTW and DXKeeper Codes -

I worked VP8PJ three times, once on each of SSB, CW, and FT8. I logged the Qs and submitted them to LoTW via Keeper. I have recently looked them up on LoTW and they are there showing that I worked them.

I have completed the "Sync" process on Keeper.

However, now when I look at them in Keeper, the fields show as follows:
APP_DXKeeper_LoTW_QSL_SENT = Y
APP_DXKeeper_LoTW_QSL_RCVD = R
APP_DXKeeper_LoTWConfirmation = blank

I looked at the flow chart but didn't understand it in regard to the above. Am I looking at the wrong fields? Why doesn't Keeper show them as Y for RCVD and Confirmed?

Thanks! 73, Rod/w7zrc

ps: Something was asked about this on here a few days ago and I have tried to find it, but no luck.


Re: Reporting question.

Paul F6EXV <f6exv@...>
 

FT4 is a sub-mode for MFSK

Le 12/03/2020 à 12:18, Scott Stembaugh a écrit :
I worked DS5USH last night on FT4 and he has confirmed on LoTW.  LotW QSL says mode FT4 and my log says FT4 and all matched up.  But the LotW status report says MFSK.

      Date      Time           Call  Band      Mode       Station Call    Result

  2020-03-11  23:03:08         DS5USH     20M      MFSK          N9LJX    new confirmation for Republic of Korea: DIGI

Is this because it is reporting the Parent Mode and not the Submode?

73,
--scott
------
Scott Stembaugh - N9LJX
radio.n9ljx@... <mailto:radio.n9ljx@...>
http://sites.google.com/site/radion9ljx
--
L'absence de virus dans ce courrier électronique a été vérifiée par le logiciel antivirus Avast.
https://www.avast.com/antivirus


Reporting question.

Scott Stembaugh
 

I worked DS5USH last night on FT4 and he has confirmed on LoTW.  LotW QSL says mode FT4 and my log says FT4 and all matched up.  But the LotW status report says MFSK.

        Date      Time           Call    Band      Mode       Station Call    Result

  2020-03-11  23:03:08         DS5USH     20M      MFSK              N9LJX    new confirmation for Republic of Korea: DIGI


Is this because it is reporting the Parent Mode and not the Submode?

73,
--scott


Trouble with 2 Radio Control in Commander

Steve / W1SMC
 
Edited

I'm having an issue with Commander controling my two radios.

I'm running a Ten-Tec Orion 2 and a Kenwood TS-890.

Whenever I select the radio button to move from the Orion 2 to the TS-890, after a few seconds the TS-890 goes into transmit.  When I go back to the Orion 2 the TS-890 returns to receive and I can operate the Orion 2.  If I select the TS-890 again she goes into transmit until I go back to the Orion 2.

If I turn off the TS-890 then select the TS-890 in Commander and turn the TS-890 back on again I can control the TS-890 fine until I swap back & forth between the radios again and the TS-890 will go into transmit.

Any ideas.  I must have messed up my Commander configuration.


Re: DXLab Commander quarantined with Trojan

Phil NA4M
 

Other than an occasional scan by Malwarebytes Free I also only use W10 Security/Defender and have since system was new. 

Have run DXLab suite also since system was purchased. Never have gotten any "hits" from Defender until after today's update.  

W10 Security/Defender did spit out a message that it quarantined Commander.  I had to "Allow" it before I could get Commander to run,

Here's Defender message:

Severe

Threat blocked 03/11/2020 22:16

Status: Quarantined Quarantined files are in a restricted area where they can't harm your device. They will be removed automatically.

Threat detected: Trojan:Win32/Azden.B!c! Alert level: Severe Date: 03/11/2020 22:16 Category: Trojan Details: This program is dangerous and executes commands from an attacker.

Learn more

Affected items:

file: C:\DXLab Commander C-V Commander1440.exe


Phil NA4M