Date   

locked Re: Incorrect logged QSO times in WSJT-X Version 2.5.4 when running MSK144 #IssueReport #logging #MSK144

Jim Brown
 

On 8/8/2022 10:16 PM, Reino Talarmo wrote:
With all respect of your problems you are actually introducing a third working related time "Caller's Start Time".
No, I did not. What I said is that the logging software sets the caller's "Start Time" under the conditions I described can often be 30-90 minutes before the QSO actually takes place, it takes place over 1-2 minutes, and the DX logs it when HE responds to the caller. In the conditions I described, these Starting Times are 30-90 minutes apart.


Of course even that is interesting on the operator's point of view, but it really involves highly probably only one station especially on MS QSOs.
So it is not something that is common to both stations.

But it doesn't matter -- the solution I proposed works for short QSOs and long ones. What matters is that the LOGGED Start Times are within 30 minutes of each other.

The other party may also be involved into another call at that time and may not consider it as a start of a QSO at all, especially DX station has that problem due to a pile.

Exactly right! THAT is the problem.

Programming that time into an automation is most probably impossible as you stated "as soon as they hear him" and e.g. there seems to be many operators that just start calling without even hearing (seeing) the DX station!
Yes, but it doesn't matter. What matters is that they log the Start Time of the QSO within 30 minutes of each other. This is a STANDARD, which in the context of this discussion, is poorly conceived, but it is the STANDARD, and we have to live with it.

BTW -- I've been a member of the Standards Committee of the Audio Engineering Society for nearly 30 years, an international committee, and am principal author of seven Standards on EMC.

One of the shortcomings of WSJT-X authors is their limited exposure to many of the ways their wonderful software is used. One of the great strengths of the AES Standards Committee is that our members come from nearly a many different disciplines in how our Standards are used. We have important contributors from TV and Radio Broadcasting, Sound Reinforcement for large and small venues, Recording, Remote Broadcast and Recording, Small Home Studios, professionals who design the systems and those who use them.

The solution I proposed is sensible, as indicated by AA6YQ, who has for 20 years studied LOTW and other such systems, and produced professional quality software to support it. My solution is trivially easy to program. I've been using Dave's DXKeeper for nearly 20 years. His contributions have been recognized by ARRL with an award for Technical Excellence.

Perhaps we should limit our logging to "QSO start time" and "QSO completion time". Those are easier to define,
No, they are NOT, for the several examples I've cited.

Consider this, Reino. The DX logs the Start Time for his QSO when he starts to work me, and the Completion Time, which doesn't matter, when he copies my RRR. But the CALLER'S logging software logs the Starting Time as 30-90 minutes earlier. This happens with ALL WSJT-X modes, not only MSK144. I've had it happen more with FT8.

73, Jim K9YC


locked Re: #band #band

pariswi2002 <KS9U@AOL.COM>
 

Reino, Your tip solved the problem I think. After clicking the box the readout still says 28313.0 but it now has turned black in freq box and first CQ was answered by a XE2. Not the first 6m XE but its appears to work now ….Thanks to all for tips

73’s Bruce

On Aug 9, 2022, at 7:44 AM, pariswi2002 <KS9U@...> wrote:

Reino, Thanks for the info. After doing that the freq in the wsjt box is no longer red although I have not worked alone there yet we will see what happens as the day and my free time progress.

’73 Bruce

On Aug 9, 2022, at 6:48 AM, Reino Talarmo <reino.talarmo@...> wrote:

Hi Bruce,
Perhaps you have not added a transverter offset to the Frequencies tab. See User Manual 8.1 VHF Setup for details.
73, Reino OH3mA

-----Original Message-----
From: main@WSJTX.groups.io [mailto:main@WSJTX.groups.io
To: main@wsjtx.groups.io
Subject: Re: [WSJTX] #band

add the frequency to the list manually. maybe it is not in your frequency table in wsjt

Dave Garber
VE3WEJ / VE3IE


On Mon, Aug 8, 2022 at 2:06 PM pariswi2002 <KS9U@...> via groups.io <KS9U@...> wrote:

I am successively using my Yaesu Mark V on 10-160 when I want to on
FT8 but when turning on the FTV 1000 transverter WSJT does not see 6m
as far as transmitting but decodes. I have no idea where it does
transmit when I try but thinking 28.313 as that is what WSJT shows in
freq window. Anyone using this combination on FT8? Thanks for your time.

Bruce

















locked Re: #band #band

pariswi2002 <KS9U@AOL.COM>
 

Reino, Thanks for the info. After doing that the freq in the wsjt box is no longer red although I have not worked alone there yet we will see what happens as the day and my free time progress.

’73 Bruce

On Aug 9, 2022, at 6:48 AM, Reino Talarmo <reino.talarmo@...> wrote:

Hi Bruce,
Perhaps you have not added a transverter offset to the Frequencies tab. See User Manual 8.1 VHF Setup for details.
73, Reino OH3mA

-----Original Message-----
From: main@WSJTX.groups.io [mailto:main@WSJTX.groups.io
To: main@wsjtx.groups.io
Subject: Re: [WSJTX] #band

add the frequency to the list manually. maybe it is not in your frequency table in wsjt

Dave Garber
VE3WEJ / VE3IE


On Mon, Aug 8, 2022 at 2:06 PM pariswi2002 <KS9U@...> via groups.io <KS9U@...> wrote:

I am successively using my Yaesu Mark V on 10-160 when I want to on
FT8 but when turning on the FTV 1000 transverter WSJT does not see 6m
as far as transmitting but decodes. I have no idea where it does
transmit when I try but thinking 28.313 as that is what WSJT shows in
freq window. Anyone using this combination on FT8? Thanks for your time.

Bruce















locked Re: #band #band

Reino Talarmo
 

Hi Bruce,
Perhaps you have not added a transverter offset to the Frequencies tab. See User Manual 8.1 VHF Setup for details.
73, Reino OH3mA

-----Original Message-----
From: main@WSJTX.groups.io [mailto:main@WSJTX.groups.io
To: main@wsjtx.groups.io
Subject: Re: [WSJTX] #band

add the frequency to the list manually. maybe it is not in your frequency table in wsjt

Dave Garber
VE3WEJ / VE3IE


On Mon, Aug 8, 2022 at 2:06 PM pariswi2002 <KS9U@...> via groups.io <KS9U@...> wrote:

I am successively using my Yaesu Mark V on 10-160 when I want to on
FT8 but when turning on the FTV 1000 transverter WSJT does not see 6m
as far as transmitting but decodes. I have no idea where it does
transmit when I try but thinking 28.313 as that is what WSJT shows in
freq window. Anyone using this combination on FT8? Thanks for your time.

Bruce






locked Re: #band #band

Dave Garber
 

add the frequency to the list manually. maybe it is not in your frequency
table in wsjt

Dave Garber
VE3WEJ / VE3IE


On Mon, Aug 8, 2022 at 2:06 PM pariswi2002 <KS9U@...> via groups.io
<KS9U@...> wrote:

I am successively using my Yaesu Mark V on 10-160 when I want to on FT8
but when turning on the FTV 1000 transverter WSJT does not see 6m as far as
transmitting but decodes. I have no idea where it does transmit when I try
but thinking 28.313 as that is what WSJT shows in freq window. Anyone using
this combination on FT8? Thanks for your time.

Bruce






locked Re: Incorrect logged QSO times in WSJT-X Version 2.5.4 when running MSK144 #IssueReport #logging #MSK144

Reino Talarmo
 

A DX station or an expedition to a rare grid or county begins operation, and those needing to work him start calling as soon as they hear him, setting the caller's Start Time.
Hi Jim,

With all respect of your problems you are actually introducing a third working related time "Caller's Start Time". Of course even that is interesting on the operator's point of view, but it really involves highly probably only one station especially on MS QSOs. So it is not something that is common to both stations. The other party may also be involved into another call at that time and may not consider it as a start of a QSO at all, especially DX station has that problem due to a pile.
Programming that time into an automation is most probably impossible as you stated "as soon as they hear him" and e.g. there seems to be many operators that just start calling without even hearing (seeing) the DX station!
Perhaps we should limit our logging to "QSO start time" and "QSO completion time". Those are easier to define, but still a bit difficult to program correctly as the example shows. One reason could be that there were two QSOs ongoing according to the ALL.txt information, if I remember proper.

73, Reino OH3mA


locked Re: Incorrect logged QSO times in WSJT-X Version 2.5.4 when running MSK144 #IssueReport #logging #MSK144

Sam Birnbaum
 

Hi John,
Disregard me previous msg sent about 5 minutes ago.
The very few times I ran MSK144 the adi record has different start stop times. In one case it's about 20 minutes:

<call:4>K2GK <gridsquare:4>FN30 <mode:6>MSK144 <rst_sent:3>-03 <rst_rcvd:3>+24 <qso_date:8>20200824 <time_on:6>142600 <qso_date_off:8>20200824 <time_off:6>142902 <band:2>6m <freq:9>50.261500 <station_callsign:5>W2JDB <my_gridsquare:4>FN30 <eor><call:4>K2GK <gridsquare:4>FN30 <mode:6>MSK144 <rst_sent:3>+00 <rst_rcvd:3>+11 <qso_date:8>20200825 <time_on:6>152015 <qso_date_off:8>20200825 <time_off:6>152100 <band:2>6m <freq:9>50.261500 <station_callsign:5>W2JDB <my_gridsquare:4>FN30 <eor><call:4>K2GK <gridsquare:4>FN30 <mode:6>MSK144 <rst_sent:3>-05 <rst_rcvd:3>+11 <qso_date:8>20200825 <time_on:6>152215 <qso_date_off:8>20200825 <time_off:6>152300 <band:2>6m <freq:9>50.261500 <station_callsign:5>W2JDB <my_gridsquare:4>FN30 <eor> Just some questions? 1: Are the log times always wrong or only if either you are calling CQ or the other ham is calling CQ?2: Are times wrong if/when you manually press Alt+Q to popup the log qso prompt or only if in contest mode and you have the Auto Log option checked? 
Just trying to isolate the condition if possible
73,
Sam W2JDB

-----Original Message-----
From: John P <j.m.price@...>
To: main@WSJTX.groups.io
Sent: Mon, Aug 8, 2022 2:24 pm
Subject: Re: [WSJTX] Incorrect logged QSO times in WSJT-X Version 2.5.4 when running MSK144 #IssueReport #logging

On Mon, Aug  8, 2022 at 02:05 PM, Sam Birnbaum wrote:


Please check the wsjtx_log.aid file
Sam... Here are the start and end times recorded in the wsjtx_log.adi file for the K0TPP QSO. Both 10:26:15

<qso_date:8>20220804 <time_on:6>102615 <qso_date_off:8>20220804 <time_off:6>102615

Don't see any reason to expect the ADI file data to be any different than the wsjtx.log file entry.

--
John P.
WA2FZW


locked Re: Incorrect logged QSO times in WSJT-X Version 2.5.4 when running MSK144 #IssueReport #logging

Sam Birnbaum
 

The person who originally started this thread never mentioned what the ADIF record in the file wsjtx_log.adi contains Do the start/end date time values in there reflect the same value or not? If not, then the problem does not lie with wsjt_x but rather downstream. 
73,

Sam W2JDB

-----Original Message-----
From: John P <j.m.price@...>
To: main@WSJTX.groups.io
Sent: Mon, Aug 8, 2022 2:14 pm
Subject: Re: [WSJTX] Incorrect logged QSO times in WSJT-X Version 2.5.4 when running MSK144 #IssueReport #logging

On Mon, Aug  8, 2022 at 02:06 PM, Philip Rose wrote:


As far as I can see the QSO actually started with the call at 102515 that
K0TPP answered
Phil... A valid point, however it still does not address the fact that both the start and end times were logged as 10:26:15.

--
John P.
WA2FZW


locked Re: Incorrect logged QSO times in WSJT-X Version 2.5.4 when running MSK144 #IssueReport #logging #MSK144

Michael Black
 

I see one problem.
I ran a local loopback test and found the CQ side logged the start time as the start time of the TX2 message and the TX1 side marked it as the start of the CQ.  Kind of the opposite one what one would expect but both sides should agree on what the start time is.So we need to fix this.
Mike W9MDB


locked Re: Incorrect logged QSO times in WSJT-X Version 2.5.4 when running MSK144 #IssueReport #logging #MSK144

Joe Subich, W4TV
 

On 2022-08-08 4:42 PM, Jim Brown wrote:
A DX station or an expedition to a rare grid or county begins
operation, and those needing to work him start calling as soon as
they hear him, setting the caller's Start Time. There are many
practical conditions of propagation and QRM that result in the DX
station hearing the caller and beginning the QSO 30-120 minutes
later.
Jim,

Set the watchdog to 5 minutes and double click on the DX Station
each time the watchdog times out. Double clicking on the DX Station
will reset the start time and you will never be "out of tolerance"
with the resulting time in your log.

73,

... Joe, W4TV

On 2022-08-08 4:42 PM, Jim Brown wrote:
You still don't understand the problem. You're describing a casual HF QSO. The Starting Time problem involves very different QSOs.
Remember that WSJT-X is used in a very wide variety of situations, everything from casual operation HF to extreme weak signal work from LF to UHF. Here's only one example.
A DX station or an expedition to a rare grid or county begins operation, and those needing to work him start calling as soon as they hear him, setting the caller's Start Time. There are many practical conditions of propagation and QRM that result in the DX station hearing the caller and beginning the QSO 30-120 minutes later. Since LOTW uses the starting times to validate a QSO, the validation fails.
I mostly use WSJT-X for weak signal work on 160M, 60M, and 6M, and to work an HF DXpedition. I've encountered this problem at least a half dozen times, losing QSOs that were quite important to me. Propagation for many QSOs on these bands is highly variable, involving multi-hop E-skip on 6M, similarly "spot-lighty" propagation on 160M. To work EU from near San Francisco on 60M, there's a window of 2-3 hours around the terminator.
73, Jim K9YC
On 8/8/2022 6:41 AM, Philip Rose via groups.io wrote:
As far as I can see the QSO actually started with the call at 102515 that K0TPP answered. The QSO comprises that transmissions highlighted below. The unanswered calls do NOT form part of the QSO.


locked Re: CQ POTA DE AB1CDE #NewUser

robert kupps
 

Hi AL, just an observation, not all POTA's give the parks or grid location , just their home QTH. Which I guess could be in a park.
Robert
W6ino
On Aug 8, 2022, at 7:49 PM, Carl Jón Denbow <carl@...> wrote:



On Aug 8, 2022, at 10:40 PM, Jim Shorney <jimNU0C@...> wrote:


My understanding is that the POTA spotter only picks up RBN spots if you have scheduled the activation in the POTA scheduler.

73

-Jim
NU0C
This has not been my experience. One time I called CQ POTA on FT8 before I spotted myself and the reverse beacon network picked me up and auto-spotted me. — 73 de Carl N8VZ


W6INO

~~~~~~~~~~~~~~~~~~~~~~~~~~~
Twenty years from now, you will be more disappointed by the things you didn't do than by the ones you did do.
So, throw off the bowlines. Sail away from the safe harbor. Catch the trade winds in your sails. Explore. Dream. Discover.
-Mark Twain


locked Re: CQ POTA DE AB1CDE #NewUser

Carl Jón Denbow
 

On Aug 8, 2022, at 10:40 PM, Jim Shorney <jimNU0C@...> wrote:


My understanding is that the POTA spotter only picks up RBN spots if you have scheduled the activation in the POTA scheduler.

73

-Jim
NU0C
This has not been my experience. One time I called CQ POTA on FT8 before I spotted myself and the reverse beacon network picked me up and auto-spotted me. — 73 de Carl N8VZ


locked Re: CQ POTA DE AB1CDE #NewUser

Jim Shorney
 

My understanding is that the POTA spotter only picks up RBN spots if you have scheduled the activation in the POTA scheduler.

73

-Jim
NU0C

On Mon, 08 Aug 2022 05:36:07 -0700
alanbeal@... wrote:

Usually, I just use CQ W1CHL EN80 and get an ok response, but I tried CQ POTA W1CHL EN80 the last time I was at a POTA park, and I noticed a couple of things.

1. The spotting on the POTA page did not seem to work. Even though I self-spotted on the POTA web page with FT8, it did not show 'last heard' for my CQ. I think the 'CQ POTA' confused the reverse beacons or whatever hears your signals and reports it on the POTA web page.

2. It seemed like I got a lot more responses to my CQ. This was just an instance so difficult to judge. People see POTA and reply.

I have to manually edit the WSJTX adi file and combine it with my HAMRS adi file before uploading to the POTA web site. I have to add my_sign_info and other fields. I wish wsjtx had a way to add additional fields to the ADI so I would have less editting for the POTA upload.





locked Re: CQ POTA DE AB1CDE #NewUser

W9VUP
 

This thread has been informative . Thanks to all.
Art

On Aug 8, 2022, at 5:48 PM, AC9XW Doug <ripondoug@...> wrote:

I do the “CQ POTA”. I’ve also seen “CQ IOTA” (islands on the air) and “CQ
SOTA”. ( summits on the air).

On Fri, Aug 5, 2022 at 10:46 PM Carl Jón Denbow <carl@...> wrote:

When I say “CQ POTA” I’m just announcing that I’m at a park and seeking
stations to call me. Sometimes, if the going is slow, I’ll add “You don’t
have to be participating in the POTA program. Any station, anywhere,
please call N8VZ now.” — 73 de Carl N8VZ
==============================
Carl Jón Denbow, N8VZ
17 Coventry Lane
Athens, Ohio 45701-3718

carl@...
www.n8vz.com
EM89wh

IRLP 4533 Echolink 116070

POTA on SSB and digital modes
=======================

On Aug 5, 2022, at 4:15 PM, Darl DEEDS <na8w@...> wrote:
Gwen!

Why in the world would you take that as a put down. I merely tried to
send him where all the answers to the questions are. AND I included the web
site. How would I know that he has looked at their web site and still don’t
understand it. Get a life and enjoy the hobby instead of dictating
negatives!

73
Darl NA8W

From: Gwen<mailto:gsw2@...>
Sent: Friday, August 5, 2022 15:33
To: main@WSJTX.groups.io<mailto:main@WSJTX.groups.io>
Subject: Re: [WSJTX] CQ POTA DE AB1CDE #NewUser

" ...

Please go to their web site and learn about about Parks on the Air.

....
"
That sounds like a put-down / diss.

The OP asked a reasonable question and should not be denegrated for
asking it.

I, too, had wondered about that --- whether the inclusion of "POTA"
meant ( Don't bother me if you aren't also a POTA station ). It is a
reasonable assumption based on other amendment protocols (such as "DX")

Might be better if the protocol specified something like: " CQ W1AW
POTA" instead of " CQ POTA W1AW " ---- the former being far LESS
confusing to Noobs.

Gwen

KI5PXQ




On 8/5/22 09:52, Darl DEEDS wrote:
Please go to their web site and learn about about Parks on the Air.

https://pota.app

NA8W

From: Chuck Gelm<mailto:nc8q-aredn@...>
Sent: Friday, August 5, 2022 11:43
To: main@WSJTX.groups.io<mailto:main@WSJTX.groups.io>
Subject: Re: [WSJTX] CQ POTA DE AB1CDE #NewUser

On 8/5/22 10:13, Robert Bower wrote:
No, it means they are at a park doing a POTA activation. They need
ten contacts for a successful activation so I also try to respond.


On 2022-08-05 06:54, Chuck Gelm wrote:
Does 'CQ POTA' mean "I only want stations at a park to reply"?

73, Chuck


Do they need 10 other POTA stations or any 10 stations?























--
Doug Iverson





locked Re: CQ POTA DE AB1CDE #NewUser

AC9XW Doug
 

I do the “CQ POTA”. I’ve also seen “CQ IOTA” (islands on the air) and “CQ
SOTA”. ( summits on the air).

On Fri, Aug 5, 2022 at 10:46 PM Carl Jón Denbow <carl@...> wrote:

When I say “CQ POTA” I’m just announcing that I’m at a park and seeking
stations to call me. Sometimes, if the going is slow, I’ll add “You don’t
have to be participating in the POTA program. Any station, anywhere,
please call N8VZ now.” — 73 de Carl N8VZ
==============================
Carl Jón Denbow, N8VZ
17 Coventry Lane
Athens, Ohio 45701-3718

carl@...
www.n8vz.com
EM89wh

IRLP 4533 Echolink 116070

POTA on SSB and digital modes
=======================

On Aug 5, 2022, at 4:15 PM, Darl DEEDS <na8w@...> wrote:

Gwen!

Why in the world would you take that as a put down. I merely tried to
send him where all the answers to the questions are. AND I included the web
site. How would I know that he has looked at their web site and still don’t
understand it. Get a life and enjoy the hobby instead of dictating
negatives!

73
Darl NA8W

From: Gwen<mailto:gsw2@...>
Sent: Friday, August 5, 2022 15:33
To: main@WSJTX.groups.io<mailto:main@WSJTX.groups.io>
Subject: Re: [WSJTX] CQ POTA DE AB1CDE #NewUser

" ...

Please go to their web site and learn about about Parks on the Air.

....
"
That sounds like a put-down / diss.

The OP asked a reasonable question and should not be denegrated for
asking it.

I, too, had wondered about that --- whether the inclusion of "POTA"
meant ( Don't bother me if you aren't also a POTA station ). It is a
reasonable assumption based on other amendment protocols (such as "DX")

Might be better if the protocol specified something like: " CQ W1AW
POTA" instead of " CQ POTA W1AW " ---- the former being far LESS
confusing to Noobs.

Gwen

KI5PXQ




On 8/5/22 09:52, Darl DEEDS wrote:
Please go to their web site and learn about about Parks on the Air.

https://pota.app

NA8W

From: Chuck Gelm<mailto:nc8q-aredn@...>
Sent: Friday, August 5, 2022 11:43
To: main@WSJTX.groups.io<mailto:main@WSJTX.groups.io>
Subject: Re: [WSJTX] CQ POTA DE AB1CDE #NewUser

On 8/5/22 10:13, Robert Bower wrote:
No, it means they are at a park doing a POTA activation. They need
ten contacts for a successful activation so I also try to respond.


On 2022-08-05 06:54, Chuck Gelm wrote:
Does 'CQ POTA' mean "I only want stations at a park to reply"?

73, Chuck


Do they need 10 other POTA stations or any 10 stations?























--
Doug Iverson


locked Re: #Cat_RigControl #Cat_RigControl

Michael Black
 

Please try this dll -- it's the 64-bit version
https://www.dropbox.com/s/7aejdv74nfjxr0q/libhamlib-4.dll?dl=0

Mike W9MDB


locked Re: Incorrect logged QSO times in WSJT-X Version 2.5.4 when running MSK144 #IssueReport #logging #MSK144

Jim Brown
 

You still don't understand the problem. You're describing a casual HF QSO. The Starting Time problem involves very different QSOs.

Remember that WSJT-X is used in a very wide variety of situations, everything from casual operation HF to extreme weak signal work from LF to UHF. Here's only one example.

A DX station or an expedition to a rare grid or county begins operation, and those needing to work him start calling as soon as they hear him, setting the caller's Start Time. There are many practical conditions of propagation and QRM that result in the DX station hearing the caller and beginning the QSO 30-120 minutes later. Since LOTW uses the starting times to validate a QSO, the validation fails.

I mostly use WSJT-X for weak signal work on 160M, 60M, and 6M, and to work an HF DXpedition. I've encountered this problem at least a half dozen times, losing QSOs that were quite important to me. Propagation for many QSOs on these bands is highly variable, involving multi-hop E-skip on 6M, similarly "spot-lighty" propagation on 160M. To work EU from near San Francisco on 60M, there's a window of 2-3 hours around the terminator.

73, Jim K9YC

On 8/8/2022 6:41 AM, Philip Rose via groups.io wrote:
As far as I can see the QSO actually started with the call at 102515 that K0TPP answered. The QSO comprises that transmissions highlighted below. The unanswered calls do NOT form part of the QSO.


locked Re: Incorrect logged QSO times in WSJT-X Version 2.5.4 when running MSK144 #IssueReport #logging #MSK144

 

On Mon, Aug 8, 2022 at 04:57 AM, Jim Brown wrote:


To the development team -- it seems to me that the time sent to logging
software as the starting time ought to be either 1) the completion time or 2)
2 minutes prior to the completion time.
Jim... Not everybody uses automatic logging. Some folks still do it manually and I would expect them to log the correct start and end times, so if WSJT-X is logging incorrect times, the problem still exists. Replacing one piece of bad data with another piece of bad data isn't such a great idea!

As GM3ZZA pointed out, the start time should probably be considered to be the call at 102515 that K0TPP answered.

--
John P.
WA2FZW


locked Re: Incorrect logged QSO times in WSJT-X Version 2.5.4 when running MSK144 #IssueReport #logging #MSK144

 

On Mon, Aug 8, 2022 at 02:05 PM, Sam Birnbaum wrote:


Please check the wsjtx_log.aid file
Sam... Here are the start and end times recorded in the wsjtx_log.adi file for the K0TPP QSO. Both 10:26:15

<qso_date:8>20220804 <time_on:6>102615 <qso_date_off:8>20220804 <time_off:6>102615

Don't see any reason to expect the ADI file data to be any different than the wsjtx.log file entry.

--
John P.
WA2FZW


locked Re: #Cat_RigControl #Cat_RigControl

Michael Black
 

Take this and place it in a file called "hamlib_settings.json" and place it in the same location as WSJT-X.ini
{     "config": { "serial_party": "Odd"
     }}
If it works OK I'll make the permanent change in Hamlib.
Mike W9MDB

On Monday, August 8, 2022 at 01:04:51 PM CDT, David Owen via groups.io <djmowen@...> wrote:

Re: Hamlib for R&S EK895

Hi Michael

Thanks for your reply to my post.

I think there will have to be some way of setting the parity of the serial characters.

I started WSJT-X 2.5.4 with the latest "libhamlib-4" and set the radio to R&S EK895.

An timeout error was displayed (see "attach_1").

The EK895 command "0000 46 3f 0d  F?.", in the middle of the error message,
looks correct to read the radio frequency according to the R&S user manual.
I tried to send this command directly to the EK895 with a terminal emulator.
This produced a correct reply from the radio - as long as - the parity is set to "ODD"
and the character length is set to 7 (see "attach_2").

I thought I would just set the radio interface to "NO PARITY" and 8 bits
but this turns out to be impossible according to the user manual (see "attach_3" and "attach_4").
It seems that R&S want users to always use some parity - at least with the EK895.

There does not seem to be a way of setting parity on the WSJT-X setup tab
so something in the  Hamlib dll might have to be altered.

Someone might know if this applies to the other R&S radios?

Regards

David Owen

GM1OXB

3121 - 3140 of 39847