BostromLabs engineering platform
BostromLabs is the parent platform. AeroTune remains the flagship internal-style workstation for FPV Blackbox analysis, conservative PID deltas, tune-change validation, parser reports, and Blackbox utility workflows.
Flagship tool
Dark engineering UI for FPV Blackbox analysis, PID recommendation deltas, motor-temperature safety, parser reporting, and safe next-flight planning.
Standalone helper
Answer symptom sections like motor temperature, throttle behavior, propwash, vibration, filtering, and recent changes. Pilot-Helper returns practical checks without changing AeroTune PID logic.
Using AeroTune
My active 7-inch FPV testing platform, now running 6045 props for a lighter, more controllable setup while AeroTune validates tune changes from real Blackbox logs.
Active test buildConversion, CSV optimization, parser reports, and file-prep tooling separated from the main tuning screen.
FPV build updates, flight tests, AeroTune development, and engineering notes tied back to real testing.
Integrated sectionYouTube updates, Patreon support, Discord community, GitHub source links, and the creator background in one cleaner section.
Platform supportAeroTune workstation
Use this page for the normal log → recommendation → test-flight loop. Advanced parser and machine outputs are still available, but the first screen stays focused on the recommendation, suggested values, safety limits, and next flight.
Upload a Betaflight CSV export directly. You can also upload a raw .BBL, .BFL, or .TXT Blackbox log; AeroTune will use the local blackbox_decode converter to turn it into a CSV first, then analyze that converted CSV.
⬇ Download optimized CSV from this logNo analysis yet.
Current drone build using AeroTune
This is the active quad I am using to test AeroTune against real Betaflight Blackbox logs. The frame is a 7-inch long-range style build, but the current prop setup is 6045 to calm the platform down, reduce the heavy 7-inch prop feel, and give AeroTune cleaner before/after data while I work toward a more locked-in tune.
A large FPV test rig built around a 7-inch class frame, tuned with AeroTune instead of random PID guessing. It is currently being tested with 6045 props to improve response, reduce load, and make the quad easier to evaluate from logs.
The build is centered around the hardware stack used in recent AeroTune testing: a GEPRC MARK4-style 7-inch frame, TSiDo 2807 1300KV motors, RushFPV flight stack hardware, analog video, ELRS control, and GoPro flight footage when needed.
The build started as a 7-inch platform, but full 7-inch props felt too much for the current testing direction. The 6045 props should make the quad feel more manageable, help reduce heavy prop load, and give cleaner feedback while tuning.
AeroTune workflow
Each flight can be logged, converted, analyzed, and compared through AeroTune. The goal is to move from a safe baseline toward a more locked-in tune using measured overshoot, bounceback, noise, motor/PID clues, and motor-temperature safety context.
Standalone FPV troubleshooting tool
Pilot-Helper is separate from AeroTune analysis. Use it when you know how the quad felt but do not yet know what to inspect. It turns symptoms into likely causes, safety checks, and the next log you should capture.
Select only what actually happened. The helper will prioritize safety and mechanical checks before tune changes.
AeroTune utility bay
Conversion, optimization, and parser inspection live here so the main analyzer remains clean. This is where users prep logs before serious tuning work.
CSV files are cleaned into AeroTune-ready columns. Raw .BBL/.BFL/.TXT Blackbox logs are automatically converted into CSV first, then cleaned into the same AeroTune-ready format.
Raw Blackbox files need Betaflight blackbox_decode. On Render, set the Build Command to bash scripts/render_build.sh. CSV uploads still work without this converter.
AeroTune advanced systems
This page keeps experimental and high-detail tools away from the primary workflow until they are mature. Safety warnings should always override style goals here.
Future frequency-domain diagnostics for gyro noise, D-term noise, and filter decisions.
PlannedFuture speed-aware analysis, efficiency scoring, mAh per distance, and rescue validation.
PlannedFuture guidance for dynamic notch, RPM filtering risk, and high-rate logging interpretation.
PlannedBostromDev / BostromLabs
This page consolidates the public-facing parts of BostromLabs into one cleaner section: who is building it, where to watch updates, and how to support the project.
BostromLabs is a practical engineering/software platform created by bostromdev to document real tools, FPV flight testing, mechanical projects, and engineering experiments over time.
Watch FPV flights, AeroTune progress, build updates, testing clips, and practical engineering notes connected to the tools on this site.
Primary media linkSupport helps cover hosting, development time, testing, documentation, and future local-download workflows for serious Blackbox analysis.
Source, releases, documentation, and project organization under the BostromDev ecosystem.
Community discussion for AeroTune testing, FPV logs, tuning questions, and future tool feedback.
BostromLabs is a place to share builds, tools, experiments, lessons learned, and real progress without fake startup fluff.
Consolidated sectionSetup, workflow, and safety
Keep setup instructions and tuning education out of the tool screens. These links are served from the local docs/ folder when the FastAPI app is running.
Local setup, Python environment, and running the site.
Open guideSafe interpretation of recommendations and field-test workflow.
Open guideHow pilot notes influence tuning without replacing Blackbox evidence.
Open notesBefore/after workflow for validating whether a change helped.
Open notesImplementation notes for the Home Hub and dedicated tool-view split.
Open notesCurrent state, site structure plan, and Pilot Performance style profiles from the workflow package.
Open redesign planExternal Blackbox tooling, Betaflight documentation, open-source libraries, and non-affiliation notes.
Open creditsCredits, references, and transparency
AeroTune is a BostromLabs / BostromDev project. Raw Blackbox conversion and several tuning concepts are grounded in outside tools and documentation, so this page makes those dependencies clear.
Created by Christopher Bostrom / BostromDev. The parser wiring, conservative scoring, tune-change tracking, UI organization, and output formatting are BostromLabs implementation work unless a file says otherwise.
BostromDev GitHubRaw .BBL/.BFL/.TXT conversion depends on the external Betaflight blackbox-tools project and its blackbox_decode executable when built on the host.
Open blackbox-toolsAeroTune's conservative heuristics are informed by official Betaflight tuning guidance such as bounceback, I-term hold, propwash, high-throttle oscillation, and motor-heat caution.
Open PID guideBlackbox logging, CSV export, multi-flight logs, and external log viewing are part of the wider Betaflight Blackbox ecosystem.
Open Blackbox ExplorerDetailed notes for blackbox_decode, Betaflight references, Python libraries, non-affiliation, and licensing boundaries.
Open local credits fileBostromLabs / AeroTune is independent and is not affiliated with, sponsored by, or endorsed by Betaflight, Blackbox Explorer, Nicholas Sherlock, or any referenced third-party project.
Open docs