700ms delay needed for ptt on transition

[mdblack98]

My 10GHz set needs 700 ms to go from receive to transmit due to the waveguide relay. So I think the audio must be delayed at least 700 ms with respect to the PTT-signal.
I could not set the TX delay to a value higher than 0.5 s.
And I am worried that the delay is too long, so that the transmission is too late

[GeoBaltz]

This commit causes me to lose PTT control from wsjt-x (on my TS-890S). Verified with git bisect.

[mdblack98]

Try the latest and if that doesn't work please provide  debug. Please place this file as described belowhttps://www.dropbox.com/s/t52ngcalsgnpm8m/wsjtx_log_config.ini?dl=0 C:\Users\[username]\AppData\Local\WSJT-X The WSJT-X_Rigcontrol.log file will be in the same location Here's a youtube video showing Windows users howto -- https://www.youtube.com/watch?v=q9tAvhNmSvc For Linux put it in   ~/.config The WSJT-X_Rigcontrol.log file will be here: ~/.local/share/WSJT-X For MacOS put it in /Users/[username]/Library/Preferences Restart WSJT-X and duplicate the problem.Shut down WSJT-X Then send me the WSJT-X_RigControl.log fileMike W9MDB On Wednesday, November 1, 2023 at 03:42:53 PM CDT, GeoBaltz ***@***.***> wrote: This commit causes me to lose PTT control from wsjt-x (on my TS-890S). Verified with git bisect. — Reply to this email directly, view it on GitHub, or unsubscribe. You are receiving this because you authored the thread.Message ID: ***@***.***>

[GeoBaltz]

Still broken with current git and wsjtx 2.6.1
WSJT-X_RigControl.log

Still looks like this is caused by the additional item added to hamlib_port_t by commit 6cb17e4 "Add post_ptt_delay for situations..."

[mdblack98]

Please try the latest..... Should be fixed  now. On Thursday, November 9, 2023 at 09:25:11 AM CST, GeoBaltz ***@***.***> wrote: Still broken with current git WSJT-X_RigControl.log Still looks like this is caused by the additional item added to hamlib_port_t by commit 6cb17e4 "Add post_ptt_delay for situations..." — Reply to this email directly, view it on GitHub, or unsubscribe. You are receiving this because you authored the thread.Message ID: ***@***.***>

[GeoBaltz]

That was with the latest, as of 2023-11-09 10:20EST

[GeoBaltz]

Pulled, made, installed, ran again - still broken.

[mdblack98]

No it wasn't -- check the log  2023-10-25T18:08:07Z On Thursday, November 9, 2023 at 09:36:33 AM CST, GeoBaltz ***@***.***> wrote: That was with the latest, as of 2023-11-09 10:20EST — Reply to this email directly, view it on GitHub, or unsubscribe. You are receiving this because you authored the thread.Message ID: ***@***.***>

[GeoBaltz]

Sorry gotta leave for appointment. Which log was that timestamp from? Today's log attached 5 comments above.

[mdblack98]

The  one you just posted. https://github.com/Hamlib/Hamlib/files/13309778/WSJT-X_RigControl.log All you have to do is "rigctld --version"  to see what version you are running. On Thursday, November 9, 2023 at 10:01:06 AM CST, GeoBaltz ***@***.***> wrote: Sorry gotta leave for appointment. Which log was that timestamp from? Today's log attached 5 comments above. — Reply to this email directly, view it on GitHub, or unsubscribe. You are receiving this because you authored the thread.Message ID: ***@***.***>

[GeoBaltz]

OK, back again.
WSJT-X_RigControl.log

Problem still exists.

Aside: bogus version info due to stale copy of hamlibdatetime.h in Hamlib/src/, which was then included instead of newly created version in Hamlib/build/src/. Dunno how it got there; this version from latest git pull;make clean;make;

[GeoBaltz]

I see my emails still don't show up here.

Anyway, still broken with latest git master - no PTT control with wsjtx(2.6.1)
Latest debug log:
WSJT-X_RigControl.log

ISTM the problem is with the item added to struct hamlib_port, in spite of the comment/warning to not touch it until 5.0. Binary or shared library incompatibility??