Date   

locked Re: 13 Colonies

Jim Cooper
 

On 2 Jul 2020 at 20:40, Paul N. Gayet AA1SU wrote:

I guess, I'll just have to keep the feature turned
on, and keep track of them on paper,
There's ONLY a dozen and a half to keep track of !!


locked Re: 13 Colonies

Paul N. Gayet AA1SU
 

Al,
This is okay if you want to work a station just once.
I'm working them on as many bands as possible this week.
I don't see a way to keep the call from popping up as a wanted call after working them.
I guess, I'll just have to keep the feature turned on, and keep track of them on paper, like Scott N2SAB.
73
Paul N. Gayet  AA1SU
ARRL Vermont Section Manager
Fists #4028
On 7/1/2020 11:47 PM, Alfred Reeves wrote:

This is the way I have the 13 Colonies alert.
1. Open "Settings" "Wanted Call Signs"
2. Check "Enable Wanted Callsign Alert"
3. Under "Options" check "Alert when decoded Callsign worked B4"
4. In the "Alert Callsigns" box enter the callsigns of the 15 "13 Colonies stations" ie K2A, K2B, etc.
5. Set the "Alert Color" to your preference.
6. Click the "Save" box at the lower right.
7. Close out.

As the 13 colonies stations are decoded they will show up colored to the preference you set even if you worked them B4 ie last year.  As you work the stations you can go and remove them from the "Alert Callsigns" box.

That's way I have been working them and it's very helpful.

Al
W1JHU 


locked Re: Worked B4 not working

Laurie, VK3AMA
 

On 3/07/2020 1:18 am, Paul AC9O wrote:
I am still having the issue where someone I just worked keeps alerting. Here's an example of KF7JZ still highlighted and it's in the worked QSO popup.
The Cyan colored grid indicates a Grid Alert was generated. Check your log and see if the last QSO with that station included a Grid and if it matches the grid decoded. If they are different or the Log record doesn't have Grid, then JTAlert will generate a Grid Alert if you have the "Ignore Gridsquare" option unchecked for the B4 Alert settings. That setting by default is ticked, if it is now  unticked than you would have made that change sometime in the past. Also check the Grid Alert settings and see if you have the "Alert when decoded Callsign worked B4" option ticked.

de Laurie VK3AMA


locked Re: Worked B4 not working

Michael Black
 

View/Alert Types Summary Window

That should show you.

Mike W9MDB




On Thursday, July 2, 2020, 05:09:26 PM CDT, Larry Banks via groups.io <larryb.w1dyj@...> wrote:


What alert is Blue?  Perhaps worked but not confirmed?

73 -- Larry -- W1DYJ

 
From: Paul AC9O
Sent: Thursday, July 02, 2020 11:18
Subject: [HamApps] Worked B4 not working
 
Hi Laurie,

I am still having the issue where someone I just worked keeps alerting. Here's an example of KF7JZ still highlighted and it's in the worked QSO popup.

I am using the latest version of all programs.



Thanks,
Paul, AC9O


locked Re: Worked B4 not working

Larry Banks
 

What alert is Blue?  Perhaps worked but not confirmed?

73 -- Larry -- W1DYJ

 

From: Paul AC9O
Sent: Thursday, July 02, 2020 11:18
Subject: [HamApps] Worked B4 not working
 
Hi Laurie,

I am still having the issue where someone I just worked keeps alerting. Here's an example of KF7JZ still highlighted and it's in the worked QSO popup.

I am using the latest version of all programs.



Thanks,
Paul, AC9O


locked Re: Worked B4 not working

Dave Garber
 

check your log or adi file to see if the grid squares match


Dave Garber
VE3WEJ / VE3IE


On Thu, Jul 2, 2020 at 11:18 AM Paul AC9O <pphiliphome@...> wrote:
Hi Laurie,

I am still having the issue where someone I just worked keeps alerting. Here's an example of KF7JZ still highlighted and it's in the worked QSO popup.

I am using the latest version of all programs.



Thanks,
Paul, AC9O


locked Re: Callsign Display Window Timing

Jim Cooper
 

Use the DECODES display window ... all the
entries stay there, it gives you much more info,
and you can click and double-click there just
like anywhere else.

On 2 Jul 2020 at 12:57, ve7gtc wrote:

This is a minor annoyance but I
can't find a way to fix it, so I'll
ask. The callsign display windows
shows callsigns for 30 seconds which
is great. However, on the last
transmission, when I send 73 or RR73,
the successful logging notice pops
up within 3 seconds, and that clears
the callsign display window. I
usually have several stations calling
and looking at the display window,
seeing SNR and location, helps me
decide who gets called next, but all
that information is gone. I can't see
any way to stop the successful log
popup. Any ideas. Tnx. Gus  K2GT


locked Re: Callsign Display Window Timing

Michael Black
 

Settings/Logging -- scroll down to the bottom of the list on the right and turn off "Clear Callsigns display after logging"

Mike W9MDB

Inline image






On Thursday, July 2, 2020, 02:57:56 PM CDT, ve7gtc <ve7gtc@...> wrote:


This is a minor annoyance but I can't find a way to fix it, so I'll ask. The callsign display windows shows callsigns for 30 seconds which is great. However, on the last transmission, when I send 73 or RR73, the successful logging notice pops up within 3 seconds, and that clears the callsign display window. I usually have several stations calling and looking at the display window, seeing SNR and location, helps me decide who gets called next, but all that information is gone. I can't see any way to stop the successful log popup. Any ideas. Tnx.
Gus  K2GT


locked Callsign Display Window Timing

ve7gtc
 

This is a minor annoyance but I can't find a way to fix it, so I'll ask. The callsign display windows shows callsigns for 30 seconds which is great. However, on the last transmission, when I send 73 or RR73, the successful logging notice pops up within 3 seconds, and that clears the callsign display window. I usually have several stations calling and looking at the display window, seeing SNR and location, helps me decide who gets called next, but all that information is gone. I can't see any way to stop the successful log popup. Any ideas. Tnx.
Gus  K2GT


locked Worked B4 not working

Paul AC9O
 

Hi Laurie,

I am still having the issue where someone I just worked keeps alerting. Here's an example of KF7JZ still highlighted and it's in the worked QSO popup.

I am using the latest version of all programs.



Thanks,
Paul, AC9O


locked Re: 13 Colonies

Larry Banks
 

Perhaps a better term would be “Rebuild Alert Database”?

73 -- Larry -- W1DYJ

 

Sent: Wednesday, July 01, 2020 23:38
Subject: Re: [HamApps] 13 Colonies
 
On 2/07/2020 1:07 pm, Carey Fisher wrote:
OK. Wasn't sure. Am now. Thanks Laurie!
73, Carey, WB4HXE
No problems Carey.

I can understand the confusion with the term "Scan Log" as B4 checks are also done against the Log.

The term "Scan Log" has been dropped in JTAlertV3, instead using "Rebuild Alert Progress" as it uses a universal "Progress" window for checking on the Status of the different Alert types. I think I will make a similar change in naming in V2 as well.

de Laurie VK3AMA


locked Re: WAE Sicily alert - Defect Confirmed

Graham Alston
 

Yes the beta fix seems to be working.

73 Graham VK3GA


locked Re: 13 Colonies

Alfred Reeves
 

Thanks for the removal tip.  That sure saves a lot of time..
Also thanks for a great product!!! KUDOS!!!

73
Al
W1JHU
Ocala, FL

On 7/2/2020 12:07 AM, HamApps Support (VK3AMA) wrote:
On 2/07/2020 1:47 pm, Alfred Reeves wrote:
This is the way I have the 13 Colonies alert.
1. Open "Settings" "Wanted Call Signs"
2. Check "Enable Wanted Callsign Alert"
3. Under "Options" check "Alert when decoded Callsign worked B4"
4. In the "Alert Callsigns" box enter the callsigns of the 15 "13 Colonies stations" ie K2A, K2B, etc.
5. Set the "Alert Color" to your preference.
6. Click the "Save" box at the lower right.
7. Close out.

As the 13 colonies stations are decoded they will show up colored to the preference you set even if you worked them B4 ie last year.  As you work the stations you can go and remove them from the "Alert Callsigns" box.

That's way I have been working them and it's very helpful.

Al
W1JHU 
Al,

Perfect! Exactly what needs to be done.

FYI, you can quickly remove a Callsign from the Wanted Call Alert by right-clicking the Callsign in JTAlert and selecting the relevant entry from the resulting popup context menu. This avoids having to open the Settings window.

de Laurie VK3AMA



locked Re: 13 Colonies

HamApps Support (VK3AMA)
 

On 2/07/2020 1:47 pm, Alfred Reeves wrote:
This is the way I have the 13 Colonies alert.
1. Open "Settings" "Wanted Call Signs"
2. Check "Enable Wanted Callsign Alert"
3. Under "Options" check "Alert when decoded Callsign worked B4"
4. In the "Alert Callsigns" box enter the callsigns of the 15 "13 Colonies stations" ie K2A, K2B, etc.
5. Set the "Alert Color" to your preference.
6. Click the "Save" box at the lower right.
7. Close out.

As the 13 colonies stations are decoded they will show up colored to the preference you set even if you worked them B4 ie last year.  As you work the stations you can go and remove them from the "Alert Callsigns" box.

That's way I have been working them and it's very helpful.

Al
W1JHU 
Al,

Perfect! Exactly what needs to be done.

FYI, you can quickly remove a Callsign from the Wanted Call Alert by right-clicking the Callsign in JTAlert and selecting the relevant entry from the resulting popup context menu. This avoids having to open the Settings window.

de Laurie VK3AMA


locked Re: 13 Colonies

Alfred Reeves
 

This is the way I have the 13 Colonies alert.
1. Open "Settings" "Wanted Call Signs"
2. Check "Enable Wanted Callsign Alert"
3. Under "Options" check "Alert when decoded Callsign worked B4"
4. In the "Alert Callsigns" box enter the callsigns of the 15 "13 Colonies stations" ie K2A, K2B, etc.
5. Set the "Alert Color" to your preference.
6. Click the "Save" box at the lower right.
7. Close out.

As the 13 colonies stations are decoded they will show up colored to the preference you set even if you worked them B4 ie last year.  As you work the stations you can go and remove them from the "Alert Callsigns" box.

That's way I have been working them and it's very helpful.

Al
W1JHU 


locked Re: 13 Colonies

HamApps Support (VK3AMA)
 

On 2/07/2020 1:07 pm, Carey Fisher wrote:
OK. Wasn't sure. Am now. Thanks Laurie!
73, Carey, WB4HXE
No problems Carey.

I can understand the confusion with the term "Scan Log" as B4 checks are also done against the Log.

The term "Scan Log" has been dropped in JTAlertV3, instead using "Rebuild Alert Progress" as it uses a universal "Progress" window for checking on the Status of the different Alert types. I think I will make a similar change in naming in V2 as well.

de Laurie VK3AMA


locked Re: 13 Colonies

Carey, WB4HXE
 

OK. Wasn't sure. Am now. Thanks Laurie!
73, Carey, WB4HXE


On Wed, Jul 1, 2020 at 10:47 PM HamApps Support (VK3AMA) <vk3ama.ham.apps@...> wrote:
On 2/07/2020 4:33 am, Carey Fisher wrote:
Did you rescan your log after setting the new date?
73, Carey, WB4HXE
FYI,

Log re-scanning has no affect on changed B4 status and alerting.

de Laurie VK3AMA



--
Carey Fisher


locked Re: 13 Colonies

HamApps Support (VK3AMA)
 

On 2/07/2020 3:18 am, Jon KM8V wrote:
Is there any way to reset the worked B4 status for Wanted Callsigns? I'm trying to re-set JT-alert for the 13 Colonies event, but even when I say "Ignore B4 before date X" it still isn't alerting.

Any ideas?

Thanks & 73 de KM8V

Resetting the B4 status will not affect Alerting unless the previously worked Callsigns, that is now not showing a B4, generates an Alert. I doubt that any of the 13 Colonies stations for a US based Ham would be generating any DXCC, State, etc, Alerts and will just be shown without any alert coloring and no alert sound.

If you want 13 colonies stations to generate an alert to get your attention, add the Callsigns as a Wanted Callsign, either individually or in bulk through a csv file import.

de Laurie VK3AMA


locked Re: 13 Colonies

HamApps Support (VK3AMA)
 

On 2/07/2020 4:33 am, Carey Fisher wrote:
Did you rescan your log after setting the new date?
73, Carey, WB4HXE
FYI,

Log re-scanning has no affect on changed B4 status and alerting.

de Laurie VK3AMA


locked Re: Decodes window not always populating

HamApps Support (VK3AMA)
 

On 2/07/2020 8:45 am, W4WT wrote:
Well, after an hour playing with sound things, I found that you can not change Voicemeeter Potato names where they will persist over a reboot regardless of the procedure you use.  Some sound devices are able to be renamed and persist but not Voicemeeter.  However, I solved the problem by using a virtual audio cable I had installed that I wasn't using at the moment.  I pointed its output to a spare Voicemeeter Potato hardware input and pointed JTAlert to the cables input.  Works just fine now and persists through a reboot.

Thanks,

Joe W4WT

Thanks for the update Joe. Good yo hear you have a working solution.

de Laurie VK3AMA

4741 - 4760 of 35329