¿ªÔÆÌåÓý


fldigi / flrig Pi Question

 

Question for any fldigi / flrig gurus. I installed both on a new Raspberry Pi 5 using the ¡°add /remove software ¡° available in the GUI. Noticed that my FT-710 wasn¡¯t supported, further investigation shows that I am running version 1.4.7 of flrig. I believe the latest is 2.2 - so I tried : sudo apt-get -y flrig. The system tells me that I already have the latest version 1.4.7¨C1. ? am I correct that there¡¯s a more recent version. Also, I posted a question about this on facebook and was told the FT-710 was not supported on any version of flrig - is this correct? If it is supported, how do I get the latest version. Please keep in mind I am a Pi novice.....
Any guidance would be greatly appreciated


Re: 2B direwolf gpio errors

 

¿ªÔÆÌåÓý

Hello Jim,

You need to install the required dependency packages and then compile the Direwolf 1.8-DEV (not 1.6) meaning the DEV branch of Direwolf:

??

--David
KI6ZHD


On 07/24/2024 08:44 PM, Jim KX0U wrote:

Thanks, David, for the information.

I have compiled direwolf 1.6 according to the steps listed in the PDF you provided a link to.? However, I didn't get the "Includes optional support for:? libgpiod" I should have.? (I did successfully install gpiod and libgpiod-dev prior to building direwolf.)

Can anyone recommend additional steps I should take to get the required support compiled into direwolf?

73,
Jim? KX0U

On Wed, Jul 24, 2024 at 9:02?AM David Ranch via <rpi4hamradio-groupsio=[email protected]> wrote:

Hello Jim,

A recent Raspberry Pi OS upgrade made many disruptive changes including deprecating the old way of interfacing to the GPIO pins.? To resolve this for Direwolf you need to compile a new Direwolf using the Direwolf DEV branch which will bring you up to the 1.8-D version:

?? Section 7.2.2
??

--David
KI6ZHD


On 07/23/2024 09:49 PM, Jim KX0U wrote:
I'm getting an error when I try to use direwolf with GPIO configured for PTT.
I'm running Raspberry Pi OS on a Pi 2B.

Raspberry Pi OS with desktop and recommended software

    Release date: July 4th 2024
    System: 32-bit
    Kernel version: 6.6
    Debian version: 12 (bookworm)

Any suggestions for troubleshooting or alternatives would be appreciated.

$ cat direwolf.conf
PTT GPIO 13
ADEVICE plughw:2,0

$ direwolf
Dire Wolf version 1.6
Includes optional support for:  gpsd hamlib cm108-ptt

Reading config file direwolf.conf
Audio device for both receive and transmit: plughw:2,0  (channel 0)
Channel 0: 1200 baud, AFSK 1200 & 2200 Hz, E+, 44100 sample rate / 3.
Error writing "13" to /sys/class/gpio/export, errno=22
Invalid argument

$ sudo direwolf -c ~/direwolf.conf
Dire Wolf version 1.6
Includes optional support for:  gpsd hamlib cm108-ptt

Reading config file /home/radio/direwolf.conf
Audio device for both receive and transmit: plughw:2,0  (channel 0)
Channel 0: 1200 baud, AFSK 1200 & 2200 Hz, E+, 44100 sample rate / 3.
Error writing "13" to /sys/class/gpio/export, errno=22
Invalid argument

$ ls -ld /sys /sys/class /sys/class/gpio /sys/class/gpio/export
dr-xr-xr-x 12 root root    0 Dec 31  1969 /sys
drwxr-xr-x 59 root root    0 Dec 31  1969 /sys/class
drwxrwxr-x  2 root gpio    0 Jul 23 22:32 /sys/class/gpio
--w--w----  1 root gpio 4096 Jul 23 22:32 /sys/class/gpio/export

$ ls -l /sys/class/gpio/
total 0
--w--w---- 1 root gpio 4096 Jul 23 22:32 export
lrwxrwxrwx 1 root gpio    0 Jul 23 22:32 gpiochip512 -> ../../devices/platform/soc/3f200000.gpio/gpio/gpiochip512
lrwxrwxrwx 1 root gpio    0 Jul 23 22:32 gpiochip566 -> ../../devices/platform/soc/3f980000.usb/usb1/1-1/1-1.5/1-1.5.2/1-1.5.2:1.0/gpio/gpiochip566
--w--w---- 1 root gpio 4096 Jul 23 22:32 unexport

$ lsmod | grep gpio
raspberrypi_gpiomem    12288  0

$








Re: 2B direwolf gpio errors

 

Thanks, David, for the information.

I have compiled direwolf 1.6 according to the steps listed in the PDF you provided a link to.? However, I didn't get the "Includes optional support for:? libgpiod" I should have.? (I did successfully install gpiod and libgpiod-dev prior to building direwolf.)

Can anyone recommend additional steps I should take to get the required support compiled into direwolf?

73,
Jim? KX0U

On Wed, Jul 24, 2024 at 9:02?AM David Ranch via <rpi4hamradio-groupsio=[email protected]> wrote:


Hello Jim,

A recent Raspberry Pi OS upgrade made many disruptive changes including deprecating the old way of interfacing to the GPIO pins.? To resolve this for Direwolf you need to compile a new Direwolf using the Direwolf DEV branch which will bring you up to the 1.8-D version:

?? Section 7.2.2
??

--David
KI6ZHD


On 07/23/2024 09:49 PM, Jim KX0U wrote:
I'm getting an error when I try to use direwolf with GPIO configured for PTT.
I'm running Raspberry Pi OS on a Pi 2B.

Raspberry Pi OS with desktop and recommended software

    Release date: July 4th 2024
    System: 32-bit
    Kernel version: 6.6
    Debian version: 12 (bookworm)

Any suggestions for troubleshooting or alternatives would be appreciated.

$ cat direwolf.conf
PTT GPIO 13
ADEVICE plughw:2,0

$ direwolf
Dire Wolf version 1.6
Includes optional support for:  gpsd hamlib cm108-ptt

Reading config file direwolf.conf
Audio device for both receive and transmit: plughw:2,0  (channel 0)
Channel 0: 1200 baud, AFSK 1200 & 2200 Hz, E+, 44100 sample rate / 3.
Error writing "13" to /sys/class/gpio/export, errno=22
Invalid argument

$ sudo direwolf -c ~/direwolf.conf
Dire Wolf version 1.6
Includes optional support for:  gpsd hamlib cm108-ptt

Reading config file /home/radio/direwolf.conf
Audio device for both receive and transmit: plughw:2,0  (channel 0)
Channel 0: 1200 baud, AFSK 1200 & 2200 Hz, E+, 44100 sample rate / 3.
Error writing "13" to /sys/class/gpio/export, errno=22
Invalid argument

$ ls -ld /sys /sys/class /sys/class/gpio /sys/class/gpio/export
dr-xr-xr-x 12 root root    0 Dec 31  1969 /sys
drwxr-xr-x 59 root root    0 Dec 31  1969 /sys/class
drwxrwxr-x  2 root gpio    0 Jul 23 22:32 /sys/class/gpio
--w--w----  1 root gpio 4096 Jul 23 22:32 /sys/class/gpio/export

$ ls -l /sys/class/gpio/
total 0
--w--w---- 1 root gpio 4096 Jul 23 22:32 export
lrwxrwxrwx 1 root gpio    0 Jul 23 22:32 gpiochip512 -> ../../devices/platform/soc/3f200000.gpio/gpio/gpiochip512
lrwxrwxrwx 1 root gpio    0 Jul 23 22:32 gpiochip566 -> ../../devices/platform/soc/3f980000.usb/usb1/1-1/1-1.5/1-1.5.2/1-1.5.2:1.0/gpio/gpiochip566
--w--w---- 1 root gpio 4096 Jul 23 22:32 unexport

$ lsmod | grep gpio
raspberrypi_gpiomem    12288  0

$







Re: 2B direwolf gpio errors

 

Another option is downgrading the kernel to 6.1.74 which was the last kernel with the deprecated GPIO. A lot more software will be affected for GPIO access and this fix will fix it for all
sudo rpi-update d86b5843d68b9972a5430a6d3da1b271cfc83521



Get
On Jul 24, 2024, at 07:02, "David Ranch via " <trinnet.net@groups.io target=_blank>[email protected]> wrote:


Hello Jim,

A recent Raspberry Pi OS upgrade made many disruptive changes including deprecating the old way of interfacing to the GPIO pins.? To resolve this for Direwolf you need to compile a new Direwolf using the Direwolf DEV branch which will bring you up to the 1.8-D version:

?? Section 7.2.2
??

--David
KI6ZHD


On 07/23/2024 09:49 PM, Jim KX0U wrote:
I'm getting an error when I try to use direwolf with GPIO configured for PTT.
I'm running Raspberry Pi OS on a Pi 2B.

Raspberry Pi OS with desktop and recommended software

    Release date: July 4th 2024
    System: 32-bit
    Kernel version: 6.6
    Debian version: 12 (bookworm)

Any suggestions for troubleshooting or alternatives would be appreciated.

$ cat direwolf.conf
PTT GPIO 13
ADEVICE plughw:2,0

$ direwolf
Dire Wolf version 1.6
Includes optional support for:  gpsd hamlib cm108-ptt

Reading config file direwolf.conf
Audio device for both receive and transmit: plughw:2,0  (channel 0)
Channel 0: 1200 baud, AFSK 1200 & 2200 Hz, E+, 44100 sample rate / 3.
Error writing "13" to /sys/class/gpio/export, errno=22
Invalid argument

$ sudo direwolf -c ~/direwolf.conf
Dire Wolf version 1.6
Includes optional support for:  gpsd hamlib cm108-ptt

Reading config file /home/radio/direwolf.conf
Audio device for both receive and transmit: plughw:2,0  (channel 0)
Channel 0: 1200 baud, AFSK 1200 & 2200 Hz, E+, 44100 sample rate / 3.
Error writing "13" to /sys/class/gpio/export, errno=22
Invalid argument

$ ls -ld /sys /sys/class /sys/class/gpio /sys/class/gpio/export
dr-xr-xr-x 12 root root    0 Dec 31  1969 /sys
drwxr-xr-x 59 root root    0 Dec 31  1969 /sys/class
drwxrwxr-x  2 root gpio    0 Jul 23 22:32 /sys/class/gpio
--w--w----  1 root gpio 4096 Jul 23 22:32 /sys/class/gpio/export

$ ls -l /sys/class/gpio/
total 0
--w--w---- 1 root gpio 4096 Jul 23 22:32 export
lrwxrwxrwx 1 root gpio    0 Jul 23 22:32 gpiochip512 -> ../../devices/platform/soc/3f200000.gpio/gpio/gpiochip512
lrwxrwxrwx 1 root gpio    0 Jul 23 22:32 gpiochip566 -> ../../devices/platform/soc/3f980000.usb/usb1/1-1/1-1.5/1-1.5.2/1-1.5.2:1.0/gpio/gpiochip566
--w--w---- 1 root gpio 4096 Jul 23 22:32 unexport

$ lsmod | grep gpio
raspberrypi_gpiomem    12288  0

$







Re: 2B direwolf gpio errors

 

¿ªÔÆÌåÓý


Hello Jim,

A recent Raspberry Pi OS upgrade made many disruptive changes including deprecating the old way of interfacing to the GPIO pins.? To resolve this for Direwolf you need to compile a new Direwolf using the Direwolf DEV branch which will bring you up to the 1.8-D version:

?? Section 7.2.2
??

--David
KI6ZHD


On 07/23/2024 09:49 PM, Jim KX0U wrote:

I'm getting an error when I try to use direwolf with GPIO configured for PTT.
I'm running Raspberry Pi OS on a Pi 2B.

Raspberry Pi OS with desktop and recommended software

    Release date: July 4th 2024
    System: 32-bit
    Kernel version: 6.6
    Debian version: 12 (bookworm)

Any suggestions for troubleshooting or alternatives would be appreciated.

$ cat direwolf.conf
PTT GPIO 13
ADEVICE plughw:2,0

$ direwolf
Dire Wolf version 1.6
Includes optional support for:  gpsd hamlib cm108-ptt

Reading config file direwolf.conf
Audio device for both receive and transmit: plughw:2,0  (channel 0)
Channel 0: 1200 baud, AFSK 1200 & 2200 Hz, E+, 44100 sample rate / 3.
Error writing "13" to /sys/class/gpio/export, errno=22
Invalid argument

$ sudo direwolf -c ~/direwolf.conf
Dire Wolf version 1.6
Includes optional support for:  gpsd hamlib cm108-ptt

Reading config file /home/radio/direwolf.conf
Audio device for both receive and transmit: plughw:2,0  (channel 0)
Channel 0: 1200 baud, AFSK 1200 & 2200 Hz, E+, 44100 sample rate / 3.
Error writing "13" to /sys/class/gpio/export, errno=22
Invalid argument

$ ls -ld /sys /sys/class /sys/class/gpio /sys/class/gpio/export
dr-xr-xr-x 12 root root    0 Dec 31  1969 /sys
drwxr-xr-x 59 root root    0 Dec 31  1969 /sys/class
drwxrwxr-x  2 root gpio    0 Jul 23 22:32 /sys/class/gpio
--w--w----  1 root gpio 4096 Jul 23 22:32 /sys/class/gpio/export

$ ls -l /sys/class/gpio/
total 0
--w--w---- 1 root gpio 4096 Jul 23 22:32 export
lrwxrwxrwx 1 root gpio    0 Jul 23 22:32 gpiochip512 -> ../../devices/platform/soc/3f200000.gpio/gpio/gpiochip512
lrwxrwxrwx 1 root gpio    0 Jul 23 22:32 gpiochip566 -> ../../devices/platform/soc/3f980000.usb/usb1/1-1/1-1.5/1-1.5.2/1-1.5.2:1.0/gpio/gpiochip566
--w--w---- 1 root gpio 4096 Jul 23 22:32 unexport

$ lsmod | grep gpio
raspberrypi_gpiomem    12288  0

$







Re: 2B direwolf gpio errors

 

I think this is the same issue.? Might give it a try on Debian version: 11 (bullseye).
?
Hope this helps...


2B direwolf gpio errors

 

I'm getting an error when I try to use direwolf with GPIO configured for PTT.
I'm running Raspberry Pi OS on a Pi 2B.

Raspberry Pi OS with desktop and recommended software

Release date: July 4th 2024
System: 32-bit
Kernel version: 6.6
Debian version: 12 (bookworm)

Any suggestions for troubleshooting or alternatives would be appreciated.

$ cat direwolf.conf
PTT GPIO 13
ADEVICE plughw:2,0

$ direwolf
Dire Wolf version 1.6
Includes optional support for: gpsd hamlib cm108-ptt

Reading config file direwolf.conf
Audio device for both receive and transmit: plughw:2,0 (channel 0)
Channel 0: 1200 baud, AFSK 1200 & 2200 Hz, E+, 44100 sample rate / 3.
Error writing "13" to /sys/class/gpio/export, errno=22
Invalid argument

$ sudo direwolf -c ~/direwolf.conf
Dire Wolf version 1.6
Includes optional support for: gpsd hamlib cm108-ptt

Reading config file /home/radio/direwolf.conf
Audio device for both receive and transmit: plughw:2,0 (channel 0)
Channel 0: 1200 baud, AFSK 1200 & 2200 Hz, E+, 44100 sample rate / 3.
Error writing "13" to /sys/class/gpio/export, errno=22
Invalid argument

$ ls -ld /sys /sys/class /sys/class/gpio /sys/class/gpio/export
dr-xr-xr-x 12 root root 0 Dec 31 1969 /sys
drwxr-xr-x 59 root root 0 Dec 31 1969 /sys/class
drwxrwxr-x 2 root gpio 0 Jul 23 22:32 /sys/class/gpio
--w--w---- 1 root gpio 4096 Jul 23 22:32 /sys/class/gpio/export

$ ls -l /sys/class/gpio/
total 0
--w--w---- 1 root gpio 4096 Jul 23 22:32 export
lrwxrwxrwx 1 root gpio 0 Jul 23 22:32 gpiochip512 -> ../../devices/platform/soc/3f200000.gpio/gpio/gpiochip512
lrwxrwxrwx 1 root gpio 0 Jul 23 22:32 gpiochip566 -> ../../devices/platform/soc/3f980000.usb/usb1/1-1/1-1.5/1-1.5.2/1-1.5.2:1.0/gpio/gpiochip566
--w--w---- 1 root gpio 4096 Jul 23 22:32 unexport

$ lsmod | grep gpio
raspberrypi_gpiomem 12288 0

$


Messaaages to group

 

¿ªÔÆÌåÓý




From:[email protected] <[email protected]> on behalf of KJ7QQG via groups.io <jpradiophone@...>
Sent:?09 July 2024 4:28
To:[email protected] <[email protected]>
Subject:?[RaspberryPi-4-HamRadio] email
?
email to verify


Larry Taylor
K5LLT
TaylorHere@...



Re: Pi-5 problem

 

¿ªÔÆÌåÓý

Thanks for your help Spence.? What is strange is that today, after the pi-5 was set aside over night, I seems to work fine.? I was able to get your Email and am about to send this on the Pi-5.

I hope the intimation here is what you wanted.? I is what I have this morning with the Pi-5 working.? There is no 169.24.XXX>XXX address.


$ sudo ifconfig

eth0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500

inet (address) netmask (address) broadcast (address)

inet6 (device in hex) prefixlen 64 scopeid (2 digit hex)<link>

ether (device in hex) txqueuelen (number removed)) (Ethernet)

RX packets 703 bytes 409541 (399.9 KiB)

RX errors 0 dropped 0 overruns 0 frame 0

TX packets 569 bytes 108931 (106.3 KiB)

TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0

device interrupt 112

I'm not sure this information will be useful as the Pi-5 seems to be working right now.

John,? WoGN

On 2024-07-13 17:30, Spence G5STO via groups.io wrote:

Try opening a terminal windows and typing -
?
ifconfig?
?
This should show you your network settings. I can almost guarantee that you will be missing IPV4 address but have IPV6.?
?
? If so then you will have to edit the DHCP setting s and assign a static IPv4 address as the negotiation between your Pi and router isn't allowing you IPV6 pass through.?
?
?Naturally is it is working you will have 192.168.1.10 for example or 192.168.0.10.
?
If you have 169.254.???.??? Then your Pi has failed to get a valid DHCP address from your router. (Anything from IP conflict to even a network cable is damaged, yeah I've had that before).
?
? First off though go to a terminal and type?
?
Ifconfig ?(or sudo ifconfig if it's asking for elevation).
?
Report back here of post ad screen short of the results.
?
De Spence G5STO
?
Sent while portable! please excuse typos.

On 13 Jul 2024, at 22:46, N5XMT via groups.io <dacooley@...> wrote:

Definitely odd. I've seen that wit WiFi before, but not Ethernet

Get
On Jul 13, 2024, at 14:27, "John via " <netins.net@groups.io target=_blank>[email protected]> wrote:

Ethernet


On 2024-07-13 14:30, N5XMT wrote:

Wifi or Ethernet?

Get
On Jul 13, 2024, at 10:55, "John via " <netins.net@groups.io target=_blank>[email protected]> wrote:
Using an 8GB pi-5 with NVme & SD card Problem with network??
Can someone figure out what is wrong from this, the only clue I found?
If I hold down the shift key and use key to reformat the SD card and then let it boot it works FB.
However, after I shut down the Pi and later boot it it can't find the internet (although the terminal does download very slowly).
OS is Bookworm 64.


Re: email

 


From: [email protected] <[email protected]> on behalf of KJ7QQG via groups.io <jpradiophone@...>
Sent: 09 July 2024 4:28
To: [email protected] <[email protected]>
Subject: [RaspberryPi-4-HamRadio] email
?
email to verify


Re: Pi-5 problem

 

¿ªÔÆÌåÓý

Try opening a terminal windows and typing -

ifconfig?

This should show you your network settings. I can almost guarantee that you will be missing IPV4 address but have IPV6.?

? If so then you will have to edit the DHCP setting s and assign a static IPv4 address as the negotiation between your Pi and router isn¡¯t allowing you IPV6 pass through.?

?Naturally is it is working you will have 192.168.1.10 for example or 192.168.0.10.

If you have 169.254.???.??? Then your Pi has failed to get a valid DHCP address from your router. (Anything from IP conflict to even a network cable is damaged, yeah I¡¯ve had that before).

? First off though go to a terminal and type?

Ifconfig ?(or sudo ifconfig if it¡¯s asking for elevation).

Report back here of post ad screen short of the results.

De Spence G5STO

Sent while portable! please excuse typos.

On 13 Jul 2024, at 22:46, N5XMT via groups.io <dacooley@...> wrote:

?
Definitely odd. I've seen that wit WiFi before, but not Ethernet

Get
On Jul 13, 2024, at 14:27, "John via " <netins.net@groups.io target=_blank>[email protected]> wrote:

Ethernet


On 2024-07-13 14:30, N5XMT wrote:

Wifi or Ethernet?

Get
On Jul 13, 2024, at 10:55, "John via " <netins.net@groups.io target=_blank>[email protected]> wrote:
Using an 8GB pi-5 with NVme & SD card Problem with network??
Can someone figure out what is wrong from this, the only clue I found?
If I hold down the shift key and use key to reformat the SD card and then let it boot it works FB.
However, after I shut down the Pi and later boot it it can't find the internet (although the terminal does download very slowly).
OS is Bookworm 64.


Re: Pi-5 problem

 

Definitely odd. I've seen that wit WiFi before, but not Ethernet

Get
On Jul 13, 2024, at 14:27, "John via " <netins.net@groups.io target=_blank>[email protected]> wrote:

Ethernet


On 2024-07-13 14:30, N5XMT wrote:

Wifi or Ethernet?

Get
On Jul 13, 2024, at 10:55, "John via " <netins.net@groups.io target=_blank>[email protected]> wrote:
Using an 8GB pi-5 with NVme & SD card Problem with network??
Can someone figure out what is wrong from this, the only clue I found?
If I hold down the shift key and use key to reformat the SD card and then let it boot it works FB.
However, after I shut down the Pi and later boot it it can't find the internet (although the terminal does download very slowly).
OS is Bookworm 64.


Re: Pi-5 problem

 

¿ªÔÆÌåÓý

Ethernet


On 2024-07-13 14:30, N5XMT wrote:

Wifi or Ethernet?

Get
On Jul 13, 2024, at 10:55, "John via " <netins.net@groups.io target=_blank>[email protected]> wrote:
Using an 8GB pi-5 with NVme & SD card Problem with network??
Can someone figure out what is wrong from this, the only clue I found?
If I hold down the shift key and use key to reformat the SD card and then let it boot it works FB.
However, after I shut down the Pi and later boot it it can't find the internet (although the terminal does download very slowly).
OS is Bookworm 64.


Re: Pi-5 problem

 

Wifi or Ethernet?

Get
On Jul 13, 2024, at 10:55, "John via " <netins.net@groups.io target=_blank>[email protected]> wrote:

Using an 8GB pi-5 with NVme & SD card Problem with network??
Can someone figure out what is wrong from this, the only clue I found?
If I hold down the shift key and use key to reformat the SD card and then let it boot it works FB.
However, after I shut down the Pi and later boot it it can't find the internet (although the terminal does download very slowly).
OS is Bookworm 64.


Pi-5 problem

 

Using an 8GB pi-5 with NVme & SD card Problem with network??
Can someone figure out what is wrong from this, the only clue I found?
If I hold down the shift key and use key to reformat the SD card and then let it boot it works FB.
However, after I shut down the Pi and later boot it it can't find the internet (although the terminal does download very slowly).
OS is Bookworm 64.


email

 

email to verify


Testers and server hosters needed for Radio Web Services (RWS) project #hf #resources #software

 

The RWS project allows anyone using an HF radio and a computer to access the internet from anywhere if needed, either because of an emergency or if you simply go somewhere that doesn't have internet.

The current implementation of the server uses the VARA modem, which is free, though the uncapped speed version costs $70. (But, if you call CQ and a server with a licensed copy of VARA answers, there won't be any restrictions, and vice versa for any unlicensed server hosters)

The server has a lot of built-in commands which allow you to:
  • View a website (either in plain text or raw HTML)
  • Perform a quick search
  • Get the weather forecast for a given city + state
  • Download a given URL (download is encoded into base64 to allow download through text, instructions for how to decode are given alongside the download)
  • View and create threads and comments in the community section of the GitHub of the project
  • Print server info, logs, and global active servers

I've read Part 97 of the FCC and I've made sure my server is fully legal.

My end goal for the project is to have hundreds or thousands of servers hosted around the world, which would allow coverage for almost everyone on Earth.

The server and instructions for how to host your own are listed at the GitHub:


To connect to a server, make sure you have VARA and VarAC installed. Once those are installed and working correctly, go to 14.110 MHz USB and call CQ. (Both 500 Hz and 2300 Hz bandwidths are supported.) Wait for at least 2 minutes. If a server has heard you, it will call back and try to connect with you. The list of commands and other instructions are sent once you're connected.

I need testers and server hosters to properly see if the server will work correctly in the real world! If you aren't using your radio at the moment, and if you have a computer connected to the radio, you can get the server running in 10 minutes and just let it sit in the background, waiting for a connection, with no further hassle needed.

If you want an external helper for dealing with the downloads and base64, KC3VPB has created a helper that can decode base64 automatically and save it to a file.


For more info or if you need help, email me:
jpradiophone@...

RWS Discord invite link:
https://discord.gg/muYEBCjqsM


Re: Open Repeater

 

¿ªÔÆÌåÓý

Hey Bill,

Glad we could help.

There are also a bunch of .tcl files associated with the PHP web stuff.

They are located in /usr/share/svxlink under events.d and modules.d

I seem to remember having a similar problem with web settings not getting saved.?

There is an openrepeater forum located at:


Aaron (N3MBH) and Dan (KG7PAR) are very helpful in answering questions.

Your W8COD QRZ page is very interesting.

-Gregg WB6YAZ


From: [email protected] <[email protected]> on behalf of Box1600 <box1600@...>
Sent: Sunday, June 23, 2024 8:36 PM
To: [email protected] <[email protected]>
Subject: Re: [RaspberryPi-4-HamRadio] Open Repeater
?
Hi Gregg,

You conf file example helped me figure it out.

Apparently, the web interface in NOT updating the TIMEOUT value in the port setup.

I manually edited the file and set the timeout to 15, saved and rebooted.

Sure enough, the controller timed-out and the PTT line dropped after 15 seconds.

After playing around and testing with different values the timeout does work as expected if you manually edit the config file.

Now to look at the PHP/JS scripts to see why the timeout value isn't saved from the web interface.

So anyway, the TIMEOUT is now set to 150 seconds (2-1/2 minutes) and working great.

I appreciate you and everyone else that took the time to answer my plea for help.


For anyone interested, I am the Chief Radio Operator aboard the American Submarine USS COD SS-224.

We operate on the ham bands using the call sign W8COD.

Check out the COD's qrz page at:


Scroll down about half way through the page for links to some really cool pictures and videos.

Again, thanks for all the help.

73 - BILL KA8VIT / W8COD
W8COD personal biography
www.qrz.com



From:[email protected] <[email protected]> on behalf of Gregg Daugherty <gregg-daugherty@...>
Sent:?Saturday, June 22, 2024 6:41 AM
To:[email protected] <[email protected]>
Subject:?Re: [RaspberryPi-4-HamRadio] Open Repeater
?
Take a look at /etc/svxlink/svxlink.conf



Below is my TX section info.



On 6/20/2024 7:49 PM, Box1600 wrote:
It has nothing to do with the repeater, (which is an MTR-2000).

In testing the software we found that the GPIO output that controls the PTT line never unkeys if the COS signal is held active longer than the set timeout period.

Everything else seems to works as it should.

Thanks, I'll check out that SXVLINK group.

73 - BILL KA8VIT



From:?[email protected] <[email protected]>?on behalf of Teton Amateur Radio Repeater Association (TARRA) <tarra@...>
Sent:?Wednesday, June 19, 2024 11:04 PM
To:?[email protected] <[email protected]>
Subject:?Re: [RaspberryPi-4-HamRadio] Open Repeater
?

Hello Bill,

With this being the issue, it be helpful to know what you are using for a repeater.

You may also want to ask the question at the svxlink at groups.io? /g/svxlink

Mick - W7CAT



Re: Can't delete WSJT-X Improved #rpi5 #software

 

¿ªÔÆÌåÓý

The touch command followed by remove-purge fixed the problem and I¡¯ve been able to install all of the updates. Thanks for your help!

On Jun 22, 2024, at 12:07?PM, Gary Rogers via groups.io <cgaryrogers190@...> wrote:

Thanks. It¡¯s the WSJT-X improved arm64.deb file using the Package Installer. I¡¯ll try this and let you know.

On Jun 22, 2024, at 11:35?AM, David Ranch via groups.io <rpi4hamradio-groupsio@...> wrote:


Where did you get and install this wsjtx package from?? It clearly has issues if it's trying to uninstall things from /tmp.? Anyway, I've dealt with similar issues by simply re-creating the "missing" files and then retry the uninstallation:

??touch /tmp/wsjtx-install-home.txt
???
sudo apt remove --purge wsjtx

--David
KI6ZHD


On 06/21/2024 07:18 AM, Gary Rogers wrote:
I¡¯m trying to remove WSJT-X Improved from my Pi 400 running Bookworm. I get the following when trying to remove/purge:

pi@KO3F:~ $ sudo apt remove --purge wsjtx
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
The following packages will be REMOVED:
?wsjtx
0 upgraded, 0 newly installed, 1 to remove and 53 not upgraded.
1 not fully installed or removed.
After this operation, 60.0 MB disk space will be freed.
Do you want to continue? [Y/n] y
(Reading database ... 149492 files and directories currently installed.)
Removing wsjtx (2.7.1-devel) ...
cat: /tmp/wsjtx-install-home.txt: No such file or directory
rm: cannot remove '/tmp/wsjtx-install-home.txt': No such file or directory
dpkg: error processing package wsjtx (--remove):
installed wsjtx package post-removal script subprocess returned error exit status 1
dpkg: too many errors, stopping
Errors were encountered while processing:
wsjtx
Processing was halted because there were too many errors.
E: Sub-process /usr/bin/dpkg returned an error code (1)
pi@KO3F:~ $?

Can anyone provide a solution as to how to completely remove the program without reimagine the SD card? I can¡¯t upgrade any packages until this is resolved. Thanks




Re: Open Repeater

 

¿ªÔÆÌåÓý

Hi Gregg,

You conf file example helped me figure it out.

Apparently, the web interface in NOT updating the TIMEOUT value in the port setup.

I manually edited the file and set the timeout to 15, saved and rebooted.

Sure enough, the controller timed-out and the PTT line dropped after 15 seconds.

After playing around and testing with different values the timeout does work as expected if you manually edit the config file.

Now to look at the PHP/JS scripts to see why the timeout value isn't saved from the web interface.

So anyway, the TIMEOUT is now set to 150 seconds (2-1/2 minutes) and working great.

I appreciate you and everyone else that took the time to answer my plea for help.


For anyone interested, I am the Chief Radio Operator aboard the American Submarine USS COD SS-224.

We operate on the ham bands using the call sign W8COD.

Check out the COD's qrz page at:


Scroll down about half way through the page for links to some really cool pictures and videos.

Again, thanks for all the help.

73 - BILL KA8VIT / W8COD
W8COD personal biography
www.qrz.com



From:[email protected] <[email protected]> on behalf of Gregg Daugherty <gregg-daugherty@...>
Sent:?Saturday, June 22, 2024 6:41 AM
To:[email protected] <[email protected]>
Subject:?Re: [RaspberryPi-4-HamRadio] Open Repeater
?
Take a look at /etc/svxlink/svxlink.conf



Below is my TX section info.



On 6/20/2024 7:49 PM, Box1600 wrote:
It has nothing to do with the repeater, (which is an MTR-2000).

In testing the software we found that the GPIO output that controls the PTT line never unkeys if the COS signal is held active longer than the set timeout period.

Everything else seems to works as it should.

Thanks, I'll check out that SXVLINK group.

73 - BILL KA8VIT



From:?[email protected] <[email protected]>?on behalf of Teton Amateur Radio Repeater Association (TARRA) <tarra@...>
Sent:?Wednesday, June 19, 2024 11:04 PM
To:?[email protected] <[email protected]>
Subject:?Re: [RaspberryPi-4-HamRadio] Open Repeater
?

Hello Bill,

With this being the issue, it be helpful to know what you are using for a repeater.

You may also want to ask the question at the svxlink at groups.io? /g/svxlink

Mick - W7CAT