Date   

locked Re: #Important : JTDX users MUST use the JTAlert JTDX shortcut #Important

HamApps Support (VK3AMA)
 

On 23/06/2021 2:31 pm, Jim Brown wrote:
I use WSJT-X almost exclusively for very long haul DX on 160 and chasing grids on 6M. I don't use FT4, so this is not an issue for me. But a point of information for you -- last year, many 6M ops started using both WSJT-X and JTDX simultaneously, because both programs (but most often JTDX), catch a weak decode that the other misses.

73, Jim K9YC
Jim,

Running WSJT-X and JTDX concurrently is not a problem, it is when someone is using JTDX and starting JTAlert with the WSJT-X shortcut, not the JTDX shortcut. By doing this the necessary character to mode remapping I need to do for JTDX FT4 spots doesn't get done and the FT4 spots appear as Q65. I have seen this mainly on 20m & 40m. I don't recall seeing it on 6m, but the band is not important.

de Laurie VK3AMA


locked Re: #Important : JTDX users MUST use the JTAlert JTDX shortcut #Important

Jim Brown
 

Hi Laurie,
I use WSJT-X almost exclusively for very long haul DX on 160 and chasing grids on 6M. I don't use FT4, so this is not an issue for me. But a point of information for you -- last year, many 6M ops started using both WSJT-X and JTDX simultaneously, because both programs (but most often JTDX), catch a weak decode that the other misses.

73, Jim K9YC


On Tue, Jun 22, 2021 at 3:48 PM HamApps Support (VK3AMA) <vk3ama.ham.apps@...> wrote:
In recent weeks there have been a number of users repeatedly spotting FT4 spots to HamSpots as Q65.

This is caused by the user using the JTAlert WSJT-X shortcut when running JTDX.

The problem stems from changes the JTDX people made to the WSJT-X UDP protocol. Specifically, the UDP decode message contains a single character that identifies the mode for the decode. The WSJT-X standard uses ":" to identify Q65, but JTDX chose to use ":" to identity FT4 decodes.

JTAlert overcomes this by using an alternate character to mode mapping table for JTDX users.

To change the character to mode mapping JTAlert needs to know what application you have JTAlert working against, WSJT-X or JTDX, this is why there are different shortcuts to start JTAlert, the Red "X" icon for WSJT-X and the Blue "X" icon for JTDX. This has been in place for quite some time.

Recently a number of users have been using the WSJT-X shortcut when running JTDX, as a result, if they are working FT4 all spots to HamSpots are flagged as Q65.

The fix is simple, use the correct JTAlert shortcut.


de Laurie VK3AMA


locked Re: Filters - A feature request

Mike Flowers
 

Thank you!  


locked Re: Filters - A feature request

Michael Black
 

Mike W9MDB
Inline image





On Tuesday, June 22, 2021, 11:00:40 PM CDT, Mike Flowers <mike.flowers@...> wrote:


I cannot find where in Settings to specify my DXCC number.

Also received this while looking ...


locked Re: Filters - A feature request

Mike Flowers
 

I cannot find where in Settings to specify my DXCC number.

Also received this while looking ...


locked Re: JTAlert 2.50.2 install on Windows 10 Edge #FT8

Jim Nuytens
 

I fail to see what Edge has to do with it.

If this is a red screen that pops up, click on "More Info", then "Run Anyway".

On 6/22/2021 6:26 PM, Pedro Alonso via groups.io wrote:
I tried to install JtAlert 2.50.2 and get this message: " JTAlert 2.50.2 install x64.exe was blocked because it could harm your devise"
Is there a way to install it on Windows 10, running Edge browser ?

Thank you,
Pedro


locked Re: JTAlert 2.50.2 install on Windows 10 Edge #FT8

neil_zampella
 

Try a different browser like Firefox, and/or add an exception in Windows defender.

Neil, KN3ILZ


locked Re: Filters - A feature request

Seb
 

Thanks for clarifying this.  I can't imagine how difficult it must be for you to track all of these settings and decodes.

Now before we get the "what is my DXCC number", for the 48 states in the union it's #291, and the setting is found in the Station Callsign selection in the settings of the main program.

For other locations, you'll find the DXCC number (displayed as Entity Code), here: http://www.arrl.org/files/file/DXCC/2020%20Current_Deleted.txt

73 de W4AS


locked Re: Filters - A feature request

HamApps Support (VK3AMA)
 

On 23/06/2021 9:40 am, Seb wrote:
I never saw a need (and actually never noticed that setting) to do so, but obviously it's important.

The setting was never important and went unused until now.

I briefly considered adding auto detection of the dxcc # but that in some instances would fail for swl and special event callsigns that may be used. So a confirmation popup prompt would have been needed along with a checkbox to not show the popup again. The code was rapidly becoming more complicated so I chose to abandon that and require the user to perform a one-time setting. With all that has happened in the last week with the NET 5.0.7 induced broken audio, I simply ran out of time to fully flesh out the documentation of the new requirements. I should have added a more prominent note about the dxcc # setting.


de Laurie VK3AMA


locked Re: JTAlert version 2.50.2

Micky Corrow
 

Sorry, I was not being helpful.
You need to add the file as an exception, and then download it again.
Then it should run, when the exception box comes up, click More Info.
Then click Run Anyway.

That should allow the installer to work.
Hope this helps...

Micky K1XH


locked Re: JTAlert version 2.50.2

Micky Corrow
 

When downloaded with Chrome, Defender still flags it as a virus...

Micky K1XH


locked Re: Filters - A feature request

Seb
 

No, and you got it! 

Now that I did, the Decodes DX panel is populating.  I never saw a need (and actually never noticed that setting) to do so, but obviously it's important.

Thanks again for adding the new functionality to an already awesome software!

73 de W4AS


locked Re: MS Shenanigans

Mike KC7V
 

Very good Laurie and thank you for the update.

--
Mike KC7V


locked Re: Filters - A feature request

HamApps Support (VK3AMA)
 

On 23/06/2021 9:12 am, Seb wrote:
Again, I'm not seeing any DX stations in the Decodes DX panel.

73 de W4AS

Have you set your DXCC number in the main JTAlert Settings?

de Laurie VK3AMA


locked Re: Filters - A feature request

Jim Cooper
 

On 22 Jun 2021 at 16:12, Seb wrote:

Again, I'm not seeing any DX stations in the Decodes DX panel.
You are decoding only ONE dx station, and that station
is flagged as B4 ... check your various B4 filters -
something is blocking them going to the DX window.


locked Re: Filters - A feature request

HamApps Support (VK3AMA)
 

On 23/06/2021 9:12 am, Seb wrote:
Hopefully the attached will display here.

Again, I'm not seeing any DX stations in the Decodes DX panel.

73 de W4AS

That doesn't look right. The PV8 should be appearing in the DX panel.

Try enabling the "Decodes Local" panel as well, so you have both DX and Local visible, are the DX calls showing in the Local panel? They should not. Post another image.

de Laurie VK3AMA


locked Re: Filters - A feature request

Seb
 

Hopefully the attached will display here.

Again, I'm not seeing any DX stations in the Decodes DX panel.

73 de W4AS


locked Re: Filters - A feature request

HamApps Support (VK3AMA)
 

On 23/06/2021 9:02 am, Seb wrote:
However, no DX stations are showing in the Decodes DX panel.

In the "Decodes DX" view are you seeing all callsigns, local and DX, or no callsigns?

If it is all callsigns that would be due to not seeing your DXCC in the JTAlert Settings.

From the 2.50 features help file...
   

de Laurie VK3AMA


locked Re: QSL Flags ver. 2.50.2

Laurie, VK3AMA
 

On 23/06/2021 9:00 am, JA9IFF Jim Nakajima wrote:
Various QSL flag displays are grouped in the upper right corner, making it difficult to judge just by the difference in symbols.
Is it possible to set it back to the original corner position?

JA9IFF
Jim Nakajima
NO.

You can chose from a list of 17 different symbols to help you distinguish between symbols.

de Laurie VK3AMA


locked Re: Filters - A feature request

Seb
 

I don't think you understood my message.  I'm seeing DX stations (outside of my country) on panels such as CQ and Distant decodes.  I understand they will appear in multiple panels depending on the type of decodes.

However, no DX stations are showing in the Decodes DX panel.

2181 - 2200 of 37662