Date   

locked Re: JTA 250.1 Error Downloading

David Marcelli
 

Thanks Jim.  I am getting around to making the changes.  what stuns me is that all has been working like a swiss watch before I made the upgrades.  I'll try your solutions.

My internet connection is fuzzy at times, not so good in the high mountains of east Tennessee.  it is generally a solid connection.  73

Dave
N4CQ




-----Original Message-----
From: Jim N6VH <N6VH@...>
To: Support@HamApps.groups.io
Sent: Fri, May 28, 2021 3:46 pm
Subject: Re: [HamApps] JTA 250.1 Error Downloading


On 5/28/2021 10:23 AM, David Marcelli via groups.io wrote:

I get the error messages in JTA on the attached JPEG (sorry for hard to read file).  I have tried multiple times to download with no success. I have seen similar, but not identical problems in the message center.

I also get  the following error message from WSJT, not sure if it related to the JTA issue. (I am working on it)

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

WSJT-X Detected Instance...
  Process Window Title : WSJT-X   v2.2.1   by K1JT, G4WJS, and K9AN
  Process Command Line : "C:\WSJT\wsjtx\bin\wsjtx.exe" 

Decode alerts and logging will be unavailable until corrected.

This system has worked successfully for along time until this attempt to upgrade the software.  I would appreciate any fix.

Dave
N4CQ

Dave,
Yes, the image is hard to read. I downloaded it and enlarged it, which helped.
What version of JTAlert were you using before you up graded to 2.50.1?
The errors shown in the JTAlert Updates screen look like there is a problem with your internet connection. When you click on Check for Updates, that goes to a website and checks to see what the most recent files are. If your internet is working OK, and it must be since you were able to send the e-mail, there might be an issue with your network protection software (firewall). You might check to see if it is blocking JTAlert from accessing the internet. Just a thought. Incidentally, the only JTAlert software that is out of date on your system is the Callsign Database. The latest version is v2021.05.22.
I also see you are using WSJT-X 2.2.1. That is almost a year old. It would be a very good idea to upgrade to the latest version, which is 2.4.0.
Regarding the "Unable to communicate with WSJT-X" message - are you running any other programs that also interact with WSJT-X, such as Grid Tracker? If so, you need to use a multicast address in WSJT-X, such as 239.255.0.0, in the UDP Port: section.
Another possibility is, once again, your network protection software. It is possible that it started blocking the access between the two programs. This happens with some software, at times.
At any rate, check the issues I mentioned, by all means, upgrade to the latest WSJT-X version, and see if that helps.
73,
Jim N6VH


locked Re: Wanted call

Michael Black
 

Inline image

Mike W9MDB




On Friday, May 28, 2021, 02:51:55 PM CDT, Dave Tucker Nu4N <dwtucker19@...> wrote:


I am new to the latest version. Where to I put in a wanted callsign ?
Thanks
--
73 NU4N Dave


locked Wanted call

 

I am new to the latest version. Where to I put in a wanted callsign ?
Thanks
--
73 NU4N Dave


locked Re: JTA 250.1 Error Downloading

Jim N6VH
 


On 5/28/2021 10:23 AM, David Marcelli via groups.io wrote:

I get the error messages in JTA on the attached JPEG (sorry for hard to read file).  I have tried multiple times to download with no success. I have seen similar, but not identical problems in the message center.

I also get  the following error message from WSJT, not sure if it related to the JTA issue. (I am working on it)

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

WSJT-X Detected Instance...
  Process Window Title : WSJT-X   v2.2.1   by K1JT, G4WJS, and K9AN
  Process Command Line : "C:\WSJT\wsjtx\bin\wsjtx.exe" 

Decode alerts and logging will be unavailable until corrected.

This system has worked successfully for along time until this attempt to upgrade the software.  I would appreciate any fix.

Dave
N4CQ

Dave,

Yes, the image is hard to read. I downloaded it and enlarged it, which helped.

What version of JTAlert were you using before you up graded to 2.50.1?

The errors shown in the JTAlert Updates screen look like there is a problem with your internet connection. When you click on Check for Updates, that goes to a website and checks to see what the most recent files are. If your internet is working OK, and it must be since you were able to send the e-mail, there might be an issue with your network protection software (firewall). You might check to see if it is blocking JTAlert from accessing the internet. Just a thought. Incidentally, the only JTAlert software that is out of date on your system is the Callsign Database. The latest version is v2021.05.22.

I also see you are using WSJT-X 2.2.1. That is almost a year old. It would be a very good idea to upgrade to the latest version, which is 2.4.0.

Regarding the "Unable to communicate with WSJT-X" message - are you running any other programs that also interact with WSJT-X, such as Grid Tracker? If so, you need to use a multicast address in WSJT-X, such as 239.255.0.0, in the UDP Port: section.

Another possibility is, once again, your network protection software. It is possible that it started blocking the access between the two programs. This happens with some software, at times.

At any rate, check the issues I mentioned, by all means, upgrade to the latest WSJT-X version, and see if that helps.

73,

Jim N6VH


locked JTA 250.1 Error Downloading

David Marcelli
 


I get the error messages in JTA on the attached JPEG (sorry for hard to read file).  I have tried multiple times to download with no success. I have seen similar, but not identical problems in the message center.

I also get  the following error message from WSJT, not sure if it related to the JTA issue. (I am working on it)

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

WSJT-X Detected Instance...
  Process Window Title : WSJT-X   v2.2.1   by K1JT, G4WJS, and K9AN
  Process Command Line : "C:\WSJT\wsjtx\bin\wsjtx.exe" 

Decode alerts and logging will be unavailable until corrected.

This system has worked successfully for along time until this attempt to upgrade the software.  I would appreciate any fix.

Dave
N4CQ


locked Re: Single/double click within callsigns window not working

BOB K5HX
 

I shut down all other running applications other than WSJT-X and HRD and still have the same result.
Also,  the netstat -ano command produced the following which contains the correct port number.   UDP  0.0.0.0:2237 and a process number which corresponded to JTAlertV2.Manager.exe

Bob  K5HX


locked Re: Suggestion for the TXT messages

John C
 

Laurie, I am already using 2.50.1 but I cant find this setting...     would you mind pointing this dumb one where to look please...

 

John


locked Re: Suggestion for the TXT messages

Laurie, VK3AMA
 

Also, The Messaging window has an option to not follow the DXCall changes.
If you want to leave that activated, then simply having any text in the message compose area will stop any DXCall changes being actioned.

de Laurie VK3AMA


locked Re: Suggestion for the TXT messages

Laurie, VK3AMA
 

On 28/05/2021 2:32 pm, John C wrote:

Several times now, the TXT messager has sent a message I have been typing to the wrong person...   Can we please get this fixed.......  what happens is this.........

While I am working people, I start to type a message to a previous contact.   Part way through typing I work another call and the messages facility changes the "to" callsign to that of the latest station I am working and I end up sending the message to the wrong person.

Is there a way that you ciould please "lock" the callsign in that I am typing to so as to prevent this happening ???

regards

John
That's already available. Upgrade your JTAlert version.

From the 2.50.1 release notes...
  Changed:

    - Messaging window: WSJT-X DX Call changes now no longer auto populate the
       Callsign field if a message is already being composed. That is if the
       message field contains text, the DX Call change is ignored.
de Laurie VK3AMA


locked Re: Suggestion for the TXT messages

Michael Black
 

Would seem reasonable while that window is the active window that it wouldn't change.

Mike W9MDB




On Thursday, May 27, 2021, 11:32:11 PM CDT, John C <vk7xx.radio@...> wrote:


Several times now, the TXT messager has sent a message I have been typing to the wrong person...   Can we please get this fixed.......  what happens is this.........

While I am working people, I start to type a message to a previous contact.   Part way through typing I work another call and the messages facility changes the "to" callsign to that of the latest station I am working and I end up sending the message to the wrong person.

Is there a way that you ciould please "lock" the callsign in that I am typing to so as to prevent this happening ???

 

regards

John


locked Suggestion for the TXT messages

John C
 

Several times now, the TXT messager has sent a message I have been typing to the wrong person...   Can we please get this fixed.......  what happens is this.........

While I am working people, I start to type a message to a previous contact.   Part way through typing I work another call and the messages facility changes the "to" callsign to that of the latest station I am working and I end up sending the message to the wrong person.

Is there a way that you ciould please "lock" the callsign in that I am typing to so as to prevent this happening ???

 

regards

John


locked Re: Single/double click within callsigns window not working

Michael Black
 

The easy way to find out is to shut down everything except WSJT-X and JTAlert.
Then test clicking....if it works then some other app is intercepting the response.

Mike W9MDB




On Thursday, May 27, 2021, 07:15:42 PM CDT, BOB K5HX via groups.io <k5hx@...> wrote:


As far as I can tell HRD is not configured for multicast UDP on the same port. 

Bob K5HX


locked Re: Single/double click within callsigns window not working

BOB K5HX
 

As far as I can tell HRD is not configured for multicast UDP on the same port. 

Bob K5HX


locked Re: Single/double click within callsigns window not working

Dave Garber
 

yes, multicast is supported.... in GT

Dave Garber
VE3WEJ / VE3IE


On Thu, May 27, 2021 at 6:57 PM Michael Black via groups.io <mdblack98=yahoo.com@groups.io> wrote:
Are you sure Grid Tracker does multicast?  

Do you have HRD listening to the WSJT-X port too maybe?

Mike W9MDB




On Thursday, May 27, 2021, 05:47:18 PM CDT, BOB K5HX via groups.io <k5hx=yahoo.com@groups.io> wrote:


Mike,

Other than WSJT-X (interfaced to HRD),  I only sometimes launch Grid Tracker which is using UDP Multicast.

Bob  K5HX


locked Re: Single/double click within callsigns window not working

Michael Black
 

Are you sure Grid Tracker does multicast?  

Do you have HRD listening to the WSJT-X port too maybe?

Mike W9MDB




On Thursday, May 27, 2021, 05:47:18 PM CDT, BOB K5HX via groups.io <k5hx@...> wrote:


Mike,

Other than WSJT-X (interfaced to HRD),  I only sometimes launch Grid Tracker which is using UDP Multicast.

Bob  K5HX


locked Re: Single/double click within callsigns window not working

BOB K5HX
 

Mike,

Other than WSJT-X (interfaced to HRD),  I only sometimes launch Grid Tracker which is using UDP Multicast.

Bob  K5HX


locked Auto Close intermittent

Ed Fuller
 

This may just be a quirk of my system: Win7 home Premium, DXLab, WSJTX 2.4.0, JTAlert 2.50.1, Net 5.0.6.  Have Auto-start set to wsjtx. works fine, except when I close jtalert it closes  the wide graph, but sometimes the main wsjtx window remains open and decoding. 

 

First noticed this after upgrading to wsjtx 2.4.0, but rolling back to 2.3.0 makes no difference.  Using "taskkill /im wsjtx.exe" in command prompt shows similar results:

 

C:\Users\PSDR>taskkill /im wsjtx.exe

SUCCESS: Sent termination signal to the process "wsjtx.exe" with PID 5532.

 

After this is returned the process wsjtx.exe still shows in task manager processes even after a refresh and wsjtx still shows in the application pane.

 

taskkill with /t /f /im wsjtx.exe always works.

 

Not a big deal, just curious.

 

Ed Fuller WA5RHG


locked Re: #FT8 Clear decode screen #FT8

 

Yes Laurie the the call sign window was not checked. That did the job. Thanks
--
73 NU4N Dave


locked Re: #FT8 Clear decode screen #FT8

HamApps Support (VK3AMA)
 

On 28/05/2021 6:36 am, Dave Tucker Nu4N wrote:
I am new to the latest version.
Is there a shortcut to deleting the decode screen the same time u clear the decode screen in WSKT-X?

Thanks
--
73 NU4N Dave

For the Decodes window, no there is not.

The Decodes window is not new, so I suspect you're referring to another window, perhaps the Callsigns window. What does the titlebar show for the window in question?

de Laurie VK3AMA


locked #FT8 Clear decode screen #FT8

 

I am new to the latest version.
Is there a shortcut to deleting the decode screen the same time u clear the decode screen in WSKT-X?

Thanks
--
73 NU4N Dave

1981 - 2000 of 36987