Topics

locked States-Wanted Boxes Auto-Untick?


Patrick Hung
 

I just began working on my WAS award, and so have ticked the numerous boxes for states that I still need on the States Wanted page of JTAlert.

I had thought that once I complete a QSO with a station from a wanted state, JTAlert would automatically "untick" that box for me, or turn off that specific alert for that particular band, so that stations from the same state won't get highlighted again. To my disappointment, it doesn't do that; I've had to remember the states I just completed, and manually turn off the alert. Is this how it's supposed to work?

Thanks.
--
Patrick - W2TAR


Mike Rhodes
 

Thinking that doesn't happen until that state is confirmed. You are linked to your log aren't you?

Mike / W8DN

On 11/15/2020 7:29 PM, Patrick Hung wrote:
I just began working on my WAS award, and so have ticked the numerous boxes for states that I still need on the States Wanted page of JTAlert.

I had thought that once I complete a QSO with a station from a wanted state, JTAlert would automatically "untick" that box for me, or turn off that specific alert for that particular band, so that stations from the same state won't get highlighted again. To my disappointment, it doesn't do that; I've had to remember the states I just completed, and manually turn off the alert. Is this how it's supposed to work?

Thanks.
--
Patrick - W2TAR


Alfred Reeves
 

I think you have to run "Rebuild Alert Database" to have the box  "untick"


Dave Cole
 

The contact needs to confirm, AND, you need to rebuild the database... Only then will it count...Both commands are in the pull down under settings.

73, and thanks,
Dave (NK7Z)
https://www.nk7z.net
ARRL Volunteer Examiner
ARRL Technical Specialist, RFI
ARRL Asst. Director, NW Division, Technical Resources

On 11/15/20 4:29 PM, Patrick Hung wrote:
I just began working on my WAS award, and so have ticked the numerous boxes for states that I still need on the States Wanted page of JTAlert.
I had thought that once I complete a QSO with a station from a wanted state, JTAlert would automatically "untick" that box for me, or turn off that specific alert for that particular band, so that stations from the same state won't get highlighted again. To my disappointment, it doesn't do that; I've had to remember the states I just completed, and manually turn off the alert. Is this how it's supposed to work?
Thanks.
--
Patrick - W2TAR


Patrick Hung
 

Mike and Alfred,

Thanks to you both for your input.

I do have JTAlert logging successfully, as a dialog box pops up to let me know of that after each QSO.

I think that Alfred may be right in the need to run a "Rebuild" - I'll test that and report back.
--
Patrick - W2TAR


Michael Black
 

As somebody already said the state (or country) has to be confirmed to not alert.  And some operators are slow about uploading their logs.

If you're working WAS you might have some fun with my LOTWQSL program that you'll find on my QRZ page.  It's easy to see the LOTW updates and if you need to update your log and JTAlert and it shows maps and a grid view of your status.  It also tracks DXCC and DXCC Mixed numbers.

Mike W9MDB




On Sunday, November 15, 2020, 06:30:03 PM CST, Patrick Hung <pathung@...> wrote:


I just began working on my WAS award, and so have ticked the numerous boxes for states that I still need on the States Wanted page of JTAlert.

I had thought that once I complete a QSO with a station from a wanted state, JTAlert would automatically "untick" that box for me, or turn off that specific alert for that particular band, so that stations from the same state won't get highlighted again. To my disappointment, it doesn't do that; I've had to remember the states I just completed, and manually turn off the alert. Is this how it's supposed to work?

Thanks.
--
Patrick - W2TAR


Patrick Hung
 

Thanks Dave and Mike - by "confirming", you mean confirming via LOTW? If that's the case, I see how someone could take a while (or never) uploading logs.

Dave mentioned Confirmation in the JTAlert Settings pull-down menu - can you clarify where, exactly?

I'll take a look at LOTWQSL - thanks.

--
Patrick - W2TAR


HamApps Support (VK3AMA)
 

On 16/11/2020 11:29 am, Patrick Hung wrote:
I just began working on my WAS award, and so have ticked the numerous boxes for states that I still need on the States Wanted page of JTAlert.

I had thought that once I complete a QSO with a station from a wanted state, JTAlert would automatically "untick" that box for me, or turn off that specific alert for that particular band, so that stations from the same state won't get highlighted again. To my disappointment, it doesn't do that; I've had to remember the states I just completed, and manually turn off the alert. Is this how it's supposed to work?

Thanks.
--
Patrick - W2TAR

JTAlert, by default, does not automatically remove an alerted entity, like a State, by simply working a Station. For most users, they require some sort of QSL confirmation before they are happy that an  entity is no-longer needed and no-longer alerted. You set the QSL requirements in the Rebuild Alert Database section of the Settings window. Alert types have independent confirmation settings, so you could have Dxcc & State set to require LoTW confirmations while Grid & Prefix alerts set to only require a worked status (no qsl needed).

If your truly want to have a State automatically removed from your Alerts list by simply working a Station, there is no need to run the Rebuild Database operation. You can just set the "Auto clear triggered Alert entity after logging" under settings for the Alert. This is available for all Alert types.

   


de Laurie VK3AMA



Patrick Hung
 

Laurie,

Thanks for the very clear explanation; I've chosen to require confirmation prior to deleting a State alert. There are three checkboxes to the right of "Confirmation": Card, eQSL, LoTW - with all three checked to mean that any of the three would suffice?
--
Patrick - W2TAR


HamApps Support (VK3AMA)
 

On 16/11/2020 6:51 pm, Patrick Hung wrote:
There are three checkboxes to the right of "Confirmation": Card, eQSL, LoTW - with all three checked to mean that any of the three would suffice?

Yes. Its an "OR" operation.

eg. If all three are enabled, that indicates that "Card" OR "Lotw" OR "Eqsl" confirmed QSOs found in the Log during the scan are candidates for considering the Entity as no longer needed.

de Laurie VK3AMA


Jim N6VH
 


On 11/15/2020 11:51 PM, Patrick Hung wrote:
Laurie,

Thanks for the very clear explanation; I've chosen to require confirmation prior to deleting a State alert. There are three checkboxes to the right of "Confirmation": Card, eQSL, LoTW - with all three checked to mean that any of the three would suffice?
--
Patrick - W2TAR
_._,_._,_


Patrick,

If you are interested in the ARRL WAS (or DXCC, etc) award, then don't tick "eQSL". The eQSL confirmations are not valid for ARRL awards. If you are interested in the eQSL awards, that's a different matter.

Incidentally, getting WAS confirmed on LOTW is fairly easy. I have 8 band WAS, all confirmed on LOTW.

73,

Jim N6VH


Patrick Hung
 

Thanks for the heads-up, Jim, I'll de-selecting eQSL.
--
Patrick - W2TAR


Patrick Hung
 

I'm still having issues with confirmed Wanted States removed from my alert list.

I have the Rebuild Database -> LOTW box selected, but continue to see states that I've worked, and LoTW showing no longer needed (confirmed?), highlighted in yellow in the Decode Window. 

For example, LoTW shows that I need six states for FT8; JTAlert still has tens of states checked as needed. 

I'm currently using Log4OM2 (set up in JTALERT settings), which is working well with the radio, as well as WSJT-X and JTALERT. When I close Log4OM2, new QSOs are successfully uploaded to LoTW automatically (I suppose that it downloads new confirmations from LoTW at the same time). Is JTALERT supposed to use these newly-downloaded confirmations on Log4OM2 to turn off the appropriate state alerts?

Lastly, I ran Rebuild Database to see if that was the missing piece - it had the opposite effect, the number of needed states increased. It looks like I'll have to manually uncheck the needed states, by band and mode... need some help, please!
--
Patrick - W2TAR


Michael Black
 

It sounds like JTAlert isn't pointing to the same database as Log4OM.

Double-check the path in the lower right corner of Log4OM2 with the path in JTAlert.

Send a snapshot of each.

Mike W9MDB




On Sunday, November 29, 2020, 09:26:49 PM CST, Patrick Hung <pathung@...> wrote:


I'm still having issues with confirmed Wanted States removed from my alert list.

I have the Rebuild Database -> LOTW box selected, but continue to see states that I've worked, and LoTW showing no longer needed (confirmed?), highlighted in yellow in the Decode Window. 

For example, LoTW shows that I need six states for FT8; JTAlert still has tens of states checked as needed. 

I'm currently using Log4OM2 (set up in JTALERT settings), which is working well with the radio, as well as WSJT-X and JTALERT. When I close Log4OM2, new QSOs are successfully uploaded to LoTW automatically (I suppose that it downloads new confirmations from LoTW at the same time). Is JTALERT supposed to use these newly-downloaded confirmations on Log4OM2 to turn off the appropriate state alerts?

Lastly, I ran Rebuild Database to see if that was the missing piece - it had the opposite effect, the number of needed states increased. It looks like I'll have to manually uncheck the needed states, by band and mode... need some help, please!
--
Patrick - W2TAR


Dave Garber
 

I found that thanks to qrz several worked states got changed by incorrectly data on the site.   Once corrected it stopped asking to update old records. As stated make the log file names match.  And is would believe program and jtalert.   Gridtracker may be missing info in its log.


On Sun., Nov. 29, 2020, 11:22 p.m. Michael Black via groups.io, <mdblack98=yahoo.com@groups.io> wrote:
It sounds like JTAlert isn't pointing to the same database as Log4OM.

Double-check the path in the lower right corner of Log4OM2 with the path in JTAlert.

Send a snapshot of each.

Mike W9MDB




On Sunday, November 29, 2020, 09:26:49 PM CST, Patrick Hung <pathung@...> wrote:


I'm still having issues with confirmed Wanted States removed from my alert list.

I have the Rebuild Database -> LOTW box selected, but continue to see states that I've worked, and LoTW showing no longer needed (confirmed?), highlighted in yellow in the Decode Window. 

For example, LoTW shows that I need six states for FT8; JTAlert still has tens of states checked as needed. 

I'm currently using Log4OM2 (set up in JTALERT settings), which is working well with the radio, as well as WSJT-X and JTALERT. When I close Log4OM2, new QSOs are successfully uploaded to LoTW automatically (I suppose that it downloads new confirmations from LoTW at the same time). Is JTALERT supposed to use these newly-downloaded confirmations on Log4OM2 to turn off the appropriate state alerts?

Lastly, I ran Rebuild Database to see if that was the missing piece - it had the opposite effect, the number of needed states increased. It looks like I'll have to manually uncheck the needed states, by band and mode... need some help, please!
--
Patrick - W2TAR


Jim N6VH
 


On 11/29/2020 7:26 PM, Patrick Hung wrote:
I'm still having issues with confirmed Wanted States removed from my alert list.

I have the Rebuild Database -> LOTW box selected, but continue to see states that I've worked, and LoTW showing no longer needed (confirmed?), highlighted in yellow in the Decode Window. 

For example, LoTW shows that I need six states for FT8; JTAlert still has tens of states checked as needed. 

I'm currently using Log4OM2 (set up in JTALERT settings), which is working well with the radio, as well as WSJT-X and JTALERT. When I close Log4OM2, new QSOs are successfully uploaded to LoTW automatically (I suppose that it downloads new confirmations from LoTW at the same time). Is JTALERT supposed to use these newly-downloaded confirmations on Log4OM2 to turn off the appropriate state alerts?

Lastly, I ran Rebuild Database to see if that was the missing piece - it had the opposite effect, the number of needed states increased. It looks like I'll have to manually uncheck the needed states, by band and mode... need some help, please!
--
Patrick - W2TAR
_._,_._,_


Patrick,

Log4OM2 does not automatically download from LOTW. You have to do that in QSL Manager. If you have not done a manual download, then those QSOs will still show as not confirmed. Do a manual download, and then do a Rebuild Database. That should work for you.

73,

Jim N6VH


Patrick Hung
 

Thanks for the input and comments. 

As Michael suggested, I checked the path for the Log4OM2 database, and JTALERT's is the same as that shown at the bottom of the Log4OM window: User/user/onedrive/documents...

I attempted a confirmation download on Log4OM2, but it found nothing to download... since "Last Download", or since 7/1/2020. I've been logging new QSOs everyday, and it's reflected on LoTW soon after I close Log4OM2 at the end of the day. 


Best regards,

Patrick Hung

--
Patrick - W2TAR


Michael Black
 

Don't use OneDrive....I've seen other users have problems with it.

Log4OM does upload automatically but does not download automatically.

If you didn't get anything with a LOTW last download date of 7/1/2020 something is horribly wrong.

Mike W9MDB


On Monday, November 30, 2020, 12:04:41 PM CST, Patrick Hung <pathung@...> wrote:


Thanks for the input and comments. 

As Michael suggested, I checked the path for the Log4OM2 database, and JTALERT's is the same as that shown at the bottom of the Log4OM window: User/user/onedrive/documents...

I attempted a confirmation download on Log4OM2, but it found nothing to download... since "Last Download", or since 7/1/2020. I've been logging new QSOs everyday, and it's reflected on LoTW soon after I close Log4OM2 at the end of the day. 


Best regards,

Patrick Hung

--
Patrick - W2TAR


Patrick Hung
 

My last download was conducted on Nov. 15 or thereabouts, and a number of confirmations were downloaded then, IIRC. Since then, I've tweaked Log4OM2 this way and that, and may have fouled something up. All my "Sent" were set to "Requested"... I don't know what else to look at/set.

I'll try to relocate the database to the hard drive and see if that makes a difference.

Back to JTALERT, does the program grab confirmation data from the Log4OM2 database, or directly from LoTW? 
--
Patrick - W2TAR


Michael Black
 

JTAlert uses your database.

Uploads change QSOs to "Requested"  -- confirmed downloads change them to "Received".

If you go to my QRZ page you'll find LOTWQSL which will also download LOTW confirmations...it's a quick check to see if you need to do Log4OM and JTAlert updates as those matter most when WAS or DXCC updates occur which my program makes easy to see.

Mike W9MDB




On Monday, November 30, 2020, 12:20:27 PM CST, Patrick Hung <pathung@...> wrote:


My last download was conducted on Nov. 15 or thereabouts, and a number of confirmations were downloaded then, IIRC. Since then, I've tweaked Log4OM2 this way and that, and may have fouled something up. All my "Sent" were set to "Requested"... I don't know what else to look at/set.

I'll try to relocate the database to the hard drive and see if that makes a difference.

Back to JTALERT, does the program grab confirmation data from the Log4OM2 database, or directly from LoTW? 
--
Patrick - W2TAR