Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

QSSTV broken with latest hamlib #46

Open
sjlongland opened this issue Jul 16, 2024 · 0 comments
Open

QSSTV broken with latest hamlib #46

sjlongland opened this issue Jul 16, 2024 · 0 comments

Comments

@sjlongland
Copy link

Hi,

I've been debugging an issue with Hamlib where it intermittently toggles the VFO, which wears out relays in the transceiver and causes quite a lot of pain with receiving SSTV transmissions unless both VFOs happen to be on the same frequency.

Hamlib/Hamlib#1576 has the background, I'm experiencing this with a Yaesu FT-897D. Hence I updated to the latest release, that seems to have cured the VFO switching issue, but has broken QSSTV.

Platform is Debian Linux (Raspbian) Bookworm on armhf. Hardware is a Raspberry Pi 4 8GB + NWDR DRAWS radio interface, with a USB pl2303-based CAT transceiver cable for the CAT connection. I am not able to access DTR/RTS pins on said CAT transceiver cable.

When I compile QSSTV against the current latest Hamlib master branch (commit 8b9c768), either QSSTV 9.5.8 (from Debian's source tree) or master branch, QSSTV reports "No Rig" in the frequency display, and fails to engage PTT on the transceiver when transmitting.

The only other way I can key the transceiver, is via /sys/class/gpio, which QSSTV does not support.

I am able to successfully engage PTT with the command rigctl -m 2 -r localhost:4532 --skipinit T 1 and release it with rigctl -m 2 -r localhost:4532 --skipinit T 0. (as well as values 2 and 3, these all engage PTT as well.)

I've tried running rigctld with and without --vfo.

I suspect Hamlib is failing to initialise with the new release, and this is therefore why PTT is not working.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant