Log4OM

Hello gurus,

I guess this topic serves both Log4OM & JTAlert users.

The following setup for LOG4OM-NG is well defined as per the manual & works fine:

1. JTDX DOES FT8.
2. JTDX WRITES TO LOG4OM-NG.
3. LOG4OM-NG WRITES TO LOG4OM VER 1.

My question:
How does one run JTAlert without it writing to any of the LOG4OM logs, or influencing in any way - just displaying and alerting on JTDX's messages?

Thanks in advance

IsaacL., 4Z1TL

Not possible to work with JTalert without logging to Log4OM. For all JTalert statistics
like "New DXCC", "New Grid" and all the others logging must be enabled and if it´s
enabled JTalert write to the Log4OM Log.

Simply let JTalert do the logging Job and disable UDP ADIF_Message from JTDX that
the QSO´s are not 2-times in the Log.

By the way, we are supporting the two Log4OM releases but not 3rd party software
like JTalert, FlDigi, Omnirig e.g.. For that you may ask the program authors of the
3rd party apps.

4z1tl wrote: 16 Apr 2020, 14:53 Hello gurus,

I guess this topic serves both Log4OM & JTAlert users.

The following setup for LOG4OM-NG is well defined as per the manual & works fine:

1. JTDX DOES FT8.
2. JTDX WRITES TO LOG4OM-NG.
3. LOG4OM-NG WRITES TO LOG4OM VER 1.

My question:
How does one run JTAlert without it writing to any of the LOG4OM logs, or influencing in any way - just displaying and alerting on JTDX's messages?

Thanks in advance

IsaacL., 4Z1TL

Dissable logging in JTALERT

Thanks guys but now I am totally confused.

Juergen : "Not possible to work with JTalert without logging to Log4OM"
Terry: "Dissable logging in JTALERT"

Which is it then?

TIA Isaac

Try disabling logging to log4om in JTALERT, you never know your luck

G4POP wrote: 16 Apr 2020, 18:16 Try disabling logging to log4om in JTALERT, you never know your luck

Terry,

That will work, but, as Juergen said, that will cause the JTAlert alerting features not to work. His suggestion of keeping JTDX from logging, and logging from JTAlert would be my preference. Of course, the final decision is up to Isaac.

73,

Jim N6VH

N6VH wrote: 17 Apr 2020, 00:53 That will work, but, as Juergen said, that will cause the JTAlert alerting features not to work. His suggestion of keeping JTDX from logging, and logging from JTAlert would be my preference. Of course, the final decision is up to Isaac.

73,

Jim N6VH

I love this alerting features too. That´s why i stopped direct logging from JTDX. But everybody
has to find out his "best" way ..

N6VH wrote: 17 Apr 2020, 00:53

G4POP wrote: 16 Apr 2020, 18:16 Try disabling logging to log4om in JTALERT, you never know your luck

Terry,

That will work, but, as Juergen said, that will cause the JTAlert alerting features not to work. His suggestion of keeping JTDX from logging, and logging from JTAlert would be my preference. Of course, the final decision is up to Isaac.

73,

Jim N6VH

Jim,
I think you will find that if you scan the Log4OM log in JTAlert and then disable logging to Log4OM in JTAlert that it will function for ALERTING as normal.

Still wondering that VK3AMA said at his pages that logging must be enabled for alerting
and the worked B4. But makes no difference for me to disable direct logging in JTDX. I,
for my self, let JTalert do his work.

Juergen,

Yes, I agree. I use WSJT-X instead of JTDX, but I think the process is the same. I have never seen any advantage to direct logging from WSJT-X (or JTDX), while there are advantages to logging via JTAlert.

Terry,

Your process might work, but it actually involves an extra couple of steps. Not a big deal, but just something else to be done.

73,

Jim N6VH