Platforms
Any platform. Any format.
Every tuning platform logs data differently -- different column names, different units, different conventions. TBK Logs normalizes all of it automatically, regardless of source.
Supported tuning software
Upload CSV exports from any of these platforms. Format is auto-detected on upload.
bootmod3 (BM3)
Full CSV support. Fuel trims logged as ratios -- we normalize to percentages. IAT = post-intercooler. Auto-detected on upload.
MHD Flasher
Full CSV support. Fuel trims as percentages. IAT = pre-turbo air (different from BM3). Boost in PSI. Auto-detected.
Ecutek RaceROM
Full CSV support. Boost in hectopascals, HPFP in megapascals, lambda as ratio instead of AFR. All converted automatically.
COBB Accessport
CSV log support for Subaru, Ford, and more. Channel layout varies by vehicle -- parser handles all variants.
Hondata
Honda/Acura CSV logs. Different channel naming and layout -- fully supported with auto-detection.
HP Tuners
Multi-platform CSV support. GM, Ford, Dodge, and more. Channel mapping handled automatically.
JB4
BMW and other platforms via the JB4 data format. Different channel layout handled automatically.
Haltech
Standalone ECU CSV logs. Flexible channel mapping supports custom configurations.
MoTeC
Professional motorsport data acquisition. CSV export with full channel mapping support.
AEM
AEM Infinity and Series 2 data logs. Auto-detected channel mapping.
Syvecs
Standalone ECU CSV logs with custom channel naming. Fully supported.
MG Flasher
Mercedes-AMG tuning platform. CSV export with channel normalization.
PTF
Performance Technic flash logs. Auto-detected on upload.
Other (CSV)
Any platform that exports a standard CSV with recognizable parameter names. Fuzzy column matching maps your data to our analysis engine automatically.
Engine platform support
Each engine platform has calibrated thresholds, known failure modes, and platform-specific analysis logic.
How platform normalization works
The same analysis engine runs on every log. The parser handles all the platform-specific differences so you don't have to.
BM3 logs fuel trims as ratios, MHD logs them as percentages, Ecutek also uses percentages -- we normalize everything.
MHD's IAT means pre-turbo air while BM3's IAT means post-intercooler air -- we know the difference.
Ecutek logs boost in hectopascals, HPFP in megapascals, and lambda as a ratio instead of AFR -- we convert it all.
JB4 exports use a different channel layout and naming scheme -- the same parser handles it. Platform is just a format detail.
If your platform logged it, we use it. If a parameter wasn't included, we tell you exactly what to add to your logging config next time.
See it in action
Browse sample reports to see how TBK Logs analyzes logs from different platforms and engines.
Don't see your platform?
Select "Other" when uploading. Our fuzzy column matching engine scans your CSV for recognizable parameter names and maps them to the analysis engine automatically. If your platform exports a standard CSV with common channel names (RPM, Boost, AFR, Knock, etc.), there's a good chance it works out of the box.
If we can't match enough columns, we'll tell you exactly which parameters to add to your logging configuration. No guesswork.
Want dedicated support for your platform or engine? We actively add new platforms and engine profiles based on community requests. Let us know what you drive and we'll prioritize it.
Ready to analyze? Upload your first log.
Get Started$6/month for drivers. $40/month for tuners. Or $5 per single log. Cancel anytime.