Greetings Y’all!!!
Quick back story.
2 months ago got the bug, so I set up a PiAware out in my building. Got it working great (Moving right on up the ‘ladder’ of Rank as it were quite well).
As you see from my handle here, I’m an Amateur Extra radio operator. Picked up an Anytone HT a while back which is APRS capable. Where I’m at, there’s not a lot of digipeaters or IG’s (internet gateways) around that it can hit. Sooooo I thought, WHY NOT!
Did a bunch of searching on stuff, had an older VHF radio laying around to use (144.39 mhz in the USA for VHF APRS), and a TNC attached to it I had previously used for an emergency WinLink setup. So it all SHOULD have worked fine.
Installed Direwolf, added a USB sound card, a powered USB hub, and a USB to Serial cable.
My RTL-SDR adapter is directly plugged into the Pi
The powered USB Hub is plugged into the Pi
The USB-Serial cable and USB Soundcard are into the powered hub
Installed Direwolf (from sudo apt-get install Direwolf), and it installed clean
As you search for info on it (should you), you’ll see that it says (based on you compiling it yourself) that there will be a direwolf.conf file in the home directory (/home/pi/direwolf.conf) but guess what? It doesn’t show up ANYWHERE when installed this way (LOCATE is your friend in *nix, sudo apt-get install locate ).
So,
Installed VSFTPD (following instructions at How to Setup FTP on the Raspberry Pi - Pi My Life Up ), and sat on my Windows system in the house and made the Direwolf config file in Notepad, saved as direwolf.conf, then FTP’d (Command Prompt in Windows, FTP xxx.xxx.xxx.xxx then it SHOULD as for login info or use your favorite flavor of FTP software) into my PiAware box and PUT (the command to transfer files) the file from my windows box to my PiAware box.
THOUGHT I had everything set up correctly. Had made the necessary mods to the Callsign area’s, the PTT (push to talk) line (PTT /dev/ttyUSB0 RTS DTR) and the rest of the config changes from the template I had used.
NO JOY on firing it up and it working to operate the radio/TNC
I checked and rechecked and triple checked and searched into the wee hours of the morning trying to figure out what went wrong where.
Turns out, there is embedded coding of the file in Windows/DOS (and MAC too) that *nix doesn’t like in files!!!
I’d open the file up (nano direwolf.conf) and I kept seeing “Converted from DOS format” at the bottom of the screen. I ignored it, REPEATEDLY.
One word here. DON’T!
It all has to do with how *nix, DOS, MAC process carriage returns and such.
On the bottom of the nano screen, you’ll see a M-D and M-M. the first M stands for using the ALT key (the ^ is CTRL key by the way), and if you press ALT and D it will either select or DESELECT DOS formatting for saving the file !!!
I FINALLY figured this out, saved the file and saw the “Filename to write: direwolf.conf [DOS FORMAT]” and hit ALT D, the Dos format went away and it saved it in native *nix formatting.
Then I sudo systemctl restart direwolf and as SOON as it came online it triggered the radio retransmitting an APRS signal like it should have!!! Talk about FRUSTRATING to say the least!!!
Now with all THAT said… I’m not sure if it would work using just the RTL-SDR dongle to receive signals, *nix is kind of funny about accessing hardware by more than one thing. It MIGHT work to run both Direwolf AND PiAware and have them both listen to sigs coming from as single dongle, so long as you DON’T have a filter in place to block out anything below 440 mhz (There are HF and VHF and UHF APRS signals, short and digital in nature )
Anyone can receive these sigs, but only licensed amateurs can transmit them.
Anyway, thanks for reading this far, I’m not a *nix genius by any stretch, I just know how to GOOGLE better than most!
Peace and Fair Journeys,
Gary - K4GHL
Might have to get another dongle and give it a shot.