Date   

locked Re: DXKeeper to LoTW

Dave AA6YQ
 

+ AA6YQ comments below

I see the option to have DXKeeper upload each new qso to LoTW. I have that checked but it is not working. At the present time I do it from the ADIF file. It's not a big deal but it would be more convenient. What am I missing?

+ Are you able to upload QSOs to LoTW when you log them from DXKeeper?

73,

Dave, AA6YQ


locked Re: unable to communicate with the WSJT-x Process

John L. Broughton
 

I get those unable to communicate with wsjt-x periodically and I just kill and restart JTalert and that fixes the problem. I am running JTalert v. 2.16.13.

John, WB9VGJ
John L. Broughton
wb9vgj@...
2silverhondas@...
www.wb9vgj.us
On 10/26/2020 1:40 PM, John Wiener wrote:

Hi.  I know this has been addressed before but I didn't understand the solution. I am running JTAlert 2.16.14
here is the error message:
Unable to communicate with the wsjt-x.  UDP port 2237, IP address: 192.168.200.233
Values read from wsjt-x config file...
C:\Users\Dr.John\AppData\local\wsjt-x/ini
wsjt-x detected instance...
Process window tgitle: wsjt-x v2.2.2
Process command line: 'c:\wsjt\wsjtx\bin\wsjtx.exe
It worked yesterday   Hmmm. AFAIK, nothing has changed
Thanks!
John

 



Virus-free. www.avg.com


locked Re: unable to communicate with the WSJT-x Process

John Wiener
 

changed UDP address to 239.255.0.0   the ADIF secondary UDP address remains at 127.0.0.1  and now it works again!
Many Thanks, Laurie!!
73 de AB8O


locked Re: DXKeeper to LoTW

Michael Black
 

Yup...you're right Bill....
John...do you have the checkboxe turned on?
Mike W9MDB

Inline image





On Tuesday, October 27, 2020, 09:00:41 AM CDT, g4wjs <bill.8@...> wrote:


Mike,

if I understand the process correctly it is not wholly down to DXKeeper. JTAlert requests that DXKeeper do a single QSO upload to LoTW when it passes a QSO to DXKeeper. It is not controlled by DXKeeper settings other than that DXKeeper has to be set up correctly to communicate with TQSL to do the upload, it is JTAlert that indirectly initiates the upload.

73
Bill
G4WJS.

On 27/10/2020 13:43, Michael Black via groups.io wrote:
Best you ask the DXKeeper folks.....nothing to do with JTAlert as long as DXKeeper is logging it.

Mike W9MDB




On Tuesday, October 27, 2020, 08:41:41 AM CDT, John <na6y34@...> wrote:


I see the option to have DXKeeper upload each new qso to LoTW. I have that checked but it is not working. At the present time I do it from the ADIF file. It's not a big deal but it would be more convenient. What am I missing? 

73,

John  NA6Y



--
73
Bill
G4WJS.


locked Re: DXKeeper to LoTW

g4wjs
 

Mike,

if I understand the process correctly it is not wholly down to DXKeeper. JTAlert requests that DXKeeper do a single QSO upload to LoTW when it passes a QSO to DXKeeper. It is not controlled by DXKeeper settings other than that DXKeeper has to be set up correctly to communicate with TQSL to do the upload, it is JTAlert that indirectly initiates the upload.

73
Bill
G4WJS.

On 27/10/2020 13:43, Michael Black via groups.io wrote:
Best you ask the DXKeeper folks.....nothing to do with JTAlert as long as DXKeeper is logging it.

Mike W9MDB




On Tuesday, October 27, 2020, 08:41:41 AM CDT, John <na6y34@...> wrote:


I see the option to have DXKeeper upload each new qso to LoTW. I have that checked but it is not working. At the present time I do it from the ADIF file. It's not a big deal but it would be more convenient. What am I missing? 

73,

John  NA6Y



--
73
Bill
G4WJS.


locked Re: DXKeeper to LoTW

Ed
 


locked Re: DXKeeper to LoTW

Michael Black
 

Best you ask the DXKeeper folks.....nothing to do with JTAlert as long as DXKeeper is logging it.

Mike W9MDB




On Tuesday, October 27, 2020, 08:41:41 AM CDT, John <na6y34@...> wrote:


I see the option to have DXKeeper upload each new qso to LoTW. I have that checked but it is not working. At the present time I do it from the ADIF file. It's not a big deal but it would be more convenient. What am I missing? 

73,

John  NA6Y


locked DXKeeper to LoTW

 

I see the option to have DXKeeper upload each new qso to LoTW. I have that checked but it is not working. At the present time I do it from the ADIF file. It's not a big deal but it would be more convenient. What am I missing? 

73,

John  NA6Y


locked Re: Subscribe problem

Neil Foster
 

Hi Dan
TNX for the reply. That was a typo on my "olde" fingers. I meant to type JT Alert...sorry about that.
Neil


locked A giant step up !

Jim Cooper
 

Gotta do a bit of bragging tonight !!

For a year, I've had my FT8 setup software
running on one of the square black desktop PCs
like we have a the club.  A year ago it was doing
fairly well with the FT8 load; but both WSJT-X
and JTAlert have been constantly adding more
and more features and still expecting everything
to be processed in less then 2 or 3 seconds at the
end of each FT8 cycle. 

I was seeing a lot of receive cycles being DROPPED
and watching the waterfall I could actually see the
pauses, where the cpu choked and so nothing was
processed in that gulp.  So it was becoming more and
more frustrating, especially while in a QSO and the
receive cycle blanked so another Tx of the same info
and eventually a good receive cycle.

And fairly recently I upgraded the PC I've been using
for my webinar recording gigs to one with better video
processing and a really good cpu -- which left the
previous recording PC, which is not so bad on processing,
open for new applications ...  like maybe FT8!!

Long story, shortened a bit here ...  after a few frustrations
like no audio to the Tx ... and JTalert not talking/receiving
with WSJT-X, etc.  everything finally came together ...
and what a difference!!!    Have not seen a receive cycle
skipped all night, and everything is perky sweet.   ;))

Then I decided that since I have a monitor screen with
several different inputs, selectable by a menu, why not put
the big screen on FT8 along with the other two screens that
were already on the PC ...  so now I have THREE monitors
and lots of room for all the FT8 windows -- including the new experimental Callsign window in JTalert.

And here's what it looks like, except now I have
"Simon's Gray Line World Map" on the left half of the
upper screen, which is the 'hamapps' "my call spotted"
chart on the right.

graphic

And a really big, awesome load of thanks to the generous hams who spend much of their life supporting and enhancing these two software packages ...  WSJT-X and JTalert ---
especially to Laurie in Australia who must have no other life
but helping users with their JTalert problems, while he is
constantly adding and improving features.  THANKS Guys.

Jim  W2JC


  


locked Re: Subscribe problem

d_ziolkowski
 

Neil

wrong group. That said you can log in your gmail from any computer, you don't need another email. 

Dan KC2STA

On Mon, Oct 26, 2020 at 5:26 PM Neil Foster <archernf@...> wrote:

  Laurie,
I have a new second PC and I am trying to subscribe to WSJT reflector with a different email address. I am subscribed on my other PC with a different email and want to keep that as is. I have been unable to do so under this email  n4fn.g0nbj@.... What could I be doing wrong?
Thanks Neil  G0NBJ

 



--
Dan Ziolkowski KC2STA
SKCC #4290T
Ubuntu LINUX


locked Subscribe problem

Neil Foster
 


  Laurie,
I have a new second PC and I am trying to subscribe to WSJT reflector with a different email address. I am subscribed on my other PC with a different email and want to keep that as is. I have been unable to do so under this email  n4fn.g0nbj@.... What could I be doing wrong?
Thanks Neil  G0NBJ

 


locked Re: unable to communicate with the WSJT-x Process

HamApps Support (VK3AMA)
 

On 27/10/2020 7:40 am, John Wiener wrote:
here is the error message:
Unable to communicate with the wsjt-x.  UDP port 2237, IP address: 192.168.200.233
Values read from wsjt-x config file...
C:\Users\Dr.John\AppData\local\wsjt-x/ini
wsjt-x detected instance...
Process window tgitle: wsjt-x v2.2.2
Process command line: 'c:\wsjt\wsjtx\bin\wsjtx.exe
It worked yesterday   Hmmm. AFAIK, nothing has changed
Thanks!
John

Likely a PC Protection software update is blocking the comms. A PC restart may help, especially if your running Win10

Since JTAlert requires WSJT-X to be running on the same PC, try changing the UDP Server address to "127.0.0.1" or better still change to using a multicast address like "239.255.0.0"

de Laurie VK3AMA


locked unable to communicate with the WSJT-x Process

John Wiener
 

Hi.  I know this has been addressed before but I didn't understand the solution. I am running JTAlert 2.16.14
here is the error message:
Unable to communicate with the wsjt-x.  UDP port 2237, IP address: 192.168.200.233
Values read from wsjt-x config file...
C:\Users\Dr.John\AppData\local\wsjt-x/ini
wsjt-x detected instance...
Process window tgitle: wsjt-x v2.2.2
Process command line: 'c:\wsjt\wsjtx\bin\wsjtx.exe
It worked yesterday   Hmmm. AFAIK, nothing has changed
Thanks!
John

 


locked Re: JTAlert seems to be in a loop

docdga@...
 

Thank you very much that did the trick.


 Dawson Andrews 

KI5IMY

 


locked Re: Request for callsign to be changed #HamSpots

Antony
 

Congratulations Graham! 73, Antony G4CUS


locked Re: JTAlert seems to be in a loop

HamApps Support (VK3AMA)
 

On 26/10/2020 1:19 pm, docdga@... wrote:
I have   wsjt-x  gridtracker and JTalert running on my machine. JTalert lets me know that I have a wanted contact. I click on the contact in JTalert that initiates a transmit  in wsjt-x. Once the contact is confirmed and wsjt-x prompts me to log when I click OK JTalert starts telling me that it successfully logged the contact multiple times and seems to be in a loop I have to kill JTalert.. I have wsjt-x logging to Ham Radio Deluxe  JTalert is  logging to standard Adif file. Also there are nine or 10 incomplete  entries in Ham Radio Deluxe. There is one complete entry.

OM (Name? Callsign?)

WSJT-X doesn't log to HRD and if you have JTAlert logging to an ADIF file than the HRD logging must be coming from GridTracker.
You will likely find that your ADIF file also contains duplicate entries.

It sounds like you have JTAlert set to resend UDP packets to the same port that WSJT-X is sending to, which is the port JTAlert is listening to, so you have JTAlert resending UDP packets back to itself, thus the looping.

Turn off the "Resend WSJT-X UDP ..." setting in JTAlert will fix your issue.

   

If you use this Resend function for GridTracker than set it to a port DIFFERENT from the UDP Server port set in WSJT-X.

de Laurie VK3AMA


locked JTAlert seems to be in a loop

docdga@...
 

I have   wsjt-x  gridtracker and JTalert running on my machine. JTalert lets me know that I have a wanted contact. I click on the contact in JTalert that initiates a transmit  in wsjt-x. Once the contact is confirmed and wsjt-x prompts me to log when I click OK JTalert starts telling me that it successfully logged the contact multiple times and seems to be in a loop I have to kill JTalert.. I have wsjt-x logging to Ham Radio Deluxe  JTalert is  logging to standard Adif file. Also there are nine or 10 incomplete  entries in Ham Radio Deluxe. There is one complete entry.

 


locked Re: Request for callsign to be changed #HamSpots

Laurie, VK3AMA
 

Done.

de Laurie VK3AMA


On 26/10/2020 12:23 am, Graham Bevan via groups.io wrote:
Hi,
Could you please changed the callsign for my HamSpots account from M7MAK to 2E0YCX?

Kind Regards,
Graham


locked Request for callsign to be changed #HamSpots

Graham Bevan
 

Hi,
Could you please changed the callsign for my HamSpots account from M7MAK to 2E0YCX?

Kind Regards,
Graham