1 | |
---|
2 | |
---|
3 | OVERVIEW |
---|
4 | |
---|
5 | This document describes the installation procedure for the Flarm-Radar Client |
---|
6 | on a Raspberry PI running Raspbian. At the time of writing this document, this |
---|
7 | is the only platform where the client has been tested over a long time period |
---|
8 | in a production-like environment. |
---|
9 | |
---|
10 | However, the client can be installed on any operating system where |
---|
11 | Perl (http://www.perl.org) can be installed. Some adaptions might be required |
---|
12 | in this case. |
---|
13 | |
---|
14 | |
---|
15 | REQUIREMENTS |
---|
16 | |
---|
17 | Note: Early versions of Raspbian had a nasty bug that caused minicom to freeze |
---|
18 | the entire system after some hours or days of operations. Don't forget to |
---|
19 | update the OS before starting with the installation. |
---|
20 | |
---|
21 | 1. Log on the Raspberry as user 'root' and install required software packages |
---|
22 | -> $# apt-get update |
---|
23 | -> $# apt-get install zip dnsutils libwww-perl minicom |
---|
24 | |
---|
25 | 2. Connect the Flarm Device and configure communication settings for minicom (baud rate, etc.). Save the |
---|
26 | configuration file. Once the configuration is correct and the Flarm Device is |
---|
27 | turned on, you must be able to see live position data when you start minicom: |
---|
28 | |
---|
29 | $> minicom |
---|
30 | .... |
---|
31 | $GPRMC,123512.00,A,4710.24781,N,00902.46662,E,0.017,237.67,240312,,,A*6E |
---|
32 | $GPGGA,123512.00,4710.24781,N,00902.46662,E,1,8,1.40,413.2,M,48.0,M,,*6E |
---|
33 | $PFLAA,0,-118,-85,1,1,4B51BC,0,,0,0.1,1*1E |
---|
34 | $PFLAA,0,-35,-124,2,1,4B51FF,158,,0,0.1,1*14 |
---|
35 | $PFLAU,2,1,1,1,0,,0,,*61 |
---|
36 | $GPRMC,123513.00,A,4710.24782,N,00902.46659,E,0.002,237.67,240312,,,A*60 |
---|
37 | $GPGGA,123513.00,4710.24782,N,00902.46659,E,1,8,1.40,413.1,M,48.0,M,,*67 |
---|
38 | .... |
---|
39 | |
---|
40 | If you reach that: Congratulations, you're nearly done :-) |
---|
41 | |
---|
42 | |
---|
43 | INSTALLATION |
---|
44 | |
---|
45 | 1. Create a new account named 'flarm' |
---|
46 | -> $# useradd -m flarm |
---|
47 | |
---|
48 | Note1: This account does not need a password (because you might loose it and |
---|
49 | it is safer anyway). |
---|
50 | |
---|
51 | 2. Make sure that the user 'flarm' has permissions to read from the device |
---|
52 | that was previously configured in minicom. If RS232-USB adapter is used, then |
---|
53 | this is /dev/ttyUSB0, or alike. It is usually sufficient to assign the user |
---|
54 | with an additional secondary group. |
---|
55 | |
---|
56 | 3. Change identity to 'flarm' |
---|
57 | -> $# su - flarm |
---|
58 | |
---|
59 | 4. Download and unzip the client from http://www.flarmradar.ch/public/dist |
---|
60 | -> $> wget http://www.flarmradar.ch/public/dist/client-SNAPSHOT.zip |
---|
61 | -> $> unzip flarmclient-SNAPSHOT.zip |
---|
62 | |
---|
63 | |
---|
64 | CONFIGURATION |
---|
65 | |
---|
66 | The client reads a single configuration file ~flarm/.flarmclient/client.conf. |
---|
67 | |
---|
68 | 1. Configure the URL of the flarm server. If you use the public server, then |
---|
69 | you can leave the default value for this setting. |
---|
70 | |
---|
71 | 2. Set the correct client key. Request a key at info@flarmradar.ch if you use |
---|
72 | the public server. |
---|
73 | |
---|
74 | |
---|
75 | TEST THE INSTALLATION |
---|
76 | |
---|
77 | 1. Start the client using one of the provided data files |
---|
78 | $> flarmclient -f testdata/2012_03_25_departure.data |
---|
79 | |
---|
80 | The client must run without errors and stream the data to the server. Check on |
---|
81 | the server while the client is processing the data file. |
---|
82 | |
---|
83 | 2. Connect the FLARM device and run the client software |
---|
84 | $> flarmclient |
---|
85 | |
---|
86 | ... if all goes well, you can see live data on your radar. Congratulations! |
---|
87 | |
---|
88 | |
---|
89 | INTEGRATION |
---|
90 | |
---|
91 | We must make sure that the client starts automatically after booting the |
---|
92 | device. There are two common options to achieve that |
---|
93 | |
---|
94 | - a cron job |
---|
95 | The job periodically checks if the client is up and restarts it if necessary. |
---|
96 | Use this option for a device that is installed on the field and where you don't |
---|
97 | have direct access to restart the process. |
---|
98 | |
---|
99 | To install the cron-job, just copy the file examples/flarmradar.cron to |
---|
100 | /etc/cron.d on you Raspberry and restart the cron service |
---|
101 | $# /etc/init.d/cron restart |
---|
102 | |
---|
103 | |
---|
104 | - a runlevel script |
---|
105 | The runlevel script starts the client automatically during at boot time. An |
---|
106 | example is shipped in 'examples/flarmradar.rc'. |
---|
107 | |
---|