DigiPi 2.3-Beta3 Released

117 views
Skip to first unread message

KM6LYW Radio

unread,
Nov 11, 2026, 4:56:37 PM (8 days ago) Nov 11
to DigiPi
https://digipi.org              DigiPi 2.3-Beta3

Changelog for 2.3-Beta3

Mercury Modem v1.9.23 (MUCH faster, KO0OOO, 30m, Nevada)
Modem73 v2.5.0, new headless/setup/ansi interface
Remove all direct and indirect support for VARA
Fix systemd service mutual-exclusions
Pat now starts rigctld - if there's a conflict start Pat last
Update hamlib, rigctld now recognizes AIOC USB device ID

Changelog for 2.3-Beta2

Fix ardop.sh ardopcf startup service
Implement GPIO ptt in hamlib library, xara now works with DRA-Zero, GPIO12
Initialize properly configures rigctld for GPIO pin12 PTT
Default hotspot to 5G wifi, use 2.4G on Zero2W with alternate parameters
Default to US region code for wifi (edit /boot/firmware/cmdline.txt)
Upgrade Pat to 1.0.1
Add experimental modem73.node.sh, starts AX25 and IP over AX25 with modem73
Add WPA3 wifi defensive parameters, downgrade wpa_supplicant

Changelog for 2.3-Beta1

Add XaraFM, XaraHF - Fully VARA-compatible modems
Add Modem73 - OFDM/Robust/MFSK modem
Migrate ARDOP to ARDOPCF
Web interfaces for Xara, Ardop, Mercury, Modem73
PHP Patch, apt upgrade, Linux 6.18.50
Tested on ic705/hamlib and AIOC

Costin ILIE

unread,
Nov 12, 2026, 4:41:55 AM (8 days ago) Nov 12
to DigiPi
Craig, I am very sorry that you removed the XARA modem from DigiPi. I consider this a huge mistake. XARA was, and still is, on GitHub. Even though the original author stopped development, others have continued it. There is NO official conflict between XARA and VARA; if VARA were to become incompatible with XARA at some point in the future, it would only be because VARA modified the protocol. At the moment, that is just a rumor. And if it were to happen, then VARA and XARA would simply be two completely separate and incompatible products. But until then—if it even happens—there is no official conflict between the two. I regret that you made this decision; you have effectively dashed the hopes of many amateur radio operators. Fortunately, I have the BETA 2 version, which includes XARA, and I will stick with that. I have full respect for your work, but I do not understand your decision. XARA was welcomed like a ray of sunshine, and now you, too, are among those extinguishing that hope. I am truly sorry. I will remain on BETA 2.

73, YO4CIL, Costin.

Craig

unread,
Nov 12, 2026, 11:34:10 AM (7 days ago) Nov 12
to Costin ILIE, DigiPi
Hi Costin, DigiPi Ops,

Vara/Xara is Fantastic!!  I agree, but unfortunately it doesn't have a future. 

Proprietary closed-standard software makers all have a choice to make,
  1. embrace open source
  2. litigate open source
  3. embrace open source then extend/corrupt/extinguish
One choice has a future. 

I was really hoping this would be different but Jose/Vara chose a combination of two
and three.  History is not on Vara's side, or we'd all still be suffering with Internet Explorer
on WindowsXP.  X0rro and I went out of our way to implement Vara's registered-speed
license attestation so he could still get funding to continue to develop a great transport. 
This accommodation was met with litigation and standards corruption.

Given the "NDA-style" wording on Xara's github page, it's clear (to me) Vara chose to litigate.

The most recent version of Vara is expected to corrupt the protocol to make
Xara (and old VARAs) incompatible (extend and extinguish), so this isn't really
a DigiPi decision. This time-bomb is expected on January 1st, so Xara will
stop working either way.

Open Sources licenses come with no indemnification nor warranty, so there are no
legal protections from patent trolls, despite decades of prior art (wifi, HDTV, OFDM etc).

Closed Source is great for "leaf" technologies, think "tax software," but not so
good in "trunk" infrastructure where interoperability is paramount.

Going forward, I'll be putting my engineering/advocacy efforts into MERCURY and
Modem73 - which is why I made the Mercury video (3128 kbps btw!) in response
to the vara/xara debacle.  I've also got Modem73 working on VHF, with APRS too!

The future is bright!  I'm just sorry vara/jose can't be a part of it.  It was really cool
technology.



best,
-craig
KM6LYW
digipi.org

Mark Cohen

unread,
Nov 12, 2026, 11:43:48 AM (7 days ago) Nov 12
to Craig, Costin ILIE, DigiPi
It’s very sad and while I knew that would happen because Jose being .. Jose. I’m sorry that he behaved this way.  What I don’t think he knew/realized was that with Xara, if you put in a Vara license, you got the elevated speeds. He could have worked with the Xara dev instead of against him and still made his money. I’ve been begging for Vara for OSX/Linux for years now and this had me hoping.. 

I’m sure I’m the only one willing to do this, but I’ve removed ALL of my Vara installations on all of my hosts. It’s just not worth running Windows hosts or Wine just to have a little speed. 

73 de K6EF

--
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/9372f675-2960-4e73-8e09-ce56dd8a7e68%40gmail.com.

Bruce Robertson

unread,
Nov 12, 2026, 11:57:41 AM (7 days ago) Nov 12
to Mark Cohen, Craig, Costin ILIE, DigiPi
I recently also learned about VardeFM, "a free and open source OFDM data modem for FM voice radios that replaces VARA FM on the host computer side, accepting the same VARA TCP client connections on ports 8300 and 8301 so Winlink, Pat, and BBS programs work unchanged". 


And a video introduction:




--

Craig

unread,
Nov 12, 2026, 12:02:02 PM (7 days ago) Nov 12
to Mark Cohen, Costin ILIE, DigiPi
Right, it might seem like a setback, but I see a huge net benefit to the community.
I should have mentioned "fear uncertainty and doubt" (Microsoft's playbook), which
we're also seeing in the radio echo chambers about Mercury, Modem73, M17, etc.

Experimentation and education will prevail in the long run.  I, for one, am really
excited about MERCURY.  It looks like we can literally drop it in the RMSTrimode
vara folder on RMS servers and they instantly starts working, it just needs a few
more tweaks on the timing. Rhizomatica is engaged.  BPQ32 RMS servers work now.

You can genuinely see MERCURY getting 3135 bps real world speeds here,
even with my crappy antenna!

         https://youtu.be/kjT5hQfuEVc?t=176   

I don't want to get ahead of ourselves, but on the VHF side, Modem73 is really
starting to shine, and not just for Winlink.   I've got it doing APRS and AX.25,
and even TCP/IP here on the workbench.

       Modem73 Winlink/AX25/IP:   https://youtu.be/2kg7IRlLOzk
       Modem73 APRS:     https://youtu.be/ZoTFmKCBr7o

DigiPi 2.3-Beta3 has the latest versions of Mercury and Modem73.  The
rough edges in those examples have already been fixed.


great stuff,
-craig
KM6LYW

Craig

unread,
Nov 12, 2026, 12:16:18 PM (7 days ago) Nov 12
to Bruce Robertson, Mark Cohen, Costin ILIE, DigiPi
Wow - what a great example!  This was on my list, but I didn't dig into
it until
just now.  Vara API compatibility makes it so all your existing vara
apps continue
to just work -- without vara!   Nobody will accept change unless we make
it super
easy.

Mark Cohen

unread,
Nov 12, 2026, 12:21:43 PM (7 days ago) Nov 12
to Craig, Bruce Robertson, Costin ILIE, DigiPi
This is exactly what I HOPE happens everywhere. Have a replacement for the server side code, make it transparent to the clients and then write a client side app. Ditch the marriage with Jose’s apps and go free everywhere.

Competition is a good thing!
> --
> 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/2d278ae7-6160-42f2-a82e-d23c79d4be1c%40gmail.com.

Costin ILIE

unread,
Nov 12, 2026, 1:10:58 PM (7 days ago) Nov 12
to DigiPi

SP2ONG-Waldek (sp2ong)

unread,
Nov 18, 2026, 3:00:50 AM (yesterday) Nov 18
to DigiPi
Hi Craig,

When mercury is compiled on Raspberry Pi OS with libhidapi-dev installed (HAVE_HIDAPI=1, which is the default behavior of make), passing device = /dev/hidraw0 with method = cm108 causes hidapi device lookup to fail with a "cannot find /dev/hidraw0" error. With HAVE_HIDAPI=1, mercury auto-detects CM108/AIOC devices by VID:PID and requires the device field to be omitted/empty. Keeping NEWDEVICEFILE=hidraw0 in localize.env for Direwolf while stripping the device line in mercury.sh when NEWRIGNUMBER=CM108 fixes PTT for AIOC, CM108, TOADs DI, and AllScan URI without affecting serial/CAT setups.

if [ "$NEWRIGNUMBER" = "CM108" ]; then
    sed -i '/^device/d' /home/pi/.config/mercury/mercury.ini
else
    sed -i "s/DEVICEFILE/$NEWDEVICEFILE/gi" /home/pi/.config/mercury/mercury.ini
fi

73 Waldek

Reply all
Reply to author
Forward
0 new messages