feat(doc/time/README):Replace ntpsec/ntp with chrony
[EVA-2020-02.git] / doc / location / README.org
... / ...
CommitLineData
1* Location Logging
2#+TITLE: Ninfacyzga-01 Manual
3#+AUTHOR: Steven Baltakatei Sandoval
4#+EMAIL: baltakatei@gmail.com
5** About
6This document was created by Steven Baltakatei Sandoval on
7~2020-06-29T12:14Z~ under a [[https://creativecommons.org/licenses/by-sa/4.0/][Creative Commons BY-SA 4.0 license]]. It
8was updated by Steven Baltakatei Sandoval on ~2020-10-16T23:32Z~
9
10** Narrative
11Ninfacyzga-01 records (logs) its position in time and space using a
12[[https://en.wikipedia.org/wiki/Satellite_navigation_device][GPS receiver]]. The NMEA location data produced by the receiver is
13converted into the more commonly used GPS data storage formats of GPX
14and KML. All three types of data are then compressed and encrypted
15against a set of public keys. The encrypted data is then written to
16disk. Data produced by the receiver is segmented into 60-second chunks
17before being processed and written to disk.
18** Description
19*** Hardware
20**** Raspberry Pi Zero W
21See the [[https://www.raspberrypi.org/pi-zero-w/][OEM]] webpage for this product.
22**** PiZ UpTime 2.0
23See the [[https://alchemy-power.com/piz-uptime-2-0/][OEM]] webpage for this product.
24*** Software
25~bklog~ : A bash script that saves its stdin stream to a tar file. The
26file may be compressed by ~gzip~ and encrypted by ~age~. It is an
27executable file contained within this repository at ~exec/bklog~. It
28should be copied to ~$HOME/.local/bin~.
29
30[[https://tracker.debian.org/pkg/gpsd][~gpsd~]] : A background daemon app capable of interfacing with the
31[[https://ozzmaker.com/berrygps-berrygps-imu-quick-start-guide/][Ozzmaker BerryGPS-IMU]]'s GPS submodule. Installed and initialized by
32~apt~. Should be installed along with the ~gpsd-clients~ package.
33
34~gpspipe~ : A command line app that polls ~gpsd~ and produces a stream
35stdout consisting of GPS data lines in NMEA format. Installed via
36~apt~.
37
38~gpsbabel~ : A command line app that converts GPS data from one format
39into another. ~bklog~ may be used to convert NMEA data into GPX and
40KML. Installed via ~apt~.
41
42~gzip~ : A simple command line app that compresses stdin into a
43smaller stdout stream.
44
45~age~ : A simple command line app that encrypts stdin against public
46keys specified in its options. Produces encrypted stdout. Is an
47executable file contained within this repository at ~exec/age~. It
48should be copied to ~$HOME/.local/bin~.
49
50**** Narrative
51~bklog~ may be used to log location data by receiving stdout produced
52by ~gpspipe~. ~bklog~ contains options that allow file writes to be
53performed at adjustable time intervals (default: 300 seconds),
54compressed (with ~gzip~), and encrypted (with ~age~). Files are
55written in the form of appendages to a ~tar~ archive saved to a
56specified location. The NMEA data produced by ~gpspipe~ may be
57processed via a ~gpsbabel~ command string specified as an option to
58~bklog~, assuming ~gpsbabel~ is installed.
59
60*** Output
61
62Several output file formats have been tested with ~bklog~.
63
64**** File Formats
65***** NMEA
66~NMEA~ is an acronym for National marine Electronics Association. The
67NMEA format described in this document follows the NMEA 0183
68standard. It is a newline-delimited streaming text format that encodes
69global positioning system (GPS) data such as WGS84 location, time and
70date information, satellite count, accuracy, and other
71information. Each line is an "NMEA sentence". Descriptions of various
72NMEA sentences can be found on [[http://aprs.gids.nl/nmea/][this]] webpage.
73
74See the [[https://en.wikipedia.org/wiki/NMEA_0183][Wikipedia page for NMEA 0183]] for this. This file format is the
75default output of the ~gpspipe -r~ command.
76***** GPX
77See the [[https://en.wikipedia.org/wiki/GPS_Exchange_Format][Wikipedia page]] for this. [[http://wiki.gis.com/wiki/index.php/WGS84][WGS84]] is the datum used. An NMEA file
78may be converted to this format using ~gpsbabel~.
79***** KML
80See the [[https://en.wikipedia.org/wiki/Keyhole_Markup_Language][Wikipedia page]] for this. [[http://wiki.gis.com/wiki/index.php/WGS84][WGS84]] is the datum used. An NMEA file
81may be converted to this format using ~gpsbabel~.
82
83**** Encryption Method
84See [[file:../setup/README.org][Main Setup]] procedures.
85
86** Operating Procedures
87*** Initial Startup
88See OEM (Ozzmaker) [[https://ozzmaker.com/berrygps-berrygps-imu-quick-start-guide/][quickstart guide for the BerryGPS-IMU]].
89**** Physical Setup
90
91BerryGPS-IMU must be electrically connected to the correct pins on the
92GPIO header of a Raspberry Pi Zero W.
93
94*Optional*: stack together with PiZ Uptime 2.0 module. No GPIO pins
95conflict so a simple stacking and soldering with long header pins is
96possible.
97
98**** Software Setup
99***** Install Executables
100Follow the [[file:../setup/README.org][Main Setup]] procedures to obtain required files from this
101repository.
102
103Install ~gpsd~, ~gpsd-clients~, and ~gpsbabel~.
104
105: $ sudo apt install gpsd gpsd-clients gpsbabel
106
107***** Setup Serial for BerryGPS
108The Ozzmaker BerryGPS-IMU unit requires that the serial console be
109disabled and the serial port enabled. (see [[https://ozzmaker.com/berrygps-setup-guide-raspberry-pi/][ref]]).
110
111: $ sudo raspi-config
112
113Navigate to ~5 Interfacing Options~, then ~P6 Serial~.
114
115When prompted "Would you like a login shell to be accessible over
116serial?", answer ~No~.
117
118When prompted "Would you like the serial port hardware to be
119enabled?", answer ~Yes~.
120
121***** Setup ~gpsd~
122~gpsd~ needs to know which serial port to look at for NMEA location
123data generated by the GPS unit. This can be done by modifying the
124~gpsd~ configuration file at ~/etc/default/gpsd~.
125
126: sudo nano /etc/default/gpsd
127
128Make sure the following lines are present:
129
130#+BEGIN_EXAMPLE
131START_DAEMON="true"
132USBAUTO="false"
133DEVICES="/dev/ttyAMA0"
134GPSD_OPTIONS="-n"
135#+END_EXAMPLE
136
137NOTE: The ~DEVICES=~ line must be adjusted if the the ~ninfacyzga~
138device is configured to also track time.
139
140NOTE: The ~-n~ option causes ~gpsd~ to begin polling GPS devices
141without waiting for a client to connect. This is important if ~gpsd~
142provides data to other applications (ex: ~gpspipe~, ~chrony~).
143
144Restart ~gpsd~ via:
145
146: $ sudo systemctl restart gpsd.service
147
148Run ~gpsmon~ to verify that location data is being recorded.
149
150: $ gpsmon
151
152***** Automatic Start Configuration
153It is recommended to create a daily ~cron~ job that executes a bash
154script that starts ~bklog~ jobs to record location along with other
155types of data recording. An example of such a script is below:
156
157#+BEGIN_EXAMPLE
158#!/bin/bash
159
160# Log location
161gpspipe -r | /bin/bash "$HOME/.local/bin/bklog" -c -e -z "UTC" -t "/dev/shm" \
162 -r age1kza7pfshy7xwygf9349zgmk7x53mquvedgw9r98qwyyqhssh830qqjzlsw \
163 -r age1ce3pvzrqfcn2pc6zqzglc8ac8yjk3fzukpy08cesqjjwns53xywqmaq7xw \
164 -R "$HOME/.config/bklog/recipients" -w ".nmea" -b "300" -B "day" \
165 -o "$HOME/Sync/Evanescent_Location" -l "location" \
166 -p "gpsbabel -i nmea -f - -o gpx -F - " ".gpx" \
167 -p "gpsbabel -i nmea -f - -o kml -F - " ".kml" &
168# Log pressure
169python ~/.local/bin/bmp388.py | /bin/bash "$HOME/git-OC/ninfacyzga-01/exec/bklog" \
170 -c -e -z "UTC" -t "/dev/shm" \
171 -r age1kza7pfshy7xwygf9349zgmk7x53mquvedgw9r98qwyyqhssh830qqjzlsw \
172 -r age1ce3pvzrqfcn2pc6zqzglc8ac8yjk3fzukpy08cesqjjwns53xywqmaq7xw \
173 -R "$HOME/.config/bklog/recipients" -w ".txt" -b "300" -B "day" \
174 -o "$HOME/Sync/Evanescent_Location" -l "pressure" &
175#+END_EXAMPLE
176
177This script, if it were saved at
178~"$HOME/.local/bin/cron/dailylog.sh"~ would then be added as a
179line in the ~crontab~ file as shown below:
180
181#+BEGIN_EXAMPLE
182$ crontab -e
1830 0 * * * /bin/bash ~/.local/bin/cron/dailylog.sh
184@reboot /bin/bash ~/.local/bin/cron/dailylog.sh
185#+END_EXAMPLE
186
187In the example script, the options are:
188
189: -c : tells bklog to compress output
190: -e : tells bklog log to encrypt output
191: -r : tells bklog to interpret the next argument as a pubkey string
192: -R : tells bklog to interpret the next argument as a directory
193: where public keys may be found (first line of each file is
194: read).
195: -o : tells bklog to write output files to the directory represented
196: -t : tells bklog to interpret the next argument as a directory
197: for storing temporary files
198: by the next argument
199: -p : tells bklog a command string through which output is piped
200: before being compressed and encrypted. Also expected is a
201: file extension to be appended before the compression and
202: encryption file extensions.
203: -w : tells bklog to save the unprocessed stdin with a specified
204: file extension (instead of the default '.stdin').
205: -b : tells bklog how long each buffer round (time between file
206: writes) lasts in seconds.
207: -B : specifies the time-to-live for the bklog script. A valid value may
208: one of the time elements such as "day" or "hour".
209: -l : specfies a custom string to be used in output file names to
210: help differentiate tar files produced via bklog from different
211: sources of data.
212: -z : specifies a time zone to be used to determine the script time-to-live.
213: By default, bklog uses whatever time is specified by the TZ
214: environment variable.
215
216***** Log Transfer Configuration
217See [[file:../setup/README.org][Main Setup]] procedures.
218
219Log files may be shared to other machines via ~syncthing~. See [[https://docs.syncthing.net/][this]]
220manual for how to set up a shared folder and add Ninfacyzga-01 as a
221device. Syncthing's directory synchronization capability allows a
222remote machine to delete files from Ninfacyzga-01 by deleting from the
223shared folder that they both share.
224
225When log files are removed from Ninfacyzga-01 is not within the scope
226of this document.
227
228***** Key Generation
229See [[file:../setup/README.org][Main Setup]] procedures.
230
231*** Normal Startup
232Turn on Ninfacyzga-01 by supplying 5VDC power to the Raspberry Pi. No
233further interaction should be required.
234*** Normal Operation
235No interaction beyond continually supplying approximately 100mA of
2365VDC power and occasionally removing log files to conserve disk space
237is required.
238**** Log Transfer
239Log files may be transferred by use of ~syncthing~ shared folders.
240**** Automatic Updates
241The ~automatic-upgrades~ package, if installed, should automatically
242install security patches to packages installed via ~apt~.
243*** Normal Shutdown
244The system may be shutdown via SSH by running:
245
246: $ sudo shutdown -r 0
247
248*** Unscheduled Shutdown
249Ninfacyzga-01 as described and setup should tolerate unscheduled power
250loss. Log files being written every 60 seconds means, at most, 60
251seconds worth of location data may be lost.
252*** End of Life Disposal
253See [[file:../setup/README.org][Main Setup]] procedures.