Date   

locked Re: JTAlert Grids not matching LOTW VUCC

Paul W5PF
 

Dan,

Are all of your LoTW confirmations FT8?

Paul W5PF

On 5/27/2021 9:40 AM, Dan R wrote:
Didn't see attachments.Trying again.
--
Dan KG0AQ


locked Re: JTAlert Grids not matching LOTW VUCC

Tom Melvin
 

Dan

Suggest you do a manual check to find a couple that have not come through and then see what they have in common - maybe you have a date restriction in JTA, different mode e.g. ssb/cw where jta is looking at digital.

Just hitting re-build time after time will not make a difference, little bit of investigation at your end will be needed.

Tom
GM8MJV


On 27 May 2021, at 15:40, Dan R <kg0aq1@...> wrote:

Didn't see attachments.Trying again.
--
Dan KG0AQ


locked Re: JTAlert Grids not matching LOTW VUCC

Dan R
 

Didn't see attachments.Trying again.
--
Dan KG0AQ


locked Re: JTAlert Grids not matching LOTW VUCC

Dan R
 
Edited

See attachments for both LOTW VUCC and JTAlert 6 Meter Grids. I have rebuilt the JTAlert Grid database multiple times and updated DXKeeper with LOTW multiple times. I could do a manual comparison but I still would not change Grids worked in JTAlert.
--
Dan KG0AQ


locked Re: reverting to previous version

Jim Denneny
 

My issue with new JTAlert version went away when I updated NET to 5.0.6.  NET website indicates issues with some apps using NET 5.


locked Re: Single/double click within callsigns window not working

Michael Black
 

What all software are you running and is anything else listening on the WSJT-X port?

Mike W9MDB




On Thursday, May 27, 2021, 05:16:17 AM CDT, BOB K5HX via groups.io <k5hx@...> wrote:


Laurie,

I have tried both the single click and double click options regarding the Wsjt-x reply and noticed no difference.  Basically,  I keep clicking in the callsigns window and eventually one of the clicks is processed by WSJT-X.  The click detection success is seemingly random.  Sometimes it works on the first click (rare) and at other times it may take multiple decode cycles before a click on a callisign is detected.

de Bob K5HX


locked Re: Single/double click within callsigns window not working

BOB K5HX
 

Laurie,

I have tried both the single click and double click options regarding the Wsjt-x reply and noticed no difference.  Basically,  I keep clicking in the callsigns window and eventually one of the clicks is processed by WSJT-X.  The click detection success is seemingly random.  Sometimes it works on the first click (rare) and at other times it may take multiple decode cycles before a click on a callisign is detected.

de Bob K5HX


locked Re: Default bug ?

Paul F6EXV
 

That is what I said, it marks the 'LoTW received" field (name of the field) as "requested" (value of the field).
It is supposed to act on the SENT field, but it acts on the received field. AFAIAC, this is a bug...
73
Paul

Le 26/05/2021 à 22:22, Dave Garber a écrit :

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: reverting to previous version

HamApps Support (VK3AMA)
 

On 27/05/2021 3:29 pm, AOL/ CompuServe Mail via groups.io wrote:
DITTO   This new version is broken. 
 
Gerald Muller K9GEM


JTAlert 2.50.1 is not broken! What makes you think it is broken? What is not working for you?

There are currently close to 10,000 JTAlert users of JTAlert 2.50.0 & 2.50.1 who have enabled spotting to HamSpots, not bad for a broken program IMO.

de Laurie VK3AMA


locked Re: reverting to previous version

HamApps Support (VK3AMA)
 

On 27/05/2021 3:06 pm, Tory Wiedenkeller wrote:

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.


There is nothing hard about setting up the new version, it utilities all your existing JTAlert settings. The only additional setup (one time) required is the install of the Microsoft .NET 5 Desktop Runtime.

Typically people having problems with the new version is when they don't take care to install the correct 32bit or 64bit version of the runtime and the matching JTAlert 32bit or 64bit installer.

I can't find any previous messages from you regarding a problem with setup. The only other message, posted today, is regarding the lack of entries in the Decodes window. That has been answered. Did it not work for you.

Old versions can be found listed at the bottom of the webpage from where you downloaded JTAlert.

Good luck.

de Laurie VK3AMA


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

3461 - 3480 of 38435