Date   

locked Re: For Laurie VK3AMA & or Coder, Receiving UDP Rebroadcast from JTAlert into my Visual Basic Program

Thomas Mize KJ4GK
 

Thank you so much Laurie VK3AMA for pointing me in the right direction. Also Hamspots.net is working PERFECT NOW! Have a great New Year buddy.
Thomas KJ4GK


locked Re: JTAlert 2.15.6 display speed and detected virus alert

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

McAfee had the same problem. I intend to file a formal request to take JTAlert off of their database. I will include a link to Laurie’s page with the virus scan info. 

Norm

On Dec 31, 2019, at 10:48 PM, HamApps Support (VK3AMA) <vk3ama.ham.apps@...> wrote:


On 1/01/2020 2:06 pm, Dave Taylor wrote:
So is there a virus issue, is it falsely triggering or what.

Dave n1fcc 
There is no virus issue, only a false-positive virus issue.

There has never been a virus/trojan/malware with any of the JTAlert releases.

de Laurie VK3AMA


locked Re: JTAlert 2.15.6 display speed and detected virus alert

HamApps Support (VK3AMA)
 

On 1/01/2020 2:06 pm, Dave Taylor wrote:
So is there a virus issue, is it falsely triggering or what.

Dave n1fcc 
There is no virus issue, only a false-positive virus issue.

There has never been a virus/trojan/malware with any of the JTAlert releases.

de Laurie VK3AMA


locked Re: JTAlert 2.15.6 display speed and detected virus alert

Dave Taylor <n1fcc@...>
 

So is there a virus issue, is it falsely triggering or what.

Dave n1fcc 


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

HamApps Support (VK3AMA)
 

Please re-download JTAlert 2.15.6 it has this defect corrected.

Once you start the new 2.15.6 check the Help -> About window, it should show build 0001, the old non-working version is build 0000.

de Laurie VK3AMA


locked Working all OK here

n4qwf .
 

Thank you for the new version. It is performing just fine. I worked numerous stations on 40m FT4 this afternoon with very little if any noticeable latency. 

Running Windows 7 Home Premium SP1 32 bit, Flex 5000, PowerSDR software version 2.7.2, WSJT-X version 2.1.2, JTAlert version 2.15.6, DXLAB suite

73<<John


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

HamApps Support (VK3AMA)
 

On 1/01/2020 7:44 am, David Burden wrote:
I have installed 2.16.6, rebooted etc. 2 instances of JT-Alert are correctly running, but only #1 is being recorded by the Decoder window.

Did I miss a step?

73 
David

David,

No you didn't miss a step, I did!

This was fixed and confirmed by the Test team a few weeks ago. In the interim, I had need to rollback some changes in one of the source files and that fix got wiped. I am recompiling the code at the moment and will push an update to the server once complete, standby.

de Laurie VK3AMA
 


locked Re: JTAlert 2.15.6 display speed

HamApps Support (VK3AMA)
 

On 1/01/2020 11:24 am, Rich - K1HTV wrote:
I installed JTAlert version 2.15.6 on my Windows 7 computer and tested it with WSJT-X on a very busy 40 Meter band with in excess of 3 dozen decodes per 15 second period. Decodes were displayed in the 9 X 4 matrix in waves, the first batch of call displayed in less than a second, the second batch about a second later and another batch of calls another second later.

Callsigns displayed in batches like this tends to occur when WSJT-X is performing multiple passes in processing its decodes. What Decode level do you have set and is AP enabled?

de Laurie VK3AMA


locked Re: Thanks for faster display of decoded Callsigns! (version 2.15.6)

Christopher Corbett
 

Yes, it resolved my issues as well!    Cheers & 73  - Christopher W0WC


locked JTAlert 2.15.6 display speed and detected virus alert

Rich - K1HTV
 

I installed JTAlert version 2.15.6 on my Windows 7 computer and tested it with WSJT-X on a very busy 40 Meter band with in excess of 3 dozen decodes per 15 second period. Decodes were displayed in the 9 X 4 matrix in waves, the first batch of call displayed in less than a second, the second batch about a second later and another batch of calls another second later.
 
I ran into a problem when I tried to use F11 to access "Manage Settings". Microsoft Security Essentials detected an item called: "Trojan:Win32/Azden.A!cl" with an alert level of Severe and quarantined it. When I restarted JTAlert I received the message:
 
The following file is missing...
"C:\Program Files (x86)\HamApps\JTAlert\plugins\JTAlertSettings.exe"
 
The fix was to add the full path to the "JTAlertSettings.exe" to the Excluded File Locations list. After reinstalling and restarting JTAlert, I was able to open the Settings/Manage Settings OK.
 
73,
Rich - K1HTV
 


locked Re: Some odd things happening

Jim N6VH
 

On 12/31/2019 11:34 AM, Laurie, VK3AMA wrote:
On 1/01/2020 4:29 am, Phil Cooper via Groups.Io wrote:
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*.
If JTAlert is showing a zone it is because it believes it is the correct zone. JTAlert will not arbitrarily show a value if it knows it is wrong. Your statement doesn't make a lot of sense. I'll investigate if this is indeed an incorrect zone.

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*.
Normally that would be the case. If a B4 station is still alerting then you have the "Play Alert when decoded Callsign worked B4" option set for that Alert type. You need to turn that off if you don't want to be alert when a Stations are B4s.


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
de Laurie VK3AMA
Laurie,

Phil didn't say what logger he is using. That might be helpful. I did a test, and put RA9DX/1 into WSJT-X, which then put the call into JTAlert (2.15.6). JTAlert shows the CQ zone as 16, as seen in the attached picture. I am using callsign datbase 2020 01 01. I then logged the (fake) QSO to Log4OM. Log4|OM shows the zone as 17. The wsjtx.log doesn't show any zone for any QSO. I don't have any lookups set in either program. It seems tha my logger is getting the zone from some source other than JTAlert or WSJT-X.

This might not be a JTAlert problem.

I wonder if Phil's logger is getting the incorrect zone from some other source.
73,

Jim N6VH


locked Re: Some odd things happening

Phil Cooper
 

Hi Laurie, and Bill G4WJS,

 

Bill, I can see the logic to your statement, and that was the case, so that problem is solved.

 

Laurie, regarding the UA9/1 case, I can’t remember the specific calls, but just lately, there have been at least two UA9 stations signing /1, and in both cases, their zone was shown as 17 and 18..

I didn’t complete with the one that called me, and the other had disappeared before I was able to work him.

Maybe a check of the WSJT log file will help there, and if it does, I will let you know which calls. That’s a job for tomorrow now…

 

HNY and 73 de Phil GU0SUP

 

From: Support@HamApps.groups.io [mailto:Support@HamApps.groups.io] On Behalf Of Laurie, VK3AMA
Sent: 31 December 2019 19:35
To: Support@HamApps.groups.io
Subject: Re: [HamApps] Some odd things happening

 

 

On 1/01/2020 4:29 am, Phil Cooper via Groups.Io wrote:

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.

If JTAlert is showing a zone it is because it believes it is the correct zone. JTAlert will not arbitrarily show a value if it knows it is wrong. Your statement doesn't make a lot of sense. I'll investigate if this is indeed an incorrect zone.


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.

Normally that would be the case. If a B4 station is still alerting then you have the "Play Alert when decoded Callsign worked B4" option set for that Alert type. You need to turn that off if you don't want to be alert when a Stations are B4s.



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


de Laurie VK3AMA


locked Re: 2.15.6 install triggers multiple malware warnings? This usually doesn't happen to me with JTAlert

neil_zampella
 

False positive ... as long as you've downloaded it from Hamapps.com, there is no virus/malware/trojan attached.

Many antivirus programs will call out ham radio programs as 'malware/malicious' as there aren't that many users of the software.  I installed and AVG didn't even give me the usual "wait 15 seconds while I scan this" message.

You can reinstall the program without worries.     

 

Neil, KN3ILZ


locked Re: McAfee Quarantines JTAlertSettings

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

Thanks.  V.5 is working fine.  Will see how it goes. Looking forwarded to v.6  Awesome program!

On Tue, Dec 31, 2019 at 11:35 AM Michael Black via Groups.Io <mdblack98=yahoo.com@groups.io> wrote:
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=yahoo.com@groups.io> 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



--

Norm


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

Thomas Mize KJ4GK
 

Ok thank you for your fast reply Laurie. It amazes me how you stay on top of all these questions which is a full time job and your doing it for the love of the hobby. If you had a donate button on Hamspots.net I would be donating quit often :)

When you get some free time, check out my programming related question with the rebroadcast of wsjt's decodes via JTAlert. Thanks a lot!


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

Thomas Mize KJ4GK
 

Thanks Laurie, This is why I actually wait 62 Seconds for every refresh. So it is actually no different then if I left the page up in my browser. I am in no way trying to cause any issues at all, just been programming since I was 10 years old and love to always try and make something to make my experience more fun.

Thank you again for your advice.

Thomas KJ4GK


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

David Burden
 

Hi Laurie,

I have installed 2.16.6, rebooted etc. 2 instances of JT-Alert are correctly running, but only #1 is being recorded by the Decoder window.

Did I miss a step?

73 
David


locked Thanks for faster display of decoded Callsigns! (version 2.15.6)

Jim AF5FH
 

Just read the email notice about version 2.15.6 being available. Installed it, and want to say thanks for the faster display of the decoded Callsigns at the end of an Rx period! Works much faster on my laptop.

73, Jim, AF5FH

P.S. - Windows Security on my Windows 10 laptop flagged JTAlertSettings.exe as a threat "Trojan:Win32/Azden.A!cl" so I had to click some buttons for the install to complete.


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

HamApps Support (VK3AMA)
 

On 1/01/2020 1:41 am, Thomas Mize KJ4GK wrote:

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

Be very careful with any automated software you use to screen-scrape HamSpots, it has the potential to trigger the anti-bot software and get your IP address blocked at the firewall. If you force refresh the spots page, rather than letting the page refresh automatically your at real risk of getting blocked.

If you refresh the spots page an excessive number of times per minute than blocking is assured.

de Laurie VK3AMA
 


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

HamApps Support (VK3AMA)
 

On 1/01/2020 1:41 am, Thomas Mize KJ4GK wrote:

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?
HamSpots is having a bad day today. It is under unprecedented load and has multiple automatic restarts within the last 24 hours. Unfortunately in this situation spots get lost. Currently the PSKReporter feed is disabled, it contributes significantly to the load due to the high spot volume so is often the first service to be disabled when trying to resolve Server issues.

de Laurie VK3AMA