Date   

locked reverting to previous version

Tory Wiedenkeller
 

How can I download a copy of the previous version of JT-Alert?

No offense, but I really hate the new version. The previous version was super easy to set up and use. 

The new version is giving me nothing but a headache. I've been trying to get it to work for two days and still can't

seem to get it to work the way the previous version did.


locked Re: JTAlert Grids not matching LOTW VUCC

HamApps Support (VK3AMA)
 

On 27/05/2021 2:49 pm, Dan R wrote:
Should I possibly select the "Enable Standard ADIF File Logging" tab in JTAlert? Would that be used for importing instead of the DXKeeper .mdb file?
--
Dan KG0AQ

NO, don't do that. I wont make any difference.

JTAlert reading the DXKeeper .mdb file is what is happening when the Rebuild Alert Database operation is performed.

Since you're using DXKeeper, what does its VUCC report show.

de Laurie VK3AMA


locked Re: V2.50.1 Logging Start time is the End time of last QSO

HamApps Support (VK3AMA)
 

On 26/05/2021 2:37 am, ed.n5dg@... wrote:
Doing a search for (logging start time End Time) I get 2014 2015 results . I'm using WSJT-X , Jtalerts V2.50.1 and AClog ... When I click on a call I'd like to work in JTalerts and after sending RR73 the logging window pops up but the start time is the End time of last QSO logged ! This can very from 1 minute to Hours . I've found what I have to do to set the Start time is double click the call in WSJT-X . I know I've missed a setting somewhere ?  The 2 J-pegs below, The left is clicking JTAlerts and right is clicking WSJT . Please not the Start time ..Thanks Ed N5DG
  
_._,_._,_

JTAlert has no control over the data presented in the WSJT-X Log QSO window.
It has no ability to automatically show the window, that is coming from WSJT-X.
Whatever data is shown in the window, correct or not, JTAlert will log.
You will need to take this up with the WSJT-X folks if you believe there is a defect/bug.

de Laurie VK3AMA


locked Re: JTAlert Grids not matching LOTW VUCC

Michael Black
 

That won't make any difference.

If the QSO you log has a different grid than what shows on LOTW (Note: LOTW does NOT use the grid you log) than your count may not match.

A manual comparison is about your only option that I know of.

Some mobile operators don't upload their grids correctly.

Mike W9MDB




On Wednesday, May 26, 2021, 11:49:24 PM CDT, Dan R <kg0aq1@...> wrote:


I forgot to mention that I am using the DXLabs Suite with database uploads and downloads to and from LOTW using DXKeeper. The .mdb file importing to JTAlert has 460 6 meter Grids worked. 401 are showing in JTAlert. I have not done a manual comparison.

Should I possibly select the "Enable Standard ADIF File Logging" tab in JTAlert? Would that be used for importing instead of the DXKeeper .mdb file?
--
Dan KG0AQ


locked Re: JTAlert Grids not matching LOTW VUCC

HamApps Support (VK3AMA)
 

On 27/05/2021 1:08 pm, Dan R wrote:
I show 460 grids in LOTW, 50mhz VUCC. After a rebuild of the grid data base in JTAlert I show 401? Any ideas of the discrepancy?  TIA!!    Wonderful program!!
--
Dan KG0AQ

Discrepancies like this are typically caused by the Log file that JTAlert is reading not having been updated with the LoTW confirmations.
What logger are you using with JTAlert?
Have you done a recent sync (from your logger) with LoTW to ensure the log has all recent confirmations?
Does your logger provide a report on your VUCC status? If so, what does it report, does it agree with LoTW or JTAlert or neither?

de Laurie VK3AMA


locked Re: window not showing decoded callsigns

HamApps Support (VK3AMA)
 

On 27/05/2021 1:40 pm, Tory Wiedenkeller wrote:

I'm not sure what setting I messed up. I had the decode window showing the incoming callsigns, but now it's not showing them.

What do I need to change so this window shows decoded callsigns? Thanks


Open the Settings of the Main JTAlert window and navigate to the "Window -> Decodes" section and tick the enable box.

de Laurie VK3AMA


locked Re: JTAlert Grids not matching LOTW VUCC

Dan R
 

I forgot to mention that I am using the DXLabs Suite with database uploads and downloads to and from LOTW using DXKeeper. The .mdb file importing to JTAlert has 460 6 meter Grids worked. 401 are showing in JTAlert. I have not done a manual comparison.

Should I possibly select the "Enable Standard ADIF File Logging" tab in JTAlert? Would that be used for importing instead of the DXKeeper .mdb file?
--
Dan KG0AQ


locked Re: JTAlert Grids not matching LOTW VUCC

Michael Black
 

That probably means the LOTW grid does not match the grid in your log.

Lots of possible reasons....here's a few I can think of...

#1 User didn't know their correct grid
#2 Mobile/Portable operations (not really sure how LOTW handles that).
#3 User didn't send grid (or you didn't log grid for whatever reason).

I don't know of an easy way to find the mismatches.   

I've got an ADIFCompare program I could probably modify to compare grids too.
Or you can just start comparing the grid list on LOTW with the one in JTAlert to find out the differences.

Mike W9MDB





On Wednesday, May 26, 2021, 10:49:53 PM CDT, Dan R <kg0aq1@...> wrote:


I show 460 grids in LOTW, 50mhz VUCC. After a rebuild of the grid data base in JTAlert I show 401? Any ideas of the discrepancy?  TIA!!    Wonderful program!!
--
Dan KG0AQ


locked JTAlert Grids not matching LOTW VUCC

Dan R
 

I show 460 grids in LOTW, 50mhz VUCC. After a rebuild of the grid data base in JTAlert I show 401? Any ideas of the discrepancy?  TIA!!    Wonderful program!!
--
Dan KG0AQ


locked window not showing decoded callsigns

Tory Wiedenkeller
 

I'm not sure what setting I messed up. I had the decode window showing the incoming callsigns, but now it's not showing them.

What do I need to change so this window shows decoded callsigns? Thanks


locked Re: JTAlert 2.50.1 does not receive from WSJT-X - Callsigns, Activity and Band heat windows don't open

Frode Igland
 

Good.
At my end it did not work even if I had the most recent NET version installed. Now JTAlert works as it should with the very same NET version, and I have no idea why it suddenly chose to work.

73, Frode LA6VQ


locked Re: Default bug ?

Dave Garber
 

It actually marks it as 'requested' not received, from jtalert, but I don't think it is a bug.   There are a few softwares that are sent to lotw ( Gridtracker) so you are basically telling log4om that this job is done.    not the way I like doing it, but easy to uncheck in jtalert , as already suggested.


Dave Garber
VE3WEJ / VE3IE


On Wed, May 26, 2021 at 8:35 AM Paul F6EXV <f6exv@...> wrote:
Hi Ron
It is still a bug, IMHO.
The JTAlert setting is about LoTW QSL sent, but it modifies the LoTW QSL received field in Log4OM.
It should not affect that.
73
Paul F6EXV

Le 26/05/2021 à 14:19, Ron W3RJW via groups.io a écrit :
Uncheck "Mark ... requested"
--
73
Ron, W3RJW

FTdx-5000, Timewave Navigator, WSJT-x 2.4.0, JTAlert 2.50.1 beta, HRD Deluxe v6.7.0.357
FTdx-3000, SignaLink USB


Garanti sans virus. www.avast.com


locked Re: Alerts window does'nt start.

Jim Denneny
 

Jeff - try NET 5.0.6 upgrade.  It solved my JTAlert  2.50.1 start problem. NET reports some issues with 5.0 with some applications.

73, Jim K7EG


locked Re: Default bug ?

Paul F6EXV
 

Hi Ron
It is still a bug, IMHO.
The JTAlert setting is about LoTW QSL sent, but it modifies the LoTW QSL received field in Log4OM.
It should not affect that.
73
Paul F6EXV

Le 26/05/2021 à 14:19, Ron W3RJW via groups.io a écrit :
Uncheck "Mark ... requested"
--
73
Ron, W3RJW

FTdx-5000, Timewave Navigator, WSJT-x 2.4.0, JTAlert 2.50.1 beta, HRD Deluxe v6.7.0.357
FTdx-3000, SignaLink USB


Garanti sans virus. www.avast.com


locked Re: Default bug ?

Ron W3RJW
 

Uncheck "Mark ... requested"
--
73
Ron, W3RJW

FTdx-5000, Timewave Navigator, WSJT-x 2.4.0, JTAlert 2.50.1 beta, HRD Deluxe v6.7.0.357
FTdx-3000, SignaLink USB


locked Re: Default bug ?

Paul F6EXV
 

Attachment here, sorry

Le 26/05/2021 à 04:46, Paul F6EXV a écrit :
Hello all
Using JTAlert v2.50.1 and Log4OM version 2.13.0.0
I have configured L4OM default LoTW snet to "requested", and LoTW received to "no".
I have configured JTAlert logging as shown on the attachment.
BUT when I log a QSO, the LoTW received in L4OM shows as requested, while it should show No... unless I missed something !

73
Paul F6EXV
--
L'absence de virus dans ce courrier électronique a été vérifiée par le logiciel antivirus Avast.
https://www.avast.com/antivirus


locked Default bug ?

Paul F6EXV
 

Hello all
Using JTAlert v2.50.1 and Log4OM version 2.13.0.0
I have configured L4OM default LoTW snet to "requested", and LoTW received to "no".
I have configured JTAlert logging as shown on the attachment.
BUT when I log a QSO, the LoTW received in L4OM shows as requested, while it should show No... unless I missed something !

73
Paul F6EXV

--
L'absence de virus dans ce courrier électronique a été vérifiée par le logiciel antivirus Avast.
https://www.avast.com/antivirus


locked V2.50.1 Logging Start time is the End time of last QSO

Ed Stallman
 

Doing a search for (logging start time End Time) I get 2014 2015 results . I'm using WSJT-X , Jtalerts V2.50.1 and AClog ... When I click on a call I'd like to work in JTalerts and after sending RR73 the logging window pops up but the start time is the End time of last QSO logged ! This can very from 1 minute to Hours . I've found what I have to do to set the Start time is double click the call in WSJT-X . I know I've missed a setting somewhere ?  The 2 J-pegs below, The left is clicking JTAlerts and right is clicking WSJT . Please not the Start time ..Thanks Ed N5DG
  


locked Re: ACL and JT alert

Dave Garber
 

make sure the api is on , in aclog


Dave Garber
VE3WEJ / VE3IE


On Tue, May 25, 2021 at 12:02 AM GMuller885 via groups.io <GMuller885=aol.com@groups.io> wrote:
I upgraded tp Armature Contact log 7.0 and JT alert 5.0 and now . Now ACL will not log the contacts to ACL from WSJT-X.  Please provide a step by step process to make this happen. I am not very computer literate. this used to work with the old version.
 


locked Re: Alerts window does'nt start.

HamApps Support (VK3AMA)
 

On 25/05/2021 10:59 am, jeff29754 M1BCM wrote:
Hi Laurie, what I call the "alerts window" is wthe window that shows all the calls which I can click on etc. I upgraded from 2.5.0. which was working fine up until the the.net and 2.5.1. installations.

Thanks for replying.

de Jeff M1BCM
Jeff,

There was no requirement for a .NET install with 2.50.1, the .NET install required for the 2.50.0 install is all that was needed. What prompted you to install a new NET 5 runtime?

Are you able to open the JTAlert Help->About window?

Are you able to open any of the new 2.50.x windows? See the "Yellow star" entries under the View menu of the main JTAlert window.
   

If none of these windows will open, that suggests a problem with the JTAlertV2.Manager process, likely it is not running or is continually stopping and starting. What does TaskManager show for this process?

The Manager process is dependent on the .NET 5 runtime. When you installed/upgraded the runtime for your 2.50.1 install did your install the correct architecture version matching that of JTAlert? The runtime needs to match JTAlert, either x86 or x64. If you're using Windows 64 bit, I suggests using the x64 version of the runtime and JTAlert. While the 32 bit (x86) runtime and JTAlert will work under 64bit Windows, IMO, it is best to keep it x64 across the board, Windows, NET runtime and JTAlert all being x64.

de Laurie VK3AMA



2261 - 2280 of 37225