HydrateOS Idea
Publicada el 2026-07-30
Descripción de la oferta
I have three tightly linked components that must come together as a single, reliable hydration-management solution for elite, high-contact sports. 1. Wearable arm-band firmware The arm-band houses electrolyte sensors only, so the code you create must interrogate those sensors at high frequency, timestamp every sample, encrypt the packet, and stream it over BLE with sub-second latency. Lossless reconnection after tackles or rapid sprints is critical. Low-power operation (full match on one charge) and an easy DFU path are also expected. 2. Sideline dashboard & analytics Live telemetry from multiple players must arrive in a browser or tablet—both form factors are required so coaches can pull it up on a laptop while trainers move with an iPad. A cloudless local-network option is preferred for stadiums with poor uplink. Once the data lands, the software must calculate each athlete’s electrolyte replenishment needs in real time and surface a clear “mix X mL of concentrate with Y mL of water” instruction. 3. Automated dispenser logic Those mix instructions drive a closed-loop pump and valve assembly. Your control software has to read the current formula, run a PID routine to hit the exact ratio, flush the line between athletes, and confirm volume delivered before clearing the bottle ID. Deliverables • Production-ready firmware (C/C++ or Rust, Nordic nRF52 family preferred but flexible) • Web/Tablet dashboard with real-time graphs, rule engine, and secure player profiles • Dispenser micro-controller code plus a small test harness that proves dosing accuracy ±1 % • Build scripts, reproducible environments, and concise hand-off docs Acceptance criteria • Zero packet loss for at least 90 min of continuous play across 20 active units • Dashboard latency from sensor read to on-screen recommendation ≤2 s • Dispenser delivers target ratio within ±1 % on a 500 mL bottle, verified over 30 cycles Please attach a detailed project proposal that walks through architecture, component choices, and an estimated timeline with milestones. Past work and general experience are helpful, but the proposal itself will weigh most heavily in selection.
Skills
Fuente original: freelancer