← Back to All Weeks
Week 18

Week 18: Invention, Intellectual Property and Income

Who I want to share TrailNAV with

My first audience is the Fab Lab community and people interested in building outdoor electronics. Hikers can also help me understand whether the controls, screen and enclosure are useful in practice. I want the documentation to explain both how the prototype is made and what it has actually demonstrated.

Dissemination plan

I plan to publish a build guide through this website, with the editable enclosure and board designs, firmware, component list and test results. A short demonstration will show the normal workflow: acquiring a location, saving a waypoint and using it again. The slide will provide a quick introduction and link back to the full build.

After the prototype works, I plan to present it at the lab and invite a small group of outdoor users to try the controls and read the display. Their feedback will guide the next revision. I would record the conditions of those trials and keep user suggestions separate from measured device performance.

Reuse and intellectual property

MIT licence notice · Documentation licence and scope · CC BY 4.0 terms

I selected the MIT License for my original code and Creative Commons Attribution 4.0 International (CC BY 4.0) for my original written documentation. The licence notices are included with the source downloads. Reused libraries, circuits, graphics, group contributions and models retain their own terms; unidentified reference artwork is not granted a new licence by my choice.

The original design files and acknowledgements matter because another maker needs to know which parts I created, which parts came from elsewhere and what can be changed or redistributed. AI assistance for the website and written revisions is described in Week 1.

Future development and possible income

A smaller board, a lower-power display and a more serviceable enclosure are possible later improvements, but the first priority is the complete waypoint workflow and a measured power budget. I would choose the next feature based on the tests and user feedback rather than adding hardware without a demonstrated need.

A kit, workshop build or assembled unit could be explored later. Before pricing one, I need the verified parts cost, assembly time, enclosure cost and repeat-build results. I have not established a production budget or income forecast. The immediate dissemination route is the documented prototype and a lab demonstration.

Progress, remaining work and sequence

The enclosure is designed and printed, and the display and solar-panel fitting are photographed. The navigation loop, final PCB, charging circuit, outdoor checks and runtime results remain to be completed or documented. At present I can describe the packaging progress; I cannot claim a validated navigation product.

I will settle the component choices, complete and test the electronics, implement navigation, finish internal mounting and then run the full-device tests. The project-development plan gives that sequence. Publishing the final build and gathering user feedback come after a working-device demonstration.

What I have learned

A project is easier to share when the files, instructions and results agree with one another. A device can look finished while its power or software is still being developed. Keeping the built parts, proposed functions and measured results clear helps me decide what to work on next and gives other makers a more useful starting point.

What I can share from the current revision

The current 1.3-inch OLED source package now contains an editable Fusion model, STEP/STL/DXF exports, the generator, firmware and a local 3D viewer. Publishing those files is different from claiming that the assembled navigation device has passed its outdoor and power tests.

I need separate reuse terms for my original writing, code and designs, and I need to retain the terms of reused material. For example, CC BY 4.0 permits reuse of documentation with attribution, while the MIT licence is an option for my original software with its copyright and licence notice retained. These are the terms I selected for my own code and written documentation. Native CAD and hardware design files still need explicit design-specific terms; the code/text selection does not silently relicense them.

The OLED package identifies TinyGPSPlus, the Adafruit display libraries and the locally bundled Google model-viewer separately. Those components retain their own licences. Unattributed reference artwork and group contributions are not automatically mine to relicense. I will finish the attribution record before applying any broader licence to the archive. My code and text notices do not override those third-party terms.

For feedback, I want users to try saving a waypoint and reading the return information, then tell me where the controls or display are unclear. I will keep that feedback separate from measured accuracy, runtime and charging results. A kit price still needs actual component and assembly costs; I have not invented an income forecast.