PiHpSDR Rig selection not working

[Bill Diaz]

I am using FreeDV 2.1.0 with a Raspberry Pi 5 under Trixie and PIhPSDR 2.5.

If I select PiHpSDR as rig, I cannot control my Apache Labs 100D.  No PTT etc.
If I select Thetis or PowerSDR as rig, I can control my radio.  FreeDV works FB.

Possible HamLib issue?

Bill KC9XG

[Mooneer Salem]

Hi Bill, 

Are you using a virtual serial port or TCP/IP for rig control? Some radio types in hamlib can only do one or the other, so that may explain your issue. 

Thanks, 

-Mooneer K6AQ 

--
You received this message because you are subscribed to the Google Groups "digitalvoice" group.
To unsubscribe from this group and stop receiving emails from it, send an email to digitalvoice...@googlegroups.com.
To view this discussion visit https://groups.google.com/d/msgid/digitalvoice/fc8aa47d-606e-42e9-b101-a10dd517eb03n%40googlegroups.com.

[Bill Diaz]

Mooneer,

    Using TCP/IP exclusively with the Apache Labs ANAN-100D.  FreeDV TCP/IP works when selecting Thetis and PowerSDR but does not  work with PiHpSDR,

Bill KC9XG

[Rick Kunath]

It isn't possible that the hamlib versions are different somehow?

Rick Kunath, K9AO

[Bill Diaz]

Rick,

    Pretty sure FreeDV uses only 1 hamlib instance.  

    Switching FreeDV Rig selections only results in internal Hamlib rig ID changes.  Thetis uses ID 2054, PowerSDR uses 2048 and PiHpSDR uses ID 2040.  Seems like HamLib ID 2040 has issues in the version used by FreeDV.

Bill KC9XG

[Bill Diaz]

Mooneer,

WSJT-X 2.7.0 controls PiHpSDR/ANAN-100D without issue.  Test CAT returns green,  PTT test keys radio, QSY's as instructed by WSJT-X

  Uses HamLib 4.6.2 2025-02-09 T21:03:50Z SHA=870364 64-bit

Bill KC9XG

[Richard Lamont]

Bill,

I use FreeDV with piHPSDR on Linux Mint, using rigctld.

I start rigctld with these parameters:
rigctld -m 2040 -r 127.0.0.1:19090

And in FreeDV I set the rig model to "NET rigctl" and hostname:port to 127.0.0.1:4532

This is with hamlib 4.5.5

73,
Richard G4DYA

> --
> You received this message because you are subscribed to the Google Groups "digitalvoice" group.

> To unsubscribe from this group and stop receiving emails from it, send an email to digitalvoice...@googlegroups.com <mailto:digitalvoice...@googlegroups.com>.
> To view this discussion visit https://groups.google.com/d/msgid/digitalvoice/fc8aa47d-606e-42e9-b101-a10dd517eb03n%40googlegroups.com <https://groups.google.com/d/msgid/digitalvoice/fc8aa47d-606e-42e9-b101-a10dd517eb03n%40googlegroups.com?utm_medium=email&utm_source=footer>.

[Mooneer Salem]

Hi Bill,

FreeDV 2.1.0 uses Hamlib 4.6.5 on Windows and macOS, so it's very possible that it's a Hamlib problem. On Windows at least, you can try replacing the Hamlib DLL file in C:\Program Files\FreeDV 2.1.0\bin with an earlier version and seeing if that helps.

Thanks,

-Mooneer K6AQ

To unsubscribe from this group and stop receiving emails from it, send an email to digitalvoice...@googlegroups.com.
To view this discussion visit https://groups.google.com/d/msgid/digitalvoice/f1f1c60e-b1aa-4145-984b-8b2f1af7f0ac%40lamont.me.uk.

[Bill Diaz]

Mooneer,

  My installed FreeDV 2.1.0 is using HamLib 4.6.2 under Raspberry Pi Trixie Linux on a Raspberry Pi 5 and Raspberry Pi 500 with PiHpSDR 2.5 connected to Apache Labs 100D. 

 FreeDV is configured to use HamLib CAT Control, 127.0.0.1:19090, Rig model is OpenHpSDR PiHpSDR, PTT uses CAT via Data port and PiHpSDR is configured to accept CAT commands on that port.  Can QSY etc using FreeDV but cannot get to PTT to work when OpenHpSDR PiHpSDR Rig model is selected.

   Ran Update Rade and FreeDV 2.1.1 was installed, along with HamLib 4.6.5.

      FreeDV 2.1.1 with PiHpSDR rig selected cannot activate PTT,  QSY changes work as expected.

      FreeDV 2.1.1 with Thetis rig selected can activate PTT. 

      FreeDV 2.1.1 with PowerSDR rig selected can activate PTT.

  Shut down FreeDV.

 Ran WSJT-x 2.7.0 using hamlib 4.6.5

     WSJT-x with PiHpSDR selected can activate PTT.  

Shut down WSJT-x.

Ran FreeDV 2.1.1 again with OpenHpSDR PiHpSDR selected.   Terminal reports following :

12:34:09 [1] INFO /home/bill/freedv-rade/freedv-gui/src/main.cpp:509: FreeDV version 2.1.1-dev-1892 starting
12:34:09 [2] INFO /home/bill/freedv-rade/freedv-gui/src/topFrame.cpp:1044: Set voice keyer button label to Start Voice &Keyer
voicekeyer
12:34:09 [3] INFO /home/bill/freedv-rade/freedv-gui/src/main.cpp:1248: Using RADE API version 1

(freedv:2853): Gtk-WARNING **: 12:34:10.033: Negative content width -33 (allocation 1, extents 17x17) while allocating gadget (node button, owner GtkButton)
(freedv:2853): Gtk-WARNING **: 12:34:10.033: Negative content height -9 (allocation 1, extents 5x5) while allocating gadget (node button, owner GtkButton)

Activated PTT and terminal reported:

12:38:12 [42] INFO /home/bill/freedv-rade/freedv-gui/src/ongui.cpp:910: Waiting for EOO to be queued
12:38:12 [43] INFO /home/bill/freedv-rade/freedv-gui/src/ongui.cpp:918: Detected that EOO has been enqueued
12:38:12 [44] INFO /home/bill/freedv-rade/freedv-gui/src/ongui.cpp:942: All TX finished (diff = 439 ms, fifo_empty = 39240, sample = 39239), going out of PTT
12:38:12 [45] INFO /home/bill/freedv-rade/freedv-gui/src/ongui.cpp:980: Pausing for a minimum of 96098 us (19388 us latency + 76710 us PTT response time) before TX->RX to allow remaining audio to go out

However radio did not key.

If WSJT-x  can activate PiHpSDR PTT with HamLib 4.6.2 and HamLib 4.6.5 but FreeDV cannot activate PiHpSDR PTT using same hamlib versions,  it is likely not an issue with hamlib.  This is reinforced by the ability of FreeDV 2.10 or 2.1.1 to activate PiHpSDR PTT when selecting Thetis or PowerSDR as the rig to use with PiHpSDR running.  Thetis, PowerSDR and PiHpSDR use the same Kenwood PTT CAT command and hamlib PTT works with each off these apps  under WSJT-X, FLRig, FLDigi and more.   

Bill KC9XG

[Rick Kunath]

Bill,

What is keying the rig? A serial port or a virtual serial port or a USB
port on the right that looks like a serial port to hamlib?

Might it be that on the Pi your user is not in the user group that
allows serial port control? Probably it's the dialout group.

Rick Kunath, K9AO

[Bill Diaz]

Rick,

   As stated previously in this thread,  using CAT control via Hamlib, PTT uses "Cat Via Data port" via 127.0.0.1;19090. Not using serial ports whatsoever.

  FreeDV 2.1.0 and 2.1.1 HamLib cannot key PiHpSDR / ANAN-100D using OpenHpSDR PiHpSDR rig selection, but it can key it if I select Theris or PowerSDR rig selection in FreeDV.  

  PiHpSDR, Thetis and PowerSDR all use the same Kenwood CAT command to key the radio, TX; .

  WSJT-x / Hamlib can key PiHpSDR/ANAN-100D using PiHpSDR rig selection via data port at 127.0.0.1:19090.  Can key PiHpSDR by sending TX; CAT command using a telnet app connecting to 127.0.0.1:19090.  0 problems with connections to PiHpSDR.   Can QSY etc with FreeDV, WSJTx and telnet app.

Appears to be a PTT only issue with the PiHpSDR rig selection in FreeDV since TX; works with PiHpSDR rig selection in WSJT-x, and the telnet  app.  

Bill KC9XG

[Mooneer Salem]

Hi Bill,

Apologies, I missed the Linux reference in the original email. (I've been traveling for the Thanksgiving holiday and have had limited access to internet.)

Would it be possible to do the following:

1. Go to Tools->Options->Debugging and check the Verbose checkbox.

2. Reconfigure FreeDV to use piHPSDR as the rig type.

3. Attempt to use FreeDV.

4. Copy/paste the console output into a text file and send this to me.

Thanks,

-Mooneer K6AQ

--

You received this message because you are subscribed to the Google Groups "digitalvoice" group.
To unsubscribe from this group and stop receiving emails from it, send an email to digitalvoice...@googlegroups.com.

To view this discussion visit https://groups.google.com/d/msgid/digitalvoice/483a63c2-ecb5-4653-9512-0a37acd1e1dbn%40googlegroups.com.