masters board issue with ptt

[Moore Atak]

Running DigiPi 2.1-BETA3 on a Pi Zero 2W with a Masters Communications DRA-Pi-Zero HAT (Audio Injector / WM8731, GPIO 12 PTT relay), driving a (tr)uSDX through a DigiRig uSDX cable. This is a type-B / no-CAT build — the truSDX's USB serial isn't connected, so SysInfo shows "no serial devices." Trying to get WSJT-X FT8 transmit working via GPIO 12 PTT.

WHAT WORKS:
- RX is solid, decoding FT8 fine. Sound card shows as audioinjector-pi-soundcard (card 0).
- To get the card to come up I manually edited /boot/firmware/config.txt to use dtoverlay=audioinjector-wm8731-audio (commented out the fe-pi line).
- Manually keying the relay works perfectly: `pinctrl set 12 op dh` puts the truSDX into TX (red PTT LED on), `pinctrl set 12 op dl` releases. So the hardware PTT path is confirmed good.

THE PROBLEM — WSJT-X won't key on transmit:
- In localize.env I set NEWRIGNUMBER=GPIO. NEWI2CAUDIO is still =fepi (wasn't sure of the right value for the Audio Injector / DRA-Pi-Zero board).
- After reboot, `ps aux | grep rigctl` shows no rigctld running.
- WSJT-X > Settings > Radio shows Rig=None, PTT=VOX.
- As a test I started rigctld manually for GPIO PTT: `rigctld -m 1 -P GPIO -p 12`. It errors with:
  "GPIO12 direction (using /sys/class/gpio/gpio12/direction): No such file or directory — cannot open PTT device GPIO12"
  Looks like Hamlib's old sysfs GPIO method isn't available on this kernel (the /sys/class/gpio interface is gone in favor of gpiochip/libgpiod), so stock rigctld can't key GPIO here.

QUESTIONS:
1. What's the correct NEWI2CAUDIO value for the DRA-Pi-Zero / Audio Injector board?
2. Does GPIO 12 PTT require a full Initialize to wire up the PTT service, or should NEWRIGNUMBER=GPIO read at runtime be enough? (My OLD values in localize.env are stale placeholders, so I held off on running Initialize.)
3. How should the WSJT-X Radio tab be set (Rig / PTT Method) to reach the GPIO 12 PTT on 2.1-BETA3?

Everything points to the hardware being fine — it's just the WSJT-X to GPIO 12 PTT bridge I can't get wired up on this build. Any pointers appreciated.

[Craig]

Hi Moore,

the Initialize values have nothing to do with wsjtx, it drives hamlib
directly.

The Linux kernel developers destroyed all GPIO api's, again, and a lot
of software just can't keep up.  I suspect wsjtx falls in this category.

You might try DigiPi 2.1 (secretly released), as it includes wsjtx 3.0.1.

-craig
KM6LYW

[Moore Atak]

Thanks for the quick reply, i just updated to new version wsjtx still no go as it kept same version of hamlib but was able to program in keying ptt for js8 at least

[Damon Leibert]

Same issue for me running Raspi Zero 2 W with the DRA-Pi-Zero_REV2 hat.   Running Digipi 2.1.  Direwolf keys TX when it should, but WSJT-X and Fldigi are not able to key PTT.   Am I on a "wild goose chase?" or does it work and if so what is the default config settings for this setup *when not using a CAT controlled radio*.   This does not appear to be hardware as Direwolf is working fine.

73 Damon N1LJK

[Craig]

Hi guys,

the linux kernel guys break the GPIO api with every release so every app
and every document stops working.  Fldigi doens't yet support the new
"gpiod" gpio model.

I'm curious what mode are you using in fldigi that needs gpio ptt?

Rigctld might support the new gpio api, check /etc/systemd/system/rigcltd.service
to have rigctld possibly drive the pin, and fldigi would use hamlib/rigctld.

--
You received this message because you are subscribed to the Google Groups "DigiPi" group.
To unsubscribe from this group and stop receiving emails from it, send an email to digipi+un...@googlegroups.com.
To view this discussion visit https://groups.google.com/d/msgid/digipi/82e32a01-2033-4f12-8c80-8dbc3c1f96f5n%40googlegroups.com.