← Back to All Weeks
Week 17

Week 17: Applications, Implications and Project Development

TrailNAV: scope and intended use

I am developing TrailNAV as a handheld waypoint-navigation device for hikers. My goal is to acquire a location, save it and display the distance and direction back without mobile data. Solar-assisted power is a proposed way to extend use away from a mains supply, subject to charging and runtime tests.

The current build record shows enclosure design, printing, display and solar-panel fitting, and wire preparation. The complete navigation and power system still needs to be demonstrated. My final project page brings the construction record together.

Prior work and design references

Waypoint navigation and solar-assisted handheld devices already exist. My contribution is to design, fabricate and integrate my own prototype, with a documented explanation of its operation and limits.

  • The Garmin eTrex Solar device overview is a reference for saving a current location as a waypoint using a physical control.
  • Garmin’s solar-charging guidance shows that sunlight and operating conditions affect battery-life extension. This is why panel fitting and charging performance are separate questions in my plan.
  • Adafruit’s GPS parsing example distinguishes incoming GPS data, a valid fix and location fields. I use it as a workflow reference, without claiming that its shield or library is installed in TrailNAV.

Any circuit or firmware reused in the final build will need its own source attribution and an explanation of my changes.

What I will design and make

The project combines enclosure CAD, additive fabrication, my own embedded electronics, firmware and physical integration. I have printed the enclosure; the final custom board, software and a separate subtractive part still need to be established. PCB milling is part of electronics production and is not the separate subtractive contribution in this plan.

The controller needs to read location and heading, respond to a waypoint control, store the selected position and update the display. The enclosure needs to support those parts and provide access to controls and connectors. I intend the assembled device to operate independently from the computer used to program it.

Components, sources and budget

For the next build I am using a 1.3-inch I²C OLED as the display target and the XIAO RP2040 as the first firmware target. My new Fusion model and software package record this revision. The exact OLED controller, mounting dimensions and final board still need to be matched to the parts. The table below retains the original proposal prices; it is not the bill of materials for the new OLED version.

Planned componentQtyRecorded unit price (RWF)Recorded line price (RWF)
XIAO ESP32-C6120,00023,600
u-blox NEO-M8N GPS119,68219,682
QMC5883 compass14,5005,310
2.7-inch E-Ink display127,08027,080
3.7 V battery19,00010,620
Solar panel, described as 12 V / 100 mA18,90010,502

This is the provisional planning budget, using the prices in my original notes rather than current quotations. The recorded line prices sum to 96,794 RWF. They do not include the charger/regulator, custom PCB, connectors or enclosure material. The differences between some unit and line prices still need an explanation, so the subtotal is not a verified final build cost.

My original sourcing notes refer to Nyereka Tech for a XIAO ESP32-C3 and Faranux for a NEO-6M, GY-271/QMC5883L, 3.5-inch TFT, 500 mAh battery and solar panel. Those references do not all match the planned component names above. The photographed screen and its test sketch also use a TFT rather than proving the planned E-Ink selection.

I will resolve the actual part identities before freezing the schematic and budget. The supplier references below are retained as planning sources, not proof of purchase or current prices.

Questions and evaluation plan

The main questions are whether the GPS acquires a reliable fix, whether a saved waypoint survives restart, how the compass behaves inside the enclosure, and whether the panel supplies useful energy compared with the device load. I will evaluate these functions separately before relying on a combined demonstration.

FunctionPlanned acceptance check
LocationAcquire a valid outdoor fix, record coordinates and fix information, and compare with a known reference.
WaypointsSave a location, restart the device and retrieve the same waypoint. Show distance and direction changing during movement.
HeadingCalibrate the compass and compare readings at known directions, both outside and inside the enclosure.
Offline useComplete the save-and-return workflow without a network connection.
PowerMeasure load and charging behaviour under recorded conditions using the actual charging circuit.
RuntimeRun a timed battery test with a recorded display update rate and operating mode.
PackagingOperate with the cover closed, secured internal parts and accessible controls.

Development sequence

I will work through the stages below in dependency order. Hardware identification comes first because it determines the PCB, firmware and enclosure interfaces. The final review follows the assembled-device tests.

StageWork and dependency
1 — Confirm the hardwareIdentify the actual controller, display, GPS, compass, battery and charging circuit. Resolve their voltage and interface requirements before finalizing connections.
2 — Build and check the electronicsComplete the board design and fabrication, then test its power rails and individual input/output connections.
3 — Implement the navigation loopAcquire valid location and heading, store a waypoint and drive the actual display before closing the enclosure.
4 — Complete the physical assemblyFinish the project’s subtractive part, mounts, connectors and wire routing after the component interfaces are settled.
5 — Test the assembled deviceRun the waypoint, offline-operation, charging and runtime checks with the intended power source and enclosure.
6 — Publish the completed buildAdd the final sources and results, update the presentation and review the project with the instructors.

The present enclosure work gives me a starting point for integration. The next priority is to settle the actual electronics and power arrangement, then produce a small working navigation loop before adding further features.

Presentation drafts

The summary slide and construction video are available in 1920 × 1080 format, with an editable SVG slide source. They show the project idea and construction progress. A final operating demonstration and confirmation of the presentation-schedule links will follow when the complete device is tested.