Date   

locked Re: Version 2.10.7 Problem

HamApps Support (VK3AMA)
 

On 21/12/2017 12:15 PM, W7JHR via Groups.Io wrote:
Just upgraded to JTAlert 2.10.7 and receiving this message shown below.  Nothing is showing up in any of the call sign display lines.  How do I fix?
Thanks,
Jim W7JHR

Jim,

Simply upgrading your JTAlert version would not cause JTAlert to stop receiving UDP data from WSJT-X, something else must have been changed at the same time.
  • Did you make changes to WSJT-X or install a new version?
  • What was the JTAlert version you were using prior to the 2.10.7 upgrade?
  • Did you ever have WSJT-X and JTAlert working together?
The correct setup for WSJT-X to work with JTAlert is documented in the JTAlert help file, Tutorials -> WSJT-X UDP Server topic.

de Laurie VK3AMA
   




locked Re: Version 2.10.7 Problem

Anthony W. DePrato
 

Just upgraded to JTAlert 2.10.7 and receiving this message shown below.
 Nothing is showing up in any of the call sign display lines.  How do
I fix? Thanks,
Jim W7JHR

Attachments:
CCCE76C1_B6BA_4176_862B_B6F43AB21D11.jpeg:
https://HamApps.groups.io/g/Support/attachment/17994/0
Jim
go into settings and report drop down about half way and check the 3 boxes
to the right of the port box.. should fix the problem.
73 Tony WA4JQS


locked Version 2.10.7 Problem

W7JHR@...
 

Just upgraded to JTAlert 2.10.7 and receiving this message shown below.  Nothing is showing up in any of the call sign display lines.  How do I fix?
Thanks,
Jim W7JHR


locked Re: Suggested Additional Capability

HamApps Support (VK3AMA)
 

On 19/12/2017 10:34 AM, Larry Banks wrote:
It would be nice if, when I clicked on an alert, that station’s current data would be pulled over to the transmit window.  If they ARE NOT calling CQ, then nothing else happens --  but I can now see the info I am looking for and get ready to call then when they do call CQ.
 
I don’t think this is currently available in JTAlert – at least I have not found it if it is.  Perhaps you could add it in some future version.

73 -- Larry -- W1DYJ


Larry,

It is not possible to setup WSJT-X per your request. Automated setup of WSJT-X from JTAlert (and any other 3rd party application working with WSJT-X) is only possible for CQing Callsigns.

This is due to restrictions within the WSJT-X UDP protocol. A restriction to avoid auto-mated QSO applications being developed fully controlling WSJT-X without user intervention. I fully support this WSJT-X UDP restriction and agree with the WSJT-X developers decision regarding this.

de Laurie VK3AMA
   


locked Re: Automatic Callsign Lookup

HamApps Support (VK3AMA)
 

On 20/12/2017 2:20 AM, Torsten - DL9GTB wrote:
Hi,

I use WSJT-X with JT-Alert and DX-Keeper for logging. It is very important to me to see who I have a QSO with. For this I have to click on the button "Q" for each QSO, so that the browser opens with QRZ.com. This is very complicated and delayed the display. Especially with FT-8 this should be fast. Is there a way that this happens automatically? I've already tried Pathfinder, but that does not work. The callsign is entered while but then I have to click on the button QRZ there again. It has to be possible somehow, right?

73 de Torsten - DL9GTB

Torsten,

I have added your request to the "todo list", but time to implement is unknown.

Since your using the DXLab suite, automatic QRZ lookup is already available via PathFinder...
  1. Set JTAlert to perform a PathFinder lookup on each WSJT-X "DX Call" change. JTAlert Settings, Applications -> DXLab Suite section.
  2. Set PathFinder QRZ.com "automatic login".
  3. On PathFinder window, Ctrl-Click QRZ button and set the "Auto" checkbox.

de Laurie VK3AMA
   


locked Re: Enter callsign without TX

HamApps Support (VK3AMA)
 

On 20/12/2017 7:50 AM, Torsten - DL9GTB wrote:
Hi,

when I double-click on a callsign in one of the upper rows, I immediately go on air and the callsign is entered below. Now you can see all information about the callsign. but I'm looking for a way to actively enter a call sign without going to tx. Just to see information about the callsign and if I already had a QSO with this country etc. The pop-up window is not enough for that. Is there a possibility?


Torsten,

The only way to populate the JTAlert Log fields and Confirmed Bands display is to change the "DX Call" field in WSJT-X.

JTAlert automatically populates the data in these areas whenever the WSJT-X "DX Call" is changed (ie a change in your QSO partner Callsign). There is no programmatic way to instruct WSJT-X to change the "DX Call" from JTAlert, the change can only happen at WSJT-X.

There are no plans at this time to alter this behaviour to allow population based on an arbitrary Callsign selected by the user.

I have added your request to the "Todo List", but implementation is not imminent and may not be part of JTAlert until sometime after the JTAlert V3 is released.

de Laurie VK3AMA
   
 


locked Re: Enter callsign without TX

Gilbert Baron <w0mn00@...>
 

Looking at this it is something I have gotten confused as a new user. I agree with those that think this right click or something similar is needed. If only to prevent unneeded and unwanted QRM, even though it would usually be short a new user might leave transmit on longer than the user really wanted to do.

 

W0MN EN34rb 44.08226 N 92.51265 W

Hierro candente, batir de repente

HP Laptop

 

From: Support@HamApps.groups.io [mailto:Support@HamApps.groups.io] On Behalf Of Rich McCabe
Sent: Wednesday, December 20, 2017 12:03
To: Support@HamApps.groups.io
Subject: Re: [HamApps] Enter callsign without TX

 

Actually, I think there is a window that this might work and doesn’t. Playing with that now.

 

 

 

From: Support@HamApps.groups.io [mailto:Support@HamApps.groups.io] On Behalf Of Barry N1EU
Sent: Wednesday, December 20, 2017 11:54 AM
To: Support@HamApps.groups.io
Subject: Re: [HamApps] Enter callsign without TX

 

"most everyone I know double clicks and then rapidly disables the TX"

The problem I find with this technique is that WSJT-X will miss decoding the current 15sec cycle if I go into xmit for even an instant.

73, Barry N1EU


locked Re: Enter callsign without TX

Rich McCabe
 

Actually, I think there is a window that this might work and doesn’t. Playing with that now.

 

 

 

From: Support@HamApps.groups.io [mailto:Support@HamApps.groups.io] On Behalf Of Barry N1EU
Sent: Wednesday, December 20, 2017 11:54 AM
To: Support@HamApps.groups.io
Subject: Re: [HamApps] Enter callsign without TX

 

"most everyone I know double clicks and then rapidly disables the TX"

The problem I find with this technique is that WSJT-X will miss decoding the current 15sec cycle if I go into xmit for even an instant.

73, Barry N1EU


locked Re: Enter callsign without TX

Rich McCabe
 

I have never lost a decode by doing this.  Double click the station in left window and quickly disable the TX.

 

 

 

From: Support@HamApps.groups.io [mailto:Support@HamApps.groups.io] On Behalf Of Barry N1EU
Sent: Wednesday, December 20, 2017 11:54 AM
To: Support@HamApps.groups.io
Subject: Re: [HamApps] Enter callsign without TX

 

"most everyone I know double clicks and then rapidly disables the TX"

The problem I find with this technique is that WSJT-X will miss decoding the current 15sec cycle if I go into xmit for even an instant.

73, Barry N1EU


locked Re: Enter callsign without TX

Barry N1EU
 

"most everyone I know double clicks and then rapidly disables the TX"

The problem I find with this technique is that WSJT-X will miss decoding the current 15sec cycle if I go into xmit for even an instant.

73, Barry N1EU


locked Re: Enter callsign without TX

Michael Black
 

I've submitted a patch for WSJT-X that does this.  Single click does what double-click does without Enable.  And the config option for double-click is removed as it's unneeded.  You probably won't see it until 1.8.2 is released as 1.8.1 will be a bug fix release.

de Mike W9MDB



On Wednesday, December 20, 2017, 8:13:30 AM CST, Rich McCabe <r.mccabe@...> wrote:


I have to agree with this. But I think this is a WSJT limitation and possibly not something JTAlert can do.

 

I wish you could send a station to the sequencing list without double clicking and activating the TX.  Typing the call and Generate standard messages is too much work/timing consuming for a mode that happens in 15 second intervals.

 

Rich

 

From: Support@HamApps.groups.io [mailto:Support@HamApps.groups.io] On Behalf Of Torsten - DL9GTB
Sent: Wednesday, December 20, 2017 4:58 AM
To: Support@HamApps.groups.io
Subject: Re: [HamApps] Enter callsign without TX

 

I think I know what you mean now. The input field DX Call, right? I had hoped that it could also be easier.

73 de Torsten - DL9GTB


locked Re: Enter callsign without TX

Brian D
 

"Rich McCabe" <r.mccabe@iowawebhosting.com> wrote:

As the OP said, it would be nice to have a way to evaluate them easier.
Honestly, most everyone I know double clicks and then rapidly disables the
TX. Not the best practice but gets the job done.
you then lose the decodes in that time slot. A right click option would be
better.

--
Brian D
G3VGZ G8AOE G3T
IO94im


locked Re: Enter callsign without TX

Michael Black
 

What you're missing is that many people use the double-click auto-enable option. 

de Mike W9MDB


On Wednesday, December 20, 2017, 8:42:58 AM CST, Tom Melvin <tom@...> wrote:


I’m a little confused.

Double clicking a call in wsjt - causes the DX Call box to be populated automatically, standard messages generated, that is carried over to JTAlert details of the user. When ready I just click enable TX and away things go.

I don’t need to type in calls or specifically generate messages - let wsjt populate all that - I don’t see that as time consuming.

What am I missing?

Tom
GM8MJV



On 20 Dec 2017, at 14:13, Rich McCabe <r.mccabe@...> wrote:

I have to agree with this. But I think this is a WSJT limitation and possibly not something JTAlert can do.

 

I wish you could send a station to the sequencing list without double clicking and activating the TX.  Typing the call and Generate standard messages is too much work/timing consuming for a mode that happens in 15 second intervals.

 

Rich

 

From: Support@HamApps.groups.io [mailto:Support@HamApps.groups.io] On Behalf Of Torsten - DL9GTB
Sent: Wednesday, December 20, 2017 4:58 AM
To: Support@HamApps.groups.io
Subject: Re: [HamApps] Enter callsign without TX

 

I think I know what you mean now. The input field DX Call, right? I had hoped that it could also be easier.

73 de Torsten - DL9GTB




locked Re: Enter callsign without TX

Torsten - DL9GTB
 

Some things are happening here now. I keep my settings as it is now. Maybe you can install an additional option in the context menu in a later version. Simply take over the callsign without going tx, just to look at the data.
 
The possibility to call up the QRZ.com page in the context menu I know, but I do not like it. I hope that it may be possible to have the QRZ.com page open automatically as soon as a callsign is active.

73 de Torsten - DL9GTB


locked Re: Enter callsign without TX

Tom Melvin
 

OK I have always run with the 'double click enable tx' switched off - lot easier to get prep work done and can decide when to start the call.

Everyone does it differently I guess - I find I have plenty of time to evaluate, set the correct tx freq etc.

Tom



On 20 Dec 2017, at 15:18, Rich McCabe <r.mccabe@...> wrote:

That works, but there are times when I am watching a couple DX in the left band activity window and waiting for one to 73 and like the instant click and TX. Adding them and then enabling TX takes too long.

 

As the OP said, it would be nice to have a way to evaluate them easier.  Honestly, most everyone I know double clicks and then rapidly disables the TX.  Not the best practice but gets the job done.

 

Rich

 

From: Support@HamApps.groups.io [mailto:Support@HamApps.groups.io] On Behalf Of DAVID BERNHEISEL via Groups.Io
Sent: Wednesday, December 20, 2017 8:55 AM
To: Support@HamApps.groups.io
Subject: Re: [HamApps] Enter callsign without TX

 

In WSJT-X settings>general tab behavior - double click enables tx� check box� Uncheck to avoid going into TX on double click......

 

On 12/20/2017 08:42, Tom Melvin wrote:

I�m a little confused.

 

Double clicking a call in wsjt - causes the DX Call box to be populated automatically, standard messages generated, that is carried over to JTAlert details of the user. When ready I just click enable TX and away things go.

 

I don�t need to type in calls or specifically generate messages - let wsjt populate all that - I don�t see that as time consuming.

 

What am I missing?

 

Tom

GM8MJV

 
 
 

On 20 Dec 2017, at 14:13, Rich McCabe <r.mccabe@...> wrote:



I have to agree with this. But I think this is a WSJT limitation and possibly not something JTAlert can do.

�

I wish you could send a station to the sequencing list without double clicking and activating the TX.� Typing the call and Generate standard messages is too much work/timing consuming for a mode that happens in 15 second intervals.

�

Rich

�

From: Support@HamApps.groups.io [mailto:Support@HamApps.groups.io] On Behalf Of Torsten - DL9GTB
Sent: Wednesday, December 20, 2017 4:58 AM
To: Support@HamApps.groups.io
Subject: Re: [HamApps] Enter callsign without TX

�

I think I know what you mean now. The input field DX Call, right? I had hoped that it could also be easier.

73 de Torsten - DL9GTB

 
 
 



locked Re: Enter callsign without TX

Rich McCabe
 

PS: to the OP, depending on the amount of monitor real-estate you have try right clicking the callsign in JTalert and opening in QRZ.

 

 

 

From: Support@HamApps.groups.io [mailto:Support@HamApps.groups.io] On Behalf Of Rich McCabe
Sent: Wednesday, December 20, 2017 9:19 AM
To: Support@HamApps.groups.io
Subject: Re: [HamApps] Enter callsign without TX

 

That works, but there are times when I am watching a couple DX in the left band activity window and waiting for one to 73 and like the instant click and TX. Adding them and then enabling TX takes too long.

 

As the OP said, it would be nice to have a way to evaluate them easier.  Honestly, most everyone I know double clicks and then rapidly disables the TX.  Not the best practice but gets the job done.

 

Rich

 

From: Support@HamApps.groups.io [mailto:Support@HamApps.groups.io] On Behalf Of DAVID BERNHEISEL via Groups.Io
Sent: Wednesday, December 20, 2017 8:55 AM
To: Support@HamApps.groups.io
Subject: Re: [HamApps] Enter callsign without TX

 

In WSJT-X settings>general tab behavior - double click enables tx� check box� Uncheck to avoid going into TX on double click......

 

On 12/20/2017 08:42, Tom Melvin wrote:

I�m a little confused.

 

Double clicking a call in wsjt - causes the DX Call box to be populated automatically, standard messages generated, that is carried over to JTAlert details of the user. When ready I just click enable TX and away things go.

 

I don�t need to type in calls or specifically generate messages - let wsjt populate all that - I don�t see that as time consuming.

 

What am I missing?

 

Tom

GM8MJV

 

 

 

On 20 Dec 2017, at 14:13, Rich McCabe <r.mccabe@...> wrote:

 

I have to agree with this. But I think this is a WSJT limitation and possibly not something JTAlert can do.

�

I wish you could send a station to the sequencing list without double clicking and activating the TX.� Typing the call and Generate standard messages is too much work/timing consuming for a mode that happens in 15 second intervals.

�

Rich

�

From: Support@HamApps.groups.io [mailto:Support@HamApps.groups.io] On Behalf Of Torsten - DL9GTB
Sent: Wednesday, December 20, 2017 4:58 AM
To: Support@HamApps.groups.io
Subject: Re: [HamApps] Enter callsign without TX

�

I think I know what you mean now. The input field DX Call, right? I had hoped that it could also be easier.

73 de Torsten - DL9GTB

 

 

 


locked Re: Enter callsign without TX

Rich McCabe
 

That works, but there are times when I am watching a couple DX in the left band activity window and waiting for one to 73 and like the instant click and TX. Adding them and then enabling TX takes too long.

 

As the OP said, it would be nice to have a way to evaluate them easier.  Honestly, most everyone I know double clicks and then rapidly disables the TX.  Not the best practice but gets the job done.

 

Rich

 

From: Support@HamApps.groups.io [mailto:Support@HamApps.groups.io] On Behalf Of DAVID BERNHEISEL via Groups.Io
Sent: Wednesday, December 20, 2017 8:55 AM
To: Support@HamApps.groups.io
Subject: Re: [HamApps] Enter callsign without TX

 

In WSJT-X settings>general tab behavior - double click enables tx� check box� Uncheck to avoid going into TX on double click......

 

On 12/20/2017 08:42, Tom Melvin wrote:

I�m a little confused.

 

Double clicking a call in wsjt - causes the DX Call box to be populated automatically, standard messages generated, that is carried over to JTAlert details of the user. When ready I just click enable TX and away things go.

 

I don�t need to type in calls or specifically generate messages - let wsjt populate all that - I don�t see that as time consuming.

 

What am I missing?

 

Tom

GM8MJV

 

 

 

On 20 Dec 2017, at 14:13, Rich McCabe <r.mccabe@...> wrote:



I have to agree with this. But I think this is a WSJT limitation and possibly not something JTAlert can do.

�

I wish you could send a station to the sequencing list without double clicking and activating the TX.� Typing the call and Generate standard messages is too much work/timing consuming for a mode that happens in 15 second intervals.

�

Rich

�

From: Support@HamApps.groups.io [mailto:Support@HamApps.groups.io] On Behalf Of Torsten - DL9GTB
Sent: Wednesday, December 20, 2017 4:58 AM
To: Support@HamApps.groups.io
Subject: Re: [HamApps] Enter callsign without TX

�

I think I know what you mean now. The input field DX Call, right? I had hoped that it could also be easier.

73 de Torsten - DL9GTB

 

 

 


locked Re: Enter callsign without TX

DAVID BERNHEISEL
 

In WSJT-X settings>general tab behavior - double click enables tx� check box� Uncheck to avoid going into TX on double click......


On 12/20/2017 08:42, Tom Melvin wrote:
I�m a little confused.

Double clicking a call in wsjt - causes the DX Call box to be populated automatically, standard messages generated, that is carried over to JTAlert details of the user. When ready I just click enable TX and away things go.

I don�t need to type in calls or specifically generate messages - let wsjt populate all that - I don�t see that as time consuming.

What am I missing?

Tom
GM8MJV



On 20 Dec 2017, at 14:13, Rich McCabe <r.mccabe@...> wrote:

I have to agree with this. But I think this is a WSJT limitation and possibly not something JTAlert can do.

�

I wish you could send a station to the sequencing list without double clicking and activating the TX.� Typing the call and Generate standard messages is too much work/timing consuming for a mode that happens in 15 second intervals.

�

Rich

�

From: Support@HamApps.groups.io [mailto:Support@HamApps.groups.io] On Behalf Of Torsten - DL9GTB
Sent: Wednesday, December 20, 2017 4:58 AM
To: Support@HamApps.groups.io
Subject: Re: [HamApps] Enter callsign without TX

�

I think I know what you mean now. The input field DX Call, right? I had hoped that it could also be easier.

73 de Torsten - DL9GTB





locked Re: Enter callsign without TX

Tom Melvin
 

I’m a little confused.

Double clicking a call in wsjt - causes the DX Call box to be populated automatically, standard messages generated, that is carried over to JTAlert details of the user. When ready I just click enable TX and away things go.

I don’t need to type in calls or specifically generate messages - let wsjt populate all that - I don’t see that as time consuming.

What am I missing?

Tom
GM8MJV



On 20 Dec 2017, at 14:13, Rich McCabe <r.mccabe@...> wrote:

I have to agree with this. But I think this is a WSJT limitation and possibly not something JTAlert can do.

 

I wish you could send a station to the sequencing list without double clicking and activating the TX.  Typing the call and Generate standard messages is too much work/timing consuming for a mode that happens in 15 second intervals.

 

Rich

 

From: Support@HamApps.groups.io [mailto:Support@HamApps.groups.io] On Behalf Of Torsten - DL9GTB
Sent: Wednesday, December 20, 2017 4:58 AM
To: Support@HamApps.groups.io
Subject: Re: [HamApps] Enter callsign without TX

 

I think I know what you mean now. The input field DX Call, right? I had hoped that it could also be easier.

73 de Torsten - DL9GTB




locked Re: Enter callsign without TX

Rich McCabe
 

I have to agree with this. But I think this is a WSJT limitation and possibly not something JTAlert can do.

 

I wish you could send a station to the sequencing list without double clicking and activating the TX.  Typing the call and Generate standard messages is too much work/timing consuming for a mode that happens in 15 second intervals.

 

Rich

 

From: Support@HamApps.groups.io [mailto:Support@HamApps.groups.io] On Behalf Of Torsten - DL9GTB
Sent: Wednesday, December 20, 2017 4:58 AM
To: Support@HamApps.groups.io
Subject: Re: [HamApps] Enter callsign without TX

 

I think I know what you mean now. The input field DX Call, right? I had hoped that it could also be easier.

73 de Torsten - DL9GTB

19841 - 19860 of 37779