Date   

locked Some odd things happening

Phil Cooper
 

Hi all,

As I have been off over the holiday period, I have been quite active on the bands with FT8 and FT4.

I have noted a couple of odd things during the past week or so.
The first is a few UA9 stations running as (for example) RA9DX/1 but I see that JTAlert wants to log them as Z17 or Z18, when in fact they are actually in Z16.
I had expected JTAlert to either show the correct Zone, or leave it blank.

The second issue I am seeing is the response to B4. An example is J79WTA, who I worked a few days ago on 20m FT8, is now showing as J79WTA in yellow, but with B4 appended to the call.
As I have done a Scan Log & Update, I had expected this to then show in grey with J79WTA - B4.

I am running the latest versions of JTAlert and Callsign Database.

Neither issue is a big deal, but I am curious, as I have not noticed this behaviour before.

I will take this opportunity to wish you all a very Happy New Year 2020, especially to Laurie, who has provided so much to the community....

Very best 73

Phil GU0SUP


locked Re: JTAlert QRZ Lookup stopping

Mike Steiner
 

I\ve had the same issue with 2.15.3 but just closing JT alert program and restarting it fixes my issue. I get a little more out, more like hours.

 

Mike K7QDX

 

From: Support@HamApps.groups.io <Support@HamApps.groups.io> On Behalf Of Morris WA4MIT via Groups.Io
Sent: Tuesday, December 31, 2019 7:34 AM
To: Support@HamApps.groups.io
Subject: [HamApps] JTAlert QRZ Lookup stopping

 

I am using JTAlert 2.15.5 with JTDX and HRD (Latest version) when working a new contact Alert is failing to look up this callsign on QRZ. Stations that have been worked previously worked the info shows OK. This has been occurring for about a week or so. This starts after operating for about an hour or so and computer had been on for a good while. I can restart computer and it will correct problem. Today I tried some things and was able to stop QRZ lookup in Alert then restart lookup and it would work for one contact then stop again. Today this has happened twice first time I restarted computer and now after about 1 hour on the air it has happened again. I looked in my firewall and Alert has a pass setting I am running Windows 10 with latest updates Microsoft security with firewall. I did notice that there were two windows updates on DEC 11 & 12. Thanks for any help/suggestion I am a long time user of JTAlert and really appreciate all your hard work Laurie.
73 Morris WA4MIT


locked Re: McAfee Quarantines JTAlertSettings

Michael Black
 

You can always downgrade to 2.15.3 again -- that version is still available for download.

2.15.6 should be out soon which seems to be working very well...it's in beta right now.

Mike





On Tuesday, December 31, 2019, 10:31:14 AM CST, Norm D'Allura <norm.dallura@...> wrote:


2.15.3. I hesitate to update due to the reports of slowness in .5. Everything is working great so far. If .5 addresses this issue, I will upgrade immediately. 

Norm

On Dec 31, 2019, at 11:27 AM, Michael Black via Groups.Io <mdblack98@...> wrote:


What version of JTAlert are you running?
I thought that problem was fixed in recent releases.

2.15.5 is the most recent.

de Mike W9MDB




On Tuesday, December 31, 2019, 10:21:58 AM CST, Norm D'Allura <norm.dallura@...> wrote:


McAfee virus protection keeps Quaranteeing JTAlertSettings.exe even though I have it on my excluded list. Their on-line help says that if the file changes, it is subject to quarantine again. It is a settings file so I expect it to change. I can restore the file, but that is annoying. If there a way to prevent this overzealous quarantine besides finding another virus program?

Norm


locked Re: McAfee Quarantines JTAlertSettings

Norm D'Allura <norm.dallura@...>
 

2.15.3. I hesitate to update due to the reports of slowness in .5. Everything is working great so far. If .5 addresses this issue, I will upgrade immediately. 

Norm

On Dec 31, 2019, at 11:27 AM, Michael Black via Groups.Io <mdblack98@...> wrote:


What version of JTAlert are you running?
I thought that problem was fixed in recent releases.

2.15.5 is the most recent.

de Mike W9MDB




On Tuesday, December 31, 2019, 10:21:58 AM CST, Norm D'Allura <norm.dallura@...> wrote:


McAfee virus protection keeps Quaranteeing JTAlertSettings.exe even though I have it on my excluded list. Their on-line help says that if the file changes, it is subject to quarantine again. It is a settings file so I expect it to change. I can restore the file, but that is annoying. If there a way to prevent this overzealous quarantine besides finding another virus program?

Norm


locked Re: McAfee Quarantines JTAlertSettings

Michael Black
 

What version of JTAlert are you running?
I thought that problem was fixed in recent releases.

2.15.5 is the most recent.

de Mike W9MDB




On Tuesday, December 31, 2019, 10:21:58 AM CST, Norm D'Allura <norm.dallura@...> wrote:


McAfee virus protection keeps Quaranteeing JTAlertSettings.exe even though I have it on my excluded list. Their on-line help says that if the file changes, it is subject to quarantine again. It is a settings file so I expect it to change. I can restore the file, but that is annoying. If there a way to prevent this overzealous quarantine besides finding another virus program?

Norm


locked McAfee Quarantines JTAlertSettings

Norm D'Allura <norm.dallura@...>
 

McAfee virus protection keeps Quaranteeing JTAlertSettings.exe even though I have it on my excluded list. Their on-line help says that if the file changes, it is subject to quarantine again. It is a settings file so I expect it to change. I can restore the file, but that is annoying. If there a way to prevent this overzealous quarantine besides finding another virus program?

Norm


locked JTAlert QRZ Lookup stopping

Morris WA4MIT
 

I am using JTAlert 2.15.5 with JTDX and HRD (Latest version) when working a new contact Alert is failing to look up this callsign on QRZ. Stations that have been worked previously worked the info shows OK. This has been occurring for about a week or so. This starts after operating for about an hour or so and computer had been on for a good while. I can restart computer and it will correct problem. Today I tried some things and was able to stop QRZ lookup in Alert then restart lookup and it would work for one contact then stop again. Today this has happened twice first time I restarted computer and now after about 1 hour on the air it has happened again. I looked in my firewall and Alert has a pass setting I am running Windows 10 with latest updates Microsoft security with firewall. I did notice that there were two windows updates on DEC 11 & 12. Thanks for any help/suggestion I am a long time user of JTAlert and really appreciate all your hard work Laurie.
73 Morris WA4MIT


locked Re: Hamspots.net's Spots seem different or slower to anyone?

Thomas Mize KJ4GK
 

Hello Laurie VK3AMA, sorry one more thing to add

Something to ADD, here is an example, It appears that some spots are being sent and some are not>

For example I am on 20m rigtht and it is always ALWAYS 50 spots on both sides which ages no later then 2 or 3 minutes but the ages are up to 20 minutes on both. This isn't right....and here is how I now that it isn't just something on my end.

There is a guy from the Isle Of Man on right now in 20m, his call is GD0TEP (No matter if he is sending Spots, to the right there should be a list of EVERYONE that has spotted him)

He has been on for over an hour, if you go look at this spots, NO ONE had spotted him and It doesn't show that I have spotted him either. Very weird. 

What is going on Laurie? I hope I am not the only one out here that is a Hamspots.net Fanatic that watches it every day lol so Imma notice something like this quick.

I guess I have been so use to it working so well it has me thrown off to see this. 

I don't know if many people understand how valuable your hamspots.net site is. It make my whole experience so much colorful.


locked Hamspots.net's Spots seem different or slower to anyone?

Thomas Mize KJ4GK
 

Hellow Laurie VK3AMA or who every is reading,

I have designed a simple program using visual studio that updates from my hamspots.net, My spots page so that I can constantly see my spots while working FT8. I have been using this for about 5 months with no problem at all.

Starting yesterday I started noticing some Delays/Lags.

Laurie Has anything changed in the way the spots are being counted or anything different with the website?

For example a few times I will see hamspots.net go through 2 or 3 60sec cycles until it does update and by then some of the spots which would say 1m is 2 or 3m in age.

I am constantly studying to one day be even half of the programmer you are 
Laurie. That is why I know I have to leave Visual Basic and go into Phython or some other language. I would love to speak with you about this in a personal email if you every would have the time Laurie. I know you are pretty much a Celebrity, or at least to me you are :) I know if I could every figure out how to receive the UDP packets from WSJT like you do for JT Alert in to my program It would be a huge jump for me. I receive the one time UDP from Jtalert after a contact perfect but the constant UDP reboardcast of the decoded messages come in as a mess of mixed ascii characters and such which I can't phrase using reg ex and make sense of it. I can't receive the UDP form WSJT at all.

Please Laurie let me know if it is ok to send you a personal email and maybe show you what I have so far and I would love to show you what I have built using your AWESOME hamspots.net. It has made my experience so much better.

Sorry for getting off in another subject...

Thomas, KJ4GK


locked Re: Unable to allocate memory error

Michael Black
 

You need to upgrade JTAlert...you're way behind....current version is 2.15.5 and 2.15.6 is due out soon.

de Mike W9MDB




On Tuesday, December 31, 2019, 07:15:58 AM CST, Dave LeDuc <n1ix@...> wrote:


I am getting the Autoit "unable to allocate memory" error popup on a regular basis.
I'm not really sure if the error is generated by WSTJ-X or JTAlert application although it has been reported in the past as a JTalert issue
When the error occurs the WSTJ-X waterfall freezes. I have to restart the computer to clear the error.

Both applications along with LOG4om ran together for at least two years before I started having this problem.

I am using the current versions of both WSTJ-X (2.1.2) and JTAlert.(2.14.4) LOG4om with the autolog feature. The PC has 6GB of ram.
Processor  is   Intel(R) Core(TM) i5-2320 CPU @ 3.00GHz, 3001 Mhz, 4 Core(s), 4 Logical Processor(s)

Any Ideas? Do I have a hardware problem? Is there a way to run a barebones version of JTAlert that doesn't allocated additional memory?

Thanks es HNY!
Dave N1IX


locked Unable to allocate memory error

Dave LeDuc
 

I am getting the Autoit "unable to allocate memory" error popup on a regular basis.
I'm not really sure if the error is generated by WSTJ-X or JTAlert application although it has been reported in the past as a JTalert issue
When the error occurs the WSTJ-X waterfall freezes. I have to restart the computer to clear the error.

Both applications along with LOG4om ran together for at least two years before I started having this problem.

I am using the current versions of both WSTJ-X (2.1.2) and JTAlert.(2.14.4) LOG4om with the autolog feature. The PC has 6GB of ram.
Processor  is   Intel(R) Core(TM) i5-2320 CPU @ 3.00GHz, 3001 Mhz, 4 Core(s), 4 Logical Processor(s)

Any Ideas? Do I have a hardware problem? Is there a way to run a barebones version of JTAlert that doesn't allocated additional memory?

Thanks es HNY!
Dave N1IX


locked Re: 2nd Instance not showing in Decode History Window

asobel@...
 

Hi

I did complain on the same problem two weeks ago.

Hope it will be solved in the next JTalert version.

 

Amos 4X4MF

 

 

From: Support@HamApps.groups.io <Support@HamApps.groups.io> On Behalf Of David Burden
Sent: יום ג 31 דצמבר 2019 00:03
To: Support@HamApps.groups.io
Subject: [HamApps] 2nd Instance not showing in Decode History Window

 

Hi,

I have two versions of WSJTX running and JT Alert 2.15.5. Each JT alert has attached itself to each WSJTX instance and shows the decodes as expected. However, only the instance started first will report to the Decodes window. Rig names and UDP ports are all set up correctly.

Any ideas on how to get this working please.

David


locked 2nd Instance not showing in Decode History Window

David Burden
 

Hi,

I have two versions of WSJTX running and JT Alert 2.15.5. Each JT alert has attached itself to each WSJTX instance and shows the decodes as expected. However, only the instance started first will report to the Decodes window. Rig names and UDP ports are all set up correctly.

Any ideas on how to get this working please.

David


locked Re: Wanted country not moving to Unwanted side when worked

Larry Banks
 

Hi Jim,
 
It won’t become unwanted until you download a confirmed QSL from LoTW  (or wherever) and you update JTA.

73 -- Larry -- W1DYJ

 

From: Jim Cary
Sent: Monday, December 30, 2019 15:19
Subject: [HamApps] Wanted country not moving to Unwanted side when worked
 
I have Wanted Alerts Set to Anyband for FT8 Mode.  But when I work a "wanted country" in doesn't move from the Wanted to the Unwanted side.  I have logging enabled (DXLab DXKeeper).

What am I doing wrong?

Jim
W2SM


locked Wanted country not moving to Unwanted side when worked

Jim Cary
 

I have Wanted Alerts Set to Anyband for FT8 Mode.  But when I work a "wanted country" in doesn't move from the Wanted to the Unwanted side.  I have logging enabled (DXLab DXKeeper).

What am I doing wrong?

Jim
W2SM


locked Re: JT alert and QRZ Logbook

Michael Ernst
 

Ken,

I am not sure if the API key changes when you renew. You should check it to name sure. You can find it by going to qrz.com. then open your logbook. On the right side about a third of the way down select settings. Your key Erik be on ether look left side in a box about middkev of the screen. Make sure it matches in your software.

73,
Mike, AE8U


Sent from my T-Mobile 4G LTE Device


-------- Original message --------
From: Ken Desjardins <zk5@...>
Date: 12/30/19 05:49 (GMT-05:00)
To: Support@HamApps.groups.io
Subject: Re: [HamApps] JT alert and QRZ Logbook

Yes it did, that's kind of when it started.  I haven't been on the air in a while and when I came back I noticed my QRZ subscription had expired. So I renewed my subscription, updated WSJTX and JTAlert all at the same time. So I'm not sure if it's an issue with my API key with QRZ or glitch in the JTAlert update.  I emailed QRZ support and they said my subscription and API key is fine. So that's what brought me here. 


locked Re: JT alert and QRZ Logbook

Ken Desjardins
 

Yes it did, that's kind of when it started.  I haven't been on the air in a while and when I came back I noticed my QRZ subscription had expired. So I renewed my subscription, updated WSJTX and JTAlert all at the same time. So I'm not sure if it's an issue with my API key with QRZ or glitch in the JTAlert update.  I emailed QRZ support and they said my subscription and API key is fine. So that's what brought me here. 


locked Re: JT alert and QRZ Logbook

Michael Ernst
 

Ken 

By any chance did your QRZ subscription expire? If it did, I don't think you can upload to the logbook any more.

73,
Mike, AE8U



Sent from my T-Mobile 4G LTE Device


-------- Original message --------
From: Ken Desjardins <zk5@...>
Date: 12/29/19 18:57 (GMT-05:00)
To: Support@HamApps.groups.io
Subject: [HamApps] JT alert and QRZ Logbook

 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

n6dl
 

Laurie,
Correct me if I'm wrong, but JTA won't open until jt-x is alive and well, at which point JTA reads the jt-x .ini file. At which point it learns the mode, frequency (thus band) and the UDP port.  That is to say JTA has not 'heard' an UDP packets or did not need to hear.
We know it does not by changing mode or band and observing the status line does not follow.  
It would be an interesting experiment to get JTA to open (without jt-x awake) and send it our own udp stream from UDP Send/Receive.


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.