fix(exec):Camera script and daily job script

[EVA-2020-02.git] / doc / setup / README.org

diff --git a/doc/setup/README.org b/doc/setup/README.org
index 7c5b63afcebc2be41a11c28b93b17ca3b0d39ac4..d4a63276639834208eb8570c9ed7759c3b75fa84 100644 (file)
--- a/doc/setup/README.org
+++ b/doc/setup/README.org
@@ -1,11 +1,11 @@
-#+TITLE:Ninfacyzga-01 Setup
+#+TITLE:Ninfacyzga-1 Main Setup

 #+AUTHOR:Steven Baltakatei Sandoval
 #+EMAIL:baltakatei@gmail.com
 * Main Setup
 ** About
 This document created by [[http://baltakatei.com][Steven Baltakatei Sandoval]] on
 ~2020-10-07T18:39Z~ under a [[http://creativecommons.org/licenses/by-sa/4.0/][CC BY-SA 4.0]] license and last updated on
 #+AUTHOR:Steven Baltakatei Sandoval
 #+EMAIL:baltakatei@gmail.com
 * Main Setup
 ** About
 This document created by [[http://baltakatei.com][Steven Baltakatei Sandoval]] on
 ~2020-10-07T18:39Z~ under a [[http://creativecommons.org/licenses/by-sa/4.0/][CC BY-SA 4.0]] license and last updated on

-~2020-10-08T00:50Z~.
+~2020-10-17T21:22Z~.

 
 This document contains information regarding setup of the
 ninfacyzga-01 hardware common to all operation modes. This includes:
 
 This document contains information regarding setup of the
 ninfacyzga-01 hardware common to all operation modes. This includes:


@@ -175,10 +175,35 @@ In summary, remote SSH access may be enabled upon initial startup of a
 freshly installed image of Raspberry Pi OS by making sure an empty
 file named ~ssh~ is present on the ~boot~ partition.
 
 freshly installed image of Raspberry Pi OS by making sure an empty
 file named ~ssh~ is present on the ~boot~ partition.
 

+***** Login via SSH
+Assuming your router supports finding your Raspberry Pi via its
+default hostname of `raspberypi`, log into the pi via Wi-Fi using the
+following command:
+
+: $ ssh pi@raspberrypi
+
+Otherwise, you may have to identify the raspbery pi's IP address via
+your network router's administration console and login via a command
+resembling this:
+
+: $ ssh pi@192.168.x.x
+
+If you had previously set up a different raspberry pi that also used
+the same hostname ~raspberrypi~ or the same IP address (ex:
+~192.168.123.123~), you may have to inform your computer that this is a
+different device. You may do so using these commands:
+
+: $ ssh-keygen -f ~/.ssh/known_hosts -R "raspberrypi"
+: $ ssh-keygen -R 192.168.123.123
+

 ***** Add SSH public key
 If the use has an SSH public key, it may be added as a line in
 ~~/.ssh/authorized_keys~.
 
 ***** Add SSH public key
 If the use has an SSH public key, it may be added as a line in
 ~~/.ssh/authorized_keys~.
 

+Add the ~~/.ssh~ directory if it doesn't already exist.
+
+: $ mkdir ~/.ssh
+

 Follow [[https://superuser.com/a/925859/][these]] directions to set permissions.
 
 : $ chmod 700 ~/.ssh
 Follow [[https://superuser.com/a/925859/][these]] directions to set permissions.
 
 : $ chmod 700 ~/.ssh


@@ -225,6 +250,8 @@ Make sure to install the ~unattended-upgrades~ package to make sure
 the latest security patches for packages are installed. See [[https://linux-audit.com/using-unattended-upgrades-on-debian-and-ubuntu/][this page]]
 for a description of how ~unattended-upgrades~ works.
 
 the latest security patches for packages are installed. See [[https://linux-audit.com/using-unattended-upgrades-on-debian-and-ubuntu/][this page]]
 for a description of how ~unattended-upgrades~ works.
 

+: $ sudo apt install unattended-upgrades
+

 The configuration file is located at:
 ~/etc/apt/apt.conf.d/50unattended-upgrades~ ([[https://linux-audit.com/using-unattended-upgrades-on-debian-and-ubuntu/][ref]]). Make sure that the
 following lines are present and not commented out.
 The configuration file is located at:
 ~/etc/apt/apt.conf.d/50unattended-upgrades~ ([[https://linux-audit.com/using-unattended-upgrades-on-debian-and-ubuntu/][ref]]). Make sure that the
 following lines are present and not commented out.


@@ -318,6 +345,47 @@ https://ideaheap.com/2013/07/stopping-sd-card-corruption-on-a-raspberry-pi/
 Raspbian 10 Buster:
 https://www.raspberrypi.org/forums/viewtopic.php?p=1490692&sid=5c596a124b7805d6b10dab8d3d7caf16#p1490692
 
 Raspbian 10 Buster:
 https://www.raspberrypi.org/forums/viewtopic.php?p=1490692&sid=5c596a124b7805d6b10dab8d3d7caf16#p1490692
 

+***** Disable Bluetooth
+In order to reduce power consumed by bluetooth transmissions,
+bluetooth functionality should be disabled (see [[https://di-marco.net/blog/it/2020-04-18-tips-disabling_bluetooth_on_raspberry_pi/][link]]).
+
+Modify the ~/boot/config.txt~ file (the Pi's equivalent to BIOS
+settings; see [[https://www.raspberrypi.org/documentation/configuration/config-txt/][link]]) to make sure the following lines are added:
+
+#+BEGIN_EXAMPLE
+# Disable Bluetooth
+dtoverlay=disable-bt
+#+END_EXAMPLE
+
+The ~hciuart~ service is associated with bluetooth functionality via
+UART which may conflict with location and time data provided via
+~/dev/ttyAMA0~. It should be disabled like so:
+
+#+BEGIN_EXAMPLE
+$ sudo systemctl disable hciuart
+#+END_EXAMPLE
+
+***** Disable login console via serial port
+Some ~ninfacyzga~ functions (location and time) require data transfer
+via ~/dev/ttyAMA0~. In order to prevent serial login programs from
+interfering with such functions, it is necessary to disable them.
+
+Run the following commands to disable login via ~ttyAMA0~:
+
+#+BEGIN_EXAMPLE
+$ sudo systemctl stop serial-getty@ttyAMA0.service
+$ sudo systemctl disable serial-getty@ttyAMA0.service
+$ sudo systemctl disable hciuart
+#+END_EXAMPLE
+
+Modify ~/boot/cmdline.txt~ to remove the console:
+
+#+BEGIN_EXAMPLE
+$ sudo nano /boot/cmdline.txt
+#+END_EXAMPLE
+
+Remove ~console=serial0,115200~
+

 ***** Log Transfer Configuration
 Log files may be shared to other machines via ~syncthing~. See [[https://docs.syncthing.net/][this]]
 manual for how to set up a shared folder and add Ninfacyzga-01 as a
 ***** Log Transfer Configuration
 Log files may be shared to other machines via ~syncthing~. See [[https://docs.syncthing.net/][this]]
 manual for how to set up a shared folder and add Ninfacyzga-01 as a