Topics

problem with logging QSO's from JTDX


Sean - G4UCJ
 

I've been using JTDX with Logger for ages now, and was able to log from, JTDX into logger via UDP or TCP without issue. Now though, I am getting an error message every time. I've tried using TCP, UDP and just about anything I can think of. Nothing helps it now. 

I've attached a grab of the error window as it seems to contain all the relevant info.

There seems very little info on the net about this particular error message.

I can add the QSO manually into Logger as usual. I even started a new log and imported the ADIF of my existing log (240k entries), recalculated stats, reformatted numbers, etc. but nothing doing.

I don't know if this is a Windows or a logger issue - I feel something has become corrupted but what that is I don't know.

Thanks for any assistance

73, Sean G4UCJ
www.hfradio.org.uk  


Bob
 

Sean, the error message is from the Logger32 database to tell you that you were about to write invalid data to the logbook. I have three recomendations:

1) Are you trying to do nasty things to your logbook, or is the logbook broken? Who knows, hopefully we will figure it out. But just in case, make an ADIF backup of you logbook and hide it under the mattress.

2) Click VIEW and check the option ENABLE ERROR TRAPPING. Now, when the error occurs, addition information is shown. Maybe this will help identify the problem.

3) Setup for logging by TCP. With the TCP server window open, you can no see the logging message. If there's bad data, we should be able to see it.

SeventyThree(s)

PS. Another possible reason for the error 1006 is that maybe your 90 day free trial has expired :)

On 09/15/2020 9:41 AM Sean - G4UCJ <sean@...> wrote:


I've been using JTDX with Logger for ages now, and was able to log from, JTDX into logger via UDP or TCP without issue. Now though, I am getting an error message every time. I've tried using TCP, UDP and just about anything I can think of. Nothing helps it now. 

I've attached a grab of the error window as it seems to contain all the relevant info.

There seems very little info on the net about this particular error message.

I can add the QSO manually into Logger as usual. I even started a new log and imported the ADIF of my existing log (240k entries), recalculated stats, reformatted numbers, etc. but nothing doing.

I don't know if this is a Windows or a logger issue - I feel something has become corrupted but what that is I don't know.

Thanks for any assistance

73, Sean G4UCJ
www.hfradio.org.uk  


Gerald Boutin
 

Sean,

I see that there has been another issue reported with a similar description. Perhaps this might be related to your issue.

https://groups.io/g/hamlogger/message/79406


--
Gerald, VE1DT


Sean - G4UCJ
 

Hi Bob,
Thanks for the speedy reply. I've got the backup ADIF (used it to make a new log in case the original one had been corrupted), so it's safe to proceed!
All I want to do is to be able to have the log entry from JTDX copy over to Logger as it used to do.

I've looked at the TCP Server window and it shows the following (for the last few things whilst I was testing):
Listening on port: 52001
Connection request ID 4328 from 127.0.0.1
Received: <COMMAND:3>LOG <PARAMETERS:264> <BAND:2>2M <CALL:5>G0CBO <FREQ:10>144.175079 <MODE:3>FT8 <QSO_DATE:8>20200915 <TIME_ON:6>094322 <QSO_DATE_OFF:8>20200915 <TIME_OFF:6>094822 <RST_SENT:3>-15 <RST_RCVD:3>-15 <TX_PWR:17>5W + 5 ELE AT 6M. <GRIDSQUARE:4>JO02 <COMMENT:25>FT8  SENT: -15  RCVD: -15 <EOR>  from 127.0.0.1 [4328]
09:48:31 G0CBO is a duplicate QSO
Sending: NAK : Duplicate QSO to 127.0.0.1 [4328]
Elapsed time 8.9 ms.
 
Elapsed time 7.6 ms.
 
Listening on port: 52001
Connection request ID 3056 from 127.0.0.1
Received: <COMMAND:3>LOG <PARAMETERS:264> <BAND:2>2M <CALL:5>G0JVT <FREQ:10>144.175079 <MODE:3>FT8 <QSO_DATE:8>Listening on port: 52001
Connection request ID 4328 from 127.0.0.1
Received: <COMMAND:3>LOG <PARAMETERS:264> <BAND:2>2M <CALL:5>G0CBO <FREQ:10>144.175079 <MODE:3>FT8 <QSO_DATE:8>20200915 <TIME_ON:6>094322 <QSO_DATE_OFF:8>20200915 <TIME_OFF:6>094822 <RST_SENT:3>-15 <RST_RCVD:3>-15 <TX_PWR:17>5W + 5 ELE AT 6M. <GRIDSQUARE:4>JO02 <COMMENT:25>FT8  SENT: -15  RCVD: -15 <EOR>  from 127.0.0.1 [4328]
09:48:31 G0CBO is a duplicate QSO
Sending: NAK : Duplicate QSO to 127.0.0.1 [4328]
Elapsed time 8.9 ms.
 
Listening on port: 52001
Connection request ID 3332 from 127.0.0.1
Received: <COMMAND:3>LOG <PARAMETERS:264> <BAND:2>2M <CALL:5>G0CBO <FREQ:10>144.175079 <MODE:3>FT8 <QSO_DATE:8>20200914 <TIME_ON:6>093047 <QSO_DATE_OFF:8>20200914 <TIME_OFF:6>093147 <RST_SENT:3>-15 <RST_RCVD:3>-15 <TX_PWR:17>5W + 5 ELE AT 6M. <GRIDSQUARE:4>JO02 <COMMENT:25>FT8  SENT: -15  RCVD: -15 <EOR>  from 127.0.0.1 [3332]
09:49:07 G0CBO is a duplicate QSO
Sending: NAK : Duplicate QSO to 127.0.0.1 [3332]
Elapsed time 7.6 ms.
 
Listening on port: 52001
Connection request ID 3056 from 127.0.0.1
Received: <COMMAND:3>LOG <PARAMETERS:264> <BAND:2>2M <CALL:5>G0JVT <FREQ:10>144.175079 <MODE:3>FT8 <QSO_DATE:8>20200915 <TIME_ON:6>095458 <QSO_DATE_OFF:8>20200915 <TIME_OFF:6>095458 <RST_SENT:3>-15 <RST_RCVD:3>-15 <TX_PWR:17>5W + 5 ELE AT 6M. <GRIDSQUARE:4>JO02 <COMMENT:25>FT8  SENT: -15  RCVD: -15 <EOR>  from 127.0.0.1 [3056]
Listening on port: 52001
Sending: ACK to 127.0.0.1 [3056]
Elapsed time 8211.1 ms.

I notice that for G0CBO, even though the start times (and end times in a couple of cases) are different, the message is saying 'Duplicate QSO' which is odd.

This is under TCP (obviously). When I log a different callsign (in this case, M0IXYTEST1) the original error message shows.

Listening on port: 52001
Connection request ID 4272 from 127.0.0.1
Received: <COMMAND:3>LOG <PARAMETERS:270> <BAND:2>2M <CALL:10>M0IXYTEST1 <FREQ:10>144.175862 <MODE:3>FT8 <QSO_DATE:8>20200915 <TIME_ON:6>143922 <QSO_DATE_OFF:8>20200915 <TIME_OFF:6>143922 <RST_SENT:3>-15 <RST_RCVD:3>-15 <TX_PWR:17>5W + 5 ELE AT 6M. <GRIDSQUARE:4>JO01 <COMMENT:25>FT8  SENT: -15  RCVD: -15 <EOR>  from 127.0.0.1 [4272]
Listening on port: 52001
Sending: ACK to 127.0.0.1 [4272]
Elapsed time 7646.3 ms.

If I try UDP, the QSO disappears - JTDX logs it to its own file but the entry never propagates to Logger. 

Attached are the dupe error message and config screens from JTDX

The PC is an i7 3770, 16GB RAM, Win10 (latest version). The hardware is all OK - I've tested every piece of it :) 

This has really confused me (that is not too difficult though!).

73, Sean


Sean - G4UCJ
 

Hi Gerald,
Yes, it is a similar problem. I tried what was suggested in that discussion, but it made no difference to my problem, unfortunately.

73, Sean


Bob
 

Sean, the first thing that jumps out at me is the TX_PWR field of <TX_PWR:17>5W + 5 ELE AT 6M. The ADIF spec calls for a power in Watts with a value greater than 0. And, internally, Logger32 only allows for 10 characters (you have 17). Change the entry to simply 5 (without the W). SeventyThree(s).

The ADIF spec calls for a power in Watts with a value greater than 0. 

On 09/15/2020 10:55 AM Sean - G4UCJ <sean@...> wrote:


Hi Bob,
Thanks for the speedy reply. I've got the backup ADIF (used it to make a new log in case the original one had been corrupted), so it's safe to proceed!
All I want to do is to be able to have the log entry from JTDX copy over to Logger as it used to do.

I've looked at the TCP Server window and it shows the following (for the last few things whilst I was testing):
Listening on port: 52001
Connection request ID 4328 from 127.0.0.1
Received: <COMMAND:3>LOG <PARAMETERS:264> <BAND:2>2M <CALL:5>G0CBO <FREQ:10>144.175079 <MODE:3>FT8 <QSO_DATE:8>20200915 <TIME_ON:6>094322 <QSO_DATE_OFF:8>20200915 <TIME_OFF:6>094822 <RST_SENT:3>-15 <RST_RCVD:3>-15 <TX_PWR:17>5W + 5 ELE AT 6M. <GRIDSQUARE:4>JO02 <COMMENT:25>FT8  SENT: -15  RCVD: -15 <EOR>  from 127.0.0.1 [4328]
09:48:31 G0CBO is a duplicate QSO
Sending: NAK : Duplicate QSO to 127.0.0.1 [4328]
Elapsed time 8.9 ms.

Elapsed time 7.6 ms.

Listening on port: 52001
Connection request ID 3056 from 127.0.0.1
Received: <COMMAND:3>LOG <PARAMETERS:264> <BAND:2>2M <CALL:5>G0JVT <FREQ:10>144.175079 <MODE:3>FT8 <QSO_DATE:8>Listening on port: 52001
Connection request ID 4328 from 127.0.0.1
Received: <COMMAND:3>LOG <PARAMETERS:264> <BAND:2>2M <CALL:5>G0CBO <FREQ:10>144.175079 <MODE:3>FT8 <QSO_DATE:8>20200915 <TIME_ON:6>094322 <QSO_DATE_OFF:8>20200915 <TIME_OFF:6>094822 <RST_SENT:3>-15 <RST_RCVD:3>-15 <TX_PWR:17>5W + 5 ELE AT 6M. <GRIDSQUARE:4>JO02 <COMMENT:25>FT8  SENT: -15  RCVD: -15 <EOR>  from 127.0.0.1 [4328]
09:48:31 G0CBO is a duplicate QSO
Sending: NAK : Duplicate QSO to 127.0.0.1 [4328]
Elapsed time 8.9 ms.

Listening on port: 52001
Connection request ID 3332 from 127.0.0.1
Received: <COMMAND:3>LOG <PARAMETERS:264> <BAND:2>2M <CALL:5>G0CBO <FREQ:10>144.175079 <MODE:3>FT8 <QSO_DATE:8>20200914 <TIME_ON:6>093047 <QSO_DATE_OFF:8>20200914 <TIME_OFF:6>093147 <RST_SENT:3>-15 <RST_RCVD:3>-15 <TX_PWR:17>5W + 5 ELE AT 6M. <GRIDSQUARE:4>JO02 <COMMENT:25>FT8  SENT: -15  RCVD: -15 <EOR>  from 127.0.0.1 [3332]
09:49:07 G0CBO is a duplicate QSO
Sending: NAK : Duplicate QSO to 127.0.0.1 [3332]
Elapsed time 7.6 ms.

Listening on port: 52001
Connection request ID 3056 from 127.0.0.1
Received: <COMMAND:3>LOG <PARAMETERS:264> <BAND:2>2M <CALL:5>G0JVT <FREQ:10>144.175079 <MODE:3>FT8 <QSO_DATE:8>20200915 <TIME_ON:6>095458 <QSO_DATE_OFF:8>20200915 <TIME_OFF:6>095458 <RST_SENT:3>-15 <RST_RCVD:3>-15 <TX_PWR:17>5W + 5 ELE AT 6M. <GRIDSQUARE:4>JO02 <COMMENT:25>FT8  SENT: -15  RCVD: -15 <EOR>  from 127.0.0.1 [3056]
Listening on port: 52001
Sending: ACK to 127.0.0.1 [3056]
Elapsed time 8211.1 ms.

I notice that for G0CBO, even though the start times (and end times in a couple of cases) are different, the message is saying 'Duplicate QSO' which is odd.

This is under TCP (obviously). When I log a different callsign (in this case, M0IXYTEST1) the original error message shows.

Listening on port: 52001
Connection request ID 4272 from 127.0.0.1
Received: <COMMAND:3>LOG <PARAMETERS:270> <BAND:2>2M <CALL:10>M0IXYTEST1 <FREQ:10>144.175862 <MODE:3>FT8 <QSO_DATE:8>20200915 <TIME_ON:6>143922 <QSO_DATE_OFF:8>20200915 <TIME_OFF:6>143922 <RST_SENT:3>-15 <RST_RCVD:3>-15 <TX_PWR:17>5W + 5 ELE AT 6M. <GRIDSQUARE:4>JO01 <COMMENT:25>FT8  SENT: -15  RCVD: -15 <EOR>  from 127.0.0.1 [4272]
Listening on port: 52001
Sending: ACK to 127.0.0.1 [4272]
Elapsed time 7646.3 ms.

If I try UDP, the QSO disappears - JTDX logs it to its own file but the entry never propagates to Logger. 

Attached are the dupe error message and config screens from JTDX

The PC is an i7 3770, 16GB RAM, Win10 (latest version). The hardware is all OK - I've tested every piece of it :) 

This has really confused me (that is not too difficult though!).

73, Sean


Sean - G4UCJ
 

Hi Bob,
Ahh - that text comes from JTDX, no mention of string length there. I will change that right now. Hopefully, that will cure it.

73, Sean - G4UCJ


Sean - G4UCJ
 

Further to my last, this has indeed cured it. 

Many thanks, Bob - as usual, operator error is the culprit!

Logging from JTDX has now resumed (I'll not make that mistake again)

73, Sean