7West Wiki - User contributions [en]

Main Page

2025-09-10T02:08:16Z

Animationb:

A wiki for 7West to keep track of projects and other important information:

===Projects:===

* [[Project Quartz]]

* [[Project Marathon]]

* [[Offline Wikipedia]]

===Microcontroller/SBC Guides===

* [[ATMega328P]]

* [[Raspberry Pi]]

==== Keeping this as I set up the site ====
* [https://www.mediawiki.org/wiki/Special:MyLanguage/Help:Contents User's Guide]
* [https://www.mediawiki.org/wiki/Special:MyLanguage/Manual:Configuration_settings Configuration settings list]
* [https://www.mediawiki.org/wiki/Special:MyLanguage/Manual:FAQ MediaWiki FAQ]
* [https://www.mediawiki.org/wiki/Special:MyLanguage/Manual:Combating_spam Learn how to combat spam on your wiki]

ATMega328P

2025-06-27T15:35:23Z

Animationb: Created page with "This page will detail how to setup a development environment and how to configure and use functions of the ATMega328P =Environment Setup= =Functions= =Bootloader= =References="

This page will detail how to setup a development environment and how to configure and use functions of the ATMega328P

=Environment Setup=

=Functions=

=Bootloader=

=References=

Raspberry Pi

2025-06-27T15:35:09Z

Animationb: Created page with "This is a page full of first-time set up instructions and how to's for the Raspberry Pi. == First-Time Setup == ==== Headless Operations ==== Place a file titled '''ssh''' in the "boot" directory, when the SD Card is plugged in to a desktop computer. Place a file titled '''wpa_supplicant.conf''' in the same "boot" directory with the following code: <nowiki> country=US ctrl_interface=DIR=/var/run/wpa_supplicant GROUP=netdev update_config=1 network={ ssid="<SSID>" sc..."

This is a page full of first-time set up instructions and how to's for the Raspberry Pi.

== First-Time Setup ==
==== Headless Operations ====
Place a file titled '''ssh''' in the "boot" directory, when the SD Card is plugged in to a desktop computer.

Place a file titled '''wpa_supplicant.conf''' in the same "boot" directory with the following code:
<nowiki>
country=US
ctrl_interface=DIR=/var/run/wpa_supplicant GROUP=netdev
update_config=1

network={
ssid="<SSID>"
scan_ssid=1
psk="<PASSWORD>"
key_mgmt=WPA-PSK
}</nowiki>

These steps will allow the Raspberry Pi to be reachable via ssh on the first boot. Use Window's PuTTY or Linux's ssh to remote in. Use your router's webpage to find the IP Address of the newly minted Raspberry Pi.
If you do not have access, try ssh'ing to the hostname "raspberrypi". On the first boot, the password will be the same as the hostname.

==== First Time Essential Commands ====
Enter '''passwd''' to change the password. Enter the following to always require password when using '''sudo''':
<nowiki>sudo visudo /etc/sudoers.d/010_pi-nopasswd</nowiki>
Then '''NOPASSWD''' to '''PASSWD'''.

Enter '''sudo raspi-config''' to edit several key Raspberry Pi configurations:
* Change the hostname
* Reduce GPU memory (optional)
* Expand the file system
* (Optional) Boot / Auto Login

Lastly run '''sudo apt-get update''' then '''sudo apt-get upgrade''' to update all the software. This will take a while.

==== SD Card Longevity====
SD Cards are not meant to be written to so many times (i.e. log files). To ensure the SD Card lasts as long as possible, we will do two things.

This will disable the swap file setup on the SD Card by default<ref>[https://raspberrypi.stackexchange.com/questions/169/how-can-i-extend-the-life-of-my-sd-card#:~:text=Leave%20plenty%20of%20free%20space,larger%20area%20of%20free%20space. Stack Exchange: Extending SD Card lifespan]</ref>:
<nowiki>sudo swapoff --all
sudo apt-get remove dphys-swapfile</nowiki>

This will install log2ram<ref>[https://levelup.gitconnected.com/extend-the-lifespan-of-your-raspberry-pis-sd-card-with-log2ram-5929bf3316f2 Installing log2ram]</ref>, which tries to delegate all log file writing to RAM:
<nowiki>sudo apt-get install git
git clone https://github.com/azlux/log2ram && cd log2ram
chmod +x install.sh && sudo ./install.sh
cd .. && rm -r log2ram</nowiki>

== How to's ==
====Aliases====
Editing '''.bashrc''' (located in the pi home directory) will let you add aliases. At the bottom of the file add the following:
<nowiki>
alias <shortcut>="<what you want the shortcut to do>"</nowiki>
Make sure there is a carriage return after the last line in the file.

====Uncomplicated Firewall====
This lets you set up a firewall and add exceptions easily. Enter the following into the terminal<ref>Rasperry Pi Networking Cookbook, by Rick Golden</ref>:
<nowiki>sudo apt-get install ufw
sudo ufw allow ssh
sudo ufw enable</nowiki>
Now you can only reach the Raspberry Pi via SSH. You can enter '''sudo ufw app list''' to see other services to add exceptions for. (www = http and https)

====NTFS External HDD====
If you are headless and mounting an external drive with the NTFS file system, you will need to do the following. External drives will probably not mount if you are headless. First use '''fdisk -l''' to find the sda of the external drive. Then in '''/etc/rc.local''' add the following line:
<nowiki>
sudo mount /dev/sda# -t ntfs-3g -o permissions /mount/point/folder</nowiki>
Now you can see the drive on reboots and can edit permissions with '''chown''' and '''chmod'''. By default, the drive is owned by root. You can change this with:
<nowiki>
sudo chown -R USER /mount/point/folder</nowiki>
Modify permissions as you please with '''chmod'''. '''700''' is recommended.

====Samba Server: Network File Server====
This will set up a shared folder on the Raspberry Pi that will be editable from Windows computers on the same network. Enter the following code on the Raspberry Pi<ref>[https://www.raspberrypi.org/documentation/remote-access/samba.md Official Raspberry Pi Tutorial for Samba]</ref><ref>[https://raspberrypihq.com/how-to-share-a-folder-with-a-windows-computer-from-a-raspberry-pi/ Share a folder with a Windows Computer]</ref>:
<nowiki>sudo apt-get install samba samba-common-bin smbclient cifs-utils
sudo smbpasswd -a pi
mkdir ~/shared
sudo nano /etc/samba/smb.conf</nowiki>
Inside the config file, ensure there is a line '''workgroup = WORKGROUP''' and add the following at the end:
<nowiki>[share]
path = /home/pi/shared
browseable=yes
writeable=yes
only guest=no
create mask=0777
directory mask=0777
public=no</nowiki>
Finally, in Windows File Explorer, right click on "This PC" and select "Map Network Drive...". Chose a drive letter and set Folder to '''\\<hostname>\share'''. Ensure "Connect using different credentials" is checked. Click finish and enter the credentials for user '''pi''' twice.

If you'd like to setup an external HDD, change the '''[share]''' to another name and the path to the drive: '''/media/pi/<Drive Name>'''. This is better for lots of storage as an HDD has much better endurance than an SD Card.

''Note: sometimes you get lucky and this folder appears in "Network" in File Explorer without having to map the drive, but it's been inconsistent.''

====Disabling WiFi====
Used if you have the Raspberry Pi only used for its Ethernet connection and WiFi is useless. In the file '''/boot/config.txt''' add the following line<ref>[https://raspberrypi.stackexchange.com/questions/43720/disable-wifi-wlan0-on-pi-3 Stack Exchange: disabling Wifi]</ref>:
<nowiki>dtoverlay=disable-wifi</nowiki>

====Flask Python Webserver: Run Python from a website====
Haven't done this yet, so figure it out: [https://www.hackster.io/mjrobot/python-webserver-with-flask-and-raspberry-pi-41b5fc Flask]

====Raspberry Pi Watchdog====
If you need the Raspberry Pi to run nonstop, you can set up the Watchdog Timer to trigger a reboot if the system hangs. Enter the following in the terminal <ref>[https://diode.io/raspberry%20pi/running-forever-with-the-raspberry-pi-hardware-watchdog-20202/ Setting up Watchdog on Raspberry Pi]</ref>:
<nowiki>sudo su
echo 'dtparam=watchdog=on' >> /boot/config.txt
reboot
sudo apt-get update
sudo apt-get install watchdog
sudo su
echo 'watchdog-device = /dev/watchdog' >> /etc/watchdog.conf
echo 'watchdog-timeout = 15' >> /etc/watchdog.conf
echo 'max-load-1 = 24' >> /etc/watchdog.conf
sudo systemctl enable watchdog
sudo systemctl start watchdog
sudo systemctl status watchdog</nowiki>
It will start itself at boot as well.

====Remote Desktop====
This will allow you to use the GUI Desktop of the Raspberry Pi remotely. Install xrdp:
<nowiki>sudo apt-get install xrdp</nowiki>
From Windows, launch Remote Desktop Connection and connect to the IP Address or hostname of the Raspberry Pi. [https://unix.stackexchange.com/questions/523152/xrdp-disconnects-immediately-after-connection-from-windows10-centos-to-centos7 Maybe?]

====rclone and Google Drive====
This will let you backup folders to Google Drive. [https://rclone.org/install/ rclone Install] offers a simple walkthrough and can help with any questions. Enter the following in the terminal:
<nowiki>curl https://rclone.org/install.sh | sudo bash</nowiki>
Use rclone's [https://rclone.org/drive/ Google Drive specific setup page] to install a new remote. Be sure to enter a Client ID and Client Secret; setting it up is shown [https://rclone.org/drive/#making-your-own-client-id here]. If your name is Adriano, you've already set most of that up.

Two commands are the most important: '''copy''' and '''sync'''. '''Copy''' moves all files from the source to the destination, '''sync''' forces the destination to look like the source (<u>including deleting files</u>). I recommend '''sync''', just because I don't like clutter. Create a shell script '''rclone_cron.sh''' somewhere:
<nowiki>#!/bin/bash
if pidof -o %PPID -x “rclone_cron.sh”; then
exit 1
fi
rclone sync -v -u /media/pi/Elements/gdrive rgdrive:sync
rclone sync -v -u rgdrive:sync /media/pi/Elements/gdrive
exit</nowiki>
The first part makes sure the ''syncing'' isn't already running. The script syncs "twice", once to make the Google Drive the same as the Network Drive (ignoring more recent files). The second sync can bring more recent files from Google Drive to the Network Drive. Be sure to modify the script to be executable ('''chmod a+x''') Place this script in crontab ('''crontab -e'''):
<nowiki>0 */4 * * * <path>/rclone_cron.sh > /dev/null 2>&1</nowiki>
Now it will sync every 4 hours and log nothing. If you need an immediate sync, just run '''rclone_cron.sh'''.

====Setting up MediaWiki====
Kinda moot because it's set up here, and if this crashes and I have to set it up again, I can't read this. However, I will back this page up somewhere. Enter the following into the terminal<ref>[https://www.mediawiki.org/wiki/Manual:Running_MediaWiki_on_Debian_or_Ubuntu MediaWiki's Guide on Raspberry Pi installation]</ref>:
<nowiki>sudo apt-get install -y mediawiki</nowiki>
This will take a while. Once it is done, we must setup the "SQL Database" (except the package is called mariadb on Raspberry Pi):
<nowiki>sudo mariadb -u root -p
CREATE USER 'wikiUser'@'localhost' IDENTIFIED BY 'THISpasswordSHOULDbeCHANGED';
quit;
sudo mariadb -u root -p
CREATE DATABASE my_wiki;
use my_wiki;
GRANT ALL ON my_wiki.* TO 'wikiUser'@'localhost';
quit;</nowiki>
''That password set for wikiUser will be stored in plaintext, so don't pick a good one''

No in a browser go to '''<hostname>/mediawiki'''. Set up, mostly keeping defaults. Be sure to use the wikiUser and not root for the database user.

Move the '''LocalSettings.php''' file to the instructed directory and edit it to change what you want to change.
'''''IMPORTANT:''''' change '''$wgMainCacheType = CACHE_ACCEL''' to '''$wgMainCacheType = CACHE_ANYTHING'''

The '''/mediawiki''' used as the main directory for the Wiki, is at '''/var/lib/mediawiki'''. It's all protected, so I recommend running '''sudo su''' before editing any of it.

To setup TLS/HTTPS, visit [https://certbot.eff.org/ Certbot] and be sure to forward port 443.

====Setting up a Dynamic DNS====
I use a Google Domain for this website, so I have to set up a Dynamic DNS in order for the domain to redirect to the Raspberry Pi. First we have to install ddclient<ref>[https://samhobbs.co.uk/2015/01/dynamic-dns-ddclient-raspberry-pi-and-ubuntu ddclient on Raspberry Pi]</ref>:
<nowiki>sudo apt-get install ddclient
sudo nano /etc/ddclient.conf</nowiki>
Now modify the .conf file you just opened. '''Note:''' during the install process ddclient probably prompted you to enter all this info already, but modify this .conf file to show this<ref>[https://support.google.com/domains/answer/6147083?hl=en Dynamic DNS with Google Domains]</ref>:
<nowiki>protocol=dyndns2
use=web
server=domains.google.com
ssl=yes
login=<username>
password='<password>'
7west.org</nowiki>
Use the ' around the password. You get the username and password from the DNS settings of your Google Domain.

ddclient will now update your IP Address every 5 minutes.

====Git Remote Server====
On the server, cd to the '''parent directory''':
<nowiki>mkdir RepoName
cd RepoName
git init --bare</nowiki>
Now on the machine with the code and local git repository:
<nowiki>git remote add RemoteName ssh://USER@DOMAIN.com:PORT/file/path/to/RepoName
git push -u RemoteName main</nowiki>
If it fails, it might be your known_hosts file. Look there and delete the applicable row. You also will have to log into USER@DOMAIN.com every time you push.

To clone this remote repo, cd to the desired '''parent directory''' and enter the following on the destination machine:
<nowiki>git clone ssh://USER@DOMAIN.com:PORT/file/path/to/RepoName
git checkout main</nowiki>

====Dwarf Fortress Server====
This is pretty silly to have here, but here it is. Download and install Dwarf Fortress as the [https://dwarffortresswiki.org/index.php/DF2014:Installation wiki] says. Get the dependancies as [https://www.reddit.com/r/dwarffortress/comments/f0rcn6/libstdcso6_cxxabi_138_not_found/ needed].

Modify init.txt in df_linux/data/init. Turn off sound and change PRINT_MODE to TEXT. Ensure your terminal is set to '''Use bright colors for bold text''' (this is in Preferences for the terminal). Then run the following:
<nowiki>sudo apt install xvfb
Xvfb :1 -screen 0 1024x768x16 &
export DISPLAY=:1
/path/to/df</nowiki>

You might also want to change some key bindings, like the Plus key.

==References==
<references />

Offline Wikipedia

2025-06-27T15:34:31Z

Animationb: Created page with "This is a look at how one could make an '''Offline Wikipedia'''. Offline means without access to the internet. This is ''not'' a doomsday prep project, but just catering to a desire to preserve information and a fun exercise. ==Basic Considerations== We must consider if we do not have internet, what else do we not have access to. So we will have two approaches: # Electricity and consumer electronics are available # Very long term endurance of the data ==Approach #1: T..."

This is a look at how one could make an '''Offline Wikipedia'''. Offline means without access to the internet. This is ''not'' a doomsday prep project, but just catering to a desire to preserve information and a fun exercise.

==Basic Considerations==
We must consider if we do not have internet, what else do we not have access to. So we will have two approaches:
# Electricity and consumer electronics are available
# Very long term endurance of the data

==Approach #1: Tablet==
This one is pretty easy.
#Buy an Android tablet with at least 256GB of storage (or a Micro SD card slot). You can buy an e-ink tablet to make it easier to read
#Install [https://kiwix.org/en/ Kiwix] on the tablet and download the offline version of Wikipedia
#You're done
You can also get a solar powered charger for the tablet and then you wouldn't need electricity. Eventually the tablet will breakdown as all electronics do.

==Approach #2: Microform==
In this case we are assuming no electricity and that we want extremely long term endurance of the data. Printing on paper is impossible due to the amount of paper needed. Computers and electronics can last a while, but not the really long time we are looking for. The solution seems to be [https://en.wikipedia.org/wiki/Microform Microform]. This is like microfilm, but is bigger. Many libraries store newspapers and periodicals in this format. Here is some math showing this is possible:
===The Math===
*Wikipedia has about 7,000,000 articles
*Wikipedia is about 4,900,000,000 words
**Each article has about 700 words
*This fills about 3,062 volumes (books)
** with 1,600,000 words per volume (at 6 characters per word)
** with a volume being 25cm tall and 5cm thick (at 500 sheets, 1000 pages)
This is too many books, but microform reduces books to ~4% their original size. 3,062 volumes becomes 123 volumes, each in the form of a roll of microform. This makes the Wikipedia collection able to fit in a cabinet.

===The Cost===
The hypothetical cost is as follows. I found a company that will "microform"-ify your documents for $0.025 (USD) per A4 page (210x297mm)
*3,062,000 pages
**3,062 volumes at 1,000 pages each
*Roughly $77,000.
This is far from affordable but is very much in the realm of possible.

===Caveats===
*Format: Wikipedia is not in bounds of volumes, it is in articles. Some utility would have to be programmed to download all of Wikipedia and parse out each article and put them into PDF books to be sent to be "microform"-ified. Wikipedia gives access to anyone to download all of it's text (I don't know about images) in some file format. I do not know how to parse or read this format or if it contains images.
*Table of Contents: You will need a decently sized index or table of contents to make the microform library useful. This is not impossible, but it will have to probably take the form of a book that is 100's of pages long AND the indexing/order of articles must be considered while parsing Wikipedia during the previous caveat.
*Images: I don't think there is an easy way to download images with Wikipedia's text, like it is with Kiwix in the tablet method.
*Reading: This is important. It is not always easy to read microform.
** If your eyes are really good, you can just barely read microform, but most microform storage places have something like a [https://en.wikipedia.org/wiki/Light_table light table] for reading. A light table is definitely a piece of equipment that can require electricity or new manufactured parts, but it's purpose can be met with a magnifying glass. If one is worried about endurance, but several magnifying glasses.
** Microform also requires a source of light. A light table takes care of that. Without electricity, maybe a mirror could use daylight to backlight the microform. Without the light table, one could hold the microform up to the sky for backlighting. The other hand can hold the magnifying glass.
** If you forgo a light table, you would need some device that could hold the microform at a specific page as holding two ends of the microform, keeping the middle part in the light, and holding a magnifying glass is near impossible for one person. A device like this doesn't really exist, but you could model and 3D print something that would meet these needs.
*Endurance: Microform will not last 1000 years like a stone tablet or printed page might, but it is claimed that it can last ~100s of years.

===Other Notes===
*Microfiche might be better. It is like microform but not in a roll. A ''page'' can hold dozens of pages. It would be easier to read than a roll, but it might also take up a little more space. Microfiche ''can'' (some forms of microfiche cannot) hold at a better ratio (~1% vs the ~4% of microform), but a microfiche page is thicker than a piece of paper if stored in a binder, for example. However, microfiche may be easier to index or "flip through" to find what you need, as opposed to spooling through a roll.

Project Marathon

2025-06-27T15:34:11Z

Animationb: Created page with "Project Marathon started out as an effort to build a long range radio project that would transmit data or even pictures over long distances. In the end it just ended up being a test of LoRa's capabilities, where I just tested signal strengths and successful transmissions at various distances. This project page will detail the setup and the tests done. ==Setup== ===Raspberry Pi Pico=== The Pico was used in this project because it's cool and new. But also because when ru..."

Project Marathon started out as an effort to build a long range radio project that would transmit data or even pictures over long distances. In the end it just ended up being a test of LoRa's capabilities, where I just tested signal strengths and successful transmissions at various distances.

This project page will detail the setup and the tests done.

==Setup==
===Raspberry Pi Pico===
The Pico was used in this project because it's cool and new. But also because when running MicroPython, the Pico can act as a easy to use terminal to interact with circuits or chips. In this case, the Pico's SPI capability allowed for control of the RFM95W. Essentially, if you define functions in the ''main.py'' file you upload to the Pico, you can trigger complicated actions with over the REPL terminal.

REPL is actually the key to all of this and it basically makes the Pico act like a Python terminal when plugged into a computer. In short, I only really wanted to control the RFM95W and the Pico offered the easiest interface to do this.

===RFM95W - LoRa Module===
I went with this module because I own two of them and they offer the best range from the modules I could find. (If there is a better module I missed, let me know somehow.) I attached a quarter wavelength antenna to each RFM95W with -3 dBi.

===Software===

==Test Results==

Project Quartz

2025-06-27T15:34:01Z

Animationb: Created page with "'''Project Quartz''' consists of two major components: # Wristwatch - small, comfortable, no wireless capabilities, and decent battery life # Base - connects to the watch to charge it and sync it's clock with GPS ===Project Metrics=== {| class="wikitable" |- | State Date:|| December 2017 |- | Completion Date:|| January 2021 |- | Cost:|| $1,000,000 |} ==Hardware== ===Base=== The base is made up of two stacked 60x160 mm circuit boards housed in a 3D printed case. The Ba..."

'''Project Quartz''' consists of two major components:
# Wristwatch - small, comfortable, no wireless capabilities, and decent battery life
# Base - connects to the watch to charge it and sync it's clock with GPS

===Project Metrics===
{| class="wikitable"
|-
| State Date:|| December 2017
|-
| Completion Date:|| January 2021
|-
| Cost:|| $1,000,000
|}

==Hardware==
===Base===
The base is made up of two stacked 60x160 mm circuit boards housed in a 3D printed case. The Base features three buttons and one 7-segment display. Two buttons are for changing the time zone and the third interacts with the syncing process. The display shows relevant information, depending on what is happening.

The Base is rather large probably a bit over-engineered. If I had to do it again, I would have found a way to make it all smaller.
====Microcontroller====
An '''ESP32''' controls all the Base operations. An '''ESP32 DevKitC''' is plugged into female headers on the Base. From there is controls the powering up and running of the '''GPS Module''', the setting of time zones, the 7-segment display, and the time message that is sent to the Watch. The '''ESP32''' is in Deep Sleep most of the time and only wakes up when syncing the Watch.

Originally, I went with the '''ESP32''' because I had never worked with it before and I had the intention of using NTP time over WiFi as a backup to GPS, but that was more work that it was worth. I should have gone with the '''ATSAMD21G18''' or a variant with more pins.

====Power====
The power system is intricate but robust. The base is charged via a Micro USB port (USB-C is still out of my scope), which charges two 18650 Li-Ion batteries. The batteries are boosted to the necessary 5V for the ESP32 and 7-segment display. Also part of the Base's power system is a second Lithium battery charger for the Watch's battery (to save space on the Watch). The Base draws 6mA when sleeping, giving it a battery life of over 30 days while sleeping.

* '''Lithium Chargers''' - MCP73871 - Great lithium battery charger (lipo and li-ion), I have used it many times and always been happy with it
* '''Voltage Booster''' - TPS61020 -
====Miscellaneous====
The '''7-Segment Display''' is just a 3 digit display that says gives time sync status and shows the time zone.
The '''GPS Module''' locks onto GPS satellites and sends an NMEA message to the '''ESP32''', of which the time is parsed.
====Models====
Base Eagle files (schematics and boards): [[:File:BaseEagle.zip]]

Base 3D files (.stl): [[:File:BaseSTL.zip]]
===Watch===
The Watch's main component is a 28x25 mm L-shaped circuit board that hosts the microcontroller, Real Time Clock ('''RTC'''), and the Liquid Crystal Display ('''LCD'''). It is contained in a 3D printed case with wrist-straps salvaged from another watch.

====Microcontroller====
An '''ATMega328P''' controls the Watch's functions: reading the time, updating the '''LCD''', and parsing the time message from the Base. The '''ATMega328P''' was selected due to its small package (4x4 mm) and low power consumption.

====Power====
A 60mAh Lithium Polymer battery powers the Watch. The Watch easily lasts longer than a week on a single charge. The battery is charged via a pin when connected to the Base. The charge controller sits on the Base, not the Watch.

====Miscellaneous====
The '''LCD''' is an ERC12864-10 LCD. It is a black and white LCD with a built in backlight. It's resolution is 128x64 pixels.
The '''RTC''' is an RV-3028, chosen for its extremely low power requirements and small size. It is smaller than a grain of rice!

====Models====
Watch Eagle files (schematics and boards): [[:File:WatchEagle.zip]]

Watch 3D files (.stl): [[:File:WatchSTL.zip]]

==Software==
===GPS and NMEA Sentences===
The first step in getting the time is receiving it from the '''GPS Module'''. GPS is normally used to calculate one's location on Earth, however, essential to calculating that, the '''GPS Module''' needs to know exactly what time it is, which the GPS Satellites help achieve. I simply take this time from the module. The '''GPS Module''' outputs National Marine Electronics Association (NMEA) sentences. They are standard across many GPS Modules and each sentence gives slightly different information. Project Quartz uses the GPRMC sentence, because it has the time, along with other basic GPS info (latitude, longitude, altitude, other-udes). Parsing of the NMEA sentence is done by a library I made, included at the end of this section. From the parsed time, the Base converts it into the bytes to be written to the Watch's '''RTC'''. Part of the conversion process relies on Andreas Spiess' [https://github.com/SensorsIot/NTPtimeESP NTP Library], not for NTP, but for its Unix-to-Normal time conversion and calculation of Leap Years and Day Light Saving Time. I did make some small changes to the library to make it not use WiFi.

The only flaw in this process, is that while the Base is sleeping, the GPS Module is turned off (it draws 200mA). So when the Watch is placed on the Base, the '''ESP32''' wakes up the '''GPS Module''' and waits for a lock on the GPS's location and time, which can take up to 5 minutes. I've also found a weird bug where the time generated from my recently locked '''GPS Module''' is exactly 3 seconds fast. However, after letting the GPS stay locked for about 20 minutes, the time becomes correct. I'm not sure what the source of this bug is, but I suspect the '''GPS Module''' is getting old, because it didn't used to do this.

[[:File:NMEAsentenceParser.zip]]

===ERC LCD Driver===
Writing to displays has always been a fun challenge with the '''ATMega328P'''. Due to it's 2KB of SRAM, it cannot hold a buffer for all 128x64 pixels. Therefore, on each screen update, the microcontroller must calculate what pixels are black or white based on the current time. The '''LCD''' is updated in 8-bit tall pages that run the length of the display; therefore, most updates do not include the date. Stored in Program Memory (so it takes up Flash, not SRAM) is a table of the bits needed for numbers 0-9 for their large and small forms. There is also a table for the few letters used. When updating the display, the code uses the current time and the location in the page to determine what bits to pull from the tables and push to the '''LCD'''. Lastly, there are two types of display updates: one that only updates the time, which occurs every second, and the other which updates the time and date, which occurs every hour.

This method saves SRAM, but does cost time in the form of CPU cycles. At the end of the day, the shorter screen update only takes a dozen milliseconds and is barely noticeable. However, designing this code did take a lot more effort. I've found that is always the trade off with microcontrollers, you can either have speed or RAM. If you need more speed you need more RAM, if you don't have enough RAM your speed takes a hit.

===Watch-to-Base Interface===
The interface between the Watch and Base is a complicated and time sensitive handshake, because it sets the time on the Watch. There are 5 pins that are used for this interface, wired differently on each component (Watch vs Base):
* PLACE_W
** Watch - This pin is tied to Ground
** Base - This pin is pulled up, but when it is set Low by plugging in the Watch, the '''ESP32''' wakes up and begins the syncing process
* INT1
** Watch - This pin is pulled down to Ground, but when set High the Watch stops everything and waits for the time message
** Base - This pin is controlled by the '''ESP32''' and let's it tell the Watch to get ready for the time message
* RX/TX
** Watch - Using UART, the '''ATMega328P''' receives the time message and sets the '''RTC'''
** Base - Sends the time message via UART.
* The other two pins are used for GND and VBAT to charge the Watch's battery

The process is mostly described by the pins above, but here it is more clearly. The Watch is placed on the Base, pulling the Base's PLACE_W pin Low. This wakes up the ESP32, which turns on the '''GPS Module''' (if it is asleep) and begins requesting the time. Once the '''GPS Module''' gives the time to the '''ESP32''', it tells the Watch to prepare for the time message and converts the GPS time into a the proper time message. Before sending the time, the '''ESP32''' inserts a delay and adds 2 seconds to the GPS time. This is done to compensate for the time it takes to receive and process the GPS time. Finally the '''ESP32''' sends the time message to the '''ATMega328P'''.

The time message is exactly the bytes that need to be written to the '''RTC''' on the Watch. The time message also includes a multi-function byte at the end. This last byte will tell the Watch how many days until the next "Day Light Savings Event" and on that day, depending on what month it is, the Watch automatically adjusts the hour. The last byte's other function occurs if the time syncing process is cancelled before '''GPS Module''' acquires the time. In this case, the Base only sends the time change if the Watch, Base, and user have changed time zones.

The time message is pretty cool and compact, however by far the hardest part of all of this was working with the '''GPS Module'''. There seemed to me a dozen edge cases where the GPS would get a lock but not the time, or it would have the time but send it a half a second off from what was expected. The code for the Base has a lot of waiting for the GPS to "get its crap together" and produce a reliable NMEA sentence. That is why 2 seconds are added to the time, as mentioned above.

===The Code===
Base Code: [[:File:BaseCode.zip]]

Watch Code: [[:File:WatchCode.zip]]

Main Page

2025-06-27T15:33:50Z

Animationb:

A wiki for 7West (mostly Adriano) to keep track of projects and other important information:

===Projects:===

* [[Project Quartz]]

* [[Project Marathon]]

* [[Offline Wikipedia]]

===Microcontroller/SBC Guides===

* [[ATMega328P]]

* [[Raspberry Pi]]

==== Keeping this as I set up the site ====
* [https://www.mediawiki.org/wiki/Special:MyLanguage/Help:Contents User's Guide]
* [https://www.mediawiki.org/wiki/Special:MyLanguage/Manual:Configuration_settings Configuration settings list]
* [https://www.mediawiki.org/wiki/Special:MyLanguage/Manual:FAQ MediaWiki FAQ]
* [https://www.mediawiki.org/wiki/Special:MyLanguage/Manual:Combating_spam Learn how to combat spam on your wiki]