Date   

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


locked Re: Does JTA get along with Gridtracker ?

Román Toledo
 

I want to thank  you all for the information supplied. I will put your replies to work. I really appreciate your time and help.

Best Regards

Roman Toledo Casabona


locked Re: NO decodes

Laurie, VK3AMA
 

On 12/08/2020 12:10 am, Lawrence Godek wrote:
I watched WSJt 2.2.1 this morning for a while.  It appears that if there is a failure to show decodes in that app it is at the end of the minute cycle.  In 1 out of about 8 minutes i actually showed decodes but in the other 7 minutes nothing showed up or changed in the Band activity window.  Short term monitor i know but that was all the time i had.  I do not see any decodes in JTalert at all unless i am watching the view>decode window.  No idea why.

Just an FYI.

Larry W0OGH
If decodes are being displayed in the JTAlert Decodes window that indicates the WSJT-X -> JTAlert -> Decodes pipeline is working correctly.

If the main JTAlert window is not displaying Callsigns or a subset of Callsigns while the Decodes window is showing all Callsigns that indicates you have one or more JTAlert Alert Filters enabled and the missing Callsigns are not passing your Filter(s).

No decodes showing in WSJT-X indicates your running with the "Show new period decodes at top" option set. Turn that option off or get into the habit of manually erasing the decodes on a periodic basis. This is caused by a known defect within the QT Framework (if I recall correctly) used in building WSJT-X.

de Laurie VK3AMA


locked Re: Does JTA get along with Gridtracker ?

B. Smith
 

All the info in my message pertains to Gridtracker UDP interoperations with JTAlert, WSJT-X, and my flavor of logging software. I felt that going beyond the simple use of GridTracker and JTAlert together that logging might as well be thrown into the mix. In my previous message the first window was Log4OM settings, the second window was JTAlert settings, and the third window was GridTracker settings. Here is my WSJTX settings for UDP that I forgot to include. Please excuse my lack of explanatory information, as I am used to communicating with engineers.


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

Dev Null
 

Multicast is the opposite of unicast - which is what you normally do, when you browse a web or send an email. It allows a "one-to-many" relationship, just like broadcasting. It actually is broadcasting... more efficient as there is no handshake to determine if packets are sent successfully.

Not much use out on the public internet, but very handy within your local network... or on the same computer.


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

g4wjs
 

On 11/08/2020 18:57, w2eck 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
Hi Paul,

answered previously here:

https://hamapps.groups.io/g/Support/message/31202

73
Bill
G4WJS.



--
73
Bill
G4WJS.


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

w2eck
 

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


locked Wanted and Ignored callsign on JTAlert

asobel@...
 

Laurie

Please make the Wanted and Ignored callsign of JTAlert become band dependent such as Wanted DXCC. The current situation creates problems. Examples: I  did  work VK1ABC on 20m and I want to work it on all all bands but I get infinite alerts from it on 20m. VK2PQR  is not wanted on 20m but wanted on 6m.

Amos 4X4MF


locked NO decodes

Lawrence Godek
 

I watched WSJt 2.2.1 this morning for a while.  It appears that if there is a failure to show decodes in that app it is at the end of the minute cycle.  In 1 out of about 8 minutes i actually showed decodes but in the other 7 minutes nothing showed up or changed in the Band activity window.  Short term monitor i know but that was all the time i had.  I do not see any decodes in JTalert at all unless i am watching the view>decode window.  No idea why.

Just an FYI.

Larry W0OGH


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

Koike Toshiya
 

Grid Tracker is running in beta at the same time.
It works fine.
I think the multicast version is very good.
Thank you Laurie.

de JL1JVT Toshiya


locked Re: Ignored CallsignsNot Coloured

HamApps Support (VK3AMA)
 

On 9/08/2020 8:51 am, Tom Job wrote:

Yes, the Ignored Callsign appears as it should if it is not B4.   I checked several random calls on 40m FT8 and it worked well.  Then I tried a couple that were B4 and it failed.

 

So, there ya go! J

 

73…..Tom


Tom,

FYI, this has been corrected for the next release (likely in 2 days time).

de Laurie VK3AMA


locked Re: Does JTA get along with Gridtracker ?

neil_zampella
 

Um ... this thread has nothing to do with Log4OM, the writer was asking about Gridtracker.

Neil, KN3ILZ


locked Re: Filtering for Date in JTAlert

D. Scott MacKenzie
 

Thank you Laurie – I followed Dave’s instructions and got it done.  Thank you for your help

 

From: Support@HamApps.groups.io <Support@HamApps.groups.io> On Behalf Of HamApps Support (VK3AMA)
Sent: Monday, August 10, 2020 8:35 PM
To: Support@HamApps.groups.io
Subject: Re: [HamApps] Filtering for Date in JTAlert

 

On 11/08/2020 8:33 am, D. Scott MacKenzie wrote:

In addition, no there is no way to restrict the log scanning for an individual Alert type to a different Log.


While I said the above about using different logs not being possible, using DXKeeper myQTH IDs will have the same affect as having different diffent (filtered) log for the State Alert. Using DXKeeper, set it to have different myQTH IDs for your different operating locations and then set the State Alert to use your current myQTH ID. The "Rebuild Alert Database" will consider only log QSOs from the enabled myQTH ID.

eg. here I have the State Alert set to only use QSO that have the "VK3AMA_QTH_1" myQTH ID, while the DXCC Alert has no myQTH ID set so all QSOs in the log are considered.



de Laurie VK3AMA


locked Re: Filtering for Date in JTAlert

HamApps Support (VK3AMA)
 

On 11/08/2020 8:33 am, D. Scott MacKenzie wrote:
In addition, no there is no way to restrict the log scanning for an individual Alert type to a different Log.

While I said the above about using different logs not being possible, using DXKeeper myQTH IDs will have the same affect as having different diffent (filtered) log for the State Alert. Using DXKeeper, set it to have different myQTH IDs for your different operating locations and then set the State Alert to use your current myQTH ID. The "Rebuild Alert Database" will consider only log QSOs from the enabled myQTH ID.

eg. here I have the State Alert set to only use QSO that have the "VK3AMA_QTH_1" myQTH ID, while the DXCC Alert has no myQTH ID set so all QSOs in the log are considered.



de Laurie VK3AMA


locked Re: Logging confusion

HamApps Support (VK3AMA)
 

On 11/08/2020 4:14 am, John Holmes W9ILY wrote:
That is really great news, Laurie. The current importer was a huge improvement and I'm looking forward to the next one. As you know, my log is rather large, over 225,000 now.
73,
John W9ILY

John,

I would appreciate access to your current 225K QSO adif file.

While I can create a large file with dummy data for testing, real-world data that is subject to unexpected user/program errors  is preferred.

If your willing to share you file, send a zipped copy to vk3ama.ham.apps [at] gmail.com

Thanks
de Laurie VK3AMA


locked Re: Filtering for Date in JTAlert

D. Scott MacKenzie
 

I am sorry Laurie – I didn’t see your response.  I apologize. 

 

From: Support@HamApps.groups.io <Support@HamApps.groups.io> On Behalf Of HamApps Support (VK3AMA)
Sent: Monday, August 10, 2020 6:32 PM
To: Support@HamApps.groups.io
Subject: Re: [HamApps] Filtering for Date in JTAlert

 

On 11/08/2020 8:26 am, D. Scott MacKenzie wrote:

When scanning the log in JTAlert, is there a way to set it so it only looks at QSOs after a certain date?  For instance, I keep one log with all my contacts.  However, I moved 1/1/2000, so that my QTH for WAS changed.  I need to figure out the needed states based on the log data after 1/1/2000 – JTAlert works perfect for this.  I presently use DXLabs.

 

If there is no way to scan logs after a certain date, then I guess I would need to establish an alternative log to search with only WAS contacts?  Can I scan one log (containing the extracted WAS contacts), and another containing the DX files (whole log)?

 

Thank you

 

Scott aka KB0FHP


Previously answered here https://hamapps.groups.io/g/Support/message/31261

In addition, no there is no way to restrict the log scanning for an individual Alert type to a different Log.

de Laurie VK3AMA

5361 - 5380 of 36454