HEAT UP THE DATA.
COOL DOWN THE COMPETITION.
Hot Flash is a serious OBD2 dashboard + logger with a videogame HUD vibe— delivering real telemetry: RPM, speed, temps, throttle, MAP/boost estimation, logs, and run summaries.
Features that feel illegal (but aren’t)
Poster energy up top. Tool energy where it matters. Here’s the “serious useful” checklist.
Race HUD Dashboard
High-contrast gauges, shift-light behavior, limiter flash, alerts, and themes that react to RPM.
- RPM / speed / throttle / temps / MAP / volts
- Shift cues with redline targets
- Track-friendly readability
Logging + Export
Record sessions and export clean CSV logs for graphs, replay, or analysis.
- One-click record
- CSV export in seconds
- Replay-ready structure
Run Analysis (Next)
Built to expand: 0–60, 60–130, peak metrics, run compare, and overlays.
- Acceleration timers
- Peak RPM / speed / temps
- Session summaries
WebSocket Bridge Ready
OBD2 dongles don’t always play nice with browsers. We bridge locally and stream data clean.
- Local Node/Python bridge
- Works with USB/BT/Wi-Fi dongles
- Stable telemetry feed to UI
Modular by Design
Swap data sources without rewriting UI. Sim mode for dev, real mode for the car.
- Simulated stream (dev)
- Real stream (bridge)
- CSV playback (replay)
Driver-first Safety
Big readouts, minimal distractions, and clear warnings. This is meant to be glanced at.
- Focus on critical info
- Optional alerts
- Clean layout scaling
How it works
Three steps. No drama. Unless your coolant temp wants to become a plot twist.
Quick Start
*Timing availability depends on vehicle / PID support.
**AFR is estimated unless a wideband is integrated.
What makes it “serious”
It’s flashy on purpose—but the structure is clean so you can actually build on it.
- One telemetry object → UI never cares where data comes from
- Bridge-based approach → fewer connection headaches in browsers
- Log format first → analysis becomes easy later
- Readable at speed → minimal clutter, clear hierarchy
OBD2 Bridge
Browsers + OBD2 dongles are awkward. The bridge is the adult in the room.
Recommended setup
Local bridge reads the adapter (USB/Bluetooth/Wi-Fi) and streams JSON telemetry over WebSocket.
- Bridge: Node.js or Python
- UI connects to ws://localhost:8787 (editable)
- Format: JSON keys like
rpm,speed_mph,throttle,ect_f…
Privacy / safety
You own your data. Default design is local-first.
- No cloud required
- Logs stay on your machine unless you export/share
- UI is glance-friendly — don’t stare at it while driving
Disclaimer: For off-road / track use and testing. Always prioritize driving and safety.
Ready to launch?
Use this landing page as your front door. Then link the real dashboard behind it.
Tip: point “Launch Hot Flash” to your dashboard URL once it’s hosted.
Contact
Need a branded variant (more “tuning suite”, less “dashboard”)? Easy rewrite.
GitHub Pages friendly: just drop index.html + hf-logo.png.
FAQ
Real questions, real answers. No marketing smoke machine.
Do I need an assets folder?
Nope. If hf-logo.png is next to index.html, you’re good. If you use /assets, change the logo path to assets/hf-logo.png.
Will this connect directly to my Bluetooth OBD2 dongle?
Usually not in a normal browser. The clean solution is a local bridge that talks to the dongle and streams data to the UI via WebSocket.
What should the main CTA link to?
Best practice: link it to your dashboard app (hosted HTML, Electron build, or download page). It’s editable at the top in the window.LANDING config.