Today I noticed that my log is showing my xmt freq as both xmt and rcv freq when logging FT8 QSOs through JTAlert 2.16.17.  At first I thought that I had changed something in JTAlert or WSJT-X to cause this but looking back in the log it started happening after I update DXK to ver 16.1.9. so now I'm wondering if that may be related.  I have my 7610 interfaced to Commander and it has always properly passed the rcv freq to DXK.

Any ideas of how I might troubleshoot this problem?

tnx

Dale, AA1QD

I just reverted back to DXK ver 16.1.5 and it's still happening.

Dale AA1QD

On 2021-07-12 10:30 AM, Dale Drake wrote:

Today I noticed that my log is showing my xmt freq as both xmt and rcv
freq when logging FT8 QSOs through JTAlert 2.16.17.

JTAlert 2.16.17 is badly out of date. The current version is 2.50.2

At first I thought that I had changed something in JTAlert or WSJT-X
to cause this but looking back in the log it started happening after
I update DXK to ver 16.1.9. so now I'm wondering if that may be
related.

My WSJTX 2.4.0/2.5.0-rc3 and JTAlert 2.50.2 system also logs the
TX and RX frequencies the same. AFAIK, that is the way they are
reported by WSJTX.


73,

... Joe, W4TV


On 2021-07-12 10:30 AM, Dale Drake wrote:

Today I noticed that my log is showing my xmt freq as both xmt and rcv freq when logging FT8 QSOs through JTAlert 2.16.17.  At first I thought that I had changed something in JTAlert or WSJT-X to cause this but looking back in the log it started happening after I update DXK to ver 16.1.9. so now I'm wondering if that may be related.  I have my 7610 interfaced to Commander and it has always properly passed the rcv freq to DXK.
Any ideas of how I might troubleshoot this problem?
tnx
Dale, AA1QD

Thanks Joe,  I changed JTAlert to log to its own ADIF file and it showed the rcv freq the same so I'm thinking the DXK is fine.  I've been using the older version of JTAlert because I can't get the .NET 5 to run on my PC for some reason which is needed for the latest JTAlert version.  The weird thing is that before July 10th my DXK logs show the rcv freq correctly but I made no changes to JTAlert.  I have WSJT-X settings split set to fake it because my rig and Commander don't react fast enough in split operation set to rig in WSJT-X.  I've always run it that way.  I posted my trouble the the Ham Apps group so maybe I'll get the help I need there.  Thanks again.

Dale AA1QD

+ AA6YQ comments below

Today I noticed that my log is showing my xmt freq as both xmt and rcv freq when logging FT8 QSOs through JTAlert 2.16.17. 

+ DXKeeper logs the QSO specified by the ADIF record it receives via TCP from JT-Alert; it makes no changes to the contents of this record.

        73,

             Dave, AA6YQ

Thanks Dave.  After I posted I figured out that the trouble is with what JTAlert is putting in the ADIF that feeds DXK.

NO! THERE IS NO "PROBLEM" WITH JTALERT.

The issue is that WSJTX supplies *ONLY ONE FREQUENCY* in it's "QSO
Logged" UDP Message. You would find the same result from *direct*
integration between WSJTX and DXKeeper/SpotCollector.

Here is the documentation of the "QSO Logged" UDP message:

* QSO Logged Out 5 quint32
* Id (unique key) utf8
* Date & Time Off QDateTime
* DX call utf8
* DX grid utf8
* Tx frequency (Hz) quint64
* Mode utf8
* Report sent utf8
* Report received utf8
* Tx power utf8
* Comments utf8
* Name utf8
* Date & Time On QDateTime
* Operator call utf8
* My call utf8
* My grid utf8
* Exchange sent utf8
* Exchange received utf8

If you want separate TX and RX frequencies *DON'T USE* the WSJTX
"QSO Logged" UDP Message (either via direct WSJTX integration or
JTAlert), instead *IMPORT* the WSJTX ADIF log. Otherwise,
complain to the WSJTX developers about the lack of TX_Freq,
RX_Freq *AND* TX_Offset, RX_Offset.


73,

... Joe, W4TV


On 2021-07-12 5:35 PM, Dale Drake wrote:

Thanks Dave.  After I posted I figured out that the trouble is with what JTAlert is putting in the ADIF that feeds DXK.