Date   

locked Re: New version problems with Resend wsjt-x udp packets port 2334

Ross KE4BCN
 

Sorry about that I just started using Swisslog  today. Before I was using gridtracker on the same port with Log4om. I also just tried the beta version then the release version today.


locked Re: JTAlert with UDP Multicast support available for testing #Beta

B. Smith
 

Decided to try UDP Multicast with Grid Tracker and immediately saw positive benefits. Callsign lookups have more info and my QSLs are showing up according to the legend colors. Still getting feet wet. One thing I will mention in addition to Russ's settings is in JTA settings - Applications - WSJT-x/JTDX you should uncheck "Resend WSJT-X UDP packets..." Nice upgrade.

73, Bill N3XL  


locked Re: Problem with new version 2.16.11

HamApps Support (VK3AMA)
 

On 13/08/2020 10:10 am, André C wrote:
                    I have been using WSJT-X with JTalert and Gridtracker for a long time now.  My config is WSJT-X talk to JTalert on port 2237 and JTalert rebroadcast on port 2337 for Gridtracker to pick it up.  Until version 10 everything works beautifully.  But When I tried version 11 it didn’t seem to work with Gridtracker.  What do you suggest to modify ?

You need to set both WSJT-X and GridTracker to use a multicast IP address.
See this message... https://hamapps.groups.io/g/Support/message/31307

de Laurie VK3AMA


locked Problem with new version 2.16.11

André C
 

Hello Laurie,

                    I have been using WSJT-X with JTalert and Gridtracker for a long time now.  My config is WSJT-X talk to JTalert on port 2237 and JTalert rebroadcast on port 2337 for Gridtracker to pick it up.  Until version 10 everything works beautifully.  But When I tried version 11 it didn’t seem to work with Gridtracker.  What do you suggest to modify ?


locked Re: Alerts for New Continents and New Grids Seem to Be Inconsistent -- See Screen Shots

Laurie, VK3AMA
 



On 13/08/2020 7:08 am, Chuck Adams wrote:
How can Cueta Melilla be BOTH Worked B4 (coded in grey) AND a New Continent, New Country and New Grid at the same time?

B4 coloring applies to individual stations NOT Continents, Countries or Grids. Your image shows 2 stations from Cueta Melilla, one colored B4 and the other not (not previously worked) and it is generating the DXCC Alert because that DXCC is not flagged as no longer needed.

de Laurie VK3AMA


locked Re: Alerts for New Continents and New Grids Seem to Be Inconsistent -- See Screen Shots

Laurie, VK3AMA
 



On 13/08/2020 7:08 am, Chuck Adams wrote:
How can K0XB be BOTH already worked AND a NEW GRID (even after the QSO is logged)?


Your image does not show K0XB as already worked (there is no B4 shown). Is K0XB in your log?

de Laurie VK3AMA


locked Re: New version problems with Resend wsjt-x udp packets port 2334

HamApps Support (VK3AMA)
 

On 13/08/2020 7:13 am, ross.slater@... wrote:
I had same problem with beta version and now with release version. Resend wsjt-x udp packets port 2334 no longer works. I went back to version 2.16.10 and very thing works again.

Pity you didn't report the problem during the Beta test.

What application are you using that requires the use of that resend facility?

de Laurie VK3AMA




locked Re: Alerts for New Continents and New Grids Seem to Be Inconsistent -- See Screen Shots

g4wjs
 

On 12/08/2020 22:08, Chuck Adams wrote:

This seems to be a recent development.  Note these two screen shots:

ABOVE:  How can Cueta Melilla be BOTH Worked B4 (coded in grey) AND a New Continent, New Country and New Grid at the same time?

BTW, since when is Cueta Melilla a continent?  My maps say it is connected to Spain. 



How can K0XB be BOTH already worked AND a NEW GRID (even after the QSO is logged)?

Thanks and 73,

Chuck Adams
KV4VT

Hi Chuck,

Cueta & Melilla are in Africa.

The new continent alert is probably because you don't have Africa confirmed yet according to the criteria you have sent in the update screen.

Did you check that your QSO K0XB is really in your log?


--
73
Bill
G4WJS.


locked Re: Alerts for New Continents and New Grids Seem to Be Inconsistent -- See Screen Shots

Larry Banks
 

Ceuta Melilla in in Africa.  I believe B4 applies to the station.

73 -- Larry -- W1DYJ

 

Sent: Wednesday, August 12, 2020 17:08
Subject: [HamApps] Alerts for New Continents and New Grids Seem to Be Inconsistent -- See Screen Shots
 

This seems to be a recent development.  Note these two screen shots:

ABOVE:  How can Cueta Melilla be BOTH Worked B4 (coded in grey) AND a New Continent, New Country and New Grid at the same time?

BTW, since when is Cueta Melilla a continent?  My maps say it is connected to Spain.



How can K0XB be BOTH already worked AND a NEW GRID (even after the QSO is logged)?

Thanks and 73,

Chuck Adams
KV4VT





locked New version problems with Resend wsjt-x udp packets port 2334

Ross KE4BCN
 

I had same problem with beta version and now with release version. Resend wsjt-x udp packets port 2334 no longer works. I went back to version 2.16.10 and very thing works again.


locked Alerts for New Continents and New Grids Seem to Be Inconsistent -- See Screen Shots

Chuck Adams
 

This seems to be a recent development.  Note these two screen shots:

ABOVE:  How can Cueta Melilla be BOTH Worked B4 (coded in grey) AND a New Continent, New Country and New Grid at the same time?

BTW, since when is Cueta Melilla a continent?  My maps say it is connected to Spain. 



How can K0XB be BOTH already worked AND a NEW GRID (even after the QSO is logged)?

Thanks and 73,

Chuck Adams
KV4VT





locked Re: JTAlert with UDP Multicast support available for testing #Beta

Russ Ravella
 

Hi Laurie,

Thanks for the response.

Right.  I’d been using GT with JTA that way until now and wanted to explicitly mention they can be used independently now and that is working perfectly.  JTA is never going anywhere in my shack so if the other apps had to run via resend from it, then that’s the way it was going to be.  No longer an issue.  Also, since performing an operation from either app “changes the state” of WSJT-X (selecting a station, initiating TX, …), the other app sees it and shows it doing so, essentially mirroring the operation as well.   Very cool.

It’s pretty amazing you’re still working so hard to maintain the V2 we’re all using - even going so far as to work out this neat piece of fancy footwork for us - while also bringing up your V3 which will eventually obsolete it.  Just wanted to point that out too.  We can't appreciate you enough Laurie, thank you again !
Russ, KR6W


On Aug 12, 2020, at 11:30 AM, HamApps Support (VK3AMA) <vk3ama.ham.apps@...> wrote:

On 12/08/2020 4:11 pm, Russ Ravella via groups.io wrote:
Just wanted to report I successfully updated JTA to 2.16.10 and have it running together with GridTracker with no issues so far.  It works perfectly as far as I can see.  Thank you yet again, Laurie !

For anyone interested in specific set-up steps, here's what I used:

        - set WSJT-X >Settings>Reporting>UPD Server to

IP = 239.255.0.0, Port = 2334                                          (using the IP Laurie tested with though anything in the MultiCast IP range (239.0.0.0 to 239.255.255.255) should work)

- set GT >Settings>General>Receive UDP Messages to

MultiCast?>enable, IP = 239.255.0.0, Port = 2334

(note: GT’s IP box stays yellow for some reason)

- no change to JTA; it detects MultiCast and configures automatically

- either can control WSJT-X and they recognize and display commands set by the other

- restart may be necessary


Russ,

Tnx for the positive report.

- either can control WSJT-X and they recognize and display commands set by the other


The point that many people are missing about multicast is that it allows multiple WSJT-X cooperating applications like JTAlert, DX Aggregator & Grid Tracker to be run simultaneously and independently. Prior to multicast, DX Aggregator and Grid Tracker were dependant on using the JTAlert UDP resend mechanism which didn't support either application directly controlling WSJT-X.

de Laurie VK3AMA



locked JTAlert 2.16.11 is available #Announcement #NewRelease

HamApps Support (VK3AMA)
 

The latest JTAlert version 2.16.11 is now available @ https://hamapps.com/JTAlert/

de Laurie VK3AMA

Release Notes.

2.16.11 (12-Aug-2020)

  *** Includes Callsign database file version 2020-08-12 (2020-Aug-12)

  New Features:

    - UDP Multicast: JTAlert now supports joining a UDP multicast group IP address
       when interacting with WSJT-X. This is automatic, using the settings as defined
       for each detected WSJT-X instance discovered running on the same PC as JTAlert.
       Multicast support across multiple PCs/Networks is not supported.
       Current JTAlert/WSJT-X setups, either single or multiple instance will operate
       as normal without any changes to WSJT-X settings.
       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.


  Changes:

    - DXCC Country Names: Names starting with "St." changed to "Saint".
       "South Africa" renamed "Republic of South Africa"

    - JTAlertV2.Manager.exe process: JTAlert will close and present an error window
       if it was unable to start the JTAlertV2.Manager.exe process. This process is
       now critical to decodes processing (due to UDP multicast implementation)

    - DXKeeper homeQTH selections: "homeQTH" has been renamed in the Settings and
       help file to "myQTH" per the current DXKeeper naming convention.

  Fixes:

    - JTAlert failing to start or closing shortly after starting with a
       "The requested action with this object has failed" error window shown.

    - TX Watchdog Alert: Options not being shown in the Settings Window (2.16.9 defect).

    - No audio output: Multiple JTAlert restarts required to get Alert sounds to play.

    - Ignored Callsigns: Ignored colors not applied if worked before (B4).


locked Re: JTAlert with UDP Multicast support available for testing #Beta

HamApps Support (VK3AMA)
 

On 12/08/2020 4:11 pm, Russ Ravella via groups.io wrote:
Just wanted to report I successfully updated JTA to 2.16.10 and have it running together with GridTracker with no issues so far.  It works perfectly as far as I can see.  Thank you yet again, Laurie !

For anyone interested in specific set-up steps, here's what I used:

        - set WSJT-X >Settings>Reporting>UPD Server to

IP = 239.255.0.0, Port = 2334                                          (using the IP Laurie tested with though anything in the MultiCast IP range (239.0.0.0 to 239.255.255.255) should work)

- set GT >Settings>General>Receive UDP Messages to

MultiCast?>enable, IP = 239.255.0.0, Port = 2334

(note: GT’s IP box stays yellow for some reason)

- no change to JTA; it detects MultiCast and configures automatically

- either can control WSJT-X and they recognize and display commands set by the other

- restart may be necessary


Russ,

Tnx for the positive report.

- either can control WSJT-X and they recognize and display commands set by the other

The point that many people are missing about multicast is that it allows multiple WSJT-X cooperating applications like JTAlert, DX Aggregator & Grid Tracker to be run simultaneously and independently. Prior to multicast, DX Aggregator and Grid Tracker were dependant on using the JTAlert UDP resend mechanism which didn't support either application directly controlling WSJT-X.

de Laurie VK3AMA


locked Re: JTAlert with UDP Multicast support available for testing #Beta

w2eck
 

Bill - thanks - that explanation was very helpful and succinct.

73 Paul


locked Re: JTAlert with UDP Multicast support available for testing #Beta

Russ Ravella
 

Just wanted to report I successfully updated JTA to 2.16.10 and have it running together with GridTracker with no issues so far.  It works perfectly as far as I can see.  Thank you yet again, Laurie !

For anyone interested in specific set-up steps, here's what I used:

        - set WSJT-X >Settings>Reporting>UPD Server to

IP = 239.255.0.0, Port = 2334                                          (using the IP Laurie tested with though anything in the MultiCast IP range (239.0.0.0 to 239.255.255.255) should work)

- set GT >Settings>General>Receive UDP Messages to

MultiCast?>enable, IP = 239.255.0.0, Port = 2334

(note: GT’s IP box stays yellow for some reason)

- no change to JTA; it detects MultiCast and configures automatically

- either can control WSJT-X and they recognize and display commands set by the other

- restart may be necessary



locked Re: JTAlert with UDP Multicast support available for testing #Beta

g4wjs
 

On 12/08/2020 00:15, w2eck wrote:
Dev
So JTAlert is doing the one to many broadcasting to .........who/what. ? Give us an example of how this might be helpful to us?

73 Paul
Paul,

if you don't understand the networking details here that's not a problem. This is a feature of the WSJT-X UDP Message Protocol that allows multiple applications to interoperate with one or more WSJT-X instances concurrently. It is something application developers need to understand, as a user you don't have to do anything other than choose a multicast group address that all the interoperating applications are going to listen for traffic on.

You are looking for something that you don't need to know about. Your choice is to use a unicast server address like 127.0.0.1 and only have one application interoperate with WSJT-X, or choose a multicast group address like 239.255.0.0 and have as many multicast capable applications as you like interoperating with one or more WSJT-X instances. All that is happening from the user perspective is that a limitation is being removed.



--
73
Bill
G4WJS.


locked Re: JTAlert with UDP Multicast support available for testing #Beta

Michael Black
 

WSJT-X multicasts it's status packets from multiple instances as with Flex Radio systems.
JTAlert can then see those status packets too.




On Tuesday, August 11, 2020, 06:15:39 PM CDT, w2eck <eckerpw@...> wrote:


Dev
So JTAlert is doing the one to many broadcasting to .........who/what. ? Give us an example of how this might be helpful to us?

73 Paul


locked Re: JTAlert with UDP Multicast support available for testing #Beta

w2eck
 

Dev
So JTAlert is doing the one to many broadcasting to .........who/what. ? Give us an example of how this might be helpful to us?

73 Paul


locked Re: JTAlert with UDP Multicast support available for testing #Beta

Dave Garber
 

i got that explanation, but I still dont see it helping me.  I can already have wsjt, jtalert, gridtracker and my log all working now.   maybe speed is difference.  I will be watching progress

Dave Garber
VE3WEJ / VE3IE


On Tue, Aug 11, 2020 at 1:57 PM w2eck <eckerpw@...> wrote:
So for me and I am sure just a few others, can someone explain exactly what Multicast is , and what benefit it brings us??

thanks & 73
Paul
w2eck

4421 - 4440 of 35529