Welp, that didn’t go well after several hours of tweaking.
I tried to check my winlink email using my km4ack build Raspberry Pi. I had troubles setting up the 705 since a good number of programs haven’t been upgraded to know that model number. Sure, for some things, I can change its hex address and make the computer think its an Icom 7100 or 9300 but apparently that doesn’t work in all cases.
km4ack’s ui widgets helped but ultimately I realized that I was leaning on those UI helpers too much and not actually understanding what was supposed to be going on under the hood.
So I read, fiddled, read some more, and fiddled some more. It wasn’t going to be just making a config file for the 705. Looking at the source code to fldigi and hamlib, it required some c hacking and I haven’t done that in 20 years although I use semicolons to terminate my statements, professionally, so how hard can C be over obj-c and ts?
Eventually I realized that my radio wasn’t PTT/TXing even though the ARDOP GUI said it was trying to. I couldn’t figure out a way to make it do that with my 705. I should try my 7100 just to prove to myself that I can get it to work.
Alas, VARA HF seems to be the new hotness software TNC so I might try that on my Surface 4 Windows machine which I bought used because just about all all the interesting SDR software is Windows-only. Ugh.
I may have to buy a Micro PC that’s essentially the same size as a Raspberry Pi but runs Windows – just to make it so I have to reboot 3x to fix problems instead of easily dropping to the CLI and executing $sudo kill -9 <pid>
