Date   

locked Re: JT alert and QRZ Logbook

HamApps Support (VK3AMA)
 

On 15/01/2020 7:10 am, Ken Desjardins wrote:
Hi Laurie, Any progress with this issue?

Ken,

I previously sent you a link to the latest JTAlert Beta build (sent 2-Jan), did that not correct your QRZ problem?
I couldn't find a response from you so I assume you didn't try it, is that the case?

All other users who received the Beta builds reported back that it corrected their intermittent problems with online logging, xml lookups, DXLab DDE, etc.

The next public release of JTAlert is 2 days away, you may want to for that and report back if your problems persist.

de Laurie VK3AMA


locked Re: TCP: QSP Data Transfer Socket Operation Timed out #FT8

HamApps Support (VK3AMA)
 

On 15/01/2020 6:11 am, Bob Davet wrote:
"TCP QSO Data transfer socket operation timed out"

Click on OK and it goes away.

This comes up when it logs the QSO into HRD.

This does not appear (as best I can remember) to be a JTAlert generated error message. Is this a Windows or HRD message?

Please post an image of the offending error window. DON'T post a capture of your entire desktop, just the error window is all that is needed.

de Laurie VK3AMA


locked Re: Ignore option

HamApps Support (VK3AMA)
 

On 15/01/2020 2:58 am, WB5JJJ - George wrote:
But on a busy band, 75% of the callsigns fall into the "I don't need/want them" category, but still clutter the display. 

--
73's
George - WB5JJJ

Simple, set JTAlert to not show any callsigns not generating an Alert via the "Alerts -> Filters" menu.

de Laurie VK3AMA


locked Re: Ignore option

HamApps Support (VK3AMA)
 

On 15/01/2020 2:31 am, Bill Barrett wrote:
Mainly interested DX and with the high number of decodes on bands like 40 & 20 would like an option to to "ignore USA" decodes. Looked around but failed to see that feature in the app. Did I miss it?.

Thanks, could not operate digital without your terrific app.

--
Bill Barrett W2PKY

Bill,

While JTAlert itself doesn't provide for explicit exclusion of Country of origin decodes, the Decodes window does. Make the "Country Name" column visible then right click the Country name of any USA decode and select hide. You can do this for multiple countries. You can save this as a Filter and apply it at any time. Once

If you don't want to use the Decodes window, you can always set JTAlert to not show any callsigns not generating an Alert via the "Alerts -> Filters" menu.

de Laurie VK3AMA


locked Re: JT alert and QRZ Logbook

Ken Desjardins
 

Hi Laurie, Any progress with this issue?


locked TCP: QSP Data Transfer Socket Operation Timed out #FT8

Bob Davet
 

Fixed the UDP problem I posted about before. Forgot to check the 3 boxes that related to UDP.

Now everything seems to be working but I am getting this error now:

"TCP QSO Data transfer socket operation timed out"

Click on OK and it goes away.

This comes up when it logs the QSO into HRD.

This is for my dad's system. He has his regular logbook. With FT8, he has those going into a different logbook. (don't know why, that is how he wants it).
I'm guessing it has to do with that.

What do I need to look at or tweak to make this error go away and not show up everytime a QSO is logged?

Thanks

Bob
W8RID


locked Re: Ignore option

WB8ASI Herb
 

There all kinds of filtering options on the Decode History window.  I like using it rather than the regular call display.

On January 14, 2020 at 10:58 AM WB5JJJ - George <wb5jjj@...> wrote:

Along the same lines, I would like to see an option to NOT display any new callsigns from a State or DXCC that is already confirmed.  This alone would greatly reduce the items in the display.  I run 3 lines of 6 and most times, that is sufficient as I also filter only LoTW to be shown as well.  But on a busy band, 75% of the callsigns fall into the "I don't need/want them" category, but still clutter the display. 

--
73's
George - WB5JJJ

 


locked Re: Ignore option

Bry Carling AF4K <af4k@...>
 

You might know that there is another program that does all of that for you.
JTDX

Best regards - Bry Carling, AF4K





On Jan 14, 2020, at 11:11 AM, WB5JJJ - George <wb5jjj@...> wrote:

Along the same lines, I would like to see an option to NOT display any new callsigns from a State or DXCC that is already confirmed.  This alone would greatly reduce the items in the display.  I run 3 lines of 6 and most times, that is sufficient as I also filter only LoTW to be shown as well.  But on a busy band, 75% of the callsigns fall into the "I don't need/want them" category, but still clutter the display. 

--
73's
George - WB5JJJ


locked Re: Ignore option

WB5JJJ - George
 

Along the same lines, I would like to see an option to NOT display any new callsigns from a State or DXCC that is already confirmed.  This alone would greatly reduce the items in the display.  I run 3 lines of 6 and most times, that is sufficient as I also filter only LoTW to be shown as well.  But on a busy band, 75% of the callsigns fall into the "I don't need/want them" category, but still clutter the display. 

--
73's
George - WB5JJJ


locked Ignore option

Bill Barrett
 

Hello Laurie-

Mainly interested DX and with the high number of decodes on bands like 40 & 20 would like an option to to "ignore USA" decodes. Looked around but failed to see that feature in the app. Did I miss it?.

Thanks, could not operate digital without your terrific app.

--
Bill Barrett W2PKY
352-437-4758


--
Bill Barrett
352-437-4758


locked Re: No sound??

Neil Foster
 

Thanks Laurie for the tip and a great program.!!
Neil    N4FN


locked Re: DxMarathon alert and B4 QSO - SOLVED

Carlo - IK2RPE
 

Yes, Yes, Yes, this year I forgot it…

 

Thank you so much and HNY

 

 

 

Carlo  IK2RPE

 

 

 

Da: Support@HamApps.groups.io <Support@HamApps.groups.io> Per conto di HamApps Support (VK3AMA)
Inviato: martedì 14 gennaio 2020 13:21
A: Support@HamApps.groups.io
Oggetto: Re: [HamApps] DxMarathon alert and B4 QSO

 

On 14/01/2020 11:06 pm, Carlo - IK2RPE wrote:

Doing the DxMarathon 2020 and having set the relevant alarms, I discovered that a Call for which I had a B4 warning (on that band, also grey colored) BUT that I need this year for DxNarathon is NOT colored as needed (neither the sound is working).
Did I miss something?

Thanks in advance

Carlo  IK2RPE

Carlo,

Set the Ignore B4 Date to 1st Jan 2020. Settings Window, "Alerts -> Worked B4" section.

   

de Laurie VK3AMA


locked Re: DxMarathon alert and B4 QSO

HamApps Support (VK3AMA)
 

On 14/01/2020 11:06 pm, Carlo - IK2RPE wrote:
Doing the DxMarathon 2020 and having set the relevant alarms, I discovered that a Call for which I had a B4 warning (on that band, also grey colored) BUT that I need this year for DxNarathon is NOT colored as needed (neither the sound is working).
Did I miss something?

Thanks in advance

Carlo  IK2RPE
Carlo,

Set the Ignore B4 Date to 1st Jan 2020. Settings Window, "Alerts -> Worked B4" section.

   

de Laurie VK3AMA


locked DxMarathon alert and B4 QSO

Carlo - IK2RPE
 

Doing the DxMarathon 2020 and having set the relevant alarms, I discovered that a Call for which I had a B4 warning (on that band, also grey colored) BUT that I need this year for DxNarathon is NOT colored as needed (neither the sound is working).
Did I miss something?

Thanks in advance

Carlo  IK2RPE


locked Re: Multiple udp

g4wjs
 

On 14/01/2020 09:25, Andy M0NKR via Groups.Io wrote:
I’m running WSJT- x 2.1.2 and JT alert 2.15.6 along with logger32.

What is the best way to receive UDP info on all programs?

As jtalert wont receive the udp because logger32 udp map is, is there a way to have all running

73
Andy
M0NKR 

Hi Andy,

in theory it works by using a multicast address group rather than the unicast 127.0.0.1 address, unfortunately the tools used to create JTAlert do not directly support multicast addressing so for now you must use a workaround that Laurie has provided. JTAlert can resend incoming UDP traffic from WSJT-X to a new server address/service port pair. This partially solves the issue, the missing part is that return traffic (in your case from Logger32 back to WSJT-X) is not handled so some functions may not work.

Set Logger32 to listen for WSJT-X UDP protocol traffic on the new service port, e.g. 2234 in the example above.


--
73
Bill
G4WJS.


locked Multiple udp

Andy M0NKR
 

I’m running WSJT- x 2.1.2 and JT alert 2.15.6 along with logger32.

What is the best way to receive UDP info on all programs?

As jtalert wont receive the udp because logger32 udp map is, is there a way to have all running

73
Andy
M0NKR


locked Re: No sound??

HamApps Support (VK3AMA)
 

On 13/01/2020 5:20 am, Neil wrote:
Recently I have set up my Elecraft K 2 to work FT 8 in QRP. I have changed my call sign from N4FN to N4FN/QRP. All is working fine and contacts are being made, however when a connection is made even tho I have sound turned on I no longer get the sound associated with a contact. I wonder why?? Is it because it is no longer a "standard call"?
Thanks
Neil   N4FN

If you have set JTAlert with the Station Callsign of "N4FN/QRP" then the own call alert will only get triggered on that Callsign, it will not trigger if someone calls you without the "/QRP" suffix.

If you want to get alerted on "N4FN" as well, open the JTAlert Setting window , go to the "Alerts -> Own Call" section and add "N4FN" as one of the alert callsigns.

de Laurie VK3AMA



locked No sound??

Neil <n4fn.neil@...>
 

Recently I have set up my Elecraft K 2 to work FT 8 in QRP. I have changed my call sign from N4FN to N4FN/QRP. All is working fine and contacts are being made, however when a connection is made even tho I have sound turned on I no longer get the sound associated with a contact. I wonder why?? Is it because it is no longer a "standard call"?
Thanks
Neil   N4FN


locked Re: Hello

Bry Carling AF4K <af4k@...>
 

Thank you for understaning Mike, and I will be delighted to try it over the next couple of days as I get time...

Sincerely,

73 - Brian "Bry" Carling, AF4K xtl





From: Support@HamApps.groups.io <Support@HamApps.groups.io> on behalf of Michael Black via Groups.Io <mdblack98@...>
Sent: Sunday, January 12, 2020 8:28
To: Support@HamApps.groups.io <support@hamapps.groups.io>; Support@HamApps.groups.io <Support@HamApps.groups.io>
Subject: Re: [HamApps] Hello
 
I'm sure you were referring to the callsigns getting cleared when you transmit....that has been improved now and is absolutely wonderful.

de Mike W9MDB




On Sunday, January 12, 2020, 05:10:09 AM CST, Bry Carling AF4K <af4k@...> wrote:


Shrug - I am not sure Laurie...  I suppose I was talking about using JT Alert again and hopefully talking with some fellow hams, which hasn.'t worked well for me in ages. The Callsigns would always disappear before I could use it to contact them. Since the JT65 & JT9 days.

Since you didn;t supply a quote of what I was sying I can only imagine that is what I was looking forward to:
A working JT Alert. I tried fror years with only little success.

I will give it a try today and see how it goes!  I am fairly certain that is what I was talking about.

Sincerely,

73 - Brian "Bry" Carling, AF4K CRYSTALS Co.
Sanford, Florida


From: Support@HamApps.groups.io <Support@HamApps.groups.io> on behalf of HamApps Support (VK3AMA) <vk3ama.ham.apps@...>
Sent: Sunday, January 12, 2020 1:02
To: Support@HamApps.groups.io <Support@HamApps.groups.io>
Subject: Re: [HamApps] Hello
 
On 12/01/2020 9:01 am, Bry Carling AF4K wrote:
Perhaps you’re reading different release notes from me then, because I just downloaded the newest release and the ones I read said that you now have a timer that can extend the amount of time the callsigns appear in the boxes on JT Alert.

Perhaps my imagination is a lot more fertile than I thought it was today.

Best regards - Bry Carling, AF4K
Bob,

When you said "you were looking forward" I interpreted that meant to some future version, not the current release.

de Laurie VK3AMA


locked Re: Hello

Michael Black
 

I'm sure you were referring to the callsigns getting cleared when you transmit....that has been improved now and is absolutely wonderful.

de Mike W9MDB




On Sunday, January 12, 2020, 05:10:09 AM CST, Bry Carling AF4K <af4k@...> wrote:


Shrug - I am not sure Laurie...  I suppose I was talking about using JT Alert again and hopefully talking with some fellow hams, which hasn.'t worked well for me in ages. The Callsigns would always disappear before I could use it to contact them. Since the JT65 & JT9 days.

Since you didn;t supply a quote of what I was sying I can only imagine that is what I was looking forward to:
A working JT Alert. I tried fror years with only little success.

I will give it a try today and see how it goes!  I am fairly certain that is what I was talking about.

Sincerely,

73 - Brian "Bry" Carling, AF4K CRYSTALS Co.
Sanford, Florida


From: Support@HamApps.groups.io <Support@HamApps.groups.io> on behalf of HamApps Support (VK3AMA) <vk3ama.ham.apps@...>
Sent: Sunday, January 12, 2020 1:02
To: Support@HamApps.groups.io <Support@HamApps.groups.io>
Subject: Re: [HamApps] Hello
 
On 12/01/2020 9:01 am, Bry Carling AF4K wrote:
Perhaps you’re reading different release notes from me then, because I just downloaded the newest release and the ones I read said that you now have a timer that can extend the amount of time the callsigns appear in the boxes on JT Alert.

Perhaps my imagination is a lot more fertile than I thought it was today.

Best regards - Bry Carling, AF4K
Bob,

When you said "you were looking forward" I interpreted that meant to some future version, not the current release.

de Laurie VK3AMA