Date   

locked Re: JTALERTX stops displaying received calls

Martin Blanz DL9SAD
 

Hello,
I am using WSJTX v 2.2.1 (WSJT-Z mod 0.44)
Martin


locked Re: JTAlert 2.16.12 setup questions

HamApps Support (VK3AMA)
 

On 25/08/2020 1:50 pm, TomK wrote:

Actually, multicast is now fully supported so that both JTA & GD may communicate with WSJT simultaneously.

Though my deep hack days are over, I have found the following to be relevant and effective.
I’m sure I’ll quickly be corrected if I got something wrong 😉


Tom,

Looks good to me.

I'd mark your post with an "NFF", which from my long past Telco support days was shorthand for "No Fault Found", which we used when signing off the fault report cards.

de Laurie VK3AMA


locked Re: JTAlert 2.16.12 setup questions

TomK
 

Actually, multicast is now fully supported so that both JTA & GD may communicate with WSJT simultaneously.

Though my deep hack days are over, I have found the following to be relevant and effective.
I’m sure I’ll quickly be corrected if I got something wrong 😉

 

To use multicast to run WSJT + JTA + GD, you need to do the following to enable multicast:

  1. Configure WSJT to use multicast for its “reporting” UDP message stream.
    To do this, we set WSJT’s reporting UDP *address* (not port) from its default of 127.0.0.1 to any address within 239.00.0 - 239.255.255.255.
    The port can be left the same as it was, e.g., 2237 or whatever.
    I use address 239.0.0.1.  This should work on “most” home networks.  A few with special routing scopes may have issues but is unlikely for most.


  2. Configure JT-Alert to use multicast = Automatic. Nothing to do.
    JTA automatically syncs to WSJT’s reporting UDP address & port.  If address is in 239 range, it will operate in multicast mode.

  3. Configure GridTracker to use multicast
    a. You explicitly set GD’s address and port to the same as WSJT’s reporting settings.
    b. You ALSO need to click the radio-button “multicast” to enable it as it doesn’t imply it.

 

That should do the trick on most systems without an unusual or complex UDP net routing structure.

KT1TK

 

 

From: Support@HamApps.groups.io <Support@HamApps.groups.io> On Behalf Of Bill Pence
Sent: Monday, August 24, 2020 2:46 PM
To: Support@hamapps.groups.io
Subject: Re: [HamApps] JTAlert 2.16.12 setup questions

 

does gridtracker connect to wsjt via udp port 2237? 2 programs cannot both connect to a UDP port...

 

On Mon, Aug 24, 2020 at 1:53 PM <dgd@...> wrote:

Hello, I'm new to the hobby and new to digital and new to FT8. But, I'm making progress. I have WSJT-X working after a month. I have GridTracker working after a week. I'm now trying to get JTAlert to work with them.
I'm running Windows & Pro  Service Pack 1. I read that I needed to download and install  "Framework 4.7.2" (which is available for Windows 7 SP1 and later only) which I have done.
I'm not sure what Framework 4.7.2 is or what it does. Is there anything else I need to do? Apparently I'm missing something.
I'm getting this error.

any suggestions or help appreciated. KI5IPM


locked Re: JTAlert Feature

Osiel Rodriguez <oc.rodriguez@...>
 

Laurie,
Please keep me in mind next time you assemble a test team.  I would be honored to help out


On Aug 24, 2020, at 2:44 PM, HamApps Support (VK3AMA) <vk3ama.ham.apps@...> wrote:


On 25/08/2020 5:50 am, Osiel Rodriguez via groups.io wrote:

This feature may already be there, however, I’ll ask for it anyway.  Is there a way to have a separate window as a queue for the folks which are responding to my CQ call?  As an example, if I’m calling CQ JA, I’d like to have all the folks who are responding begin to queue up in a separate window and a count of the times they’ve call me displayed.  This would allow me to priorities my responses.

 

73 d

NG7E

Osiel,

Interesting you ask about this at this time. I have recently coded such a feature for the future JTAlertV3 (still many months from release).

While it will be available in JTAlertV3, I am expecting it may make it into JTAlertV2 as part of the current hybridization effort integrating existing JTAlertV3 modules into JTAlertV2.

Currently the code framework to make this hybridization work is in the hands of the Test team. Once that has passed and I am happy with it, I will be pushing forward with the introduction of key JTAlertV3 features/functionality in JTAlertV2.

No promises on when it will be available in JTAlertV2.

de Laurie VK3AMA
 


locked Re: JTAlert Feature

HamApps Support (VK3AMA)
 

On 25/08/2020 5:50 am, Osiel Rodriguez via groups.io wrote:

This feature may already be there, however, I’ll ask for it anyway.  Is there a way to have a separate window as a queue for the folks which are responding to my CQ call?  As an example, if I’m calling CQ JA, I’d like to have all the folks who are responding begin to queue up in a separate window and a count of the times they’ve call me displayed.  This would allow me to priorities my responses.

 

73 d

NG7E

Osiel,

Interesting you ask about this at this time. I have recently coded such a feature for the future JTAlertV3 (still many months from release).

While it will be available in JTAlertV3, I am expecting it may make it into JTAlertV2 as part of the current hybridization effort integrating existing JTAlertV3 modules into JTAlertV2.

Currently the code framework to make this hybridization work is in the hands of the Test team. Once that has passed and I am happy with it, I will be pushing forward with the introduction of key JTAlertV3 features/functionality in JTAlertV2.

No promises on when it will be available in JTAlertV2.

de Laurie VK3AMA
 


locked JTAlert Feature

Osiel Rodriguez
 

Laurie,

 

This feature may already be there, however, I’ll ask for it anyway.  Is there a way to have a separate window as a queue for the folks which are responding to my CQ call?  As an example, if I’m calling CQ JA, I’d like to have all the folks who are responding begin to queue up in a separate window and a count of the times they’ve call me displayed.  This would allow me to priorities my responses.

 

73 d

NG7E

 


locked Re: UDP Socket Conflict

HamApps Support (VK3AMA)
 

On 19/08/2020 7:15 am, Bud Governale wrote:
Each time I open N1MM when JTAlert is open I get the following message at the start of N1MM:

"Receiving UDP Socket 2237 for WSJT/JTDX Messages is already in use".

What do I do to resolve this apparent conflict.

Please help.

73,

Bud W3LL

Bud,

Your getting this error because N1MM and JTAlert both cannot connect to the same unicast IP address:port, 127.0.0.1:2237

The recent introduction of UDP multicast support to JTAlert avoids these type of conflicts, BUT based on my most recent searches it appears that N1MM does not support multicast (I may be wrong however, please advise if that is the case)

Since N1MM does not support multicast, your only option to run both JTAlert and N1MM concurrently is to set N1MM to listen to the "UDP Resend" traffic from JTAlert (don't set the port to that used by WSJT-X, they need to be different)
   

Having N1MM listening to JTAlert UDP does not allow N1MM to interact directly with WSJT-X. If you want that functionality you cannot have JTAlert running (due to the lack of multicast support by N1MM)

de Laurie VK3AMA



locked Re: JTALERTX stops displaying received calls

HamApps Support (VK3AMA)
 

On 24/08/2020 11:47 pm, Martin Blanz DL9SAD wrote:
I am using JTalert v 2.16.12 together with WSJT-X and Gridtracker  in Multicast mode.

After several minutes it stops decoding the received QSOs. What can I do ?

73, Martin DL9SAD

What version of WSJT-X?

de Laurie VK3AMA


locked Re: Alert Colors

HamApps Support (VK3AMA)
 

On 25/08/2020 12:51 am, Todd Shiffer wrote:
On top of what Laurie just said, don't forget about the alerts priority. Which can be found under settings > manage settings > alerts > alerts priority. So if you are seeing a CQ and it's not showing as a CQ more than likely it's coming up as something else say like "Wanted Grid". If "Wanted Grid" is before CQ then the color is going to be "Wanted Grid" & not CQ. So I suggest checking your Alert Priority order & put what you're looking for closer to the top of the list.

73
Todd, N3PKJ

A CQ is lower priority than other Wanted Alerts resulting in a Callsign being colored with the highest priority Alert so there wont be CQ color highlighting. To quickly identify which Callsigns generating Alerts that are also CQing enable the CQ indicators "Alerts -> CQ" section of the Settings.

eg. Here are two Callsigns generating a Wanted DXCC Alert. Note the "*" indicator and colored border, both  identifying SV1RRP as calling CQ.
   

de Laurie VK3AMA


locked Re: JTAlert 2.16.12 setup questions

HamApps Support (VK3AMA)
 

On 25/08/2020 1:23 am, dgd@... wrote:
Hello, I'm new to the hobby and new to digital and new to FT8. But, I'm making progress. I have WSJT-X working after a month. I have GridTracker working after a week. I'm now trying to get JTAlert to work with them.
I'm running Windows & Pro  Service Pack 1. I read that I needed to download and install  "Framework 4.7.2" (which is available for Windows 7 SP1 and later only) which I have done.
I'm not sure what Framework 4.7.2 is or what it does. Is there anything else I need to do? Apparently I'm missing something.
I'm getting this error.

any suggestions or help appreciated. KI5IPM
_._,_._,_



If you want to run JTAlert and Grid Tracker concurrently, than you need to have WSJT-X set to use a multicast IP address and set GT to use that address. Use an address in the 239.0.0.0 to 239.255.255.255 range. Nothing needs to be set in JTAlert.

See the JTAlert Help File, "Tutorials -> WSJT-X UDP Setup" section or the recent release notes, eg.
       Users who want to take advantage of concurrently running applications like DX
       Aggregator or Grid Tracker along-side JTAlert will need to set the WSJT-X UDP
       Server to a valid Multicast IP (in the 239.0.0.0 to 239.255.0.0 range) and set
       those applications to use that IP address. JTAlert requires zero-configuration.

Don't use the 224.0.0.1 address recommended by some it wont work.

de Laurie VK3AMA



locked Re: JTAlert 2.16.12 setup questions

David De Coons
 

2.16.12 and Grodtracker support multicast. 

Dave wo2x

Sent from my waxed string and tin cans. 

On Aug 24, 2020, at 2:46 PM, Bill Pence <pence.bill@...> wrote:


does gridtracker connect to wsjt via udp port 2237? 2 programs cannot both connect to a UDP port...

On Mon, Aug 24, 2020 at 1:53 PM <dgd@...> wrote:
Hello, I'm new to the hobby and new to digital and new to FT8. But, I'm making progress. I have WSJT-X working after a month. I have GridTracker working after a week. I'm now trying to get JTAlert to work with them.
I'm running Windows & Pro  Service Pack 1. I read that I needed to download and install  "Framework 4.7.2" (which is available for Windows 7 SP1 and later only) which I have done.
I'm not sure what Framework 4.7.2 is or what it does. Is there anything else I need to do? Apparently I'm missing something.
I'm getting this error.
<jtalert2.jpg>

any suggestions or help appreciated. KI5IPM


locked Re: JTAlert 2.16.12 setup questions

Bill Pence
 

does gridtracker connect to wsjt via udp port 2237? 2 programs cannot both connect to a UDP port...


On Mon, Aug 24, 2020 at 1:53 PM <dgd@...> wrote:
Hello, I'm new to the hobby and new to digital and new to FT8. But, I'm making progress. I have WSJT-X working after a month. I have GridTracker working after a week. I'm now trying to get JTAlert to work with them.
I'm running Windows & Pro  Service Pack 1. I read that I needed to download and install  "Framework 4.7.2" (which is available for Windows 7 SP1 and later only) which I have done.
I'm not sure what Framework 4.7.2 is or what it does. Is there anything else I need to do? Apparently I'm missing something.
I'm getting this error.

any suggestions or help appreciated. KI5IPM


locked JTAlert 2.16.12 setup questions

dgd@...
 

Hello, I'm new to the hobby and new to digital and new to FT8. But, I'm making progress. I have WSJT-X working after a month. I have GridTracker working after a week. I'm now trying to get JTAlert to work with them.
I'm running Windows & Pro  Service Pack 1. I read that I needed to download and install  "Framework 4.7.2" (which is available for Windows 7 SP1 and later only) which I have done.
I'm not sure what Framework 4.7.2 is or what it does. Is there anything else I need to do? Apparently I'm missing something.
I'm getting this error.

any suggestions or help appreciated. KI5IPM


locked JTALERTX stops displaying received calls

Martin Blanz DL9SAD
 

Hello,
I am using JTalert v 2.16.12 together with WSJT-X and Gridtracker  in Multicast mode.

After several minutes it stops decoding the received QSOs. What can I do ?

73, Martin DL9SAD


locked Re: Alert Colors

Todd Shiffer (N3PKJ)
 
Edited

On top of what Laurie just said, don't forget about the alerts priority. Which can be found under settings > manage settings > alerts > alerts priority. So if you are seeing a CQ and it's not showing as a CQ more than likely it's coming up as something else say like "Wanted Grid". If "Wanted Grid" is before CQ then the color is going to be "Wanted Grid" & not CQ. So I suggest checking your Alert Priority order & put what you're looking for closer to the top of the list.

73
Todd, N3PKJ


locked Re: Alert Colors

Robert Mayzer
 

Jim, W2JC sent me a note explaining the reasoning behind the operation of the Alerts along with a suggestion on trying split operation. I'm going to read up on that and give it a try. It sounds like a good way to deal with wanted calls

Thanks for the replies, I appreciate it.

Bob
N8VWQ.


locked Worked B4

Greg Foster
 

I  use standard ADIF file logging and I would like to set the Work B4 date to be the contest start. When I set the "worked B4 status date to the current date I still get worked before stations. I also created a new empty worked B4 data base file and it did not help, what am I missing?

Running Ver 2.16.10
Windows 7 
WSJTX 2.2.2

one thing I do not understand is the statement "If the QRG is not set in WSJT-X ....." Where do I set this?


Greg
VE3pj


locked Re: OT: moderation. or?

KD7YZ Bob
 

On 8/22/2020 10:07, neil_zampella wrote:

You may be moderated because a) you've not posted previously in any
group and its a precaution to keep people from SPAMMING the groups, or
b) you've not verified your email address.

Hi Neil.

Been on the "List" for at least ten years.
Haven't changed my email addy in ,uhhh, more than a decade.
Post every so often when I'm Flummoxed.

This being moderated started maybe 6 months to a year ago.

--
73
Bob KD7YZ
AMSAT LM #901


locked Re: OT: moderation. or?

neil_zampella
 

Mike ..

That was just the 'pinned' post at the very top of the group, had nothing to do with his issue.

You may be moderated because a) you've not posted previously in any group and its a precaution to keep people from SPAMMING the groups, or b) you've not verified your email address.

 

Neil, KN3ILZ


locked Re: OT: moderation. or?

KD7YZ Bob
 

On 8/21/2020 17:45, Michael Black via groups.io wrote:
Maybe it's the #TIP thing causing it?
Hi Mike.
Dunno what #TIP is, sri

--
73
Bob KD7YZ
AMSAT LM #901