Page 1 of 1

Import from JTDX

Posted: 22 Nov 2020, 14:45
by F6EXV
Hi all
My JTDX QSOs are imported directly.
In Log4OM, I have set (among others) Eqsl to NO for both sent and received, and LoTW rcvd to NO, as default.

When a QSO comes in from JTDX, the HRD, HamQTH and qrz.com default are not changed, the eQSL is changed to Requested for both Sent and Rcvd, and LoTW Rcvd is changed to Requested.

1/ If a default is defined in the config setup, how come SOME of the QSLing is modified, others are not ? And why these, not the others ?
2/ Shouldn't the default have priority on these fields over anything imported, rather than having SOME changed ?

Or have I missed something ?

Re: Import from JTDX

Posted: 22 Nov 2020, 15:16
by DF5WW
Did you mean that JTDX is sending the QSO directly to Log4OM without using JTalert ?
If so it´s not possible that JTDX changing the QSL status so JTDX send no wsl status
lines to Log4OM and/or JTalert.

In JTalert you can set that LotW will stored as REQUESTED (or not) and this will
overwrite the Log4OM defaults.

1.png
1.png (44.59 KiB) Viewed 2285 times

Re: Import from JTDX

Posted: 22 Nov 2020, 16:41
by F6EXV
This is exactly what I missed, in JTAlert, Juergen !
Thank you for pointing that out to me !

Re: Import from JTDX

Posted: 22 Nov 2020, 17:25
by F6EXV
Well, I thought that was it... It is part of it !
Now the QSO is logged twice, some seconds apart, both with no longer changing the QSL options in L4OM.
The ONLY thing I changed was to tick these 2 off, so how come the QSOs are now logged twice ... ?

Re: Import from JTDX

Posted: 22 Nov 2020, 17:38
by F6EXV
SV2HXX.jpg
SV2HXX.jpg (17.1 KiB) Viewed 2272 times

Re: Import from JTDX

Posted: 22 Nov 2020, 18:50
by G4POP
Seems you set it up incorrectly

Your either using JTalert to log and also UDP

or

You are using the ADIF monitor and UDP


Either will cause dupes

Re: Import from JTDX

Posted: 22 Nov 2020, 19:10
by F6EXV
For a reason I am unable to explain, I prefer the logging to come from JTDX rather than JTAlert.

These UDP things are something I have NO understanding whatsoever. You are talking Javanese to me (not a criticism).
I want JTDX to log to Log4OM, and JTAlert to only alert me on new ones that I have programmed. I have two sessions running at the same time (you all read about it, right ?!), and as you can see on the attachment, my JTDX settings are absolutely identical (except the port numbers)
One session logs correctly (once), the other session logs twice.
On the JTAlert, there are two "pages" that are important (I think)
The logging page : I have the upper part correctly set up, all the logging options are ticked out, except the last one (Clear callsigns display after logging). This is identical on both sessions
The 'Log4OM V2" page : Enable Log4OM V2 logging is enabled, and "send WSJTx DX Call to Log4OM" is also ticked, on BOTH sessions. The rest of that page is identical, except the callsigns of course, and the path to the log (SQLite)

So where must I look to correct this double logging, while both sessions are set up the same way, one works fine, not the other ??
settings.jpg
settings.jpg (156.25 KiB) Viewed 2266 times

Re: Import from JTDX

Posted: 22 Nov 2020, 19:52
by G4POP
Your in the wrong Place

If you want JTalert just to show required but NOT to log ...... disable logging to log4om in the JTALERT settings

Re: Import from JTDX

Posted: 23 Nov 2020, 02:10
by F6EXV
Hi Terry
Yes, that works.
But on the other callsign setup, this "Enable logging" is enabled, and QSOs are logged only once. Out of curiosity, how come ?

Re: Import from JTDX

Posted: 23 Nov 2020, 08:30
by G4POP
F6EXV wrote: 23 Nov 2020, 02:10 Hi Terry
Yes, that works.
But on the other callsign setup, this "Enable logging" is enabled, and QSOs are logged only once. Out of curiosity, how come ?
You must have done something wrong on the UDP setup for the other call sign, or you set it up using duplicated UDP port numbers