TrailNAV is my proposed handheld waypoint-navigation device. The intended use is to save a location and display the direction and distance back without mobile data. At this review stage, I have enclosure design and fitting work to build on; the complete electronics, firmware and power tests are still under development.
This diagram shows the intended functional blocks, using the original component proposal. It is not a pin-level wiring diagram or an as-built component list. The controller and display choices need to be reconciled with the actual hardware before the connections are finalized.
The GPS provides position and the compass provides heading. The controller would store a waypoint and calculate information for the display. Power would pass through a charging and regulation arrangement suited to the selected battery and electronics; an MPPT controller has not been established for this build.
My weekly archive covers website setup, CAD, cutting, embedded programming and electronics fabrication. The RP2040 board exercises give me experience with inputs, outputs and computer-to-board communication. The enclosure work applies CAD and printing to the final project.
The scan reconstruction, physical networking demonstration, complete machine-contribution record and several measured fabrication results still need to be added. I will use the weekly pages to connect each result with its process and original files, rather than treating the final project as a replacement for those assignments.
I plan to use the following sequence so that unresolved hardware choices do not carry forward into the finished enclosure. The detailed budget and function tests are in Week 17.
| Stage | Work and dependency |
|---|---|
| 1 — Confirm the hardware | Identify the actual controller, display, GPS, compass, battery and charging circuit. Resolve their voltage and interface requirements before finalizing connections. |
| 2 — Build and check the electronics | Complete the board design and fabrication, then test its power rails and individual input/output connections. |
| 3 — Implement the navigation loop | Acquire valid location and heading, store a waypoint and drive the actual display before closing the enclosure. |
| 4 — Complete the physical assembly | Finish the project’s subtractive part, mounts, connectors and wire routing after the component interfaces are settled. |
| 5 — Test the assembled device | Run the waypoint, offline-operation, charging and runtime checks with the intended power source and enclosure. |
| 6 — Publish the completed build | Add the final sources and results, update the presentation and review the project with the instructors. |
For the local and global instructor review, I will present this system proposal, the weekly progress and the development sequence. The questions to resolve are the final electronics scope, the separate subtractive part, the power arrangement and the practical order of testing.
The review outcome has not yet been recorded here. After the meeting, I will document the agreed scope, priorities and feedback, then apply those decisions to the project plan.
I can now present the 1.3-inch OLED revision alongside the original proposal. Its Fusion model, design captures and first RP2040 firmware are available. The firmware builds and the digital model can be inspected, while the real GPS/display, persistent waypoint and closed-device tests still need to be recorded.
| Bench connection | Current software target |
|---|---|
| Controller | XIAO RP2040, Arduino-Pico core 4.5.3 |
| GPS data | GPS TX to D7/GPIO1, NMEA at a configurable 9600 baud |
| Display bus | D4/GPIO6 SDA, D5/GPIO7 SCL; 1.3-inch 128 × 64 I²C OLED, exact module pending |
| Waypoint button | D2/GPIO28 to GND, internal pull-up |
| First power source | USB; battery, charger and panel circuit remain separate design work |
| Heading | Current firmware shows true-north bearing to the waypoint; compass-relative heading is not implemented yet |
This is a proposed bench pin map, not the final as-built wiring. I need to check that the fabricated board exposes these signals and that each module has compatible supply and logic levels. The archived electronics findings in Week 6 must be resolved against the actual board before a repeat fabrication.
I will bring the working-loop results, the new enclosure source and the unresolved power/circuit choices to the instructor review. No local or global review approval is claimed until its actual feedback is recorded.