Date   

locked Re: UDP Not accessible for DXLAB logging and such

g4wjs
 

On 30/12/2019 03:24, Rick wrote:
So I changed UDP Server
port number to 2242 with all 3 boxes cleared and then tic'd again.
Secondary UDP Sever is 2333  both port number 127.0.0.1.

Hi Rick,

ok, so JTAlert will read the WSJT-X settings file directly and work out that it needs to listen on port 2242. While both are running you should type:

netstat -an -p udp | findstr 2242

into  command prompt window. You will get a list of servers listening on port 2242, something like this:

C:\>netstat -an -p udp | findstr 2242
  UDP    127.0.0.1:2242         *:*

Note that only one line is printed, if there is more than one then another application is listening on port 2242, i.e. not just JTAlert. That is not supported on a unicast address like 127.0.0.1 and JTAlert does not support multicast address groups so it cannot interoperate with other applications listening on the same port as it is.

Let me know if you see two lines, if so I will explain how to determine what the other application is.


--
73
Bill
G4WJS.


locked Re: UDP Not accessible for DXLAB logging and such

Rick
 

Yes, WSJT and JTAlert were both running.

Here is the error

Unable to communicate with the WSJT-X process.
  UDP Port : 2242
  IP Address : 127.0.0.1
  Values read from WSJT-X config file...
    C:\Users\Radio 7\AppData\Local\WSJT-X\WSJT-X.ini

WSJT-X Detected Instance...
  Process Window Title : WSJT-X   v2.1.2   by K1JT
  Process Command Line :

Decode alerts and logging will be unavailable until corrected.

On 12/29/2019 10:12 PM, g4wjs wrote:
On 30/12/2019 03:07, Rick wrote:
I had changed the code to 2242
Hi Rick,

why? Do you have the UDP server port set to 2242 in the WSJT-X or JTDX
"Settings->Reporting->UDP Server->UDP Server port number" field?

Just to double check, you did have JTAlert and WSJT-X or JTDX running
when you typed the command I gave into a command prompt window?

73
Bill
G4WJS.


--


Only losers need rally caps.


locked Re: UDP Not accessible for DXLAB logging and such

Rick
 

Hi back......don't you sleep?

I was told by Laurie to try other port numbers. So I changed UDP Server
port number to 2242 with all 3 boxes cleared and then tic'd again.
Secondary UDP Sever is 2333  both port number 127.0.0.1. Please remember
I'm a hardware guy.  I can build/repair them but not so good at
programming them.  I'm using WSJT-X btw.  In JTAlert 2.15.3   In JTAlert
I have last qso api/udp transmission of last qso port set to 2242.  Is
that correct?  I guess this info is available somewhere but With my
Parkinson's it's difficult to read/turn pages etc...if you tell me where
to look I can find it on the computer.  Then it's easier to read.


On 12/29/2019 10:12 PM, g4wjs wrote:
On 30/12/2019 03:07, Rick wrote:
I had changed the code to 2242
Hi Rick,

why? Do you have the UDP server port set to 2242 in the WSJT-X or JTDX
"Settings->Reporting->UDP Server->UDP Server port number" field?

Just to double check, you did have JTAlert and WSJT-X or JTDX running
when you typed the command I gave into a command prompt window?

73
Bill
G4WJS.


--


Only losers need rally caps.


locked Re: UDP Not accessible for DXLAB logging and such

g4wjs
 

On 30/12/2019 03:07, Rick wrote:
I had changed the code to 2242
Hi Rick,

why? Do you have the UDP server port set to 2242 in the WSJT-X or JTDX "Settings->Reporting->UDP Server->UDP Server port number" field?

Just to double check, you did have JTAlert and WSJT-X or JTDX running when you typed the command I gave into a command prompt window?

73
Bill
G4WJS.



--
73
Bill
G4WJS.


locked Re: UDP Not accessible for DXLAB logging and such

Rick
 

Bill,

I had changed the code to 2242 (no help)  so I typed that into your string. Don't know what was supposed to happen but nothing did.

Any help you can give me will be greatly received.

73, Rick W3BI


On 12/29/2019 5:04 PM, g4wjs wrote:
netstat -an -p udp | findstr 2237
--


Only losers need rally caps.


locked JT alert and QRZ Logbook

Ken Desjardins
 

Hi, I have been using JTAlert with ACLOG and QRZ Logbook for years with no problem. Lately, JT Alert stopped uploading logs to my QRZ Book but it does still continue to log to ACLOG. My API key is in there correctly with no spaces and QRZ logging is enabled. As far as I can tell, My antivirus isn't blocking anything. I would like some help with this matter if you could. Thanks

Ken.


locked Re: UDP Not accessible for DXLAB logging and such

Rick
 

Laurie,

I really don't expect you to but don't have anyone that fits that bill.  I guess I'm relegated to Fldigi, which is also a great program.

Thanks anyway ......

73, Rick W3BI


On 12/29/2019 4:58 PM, HamApps Support (VK3AMA) wrote:
On 28/12/2019 2:27 pm, Rick wrote:

You are working on the problem?!

73, Rick W3BI

Sorry Rick, It is difficult(impossible) to work on a problem without experiencing the problem and all our previous tests/changes requested via email have not identified or rectified the cause.

Your support files show that JTAlert is hearing WSJT-X fine as indicated by the titlebar status. The mode symbol and band shown in the status only get populate when data is received from WSJT-X, after that all UDP traffic is lost.

At this point you need to have someone (who is WSJT-X and JTAlert knowledgeable) gain remote access into you PC and observe what is happening in real-time and examine your application settings.

Hopefully someone on this group can help you out.  I am not in a position to offer that type of remote-access support , sorry.

de Laurie VK3AMA

--


Only losers need rally caps.


locked Re: UDP Not accessible for DXLAB logging and such

g4wjs
 

On 29/12/2019 21:58, HamApps Support (VK3AMA) wrote:
On 28/12/2019 2:27 pm, Rick wrote:

You are working on the problem?!

73, Rick W3BI

Sorry Rick, It is difficult(impossible) to work on a problem without experiencing the problem and all our previous tests/changes requested via email have not identified or rectified the cause.

Your support files show that JTAlert is hearing WSJT-X fine as indicated by the titlebar status. The mode symbol and band shown in the status only get populate when data is received from WSJT-X, after that all UDP traffic is lost.

At this point you need to have someone (who is WSJT-X and JTAlert knowledgeable) gain remote access into you PC and observe what is happening in real-time and examine your application settings.

Hopefully someone on this group can help you out.  I am not in a position to offer that type of remote-access support , sorry.

de Laurie VK3AMA

Rick,

when the issue is happening please type this into a command prompt window and report back what is printed please?

netstat -an -p udp | findstr 2237

73
Bill
G4WJS.


--
73
Bill
G4WJS.


locked Re: UDP Not accessible for DXLAB logging and such

HamApps Support (VK3AMA)
 

On 28/12/2019 2:27 pm, Rick wrote:

You are working on the problem?!

73, Rick W3BI

Sorry Rick, It is difficult(impossible) to work on a problem without experiencing the problem and all our previous tests/changes requested via email have not identified or rectified the cause.

Your support files show that JTAlert is hearing WSJT-X fine as indicated by the titlebar status. The mode symbol and band shown in the status only get populate when data is received from WSJT-X, after that all UDP traffic is lost.

At this point you need to have someone (who is WSJT-X and JTAlert knowledgeable) gain remote access into you PC and observe what is happening in real-time and examine your application settings.

Hopefully someone on this group can help you out.  I am not in a position to offer that type of remote-access support , sorry.

de Laurie VK3AMA


locked Re: UDP Not accessible for DXLAB logging and such

HamApps Support (VK3AMA)
 

On 29/12/2019 4:38 pm, n6dl wrote:
Laurie,
Please to review the email thread..
The email thread from me to you:
9/27/2019 8:51 PM
9/29/2019 5:38 PM
9/30/2019 7:27 PM
10/2/2019 7:37 PM
10/5/2019 8:51 Pm
10/12/2019 5:45 PM
10/29/2019 5:40 PM
The email thread from you to me:
9/27/2019 7:29 PM
9/28/2019 3:10 PM
9/30/2019 4:16 PM
10/1/2019 9:42 PM
10/5/2019 6:21 PM
12/2/2019 8:26 PM

73 Dave N6DL
OK Dave,

I was searching the forum for previous posts from you rather than my JTAlert support requests archive.

Your problem is that JTAlert stops receiving UDP traffic from WSJT-X rather than the more common never receives UDP traffic.

Your support files show that
JTAlert is hearing WSJT-X fine as indicated by the titlebar status. The mode symbol and band shown in the status only get populate when data is received from WSJT-X
JTAlert 2.15.2 N6DL [~,40m,HRD6+,#1]

After that initial UDP reception, nothing further is received (at what point that breaks I cannot determine). My guess is that some application on your PC is taking exclusive control of the 2237 UDP server port. What happens if your start WSJT-X and JTAlert without HRDLogbook running, does that resolve the problem?

de Laurie VK3AMA



locked Re: UDP Not accessible for DXLAB logging and such

n6dl
 

Laurie,
Please to review the email thread..
The email thread from me to you:
9/27/2019 8:51 PM
9/29/2019 5:38 PM
9/30/2019 7:27 PM
10/2/2019 7:37 PM
10/5/2019 8:51 Pm
10/12/2019 5:45 PM
10/29/2019 5:40 PM
The email thread from you to me:
9/27/2019 7:29 PM
9/28/2019 3:10 PM
9/30/2019 4:16 PM
10/1/2019 9:42 PM
10/5/2019 6:21 PM
12/2/2019 8:26 PM

73 Dave N6DL


locked Re: UDP Not accessible for DXLAB logging and such

Rick Johnson
 

Not running either program as admin.
Been using DXKeeper forever. And you're right....best one for sure.

73, Rick W3BI


On Sat, Dec 28, 2019 at 9:53 AM Gilbert Baron <w0mn00@...> wrote:
  1. DO NOT run as administrator. Not needed and can cause all sorts of trouble.
  2. Best configuration documentation is in the help files and if you follow them to the letter it will work with W10.
  3. If you wat to use DXLABS (Best logging and spot collecting there is) then follow this to set up.

 

https://www.dxlabsuite.com/dxlabwiki/GettingStartedwithK1JTModesDirect

 

Outlook Laptop Gil W0MN

Hierro candente, batir de repente

44.08226N 92.51265W EN34rb

 

From: Support@HamApps.groups.io <Support@HamApps.groups.io> On Behalf Of Rick
Sent: Saturday, December 28, 2019 08:26
To: Support@HamApps.groups.io
Subject: Re: [HamApps] UDP Not accessible for DXLAB logging and such

 

Neil,

I don't know if this was meant for me or the other person, as it was sent "To..HamApps.groups.io."  So I'll answer.

I have sent many "Contact Support" communications to Laurie.  I feel bad about taking up so much of his time, but he is the expert. Many communiques between Australia and U.S.  Laurie's fantastic program just sits on the screen like a jpg.

Congratulations on using JTAlert on Windows 10 without an issue. Doesn't help me a bit.

I have been using the combination successfully for over 28,000 JT/FT QSO's without issue. Then this.

My version of Win10 does not present me with a "detail" dropdown so I can select info on if I'm running any of them under the "Run as administrator" function of Windows. Any help there?

Thank you for your assistance.

73, Rick W3BI

=============================================

On 12/28/2019 8:13 AM, neil_zampella wrote:

[Edited Message Follows]

I think Laurie means that he didn't see anything from this person about this issue previously. 

Have you used the "Contact Support" link under the JT-Alert HELP menu to send the JT-Alert information to Laurie so he can see what's happening?

That said, I've been using JT-Alert on Windows 10 without an issue with the latest updates to Win10.   How did you install JT-Alert and WSJT-X?   Are you running any of them under the 'Run as administrator" function of Windows?

Neil, KN3ILZ

--
 
 
Only losers need rally caps.


--

W0MN EN34rb 44.08226 N 92.51265 W

Hierro candente, batir de repente


locked Re: UDP Not accessible for DXLAB logging and such

Rick Johnson
 

Head bowed.....nope.  But now I will.  ;c  )

73, Rick W3BI


On Sat, Dec 28, 2019 at 10:26 AM g4wjs <bill.8@...> wrote:
Rick,

did you start them up before you check for them in Task Manager?

On 28/12/2019 15:23, Rick Johnson wrote:
As you can see, neither JTAlert.exe or wsjt.exe are there.
I missed one word in the Google instructions...."Column Heading"   aw   RTFQ. or RTFA  whatever.
Thanks.....now what.
73, Rick W3BI


On Sat, Dec 28, 2019 at 9:44 AM g4wjs <bill.8@...> wrote:
On 28/12/2019 14:25, Rick wrote:
> My version of Win10 does not present me with a "detail" dropdown so I
> can select info on if I'm running any of them under the "Run as
> administrator" function of Windows. Any help there?

Rick,

use Windows Task Manager to determine definitively if an application is
running with elevate rights. Start Task Manager, select the "Details"
tab, right-click any column heading, press the "Select columns" button
on the pop up menu, check the "Elevated" option on the list of possible
columns that is shown; then click "Ok". That will add a column headed
"Elevated" to the process list with possible values of "Yes" or "No".
The WSJT-X process that sends UDP messages is running wsjtx.exe, the
JTAlert process that listens for WSJT-X UDP traffic is running
JTAlert.exe. Neither should be showing "Yes" in the "Elevated" column.



--
73
Bill
G4WJS.



--
73
Bill
G4WJS.


locked JTAlert wont run

Rick
 

Bill,

I just noticed that when I start WSJT-x and JTAlert  the callsign in
"Generate Standard Messages" is picked up by JTAlert.  That's the only
movement on JTAlert.

73, Rick W3BI


--


Only losers need rally caps.


locked Re: UDP Not accessible for DXLAB logging and such

g4wjs
 

Rick,

did you start them up before you check for them in Task Manager?

On 28/12/2019 15:23, Rick Johnson wrote:
As you can see, neither JTAlert.exe or wsjt.exe are there.
I missed one word in the Google instructions...."Column Heading"   aw   RTFQ. or RTFA  whatever.
Thanks.....now what.
73, Rick W3BI


On Sat, Dec 28, 2019 at 9:44 AM g4wjs <bill.8@...> wrote:
On 28/12/2019 14:25, Rick wrote:
> My version of Win10 does not present me with a "detail" dropdown so I
> can select info on if I'm running any of them under the "Run as
> administrator" function of Windows. Any help there?

Rick,

use Windows Task Manager to determine definitively if an application is
running with elevate rights. Start Task Manager, select the "Details"
tab, right-click any column heading, press the "Select columns" button
on the pop up menu, check the "Elevated" option on the list of possible
columns that is shown; then click "Ok". That will add a column headed
"Elevated" to the process list with possible values of "Yes" or "No".
The WSJT-X process that sends UDP messages is running wsjtx.exe, the
JTAlert process that listens for WSJT-X UDP traffic is running
JTAlert.exe. Neither should be showing "Yes" in the "Elevated" column.



--
73
Bill
G4WJS.



--
73
Bill
G4WJS.


locked Re: UDP Not accessible for DXLAB logging and such

Rick Johnson
 

image.png
image.png

As you can see, neither JTAlert.exe or wsjt.exe are there.
I missed one word in the Google instructions...."Column Heading"   aw   RTFQ. or RTFA  whatever.
Thanks.....now what.
73, Rick W3BI


On Sat, Dec 28, 2019 at 9:44 AM g4wjs <bill.8@...> wrote:
On 28/12/2019 14:25, Rick wrote:
> My version of Win10 does not present me with a "detail" dropdown so I
> can select info on if I'm running any of them under the "Run as
> administrator" function of Windows. Any help there?

Rick,

use Windows Task Manager to determine definitively if an application is
running with elevate rights. Start Task Manager, select the "Details"
tab, right-click any column heading, press the "Select columns" button
on the pop up menu, check the "Elevated" option on the list of possible
columns that is shown; then click "Ok". That will add a column headed
"Elevated" to the process list with possible values of "Yes" or "No".
The WSJT-X process that sends UDP messages is running wsjtx.exe, the
JTAlert process that listens for WSJT-X UDP traffic is running
JTAlert.exe. Neither should be showing "Yes" in the "Elevated" column.



--
73
Bill
G4WJS.




locked Re: UDP Not accessible for DXLAB logging and such

Gilbert Baron <w0mn00@...>
 

  1. DO NOT run as administrator. Not needed and can cause all sorts of trouble.
  2. Best configuration documentation is in the help files and if you follow them to the letter it will work with W10.
  3. If you wat to use DXLABS (Best logging and spot collecting there is) then follow this to set up.

 

https://www.dxlabsuite.com/dxlabwiki/GettingStartedwithK1JTModesDirect

 

Outlook Laptop Gil W0MN

Hierro candente, batir de repente

44.08226N 92.51265W EN34rb

 

From: Support@HamApps.groups.io <Support@HamApps.groups.io> On Behalf Of Rick
Sent: Saturday, December 28, 2019 08:26
To: Support@HamApps.groups.io
Subject: Re: [HamApps] UDP Not accessible for DXLAB logging and such

 

Neil,

I don't know if this was meant for me or the other person, as it was sent "To..HamApps.groups.io."  So I'll answer.

I have sent many "Contact Support" communications to Laurie.  I feel bad about taking up so much of his time, but he is the expert. Many communiques between Australia and U.S.  Laurie's fantastic program just sits on the screen like a jpg.

Congratulations on using JTAlert on Windows 10 without an issue. Doesn't help me a bit.

I have been using the combination successfully for over 28,000 JT/FT QSO's without issue. Then this.

My version of Win10 does not present me with a "detail" dropdown so I can select info on if I'm running any of them under the "Run as administrator" function of Windows. Any help there?

Thank you for your assistance.

73, Rick W3BI

=============================================

On 12/28/2019 8:13 AM, neil_zampella wrote:

[Edited Message Follows]

I think Laurie means that he didn't see anything from this person about this issue previously. 

Have you used the "Contact Support" link under the JT-Alert HELP menu to send the JT-Alert information to Laurie so he can see what's happening?

That said, I've been using JT-Alert on Windows 10 without an issue with the latest updates to Win10.   How did you install JT-Alert and WSJT-X?   Are you running any of them under the 'Run as administrator" function of Windows?

Neil, KN3ILZ

--
 
 
Only losers need rally caps.


--

W0MN EN34rb 44.08226 N 92.51265 W

Hierro candente, batir de repente


locked Re: UDP Not accessible for DXLAB logging and such

g4wjs
 

On 28/12/2019 14:25, Rick wrote:
My version of Win10 does not present me with a "detail" dropdown so I can select info on if I'm running any of them under the "Run as administrator" function of Windows. Any help there?
Rick,

use Windows Task Manager to determine definitively if an application is running with elevate rights. Start Task Manager, select the "Details" tab, right-click any column heading, press the "Select columns" button on the pop up menu, check the "Elevated" option on the list of possible columns that is shown; then click "Ok". That will add a column headed "Elevated" to the process list with possible values of "Yes" or "No". The WSJT-X process that sends UDP messages is running wsjtx.exe, the JTAlert process that listens for WSJT-X UDP traffic is running JTAlert.exe. Neither should be showing "Yes" in the "Elevated" column.



--
73
Bill
G4WJS.


locked Re: UDP Not accessible for DXLAB logging and such

Rick
 

Neil,

I don't know if this was meant for me or the other person, as it was sent "To..HamApps.groups.io."  So I'll answer.

I have sent many "Contact Support" communications to Laurie.  I feel bad about taking up so much of his time, but he is the expert. Many communiques between Australia and U.S.  Laurie's fantastic program just sits on the screen like a jpg.

Congratulations on using JTAlert on Windows 10 without an issue. Doesn't help me a bit.

I have been using the combination successfully for over 28,000 JT/FT QSO's without issue. Then this.

My version of Win10 does not present me with a "detail" dropdown so I can select info on if I'm running any of them under the "Run as administrator" function of Windows. Any help there?

Thank you for your assistance.

73, Rick W3BI

=============================================

On 12/28/2019 8:13 AM, neil_zampella wrote:

[Edited Message Follows]

I think Laurie means that he didn't see anything from this person about this issue previously. 

Have you used the "Contact Support" link under the JT-Alert HELP menu to send the JT-Alert information to Laurie so he can see what's happening?

That said, I've been using JT-Alert on Windows 10 without an issue with the latest updates to Win10.   How did you install JT-Alert and WSJT-X?   Are you running any of them under the 'Run as administrator" function of Windows?

Neil, KN3ILZ

--


Only losers need rally caps.


locked Re: UDP Not accessible for DXLAB logging and such

neil_zampella
 
Edited

I think Laurie means that he didn't see anything from this person about this issue previously. 

Have you used the "Contact Support" link under the JT-Alert HELP menu to send the JT-Alert information to Laurie so he can see what's happening?

That said, I've been using JT-Alert on Windows 10 without an issue with the latest updates to Win10.   How did you install JT-Alert and WSJT-X?   Are you running any of them under the 'Run as administrator" function of Windows?

Neil, KN3ILZ