Date   

locked Re: JTAlert not logging

Dave Garber
 

Is it trying to go to the correct log file and is acI running. 

sent by my LG phone

On Tue, Sep 1, 2020, 4:34 PM deni, <deni@...> wrote:
All of a sudden this started happening, no logging to acl.  I have restarted the app and upgraded to 2.16.13 and the problem still exists.  Any help on this one.
Thanks
Deni - WB0TAX


locked JTalert to JTDX click

Robert galambos
 

When i double click in jtalert for wsjt-x it automatically sets it up for transmission within wsjt-x.

However, this does not happen within JTalert/jtdx. what am I doing wrong?


locked JTAlert not logging

deni
 

All of a sudden this started happening, no logging to acl.  I have restarted the app and upgraded to 2.16.13 and the problem still exists.  Any help on this one.
Thanks
Deni - WB0TAX


locked Re: Feature request - More Callsign display slots.

John C
 

thanks for your reply and suggestions Laurie.   My friend is not very computer literate and has problems with even some simple things so forums are not for him.   At your suggestion, I took him on a step by step journey through the filters and after setting the B4 filter he is much happier.

 

cheers

Joihn


locked Re: JTAlert-X Show Log Fields

Alfred Reeves
 

Laurie..that was it..stupid me.. TNX for your response.

73
Al
W1JHU

On 9/1/2020 2:46 PM, HamApps Support (VK3AMA) wrote:
On 2/09/2020 4:13 am, Alfred Reeves wrote:
Setting up a new computer for the shack.  I'm unable to get the "Show Log Fields" to display.  It is grayed out so can't access.  Ideas??

Al
W1JHU

You need to have a Logger enabled.

de Laurie VK3AMA



locked USA Filter

Bill Barrett
 

Hello Laure-
Would be nice to filter USA calls from the display. Currently the NA
continent filter removes calls that are of interest on some bands,
for example 6M.
Thanks;
--
Bill Barrett
W2PKY


locked Re: JTAlert does crash again

asobel@...
 

Laurie

 

JTAlert did ceash again few times today.

 

The news is about the new message in the above snip

 

Amos 4X4MF

=================================

Laurie

 

3 weeks after “Good news1” JTAlert does crash again quite often.

It did crash before but Last week I did install Norton360 and the frequency of crash did increase dramatically.

I have the impression that the JTAlert crash frequency does increase with time after installation on a new Win10 disk.

This applies to JTAlert only. Other applications are not affected.

 

Amos 4X4MF

 

 

From: Support@HamApps.groups.io <Support@HamApps.groups.io> On Behalf Of HamApps Support (VK3AMA)
Sent: Monday, August 10, 2020 4:06 AM
To: Support@HamApps.groups.io
Subject: Re: [HamApps] JTAlert does crash rem 2

 

On 10/08/2020 1:09 am, asobel@... wrote:

This morning, I did complete rebuilding my computer on an SSD disk. Unintentionally I did also rebuild the HRD Logbook using ADIF file backup similar to your description. 12 hours later, there was no fail. I hope it will stay so. Be sure, I will let you know if it fails


Good news!

de Laurie VK3AMA


locked Re: JTAlert-X Show Log Fields

HamApps Support (VK3AMA)
 

On 2/09/2020 4:13 am, Alfred Reeves wrote:
Setting up a new computer for the shack.  I'm unable to get the "Show Log Fields" to display.  It is grayed out so can't access.  Ideas??

Al
W1JHU

You need to have a Logger enabled.

de Laurie VK3AMA


locked JTAlert-X Show Log Fields

Alfred Reeves
 

Setting up a new computer for the shack.  I'm unable to get the "Show Log Fields" to display.  It is grayed out so can't access.  Ideas??

Al
W1JHU


locked Re: JTAlert 2.16.12 setup questions

Jeff - G4IUA
 

Many thanks for the suggestions.  

Multicast was selected in GT.  Sometimes easy to overlook the obvious so no problem at all suggesting double checking!

 

Great news in that Log4OM, WSJT-X, JTA and GT all nicely talk to each other now. 

 

Changed GT port to 2237, Multicast ON, 239.0.0.1.  I don’t know what to do re Forward UDP Messages but ATM they are 127.0.0.1 and 2233 but enabled/disabled make no difference so I guess they aren’t relevant.

 

WSJT/Reporting:  UDP Server 239.0.0.1 and UDP Server port 2237.  I’m not sure of the function of the Secondary UDP Server (Deprecated) but it made no difference whether selected or not.

 

Despite what I read in other posts, in JTA I changed WSJT-X/JTDX: Resend UDP Packets (rx only) from 127.0.0.1 to 239.0.0.1.  Logging to Log4OM remains unchanged as: UDP Connections 127.0.0.1, ADIF_Message port 2235, Control port 2241.  No changes in Log4OM. 

 

It all started working and I’ve power recycled several times and everything still comes up beautifully.  GT is a great addition to the arsenal and it's useful having so much information displayed on the 2 monitors.  I really need to brush up on all this UDP, Multicast stuff as I hate just blindly going in and not knowing what I'm doing.  Not sure where to find a good basic tutorial but I'm sure the Internet will come up with something as usual!


Thanks again for the input.

Jeff - G4IUA

 


locked Re: JTAlert 2.16.12 setup questions

TomK
 

I hate to ask what you could find to be a terrible obvious question but did you also changed GT’s additional setting to specifically force it’s use of UDP multicast mode?

That setting is a radio button (a circular pushbutton) labelled as Multicast? (0) . See below.

Unlike WSJT & JTA, GT does not presume Multicast mode based on the port address.

 

   “As long as the port numbers and multicast address in WSJT and GT match, GT works but not JTA. “

 

I’m not 100% sure but I suspect this might be true if you have not enabled the specific Multicast override option in GT.  WSJT and GT may work (if they were started 1st) because when using the WSJT multicast address range 239.x.x.x.x, GT may still work without its Multicast override enabled because there has not yet been a conflicting app (JTA in this case) to compete for the same UDP messaging queue.

 

   “Whenever WSJT's UDP server set from 127.0.0.1 to 239.0.0.1 JTA stops working.”

 

I think you are re-iterating the same scenario with the above phrase since both sentences refer to JTA not working.

 

Can you verify you have done all of the following:

 

  1. WSJT:
    Set its USP port address to something in the range 239.0.0.0 - 239.255.255.255. I recommend avoiding 239.0.0.0 or 239.255.255.255 as they have special meaning in some networking subnet routing scenarios. I recommend staying with the 239.0.0.1 you said you are using.

  2. JT Alert:
    Automatically tracks and follows WSJT settings so it will always match WSJT.

  3. Gridtracker:
    In this app you need to set 3 things:
    1. UDP address: Set to 239.0.0.1 (or whatever else you set WSJT  to in step 1 in the 239.x.x.x range).
    2. UDP port: Set to same port you set in WSJT. I recommend the default of 2237.
    3. Multicast Enablement: You must also enabled the radio button: Multicast? (@(Solid green means enabled)

 

There is a small chance that Windows and/or other apps may be using the chosen 239.x address and/or port 2237. But it is very rare.

I’d carefully re-check your settings as described above.

Apologies if you know all this.  It was not clear.

KT1TK 73

 

 

From: Support@HamApps.groups.io <Support@HamApps.groups.io> On Behalf Of Jeff - G4IUA
Sent: Monday, August 31, 2020 6:12 AM
To: Support@HamApps.groups.io
Subject: Re: [HamApps] JTAlert 2.16.12 setup questions

 

As long as the port numbers and multicast address in WSJT and GT match, GT works but not JTA.  Whenever WSJT's UDP server set from 127.0.0.1 to 239.0.0.1 JTA stops working.  I fail to understand why; other postings say nothing needs to be changed in JTA.

Jeff - G4IUA


locked Re: Feature request - More Callsign display slots.

John Kjos
 

I was not looking for MORE overall. Was wanting to have more slots than the 9 available, so it is wider on the screen to save space.

73 John W9RPM

On 8/31/2020 7:12 AM, Craig wrote:
Agree. Filter and make the 36 most effective. 


On Aug 31, 2020, at 01:09, Alfred Reeves <areeves18@...> wrote:

Why do you need more than 36 decodes displayed?  In the 15 sec decode interval is difficult to examine 36.  What if Laurie gives you 56, 72 etc. your not fast enough to examine them. IMHO it's a waste of programming time and resources.  Just my thoughts.
Al, W1JHU
-- 
EMAIL: john@...
WEBPAGE: http://www.w9rpm.com/
DX CLUB: http://www.tcdxa.org/


locked Re: Feature request - More Callsign display slots.

chas cartmel
 

I tend to agree that 36 is enough, however to put an opposing argument those using JT65/JT9 which are my favourite modes there will be more time to examine the ‘extra’ calls.


73 Charlie

G4EST

www.g4est.me.uk

Stay safe out there

 

 

 

From: Support@HamApps.groups.io [mailto:Support@HamApps.groups.io] On Behalf Of Craig
Sent: 31 August 2020 13:12
To: Support@hamapps.groups.io
Subject: Re: [HamApps] Feature request - More Callsign display slots.

 

Agree. Filter and make the 36 most effective. 


On Aug 31, 2020, at 01:09, Alfred Reeves <areeves18@...> wrote:

Why do you need more than 36 decodes displayed?  In the 15 sec decode interval is difficult to examine 36.  What if Laurie gives you 56, 72 etc. your not fast enough to examine them. IMHO it's a waste of programming time and resources.  Just my thoughts.
Al, W1JHU


locked Re: Feature request - More Callsign display slots.

Craig
 

Agree. Filter and make the 36 most effective. 


On Aug 31, 2020, at 01:09, Alfred Reeves <areeves18@...> wrote:

Why do you need more than 36 decodes displayed?  In the 15 sec decode interval is difficult to examine 36.  What if Laurie gives you 56, 72 etc. your not fast enough to examine them. IMHO it's a waste of programming time and resources.  Just my thoughts.
Al, W1JHU


locked Re: Feature request - More Callsign display slots.

 

I tried to upgrade to the new version. Then after shutting down the program I couldnt get it to load. I did a restart and that didn't work.

So I installed the last version and its work FB.

Software bug or Me?

Anyone else having this issue??


73 Dave NU4N





--
DAVE NU4N


locked Re: Problem with JTAlert 2.16.12 and 2.16.13

Gerard de Veer
 

Hello Laurie,

The problem is that I use JTDX and not WSJT-X.
Version 2.16.10 is running without problems but it started with 2.16.12.
And also version 2.16.13 has the same issue.

I checked JTDX  (rc-152) and all parameters are standing normal.


Best 73

Gerard PD0GIP


locked Re: Distorted audio on receive

Bill Howard
 

On Mon, Aug 31, 2020 at 04:22 AM, HamApps Support (VK3AMA) wrote:
On 31/08/2020 4:42 am, Bill Howard wrote:
Thank you Laurie. Very much appreciate your software. I am running a refurbished Dell Optiplex 3010 on Win 10 latest version, with 4gb memory. Only running WSJT-X and JTA lert. Tried everything you suggested with no joy. Switched to an earlier version on WSJT-X and the problem is gone!  Live and learn.
73 - Bill WB3V

Bill, What version of WSJT-X did you downgrade to?

How many CPU cores does the "Dell Optiplex 3010" have?  What model is the cpu (i5 ????).

de Laurie VK3AMA


 The Pc Uses an 3.3 GHz Intel core i3-3220.
]dual core on the Ivy bridge architecture. Due to hylerthreading, the two cores can handle up to four threads in parallel. Each core has a base speed of 3.3 GHz.

I downgraded to an early 2.15 version of WSJT-X and the system together with JTAlert is back to working well.


locked Re: JTAlert 2.16.12 setup questions

Jeff - G4IUA
 

As long as the port numbers and multicast address in WSJT and GT match, GT works but not JTA.  Whenever WSJT's UDP server set from 127.0.0.1 to 239.0.0.1 JTA stops working.  I fail to understand why; other postings say nothing needs to be changed in JTA.

Jeff - G4IUA


locked Re: Feature request - More Callsign display slots.

TomK
 

As a fellow JTA user, I may have misunderstood your request.

If you are referring the displayed messages in the DECODES window,

then there is a specific option to do *exactly* that.

It’s called  Alerts Only Option.

Click [Filter], then [X] Show Only Alerts

I use it often to seek logging only Grid/Prefixes/New DX/State/Prov, etc.

Works like a champ on steroids.

 

If you meant to limit the default QSO display grid (not DECODES window)

then I am not sure of its value since the DECODES window does all the same and so much more.

I like to see the lower grid disappear and focus on bit diddling the DECODES window to increase its speed and reduce its latency.

Just my 13 cents.

 

TomK / KT1TK / 73

 

 

From: Support@HamApps.groups.io <Support@HamApps.groups.io> On Behalf Of HamApps Support (VK3AMA)
Sent: Monday, August 31, 2020 3:12 AM
To: Support@HamApps.groups.io
Subject: Re: [HamApps] Feature request - More Callsign display slots.

 

On 31/08/2020 3:47 pm, Chuck Adams wrote:

Or you can use Settings > Manage Settings > Miscellaneous Alerts > Filters > Show only Callsigns generating alerts.  That will certainly reduce the number of decodes displayed in JTAlert.

73,

Chuck Adams

KV4VT


Chuck,

A quicker method to achieve the same result without the delay in opening the Settings window is to use the "Alerts -> Filters" menu.

de Laurie VK3AMA


locked Re: double-click in JTAlert not working #FT8

Ray KV4K Port Orchard WA
 

Here's the solution that worked for me. Now I can click on a callsign slot in JTAlerts and it will start a QSO in WSJT-X
reference message 
  by Laurie for more explanation.
What I did--
In the WSJT-X program 
-File
 -Settings
  -Reporting
under network services 
UDP server enter:
239.255.0.0
leave port at 2237
put check marks in the three boxes right there alongside in that section.
click OK