[211] | 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 install zip dnsutils libwww-perl minicom |
---|
| 23 | |
---|
| 24 | 2. Connect the Flarm Device and configure communication settings for minicom (baud rate, etc.). Save the |
---|
| 25 | configuration file. Once the configuration is correct and the Flarm Device is |
---|
[215] | 26 | turned on, you must be able to see live position data when you start minicom: |
---|
| 27 | |
---|
| 28 | $> minicom |
---|
[211] | 29 | .... |
---|
| 30 | $GPRMC,123512.00,A,4710.24781,N,00902.46662,E,0.017,237.67,240312,,,A*6E |
---|
| 31 | $GPGGA,123512.00,4710.24781,N,00902.46662,E,1,8,1.40,413.2,M,48.0,M,,*6E |
---|
| 32 | $PFLAA,0,-118,-85,1,1,4B51BC,0,,0,0.1,1*1E |
---|
| 33 | $PFLAA,0,-35,-124,2,1,4B51FF,158,,0,0.1,1*14 |
---|
| 34 | $PFLAU,2,1,1,1,0,,0,,*61 |
---|
| 35 | $GPRMC,123513.00,A,4710.24782,N,00902.46659,E,0.002,237.67,240312,,,A*60 |
---|
| 36 | $GPGGA,123513.00,4710.24782,N,00902.46659,E,1,8,1.40,413.1,M,48.0,M,,*67 |
---|
| 37 | .... |
---|
| 38 | |
---|
| 39 | If you reach that: Congratulations, you're nearly done :-) |
---|
| 40 | |
---|
| 41 | |
---|
| 42 | INSTALLATION |
---|
| 43 | |
---|
| 44 | 1. Create a new account named 'flarm' |
---|
| 45 | -> $# useradd -m flarm |
---|
| 46 | |
---|
| 47 | Note: This account does not need a password (because you might loose it and |
---|
| 48 | it is safer anyway). |
---|
| 49 | |
---|
| 50 | 2. Change identity to 'flarm' |
---|
| 51 | -> $# su - flarm |
---|
| 52 | |
---|
[215] | 53 | 3. Download and unzip the client from http://www.flarmradar.ch/public/dist |
---|
[211] | 54 | -> $> unzip flarmclient-<version>.zip |
---|
| 55 | |
---|
| 56 | |
---|
| 57 | CONFIGURATION |
---|
| 58 | |
---|
| 59 | The client reads a single configuration file ~flarm/.flarmclient/client.conf. |
---|
| 60 | |
---|
| 61 | 1. Configure the URL of the flarm server. If you use the public server, then |
---|
| 62 | you can leave the default value for this setting. |
---|
| 63 | |
---|
| 64 | 2. Set the correct client key. Request a key at info@flarmradar.ch if you use |
---|
| 65 | the public server. |
---|
| 66 | |
---|
| 67 | |
---|
| 68 | TEST THE INSTALLATION |
---|
| 69 | |
---|
| 70 | 1. Start the client using one of the provided data files |
---|
| 71 | $> flarmclient -f testdata/2012_03_25_departure.data |
---|
| 72 | |
---|
| 73 | The client must run without errors and stream the data to the server. Check on |
---|
| 74 | the server while the client is processing the data file. |
---|
| 75 | |
---|
[215] | 76 | 2. Connect the FLARM device and run the client software |
---|
| 77 | $> flarmclient |
---|
| 78 | |
---|
| 79 | ... if all goes well, you can see live data on your radar. Congratulations! |
---|
| 80 | |
---|
| 81 | |
---|
| 82 | INTEGRATION |
---|
| 83 | |
---|
| 84 | We must make sure that the client starts automatically after booting the |
---|
| 85 | device. Additionally we want to make sure that the client is automatically |
---|
| 86 | restarted if the process dies for whatever reason. |
---|
| 87 | |
---|
| 88 | ... still needs some writing. |
---|