About CobbVision

Our mission

Reading a raw Accessport CSV is hard. Hundreds of rows, dozens of cryptic column names, and thresholds that only make sense relative to RPM and boost. Most owners either pay a tuner to glance at every log or — worse — ignore the warning signs. CobbVision exists to give Cobb Accessport tuners a fast, honest, and vehicle-aware read on every datalog, so a healthy log looks healthy and a real problem stands out immediately — for every Accessport platform, not just Subaru.

What CobbVision does

• Parses Cobb AccessPort CSV datalogs, aliasing every column-name variant to a canonical key (132-monitor alias map).
• Computes a health score (0–100) from anomaly density and critical-event count.
• Runs RPM- and boost-scoped anomaly detection — thresholds adapt to load rather than firing flat alarms.
• Performs knock analysis across DAM, Feedback Knock Correction, and Fine Knock Learning to distinguish real detonation from false knock.
• Applies a cross-channel relationship engine for failure signatures single gauges miss.
• Replays sessions in a Datalog Player with gauges, sparklines, and a GPS lap map.
• Builds Cobb AP Preset (.ptc) files, tracks vehicle profiles, and generates AI narratives.

Methodology

CobbVision's analysis is deliberately vehicle-aware rather than a generic OBD threshold checker. Deep Subaru knowledge (EJ/FA-DIT engine families, DAM/FKL/FKC knock logic) forms the foundation; rules are tiered by manufacturer, model, and engine family so they apply precisely to the vehicle being analyzed:

• Scoped, not flat. Anomaly detection is scoped to RPM and boost. A lean AFR at cruise is normal; the same value under boost is flagged.
• Real vs false knock. Subaru's single knock sensor picks up mechanical noise that isn't detonation. CobbVision judges by how DAM, feedback knock, and Fine Knock Learning move together at WOT under positive boost — not by any single blip.
• Engine-family aware. A sub-1.0 DAM is a warning on an EJ but often normal on an FA DIT engine, where DAM fluctuates as a proactive octane compensator. Rules are scoped to EJ, FA-DIT, FA24, or universal.
• Assess what we know. Relationship scoring excludes sessions that didn't log a given channel, so a missing monitor never counts against a vehicle's score.

Where the data comes from

CobbVision's interpretations draw on three clearly-separated bodies of knowledge:

• Cobb monitor list & OTS map notes — the canonical channel/parameter list, thresholds, knock-monitoring logic, and per-map notes derived from official Cobb Tuning documentation.
• Community tuning wisdom — false-knock-vs-real-knock heuristics, AFR targets, and failure signatures from enthusiast and tuner communities (NASIOC, ClubWRX, IWSTI, RomRaider, Reddit r/WRX). These are community-validated rules of thumb, seeded separately so their provenance stays clear.
• Other data — NHTSA vPIC for VIN decoding and user-supplied GPS tracks (GPX / NMEA / UBX / CSV) for lap correlation.

The full source-by-source breakdown lives on the Data Sources & Credits page.

Non-affiliation disclaimer

CobbVision is an independent analysis tool and is not affiliated with, endorsed by, or sponsored by COBB Tuning Products LLC, Subaru Corporation, or any other manufacturer. “COBB”, “Accessport”, “Subaru”, “WRX”, and “STI” are trademarks of their respective owners. Reference data derived from manufacturer documentation is reproduced for vehicle owners' personal diagnostic and educational use. CobbVision provides diagnostic insight, not tuning advice — always validate with a wideband and a qualified tuner before changing a calibration.