¿ªÔÆÌåÓý

ctrl + shift + ? for shortcuts
© 2025 Groups.io

Logging FT8 QSO no LotW update


 

When I log an FT8 QSO now it does not update the LotW membership status of the station worked.

Thanks
73
Kent
N6WT


 

+ AA6YQ comments below

When I log an FT8 QSO now it does not update the LotW membership status of the station worked.

+ Are you using JTAlert, or the direct interoperation between WSJT-X and DXLab?

73,

Dave, AA6YQ


 

Dave

With JTAlert.

Thanks
73
Kent
N6WT


On Mon, Feb 24, 2020 at 10:20 PM Dave AA6YQ <aa6yq@...> wrote:
+ AA6YQ comments below

When I log an FT8 QSO now it does not update the LotW membership status of the station worked.

+ Are you using JTAlert, or the direct interoperation between WSJT-X and DXLab?

? ? ? 73,

? ? ? ? ? ? Dave, AA6YQ






 

* more AA6YQ comments below

With JTAlert.

* On the "JTAlertX Settings" window, use the panel on the left to navigate to the "LoTW/eQSL(AG) Flags" page in the Alerts/"Miscellaneous Alerts" section.

* Note the requirement for the presence of the "HamApps Callsign Database" at the top of the panel on the right.

* In the "Enable Membership Indicators" section of the panel on the right, check the "Enable LoTW Stripe/Flag" box. I assume that JTAlertX will then include LoTW membership status in each QSO it logs to DXKeeper. If that's not the case, we'll have to ask Laurie VK3AMA for help.

73,

Dave, AA6YQ


 

Dave

I have the latest database?installed and "Enable LotW Stripe/Flag" checked.?

It happened?a couple of times before but the last time it was on VP8PJ so the JTAlerts database?may not be updated correctly.

Thanks
73
Kent
N6WT


On Tue, Feb 25, 2020 at 9:04 AM Dave AA6YQ <aa6yq@...> wrote:
* more AA6YQ comments below

With JTAlert.

* On the "JTAlertX Settings" window, use the panel on the left to navigate to the "LoTW/eQSL(AG) Flags" page in the Alerts/"Miscellaneous Alerts" section.

* Note the requirement for the presence of the "HamApps Callsign Database" at the top of the panel on the right.

* In the "Enable Membership Indicators" section of the panel on the right, check the "Enable LoTW Stripe/Flag" box. I assume that JTAlertX will then include LoTW membership status in each QSO it logs to DXKeeper. If that's not the case, we'll have to ask Laurie VK3AMA for help.

? ? ? ? ? 73,

? ? ? ? ? ? ? ? ? ? Dave, AA6YQ






 

+ AA6YQ comments below

I have the latest database installed and "Enable LotW Stripe/Flag" checked.

It happened a couple of times before but the last time it was on VP8PJ so the JTAlerts database may not be updated correctly.

+ When you're logging QSOs via an external application like JTAlert or MultiPSK, it is responsible for all of the content of the QSO being logged.

+ DXView does provide a lookup service that such applications can use to determine a callsign's LoTW participation, among other things.

73,

Dave, AA6YQ


 

¿ªÔÆÌåÓý

On 26/02/2020 5:26 am, Kent Olsen wrote:
It happened?a couple of times before but the last time it was on VP8PJ so the JTAlerts database?may not be updated correctly.

JTAlert doesn't include non-active Lotw participating callsigns in the database. VP8PJ last uploaded to LoTW ~11 years ago. 11 years is outside the threshold of 3 years? uses to strip non-active callsigns. Once VP8PJ starts uploading to LoTW and his upload date is adjusted in the official Lotw membership file than The callsign will appear in the next JTAlert Callsign database published after that date.

de Laurie VK3AMA


 

Laurie

That explains it.

Thanks
73
Kent
N6WT


On Tue, Feb 25, 2020 at 11:09 AM HamApps Support (VK3AMA) <vk3ama.ham.apps@...> wrote:
On 26/02/2020 5:26 am, Kent Olsen wrote:
It happened?a couple of times before but the last time it was on VP8PJ so the JTAlerts database?may not be updated correctly.

JTAlert doesn't include non-active Lotw participating callsigns in the database. VP8PJ last uploaded to LoTW ~11 years ago. 11 years is outside the threshold of 3 years? uses to strip non-active callsigns. Once VP8PJ starts uploading to LoTW and his upload date is adjusted in the official Lotw membership file than The callsign will appear in the next JTAlert Callsign database published after that date.

de Laurie VK3AMA