Date   

locked Re: JTalert and 2m imported ADIF log does not rebuild - 4m GREEN and CANCEL in REBUILD

Franco
 
Edited

On Tue, Jun 9, 2020 at 06:04 AM, Franco HB9oab wrote:
1. I can't make the rebuild understand the vision of the fields in 2m.
I use an imported ADIF LOG, on all bands it works but not in 2m, I tried with BAND and FREQ but it is always zero on all fields even if I have enabled 2m (see images)

Solution:
I solved for the 2m ...
1. I have things not quite the same as my ADIF log, but it is still calculated on 2m, I will check if it complies with the QSOs. My config error...

2. For the 4m I have disabled and it no longer calculates it.

3. For the CANCEL key during REBUILD I have no solution ...

Thanks for help
73
Franco, HB9oab
http://qrz.com/db/hb9oab


locked Re: Special callsigns

WB8ASI Herb
 

Take a look at the JTA Decodes window.  I use it all the time because I can scan everything vertically much faster, and you can fine tune any filtering you desire.  Try it and I think you'll like it.  73 Herb WB8ASI


locked Re: JTAlert 2.16.7 is available

Frank C. D'Amato
 

I'm in the same boat with ESET Internet Security.  Unable to get JTALERT installed


locked JTalert and 2m imported ADIF log does not rebuild - 4m GREEN and CANCEL in REBUILD

Franco
 

Hi Laurie
I'm having some problems with REBUILD which I don't know if it's my problem and what I need to configure.

There are three working problems on the ADIF LOG:

1. I can't make the rebuild understand the vision of the fields in 2m.
I use an imported ADIF LOG, on all bands it works but not in 2m, I tried with BAND and FREQ but it is always zero on all fields even if I have enabled 2m (see images)

2. the 4m field is always green (I have no QSO in the 4m band), even after more rebuilds it is still green as if there were "new" 

3. during the rebuild the CANCEL key remains active, if I press it, at the end of the analysis it asks me whether to exit or continue. If I EXIT LOG SCAN, it only exits the table it is doing but continues anyway, resetting everything and putting the table in green as if there were "new"



I can't correct these and I don't know if I'm wrong somewhere in my configuration.

Thanks for help
73
Franco, HB9oab
http://qrz.com/db/hb9oab

 


locked Re: JTAlert stops updating for about 2 minutes

John Singler
 

Windows Defender and I already put the WSJT-X, JTAlert, and HRD data and program directories on the exception list
John S


locked Re: JTAlert 2.16.7 is available

Hasan Schiers N0AN
 

Further hints: For Defender 
...and spare us the "Defender sucks" comments.  This is advice for those who run Defender and are staying with it.

On another machine Chrome blocked it but allowed me to let it continue after I read the warning at the file download window.

If you can't get the file to download at all:

(Do this ONLY if you are confident that the file is safe) Any file from Laurie is SAFE as far as I am concerned)

Virus & Threat Protection > Manage Settings > 

1. Turn Real-time protection OFF
2. Turn Cloud-delivered OFF
3. Turn Automatic sample submission OFF
4. Turn Tamper Protection OFF

(Do this ONLY if you are confident that the file is safe) Any file from Laurie is SAFE as far as I am concerned)

Download the file

Then turn all of the above back ON
73, N0AN
Hasan


On Tue, Jun 9, 2020 at 5:51 AM Hasan Schiers N0AN via groups.io <hbasri.schiers6=gmail.com@groups.io> wrote:
2.16.7 Downloaded and Installed without any issues with Win10Pro and Windows Defender, as long as

1. Windows Defender is Up to Date and...
 
2. Proper exclusions were set up ahead of time (and they have been for months)

Running just fine on two different machines.

73, N0AN
Hasan


On Tue, Jun 9, 2020 at 3:51 AM <dk1wb@...> wrote:
Laurie,
Windows Defender warned that Trojan:Win32/Azden.A!cl was found in
x86)\HamApps\JTAlert\plugins\JTAlertSettings.exe and deleted it.
Please confirm.
73,
Hans, DK1WB

Carlos Reboreda schrieb am 09.06.2020 10:18 (GMT +02:00):

Hi all,

 

My experience here is the same… when there are abt 100 Kb left to finish the download, the ESET (for the first time) cancels the download, because it has detected something dangerous on dnl.hamapps.com … I’m not saying that this is the real matter, I just describe what ESET is doing about this download. I’m user of this antivirus for more tan 15 years, every euro i pay every

year for it is worth it. I tried the download with Opera, Edge and Chrome, so I think it isn’t a matter of the web browser you use. Lets see if there any other members experimenting the same

problem or it happens to be a false detection.

 

73 to all!

 

Carlos R.

EA1DWI

 

Enviado desde Correo para Windows 10

 

De: chas cartmel
Enviado: martes, 9 de junio de 2020 9:50
Para: Support@hamapps.groups.io
Asunto: Re: [HamApps] JTAlert 2.16.7 is available

 

Jacques

08:48 BST – all OK here in the UK.
Have you tries a different browser? Occasionally this works for me if I have a ‘glitch’.

73 Charlie

G4EST

www.g4est.me.uk

 

 

 

From: Support@HamApps.groups.io [mailto:Support@HamApps.groups.io] On Behalf Of Jacques Corbu
Sent: 09 June 2020 07:09
To: Support@HamApps.groups.io
Subject: [HamApps] JTAlert 2.16.7 is available

 

HI Laurie

cannot access new version the website is given as non accessible when I hit download ?  I have never had this issue and it has all the exception requires in avast etc  but this come up 

any idea would be welcomed 

stay safe Jacques F1VEV

 

This email has been scanned by BullGuard antivirus protection.

For more info visit www.bullguard.com

 

 


locked Re: JTAlert 2.16.7 is available

Hasan Schiers N0AN
 

2.16.7 Downloaded and Installed without any issues with Win10Pro and Windows Defender, as long as

1. Windows Defender is Up to Date and...
 
2. Proper exclusions were set up ahead of time (and they have been for months)

Running just fine on two different machines.

73, N0AN
Hasan


On Tue, Jun 9, 2020 at 3:51 AM <dk1wb@...> wrote:
Laurie,
Windows Defender warned that Trojan:Win32/Azden.A!cl was found in
x86)\HamApps\JTAlert\plugins\JTAlertSettings.exe and deleted it.
Please confirm.
73,
Hans, DK1WB

Carlos Reboreda schrieb am 09.06.2020 10:18 (GMT +02:00):

Hi all,

 

My experience here is the same… when there are abt 100 Kb left to finish the download, the ESET (for the first time) cancels the download, because it has detected something dangerous on dnl.hamapps.com … I’m not saying that this is the real matter, I just describe what ESET is doing about this download. I’m user of this antivirus for more tan 15 years, every euro i pay every

year for it is worth it. I tried the download with Opera, Edge and Chrome, so I think it isn’t a matter of the web browser you use. Lets see if there any other members experimenting the same

problem or it happens to be a false detection.

 

73 to all!

 

Carlos R.

EA1DWI

 

Enviado desde Correo para Windows 10

 

De: chas cartmel
Enviado: martes, 9 de junio de 2020 9:50
Para: Support@hamapps.groups.io
Asunto: Re: [HamApps] JTAlert 2.16.7 is available

 

Jacques

08:48 BST – all OK here in the UK.
Have you tries a different browser? Occasionally this works for me if I have a ‘glitch’.

73 Charlie

G4EST

www.g4est.me.uk

 

 

 

From: Support@HamApps.groups.io [mailto:Support@HamApps.groups.io] On Behalf Of Jacques Corbu
Sent: 09 June 2020 07:09
To: Support@HamApps.groups.io
Subject: [HamApps] JTAlert 2.16.7 is available

 

HI Laurie

cannot access new version the website is given as non accessible when I hit download ?  I have never had this issue and it has all the exception requires in avast etc  but this come up 

any idea would be welcomed 

stay safe Jacques F1VEV

 

This email has been scanned by BullGuard antivirus protection.

For more info visit www.bullguard.com

 

 


locked Re: JTAlert 2.16.7 is available

dk1wb@...
 

Laurie,
Windows Defender warned that Trojan:Win32/Azden.A!cl was found in
x86)\HamApps\JTAlert\plugins\JTAlertSettings.exe and deleted it.
Please confirm.
73,
Hans, DK1WB

Carlos Reboreda schrieb am 09.06.2020 10:18 (GMT +02:00):

Hi all,

 

My experience here is the same… when there are abt 100 Kb left to finish the download, the ESET (for the first time) cancels the download, because it has detected something dangerous on dnl.hamapps.com … I’m not saying that this is the real matter, I just describe what ESET is doing about this download. I’m user of this antivirus for more tan 15 years, every euro i pay every

year for it is worth it. I tried the download with Opera, Edge and Chrome, so I think it isn’t a matter of the web browser you use. Lets see if there any other members experimenting the same

problem or it happens to be a false detection.

 

73 to all!

 

Carlos R.

EA1DWI

 

Enviado desde Correo para Windows 10

 

De: chas cartmel
Enviado: martes, 9 de junio de 2020 9:50
Para: Support@hamapps.groups.io
Asunto: Re: [HamApps] JTAlert 2.16.7 is available

 

Jacques

08:48 BST – all OK here in the UK.
Have you tries a different browser? Occasionally this works for me if I have a ‘glitch’.

73 Charlie

G4EST

www.g4est.me.uk

 

 

 

From: Support@HamApps.groups.io [mailto:Support@HamApps.groups.io] On Behalf Of Jacques Corbu
Sent: 09 June 2020 07:09
To: Support@HamApps.groups.io
Subject: [HamApps] JTAlert 2.16.7 is available

 

HI Laurie

cannot access new version the website is given as non accessible when I hit download ?  I have never had this issue and it has all the exception requires in avast etc  but this come up 

any idea would be welcomed 

stay safe Jacques F1VEV

 

This email has been scanned by BullGuard antivirus protection.

For more info visit www.bullguard.com

 

 


locked Re: JTAlert 2.16.7 is available

Carlos Reboreda
 

Hi all,

 

My experience here is the same… when there are abt 100 Kb left to finish the download, the ESET (for the first time) cancels the download, because it has detected something dangerous on dnl.hamapps.com … I’m not saying that this is the real matter, I just describe what ESET is doing about this download. I’m user of this antivirus for more tan 15 years, every euro i pay every

year for it is worth it. I tried the download with Opera, Edge and Chrome, so I think it isn’t a matter of the web browser you use. Lets see if there any other members experimenting the same

problem or it happens to be a false detection.

 

73 to all!

 

Carlos R.

EA1DWI

 

Enviado desde Correo para Windows 10

 

De: chas cartmel
Enviado: martes, 9 de junio de 2020 9:50
Para: Support@hamapps.groups.io
Asunto: Re: [HamApps] JTAlert 2.16.7 is available

 

Jacques

08:48 BST – all OK here in the UK.
Have you tries a different browser? Occasionally this works for me if I have a ‘glitch’.

73 Charlie

G4EST

www.g4est.me.uk

 

 

 

From: Support@HamApps.groups.io [mailto:Support@HamApps.groups.io] On Behalf Of Jacques Corbu
Sent: 09 June 2020 07:09
To: Support@HamApps.groups.io
Subject: [HamApps] JTAlert 2.16.7 is available

 

HI Laurie

cannot access new version the website is given as non accessible when I hit download ?  I have never had this issue and it has all the exception requires in avast etc  but this come up 

any idea would be welcomed 

stay safe Jacques F1VEV

 

This email has been scanned by BullGuard antivirus protection.

For more info visit www.bullguard.com

 


locked Re: JTAlert 2.16.7 is available

chas cartmel
 

Jacques

08:48 BST – all OK here in the UK.
Have you tries a different browser? Occasionally this works for me if I have a ‘glitch’.


73 Charlie

G4EST

www.g4est.me.uk

 

 

 

From: Support@HamApps.groups.io [mailto:Support@HamApps.groups.io] On Behalf Of Jacques Corbu
Sent: 09 June 2020 07:09
To: Support@HamApps.groups.io
Subject: [HamApps] JTAlert 2.16.7 is available

 

HI Laurie

cannot access new version the website is given as non accessible when I hit download ?  I have never had this issue and it has all the exception requires in avast etc  but this come up 

any idea would be welcomed 

stay safe Jacques F1VEV


This email has been scanned by BullGuard antivirus protection.
For more info visit www.bullguard.com


locked JTAlert 2.16.7 is available. WSJT-X 2.2.x fix + new features. #NewRelease #Announcement

HamApps Support (VK3AMA)
 

The latest JTAlert version 2.16.7 is now available @ https://hamapps.com/JTAlert/
 

Please see the release notes below.

de Laurie VK3AMA

Release Notes:

2.16.7 (09-Jun-2020)

  *** Includes Callsign database file version 2020-06-08 (2020-Jun-08)

  New Features:

    - 4m Band Alerting: All the Wanted Alerts, Scan Log, QSO History & Bands
       Confirmed display now support the 4m band.

    - Multiple Grids per QSO Logs: Logs that support recording multiple grids
       (1,2 or 4) are now supported by the Scan Log & Rebuild operation for
       updating the internal "Wanted Grid" lists and the Worked B4 checks.
       Currently only DXKeeper and standard ADIF logs are supported.

    - WSJT-X decode highlighting: The grid in a decode is now only colored if
       a Wanted Grid Alert is generated using the Grid Alert colors.

  Changes:

    - WSJT-X decode highlighting: Only the "CQ Callsign" in a CQ decode is
       colored, previously the entire decode "CQ Callsign Grid" was colored.

    - WSJT-X decode highlighting: For non-CQ decodes, only the DX Callsign is
       Coloured, previously the exchange part of the decode (eg, report, grid,
       RR73, etc) was also colored.

  Fixes:

    - WSJT-X 2.2.x FT8: Random loss of some early first-pass FT8 decodes received
       at the 11 second point of the Rx period.



locked Re: needed grids not updating once needed one worked

Jim Cary
 

Thanks.
73, Jim


locked Re: needed grids not updating once needed one worked

Larry Banks
 

Hi Jim,
 
Same as DXCC or WAS, the scan is required.

73 -- Larry -- W1DYJ

 

From: Jim Cary
Sent: Monday, June 08, 2020 13:27
Subject: [HamApps] needed grids not updating once needed one worked
 
When I work a needed grid, the needed list is not being updated and the grid still shows as needed.  The only way I can get it to update is to do a complete log scan.  What am I doing wrong?

Jim
W2SM


locked needed grids not updating once needed one worked

Jim Cary
 

When I work a needed grid, the needed list is not being updated and the grid still shows as needed.  The only way I can get it to update is to do a complete log scan.  What am I doing wrong?

Jim
W2SM


locked Re: Using WSJT-X, JTAlert and MacLoggerDX together nicely

Jay
 

That was the work around.  I keep changing the entry in "Logging" for retransmission and the evidently only works on 127.0.0.1.  Never saw the WSJT-X/JTDX entry.

Thanks

jb  N4NQY


locked Re: JTAlert stops updating for about 2 minutes

Michael Black
 

What antivirus are you using?  

Mike W9MDB




On Monday, June 8, 2020, 10:26:38 AM CDT, John Singler <jes148@...> wrote:


I've been trying to solve this for a couple of months and run out of ideas. JTAlert runs fine for minutes to hours and then stops updating call signs. If I mouse over the form, I get an hourglass. The form shrinks a bit (but not the displayed call signs) and the top margin text gets pale. After about 90 seconds the top margin text gets dark again, usually with a Not Responding message,  and after about 2 minutes most or all the call signs decoded while the display is off get written. While all this is annoying, the thing that will eventually bite me is that if I log a QSO while JTAlert is stopped, when it comes back I  get a QSO not logged message - QSO and DX Call call signs don't match.
First thing I did was follow Mike Black's guidance and put the program and data directories for WSJT-X, JTAlert and HRD5 (my logger) on the Windows Defender exception list. JTAlert stops even it it has been minutes to hours since my last transmission and WSJT-X and CAT control are not impacted so I don't see how it can be RFI (but I did put an RFI suppression kit on anyway). . I've checked the CPU load with Performance Monitor and it is 12% to 25%. There was often a spike in HDD activity just before JTAlert stopped but not while it is stopped and that was usually WSJT-X writing a .wav file. WSJT-X doesn't do that any more and JTAlert still stops. I saw message 29770 about a potential fix but missed it the first time and now I get a page not found error for the beta.
I am using Windows 10, ver 1903, WSJT-X 2.2.0, and JTAlert 2.16.6
Any ideas? Thanks
John, KA5BJC


locked JTAlert stops updating for about 2 minutes

John Singler
 

I've been trying to solve this for a couple of months and run out of ideas. JTAlert runs fine for minutes to hours and then stops updating call signs. If I mouse over the form, I get an hourglass. The form shrinks a bit (but not the displayed call signs) and the top margin text gets pale. After about 90 seconds the top margin text gets dark again, usually with a Not Responding message,  and after about 2 minutes most or all the call signs decoded while the display is off get written. While all this is annoying, the thing that will eventually bite me is that if I log a QSO while JTAlert is stopped, when it comes back I  get a QSO not logged message - QSO and DX Call call signs don't match.
First thing I did was follow Mike Black's guidance and put the program and data directories for WSJT-X, JTAlert and HRD5 (my logger) on the Windows Defender exception list. JTAlert stops even it it has been minutes to hours since my last transmission and WSJT-X and CAT control are not impacted so I don't see how it can be RFI (but I did put an RFI suppression kit on anyway). . I've checked the CPU load with Performance Monitor and it is 12% to 25%. There was often a spike in HDD activity just before JTAlert stopped but not while it is stopped and that was usually WSJT-X writing a .wav file. WSJT-X doesn't do that any more and JTAlert still stops. I saw message 29770 about a potential fix but missed it the first time and now I get a page not found error for the beta.
I am using Windows 10, ver 1903, WSJT-X 2.2.0, and JTAlert 2.16.6
Any ideas? Thanks
John, KA5BJC


locked Wider window would be nice

Mark
 

JTAlert is Great, but I would like to have more information available horizontally.  I have JTAlert's display placed above the WSJT-X display and have room to expand JTAlert's information by four more display fields on each of the three existing rows.

Merk, K6FG


locked Re: Special callsigns

WB5JJJ - George
 

My solution is, and has always been right in front of my face. 

I just watch the WSJTx Band Activity window and let JTA do what it does the best, the voice announcements to get my attention for anything I might overlook, like a new DXCC.  1x1's and other special calls jump out at me all the time, even if they are color-coded as having been worked before for some previous special event. 

I spend most of my time watching the BA window as it's easier to scan with everything in a single row, whereas the JTA has things in a horizontal AND vertical plane per entry.  I can scan the BA window in half the time it takes me to scan the JTA grid.  I have B4 ignore turned on, CQ only unchecked and using the 8x3 display.  This setup still gets a bit overwhelming to decipher in less than 15s. 

Don't get me wrong, but the JTA announcements and grid display are a vital part of my operation.  And yes, I do scan it frequently, but as a backup to WSJTx which is a much faster visual scan for these older eyes and slower reaction times. 
--
73's
George - WB5JJJ


locked Re: Special callsigns

Tom Melvin
 

Morning

One issue, this would have to be under a UI - some users, shall we say, by their nature are nervous around computers, letting them loose with a text editor - I can imaging the traffic here. The file will as you point out will be OK for US users but as Laurie commented   'Any coded solution I develop is guaranteed to be incorrect for some users 5 minutes after a public release.

Just playing devil’s advocate here as 1x1 US calls don’t affect me in the slightest.

The saying 'Can of Worms' comes to mind.

Tom
--
73

Tom
GM8MJV (IO85)





On 8 Jun 2020, at 05:00, Michael Black via groups.io <mdblack98@...> wrote:

Come to think of it though, the grid alert could be very annoying for a lot of ops alerting every decode cycle on all the non-special calls.

The wanted callsign would alert you when they call, and then you'd leave it for working multiple bands, but then get a new alert every time it showed up again in the same band.

Neither is a robust solution.

Perhaps a special callsign file that gets referred to for the 1x1 pattern and has an expiration date of 15 days?

That file could then have foreign special calls added too of course.

Starter file

Mike

On Sunday, June 7, 2020, 10:32:20 PM CDT, Black Michael <mdblack98@...> wrote:


Actually there is a clearly defined answer in the U.S.


The grid alert solution should work as long as they provide a grid.

Mike




On Sunday, June 7, 2020, 05:17:19 PM CDT, HamApps Support (VK3AMA) <vk3ama.ham.apps@...> wrote:


On 8/06/2020 3:52 am, Michael Black via groups.io wrote:
There are 750 special event callsigns in U.S.  I haven't looked up foreign ones.

The point here to get JTAlert to recognize these as need-to-be-worked since they expire so quickly.

A regular expression detects them.

"[WKN][0-9][A-WYZ]"

And this to detect one with a suffix.
"[WKN][0-9][A-WYZ]/"

Mike W9MDB

Any coded solution has to be flexible enough to take into account the fundamental question "what is a special event Callsign? There is no clearly defined answer, is is subject to the whims of a user. A 1x1 callsign is may be a special event call to a US based Ham, but not so for many others. Here in VK 1x1 callsigns are not permitted or available . What is a special event callsign is no different from what is a DX callsign, there is no right or wrong answer.

Any coded solution I develop is guaranteed to be incorrect for some users 5 minutes after a public release.

My preferred option is to allow the user to decide what is a special event callsign and adjust their alerting as need.

Using the current JTAlert framework there are a number of ways to tackle the "avoid reporting B4 for special event Callsigns".
  • With the 1x1 callsigns, changing hands every week or so, they will likely be operating from different locations, so setting the B4 alert to consider the on-air Grid will allow for Alerting when the Callsign is reassigned and they start CQing from a new Grid. This also works for roving stations that may operated from a number of Grids iover a short period of time (hours, days, weeks, etc).

  • Add the special event Callsign(s) as a Wanted Callsign and enable the "ignore B4" option for that Alert. Either a list of callsigns can be imported for the Wanted Callsign Alert or add the Callsigns as needed via the right-click context menu of the alerted Callsign.

de Laurie VK3AMA