As I brought up in another thread about 73 Linux, and was eloquently pointed out.
Part of this is also about setting expectations.
There is a VERY GOOD Winlink client available for the Raspberry Pi platform called "PAT" (getpat.io)
It supports the ICS forms (and others) that the Winlink team relies on so heavily, and runs in a web browser for the UI over a fat client that needs WINE.
Just like Winlink, it does not have it's own softmodem built in.
Pick a softmodem. Any softmodem. Rigctl already exists, in a limited fashion. Audio ports have already been defined. (Thx to Mike!)
We just need to get a softmodem going that can support qsy and ptt. The rest is doable.
?
I, personally, am partial to ardop, and piardopc with it's gui, because it's something we can work on.
I have a functioning model of ardop/piardopc/pat/etc on the R-Pi that runs my ICOM for a reference model. We just need to find the specific hooks that are needed to make it work.
I am willing to engage on this topic. I'm willing to host zoom sessions. I'm willing to work my booty off for it, but I can't do it on my own, and I will need help from folks who understand the way the sbitx is working under the hood much better than I do. I'm also willing to write up the step by step process to make it work, and possibly provide a script.
?
But, I've gotta get help.
