connecting Rpi5 runnning PiHPSDR to wsjt-x

[Rock Dubois]

Hello,

I have both PiHPSDR and wsjt-x running on my Pi 5 but couldn't find the settings to 

connect them.

I read that the radio should be selected as TS2000 and I matched the baud rate on 

both PiHPSDR and wsjt-x to 9600 baud.

The audio in and out shows a long list of devices and I couldn't find any information 

on which device to select.

Any help would be appreciated.

73, Yvon AE7YD

[DL1YCF]

This is explained in detail in the manual (Appendix F)
that is available on GitHub:

https://github.com/dl1ycf/pihpsdr/releases/download/current/piHPSDR-Manual.pdf

> --
> You received this message because you are subscribed to the Google Groups "Hermes-Lite" group.
> To unsubscribe from this group and stop receiving emails from it, send an email to hermes-lite...@googlegroups.com.
> To view this discussion visit https://groups.google.com/d/msgid/hermes-lite/abc7c24e-1f34-4b48-b52f-8bab7d7f79a5n%40googlegroups.com.

[Rock Dubois]

Thank you for the prompt reply.

This time I did reinstall it from sources and now it shows Audio Module: ALSA. However in wsjt-x I only see alsa_output_platfom_output.... no input.

In PiHPSDR RigCTRL I cannot enable any of the serial ports.

Yvon,

[Andrew Kovac]

Check which serial port you are using and type that in the tab.

You may need to add USER to dialout group in the Terminal.

Do a serach, but this should work;  sudo usermod -a -G dialout $USER

[DL1YCF]

This is not very helpful.

If piHPSDR and wsjtx are running on the
same machine, no serial port is used, the cat connection
goes via TCP.

> To view this discussion visit https://groups.google.com/d/msgid/hermes-lite/fc7125a5-8027-44d6-9cb8-e446aaf54363n%40googlegroups.com.

[DL1YCF]

> Am 16.11.2024 um 20:53 schrieb Rock Dubois <rockdub...@gmail.com>:
>
> Thank you for the prompt reply.
> This time I did reinstall it from sources and now it shows Audio Module: ALSA. However in wsjt-x I only see alsa_output_platfom_output.... no input.

You need to create ALSA „loopback“ devices used for connecting pihpsdr and wsjtx.

> In PiHPSDR RigCTRL I cannot enable any of the serial ports.
>

This is the expected behaviour if you have not connected any USB-to-Serial converters.
Connecting piHSPDR and wsjtx goes via TCP by the way.


Christoph

[Rock Dubois]

Thanks Christoph.

now I have the ALSO devices but they are both 'output'.

"alsa_output.platform-107c701400.hdmi.hdmi-hdmi-stereo.monitor"

and 

"alsa_output.platform-107c706400.hdmi.hdmi-hdmi-stereo"

In Radio I select Hamlib NET rigctl with the IP address of the PiHPSDR 192.168.1.22 and it comes back with a long connection error.

In PiHPSDR for Rigctl it shows "TCP 19090

Any other suggestion on what I might do wrong. SSH is enabled on the Pi  and I can SSH to the Pi from my PC.

Thanks and 73, Yvon

AE7YD

[Rock Dubois]

this is the error message:

Hamlib error: rig_set_conf called
rig_confparam_lookup called for 1073741834
rig_set_conf: rig_pathname='192.168.1.22'
rig_token_lookup called for no_xchg
rig_confparam_lookup called for no_xchg
 1:rig.c(817):rig_open entered
rig_settings_get_path: path=/home/pi/.config//home/pi/hamlib_settings
rig_settings_load_all: settings_file (/home/pi/.config//home/pi/hamlib_settings>
rig_open: cwd=/home/pi
rig_open: /home/pi/.config//home/pi/hamlib_settings does not exist
rig_open: async_data_enable=0, async_data_supported=0
rig_open: using network address 192.168.1.22
network_open: hoststr=192.168.1.22, portstr=
connect to 192.168.1.22 failed, (trying next interface): Network error 111: Con>
network_open: failed to connect to 192.168.1.22
rig_open: rs->comm_state==0?=0
 1:rig.c(1023):rig_open returning(-6) IO error

IO error
IO error
 while opening connection to rig

[Ron Lewkowicz]

In WSJT-X  for radio rig choose OpenHPSDR PIHPSDR.  Then set correct IP address and port configured in PiHPSDR.  I believe that you have this second part already correct.

[Rock Dubois]

Thanks Ron, but I already tried that and if I select OpenHPSDR PIHPSDRit shows the serial port selection or USB but NOT the IP address.

[Ron Lewkowicz]

In WSJT-X  just type your IP and port into the box that says serial port.

192.168.1.22:19090

It perhaps is an issue with WSJT-X  that it only shows serial and not network, but it does work.  I have tried Hamlib NET rigctl with PiHPSDR and it did not work. Must be OpenHPSDR PIHPSDR.  Hamlib NET rigctl works for Quisk.

Christoph had noticed that you had not specified the port correctly previously and sent a reply but it seems it did not come to the list. I got his email. Hopefully you did as well. For others future reference possible options to enter IP and port into that box are:

:19090

localhost:19090

or a specific host such as your case

192.168.1.22:19090

[Rock Dubois]

The problem is that the Hermes Lite 2+ is not working with virtual audio cable. I uses a different gateware and it is the same problem with Thetis and Sparksdr on the PC. I asked WA2T if he uses his Hermes Lite2+ with wsjt-x he replied that he himself doesn't do digital mode. And I didn't get anyone telling that they use the 2+ with wsjt-x.

I'll have to decide if I want to use physical cable or restore it to its original configuration and reprogram the FPGA.

Thanks to all who replied and helped.

["Christoph v. Wüllen"]

This is not true. Virtual audio cables are something on the host computer and
have nothing to do with HL2 or the HL2+.

If pihpsdr and wsjtx run on the *same* computer, then the virtual cable
just connects these two programs and no matter what radio is there.

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

> To view this discussion visit https://groups.google.com/d/msgid/hermes-lite/0772d059-86e9-4992-b0ab-9697873e3551n%40googlegroups.com.