How renatobo/bonogps works
Main Components
a. Hardware Layer:
• ESP32 Device – the central processing unit running the embedded firmware.
• GPS Receiver(s) – support for u‐blox M8 and M10 series modules (e.g., BN880, BN220).
• Power/Battery and associated peripheral hardware (assembled parts, 3D printed components) found in hardware/assembled and hardware/esp32.
b. Firmware/Software Layer:
• Core Firmware – the source code in src (e.g., bonogps.cpp) and supporting headers and settings in the include folder.
• Connection Handlers – separate modules for interfacing with different connection transports such as BLE, BT-SPP, and TCP-IP (reflected in the software/connecting folder with app-specific configurations).
• Web-based Configuration Interface – the HTML/CSS assets (in software/using and include subfolders) that empower on-device configuration over WiFi.
• Build System – the PlatformIO configuration (platformio.ini and build scripts) indicating dependencies and build instructions.
c. External Interactions:
• Mobile Applications – external devices using apps like Harry’s Lap Timer, RaceChrono, RaceTime, and TrackAddict that receive GPS data (initialized by connecting over BLE/BT/TCP-IP).
• uBlox u-center – debugging/configuration tool via TCP-IP for GPS setup (as referenced in the README).
Relationships and Interactions
• The firmware processes these GPS messages, applying any settings found in configuration headers (include), then dispatches the processed data via multiple connectivity stacks:
• Over BLE (for iOS support especially).
• Over BT-SPP (for Android devices, as well as other app compatibilities).
• Via TCP-IP (allowing connectivity both from mobile apps and uBlox u-center for configuration).
• Finally, the external mobile apps are shown connecting and receiving data through these various interfaces. They can also (optionally) inspire configuration changes that loop back via the web interface.
Architectural Patterns / Design Principles
• Modular Separation – The file tree is clearly divided between hardware (with schematics, assembly, and GPS configurations) and software (with dedicated modules for building and connecting), which implies a clean separation of concerns.
• Configurability – The presence of runtime configuration and preset save/load functionality of the device should be highlighted. The web configuration interface is a key component, and its role in altering behavior (like toggling WiFi modes) should be clearly depicted.
Tools and Technologies
• ESP32 microcontroller.
• u-blox GPS receivers.
• PlatformIO (for build and development).
• Web technologies (HTML, CSS) for the configuration interface.
• Bluetooth and WiFi stacks of the ESP32.
• Mobile app integration proxies for Harry’s Lap Timer, RaceChrono, etc.
Essential Elements
• Clear labels for every component (e.g., “GPS Receiver,” “ESP32 Processing Unit,” “BLE Service Module,” “Web Server”).
• Interface types (UART for hardware interconnect, WiFi for web interface, Bluetooth for direct mobile app connectivity).
• Annotations for configuration paths such as “Device Configuration via Web Interface” or “Preset Loading / Saving” based on the README.