How can I get to the "HamApps JTAlert" Windows Start Menu Group?  I need to correct the station callsign.  I even tried un installing and reinstalling the app, but even that didn't work.

Please, please.

The JTAlert start menu group (named HamApps JTAlert) is found via clicking the Windows Start icon (bottom left of your screen) then navigating the resulting menu down to the "H" entries. Using the Windows key on your keyboard achieves the same result.

   
   

de Laurie VK3AMA

When I was installing and setting up JTalert, as I was entering my callsign, my cat jumped into my lap hitting the return key before I finished entering the complet call.  I spent a couple of hours last night trying to edit this.  It appears I must go to the JTalert Startup group and run a short cut I will find there.  How do I get to this Start Up Group please?
Thanks,
Jim KF4RX

The JTAlert start menu group (named HamApps JTAlert) is found via clicking the Windows Start icon (bottom left of your screen) then navigating the rustling menu down to the "H" entries. Using the Windows key on your keyboard achieves the same result.

de Laurie VK3AMA

Does anyone have a detailed document on resetting the Alert database?

I exported my primary electronic log file from QRZ and want to use it to populate my Alert database.

Follow up.................

How does one reset a single State on a single band?

The JTAlert Wanted Alert lists are contained within the JTAlert config.sqlite file (please don't try an edit this file manually).
The easiest way to reset all the Wanted Alert lists (along with the different Band/Mode tracking combinations) is to run the Scan Log against your enabled logger when it has been set to a new empty log. If your not using one of the supported loggers, than set JTAlert to use ADIF logging with an empty ADIF log file and run the Scan Log against that.

Manually setting/unsetting a State on a single Band is easy, just select the Band and mode and untick the State, BUT be warned that any manual changes you make will be lost if your run a Scan Log.

de Laurie VK3AMA

Where does the feed for the 2 boxes, AZIMUTH and DX GRID come from? Pressing the lookup key does not do anything. I am scratching my head on this one

Scott

N2SAB

No idea, but since these are WSJT-X specific most likely the answer is contained within the very comprehensive WSJT-X documentation/Help.

de Laurie VK3AMA

Three issues with JTAlert Ver 2.15.3:

1)  Same here - no audio.  Changed sound devices - no audio.  Checked microphone permissions - no audio. Ran troubleshooting diagnostics on audio system (from drive inputs to speaker) - no audio. 

2) Online XML Callbook information does not populate the "Name," "QTH," and "Grid" on every instance of a callsign being selected.  Information populates the blocks about 10% of the time; information needs to be manually inserted into blocks 90% of the time.

3) Callsign information is not routed to (DXLab Suite's) Pathfinder for information look-up until after a QSO has been logged (and info goes to DXKeeper logging software).

Reverted back to JTAlert Ver 2.15.0 - the most trusted version of the Ver 2.15.x series.

73

Paul  DU2FIS / K8SQ

Paul,

All the problems you list indicate failed (or blocked) communication between the JTAlert.exe process and the JTALertV2.Manager.exe process (which is new as of 2.15.1). The JTALertV2.Manager.exe process (from the JTAlertV3 project) replaces the old plugin manager and its 15 plugin files. The functions handled by the Manager are... (taken form the 2.15.1 Release notes)

         - Playing alert sounds.
         - XML lookups (QRZ and HamQTH)
         - Weblog uploads (QRZ, Eqsl, HrdLog, ClubLog and HamQTH)
         - Uploading of Spots to HamSpots.
         - Downloading of Band Activity data from HamSpots
         - Managing sending/receiving of Text messages and Callsigns online checks.
         - User defined Alerting.
         - JTAlert session files cleanup.
         - Program updates available checks.
         - All DXLab DDE based functions. This includes DXK, DXV and PF callsign
            lookup, DXV rotator control and local spotting to SC.

The most likely cause of the comms failure are a UDP port collision with an existing running process on your PC or Protection software interference.
I can't help if it is your protection software, but for a port collision I have redesigned JTAlert to use dynamically assigned ports (provided by the OS and guaranteed to be free and not in use by another process). Check your email as I have sent you a link to this latest build of JTAlert.

de Laurie VK3AMA

Three issues with JTAlert Ver 2.15.3:

1)  Same here - no audio.  Changed sound devices - no audio.  Checked microphone permissions - no audio. Ran troubleshooting diagnostics on audio system (from drive inputs to speaker) - no audio. 

2) Online XML Callbook information does not populate the "Name," "QTH," and "Grid" on every instance of a callsign being selected.  Information populates the blocks about 10% of the time; information needs to be manually inserted into blocks 90% of the time.

3) Callsign information is not routed to (DXLab Suite's) Pathfinder for information look-up until after a QSO has been logged (and info goes to DXKeeper logging software).

Reverted back to JTAlert Ver 2.15.0 - the most trusted version of the Ver 2.15.x series.

73

Paul  DU2FIS / K8SQ

I think WSJT-X calculates them based on the grid squares. There was a discussion about 2 yesrs ago on the WSJT-X yahoo gropu about the program crashing if both stations were in the same square
John KA5BJC

Does anyone have a detailed document on resetting the Alert database?

I exported my primary electronic log file from QRZ and want to use it to populate my Alert database.

Follow up.................

How does one reset a single State on a single band?

2.15.3 Sound does not work for me.

I tried changing the sound device and that made no difference. I have gone back to 2.15.2 and that is working !

Hi Laurie,

I have Logging disabled and am tracking Wanted DXCC By Individual Band and Any WSJT-X Mode. I am noticing that sometimes a new DXCC for a particular band comes up in grey rather than a yellow alert. I think this happens if I have worked the DX station before on another band. Sometimes, I have the opposite, a yellow alert for a DXCC that I have already set to Not Wanted for that band.

Any ideas?

I have looked for help on the Worked B4 settings but cannot find any info on them in the Help file. Is there another source for this information?

Thanks,
Graham VK3GA
V2.15.3

Loaded JTAlert update Ver 2.15.3.  Now have no audio alert.  It was working fine on previous version.

I've checked all setting in the Sounds menu and Sound ON is showing in the tool bar.

How can I get to the "HamApps JTAlert" Windows Start Menu Group?  I need to correct the station callsign.  I even tried un installing and reinstalling the app, but even that didn't work.

Please, please.

Dear Hamapps,
When I was installing and setting up JTalert, as I was entering my callsign, my cat jumped into my lap hitting the return key before I finished entering the complet call.  I spent a couple of hours last night trying to edit this.  It appears I must go to the JTalert Startup group and run a short cut I will find there.  How do I get to this Start Up Group please?
Thanks,
Jim KF4RX