How gopro2027/arduinoairsuspensioncontroller works
Main Components
• Main Board Firmware – Represented by the OASMan_ESP32 directory; this firmware runs on the ESP32 controller and handles sensor inputs, actuator outputs (compressor, valves, solenoids, etc.), and overall air suspension logic.
• Wireless Controller Module – Shown by the Wireless_Controller folder; this dedicated controller (with its associated PCB design and embedded code) provides an alternate interface (via BLE/Bluetooth) to control the system.
• Mobile Application – Two parts exist here:
– The new MobileApp (Flutter based using BLE) for modern user interaction.
– The legacy AirSuspension Android app (for traditional Bluetooth).
• Shared Libraries – ESP32_SHARED_LIBS holds shared configuration and common code between the main board and the wireless controller.
• Hardware Design & Manufacturing – PCB folder (with versioned Gerber files, DXF designs, etc.) and 3d Prints (STL files, 3D printable housing for manifolds, sensors, and display elements).
• Supporting Tools – LCDImageCreatorTool (for generating images for the tiny 128x64 display on the manifold) and PS3_Controller_Tool (for pairing a PS3 controller as an alternative control scheme).
• Tutorial & Documentation – The tutorial directory contains build instructions that help tie together the physical assembly and wiring.
Relationships and Data Flows
• The mobile app communicates via Bluetooth Low Energy (or traditional Bluetooth on legacy systems) to the Wireless_Controller and/or directly to the OASMan_ESP32 main board.
• The Wireless Controller module itself acts as a bridge to the main board, receiving commands from the mobile app or alternative inputs (for instance, from a PS3 controller configured by the PS3_Controller_Tool).
• Both controllers (ESP32 and wireless module) use shared code components from the ESP32_SHARED_LIBS.
• On the hardware side, the PCB designs and 3D printed parts physically integrate sensors, valves, compressor connections, and display components (like the tiny screen managed via the LCDImageCreatorTool).
Architectural Patterns and Design Principles
• The system is designed in a modular fashion: individual subprojects separate concerns (e.g., motion/sensor processing, connectivity, UI) while sharing common libraries/config files.
• There is clear separation between hardware (PCB, 3D printed hardware), embedded firmware (OASMan_ESP32 and Wireless_Controller), and the user interface layers (mobile app and supporting PC tools).
• Data flow relies on well-defined communication channels (Bluetooth/BLE), with the mobile apps acting as the user interface layer and the embedded systems managing the control logic and interfacing with physical components.