I think I know the answer, but will ask anyway.

Is there any way to select audio alerts by band?

I have audio alerts for DXCC, Zone, Continent, etc on all bands. Also have alerts turned on for Prefix, Grid on all bands.

Audio grid alerts on HF bands would be fairly constant and annoying. I prefer just to see the alert color.

However, on VHF, I would like to hear alerts, especially if I am away from the desk. But I can't find any settings by band for audio.

Not a big deal, but can always hope!

Thanks for all the great work! 

73
Paul, AC9O

Simplest solution is to click the "Sound" menu to "Sound OFF" to mute the sounds when on HF and turn them back on when on VHF.

If your running multiple JTAlert instances, say one on HF and one on VHF, then turn the Sounds off (via the main window menu) on the HF instance and leave the Sounds on for the VHF instance.

There is also the opinion to restrict Alert sounds to specific UTC hours.

de Laurie VK3AMA

I'm a little creeped out by how you know what version of WSJT I'm using since I didn't say.

While you didn't mention your WSJT-X version, but did specify your JTAlert version, (why is that?) your described symptoms matched those of other users using very old WSJT-X versions, specifically 2.0.1. A quick check on PSKReporter confirmed my initial thoughts.

   

de Laurie VK3AMA

The station calling CQ from JO21 is alerted as NEW GRID on 4m.
In my logbook I found 4 other stations from this square which verified the
contact via LoTW.
Same result for other stations calling CQ from JO21 and JO31.

As 4m is a new band for JTAlert, all the 4m specific wanted lists are empty.
You need to run a "Scan Log & Rebuild" to get those internal lists updated with your 4m Log data.

de Laurie VK3AMA

For more than a month my JTAlert cannot find any of my previous contacts. It's logs fine to HRDLogbook and displays the worked contact alert colors for the current session. However, when I open a new session there at no previous contacts referenced or shown in the JTAlert screen.

I do not find the %localappdata%\HamApps\VE2ESU\session\JTAlertX\HRDLogbook.trace file on my computer. 

How do I add this file to the computer?

OM,

The HRDLogbook.trace file is always created and updated when you have HRD logging enabled in JTAlert.

Your group membership suggests that "VE2ESU" is not your callsign. Try changing "VE2ESU" to the Station Callsign used in JTAlert.

de Laurie VK3AMA

For more than a month my JTAlert cannot find any of my previous contacts. It's logs fine to HRDLogbook and displays the worked contact alert colors for the current session. However, when I open a new session there at no previous contacts referenced or shown in the JTAlert screen.

I do not find the %localappdata%\HamApps\VE2ESU\session\JTAlertX\HRDLogbook.trace file on my computer. 

How do I add this file to the computer?

I think I know the answer, but will ask anyway.

Is there any way to select audio alerts by band?

I have audio alerts for DXCC, Zone, Continent, etc on all bands. Also have alerts turned on for Prefix, Grid on all bands.

Audio grid alerts on HF bands would be fairly constant and annoying. I prefer just to see the alert color.

However, on VHF, I would like to hear alerts, especially if I am away from the desk. But I can't find any settings by band for audio.

Not a big deal, but can always hope!

Thanks for all the great work! 

73
Paul, AC9O

On 05/06/2020 15:08, Ron / W4MMP via groups.io wrote:

Everyone using PSK Reporter knows what version of WSJT you are running.

RR, and every web site knows what browser and version you are using, also every email server knows what email client and version you are using. There's nothing suspicious going on here, you consent to using an Internet service, you give them some information. At least no-one is turning you into a product for profit by monetizing this information ;)

73
Bill
G4WJS.



--
73
Bill
G4WJS.

Everyone using PSK Reporter knows what version of WSJT you are running.


73,
Ron

On 05/06/2020 14:44, Bob Craig wrote:

I'm a little creeped out by how you know what version of WSJT I'm using since I didn't say.

Bob,

it is your choice as to whether you upload spots to HamSpots, if you don't like helping the community with spot information you can turn that facility back off. I believe it is off by default so I think you must have chosen to enable it at some point.



--
73
Bill
G4WJS.

I'm a little creeped out by how you know what version of WSJT I'm using since I didn't say.

I went to your website to retrieve a new callsign database. I availed myself of the opportunity to upgrade to 2.16.6.

I didn't know it would trigger a cascade

Sorry..

Laurie,

TU for the Beta Version.

This morning we had a short opening on 4m.

ALERT Priority was set as follows:

- WANTED GRID
- WANTED DXCC
- CQ

The screen short shows what I found.

The station calling CQ from JO21 is alerted as NEW GRID on 4m.
In my logbook I found 4 other stations from this square which verified the
contact via LoTW.
Same result for other stations calling CQ from JO21 and JO31.

Few minutes later a station from IO75 was alerted as NEW GRID. This was
okay, because I never logged a station from this sqaure on 4m.

The B4 alerts are okay.

I had quick look on 20m and checked about 20 alterted WANTED GRID´s manually
against my log. Found no error. These GRID´s have been never worked B4 oder
the worked B4 were not verfied via LoTW or QSL card.

My working environment:
- Windows 10, 64 bit
- WSJT-X 2.2.0 GA 64 bit
- JTAlert 2.16.6
- HRD Log 6.7.0.277, logging via JTAlert

Hope this findings are helpful to you.

If you want some more tests please let me know.

73



______________
Norbert Graf
D D 3 K F

-----Ursprüngliche Nachricht-----
Von: Support@HamApps.groups.io <Support@HamApps.groups.io> Im Auftrag von
HamApps Support (VK3AMA)
Gesendet: Freitag, 5. Juni 2020 02:05
An: Support@HamApps.groups.io
Betreff: Re: [HamApps] JTAlert missing "bands" = 4m-band


Here you go, the latest JTAlert build with full 4m support.

There was a lot of code changes so I might have broken something.
Please provide some feedback regarding the changes. Do they work correctly,
is anything broken or missing, etc?

https://dnl.HamApps.com/Beta/JTAlert.2.16.6.build.0008.Beta.Setup.exe

de Laurie VK3AMA

Scott

if you have an issues with that setup or my instruction feel to email me. My email is good on QRZ.

73

Todd (N3PKJ)
Meadville, Pa.
EN91

Decodes window 2.16.6 no longer populates.
View says 0 Recs. Set for 2,000 records.
Worked perfectly since day one.
I use it to see the SP column for trends where to point the beam.

Reboot did not help.
Reinstall did not help.

The main window 16 columns populate and voice announcements are working properly.

Need help.

73,

Bud W3LL
W3LL@...

You will need to delete the Decodes database file.

• Stop JTAlert
• Using Windows File Explorer navigate to %localappdata%\HamApps\JTAlert\W3LL\Decode\
• Delete any files with names starting "decodes".
• Start JTAlert

de Laurie VK3AMA

Decodes window 2.16.6 no longer populates.
View says 0 Recs. Set for 2,000 records.
Worked perfectly since day one.
I use it to see the SP column for trends where to point the beam.

Reboot did not help.
Reinstall did not help.

The main window 16 columns populate and voice announcements are working properly.

Need help.

73,

Bud W3LL
W3LL@...

Here you go, the latest JTAlert build with full 4m support.

There was a lot of code changes so I might have broken something.
Please provide some feedback regarding the changes. Do they work correctly, is anything broken or missing, etc?

https://dnl.HamApps.com/Beta/JTAlert.2.16.6.build.0008.Beta.Setup.exe

de Laurie VK3AMA

I have just updated from 2.12.8 to 2.16.6. Everything is great with one exception:

The JTAlert panel quits displaying callsigns after 5-12 minutes have elapsed since program start. 

The behavior at failure is WSJT (FT8) will complete a decode but the JTAlert callsign display will not update and continue to display the callsigns from the previous decode cycle.
At the 2nd WSJT decode after this failure the JTAlert display will be cleared but nothing will be displayed even though WSJT continues to decode and display normally.
Closing, then restarting the JTAlert/WSJT combo will restore function again temporarily.

There is no correlation between number of calls decoded and the failure point. That is, on 20 meters with a busy band, it can take as long as 12 minutes to fail while on 10m during an E opening it has failed after only 5 minutes of 1 or 2 calls decoded per 15 second cycle.
73, Bob, K8RC

Bob,

Update your WSJT-X version, 2.0.1 is rather old.

de Laurie VK3AMA

I have just updated from 2.12.8 to 2.16.6. Everything is great with one exception:

The JTAlert panel quits displaying callsigns after 5-12 minutes have elapsed since program start. 

The behavior at failure is WSJT (FT8) will complete a decode but the JTAlert callsign display will not update and continue to display the callsigns from the previous decode cycle.
At the 2nd WSJT decode after this failure the JTAlert display will be cleared but nothing will be displayed even though WSJT continues to decode and display normally.
Closing, then restarting the JTAlert/WSJT combo will restore function again temporarily.

There is no correlation between number of calls decoded and the failure point. That is, on 20 meters with a busy band, it can take as long as 12 minutes to fail while on 10m during an E opening it has failed after only 5 minutes of 1 or 2 calls decoded per 15 second cycle.
73, Bob, K8RC

Good Morning,

Trying to help a friend set up his N1MM and WSJT-X for field day.

We have done on air testing and all works well except for when his prompt to log window opens, it does not have his report sent filled in in the "Exch Sent" area at the bottom.

I have called CQ FD, he has answered me, I receive his FD exchange, he receives mine, 73's are sent. When my prompt to log qso window opens, both my sent and received exchanges are there.  His sent exchange is blank.

What are we missing here?

We have closed both WSJT-X and N1MM and restarted them several times and this keeps happening.

Bob, K2RET

Hi Bob,

this is not a JTAlert issue.

Is your QSO partner using the Tab 1 messages in WSJT-X?

--
73
Bill
G4WJS.