Date   

locked Re: UDP Not accessible for DXLAB logging and such

HamApps Support (VK3AMA)
 

On 27/12/2019 6:22 am, Gilbert Baron wrote:
I cannot get UDP working on JTALERT. I have all 3 boxes checked but something is forbidding it to operate. I cannot find anything in help to describe exactly what to do. I assume the firewall needs some permission, but some documentation is needed here. It used to work fine before UDP is now used and I understand that UDP is a better way but I am not able to get it set up. Again, I do have the three boxes checked.

How long ago were you using JTAlert. UDP is the only way JTAlert interacts with WSJT-X and that has been the case for over 2 years (probably more).

Did you setup WSJT-X per the JTAlert help file instructions, "Tutorials -> WSJT-X UDP Setup" topic?

What IP address and port do you have set in WSJT-X?

Make sure your not running WSJT-X with elevated privileges (set to run as administrator), there is never any legitimate reason to run WSJT-X elevated.

What is the actual error message? JTAlert when showing an error window will often place a copy of the error message into the Windows clipboard, try pasting that into your reply.

de Laurie VK3AMA


locked Re: Autostart jtalert/wsjt-x problem

Dave Garber
 

Why not use jtalert setup to start wsjtx and your log software.    

sent by my LG phone

On Thu, Dec 26, 2019, 7:20 AM g4wjs, <bill.8@...> wrote:
On 26/12/2019 10:19, marsip@... wrote:
I'm using DXlab launcher (ver 2.1.2) which can start applications, after DXlab has started.
I have entered JTAlert as an option for this.
JTAlert starts, but I get a popup, where I have to select to start WSJT-X or JTDX.

The desktop icon for JTAlert, has a start path "C:\Program Files (x86)\HamApps\JTAlert\JTAlert.exe" /wsjtx".
But if I add "wsjtx" as an start program option in DXlab launcher, it doesn't work (or at least I can't get to work).

Is it possible to start WSJT-X in this way, without getting the popup select window from JTAlert?

OM,

try writing a one line batch file:

"C:\Program Files (x86)\HamApps\JTAlert\JTAlert.exe" /wsjtx

then invoke that from DX Lab Suite Launcher.

73
Bill
G4WJS.


--
73
Bill
G4WJS.


locked Re: UDP Not accessible for DXLAB logging and such

Dave Garber
 

Make sure jtalert wsjtx are not running in administrator modes

sent by my LG phone

On Thu, Dec 26, 2019, 2:22 PM Gilbert Baron, <w0mn00@...> wrote:

I cannot get UDP working on JTALERT. I have all 3 boxes checked but something is forbidding it to operate. I cannot find anything in help to describe exactly what to do. I assume the firewall needs some permission, but some documentation is needed here. It used to work fine before UDP is now used and I understand that UDP is a better way but I am not able to get it set up. Again, I do have the three boxes checked.

 

 

I am not asking for a full step by step here if you can point me to the correct documentation, that would be enough.

I am using W10.

 

I tried to find an answer in the online help but search did not provide an answer. Is there a PDF version that allows for full text search?

 

 

 

 

Outlook Desktop Gil W0MN

Hierro Candente Batir de Repente

44.08226 N 92.51265 W EN34rb

 


--

W0MN EN34rb 44.08226 N 92.51265 W

Hierro candente, batir de repente


locked Re: UDP port problems

Gilbert Baron <w0mn00@...>
 

I found the Alt F4 or Close option. I was just assuming the normal close without looking. Sorry for all the noise.

 

Outlook Desktop Gil W0MN

Hierro Candente Batir de Repente

44.08226 N 92.51265 W EN34rb

 

From: Support@HamApps.groups.io <Support@HamApps.groups.io> On Behalf Of Gilbert Baron via Groups.Io
Sent: Thursday, December 26, 2019 13:47
To: Support@HamApps.groups.io
Subject: Re: [HamApps] UDP port problems

 

I was not able to get JTALERT to work over the UDP. I got the message about checking the three boxes and then tried it. I got a permission error. After checking the three UDP boxes in settings AND terminating both programs and restarting it seems to be working. I need to play with it and learn it for a bit to see but I think it was my fault.

 

I have been using FT8 and just using the log file to import to DXKEEPER but want it to set it up with DXLABS now so it will be a bit of learning. There is a pretty big learning curve with these programs , especially if you add in spot collector. 😝-)

 

I do have one other problem. I have trouble closing JTALERT. Click the X just brings up the callsigns per band screen. I do not see a terminate button , no red square etc. like other windows programs.

 

Outlook Desktop Gil W0MN

Hierro Candente Batir de Repente

44.08226 N 92.51265 W EN34rb

 

From: Support@HamApps.groups.io <Support@HamApps.groups.io> On Behalf Of Gilbert Baron via Groups.Io
Sent: Thursday, December 26, 2019 13:29
To: Support@HamApps.groups.io
Subject: Re: [HamApps] UDP port problems

 

Yup, I get this same nasty error. I posted about it a few minutes ago but did not have your nice screen shot.

 

Outlook Desktop Gil W0MN

Hierro Candente Batir de Repente

44.08226 N 92.51265 W EN34rb

 

From: Support@HamApps.groups.io <Support@HamApps.groups.io> On Behalf Of Rick Johnson
Sent: Wednesday, December 4, 2019 10:34
To: Support@HamApps.groups.io
Subject: [HamApps] UDP port problems

 

JTAlert 2.15.3 will not communicate with WSJT-X 2.1.2.  Get the famous

 

 

I have rebooted the computer, reloaded both programs, checked that the 3 boxes are checked.  I don’t know what else to do.

The setup in config for WSJT is correct.  I have not changed my virus software….same ones that have been running for months.

Can someone suggest something.

 

73, Rick W3BI

polarmail@...

 

 

 

Sent from Mail for Windows 10

 


--

W0MN EN34rb 44.08226 N 92.51265 W

Hierro candente, batir de repente


--

W0MN EN34rb 44.08226 N 92.51265 W

Hierro candente, batir de repente


--

W0MN EN34rb 44.08226 N 92.51265 W

Hierro candente, batir de repente


locked Re: UDP port problems

Gilbert Baron <w0mn00@...>
 

I was not able to get JTALERT to work over the UDP. I got the message about checking the three boxes and then tried it. I got a permission error. After checking the three UDP boxes in settings AND terminating both programs and restarting it seems to be working. I need to play with it and learn it for a bit to see but I think it was my fault.

 

I have been using FT8 and just using the log file to import to DXKEEPER but want it to set it up with DXLABS now so it will be a bit of learning. There is a pretty big learning curve with these programs , especially if you add in spot collector. 😝-)

 

I do have one other problem. I have trouble closing JTALERT. Click the X just brings up the callsigns per band screen. I do not see a terminate button , no red square etc. like other windows programs.

 

Outlook Desktop Gil W0MN

Hierro Candente Batir de Repente

44.08226 N 92.51265 W EN34rb

 

From: Support@HamApps.groups.io <Support@HamApps.groups.io> On Behalf Of Gilbert Baron via Groups.Io
Sent: Thursday, December 26, 2019 13:29
To: Support@HamApps.groups.io
Subject: Re: [HamApps] UDP port problems

 

Yup, I get this same nasty error. I posted about it a few minutes ago but did not have your nice screen shot.

 

Outlook Desktop Gil W0MN

Hierro Candente Batir de Repente

44.08226 N 92.51265 W EN34rb

 

From: Support@HamApps.groups.io <Support@HamApps.groups.io> On Behalf Of Rick Johnson
Sent: Wednesday, December 4, 2019 10:34
To: Support@HamApps.groups.io
Subject: [HamApps] UDP port problems

 

JTAlert 2.15.3 will not communicate with WSJT-X 2.1.2.  Get the famous

 

 

I have rebooted the computer, reloaded both programs, checked that the 3 boxes are checked.  I don’t know what else to do.

The setup in config for WSJT is correct.  I have not changed my virus software….same ones that have been running for months.

Can someone suggest something.

 

73, Rick W3BI

polarmail@...

 

 

 

Sent from Mail for Windows 10

 


--

W0MN EN34rb 44.08226 N 92.51265 W

Hierro candente, batir de repente


--

W0MN EN34rb 44.08226 N 92.51265 W

Hierro candente, batir de repente


locked Re: UDP port problems

Gilbert Baron <w0mn00@...>
 

Yup, I get this same nasty error. I posted about it a few minutes ago but did not have your nice screen shot.

 

Outlook Desktop Gil W0MN

Hierro Candente Batir de Repente

44.08226 N 92.51265 W EN34rb

 

From: Support@HamApps.groups.io <Support@HamApps.groups.io> On Behalf Of Rick Johnson
Sent: Wednesday, December 4, 2019 10:34
To: Support@HamApps.groups.io
Subject: [HamApps] UDP port problems

 

JTAlert 2.15.3 will not communicate with WSJT-X 2.1.2.  Get the famous

 

 

I have rebooted the computer, reloaded both programs, checked that the 3 boxes are checked.  I don’t know what else to do.

The setup in config for WSJT is correct.  I have not changed my virus software….same ones that have been running for months.

Can someone suggest something.

 

73, Rick W3BI

polarmail@...

 

 

 

Sent from Mail for Windows 10

 


--

W0MN EN34rb 44.08226 N 92.51265 W

Hierro candente, batir de repente


locked UDP Not accessible for DXLAB logging and such

Gilbert Baron <w0mn00@...>
 

I cannot get UDP working on JTALERT. I have all 3 boxes checked but something is forbidding it to operate. I cannot find anything in help to describe exactly what to do. I assume the firewall needs some permission, but some documentation is needed here. It used to work fine before UDP is now used and I understand that UDP is a better way but I am not able to get it set up. Again, I do have the three boxes checked.

 

 

I am not asking for a full step by step here if you can point me to the correct documentation, that would be enough.

I am using W10.

 

I tried to find an answer in the online help but search did not provide an answer. Is there a PDF version that allows for full text search?

 

 

 

 

Outlook Desktop Gil W0MN

Hierro Candente Batir de Repente

44.08226 N 92.51265 W EN34rb

 


--

W0MN EN34rb 44.08226 N 92.51265 W

Hierro candente, batir de repente


locked Re: JT Alert 2.15.5 slow - Official Response.

jwhiteak.hou@...
 

Hi Laurie,

Thanks for your efforts on an excellent app! I hope you and the family are enjoying some seasonal downtime.

I wanted to followup to your suggestion of trying 2.15.5 beta. I did finally download it, and the callsign display speed is normal - just as fast as 2.15.3.

Take care!

-Jason, NK9B


locked Re: Callsign checking too slow

Jim Reisert AD1C
 

On Thu, Dec 26, 2019 at 7:08 AM Larry Banks W1DYJ wrote:

There are apparently some issues with delayed decodes for some users with
2.15.5. Most users who see this have gone back to 2.15.3 or, as I have,
stayed on 2.15.3 until Laurie has a chance to diagnose and update the sw.
Thanks, Larry. I have been away for a couple of weeks and didn't
realize this was a recent problem. 2.15.3 seems much better.

In my setup, it's still taking one second into the next Tx period to
display the decoded callsigns. My belief is that it should not take
even that long to cross-check 20-some-odd callsigns against an SQLITE
database.

--
Jim Reisert AD1C, <jjreisert@alum.mit.edu>, http://www.ad1c.us


locked Re: Callsign checking too slow

Larry Banks
 

Hi Jim,

There are apparently some issues with delayed decodes for some users with 2.15.5. Most users who see this have gone back to 2.15.3 or, as I have, stayed on 2.15.3 until Laurie has a chance to diagnose and update the sw.

73 -- Larry -- W1DYJ

-----Original Message-----
From: Jim Reisert AD1C
Sent: Thursday, December 26, 2019 9:01
To: Support@hamapps.groups.io
Subject: [HamApps] Callsign checking too slow

I'm using JTAlert 2.15.5 on a relatively fast 64-bit Windows 10
computer (Core i7-7000, 24 GB RAM, ATA SSD). I am reading in my FT8
QSOs via an ADIF file. There are 9400 QSOs in the log. I have the
latest version of WSJT-X (2.1.2).

I'm currently monitoring FT8 on 7074 KHz. WSJT-X is decoding around
25 callsigns per period. It's taking several (3) seconds into the
next Tx period for JTAlert to populate the callsigns in the window.
So it's pretty much too late to decide to call a station that was just
decoded.

Why can't JTAlert finish the callsign checking and display the results
before the next period starts?

I have (only) the following checks turned on:

- Wanted DXCC
- Wanted Grid
- Wanted Callsigns

If this is based solely on the # of QSOs in the log, I can't imagine
how long the wait must be for 20K or more QSOs.

--
Jim Reisert AD1C, <jjreisert@alum.mit.edu>, http://www.ad1c.us


locked Callsign checking too slow

Jim Reisert AD1C
 

I'm using JTAlert 2.15.5 on a relatively fast 64-bit Windows 10
computer (Core i7-7000, 24 GB RAM, ATA SSD). I am reading in my FT8
QSOs via an ADIF file. There are 9400 QSOs in the log. I have the
latest version of WSJT-X (2.1.2).

I'm currently monitoring FT8 on 7074 KHz. WSJT-X is decoding around
25 callsigns per period. It's taking several (3) seconds into the
next Tx period for JTAlert to populate the callsigns in the window.
So it's pretty much too late to decide to call a station that was just
decoded.

Why can't JTAlert finish the callsign checking and display the results
before the next period starts?

I have (only) the following checks turned on:

- Wanted DXCC
- Wanted Grid
- Wanted Callsigns

If this is based solely on the # of QSOs in the log, I can't imagine
how long the wait must be for 20K or more QSOs.

--
Jim Reisert AD1C, <jjreisert@alum.mit.edu>, http://www.ad1c.us


locked Re: Running JTAlert on a separate computer

neil_zampella
 

He wants to run WSJT-X on a Raspberry Pi, with JT-Alert on another computer where he controls the Pi with VNC.  ...

Neil, KN3ILZ


locked Re: Autostart jtalert/wsjt-x problem

g4wjs
 

On 26/12/2019 10:19, marsip@... wrote:
I'm using DXlab launcher (ver 2.1.2) which can start applications, after DXlab has started.
I have entered JTAlert as an option for this.
JTAlert starts, but I get a popup, where I have to select to start WSJT-X or JTDX.

The desktop icon for JTAlert, has a start path "C:\Program Files (x86)\HamApps\JTAlert\JTAlert.exe" /wsjtx".
But if I add "wsjtx" as an start program option in DXlab launcher, it doesn't work (or at least I can't get to work).

Is it possible to start WSJT-X in this way, without getting the popup select window from JTAlert?

OM,

try writing a one line batch file:

"C:\Program Files (x86)\HamApps\JTAlert\JTAlert.exe" /wsjtx

then invoke that from DX Lab Suite Launcher.

73
Bill
G4WJS.


--
73
Bill
G4WJS.


locked Autostart jtalert/wsjt-x problem

marsip@...
 

I'm using DXlab launcher (ver 2.1.2) which can start applications, after DXlab has started.
I have entered JTAlert as an option for this.
JTAlert starts, but I get a popup, where I have to select to start WSJT-X or JTDX.

The desktop icon for JTAlert, has a start path "C:\Program Files (x86)\HamApps\JTAlert\JTAlert.exe" /wsjtx".
But if I add "wsjtx" as an start program option in DXlab launcher, it doesn't work (or at least I can't get to work).

Is it possible to start WSJT-X in this way, without getting the popup select window from JTAlert?


locked Re: Running JTAlert on a separate computer

RED
 

HI Richard, Do you only want to run only JTAlert on a separate-computer, or would you like to run both WSJT-X and JTAlert on the separate-computer?  If it is the latter, I may have a solution for you.  Also, how are you connecting to your radio, USB or Ethernet?
de Bob K0SIR


locked Re: JTAlert not logging to DXKeeper

Ed Ireland
 

Thanks Laurie.  That fixed it.  I never had to hit the OK button in my previous setup.  When the "73" message (Tx5) on =WSJT-X was sent, a box popped up that said "QSO successfully logged".  Is there a setting for automatic logging?  Thanks for your help.

Ed K5YZW 

On Wed, Dec 25, 2019 at 1:41 PM HamApps Support (VK3AMA) <vk3ama.ham.apps@...> wrote:
On 26/12/2019 6:17 am:
I have not been able to get JTAlert to log to DXKeeper after moving to a new computer.  There are no error messages but QSO's are not logged.  Any suggestions are appreciated.
OM,

If JTAlert is not showing a logging failure message (assuming you haven't turned off those notifications), the likely cause of non-logging is that your not clicking the "OK" button on the WSJT-X "Log QSO" window. While JTAlert logging is automatic that only occurs when it receives a QSO logged data packet from WSJT-X which requires you manually hit the "OK" button.

de Laurie VK3AMA


locked Re: JTAlert not logging to DXKeeper

HamApps Support (VK3AMA)
 

On 26/12/2019 6:17 am:
I have not been able to get JTAlert to log to DXKeeper after moving to a new computer.  There are no error messages but QSO's are not logged.  Any suggestions are appreciated.
OM,

If JTAlert is not showing a logging failure message (assuming you haven't turned off those notifications), the likely cause of non-logging is that your not clicking the "OK" button on the WSJT-X "Log QSO" window. While JTAlert logging is automatic that only occurs when it receives a QSO logged data packet from WSJT-X which requires you manually hit the "OK" button.

de Laurie VK3AMA


locked JTAlert not logging to DXKeeper

Ed Ireland
 

I have not been able to get JTAlert to log to DXKeeper after moving to a new computer.  There are no error messages but QSO's are not logged.  Any suggestions are appreciated.


locked Re: ASTERISK

Michael Black
 

Means they are calling CQ.

de Mike W9MDB




On Wednesday, December 25, 2019, 10:49:57 AM CST, KR4LU <dwimmer34@...> wrote:


What is the meaning of an asterisk in front of a callsign in a callsign box?


locked ASTERISK

KR4LU
 

What is the meaning of an asterisk in front of a callsign in a callsign box?

8021 - 8040 of 34798