On 09/03/2017 19:42, mike_ph4@... [direwolf_packet] wrote:
I've been researching and trying to see if it's at all possible to run Dire Wolf with a virtual TNC over Bluetooth SPP for use with APRSDroid. I can easily do it over TCP/IP, but Bluetooth is more convenient and suits my project a bit better. Any have any ideas?
I've managed to get a very crude hack working to connect APRSDroid and Direwolf on a Pi Zero W.
Pi Zero W has built-in WiFi and Bluetooth.
Paired my Nexus 7 with the Pi Zero W.
Make the Pi discoverable:|
$ sudo hciconfig hci0 piscan
Then search and pair from the Nexus.
|
Configure APRSDroid to use connection protocol - Bluetooth TNC.
Connection configuration - client mode. Bluetooth channel 22.
On the Pi, I use socat to connect the Bluetooth rfcomm0 device that gets created on connection to the kiss tnc service in Direwolf (tcp port 8001).
Start direwolf in one terminal window.
In another terminal, start the rfcomm service which spawns socat to connect to the kiss tnc in Direwolf:
$ sudo rfcomm watch /dev/rfcomm0 22 socat -d -d tcp4:127.0.0.1:8001 /dev/rfcomm0
Now try and send some beacons from APRSDroid. You should see incoming connections in the rfcomm terminal window, then a "Connected to KISS client" message in Direwolf followed by a beacon.
TX appears to work, I'll see if I can verify RX when I get time...
73
Nick.
Nick G4IRX