3D printing filament calibration dashboard

As my 3D printing setup became more capable, the filament-management side became harder to trust. Bambu Studio stores filament presets, process profiles, printer settings, AMS material assignments, and K / Flow Dynamics calibration data in ways that are useful to the software but not always clear to the person trying to maintain a consistent setup.

The practical problem was simple: with multiple nozzle sizes, standard and high-flow hotends, left and right toolheads, and many filament presets, it became difficult to answer which values were actually calibrated and which ones were inherited defaults.

I started building a local calibration-management dashboard to make that information visible. The tool scans Bambu Studio filament preset files, pulls out the settings that matter most, and presents them in a searchable dashboard. It can compare profiles side by side, highlight meaningful differences, and help identify near-duplicate presets that should probably be cleaned up or consolidated.

A key part of the work was tracking K / Flow Dynamics values. Instead of relying only on Bambu Studio’s less visible printer-side calibration records, the tool stores calibration notes in a structured block inside the existing filament notes field. That keeps the information close to the filament profile, makes it human-readable, and preserves any notes that were already there.

The dashboard focuses on the settings that affect real printing decisions: flow ratio, maximum volumetric flow, temperatures, cooling, nozzle and hotend context, and calibration values. The goal is not to replace Bambu Studio, but to make its preset data easier to audit and maintain.

I built the first version in Python with a Streamlit interface so it could be tested quickly on macOS and Windows. Because the tool edits local preset files, I treated safety and reversibility as part of the design. Before writing changes, it creates backups, validates the JSON files, and logs what changed so the workflow is easier to trust.

This is a personal tooling project, but it reflects a broader process-improvement pattern: when a system becomes too complex to manage reliably by memory, make the important information visible, comparable, backed up, and easier to maintain.