A CANBUS logger, highspeed recording, GPS TimeSync, all tied to robust data review tools.

OBD2 by its nature was never meant to be high speed data, mandated by governments and only for your local tech to diagnose your car. The OBD2 protocol works by requesting data in an ASK > WAIT process, for EACH individual data point. The more data points you want, the longer it takes for the ECU to process and respond to each data point. CANBUS meanwhile is the network of modules in your car, constantly publishing datapoints at up to 100x the speed at which OBD2 can report, while also exposing data that the OEMs chose not to allow over OBD2 (such as steering angle, brake pressure, yaw rate and more).

KAN_ uses the existing CANBUS network in your car to give you highest speed, detailed and accurate data, while also recording it locally for whatever you want to do with it.

As we said, OBD2 was never designed to support track level data logging into your phone using a cheap Bluetooth OBD2 adapter and a dated application. Because KAN_ can expose so many data points, with more to come, you can begin to extract actual insight from your laps and improve as a driver or identify areas of mechanical concern. Was it your braking characteristics, turn in point or throttle modulation that gained you a new PB? Were your temps or pressures struggling to keep up? With proper data comes proper insights.

Closed down systems are a bane to use, railroading users into less than optimal workflows that sap any joy or want to continue. KAN_ exists because I got so fed up spending half a weekend organising data before I could begin editing a YT video. So from the ground up, I wanted this system to be agnostic and user friendly. KAN_ by default generates a templated and consistent data file for every session, which is universal in its file type. No matter if you want to review your data in KAN_PITWALL, the dedicated review and overlay tool, or your favourite table based software or overlay software, KAN_ will always play nice.

Because KAN_ wants to play nice with everything, all data is time-synced through GPS, a trick I learnt in my day job as a control systems engineer. While KAN_ will log your position in space with GPS and allow you to display it, its main goal is to make sure that syncing action cam video or other data loggers — such as notable GPS lap timers — can be done accurately and reliably. For every frame of data, there is an exact UTC time code which you can use to match to the same time code saved in the metadata of most action cams and other devices. Trying to sync your data overlay and awesome footage in editing by hand is now a thing of the past (thank god). The example data you see on this page was matched to 0.9994 r correlation (0 being no match, 1 being perfect match) between GoPro and KAN_ hardware.