Date   

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


locked Re: Lost 'Successful Logging' Pop-up

HamApps Support (VK3AMA)
 

On 2/07/2020 12:55 am, Thomas Webb wrote:
I am clicking 'OK' when the logging reminder pops up and QSO is going into the 'WSJT-X adi' log.  Not using any external logging.

Tom, WA9AFM

If you not using a logger with JTAlert than there is nothing for JTAlert to confirm so you wont get a success/failure popup. JTAlert has never performed any logging confirmation of WSJT-X self logged QSOs, that is the responsibility of WSJT-X.

de Laurie VK3AMA


locked Re: Decodes window not always populating

W4WT
 

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


locked Re: 13 Colonies

Carey, WB4HXE
 

Jon,
Did you rescan your log after setting the new date?
73, Carey, WB4HXE

On Wed, Jul 1, 2020 at 1:18 PM Jon KM8V <perlguy9@...> 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



--
Carey Fisher


locked Re: 13 Colonies

Michael Black
 

Short term fix would be to add them to wanted calls and remove when you work them.

Mike W9MDB




On Wednesday, July 1, 2020, 12:23:36 PM CDT, Jon KM8V <perlguy9@...> wrote:


Yes.


locked Re: 13 Colonies

scot
 

I do it the old fashioned way and keep a log sheet at the operating position

Scott
N2SAB


locked Re: 13 Colonies

Jon KM8V
 

Yes.


locked Re: 13 Colonies

Michael Black
 

Did you restart JTAlert?

Mike W9MDB




On Wednesday, July 1, 2020, 12:18:23 PM CDT, Jon KM8V <perlguy9@...> 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


locked 13 Colonies

Jon KM8V
 

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


locked Re: Lost 'Successful Logging' Pop-up

Thomas Webb
 

I am clicking 'OK' when the logging reminder pops up and QSO is going into the 'WSJT-X adi' log.  Not using any external logging.

Tom, WA9AFM


locked Re: WAE Sicily alert - Defect Confirmed

HamApps Support (VK3AMA)
 

On 30/06/2020 4:12 pm, Graham Alston wrote:
I have the list set on Any Band/Any Mode.
I have only noticed this issue for WAE Sicily.
Debug and log sent.
Many thanks for your help.
73 Graham VK3GA
I can confirm this defect. It affected all 6 WAE Entities.
It has now been corrected for the next public release.

Check your email, I have sent a link to the latest build for you to test.

de Laurie VK3AMA


locked Re: Lost 'Successful Logging' Pop-up

HamApps Support (VK3AMA)
 

On 1/07/2020 12:50 pm, Thomas Webb wrote:

     That instruction is not checked and I still do not get a report.

Tom, WA9AFM

Do you have logging enabled in JTAlert?

Are the QSOs making it into your log? If not, than likely you not hitting the "OK" button in the WSJT-X "Log QSO" window.

If the QSOs are getting logged without an accompanying success/failure popup should not happen unless your Logger (what do you use) is doing the logging direct.

de Laurie VK3AMA


locked Re: Lost 'Successful Logging' Pop-up

Thomas Webb
 

Laurie,

     That instruction is not checked and I still do not get a report.

Tom, WA9AFM


locked Re: UDP Communications Failure/No JTAlert

HamApps Support (VK3AMA)
 

On 1/07/2020 6:43 am, K5GLB wrote:
Everything was working fine before I set everything up for FD and had to change all of my setting to work with N3FJP FD. I probably have some parameter wrong, but I've messed with this for hours trying to get something to show up on JTAlert. Thanks for your help.

Gary K5GLB
Your settings look OK.

Perform a PC Restart as a first step.

If still no joy despite the correct settings, check that you don't have another application trying to use the WSJT-X UDP Server port (2237) which would prevent JTAlert from receiving UDP messages and ultimately throw the error dialog you are getting.

Another common problem is people running WSJT-X with elevated privileges, that is set to run as Administrator. There is no need to run WSJT-X elevated. Check both the wsjtx.exe file properties AND the shortcut used to start WSJT-X.

If you have another application auto-starting WSJT-X for you, make sure it is not running elevated as that setting will automatically be applied to any applications it starts.

de Laurie VK3AMA


locked Re: Lost 'Successful Logging' Pop-up

HamApps Support (VK3AMA)
 

On 1/07/2020 11:02 am, Thomas Webb wrote:
I seem to have lost the 'successful logging' message that pops up when a contact is logged within WSJT-X.  Gave the online manual a close read, but found nothing.  Where is the menu item/control for that function?

Tom WA9AFM/5



de Laurie VK3AMA


locked Lost 'Successful Logging' Pop-up

Thomas Webb
 

I seem to have lost the 'successful logging' message that pops up when a contact is logged within WSJT-X.  Gave the online manual a close read, but found nothing.  Where is the menu item/control for that function?

Tom WA9AFM/5

4861 - 4880 of 35434