Setup Packetradio on a Raspberry
I have made a quik guide to install direwolf, bpq and jnos on a Raspberry Pi. if you follow the instructions in the examples you should get it to work. You only need to adjust the configuration files direwolf.conf, bpq32.cfg, autoexec.nos
Install Direwolf on Raspberry Pi
The Pi plus a USB soundcard is all you need to get started with Packet Radio. Instead of using a dedicated hardware TNC, the Pi can be coaxed to do the hard work of managing the Packet protocol.
Full instructions can be found on the WB2OSZ’z website at:
https://github.com/wb2osz/direwolf
Installation version 1.6
Raspbian update:
>> sudo apt-get update
>> sudo apt-get dist-upgrade
>> sudo rpi-update
>> sudo reboot
Remove pulseaudio:
>> sudo apt-get remove --purge pulseaudio
>> sudo apt-get autoremove
>> rm -rf /home/pi/.pulse
>> sudo reboot
Software development packages:
>> sudo apt-get install git
>> sudo apt-get install gcc
>> sudo apt-get install g++
>> sudo apt-get install make
>> sudo apt-get install cmake
>> sudo apt-get install libasound2-dev
>> sudo apt-get install libudev-dev
Remove old install:
>> sudo rm -rf direwolf (remove old install)
Install Direwolf:
>> cd ~
>> sudo git clone https://www.github.com/wb2osz/direwolf
>> cd direwolf
>> sudo git checkout dev
>> sudo mkdir build && cd build
>> sudo cmake ..
>> sudo make -j4
>> sudo make install
>> sudo make install-conf
This gives you the latest development version.
Leave out "git checkout dev" to get the most recent stable release.
Make direwolf executable:
>> sudo chmod a+x direwolf
Configuration direwolf.conf:
>> sudo editor direwolf.conf (example)
ADEVICE plughw:1,0
ACHANNELS 1
CHANNEL 0
MYCALL CALLSIGN
MODEM 1200 E+
PTT GPIO 21
DWAIT 30
SLOTTIME 10
PERSIST 64
TXDELAY 20
TXTAIL 05
AGWPORT 8000
KISSPORT 8001
FIX_BITS 0 AX25
Update direwolf:
>> sudo apt-get update
>> sudo apt-cache showpkg direwolf
>> sudo apt-get install direwolf
Install BPQ on Raspberry Pi
The purpose of this mini howto is to get a working BPQ configuration on a Raspberry Pi. This is the most simple methode to install and configure BPQ on you Raspberry Pi
Full instructions can be found on the G8BPQ website at:
http://www.cantab.net/users/john.wiseman/Documents/
Installation
Create directory:
>> sudo mkdir BPQ
>> cd BPQ
Download bpq-config:
>> sudo wget http://www.prinmath.com/ham/bpq-config
Make bpq-config executable:
>> sudo chmod a+x bpq-config
Run bpq-config:
>> sudo ./bpq-config
Install Jnos2 on Raspberry Pi
The purpose of this mini howto is to get a working Jnos configuration on a Raspberry Pi. This is the most simple methode to install and configure Jnos on your Raspberry Pi
Full instructions can be found on the VE4KLM website at:
https://www.langelaar.net/projects/jnos2/
Make directory and download Jnos:
>> sudo mkdir ./Jnos
>> sudo rsync -a www.langelaar.net::jnos2 ./Jnos
Install ncurses development package:
>> sudo apt-get install libncurses5-dev libncursesw5-dev
Configure script Jnos:
>> cd Jnos
>> sudo ./configure
Build the Jnos executable:
>> sudo make
Make jnos executable:
sudo chmod a+x jnos
Run Jnos:
>> sudo ./jnos
Update JNOS 2.0m.4 systems:
>> cd <your JNOS source>
>> sudo rsync -av www.langelaar.net::jnos2 .
After rsync is complete a new file: update_jnos.2.0m.5?.tar.gz
Extract the files using :
>> sudo tar xvzf update_jnos.2.0m.5B.tar.gz
More information about configure your Jnos system (Click)
Solution bring Jnos colors back
add : -fsigned-char to the CFLAGS in the makefile.
CFLAGS = -DUNIX $(DEBUG) $(PATCHES) $(WARNINGS) -fsigned-char
Install LCD screen on Raspberry Pi
Activate LCD touchscreen:
>> sudo rm -rf LCD-show
>> sudo git clone https://github.com/goodtft/LCD-show.git
>> sudo chmod -R 755 LCD-show
>> cd LCD-show/
>> sudo ./LCD35-show
Calibrate LCD touchscreen:
>> sudo apt-get install -y xinput-calibrator
Activate HDMI screen
>> sudo ./LCD-hdmi
Install Xastir (APRS)
Update your package lists:
>> sudo apt-get update
If you forget to do this, you may find apt-get telling you some packages below are not available.
Get the basic set of build tools:
>> sudo apt-get install build-essential
Get the libraries essential for building xastir:
>> sudo apt-get install git autoconf automake xorg-dev graphicsmagick gv libmotif-dev libcurl4-openssl-dev
The packages above are required for the most basic minimum build of xastir. gv is not strictly required, but if you don't install it you will be unable to print. Note that the graphicsmagick package above is not the one that gives you on-line map support, it's the one that provides the "convert" utility needed to create the postscript that gv will use to print. This package and gv are both required to be able to print from xastir even with minimal map support.
Get additional libraries that will help for extra features:
>> sudo apt-get install gpsman gpsmanshp libpcre3-dev libproj-dev libdb5.3-dev python-dev libax25-dev libwebp-dev
>> sudo apt-get install shapelib libshp-dev festival festival-dev libgeotiff-dev libwebp-dev libgraphicsmagick1-dev
Get default fonts left out of the base system With recent versions of xorg, they've dropped the 100dpi and 75dpi fonts packages from the "depends" list, so they don't get installed. Of course, Xastir uses fonts in those packages as default fonts, and if you don't take this step you'll get warnings from Xastir about being unable to convert a string to a font:
>> sudo apt-get install xfonts-100dpi xfonts-75dpi
>> sudo xset +fp /usr/share/fonts/X11/100dpi,/usr/share/fonts/X11/75dpi
The second line tells your running X server to start looking for fonts in the newly installed directories. Get XASTIR source code From the GitHub repository In this method, you get your source code directly from the repository the developers use to work on the software. Here's the step-by-step method for getting it this way. You can make different choices here for where you want to store your code. This example puts it in a src directory under the user's home directory:
>> mkdir ~/src
>> cd ~/src
Then issue the following command to retrieve the latest Xastir code:
>> sudo git clone https://github.com/Xastir/Xastir.git
The above command could take a while to finish if you're on a slow link, as there are a lot of files to download.
Run bootstrap to generate Makefile.am and configure:
>> cd Xastir
>> sudo ./bootstrap.sh
You've now got all the libraries in place and can build the fully enabled code.
Configure the code:
>> cd ~/src/Xastir
>> sudo mkdir build
>> cd build
>> sudo ../configure CPPFLAGS="-I/usr/include/geotiff"
Build the code:
>> sudo make
>> sudo make install
If you intend to use Kernel AX.25 networking, you should also set the installed Xastir binary to be SUID root:
>> sudo chmod u+s /usr/local/bin/xastir
Enjoy! You now have a fully functional xastir with all features enabled. You can launch it like this:
>> xastir
Install Polaric Server (APRS)
The “Polaric Server” is an advanced open-source web-based service to present tracking information (APRS or AIS) on maps and where the information is updated in real- time.
Full instructions can be found on the Polaric website at:
http://aprs.no/dokuwiki/doku.php/polaricserver
We offer DEB packages to help you install the software. To get started you first need to add a package repository.
Do as follows (as root): (sudo su)
>> echo "deb http://aprs.no/debian-rep binary-dev/">> /etc/apt/sources.list
>> apt-get install gnupg2 dirmngr
>> gpg --keyserver pool.sks-keyservers.net --recv-keys 89E7229CFFD59B2F
>> gpg --export --armor 3E61003E24632585EB3DFE3D89E7229CFFD59B2F | apt-key add -
>> apt-get update
Installing the APRS daemon (Polaric-APRSD)
>> apt-get install polaric-aprsd
>> tail -f /var/log/polaric/aprsd.log
http:// <hostname>:8081/config_menu or if the server runs on the same computer: http://localhost:8081/config_menu
You will be prompted for a username and a password. The package initially comes with an admin-user ('admin') with password 'polaric'
There are also some setting (for more advanced users) that can by changed manually by editing the file: /etc/polaric-aprsd/server.ini
Some of the properties can also be set in another file: /var/lib/polaric/config.xml. This is meant to be used by the web interface and should normally not be edited by hand. The property values here will override the values defined in server.ini. This means that if the web-interface for configuration is used, the values defined in server.ini are then just default values. Properties that is set by the web interface is written in blue italic fonts here. The properties set in the web interface are usually sufficient for getting the server running. The other properties are meant for advanced user
>> polaric-restart
Installing the web-application (webapp2)
>> apt-get install polaric-webapp2
It connects to a local aprsd through port 8081.
By default the webapp can be accessed through http://hostname/aprs where hostname is the ip adress or host name of the machine it is running on. If it is on your own computer, localhost or 127.0.0.1 should do.
Configuration files
The following config file is important:
>> sudo editor /etc/polaric-webapp2/config.js
Here you may change setup of backend-server, map-layers, default map views and filters: It is a Javascript file which is run on clients, but even if you don't know Javascript very well, it should be fairly self-explanatory wrt. the most important configuration options.
The server runs a mapcache instance. It is configured in:
>> sudo editor /etc/polaric-webapp2/mapcache.xml
To change the Apache webserver setup for the application edit:
>> sudo editor /etc/apache2/aprs.conf
