Page 1 of 1

1.39 question

Posted: 27 Aug 2019, 14:48
by W4EBB
I use JTAlert with wsjt-x. Am I correct that if I install Log4om I have to "turn on" the new UDP support in Log4om and then turn it off in JtAlert.
If I don't turn on the new UDP support in Log4om then all should be okay. Right?
Charlie

Re: 1.39 question

Posted: 27 Aug 2019, 16:28
by DF5WW
If you leave all as is in your settings logging via JTalert to Log4OM will be the same as before.
If you enable new UDP in Log4OM and not turning off in JTalert there will be double entries
in your Log. For direct WSJT-x to L4O enable new support in the logger and disable in JTalert.

;) ;)

Re: 1.39 question

Posted: 27 Aug 2019, 17:20
by W4EBB
Thanks!
My follow-up question: is there an advantage one way or the other?
Charlie

Re: 1.39 question

Posted: 27 Aug 2019, 17:35
by DF5WW
Hi Charlie,

don´t think so. On my end i will log via JTalert as in the past but some guys need direct logging
from WSJT-X (JTDX) to Log4OM without the need of JTalert.

;) ;)

Re: 1.39 question

Posted: 29 Aug 2019, 20:29
by N6VH
There could be one disadvantage to logging with WSJT-X instead of JTAlertX. If you do this, JTAlert might not work for giving you alerts, and Scan Log might not work.

Re: 1.39 question

Posted: 30 Aug 2019, 11:18
by KI5IO
N6VH wrote: 29 Aug 2019, 20:29 There could be one disadvantage to logging with WSJT-X instead of JTAlertX. If you do this, JTAlert might not work for giving you alerts, and Scan Log might not work.
And that may not be any problem for some OM. They may not want to use JTAlert or may not even be aware of its availability.

At the least this gives more options and functionality.

Re: 1.39 question

Posted: 31 Aug 2019, 21:59
by N6VH
KI5IO wrote: 30 Aug 2019, 11:18
N6VH wrote: 29 Aug 2019, 20:29 There could be one disadvantage to logging with WSJT-X instead of JTAlertX. If you do this, JTAlert might not work for giving you alerts, and Scan Log might not work.
And that may not be any problem for some OM. They may not want to use JTAlert or may not even be aware of its availability.

At the least this gives more options and functionality.
Yes, I understand that. However, the OP asked - "My follow-up question: is there an advantage one way or the other?"

I was merely answering his question.

Jim N6VH

Re: 1.39 question

Posted: 01 Sep 2019, 05:51
by NN7D
You can log directly from WSJTx to Log4OM, and still run JTAlert for its alert features. Just turn off Log4Om logging in JTAlert.

I believe based on my experience that direct logging is more reliable.

Doug
W7DRM

Re: 1.39 question

Posted: 02 Sep 2019, 01:20
by N6VH
W7DRM wrote: 01 Sep 2019, 05:51 You can log directly from WSJTx to Log4OM, and still run JTAlert for its alert features. Just turn off Log4Om logging in JTAlert.

I believe based on my experience that direct logging is more reliable.

Doug
W7DRM
If you turn off Log4OM logging in JTAlert, then Scan Log and Rebuild won't work, and therefore, alerts won't work correctly either. It is certainly possible that some might not need or want those features, but it is something to be aware of.

Based on my experience, JTAlert logging is very reliable. I did have to increase the timing for the Check QSO Log Record setting, but then logging works fine.

73,
Jim N6VH