Need detailed documentation on DigiPi configuration files

52 views
Skip to first unread message

Glenn Meader

unread,
Sep 16, 2026, 2:50:44 AMSep 16
to DigiPi
I'm finding that my DigiPi v2.2-1 is not working correctly when I connect a DigiRig Mobile and my IC-7000. Various configuration settings are not correct after doing the .

I may be doing some things wrong, but after doing the Initial setup I find that I had to ssh in to the DigiPi, make the SDcard writeable and hand edit files such as rigctld.service to get CAT working. 

I had to dig around and ask AI a bunch of questions (which it often gave the wrong answers to) to figure out how to edit the config file and then test that CAT was properly working.

So unless I'm missing some info, I think some tech documentation is called for on configuring each subsystem in DigiPi. Maybe even create general documentation on what each subsystem does and basically how to use it.  I'm willing to lead an effort to create such documentation. Lots of the info probably already exists out there, but pulling it all together in one place, with links would help.

There's info in https://github.com/craigerl/digipi/wiki/DigiPi-Wiki Maybe that's the place to add more info?

Anyone have suggestions or wants to help?

Craig

unread,
Sep 16, 2026, 10:23:40 AMSep 16
to Glenn Meader, DigiPi
Hi Glenn - the wiki is a great place for user-documentation-contributions!

rigcltd should be configured properly if you selected digirig as your interface,
specifically for the RTS signal for PTT.  If you have a hybrid radio that uses
digirig AND cat commands (yaesu), yes a hand-edit is required at this time,
and we should document that (or better yet, i fix it!)

rigctld is used with Pat and qSSTV, behind the scenes.


cool,
-craig
KM6LYW
--
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/ddacf90b-de15-48cf-9b0e-3e91be08f6fcn%40googlegroups.com.

Gwen Patton

unread,
Sep 16, 2026, 10:31:43 AMSep 16
to Glenn Meader, DigiPi
Yeah, be careful of AI trying to "help" you. I managed to fix my quiet APRS problem with some help from Gemini, but I had to correct the AI more than once when it tried to tell me syntax.

Worse, it tried to tell me it was going to monitor activity on APRS.fi and tell me when things changed, but that sounded fishy so I said "are you sure you can actually do that?" And it came clean and told me it couldn't.

You have to remind these agents not to just tell you what they believe you want to hear, but only actual facts. Otherwise, you can waste a lot of time waiting for them to do something they actually don't have the ability to do at all. Even then, they'll periodically forget you told them not to lie to you.

So take everything an AI tells you with a grain of salt...the size of a water softener block. They can be useful, but they do tend to use the "it's true -- from a certain point of view" paradigm.


-=-=-=-=-=-=-=-=-
73,
Gwen, NG3P

--

Scott Sheppard

unread,
Nov 2, 2026, 11:18:27 AMNov 2
to Glenn Meader, DigiPi
Hello 

I would like to add a page to teh wiki for digipi. 

I have added a AX3000 and a memo puck to my digipi and dramatically increased my wifi range.  What permissions do I need to do this?


DigiPi Dual-Radio Wi-Fi Setup

USB AX3000 adapter + MIMO puck antenna for the DigiPi hotspot, onboard Wi-Fi kept for the home network

RadioInterfaceDriverRole
Onboard Pi 3B+ Wi-Fiwlan0brcmfmacClient on home Wi-Fi (e.g. 192.168.1.224) for SSH and internet
USB AX3000 adapter + ANT-132-S02 puckwlan1mt7921u (MediaTek MT7921AU, USB ID 0e8d:7961)DigiPi hotspot, 10.0.0.5/24, 2.4 GHz, serves the weather network (GW1200 at 10.0.0.6)

At home both run at once. In the field, home Wi-Fi is simply absent and the hotspot keeps running.

Tested on: Raspberry Pi 3B+, DigiPi on Raspberry Pi OS Trixie.


Important DigiPi rules (read first)

  1. The SD card is read-only. Run sudo remount before changing anything, and sudo reboot when finished to return to read-only. Do not leave it writable across a power loss.
  2. Do not use nmcli connection modify on DigiPi. NetworkManager starts while the card is read-only and keeps that view even after sudo remount, so nmcli modify fails with "Read-only file system". Edit the .nmconnectionfiles directly with sudo sed, then run sudo nmcli connection reload.
  3. Use sudo to read NetworkManager files. /etc/NetworkManager/system-connections/ and /var/lib/NetworkManager/ are root-only. Wildcards such as sudo ls /var/lib/NetworkManager/dnsmasq-*fail because your shell expands the * before sudo runs; list the folder instead (sudo ls -l /var/lib/NetworkManager/).
  4. Do not add dtoverlay=disable-wifi. The onboard radio is needed for the home network.

0. Hardware

  1. Connect the puck's RP-SMA lead(s) to the USB adapter. Use both leads if the adapter has two antenna ports (2×2 MIMO).
  2. Plug the adapter into a Pi USB port. It can draw significant current when transmitting, so use a solid 5 V / 2.5 A supply or a powered USB hub; budget an extra 2–3 W on battery/solar systems.
  3. Mount the puck high and clear of metal. Placement matters as much as gain.

1. Connect, make writable, back up

From the Mac, join the DigiPi network (or use the home network) and SSH in. See section 9 for the Mac SSH config.

On the Pi:

bash
sudo remount
sudo tar czf /tmp/net-backup-$(date +%F).tar.gz /etc/NetworkManager/system-connections /boot/firmware/config.txt /etc/rc.local /etc/chrony

In a second Terminal window on the Mac:

bash
scp 'digipi-field:/tmp/net-backup-*.tar.gz' ~/
ls -l ~/net-backup-*.tar.gz

2. Identify the radios and record MAC addresses

bash
lsusb | grep -i 0e8d
for i in wlan0 wlan1; do echo "$i  $(basename $(readlink /sys/class/net/$i/device/driver))  $(cat /sys/class/net/$i/address)"; done
iw list | grep -E "^Wiphy|^[[:space:]]+\* AP$"

Expected:

  • lsusb shows 0e8d:7961 MediaTek Inc.
  • brcmfmac = onboard radio (MAC usually starts b8:27:eb), mt7921u = USB adapter
  • Both phys list * AP

Record both MACs, in uppercase, for the next steps:

bash
ONBOARD_MAC=B8:27:EB:xx:xx:xx    # brcmfmac radio
USB_MAC=90:DE:80:xx:xx:xx        # mt7921u adapter

(Type these two lines at the prompt with your real values; later commands use them. If you log out, set them again.)


3. Set the Wi-Fi country

The default "world" domain (country 00) limits power and channels.

bash
sudo raspi-config nonint do_wifi_country US
sudo iw reg set US
iw reg get | head -3

Expected: country US: DFS-FCC.


4. Lease file in RAM for the hotspot on wlan1

DigiPi already redirects the wlan0 lease file to /run (RAM). Add the same for wlan1, because NetworkManager's dnsmasq can't write to the read-only card.

bash
sudo ln -sf /run/dnsmasq-wlan1.leases /var/lib/NetworkManager/dnsmasq-wlan1.leases
sudo touch /run/dnsmasq-wlan1.leases
sudo sed -i 's|^  touch /run/dnsmasq-wlan0.leases$|&\n  touch /run/dnsmasq-wlan1.leases|' /etc/rc.local
grep -n "dnsmasq-wlan" /etc/rc.local
sudo ls -l /var/lib/NetworkManager/

Expected:

  • rc.local shows both touch /run/dnsmasq-wlan0.leases and touch /run/dnsmasq-wlan1.leases
  • Both dnsmasq-wlan0.leases and dnsmasq-wlan1.leases are symlinks to /run/...

If the wlan0 symlink or touch line is missing on your image, create it the same way.


5. Move the hotspot to the USB adapter

The stock DigiPi hotspot profile is tied to wlan0 and has autoconnect=false (DigiPi's autohotspot.servicenormally starts it). Tie it to the USB adapter's MAC and let NetworkManager start it at every boot.

bash
F=/etc/NetworkManager/system-connections/hotspot.nmconnection
sudo sed -i '/^interface-name=/d' $F
sudo sed -i '/^mac-address=/d' $F
sudo sed -i "/^\[wifi\]\$/a mac-address=$USB_MAC" $F
sudo sed -i 's/^autoconnect=false$/autoconnect=true/' $F
sudo sed 's/^psk=.*/psk=xxxx/' $F

Check the printed file (password masked):

  • No interface-name= line
  • [wifi] contains mac-address=<USB_MAC>, band=bg, mode=ap, ssid=DigiPi
  • autoconnect=true
  • [ipv4] has address1=10.0.0.5/24 and method=shared

band=bg (2.4 GHz) is required: the GW1200 is 2.4 GHz only, and 2.4 GHz gives the best range.

Change the hotspot password if it is still the default or a weak one:

bash
sudo sed -i 's|^psk=.*|psk=NEW-HOTSPOT-PASSWORD|' $F

6. Set up the home Wi-Fi client on the onboard radio

The stock wlan0.nmconnection may have an empty ssid= line. NetworkManager silently ignores such a profile (it won't appear in nmcli connection show).

bash
W=/etc/NetworkManager/system-connections/wlan0.nmconnection
sudo sed 's/^psk=.*/psk=xxxx/' $W | cat -A

Look for an empty ssid= or psk=, and for ^M at line ends (Windows line endings; remove with sudo sed -i 's/\r$//' $W).

Fix and pin it to the onboard radio (replace the SSID and password with yours; keep the single quotes):

bash
sudo sed -i 's|^ssid=.*|ssid=YOUR-HOME-SSID|' $W
sudo sed -i 's|^psk=.*|psk=YOUR-HOME-PASSWORD|' $W
sudo sed -i '/^interface-name=/d' $W
sudo sed -i '/^mac-address=/d' $W
sudo sed -i "/^\[wifi\]\$/a mac-address=$ONBOARD_MAC" $W
sudo sed 's/^psk=.*/psk=xxxx/' $W

If the SSID or password contains |, & or \, put a \ before each of those characters in the command.

If the file doesn't exist at all, create it (sudo nano $W), then sudo chmod 600 $W:

ini
[connection]
id=wlan0
type=wifi
autoconnect=true
autoconnect-retries=0

[wifi]
mac-address=B8:27:EB:xx:xx:xx
mode=infrastructure
ssid=YOUR-HOME-SSID

[wifi-security]
auth-alg=open
key-mgmt=wpa-psk
psk=YOUR-HOME-PASSWORD

[ipv4]
method=auto

[ipv6]
method=auto

(A uuid= line is optional; NetworkManager generates one if absent.)


7. Reload and check before rebooting

bash
sudo chmod 600 /etc/NetworkManager/system-connections/*.nmconnection
sudo nmcli connection reload
nmcli connection show

Expected: both hotspot and wlan0 are listed. Until the reboot, the hotspot still runs on the onboard radio and wlan0shows no device. That is normal.

About DigiPi's autohotspot.service

/etc/systemd/system/autohotspot.service runs /usr/local/bin/digihotspot.sh 30 seconds after boot. If wlan0 is not connected, it runs nmcli connection down wlan0, then nmcli connection up hotspot, and adds a firewall rule rejecting TCP port 53. It doesn't name an interface for the hotspot, so with the MAC lock the hotspot stays on the USB adapter. Leave it enabled.

Quirk: if the home router takes longer than 30 seconds to connect, the script disconnects home Wi-Fi until the next reboot (the hotspot is unaffected). If this happens often, disable it with sudo systemctl disable autohotspot.service; the hotspot still starts via autoconnect=true.


8. Reboot and verify

bash
sudo reboot

Wait about a minute, rejoin DigiPi, ssh digipi-field, then:

bash
nmcli device status
iw dev
ping -c 3 10.0.0.6
chronyc sources
iw reg get | head -3

Expected:

  • wlan1 connected → hotspot; wlan0 connected → wlan0 (when home Wi-Fi is in range)
  • iw dev: wlan1 type AP, ssid DigiPi, channel 11 (2.4 GHz); wlan0 type managed on your home SSID (2.4 or 5 GHz)
  • ping replies from the GW1200. The first one or two may be slow (1–2 s) while it wakes or rejoins.
  • chronyc sources: internet servers when home Wi-Fi is up; NMEA becomes active when the GPS has a fix
  • country US

Transmit power reading

iw dev shows txpower 3.00 dBm for wlan1 even with sudo iw dev wlan1 set txpower fixed 2000. This is a known MT7921 reporting quirk, not the real output. Check the actual signal from the Mac while joined to DigiPi:

bash
system_profiler SPAirPortDataType | grep -m1 "Signal / Noise"

Around −40 to −60 dBm nearby is normal (measured −52 dBm / −93 dBm noise). Better than about −70 dBm at the point of use gives a solid link. (Option-clicking the Wi-Fi icon may not show RSSI on newer macOS.)


9. Mac SSH setup

Without IdentitiesOnly, the Mac offers every key it has and the Pi disconnects with "Too many authentication failures". Keys live in ~/.ssh/keys/.

~/.ssh/config entries (keep them above any Host * section):

Host digipi224 192.168.1.224
    HostName 192.168.1.224
    User pi
    IdentityFile ~/.ssh/keys/id_digipi224
    IdentitiesOnly yes

Host digipi-field 10.0.0.5
    HostName 10.0.0.5
    User pi
    IdentityFile ~/.ssh/keys/id_digipi224
    IdentitiesOnly yes

(AddKeysToAgent yes and UseKeychain yes are set globally at the top of the file.)

  • On the DigiPi network: ssh digipi-field
  • On the home network: ssh digipi224

Installing the key on a fresh Pi

If SSH offers the key but still asks for a password, the Pi doesn't have the key (common after a rebuild). Check with:

bash
ssh -v digipi224 exit 2>&1 | grep -iE "offering|accepted|denied"

To install the key: on the Pi, run sudo remount. Then on the Mac:

bash
ssh-copy-id -i ~/.ssh/keys/id_digipi224.pub digipi-field
ssh digipi-field          # should log in without a password

Then on the Pi: sudo reboot. One install covers both host entries (same Pi).


10. Time (field operation)

The GW1200 gets its time from the Pi (chrony), so the Pi needs good time without internet. Confirm these are in place:

bash
grep -nE "^(allow|local|refclock)" /etc/chrony/chrony.conf /etc/chrony/conf.d/* 2>/dev/null
systemctl status rtc-to-system --no-pager
systemctl status gpsd --no-pager

Expected:

  • allow 10.0.0.0/24: the weather network may query the Pi
  • local stratum 10: serve RTC-based time when no other source is available
  • refclock SHM 0 ... refid NMEA (in conf.d/GPS.conf): GPS time via gpsd
  • rtc-to-system.service ran successfully: DS3231 RTC sets the clock at boot, before WeeWX
  • gpsd active with -n

Priority: internet (home) → GPS (field, with a fix) → RTC / local stratum 10 (fallback). chrony's rtcsync keeps the RTC corrected whenever it's synced.

Note: gpsd is set to /dev/ttyACM1. The audio interface (All-In-One-Cable) may also appear as ttyACM, and the two can swap numbers after a reboot. Pointing gpsd at the GPS's fixed /dev/serial/by-id/ name avoids this.


11. Rollback

If the hotspot doesn't return after the reboot, put the Mac on home Wi-Fi and ssh digipi224 (or use Ethernet, or a keyboard and monitor). Then:

bash
sudo remount
F=/etc/NetworkManager/system-connections/hotspot.nmconnection
sudo sed -i '/^mac-address=/d' $F
sudo reboot

This frees the hotspot to run on the onboard radio again. For a full restore, unpack the backup from step 1 (sudo tar xzf net-backup-YYYY-MM-DD.tar.gz -C / after copying it back to the Pi and running sudo remount).


12. Finish

When all checks pass:

bash
sudo reboot

This returns the SD card to read-only.

Scott Sheppard
1702 Frazier Park Drive 
Decatur, GA 30033
KJ4ZZB Call Sign

Glenn Meader

unread,
Nov 2, 2026, 12:40:53 PMNov 2
to Scott Sheppard, DigiPi
You do not need any permissions to add info to the Wiki. I would suggest making a new Wiki page named something like Dual Radio WiFi. 
I would suggest you add a paragraph at the top of your page explaining to a novice what this dual radio stuff is for and why it’s useful. I for one, have no idea.

— Glenn

On Nov 2, 2026, at 8:18 AM, Scott Sheppard <sshe...@bellsouth.net> wrote:

Hello 
Reply all
Reply to author
Forward
0 new messages