Date   

locked Re: Erroneous error message !

Paul F6EXV
 

Hi Mike
Thank you for replying so quickly.
You are faster than your shadow !

Actually, the E is where I backup the log, so now I realize both really must the same path.
Once that corrected, of course everything works fine !
MANY thanks ! keep up the good work
73 and stay safe
Paul F6EXV

Le 17/11/2020 à 20:07, Michael Black via groups.io a écrit :
Those are two completely different paths.

E:\F4KMA.Sqlite

and
C:\Users\Utilisateur\Desktop\F4KMA\F4KMA.Sqlite

Change one of them to whichever file is best...which I expect is the one on the C: drive as that's the one Log4OM is using.

Mike W9MDB




On Tuesday, November 17, 2020, 01:04:06 PM CST, Paul F6EXV <f6exv@...> wrote:


Here they are

Le 17/11/2020 à 16:08, Michael Black via groups.io a écrit :
Send a screen shot of your JTAlert Log4OM settings and the lower right corner of Log4OM.

Mike




On Tuesday, November 17, 2020, 08:39:38 AM CST, Paul F6EXV <f6exv@...> wrote:


Hi Mike
Thanks for the reply.
Yes, I do want Log4OM to log my JTDX QSOs, and it does. But even thouygh the QSO is logged, I get an error message saying it was not...
You mean JTAlert pointing to the right file... Actually, it does, the test is passed without any issue.
I did turn off the Last QSO API, no change = I still get the wrong error message. So the last QSO API is not the source of the problem...
73
Paul F6EXV

Le 17/11/2020 à 14:09, Michael Black via groups.io a écrit :
I take it you just want Log4OM logging, right?

Turn off the "Last QSO API".  You don't need it.

It sounds like you don't have the Log4OM SQLite Log pointing to the correct file.  Should be the same path you see in the lower right corner of Log4OM.
Mike W9MDB









On Tuesday, November 17, 2020, 02:41:09 AM CST, Paul F6EXV <f6exv@...> wrote:


Hi all
No reply to this... Anyone with any idea ?
73
Paul F6EXV

Le 15/11/2020 à 23:13, Paul F6EXV a écrit :
> Hi all
> Strange behaviour...
> Using Log4OM latest version, JTDX v2.2.0-rc152 and JTAlert 2.16.15 on
> Windows 10.
> I am getting the attached error message when logging a QSO onto Log4OM.
> But the QSO is indeed logged...
>
> I have :
> Enable transmission of last QSO ticked, on port 2333 in the "Last QSO
> API" setup
> Enable Standard ADIF file logging unticked in the Standard ADIF file
> setup
> Enable Log4OM V2 logging tocked, UDP connections on IP 127.0.0.1 on
> ADIF message port #2236
> When I ask JTAlert to show Log Fields, the screen expands, but remains
> grey.
> The headline says "JTAlert 2.16.15 F6EXV {80m,FT8,LogV2,#1}
>
> If I untick "Enable Log4OM Logging", then I do not have access to
> "View log fields", and the expanded grey screen disappears, and the
> header will now show "NO LOG".
>  And the QSO IS logged onto Log4OM, without any success message....
>
> 1/ How can I get access to the log fields below the display lines ?
> 2/ The "NO LOG" indication makes reference to which log ?
> 3/ How do I get a logging success message ?
>
> Thanks + 73
> Paul F6EXV
>


--
L'absence de virus dans ce courrier électronique a été vérifiée par le logiciel antivirus Avast.







Garanti sans virus. www.avast.com



locked Re: Erroneous error message !

Michael Black
 

Those are two completely different paths.

E:\F4KMA.Sqlite

and
C:\Users\Utilisateur\Desktop\F4KMA\F4KMA.Sqlite

Change one of them to whichever file is best...which I expect is the one on the C: drive as that's the one Log4OM is using.

Mike W9MDB




On Tuesday, November 17, 2020, 01:04:06 PM CST, Paul F6EXV <f6exv@...> wrote:


Here they are

Le 17/11/2020 à 16:08, Michael Black via groups.io a écrit :
Send a screen shot of your JTAlert Log4OM settings and the lower right corner of Log4OM.

Mike




On Tuesday, November 17, 2020, 08:39:38 AM CST, Paul F6EXV <f6exv@...> wrote:


Hi Mike
Thanks for the reply.
Yes, I do want Log4OM to log my JTDX QSOs, and it does. But even thouygh the QSO is logged, I get an error message saying it was not...
You mean JTAlert pointing to the right file... Actually, it does, the test is passed without any issue.
I did turn off the Last QSO API, no change = I still get the wrong error message. So the last QSO API is not the source of the problem...
73
Paul F6EXV

Le 17/11/2020 à 14:09, Michael Black via groups.io a écrit :
I take it you just want Log4OM logging, right?

Turn off the "Last QSO API".  You don't need it.

It sounds like you don't have the Log4OM SQLite Log pointing to the correct file.  Should be the same path you see in the lower right corner of Log4OM.
Mike W9MDB









On Tuesday, November 17, 2020, 02:41:09 AM CST, Paul F6EXV <f6exv@...> wrote:


Hi all
No reply to this... Anyone with any idea ?
73
Paul F6EXV

Le 15/11/2020 à 23:13, Paul F6EXV a écrit :
> Hi all
> Strange behaviour...
> Using Log4OM latest version, JTDX v2.2.0-rc152 and JTAlert 2.16.15 on
> Windows 10.
> I am getting the attached error message when logging a QSO onto Log4OM.
> But the QSO is indeed logged...
>
> I have :
> Enable transmission of last QSO ticked, on port 2333 in the "Last QSO
> API" setup
> Enable Standard ADIF file logging unticked in the Standard ADIF file
> setup
> Enable Log4OM V2 logging tocked, UDP connections on IP 127.0.0.1 on
> ADIF message port #2236
> When I ask JTAlert to show Log Fields, the screen expands, but remains
> grey.
> The headline says "JTAlert 2.16.15 F6EXV {80m,FT8,LogV2,#1}
>
> If I untick "Enable Log4OM Logging", then I do not have access to
> "View log fields", and the expanded grey screen disappears, and the
> header will now show "NO LOG".
>  And the QSO IS logged onto Log4OM, without any success message....
>
> 1/ How can I get access to the log fields below the display lines ?
> 2/ The "NO LOG" indication makes reference to which log ?
> 3/ How do I get a logging success message ?
>
> Thanks + 73
> Paul F6EXV
>


--
L'absence de virus dans ce courrier électronique a été vérifiée par le logiciel antivirus Avast.







Garanti sans virus. www.avast.com


locked Re: Erroneous error message !

Paul F6EXV
 

Here they are

Le 17/11/2020 à 16:08, Michael Black via groups.io a écrit :
Send a screen shot of your JTAlert Log4OM settings and the lower right corner of Log4OM.

Mike




On Tuesday, November 17, 2020, 08:39:38 AM CST, Paul F6EXV <f6exv@...> wrote:


Hi Mike
Thanks for the reply.
Yes, I do want Log4OM to log my JTDX QSOs, and it does. But even thouygh the QSO is logged, I get an error message saying it was not...
You mean JTAlert pointing to the right file... Actually, it does, the test is passed without any issue.
I did turn off the Last QSO API, no change = I still get the wrong error message. So the last QSO API is not the source of the problem...
73
Paul F6EXV

Le 17/11/2020 à 14:09, Michael Black via groups.io a écrit :
I take it you just want Log4OM logging, right?

Turn off the "Last QSO API".  You don't need it.

It sounds like you don't have the Log4OM SQLite Log pointing to the correct file.  Should be the same path you see in the lower right corner of Log4OM.
Mike W9MDB









On Tuesday, November 17, 2020, 02:41:09 AM CST, Paul F6EXV <f6exv@...> wrote:


Hi all
No reply to this... Anyone with any idea ?
73
Paul F6EXV

Le 15/11/2020 à 23:13, Paul F6EXV a écrit :
> Hi all
> Strange behaviour...
> Using Log4OM latest version, JTDX v2.2.0-rc152 and JTAlert 2.16.15 on
> Windows 10.
> I am getting the attached error message when logging a QSO onto Log4OM.
> But the QSO is indeed logged...
>
> I have :
> Enable transmission of last QSO ticked, on port 2333 in the "Last QSO
> API" setup
> Enable Standard ADIF file logging unticked in the Standard ADIF file
> setup
> Enable Log4OM V2 logging tocked, UDP connections on IP 127.0.0.1 on
> ADIF message port #2236
> When I ask JTAlert to show Log Fields, the screen expands, but remains
> grey.
> The headline says "JTAlert 2.16.15 F6EXV {80m,FT8,LogV2,#1}
>
> If I untick "Enable Log4OM Logging", then I do not have access to
> "View log fields", and the expanded grey screen disappears, and the
> header will now show "NO LOG".
>  And the QSO IS logged onto Log4OM, without any success message....
>
> 1/ How can I get access to the log fields below the display lines ?
> 2/ The "NO LOG" indication makes reference to which log ?
> 3/ How do I get a logging success message ?
>
> Thanks + 73
> Paul F6EXV
>


--
L'absence de virus dans ce courrier électronique a été vérifiée par le logiciel antivirus Avast.







Garanti sans virus. www.avast.com


locked Re: ADIF file will not ..

Michael Black
 

I just created an  ADIF file from JTAlert and it uploaded with TQSL just fine and registered the QSO OK.

So if you're having problems maybe show us the ADIF file?

Mike W9MDB




On Tuesday, November 17, 2020, 10:45:47 AM CST, Rick Wyrwas <rwyrwas48@...> wrote:


ADIF file will not decode nor upload to Tqsl

 

73

WA9JBQ

 

Sent from Mail for Windows 10

 


locked Re: LOTW data is often wrong

Ross Lambert
 

LOTW is only as good as the info it's given.  Often the times for the QSO that each operator, or their logging software,  provides will be different, especially if they are using FT-8 or other digital modes where the "completion" times may be very different  The times  may be minutes apart. 

Ross
W2TT


On Tue, Nov 17, 2020 at 12:31 PM Michael Black via groups.io <mdblack98=yahoo.com@groups.io> wrote:
You're going to have to give some examples of what's "wrong".

LOTW doesn't use many fields.

Mike W9MDB



On Tuesday, November 17, 2020, 11:17:39 AM CST, Torsten - DL9GTB <torsten-ernst@...> wrote:


Hi,

unfortunately for a long time I have had to find out again and again that the LOTW data is often incorrect or not up-to-date. How can I improve this?

73 de Torsten - DL9GTB


locked Re: ADIF file will not ..

Michael Black
 

Actually is a question for JTAlert if it's the JTAlert ADIF file having problems.

Mike W9MDB


On Tuesday, November 17, 2020, 11:35:18 AM CST, neil_zampella <neilz@...> wrote:


That's a question for the LoTW group, has nothing to do with JT-Alert.

Neil, KN3ILZ


locked Re: ADIF file will not ..

neil_zampella
 

That's a question for the LoTW group, has nothing to do with JT-Alert.

Neil, KN3ILZ


locked Re: LOTW data is often wrong

Michael Black
 

You're going to have to give some examples of what's "wrong".

LOTW doesn't use many fields.

Mike W9MDB



On Tuesday, November 17, 2020, 11:17:39 AM CST, Torsten - DL9GTB <torsten-ernst@...> wrote:


Hi,

unfortunately for a long time I have had to find out again and again that the LOTW data is often incorrect or not up-to-date. How can I improve this?

73 de Torsten - DL9GTB


locked Re: Text message window

Guy G4DWV 4X1LT
 

Hi laurie,
That option is greyed out when the "Receive text Messages from other JTAlert users" is not selected, as indeed are all the options. I had assumed that that meant all the options were set to the state as if the box were unticked. I do not recall ever having to enable an item to un-grey out an option so I could change it. OTOH, my chemo may be pickling my brain.
--
73 de Guy G4DWV 4X1LT


locked LOTW data is often wrong

Torsten - DL9GTB
 

Hi,

unfortunately for a long time I have had to find out again and again that the LOTW data is often incorrect or not up-to-date. How can I improve this?

73 de Torsten - DL9GTB


locked Re: unsuccessful contacts with 7q7ru

Guy G4DWV 4X1LT
 

JTDX does not use the WSJT-X decoders, though the ones in the program are based on the originals. Theirs are much better in that they get more decodes than the original program. You can even download their audio samples and prove it for yourself if you do not believe the devs.
I only have WSJT-X installed for testing purposes and do not use it for QSOs.
--
73 de Guy G4DWV 4X1LT


locked Re: ADIF file will not ..

Tom Melvin
 

Rick

You will need to provide a little more detail.

ADIF files are pure text - you can open them with Notepad or any text editor - there is nothing to ‘decode’

There is no reason that tqsl will not process a proper adif file aimed at lotw.

It make me think you are looking at something different.

What is the location / name of the adif file you are trying to do something with.

Do you get any error messages?

Tom
GM8MJV

On 17 Nov 2020, at 14:50, Rick Wyrwas <rwyrwas48@...> wrote:

ADIF file will not decode nor upload to Tqsl
 
73
WA9JBQ
 
Sent from Mail for Windows 10
 


locked ADIF file will not ..

Rick Wyrwas
 

ADIF file will not decode nor upload to Tqsl

 

73

WA9JBQ

 

Sent from Mail for Windows 10

 


locked Re: States-Wanted Boxes Auto-Untick?

Patrick Hung
 

Thanks for the heads-up, Jim, I'll de-selecting eQSL.
--
Patrick - W2TAR


locked Re: New install of JTAlert keeps crashing saying "invalid callsign"

Ron W3RJW
 

On Tue, Nov 17, 2020 at 05:43 AM, <steve@...> wrote:
a fresh and totally updated windows install.
There you go ....
 
--
73
Ron, W3RJW


locked Re: LoTW User updates

Ron W3RJW
 

On Tue, Nov 17, 2020 at 06:38 AM, David Gould wrote:
The Help file says the file come from ARRL, but does not say how it gets into JTAlert.  Do I have to do anything to get/apply the latest version?
Dave,

One has nothing to do with the other. 

Both programs independently require periodic update of the lOTW users list.  Every version update of JTA includes the latest list or you can manually uodate as described in the other post.  
WSJT-X has a separate update in the 'settings', 'colors' tab, which you seem to have found.
 
--
73
Ron, W3RJW


locked Re: Erroneous error message !

Michael Black
 

Send a screen shot of your JTAlert Log4OM settings and the lower right corner of Log4OM.

Mike




On Tuesday, November 17, 2020, 08:39:38 AM CST, Paul F6EXV <f6exv@...> wrote:


Hi Mike
Thanks for the reply.
Yes, I do want Log4OM to log my JTDX QSOs, and it does. But even thouygh the QSO is logged, I get an error message saying it was not...
You mean JTAlert pointing to the right file... Actually, it does, the test is passed without any issue.
I did turn off the Last QSO API, no change = I still get the wrong error message. So the last QSO API is not the source of the problem...
73
Paul F6EXV

Le 17/11/2020 à 14:09, Michael Black via groups.io a écrit :
I take it you just want Log4OM logging, right?

Turn off the "Last QSO API".  You don't need it.

It sounds like you don't have the Log4OM SQLite Log pointing to the correct file.  Should be the same path you see in the lower right corner of Log4OM.
Mike W9MDB









On Tuesday, November 17, 2020, 02:41:09 AM CST, Paul F6EXV <f6exv@...> wrote:


Hi all
No reply to this... Anyone with any idea ?
73
Paul F6EXV

Le 15/11/2020 à 23:13, Paul F6EXV a écrit :
> Hi all
> Strange behaviour...
> Using Log4OM latest version, JTDX v2.2.0-rc152 and JTAlert 2.16.15 on
> Windows 10.
> I am getting the attached error message when logging a QSO onto Log4OM.
> But the QSO is indeed logged...
>
> I have :
> Enable transmission of last QSO ticked, on port 2333 in the "Last QSO
> API" setup
> Enable Standard ADIF file logging unticked in the Standard ADIF file
> setup
> Enable Log4OM V2 logging tocked, UDP connections on IP 127.0.0.1 on
> ADIF message port #2236
> When I ask JTAlert to show Log Fields, the screen expands, but remains
> grey.
> The headline says "JTAlert 2.16.15 F6EXV {80m,FT8,LogV2,#1}
>
> If I untick "Enable Log4OM Logging", then I do not have access to
> "View log fields", and the expanded grey screen disappears, and the
> header will now show "NO LOG".
>  And the QSO IS logged onto Log4OM, without any success message....
>
> 1/ How can I get access to the log fields below the display lines ?
> 2/ The "NO LOG" indication makes reference to which log ?
> 3/ How do I get a logging success message ?
>
> Thanks + 73
> Paul F6EXV
>


--
L'absence de virus dans ce courrier électronique a été vérifiée par le logiciel antivirus Avast.







Garanti sans virus. www.avast.com


locked Re: Erroneous error message !

Paul F6EXV
 

Hi Mike
Thanks for the reply.
Yes, I do want Log4OM to log my JTDX QSOs, and it does. But even thouygh the QSO is logged, I get an error message saying it was not...
You mean JTAlert pointing to the right file... Actually, it does, the test is passed without any issue.
I did turn off the Last QSO API, no change = I still get the wrong error message. So the last QSO API is not the source of the problem...
73
Paul F6EXV

Le 17/11/2020 à 14:09, Michael Black via groups.io a écrit :
I take it you just want Log4OM logging, right?

Turn off the "Last QSO API".  You don't need it.

It sounds like you don't have the Log4OM SQLite Log pointing to the correct file.  Should be the same path you see in the lower right corner of Log4OM.
Mike W9MDB









On Tuesday, November 17, 2020, 02:41:09 AM CST, Paul F6EXV <f6exv@...> wrote:


Hi all
No reply to this... Anyone with any idea ?
73
Paul F6EXV

Le 15/11/2020 à 23:13, Paul F6EXV a écrit :
> Hi all
> Strange behaviour...
> Using Log4OM latest version, JTDX v2.2.0-rc152 and JTAlert 2.16.15 on
> Windows 10.
> I am getting the attached error message when logging a QSO onto Log4OM.
> But the QSO is indeed logged...
>
> I have :
> Enable transmission of last QSO ticked, on port 2333 in the "Last QSO
> API" setup
> Enable Standard ADIF file logging unticked in the Standard ADIF file
> setup
> Enable Log4OM V2 logging tocked, UDP connections on IP 127.0.0.1 on
> ADIF message port #2236
> When I ask JTAlert to show Log Fields, the screen expands, but remains
> grey.
> The headline says "JTAlert 2.16.15 F6EXV {80m,FT8,LogV2,#1}
>
> If I untick "Enable Log4OM Logging", then I do not have access to
> "View log fields", and the expanded grey screen disappears, and the
> header will now show "NO LOG".
>  And the QSO IS logged onto Log4OM, without any success message....
>
> 1/ How can I get access to the log fields below the display lines ?
> 2/ The "NO LOG" indication makes reference to which log ?
> 3/ How do I get a logging success message ?
>
> Thanks + 73
> Paul F6EXV
>


--
L'absence de virus dans ce courrier électronique a été vérifiée par le logiciel antivirus Avast.







Garanti sans virus. www.avast.com


locked Re: Callsigns get cleared before I can see them

John Peck
 

And.... thanks for all the new features and upgrades in the last six months! Can't wait to try them all.


locked Re: Callsigns get cleared before I can see them

John Peck
 

Apparently when I began operations again after the summer break I clicked on the wrong link and installed 2.16.4 instead of 2.16.15. Problem solved. Sorry for the false alarm.

4281 - 4300 of 36454