DB0SIG has been running for some years on the same hardware setup. This setup consisted of an old Alinco mobile radio and a TNC with APRS-Digi firmware. In the beginning the TNC had occasional bit flips what did not strengthen my confidence in the system. So, as time allowed, I ordered some new parts to assemble a new and hopefully more reliable and flexible APRS digipeater.
The new Setup
The new setup consists of the following parts:
…and this is how it looks all glued together. Obviously I forgot to buy a box.
Setting up the TNC-Pi
I ordered the TNC-Pi as a kit which apparently gave the guys at the German customs a little headache. After tracking said the packet arrived at the customs, nothing happened for almost two weeks. When I had almost given up on the project, the post woman unexpectedly delivered the packet after all. Building the kit by the manual worked very well. The only deviation I had was the voltage at the PIC being only 3V, not the stated 3.3V. After powering up the TNC-Pi on the Raspberry Pi, one has to disable the serial console that supplies debug output on the device
/dev/ttyAMA0. This is the port where the TNC-Pi connects. For this I removed all references to the device from the boot command line in
/boot/cmdline.txt and added
/boot/config.txt. After that and configuring kiss as stated in the manual,
kissattach still failed. Some research brought me to the solution that you have to remove the line
T0:23:respawn:/sbin/getty -L ttyAMA0 115200 vt100
from the file
/etc/inittab. One reboot later, everything worked as expected.
Setting up the RS-UV3
The RS-UV3 required some minor modifications to run with the power amplifier. The more interesting part was powering up the device to see if it is really working. As I had no USB-to-serial adapter at hand, I used an Arduino with the soft serial example as a simple interface and Minicom as the terminal.
On the Raspberry Pi, Raspbian was already installed. On the APRS side, I use APRX which can be downloaded here. OH2MQK provides .deb packages ready for the Pi. These can be identified by the armhf (instead of the i386) in the filename. When the file has been downloaded onto the Pi, the installation reduces to a simple
dpkg -i aprx_2.08.593-1_armhf.deb. The final task was to adapt the configuration in
/etc/aprx.conf to my needs. As the file is very well commented, it is easy to come to a working setup. In the long run some parameters may need some fine tuning. For example, I activated the telemetry but it generates a lot of traffic so I will probably deactivate it once the setup has been running stable for some weeks.