Date   

locked Re: Can't access settings

Gerry S
 

Found it pinned below FT8 window where I couldn't see it.

Tks all


locked JTAlert not connecting to WSJT-X #FT8

Bob McLeod
 

A friend is setting up his FT8 programs on a new PC.  He has WSJT-X, JTAlert and DXKeeper.  It was all working fine on the old PC, and he thinks he has installed it in the same way on the new PC.  In fact it seemed to be working, but the PC went to sleep at some stage with the programs open, and now JTAlert doesn't connect to WSJT-X (there is no band information in the title bar). That could have been a coincidence, but nothing he has tried will make it connect now - including making sure the 3 tick boxes on the WSJT-X Reporting tab that deal with UDP are checked.  I hope to be able to log on to remote view his PC later today, and I will go through checking the installations and settings against those on my working copy, but has anyone come across this before, or have any suggestions? Thanks Bob VP8LP


locked Can't access settings

Gerry S
 

I updated to the latest JTalert.

I cannot find the settings area now.  I do not see this (see below) and cannot access it so far. JTalert still decodes etc.  Howver, I cannotmanage my settings.

what did I do wrong?

Tks Gerry


locked JTAlert for WSJT-X vs JTAlert for JTDX

Mike Wilson <mwilson1946@...>
 

I recently tried out the jtdx, but found that the stations I have worked before are showing up as not worked. Is this normal? I thought I read that both alert’s used the same database file?

 

73 de KE5WCT

Mike Wilson

Sent from Mail for Windows 10

 

 


locked Re: Wanted US States not updating

JTAlert Support (VK3AMA)
 

On 9/10/2021 6:02 am, Paul Sturpe wrote:
With those settings I would expect to get no further alerts for a state once I work that state on 12 meters.

How are you determining that the State is still being alerted? is it ny the coloring of the Callsign , by a State audio alert or both?

If it is only by the coloring of the Callsign, it may be the Wanted Dxcc alert being triggered. Both alert types have the same yellow background coloring with the font color, red or black distinguishing the alert type.

Hover you mouse over the Callsign of what you believe is incorrect alerting station and observe the resulting tooltip, it should indicate what Alert types were triggered for the callsign, the State, Dxcc, etc will be in bold if they are associated with an Alert type.

de Laurie VK3AMA


locked Re: Wanted US States not updating

Paul Sturpe
 

Laurie,

Whoops.  I was looking at that table backwards.   Like you say, I want to see a check mark removed when I work a new state.  I'll do a little more testing before I bother you again.

Thanks and 73,

Paul, W3GQ


locked Re: Wanted US States not updating

JTAlert Support (VK3AMA)
 

On 9/10/2021 6:02 am, Paul Sturpe wrote:
Then when I look at the list of states worked, I would expect to see a new check mark for the state I just worked.

Neither of those two things are happening i.e. I continue to get alerts for the state I just worked and a check mark does not show up in that state's box.

A check-mark indicates that a State is needed. No check-mark is what you want. If you have the "Auto clear triggered ... " setting enabled, than there is no need to manually change the need status of individual States.

Please use the "Help" -> "Contact Support" menu, on the main JTAlert window, to send me your JTAlert files for analysis.

de Laurie VK3AMA


locked Re: Wanted US States not updating

Paul Sturpe
 

Oh crap.  I hope I didn't inadvertantly send a partial reply.

Anyway, Laurie, I want to say first of all how much I enjoy the program and have passed it on to several of my ham friends.

I'm just trying to see if things are working here the way they should or if I am missing a "switch" somewhere.

Using 12 meters as an example, I uploaded my settings.  Yes I don't care about confirmations for the time being.   With those settings I would expect to get no further alerts for a state once I work that state on 12 meters.

Then when I look at the list of states worked, I would expect to see a new check mark for the state I just worked.

Neither of those two things are happening i.e. I continue to get alerts for the state I just worked and a check mark does not show up in that state's box.

Am I expecting something that is not supposed to happen?

Thanks,
Paul, W3GQ

 


locked Re: incorrect shortcut

Laurie, VK3AMA
 

On 9/10/2021 2:53 am, Paul Sturpe wrote:
I know this has been discussed in the past and I have looked at the solutions, but they don't seem to work for me.

I have tried it with and without a dash between the t and the j (wsjt-x) and several other versions but all of them end up with the window asking me to select wsjt-x or jtdx

"C:\Program Files (x86)\HamApps\JTAlert\JTAlert.exe" /wsjtx

Now the shortcut for JTDX (below) works fine.  I have to be missing something simple!

"C:\Program Files (x86)\HamApps\JTAlert\JTAlert.exe" /jtdx

Paul, W3GQ
Is this a JTAlert installer created shortcut or one you created/modified yourself?

The correct parameter is, /wsjtx . There is no hyphen. Make sure the is no space between the slash and the "wsjtx"

de Laurie VK3AMA


locked Re: Wanted US States not updating

JTAlert Support (VK3AMA)
 

On 9/10/2021 5:13 am, Michael Black via groups.io wrote:
It's only updated when it's confirmed.

Mike W9MDB

That is wrong!

The OP is using the "Auto cleared triggered ..." setting, so States are automatically removed when a suitable station is worked, there is no confirmation requirement. Confirmation requirements only come into play when running the database rebuild and then only if one or more confirmation types are set.

de Laurie VK3AMA


locked Re: Wanted US States not updating

JTAlert Support (VK3AMA)
 

On 9/10/2021 5:10 am, Paul Sturpe wrote:
Here are my settings.  Alerts work fine but the list is not getting updated automatically upon working a new state.   Shouldn't it be updating automatically?

Paul, W3GQ

Paul,

Your settings look fine.

Are you running the Alert database Rebuild of the Wanted States? If so, that will be the cause of the need status being reset.
Since you're not interested in States requiring confirmation, there is no need to run the rebuild since you have the "Auto cleared triggered ... " setting enabled.

de Laurie VK3AMA


locked Re: Wanted US States not updating

Paul Sturpe
 

Two questions then.

  • What does the checked box do on the attached file?
  • Is there no way to select "no confirmation required" like there is on the DXCC alerts?

Thanks,
Paul, W3GQ


locked Re: Wanted US States not updating

Michael Black
 

It's only updated when it's confirmed.

Mike W9MDB




On Friday, October 8, 2021, 01:10:17 PM CDT, Paul Sturpe <sturpe@...> wrote:


Here are my settings.  Alerts work fine but the list is not getting updated automatically upon working a new state.   Shouldn't it be updating automatically?

Paul, W3GQ


locked Wanted US States not updating

Paul Sturpe
 

Here are my settings.  Alerts work fine but the list is not getting updated automatically upon working a new state.   Shouldn't it be updating automatically?

Paul, W3GQ


locked JTAlert/WSJT-X Issues with AK and HI, plus B4 problem

Ronald Clanton
 

I continue to see AK and HI as a wanted DXCC/State in the decode box (marked by yellow) despite having many confirmed log entries.  Is there a setting that I'm missing?

Also, I thought in the past that a contact was only marked "B4" when confirmed?  I have a situation where it indicated it as B4, but isn't a confirmed contact.  Additionally, in the decode box, it doesn't flag it as a wanted DXCC (only grey)... even though that unconfirmed contact is the only one for that DXCC entry.

Thanks,

Ron


locked incorrect shortcut

Paul Sturpe
 

I know this has been discussed in the past and I have looked at the solutions, but they don't seem to work for me.

I have tried it with and without a dash between the t and the j (wsjt-x) and several other versions but all of them end up with the window asking me to select wsjt-x or jtdx

"C:\Program Files (x86)\HamApps\JTAlert\JTAlert.exe" /wsjtx

Now the shortcut for JTDX (below) works fine.  I have to be missing something simple!

"C:\Program Files (x86)\HamApps\JTAlert\JTAlert.exe" /jtdx

Paul, W3GQ


locked Re: No decode window?

Greg Clark <greg@...>
 

That was it Joe - the link in the checking tool does not take you to the desktop - but its all in and working.  Thanks for the assist.


locked Re: No decode window?

N6HA
 

If you click the "about JTAlert" does it bring anything up? If not make sure you have the "Desktop" version of .NET 5.0 installed. The website has a confusing UI that makes it look like it's for Linux. If you installed the "Console" version it will have the symptom of the "about JTalert" not loading.


locked Callsign window won't load fix #TIP

N6HA
 

I recently installed JTAlert on a new computer and couldn't get the callsign window to load. I had followed the installer to instructions to install .NET framework 5.0 but the UI for the download is a bit confusing. If you're rushing through it like I was the "Desktop" version of .NET looks like it was supposed to be for Linux and not Windows and so I mistakenly downloaded the "Console" version. It might be worth adding some sort of error message in the JTAlert app itself to detect issues like this.

Symptoms:
- callsign window won't load
- "about JTAlert" menu item does nothing
- FrameworkCheck.exe gives a warning "The framework 'Microsoft.WindowsDesktop.App', version '5.0.0' was not found." but 5.0.10 is installed from the link followed by the installer.
- decodes is blank with all filters off


locked Re: No decode window?

Joe Subich, W4TV
 

You have installed the *WRONG* dotNet runtime. You must install
the *DESKTOP* version - it will say *DESKTOP* in the name.

You have installed .NET Runtime 5.0.10 *not* .NET Desktop Runtime 5.0.10

Try this link:
<https://download.visualstudio.microsoft.com/download/pr/78fa839b-2d86-4ece-9d97-5b9fe6fb66fa/10d406c0d247470daa80691d3b3460a6/windowsdesktop-runtime-5.0.10-win-x64.exe>
(From message <https://hamapps.groups.io/g/Support/message/35794>)

or

<https://dotnet.microsoft.com/download/dotnet/thank-you/runtime-desktop-5.0.10-windows-x64-installer>

(from: <https://dotnet.microsoft.com/download/dotnet/5.0>)

Again, *YOU MUST USE THE .NET DESKTOP VERSION*


73,

... Joe, W4TV

On 2021-10-07 2:51 PM, Greg Clark wrote:
Joe et al
I used the .NET checker in the START menu and get this:
BUT - I .NET is installed, its 5.0.10, not 5.0.0 per the checker (if that makes a difference).  I have installed .NET and uninstalled it and installed again and the results are the same = it appears that JTAlert does not see my version of .NET on the PC.  It was downloaded and installed:
So not sure where to go from here.
Thanks
Greg

3261 - 3280 of 40358