Read your engine like a race engineer.
Drop an MHD datalog to map boost error onto your base table, plot dyno-style power and torque, and trace knock cell by cell. Then tune the bin itself — from your own XDF, on desktop or in the car.
Personal best from a logged pull — not live output.
Analyze→
Boost, WGDC, timing, knock, AFR, load, rail, EGT — every channel mapped cell by cell against your base table.
PowerDyno→
Peak and sustained-average power & torque, plotted like a dyno sheet, with true 100–200 km/h timing from the log.
KnockHeatmaps→
Timing pull and knock events rendered as a heatmap over the RPM-and-load grid — every cell that retards timing, flagged at a glance.
ReplayLive→
Replay a pull in real time — target versus actual boost, WGDC, and the active base-table cell lighting up as the run unfolds.
SuggestDial→
Feed a base table and a stack of logs to get per-cell WGDC suggestions, each traced to P-Factor, boost error, and sample count.
BinTune→
Load your own XDF and bin. Read every table, edit values, export a flash-ready file — the whole loop, in the browser.