Date   

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


locked Re: UDP Not accessible for DXLAB logging and such

Rick
 


It appears that OM is experiencing the same problem we have been working on.  I even tried JTDX and the proper version of JTDX and that exhibited the same problem.

You are working on the problem?!

73, Rick W3BI

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

On 12/27/2019 8:49 PM, HamApps Support (VK3AMA) wrote:
On 28/12/2019 12:09 pm, n6dl wrote:
Ah, so I'm not the only one!
for whom win10 has stopped JTAlert from 'hearing' the data stream from WSJT-X
I found UDP-Sender/Receiver from the Microsoft store..  allows one to observe the UDP data from WSJT-x.. on what ever port you choose.
Yes WSJT is streaming date and JTA is not receiving/decoding it. 
OM,

I couldn't find any previous messages from you regarding this. An unreported problem/defect is a problem/defect that will unlikely not get resolved.

What is the actual error message your getting? JTAlert when showing this error window will place a copy of the error message into the Windows clipboard, paste that into your reply.

de Laurie VK3AMA
--


Only losers need rally caps.


locked Re: UDP Not accessible for DXLAB logging and such

HamApps Support (VK3AMA)
 

On 28/12/2019 12:09 pm, n6dl wrote:
Ah, so I'm not the only one!
for whom win10 has stopped JTAlert from 'hearing' the data stream from WSJT-X
I found UDP-Sender/Receiver from the Microsoft store..  allows one to observe the UDP data from WSJT-x.. on what ever port you choose.
Yes WSJT is streaming date and JTA is not receiving/decoding it. 
OM,

I couldn't find any previous messages from you regarding this. An unreported problem/defect is a problem/defect that will unlikely not get resolved.

What is the actual error message your getting? JTAlert when showing this error window will place a copy of the error message into the Windows clipboard, paste that into your reply.

de Laurie VK3AMA


locked Re: UDP Not accessible for DXLAB logging and such

n6dl
 

Ah, so I'm not the only one!
for whom win10 has stopped JTAlert from 'hearing' the data stream from WSJT-X
I found UDP-Sender/Receiver from the Microsoft store..  allows one to observe the UDP data from WSJT-x.. on what ever port you choose.
Yes WSJT is streaming date and JTA is not receiving/decoding it. 


locked Re: Autostart jtalert/wsjt-x problem

Dave Garber
 

settings/scroll to applications, then click on autostart tab

you have to select the path of any software you wish to start, then check the 'start' or 'close' boxes as you desire

then remember to save, before closing.    

you will need to close jtalert, and any programs in the 'start' lines...   then restart jtalert

I use this for wsjt-x, n3fjp aclog, and have used it for HRD
Dave Garber
VE3WEJ / VE3IE


On Fri, Dec 27, 2019 at 3:07 AM <marsip@...> wrote:

[Edited Message Follows]

I tried write a batfile which start JTAlert, but I couldn't make it work.


locked Re: Saving settings for later restore to the same or other computer

Michael Black
 

Look in the Help/FAQ for "Move JTAlert to a new computer".  Tells you what you need to copy.

de Mike W9MDB




On Friday, December 27, 2019, 05:47:05 AM CST, Gilbert Baron <w0mn00@...> wrote:


Is there a way to save my settings other than clone and rename?  Is there a file I could save and then restore to do this? I want to set it up with DXLABS but if I make a mess I would like to easily recover. I realize the clone and configuration options are probably the way to go but what would I do if I wanted to move to a different computer or if I am forced to do a clean windows install?

 

Running latest Windows 10 with all updates if that makes any difference.

 

Outlook Laptop Gil W0MN

Hierro candente, batir de repente

44.08226N 92.51265W EN34rb

 


--

W0MN EN34rb 44.08226 N 92.51265 W

Hierro candente, batir de repente


locked Saving settings for later restore to the same or other computer

Gilbert Baron <w0mn00@...>
 

Is there a way to save my settings other than clone and rename?  Is there a file I could save and then restore to do this? I want to set it up with DXLABS but if I make a mess I would like to easily recover. I realize the clone and configuration options are probably the way to go but what would I do if I wanted to move to a different computer or if I am forced to do a clean windows install?

 

Running latest Windows 10 with all updates if that makes any difference.

 

Outlook Laptop Gil W0MN

Hierro candente, batir de repente

44.08226N 92.51265W EN34rb

 


--

W0MN EN34rb 44.08226 N 92.51265 W

Hierro candente, batir de repente


locked Re: Autostart jtalert/wsjt-x problem

marsip@...
 
Edited

Good idea make JTAlert start DXlab launcher.
Now it works flawlessly!


locked Re: Autostart jtalert/wsjt-x problem

marsip@...
 
Edited

I tried write a batfile which start JTAlert, but I couldn't make it work.


locked Re: UDP port problems

Rick
 

Welcome to the club.  Happy New Year.

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

On 12/26/2019 2:28 PM, Gilbert Baron wrote:

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

--


Only losers need rally caps.


locked JTAlert 2.15.5 - DXLab DXView and DXKeeper Lookup not working

Scott
 

Before I upgraded to JTAlert 2.15.5 whenever I would be working a station in FT8, while working the station I could see if I had worked that station's country before, and on what bands, and if they were confirmed or not, plus my DXKeeper would display how many times and what bands and modes I worked that station on in the past. Now when working a station, I don't see those items, however the QSO successfully logs to my logbook in DXKeeper and then will display in DXView. Under Applications/DXLab Suite I have checked DXKeeper/DXView/Pathfinder Lookup on new DX Call. Is there something else I'm forgetting?

Win10 64 Bit / JTAlert 2.15.5 / DXKeeper 15.3.1

Thanks in advance.
Scott/KN3A


locked Re: Callsign checking too slow

HamApps Support (VK3AMA)
 

On 27/12/2019 1:37 am, Jim Reisert AD1C wrote:
My belief is that it should not take
even that long to cross-check 20-some-odd callsigns against an SQLITE
database.
Your assuming that a Callsign lookup is all that is being performed. If that was the case, then a 20 callsign lookup wouldn't take an inordinate time, but there is a lot more happening within JTAlert plus whatever delays there are in WSJT-X processing the recorded signals and sending the UDP decode traffic. See my response to your initial message in this topic.

de Laurie VK3AMA


locked Re: Callsign checking too slow

HamApps Support (VK3AMA)
 

On 27/12/2019 1:01 am, Jim Reisert AD1C wrote:
Why can't JTAlert finish the callsign checking and display the results
before the next period starts?
Simple really, there is only one second from the end of one period before the start of a new period (FT8). In that one second, WSJT-X has to decode all the signals which can be many on the busy bands and may run multiple passes (up to 3) depending on the decode level you have set, JTAlert cannot start processing the decodes until they are received (via UDP) then it may have to perform slow disk-file based Log lookups depending on whether a Callsign has been processed in earlier periods, make decisions as to what alerts are triggered and if they pass whatever filters you have set, paint the callsigns and generate the audio alerts (3 voiced audio alerts are likely to take one second or more to play).

How long is WSJT-X taking to process a busy band of decodes? That time comes out of the one second available to JTAlert if it was ever to meet your desired requirement of alerting before the start of the new period.

Expecting all that in less than a second is unrealistic and likely will only be achieved when there are a small number of decodes (say less than 6) that already have their alerting status cached in memory after earlier decodes that required slower log file checks.

None of the above takes into consideration how aggressive your PC protection software may be set, is it actively monitoring/analyzing the temp files created by WSJT-X and JTAlert causing slower disk-reads. Is it intercepting/monitoring network traffic. While you might have a high end PC, what does its CPU and memory usage look like at the end of a period when WSJT-X is at its busiest? What other high-memory use apps are running concurrently?

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.
There is no practical difference in the sqlite log lookup between a small QSO and high QSO count log. The appropriate indexes are in place, so a lookup against a 200,000 QSO log will be near the same time as for 2,000 QSO log.

Jim Reisert AD1C
de Laurie VK3AMA


locked Re: UDP port problems

HamApps Support (VK3AMA)
 

On 27/12/2019 6:49 am, Gilbert Baron wrote:

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

JTAlert not responding to a click on the close button, is a known problem affecting a small number of Win10 users. The fix is to simply run the "Alt Layout" version of JTAlert using the correct JTAlert shortcut. This is mentioned at the very top of the webpage from where you download JTAlert.

de Laurie VK3AMA


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