Date   

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
 

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


locked Re: Does JTA get along with Gridtracker ?

neil_zampella
 

You may want to take a look at the beta version that has added UDP multicasting support.

 

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.

 

 


locked #Announcement : JTAlert with UDP Multicast support available for testing #Announcement

HamApps Support (VK3AMA)
 

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


locked Re: Access setting without WSJT-X open

James Fuller N7VR <n7vr@...>
 

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

On 8/10/2020 12:33 PM, Dave Garber wrote:
Why can't you?

sent by my LG phone

On Mon, Aug 10, 2020, 2:16 PM James Fuller N7VR via groups.io, <n7vr=n7vr.org@groups.io> wrote:
It would be nice if we could access settings for JTALERT when WSJT-x is
not open.

I often get requests to listen for a station attempting to complete an
award. I normally add the call sign to the wanted call sign list. This
notifies me when they are operating. I, also, like to change the
configuration of the link to programs like DXLABS, N1MM, Etc depending
on the upcoming operating situation. Having to bring up WSJT-x when the
radios are not on or disconnected is troublesome. Therefore I suggest
there be a way to access the settings without having WSJT-x up.

73

--
Jim Fuller
Montana Section Emergency Coordinator
N7VR -- http://www.n7vr.org
ARRL Life Member
CWOP-2 -- http://www.wxqa.com
Original ARECC contributor





-- 
Jim Fuller
Montana Section Emergency Coordinator
N7VR -- http://www.n7vr.org
ARRL Life Member
CWOP-2 -- http://www.wxqa.com
Original ARECC contributor


locked Re: Access setting without WSJT-X open

Dave Garber
 

Why can't you?

sent by my LG phone

On Mon, Aug 10, 2020, 2:16 PM James Fuller N7VR via groups.io, <n7vr=n7vr.org@groups.io> wrote:
It would be nice if we could access settings for JTALERT when WSJT-x is
not open.

I often get requests to listen for a station attempting to complete an
award. I normally add the call sign to the wanted call sign list. This
notifies me when they are operating. I, also, like to change the
configuration of the link to programs like DXLABS, N1MM, Etc depending
on the upcoming operating situation. Having to bring up WSJT-x when the
radios are not on or disconnected is troublesome. Therefore I suggest
there be a way to access the settings without having WSJT-x up.

73

--
Jim Fuller
Montana Section Emergency Coordinator
N7VR -- http://www.n7vr.org
ARRL Life Member
CWOP-2 -- http://www.wxqa.com
Original ARECC contributor





locked Re: Does JTA get along with Gridtracker ?

Jamie GOLLY
 

The answer is yes. 

Take a look at how I made it work, disregarding the radio settings itself. 






GL, Jamie
K6NGN 

On Aug 10, 2020, at 10:23 AM, Román Toledo via groups.io <rtoledo2002@...> wrote:

Sorry if this is not the place.  it's just that I just installed Gridtracker and noticed JTA  seemed to be disconnected or disabled by GRID

any replies are welcomed

thanks


locked Access setting without WSJT-X open

James Fuller N7VR <n7vr@...>
 

It would be nice if we could access settings for JTALERT when WSJT-x is not open.

I often get requests to listen for a station attempting to complete an award. I normally add the call sign to the wanted call sign list. This notifies me when they are operating. I, also, like to change the configuration of the link to programs like DXLABS, N1MM, Etc depending on the upcoming operating situation. Having to bring up WSJT-x when the radios are not on or disconnected is troublesome. Therefore I suggest there be a way to access the settings without having WSJT-x up.

73

--
Jim Fuller
Montana Section Emergency Coordinator
N7VR -- http://www.n7vr.org
ARRL Life Member
CWOP-2 -- http://www.wxqa.com
Original ARECC contributor


locked Re: Logging confusion

John Holmes W9ILY
 

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


locked Does JTA get along with Gridtracker ?

Román Toledo
 

Sorry if this is not the place.  it's just that I just installed Gridtracker and noticed JTA  seemed to be disconnected or disabled by GRID

any replies are welcomed

thanks


locked Re: Signal report display

Jim N6VH
 


On 8/10/2020 7:08 AM, VE3JI wrote:
Hi All

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

Ian , VE3JI 
_._,_._,_


Ian,

Try this - go to Settings/Manage Settings/Window. Check Show db (DXCC Name). See attached picture. Hope this helps.

73,

Jim N6VH


locked Re: 2.16.10 showing as 2.15.3 in "Program Updates"

Joe Bennett
 

On Sun, Aug 9, 2020 at 09:43 PM, HamApps Support (VK3AMA) wrote:
Try deleting the JTAlert.ini file located at %localappdata%\HamApps
Excellent!!! Worked like a charm.

When looking at the file date of the .ini file, it reminded me that this was not a fresh install of 2.16.10. I did have a previous version of JTAlert on this machine. Most likely 2.15.3...

Thank you for your help!



-Joe
KA3NAM

4441 - 4460 of 35517