Date   

locked Re: Does JTA get along with Gridtracker ?

B. Smith <bill.n3xl@...>
 

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


locked Re: Filtering for Date in JTAlert

HamApps Support (VK3AMA)
 

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


locked Filtering for Date in JTAlert

D. Scott MacKenzie
 

Hi All:

 

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


locked Re: Access setting without WSJT-X open

HamApps Support (VK3AMA)
 

On 11/08/2020 5:00 am, James Fuller N7VR via groups.io wrote:
Every time I open JTALert with out WSJT-x running, I get an error message waiting for WSjt-x.
Only option is to wait or close.
I9m Fuller N7VR

JTAlert does not complete its startup until WSJT-X or JTDX is running, as critical communication settings in JTAlert cannot be set until the settings of WSJT-X/ JTDX are determined.

JTAlert needs to be running, fully started, before you can access the Settings window.

FWIW, I am not aware of any other applications that provide gui access to their settings without the parent application being first started, JTAlert is no different.

de Laurie VK3AMA


locked Re: Signal report display

HamApps Support (VK3AMA)
 

On 11/08/2020 12:08 am, VE3JI wrote:
Hi All

is there any way to display the signal report on the JTAlert call sign block ??

Ian , VE3JI 

The signal report can be made visible by enabling the "View -> Show DXCC Names" menu option and setting the following in the Settings Window.
   

Alternatively, just hover your mouse over a Callsign and and view the resulting tooltip, top line.
   

Another alternative is to have the Decodes window open and have the "DB" column visible.

de Laurie VK3AMA


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

HamApps Support (VK3AMA)
 

On 11/08/2020 6:26 am, André C wrote:
Hello Laurie,  Do we need to delete our config file tui use the beta version ?



No, you don't need to delete the JTAlert or WSJT-X config files.

JTAlert provides for zero-configuration changes, everything is automatic.

You don't need to make any changes to WSJT-X unless you want to use DX Aggregator or Grid Tracker when they are set to use multicast UDP, in which case you need WSJT-X set to use the same Multicast IP address as those applications.

Please note, the multicast IP must be in the range 239.0.0.0 to 239.255.255.255

I used 239.255.0.0 in my testing.

de Laurie VK3AMA


locked Re: Does JTA get along with Gridtracker ?

B. Smith <bill.n3xl@...>
 

This is how I have JTAlert - WSJT-X and Log4OM working together (see pics below). You do not need UDP multicast.


locked JTAlert with UDP Multicast support available for testing #Beta

André C
 

Hello Laurie,  Do we need to delete our config file tui use the beta version ?


Garanti sans virus. www.avg.com


Le lun. 10 août 2020, à 15 h 04, HamApps Support (VK3AMA) <vk3ama.ham.apps@...> a écrit :
Users who want to test UDP Multicast support provided by the current Beta build of JTAlert can try this build...

https://dnl.HamApps.com/Beta/JTAlert.2.16.10.build.0012.Beta.Setup.exe

Please report your experiences/observations with this build. I am keen to hear from DX Aggregator and Grid Tracker users when those applications have been correctly set to use the WSJT-X multicast IP address (NOT the JTAlert UDP resend feature) and running along-side JTAlert

Note: This is a Beta release and will cease functioning after 4 weeks.

From the release notes...
    - 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.

de Laurie VK3AMA

5821 - 5840 of 36907